Originally Posted by stashcroft
Not seeing any time in suspend_backoff. I think the fix for that on the 25th has worked.
I'll keep digging around to see if I can figure out why I'm suddenly seeing time in PowerManagerSevice.WakeLocks.
I've not installed any new apps.
Looks like it is something in bluetooth. I've got bluetooth turned on but not connected and the process com.android.bluetooth is running.
Running 'dumpsys power' every few seconds shows that the StartingObexMapTransaction partial wakelock is always taken.
BBS doesn't see this and says that lock has only been taken for a few minutes where as using dumpsys shows it taken for hours.
So I wonder if there's a path in the bluetooth app which doesn't release the lock or a bug in the kernel where the bluetooth app calls to release the lock, BBS sees that but in fact the lock isn't released.