CM7 really bad battery life? - HTC Incredible S

Hey everyone. I'm brand new to the community and just successfully rooted and installed the latest release of CM7. I tried looking around the forums but couldnt find any answers about getting really bad battery life on the Incredible specifically with CM7. I am actually getting worse battery life than with my stock ROM. I havent adjusted any settings but I did use a battery calibration app after the ROM was installed. There is some problems with the battery readings, specifically with starting at ~90% (I did not overcharge, battery calibration app told me when to calibrate at 100%) and then the quick and unannounced drop off at ~20%.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anyone have any ideas as to how I might be able to improve this or what I am doing wrong? Thanks in advance.

Mine is like this also.
My uptime and wake time are identical so something in the phone is keeping it awake. I'm yet to find out what it is.
What's strange is that I use my display quite a bit (1 and a half hours), yet it only uses 10% and it says cell standby uses the most??

Cm7 is the best battery life for me.
Get cpu spy the app and check to see if your phone is going into deep sleep

Is WiFi on always, or are you updating mail, weather, Facebook and so all the time?

gmail is on push
facebook notifications just pop up asap I dunno...
that's it..
Got juicedefender on, but don't want it to disconnect my connection when the phone is idle because I still want to receive notifications almost instantly.. Plus on the battery widget I had "currentwidget" it only used 30mA idle with connectivity on
and like 29mA with it off, so no big deal..
Also, wifi is on but doesn't turn on when the screen is off - it uses 3g....
Today I didn't use my phone much, just sitting at home pretty much and sent about 10 texts, it's down to 55% when I took it off charge about 10 hours ago. But maybe because my wake time is identical to my uptime that could mean something is using the battery...

scoobysnacks said:
Cm7 is the best battery life for me.
Get cpu spy the app and check to see if your phone is going into deep sleep
Click to expand...
Click to collapse
This is what I do. If your phone doesn't go into deep sleep then it will use alot more power than it should

http://i.imgur.com/FK5KK.jpg
That's my cpu spy and it seems to be going into deep sleep just fine. After just over four hours im down to just under 70% battery life. I really don't understand what's going on
Sent from my Incredible S using XDA App

tcardozo said:
http://i.imgur.com/FK5KK.jpg
That's my cpu spy and it seems to be going into deep sleep just fine. After just over four hours im down to just under 70% battery life. I really don't understand what's going on
Sent from my Incredible S using XDA App
Click to expand...
Click to collapse
Try tiamat kernel version 1.14 on smartass v2

scoobysnacks said:
Try tiamat kernel version 1.14 on smartass v2
Click to expand...
Click to collapse
For all intensive purposes this is like speaking another language. Could you provide a resource where I might be able to learn what you are talking about
Sent from my Incredible S using XDA App

try to adjust the brightness to 30% and close the 3g or wifi and data sync off when not in use hope this help

tcardozo said:
For all intensive purposes this is like speaking another language. Could you provide a resource where I might be able to learn what you are talking about
Sent from my Incredible S using XDA App
Click to expand...
Click to collapse
Go to the development section, and find the kernel called tiamat. Flash version 1.14 in recovery.
Download set cpu, set whatever max and min freq you want and set the governor in the drop down menu to smartass v2.

Well this has spiraled downhill fast for me. I attempted to flash the kernel mentioned above. I cleared both the caches and then my phone got stuck on the HTC logo at boot. I attempted to restore using clockwork but I got an MD5 error. No big deal, just had a fresh root anyways. did a factory reset, re installed CM7 and Gapps, everything booted up fine and I got all the basics set up again. Then went back into recovery to flash the kernel and again it is getting stuck on the boot screen. Anyone have any ideas? the effort and help is greatly appreciated

tcardozo said:
Well this has spiraled downhill fast for me. I attempted to flash the kernel mentioned above. I cleared both the caches and then my phone got stuck on the HTC logo at boot. I attempted to restore using clockwork but I got an MD5 error. No big deal, just had a fresh root anyways. did a factory reset, re installed CM7 and Gapps, everything booted up fine and I got all the basics set up again. Then went back into recovery to flash the kernel and again it is getting stuck on the boot screen. Anyone have any ideas? the effort and help is greatly appreciated
Click to expand...
Click to collapse
Are you sure that you downloaded the Kernel for the Incredible S and not for another device?
I just flashed Timant 1.1.5 with no problems.
You could also try using the Kernel Updatet Utility.
/ Jess Kölner /
/ Sent from my phone /

jkolner said:
Are you sure that you downloaded the Kernel for the Incredible S and not for another device?
I just flashed Timant 1.1.5 with no problems.
You could also try using the Kernel Updatet Utility.
/ Jess Kölner /
/ Sent from my phone /
Click to expand...
Click to collapse
Just double checked
This is the kernel that the previous poster told me to use, specifically to use 1.1.4. I guess I can try it with 1.1.5 and see if that works :S No idea why 1.1.4 from that site won't work though
**EDIT** attempting to flash 1.1.5 also results in getting locked on the bootscreen -.-

You're the first person I've seen have any issue flashing tiamat.
When flashing don't wipe anything and leave your phone for a bit it might take a bit longer to boot up.

FML. newbie mistake. for whatever reason the http://tiamat-dev.com/ site only has links on the side for the Droid Incredible 2 and not the Incredible S. As such, I was, in fact, using the wrong kernel. I managed to find a direct link/ elsewhere on the in the forums. Disaster has been averted. I will report back on (hopefully) battery life increase. Thank you everyone for your time.

Yeah dude cm nightlies 114 and tiamat 1.14 smartass v2 UV - 75 = insane battery life. Car charger is a waste of money with these settings.

itsbeertimenow said:
Yeah dude cm nightlies 114 and tiamat 1.14 smartass v2 UV - 75 = insane battery life. Car charger is a waste of money with these settings.
Click to expand...
Click to collapse
Agreed best battery life I've had on an Android phone yet.

itsbeertimenow said:
Yeah dude cm nightlies 114 and tiamat 1.14 smartass v2 UV - 75 = insane battery life. Car charger is a waste of money with these settings.
Click to expand...
Click to collapse
Any chance you could take the time to tell me what nightlies are? and how much different they might be from regular CM releases? also what do you mean by "UV - 75"?

tcardozo said:
Any chance you could take the time to tell me what nightlies are? and how much different they might be from regular CM releases? also what do you mean by "UV - 75"?
Click to expand...
Click to collapse
Nightlies are the nightly builds of cm7 they are released every day around noon and contain very few updates of cm7 but are the main way of beta testing. The version you have downloaded is essentially nightlies 109 because 108 was deemed bug free the stable nightlies 109 was declared the next user friendly version of cm7. There is a thread for this on the Dev forum.
As for UV it stands for undervolting. Read about it if you want. If not grab incredicontrol from the market. After opening you'll see the voltage settings for each CPU freq just hit all - 3 times you'll be undervolted by 75.

Related

Best battery on any ROM in past 30 days

Looking for the best battery life. Liking axura 2.5 look but I need max battery due to work for the next few weeks. Opinions of the best released in the past 30 days?
gocats7 said:
Looking for the best battery life. Liking axura 2.5 look but I need max battery due to work for the next few weeks. Opinions of the best released in the past 30 days?
Click to expand...
Click to collapse
Try this:
Code:
http://forum.xda-developers.com/showthread.php?t=848066
I got pretty good battery life on v2.5. Post 624 in the same thread has the version that I feel was best of all in terms of battery life.
You can read through the thread and see people's comments on awesome battery life.
Downloading now, will give it a look. I have never used one of these ROM's so it will be interesting. What irritates the heck out of me is there was one version of axura that had insane battery life a while ago, there have been a few perceptions, a few cognitions but I cant remember a damn one of them...LOL.
In regards to the ROM you suggested, just checking on your opinion on GPS, speed, etc. Battery is my main goal, just curious.
If you really want to save battery, you should probably turn down the brightness, use a completely black wallpaper, and underclock(the phone is still pretty snappy at 800mhz) and undervolt it.
But I find that the JL3 modem gives me the best battery life and best signal
I am on assonance 5.2 and I have had the best battery life ever. I turn off mobile network from the power menu popup when im not using it and I found that I got 33+ hours this past weekend.
Sent from my SAMSUNG-SGH-I897 using XDA App
gocats7 said:
Downloading now, will give it a look. I have never used one of these ROM's so it will be interesting. What irritates the heck out of me is there was one version of axura that had insane battery life a while ago, there have been a few perceptions, a few cognitions but I cant remember a damn one of them...LOL.
In regards to the ROM you suggested, just checking on your opinion on GPS, speed, etc. Battery is my main goal, just curious.
Click to expand...
Click to collapse
Speed is very snappy! And GPS works too. I get a lock even when I am inside my home.
Rockliveson123 said:
I am on assonance 5.2 and I have had the best battery life ever. I turn off mobile network from the power menu popup when im not using it and I found that I got 33+ hours this past weekend.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Im using Assonance 5.1 with the xcalibur kernel 2.2.1 and I'm getting about the same while still running the mobile network. I also keep it at full brightness most of the time and would say I'm a moderate user.
Sent from my SAMSUNG-SGH-I897
on di11igaf's 2.5 right now as recommended earlier. Cant say yet, loaded last night, recalibrated battery and it dropped the same over night as 2.5 axura did...but the dialer process was going nuts I found via os monitor. Rebooted and it was normal so that was not a good test of how much better it willl be. I do think it proves to me it will be better though as the dialer should be a fluke.
I was thinking of which versions of axura, etc was the best as far as battery and I think it was axura 2.4. I flash so darn often, they blur together after a while. I think perception 4 was good too, but it seemed more buggy if I recall.
Have never tried assonance, do hear good things about 4.3.
gocats7 said:
on di11igaf's 2.5 right now as recommended earlier. Cant say yet, loaded last night, recalibrated battery and it dropped the same over night as 2.5 axura did...but the dialer process was going nuts I found via os monitor. Rebooted and it was normal so that was not a good test of how much better it willl be. I do think it proves to me it will be better though as the dialer should be a fluke.
Click to expand...
Click to collapse
Maybe u should give it try for 3 days before u pass ur judgement
Sent from my GT-I9000 using XDA App
docs port is great with battery.
using xcal kernel.
71% left in case it us hard to read
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SCH-I897 using XDA App
diablo009 said:
Maybe u should give it try for 3 days before u pass ur judgement
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
LOL, good point. My plan is to leave it on for the next few weeks unless it proves not to be good enough on battery which I seriously doubt (or I just cant stand not flashing!). I was just rambling what I have seen so far in that its pretty obvious it will be better since I had that runaway process and it still matched my previous battery life.
Thanks for your help and recommendation.
mcord11758 said:
docs port is great with battery.
using xcal kernel.
71% left in case it us hard to read
Sent from my SCH-I897 using XDA App
Click to expand...
Click to collapse
Great!! Could you list out the exact steps u did to load this ROM. I am not new to ROMs, but just trying to know if u did anything else since u mentioned "with xcal's kernel".
diablo009 said:
Great!! Could you list out the exact steps u did to load this ROM. I am not new to ROMs, but just trying to know if u did anything else since u mentioned "with xcal's kernel".
Click to expand...
Click to collapse
Flashed stock and master cleared using odin.
Loaded rom through clockwork recovery.
Let it boot up first time. Kernel the rom comes worth is oc with ulf, which I do not care for. after first boot I downloaded xcal kernel, there us a link in the op for the rom. Went back into clockwork, made sure no lag fix was pre installed, which it was not. flash the zip through clockwork. Did battery recalibration, then ran till dead/turned off. Charged till full while off
Sent from my SCH-I897 using XDA App
mcord11758 said:
after first boot I downloaded xcal kernel, there us a link in the op for the rom. Went back into clockwork, made sure no lag fix was pre installed, which it was not. flash the zip through clockwork.
Click to expand...
Click to collapse
Ok. So to load xcal kernel, all I would need to do is to place the zip in sd card root and apply the zip through CWM. Wow, this sounds do-able. I'll try this the next time my mind itches for a new ROM flash. Thanks a bunch sir.
diablo009 said:
Ok. So to load xcal kernel, all I would need to do is to place the zip in sd card root and apply the zip through CWM. Wow, this sounds do-able. I'll try this the next time my mind itches for a new ROM flash. Thanks a bunch sir.
Click to expand...
Click to collapse
Outside of battery life it is a really solid rom. 2.2.1 base, stable, fast, and clean. It also had a bunch of themes you can flash that are not available on most captivate roms
Sent from my SCH-I897 using XDA App
mcord11758 said:
Outside of battery life it is a really solid rom. 2.2.1 base, stable, fast, and clean. It also had a bunch of themes you can flash that are not available on most captivate roms
Sent from my SCH-I897 using XDA App
Click to expand...
Click to collapse
One question here, does this ROM support backing up and restoring using CWM recovery console?
Do you guys feel that xcal kernel is better for battery life than setiron with oc/uv? I never oc anymore but I do uv to save battery and limit clock to 1000.
gocats7 said:
Do you guys feel that xcal kernel is better for battery life than setiron with oc/uv? I never oc anymore but I do uv to save battery and limit clock to 1000.
Click to expand...
Click to collapse
To be honest, I hardly noticed any noticeable difference between reducing clock speed. There might be a difference, but atleast I personally didn't notice.
diablo009 said:
One question here, does this ROM support backing up and restoring using CWM recovery console?
Click to expand...
Click to collapse
Have not tried but it does have working cmw
Sent from my SCH-I897 using XDA App
mcord11758 said:
Have not tried but it does have working cmw
Sent from my SCH-I897 using XDA App
Click to expand...
Click to collapse
Is this the ROM u r referring to?
[ROM] Official Darky Port v7.0.1! No Wipe! Ever!"It's over 9000!"
Code:
http://forum.xda-developers.com/showthread.php?t=880859
Edit:
Nvm, I think I found it.
[ROM][PORT]Doc's ROM JPY V6.1.3 CE *EXCLUSIVE THEME!* 12/23/10 *NO WIPE ADDED!*
Code:
http://forum.xda-developers.com/showthread.php?t=882397
How is the signal strength on this? Last time I loaded this, if I remember right, I had taken this off 'cos I was getting like 1 or 2 bars, while I have full signal on other ROMs.

[Q] Maybe a clue to battery issues? 2 instances android.process.acore using 100% CPU

Let me start by saying Thank You VERY much DroidTheory (and everyone who has contributed to making this an excellent stable ROM).
I am on the 1.4 (wiped cache, dalvik, battery stats, formatted system) build and I've been having the battery issues that everyone is talking about since 1.2. I am in the forums constantly and I have read all of the posts and the fixes for them. I have wiped battery data from a full charge, I'm on 1.4 so OMA files are already gone, I'm in Portland Or and we have stong 4G no drops ever since I have had my phone. So it isn't the cycling 4G/3G issue.
So I know there are multiple "my battery is dying" threads but I had not seen this one mentioned in any and don't want to get buried.
So I am having a bit of an issue getting a screen shot of it everytime I try I just get a wierd distorted image. That is not the issue I came for but if anyone knows.
What I am noticing is when I use the "Android System Info" app in the processes if I sort by CPU% I see 2 instances of the same thing "android.process.acore" both reporting 100% CPU and 35.28MB RAM. My total CPU is reporting around 50% at most times. I have tried killing the processes to see what may happen and there are no negative effects but the processes just seem to come back eventually if I check an hour (not exact) later there they are again.
I assume it's impossible for 200% of CPU to be used right now but what I'm wondering is would 100% CPU on one process equal to 50% when considering that nothing uses both cores yet?
Any clues what these processes (android.process.acore) are and if there is anything I can do. If someone can suggest a good way to take screens I will be happy to post one as well.
Use Screenshot ER instead of AndroSS. Curious to your findings. Massive battery drain here. I dropped 10% in 45 minutes doing absolutely nothing. Nothing rogue in my battery stats...
Sent from my DROID BIONIC using xda premium
Now I did notice that both say com.fede.launcher. This seems to say to me it is launcher pro as the dev is Federico Carnales. Im really hoping the 2 aren't in compatible as I've been using this since it came out in my D1 and I am damn used to it. Anyways here is my screen shot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my DROID BIONIC using XDA App
Also I should mention that when I kill one process it kills both at the same time. I am using 0 of the launcher pro widgets so it doesn't seem to be polling or syncing. And nothing acts any differently (that I can see) after the kill. No restart of launcher or anything.
Sent from my DROID BIONIC using XDA App
Proff3ss0r Farnsw0rth said:
Now I did notice that both say com.fede.launcher. This seems to say to me it is launcher pro as the dev is Federico Carnales.
Click to expand...
Click to collapse
Pretty sure Fed said LP/LP+ isn't tested to work on gingerbread yet
Maybe that'll be fixed once he's done w/ the rewrite?
Wish I could help ya tho...just another pointless reply here
Proff3ss0r Farnsw0rth said:
Also I should mention that when I kill one process it kills both at the same time. I am using 0 of the launcher pro widgets so it doesn't seem to be polling or syncing. And nothing acts any differently (that I can see) after the kill. No restart of launcher or anything.
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
I see this, 100% CPU on 1 or more threads of a single process on multiprocessor linux boxes where that process has run away/spinning in code... on a 2 processor system the system would look always loaded 50% or more...
Hey that's news to me man. Honestly by the time I put GB on my D1 I couldn't tell a difference because my battery was suffering as is so it could have been doing it there too...
Mista Wolf are you running launcher pro as well?
Sent from my DROID BIONIC using XDA App
That was my guess on the cores was 100% of of what it has the ability to use right now is only 50% of available.
Sent from my DROID BIONIC using XDA App
I have launcher pro and those processes don't run at all on my phone.
Sent from my DROID BIONIC using XDA App
Proff3ss0r Farnsw0rth said:
Hey that's news to me man. Honestly by the time I put GB on my D1 I couldn't tell a difference because my battery was suffering as is so it could have been doing it there too...
Mista Wolf are you running launcher pro as well?
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
I am using the stock Blur launcher. My battery is just taking a beating...
I really want to figure this out because I love this ROM.
I swapped out to launcher ex I was pretty much able to duplicate my lp+ setup I'll see what happens I'm good so far no return. We'll see if this cures my battery issues.
Sent from my DROID BIONIC using XDA App
And its back... so I seem to be getting this no matter what launcher I use on top of stock. Can anyone else confirm this? Could someone that can dig deeper into this try to duplicate and find out why these processes seem to be taxing the cpu so much or are there any resources I can pull that could help me get this figured out?
Sent from my DROID BIONIC using XDA App
I get great battery life with launcher pro. It may not be optimized for gingerbread(or so it's said) but it runs great for me. I was getting a day and a half on Eclipse for the x2.
Sent from my DROID BIONIC using xda premium
I have been running zeam launcher, and have had absolutely amazing battery life, unplugged at 6:30, and will still be in the 70's with light use, or 60's with moderate use come quitting time.
Sent from my DROID BIONIC using xda premium
Proff3ss0r Farnsw0rth said:
And its back... so I seem to be getting this no matter what launcher I use on top of stock. Can anyone else confirm this? Could someone that can dig deeper into this try to duplicate and find out why these processes seem to be taxing the cpu so much or are there any resources I can pull that could help me get this figured out?
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
I installed Android System Info and checked that my android.process.acore was not using any cpu cycles (0%). I use the Go Launcher. I would suggest trying the dreaded "Factory Hard Reset". I know it's a pain and time consuming, but it cures a lot of random ills.
Good luck.
Yeah I am doing a reinstall with a rewipe at the moment (I know this isn't hard reset). I am a very process oriented person so I doubt I missed any of the wipe/formats needed for Unleashed but I'm going to give it another try.
After doing a bit of google searching for "android.process.acore" I find ALOT of people with the exact same issues (on different phones) all with non-stock launchers. I have found a few suggested fixes. Like removing widgets from stock browser and all other launchers (I have a few right now as I've been testing and trying to work around.
This does seem to be a widespread problem though for more than just us.
Geezer could you please keep checking on Android System Info for me randomly (this is not an all of the time thing) I can kill the process and it will stay dead for a seemingly random amount of time (haven't been able to notice a pattern yet) at seemingly random points(I'm not noticing any one action causing this). But from the other references I'm seeing to this problem all seem to revolve around updating but most for different things... I have been taking note of PID in Android System info and searching for the PID in CATLOG I am finding references to the PID but honestly I don't see any glaring problems but I'm no dev and I don't fully understand what it is telling me. If I provide LOGCAT of the process could someone translate for me?
Proff3ss0r Farnsw0rth said:
Geezer could you please keep checking on Android System Info for me randomly (this is not an all of the time thing) I can kill the process and it will stay dead for a seemingly random amount of time (haven't been able to notice a pattern yet) at seemingly random points(I'm not noticing any one action causing this). But from the other references I'm seeing to this problem all seem to revolve around updating but most for different things... I have been taking note of PID in Android System info and searching for the PID in CATLOG I am finding references to the PID but honestly I don't see any glaring problems but I'm no dev and I don't fully understand what it is telling me. If I provide LOGCAT of the process could someone translate for me?
Click to expand...
Click to collapse
Will do. I just checked and it's still at 0. I'll check throughout the day and let you know tonight.
Good luck.
ROB281 said:
I have been running zeam launcher, and have had absolutely amazing battery life, unplugged at 6:30, and will still be in the 70's with light use, or 60's with moderate use come quitting time.
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
+1
Zeam launcher is awesome.
I checked out zeam but I just can't deal with how minimal it is don't get me wrong I run very minimal home screens (nearly 0 widgets but battery and clock and only 2 home screens. I just can't deal with the lack of options in zeam. I don't really have any further leads on this I've been fighting with it as I've had chances at work but still no luck. Does anyone here know how to actually read a logcat or will that even get me what I need?
Sent from my DROID BIONIC using XDA App
FWIW, I'm getting ABYSMAL battery life (7h4m from full charge to shutdown as of my last cycle just now), with only 8 minutes of phone calls, light surfing, light texting, email sysncs at 1/hour.
I'm running GoLauncher with UNL3EASH3D v4. I have yet to see the process you describe (and I've been checking it pretty frequently trying to track down my drain- in fact, without exception every time I check, Android System Info is the process using the highest cycles at about 10-13%). I also used Go with stock for a day or so and didn't have this level of drain. HOWEVER, I didn't duplicate my stock setup when i flashed unleashed, so it may well be unrelated to the ROM.
I AM seeing waaaaaay too much awake time on the stock battery stats screen.
I'm about to do a wipe and reinstall and run minimal for a few days to see if I can pinpoint anything. Trying to hold out for the update if I can... (Love the ROM, so really don't wanna go stock)

[BATTERY IMPROVEMENT] Works every time half the time :)

DISCLAIMER AS PER USUAL: YOU DO IT AT YOUR OWN RISK.
Although procedure itself is simple enough, but as alway, anything involving flashing, especially firmware has it's risks.
Oki doki. Time to come out in the open
Prelude. I was hard pressed to get 4h screen on time in 10-12h off charger. Then i screwed something up (irrelevant ) and had to reflash stock images.
Now my next findings are sure to attract so flaming from more experienced users that will say "it's placebo", "it doesn't work like that" etc. While I don't have screenies to confirm pre flash stats, i have gathered a few post flash stats. Here we go.
Some cycles are missing, since i either accidently deleted screenies or forgot to take them. But that should give you a general idea. WiFi used mainly, apart from last cycle, where 12 were on data only and the rest was while connected to wifi and reading a book in fbreader.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
And this is ROM/KERNEL i used before and after flashing images. Note, kernel has been updates since, but it didn't make much difference.
So for me it's fairly conclusive, reflashing stock images has GREATLY improved my battery life. I had a few chats and we came to a conclusion that it is possible that at the factory device has simply not been flashed "properly", mass flashing differs from your usual .img flashing normally.
What you think...Well, it's up to you for decide. I know few more people who've done the same, and while their improvement is not as drastic as mine, it is still an improvement.
Please vote AFTER you try it, and after min of 2 cycles.
How to in post no2
Simply follow this great guide by efrant. Keep in mind it will wipe your storage, so backup all the pics and other stuff.
Before you do it, take below quote into consideration if you use google wallet.
dacho said:
Oh yes, you have to reset Google wallet before you flash it. You would log into Google wallet then settings and click reset wallet. I remember this from galaxy nexus days.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
efrants guide
People who are more experienced will know how to cut corners If you don't know what you are doing, I suggest you follow efrants guide to the letter. This way you'll learn a fair bit too.
Same process for every images version. Also, I ALWAYS do it for any images update, since I'm not a believer in patching. I might be wrong, but hey, it works for me. So my personal recomendation would be to redo this after every new OTA.
So:
1. Backup your "SD" contents.
2. Flash ALL stock images as per efrants guide (or any other way if you know how to)
3. You are most likely to get stuck on boot. Hold power button, shut down, reboot into recovery. Once you see broken droid hold power button and tap +vol. Once in recovery do factory reset. If you don't get stuck on boot, still do it.
4. Boot on stock. It's a good idea to transfer your rom and kernel onto sd now since you can't mount sd in recovery.
5. Reboot into bootloader and proceed to push recovery and then flash your previous setup (ROM/KERNEL)/
How to push recovery.
Code:
fastboot flash recovery recovery-image-name.img
I will not tolerate any flaming, just report if it worked for you or it didn't. If you want to stir some **** you better go elsewhere. Chit chat related to the topic is approved and appreciated
I want to mention DowntownJeffBrown, DirtyHamster, ctowe, Jayrod1980, siloner, estallings15 and anyone else I forgot (just remind me in the thread) for being the beta bunnies Thank you.​
I'm gonna try this and report thre results. Were you on auto-brightness, sync, gps...? Give us some more infos about what your configurations are
Thank you for the tip, I'll try.
sorcio91 said:
I'm gonna try this and report thre results. Were you on auto-brightness, sync, gps...? Give us some more infos about what your configurations are
Thank you for the tip, I'll try.
Click to expand...
Click to collapse
All on auto, the only two things i have disabled is gnow and location reporting (which is primarily used for gnow anyway) and had that disabled from day one. The rest of the settings are irrelevant, since they are the same from before i reflashed stock.
Interesting, be good to see what others report.
If i hear a few good reports, i might take the plunge next week.
Edit: might just be Rasbean jelly giving you good battery life!
Cool, I'll give it a try and see what it does!
I'm struggling to get +4 hours of battery life ATM, so let's hope this helps.
superleeds27 said:
Interesting, be good to see what others report.
If i hear a few good reports, i might take the plunge next week.
Edit: might just be Rasbean jelly giving you good battery life!
Click to expand...
Click to collapse
It's not. Wait till some Americans who done the same thing wake up
There are about 4-5 more people who report the same, that's why i decided to share. Had to make sure first that it's not a fluke.
Re: [BATTERY IMPROVEMENT] Works 100% so far.
The thing that's helping battery life here isn't the reflash, it's the factory reset that happened when you did it.
Rusty! said:
The thing that's helping battery life here isn't the reflash, it's the factory reset that happened when you did it.
Click to expand...
Click to collapse
I would tend to agree. But which would be the cause, removed culprit user installed app(s) or something not set as intended from factory as a result of mass flash/ reset etc at factory? Or both?
Maybe even a difference between OTA updating new units after setup or before?
Would be easy to test the theory by just doing a factory reset without re-flashing and see if it makes a difference.
Rusty! said:
The thing that's helping battery life here isn't the reflash, it's the factory reset that happened when you did it.
Click to expand...
Click to collapse
I did think of that. Thing is flashing ROM fresh IS factory reset. Factory reset doesn't do more than delete all the data and maybe reflash /system. So i disagree with you here Rusty. Think about it. I took my time to carefully evaluate changes, and you might know from my time in Sensation forum that I do look into things before posting it.
clockcycle said:
I would tend to agree. But which would be the cause, removed culprit user installed app(s) or something not set as intended from factory as a result of mass flash/ reset etc at factory? Or both?
Maybe even a difference between OTA updating new units after setup or before?
Would be easy to test the theory by just doing a factory reset without re-flashing and see if it makes a difference.
Click to expand...
Click to collapse
See above.
Also, apps have nothing to do with it, since my (and other people) setup is identical to what it was before doing that.
And thanks to the person voting NO. I guess following simple request is too difficult.
If you guys are sceptical, do it before you do next fresh install since you don't lose anything and report back.
undercover said:
I did think of that. Thing is flashing ROM fresh IS factory reset. Factory reset doesn't do more than delete all the data and maybe reflash /system. So i disagree with you here Rusty. Think about it. I took my time to carefully evaluate changes, and you might know from my time in Sensation forum that I do look into things before posting it.
See above.
Also, apps have nothing to do with it, since my (and other people) setup is identical to what it was before doing that.
And thanks to the person voting NO. I guess following simple request is too difficult.
If you guys are sceptical, do it before you do next fresh install since you don't lose anything and report back.
Click to expand...
Click to collapse
Thanks for posting this! Very interesting if others are experiencing the same. I will try it when I get time. What do you think is the improvement? Did you restore a nandroid or did you manually reinstall everything? Thx bro!
Re: [BATTERY IMPROVEMENT] Works 100% so far.
jonup said:
Thanks for posting this! Very interesting if others are experiencing the same. I will try it when I get time. What do you think is the improvement? Did you restore a nandroid or did you manually reinstall everything? Thx bro!
Click to expand...
Click to collapse
I can vouch for this experiment that we somehow agreed to without even hesitating lol.
Personally, i manually installed EVERYTHING. no nandroid or titanium back up. Before i would get roughly 9hr phone usage with 2.5-3 hrs battery. After going through this i now get 13-14hrs phone usage with 4-4.5 screen on. I know that's normal for some but compared to what i had before, is an improvement. This was just in the first cycle. I'm on my second and wool report back when I'm done
Sent from my Nexus 4 using xda premium
As it stands i can hit 5 n half hours with round a day standby.
Would it be worth doing?
Re: [BATTERY IMPROVEMENT] Works 100% so far.
superleeds27 said:
As it stands i can hit 5 n half hours with round a day standby.
Would it be worth doing?
Click to expand...
Click to collapse
Not sure. But someone already had very decent battery life and extended it by another 0.5-1h screen on. I guess you wouldn't lose anything if you tried. Just a half an hour of setting things up.
Sent from my Nexus 4 using Tapatalk 2
Re: [BATTERY IMPROVEMENT] Works 100% so far.
undercover said:
Not sure. But someone already had very decent battery life and extended it by another 0.5-1h screen on. I guess you wouldn't lose anything if you tried. Just a half an hour of setting things up.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
+1 I've seen their posts.
Make a nandroid. You have nothing to lose but time. It's the weekend anyway.
Dont want to say anything but on screenshoots there is practically no apps other than browser or taptalk, play a game, watch a clip on YT, listen to some music ohh and switch off WiFi. Phone is to be used outside where you dont have a WiFi, At home I have my Laptop that is far much better than than a phone to read stuff, and XBox that is far much better for gaming....
I could probably pull 8h screen if I switch everything off sans WiFi and just have web browser opened on one page.
Ohh And I'm on stock since day 1 + had to reflash image due to kernel net being compatibile with screen sensitivity driver .... No changes, What you have on images wont repeat itself outdoors.
Look at that screen where you dont have WiFi on. Your usage dropped by 8hrs screen time by 1hr and still no phonecalls, txt, nothing really.... just chrome
I get 3hrs 30min screen + 17hrs usage with music in bacground, quick game + and reading, no reception for about 8hrs or if there is any its 1bar....(and that drains the battery)
Re: [BATTERY IMPROVEMENT] Works 100% so far.
MattSkeet said:
Dont want to say anything but on screenshoots there is practically no apps other than browser or taptalk, play a game, watch a clip on YT, listen to some music ohh and switch off WiFi. Phone is to be used outside where you dont have a WiFi, At home I have my Laptop that is far much better than than a phone to read stuff, and XBox that is far much better for gaming....
I could probably pull 8h screen if I switch everything off sans WiFi and just have web browser opened on one page.
Ohh And I'm on stock since day 1 + had to reflash image due to kernel net being compatibile with screen sensitivity driver .... No changes, What you have on images wont repeat itself outdoors.
Look at that screen where you dont have WiFi on. Your usage dropped by 8hrs screen time by 1hr and still no phonecalls, txt, nothing really.... just chrome
I get 3hrs 30min screen + 17hrs usage with music in bacground, quick game + and reading, no reception for about 8hrs or if there is any its 1bar....(and that drains the battery)
Click to expand...
Click to collapse
Ok. I think I have to explain something. This is absolutely not about how or what for phone is used. I used it in the same way before I flashed images.
Concentrate on the MAIN thing. Same usage, same rom and kernel, same settings, same apps. The only difference is battery life after flashing stock images files. Immediately.
Sent from my Nexus 4 using Tapatalk 2
Re: [BATTERY IMPROVEMENT] Works 100% so far.
undercover said:
Ok. I think I have to explain something. This is absolutely not about how or what for phone is used. I used it in the same way before I flashed images.
Concentrate on the MAIN thing. Same usage, same rom and kernel, same settings, same apps. The only difference is battery life after flashing stock images files. Immediately.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, he totally missed the point. Same usage, but better battery life. This is not a battery life comparison thread.
Re: [BATTERY IMPROVEMENT] Works 100% so far.
estallings15 said:
Yeah, he totally missed the point. Same usage, but better battery life. This is not a battery life comparison thread.
Click to expand...
Click to collapse
Spot on.
Screenies are there just to show consistency.
Sent from my Nexus 4 using Tapatalk 2
Re: [BATTERY IMPROVEMENT] Works 100% so far.
Well, I guess poll won't reflect true outcome. This is annoying since I do it for you guys. I get no benefit from sharing that, I don't ask for donations or thanks, don't ask for credit. I just want people to enjoy great battery life I'm enjoying.
"Thanks" guys....
Sent from my Nexus 4 using Tapatalk 2

I am loosing my mind! Note eating battery and superslow

Hi!
My Note has for a quite long time now been slow, laggy and eating battery.
Didn't mind, had a car charger, suspected old battery and clogged storage.
About a week ago it came to a complete stop, taking 30 sec to open facebook.
And typing in Swiftkey an impossibillity, having keystrokes on a 5-10sec lag.
So finally i got a new battery, whiped the phone clean.
Flashed the phone with a fresh rom (Team Union JB XXLT4 V7)
Installed my apps manually, making shure no crap cache was brought.
Formatted internal storage and got a new 32Gb SanDisk Ultra card.
Fresh start, fast phone right? no.
Apps still unusably slow, typing on swiftkey impossible without lagging.
Battery from a full charge last about 6h with light usage.
Would like to stay on TW only for the MHL capability, but now i am open to anything.
Can't really afford a new phone, so if this can't get resolved ill switch to my old 3GS.
What do i do now?
What can i try?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The screenshots are from different days and scenarios, but changing governor or other settings gives me about the same result.
Just listened to som music, and some light surfing, thats about all. Battery blames is all on the screen and os about 33% & 33%.
YOu should try AOSP/AOKP Roms!!!
I think one of the apps you have is causing the problem.
When i had the same problem it turned out to be the podcasting app i had.
https://play.google.com/store/apps/details?id=com.asksven.betterbatterystats&hl=en
Or go to the terminal and run top, see whats eating the cpu.
have you try to replace new battery ?!
NoteboyTech said:
YOu should try AOSP/AOKP Roms!!!
Click to expand...
Click to collapse
Thanks for the reply, but i am afraid ill have the same issues.
Azeazezar said:
I think one of the apps you have is causing the problem.
When i had the same problem it turned out to be the podcasting app i had.
https://play.google.com/store/apps/details?id=com.asksven.betterbatterystats&hl=en
Or go to the terminal and run top, see whats eating the cpu.
Click to expand...
Click to collapse
Good suggestion, i'll run top once in a while, see i find anything.
nokia2002 said:
have you try to replace new battery ?!
Click to expand...
Click to collapse
Well, yeah couldn't find any original though, and don't want to wait weeks for a shipment, so got a copy brand "ENERGY" spacy logo and made here in Thailand. Only 2350mAh compared to the original 2500mAh.
Found that the new battery didn't really make any difference, about the same.
So worried i got new but crappy battery I'm now back on original, without any noticable change.
Considering getting a external charger and carrying the spare battery, that is not really a solution either.
Got get this phone working reliably soon, or i need to find a replacement.
Appreciate the tips, and ill try and make a study with "top" and get back to you guys.
Maybe i have a energy hog after all...
It's a pain in the butt, but it looks like the only way to resolve it is to do a clean wipe, then install each
app one by one, giving yourself a day or two of usage. Sucks, but it sure sounds like one app is
screwing up another one. Any chance you can (shudder) use a "memory cleaner/program closer"
after you use each app, to make sure it's closed as a test? Sounds like something sure is
interacting with something else.
USe Greenify and hibernate all apps!!!
Check your Google account settings. If you have sync Internet ticked disable it.
Sent from my GT-N7000 using XDA Premium 4 mobile app
You think you have it bad? I'm only getting 4.5 hours
Sent from my GT-N7000 using xda app-developers app
JellybeanSandwich said:
You think you have it bad? I'm only getting 4.5 hours
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Really?
I thought my battery life was bad. 7h15m with 45 min screen time after charging my battery is at 67%
That is with wifi and bluetooth (with music playing) on and connected.
GPU overclocked and lowest step 200mhz(from 133 and max 400) and cpu up to 1550 Mhz.(okay, i did reduce the voltages, sue me)
and google location service on.
On original battery (dec 2011), that is about to die (screen starts glitching around 30%)
Somehow you are doing it wrong.
You would be surprised at what a speed deference you will get and battery life with aosp roms I have used tw and aosp and always go back to aosp based when tw starts to get laggy. But as most have said most likely a app causing your problem you should try install new Rom with all wipes inclueding preload I think thats what its called and make sure that media scan is not always running
Sent from my GT-N7000 using XDA Premium 4 mobile app
I'm pretty dependant on my camera for my kids. From my readings of AOSP threads, the camera app has never really worked well? Or am I misinformed?
Sent from my GT-N7000 using xda app-developers app
I do not use the camera that much, but i have not had problems with it.
Focal does crash for me and makes me reboob my phone.
Azeazezar said:
Really?
I thought my battery life was bad. 7h15m with 45 min screen time after charging my battery is at 67%
Click to expand...
Click to collapse
With a new battery original OEM just purchased yesterday, I am at 4h10m with 55 minutes screen time at 64%
This is much better.
Sent from my GT-N7000 using xda app-developers app
Just an update everyone:
I'm currently at 7h15m with 2 hours screentime.
The battery is at 38%
I will have to chalk this up to a worn battery being replaced by a real Samsung battery and not a knockoff 3rd party battery.
Sent from my GT-N7000 using xda app-developers app
Batteries make a big difference and as for cm roms and the camera they work great
Sent from my GT-N7000 using XDA Premium 4 mobile app
How about tying to read or post on the battery thread in Q&A instead of posting new threads in the wrong section?
This didn't start out as a battery discussion
Sent from my GT-N7000 using xda app-developers app
AndroidSlave said:
How about tying to read or post on the battery thread in Q&A instead of posting new threads in the wrong section?
Click to expand...
Click to collapse
JellybeanSandwich said:
This didn't start out as a battery discussion
Click to expand...
Click to collapse
How about reading the first post AndroidSlave?
What's this snarkyness that's infected xda?
Shure wasn't around back in the WM days.
This is and or was a very "General" issue with my phone, as i am still not entierely shure is a plain software issue.
However i've made the switch to a or the PA-rom out of desperation.
Still too early too tell, as it is first day after flash, but feels smoother.
What is driving me mad on PA is the lack of lockscreen-homebutton-torch.
Also a bit dissapointed in "Screen Mode" dynamic mode missing.
Missning SPen->screenshot->notetaking is bugging me aswell, but i'm shure ill find some replacement thing for that.
EDIT:
You, know what.
I apoligise if i posted this in the wrong place.
And no bad intentions towards you AndroidSlave.
I just feel that it's the place of a MOD and not of a user to make these claims.
Please just use the report button in if you feel like this, instead of posting a retorical question.
I know, right? What's up with the uninformed snark?
Sent from my GT-N7000 using xda app-developers app

V10 (msm 8992) | CPU, GPU, IO, RAM, Interactive Gov. || TWEAKS

Original post, here, in TMO section
http://forum.xda-developers.com/tmo...-msm-8992-cpu-io-ram-interactive-gov-t3351478
Cheers mates :highfive:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This was my result after 3 days...
Sent from my LG-H900 using Tapatalk
its kinda like u r sucking ur battery. never saw this kind of droppage, i shuld try a factory reset!
greekunit690 said:
This was my result after 3 days...
Sent from my LG-H900 using Tapatalk
Click to expand...
Click to collapse
You are literally the only person to have these results..
Stop spamming. You screwed something up while installing it (hard to do because I gave you the lines to copy/paste over) or you are running some kernel or ROM causing this drain. I'd like to see something other than the battery graph, to see what your app usage was...
Go home troll.
warBeard_actual said:
You are literally the only person to have these results..
Stop spamming. You screwed something up while installing it (hard to do because I gave you the lines to copy/paste over) or you are running some kernel or ROM causing this drain. I'd like to see something other than the battery graph, to see what your app usage was...
Go home troll.
Click to expand...
Click to collapse
I actually wasn't trying to be a troll or spam. I'm on an AT&T V10 so I'm obviously running stock Rom rooted (as there's no unlocked bootloader yet). Only other thing I have from xposed is gravity box only for visual changes. I copied and pasted directly to the ETC folder as you stated was allowable later in the thread. I only asked to see because, like you said, it's hard to mess something up. Don't really appreciate being called a troll for asking a simple question....
Edit: only other thing I can think of is I changed batteries on a daily basis because I'm away from outlets for most of the day and have nowhere to recharge. I think I read something that the phone takes up battery on start up. But without this mod I would usually get 5-6 hours SOT and about 14 hours on a full charge
Sent from my LG-H900 using Tapatalk
greekunit690 said:
I actually wasn't trying to be a troll or spam. I'm on an AT&T V10 so I'm obviously running stock Rom rooted (as there's no unlocked bootloader yet). Only other thing I have from xposed is gravity box only for visual changes. I copied and pasted directly to the ETC folder as you stated was allowable later in the thread. I only asked to see because, like you said, it's hard to mess something up. Don't really appreciate being called a troll for asking a simple question....
Edit: only other thing I can think of is I changed batteries on a daily basis because I'm away from outlets for most of the day and have nowhere to recharge. I think I read something that the phone takes up battery on start up. But without this mod I would usually get 5-6 hours SOT and about 14 hours on a full charge
Sent from my LG-H900 using Tapatalk
Click to expand...
Click to collapse
Your screen shot included nothing but a battery graph. No app usage, no explanation of what you are running / doing. And your saying "I'm rooted running xposed and all stock" is not you running stock. It is you running xposed rooted and probably with other small modifications here and there.
Just would be useful to not just come up here and make it look like this script magically destroyed your battery life somehow when it is literally nothing but basic shell scripts to modify very high level parameters of device operation. Like I said, you are literally the only person to ever have an issue. Post something useful other than "hey this is terrible here's a one off screen shot and no other information about what makes me unique from everyone else."
I didn't respond to your original question in the other thread because it was uninformative as to what you might have done wrong while installing the file. You posted a graph, then asked what you did wrong.
Good question. I have no idea. But obviously something because I've been using this for weeks now, and many other people as well and nobody has experienced this mystery battery sucking you are seeing.
It is important to note that your device will boot with all CPU governors set to "performance" which taps your frequency to max. This file changes it post boot, so if you didn't copy the file, or more importantly didn't set it's permissions properly afterwards, your device will be stuck running performance, possibly reboot, and certainly will suck your battery dry very quick.
You need to give me more if you want my help, otherwise I will ignore you. I do this stuff for a living and it isn't my job to be a test engineer for your device as well as my own.
warBeard_actual said:
Your screen shot included nothing but a battery graph. No app usage, no explanation of what you are running / doing. And your saying "I'm rooted running xposed and all stock" is not you running stock. It is you running xposed rooted and probably with other small modifications here and there.
Just would be useful to not just come up here and make it look like this script magically destroyed your battery life somehow when it is literally nothing but basic shell scripts to modify very high level parameters of device operation. Like I said, you are literally the only person to ever have an issue. Post something useful other than "hey this is terrible here's a one off screen shot and no other information about what makes me unique from everyone else."
I didn't respond to your original question in the other thread because it was uninformative as to what you might have done wrong while installing the file. You posted a graph, then asked what you did wrong.
Good question. I have no idea. But obviously something because I've been using this for weeks now, and many other people as well and nobody has experienced this mystery battery sucking you are seeing.
It is important to note that your device will boot with all CPU governors set to "performance" which taps your frequency to max. This file changes it post boot, so if you didn't copy the file, or more importantly didn't set it's permissions properly afterwards, your device will be stuck running performance, possibly reboot, and certainly will suck your battery dry very quick.
You need to give me more if you want my help, otherwise I will ignore you. I do this stuff for a living and it isn't my job to be a test engineer for your device as well as my own.
Click to expand...
Click to collapse
Sorry for the confusion. Yes I meant stock Rom as in no custom Rom. And as stated all I have xposed wise is gravity box with visual only.
I'm going to try a factory reset as someone else stated and copy only your file and see what happens after a few days.
I'm no noob when it comes to flashing and changing parameters which is why I was confused about why this had such a detrimental effect.
Again I thank you for your hard work and all the positive things you've given xda on your own time. I'm sure it's just something to do with only upgrading from root and not starting fresh
Sent from my LG-H900 using Tapatalk
greekunit690 said:
Sorry for the confusion. Yes I meant stock Rom as in no custom Rom. And as stated all I have xposed wise is gravity box with visual only.
I'm going to try a factory reset as someone else stated and copy only your file and see what happens after a few days.
I'm no noob when it comes to flashing and changing parameters which is why I was confused about why this had such a detrimental effect.
Again I thank you for your hard work and all the positive things you've given xda on your own time. I'm sure it's just something to do with only upgrading from root and not starting fresh
Sent from my LG-H900 using Tapatalk
Click to expand...
Click to collapse
I think it would be good if you post the command output of
Code:
ls -l /etc/init.qcom.post_boot.sh
and also a screenshot with the app usage stats.
WillyPillow said:
I think it would be good if you post the command output of
Code:
ls -l /etc/init.qcom.post_boot.sh
and also a screenshot with the app usage stats.
Click to expand...
Click to collapse
Seems to be doing a bit better today but again not much difference from without the change.
Here is the output in from terminal emulator
And here's screen time
And the app usage
Sent from my LG-H900 using Tapatalk
greekunit690 said:
Seems to be doing a bit better today but again not much difference from without the change.
Here is the output in from terminal emulator
And here's screen time
And the app usage
Sent from my LG-H900 using Tapatalk
Click to expand...
Click to collapse
@greekunit690 it might just be coincidence, but under your display settings try unchecking & rechecking the Auto option under Brightness. I've found that for whatever reason the brightness setting will get stuck at the highest level even though I have Auto selected. This has led to rapid battery drain for me when it happens.
Dryvlyne said:
@greekunit690 it might just be coincidence, but under your display settings try unchecking & rechecking the Auto option under Brightness. I've found that for whatever reason the brightness setting will get stuck at the highest level even though I have Auto selected. This has led to rapid battery drain for me when it happens.
Click to expand...
Click to collapse
I change my brightness throughout the day so I'm sure that wouldn't be the case..thanks for the input though
Sent from my LG-H900 using Tapatalk
Just saying...im running your mod and its great I love it!
Sent from my VS990 using Tapatalk
in99flames said:
Just saying...im running your mod and its great I love it!
Sent from my VS990 using Tapatalk
Click to expand...
Click to collapse
i cant use it
how did you install it ?
Its not hard. Just follow the instructions and use terminal emulator to input the commands. After you do it once from the commands you can simply copy and paste the file in the appropriate folder and correct the permissions when an update is posted.
rowihel2012 said:
i cant use it
how did you install it ?
Click to expand...
Click to collapse
If you're having issues you can try this
http://forum.xda-developers.com/showthread.php?t=3388850
Sent from my LG-H901 using XDA-Developers mobile app
another holy mother of earth issue with our v10 mine with zerolemon charged for 12 hours getting 6hours SOT , drains 20% overnight. WTH
warBeard_actual said:
Original post, here, in TMO section
http://forum.xda-developers.com/tmo...-msm-8992-cpu-io-ram-interactive-gov-t3351478
Cheers mates :highfive:
Click to expand...
Click to collapse
Having a little trouble in that thread determining which one is the latest version to download, could you link me to the latest dangerously version and regular version please? Ty
Can i use it on H960A?
brenas25 said:
Can i use it on H960A?
Click to expand...
Click to collapse
yes

Categories

Resources