| da5b6f2dc4ba23b6b70209f9b34fb39c93a51fc4 |
14-Aug-2013 |
John Spurlock <jspurlock@google.com> |
Normalize dream service dump check with other services.
Bug:10310128
Change-Id: Ieeeccc01832b569cf7fb3d1633d7dde60fceb7b2
reamManagerService.java
|
| a00271533f639c8ed36429c663889ac9f654bc72 |
25-Jun-2013 |
Svetoslav Ganov <svetoslavganov@google.com> |
Refactoring of the print sub-system and API clean up.
1. Now a user state has ins own spooler since the spooler app is
running per user. The user state registers an observer for the state
of the spooler to get information needed to orchestrate unbinding
from print serivces that have no work and eventually unbinding from
the spooler when all no service has any work.
2. Abstracted a remote print service from the perspective of the system
in a class that is transparently managing binding and unbinding to
the remote instance.
3. Abstracted the remote print spooler to transparently manage binding
and unbinding to the remote instance when there is work and when
there is no work, respectively.
4. Cleaned up the print document adapter (ex-PrintAdapter) APIs to
enable implementing the all callbacks on a thread of choice. If
the document is really small, using the main thread makes sense.
Now if an app that does not need the UI state to layout the printed
content, it can schedule all the work for allocating resources, laying
out, writing, and releasing resources on a dedicated thread.
5. Added info class for the printed document that is now propagated
the the print services. A print service gets an instance of a
new document class that encapsulates the document info and a method
to access the document's data.
6. Added APIs for describing the type of a document to the new document
info class. This allows a print service to do smarts based on the
doc type. For now we have only photo and document types.
7. Renamed the systemReady method for system services that implement
it with different semantics to systemRunning. Such methods assume
the the service can run third-party code which is not the same as
systemReady.
8. Cleaned up the print job configuration activity.
9. Sigh... code clean up here and there. Factoring out classes to
improve readability.
Change-Id: I637ba28412793166cbf519273fdf022241159a92
reamManagerService.java
|
| 27b89e6658a0d233a53f5d7ca20dc57fec82d955 |
16-Jan-2013 |
Amith Yamasani <yamasani@google.com> |
Rename bindService to bindServiceAsUser to follow convention.
This is for the multi-user version of bindService, not the original.
Change-Id: Ib2de35941196accf387b1a276a77e6f9af805ec0
reamController.java
|
| f5df689aa65682ce9217405e4a6b686e94129e8f |
14-Dec-2012 |
John Spurlock <jspurlock@google.com> |
Fix NPE inside DreamManagerService.
Bug:7741911
Change-Id: Icfc39b2d89f57bba79866030df85b822e3f73ae2
reamManagerService.java
|
| bbdb062d98275f6833ebc2f0998b9e2a6534cecb |
11-Dec-2012 |
John Spurlock <jspurlock@google.com> |
Fallback to default dream if the current dream is removed.
To minimize fix size, return only valid dreams from the service api.
Settings will "just work" with no changes.
Bug:7699398
Change-Id: I3eb88237a8ccc421fdb68d1de19820614b13d7b8
reamManagerService.java
|
| 006f567c214d67752cc7c2b6446c328744f40af7 |
03-Dec-2012 |
John Spurlock <jspurlock@google.com> |
Kill dreams that do not create a timely service connection.
Implement a timeout between when the dream binds and
when the dream creates the service connection. If
the connection is not created within a certain amount of
time, stop the dream.
This fixes the current bug where a dream that crashes in
onCreate (or the ctor) can put the dream controller in a
bad state until the screen is turned off.
The timeout is equal to the service restart delay in
activity manager (ActiveServices) to avoid restarting
(and recrashing).
Bug:7596707
Change-Id: I3e11efc6af0b79ec4cb0fbc94e4e109c7602ddac
reamController.java
|
| 40e9f2922cae76ffcbc521481e5be8e80e8744ef |
28-Nov-2012 |
Dianne Hackborn <hackbod@google.com> |
Quiet down a lot of logging.
Also fix a little problem where the USER_STARTED broadcasts
were not being sent as ordered broadcasts(!).
Change-Id: I3aa3e0a9b3900967cdd2d115ee103371b0a50c41
reamManagerService.java
|
| cd75706117432e33d11639e675bcff50479a6bb9 |
20-Oct-2012 |
Amith Yamasani <yamasani@google.com> |
System server should always send broadcasts to a specific or all users
Bug: 7368245
Log a warning if the system process calls unqualified sendBroadcast()
and other calls.
As a result of the logging above, found a few more method calls such as
bindService() that would benefit from being more explicit to avoid
future confusion and reduce the log warnings.
Change-Id: I17f15c8be9adf7becd456d6abbab606f19befdbf
reamController.java
|
| 2d78490292090eeab84694330978c9ad7fad2d37 |
04-Oct-2012 |
Daniel Sandler <dsandler@android.com> |
DreamService API revisions.
Reduce reliance on Service interface overrides, instead
steering clients to the DreamService-specific lifecycle
hooks:
onAttachedToWindow .. onDreamingStarted ..
onDreamingStopped .. onDetachedFromWindow
The old Dream.java is finally gone now too.
Bug: 7281802
Change-Id: Ib7802c3397fde60ad1132fa49831da182eef4d7a
reamController.java
|
| be87e2f5885b28145a788fd31d1fb5ae88a71100 |
29-Sep-2012 |
Dianne Hackborn <hackbod@google.com> |
Fix issue #7255954: API Review: rename Dream to DreamService
Change-Id: I89ecf2c3ec4fef09c0495aa68de11576f9cfd872
reamController.java
|
| 591a9e8d6ef2cab3ab3a701bd6279b6c12e6e4c6 |
28-Sep-2012 |
John Spurlock <jspurlock@google.com> |
Close the notification shade when starting dream.
Bug:7205491
Change-Id: I17d2b75bc502ff8fb739a6cbb4d0219681fa4e8a
reamController.java
|
| 62c82e4d92cc0b856059f905d81885f7808a0e7d |
26-Sep-2012 |
Jeff Brown <jeffbrown@google.com> |
Make DreamManagerService more robust.
Clearly isolated the DreamManagerService and DreamController
responsibilities. DreamManagerService contains just enough logic to
manage the global synchronous behaviors. All of the asynchronous
behaviors are in DreamController.
Added a new PowerManager function called nap() to request the device
to start napping. If it is a good time to nap, then the
PowerManagerService will call startDream() on the DreamManagerService
to start dreaming.
Fixed a possible multi-user issue by explicitly tracking for
which user a dream service is being started and stopping dreams
when the current user changes. The user id is also passed to
bindService() to ensure that the dream has the right environment.
Fix interactions with docks and the UI mode manager. It is
important that we always send the ACTION_DOCK_EVENT broadcast
to the system so that it can configure audio routing and the like.
When docked, the UI mode manager starts a dock app if there is
one, otherwise it starts a dream.
This change resolves issues with dreams started for reasons other
than a user activity timeout.
Bug: 7204211
Change-Id: I3193cc8190982c0836319176fa2e9c4dcad9c01f
reamController.java
reamManagerService.java
|
| cef440f2a2bb8b6e8d082d12a67dc21f2ee65e3c |
26-Sep-2012 |
Jeff Brown <jeffbrown@google.com> |
Move DreamManagerService to its own package.
Bug: 7204211
Change-Id: Ia6cfe252647161df357a4de149a06fa1e3fd63fa
reamController.java
reamManagerService.java
|