Have been monitoring for battery life, and tweaking settings, and testing different governors to find which keeps the device at the lowest state. I have noticed recently no matter what governor I select I am using higher lvl CPU states. Out of 4 hours on, I have:
300MHZ - 1h54m
1.19GHz - 1h
1.5GHZ - 26m
1.73GHZ - 36m
2.27GHZ - 13m
Also just monitoring the touch screen boost (by leaving a cpu monitoring program open and touching the screen), it automatically boosts to 1728MHZ on screen touch. Can anyone confirm that this is what they are seeing as well, and give me any of your numbers for CPU states. I know we don't have custom kernels like on my S3 and we can't customize the touch screen boost, just wondering what everyone else is getting. Also these CPU states are from just texting, web, and a couple of other basic apps. No Gaming.
jokesonme said:
Have been monitoring for battery life, and tweaking settings, and testing different governors to find which keeps the device at the lowest state. I have noticed recently no matter what governor I select I am using higher lvl CPU states. Out of 4 hours on, I have:
300MHZ - 1h54m
1.19GHz - 1h
1.5GHZ - 26m
1.73GHZ - 36m
2.27GHZ - 13m
Also just monitoring the touch screen boost (by leaving a cpu monitoring program open and touching the screen), it automatically boosts to 1728MHZ on screen touch. Can anyone confirm that this is what they are seeing as well, and give me any of your numbers for CPU states. I know we don't have custom kernels like on my S3 and we can't customize the touch screen boost, just wondering what everyone else is getting. Also these CPU states are from just texting, web, and a couple of other basic apps. No Gaming.
Click to expand...
Click to collapse
thats actually not bad at all and as for the spike when touching the screen idk if id want to change that, it does a lot of calulations when the screen is touched so if you downclock that it might make a lag effects
Related
I was thinking about installing SetCPU but I have heard stories of it not working very well on the Captivate. Does anyone use this, and if so what kind of battery life improvement are you seeing? Post config settings too please!
Its working just fine. I have a live background so my battery usage isnt very great so long as the screen is on. I had some trouble with the system being slow to respond every time I turned the screen back on when I had "screen off" profile set to max 200 and min 100. then it dawned on me that it would always just underclock to 100 I set it to max 200 and min 200 when the screen is off and also started using launcher pro and it is no longer sluggish at all.
This has saved me a gratuitous amount of battery life when the phone is idle.
Default profile
Max 1Ghz
Min 800Mhz
scaling Conservative
Charging/full profile
Same as default but scales on performance
Battery <50%
Max 800Mhz
Min 400Mhz
scaling Ondemand
screen off
Max 200
Min 200
Scale powersave
kenjindomini said:
Its working just fine. I have a live background so my battery usage isnt very great so long as the screen is on. I had some trouble with the system being slow to respond every time I turned the screen back on when I had "screen off" profile set to max 200 and min 100. then it dawned on me that it would always just underclock to 100 I set it to max 200 and min 200 when the screen is off and also started using launcher pro and it is no longer sluggish at all.
This has saved me a gratuitous amount of battery life when the phone is idle.
Default profile
Max 1Ghz
Min 800Mhz
scaling Conservative
Charging/full profile
Same as default but scales on performance
Battery <50%
Max 800Mhz
Min 400Mhz
scaling Ondemand
screen off
Max 200
Min 200
Scale powersave
Click to expand...
Click to collapse
Thanks for these, I was looking for a some decent settings. Mine were close to that to start, but I had no idea what I was doing, haha
I had some stability problems with it that I am now fairly certain are related to adjusting the polling frequency in advanced settings. After disabling setting advanced settings on boot, and a reboot, it has not caused the phone to hang once. I am also fairly sure that the phone boots with the conservative governor enabled and min/max frequencies set to 100MHz and 1GHz, even without SetCPU - so the main benefit here is profiles to force lower clocks with screen off, or during overheat or low battery.
CPU throttles itself. Any effects of setCPU is placebo effect
Err if you set the clocks yourself, you can produce a difference depending on what it's catered towards. I'm sure if I set the max clock to 200 (assuming the app works) for all situations there will be a difference.
Does the stock ROM have a perflock like the EVO that we need to disable?
Also, does the stock ROM automatically underclock at times, or???
I've now verified after clearing user data, the stock firmware already sets the conservative governor and allows it the full range of frequencies supported by the CPU. Only benefit from SetCPU should be profiles - reduce max clock when hot or low battery, that sort of thing.
Sent from my Samsung Captivate
I was going to make a screen off profile of 200mhz, to save battery. Should I bother doing this?
Edit: Nevermind, I'm just going to uninstall it. It's locked up my phone twice already
Default Profile: 800 MHz
Profiles:
Temp > 46 C -- 400 Max 100 Min Conservative
Battery < 40 -- 400 Max 100 Min Conservative
Screen Off -- 400 Max 100 Min Conservative
This now gives my phone life of about 2 days with moderate use (1 hour calls, 1 hour browsing and another 30-45 mins of using apps that need screen on like games, etc)
brandonb81 said:
I was going to make a screen off profile of 200mhz, to save battery. Should I bother doing this?
Edit: Nevermind, I'm just going to uninstall it. It's locked up my phone twice already
Click to expand...
Click to collapse
One thing u got to keep in mind, CPU scales up when woken from low speeds (like when u set for 200 n this takes a second or two). After some R&D i realized 400 MHz when sleeping is optimal with hardly noticeable lag.
Unhelpful said:
I had some stability problems with it that I am now fairly certain are related to adjusting the polling frequency in advanced settings. After disabling setting advanced settings on boot, and a reboot, it has not caused the phone to hang once. I am also fairly sure that the phone boots with the conservative governor enabled and min/max frequencies set to 100MHz and 1GHz, even without SetCPU - so the main benefit here is profiles to force lower clocks with screen off, or during overheat or low battery.
Click to expand...
Click to collapse
well, i have tried playing heavy games like asphalt 5, dungeon hunter, assasin's creed... these all games seemed to work with no lag even at 400 MHz when my battery was less than 40. Most apps I have or used or saw were very comfortable even at 400 MHz. But with multiple apps open, sometimes there was lag, so i set the max at 800 MHz, instead of 1 GHz.
Also, I set my connection to EDGE from 3G. This helped reduce phone from getting heated up with long calls.
I tried using this app myself but uninstalled it after a week. While I'm sure there was some underlying cause, it made my phone never wake up from sleep mode when it turned off.
Honestly thou, I know several android phone owners with s lot of phones That didn't see any real change in their battery life as s result. And based on my experiences, I'd say stay away from it.
Just my 2 cents thou
Sent from my SAMSUNG-SGH-I897 using XDA App
.
..
I use setcpu to do this.
Look into the governors, choose one.
Then choose the appropriate thresholds (in the advanced menu) for what you do.
It doesn't allow you to tweak per app, but tells the cpu governor at what %of cpu to move to the next cpu speed (up or down).
I set mine very low, as i care more about battery than performance. So my up threshold is like 95% or something.
But my down threshold is a lot more agressive.
But you do the opposite.
MuF123 said:
Hello,
my question is regarding dynamic overclocking. I've used the ones that raise the speed when under a load - but my question is -
Is there a way to return to stock clocks after certain time?
Explanation:
situation1: I want to check new single mail or open new single IM or check university's website for some news, I want the device to be FAST as possible, nevermind the battery.
situation2: I want to use maps/navigation/IM/games/web browsing for longer period of time (hours?) with the screen on. I don't need all the power when I play solitaire, text on IM or browse not-so-important news websites.
I think when I've seen the realtime clock displayed on my phone it jumped to max clock right after I've clicked almost anything on the screen. I want the speed-up, but after certain period of time to stop doing this in favor of the battery life-time.
Any ideas how to do this? Thanks!
Click to expand...
Click to collapse
Sent from my Milestone using Tapatalk
Yes, just throttle the cpu to give you more power when you are sluggish. That could work for you.
Me? I have my droid do 110 when screen is off (works quite well!), and then I FORCE the unit to 1000 when plugged in. Besides that i throttle the cpu based on battery power: more cpu power with more battery life. Makes my droid last longer.
I might want to add a throttle up when sluggish and not in my personal battery red zone and a throttle down when the cpu gets too hot period.
Any cpu frequencies that you all would suggest?
..
MuF123 said:
Thanks for the reply, but - think about this, I will start a 3D game, it will use 100% of the cpu so it would always stay at the highest possible frequency (+highest voltage). I don't want that.
Click to expand...
Click to collapse
I dont get it?
You dont want max speed in game? Why do you overclock?
If the game requires 100%, the it will (and should) clock up.
As soon as the game doesnt, it will clock down (depends on your threshold).
The only other i could see, is to change the max clock rate in setcpu before you play the game. This will ensure it doesnt clock higher than your choice, but requires a manual step.
But seriously, if your cpu is pegged at 100, why would you not want it to step up the higher speed?
Sent from my Milestone using Tapatalk
..
MuF123 said:
exactly - I don't want minimum battery in game, that's why I don't want to overclock.
actually from the nature of 3d rendering I think every game will run at 100%, but the situation when the game hits the frame limiter (not likely on milestone).
I want snappy performance while doing few quick tasks:
e.g.: new IM comes, I want to unlock, load the application, get to the IM, reply, lock. (40seconds)
or
taking phone from cradle - I want the phone to load homescreen fast, rotate the screen, open phone app, to look at last missed call and call back (20seconds).
Battery life won't be affected by 40 or 20seconds of ~1100mhz, okay.
And then I start a game for a prolonged time. It will run smoothly even on 550MHz, the additional frames I see are just waste of battery = I don't want that.
So now I have two options - either run at max speed and it will be always fast and it will drain my battery when I decide to play for an hour.
OR
I can use default speeds for longer battery life for everything and I will wait an hour to rotate the screen in browser or IM app.
Click to expand...
Click to collapse
You could compromise and find a max speed that you could undervolt to make it drain battery like stock. My 800mhz vsel is less than the default vsel @550. So the battery drain is less...
It requires some trial and error, but most "slight" overclocks (700,800; depends on the phone) can be configured to drain less than stock.
Of course, if you feel you need 1000 or 1100, this wont work as it requires increasing the vsel (or at least not decreasing it).
Sent from my Milestone using Tapatalk
My specific issue involves SetCPU but I'm wondering about the larger scheme of how things work.
My phone gets hot in the car dock when running GPS, Navigation, and Bluetooth (I don't turn it on but I think my dock does it automatically). The general consensus is to underclock slightly when charging because charging generates heat, and I have a SetCPU profile to do that. Then comes the issue of heat generated from GPS and Bluetooth, and possibly processor load when running apps while docked, so I have two profiles for that: one to underclock a few steps down from the charging CPU speed when the temperature of the phone is at 40* C, another to clock down one more step when the temp hits 42* C, which I feel is at the point the phone gets a little too warm for use.
I've noticed that my phone doesn't necessarily stay cooler and in fact, sometimes it gets hotter than before I started using SetCPU. Over the past few days I've seen temps of near 45* C (113* F), toasty enough that I have to let my phone cool down before I can use it again.
So, my question is if underclocking too much is bad. For example, if I'm underclocking too much, does that strain the processor while it is trying to run apps and hardware? Is it better to let the system handle processor speed? I see this in driving a manual/standard transmission car - if I attack a hill in a high gear, I can eventually reach the top but with increased load on my engine. Maybe the processor speed works opposite - too low and it strains too much?
I used to be concerned about clock speed vs. battery life but now that I'm docking in my car more and noticing the heat, I'm more concerned about the heat. I'm currently using redstar's kernel but get the same results with that or the CM kernel that comes with the nightlies.
If it helps to troubleshoot, or if you want to critique me, here's my profile list.
Normal: 245 min, 998 max (default settings)
Priority 100 - temp > 42*C: 460 max, 245 min
P 90 - temp > 40*C: 499 max, 245 min
P 80 - screen off: 384 max, 245 min
P 70 - charging AC: 576 max, 245 min
(SetCPU related question, sorry if this is too far off forum topic) Are there better profile settings I could be using?
Also, I don't quite understand undervolting in terms of kernels. What effect does that have, if any?
When I bought Xperia T, after a while, I started to be a little disappointed with performance, autobrightness, discharging when playing, etc.
After some digging deeper into this problem, I have found, that cpu is throttled by temperature. And not only the cpu.
A few minutes of playing game, cpu goes to 800MHz, display brightness goes to level 100 (max. is 255), wall charger current is reduced (even when connected, it is discharging), radio power is reduced, etc.
Change it yourself:
Example:
xo_therm 14 -1000 380 20 NOTIFY CAM_NORMAL cpu_perflevel:1728000 charge_current_limit:0 usb_current_limit:1 modem_level0 lcd_brightnesslevel:240
xo_therm 14 = sensor step
-1000 = -100,0°C
380 = 38,0°C
20 = don't know (maybe some kind of sample rate?)
NOTIFY CAM_NORMAL = obvious (camera)
cpu_perflevel:1728000 = cpu frequency
charge_current_limit:0 = obvious (0 is 1300mA I think, 1 is 1100mA, 2 is 900mA, etc.)
usb_current_limit:1 = obvious (has impact on charging too)
modem_level0 = power of modem
lcd_brightnesslevel:240 = obvious (0 - 255)
Set the highest temperatures, with low enough frequencies and charging current values, to let phone cool down.
"gpu_perflevel" can be used too and there are some other thermal sensors in sysmon.cfg, which are also responsible for thermal throttling.
Disclaimer:
Each device is different and I am not responsible, if your device burns with some values from here.
Both CPU cores always on:
Echo 1 in /sys/devices/system/cpu/cpu1/online and change permissions to 444. And if you want to prevent errors from log (and maybe some unwanted wake locks), rename /system/bin/mpdecision to something else or delete it.
what is temp at what cpu throttles (and other things)?
seems it is lower than other devices, something like 40C, i think my sgs3s was at 76C or similar.. not sure, will check later.
sgs3 was a very hot phone.
Sent from my Xperia T
You can see the temperatures in sysmon.cfg - xo_therm 400 500 = 40 - 50°C for example. Cpu temperature, not battery. There is no tool to monitor cpu temperature, but if you set your own frequencies, you can see with Cool Tool, how long it takes to the lowest frequency.
peetr_ said:
You can see the temperatures in sysmon.cfg - xo_therm 400 500 = 40 - 50°C for example. Cpu temperature, not battery. There is no tool to monitor cpu temperature, but if you set your own frequencies, you can see with Cool Tool, how long it takes to the lowest frequency.
Click to expand...
Click to collapse
thanks, will check. i am on cm10 and didn't notice throttling yet, but i will check now as it is ****ty if so.
Sent from my Xperia T
I have noticed the throttling but it doesn't affect the performance in my case, playing games and watching HD video are fine, just annoying when the screen suddenly does dim.
Sent from my LT30p using xda premium
@OP:
If you don't want throttling, uninstall Androids inbuilt Thermal monitor(No need to tell you the risk by doing that I guess).
Thanks for you valuable advice.
Don't think it would help as that file says 2nd core off values are hardcoded
Sent from my LT30p using Tapatalk 2
I think, that it works, because I tested it and I am using my own values.
Good thing I won't be playing games when my T will arrive
https://developer.qualcomm.com/mobile-development/development-devices/trepn-profiler
Stay Informed
Trepn Profiler is currently being redesigned. Sign up to be notified when Trepn Profiler is reintroduced.
Click to expand...
Click to collapse
Still? Damn how long do they take ? -.-
Here is the .apk of the old version. No idea how much works and what doesn't!
Hello,
Could it be some kind of default on your device ? or maybe the application ?
Cause I remember Qualcomm's communicating on their S4 being "cooler" than its opponents when under heavy load.
Can someone else confirm ?
What's strange is that the game you mention (Osmos HD, which I bought some time ago for my TF101) does not even use super high end 3D graphics etc etc ... maybe the perf drop could come much quicker with some cpu/gpu intensive apps.
If confirmed, it might even become a big "no go" on this phone for me.
Nickola
nickola said:
Hello,
Could it be some kind of default on your device ? or maybe the application ?
Cause I remember Qualcomm's communicating on their S4 being "cooler" than its opponents when under heavy load.
Can someone else confirm ?
What's strange is that the game you mention (Osmos HD, which I bought some time ago for my TF101) does not even use super high end 3D graphics etc etc ... maybe the perf drop could come much quicker with some cpu/gpu intensive apps.
If confirmed, it might even become a big "no go" on this phone for me.
Nickola
Click to expand...
Click to collapse
I've had this phone for a while now and I haven't had a bit of lag while playing any game I have. Everything seems fine except the sudden dimming of the screen when playing games. Don't let this put you off buying the phone, its a great phone
Edit: been playing Osmos HD for at least 25 minutes, I'm experiencing no such lag or performance issue. Only the dimming issue I seem to get.
Well, after some more investigation, I have found, that lags in Osmos HD are not caused by cpu throttling, but wifi disconnecting.
Playing the game is fine, but still, with default settings the temperature is going high and except the screen dimming, cpu goes to 800MHz, (1 core disabled on highest temperature), and phone is discharging even when connected to wall charger.
It seems to me, that the overheating is not caused that much by cpu, but gpu. It would be nice, if it could be tested somehow by lowering the frequency of gpu.
I wonder if the heating issues could be fixed with software patches. Given Sony's desire to incorporate playstation stuff, I find it hard to believe there is some sort of hardware issue.
Wish we could get some more samples to work with.
Sent from my HTC_Flyer_P512_NA using xda app-developers app
Just measured with my settings (in the room - about 23°C):
10 minutes of playing Osmos HD without charging = 62°C CPU temp
With one core running on 1350 MHz and LCD brightness value 150, it's not increasing anymore.
When charging, the temperature will go higher. I will test it too.
peetr_ said:
Just measured with my settings (in the room - about 23°C):
10 minutes of playing Osmos HD without charging = 62°C CPU temp
With one core running on 1350 MHz and LCD brightness value 150, it's not increasing anymore.
When charging, the temperature will go higher. I will test it too.
Click to expand...
Click to collapse
Have you tried treppn profiler?
Anandtech says a CPU core draws around 450-750mW while gpu goes 800-1200mW!
Seems like 400mhz is a hard Task for an 225.
If you are still on ics maybe try jellybean? Perhaps project butter may more efficiently handle the gpu.
Maybe even make a list of "stress test" for people to try and see what the various results are.
If all else fails try undervolting the gpu and cpu.
Sent from my HTC_Flyer_P512_NA using xda app-developers app
Haldi4803 said:
Have you tried treppn profiler?
Anandtech says a CPU core draws around 450-750mW while gpu goes 800-1200mW!
Seems like 400mhz is a hard Task for an 225.
Click to expand...
Click to collapse
Yes, I tried trpn profiler provided by you, but there are limited options.
It looks like the GPU cannot handle this frequency.
Undervolting won't help anything, but lowering GPU frequency would help I guess. But this cannot be done without custom kernel, allowing this.
LegibleEel said:
I've had this phone for a while now and I haven't had a bit of lag while playing any game I have. Everything seems fine except the sudden dimming of the screen when playing games. Don't let this put you off buying the phone, its a great phone
Edit: been playing Osmos HD for at least 25 minutes, I'm experiencing no such lag or performance issue. Only the dimming issue I seem to get.
Click to expand...
Click to collapse
Same here. I've been playing Speedball 2 and GTA3 mainly but I have played a few others too and haven't experienced any lag and no performance issues observed at all.
Is it safe to use this profile while gaming?
Normally when the OS sets the profiles, I've often seen that the prime core will downclock very fast or just shut off in few mins @~45-50C.
Consecutive benchmark runs suffer heavily as a result of that & the prime core takes a long time to come back online & that too most often not even at the full speeds of 2.8Ghz but only 2.4 or 1.8Ghz.
When setting the dynamic profile from a kernel manager there's absolutely no shutting down of cores & benchmark scores often show a increase in the total score.
But cpu temp reported is also around 62-68C.
Battery temps remain well under 40C, only the cpu is on the higher side obviously because it's running much faster & not throttling heavily.
So what's the opinion of any experts here - is it ok to run games like pubg with this profile?
I find the behaviour of the default thermal profile (whichever it is that's selected by the OS automatically) to be very conservative.
Honestly, temps are starting to be ,,dangerous'' above 90C so u can run this profile with no worries. Just be ready to feel the phone a bit warmer.