My wife and I both have the AT&T US galaxy S4 (32 GB). I have loaded GSAM battery monitor and the XDA version of BetterBatteryStats, and what I've noticed is that there is no TIME listed for bluetooth in GSAM (nor any usage). If i check the graphs -> more graphs in BBS, there is nothing there under the bluetooth graph. I have enabled bluetooth in both of our phones and have tested the usage by transferring images and videos between our phones. Nothing ever shows up.
I went to my local AT&T store, downloaded GSAM and made sure bluetooth was on, on their floor model S4s and the same thing happens, no bluetooth stats.
Previous to my S4, i had purchased an HTC One, which with GSAM loaded, always showed a running time in GSAM next to "bluetooth" whenever bluetooth was enabled.
Has anyone else noticed this?
Related
I've had my N4 since the day it was released and the battery has been generally acceptable.....until I upgraded to 4.3 (stock, rooted).
BetterBatteryStats is indicating the suspend_backoff wakelock is rampant. WakelockDetector is showing I'm only getting 20% deep sleep on days I'm only lightly using my phone. On Android's Battery screen "Android OS" is listed as the top culprit, consuming 40% or more of the total battery.
Google/XDA searches indicate suspend_backoff is related to Chrome, but I'm convinced this is somehow a wifi connectivity problem as this wakelock ONLY happens when connected to my work wifi. On the weekends when not working my battery is fine and I don't see suspend_backoff. If I don't connect to my work wifi while at work suspend_backoff does not show up at all and I'm deep sleeping at 80%.
Unfortunately at work I don't have the capability of configuring/swapping wifi hardware/settings, so I'm limited to finding a solution on my end. Hopefully the solution isn't to have to sit on mobile data all day long instead of connecting to my work wifi.
Any suggestions?
hfuizo said:
I've had my N4 since the day it was released and the battery has been generally acceptable.....until I upgraded to 4.3 (stock, rooted).
BetterBatteryStats is indicating the suspend_backoff wakelock is rampant. WakelockDetector is showing I'm only getting 20% deep sleep on days I'm only lightly using my phone. On Android's Battery screen "Android OS" is listed as the top culprit, consuming 40% or more of the total battery.
Google/XDA searches indicate suspend_backoff is related to Chrome, but I'm convinced this is somehow a wifi connectivity problem as this wakelock ONLY happens when connected to my work wifi. On the weekends when not working my battery is fine and I don't see suspend_backoff. If I don't connect to my work wifi while at work suspend_backoff does not show up at all and I'm deep sleeping at 80%.
Unfortunately at work I don't have the capability of configuring/swapping wifi hardware/settings, so I'm limited to finding a solution on my end. Hopefully the solution isn't to have to sit on mobile data all day long instead of connecting to my work wifi.
Any suggestions?
Click to expand...
Click to collapse
In Settings, Wifi, Advanced Settings turn Network notification and Scanning always available off and see if it helps. Drainage can also be an issue when the Wifi signal is weak, but it can be Google Now! related among other things, Now! likes to give you fresh cards like traffic, news, nearby things and weather, turning Now! off entirely (voice search still works) could still be help. Also using other apps than Google. I know, hardly a real soluton but I replaced as many as I can.
No, wifi scanning is irrelevant since OP wants to use wifi.
What radio are you on OP? I'm assuming .84?
Yep, .84 radio, Google Now is disabled
Anybody?
rom kernel info? screenshots of the issue?
Back in the Galaxy S II days it was related to Google Chrome with the tilt scrolling. I always disable it though.
Sent from my Nexus 4 using Tapatalk
I am experiencing the same issue starting from yesterday, God knows why. The most common advice is to disable tilt-scrolling in Chrome but as far as I could see the Development Tools option has been removed from teh settings. Any other ideas?
could it be because you're using Touch Control for S2W or D2W?
Your work's wifi may have a combination of 2.4 and 5 GHz signals. I would get this wakelock if I allowed android to choose automatically which band to connect to, but if I forced either 2.4 or 5, the wakelock would let up.
Lookas a kernel bug, which has been fixed in teh latest Franco's release.
I'm having major issues with my g2. I've tried a factory reset, but no matter what I do, the phone's battery drains quickly and the "android os" stays awake for 3.5 hours, even though the screen has only been on for two.
I have both BBS and Gsam, but there are so many different wake locks listed, I don't know what's normal and what's not. I've attached my latest BBS logs. Can someone with expertise help me out with some feedback?
Most your wakelocks seem to be location services... That can be decreased by disabling google now, google location reporting and alternatingly using unbounce xposed module
Hey guys...
Just here to say that I unplugged this phone at around 5 in the morning, and around 5 hours later its already down to 74%.
What did I do? Only about 10 minutes of mobile hotspot, a 2 minute phone call, and three text messages. The rest just idling...
1/4th of my battery life for just that?
What the heck?
Everything is disabled and the screen brightness is low... Whats the matter with this phone?
Looks like something is keeping your device awake.
Can you please add some screenshots of your battery graph?
In addition, you can try to boot into safe mode. If your problem is gone in safe mode, a third party app is interfering.
If you're rooted, try installing Wakelock detector or BBS (Better Battery Stats) and check out what is waking up your device.
If you use Gas Buddy, it was known to be causing massive bluetooth wakelocks. Either uninstall it or update it to the latest version.
Set your wifi to 2.4 ghz only. On 6.0 and 6.0.1, the 5 ghz band has been causing abnormal battery drain and keeping phones from entering doze mode. Here's the issue being reported: https://code.google.com/p/android/issues/detail?id=197460
If neither of these make a big improvement, you'll have to use your battery stats (and if rooted, use Better Battery Stats or Wakelock Detector) to specifically see what's keeping the phone awake. In either of these apps, filter the view by "Alarms" or "wakeup triggers" and you'll see what the heavy hitters are.
Be sure to go into Location>Settings and turn off wifi and bluetooth scanning.
Hi.the maps app isvuding WiFi and gps even though both are disabled and I'm not using it... Any ideas?
Hi All,
We have two S7 Edge units - 1 from T-Mobile the other from AT&T. Both are having a battery drain issue.
It seems Android Kernel and Android System are draining the battery constantly. The phone doesn't seem to be falling into deep sleep either.
Average rate of battery drain is 7-10%/hr while idle (screen-off).
The T-Mobile phone has the "U Firmware" installed.
The AT&T Phone is stock with the latest OTA installed.
I've attached the GSam statistics here:
https://i.imgur.com/sfCeHoj.jpg
Note: I've tried the following
Disable Wi-Fi, Bluetooth, Location, NFC
Disable Google Backup
Disable Wi-Fi and Bluetooth Scanning (Location Services)
Updating Play Store & Galaxy Store Applications
Removing unnecessary applications
Clearing Cache partition from Recovery
Rebooting 3 times simultaneously
So I noticed my new 6T was having some heavy drain on standby so decided to install GSam.
I've clicked a screenshot of the GSam page below
https://i.imgur.com/qFE3xCe.jpg
Google play services is showing crazy amount of wakelocks. Anyone knows what's 'dozeservice'?
My battery stats show I've last charged my phone 17 hours before, OST 1 hour and 57 minutes as of now. Majority of the time phone was on WiFi and Bluetooth on (connected to my smart watch), adaptive battery disabled.
My battery stats: https://i.imgur.com/BZOL8Ep.jpg
Any solution?
These types of reports are generally not that informative - you should take an adb bugreport and then parse it with the Google Battery Historian: https://github.com/google/battery-historian. The Wakelock you are seeing is most likely not the cause of the CPU drain, especially when the Doze service is up top (which puts the phone to sleep). The NlpWakelocks are most likely due to you having Google Location Reporting turned on. Turning it off would conserve some battery, although you will also lose that functionality. But definitely give that a try and see how it goes (you will need to setup a Docker instance to get it up though)...