Develop Bugs

[Q] Battery Drain in Airplane Mode, and even otherwise - Andromadus Mimicry

Hey all,
I have a rooted Desire Z, that's almost 2 years old. I had been using the Virtuous Sense ROM for the most part and had been quite happy with it. Recently, I figured it was time I switched to ICS. So I flashed the Andromadus Mimicry ROM and have been loving it ever since. My only gripe with it is the battery life. I have been meaning to test it out extensively before I could bother the DEV with my nooby queries, but haven't had the time to do so.
When I check Settings > Battery, the screen always seems to be using up most of the %. I have searched through the forums and have done the following, in addition to a few steps that I could think on my own -
Re-calibrated Battery Stats
Clear cache & devklik cache fortnightly
Brightness - Set to 20% (No Auto)
Set to dim after 30 seconds
No render effects (ROM specific I think)
Animations are On.
No Bloatware Installed (Facebook, Twitter, Chrome, etc)
Sync is Auto (I need this)
Froze Google Maps and few other unnecessary background apps that I rarely use with Titanium (using Watchdog to monitor what was eating up CPU)
Disabled Google Backup
Wifi is always Off (I have to depend on 3G for my connectivity needs)
No Battery Saving Apps or Auto Kill Task Managers installed.
News & Facebook widgets set to manual update.
V6 SuperCharger with stock Services.jar.
CPU clock runs @ 245 Mhz on idle, which is most of the time.
GPS is always Off
Google's Location Service (Wifi & mobile network) is On.
Coming to the point, last night the phone was fully charged to 100%. I decided to turn Airplane mode On before I went to sleep to figure the drain in the absence of networks. Woke up to find 78%. That's 2.2% per hour. I checked Better Battery Stats and it seems the phone was awake for the whole ~10 hours. The culprit seems to be GPSLocationProvider. Note that the GPS is Off ; so this has to be the Google's Location Service (Wifi & mobile network)? Disabling this would be inconvenient because it's needed for Weather, and a few other things.
I'm attaching the screens, because I'm pretty new to this and would like to see what people who know more than me have to say about this. A drain of 22% in Airplane mode isn't normal and is crazy, right? Or perhaps,it's time to get a new battery?
PS: The battery has drained a further 20% since the time I took the screenshots, while I was typing this. I merely used the phone for a few messages and to check my mail. (see second-to-last vs last screen)
Radio - 12.56.60.25_26.10.04.03. Signal Strength is usually ~ -89dBm. I have noticed people claiming that the .19 radio is quite battery-friendly but I live in India, so I had to go with the WWE radio that seemed the latest. I didn't think it'd work here. Perhaps I'm wrong?
Any insights offered would be greatly appreciated.

It's an app calling the location services api. Try disabling Facebook and/or whatsapp and see if that helps. I'm unfamiliar with either of those apps, but I've heard nothing but bad things about the Facebook app, so that would be the first one I'd remove to see if it helps.
This goes without saying but of course make sure you've done a full wipe of /data since coming from your old rom. Hope that helps. I'm currently sitting at 12 days since my vision has been unplugged in airplane mode (radio off, wifi off, etc).
Sent from my SAMSUNG-SGH-I747 using xda premium

GPSLocationProvider - Reboot to Fix.
Thanks for your input, blk_jack. I did do a full wipe before migrating. As suggested in your ROM's OP, I don't use the Facebook app. The Facebook entry seen in the screenshot belongs to the Facebook Messenger app, which might partly be the cause. Upon further searching, I found that many people have been complaining about this issue on many different flavors of ROMs (ICS / JB) and hardware (HTC, Samsung, LG). Let me elaborate.
Searching for 'GPSLocationProvider' brings a ton of threads about this issue. I will post here whatever I could gather from these posts, for the benefit of others who face this.
Some people get this wakelock if they use GPS for anything and then turn it off. For example, if you turn on GPS, use a map application for a short while, close the map application and turn off GPS, the wakelock is born. Even if you kill any active map services, it will still be there and ends up draining your battery.
It seems to be chiefly caused by apps that use Location such as Google Maps, Facebook, Facebook Messenger, etc. Turning off all location services is advisable.
In some cases, the GPS does not turn back on until the phone is rebooted but that is not the case in this ROM. GPS works when turned On.
To get rid of the wakelock caused by GPSLocationProvider, rebooting seems to be the only working option as of now.
There is a step-by-step instruction guide (written by Karpfenhai) in the [APP]BetterBatteryStats thread OP, that deals with configuring autostarts, which apparently fixes this issue. I'm yet to try it, so I can't comment if it works or not.
I wish I'd been smarter and searched for 'GPSLocationProvider' instead, before creating this thread. Thanks for your time, anyway.

Screen Off Widget/Shortcut on Desktop?
@blk_jack
If I may use this opportunity to ask you something else related to your ROM.. I just found out that I don't have 10 posts yet, so I can't post it in the ROM thread.
Is it possible to create a widget/shortcut on the desktop to turn off the screen, perhaps by using the Launcher Activity options? I am currently using the one that's there in the Notification Drawer (Power Widget), pulling it down each time to turn the screen off is a tad inconvenient. The desktop Power Widget doesn't seem to have the Screen Off option. Is this possible at all without having to use an external app?

Yep, I have a nova launcher gesture set to run the root app killscreen.apk (search google).
You could add that app to your home screen too.
Sent from my SAMSUNG-SGH-I747 using xda premium

[Q] Battery drain on Note 2 after 4.3 update

Hello
I have had a massive battery drain problem on my Note 2, a couple of days after the 4.3 update. While being idle during the night it loses 25% to 30% of its battery and while using it I can literally see the percentage drop. I have tried everything that I could find on the net. EVERYTHING! Nothing worked. These included: Factory reset (twice), letting the battery frain completely and then recharging it while the phone was switched off, switching off all sync,disabling bloatware including KNOX components (the actual KNOX app is not installed), installing only a few apps after factory reset, using Gsam, Wakelock detector, Deep sleep battery saver (which could not make my phone sleep), no GPS, no 3G, wifi on only when needed and more besides.
The phone is only one year old and unrooted. On 4.1.2 it had a beastly battery performance of almost 1.5 days of normal to heavy use, with 300 apps on it. Now it cannot go for more than a few hours with the same use.
I cannot say for sure but it seems to me that the drain is the same when it is sleeping and when I am using it. Wakelock has given me a 75% awake time even though I only use it for 15-20% of the day at most nowadays. Battery settings show everything normal, or at least I think so, eg Screen 35%, Android OS 15-28%, Voice calls 10%, Android system 5-15%, Cell standby 7%, Device idle 4%, Media server 4%. The batttery chart shows a constant steep drop all the time.
The problem started one day when the Media server went mad consuming 50% of the battery. After I did the factory reset it has never again been a problem but the drain still persists.
I have also read that it's a mess up between syncing of Samsung apps and Google services, but I have no way of verifying that.
Can anyone help?
Thanks

I had the very same problem until yesterday myself but think I found a solution on the web.. Uninstall Google Search and Google Play Services and the goto the Play Store and wait for them to reinstall and that's it....! As I found that there is a bug in Google Services (Nlpwakelock and Location service)
Hope this helps...?
Sent from my GT-N7100 using xda app-developers app

terzisc said:
Hello
I have had a massive battery drain problem on my Note 2, a couple of days after the 4.3 update. While being idle during the night it loses 25% to 30% of its battery and while using it I can literally see the percentage drop. I have tried everything that I could find on the net. EVERYTHING! Nothing worked. These included: Factory reset (twice), letting the battery frain completely and then recharging it while the phone was switched off, switching off all sync,disabling bloatware including KNOX components (the actual KNOX app is not installed), installing only a few apps after factory reset, using Gsam, Wakelock defender, Deep sleep battery saver (which could not make my phone sleep), no GPS, no 3G, wifi on only when needed and more besides.
The phone is only one year old and unrooted. On 4.1.2 it had a beastly battery performance of almost 1.5 days of normal to heavy use, with 300 apps on it. Now it cannot go for more than a few hours with the same use.
I cannot say for sure but it seems to me that the drain is the same when it is sleeping and when I am using it. Wakelock has given me a 75% awake time even though I only use it for 15-20% of the day at most nowadays. Battery settings show everything normal, or at least I think so, eg Screen 35%, Android OS 15-28%, Voice calls 10%, Android system 5-15%, Cell standby 7%, Device idle 4%, Media server 4%. The batttery chart shows a constant steep drop all the time.
The problem started one day when the Media server went mad consuming 50% of the battery. After I did the factory reset it has never again been a problem but the drain still persists.
I have also read that it's a mess up between syncing of Samsung apps and Google services, but I have no way of verifying that.
Can anyone help?
Thanks
Click to expand...
Click to collapse
Download wakelock detector from the play store. It detect which app is waking your device (both screen and cpu) by list.. Then download greenify from the play store and herbinate (greenify) upper most apps from wakelock detector. Hope you can solve your problem
Sent from my GT-N7100 using XDA Premium 4 mobile app

yeminswe said:
Download wakelock detector from the play store. It detect which app is waking your device (both screen and cpu) by list.. Then download greenify from the play store and herbinate (greenify) upper most apps from wakelock detector. Hope you can solve your problem
Sent from my GT-N7100 using XDA Premium 4 mobile app[/
Thanks. I already have Wakelock Detector on. I mistakenly wrote "defender" instead of detector on the original post. It gives me Viber and Messenger as the most active wakelock apps. But they both were not installed when the problem started. Besides, on the 4.1.2 they created no problems. In essence I believe that Wakelock Detector cannot help much. Whatever this problem is , it is well hidden. Thanks for your interest and help anyway. Much appreciated.
Click to expand...
Click to collapse

In wifi settings, goto advanced and untick scanning always available.
Sent from my GT-N7100 using Tapatalk

Manjunath324 said:
In wifi settings, goto advanced and untick scanning always available.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Thanks, but I have checked and it was not ticked in the first place...unfortunately...

terzisc said:
Thanks, but I have checked and it was not ticked in the first place...unfortunately...
Click to expand...
Click to collapse
Which kernel you are using? And also i recommend using Greenify. Widgets usually eat a lot of battery, I went from battery lasting only 8 hours to get my battery use only 30% in 8 hours.
What i did: installed wakelock detector, gsam battery monitor and better battery stats.
Monitorized the wakelocks.
Applied greenify to the apps which were waking most
Removed widgets which were waking alot
Installed Toggle 2G.
Kernel settings: 200-1600mhz | zzmoove | AFTR+LPA | Multicore power saving (SCHED_MC) = 0 | GPU = stock settings
Works like a charm for me. Hope it helps! Any question, ask!

I've read all sorts of things about this problem since I updated and got hit. I have too much app data to lose by trying the factory restore (which by all accounts shouldn't change anything anyway since you'd still be stuck with 4.3)
I finally decided to try the age old blackberry cure-all: "if in doubt, pull it out" (the battery). Since the entire issue seemed to be related to battery caused problems (ie slow charging, fast drain, etc) it made a lot of sense.
And it worked.
I think the main reason this isn't more commonly tried to fix issues on Android is the same reason I didn't try it earlier. My case is pretty serious and isn't easy to remove. I'm glad I did take the time to take the case off though or I could have ended up wiping my phone.

Nukkels said:
I've read all sorts of things about this problem since I updated and got hit. I have too much app data to lose by trying the factory restore (which by all accounts shouldn't change anything anyway since you'd still be stuck with 4.3)
I finally decided to try the age old blackberry cure-all: "if in doubt, pull it out" (the battery). Since the entire issue seemed to be related to battery caused problems (ie slow charging, fast drain, etc) it made a lot of sense.
And it worked.
I think the main reason this isn't more commonly tried to fix issues on Android is the same reason I didn't try it earlier. My case is pretty serious and isn't easy to remove. I'm glad I did take the time to take the case off though or I could have ended up wiping my phone.
Click to expand...
Click to collapse
Thank you for the suggestion. I have already taken the battery on and off several times. It had no improvement. The phone is only a year old, that is why I don't believe the battery is the culprit. Besides, problems started only after the 4.3 update. Before that it was working perfect. Too much of a coincidence.

Sorry to hear that it didn't work for you
I'm not saying the battery is faulty in any way - however removing the battery and letting the phone power drain completely seems to stop whatever process is running under the buggy 4.3 long enough for it to work again as intended. It's basically just a more thorough way to reboot.
As I said, I've read all sorts of suggestions, many of which don't work for everyone (such as the factory reset) - this is hopefully just one more thing for people to try before they end up wiping their phone in desperation. I mainly posted here in the hopes that others with this issue that may not be forum members can get some more suggestions.
At least for me, wakelock and all the other diagnostic tools at my disposal showed nothing different to before the update. Many other people have found that the Android System is using a lot more of their battery than normal or some other apps are involved - if this is the case, it's likely to be a combination of things causing the issue (the firmware, the drivers, apps, hidden Samsung processes, etc).
Also, for what it's worth, I found that Knox supposedly wasn't installed (when I find it in the apps list, the button to install it is showing...). But it's showing in the list of apps so it must already be installed. I dug through the list of running processes (had to show the system processes too) and I discovered that several Knox and some other new Samsung processes were indeed running.
One other quick tip - If you wanted to check/tweak the 'developer options' and can't seem to find it any more, that's because it's now hidden since 4.2 - go to 'About Device' and tap 7 times on the Build Number. I tried disabling all background processes however it seems this only disables application level processes, not system level processes but if you've tried everything else, it can't hurt to try playing around with some of the options in there.

Nukkels said:
Sorry to hear that it didn't work for you
I'm not saying the battery is faulty in any way - however removing the battery and letting the phone power drain completely seems to stop whatever process is running under the buggy 4.3 long enough for it to work again as intended. It's basically just a more thorough way to reboot.
As I said, I've read all sorts of suggestions, many of which don't work for everyone (such as the factory reset) - this is hopefully just one more thing for people to try before they end up wiping their phone in desperation. I mainly posted here in the hopes that others with this issue that may not be forum members can get some more suggestions.
At least for me, wakelock and all the other diagnostic tools at my disposal showed nothing different to before the update. Many other people have found that the Android System is using a lot more of their battery than normal or some other apps are involved - if this is the case, it's likely to be a combination of things causing the issue (the firmware, the drivers, apps, hidden Samsung processes, etc).
Also, for what it's worth, I found that Knox supposedly wasn't installed (when I find it in the apps list, the button to install it is showing...). But it's showing in the list of apps so it must already be installed. I dug through the list of running processes (had to show the system processes too) and I discovered that several Knox and some other new Samsung processes were indeed running.
One other quick tip - If you wanted to check/tweak the 'developer options' and can't seem to find it any more, that's because it's now hidden since 4.2 - go to 'About Device' and tap 7 times on the Build Number. I tried disabling all background processes however it seems this only disables application level processes, not system level processes but if you've tried everything else, it can't hurt to try playing around with some of the options in there.[/Q
Thanks mate
I think you are right. It is probably a combination of many things. I have opened the Developer options some time back. The one thing that I do for sure in there is limit background processes to 4. Besides that I don't experiment much, exept maybe to change transition animation scale. I am actually thinking of rooting the phone and downgrading to 4.1.2. It was just fine before. I can live without the 4.3 add ons.
Click to expand...
Click to collapse

Problem still persists, even with Google+ and most other Google applications disabled

Sent from my GT-N7100 using xda app-developers app Some screenshots taken from 3 different apps. Wakelock detector, Better battery stats and Gsam battery monitor

Sent from my GT-N7100 using xda app-developers app

The only battery apps on my phone are the 3 mentioned above, so I don't know what the battery monitor that keeps my phone awake is. The drain existed before I installed these apps. I have read that Chrome could prevent the phone from going to sleep but it is disabled on my phone.
Sent from my GT-N7100 using xda app-developers app

http://www.youtube.com/watch?v=ak1sYWRaEKg

I faced same battery drainage issue, after installing wanam kernel and freezing all bloatwares through Titanium Backup. I'm satisfied with my battery now.
You can try.
Sent from my GT-N7100 using XDA Premium 4 mobile app

Here is detail-
Disable sync always, enable when needed.
Disable wifi always scan from settings
Display set to auto
Uninstall apps of playstore you rarely use
Use widgets on lock and homescreen as less as you can (I don't use any)
Disable motion on settings
Freeze all bloatwares by TB except allshare and samsung content agent
Install Agni kernel, from agni control app-
profile: normal
Governor: pegasusq
Scheduler: cfq
Don't touch other tweaks, hardly you can tweak sound boost.
THIS GIVES ME A SATISFIED BATTERY STATUS.
regards.
Sent from my GT-N7100 using XDA Premium 4 mobile app

Wew 4.3 does have may bugs

Lg G3 Massive Battery Drain from bam_dmux_wakelock (Pics Included)

Alright everyone,
Some details about my phone before we begin-
I am a moderate user. I play some games, check emails, text and that's about it.
My phone is NOT rooted and obviously I am not running a custom rom, or a alternate launcher, and I haven't really modified many if at all any settings.
So, that being said I am experience some sever kernel wake lock issues form bam_dmux_wakelock for the past week or so. As you see in my picture, 6 out of my 7 hours of up time (off charger) has been kept from deep sleep, therefore destroying my battery time.
Today I have maybe 30-40 minutes total of screen on time, but not nearly the 6 hours of non deep sleep time.
I've turned off "okay google" detection, disabled wifi when screen is off, restricted background data for youtube, disabled google + (I don't use social media) and my brightness is on auto mode, typically around 35% when the screen is on.
If google can see this I would like to offer them a huge F you for changing the permission architecture so that gplay apps cant detected whats causing the wake-lock without root. They are pretty much forcing us to root our phones to access features locked meanwhile continuing to call android "Open Source"
Can anyone give me a recommendation on what are my options? Or should I really just root my phone, which I don't want to do (I have in the past but I haven't needed too with the G3 since it has everything I want without root)

I don't think it's Google's fault if LG makes a sucks kernel. Anyway, bam_dmux seems to be related to radios. Could it be that during those wake locks you were in an area where there is weak signal? Are you still experiencing this error after a reboot of the phone?

keithleyson said:
I don't think it's Google's fault if LG makes a sucks kernel. Anyway, bam_dmux seems to be related to radios. Could it be that during those wake locks you were in an area where there is weak signal? Are you still experiencing this error after a reboot of the phone?
Click to expand...
Click to collapse
I've reset the phone multiple times, and have also cleared the cache from the bootloader as well. I don't have a weak signal in my area; also the radio interface is a separate wake lock code from bam_dmux. From what I read bam_dmux has to do with google background services.

Bump

JetForceF22 said:
I've reset the phone multiple times, and have also cleared the cache from the bootloader as well. I don't have a weak signal in my area; also the radio interface is a separate wake lock code from bam_dmux. From what I read bam_dmux has to do with google background services.
Click to expand...
Click to collapse
Google location service may be running in the background to much too long.

gee2012 said:
Google location service may be running in the background to much too long.
Click to expand...
Click to collapse
I don't see a google location service only the Verizon Location Agent; there are two other services called "LocationServices" under All in my application manager, and they are both listed at being 0.00 bytes in size (?) I force stopped those anyways along with the verizon location agent which restarted anyways. I also have location completely off in my quick menu from the pull down bar, I only turn it on when I'm using GPS.

fire OS using most the battery, new update to blame?

The date I noticed my battery issues coincides with when the update went live. I've tried tinkering as much as I can to disable wake lock permissions in all sorts of apps and using wake lock detector, but I can't really find the culprit.
I'm rooted, on 4.6.3. Is there a way to turn off the OTA check, or fool it into thinking I have 4.6.3.
Is it something else? I have a lot of apps, but the only thing wake lock can tell me about the sheer number of wakes is google play services, which has had it's permission to wake disabled but still is somehow the cause. That and system are about equal. Awake time is 91% since my last full charge and unplug. Not good.
Thanks for any help.

Just to maybe assist you in finding the culprit I'm on 4.6.3 with google apps but no root. I've not experienced any wake locks. Perhaps clearing Google's cache and data?

Sorry I meant I was on 4.6.1 still. Will clear data and see.

adam.nox said:
The date I noticed my battery issues coincides with when the update went live. I've tried tinkering as much as I can to disable wake lock permissions in all sorts of apps and using wake lock detector, but I can't really find the culprit.
I'm rooted, on 4.6.3. Is there a way to turn off the OTA check, or fool it into thinking I have 4.6.3.
Is it something else? I have a lot of apps, but the only thing wake lock can tell me about the sheer number of wakes is google play services, which has had it's permission to wake disabled but still is somehow the cause. That and system are about equal. Awake time is 91% since my last full charge and unplug. Not good.
Thanks for any help.
Click to expand...
Click to collapse
Probably one of those glitches that can be solved by a reboot. However, you can disable updates using hdxposed module for xposed if you want.

Done both of those things plus much more. Anyone else having this issue?

try taking a titanium backup of everything and then factory reset.. with everything backed up to your PC. then root and start restoring everything gradually.. start by social apps and call log and messages.. then your essential apps.. and see.. then add the rest of the apps bit by bit till you find the offending application or maybe something just got screwed will be fixed when the data clears..
just make sure there is nothing out of the norm in your essential apps, meaning they are all tried and tested by everyone.. facebook, whatsapp, keep, launcher.. that stuff. and also make sure in these apps to limit their ability to check every X minutes as they can really drain your battery.

I've disabled wakelock on anything that has reported to use it by wake lock detector that I don't absolutely need to have it. I've uninstalled any non-essential apps. I've done too much tinkering and have too much important app data to risk doing a reset when it may not work.
I need a way to actually get to the bottom of it first.
Why is google play services waking the phone 2000+ times per day? Wake lock detector says the phone has been awake 5 hours out of 10, but then the list of times for each app only adds up to 20 minutes. How do I find out what was keeping it awake the rest of the time?

Possibly some kind of location based frippery. Try removing location access from troublesome app. And turn off auto sync if it's on

Location services are completely disabled. Auto sync is off. Both have been since this started happening.
Used app quarantine to disable almost every app I put on here, and Fire OS is still 51%.
Possible culprits, though I'm not sure if I find it likely: Ultimate dynamic navbar, lightning chat, foscam viewer, google apps, xposed mods (have a few). greenify (that would be ironic), flixter, es file explorer, buildprop editor, calculator, jellybean keyboard, multi timer, skana battery alerts, nova launcher, power toggles, slacker radio, bank app, super user, terminal emulator, outlook, wakelock detector.

Get better battery stats from xda, it gives a better breakdown of wake locks.

Alright what should I look for in there?

Ok here is what I believe I have found out, using network log along with better battery stats.
The phone is waking up constantly due to netbios pings (I know not technically pings), from various computers on my network, mostly my main PC. I don't know why it's doing this. Could be one of many background processes. In my opinion, it shouldn't matter. The phone shouldn't be that stupid.
I was able to... I think, mitigate a lot of this by doing a few things.
The first is editing qcom's ini inside etc/wifi so that if it says offload, I put a 0, I assume it's offloading to the cpu, which causes it to wake for pointless crap. The second thing I did was re-enable optimized wifi. This is probably already on, on everyone else's phone. I turned it off because I was trying to figure out how to tether while connected to a vpn through the phone. Still can't get that to work. And I know how to, because I did it on my nexus prime, but something in the fire OS is f'ing that method up (iptable configs).
I'm considering seeking an app to turn off wifi when the phone sleeps, because better battery shows wifi on 100%, and even with the changes above, I was still responding to some netbios pings in the network (about 1/5th as many). I imagine most networks will have noise like this.
However, even after all this, fire OS is still the main battery draw. Better Battery doesn't account for all the wake time, not even by half.
For now I've put enough time into this.

Android OS wakelock

Hello everybody.
I have recently rooted my phone to try and identify the cause to my fast battery drain, which is primarily from the Android OS process.
I can't seem to find it. I see that the process "system" is working a lot and that the Android OS is awake for way to long.
Maybe you guys can point out something I'm missing here.
I would appreciate every help from you !
Thx

raied115 said:
Hello everybody.
I have recently rooted my phone to try and identify the cause to my fast battery drain, which is primarily from the Android OS process.
I can't seem to find it. I see that the process "system" is working a lot and that the Android OS is awake for way to long.
Maybe you guys can point out something I'm missing here.
I would appreciate every help from you !
Thx
Click to expand...
Click to collapse
This really could be anything. I recently had this and experimented for days whenever I took a break. For me, it turns out that it was my work's wifi hotspot making my phone stay awake to stay connected. I turned off wifi and it was fixed. But this isn't a solution. I ended up connecting to my own wireless repeater and problem was gone.
Bottom line is you'll have to figure out what's going on yourself.

htr5 said:
This really could be anything. I recently had this and experimented for days whenever I took a break. For me, it turns out that it was my work's wifi hotspot making my phone stay awake to stay connected. I turned off wifi and it was fixed. But this isn't a solution. I ended up connecting to my own wireless repeater and problem was gone.
Bottom line is you'll have to figure out what's going on yourself.
Click to expand...
Click to collapse
Thank you for your reply.
I couldn't find any cause to the problem, that's why I thought that maybe another pair of eyes (or more ) might help...

raied115 said:
Thank you for your reply.
I couldn't find any cause to the problem, that's why I thought that maybe another pair of eyes (or more ) might help...
Click to expand...
Click to collapse
I'll tell you what I've done for battery life on my phone and maybe on of those will fix your problem.
1. Uninstall stock bloat (only the stuff actually running in the background; no need to remove stock launcher ect.)
2. Disable Wi-Fi scanning when wifi off
3. Use Amplify to limit wakelocks and alarms
4. Freeze the apps you don't regularly use. I have a titanium backup widget on my homescreen that will unfreeze snapchat and launch it. It is the pressed again to freeze it after use.
5. Greenify apps you don't want running in the background for no good reason. If you get the donate version, you can still get GCM notifications so it's win win. For apps that don't have GCM notifications, it will coalesce the notifications so your phone doesn't wake up as often.
6. Make sure you have all logging turned off from the LG hidden menu.
7. If you're on a bad wi-fi network run by work/school, then get the auto disable IPv6 app on the play store.
8. Use the HEBF Optimzer app to prevent Google wakelocks and battery drains.
9. Use PNF Root app on the play store to custom choose how often your phone checks for GCM notifications.
With these changes, I finish the day with around 4 hours of screen on time doing regular things. Don't believe the posts about 7-8 hours SOT because you don't know what they were doing. I once used my phone as a timer while studying and had the screen on for 3 hours and only drained 12% battery.

absolutely the same issue here. No luck with factory reset, not using whatsapp or messenger, not using wifi, not using mobile data, no luck with any kind of debloating, uninstalling, installing greenify, amplify whatever. In the end, the Android OS will come back and drain the battery. I've spent a way too much time on this issue.

kakaovnik said:
absolutely the same issue here. No luck with factory reset, not using whatsapp or messenger, not using wifi, not using mobile data, no luck with any kind of debloating, uninstalling, installing greenify, amplify whatever. In the end, the Android OS will come back and drain the battery. I've spent a way too much time on this issue.
Click to expand...
Click to collapse
Try clearing the Google Play Services data, then removing all Google accounts and then adding them back. This time, make sure not to agree to any data collection.
When you turn GPS on, it should show as GPS only in the location settings. Disagree to any prompts.
If your location defaults to high energy GPS and networks, then try flicking the toggle on and off very quickly after you have cleared the play services data. This is how I got the prompt for data collection to come back. It's annoying and you have to always disagree but it fixed my mysterious battery drains from android os.