Obsolete
Status Update
Comments
gi...@gmail.com <gi...@gmail.com> #2
Red
gi...@gmail.com <gi...@gmail.com> #3
Hi, I see no one has even read this bug report... Typical from Google...
Anyhow, found the problem: the wifi range extender. Maybe it is sending packets on the net that is keeping wifi alive and preventing phone to sleep well, causing a 2% per hour drainage. Tonight I kept it off and lost 2% in 9h.
My 3 Samsung devices (A3, S6 and Tab S2) are not experiencing this problem, so it must be a bug in nexus 6p kernel.
May I please have a feedback?
Anyhow, found the problem: the wifi range extender. Maybe it is sending packets on the net that is keeping wifi alive and preventing phone to sleep well, causing a 2% per hour drainage. Tonight I kept it off and lost 2% in 9h.
My 3 Samsung devices (A3, S6 and Tab S2) are not experiencing this problem, so it must be a bug in nexus 6p kernel.
May I please have a feedback?
sa...@google.com <sa...@google.com> #5
Thank you for your feedback. We assure you that we are doing our best to address the issue reported, however our product team has shifted work priority that doesn't include this issue. For now, we will be closing the issue as won't fix obsolete. If this issue currently still exists, we request that you log a new issue along with latest bug report here https://goo.gl/TbMiIO .
Description
As of day one I am experiencing a constant discharge overnight of 20% for no apparent reason.
Phone is stock, not rooted, original bootloader. The problem is happening also in safe mode, so cannot be a 3rd party app.
Location and wifi are on but òlocation scanning and google backup is off.
I am only syncing google stuff (contacts, calendar, inbox, etc.) and whatsapp, no facebook.
I also have a Samsung S6 Edge+ configured in exactly the same way (same apps, same launcher, same versions of the apps, same network setting etc.) and at night ot runs ok with a normal discharge of 3-4% per night.
I believe the problem must be related somehow to wifi: if I upload the attached bugreport to battery historian I see netmgr_wl being on top of Kernel Wakesources.
Please someone could check the attached bugreport to find out the real problem?
Thanks