73ea0ae15fafd66ab8a8e2679723715c189bbba3 |
|
11-Aug-2016 |
Jeff Sharkey <jsharkey@android.com> |
Fix bugs around manager fetching. A recent patch started returning "null" when a Binder service required to provide a manager wasn't yet registered. This fixes four locations where that new logging was triggered: in two cases by adjusting the fetching ordering, and in two other cases by only fetching when the device supports the manager. Bug: 28634953 Change-Id: I84dbccffa4ac760c10a2bbcb234f21272bfecb91
/frameworks/base/services/appwidget/java/com/android/server/appwidget/AppWidgetService.java
|
cbd4ad1f7e23d3dd261c872accb2ed555b16b279 |
|
08-Aug-2016 |
joonyoung.cho <joonyoung.cho@lge.com> |
Merge "fix safeMode status in AppWidgetService" am: 78a72f0698 Change-Id: I21559690f6371102cf48132d8930343923d60011
|
57c9e16d041c9047a1618aab9c52be5608fae1cf |
|
21-May-2016 |
Winson <winsonc@google.com> |
Process user events from service lifecycle callbacks. - Instead of waiting for the broadcast to start loading the user’s widgets, handle them in the service callbacks to ensure the app widget update broadcasts are enqueued earlier. Bug: 27262341 Change-Id: I095abe5e15fe46412d00438986f7a9aee50872ca
/frameworks/base/services/appwidget/java/com/android/server/appwidget/AppWidgetService.java
|
2f30cc1cfeadc9501e01089b95f7f1567a134573 |
|
08-Apr-2015 |
joonyoung.cho <joonyoung.cho@lge.com> |
fix safeMode status in AppWidgetService AppWidgetService uses safemode value that defined on SystemServiceManager. however mSystemServiceManager.setSafeMode never called. therefore AppWidgetService doesn't know whether safemode or not in boot phase. In safemode, it causes NullPointerException in parsing function. after that all of placed widgets disappear at launcher app. Change-Id: I7576dcba7a2f548b2afa48ff2c700372c6920fe8
/frameworks/base/services/appwidget/java/com/android/server/appwidget/AppWidgetService.java
|
39999cf0263d0568337a87d0e586dcafd9e22ba1 |
|
17-Jul-2014 |
Svetoslav <svetoslavganov@google.com> |
Allow adding widgets from user profiles. The goal of this change is to enable support for appwidget from user profiles to the user main profile. A user profile is a user which is associated as a child of the main user profile. For example, a user may have a personal (parent) and corporate (child) profile. The device policy should be able to control whether adding a widget from a child profile and given packages is allowed. This change assumes that all packages from managed profiles are white listed. Another change will add the device policy changes. (cherrypicked 8cd27c3c to work around Gerrit issue) Change-Id: I267260b55d74c48b112a29979a9f59eef7a8194e
/frameworks/base/services/appwidget/java/com/android/server/appwidget/AppWidgetService.java
|
976e8bd2017d0263216c62111454438cc0f130e3 |
|
17-Jul-2014 |
Svetoslav <svetoslavganov@google.com> |
Allow adding widgets from user profiles. The goal of this change is to enable support for appwidget from user profiles to the user main profile. A user profile is a user which is associated as a child of the main user profile. For example, a user may have a personal (parent) and corporate (child) profile. The device policy should be able to control whether adding a widget from a child profile and given packages is allowed. This change assumes that all packages from managed profiles are white listed. Another change will add the device policy changes. Change-Id: I267260b55d74c48b112a29979a9f59eef7a8194e
/frameworks/base/services/appwidget/java/com/android/server/appwidget/AppWidgetService.java
|
d83a096f299abd9c7fe5e441ef1bb169c314b575 |
|
03-May-2014 |
Dianne Hackborn <hackbod@google.com> |
Bump up priority of system receiving BOOT_COMPLETED. Change-Id: I5166f88f11f781914312e867cb653c8ecbefa705
/frameworks/base/services/appwidget/java/com/android/server/appwidget/AppWidgetService.java
|
adfe8b86e9178a553b6db9722340fa4ff5201cf1 |
|
05-Feb-2014 |
Christopher Tate <ctate@google.com> |
App widget backup/restore infrastructure Backup/restore now supports app widgets. An application involved with app widgets, either hosting or publishing, now has associated data in its backup dataset related to the state of widget instantiation on the ancestral device. That data is processed by the OS during restore so that the matching widget instances can be "automatically" regenerated. To take advantage of this facility, widget-using apps need to do two things: first, implement a backup agent and store whatever widget state they need to properly deal with them post-restore (e.g. the widget instance size & location, for a host); and second, implement handlers for new AppWidgetManager broadcasts that describe how to translate ancestral-dataset widget id numbers to the post-restore world. Note that a host or provider doesn't technically need to store *any* data on its own via its agent; it just needs to opt in to the backup/restore process by publishing an agent. The OS will then store a small amount of data on behalf of each widget-savvy app within the backup dataset, and act on that data at restore time. The broadcasts are AppWidgetManager.ACTION_APPWIDGET_RESTORED and ACTION_APPWIDGET_HOST_RESTORED, and have three associated extras: EXTRA_APPWIDGET_OLD_IDS EXTRA_APPWIDGET_IDS EXTRA_HOST_ID [for the host-side broadcast] The first two are same-sized arrays of integer widget IDs. The _OLD_IDS values are the widget IDs as known to the ancestral device. The _IDS array holds the corresponding widget IDs in the new post- restore environment. The app should simply update the stored widget IDs in its bookkeeping to the new values, and things are off and running. The HOST_ID extra, as one might expect, is the app-defined host ID value of the particular host instance which has just been restored. The broadcasts are sent following the conclusion of the overall restore pass. This is because the restore might have occurred in a tightly restricted lifecycle environment without content providers or the package's custom Application class. The _RESTORED broadcast, however, is always delivered into a normal application environment, so that the app can use its content provider etc as expected. *All* widget instances that were processed over the course of the system restore are indicated in the _RESTORED broadcast, even if the backing provider or host is not yet installed. The widget participant is responsible for understanding that these are promises that might be fulfilled later rather than necessarily reflecting the immediate presentable widget state. (Remember that following a cloud restore, apps may be installed piecemeal over a lengthy period of time.) Telling the hosts up front about all intended widget instances allows them to show placeholder UI or similarly useful information rather than surprising the user with piecemeal unexpected appearances. The AppWidgetProvider helper class has been updated to add a new callback, onRestored(...), invoked when the _RESTORED broadcast is received. The call to onRestored() is immediately followed by an invocation of onUpdate() for the affected widgets because they will need to have their RemoteViews regenerated under the new ID values. Bug 10622506 Bug 10707117 Change-Id: Ie0007cdf809600b880d91989c00c3c3b8a4f988b
/frameworks/base/services/appwidget/java/com/android/server/appwidget/AppWidgetService.java
|
b880d880c6cd989eacc28c365fc9a41d31900da1 |
|
11-Feb-2014 |
Jeff Brown <jeffbrown@google.com> |
Make SystemService constructor take a Context. This change simplifies the process of initializing a SystemService by folding the onCreate() step back into the constructor. It removes some ambuiguity about what work should happen in the constructor and should make it possible for services to retain most of their final fields after refactoring into the new pattern. Change-Id: I25f41af0321bc01898658ab44b369f9c5d16800b
/frameworks/base/services/appwidget/java/com/android/server/appwidget/AppWidgetService.java
|
817ec49e7991d4cac50b2308cd7cf5f8641e1e29 |
|
20-Dec-2013 |
Amith Yamasani <yamasani@google.com> |
Wrap some services into a SystemService These services can now be excluded by modifying the list of REQUIRED_SERVICES (TB renamed) Changed appwidget, devicepolicy, backup and print services. Change-Id: Id8e2855d5c045cd57bdb02dca9ed75172803bce7
/frameworks/base/services/appwidget/java/com/android/server/appwidget/AppWidgetService.java
|
9158825f9c41869689d6b1786d7c7aa8bdd524ce |
|
22-Nov-2013 |
Amith Yamasani <yamasani@google.com> |
Move some system services to separate directories Refactored the directory structure so that services can be optionally excluded. This is step 1. Will be followed by another change that makes it possible to remove services from the build. Change-Id: Ideacedfd34b5e213217ad3ff4ebb21c4a8e73f85
/frameworks/base/services/appwidget/java/com/android/server/appwidget/AppWidgetService.java
|