Related
Hey guys,
Just updated to the x10 after my samsung galaxy died on me, so far i am rather happy - except for the lack of root, but that will come.
I have noticed many complaints on the forum about battery life, and have experienced the same thing myself. From my experience, i think this looks like the same issue that was faced on a leak of 1.6 for the galaxy - it was referred to as the "No Sleep Bug".
TBH, the name says it all - for some reason, in many builds of android 1.6, phones were not sleeping correctly. There are many theories as to why, from cpu not being allowed to sleep, to permanent communication with google servers.
Despite all these different theories, one thing seemed to fix the problem - turning off all location services. Some people argue that a different carrier build, turning off just 'share with google' under location, turning off just AGPS etc. would fix it, but from my experience, the only real way to fix the issue was to turn off all GPS usage unless you need it. The once you have used it, reboot your phone.
This fix obviously sucks, and a new fix has recently been released by a veritable android-demigod around the Galaxy.
HERE IS A THREAD ABOUT NO SLEEP ON i7500 GALAXY;
(ok, some stupid rule says i can't post links - can a mod help me out?)
HERE IS THE FIX FOR THAT PARTICULAR BUG;
(ok, some stupid rule says i can't post links - can a mod help me out?)
LINKS ARE IN POST #5 - THANKS TO ONDOTEAM (would still be nice to get them in this original post though)
Now, from my experience, no sleep behave exactly the same way on the x10 as it does on the Galaxy;
1) I turn of all location services, and my battery life at least doubles.
2) After said turning off of services, 'spare parts' no longer says 100% running time under battery usage - in fact it can be as low as 10%.
These two factors are identical to my experience with Galaxy. SO; is there any way drakaz's fix can be applied to our X10's? It seems to me that the files he mods are standard Android system files, not sony/samsung specific.
Now i am no developer, so i dont know it this is possible - the first question that comes to mind for me is "do we need root access, or can this be done through developer tools using the android SDK?"
Can anyone help shed anymore light on this?
Seems to work for me. I disabled all location services. Spare Parts went down from 100% to 7.6%.
I'll just have to enable GPS when I need to use it..
Awesome! Glad to hear it has helped.
Let's keep testing this guys - if it does show up to be a big cause, then perhaps the devs around this place can help is figure out a patch for Drakas' mod to make it work with our x10's!
n3man said:
Awesome! Glad to hear it has helped.
Let's keep testing this guys - if it does show up to be a big cause, then perhaps the devs around this place can help is figure out a patch for Drakas' mod to make it work with our x10's!
Click to expand...
Click to collapse
Hello send me a PM with links, I will try to post it
http://androidforums.com/samsung-i7500/61168-no-sleep-has-nothing-do-anything.html
http://androidforums.com/samsung-i7500/78471-no-sleep-bug-fixed-drakaz.html
Links from n3man
No sleep is easy to fix, took me a while to figure it...
Turn your screen brightness from manual to auto, spare parts will now start showing proper running stats, no more 100% running.
The screen is a little dark in auto but it will cure the 100% running.
GPS and location services etc make no difference to my X10i, I am running the 1.6 version unbranded UK handset, the only thing to stop mine running 100% is to put the screen on Auto.
ronnyuk said:
No sleep is easy to fix, took me a while to figure it...
Turn your screen brightness from manual to auto, spare parts will now start showing proper running stats, no more 100% running.
The screen is a little dark in auto but it will cure the 100% running.
GPS and location services etc make no difference to my X10i, I am running the 1.6 version unbranded UK handset, the only thing to stop mine running 100% is to put the screen on Auto.
Click to expand...
Click to collapse
LOL... this is already going the way of the Galaxy thread!
My phone came out of the box with auto-brightness and i never changed that option, yet i still had no sleep.
Drakaz has done some fairly deep digging and is next to certain that it is an artefact of the geolocation bug discussed in the thread in which the problem was fixed.
I can't see "Spare Parts" in About Phone -> Battery Info
tuxStyle said:
I can't see "Spare Parts" in About Phone -> Battery Info
Click to expand...
Click to collapse
Me neither.. I was wondering about that myself!..
Although I'd half assumed that they were referring to the total "up-time" figure which you can see at the bottom of the "about phone"; "Status" screen.. But perhaps not.?
Spare Parts is a standalone Program ...
(i don't know for sure if it is in the market or downloadable as .apk from somewhere here in the forum ...)
Bax
im_iceman said:
Me neither.. I was wondering about that myself!..
Although I'd half assumed that they were referring to the total "up-time" figure which you can see at the bottom of the "about phone"; "Status" screen.. But perhaps not.?
Click to expand...
Click to collapse
You can download it here
Spare parts is indeed available from the market - it is a much more powerful tool for indicating battery usage than the regular android methods. The galaxy stared on 1.5 which had NO indicator of battery usage statistics at all, so we all learned about spare parts very fast.
Perhaps that is why no x10 users have realised about the potential no sleep bug; because so far only the android usage indicators have been used?...
Anyway, hopefully this can help us all understand the way our phones are working better together
n3man said:
Spare parts is indeed available from the market - it is a much more powerful tool for indicating battery usage than the regular android methods. The galaxy stared on 1.5 which had NO indicator of battery usage statistics at all, so we all learned about spare parts very fast.
Perhaps that is why no x10 users have realised about the potential no sleep bug; because so far only the android usage indicators have been used?...
Anyway, hopefully this can help us all understand the way our phones are working better together
Click to expand...
Click to collapse
14% it's mine value for running time, not 100%. By the way thats 30 minutes of 210 in total :S
I'm also experiencing "No sleep bug" after i used GPS. I use Battery Graph to plot my power consumption and after I use GPS, I can clearly see that power consumption is high even if i turn the phone in plane mode.
In addition SE widget, used to turn on/off GPS, seems to not work very well for me. So, to fix the bug, i manually disable GPS in parameter menu and restart my phone. After that power consumption is hardly null (20% in 8h with MP3 on almost all the time).
mimok said:
I'm also experiencing "No sleep bug" after i used GPS. I use Battery Graph to plot my power consumption and after I use GPS, I can clearly see that power consumption is high even if i turn the phone in plane mode.
In addition SE widget, used to turn on/off GPS, seems to not work very well for me. So, to fix the bug, i manually disable GPS in parameter menu and restart my phone. After that power consumption is hardly null (20% in 8h with MP3 on almost all the time).
Click to expand...
Click to collapse
Do you have 3G always on?
My phone has no trouble sleeping.
Gps hasn't really been an issue but I keep it off when not needed.
Here's my solid settings:
1) No auto sync
2) No moxier
3) Gps off
4) Restart after using wireless
As long as it's like this my phone lasts 2 days easily
ondoteam said:
Do you have 3G always on?
Click to expand...
Click to collapse
Yes, but I made a lot of test with and without 3G enabled and 3G seems not to be a problem for me. I think my problem comes from GPS.
ondoteam said:
Do you have 3G always on?
Click to expand...
Click to collapse
3G always on.
n3man said:
LOL... this is already going the way of the Galaxy thread!
My phone came out of the box with auto-brightness and i never changed that option, yet i still had no sleep.
Drakaz has done some fairly deep digging and is next to certain that it is an artefact of the geolocation bug discussed in the thread in which the problem was fixed.
Click to expand...
Click to collapse
I have been playing with mine for a month to work out what caused mine to not go into sleep, I keep GPS wifi etc on 24/7 but in spare parts I was running 100%, after numerous reinstalls and removing everything i chanced on turning on auto screen brightness, now when i unplug my x10 the running sits at the correct level.
No Geolocation bug here
I have this problem with 100% on and off. Sometimes when I check its under control (~10%), other times its at 100%. I have GPS off, no WiFi, auto brightness... don't know why it sometimes just gets stuck at 100% :/
Heyo bros so I'm experiencing what I'm afraid might be a problem:
I've been getting watchdog alerts regarding the "Base System" process. It notifies me that the CPU % at the time of the captures range from 40% to 60+%. Coincidence or not, it usually happens when I wake my phone from sleep- not when I unlock it, just when I press the power button. The moment the lock screen pops up, the phone's already vibrating and the watchdog notification is up in the status bar.
Battery life so far is:
9h 22m @ 74%; Phone Idle- 56% | Cell Standby- 22% | Display 17% (40m) | Android OS 3% | Voice calls- 3%
Who knows, maybe this^ looks normal. I just want to be sure.
I've heard talk of 'wakelocks' but I don't know exactly what they are, what might cause them, and how I can track them.
I'm currently running:
Atrix 4G (not 2, just for clarification)
CM7 xB^xN
Baseband reads: N_01.77.30P
Kernel version reads: 2.6.32.39-MB860-GB-Faux123-v0.2.1 [email protected] #14
Build number: GWK74
Totally honest, I don't know if that might be able to help diagnose the problem, but for what it's worth, I want to check two things:
1) I flashed Faux's enhanced stock CM7 kernel, and am pretty sure it took, but does that look to be the proper kernel version? I just want to be sure.
2) While I also flashed the "latest radio" in the CM7 xB^xN thread, I was certain there was an xx.97 radio (vs the x.77 radio that mine appears to currently have). Am I indeed on the latest radio version?
Would it hurt to reflash these two? Could either one, or maybe both, be the cause of this?
It also occurs to me: I've been using SetCPU and have ONE profile set up that forces my CPU to min/max 216/216 when the screen is off. Could that be causing it?
Thanks so much for any and all insight bros. Also, please let me know if there's any more info you might want to help diagnose what the dealio is.
Heyo guys,
I hate to bump this kinda soon, but this is definitely a problem.
It's getting to be that I don't even have to wake the phone up for the Base System to spike. I was woken up a couple times in the middle of the night by notifications saying it was really high.
You guys have any thoughts? I'd really like to get this resolved as CM7 is AWESOME.
Yes, you guessed it- I'm not anal about the fingerprint scanner or webtop. Just a stable and fully functional release.
Thanks for any help bros I really appreciate it.
Hi, new member here.
I get the same weird spike to 50-60% (and was woken up too in the middle of the night by watchdog). I have narrowed this occurrence to when I have both Watchdog & Juice Defender enabled at the same time. (Yeah it took me a while to figure out)
When I disable Juice defender the problem seems to go away. So I'm thinking one of the power saving settings turns the radio off & a core system process really does not like that.
This is on a non-rooted Atrix, I have not tested on a rooted Atrix.
So far I had to turn off the watchdog alarm so I can sleep. If anyone can think of a solution it would be appreciated!
AX-MA said:
Hi, new member here.
I get the same weird spike to 50-60% (and was woken up too in the middle of the night by watchdog). I have narrowed this occurrence to when I have both Watchdog & Juice Defender enabled at the same time. (Yeah it took me a while to figure out)
When I disable Juice defender the problem seems to go away. So I'm thinking one of the power saving settings turns the radio off & a core system process really does not like that.
This is on a non-rooted Atrix, I have not tested on a rooted Atrix.
So far I had to turn off the watchdog alarm so I can sleep. If anyone can think of a solution it would be appreciated!
Click to expand...
Click to collapse
Thanks for the insight bro. For what it's worth, I'm not running Juice defender, or any other kind of battery saver app.
Looks like a couple of us are having problems then, though. We'd both really appreciate any info, advice, or help.
Ok, it seems it was just a coincidence with Juice Defender then.
The problem may be unrelated to power savings, but it is indeed a problem.
xyrovice said:
For what it's worth, I'm not running Juice defender, or any other kind of battery saver app.
Click to expand...
Click to collapse
AX-MA said:
Ok, it seems it was just a coincidence with Juice Defender then.
The problem may be unrelated to power savings, but it is indeed a problem.
Click to expand...
Click to collapse
It doesn't have to be unrelated to power saving just because xyrovice is not running Juice Defender, there is a option for power saving in the battery settings for the Atrix that does a similar function.. Before ruling out power savings as unrelated I would make sure xyrovice is set to "performance mode".
WiredPirate said:
It doesn't have to be unrelated to power saving just because xyrovice is not running Juice Defender, there is a option for power saving in the battery settings for the Atrix that does a similar function.. Before ruling out power savings as unrelated I would make sure xyrovice is set to "performance mode".
Click to expand...
Click to collapse
I'm running CM7 and skimmed through the settings menu and didn't find anything about 0ower features. I know that in Blue ROMs there's the battery manager section, but I don't think CM7 has this. Anything else I should look at, though?
Thanks for the insight too bro.
xyrovice said:
I'm running CM7 and skimmed through the settings menu and didn't find anything about 0ower features. I know that in Blue ROMs there's the battery manager section, but I don't think CM7 has this. Anything else I should look at, though?
Thanks for the insight too bro.
Click to expand...
Click to collapse
oIc, no I dont guess you will have those settings in CM, I should have thought of that. I wish I could help because I had the exact same prob with Watchdog constantly alerting for "Android Core Processes" and "Android Media processes", but I dont get those alerts anymore. I haven't changed ROMs or anything.. The only thing I can think of is I changed the MinFree values, I used the app "AutoKiller Memory Optimizer" to change them.
WiredPirate said:
oIc, no I dont guess you will have those settings in CM, I should have thought of that. I wish I could help because I had the exact same prob with Watchdog constantly alerting for "Android Core Processes" and "Android Media processes", but I dont get those alerts anymore. I haven't changed ROMs or anything.. The only thing I can think of is I changed the MinFree values, I used the app "AutoKiller Memory Optimizer" to change them.
Click to expand...
Click to collapse
Do you know why that seemed to solve the problem...or if it even WAS the problem, per se?
Also, is there any reason CM7 would have the minfree set to a default that causes this?
Lastly, what did you alter the minfree values to? You think ROM toolbox might have this capability?
Thanks so much for saying this bro. Who knows, this might be the problem.
PS: I just tried this and am going to see if it works. Post #13 is the one that would really sum up my reaction of successful.
Hopefully maybe this helps my other bros.
xyrovice said:
1Do you know why that seemed to solve the problem...or if it even WAS the problem, per se?
2Also, is there any reason CM7 would have the minfree set to a default that causes this?
3Lastly, what did you alter the minfree values to? You think ROM toolbox might have this capability?
Click to expand...
Click to collapse
1.) no I can't say for sure what the problem was or why I no longer get the Watchdog alerts. I was just trying to think what I have changed since they stopped because I haven't changed ROMs.. Since changing the MinFree has to do with how many or what apps are left running I'm just kinda throwing it out there as a possibility since your at a loss for things to try.
2.) no I can't think of any reason, and most with CM don't have this prob right..?
3.) It's posible it does have the capability because it does allot but I am not sure.
Foreground 12
Visible 18
Secondary 36
Hidden 121
Content 129
Empty 137
possible solutionary steps I've taken:
So Update:
I actually ended up checking out my (partial) Wakelocks with betterbatterystats, and I think I may have found a problem (diagnosed with alarmdump.txt from the Alarm Manager):
1) When I first flashed CM7 I thought, "Oh well why not really get comprehensive about keeping apps up to date" and I actually, for every single app, checked the "Automatically update" box in each one's market page. This led to a CATACLYSMIC wakelock that I'm now pretty sure could be the problem.
2)Google talk also seemed to be a little active with the screen off so I unticked the "sign me in auto..." box and made sure I signed out.
Lastly (not related to wakelocks), I checked on my TTS settings (see my last post about that).
Oh also LASTLY lastly I froze the modem fastdormancy manager in TiBU (kinda just for ****s and giggles). That said though, is the consensus on this that it's pretty harmless?
So, other bro who was having a problem, check and see if this might help you at all AYY
WiredPirate said:
1.) no I can't say for sure what the problem was or why I no longer get the Watchdog alerts. I was just trying to think what I have changed since they stopped because I haven't changed ROMs.. Since changing the MinFree has to do with how many or what apps are left running I'm just kinda throwing it out there as a possibility since your at a loss for things to try.
2.) no I can't think of any reason, and most with CM don't have this prob right..?
3.) It's posible it does have the capability because it does allot but I am not sure.
Foreground 12
Visible 18
Secondary 36
Hidden 121
Content 129
Empty 137
Click to expand...
Click to collapse
Thanks for posting this. I checked ROM toolbox and it does indeed have the capability. That said, if my aforementioned possible solutions don't work, I'm turning here. Thanks for the info bro.
Watchdog is flagging the "base process" app because IT IS using over 60% of your CPU BUT it is using 60% of your CPU that is running at 216MHZ.
It's your screen off setcpu profile of 216/216, if you bump up the max to 456 the alert will go away. When you have it set as 216/216 Watchdog (I believe) thinks that is the actual max cpu speed and bases its percentages off of that. I got that warning before and after a bit of troubleshooting (actually tried several different things) found that was the problem.
I am not sure but if you "whitelist" a app in watchdog it might ignore it as well. However my alert level was set at 80% and it would still set it off, so I think the higher speed might just be better.
Article about the bug: http://www.xda-developers.com/xposed-module-to-fix-mobileradioactive-bug/
Details here:
http://forum.xda-developers.com/note-4/general/xposed-mobile-radio-active-fix-t3137573
This should be considered a must have along with the Lollipop memory leak fix xposed module for anyone rooted even if they don't use any other xposed modules*.
This should noticeably improve battery life.
* Rootcloak is also useful to idol users because it allows system update checker to CHECK for updates without the "root detected" error. You should still not actually INSTALL updates until fully unrooted.
Thanks for the info Famewolf !
I've been closely following the thread but it seems this only fix the wrong reporting of mobile radio in the battery stats and only improve a little the battery life.
Still better than nothing tough.
I'm astonished this huge bug is only looked into by xda volunteers and not by Google...
Bazoocaze did an amazing job btw !
Cannadoux said:
Thanks for the info Famewolf !
I've been closely following the thread but it seems this only fix the wrong reporting of mobile radio in the battery stats and only improve a little the battery life.
Still better than nothing tough.
I'm astonished this huge bug is only looked into by xda volunteers and not by Google...
Bazoocaze did an amazing job btw !
Click to expand...
Click to collapse
It's more than just "reporting". It's the equivalent of opening the door to your garage or outside in the middle of summer and then wondering where all your cool air conditioning is going. Check your power bill the next month when in this analogy you would have left the door open for hours and hours at a time.
It fixes a bug that dropped the instruction telling it to close the radio so the radio connection remained open using up battery needlessly. I do however agree that it is sad Google and others didn't fix this a long while back as it's been widely reported.
My radio is fine
Sent from my 6045Y using xda-developers.com, powered by appyet.com
unrafa said:
My radio is fine
Sent from my 6045Y using xda-developers.com, powered by appyet.com
Click to expand...
Click to collapse
Then you have somehow magically fixed a known bug in all versions of Lollipop.
I have a 6039S with no sim card installed, and it still shows "Cell standby" using a few percentage of power. Is this a bug, and is it the same as the Mobile Radio Active bug?
Judith007 said:
I have a 6039S with no sim card installed, and it still shows "Cell standby" using a few percentage of power. Is this a bug, and is it the same as the Mobile Radio Active bug?
Click to expand...
Click to collapse
You might ask in the actual radio fix thread linked in the message I linked to as they can better provide you details but it's a given that if you have not patched the bug then you still HAVE the bug.
So, does it actually work?
I think Radio active bug is not present in this phone, i have been all day on LTE and Radio active time shows 2 hours. which is more or less the screen on time, and the phone was 12 more hours in my pocket or on my desk.
Sent from my 6045Y using xda-developers.com, powered by appyet.com
unrafa said:
I think Radio active bug is not present in this phone, i have been all day on LTE and Radio active time shows 2 hours. which is more or less the screen on time, and the phone was 12 more hours in my pocket or on my desk.
Sent from my 6045Y using xda-developers.com, powered by appyet.com
Click to expand...
Click to collapse
Multiple people on the forum have reported they had to put their phone into wcdma mode to stop excessive battery drainage. You are free to believe as you wish. See previous posts and the thread related to the bug as it's not my job to convince you.
have used Xposed with this module and with the memory fix module for 5.0.x firmware for two weeks, but didnt notice any noticable battery improvements or less lagging,so i deleted all modules and xposed.
I don't have this bug too. Maybe it's on some carrier or some lte frequencies... report thing is easy but send logs or open a real thread about that is difficult for you Famewolf and you don't even know or you can't prove if the module do something on this phone execpt a placebo in the battery stats... So please stop send stroll people because their device work or have not the same bug or problem of yours .... (by the way i think the governor of the cpu is catastrophic and it can be better with a little bit of tweaking) Bye
Dead-neM said:
I don't have this bug too. Maybe it's on some carrier or some lte frequencies... report thing is easy but send logs or open a real thread about that is difficult for you Famewolf and you don't even know or you can't prove if the module do something on this phone execpt a placebo in the battery stats... So please stop send stroll people because their device work or have not the same bug or problem of yours .... (by the way i think the governor of the cpu is catastrophic and it can be better with a little bit of tweaking) Bye
Click to expand...
Click to collapse
Try reading xda-developer thread I linked to in the 1st post that talks about the bug. I agree..the cpu governor is crappy but until we get a custom kernel we are stuck with it.
http://www.androidpolice.com/2015/0...amous-mobile-radio-active-bug-in-android-6-0/
Oh well sorry, my mistake. i just realiced after reading your last post; that i am in europe, we don't have cdma here. so no bug for europeans i guess. thanks mistery Solved
Sent from my 6045Y using xda-developers.com, powered by appyet.com
hey guys now I can't permanently keep the data to " wcdma only" by going in phone testing (*#*#4636#*#*) remember that?
perhaps it is because of the "mobile active radio fix"
Xposed module because it was working fine earlier but even though now I have tried disabling module and uninstalling module but I can't change it to wcdma only, it keeps fixed on gsm only.
even though in setting I have it set to 3g preferred but because of poor reception many time it goes to 2g and back to 3g it is very irritating.
btw I am able to use 3g, can anyhody tell me how to fix that with fixing of mobile radio active bug
or is it a problem with the cm12.1 itself, btw I'll post in both forums
booo159159 said:
hey guys now I can't permanently keep the data to " wcdma only" by going in phone testing (*#*#4636#*#*) remember that?
perhaps it is because of the "mobile active radio fix"
Xposed module because it was working fine earlier but even though now I have tried disabling module and uninstalling module but I can't change it to wcdma only, it keeps fixed on gsm only.
even though in setting I have it set to 3g preferred but because of poor reception many time it goes to 2g and back to 3g it is very irritating.
btw I am able to use 3g, can anyhody tell me how to fix that with fixing of mobile radio active bug
or is it a problem with the cm12.1 itself, btw I'll post in both forums
Click to expand...
Click to collapse
Perhaps you can use something like:
https://play.google.com/store/apps/details?id=com.tapbase.LTEswitcher
Sent from my 6045I using Tapatalk
booo159159 said:
hey guys now I can't permanently keep the data to " wcdma only" by going in phone testing (*#*#4636#*#*) remember that?
perhaps it is because of the "mobile active radio fix"
Xposed module because it was working fine earlier but even though now I have tried disabling module and uninstalling module but I can't change it to wcdma only, it keeps fixed on gsm only.
even though in setting I have it set to 3g preferred but because of poor reception many time it goes to 2g and back to 3g it is very irritating.
btw I am able to use 3g, can anyhody tell me how to fix that with fixing of mobile radio active bug
or is it a problem with the cm12.1 itself, btw I'll post in both forums
Click to expand...
Click to collapse
I use wcdma only mode all the time as i'm in a fringe area that barely has 3g in both stock and now in cm12.1....the radiofix module wouldn't have anything to do with it. You can go into the dialer and do a *#*#4636#*#* then go into phone info which will let you select wcdma only or you can install the "network" app from either google play or f-droid which when ran acts as a shortcut to take you straight to the phone info screen so you can set wcdma only.
famewolf said:
I use wcdma only mode all the time as i'm in a fringe area that barely has 3g in both stock and now in cm12.1....the radiofix module wouldn't have anything to do with it. You can go into the dialer and do a *#*#4636#*#* then go into phone info which will let you select wcdma only or you can install the "network" app from either google play or f-droid which when ran acts as a shortcut to take you straight to the phone info screen so you can set wcdma only.
Click to expand...
Click to collapse
I tried both it doesn't seem to stick to anything other than gsm only.
though my 3g works, weird
Hello, i have a LG G6 model H870 with SW Versione V10L-EUR-XX.
I'm experiencing big battery drain, even when not in use the battery is wiped in matter of 5-6 hours.
Using BetterBatteryStats i found that the culprit is the process com.android.phone that spams wakeups like no tomorrow.
How can i fix this? can i temporary switch to another dialer app or that won't fix the problem and i have to wait an update from LG?
(i'm a new user so i can't post images )
MogaWine said:
Hello, i have a LG G6 model H870 with SW Versione V10L-EUR-XX.
I'm experiencing big battery drain, even when not in use the battery is wiped in matter of 5-6 hours.
Using BetterBatteryStats i found that the culprit is the process com.android.phone that spams wakeups like no tomorrow.
How can i fix this? can i temporary switch to another dialer app or that won't fix the problem and i have to wait an update from LG?
(i'm a new user so i can't post images )
Click to expand...
Click to collapse
Go to the LG's Service Menu by using this code in the dialer app: *#546368#*870#, then go to: Field Test - Modem Settings - PDP Setting - Set LG Fast Dormancy - Enable/Disable Fast Dormancy - Off. From now on check whether or not the percentage change, it should decrease.
How would I get to this menu on my Verizon G6? It is a VS988. I tried swapping out the 870 with 988 but it didn't work.
Sent from my VS988 using Tapatalk
now i see that the problem moved to Wi-Fi.
It is always one even when turned off by the toggle in the menu. It seems the same exact problem that i had with Honor 7 years ago and i couldn't fix
Report to LG and they would change it, I think.
Killua96 said:
Go to the LG's Service Menu by using this code in the dialer app: *#546368#*870#, then go to: Field Test - Modem Settings - PDP Setting - Set LG Fast Dormancy - Enable/Disable Fast Dormancy - Off. From now on check whether or not the percentage change, it should decrease.
Click to expand...
Click to collapse
I have the same problem, I'll try. Thank you!
Lately I have been struggling with some very bad battery drain. I'm a very light user. Before the Oreo update by the end of the day I would have 80% battery left. Now I'd be happy to have 40% left. I tried everything including greenify to no avail. Something keeps my phone awake. I found that a partial wakelock caused by LgeGnssLocationProvider is the culprit.
The fun part is when you google it.
Any ideas what the hell I'm supposed to do? I'm considering rooting my phone to get rid of all the bloatware. Would that also allow me to get a better insight of what is causing this wakelock?
I'm also have notice this, but the wakelock seems to be related with some LG bloatware. I have disabled multiple GNSS LG apps running in background, and that solve the issue. (i have root)
DJPRMF said:
I'm also have notice this, but the wakelock seems to be related with some LG bloatware. I have disabled multiple GNSS LG apps running in background, and that solve the issue. (i have root)
Click to expand...
Click to collapse
Which applications did you disable? I listed all the packages that contained gnss and disabled those without any luck. Worst part is, it does not always happen. Sometimes I can go the entire day without the wakelock.
I can not believe I am the only one who is experiencing this issue.
You are not the only one, I am having the same problem on my V30. Any ideas how to solve that problem??
I'm still working on figuring out what is causing the wakelock. Can't seem to find it though
I'm going to bump this again in the hope that someone sees it and know's what is going on.
Is there a way to find what triggered a wakelock?
Ortix92 said:
I'm going to bump this again in the hope that someone sees it and know's what is going on.
Is there a way to find what triggered a wakelock?
Click to expand...
Click to collapse
https://www.xda-developers.com/stop-wakelocks-android-without-root/
Flashing_Expert said:
https://www.xda-developers.com/stop-wakelocks-android-without-root/
Click to expand...
Click to collapse
I've come across this many many times but it doesn't help me. The wakelock is caused by Android System, but I want to know what exactly triggered it. Because it does not occur all the time.
Ortix92 said:
I've come across this many many times but it doesn't help me. The wakelock is caused by Android System, but I want to know what exactly triggered it. Because it does not occur all the time.
Click to expand...
Click to collapse
it's not system itself it's always some app using system interface...
posibly even some LG bloatware that uses location...
weather and so on...
Has anyone managed to solve this absurd wakelock?