| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Dima Zavin <dima@android.com>
|
|
|
|
| |
architecture as camera services
|
|\
| |
| |
| |
| |
| |
| | |
Merge commit 'b8546001701405a76dad7e6235046e592296fac2'
* commit 'b8546001701405a76dad7e6235046e592296fac2':
Fix issue #2048263: More debugging information
|
| |
| |
| |
| |
| | |
We now hopefully do better about generating the anr reports, and include
information about the malloc loaded assets in meminfo.
|
| |
| |
| |
| | |
"SurfaceFlinger will now allocate buffers based on the usage specified by the clients. This allows to allocate the right kind of buffer automatically, without having the user to specify anything."
|
| |
| |
| |
| |
| |
| | |
specified by the clients. This allows to allocate the right kind of buffer automatically, without having the user to specify anything."
This reverts commit 8b76a0ac6fbf07254629ed1ea86af014d5abe050.
|
| |
| |
| |
| |
| |
| |
| | |
clients. This allows to allocate the right kind of buffer automatically, without having the user to specify anything.
This change makes SurfaceHolder.setType(GPU) obsolete (it's now ignored).
Added an API to android_native_window_t to allow extending the functionality without ever breaking binary compatibility. This is used to implement the new set_usage() API. This API needs to be called by software renderers because the default is to use usage flags suitable for h/w.
|
| | |
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
* changes:
update most gl tests to use EGLUtils
added two EGL helpers for selecting a config matching a certain pixelformat or native window type
added NATIVE_WINDOW_FORMAT attribute to android_native_window_t
|
| | |
| | |
| | |
| | | |
or native window type
|
| | | |
|
|/ /
| |
| |
| | |
Signed-off-by: Iliyan Malchev <malchev@google.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The major things going on here:
- The MotionEvent API is now extended to included "pointer ID" information, for
applications to keep track of individual fingers as they move up and down.
PointerLocation has been updated to take advantage of this.
- The input system now has logic to generate MotionEvents with the new ID
information, synthesizing an identifier as new points are down and trying to
keep pointer ids consistent across events by looking at the distance between
the last and next set of pointers.
- We now support the new multitouch driver protocol, and will use that instead
of the old one if it is available. We do NOT use any finger id information
coming from the driver, but always synthesize pointer ids in user space.
(This is simply because we don't yet have a driver reporting this information
from which to base an implementation on.)
- Increase maximum number of fingers to 10. This code has only been used
with a driver that reports up to 2, so no idea how more will actually work.
- Oh and the input system can now detect and report physical DPAD devices.
|
| |
| |
| |
| | |
hardware accelerated blitting.
|
|\ \
| | |
| | |
| | |
| | | |
* changes:
fixed some issues with the software renderer when surfaces are made current.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
there was several issues:
- when a surface was made non-current, the last frame wasn't shown and the buffer could stay locked
- when a surface was made current the 2nd time, it would not dequeue a new buffer
now, queue/dequeue are done when the surface is made current.
for this to work, a new query() hook had to be added on android_native_window_t, it allows to retrieve some attributes of a window (currently only width and height).
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | |
| | | |
Merge commit '25dff70f153529b87f5ad4a92f4de21e8950b1de'
* commit '25dff70f153529b87f5ad4a92f4de21e8950b1de':
Fix #2018814: System cannot correctly render assets with "wrap_content" attribute in QVGA
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
attribute in QVGA
It turns out we were not returning the density for anything retrieved from a
TypedArray... which basically means any bitmap references from a layout or style...!!!
This is now fixed.
Also fiddle with the density compatibility mode to turn on smoothing in certain situations,
helping the look of things when they need to scale and we couldn't do the scaling at
load time.
|
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| | |
Initial commit for review.
Integrated comments after patch set 1 review.
Fixed lockup in AudioFlinger::ThreadBase::exit()
Fixed lockup when playing tone with AudioPlocyService startTone()
|
|\ \
| | |
| | |
| | |
| | | |
* changes:
Make MemoryDealer's destructor protected instead of public.
|
| | |
| | |
| | |
| | | |
MemoryDealer, like all other subclasses of RefBase,MUST NOT BE stack-allocated, a protected destructor prohibits stack-allocation while allowing the baseclass to properly invoke the subclass' destructor once the refcount drops to 0.
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | |
| | | |
Merge commit '9fc20b0e381b5fe00b7049ef357c839cd05a33bf'
* commit '9fc20b0e381b5fe00b7049ef357c839cd05a33bf':
First pass at reworking screen density/size APIs.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This changes the names of the directories in aapt, to what you see
in the list of DpiTest resources. Also adds a new "long" configuration
for wide screens, which the platform sets appropriate, and introduces
a new kind of resizeability for not large but significantly larger
than normal screens which may have compatibility issues.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
* changes:
Hardware overlay support
|
| | |/
| |/|
| | |
| | | |
Enable hardware overlay support for camera and video playback use cases
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | |
| | | |
Merge commit 'aad0fcc9619eb72c18a6afff48ebc9d4011f0f54'
* commit 'aad0fcc9619eb72c18a6afff48ebc9d4011f0f54':
Add "nodpi" density, and expose a bunch of density-related APIs.
|
| | |
| | |
| | |
| | |
| | | |
Also update the DpiTest app to use nodpi images, and try to have a mode
where it turns off compatibility though it's not quite working.
|
| |/
|/|
| |
| |
| |
| |
| | |
This will be used to avoid unnecessarily listening to data from sensors
that function as event devices.
Signed-off-by: Mike Lockwood <lockwood@android.com>
|
|\ \
| | |
| | |
| | |
| | | |
* changes:
Implement virtual button support.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The kernel can now publish a property describing the layout of virtual
hardware buttons on the touchscreen. These outside of the display
area (outside of the absolute x and y controller range the driver
reports), and when the user presses on them a key event will be
generated rather than a touch event.
This also includes a number of tweaks to the absolute controller
processing to make things work better on the new screens. For
example, we now reject down events outside of the display area.
Still left to be done is the ability to cancel a key down event,
so the user can slide up from the virtual keys to the touch screen
without causing a virtual key to execute.
|
|/ /
| |
| |
| | |
by sf and af an soon will allow some optimization in the kernel for non shared mutexes
|
| |
| |
| |
| |
| | |
internally pthread uses futex. the implementation consists of simple inlines
there are no implementation files anymore.
|
|\ \
| |/
| |
| |
| |
| |
| | |
Merge commit '8a715b4b791db4390d12e0ded02280592634a424'
* commit '8a715b4b791db4390d12e0ded02280592634a424':
Add useful functions to String8, which enables users to convert between UTF-8 and UTF-32
|
| |\
| | |
| | |
| | |
| | | |
* changes:
Add useful functions to String8, which enables users to convert between UTF-8 and UTF-32 It will be used in SQL functions in external/sqlite/android. See https://android-git.corp.google.com/g/Gerrit#change,5511 for example.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
UTF-8 and UTF-32
It will be used in SQL functions in external/sqlite/android.
See https://android-git.corp.google.com/g/Gerrit#change,5511 for example.
Related internal bug id: 1707173
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
* changes:
resolved conflicts for merge of 04c7d0f8 to master
|
| |\ \ \
| | |/ / |
|
| | |/
| | |
| | |
| | | |
Bug 1927069.
|
|/ / |
|
|\ \
| | |
| | |
| | |
| | | |
* changes:
add a virtual destructor to region_rasterizer, to be on the safe side
|
| | | |
|
|/ /
| |
| |
| |
| | |
Looks like older gcc (4.1.x) doesn't properly handle templated
fanciness. Apparently that's what we have on the build server.
|
|\ \ |
|
| |\ \
| | |/
| | |
| | |
| | |
| | |
| | | |
Merge commit '991eec03a73f8803d0f8c80b418480ea25293cfb'
* commit '991eec03a73f8803d0f8c80b418480ea25293cfb':
Don't re-parse the framework resources all the time.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
A small optimization to the resource code, to not re-parse the framework
resources every time we build a new AssetManager. Instead, you can now
construct a ResTable from a previously created one... of course, like the
existing code for using the data in-place, you can't delete the original
ResTable until you have deleted the one that has been constructed from it.
|
| |\ \
| | |/
| | |
| | |
| | |
| | |
| | | |
Merge commit 'c7396025e59524e7ef639fd86fc23123939ee91c'
* commit 'c7396025e59524e7ef639fd86fc23123939ee91c':
Return CAMERA_ERROR_SERVER_DIED to camera app when camera service dies (bug 1956726)
|
| | |
| | |
| | |
| | | |
1956726)
|
| |\ \
| | |/
| | |
| | |
| | |
| | |
| | | |
Merge commit '6e1647a212317f4ee8bcc23948b6621a59172954'
* commit '6e1647a212317f4ee8bcc23948b6621a59172954':
Fix issue #1673793: Theme styles don't apply.
|