summaryrefslogtreecommitdiffstats
path: root/libs
Commit message (Collapse)AuthorAgeFilesLines
* Textured text calls could be invisibleRomain Guy2012-06-112-0/+5
| | | | | | | | | | | | | | | | | | | | | | | Bug #6597730 Text would sometimes not appear when rendered with textured content (BitmapShader, LinearGradientShader, etc.) This was due to a misuse of OpenGL texture unit in FontRenderer. Textured text normally uses two texture units: - texture unit 0 for the font cache - texture unit 1 for the textured content (gradient, etc.) Recent changes to the font renderer allow it to bind new textures while processing the text's geometry (this happens when caches get full or when switching font size for instance.) The bindings were done without ensuring the texture unit was the correct one (unit 0), thus replacing the content of another texture unit (unit 1). This lead to text being drawn using the font cache itself as the content texture, making the text invisible. Change-Id: I392b4c884f09223305f6cbc6253e2ef9a98944c9
* Track canvas clearing for swap buffers logic.Chet Haase2012-06-076-11/+15
| | | | | | | | | | | | | | | | A previous fix made it necessary for a frame to render something to GL in order to cause a call to eglSwapBuffers(). Besides the calls being tracked as part of issuing a DisplayList, there is also a potential call to clear the canvas (via glClear()) on non-opaque surfaces. This call is also good to track, since a surface that gets cleared without any other drawing operations is worth flipping to the screen (to erase old contents on that surface). This fix tracks the status of the pre-draw operations to find out whether glClear() was called and then sets the drawing status appropriately. Issue #6606422 QuickContact dismissal is janky again (Tracking) Change-Id: I5fcaccfdc9293dd46b83f2fc279730a5d2740ebf
* Revert "Add more temporary logging for investigating detachFunctor"Chris Craik2012-06-061-5/+2
| | | | | | | | bug:6608646 This reverts commit 8857b2f76abad1e4ec742dfd85d0c997880be376 Change-Id: I1563b5974c52b84201ae448298f804eb0dcc235d
* Add more temporary logging for investigating detachFunctorChris Craik2012-06-051-2/+5
| | | | | bug:6596807 Change-Id: Ic9e34e323b12a887f2e8df0773a6155627b6a64f
* Port the legacy velocity tracker strategy.Jeff Brown2012-06-041-0/+126
| | | | | | | | For comparison purposes, port the legacy velocity tracker algorithm as it behaved prior to ICS. Bug: 6413587 Change-Id: I7e8e56584dcdb1a3c660ca9d8f9c5bd5d868e449
* Implement a second order integrating VT strategy.Jeff Brown2012-06-041-11/+37
| | | | | Bug: 6413587 Change-Id: I51bc7b8cbff22b10b728fc84ee15370e9984dd55
* Implement a weighted least squares VelocityTracker strategy.Jeff Brown2012-06-041-21/+126
| | | | | | | No change to the default strategy. Bug: 6413587 Change-Id: I08eb6f9a511e65ad637359b55b5993c26ba93b40
* Merge "Implement an integrating VelocityTracker strategy." into jb-devJeff Brown2012-06-031-0/+104
|\
| * Implement an integrating VelocityTracker strategy.Jeff Brown2012-06-031-0/+104
| | | | | | | | | | | | | | | | | | | | | | This algorithm better tolerates certain kinds of errors in the touch input than the least squares strategy but it may underestimate the velocity of accelerating movements. This algorithm is mainly of interest as a baseline for testing and comparison with the least squares algorithm, which remains the default. Bug: 6413587 Change-Id: I8ddb50084e44875e234717907e5b06d03f59788c
* | Merge "Make velocity tracker strategy configurable." into jb-devJeff Brown2012-06-031-17/+74
|\ \ | |/
| * Make velocity tracker strategy configurable.Jeff Brown2012-06-031-17/+74
| | | | | | | | | | | | | | | | | | | | This change is very useful for testing purposes because it makes it easy to compare different implementations to see how they behave. There is no change to the current default strategy. Bug: 6413587 Change-Id: I4d8567aa4160571ba9fa397ce419882cd9366749
* | Skip eglSwapBuffers() call when we do not draw to GLChet Haase2012-05-314-147/+202
|/ | | | | | | | | | The fix is to track when we issue GL drawing commands, and to skip the call to eglSwapBuffers() when a DisplayList does not result in any actual rendering calls to GL. Issue #6364143 QuickMuni list items and buttons flicker instead of fade Change-Id: I60a02c61a58c32d92481a1e814b4c8a49c6a37a3
* Merge "Avoid crash if onDetachedFromWindow called after destroy" into jb-devChris Craik2012-05-221-2/+1
|\
| * Avoid crash if onDetachedFromWindow called after destroyChris Craik2012-05-221-2/+1
| | | | | | | | | | | | | | | | This also removes the temporary logging from commit f8dafa14e058cdc2f408b59be7911abaceb73c47. bug:6535911 Change-Id: Icf1d0438b349a0e92e7d9cefed57a252eed2b9b0
* | Merge "Add temporary functor lifetime logging" into jb-devChris Craik2012-05-221-1/+2
|\ \ | |/
| * Add temporary functor lifetime loggingChris Craik2012-05-221-1/+2
| | | | | | | | | | | | bug:6535911 Change-Id: Ida5cc1def7fe1fc314317bbc5df50e1465753deb
* | Merge "Ensure we always set the proper blending mode Bug #6527305" into jb-devRomain Guy2012-05-223-10/+24
|\ \ | |/ |/|
| * Ensure we always set the proper blending modeRomain Guy2012-05-223-10/+24
| | | | | | | | | | | | | | | | | | | | Bug #6527305 At the beginning of a frame, always set the blending mode that we think GL is using just in case it was modified by another entity (for instance a WebView functor.) Change-Id: I0e1d0abee8a2abb2b8e7622aed28346e89562c06
* | Don't clear the functor at every drawChris Craik2012-05-221-1/+2
|/ | | | | | | instead clear functors at invoke time, and let them detach themselves as needed. bug:6511995 Change-Id: I9115fcadffb27eb850c1d1773c098d3d2e22788b
* Sanitize display list propertiesRomain Guy2012-05-183-14/+11
| | | | | | | | | | | The comparisons used in the various properties setters could fail badly in some specific conditions. The scale properties in particular did not use the same comparisons. This change also clamps alpha to the 0..1 range which avoids overflow issues with lowp registers in GLSL computations. Change-Id: I3e73b584e907a14e2c33d0865ca0d2d4d5bff31d
* Avoid unnecessary copy when invoking drawBitmap(int[])Romain Guy2012-05-155-35/+55
| | | | | | Bug #6483390 Change-Id: I4d2d725ef50c9401b4bd998b6160128102b40745
* Merge "Remove all Dalvik allocations from Cavnas.drawBitmap(int[], ...)" ↵Romain Guy2012-05-146-9/+91
|\ | | | | | | into jb-dev
| * Remove all Dalvik allocations from Cavnas.drawBitmap(int[], ...)Romain Guy2012-05-146-9/+91
| | | | | | | | Change-Id: Ie28538a2104d21154fdc78a56525e7403f08287d
* | Merge "Detect when pointer has stopped moving." into jb-devJeff Brown2012-05-141-6/+25
|\ \
| * | Detect when pointer has stopped moving.Jeff Brown2012-05-141-6/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some input devices do not generate ACTION_MOVE events while all pointers have stopped, thereby lulling the VelocityTracker into a false sense of complacency. Before handling the following sample, reset the VelocityTracker state so as not to be influenced by earlier samples before the pointer stopped. The velocity after stopping is assumed to be discontinuous. Bug: 6413587 Change-Id: I6387bc036ff141d083d3d17a89e37eeaa3188349
* | | Merge "Fix pointer indexing issue in VelocityTracker." into jb-devJeff Brown2012-05-141-6/+13
|\ \ \ | |/ /
| * | Fix pointer indexing issue in VelocityTracker.Jeff Brown2012-05-141-6/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | VelocityTracker was implicitly assuming that the pointer ids in a MotionEvent were ordered. That is not necessarily the case so we need to be careful while copying the pointer coordinates out. Bug: 6413587 Change-Id: I3b23a954f893eebdf786f2a94207149b092ef036
* | | Merge "Improve touch event resampling." into jb-devJeff Brown2012-05-142-67/+153
|\ \ \ | |/ /
| * | Improve touch event resampling.Jeff Brown2012-05-142-67/+153
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixed a few bugs related to the id-to-index mapping for pointer coordinates. Tightened the bounds on the resampling time interval to avoid predicting too far into the future. Only lerp X and Y components of motion events. Alter the future to satisfy past predictions. (Rewrite touch events to conceal obvious discontinuities.) Added a system property to control whether resampling is enabled for debugging purposes. Bug: 6375101 Change-Id: I35972d63278bc4e78148053a4125ad9abeebfedb
* | | Merge "More VelocityTracker refactoring." into jb-devJeff Brown2012-05-141-49/+89
|\ \ \ | |/ / | | / | |/ |/|
| * More VelocityTracker refactoring.Jeff Brown2012-05-131-49/+89
| | | | | | | | | | Bug: 6413587 Change-Id: Ida1152e7a34d5fe5caab5e6b5e1bc79f6c7a25e6
* | Forget the name of a texture after freeingRomain Guy2012-05-142-6/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Bug #6408362 FontRenderer allocates large font textures when more room is needed to store all the glyphs used by an application. Thse large textures are the first to be freed when memory needs to be reclaimed by the system. When freeing a texture, the renderer would however not set the texture name to an invalid name, leading future allocations to be performed on the same texture name. That name could have by then be recycled by the driver and returned by a call to glGenTexture and used to create an entirely different texture. This would cause the font renderer to point to the wrong texture, thus leading to the "corruptions." Change-Id: I8a1e80e5b79e8f21d1baf5320c090df4f2066cd4
* | Fix two memory leaksRomain Guy2012-05-142-17/+30
| | | | | | | | | | | | Bug #6408362 Change-Id: I58543938e7b64d83504e11e97b0dd21ef8ebf3b6
* | Properly pre-cache latin glyphsRomain Guy2012-05-142-14/+17
|/ | | | | | Bug #6408362 Change-Id: Ie11644c5a9e2d87d3b851b7e619e5f04b60a7e02
* Add call sites for OpenGL's debug label extensionRomain Guy2012-05-123-22/+53
| | | | Change-Id: I9c689127e8166cbef92c935f8aa07217ab806dda
* Minor refactoring before starting on velocity tracker changes.Jeff Brown2012-05-114-508/+558
| | | | | Bug: 6413587 Change-Id: I5eba2bb57193bff78cb3740de5f87aca0b31d154
* Merge "Revert "Add temporary functor lifetime logging"" into jb-devChris Craik2012-05-081-1/+0
|\
| * Revert "Add temporary functor lifetime logging"Chris Craik2012-05-081-1/+0
| | | | | | | | | | bug:6445573 This reverts commit 2fe99801e81bb7c0ff846b536cbb7a12707410ed
* | Merge "Fix issue where scale-animating text would jump temporarily a few ↵Chet Haase2012-05-072-8/+5
|\ \ | | | | | | | | | pixels" into jb-dev
| * | Fix issue where scale-animating text would jump temporarily a few pixelsChet Haase2012-05-072-8/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some logic in the native matrix code would determine that a matrix was 'pureTranslate' based on the scale values of a matrix being close-enough to 1, which was within a very small epsilon. This works in general, because screen space coordinates make that epsilon value irrelevant, so close-enough really is close-enough. However, TextView, when centering text, works in a coordinate system that is quite huge, with left/right values about 500,000. These numbers multiplied times that small epsilon value would give a result that was significant, and would cause a miscalculation of up to 4-5 pixels, causing the snap that we'd see for a couple of frames as the scale got "close enough" to 1. The fix is to remove the optimization of "close enough". What we really need the matrix to do is to identify itself as being translate-only when no scale as been set (which is the default). For the purposes of that check, it is good enough to simply check the values against 1 directly. Similarly, the bounds-check logic needs to check against 0 and 1 directly. Issue #6452687: Glitch when changing scale of a view containing text Change-Id: I167fb45d02201fb879deea0e5a7ca95e38128e17
* | | Fix hang/crash in native path codeChet Haase2012-05-032-0/+27
| |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | An optimization for paths is to only create a texture for the original native Path object, and have all copies of that object use that texture. This works in most cases, but sometimes that original path object may get destroyed (when the SDK path object is finalized) while we are still referencing and using that object in the DisplayList code. This causes undefined errors such as crashes and hanging as we iterate through the operations of a destroyed (and garbage-filled) path object. The fix is to use the existing ResourceCache to refcount the original path until we are done with it. Issue #6414050 Analytics Dogfood App crashes reliably on Jellybean Change-Id: I5dbec5c069f7d6a1e68c13424f454976a7d188e9
* | Add temporary functor lifetime loggingChris Craik2012-05-021-0/+1
| | | | | | | | | | | | | | | | bug:6405861 Note: revert once the above bug is verified fixed Change-Id: Iae04ec6ffa73a2711f96e128d60011bcb5864b5c
* | Merge "Improve handling of built-in keyboard." into jb-devJeff Brown2012-05-011-3/+4
|\ \ | |/ |/|
| * Improve handling of built-in keyboard.Jeff Brown2012-05-011-3/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The window manager policy made some incorrect assumptions about the meaning of the Configuration.keyboard field. We need to be more careful about distinguishing between built-in and external keyboards. Most of this change is to move the determination of the parts of the Configuration related to input devices into the WindowManagerService leveraging new features of the InputManagerService to good effect. Then we plumb through the flag that indicates whether a device is internal or external so that we can be more particular about how the lid switch effects changes to the Configuration. Bug: 6424373 Change-Id: I36a1c22ade35e578955465a25940a33f227b9763
* | Fix launcher invisibility bugChet Haase2012-05-011-2/+2
|/ | | | | | | | | | | | | | | | | | There was a bug in the DisplayList code for layers where we would set the alpha value for a layer only if the alpha were non-1. This works most of the time (since the value is usually 1 and doesn't need to be set at all, and if the value is non-1, it is set correctly). But when the value has been set to a non-1 value, setting alpha back to 1 cannot happen due to this logic. This caused launcher to have some invisible pages when returning to Home because those pages previously had an alpha value of 0, and setting the alpha to 1 had no effect due to this DisplayList code. The fix is to simply remove the check for non-1 values; we should always set the alpha value of layers to handle all cases. Issue #6413892 alpha value is messed up after AlphaAnimation Change-Id: Ia51acb2eaaf0609ea7189998ed449bdd9ea7e05f
* Merge "Resample touch events on frame boundaries." into jb-devJeff Brown2012-04-273-51/+302
|\
| * Resample touch events on frame boundaries.Jeff Brown2012-04-273-51/+302
| | | | | | | | | | Bug: 6375101 Change-Id: I8774e366306bb2b6b4e42b913525bf25b0380ec3
* | Merge "Work-around for a Skia rasterization bug Bug #6411457" into jb-devRomain Guy2012-04-273-38/+108
|\ \
| * | Work-around for a Skia rasterization bugRomain Guy2012-04-273-38/+108
| | | | | | | | | | | | | | | | | | | | | | | | | | | Bug #6411457 Skia does not generates the bottom right pixel of a rect when drawing a rect as an SkPath into an alpha8 bitmap. Change-Id: Ifb5286ae67745c9e44ee387b6d6ad607a9a2e6ce
* | | Merge "Decode common GL error codes when logging frame error status" into jb-devRomain Guy2012-04-261-1/+10
|\ \ \ | |/ /
generated by cgit v1.1 at 2025-01-12 08:11:40 +0000