When syncing, put time zone into exception events
Bug: 2545885 Change-Id: I41d504f16e9fc4776d2d8d7bbd2682b5940cf1d1
This commit is contained in:
parent
812983a341
commit
249c6f77c1
@ -533,6 +533,7 @@ public class CalendarSyncAdapter extends AbstractSyncAdapter {
|
|||||||
cv.put(Events.ORIGINAL_ALL_DAY, parentCv.getAsInteger(Events.ALL_DAY));
|
cv.put(Events.ORIGINAL_ALL_DAY, parentCv.getAsInteger(Events.ALL_DAY));
|
||||||
cv.put(Events.EVENT_LOCATION, parentCv.getAsString(Events.EVENT_LOCATION));
|
cv.put(Events.EVENT_LOCATION, parentCv.getAsString(Events.EVENT_LOCATION));
|
||||||
cv.put(Events.VISIBILITY, parentCv.getAsString(Events.VISIBILITY));
|
cv.put(Events.VISIBILITY, parentCv.getAsString(Events.VISIBILITY));
|
||||||
|
cv.put(Events.TIMEZONE, parentCv.getAsString(Events.TIMEZONE));
|
||||||
|
|
||||||
// This column is the key that links the exception to the serverId
|
// This column is the key that links the exception to the serverId
|
||||||
// TODO Make sure calendar knows this isn't globally unique!!
|
// TODO Make sure calendar knows this isn't globally unique!!
|
||||||
|
Loading…
Reference in New Issue
Block a user