• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help need help with NON rooted verizon G2 android services

K

kyennamo

Newbie
Ok so I upgraded from a droid 2 a few months ago and love my LG G2 for the most part. But I am noticing that "android system" is using 30 or more percent of my battery ALL THE TIME. I also had a problem with "media server" consuming vast amounts of battery and was able to trace it to a problem with corrupted files. That problem has been solved. But I don't know what to do about the android system. On my wife's phone that also has jellybean android system uses approximately 2-5% of her battery. I have disabled everything I could think of and am now even experimenting with disabling stuff I probably shouldn't. Any suggestions? I installed Gsam battery monitor already. And please, if you are going to suggest rooting don't even comment and just move on. I'm a good girl and I don't break the rules :P
 
If I were you, I'd back up your files (music, pictures, downloaded .PDFs or other stuff you want to keep), copy down important settings (like for email, or contact information (should be backed up on Google but just to be safe)), and perform a Factory Data Reset.

Sometimes performing a SW Upgrade without an FDR results in a process or app running in a way that it shouldn't because all memory isn't initialized to known good state before it is used. Sometimes we get lucky and don't have to perform a FDR following an upgrade... but upgrades aren't perfectly written to handle the infinite configurations that might exist on everyone's devices receiving that upgrade.

I think my personal track record is in 7 SW updates over the years on various devices, 3 necessitated an FDR, 4 didn't. YMMV

Even phones right out of the box might mis-behave, and others have reported bizarre behavior that has been rectified via an FDR.

That said, an FDR might not fix your problem - I'm not claiming it will with certainty... But it is a logical thing to try.
 
That is the absolute LAST resort. To be honest though
I don't recall if this was a problem before the update or not so I don't wanna do that If I don't have to
 
It is your prerogative to attempt other avenues towards a solution. I respect your desire not to "go backwards".

It's not really all that scarey to start over. Perhaps you haven't done this previously on another device. Once you've done it a few times, it becomes kind of second nature - sort of like a challenge to yourself to see how long it takes to return your device to a familiar state you find most usable and to your liking.

I think of it like moving... which forces you to discard, sell off, or give away what you don't really need in your new digs (unless you are the type that likes to hang onto everything you've acquired, even the stuff you don't use anymore, or is boxed and out of sight which you don't know you even have).

Sometimes the quickest way forward IS to re-visit the starting point and re-apply your customizations.

What else is mangled? What might you have done which you'll potentially have to undo?

I suspect you may have applied an update/upgrade with memory in an uninitialized state... It happens. Strange unanticipated behaviors can result. Manufacturers and carriers don't really want to tell you with an Upgrade you should do an FDR. But if you call, email or chat with support, likely it will be the thing they suggest you do.

Realistically, the only way to get it to a known-good state is via the FDR. This will help you determine if there might be something else wrong with the device worth seeking a replacement.

You can go through the process of uninstalling everything... but really what you will be in essence doing is a poor-mans FDR, and yet it will be incomplete.

I have no desire to persuade you. Only by digging in might you find exactly (?) what is causing your issue and that is a worthy goal.

The problem(s) become(s), what tools are you going to need, and what additional effort will you have to expend, will you find it, and will you be able to mitigate it through some process other than the very FDR you wish to avoid?

You've already gone to disabling stuff (probably won't help - likely will only hurt you), and you are anticipating getting yourself into trouble... and that is not a good path to be on.

Hopefully someone else can provide you alternate advice that resonates with you. Best of luck.
 
This is what I've got right now. I'm not having any problems with battery life.
vumygy5e.jpg
 
Glad you posted that. I had to look myself. I get great battery life and my battery stats indicate Android System at 34%. :) I guess its important to interpret those values correctly.

Research time...
 
Fact is my battery lasts me 2 days before its at 20% and needs to be recharged. And if I would have said that upfront you would have told me there wasn't a problem. But that's the thing. I hardly use my phone. In 2 days I have literally 20 min of talk time and less than an hour of screen time set to super low brightness. And all pervious android phones never showed the android system usage above 15% MAX. Usually closer to 2-5%. And with the same usage profile gave me at least 3 days between charges with batteries Half the size of the G2. I understand faster processors, more RAM and all that equals more battery consumption but it shouldn't when the phone is sleeping 97% of the time. Literally almost everything the phone came with that I can turn off is disabled, WiFi and GPS disabled, Location access to apps (and to google apps) is turned off. And The only apps downloaded and installed are literally Skype and Facebook which use 6 and 2 percent of the battery respectively the way I have them configured. I don't expect the claimed standby times of the device (11.4 days by the way) But with my usage profile and the size of the battery I should easily be able to get 3 or more days out of the battery. Something doesn't add up here.
 
That claimed stand-by time is calculated by different means in the factory [most important - NO wireless connection & airplane mode]. If your phone is sleeping most of the times, than that ~30% is a correct amount ! As said before, it's important to interpret those values correctly.

It also depends on how much bloatware/installed apps/apps that run in backgroud and use system processes you have installed.

Once again, i also recommend a factory reset.
 
Again. All bloatware disabled and i got better battery life from 2 phones with a battery HALF this size. And one of them was running jellybean just like the G2. And the reset didnt work. Still the same issue. And I dont give a F*** how you interpret those values. Both previous android phones lasted longer with MUCH smaller batteries and only show android system usage at 5ish percent. How is it that a original droid F-ing Razr on jellybean shows me 3% android system usage and lasts me 3 days? But the G2 lasts barely 2 and shows android system usage between 35 and 50% . How can one phone use 50 and one use 3 when they are on the same OS. And yes the numbers are relative. But again, SAME USAGE PROFILE. No matter how you slice it something is not right with this phone. Whether it be overblown, unneeded, undisableable system processes or a coding error. While this amount of android system usage may be common for some phones it is NOT (let me repeat that ) NOT normal. And I suggest anyone with these numbers to be proactive and not take it lying down. There is at least 1 KNOWN android system battery consumption bug with jellybean but it requires root to fix. And considering the root detection LG implemented in this device, I wanted to wait till my warranty expired before I root. I will however pose a question for G2 root users. How much does android system take up on your phone? I pose the same question to anyone with a motorola device root or not.
 
I'm rooted but didn't do anything to fix a bug. I take my phone off the charger at night. The battery goes down about 2% in eight hours with 15 apps updating stuff.
 
yeah I'm looking at a 6-7 percent drain overnight with almost nothing running. I also found this for anyone interested in seeing exactly how much battery Android system should take up [Q] How Much Battery Percentage Is Android OS Using On Your S3? - Android Forums at AndroidCentral.com its from another forum and I don't know the rules about posting crap from other forums but here it is in black and F-ing white. It's from a GS 3 but you get the idea. And here is the supposed solution I found How to Reduce Battery Drain on Your Samsung Galaxy S3 by Fixing Android System Usage
 
Battery life is insanely good on this phone. I don't use mine a ton but I find Android OS to be less than 20% (granted I'm on a custom ROM, CM11).
I'd say there's something wrong with your phone if you're finding that to be eating the most of your battery.
 
I had an issue, as one member mentioned before... i was getting lots of overnight battery drain [4-5-7%] - don't know why, i have the same stuff installed on the device as i had one the HTC One, but when i changed the firmware on the devil [non-rooted, changed the ROM w/ a stock one, but this time for my country] i am getting now : 1-2% drain overnight. There's definitely something going on with the ROM [bloatware and stuff that carriers place] and should be looked at ... even tough mine was and is not carrier locked !

A battery fail may also be the case, but i still bet on the ROM !
 
I have the Verizon version and after a days use (15 hours as I write this) mine shows android system as using 30%, screen 19%, cell standby 14%, android os 10%, phone idle 8%, google play services 4%, mediaserver 3%, wireless storage 3% and wi-fi 3% with 81% of the battery charge left. And I'm what I would say is a moderate user. Now my phone is rooted and that is all it is, I rooted it so that I could install Titanium Backup, I do not have a custom recovery installed and I have never installed any custom roms ( the only phone I've never seen or had an urge to do so on ). I would say do the dreaded factory reset and see how it goes, if it continues I would almost say it's a bad battery.
 
I have read somewhere on XDA that the knock-on feature wakes Android System all the time. It seems that if you disable it, Android System does not take so much battery. I have not tried this, just thought you may want to know.
 
Turn off one of the best features of the device? :)

I can't imagine it using that much battery when monitoring for the double tap... on the other hand, the act of waking the phone's screen many times... NOW THAT I could see could use a lot of the battery; taking the display from a low-energy state to a high state would necessitate a good draw on the battery.
 
You must log in or register to reply here.
Back
Top Bottom