Hi all,
The s3 mini from my girlfriend has a intermittent problem. (Stok no root)
Sometimes appears a wakelock keeping the movile on (no deep sleep) until reboot. Then maybe 2 or 3 days working grate and then appears the wakelock again.
Exploring with battery stats I can see "radio-interface" wakelock permanent when kernel is failing. And "svnet" walelock about 70% of the time.
Reboot again and solved. But some days later... again return home after 14h with just 20% battery left. When movile working fine arrives at 70% batery left (few use)
Anyone knows what can cause this? Anyone else with this problem?
Thnxs 4 your attention!
Do not look into the percentage of application.. "Count" is what that matters the most... Charge the phone to 100%, under batterstat set it for Partial Wakelocks and Since Unplugged. For every app under this setting, there will a number indicating the count. Find the application with the Most Count, force stop it and test the battery backup Betta ta uninstall test and respond back
HI all,
After updating to 4.4.2, I have serious battery drain. I did a full wipe and still the same. I did a factory reset as well. My battery would only last 5-7 hours on the average without constant use. Tried installing custom and stock kernel but still the same issue. Im on firmware 4.19, viper 5.0 if that would help. Appreciate any response.
We need more information
Install betterbatterystats or Wakelock Detector.
Charge your phone to 100%
Use your phone "as you normally would"
After the phone has been on for an hour or two, sends us your wakelocks for all screens
Galactus said:
We need more information
Install betterbatterystats or Wakelock Detector.
Charge your phone to 100%
Use your phone "as you normally would"
After the phone has been on for an hour or two, sends us your wakelocks for all screens
Click to expand...
Click to collapse
Hi, thanks for a response. I just did another reformat and complete 1 cycle, everything seems to be fine now.
Currently my average is around 18 hours. Used 40% in 11 hours with more than 2 hours screen time and wifi /data always on.
Dev Edition -> GPE also serious battery drain
Hi,
I'm not the OP but I have the same problem, significantly worse battery life after converting my Developer Edition to Google Play Edition.
For conversion I used the pre-rooted RUU available in this thread. The only issue that I encountered was having to use [URL="http://firewater-soff.com]firewater[/URL] instead of rumrunner or moonshine to get s-off.
I used Titanium Backup to restore apps+data (I did not restore system apps/data).
Pre-conversion my battery would last 18-22 hours on average with rooted stock 4.4.2/HTC Sense 5.5, about 16-18 hours on Cyanogenmod 11.
Post-conversion battery life is 5-7 hours, often connected to WiFi with very low screen usage. Phone is consistently warmer than before conversion.
I've disabled Google Now, set Location Mode to "Battery" and turned off Google Location Reporting.
I've attached screenshots from Wakelock Detector and GSAM. (I can also post additional screenshots/details if needed). Additional stats for top-listed usage apps/services from GSAM:
GSAM Kernel Wakelocks---> (#1) Combined App Wakelocks: 21m; (#2) msm_hsic_host: 12m; (#3) wlan_ctrl_wake: 7m
GSAM App Details--->Facebook: CPU Usage 7m, Keep Awake 16s, Wakelocks 70, Num. Times Waking Device 61
GSAM App Details--->Android System: CPU Usage 4m, Keep Awake 2m, Wakelocks 907, Num. Times Waking Device 92
GSAM App Details--->Google Play Services: CPU Usage 1m, Keep Awake 1m, Wakelocks 1508, Num. Times Waking Device 309
GSAM Phone Radio--->Signal Strength: Medium 72%, High 24%, Low 4%, Scanning for Signal: 8m
GSAM Screen On---> Screen On: 12m, Discharge While On/Off: 17%/68%, Screen Brightness % Time: Dark 11%, Medium 6%, Light 28%, Bright 55%
Any insights would be greatly appreciated!
Thanks!
ryski said:
Hi, thanks for a response. I just did another reformat and complete 1 cycle, everything seems to be fine now.
Currently my average is around 18 hours. Used 40% in 11 hours with more than 2 hours screen time and wifi /data always on.
Click to expand...
Click to collapse
that's totally normal to drain 40% battery with 11 hours & 2+ screen-on time
Sent from my One using Tapatalk
---------- Post added at 06:03 PM ---------- Previous post was at 06:01 PM ----------
etm001 said:
Hi,
I'm not the OP but I have the same problem, significantly worse battery life after converting my Developer Edition to Google Play Edition.
For conversion I used the pre-rooted RUU available in this thread. The only issue that I encountered was having to use [URL="http://firewater-soff.com]firewater[/URL] instead of rumrunner or moonshine to get s-off.
I used Titanium Backup to restore apps+data (I did not restore system apps/data).
Pre-conversion my battery would last 18-22 hours on average with rooted stock 4.4.2/HTC Sense 5.5, about 16-18 hours on Cyanogenmod 11.
Post-conversion battery life is 5-7 hours, often connected to WiFi with very low screen usage. Phone is consistently warmer than before conversion.
I've disabled Google Now, set Location Mode to "Battery" and turned off Google Location Reporting.
I've attached screenshots from Wakelock Detector and GSAM. (I can also post additional screenshots/details if needed). Additional stats for top-listed usage apps/services from GSAM:
GSAM Kernel Wakelocks---> (#1) Combined App Wakelocks: 21m; (#2) msm_hsic_host: 12m; (#3) wlan_ctrl_wake: 7m
GSAM App Details--->Facebook: CPU Usage 7m, Keep Awake 16s, Wakelocks 70, Num. Times Waking Device 61
GSAM App Details--->Android System: CPU Usage 4m, Keep Awake 2m, Wakelocks 907, Num. Times Waking Device 92
GSAM App Details--->Google Play Services: CPU Usage 1m, Keep Awake 1m, Wakelocks 1508, Num. Times Waking Device 309
GSAM Phone Radio--->Signal Strength: Medium 72%, High 24%, Low 4%, Scanning for Signal: 8m
GSAM Screen On---> Screen On: 12m, Discharge While On/Off: 17%/68%, Screen Brightness % Time: Dark 11%, Medium 6%, Light 28%, Bright 55%
Any insights would be greatly appreciated!
Thanks!
Click to expand...
Click to collapse
why don't you revert back to stock and see if it helps
Sent from my One using Tapatalk
kamilmirza said:
that's totally normal to drain 40% battery with 11 hours & 2+ screen-on time
Sent from my One using Tapatalk
---------- Post added at 06:03 PM ---------- Previous post was at 06:01 PM ----------
why don't you revert back to stock and see if it helps
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Sure, I'll revert to stock if I have to do so. I was hoping to solve this problem and stick with GPE if I can.
etm001 said:
Sure, I'll revert to stock if I have to do so. I was hoping to solve this problem and stick with GPE if I can.
Click to expand...
Click to collapse
GPE Roms don't have battery life thats as good I find (despite phone sites saying it lasts longer). It shouldnt be as bad as it is for you though. Only wakelocks I can see are from Google Play Services and a few from facebook and your weather app.
I find betterbatterystats better than wakelock. Personal preference
Hey guys, I too have a problem with battery drain
Have the One now since short before Christmas and began with Viper ROM 3.5, then an update to 4.1 and further to 4.2 and 4.3 both via OTA, then i had random reboots and it was just for half a minute till it began a reboot again. Then fresh install with full wipe and flashing full ROM 4.3, then again after 3 days random reboot where it doesnt go past the bootscreen till i did a full wipe again
Then update to 5.0.0, and ever since then the phone is sort of over clocked, on a sense ROM 2 of the cores run on at least 1134MHz if its on idle, if i do sth all 4 cores run on 1134 and over (mostly 1728MHz). On an AOSP ROM 2 cores are on 1026MHz on idle and no gapps installed
Also on viper ROM it was that even though it was connected to the charger it discharged to 0% over night.
So, any suggestions what it could have and how it could be fixed?
Or should i send it in? (Also i am just dev unlocked and s-on, is that maybe a problem when i send it in?)
Greets Vauvenal7
Hi everyone,
The battery drain on my phone is atrocious, and I'm thinking it's a software related issue rather than hardware (phones aren't really my area, so this thinking isn't based on much). Now I don't use my phone much, and when in standby pretty much all of the toggles are turned off (no wifi, data, bluetooth, NFC). Yet even so, if I charge my phone and then unplug it before going to sleep, in the morning I'll only have 20-50% charge left. This is the most common outcome, though once or twice this drain hasn't happened and I've had 2 or 3 solid days of use.
As mentioned phones aren't really my area, but I've installed several apps (Doze, Gsam, Wakelock detector) and tried to lock everything down when not in use, without results.
I'm using Cyanogenmod 13.0-20160908, and Nova Launcher. I've got screenshots from Gsam, but not sure how to add them here (or where to upload them to link to them). Some of the details include (after being charged then not used till I took the screenshots):
Used 77% in 21h 9m (3.6%/h - 13h 54m Active)
Phone 0%
Screen 00:13:49 2%
Phone Radio 21:09:31 7%
Wifi Active 21:09:31 2%
Held Awake 13:40:30 12%
App Usage 76%
Then from App Usage breakdown:
Kernel (Android OS) 25.7% --> CPU Usage (Background Only) 2h 36m, Keep Awake 13h 35m
CyanogenMod System 20.6% --> CPU Usage (Background Only) 2h 5m, Keep Awake 26s, No of Wake Locks 233, No of times waking device 40
Phone Services 17.7% --> CPU Usage (Background Only) 1h 47m, Keep Awake 3m, No of Wake Locks 11107 --> Wakelock Detail: RILJ 3.6m (9884), ServiceStateTracker 15.5s (1223).
Let me know what details would be useful, and thanks in advance for any help. If flashing another rom or back to miui would be likely to fix things I'll do it. I have a few other minor niggles, but if this can be fixed I'd appreciate it.
I'm hoping someone can assist me. I can't seem to find much information regarding the "video2" kernel wakelock.
I just charged my phone to 100% over night. I have only used it for about 19 minutes and the battery is at 75%.
I am rooted, on the latest OOS - stock; running xposed and magisk (latest versions)
I have forcedoze and leandroid running and I also use wakeblock to limit some wakelocks.
I use an app called WLD (Wakelock Detector) - to show me what wakelocks are being used and I see one in particular that is "video2". What could this be?
video2 shows 3h 28m x1244 in WLD
PowerManagerService.WakeLocks shows 6m 20s x407
All the other kernel wakelocks are under 1m
leandroid should be turning off my network settings when the screen is off, and only turning it on hourly for 60 seconds to get the occassional notifications if there are any and then turn off again.
I am normally connected to WiFi and my location services (GPS) is turned on as well, but as I mentioned, when it's not in use leandroid should be powering them off.
I'm trying to figure out what is using up over 25% of my battery only after 19 mins of use. When I go into settings to look at the battery I see the following:
Screen Usage since full charge - 19m
Android system - 4%
Phone Idle - 2%
Android OS - 2%
Cell standby - 1%
Screen 1%
Use Betterbatterystats and report back all findings from Alarms tab
Sent from my ONEPLUS A3003 using Tapatalk
RASTAVIPER said:
Use Betterbatterystats and report back all findings from Alarms tab
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
Thanks for the response, I exported all the logs from BBS. I ended up charging my phone to 100% again and then just left it doze for a bit and once again it eats through the battery idle.
I hope these logs help.
I am uploading screenshots from my phones battery and the BBS screens.
I have left my phone idle since yesterday. SOT is only 3 mins and I'm down to 61%. I would really appreciate any help I can get.
Well, I assume for those who had a look over this thread, you were as baffled by this issue as I initially was.
After a lot of trial and error, I believe I resolved my issue. To help others (in case other users run into a similar issue as I), I will write up a detailed summary of what I did to fix the issue and the apps I used. For now a quick summary.
I would like to bring up an interesting fact, and I'm not sure if my scenario is just an anomaly, but it turned out that the reason I was having this issue is because of having "doze mode" enabled in the developer menu. Apparently this setting conflicted with the battery saving apps I run such as forcedoze and leandroid.
If you use custom apps to save battery, make sure you disable force doze on your OP3T. I did a few other changes on my phone, but after disabling this option, I saw an immediate difference in my phone battery when it was idle and screen off. I only lost 1% battery in about 5 hours, whereas before it seemed less than 1 hour.
For several years, my Note 4 would end the day at 75% to 80% charge with light usage - one or two quick calls and checking a few texts.
About 6 weeks ago, something changed. With the same usage pattern, in the same locations, the battery is now at 35-40% at the end of the day.
I though the battery was at fault and bought a new one, but have exactly the same pattern.
I bought "Better Battery Stats" app to see what's going on. The summary stats shows Deep Sleep 76% and Awake Screen Off 23%. Interestingly, Wi-Fi On and Wi-Fi Running are both 100%. I have not made any changes to Wi-Fi, Apps or other settings.
Under Kernel Wakelock, PowerManagerServiceWakeloks is 14%, and "bluesleep" is 10%.
Under Partial Wakelock, the highest is bluedroid_timer at 3%
Under Alarms, com.googleandriod.gms is 57%.
Does anyone have suggestions on where to look to find the root cause issue?