KJ78
Well-known member
I take comfort at night knowing that Google is worried enough about the few watts of power wasted by a charging phone that it has to warn us incessantly about it with no option to turn it off.
I can't swear this will work for everyone, but it worked for me. I use a clock app when charging and after the lollipop upgrade I started getting the bright white, woke-me-up-at-3am-battery-fully-charged notifications. My research indicated that these notifications only happen when the phone is active or unlocked. In Kit-Kat, the phone would automatically lock using the clock app after about a minute, but this was not so in Lollipop. So, it occurred to me I might have to manually lock (secure, make-it-need-a-pin-to-use-it) myself. I did this by plugging in the charger, turning on the clock app, manually pressing the power button quickly to make the screen turn off, then pressing it again to make the screen turn on. The clock app was displayed and battery notification never displayed at 100%. Once again, I could sleep through the night.
I hope you find this useful.
I can't swear this will work for everyone, but it worked for me. I use a clock app when charging and after the lollipop upgrade I started getting the bright white, woke-me-up-at-3am-battery-fully-charged notifications. My research indicated that these notifications only happen when the phone is active or unlocked. In Kit-Kat, the phone would automatically lock using the clock app after about a minute, but this was not so in Lollipop. So, it occurred to me I might have to manually lock (secure, make-it-need-a-pin-to-use-it) myself. I did this by plugging in the charger, turning on the clock app, manually pressing the power button quickly to make the screen turn off, then pressing it again to make the screen turn on. The clock app was displayed and battery notification never displayed at 100%. Once again, I could sleep through the night.
I hope you find this useful.
I know this is old and I myself have this issue but on a note 3 and I want to clear things up a bit..the reason you guys with a nexus 7 that don't have this issue is because it's a Samsung thing not a Google thing. I've had this issue since my sgs3 and previously an xposed module would of worked but it doesn't work on lollipop (yes xposed now works for TouchWiz roms)
Samsung fixed this in a Lollipop release months ago, see post #31. Anyone still experiencing this problem will be running firmwares based on much older Lollipop releases.