Permalink
Switch branches/tags
android-wear-p-preview-2 android-wear-o-preview-4 android-wear-o-preview-3 android-wear-n-preview-2 android-wear-n-preview-1 android-wear-8.0.0_r1 android-wear-7.1.1_r1 android-wear-5.1.1_r1 android-wear-5.1.0_r1 android-wear-5.0.0_r1 android-vts-8.1_r3 android-vts-8.0_r8 android-vts-8.0_r7 android-vts-8.0_r6 android-vts-8.0_r2 android-vts-8.0_r1 android-sdk-support_r11 android-sdk-adt_r20 android-sdk-adt_r16.0.1 android-sdk-4.4.2_r1.0.1 android-sdk-4.4.2_r1 android-sdk-4.0.3_r1 android-sdk-4.0.3-tools_r1 android-p-preview-3 android-p-preview-2 android-p-preview-1 android-o-preview-4 android-o-preview-3 android-o-preview-2 android-o-preview-1 android-o-mr1-preview-2 android-o-mr1-preview-1 android-o-mr1-iot-release-1.0.1 android-o-mr1-iot-release-1.0.0 android-o-mr1-iot-preview-8 android-o-mr1-iot-preview-7 android-o-mr1-iot-preview-6 android-o-iot-preview-5 android-n-preview-5 android-n-preview-4 android-n-preview-3 android-n-preview-2 android-n-preview-1 android-n-mr2-preview-2 android-n-mr2-preview-1 android-n-mr1-preview-2 android-n-mr1-preview-1 android-n-iot-release-polk-at1 android-n-iot-release-lg-thinq-wk7 android-n-iot-preview-4 android-n-iot-preview-2 android-m-preview android-m-preview-2 android-m-preview-1 android-l-preview_r2 android-cts-verifier-4.0.3_r1 android-cts-verifier-4.0_r1 android-cts-8.1_r6 android-cts-8.1_r5 android-cts-8.1_r4 android-cts-8.1_r3 android-cts-8.1_r2 android-cts-8.1_r1 android-cts-8.0_r10 android-cts-8.0_r9 android-cts-8.0_r8 android-cts-8.0_r7 android-cts-8.0_r6 android-cts-8.0_r5 android-cts-8.0_r4 android-cts-8.0_r3 android-cts-8.0_r2 android-cts-8.0_r1 android-cts-7.1_r18 android-cts-7.1_r17 android-cts-7.1_r16 android-cts-7.1_r15 android-cts-7.1_r14 android-cts-7.1_r13 android-cts-7.1_r12 android-cts-7.1_r11 android-cts-7.1_r10 android-cts-7.1_r9 android-cts-7.1_r8 android-cts-7.1_r7 android-cts-7.1_r6 android-cts-7.1_r5 android-cts-7.1_r4 android-cts-7.1_r3 android-cts-7.1_r2 android-cts-7.1_r1 android-cts-7.0_r22 android-cts-7.0_r21 android-cts-7.0_r20 android-cts-7.0_r19 android-cts-7.0_r18 android-cts-7.0_r17 android-cts-7.0_r16 android-cts-7.0_r15 android-cts-7.0_r14
Nothing to show
Commits on Feb 23, 2018
  1. Merge "packages/providers/CalendarProvider: Set LOCAL_SDK_VERSION whe…

    hansson Gerrit Code Review
    hansson authored and Gerrit Code Review committed Feb 23, 2018
    …re possible."
Commits on Feb 22, 2018
  1. packages/providers/CalendarProvider: Set LOCAL_SDK_VERSION where poss…

    Anton Hansson
    Anton Hansson committed Feb 22, 2018
    …ible.
    
    This change sets LOCAL_SDK_VERSION for all packages where
    this is possible without breaking the build, and
    LOCAL_PRIVATE_PLATFORM_APIS := true otherwise.
    
    Setting one of these two will be made required soon, and this
    is a change in preparation for that. Not setting LOCAL_SDK_VERSION
    makes the app implicitly depend on the bootclasspath, which is
    often not required. This change effectively makes depending on
    private apis opt-in rather than opt-out.
    
    Test: make relevant packages
    Bug: 73535841
    Change-Id: I511e394a3b36ca0800180cacd150346408abedb9
Commits on Dec 13, 2017
  1. Merge "Update OWNERS"

    Treehugger Robot Gerrit Code Review
    Treehugger Robot authored and Gerrit Code Review committed Dec 13, 2017
  2. Merge "Fix calendar alarms not being triggered after 22h"

    Treehugger Robot Gerrit Code Review
    Treehugger Robot authored and Gerrit Code Review committed Dec 13, 2017
  3. Update OWNERS

    Makoto Onuki
    Makoto Onuki committed Dec 13, 2017
    Test: n/a
    
    Change-Id: I2ca50712bc07b084a2955d0458094eb00049f03c
Commits on Dec 12, 2017
  1. Fix calendar alarms not being triggered after 22h

    talyz authored and Makoto Onuki committed Nov 2, 2017
    Fix two bugs:
    
    1) scheduleNextAlarmLocked is supposed to schedule the next check for
       alarms in (24h - 15min) if it can't find any alarms within the next
       24h. It doesn't, because the comparison at the end
    
       if (nextAlarmTime == Long.MAX_VALUE)
    
       is never true, since nextAlarmTime is set to the value of the
       variable end at the beginning.
    
       Fix this by introducing a new boolean, mAlarmScheduled, which is
       set true by scheduleAlarm.
    
    2) With the first issue fixed, we still have a blind spot of 1h 45min
       where no alarm would be triggered, because the end variable is
       calculated from start, which is always set to two hours before the
       function is run; end adds 24h to this, so we end up 22h in the
       future and don't look for any alarms past that. When we schedule
       the next check, we do so 23h 45min in the future and thereby end up
       with a 1h 45min window in which no alarm would be triggered.
    
       Fix this by calculating end from currentMillis instead. Also use
       DateUtils.DAY_IN_MILLIS for consistency.
    
    Also, schedule the next alarm based on the value of end instead of a
    constant for more flexibility and less risk of future breakage.
    
    Test: Tested using the android emulator and an offline calendar app
    (https://play.google.com/store/apps/details?id=org.sufficientlysecure
    .localcalendar&hl=en) in the following manner:
    
    1) Temporarily changed the time scale to 10 minutes instead of 24
       hours for feasibility. To do this, the second fix had to be applied,
       since without it the window we're looking at is two hours back. That
       is, line 281 was changed to
    
       final long end = currentMillis + (10 * 60 * 1000);
    
       and lines 478-479 to
    
       scheduleNextAlarmCheck(end);
    
    2) With no further changes I verified the bug by adding one event with
       the alarm set within ten minutes from the current time and one
       with the alarm set for later than ten minutes after the first
       alarm. The first triggers, but the second doesn't.
    
    3) Applied the rest and did the same test again to verify that both
       alarms now trigger.
    
    Bug: 69456806
    Test: atest packages/providers/CalendarProvider/tests/
    Change-Id: I7635258dc55257e5c8616a07f611d20b04fe0ff8
    Signed-off-by: Kim Lindberger <kim.lindberger@gmail.com>
Commits on Jun 22, 2017
  1. Merge "Add OWNERS in packages/providers/CalendarProvider" am: 8da754f

    chih-hung authored and android-build-merger committed Jun 22, 2017
    …am: 5de0d41 am: 1e487cd
    
    am: 8028388
    
    Change-Id: I26bdd65df73e77f66f3da025dc54b9d68dbe6c51
  2. Merge "Add OWNERS in packages/providers/CalendarProvider" am: 8da754f

    chih-hung authored and android-build-merger committed Jun 22, 2017
    …am: 5de0d41
    
    am: 1e487cd
    
    Change-Id: I81526ad92635144e95dedebd16ab8e798d0abb5f
  3. Merge "Add OWNERS in packages/providers/CalendarProvider" am: 8da754f

    chih-hung authored and android-build-merger committed Jun 22, 2017
    am: 5de0d41
    
    Change-Id: Ib30553c84f31876441ca382f9a2918c52c4bbad1
  4. Merge "Add OWNERS in packages/providers/CalendarProvider"

    chih-hung authored and android-build-merger committed Jun 22, 2017
    am: 8da754f
    
    Change-Id: I2e929f6a752c8df1da011acf406ea3930b50fac2
  5. Merge "Add OWNERS in packages/providers/CalendarProvider"

    chih-hung authored and Gerrit Code Review committed Jun 22, 2017
Commits on Jun 15, 2017
  1. Add OWNERS in packages/providers/CalendarProvider

    chih-hung committed Jun 14, 2017
    * Owners are selected from top CL approvals or owners.
      They will be suggested to review/approve future CLs.
    * OWNERS files are recognized by the new find-owners plugin, see .md files in
      https://gerrit.googlesource.com/plugins/find-owners/+/master/src/main/resources/Documentation/
    
    Test: build/make/tools/checkowners.py -c -v OWNERS
    Change-Id: I220ae866df40c9d05134d4e6d5c43724f6213f4d
Commits on Mar 22, 2017
  1. Add test config to CalendarProviderTests

    Dan Shi
    Dan Shi committed Mar 22, 2017
    Details about test configs changes are tracked in doc
    https://docs.google.com/document/d/1EWUjJ7fjy8ge_Nk0YQbFdRp8DSHo3z6GU0R8jLgrAcw/edit#
    
    Bug: 35882476
    Test: local test
    
    Change-Id: Ide8fec072aee8fb05619cae5c0dcce0cde9e8f5a
Commits on Mar 15, 2017
  1. packages/providers/CalendarProvider: Add APCT tests to the device-tes…

    Simran Basi
    Simran Basi committed Mar 15, 2017
    …ts suite.
    
    This CL adds the APCT tests within this project to
    a similar suite as CTS known as device-tests.
    
    The current method of running APCT tests in the infrastructure
    is unaffected.
    
    Bug: 35882476
    Test: `make dist device-tests -j` and local builds of
          continuous_instrumentation_tests & continuous_native_tests
    
    Change-Id: Idb501205311f6c82490cd2374ed5a4037aaffe49
Commits on Mar 3, 2017
  1. Clean up CalendarProvider2

    Makoto Onuki
    Makoto Onuki committed Mar 3, 2017
    - Set RESULT_OK in the receiver properly.
    - Don't create the provider instance in static; use a proper API for that.
    
    Bug: 35938801
    Test: adb shell am instrument -w com.android.providers.calendar.tests
    
    Change-Id: I34eada3d9f14e9688c6af9899b4c69c367e1f6b1
Commits on Feb 22, 2017
  1. Remove BG service from calendar provider.

    Makoto Onuki
    Makoto Onuki committed Feb 17, 2017
    The purpose of EmptyService was to keep the process running until
    it sends a broadcast with a delay which is scheduled with a handler...
    
    However "sending a broadcast with a delay" can just be done
    
    Bug 35350114
    
    Test: Manual tests with the verbose log enabled.
    - adb shell setprop log.tag.CalendarProvider2 VERBOSE &&
        adb shell am force-stop com.android.providers.calendar
    - Then create/delete events on the calendar app and monitor
    adb logcat | grep 'sendUpdateNotification'
    - Then check the alarm and make sure PROVIDER_CHANGED is scheduled
    at the right time.
    adb shell dumpsys alarm | grep -A 4 -P 'ELAPSED.*com.android.providers.calendar'
    
    Change-Id: Id2c0e10604bb7fdd3e9f8650295da83b3a62ecff
Commits on Feb 17, 2017
  1. Change target SDK for now for calendar provider

    Makoto Onuki
    Makoto Onuki committed Feb 17, 2017
    Test: boot and some manual tests (add acccount, add event and remove the account)
    Bug 35350114
    
    Change-Id: Ibae2c32d3e2e4304bb8052355efbaa35f9098594
Commits on Feb 10, 2017
  1. Stop using IntentService and use async receiver.

    Makoto Onuki
    Makoto Onuki committed Feb 10, 2017
    Also:
    - Set FLAG_RECEIVER_INCLUDE_BACKGROUND for ACTION_EVENT_REMINDER
    - Remove the wake lock; with goAsync() now it's not needed.
    
    Test: Manual test with: adb shell am broadcast --receiver-include-background -a android.intent.action.EVENT_REMINDER -d content:
    Bug 35207106
    
    Change-Id: Ib3afd744c5b94522d08778c367641d7c8f444a1f
Commits on Jan 18, 2017
  1. Merge "Prepare for removal of legacy-test from default targets" am: 5…

    paulduffin authored and android-build-merger committed Jan 18, 2017
    …644a6e am: 63c6f8b am: ea01c26
    
    am: 9ad7d0d
    
    Change-Id: I020ac951cc59af87b5c8b17297793f04aa6e11df
  2. Merge "Prepare for removal of legacy-test from default targets" am: 5…

    paulduffin authored and android-build-merger committed Jan 18, 2017
    …644a6e am: 63c6f8b
    
    am: ea01c26
    
    Change-Id: I384097f4dce1f68c9e880e8f2f04f01f4e791c58
  3. Merge "Prepare for removal of legacy-test from default targets" am: 5…

    paulduffin authored and android-build-merger committed Jan 18, 2017
    …644a6e
    
    am: 63c6f8b
    
    Change-Id: Ic3283992689de0d8edb59fd7f331833bfdcb0c2e
  4. Merge "Prepare for removal of legacy-test from default targets"

    paulduffin authored and android-build-merger committed Jan 18, 2017
    am: 5644a6e
    
    Change-Id: Iff3720214e22747498537162871b5ca2f37bbaa7
  5. Merge "Prepare for removal of legacy-test from default targets"

    Treehugger Robot Gerrit Code Review
    Treehugger Robot authored and Gerrit Code Review committed Jan 18, 2017
Commits on Jan 17, 2017
  1. Prepare for removal of legacy-test from default targets

    paulduffin committed Jan 17, 2017
    In preparation for removing junit classes from the Android API
    the legacy-test target will be removed from the
    TARGET_DEFAULT_JAVA_LIBRARIES. This change adds explicit
    dependencies on junit and/or legacy-android-test to ensure that
    modules will compile properly once it is removed.
    
    Bug: 30188076
    Test: make checkbuild
    Change-Id: I3c036858431a64946c0cb1a6f1b4f8056e79705f
Commits on Jan 11, 2017
  1. Rename language+country resources to just language

    roozbehp committed Jan 11, 2017
    Bug: 26496609
    Test: none
    Change-Id: Ia296ffe335fb523c2ebc5504c6dbe33498c306b0
Commits on Dec 6, 2016
  1. Merge "Remove unnecessary PROVIDER_CHANGED broadcast on launch" am: 4…

    rickywai android-build-merger
    rickywai authored and android-build-merger committed Dec 6, 2016
    …0cc0c9 am: fbd3414 am: 304dba3
    
    am: c875e20
    
    Change-Id: I68809549936e3393bc91ae427cd100b164c3c8b4
  2. Merge "Remove unnecessary PROVIDER_CHANGED broadcast on launch" am: 4…

    rickywai android-build-merger
    rickywai authored and android-build-merger committed Dec 6, 2016
    …0cc0c9 am: fbd3414
    
    am: 304dba3
    
    Change-Id: I9d22adac20bb486a45cf1d3b3be14c6c12021662
  3. Merge "Remove unnecessary PROVIDER_CHANGED broadcast on launch" am: 4…

    rickywai android-build-merger
    rickywai authored and android-build-merger committed Dec 6, 2016
    …0cc0c9
    
    am: fbd3414
    
    Change-Id: I803a750635fea96e4c39ae0d108f62ebfd7f225c
  4. Merge "Remove unnecessary PROVIDER_CHANGED broadcast on launch"

    rickywai android-build-merger
    rickywai authored and android-build-merger committed Dec 6, 2016
    am: 40cc0c9
    
    Change-Id: I79194c3e79661e311b6f7d33849ed73e1961b1ce
  5. Merge "Remove unnecessary PROVIDER_CHANGED broadcast on launch"

    rickywai Gerrit Code Review
    rickywai authored and Gerrit Code Review committed Dec 6, 2016
Commits on Dec 2, 2016
  1. Remove unnecessary PROVIDER_CHANGED broadcast on launch

    Snild-Sony authored and jzoran committed Mar 8, 2016
    When the calendar provider process launches, removeStaleAccounts() is
    called. This would cause a PROVIDER_CHANGED broadcast regardless of
    whether any changes were made or not -- starting all receivers of that
    action for no good reason.
    
    Let's only do the broadcast when something actually changed.
    
    Bug: 32997676
    Change-Id: I660742b0cb13297a6489fa340be52e372a91112a
Commits on Nov 14, 2016
  1. Update usage of ActivityManagerNative.

    Sudheer Shanka
    Sudheer Shanka committed Nov 11, 2016
    Bug: 30977067
    Test: N/A
    Change-Id: Ic06ffb7147e6dd16fd3ea11721a88aaee98fddbb
Commits on Sep 14, 2016
  1. Fix tests: Don't hardcode column indices.

    Sudheer Shanka
    Sudheer Shanka committed Sep 14, 2016
    Change-Id: I8be159c89c87a0f9cde44fba7bf823569e4d1a29
Commits on Jun 14, 2016
  1. Merge \"Merge \\\"CalendarProvider2: log failures to get the cached c…

    Leszek Ślażyński android-build-merger
    Leszek Ślażyński authored and android-build-merger committed Jun 14, 2016
    …alling package.\\\" into nyc-dev am: bcc65b8 am: c8db322\" into nyc-mr1-dev-plus-aosp
    
    am: 07f1586
    
    Change-Id: I7aebf2380ca19fa38abea58d5e8a14e5f32a431b
  2. Merge \"Merge \\\"CalendarProvider2: log failures to get the cached c…

    Leszek Ślażyński android-build-merger
    Leszek Ślażyński authored and android-build-merger committed Jun 14, 2016
    …alling package.\\\" into nyc-dev am: bcc65b8 am: e34e1da\" into nyc-mr1-dev-plus-aosp
    
    am: a3133a3
    
    Change-Id: I2bf9f7417d66054ace0fc7436fee3f7c402e30be