Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/caarmen/testalarmmanager
https://github.com/caarmen/testalarmmanager
bug-reproduction
Last synced: 11 days ago
JSON representation
- Host: GitHub
- URL: https://github.com/caarmen/testalarmmanager
- Owner: caarmen
- Created: 2015-08-02T08:38:13.000Z (over 9 years ago)
- Default Branch: master
- Last Pushed: 2015-08-03T08:56:12.000Z (over 9 years ago)
- Last Synced: 2023-03-24T00:21:48.974Z (over 1 year ago)
- Topics: bug-reproduction
- Language: Java
- Size: 207 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
Demonstration of Alarm Manager bug on Samsung Galaxy S6
=======================================================
Summary:
--------
Alarms are not scheduled at the proper time in the following cumulative conditions.
Note that the alarms are actually scheduled BEFORE the expected time, whether ```set```
or ```setExact``` are used, which is against [the documentation of the AlarmManager class] (http://developer.android.com/reference/android/app/AlarmManager.html#set%28int,%20long,%20android.app.PendingIntent%29).
The conditions:
* The alarm is scheduled in the future at 600 seconds [1]
AND
* The applicationId does NOT contain the word "alarm"
AND
* The application creates an account on the device
If any one of these conditions is not true, the alarm is scheduled correctly.
Steps to reproduce:
-------------------
* Modify app/build.gradle: change the applicationId to anything that does NOT contain "alarm".
* Build this app:
```
./gradlew clean assembleDebug
```
* Install the app to an S6 device
* Set the "Alarm delay" to 600 seconds.
* Tap the enable switch to schedule the alarm
* Run the following command to see at what time the alarm is really scheduled: ``` adb shell dumpsys alarm | grep -B1 -A4 tag.*carmen ```
* => You will notice that the alarm was not scheduled at the expected time. It is scheduled before the expected time.
* Tap the switch to disable the alarm
* Run the dumpsys alarm command again
* => You will not see the alarm, which is correct.
* Tap the switch to enable the alarm again
* Run the dumpsys alarm command again
* => You will notice that the alarm was once again incorrectly scheduled. Furthermore, you can see that it was scheduled at the same time the previous alarm was scheduled.
Any one of the following changes will result in the alarm being properly scheduled:
* Change the delay of the alarm. I'm not sure what values of alarms have issues, but I've noticed that alarms in the near future (like 60 seconds) don't have the problem.
* In build.gradle, make sure the applicationId contains the word "alarm"
* In AlarmManagerTester.onCreate, comment out this line:
```
// AccountUtils.createAccount(this);
```
[1]: Note on the alarm delay:
-----------------------------
As for the alarm delays having this bug, there have been different observations.
* On one day and one S6, I saw the bug on alarms longer than 596 seconds
* Another person on a second S6 noticed the bug on alarms at multiples of 5 minutes plus or minus 5 seconds.
* On another day on a third S6, I noticed the bug on 600 seconds and 403 seconds, but not 60 seconds. I didn't do enough testing to find a pattern.