| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
DO NOT MERGE
Change-Id: Iae685158ac9c08e3a074e36d60004faf995fd1c7
|
|
|
|
|
|
| |
This reverts commit 7d7d4d6b86bdbfc54c63830351cf8d2f3830b68a.
Change-Id: I41e89bf297cb11db62601b3df0e6c655d7579007
|
|
|
|
| |
Change-Id: Iaab9d0965511d0394e7be29adb0fbcfd2904b857
|
|
|
|
|
|
| |
This reverts commit 99296a12c0d9a036518704610be07d3466b7e4b0.
Change-Id: Icf047da4ed344a86d84d1da7892a4303468919ca
|
|
|
|
| |
Change-Id: Icdf0e9238846f943db527becde92d38f362a9f32
|
|
|
|
| |
Change-Id: I94a611f4bdc2b9c7f305727aacf2edbe63b4ece7
|
|
|
|
|
|
| |
actually decent layout with images
Change-Id: I45047158b61d3d8202b0f77e1ff8aea9c57da7c5
|
|
|
|
| |
Change-Id: I1f5ab49236b85cd1bd46e8199e7fd6decad73064
|
|
|
|
| |
Change-Id: I5b333daa32ff9a50724151631661fab126b68704
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The existing code for notification manager/listeners uses a oneway
binder api to deliver messages. One problem with this is that
notification objects can sometimes get fairly large, and can bump
into the oneway binder transaction buffer if many happen at once.
To reduce this issue, flip the service into a oneway delivery of
a status bar notification holder, whose wrapped content is then
immediately fetched upon receipt of the one-way message. This moves
the meat of the fetch to be over a two-way interface without changing
the properties of which object is actually sent (a tickle solution
with lookup key would have changed this)
Further research: attempt to chunk notification objects themselves.
They can sometimes transfer hundreds of KB over a binder transaction.
Bug: 15426276
Change-Id: Ib1a1f4ff848c16f80bcf2ae4dfd2b87a9091f0b2
|
|\
| |
| |
| |
| |
| |
| | |
supported APIs that are not useful for 3rd party developers.
* commit 'e05077d78c9abde054a754db53e71c647b9a705c':
Added a private apis jar that includes explicitly supported APIs that are not useful for 3rd party developers.
|
| |\
| | |
| | |
| | |
| | |
| | |
| | | |
APIs that are not useful for 3rd party developers.
* commit '83da75d938d519bbcffb9c3b52802fd2daad4aee':
Added a private apis jar that includes explicitly supported APIs that are not useful for 3rd party developers.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
not useful for 3rd party developers.
The first set of these APIs is for telephony:
Added some APIs to ITelephony and created a first party framework for them
toggleHold()
merge()
mute(boolean mute)
playDtmfTone(char digit, boolean timedShortCode)
stopDtmfTone()
swap()
addListener(ITelephonyListener listener)
removeListener(ITelephonyListener listener)
Bug: 13302451
Change-Id: Iefec5688c26a1b4fe77f5643eba6e1690a057ee6
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This CL adds a system service handling HDMI-CEC protocol. The service
is equipped with the capability sending/receiving HDMI-CEC messages
Not all the messages are in place. Currently it has messages to support
a few features only, as follows:
- One touch play
- System information
- Routing control (partially - active source status maintenance only)
- Device OSD transfer
- Power status
It will be extended to cover the wider usages in the follow up CLs.
The CEC standard version referenced in the implementation is 1.3a.
Change-Id: Ifed0b02f52ebf098eddb3bd0987efbf353b7e8fe
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When a doze component has been specified in a config.xml resource
overlay, the power manager will try to start a preconfigured dream
whenever it would have otherwise gone to sleep and turned the
screen off. The dream should render whatever it intends to show
then call startDozing() to tell the power manager to put the display
into a low power "doze" state and allow the application processor
to be suspended. The dream may wake up periodically using the
alarm manager or other features to update the contents of the display.
Added several new config.xml resources related to dreams and dozing.
In particular for dozing there are two new resources that pertain to
decoupling auto-suspend mode and interactive mode from the display
state. This is a requirement to enable the application processor
and other components to be suspended while dozing. Most devices
do not support these features today.
Consolidated the power manager's NAPPING and DREAMING states into one
to simplify the logic. The NAPPING state was mostly superfluous
and simply indicated that the power manager should attempt to start
a new dream. This state is now tracked in the mSandmanSummoned field.
Added a new DOZING state which is analoguous to DREAMING. The normal
state transition is now: AWAKE -> DREAMING -> DOZING -> ASLEEP.
The PowerManager.goToSleep() method now enters the DOZING state instead
of immediately going to sleep.
While in the doze state, the screen remains on. However, we actually
tell the rest of the system that the screen is off. This is somewhat
unfortunate but much of the system makes inappropriate assumptions
about what it means for the screen to be on or off. In particular,
screen on is usually taken to indicate an interactive state where
the user is present but that's not at all true for dozing (and is
only sometimes true while dreaming). We will probably need to add
some more precise externally visible states at some point.
The DozeHardware interface encapsulates a generic microcontroller
interface to allow a doze dream for off-loading rendering or other
functions while dozing. If the device possesses an MCU HAL for dozing
then it is exposed to the DreamService here.
Removed a number of catch blocks in DreamService that caught Throwable
and attempted to cause the dream to finish itself. We actually just
want to let the process crash. Cleanup will happen automatically if
needed. Catching these exceptions results in mysterious undefined
behavior and broken dreams.
Bug: 12494706
Change-Id: Ie78336b37dde7250d1ce65b3d367879e3bfb2b8b
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
groups and landing pages.
* commit '9c50271dc34e48d527db7da85c3b3474574faee2':
Doc change: add new samples TOC groups and landing pages.
|
| |\ \ \
| | |/ /
| | | |
| | | |
| | | |
| | | |
| | | | |
pages.
* commit '257f67249afb017c9a3d0a79e545da567aa5bd02':
Doc change: add new samples TOC groups and landing pages.
|
| | |\ \
| | | | |
| | | | |
| | | | |
| | | | | |
* commit '35cb4e49365a8a8da0607c2659399aaad9ea5a1c':
Doc change: add new samples TOC groups and landing pages.
|
| | | | |
| | | | |
| | | | |
| | | | | |
Change-Id: I2f39e82fb79d4f19362d9fe2deafdde5d87873a7
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- Introduce concept of ActivityStacks residing on Displays and able
to be decoupled and moved around.
- Add a new interface, IActivityContainer for clients to handle
ActivityStacks.
- Abandon ordering of stacks based on mStackState and instead use
ActivityDisplayInfo.stacks<ActivityStack> ordering.
Progress towards closing bug 12078972.
Change-Id: I7785b61c26dc17f432a4803eebee07c7415fcc1f
|
|\ \ \ \
| |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | | |
functions."
* commit 'dcbde1b02ad69c18509afd87974c72c3a22f45dd':
libcore_to_document and junit_to_document are no longer functions.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
They are evaluated only once in the corresponding export .mk file.
This fixes build log spam reported in:
https://code.google.com/p/android/issues/detail?id=63184
Change-Id: I549eb052272bbdebef8fca697822f5eaa0fe5764
|
|\ \ \ \
| | |/ /
| |/| |
| | | |
| | | | |
* commit '6000f1ed3d402e3136df173d987c901cc3cc1ff2':
Re-enable samples browser.
|
| | | |
| | | |
| | | |
| | | | |
Change-Id: I9d0c5966422ba0cf8bca576895f30679d40a19ab
|
|\ \ \ \
| |/ / /
| | | |
| | | |
| | | | |
* commit '9eaa94439121f6cb03bff8ecf0acbcbc74442f2d':
Disable samples browsing temporarily.
|
| | | |
| | | |
| | | |
| | | | |
Change-Id: I65fe533f1b43903d6605d17691ec142d062b6b5e
|
|\ \ \ \
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | | |
point for generating samples browsing files. Removes older project-based configuration." into klp-docs
* commit '1448d3cd81a685c68b0102e8303c0db4e6e5668f':
Pass a new samplesdir param to doclava as the starting point for generating samples browsing files. Removes older project-based configuration.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
samples browsing files. Removes older project-based configuration.
Change-Id: If59372a92f0572d54af0f2ed7f9f9e401fbce067
|
|\ \ \ \
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | | |
output remains the same for online, offline, and ds docs." into klp-docs
* commit 'acca12faea5fc1c9de63fdc08ae4d6bc0bad864a':
Doc change: move localized files into an intl dir. Build output remains the same for online, offline, and ds docs.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
same for online, offline, and ds docs.
Change-Id: Ia75712323563cf56f0224822cb7977f3421f8527
|
|\ \ \ \
| | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | | |
displays." into klp-dev
* commit 'd40a4d74c623175c96a2e9d865a99826e56d1132':
Add media router service and integrate with remote displays.
|
| |\ \ \
| | | | |
| | | | |
| | | | | |
klp-dev
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This change adds a new media router service whose purpose is to track
global state information associated with media routes. This service
publishes routes to the media router instance in application processes
and handles requested state changes such as selecting or unselecting
global routes. The service also binds to remote display provider
services which can offer new remote display routes to the system.
Includes a test application for manually verifying certain aspects
of the operation of the media router service.
The remote display provider interface is essentially a stripped down
media route provider interface as defined in the support library
media router implementation. For now, it is designed to be used only
by first parties to publish remote display routes to the system so
it is not exposed as public API in the SDK. In the future, the remote
display provider interface will most likely be deprecated and replaced
with a more featureful media route provider interface for third
party integration, similar to what is in the support library today.
Further patch sets integrate these new capabilities into the System UI
and Settings for connecting remote displays.
Bug: 11257292
Change-Id: I31109f23f17b474d17534d0f5f4503e388b081c2
|
|\ \ \ \ \
| |/ / / /
| | | / /
| |_|/ /
|/| | |
| | | |
| | | | |
into klp-dev
* commit '1f7a8a06256907e03405f89108f081289c23e97a':
Add a platform library for remote display providers.
|
| |\ \ \
| | |/ / |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This interface allows applications to register services that offer
remote displays to the system. The system will then provide UI
to allow user to connect to these displays and enable mirroring.
Bug: 11257292
Change-Id: I34da5b9dfdaf71267bd3450c505bc1b7368d1b40
|
| | | |
| | | |
| | | |
| | | | |
Change-Id: Ic47ef693dd5b2cd4010e68a600cae3b88d426bd2
|
| | | |
| | | |
| | | |
| | | | |
Change-Id: I9916113fde67afa04789f451355da215f9b015f7
|
| | | |
| | | |
| | | |
| | | | |
Change-Id: I76f1e64f68b9db7c39ab3ec9bbbe0ecdd7729ae6
|
|/ / /
| | |
| | |
| | | |
Change-Id: Ic47ef693dd5b2cd4010e68a600cae3b88d426bd2
(cherry picked from commit e8b32feb72bf4347c1bd98e6b21b18a506d2c5e3)
|
|/ /
| |
| |
| | |
Change-Id: I5f0c6899a34ada9f8dfc492f849c9e03203bc920
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. For an app to print it creates a PrintDocumentAdapter implementation
which is passed to the print dialog activity. If the activity that
created the adapter is destroyed then the adapter, which may rely on
the activity state, may be in an invalid state. For example, an app
creates an adapter and calls print resuting in the app activity and
the print dialog activity being stacked. Now the user rotates the
device which triggers the recreating of the activity stack (assume the
app does not handle rotation). The recreated print dialog activity
receives the intent that originally created it with containing the
adapter that was constructed in the context of the old, now destroyed,
app activity instance.
To handle this we are limiting an app to be able to print only from
and activity and when this activity is destroyed we mark the adapter
as invalid which will result in hiding the print dialog activity. Note
that if the app process is killed we already handle this in the print
dialog activiy by registering a death recipient on the adapter binder.
2. In the PrintManager.PrintDocumentAdapterDelegate some of the state is
accessed only on the main thread and some from miltiple threads. The
code was trying to avoid locking for state that is not accessed by
multiple threads but this is error prone and the benefit does not
justify the complexity and added fragility. Now grabbing a lock all
the time.
3. The PrintJobConfigActivity waits for it to bind to the print spooler
service before instantiating its print controller and editor. However,
these can be accessed by invoking some of the activity cycle callbacks.
This change is adding null checks for the case where the activity
callbacks are called before the binding to the spooler is completed.
bug:11242661
Change-Id: Id906b3170e4f0a0553772dfa62686f06fdca0eaf
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. Before the print job activity was started asyncronously with
respect to the print call on to the print manager. This was
creating a situation where the starting activity may finish
before the print dialog appears which may lead to an orphaned
print document adapter with no data to print (as the UI is
is gone), or strange behaviors where the print dialog starts
on as a separate task.
To address this the pending intent for starting the print
dialog is not started by the print spooler since we cannot
call into it synchronously as we have to start its process
and bind to the spooler service which leads to jankyness in
the client app. Now the pending intent is created by the
print manager service in the synchronous print call so
from an app's perspective calling print starts the activity.
The side effect of this design is that the print dialog
activity may start before the system is bound to the spooler
service. In such a case the print activity cannot start
poking the print spooler state as the system registers
callback to observe the spooler state. To address this
the print spooler activity disables the UI and also binds
to the spooler service which happenes immediately after it
is started. As soon as the print dialog binds to the
service it starts the UI.
2. Fixed an bug in the printer adapter of the print dialog that
was leading to a crash if the only item in the adater is the
all pritners option and it is selected.
3. Piping the package name that started the printing so we can
pass it to the storage UI as a hint to open the last location
the app used.
bug:11127269
Change-Id: Ia93820bdae0b0e7600a0930b1f10d9708bd86b68
|
|
|
|
| |
Change-Id: I881510209a56204a464df082840d2dde56312303
|
|
|
|
| |
Change-Id: I96e7e31f93b1e3c3877a342b84fb069bda5d92e3
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Add directory containing android/provider/Telephony.java to build.
Add unhidden Telephony fields and classes to api/current.txt.
Bug: 10653081
Change-Id: Ib4ba66e09be5320d35257fcf481db58f840fdc53
|
|/
|
|
|
|
|
|
| |
This is needed for implementing the print job settigns UI.
bug:10935736
Change-Id: I63b42cbf4ce6a259fa1af47fa368b148ca5621c1
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This changes the PAC support to not broadcast the Proxy information until
the Local Proxy has started up and successfully bound to a port so that
the local proxy information can be guaranteed to be owned by the proxy.
Bug: 10459877
Change-Id: I175cd3388c758c55e341115e4a8241884b90d633
|