comments from Colin I've worked through all the images now and can see that deep suspend sometimes fails to work completely because of a series of COMM events that cause excessive wakeups. Typically, in this scenario, one sees 300-700 CONN wakeup events over a 300 second interval. This either prevents deep suspend from occurring, or wakes deep suspend almost immediately it occurs. In this scenario, instead of a 7-10mA deep sleep, I observe ~70-100mA being drawn.
I can trigger this on all the images I've now tested. One easy way to trigger this is via the USB adb connection and yanking out the cable and then going into deep sleep without exiting adb and then going into deep sleep. I also believe going into deep sleep while connected to adb and then yanking out the USB cable also can cause this issue. If I recall correctly, the CONN event relates to the USB connections and does seem to correlate with this adb connection over USB. This explains the difficulty I had bisecting the issue earlier on. I believe I may have been careless in putting the device into deep sleep with USB connected, and then disconnecting before measuring deep sleep current with the multimeter. So, for the anecdotal reports of battery life being reduced: a) It may be this USB issue causing deep sleep to be interrupted by CONN events. b) It may be something entirely different. it's hard to say. But I do now have evidence that between revision 153 and 202 there are not any observable changes in deep sleep characteristics. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1372413 Title: Extensive battery drain on RTM To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1372413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
