5c6756fefb6db0fe468b9d747960a6da344880ad |
|
02-Oct-2014 |
Matthew Williams <mjwilliams@google.com> |
Revert "Protect LOGIN_ACCOUNTS_CHANGED receiver in SyncManager" This reverts commit cf2bd348e73e880fe5bfc7a025732d4ec606ff1f. Reverted because for account removal the AccountManagerService delegates the sending of LOGIN_ACCOUNTS_CHANGED to the authenticator. See b/17511110. Change-Id: Ic03016af98070b4add5f7a5ec1fdff32ba63298e
/frameworks/base/services/core/java/com/android/server/content/SyncManager.java
|
119aac93f8d757ff464dd4d1135ffcf37f7cda02 |
|
29-Sep-2014 |
Matthew Williams <mjwilliams@google.com> |
Fix deadlock caused by clearAllBackoffs in SSE BUG: 17420163 This CL is a copy of ag/359292 That commit was lost, see the bug for more details. Change-Id: I68747d447f8c95e6b5022f9bc8cbab677e0c3d4e
/frameworks/base/services/core/java/com/android/server/content/SyncManager.java
|
86f0c21417fd78de78e1d56400b84fbc538d1e24 |
|
10-Sep-2014 |
Matthew Williams <mjwilliams@google.com> |
Protect LOGIN_ACCOUNTS_CHANGED receiver in SyncManager BUG: 17359770 Reuse the Manifest.permission.ACCOUNT_MANAGER to protect this receiver, because when this intent lands it kicks off a sync for every account/provider on the device. Semantically this means "if you can't talk to an authenticator to do things like get a token or add an account, then you can't send an intent to the SyncManager that the accounts on the device have changed in some drastic way" Change-Id: I7eccc38e135cb00ebb0aafc69afc802fe1c4f219
/frameworks/base/services/core/java/com/android/server/content/SyncManager.java
|
07ad8dc2087aa02da48353acc19ba82e62d99f82 |
|
01-Sep-2014 |
Kenny Guy <kennyguy@google.com> |
Use context for user when calling notifyAsUser Create a context for the user the notification is being posted for when using NotificationManager.notifyAsUser. Bug: 17002733 Change-Id: Ie41d27bbb781ca38cc9bc910bd4410b8862edee1
/frameworks/base/services/core/java/com/android/server/content/SyncManager.java
|
92a1c09aa467f03dad78472098d40992303937fb |
|
26-Aug-2014 |
Matthew Williams <mjwilliams@google.com> |
Add maximum time-out to sync operation BUG: 16219182 We have seen cases where run-away syncs keep going for a very long time. The default behaviour is that a sync can run for as long as it wants once there is nothing else waiting. This CL will change that, and impose a maximum time-limit of 30mins on each sync, after when the op with be cancelled and the adapter will go into back-off. This behaviour will only take effect for syncs that are not initializations, or user-initiated. Change-Id: I1731270ca2a6500b19fc125186aa0b0cd81d1126
/frameworks/base/services/core/java/com/android/server/content/SyncManager.java
|
3c8a42ddd9482ebc8541f7af6f15afdf3b3ec151 |
|
26-Aug-2014 |
Matthew Williams <mjwilliams@google.com> |
Don't back-off ALREADY_IN_PROGRESS syncs BUG: 16219182 The issue is that some adapters get into a bad state where SyncManager assumes them complete yet they are still going. This result in ALREADY_IN_PROGRESS coming back from the adapter, the default retry-time for which is about 10s. Subject ALREADY_IN_PROGRESS to exponential back-off to avoid waking up SM every ~10 seconds Change-Id: I6cef787366436c678bac762ec6daf6212f04badc
/frameworks/base/services/core/java/com/android/server/content/SyncManager.java
|
255dd04271088590fedc46c8e22b2fd4ab142d39 |
|
19-Aug-2014 |
Selim Cinek <cinek@google.com> |
Added notification color to all system notifications Bug: 17128331 Change-Id: I81a94510ef51b99916f314c0dd65852426a1fbeb
/frameworks/base/services/core/java/com/android/server/content/SyncManager.java
|
fdb1956ff71ff57fcdaafaaeb7f42c19de3d7c2f |
|
12-Jul-2014 |
Dianne Hackborn <hackbod@google.com> |
Fix issue #15681802: Missing RESET:TIME in complete battery histories But wait, there's more! - Keep track of sync durations in the aggregated stats. - Add events for users that are running and in the foreground. - Rework the activity manager's tracking of stuff using battery in the background to be based on proc stats, which allows it to be better about determing when it should reset its tracking of background work. - Also add tracking of scheduled job execution, like we are doing for syncs. - And once I started hooking battery stats in to JobSchedulerService, I found a few things I couldn't stop myself from changing: (1) make it very explicit that it doesn't start scheduling jobs until we have reached the point in system boot where third party apps are allowed to run, and (2) adjust the various for loops to not use iterators. Change-Id: I69d812e27bcfee9e58a614f0f6b1c7545d7530b1
/frameworks/base/services/core/java/com/android/server/content/SyncManager.java
|
d83a096f299abd9c7fe5e441ef1bb169c314b575 |
|
03-May-2014 |
Dianne Hackborn <hackbod@google.com> |
Bump up priority of system receiving BOOT_COMPLETED. Change-Id: I5166f88f11f781914312e867cb653c8ecbefa705
/frameworks/base/services/core/java/com/android/server/content/SyncManager.java
|
cde7086b900fd192a8e389f62ab5007d351d86b8 |
|
21-Mar-2014 |
Matthew Williams <mjwilliams@google.com> |
Merge "Downgrade expedited to normal on reschedule."
|
d45665bf0b26fddf5716a0fd43036848d9301960 |
|
26-Feb-2014 |
Dianne Hackborn <hackbod@google.com> |
Collect per-uid mobile radio usage. We now compute radio active time per application, by distributing the active time across all applications each time the radio goes down, weighting it by the number of packets transferred. Per-app radio power use is now computed using this radio active time. This also gives us a new metric "ms per packet", which give an idea of how effectively an application is using the radio. This is collected and reported as a new set of stats in the human- readable checkin. (It can be computed from the raw checkin data). Also improve sync reporting to include the sync source as used in wake locks, not just the component name. Change-Id: I0b0185fadd1e47ae749090ed36728ab78ac24c5e
/frameworks/base/services/core/java/com/android/server/content/SyncManager.java
|
a1f1a3c573acd91024fda0ceb3b921c73b186963 |
|
25-Feb-2014 |
Dianne Hackborn <hackbod@google.com> |
More battery stats. - Add events for sync. - Add more descriptive tags for wake events. - Fix battery reset. - Fix tracking of wifi data. Change-Id: Ic07f2a86a5ed33e7da57eb1108c31c777ecd801f
/frameworks/base/services/core/java/com/android/server/content/SyncManager.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/core/java/com/android/server/content/SyncManager.java
|
31068163b660ff041e45f35174f75106dcb47ade |
|
30-Jan-2014 |
Patrick Tjin <pattjin@google.com> |
Formatting fix Remove whitespace from end of Sync Status table Change-Id: I5b0bf3380e0c67c769ec9c334f1374713c94aa94
/frameworks/base/services/core/java/com/android/server/content/SyncManager.java
|
49782e46c0eb85a25ae2abcf80880c48dbab5aea |
|
20-Dec-2013 |
Amith Yamasani <yamasani@google.com> |
am 9158825f: Move some system services to separate directories * commit '9158825f9c41869689d6b1786d7c7aa8bdd524ce': Move some system services to separate directories
|
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/core/java/com/android/server/content/SyncManager.java
|