Issue 36949180 mentiones https://code.google.com/p/android/issues/detail?id=189948:
"My apologies. This is apparently semi-documented behavior, if comments from Dianne Hackborn on a G+ post constitute "documented": https://plus.google.com/+AndroidDevelopers/posts/94jCkmG4jff"

I cannot reproduce this semi-documented behavior.
Android M, MRA58K Nexus 5 and MRA58N Nexus 6

My foreground service has an associated notification and I hold a partial wake lock. Unfortunately Doze mode takes over and my wake lock is broken. I was only able to prevent this by an opt-out from battery optimization..

Can we get some more details on when exactly does a foreground service prevent the device from dozing? This needs to be documented properly.

I'm implementing an app for sleep tracking which is broken due to doze mode, definitely this belongs under the other use-cases category

- Steps to reproduce the problem (including sample code if appropriate).

XY extends android.app.Service
public int onStartCommand(Intent intent, int flags, int startId) {
...
startForeground(NOTIFICATION_ID, notificationBuilder.build());
final PowerManager pm = (PowerManager) context.getSystemService(Context.POWER_SERVICE);
cpuLock = pm.newWakeLock(PowerManager.PARTIAL_WAKE_LOCK, LOCK_TAG);
cpuLock.acquire();

// gathering sensor data through sensor API
...

- What happened.

Sensor data gathering stops due to the device entering doze mode, even the foreground service is running and the wake lock is held

- What you think the correct behavior should be.

Based on "semi-documentation" by Dannie Hackborn https://plus.google.com/+AndroidDevelopers/posts/94jCkmG4jff device should not enter doze mode.

Issue 37070074

Mentioned issues (2)

Links (13)

Issue metadata