Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PoM Critical AlarmManager bug #10

mudar opened this issue Jan 9, 2014 · 0 comments


Copy link

@mudar mudar commented Jan 9, 2014

I have noticed 2 issues with the use of the AlarmManager.

The first one is a performance issue: once started repeatingly, the alarm is never cancelled, even when PoM is not running. Meanning that the app will repeatedly send a broadcast every minute.

The other issue could be a bigger problem: using AlarmManager.RTC every minute does not wake the phone (from deep sleep) to trigger the alarm (which is supposed to stop PoM). Meaning that if a user sets PoM for 1 hour, the phone will stay in airplane mode after that duration until the user wakes up the phone (turning on the screen). This is critical since the user cannot receive calls for a longer duration than expected!!

To reproduce: set PoM to 5 minutes, disconnect phone charger and turn off display. If left idle, the phone cannot receive any phone calls 7 or 8 minutes later.

I have not tested using the original app, but that's the case currently in my fork and very probably the case in the original app since my modifications are not related to the AlarmManager and BroadcastReceiver.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
1 participant
You can’t perform that action at this time.