| ccf6c6814736e368949b64aadce676ab6d045fdc |
|
18-Jun-2015 |
Hyunyoung Song <hyunyoungs@google.com> |
AppWidgetServiceImpl should use ParceledListSlice as return object
b/19904873
> Reason: to prevent TransactionTooLargeException from occuring when
binder transaction size goes over the limit.
Change-Id: I054cb161d235234f3ccdaadd70314163e690b0db
/frameworks/base/core/java/com/android/internal/appwidget/IAppWidgetService.aidl
|
| e4a8da8ea241858b52d8122480316db79582c44d |
|
01-May-2015 |
Amith Yamasani <yamasani@google.com> |
Exclude bound app widgets from idle app list
Track package names of bound app widgets and use the list when
querying for idle apps.
Bug: 20066058
Change-Id: If8039397a061ef04bb13aa38d57cd7f0221f5fc7
/frameworks/base/core/java/com/android/internal/appwidget/IAppWidgetService.aidl
|
| 8e1d299da27da534b508b1da51ebe351a689cefa |
|
08-Aug-2014 |
Svetoslav <svetoslavganov@google.com> |
Polish the new cross-profile app widget APIs
bug:14991269
Change-Id: I5996f8c69a3d151ff1ecd8f19403dd606f588150
/frameworks/base/core/java/com/android/internal/appwidget/IAppWidgetService.aidl
|
| 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/core/java/com/android/internal/appwidget/IAppWidgetService.aidl
|
| 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/core/java/com/android/internal/appwidget/IAppWidgetService.aidl
|
| a75a883fe9ea1790803148f0a561473073e3f264 |
|
08-Feb-2013 |
Jim Miller <jaggies@google.com> |
Add explicit userId to AppWidget binder calls
Keyguard currently relies on being in the system process to grab the
given user's widgets. When we split keyguard into a new process,
it will need to have access to user-specific info to instantiate a
specific user's widgets. In order to accomplish this, we add an
explicit userid to each binder call as well as new permission
check to allow keyguard access.
This also fixes a potential race condition of having an incorrect user id
due to an async call to change the user. Every binder call now has a specific
user id. The user id is either the calling process user's id or an explicit
one passed by applications like keyguard. It is created once when an
AppWidgetManager is instantiated and remains for the lifetime of the object.
Fixed bug where widgets sometimes didn't show up for secondary users.
Moved permission check in AppWidgetService into getImplForUser()
Refactored to use userid from context associated AppWidgetManager instance.
Clean up AppWidgetHost to use userId from Context.
Remove redundant userId check in checkPermission since it's handled by
ActivityManager.handleIncomingUser()
Removed redundant userid check.
Upload after rebase...
Change-Id: Iae3e20f2b342c323bb58768b3d22051510f8268b
/frameworks/base/core/java/com/android/internal/appwidget/IAppWidgetService.aidl
|
| c566b43d02596cba437e9a2723e9f989297cca72 |
|
01-Dec-2012 |
Amith Yamasani <yamasani@google.com> |
Fix crosstalk between users for widgets hosted in lockscreen
This was initially about the Clock widget crashing repeatedly on some
devices with multiple users. Turned out that there were race conditions
when switching users that could result in remote views of one user calling
back to the RemoteViewsAdapter in keyguard that in turn sent an incorrect widget id
to a different user's widget, resulting in a crash.
Since KeyguardHostView is instantiated in the same process for different users,
it needs to carry a user identity to pass along to AppWidgetService so that
remote views services were bound to the correct user and callbacks were attached and
detached properly.
Added some aidl calls that take the userId to do the binding properly. A more
complete fix might be needed in the future so that all calls from Keyguard carry
the user id.
Also, there was a problem in comparing host uid for secondary users, since Settings
for a secondary user has a different uid than keyguard. Not an issue on single-user
systems. Changed the host.uid comparison to accomodate for the secondary user.
Bug: 7450247
Change-Id: Idbc36e3c60023cac74174f6cb7f2b2130dd3052c
/frameworks/base/core/java/com/android/internal/appwidget/IAppWidgetService.aidl
|
| d9e5af3851f592a00549b689dec325dc46268606 |
|
29-Nov-2012 |
Adam Cohen <adamcohen@google.com> |
Making sure keyguard and homescreen only display eligible widgets (issue 7550090)
Change-Id: I25acb7bde2e8e5ac3185a009f5c7151b81f0ae19
/frameworks/base/core/java/com/android/internal/appwidget/IAppWidgetService.aidl
|
| 75b5cfb4a41030333820d072578a288d4ec9899c |
|
16-Nov-2012 |
Michael Jurka <mikejurka@google.com> |
Delete appWidgetId when removing lockscreen widgets
Bug: 7550012
Change-Id: Ia9f5266256016eb91bfd6a2d5a7f910c42948f1e
/frameworks/base/core/java/com/android/internal/appwidget/IAppWidgetService.aidl
|
| 0aa2d42e87e4a1ed5b83f356690e465d6a3587cc |
|
08-Sep-2012 |
Adam Cohen <adamcohen@google.com> |
Adding notion of keyguard widgets
-> Persisting certain appwidget options
-> Adding ability to specify appwidget options on bind
so as to avoid AppWidgetProvider update call with no
options.
Change-Id: I5631039f19f1822b8e123b559b6353c880c0192e
/frameworks/base/core/java/com/android/internal/appwidget/IAppWidgetService.aidl
|
| d2097ebacf3a3658624cad10669a4d98e8d7d846 |
|
02-May-2012 |
Adam Cohen <adamcohen@google.com> |
Changing app widget "extras" to "options" and another small API Review issue
-> (issue 6427146), (issue 6427861)
Change-Id: Ib69a9b3717a5b62317ec227936bc3b2fd5954043
/frameworks/base/core/java/com/android/internal/appwidget/IAppWidgetService.aidl
|
| 61a5b0160d9f2e53ef4d4b451212a63032dad32d |
|
13-Apr-2012 |
Michael Jurka <mikejurka@google.com> |
New API to allow third-party apps to bind widgets
Change-Id: I1a3761c1a0f557a32d4d3bdd0207567fec918ba7
/frameworks/base/core/java/com/android/internal/appwidget/IAppWidgetService.aidl
|
| e8724c82ab1479f13c85a2c6219841e1fd95f2d2 |
|
20-Apr-2012 |
Adam Cohen <adamcohen@google.com> |
Adding callback for widget size changed, and potentially other extra info
Change-Id: I57738c92b6a0ba68ae66b19a533559470c64e6f1
/frameworks/base/core/java/com/android/internal/appwidget/IAppWidgetService.aidl
|
| 81f39eb6e76d0be1dd341af835e8002a0f80524e |
|
12-Jan-2011 |
Winson Chung <winsonc@google.com> |
Refactoring app widgets to address security/performance issues.
- Moving the service binding to AppWidgetService to prevent arbitrary apps from binding to widget services
- Requiring RemoteViewsServices to require android.permission.BIND_REMOTEVIEWS permission
Change-Id: Id135bafba998299eb278067712b8a5d8487cfd04
/frameworks/base/core/java/com/android/internal/appwidget/IAppWidgetService.aidl
|
| 6394c0e52cf641d93f678fd052499aa952e3595d |
|
16-Aug-2010 |
Winson Chung <winsonc@google.com> |
Adding callback and fix to RemoteViewsFactory on notifyDataSetChanged.
Also removing extra parameter in AppWidgetManager.notifyDataSetChanged.
Change-Id: Ic771fe045ae793a6dacf09f1230e7c1c4b59a13e
/frameworks/base/core/java/com/android/internal/appwidget/IAppWidgetService.aidl
|
| 2dd2197805edb4d9547b143deef2226413218f4c |
|
16-Aug-2010 |
Adam Cohen <adamcohen@google.com> |
-> Enabled partial updates to app widgets through AppWidgetManager.
Partial updates are not cached by the AppWidgetService.
-> Added the ability to insert commands with no parameters into
RemoteViews objects.
-> Added showNext() and showPrevious() methods to RemoteViews.
-> Made showNext() / showPrevious() of AdapterViewFlipper remotable.
Change-Id: Ic5491bb374424a54728c4ca92b94b1f00dfb87ff
/frameworks/base/core/java/com/android/internal/appwidget/IAppWidgetService.aidl
|
| 499cb9f516062b654952d282f211bee44c31a3c2 |
|
16-Jul-2010 |
Winson Chung <winsonc@google.com> |
Initial changes to allow collections in widgets.
Change-Id: I3cfa899bae88cd252912cecebc12e93c27a3b7c9
/frameworks/base/core/java/com/android/internal/appwidget/IAppWidgetService.aidl
|
| c39a6e0c51e182338deb8b63d07933b585134929 |
|
11-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //branches/cupcake/...@137873
/frameworks/base/core/java/com/android/internal/appwidget/IAppWidgetService.aidl
|