| db1cd8456a0cf273890cd3da10d0d5f00aadbb45 |
|
23-Jul-2014 |
Anthony Lee <anthonylee@google.com> |
b/16380611. Check for null Account objects before using.
It seems that there is a timing issue where the account is
deleted during onPerformSync(). Since we don't check for
a null Account. We crash. A null return value from
restoreXYZFromId() is valid so we should handle it.
Change-Id: I333090f6f8e69c555ab765aa58406f29300a3126
/packages/apps/Exchange/src/com/android/exchange/service/CalendarSyncAdapterService.java
|
| f8cccaecc8148d12d58ffcba5ce7366191316ac0 |
|
25-Jun-2014 |
Martin Hibdon <mhibdon@google.com> |
Make Calendar and Contacts syncing go through EasService
Now, instead of forwarding the request to the EmailSyncAdapterService,
both Calendar and Contacts syncAdapterServices actually make calls
through to the EasService to perform the sync.
Change-Id: I60346736e1639838593f4b52934a3d15b3faf543
/packages/apps/Exchange/src/com/android/exchange/service/CalendarSyncAdapterService.java
|
| bb0141b49e7eff978fa445249dc888461ea581e3 |
|
03-Jun-2014 |
Martin Hibdon <mhibdon@google.com> |
Delete obsolete code
ExchangeService was only being used for GalSearch. That
code has been moved EasService.
Other services, EasAccountService, EasOutboxService, and
EasSyncService are no longer used and have been removed,
along with a bunch of other unused helper classes.
Change-Id: I25c7e53896125818cfd6d3e3bf630ff671f142d1
/packages/apps/Exchange/src/com/android/exchange/service/CalendarSyncAdapterService.java
|
| 3eef378426c7c88608f53f5a268baed40259ccf6 |
|
14-Oct-2013 |
Alon Albert <aalbert@google.com> |
Bring log change back in
Revert "Revert "Cleanup Logs""
This reverts commit a3f990ee76828d01e1e2812c4446221a1c523aa4.
Bug: 11149133
Change-Id: I3fabb4e508cf9063e056979c8ed807ebf372fa4a
/packages/apps/Exchange/src/com/android/exchange/service/CalendarSyncAdapterService.java
|
| a3f990ee76828d01e1e2812c4446221a1c523aa4 |
|
12-Oct-2013 |
Alon Albert <aalbert@google.com> |
Revert "Cleanup Logs"
This reverts commit fcacd1e1e214f5f5b8aea0602e55ae6ca3bbf175.
Will re-merge this on Monday so we can still have logs from weekend testers
Change-Id: I697eed2806a17a180a8733110391f44d3a80fc59
/packages/apps/Exchange/src/com/android/exchange/service/CalendarSyncAdapterService.java
|
| fcacd1e1e214f5f5b8aea0602e55ae6ca3bbf175 |
|
11-Oct-2013 |
Alon Albert <aalbert@google.com> |
Cleanup Logs
Bug: 11149133
Change-Id: I736cb022bfd7f136f6e88010b91837f2aa3171f2
/packages/apps/Exchange/src/com/android/exchange/service/CalendarSyncAdapterService.java
|
| 4427badd747b7c172934014b9f95a1be1256f35a |
|
09-Oct-2013 |
Martin Hibdon <mhibdon@google.com> |
Allow multiple mailboxes to sync at one time
b/11103878
Change-Id: I6a3944c9171948d3f80bbb51294841a84cf409aa
/packages/apps/Exchange/src/com/android/exchange/service/CalendarSyncAdapterService.java
|
| 77b653fa1b5baabddb76802f0333c78f80c29ace |
|
08-Oct-2013 |
Yu Ping Hu <yph@google.com> |
Improve sync logic.
- Always request FolderSync when the account hasn't synced
yet.
- Change the account broadcast receiver to only initiate
FolderSync for accounts with all syncs disabled.
- Add a mailbox type filter to ONLY sync calendar/contacts.
Type filtered sync does not trigger FolderSync.
- Do not sync non-enabled types when syncing multiple folders
(i.e. for account sync, or for type sync).
Bug: 11081520
Change-Id: Ic98e43a9fa3ed46d0597c348a5823d1accab7045
/packages/apps/Exchange/src/com/android/exchange/service/CalendarSyncAdapterService.java
|
| 3c232ef228e1282dc811ec24f9f85300774734bb |
|
03-Oct-2013 |
Martin Hibdon <mhibdon@google.com> |
Only make mailbox syncing expedited if the incoming request was
b/10970795
In CalendarSyncAdapterService and ContactsSyncAdapterService,
when we get an onPerformSync(), we just make a new sync request
for a particular exchange mailbox. The trouble is that if the
new request is "expedited", and the original request was not,
then the original request will be canceled. When this happens,
after the second sync completes, the original will be started
again. This can put us in a rapidly spinning infinite loop.
With this CL, our new sync request will only be expedited if
the incoming request was also expedited. This should prevent the
infinite loop. It unfortunately means that background calendar
and contacts syncs can take extra long to start, because we must
wait for the sync manager to decide to run the original sync,
and then wait again for it to perform the actual mailbox sync.
That's a good enough trade off for now.
Change-Id: I51689f4a54b3b9bae2f797730287e30eb39f4649
/packages/apps/Exchange/src/com/android/exchange/service/CalendarSyncAdapterService.java
|
| de96f1cd298fd7cfb9766a71b0a8e05c955ec8db |
|
03-Oct-2013 |
Martin Hibdon <mhibdon@google.com> |
Only sync the given calendar or contacts mailbox
b/10970795
Prior to this CL, if CalendarSyncAdapterService or
ContactsSyncAdapterService received an onPerformSync
for a single mailbox, we'd still sync all calendar or
contacts mailboxes. In addition to just being unneccessary,
it could also trigger extra pings: Suppose that we have
two calendar mailboxes, X and Y. Y is out of sync, so
CalendarSyncAdapterService receives an onPerformSync().
It first syncs mailbox X. As soon as it finishes, it
will restart the ping. The ping will notice the mailbox
Y is still out of sync, and request a sync again.
Instead, in this case, we should just sync mailbox Y
in the first place.
Change-Id: Ibf55f1ce2da05cae48a78ea67331e730827eaa64
/packages/apps/Exchange/src/com/android/exchange/service/CalendarSyncAdapterService.java
|
| 2e47c34cba847b47992420f8634ae51dddc90cd5 |
|
02-Oct-2013 |
Martin Hibdon <mhibdon@google.com> |
Put device phone number in the settings and provision
b/11032223
Add phone number, imei, device language and
mobile operator to the exchange settings and
provision.
Change-Id: I0b6ac327f8121b80479220c0e2c2b4784bbe0f45
/packages/apps/Exchange/src/com/android/exchange/service/CalendarSyncAdapterService.java
|
| 9c7165d4c6b90101b781f90b17451efd42a17929 |
|
02-Oct-2013 |
Martin Hibdon <mhibdon@google.com> |
More logging improvements
Change-Id: I023c8270647a63d1528aa86120fd4b14712ce345
/packages/apps/Exchange/src/com/android/exchange/service/CalendarSyncAdapterService.java
|
| 110837ebff288a75f9bda067c38e2c46797d99b5 |
|
27-Sep-2013 |
Alon Albert <aalbert@google.com> |
Unify Log Tags
Use a single log tag
Change-Id: I6f08c1eb6e84971cc21497ca14bf60860f75bab4
/packages/apps/Exchange/src/com/android/exchange/service/CalendarSyncAdapterService.java
|
| 1424b228e105b1c5c8b54eb0f401a549161f8f5f |
|
24-Sep-2013 |
Alon Albert <aalbert@google.com> |
Support Multiple Calendars
Bug: 10893901
Change-Id: I7c704b4b841266353673ad6aa3e1091a31661e63
/packages/apps/Exchange/src/com/android/exchange/service/CalendarSyncAdapterService.java
|
| 24e1187f8511d301fa586759cd1b3bd5ad2ccf41 |
|
19-Sep-2013 |
Yu Ping Hu <yph@google.com> |
Make sync adapters singletons.
We saw multiple sync adapter objects concurrently, which is BAD.
If service.onCreate got called while a sync was in flight, this
could happen (and all evidence pointed to this being the case),
so let's just not let that happen at all.
Bug: 10150344
Change-Id: Ia914bd256aa05ccb86cfa5203e18df5a03aa34be
/packages/apps/Exchange/src/com/android/exchange/service/CalendarSyncAdapterService.java
|
| 99d00f13bbbb02bb4db4fa71afb700eb178a2238 |
|
28-Aug-2013 |
Paul Westbrook <pwestbro@google.com> |
Fix NPE
Bug: 10513216
Change-Id: I2db3957311addcac51dd3df9bd595ee23f973284
/packages/apps/Exchange/src/com/android/exchange/service/CalendarSyncAdapterService.java
|
| 56d35257ef1493e849522c3c2828d904e4c5531f |
|
26-Jun-2013 |
Scott Kennedy <skennedy@google.com> |
Clean up a bunch of warnings
Bug: 9565838
Change-Id: Ieb65ab41c1e320647a1a17b835371c5eb8e342db
/packages/apps/Exchange/src/com/android/exchange/service/CalendarSyncAdapterService.java
|
| b31070f7484eeeb15c4bce89dbc61388d05d0bfc |
|
11-Jun-2013 |
Yu Ping Hu <yph@google.com> |
Fix upsync for calendars.
Change-Id: If3d48a942c145b6e3e2c08c17264a54b1805de16
/packages/apps/Exchange/src/com/android/exchange/service/CalendarSyncAdapterService.java
|
| 942b7d73f2f5b3d6c651e39463e615fe6902a910 |
|
06-Jun-2013 |
Scott Kennedy <skennedy@google.com> |
Unify LogTag
There is now only one LogTag class. The static initializer of
GmailApplication (existing), EmailApplication (new), and
Exchange (existing) will now set the log tag to "Gmail" and "Email",
respectively. Up until that code is run, it will be "UnifiedEmail".
"setprop log.tag.Gmail VERBOSE" (or .Email, .Exchange) will trigger
all logs to be printed as long as they go through LogUtils,
regardless of what tag is used by that individual log. This lets us
still turn on logging everywhere in one command, but also lets us use
more descriptive tags (like the class name).
And since we no longer have three com.android.mail.utils.LogTag
classes, builds will be much easier.
Also, we now use LogUtils everywhere.
Change-Id: Ib565414fae51d0c3367370db9717aece45f7eb36
/packages/apps/Exchange/src/com/android/exchange/service/CalendarSyncAdapterService.java
|
| 6e66ab513197793c34f5dcda159043da39224ff9 |
|
29-May-2013 |
Yu Ping Hu <yph@google.com> |
Initial fix for Contacts and Calendar.
This comes in a few parts:
- We can't use the same SyncAdapter service for all
sync types, so for now this forwards syncs to the
Contacts and Calendar services to the Email service.
This should get cleaned up later.
- Refactor EasSyncHandler to cover all the common code for
syncing Exchange collections and adjust
EasMailboxSyncHandler to match this change.
- Implement EasSyncHandler subclasses for Contacts and
Calendar.
This is only a first pass -- for example, upsync is
still not yet implemented.
Change-Id: I722b540830b292bac4c79bf8426d8eec62112d9d
/packages/apps/Exchange/src/com/android/exchange/service/CalendarSyncAdapterService.java
|
| 9696d7f701599644d1c108863d6195af88da2c30 |
|
01-May-2013 |
Yu Ping Hu <yph@google.com> |
Refactor common sync adapter code.
Change-Id: I548d4657f31b04f4f944c5e54207523aeeeafe09
/packages/apps/Exchange/src/com/android/exchange/service/CalendarSyncAdapterService.java
|
| d7fa6b782093f91066b3fcbdb48c7ee47a685012 |
|
30-Apr-2013 |
Yu Ping Hu <yph@google.com> |
Code cleanup.
- Remove some dead code.
- Add some @Overrides where needed.
- Remove some unnecessary throws declarations.
- Clean up SyncAdapters to not use statics and locks.
Change-Id: I0dcfa159ea0535d726d9f943196d127b6c4c13cc
/packages/apps/Exchange/src/com/android/exchange/service/CalendarSyncAdapterService.java
|
| 9e8fa1d2deeac26aac4e92c4cc5f7e1cc8b7608c |
|
05-Apr-2013 |
Paul Westbrook <pwestbro@google.com> |
Prevent NPEs
ContentResolver#query() can return null. Log if this happens, and don't
crash
Bug: 7225209
Change-Id: Iea8f8ce3da81856562cbc9db793106fa5b118f14
/packages/apps/Exchange/src/com/android/exchange/service/CalendarSyncAdapterService.java
|
| bbafcf7dbcb92063aa207113451c1d29235bc5dd |
|
10-Sep-2012 |
Marc Blank <mblank@google.com> |
Make sure EmailContent.init() is called on startup
* If the app is started via a SyncAdapterService, this wasn't
happening
Bug: 7133858
Change-Id: I5e6fdaa35d1f77161420d068759d07ee84a7c28d
/packages/apps/Exchange/src/com/android/exchange/service/CalendarSyncAdapterService.java
|