Discussion in 'Android Devices' started by bigb3456, Sep 5, 2010.
My Eris becomes lagtastic when i unlock it and i don't know what to set my profiles as to help this.
I've been running the following SetCPU profiles for about 2 months and my phone runs slicker than snot on glass.
Awake: 768 max, 528 min
Temp>45.2*C: 480 max, 122 min (priority: 100)
Charging AC/Full: 710 max, 245 min (priority: 50)
Screen Off: 528 max, 122 min (priority: 50)
Currently running xtrSense 18.104.22.168
In addition to user experiences you'll see posted around the Eris forums (and in this thread ), have a look here, bigb:
SetCPU for Root Users
These are my SetCPU settings:
Main: 787/710 interactive
Temp >42.1 C: 480/245 interactive Priority 100
Screen off: 480/245 interactive Priority 95
Charging/Full: 480/245 interactive Priority 90
I get 1-2 days of battery life with these settings.
Note: You can only get the interactive governor if you have the new kernels installed.
"787/710" .. aggressive stuff.
Here's mine. Note four things:
- The over-temperature profile should always be your highest priority profile; and for battery savings, the "Screen Off" profile the next highest.
- The minimum clock speed that you can get away with depends on the specifics of the kernel involved: for some of the recent (but not most recent, as of 2010-09-05) Froyo kernels, you can set the minimum to 19 Mhz in all profiles; OTOH, for the new experimental kernels (BFS & CFS schedulers with an interactive governor), you probably shouldn't go below 245 Mhz for any profiles using the interactive governor. ( see note below ** ) If you are having problems with calls not waking the phone up (or slow to respond to calls), or sluggishness when unlocking the device, or skipping music - in all cases you should consider raising your minimum frequencies.
AFAIK, only some of the 2.2 CM6 kernels will behave well with 19Mhz + ondemand; most require higher minimum clocking than that to stay happy.
- I have multiple profiles based on battery % in order to stretch battery life, as I would rather have a slow phone at the end of the day than a dead battery. If you do this, you need to set the profiles with a lower battery % criteria to have a higher priority.
- Setting up your profiles is to some degree a matter of taste - people that sit in an office all day with a charger or dock right in front of them will prefer snappier response over battery reserve. Same thing goes for people who want to play music with the screen off - they will need a little more oomph in their minimum clocking for the "Screen Off" profile. OTOH, if you are outside or away from your desk much of the day, battery reserve will probably be considerably more important to you. Adjust your profiles accordingly.
[B]Prio Min Max Governor Criteria[/B]
80 x 480 G Temp > 50.0 C
70 x 480 ondemand Screen Off
60 x 480 G Battery < 20%
50 y 604 G Battery < 40%
40 y 710 G Battery < 65%
30 y 768 G Battery < 100%
20 y 768 G Full/Charging
where x,y,G depend on the kernel:
[B]OS/Kernel x y G[/B]
2.1 ROMs 160 245 ondemand
2.2 CM6-Froyo 19 19 ondemand
[COLOR=grey]2.2 CFS & BFS 245 245 interactive[/COLOR][COLOR=red] (retracted, see note below **) [/COLOR]
Some people might argue that the "Full/Charging" profile, or some of the higher % battery charge profiles should use either a much higher minimum clock rate, or a "performance" governor. Doing that is certainly acceptable, and it will get you a slightly more snappy response - but at the cost of higher battery temperatures and/or faster battery draining.
**[ Edit ] I'm having troubles with SetCPU and CFS2 kernels - seethis post in the Tazz V3.0 thread.
lol. I want my Eris to be fast!
No set cpu for me here. Crazy fast ROM. 528mhz ftw.
also make sure to ditch the setcpu widget, causes a lot of lag on unlock for some people.
whats everyones opinion on baked-in OCs (xtrrom, xtrsense) vs a setcpu profile? There shouldn't be any difference, right?
I'm running xtrSense with the CPU default gscript added so that I could use the above-mentioned profile settings.
yeah i'm on xtrrom, and I've been playing with using setcpu vs using the default 245/710 OC. doesn't seem to make much difference, except I like having the failsafe temperature setting in there so I'll probably stick with it
Another thing, does anyone's phone run hot while charging? My phone get's up to 111 degrees while charging. I don't think that's normal.
111 degrees is inching up toward overheating, although not quite there.
If I were overclocking, I'd set a temp and a charging profile.. take a look back at that link I provided in an earlier post.
One thing that you can do with SetCPU is to set more severe underclocking while the phone's display is off, to help save battery life. That said, SetCPU is an app that runs in the background, so there is going to be a performance penalty.
It's probably best to run both ways. I am considering running my phone normal (without SetCPU0 most of the time, but then run SetCPU when I know that I am going to be in a weak signal area, or, especially, driving through one.
111 degrees actually is overheating. HTC's temperature specs say that operating temperature range is through 40C, which is 104F.
I'd say try a different charger, or, as Frisco recommended, set a temp threshold profile in SetCPU with a priority of 100 set to clock no faster than 528 (or maybe 480, if you can stand the phone running that slow and you actively use the phone while charging.)
I will say, though, that I used Nav with the screen on one day last week for about 30 minutes (I usually run it with the screen off and just listen for voice prompts) and my phone was at 120 degrees, with the temp profile active, and it took quite a while for it to cool down. The phone is still fine. Brief periods at 111 are probably not going to kill your phone all that fast.
"111 degrees actually is overheating. HTC's temperature specs say that operating temperature range is through 40C, which is 104F."
111 degrees is not overheating, and not worrisome in the sense of likely damage to the device or battery, that's why I posted my response to the question as I did.
Especially if not constant; during the Summer we'll see the (outdoor) device/battery temps approach 120 degrees. Cooling it off will extend that day's battery life, and perhaps the comfort level of holding it.
The HTC specs are there for ideal circumstances, etc.
not normal? its absolutely normal to get hot while charging, especially charging from the wall vs. usb. Even moderate heat during use or storage WILL decrease the life and capacity over time of a battery. by the time it affects you, it will be time for a new phone or at least a new battery anyway.
I'm pretty sure my phone never goes BELOW 120 when Its docked in my car, charging, and streaming radio. screw it, I'm insured.
Most OEMs write their specs for ambient temperature, not internal temperatures. Their spec here only tells you the phone is not guaranteed to operate correctly when the air temperature is above 104F (and using stock software, of course).
Since the phone would come to room temperature even if it was turned off, that seems to imply that battery temperatures well in excess of 104 F would be perfectly acceptable. (I set my setCPU overtemp profile to 50.0 C ~= 127 F)
Help. Just installed SetCPU and setting up profiles, but in the main menu the max speed is 528 MHz. What gives?
I run 480/710 as do most people.
That's the problem: in the main menu, the max I can scale it is 528 MHz. I can't slide it any higher than that. Does that make sense?
Does it have root access? Go into the superuser app and see if it has access.
SetCPU is listed as one of the Superuser Permissions.
But does it have a plus or minus beside it?
It should have a green dot beside it.