Related
First off, this might be a topic for the general forum, but since is pertains directly to development, i thought i would put it here... Mods.. please move if you feel this is inappropriate.
There seems to be some HUGE differences with Ava v10 and battery life and i wanted to try and narrow down what the differences are to see what is up!
What i am curious about and would like you to post is the following:
Hardware Version
Screen
Kernel you are using
battery life / Usage
If we are seeing a pattern here then we should be able to determine the problem and hopefully yield some good data for devs to use. If it is still very random.. then its got to be an app that is causing the issues.
I will start
Hardware 003
Epson
Stock Kernel
8 - 9 hours MAX on moderate - use (lots of texting, some calls, and a little web browsing) Was getting WAY better on v9 before 3.30 update (v9a)
It is apparent the 3.30.2/3 has drastically ****ed battery life. There has been way too many posts about it to ignore it now.
It isn't HTC kernel 17 related like someone said earlier either. It goes deeper than that because I never run HTC kernels, not even for 5 minutes after installing a rom and I notice it very much. It appears that the current during idle isn't affected. And it isn't a rogue program PR anything keeping the CPU from idling. I dunno what it is. But it really is very noticeable.
I wish more dev's would realize it and make updated 3.29s with some of the new stuff built-in like the pnotification pulldown switch thing, and stuff like that.
Thanks azrael so far for not ignoring the situation. Lol. I'm sure HTC will put out a version 3.40.00 or whatever that has ackrite for all hardware versions. And then it will be easier on the devs
skydeaner said:
It is apparent the 3.30.2/3 has drastically ****ed battery life. There has been way too many posts about it to ignore it now.
It isn't HTC kernel 17 related like someone said earlier either. It goes deeper than that because I never run HTC kernels, not even for 5 minutes after installing a rom and I notice it very much. It appears that the current during idle isn't affected. And it isn't a rogue program PR anything keeping the CPU from idling. I dunno what it is. But it really is very noticeable.
I wish more dev's would realize it and make updated 3.29s with some of the new stuff built-in like the pnotification pulldown switch thing, and stuff like that.
Thanks azrael so far for not ignoring the situation. Lol. I'm sure HTC will put out a version 3.40.00 or whatever that has ackrite for all hardware versions. And then it will be easier on the devs
Click to expand...
Click to collapse
It seems only hardware version 0004 is mostly unaffected by the new frame software and I know the only difference is camera hardware but that may be it
Sent from my EVO at the edge of hell
Hardware: 003
Screen: not sure how to tell I am a newbie
stock kernel that comes with AVA V10
Right now I am home and not on the road working so my useage is lighter but I did go to bed last night with >50% life remaining and the phone had been off charger >15 hours
4-5 calls none were more than 5 min long
a little texting, couple emails (with polling every 30 min from 8-8), FB and Twitter updating at a regular interval (about every 30 min)
Bluetooth on for around 2 hrs, wifi on most of the day as I was at home using my home network so it was connected and not scanning.
Went to mall for about an hour and that has notoriously bad Sprint signal inside most places.
I ran the following:
hardware 002
Novatek screen
kernel: HTC 10, HTC 11, HTC 17, Kings #10 & #11 (both variants), Netarchy 4.1.9.1 & 4.2.1 beta (havs, no havs, bfs, cfs, smartass)
Some web browsing, facebook, texts, maybe 10-20 min of calls per day if that.
I'd get MAX 6-8 hours from fully charged to completely dead.
Went back to MIUI 11.19 and am consistently getting 15+ hours with moderate to heavy use.
If I try and run any ROM with the 3.30 file system, my battery totally sucks no matter which kernel I use.
Evo hardware version: 003
Screen Type: unknown (don't know how to tell)
3.30-ROMs tested: Ava V10, EViO 2
Kernels: various, in text
When I first switched to the first 3.30-based ROM, I noticed a big reduction in battery life. I tried another and ran into the same thing.
After one day on Ava V10, on a recommendation I tried the EViO 2 v1.6, along with the "netarchy-toastmod-4.2.1-bfs-bfq-nohavs-smartass-universal (No HAVS)" kernel, and with extremely light usage (1 short call, and few texts) after 19-hours I was showing an 89% charge. With this kernel the phone slept very well. The problem was that with that same kernel, even moderate usage sucked the battery very quickly.
So, based on things that I read I switched to the "netarchy-toastmod-4.2.1-bfs-bfq-havs-more-smartass-universal (More Aggressive Undervolting)". Using this combo, sitting on my desk with zero usage for 11-hours it was displaying 89% charge, so sleeping did not appear to be as efficient. However through the day, normal usage (moderate) seemed to provide a bit more time per charge. It did not appear to be a drastic difference.
On another recommendation, I then tried the netarchy-toastmod-4.1.9.1-cfs-NoHAVS-universal kernel. Overnight, no usage, after 9-hours I was again at 89% charge. Normal usage netted slightly worse time than the netarchy-toastmod-4.2.1-bfs-bfq-nohavs-smartass-universal (No HAVS) kernel provided.
Behavioral observation: The 4.2.1 No HAVS kernel produced slightly higher Quadrant scores than the 4.1.9.1 kernel did, but overall in normal operation, the phone was more sluggish and draggy on the 4.2.1 kernel, while being snappier and feeling faster overall using the 4.1.9.1 kernel.
Also, please note that the best battery time I ever got on any 3.30-based ROM pales in comparison to my experience earlier in the year with DC3.5 and an older Toastmod DC-compatible kernel. Once, after almost 21-hours off the charger, light usage throughout the night and at the very end of a 3+ hour phone call, I got the charge warning that I was at 15%. I don't know why I changed.
At this point I made an inquiry through a friend and was told that the difference between the 3.29-build and the 3.30-build was that the 3.30-build has a few small changes made to support hardware changes on version 004 Evo's only. I was also told that 3.30-build ROMs were not going to run well on 001-003 Evo's. I'm sure that is not absolute and they can be made to, but it may take some work.
Sorry for the novella, and I hope that it helps. Thank you for your time.
Hardware Version: 0003
Screen: EPSON
Kernel you are using: STOCK
battery life / Usage: MOD to HEAVY USAGE - OVER 25 HOURS on FIRST FULL CHARGE of battery!
NOTE: I also had AUTOKILLER set to STRICT during this entire time, and not to AGGRESSIVE.
Detailed post with pic showing my over 20 hour mark still in the GREEN:
HERE!!!
I'm now in the process of trying out Net-TM 4.2.1 CFS-HAVS-LESS AGG with V10.
bender1077 said:
Hardware Version: 0003
Screen: EPSON
Kernel you are using: STOCK
battery life / Usage: MOD to HEAVY USAGE - OVER 25 HOURS on FIRST FULL CHARGE of battery!
NOTE: I also had AUTOKILLER set to STRICT during this entire time, and not to AGGRESSIVE.
Detailed post with pic showing my over 20 hour mark still in the GREEN:
HERE!!!
I'm now in the process of trying out Net-TM 4.2.1 CFS-HAVS-LESS AGG with V10.
Click to expand...
Click to collapse
what was your "awake" time with this? This will be the tell.
When i ran ava 10 i got like 10 hours max. Alot of the 3.30 roms sucked my battery life. Fresh 3.3 rom gave me best battery life and i upgraded to his 3.4 and my bat sucked. Now im running airbourne rc4 and i think im getting the best battery I've ever had and its 3.30 based. It does have the sense launcher removed but all other sense is still there that could be the problem.
Novatek and 003
I decided to reload v10 and only restore a few essential apps and see where i was at. i did this, and had a full charge late last night.
This was with ALL settings defaulted to what is in v10 and no setcpu. The ONLY thing that i changed was the autokiller settings to "optimum"
It has now been 14.5 hours since i unplugged it (7 was me sleeping)
and "awake time" has only been 2.5 hours
It has been a pretty light day for usage - couple phone calls, mostly texts and emails and i am at 50%
This is MUCH better, but i really have not used my phone like i normally do. And this is with only a few apps installed.
frettfreak said:
what was your "awake" time with this? This will be the tell.
Click to expand...
Click to collapse
I think was a little over 5 hours. I'll have to remember to get a pic of that next time
bender1077 said:
I think was a little over 5 hours. I'll have to remember to get a pic of that next time
Click to expand...
Click to collapse
huh.. thats pretty good! lol... hmm..
a little off topic......how do you tell who made the screen on your EVO?
skydeaner said:
It is apparent the 3.30.2/3 has drastically ****ed battery life. There has been way too many posts about it to ignore it now.
It isn't HTC kernel 17 related like someone said earlier either. It goes deeper than that because I never run HTC kernels, not even for 5 minutes after installing a rom and I notice it very much. It appears that the current during idle isn't affected. And it isn't a rogue program PR anything keeping the CPU from idling. I dunno what it is. But it really is very noticeable.
I wish more dev's would realize it and make updated 3.29s with some of the new stuff built-in like the pnotification pulldown switch thing, and stuff like that.
Thanks azrael so far for not ignoring the situation. Lol. I'm sure HTC will put out a version 3.40.00 or whatever that has ackrite for all hardware versions. And then it will be easier on the devs
Click to expand...
Click to collapse
nYdGeo said:
...
At this point I made an inquiry through a friend and was told that the difference between the 3.29-build and the 3.30-build was that the 3.30-build has a few small changes made to support hardware changes on version 004 Evo's only. I was also told that 3.30-build ROMs were not going to run well on 001-003 Evo's. I'm sure that is not absolute and they can be made to, but it may take some work.
Sorry for the novella, and I hope that it helps. Thank you for your time.
Click to expand...
Click to collapse
So dont remember where I got this from (someone in another topic), but it completely confirms everything that we have been talking about...
NO 3.30 rom is made for hardware 001-003 period.. directly from sprint.
http://community.sprint.com/baw/com.../blog/2010/11/05/htc-evo-maintenance-releases
so the problem now is devs are either going to have to split their roms in to 2 branches (one for pre-004 hardware and one for 004 hardware) OR... sprint need to come out with a unified release. SO... hopefully devs will read this and make changes accordingly
I've had a very sudden and dramatic improvement in battery life and I thought that I'd post what seems to have worked for me.
I installed setCPU and set it for
768/254 on demand - main
245/245 performance screen off
368/368 performance - battery<41%
battery<101% 768/245 on demand
I installed Ultimate JuiceDefender and set it for extreme - blocking all connectivity except for a white-list
I decided that I could do a better job than the auto screen, so I installed Brightness level and I keep it generally at about 20% and then flick it up a bit if I need it.
I disabled auto rotation and now toggle the screen with a widget.
I've taken phone calls, recorded phone calls, checked email a few times, tweeted - very often using wifi which I operate using a toggle widget
I had the phone on charge all night switched off.
Disconnected it at 8.00 this morning and at 6.30 this evening, the JD widget tells me that there is still 12hrs and 28 mins of battery time left.
Considering the size of the screen and what this phone does. And considering the very poor battery life - 8hrs max I was getting before, I am far happier and the phone now becomes a practical item to have.
Whats your percentage battery left?
seems to be saying 72%
I also noticed that for the first time screen usage is less than running usage.
Screen consumption has always been the big factor on phone - and I see that is what people say on the forum, so I'm very pleased to have reduced it so well.
The Brightness level app allows a variable control whereas all the other screen controllers have seen allow you only to rotate through three or four preset brightness levels.
Brightness Level lets you do that with a widget but it also has a slide bar, which is what I was looking for
So basically you've downgraded the DHD to a level of a Nokia S40 device imo As this has been covered by many others in many other battery life related threads I'm just saying this short and simple. Just use the device as it is supposed to, enjoy the awesome features it provides at the full potential and don't get fixated on the battery life, it'll get you through the day no problem (doesn't include playing angry birds for three hours straight ) and just plug it in when you have the chance.
About battery, some tips, my battery life is around 2 days with normal usage of phone, only i dont use 3g only wi-fi:
Brightness - between 25% and 50%
When you on the internet and use native explorer for android go to "Menu-more-settings-enable plugins" and set it to "On demand"
Tupe *#*#4636*#*# - "Phone information" and set "Preffered network type" to "GSM Auto Prl"
Android Revolution HD 2.15 rom
lejars1 said:
I've had a very sudden and dramatic improvement in battery life and I thought that I'd post what seems to have worked for me.
I installed setCPU and set it for
768/254 on demand - main
245/245 performance screen off
368/368 performance - battery<41%
battery<101% 768/245 on demand
I installed Ultimate JuiceDefender and set it for extreme - blocking all connectivity except for a white-list
I decided that I could do a better job than the auto screen, so I installed Brightness level and I keep it generally at about 20% and then flick it up a bit if I need it.
I disabled auto rotation and now toggle the screen with a widget.
I've taken phone calls, recorded phone calls, checked email a few times, tweeted - very often using wifi which I operate using a toggle widget
I had the phone on charge all night switched off.
Disconnected it at 8.00 this morning and at 6.30 this evening, the JD widget tells me that there is still 12hrs and 28 mins of battery time left.
Considering the size of the screen and what this phone does. And considering the very poor battery life - 8hrs max I was getting before, I am far happier and the phone now becomes a practical item to have.
Click to expand...
Click to collapse
your on stock rom mate?
i can see that you can charge your phone while its turnd off..
i think on customized ROM like ARHD LD CORE cm7 and etc cannot charge their phone while its off because iT will BOOTup to recovery mode
Doesn't performance mode just keep the CPU clock on it's maximum? It would rather shorten the battery life than prolong it.
Why buy a smartphone and use it like a landline lol i hammer my phone and still get 10-14 hours out of it, thats fine for me, i only get 3hrs out of my laptop lol
Sent from my Desire HD using Tapatalk
Mate there is something eating your battery if u only get 8 hours battery life.
These adjustments you made are unnecessary if you find the culprit that is eating your battery, why get a phone like the dhd and run it on 20% brightness and lower the cpu to such a level.
Have you used spare parts to check your battery usage?
Im currently on 40% and my phone has been unplugged since 27 hours and I don't even have setcpu installed.
Maybe you should post details on your barret usage!
Swyped from my sexy galaxy tab
But I'm not compromising anything now. I'm completely happy with the way that the phone works for me now.
I'm actually operating the screen at 12% for most of the time - when I am not outside and it doesn't present any difficulty for me.
Obviously I would always like better battery life and I'll look for more ways to improve it.
Doesn't performance mode just keep the CPU clock on it's maximum? It would rather shorten the battery life than prolong it.
Click to expand...
Click to collapse
According to setCPU, if you set it to on demand, it will keep on scanning for required power level. Performance automatically goes to the max. Apparently on demand uses slightly more power so they advice to use performance when possible. So I set the same max/min figure and use a performance governor.
i would actually consider rooting the phone as an alternative, or getting a bigger battery. i have alot of issue with the battery life previously, but after switching rom, it actually help alot
Well it is rooted to enable JD and setcpu to work. But I haven't dared go further because I am still trying to understand the entire process - and also the way back!
I probably will eventually.
I've ordered a 1500 Mugen - and if that actually exists and if it is an improvement on the stock battery then that will advance things as well.
I'm very pleased with the improvement I have achieved so far because at least I'm able to take the thing off the tit for a full working day and use it as a real mobile phone!!
lampz said:
your on stock rom mate?
i can see that you can charge your phone while its turnd off..
i think on customized ROM like ARHD LD CORE cm7 and etc cannot charge their phone while its off because iT will BOOTup to recovery mode
Click to expand...
Click to collapse
this is only true if you're using CMW Recovery 3.x.x.x
redlinux said:
this is only true if you're using CMW Recovery 3.x.x.x
Click to expand...
Click to collapse
No, its on all versions of cwm, you can still charge your phone though, even in recovery
Sent from my Desire HD using Tapatalk
AndroHero said:
No, its on all versions of cwm, you can still charge your phone though, even in recovery
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Yup2x, it's true that we can charge it very well while in recovery mode. I was referring to the situation wherein the printer reboots to recovery as soon as you plug in the charger to your DHD. Some users have reported that and they are all using 3.x.x.x.
lejars1 said:
So I set the same max/min figure and use a performance governor.
Click to expand...
Click to collapse
As far as I've understood, you will always have max frequency when performance is applied. So there is no use setting min value really as it doesn't matter.
Sent from my %s using XDA Premium App, pardon my typos.
Vispe85 said:
So basically you've downgraded the DHD to a level of a Nokia S40 device imo As this has been covered by many others in many other battery life related threads I'm just saying this short and simple. Just use the device as it is supposed to, enjoy the awesome features it provides at the full potential and don't get fixated on the battery life, it'll get you through the day no problem (doesn't include playing angry birds for three hours straight ) and just plug it in when you have the chance.
Click to expand...
Click to collapse
By far the most excellent advice. I totally agree with you.
Yo dudes and dudettes.
Firstly, apologies if this is in the wrong section.
Would just like to share my wonderful experience with CheckRom + Siyah.
Ok, so what I have is an international SGS2 (white) with the STOCK 1650mah battery. I have pretty good signal in my city (Cape Town, South Africa). I was mostly on WiFi for the last ~40 hours.
I recently installed CheckRom RevoHD V6 with Siyah kernel.
I immediately installed (or rather updated) the CheckRom KitchenPro App and from there I installed ICS Domination theme along with all its various user interface tweaks. Then restored all my various apps from my previous backup I made while I was on stock Samsung ROM with Titanium Backup.
Then I installed SetCPU and ExTweak.
I followed this guide that explains kernel governors, i/o schedulers, cpu tweaks, etc.
I set my governors to conservative and tweaked it a bit, using the SIO I/O scheduler. I also followed various guides to under volt my CPU and my GPU and to optimize their frequencies at various levels of "work", also disable the 2nd core when I don't need it and A LOT of other tweaks I can't recall at this moment. My CPU runs between 200MHz and 1.2GHz. So I get the best of both worlds, saving battery when I can and still having that wonderful SGS2 speed when I need it.
Right so let me get to what I actually want to say.
Today I planned to study for my up coming exam on Monday, but I found my self stranded with out a PC for the rest of the day due to unforeseen happenings. Luckily I still had WiFi and my SGS 2 with me. (Note that I don't use physical books to study from, I study from e-books, 80% of my material is digital.) Anyway, I then decided I was going to see how many hours I can get from this setup without charging it (and at the same time give it a nice full charge/dis charge cycle). I unplugged it from charge Friday evening before I went to bed it was at 100% then.
So I used my phone to view my PDF books, my Evernote notes, voice notes, do all my searches online and watch some tutorials here and there. The following apps where open pretty much all the time:
Adobe Reader (for my e-book text book)
Evernote (voice notes, picture notes, text notes)
Dolphin HD Browser (for my uni's interactive learning portal)
Opera Mini (for simple static sites)
My phone's screen was on all the time. I used jKay deluxe to set the time out to 30mins and to disable my security for this time.
I am happy to say that i got 7 hours 20+ mins screen-on time and this was with the STOCK 1650mah battery doing fairly heavy work. (note: the screen had to display quite a lot of white pixels at a brightness of roughly 40% and as you can see that was the most battery taxing component as expected though)
here is a screen shot I took:
Also here is a screen shot of the "About Phone" section:
and here is my current PDA/Phone/CSA:
I am very happy with this kernel/ROM combo.
Anybody else experience such awesome battery performance?
Credit goes to:
Gokhan - Siyah Kernel and ExTweaks
Leomar/Gadget - CheckRom RevoHD V6
droidphile - for this awesome guide
Vertumus - ICS Domination Theme
Yeah, this is quite amazing. Never passed the 5 hours of screen on using my ics Rom. I think my battery is slowly dying..
Envoyé depuis mon GT-I9100 avec Tapatalk
Pretty insane battery life with tweaks, I never get passed 4 hours on screen time, which is a little sad.
I followed this guide that explains kernel governors, i/o schedulers, cpu tweaks, etc.
I set my governors to conservative and tweaked it a bit, using the SIO I/O scheduler. I also followed various guides to under volt my CPU and my GPU and to optimize their frequencies at various levels of "work", also disable the 2nd core when I don't need it and A LOT of other tweaks I can't recall at this moment. My CPU runs between 200MHz and 1.2GHz. So I get the best of both worlds, saving battery when I can and still having that wonderful SGS2 speed when I need it.
Click to expand...
Click to collapse
For this to actually help us, find out which tweaks you applied please
@OP, along with Gokhan and Leomar/Gadget, can i also take a small credit for that 'massive' screen-on time?
WTF i never get more than 2.5hrs of on screen time
+ 1 please can you post your exact values
anshmiester78900 said:
WTF i never get more than 2.5hrs of on screen time
Click to expand...
Click to collapse
same here... only once got 3+ hours :/ no matter what i do... uv,dimm brightness,....
thez3ro said:
same here... only once got 3+ hours :/ no matter what i do... uv,dimm brightness,....
Click to expand...
Click to collapse
Yup for me it doest matter i the brightness is on 50% or 20% i wont get more than 2.5 hrs of on screen time
Nice results. On most days I get only around 4-5 hours screen time, because Im usually out of the house and on 3G. That consumes more battery then on a wifi connection
When Im at home all day and am connected to wifi, I get even more screen time. It really depens on how you use your phone (btw, a screenshot of the battery usage screen would have been nice. You know with how much % each app consumed). Playing a few flash videos in Stock/Dolphin browser really consumes your battery... anyway. Browsing normallhy, whatsapp, facebook etc on a wifi connection all day and I can get around 5-7hours of screen time.
I have the 2000mAh battery though, so your results are insane!
Edit: it just hit me that I know the reason for your crazy results. If Im correct you viewed a lot of documents and notes. This means the screen was on a lot of the time with you just reading (based on the 30min screen time out). Your processor probably stayed at 200MHz most of the time, because viewing those documents (and leaving it on a page for 15 min or something, not scrolling or anything) is a very "light" process. So that's where so much screen time came from Imagine if you had mostly black on the screen, 9h screen time xD
But to all the people going crazy that they want 7h20m of screen time as well: realise how he used the phne. If you do the same light tasks you will also get a lot more screen time.
Edit: not saying it's still not crazy lol...with a stock battery, damn
Sorry to say this but we want more solid proof in the form of that screenshot of battery graph and the settings u have applied.
7.5 hrs and that too with Dolphin hd and opera browser and Adobe reader!!!!
OMG!!
Sent from my Galaxy Tab using TT
With stock battery and standard browsing i don't believe it's possible to achieve such screen time on a stock battery no matter how much you tweak. Maybe if i read white text on black screen and use screen filter to reduce brightness even more.
Unfortunately I did not take a screen shot of the battery page and graph, I admit that was a stupid mistake of me. I will post my exact settings soon when I have time to go through each and every one of them, writing tomorrow so still studying. I was amazed at this result (hence the post) so I will try and remake these results and take a lot of screenshots.
Not trying to hate or anything but he could have easily just put a black wallpaper for 7 hours and 20 mins and just simply leave it on and go away for a few hours and BAM! Great results without touching your phone at all!!
0,0
That's very impressive!
I myself am happy with 4hours of screen on. Anyway, looking forward to seeing your setup.
Sent from my GT-I9100 using Tapatalk
Quite a few people have hit 7 hours screen on time using hyperdroid, someone else got 8 hours as well, mainly web browsing and watching videos so I hardly doubt he's lying despite the yells for graphs, even IF he is lying its not impossible
yeah watching movie is possible because it's predominantly dark but web browsing cannot get past 5 hours with readable brightness.
Also post a screenshot of CPU Spy...
same here, on a good day only barely get past 4hrs. whats your tweaks like on setcpu?
damn mate awesome numbers, im already a user of CheckRom but didn't try with different kerneles so i shall download siyah and tweak couple things
cheers
So since I had my nexus 4, I had to complain about its terrible battery life.
I would never get more than 3h of screen on time, despite my best efforts in conserving battery. Even with the phone in flight mode and on Wifi, I could not cross 3h give or take a few minutes. I even tried disabling location, google now, sync and everything else.
It was deep-sleeping nice, while the screen was off, standby time was awesome for me. If I turned it on though, it started to burn through battery insanely quick. So I started monitoring the frequency states with battery spy, and noticed that as if there was a little load, it spiked to 1026MHz and then stayed there for about three seconds every time before falling back to 386 MHz. So I tried setting the max cpufreq to 916Mhz with CPU tuner, and was astonished to find out, that immediately after the load was done, it went back to the lowest frequency. Like it should be, not hanging for multiple seconds on the high step.
Also, If I start CPU tuner, the min freq is always shown as 1026MHz. So I changed min to 386 and max to 916. Afterwards, this stays until I swipe cpu tuner away from the recent apps list. If I start it again, the settings revert. Strange...
With my cpu limited to 916MHz, I get about 5h and 50 min of screen on time without any other measures. Location on, Wifi on, Google now and sync all active. If I just go one step higher and set my max frequency to 1026, the old behavior starts again, and screen time drops to 3h because it seems to be stuck on that freq. Therefore I would like everybody who also has bad screen time to try that out and report back.
I don't really understand why it would take so long to drop back from the 1GHz step, and drop back immediately from the 0,9GHz step?
Of course, this is with normal surfing via chrome, or using normal apps that are not that much CPU intensive. Also, you hardly notice the performance limitation without playing games. There probably is an easy way to fix this?
Feedback would be appreciated. Maybe I see this wrong...
Thanks
tl;dr : if screen on, for me only 1026mhz is used, if max freq is set to anything lower, the phone spends most of the time at the lowest step 386mhz, greatly increasing screen time for me.
Flash Franco Kernel and buy the app and you'll be set.
Sent from my Nexus 4 using xda app-developers app
NoLunchBox_ said:
Flash Franco Kernel and buy the app and you'll be set.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Maybe, but I really first wanted to examine out of the box behavior
This is caused by qualcoms Mpdecision which ramps up the cpu to 1ghz on screen on and touches. All in the name of speed. It's basically a hot plugging technique such that smoothness is guaranteed under loaded gui transitions and scrolling. Before this you would have to wait for the cpu to be loaded for it to ramp up speed. Now the OS can demand speed.
You can see in Franco kernel he replaced Mpdecision with an open source alternative and swapped the lowest cpu speed to 368mhz. Then added a load step of 768mhz (for 60% loads). This actually added a bit of lag but should be better in the battery department. Some more tweaking to be done though.
Qualcoms thermald is what is causing thermal throttling.
Edit: this could be wrong. But I think I'm in the general area of what's going on...
Sent from my Nexus 4 using xda premium
This does sound logical, but why the hell waste nearly half of the possible screen time on "perfect smoothness" when even if limited to 0,9ghz everything runs pretty amazing... I will look into francos kernel, even though I dont like to buy an app to tune it,
ArRaY92 said:
This does sound logical, but why the hell waste nearly half of the possible screen time on "perfect smoothness" when even if limited to 0,9ghz everything runs pretty amazing... I will look into francos kernel, even though I dont like to buy an app to tune it,
Click to expand...
Click to collapse
You don't have to buy an app, everything can be set through scripts. The app just automates the process, allows you to back up kernels, download the latest nightly and milestone (when one becomes available). It's really worth the investment, plus you're helping out a great Dev who has shared his awesome work with us for a long time.
Sent from my Nexus 4 using Tapatalk 2
I like my phone to sleep. I bumped it down to 384!
No need to keep it @ the 1.026, it will pretty much kill battery! Makes no sense to me.
Sent from my Nexus 4 using Tapatalk 2
You can set the max to 384 mhz.. and still everything is smooth
Can I use SetCPU or is that app defunt now? And to change my CPU speeds can that be done on a phone that's simply rooted or do I need a custom kernel?
EDIT: I downloaded CPU tuner, but I'm not sure if it's working or not. Does it work w/ stock kernel or no?
Faux's Intellidemand fixes pretty much what you're describing. Since mpdecision is not used instead of fauxs alternative.
Sent from my Nexus 4
What is max frequency by default?
Have to say firstly, that the perfect smoothness of this phone is what has sold me on it as the camera is well below average, it has some bugs and the output quality and volume of the audio is shocking, but it is the single smoothest phone out there.
Get rid of what I came to know as Touchboost (feature brought in in jelly bean to introduce the lag free experience of project butter I imagine) from my Sgs3 days, and the phone becomes as laggy as every other android phone out there.
Secondly, I get around 3.5 hours screen on time, without messing about, wifi on constant, depending on whether i'm on the net or not, I can get more.
I find AOKP perfect as its super fast and battery is excellent.
Franko kernel works, but the phone then feels choppy. Setting the cores to 1ghz makes the phone laggy also.
All I can say is, get lots of chargers, I have two at home, two at work, one in the car, one at the other halfs, and it's trickle charging when and if I can and I never worry about battery anyway. I find it wastes far too much life.
Good luck.
biffsmash said:
Have to say firstly, that the perfect smoothness of this phone is what has sold me on it as the camera is well below average, it has some bugs and the output quality and volume of the audio is shocking, but it is the single smoothest phone out there.
Get rid of what I came to know as Touchboost (feature brought in in jelly bean to introduce the lag free experience of project butter I imagine) from my Sgs3 days, and the phone becomes as laggy as every other android phone out there.
Secondly, I get around 3.5 hours screen on time, without messing about, wifi on constant, depending on whether i'm on the net or not, I can get more.
I find AOKP perfect as its super fast and battery is excellent.
Franko kernel works, but the phone then feels choppy. Setting the cores to 1ghz makes the phone laggy also.
All I can say is, get lots of chargers, I have two at home, two at work, one in the car, one at the other halfs, and it's trickle charging when and if I can and I never worry about battery anyway. I find it wastes far too much life.
Good luck.
Click to expand...
Click to collapse
Thank you for not contributing to this thread with that useless comment. The rest of us may not want to charge the phone 1500 times a day (or are even able to), and are looking for ways to help battery discharge go slower while using the phone. If you're fine with charging your phone nonstop, then what are you doing in this thread? Everyone knows you can buy many chargers, that's not a solution.
ksc6000 said:
Thank you for not contributing to this thread with that useless comment. The rest of us may not want to charge the phone 1500 times a day (or are even able to), and are looking for ways to help battery discharge go slower while using the phone. If you're fine with charging your phone nonstop, then what are you doing in this thread? Everyone knows you can buy many chargers, that's not a solution.
Click to expand...
Click to collapse
Welcome to Project Butter. If you want to do something different than Google's goals for UI smoothness and responsiveness, which is what everyone has been complaining about in Android vs iOS, then you'll have to go the custom ROM/kernel route. Thankfully that is easily available to you on this hardware and software platform. Me? I like the N4 just fine the way it is stock.
[hfm] said:
Welcome to Project Butter. If you want to do something different than Google's goals for UI smoothness and responsiveness, which is what everyone has been complaining about in Android vs iOS, then you'll have to go the custom ROM/kernel route. Thankfully that is easily available to you on this hardware and software platform. Me? I like the N4 just fine the way it is stock.
Click to expand...
Click to collapse
Dude, this has nothing to do with googles project, but instead with Qualcomms responsivness "fix". Please read the answer to my inital post, and you will understand. Also, the phone does in no way feel choppy if you restict it to .9ghz. Except if you load it so much, that it cant cope with this max frequency. But then again, this is not the issue, but the issue is, that 1026 stays active for to long, so that it burns through your battery. There would be only a small change needed to change this behavior, and "possibly" loosing about a fraction of a second of responsivness, that most of the time you wouldnt even notice... Everybody who tells me he is happy with barely 3h of screen time or even less is just the android equivalent of an isheep, because this is in no way acceptable.
ArRaY92 said:
Dude, this has nothing to do with googles project, but instead with Qualcomms responsivness "fix". Please read the answer to my inital post, and you will understand. Also, the phone does in no way feel choppy if you restict it to .9ghz. Except if you load it so much, that it cant cope with this max frequency. But then again, this is not the issue, but the issue is, that 1026 stays active for to long, so that it burns through your battery. There would be only a small change needed to change this behavior, and "possibly" loosing about a fraction of a second of responsivness, that most of the time you wouldnt even notice... Everybody who tells me he is happy with barely 3h of screen time or even less is just the android equivalent of an isheep, because this is in no way acceptable.
Click to expand...
Click to collapse
I'm getting around 4-5. Auto brightness, 1 Gmail push, 1 touchdown push, Google now on, HD widgets weather, greader pro syncing, falcon pro syncing, all location services on (I like the monthly reports). Wi-Fi when I can.
[hfm] said:
I'm getting around 4-5. Auto brightness, 1 Gmail push, 1 touchdown push, Google now on, HD widgets weather, greader pro syncing, falcon pro syncing, all location services on (I like the monthly reports). Wi-Fi when I can.
Click to expand...
Click to collapse
What kernel are u using? Im using franco kernel + latest CM 10.1 nightly.
My min CPU speed is 1 GHz and in still getting 4 hours on screen time though. I don't think setting my min at 384 MHz even made much difference in my battery, will try it again soon.
Sent from my Nexus 4 using xda premium
droyd4life said:
What kernel are u using? Im using franco kernel + latest CM 10.1 nightly.
Click to expand...
Click to collapse
Stock never rooted bootloader still locked.
If you are getting bad battery... simply flash a custom kernel. You get to keep your stock ROM or whatever but you will get substantial benefits. I prefer Trinity Kernel. Only the second or third update on this kernel and now the phone has made huge gains in battery life. Like hfm, I good on screen time... usually 5-5.5. I have auto brightness on, mobile on 100% of the time, and all Google services synced including books, gmail, currents, google now, etc etc. I have locations on, gps on... everything. Sometimes I turn off NFC because I rarely am somewhere where I can use those cool RFID card scanners. What sucks battery is probably a problem in Android 4.2. The phone does not sleep as much as it should. Go ahead and turn all your sync stuff off and keep the screen on static and let the battery die at stock clock speeds. Probably will get at least 5 hours with auto-brightness on. My phone probably sleeps 60% of the time now according to CPU spy when it sits idle in my car for my 8-10 hour work day. I usually get to the car with a bunch of emails, a text or two waiting for me, and the phone has only been asleep the aforementioned 60% and around 90-91% battery life. On a new phone, starting from full charge, this should be at least 95%. My N10 that doesn't have mobile data, only loses about 1% overnight. Apples to oranges but still. I'm convinced that stock voltages on this device are too high, and that Qualcomm did not give Google the latest drivers... maybe because it's not releasable to AOSP as of yet. I really don't know, but it's gotta be something buggy. This SoC is capable of doing better... and it does in the Optimus G and even with sense, 1080p screen, and a 100mah smaller battery the HTC Droid DNA/Butterfly gets 3.5-4 hours stock screen time. None of the other phones using the S4 Pro are running 4.2. I'm hoping either Qualcomm pulls a Samsung and releases some updated drivers/firmware that Google can incorporate or that Google fixes whatever bugs they may have not worked out. In the next calendar year other phones will be out that use the S4 Pro and 4.2 and I doubt Qualcomm wants to lose the luster it earned with the regular S4 Kraits performance/efficiency. When 4.2 comes to other devices we will probably know whether or not Google is to blame for this or that the Nexus 4 is just a poor performer.
Hey guys. I'm wondering how much better the battery has gotten since the first week y'all got it, to now.
For me I'm satisfied with the battery and I've had it for 4 days. I get about 2-2.5 hours screen on time with fairly heavy internet usage, texting, etc.
Beerad875 said:
Hey guys. I'm wondering how much better the battery has gotten since the first week y'all got it, to now.
For me I'm satisfied with the battery and I've had it for 4 days. I get about 2-2.5 hours screen on time with fairly heavy internet usage, texting, etc.
Click to expand...
Click to collapse
Are you taking any measures to save battery life, like certain screen brightness, disabling of certain features or radios, undervolting or CPU/Governor changes, etc?
First thing I installed on mine ( haven't had mine a week yet ) was Battery Monitor Widger Pro, since I've used that on my past devices when I was testing out generic batteries (speaking of which the 8$ ebay 3800mAh on my Desire-Z is still kicking strong after a year).
Problem with estimates, is that they are basically just that, and the difference between browsing on mobile vs browsing on wifi or mix, and your reception quality can also have an impact on your battery. (in the end, your screen is the biggest impact).
Mine lately, say if I had it charged at 100% , it'll take about 2 hours on mobile to get to 91%, with the screen being on about 25%-35% of that time (auto-brightness), receive/send text, take out of pocket to check email or facebook notifications, and so forth. Which would normally show as screen 30%, Google services 13%, Wifi 9% (when I had it on between house and destination). Phone idle 8%, Android OS 7% etc.
The widget I mentioned earlier can basically monitor your draw from time to time and if the screen was off or on and such during those times (default interval on it if using a widget is around 10 minutes on the logging, shorter may actually impact the battery it's monitoring oddly enough)
PS: The other day when I actually drained it down to 0% it took about 5-6 hours
Beerad875 said:
Hey guys. I'm wondering how much better the battery has gotten since the first week y'all got it, to now.
For me I'm satisfied with the battery and I've had it for 4 days. I get about 2-2.5 hours screen on time with fairly heavy internet usage, texting, etc.
Click to expand...
Click to collapse
I had about 3-4.5 hours of screen time other moderate to heavy usage on my first week as I was testing it's battery life. As that I just used my phone under light to moderate usage. My brightness level is always at it's lowest but when I'm outside I turn it up to about 50%. I rarely play games on my device. I read a lot on my phone. I use my phone to record lectures in class and do a bit of homework on it. 7 months later and I'm pretty much doing the same. I have a custom kernel installed and I'm really confidence about it. I carry a external battery pack with me all the time but I hardly use. After having a custom kernel for the past 7 months I can say battery life has been relativity the same screen time wise. I learned how to manage my apps so they won't prevent my phone from sleeping to save power. Your mileage will vary depending on what you're doing on your phone and how you manage your device. Cell service is crucial to the phone. If you're in area with little to no service your device will use up more power to stay connected. This is when "Airplane mode" comes in handy.
kbeezie said:
Are you taking any measures to save battery life, like certain screen brightness, disabling of certain features or radios, undervolting or CPU/Governor changes, etc?
First thing I installed on mine ( haven't had mine a week yet ) was Battery Monitor Widger Pro, since I've used that on my past devices when I was testing out generic batteries (speaking of which the 8$ ebay 3800mAh on my Desire-Z is still kicking strong after a year).
Problem with estimates, is that they are basically just that, and the difference between browsing on mobile vs browsing on wifi or mix, and your reception quality can also have an impact on your battery. (in the end, your screen is the biggest impact).
Mine lately, say if I had it charged at 100% , it'll take about 2 hours on mobile to get to 91%, with the screen being on about 25%-35% of that time (auto-brightness), receive/send text, take out of pocket to check email or facebook notifications, and so forth. Which would normally show as screen 30%, Google services 13%, Wifi 9% (when I had it on between house and destination). Phone idle 8%, Android OS 7% etc.
The widget I mentioned earlier can basically monitor your draw from time to time and if the screen was off or on and such during those times (default interval on it if using a widget is around 10 minutes on the logging, shorter may actually impact the battery it's monitoring oddly enough)
PS: The other day when I actually drained it down to 0% it took about 5-6 hours
Click to expand...
Click to collapse
Nah. All stock, not rooted yet, auto-brightness, No auto sync. I don't get very good service at my work and I was about 28% without service during the time I was there. I would get on facebook and message people on facebook and text, surf the internet etc because it was slow. I had maybe 2 hours screen time and 8% battery life when I left work. It was probably 9 hours off the charger. Here. I'll post a screen shot after this post (On my computer right now)
Sent from my Nexus 4 using xda premium
Beerad875 said:
Nah. All stock, not rooted yet, auto-brightness, No auto sync. I don't get very good service at my work and I was about 28% without service during the time I was there. I would get on facebook and message people on facebook and text, surf the internet etc because it was slow. I had maybe 2 hours screen time and 8% battery life when I left work. It was probably 9 hours off the charger. Here. I'll post a screen shot after this post (On my computer right now)
Click to expand...
Click to collapse
One of the benefits to custom roms (though 'stock' on a nexus is well AOSP so...) is the ability to tweak that stuff to finer details, top it off with a custom kernel and can optimize even further. Just a matter of how far you want to take it.
I have a history of immediately rooting anything I get my hands on, so I tend to have very little experience with stock. But the Nexus devices are probably the only ones I could survive having stock (but rooted) as opposed to say touchWhiz on samsung.
I can say that this phone charges FAAAAAAST.
kbeezie said:
One of the benefits to custom roms (though 'stock' on a nexus is well AOSP so...) is the ability to tweak that stuff to finer details, top it off with a custom kernel and can optimize even further. Just a matter of how far you want to take it.
I have a history of immediately rooting anything I get my hands on, so I tend to have very little experience with stock. But the Nexus devices are probably the only ones I could survive having stock (but rooted) as opposed to say touchWhiz on samsung.
Click to expand...
Click to collapse
Coming from the the backflip's motoblur to the Captivate's touchwiz then onto One X's sense to AOSP.. I'm going to stay android purist from now on. I'm in love with AOSP
Beerad875 said:
Coming from the the backflip's motoblur to the Captivate's touchwiz then onto One X's sense to AOSP.. I'm going to stay android purist from now on. I'm in love with AOSP
Click to expand...
Click to collapse
At least all the available kernels work just fine with AOSP. (Francos seems to be pretty popular for battery, I prefer bricked though on both my N4 and N7).
kbeezie said:
At least all the available kernels work just fine with AOSP. (Francos seems to be pretty popular for battery, I prefer bricked though on both my N4 and N7).
Click to expand...
Click to collapse
Why do you prefer them?
So with battery monitor widget pro do I just let it run and collect data?
kbeezie said:
At least all the available kernels work just fine with AOSP. (Francos seems to be pretty popular for battery, I prefer bricked though on both my N4 and N7).
Click to expand...
Click to collapse
Guess tonight I'm going to work on getting it drained down to 0% just remembered it was my N7 that I did a full cycle on with monitoring, I haven't done so yet to the N4.
PS: I usually do a dual-graph (mV and mA), but in this screenshot you can see generally speaking with my current configuration, I tend to drain around 200-300 mA screen on, and around -20-50 with it off.
PS#2 : It only went up to the -400 or so mA on the top right because I had changed my screen brightness to about half instead of autobrightness.
Beerad875 said:
Why do you prefer them?
Click to expand...
Click to collapse
Additional options. Take for example the Bricked kernel for the N4 in my signature. This is it's feature list, it's not aimed for hardcore overclockers or such but gives you some options (The one for the Nexus 7 is a bit more configurable during the installation).
* Based upon Googles msm 3.4 source
* Various other fixes (look @ github)
* Compiled with gcc4.7.2 toolchain (linaro 09.12)
* -O3 optimized
* Snapdragon S4 & CortexA15 optimizations
* Sweep2wake
* 192Mhz min clock
* replaced qcoms hotplug binary with msm_mpdecision (IN-KERNEL, better battery life + performance)
* Extensive sysfs interface for mpdecision with all the tuneables you want (/sys/kernel/msm_mpdecision/)
* replaced the thermald binary with my IN-KERNEL solution. (/sys/kernel/msm_thermal/)
* export krait version to: /sys/kernel/debug/krait_variant
* modified ondemand governor
* Allow OC up to 1,83Ghz, faux123 (from a thermal point of view that is now SAFE)
* Fixed min cpufreq resets
* Undervolting (faux123)
* Default clocks: 384min & 1512max
Click to expand...
Click to collapse
Sweep2Wake is kind of nice too, you just slide accross the screen to turn it on without having to touch the power button (And yes your phone is still asleep doing this, it just works off interupts.)
other kernels can be a bit more involved, such as being aimed towards overclocking the CPU or GPU, or adding in extra features not normally found in stock, and so forth. I've had the best luck with Bricked and Francos'
Beerad875 said:
So with battery monitor widget pro do I just let it run and collect data?
Click to expand...
Click to collapse
Yep, if you have a widget on the home screen (I usually do 2x1 size) it'll collect every 10 mins by default. If you don't use a widget you'd have to check a box in preference to monitor without widget or it won't log times (note for example the missing 'blocks' from my history log).
---------- Post added at 11:29 PM ---------- Previous post was at 11:22 PM ----------
Speaking of battery, anyone ever gotten more than say 800mA charge on their N4? Cuz even on my old Desire-Z if I plugged it into a 2.1A charger it would actually charge up around 1300-1500mA, but with the Nexus 4 seems that even on a 2.1A port it rarely charges more than 500-600mA.
It'll probably become more accurate once I actually drain it down to 0% and have the widget record it's history from 0% to 100% since it bases a lot of it's mA estimates off that (ie: off the rate of decrease of the battery's mv since batteries typically have a certain voltage once they hit near 0% and when they're at 100%, comebine that with what it knows the battery's mA to be it can determine the charge/discharge based off that).
kbeezie said:
[/COLOR]Speaking of battery, anyone ever gotten more than say 800mA charge on their N4? Cuz even on my old Desire-Z if I plugged it into a 2.1A charger it would actually charge up around 1300-1500mA, but with the Nexus 4 seems that even on a 2.1A port it rarely charges more than 500-600mA.
It'll probably become more accurate once I actually drain it down to 0% and have the widget record it's history from 0% to 100% since it bases a lot of it's mA estimates off that (ie: off the rate of decrease of the battery's mv since batteries typically have a certain voltage once they hit near 0% and when they're at 100%, comebine that with what it knows the battery's mA to be it can determine the charge/discharge based off that).
Click to expand...
Click to collapse
I can get back to you when I figure this app out more and start using it.
What'd you say your screen on time usually was?
Beerad875 said:
I can get back to you when I figure this app out more and start using it.
What'd you say your screen on time usually was?
Click to expand...
Click to collapse
Just in the last 2 hours or so, probably 30-45 minutes. I was in the car so it wasn't coming on all that often. Since I actually have the widget on my home screen now, I'll just post an update again probably in the morning as I play with the phone some more, maybe play a game or two (I'll set a Market in the battery history before I start and after I end it).
Far as figuring it out, it's pretty easy since most of it is already set up by default once you open it. You can basically just pop a 2x1 widget on the home screen and just leave it.
My battery life has improved drastically by just sticking with one setup and letting the phone get used to it. That means keep the same rom and kernel so the phone settles in and gets used to it. After a few cycles your usage should increase.
I recommend straight CM 10.1 with Franco kernel.
Also use 2g instead of HSPA+ when you're not using data to save power.
If you're using touch control, don't, it drains more power for sure.
Undervolting helps too.
Sent from my Nexus 4 using xda app-developers app
nyyankees1237 said:
If you're using touch control, don't, it drains more power for sure.
Click to expand...
Click to collapse
Can you clarify on this, other than the power/volume there's not much else to actually control the phone with.
kbeezie said:
Can you clarify on this, other than the power/volume there's not much else to actually control the phone with.
Click to expand...
Click to collapse
The app 'touch control' , many nexus 4 owners use it to wake and lock the phone using touch gestures in place of the traditional power button. In my usage it definitely drains the battery quicker.
Sent from my GT-N5110 using xda app-developers app
nyyankees1237 said:
The app 'touch control' , many nexus 4 owners use it to wake and lock the phone using touch gestures in place of the traditional power button. In my usage it definitely drains the battery quicker.
Sent from my GT-N5110 using xda app-developers app
Click to expand...
Click to collapse
Oh you mean like Sweep2Wake in the Bricked Kernel I'm using, except that doesn't use any battery cuz that's in the kernel using interrupts rather than an app that would keep the phone awake. (course that's all it does too, wake, nothing more sophisticated than that).
But yea I didn't know about that app.
kbeezie said:
Just in the last 2 hours or so, probably 30-45 minutes. I was in the car so it wasn't coming on all that often. Since I actually have the widget on my home screen now, I'll just post an update again probably in the morning as I play with the phone some more, maybe play a game or two (I'll set a Market in the battery history before I start and after I end it).
Far as figuring it out, it's pretty easy since most of it is already set up by default once you open it. You can basically just pop a 2x1 widget on the home screen and just leave it.
Click to expand...
Click to collapse
So yeah. You should drain it then report with some screenshots.
It's at 44% right now
Sent from my Nexus 4 using XDA Premium HD app