Skip to content
Commits on Jul 25, 2012
  1. @eyeballer @Whitehawkx

    surfaceflinger: fix filter for samsung omx patches

    Currently, any device that doesn't have TARGET_SOC
    defined is broken.
    
    Change-Id: I573e770b1857706773186ab6879c4c572f6115dd
    eyeballer committed with Whitehawkx Jul 22, 2012
  2. @xplodwild @Whitehawkx

    Add Samsung OMX and Color Format support (1/2)

    Change-Id: I842e5a84a81bdb39234162cdc262d9ce6ba2688e
    xplodwild committed with Whitehawkx Jul 15, 2012
Commits on Jul 20, 2012
  1. @AndroidMeda @Whitehawkx

    surfaceflinger: Enable dithering if persist.sys.use_dithering=1|2

    * Fixes color banding(1) and blur effect(2)
    
    0: surface doesn't need dithering
    1: enable dithering if necessary (default)
    2: enable dithering (always)
    
    Change-Id: Icda52b0b11ed3e2fa0db769d581582c23beb90fd
    AndroidMeda committed with Whitehawkx Jul 18, 2012
  2. @aleho @Whitehawkx

    Implement additional keycodes

        Adds keys for
    
        *) WLAN, Bluetooth, touchpad toggle,
        *) brightness down, up, auto and
        *) screenshot
    
        as found on docks for current Asus Transformer devices.
    
    Change-Id: Icf7141e559b6bd29cfbe28148944d2081a0dd525
    aleho committed with Whitehawkx Jul 15, 2012
Commits on Jul 15, 2012
  1. @labbott @cyanogen

    binder: add support for Ion

    Add classes to allocate from the Ion memory manager.
    
    Change-Id: I72ad0c95a06c47a5d7441f7f699ba1462e1b8632
    
    binder: Get rid of old flag
    
    MAP_LOCKED_MAP_POPULATE is an outdated flag that is not used
    anymore. Get rid of this flag in MemoryHeapIon
    
    Change-Id: Ib43d2a413f5177b98a66bf3ef1476db8caef56cd
    labbott committed with cyanogen Mar 4, 2012
Commits on Jul 13, 2012
  1. @rmcc

    Revert "get rid of MemoryHeapPmem"

    This reverts commit 7a75248 and
    makes MemoryHeapPmem conditioned to BOARD_NEEDS_MEMORYHEAPPMEM
    
    Change-Id: I2f38340984ba87d6970d17ec944e3faded4132c8
    rmcc committed Jul 13, 2012
  2. Fixed sample video corrupted in MediaCodec mode.

    Change-Id: Ibe11a83199f3db1ba6266a1a9e11c7fc24ceb554
    related-to-bug: 6732061
    Edwin Wong committed Jul 10, 2012
Commits on Jul 12, 2012
  1. @cyanogen

    Merge "MemoryHeapBase: ifdef for gingerbread/froyo compatibility" int…

    …o jellybean
    cyanogen committed with Gerrit Code Review Jul 12, 2012
Commits on Jul 11, 2012
  1. @tpruvot @AndroidMeda

    MemoryHeapBase: ifdef for gingerbread/froyo compatibility

    Allow to "revert" by a board config flag the offset member addon
    see commit f24c4cd0f20 (aosp change id Ie618fb5c0718e)
    
    This change is required to use overlay based proprietary camera libs
    coming from gingerbread and froyo builds.
    
    This change also requires a global cflag named BINDER_COMPAT
    because a lot of modules use the MemoryHeap includes
    
    Add this in your BoardConfig.mk :
    COMMON_GLOBAL_CFLAGS += -DBINDER_COMPAT
    
    Backported from /#/c/13317/
    
    Change-Id: I2e5c10d3cd9584803dd282aa17650661d6499e5b
    tpruvot committed with AndroidMeda Jul 11, 2012
  2. @TomGiordano @tilal6991

    surfaceflinger: allow 180 degree hardware rotation

    Change-Id: Id6991021701b15f2ce1e5513474238a09d8862bf
    TomGiordano committed with tilal6991 Jul 11, 2012
Commits on Jun 21, 2012
  1. merge in jb-release history after reset to jb-dev

    The Android Automerger committed Jun 21, 2012
Commits on Jun 20, 2012
  1. Exit boot animation cleanly.

    The desc.txt file can now mark parts as 'must finish cleanly' by using
    'c' as the part line prefix rather than 'p'.  If so indicated, if the
    bootanimation is asked to quit it will do so only after waiting to
    finish that part.
    
    I considered either making init.c service killing smarter or promoting
    bootanim to be a bindable service with a requestExit method.  However,
    these changes are probably too big/risky given our ship date.  So
    I used a property as a mailbox between SurfaceFlinger and bootanim.
    
    Bug: 6679877
    Change-Id: Id7dca22caa50b450fff25ca94f7242d971034f41
    Mathias Agopian committed Jun 19, 2012
Commits on Jun 16, 2012
  1. merge in jb-release history after reset to jb-dev

    The Android Automerger committed Jun 16, 2012
Commits on Jun 15, 2012
  1. SF could get stuck waiting for vsync when turning the screen off

    When turning the screen off we could have 2 waiters on the
    vsync condition: The main vsync waiter as well as one in
    onScreenReleased(). We were only signaling the condition though,
    so it it would be possible to wake onScreenReleased() without waking
    the main vsync thread which would then be stuck in .wait().
    
    We fix this by just using broadcast() when receiving a vsync event.
    
    We also add a broadcast() to signal when the state of
    mUseSoftwareVSync changes.  This is important particularly for
    the transition from hardware to software vsync because the main
    vsync waiter might have observed mUseSoftwareVSync == false
    and decided to block indefinitely pending a hardware vsync
    signal that will never arrive.
    
    Removed a potentially deadlocking wait for a signal in
    onScreenReleased().  The function was trying to wait for the last
    vsync event from the hardware to be delivered to clients but there
    was no guarantee that another thread would signal it to wake up
    again afterwards.  (As far as I can tell, the only other other
    thread that might wake it up at this point would be a client
    application issuing a vsync request.)  We don't really need to wait
    here anyhow.  It's enough to set the mUseSoftwareVSync flag,
    wake up the thread loop and go.  If there was a pending vsync
    timestamp from the hardware, then the thread loop will grab
    it and use it then start software vsync on the next iteration.
    
    Bug: 6672102
    Change-Id: I7c6abc23bb021d1dfc94f101bd3ce18e3a81a73e
    Mathias Agopian committed with The Android Automerger Jun 14, 2012
  2. @j9brown

    Merge "SF could get stuck waiting for vsync when turning the screen o…

    …ff" into jb-dev
    j9brown committed with Android (Google) Code Review Jun 15, 2012
  3. @j9brown

    SF could get stuck waiting for vsync when turning the screen off

    When turning the screen off we could have 2 waiters on the
    vsync condition: The main vsync waiter as well as one in
    onScreenReleased(). We were only signaling the condition though,
    so it it would be possible to wake onScreenReleased() without waking
    the main vsync thread which would then be stuck in .wait().
    
    We fix this by just using broadcast() when receiving a vsync event.
    
    We also add a broadcast() to signal when the state of
    mUseSoftwareVSync changes.  This is important particularly for
    the transition from hardware to software vsync because the main
    vsync waiter might have observed mUseSoftwareVSync == false
    and decided to block indefinitely pending a hardware vsync
    signal that will never arrive.
    
    Removed a potentially deadlocking wait for a signal in
    onScreenReleased().  The function was trying to wait for the last
    vsync event from the hardware to be delivered to clients but there
    was no guarantee that another thread would signal it to wake up
    again afterwards.  (As far as I can tell, the only other other
    thread that might wake it up at this point would be a client
    application issuing a vsync request.)  We don't really need to wait
    here anyhow.  It's enough to set the mUseSoftwareVSync flag,
    wake up the thread loop and go.  If there was a pending vsync
    timestamp from the hardware, then the thread loop will grab
    it and use it then start software vsync on the next iteration.
    
    Bug: 6672102
    Change-Id: I7c6abc23bb021d1dfc94f101bd3ce18e3a81a73e
    Mathias Agopian committed with j9brown Jun 14, 2012
  4. @j9brown

    Add ASSIST keycode.

    Bug: 6594275
    Change-Id: I032b055207d16bfff93ee8a350c0dc52b9102926
    j9brown committed Jun 15, 2012
Commits on Jun 12, 2012
  1. merge in jb-release history after reset to jb-dev

    The Android Automerger committed Jun 12, 2012
Commits on Jun 11, 2012
  1. Merge "reduce PB size from 2MB to 512KB" into jb-dev

    Mathias Agopian committed with Android (Google) Code Review Jun 11, 2012
  2. merge in jb-release history after reset to jb-dev

    The Android Automerger committed Jun 11, 2012
Commits on Jun 8, 2012
  1. @j9brown

    Merge "Include stack traces for certain native processes in bugreport…

    …." into jb-dev
    j9brown committed with Android (Google) Code Review Jun 8, 2012
  2. I am having second thoughts about 512m for the large heap size.

    Let's go with 384 megs, half way between the large heap size on
    Xoom and 512.
    
    Change-Id: I4a7f2e5a8b2920b49fa53777725e24811145f5f2
    Dianne Hackborn committed Jun 8, 2012
  3. @j9brown

    Include stack traces for certain native processes in bugreport.

    Bug: 6615693
    Change-Id: I64c3b3ce0bba62d9c332a795f7d979fb753dc27b
    j9brown committed Jun 7, 2012
  4. merge in jb-release history after reset to jb-dev

    The Android Automerger committed Jun 8, 2012
  5. sometimes we would incorrectly scale the content of a surface

    this would happen when a resize was pending (ie: we have received
    and processed a resize transaction but have not received a buffer
    with the right size) and a new transaction came in that didn't
    involve a resize, for instance a translate-only transaction.
    
    in this case, we would incorrectly update the drawing state
    with the pending size, eventhough we still don't have a buffer
    for it.
    
    the solution is quite simple, we never allow the size to propagate
    from current to drawing state during the regular transaction processing
    (unless we are in fixed-size mode -- meaning we don't need to have
    a matching size buffer), this propagation happens later once we
    receive the buffer.
    
    Bug: 6624163
    Change-Id: I11a97e4b88a7f3a0571ddcfe99c86cb04ce01a4d
    Mathias Agopian committed Jun 7, 2012
Commits on Jun 7, 2012
  1. merge in jb-release history after reset to jb-dev

    The Android Automerger committed Jun 7, 2012
Commits on Jun 6, 2012
  1. @jgennis

    Merge "SurfaceFlinger: remove all GLES scissor calls." into jb-dev

    jgennis committed with Android (Google) Code Review Jun 6, 2012
  2. reduce PB size from 2MB to 512KB

    this allows us to enable h/w acceleration on low-end
    devices while keeping memory usage down.
    
    Bug: 6557760
    Change-Id: I8af2de3038dc2579360b8b73aa452cb7a0e506a9
    Mathias Agopian committed Jun 5, 2012
  3. @jgennis

    SurfaceFlinger: remove all GLES scissor calls.

    Bug: 6576505
    Change-Id: I494b7627f2e271a234706bf49a9490f8ac56c77a
    jgennis committed Jun 4, 2012
  4. Add new Dalvik memory limit definition.

    This is for a 7in hdpi/tvdpi tablet with 1G of RAM.
    
    That sounds kind-of familiar.  I don't know.  Have I seen
    such a thing before?  Maybe.
    
    Bug: 6576049
    Change-Id: Iabc245692d5106feec9199eb2b5a3d06e27a9b83
    Dianne Hackborn committed Jun 5, 2012
Commits on Jun 5, 2012
  1. merge in jb-release history after reset to jb-dev

    The Android Automerger committed Jun 5, 2012
  2. sometimes SF would not process a surface resize

    this would happen when a window started with size A, was
    resized to B and immediately resized to A. In this situation
    the erquested and active size would be the same, and SF
    would think a transaction wasn't needed.
    
    we fix this by always comparing the requested sizes.
    
    Also, make sure to set mRefreshPending once we're sure
    we have succesfully called updateTexImage().
    
    Bug: 6580962
    Change-Id: I2c48b4df7f05fd35c9e1d2dd82095b0f3d5a0b6a
    Mathias Agopian committed Jun 4, 2012
Commits on Jun 3, 2012
  1. merge in jb-release history after reset to jb-dev

    The Android Automerger committed Jun 3, 2012
Commits on Jun 1, 2012
  1. @j9brown

    Merge "Support looper callbacks based on smart pointers." into jb-dev

    j9brown committed with Android (Google) Code Review May 31, 2012
  2. @j9brown

    Merge "Delete unused poll() code." into jb-dev

    j9brown committed with Android (Google) Code Review May 31, 2012
Something went wrong with that request. Please try again.