9d0791bf6a047dbf7a99034130a5c4b437510fcf |
10-Oct-2012 |
Jeff Sharkey <jsharkey@android.com> |
Fix build, only invalidate when creating user. Bug: 7276595 Change-Id: I322f9d76a682b2d45fc556e35381442458168fe5
ccountManagerServiceTest.java
|
6ab72d74b86e5f4ec3c3909366fd46c225a66bd7 |
09-Oct-2012 |
Jeff Sharkey <jsharkey@android.com> |
Make RegisteredServicesCache multi-user aware. RegisteredServicesCache is used to track account authenticators and sync adapters, which can vary based on user. This change requires that callers now provide a userId when making cache requests. It continues persisting into a single file for now, which is keyed based on UID. It now watches for package broadcasts from all users, and scans packages on-demand. It changes cache callers to provide a relevant userId, and evicts cache entries when users are stopped. Changes SyncManager to only work with accounts from running users, only kicking off pending syncs once a user is started. Bug: 7276595, 7316150 Change-Id: I79466a84aa69aa37e4bd9691c5d6221d3662ff29
ccountManagerServiceTest.java
|
50cdf7c3069eb2cf82acbad73c322b7a5f3af4b1 |
24-Sep-2012 |
Dianne Hackborn <hackbod@google.com> |
Fix issue #7214090: Need to be able to post notifications to all users Also fix a bunch of system services that should be doing this. And while doing that, found I needed to fix PendingIntent to evaluate USER_CURRENT at the point of sending, not creation. Note that this may end up with us having some notification shown to non-primary users that lead to settings UI that should only be for the primary user (such as the vpn notification). I'm not sure what to do about this, maybe we need a different UI to come up there or something, but showing the actual notification for those users at least seems less broken than not telling them at all. Change-Id: Iffc51e2d7c847e3d05064d292ab93937646a1ab7
ccountManagerServiceTest.java
|
ae652cc97c9aa71838820d6d47f7535b18688436 |
31-Jul-2012 |
Kenny Root <kroot@google.com> |
Fix AccountManagerServiceTest The MockAccountAuthenticatorCache needs to implement the new method. Bug: 6820670 Change-Id: I5d1cb3aecec63602ae4541cd01ae8e28c8328e5a
ccountManagerServiceTest.java
|
f9f240e3ad5ff5eeaa32fbb2dd65ef7f3b06af32 |
25-Feb-2011 |
Fred Quintana <fredq@google.com> |
Fix a deadlock in AccountManagerService cause by different paths of code getting the mCacheLock and DB locks in different orders. The philosophy I followed for this was to ensure that the DatabaseHelper is only ever accessed from within a synchronized(mCacheLock) block. I also renamed a bunch of methods to make it easier to know if a given method should be called from within this synchronized block. Bug: 3404506 Change-Id: Ia48f95e77b77647d0717f70f1d8364da3719cc13
ccountManagerServiceTest.java
|
56285a60e83138bb4b4f2d3bdec91b2f3ca11aa2 |
02-Dec-2010 |
Fred Quintana <fredq@google.com> |
add caching to the AccountManagerService - cache the accounts, userdata and authtokens - make the AccountManagerServiceTest work again - add a log statement for every binder call http://b/issue?id=3188457 Change-Id: I96b94b9b690cf391fe4341e2a72893a6d823777b
ccountManagerServiceTest.java
|
1a44d5dcabc18cd5ef111f732ccff91683a1a093 |
13-Jan-2010 |
Neal Nguyen <tommyn@google.com> |
Phase 2 of test cleanup: moving test files from AndroidTests closer to their sources. Most of these are file moves; a couple notable exceptions are the changes due to the move, and fixing up test code: - database/DatabaseCursorTest.java - database/DatabaseStatementTest.java - net/UriTest.java
ccountManagerServiceTest.java
|