Why is Doze mode not affecting AlarmManager setExact() method?

[Syed Noorullah Shah]

I'm trying to test the behavior of my Android app when the OS goes in Doze mode. I'm using a gennymotion emulator running Android API 25. The application launches an IntentService through the AlarmManager using the method setExact with type RTC_WAKEUP. I set the alarm to fire after 1 minute (only for testing purposes).I succeed to put the emulator in IDLE state by running the suggested dumpsys (force-idle) command.
When the device is IDLE I'm still able to see the IntentService being launched by the alarm. This should not be the expected behavior according to the docs. I was expecting the opposite(since according to docs, setExact() is not triggered if the device is on doze mode).
I have even tested this on a real device (running Android 6) and getting the same results.

Is this a bug? Or am I missing something?

 

[Rukbat]

Moving this to the developer forum for better exposure. (And I apologize for not giving you an answer, but I've never played with setExact() or doze.)

 

[hallux]

Our pals down in the developer's area might be able to help - https://forums.androidcentral.com/android-developers/

You'll need to be a member to post new threads there, and to reply to this thread - see this link for instructions on how to join Android Central.

We can also have this thread moved there so it gets the visibility it deserves.

Edit - posted at the same time as @Rukbat

 

[mustang7757]

Duplicate post

https://forums.androidcentral.com/showthread.php?t=979885