Using setcpu after jb install - HTC One X

I've been running ahrd 12 for a day now, it's pretty impressive compared to ahrd 9.7.2 or stock.
My question relates to having to run apps like setcpu and juicy defender.
Are they still required , or will they just stuff up the better cpu and memory management that jb already has.
Thanks
Jason
Sent from my HTC One X using xda app-developers app
Sent from my HTC One X using xda app-developers app

Good question, I'd like to know this to.
I'm still on ARHD 11.1 (also JB) and loving it. But this phone is very power hungry so I'm trying as much as I can to keep the battery drainage as low as possible whilst retaining a very fast and responsive phone.
Currently I'm using SetCPU to reduce the CPU speed to 1GHz (interactive) for normal use, 860MHz (on demand) when the battery is below 25%.
CPU is limited to 640MHz (on demand) when sceen is off and may run at 1,2GHz (interactive) when charging.
As the screen is also a big battery hog I'm using Lux to change the screen brightness and I find the normal brightness way to bright.

Related

SetCPU

Hi all,
I've set some profiles in SetCPU but haven't noticed too much in battery life savings. I was wondering what others who are using CM 6.1 have been doing/would recommend. Should I get rid of the profiles and just have it set to on demand? Do I really need it at all with CM?
Many thanks!
Sent from my HTC Vision using XDA App
geckobear said:
Hi all,
I've set some profiles in SetCPU but haven't noticed too much in battery life savings. I was wondering what others who are using CM 6.1 have been doing/would recommend. Should I get rid of the profiles and just have it set to on demand? Do I really need it at all with CM?
Many thanks!
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
How high are you overclocking?
What's your usage?
What's are your profiles?
Overclocking to 1401 on demand
I use power amp with scrobbing to last fm for probably an hour or two when not charging, while playing games that aren't to elaborate (boring stuff like sudoko) during my commute to/from work, which is probably my heaviest usage. I also do the same music set up while at work but I'm plugged in most of the time for that and volume is way down. Calls range from 30 min to an hour a day. Some intermittent web and video streaming while at home and on wifi. Typically only on wifi when at home, only when I need heavy data. Data sync is turned off when I'm not charging unless I want to sync.
I have profiles of 368/245 while sleeping, 75 priority; 738/245 when temp is 40.5 C, 60 Priority, 1401/245 when plugged and fully charged, 50; 368/245 when battery less than 10, 60; 806/245 when battery less than 40, 50 priority.
I'm thinking the fully charged one is probably redundant. Should I raise the priority on some of them?
xomikronx said:
How high are you overclocking?
What's your usage?
What's are your profiles?
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App
I always set temp as the highest priority however i OC a lot higher then you. What oc kernel are you useing? This makes a huge difference some have a lot more steps which allow better power use. Pershoot is the most efficient imo right now.
Sent from my HTC Vision using XDA App
I think I'm just using the cyogen mod kernel...but I'm new at this so I am a little clueless on that part. I did set higher priority on the temp and the screen off, got rid of the charging profile. I'm at 13% battery after about 15 hours, which isn't horrible but not the 30 hours some folks have been posting.
Sent from my HTC Vision using XDA App
had to dig back to find a good thread to post this on....
so I'm really leaning toward deciding that setcpu profiles do more harm than good in terms of battery. I had profiles set for temp, screen off, charging, battery below 30, and battery below 10. its pretty clear to me now that it wasn't helping my battery. and the only time I even had it overclocked was while charging.
next I'm going to just enable only a screen off profile, and see if having setcpu monitor for less profiles makes a difference. i'm not going to overclock at all. we'll see what happens.
btw I've had a rooted android phone since the G1 so its not like I don't have experience with setcpu. seems that setcpu affects different phones in different ways. so I'm still figuring out how it is on the G2.
anyone have any thoughts on this?
The screen off profile does not work.
Just use the phone out of the box and charge when its empty
snudel said:
The screen off profile does not work.
Just use the phone out of the box and charge when its empty
Click to expand...
Click to collapse
really? I hadn't heard that. is this confirmed?
though, it never seemed to make all that much sense anyway, as I wouldn'y think there would be any reason for the cpu not to remain at a low freq with the screen off
The screen off profile works for me. I just set to "ondemand". Lately I've been using "cpu tuner" instead and have noticed better battery life then with set cpu. Plus with cpu tuner you get more profile options.
Sent from my CyanogenMod powered G2.
To be honest, not sure if its the case for you but profiles was the cause of my battery life drain. I took off all profiles and only kept screen off. Even since I did that I get about 24 hours + of battery.
[G2/HTC Vision]
luis86dr said:
To be honest, not sure if its the case for you but profiles was the cause of my battery life drain. I took off all profiles and only kept screen off. Even since I did that I get about 24 hours + of battery.
[G2/HTC Vision]
Click to expand...
Click to collapse
I had a similar experience. The more profiles I had enabled, the faster my battery would drain.
I am using the same setup now and have great battery life. Even with heavy usage I can make it through the entire day without needing a charge.
Running On Demand 1209/245 and screen off 245/245.
Haha this was an old thread. I'm now on CM7 nightlies and would say that in my experience I've had the best battery life running no profiles whatsoever in setcpu. I only overclock to 1017 and it's been pretty snappy still. My experience in going higher than this on CM7 has lead to issues with wake, temperature and battery drain. I personally Have no need for more than 1017.
Sent from my HTC Vision using XDA App
agreed. this setcpu stuff did not help at my device. nor did it work reliant.
i am managing 1day with heavy use and a full weekend with moderate use without any "tuning".
that is enough for me.
I used setcpu for awhile, but I have been much happier using cpu tuner and "power control".
My battery life is increased by 12 to 24hrs. The key for me is really using power control to manage the screen brightness and under clocking rather than overclocking. The only time I found overclocking usedful was when playing fifa10.
Good luck
Sent from my HTC Vision using XDA App

Phone is still hella butter even @ 1.2ghz

I'm big into getting the most speed out of all my purchases but came to the realization that underclocking my phone to 1.2Ghz (Trinity kernel/free gs3 rom/Nova Launcher) with SetCPU is just as responsive at 1.2Ghz as it is at 1.8Ghz for the most part. Not a big gamer but from the ones I've tested I noticed no lag whatsoever. Just thought I'd share for everyone addicted to benchmarking their phones for evaluating what speed they want to run with. In real world usage I'm still very happy @1.2Ghz and battery life went from wonderful to phenomenal. Best part is that with the savings I'm seeing on the battery I now feel more comfortable increasing the brightness to a more comfortable level.
I use touch wiz launcher and with it under clicked to 1.3 I start seeing noticeable lag. And battery life was not that much better. I do keep my screen at full brightness though.
Sent from my SGH-T999 using xda premium
circuit.007 said:
I use touch wiz launcher and with it under clicked to 1.3 I start seeing noticeable lag. And battery life was not that much better. I do keep my screen at full brightness though.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I do keep my screen at full brightness though
The brightness setting is what's limiting your battery.

[Q] Underclocking Query

How much can the phone be underclocked while maintaining the stability of the system?
What would happen if i set Max freq to 600 Mhz?
What is the best thing to do to save up the very last bit of juice in the battery for emergency situations where i would only need the phone and message facility? Besides switching off Bt,wifi,sync.
Im asking because i was wondering if underclocking "too much" saves a substantial amount of battery when my battery is quite low and I am "hours away" from a charging port!
And is there a way to change the carrier name on the notification drop down to whatever we want.
Sorry if i sound noobish or if a similar query has been asked before
Thnx.
Underclocking the CPU dramatically isn't going to gain you a great deal in the way of extra battery life because:
1. Unless you are heavily taxing the CPU (complex 3d games etc), the biggest drains on the battery are the screen and the radio.
2. If the screen is off, the phone will drop the CPU frequency right down anyway.
The best way to get extended battery life is simply to carry spare batteries!
Regards,
Dave
Sent from my GT-N7100 using Tapatalk 2
I think 600mhz is way too low and counter productive or for that matter anything less than 1ghz. The phone will lag alot and you'll have freezes. You'll probably end up using up alot of the battery life trying to get tasks completed. You could try leaving the stock clockspeed 1.6ghz, set minimum cores to 2 and slightly undervolt to -25mv, leave the gpu setup to its default 533mhz and also undervolt to -25mv using a kernel that supports stweak app. Then run an app called Stability Test for 10minutes to check for errors.
Also I tried Go Power Master, which can be assigned to disable certain features once your battery hits critical low levels.
Sent from my GT-N7100 using xda premium
bushako said:
I think 600mhz is way too low and counter productive or for that matter anything less than 1ghz. The phone will lag alot and you'll have freezes. You'll probably end up using up alot of the battery life trying to get tasks completed. You could try leaving the stock clockspeed 1.6ghz, set minimum cores to 2 and slightly undervolt to -25mv, leave the gpu setup to its default 533mhz and also undervolt to -25mv using a kernel that supports stweak app. Then run an app called Stability Test for 10minutes to check for errors.
Also I tried Go Power Master, which can be assigned to disable certain features once your battery hits critical low levels.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Thats quite informative. Thanx!

What kind of battery life are you getting?

Please say what ROM you are using, kernel, using auto brightness or not, governor/scheduler, under clock/over clock, and your average screen on time. I will post a screen shot of my battery stats at the end of the day tomorrow.
But I'm on Jmz's stock modded rom, medium brightness all day, Jmz kernel, cfq scheduler with smart ass V2 governor, over clocked at 1.3ghz, and I average about 4-5 hours screen on time. Just average use with Twitter, xda, Internet searches, etc. Barely ever play games. Not sure about total battery life, will know tomorrow.
Sent from my HTC One VX using xda app-developers app
I'm on the stock HTC ROM. Also on stock kernel. CPU settings are down below and I run on low brightness all day. Most of my usage is heavy browsing and Google music. Also, Bluetooth is on for about an hour at a time. I'll update later with the time of death and how long it was for full battery time.
Sent from my HTC One VX using xda app-developers app

In your opinion

Which rom+kernel do you think gives the best gaming performance? Im currently on liquidsmooth and gaming is great but my phone becomes a little too hot after awhile.
No matter the Rom any game I play heats the phone up.
Sent from my HTC6500LVW using Tapatalk
HTC has had portable hand warmer issues since tree he rezound. They have come a long way in fixing these heating "features" but it still happens. I found just live with it or throttle your phone down to "power saving" mode at 1242 mhz on the CPU to reduce heating. The phone can usually do most tasks quite well with the lower clock frequency and can reduce heating.
Sent from my HTC6500LVW using XDA Free mobile app

Categories

Resources