2b4c8f926fdc8a2ccb88668ca85edfd3ecb9913a |
|
09-Feb-2016 |
Shreyas Basarge <snb@google.com> |
SyncManager sync blow up fix Duplicates for periodic syncs would be created just after boot and when a periodic sync was delayed. This CL fixes the behavior. Bug: 26954967 Change-Id: I2440961629d443a62f96360563d435af9137857b (cherry picked from commit 1675400a7cd0b56e5adc5606fb4fea77f8d24ea5)
/frameworks/base/services/tests/servicestests/src/com/android/server/content/SyncOperationTest.java
|
8c834c07675052c984728cbf79f7c2e0d8246e43 |
|
07-Jan-2016 |
Shreyas Basarge <snb@google.com> |
SyncManager on JobScheduler SyncManager now uses JobScheduler for scheduling and persistence purposes. Change-Id: I38c92aedbf4d891ca297644d0b706835aaedfcd6
/frameworks/base/services/tests/servicestests/src/com/android/server/content/SyncOperationTest.java
|
bef28feba57be7fd6a4d14a85a8229154338b2ed |
|
30-Oct-2015 |
Dianne Hackborn <hackbod@google.com> |
Initial stab at background check. Actually, this implementation is more what we want for ephemeral apps. I am realizing the two are not really the same thing. :( For this implementation, we now keep track of how long a uid has been in the background, and after a certain amount of time (currently 1 minute) we mark it as "idle". Any packages associated with that uid are then no longer allowed to run in the background. This means, until the app next goes in the foreground: - No manifest broadcast receivers in the app will execute. - No services can be started (binding services is still okay, as this is outside dependencies on the app that should still be represented). - All alarms for the app are cancelled and no more can be set. - All jobs for the app are cancelled and no more can be scheduled. - All syncs for the app are cancelled and no more can be requested. Change-Id: If53714ca4beed35faf2e89f916ce9eaaabd9290d
/frameworks/base/services/tests/servicestests/src/com/android/server/content/SyncOperationTest.java
|
6428046767ee4195617fb41b5639eefa2ca7a939 |
|
09-Jan-2014 |
Matthew Williams <mjwilliams@google.com> |
Downgrade expedited to normal on reschedule. bug: 12033540 Expedited was previously tracked by a redundant internal variable, ostensibly as an optimisation. This variable could differ from the value in the bundle depending on how the operation is initialised, which led to confusion. Now an expedited sync will only be treated as such on its first execution. Change-Id: I9979102317aecbe8bc53a36381d4b2782ac131be Conflicts: services/core/java/com/android/server/content/SyncOperation.java services/core/java/com/android/server/content/SyncQueue.java
/frameworks/base/services/tests/servicestests/src/com/android/server/content/SyncOperationTest.java
|
fa77418134c6f1f80af225a78819f069e9c974fb |
|
19-Jun-2013 |
Matthew Williams <mjwilliams@google.com> |
AnonymousSyncService & SyncRequest. Changes to the way bundles are parcelled broke SM, this update writes out the bundle as xml. This circumvents the need for parcel, and makes it easier to debug whats happening. Change-Id: I6cd5d3a2eb80bfa5b3ae0c7f2d2ff91a65daaa34
/frameworks/base/services/tests/servicestests/src/com/android/server/content/SyncOperationTest.java
|
7a96c39c510923ef73bbb06ab20109f0168b8eb1 |
|
15-Nov-2012 |
Jeff Sharkey <jsharkey@android.com> |
Move lingering services to services.jar. This helps reduce the pressure on framework.jar, and makes it clear that it should only be used by the system_server. Bug: 7333397 Change-Id: I0858904239535380fbf30562b793e277d8c3f054
/frameworks/base/services/tests/servicestests/src/com/android/server/content/SyncOperationTest.java
|