Related
so im currently running MCK 2.2 rom with the updated kernel but without compcache enabled because i havent been able to get it working yet.
here's the problem though, about once a day my phone will slow down to an unberable speed... just like it used to with the OEM Rom.
when I open up SetCpu (which i know isnt supposed to do anything on the hero) it tells me that my CPU is running at 245mhz, but the control bars in SetCPU are set for 528/480mhz... when i hit refresh the phone comes back up to 528/480 and its fast(er) again...
anybody have any ideas on this one?
dmc971989 said:
so im currently running MCK 2.2 rom with the updated kernel but without compcache enabled because i havent been able to get it working yet.
here's the problem though, about once a day my phone will slow down to an unberable speed... just like it used to with the OEM Rom.
when I open up SetCpu (which i know isnt supposed to do anything on the hero) it tells me that my CPU is running at 245mhz, but the control bars in SetCPU are set for 528/480mhz... when i hit refresh the phone comes back up to 528/480 and its fast(er) again...
anybody have any ideas on this one?
Click to expand...
Click to collapse
What gov. are you using on setcpu?
theoottesen said:
What gov. are you using on setcpu?
Click to expand...
Click to collapse
performance, and profiles are not enabled... again, it only happens after 12-15 hours or so... about once a day
Similar problem...
dmc971989 said:
performance, and profiles are not enabled... again, it only happens after 12-15 hours or so... about once a day
Click to expand...
Click to collapse
I have a similar problem. I experience serious slowdowns (compcache enabled or disabled) about once per day. I have not verified the CPU speed as I'm not using SetCPU. I am using the "performance" governor in MCK.
My typical solution is a reboot.
im just curious if this is the original problem or a new one cause by this rom setup... because I dont ever recall reading anything about the CPU getting stuck at 245mhz from sleep mode being the source the slow downs....
Have you tried disabling the location services to verify it's not that particular bug you're seeing/experiencing?
x99percent said:
Have you tried disabling the location services to verify it's not that particular bug you're seeing/experiencing?
Click to expand...
Click to collapse
yes, i keep them disabled...
jamesthomas128 said:
I have a similar problem. I experience serious slowdowns (compcache enabled or disabled) about once per day. I have not verified the CPU speed as I'm not using SetCPU. I am using the "performance" governor in MCK.
My typical solution is a reboot.
Click to expand...
Click to collapse
I look in the kernel and there are two sets of settings: The profiles and a set of setting for the kernel speed (this is split into min/max for screen on and min/max for screen off)
For screen on, it is set for 480000 min/528000 max
For screen off, it is set for 245760 min/245760 max
If the screen is off, it's possible that the kernel went into the lower settings and didn't come back.
I've heard different reports on whether the profiles work in the Hero. I'm curious myself. I do know the stock rom has everything locked, but since the kernel source has been released and Modaco released his kernel, I'm not so sure if the lock statement is true anymore.
I'm compiling a kernel as we speak with the cpu frequency scaling on. Had some issues with the cpufreq.h file not seeing two variables necessary for the userspace profile, but hopefully I was able to fix that (won't know until I run it).
tkirton said:
I look in the kernel and there are two sets of settings: The profiles and a set of setting for the kernel speed (this is split into min/max for screen on and min/max for screen off)
For screen on, it is set for 480000 min/528000 max
For screen off, it is set for 245760 min/245760 max
If the screen is off, it's possible that the kernel went into the lower settings and didn't come back.
I've heard different reports on whether the profiles work in the Hero. I'm curious myself. I do know the stock rom has everything locked, but since the kernel source has been released and Modaco released his kernel, I'm not so sure if the lock statement is true anymore.
I'm compiling a kernel as we speak with the cpu frequency scaling on. Had some issues with the cpufreq.h file not seeing two variables necessary for the userspace profile, but hopefully I was able to fix that (won't know until I run it).
Click to expand...
Click to collapse
im fairly positive that the CPU is getting stuck in the sleep mode while the rest of the phone is not, causing me these issues... the problem is i dont know how to fix them
dmc971989 said:
performance, and profiles are not enabled... again, it only happens after 12-15 hours or so... about once a day
Click to expand...
Click to collapse
Ok, modaco rom sets the governor to "performance" on boot. This essentially "sticks" your CPU to max throttle.
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Will tell you where you are, governor wise..
I'm not entirely sure what setCPU does, I've never used it, but I assume it just tweaks your top and bottom Mhz and maybe changes governor to performance when the screen is on? If it's configured properly? Maybe not, who knows?
If you want the best battery life, put the governor back to msm7k, it's a custom governor modified by HTC to make your battery last longer.
I changed the following line in modaco.sh:
echo "performance" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
to:
echo "msm7k" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_govern
and haven't noticed any slowdown from it.. my battery is lasting longer than it did on Stock or Fresh 1.1...
this may be posted in the wrong section but i would like everyone running froyo to test this out
HERE IS THE LINK TO GET THE LATEST SETCPU
http://forum.xda-developers.com/showthread.php?t=505419
So I have been doing some experiments on ways to save battery life....I think i have made a break through it is not fully tested i would like for some of you to try it out.
with the latest updates to your ROM itself, setcpu, superuser, and the addition of cache cleaner and the incredible AUTOKILLER (a must have) i have been able to run extremely low setcpu sleep profiles without any noticeable loss of performance.
Believe it or not i have my sleep profile down clocked to 19200mhz with out "noticeable" performance loss
i would like for some of you if possible to try these profile out for a while and see how it works out for you
DEFAULT 480min---whatever you want max (mine is 787) ondemand (for performance)
OR DEFAULT 245min---whatever max (for even more battery savings)
SLEEP 192min---480max ondemand (works great even without sleep to wake lag)
it works dont believe me then check out set cpus new feature "time in state"
open setcpu
go over to info
scroll down a little and you will see the times in state your phones cpu runs in the most
you should now see values at the lowest state of 19200
if this works in theory we can benefit from longer battery life
and faster charging
please try these out and report back to the post or PM me...this could be good
Thanks
UPDATE 8/22 EDIT: some users are having success running an even lower default 19min--whatever max (thats even more savings) will be looking into it
try these even lower profiles
DEFAULT 122min--whatever max (screen ON cpu does not drop below 122mhz)
Screen OFF 19min--245max (no lag just ran pandora and cardio trainer at the same time here no lag from sleep to wake either)
or Screen Off 19min--480 max for more performance
REMEMBER not to have conflicting profiles and to have SCREEN OFF at your highest priority
please post here your own findings and results
Thanks again
UPDATE 08/24/2010
after experimenting with other speeds i have finally settled on these speeds for my personal taste on performance and battery savings
MY FINAL SETTINGS...
DEFAULT 19MIN---786 or whatever MAX on demand
SCREEN OFF 19MIN---480 MAX on demand (highest priority) think deeply about why this is the highest
TEMP <40 19MIN---528MAX (screen off overrides this which cools anyway)
BATT <40 19MIN---604MAX
next more into advanced settings....coming soon
UPDATE 08/26/2010
im almost at the holy grail here
try this set up
SCREEN OFF 19--480 (95 priority)
TEMP <40 19--580 (90 priority)
ADVANCED SETTINGS
SAMPLING RATE---100000
UP THRESHOLD---98
ignore nice ---0
power save bias---0
hit apply (if you like it check set at boot)
ALL CPUS ARE NOT CREATED EQUALLY WE ALL KNOW THIS SO DONT EXPECT MY EXACT SETTING TO WORK FOR EVERY SINGLE PHONE
I CAN ONLY OFFER A STARTING POINT BUT ITS UP TO YOU TO TWEAK IT BUT ITS WORK
I HOPE THIS HELPS
things to notice....
in the main screen in setcpu watch the main frequency values bounce up and down...after a few seconds the values seem to stabilize at the lowest frequency of 19
in time of state screen even when screen on most of the time the 19 freq get the most values
i need a few guys to run, test and monitor the values that i just posted ^^^HERE^^^
this may further the battery life once we stabilize the frequency to 19 most of the time while keep the SAME performance which i think i may have did
run some linpacks and quadrants with those setting
i got
5.4 linpack running 787max
431 quad running 787max
then it drops back to 19 and stabilizes
hope this works and please post all your feed back and setting so we can learn this and get it perfect
thanks
I even use 122 and 480 for my screen off profile.. And I don't have any lag at all.
thisisreallygay said:
I even use 122 and 480 for my screen off profile.. And I don't have any lag at all.
Click to expand...
Click to collapse
19 is even lower try it
Oh 19200? Wow I wasn't paying attention well enough. I'll try it.
Almost from the beginning of my rooting in May and using SetCPU, I've been using 19.2- 748.8 (on demand) with the screen on (sometimes higher but recently reduced the max to see if it helped with some FC's I was having - still haven't determined if it was the profile or the ROM that fixed my FC's).
I use 19.2-245 for screen off. I'd venture that there's about a one second delay for the caller ID to work once a call rings in, but it's more than bearable and worth it.
I have it go to 19.2-528 when the battery is less than 25%,and 19.2-480 if the temperature is above 49 degrees celcius.
I wonder what it's like when receiving a call. I just set it and I'm not having any lag with just turning it on or anything. I'll test it out with other things. I hope this greatly improves my battery.
roirraW "edor" ehT said:
Almost from the beginning of my rooting in May and using SetCPU, I've been using 19.2- 748.8 (on demand) with the screen on (sometimes higher but recently reduced the max to see if it helped with some FC's I was having - still haven't determined if it was the profile or the ROM that fixed my FC's).
I use 19.2-245 for screen off. I'd venture that there's about a one second delay for the caller ID to work once a call rings in, but it's more than bearable and worth it.
I have it go to 19.2-528 when the battery is less than 25%,and 19.2-480 if the temperature is above 49 degrees celcius.
Click to expand...
Click to collapse
shame on you for keeping that secret all to yourself
SHAME
By the way why did you say froyo roms specifically? I'm trying this on tainted tenzo and it's working. I'm usually on a frooy ROM though.
Hi Guys,
Can you please tell me how to get setcpu? I can't find it in the market.
Sent from my Nexus One using XDA App
Search for it on his website, idk what his website is you'll have to search for it. Or download a ROM with it already in it.
im on froyo 30 and was unable to get the 19.2 to show on time in state with screen off profile set to 100 priority at 245/19.2
i was however able to have it start using that frequency by using 710/19.2 as my default setting, then enabling the 245/19.2 profile as screen off.
ive read its not too good to have the cpu jump more than 300mhz per profile though so im not sure how this will work out.
thisisreallygay said:
By the way why did you say froyo roms specifically? I'm trying this on tainted tenzo and it's working. I'm usually on a frooy ROM though.
Click to expand...
Click to collapse
hmm last time i was on sense rom sense fell apart if you clocked lower than 245
epically receiving a phone call
but i only test this method on froyo
I've heard that too. Although I don't know what is bad about it.
sh_mohanna said:
Hi Guys,
Can you please tell me how to get setcpu? I can't find it in the market.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
HERE
http://forum.xda-developers.com/showthread.php?t=505419
eklipze said:
im on froyo 30 and was unable to get the 19.2 to show on time in state with screen off profile set to 100 priority at 245/19.2
i was however able to have it start using that frequency by using 710/19.2 as my default setting, then enabling the 245/19.2 profile as screen off.
ive read its not too good to have the cpu jump more than 300mhz per profile though so im not sure how this will work out.
Click to expand...
Click to collapse
i heard that too but all froyo dev have a 245 to 710 stock on their roms
thats why i kinda spilt the two profiles and why 245min--- is experimental
leave your screen off for a while and see if the ime of state shows up
also make sure not to have conflicting profiles running in setcpu
Hmm. Well tainted is vanilla but has some sense elements (like sense dialer) So idk. It seems to work. I'll test out calls.
thisisreallygay said:
Hmm. Well tainted is vanilla but has some sense elements (like sense dialer) So idk. It seems to work. I'll test out calls.
Click to expand...
Click to collapse
oh ok tainted is not vanilla
tainted IS sense with sense removed with vanilla remaning hence the word tainted
some sense is still there
i think
Yeah it's got sense contacts and stuff but vanilla messaging. But it has the sense dialer so I think it would also have lag with calls if the sense ones were having lag. And I just tested it and it took a lil while for it to recognize whose number it was but it still gave me plenty of time to answer the call. I'll be testing to see how it improves battery. Thanks for the find
Im also testing setcpu Advanced settings batery life (without performance loss)
What settings are those?
Sorry, not sure if this is int he right section but from the 1000+ hours i have used on this forum i decided to create my own post. Battery life on Android seems to be the evil culprit of MANY, i have finally found the BEST combo for battery life.
I have tried about 90% of the radios and android builds out there and this by far is the BEST. FIRST i wanna thank ALL developers, mods, beta testers and commenter's because without you all, this would not be possible(Android on the HD2)
My CURRENT setup(which i will probably leave on forever since its set now)
US Tmobile HD2
- Radio 2.12 (the latest one)
-Rom: Elegencia Rom (GTX version) --> http://forum.xda-developers.com/showthread.php?t=651729 So i dont get the robot voice anymore
- Android Rom ---> ▐HYBRID▐07.09.2010▐warrenb213 CM6 9/6-V1.5a T-Mo US Optimized▐ Kernel:mitchyprima r10▐ RMNET version http://forum.xda-developers.com/showthread.php?t=775150
- Special Settings in Windows Mobile: Turn off Auto backlight in windows mobile, turned of sync, weather, facebook, all that stuff that may secretly be on by default in windows mobile.
- Special settings in Android: Note: i turned OFF Auto sync for GMAIL email( since the FREE app called K-9 mail has MUCH better push email which uses much less battery than gmail's auto sync), no gps(sometimes wireless network location is used), no facebook sync, weather or news sync. You can set to whatever set cpu settings or sync settings you prefer, im just letting you know my configuration, the main thing to FOCUS on is the RADIO, the ROM(s) the Set cpu SCREEN off settings and the task killer settings.
1. Installed Set Cpu (Free to download on xda but i paid for the donate version to support the dev)
2. Set Cpu settings are in the PHOTO BELOW but as a recap
a. Click Autodetect
b. On MAIN tab, i set the max processor speed to about 652800 and the min to 245000, CONSERVATIVE SCALING, click SET ON BOOT
c. on PROFILES TAB, I added THREE profiles bt only ONE is necessary to get better battery life: SCREEN OFF profile, 384 max and 245 min, priority 100! POWERSAVE scaling
d. click on advanced tab, all the settings should be default, mines are
Sampling rate 200000, Upthreshold 80, down thresh 20, Ignore Nice load 0 and Freq Step 5, click APPLY and SET ON BOOT.
I also installed advanced task killer, not sure if it helps but my battery has been great since. Settings on there:
AUTO START checked, Show notification checked, Auto Kill Level: SAFE, AutoKill frequency when SCREEN OFF, Security level HIGH. OF COURSE you will have to put various apps on IGNORE so task killer doesnt kill them when the screen is off, so far i have ignored: App Brain, Advanced Task Killer(MAKE SURE TO PUT THIS ON IGNORE OR ELSE IT WONT WORK BECAUSE IT WILL KILL ITSELF lol), SetCPU, SUPERUSER, Google search, ad free, k9 mail and battery indicator pro.
All on ignore so they dont get killed, and i noticed ALOT of people use task killer but forget to put superuser, setcpu and advanced task killer on the ignore list so they may be getting closed out sometimes, which will make them ineffective for you.
Im in Chicago, my data has got up to about 1.5mb down with this rom, FASTEST speed i got yet! As you can see from the picture, I took my phone Off the wall charger around NOON YESTERDAY, it was on 100%, played word feud all day basically, browsed the web and tweeted, couldn't do much since i worked a 12hours shift but by 10pm when i left the office, i STILL had 88% battery left, used the device more when i got off, played angry birds, texted, tweeted, talked to a few people, fell asleep without charging and got scared that it would be dead, but i wake up at 9am...... STILL 68% i played more games, texted and tweeted, now im at 63% and its going on NOON again, so 24hrs decent amount of phone use and im at 63%, thats CRAZY!
My data is on H and 3g, DOES not turn off when the screen is off, i still get my WordFeud push notifications and K9 mail email PUSH when i get new ones(that also helped ALOT when i turned off the gmail push, and downloaded K9 mail, its FREE, has integrated inbox and is the BEST email app out there that ses the LEAST battery to have TRUE push notifications when people send an email to me.
Hope this helps you all, Give my combo a try, let me know your results, but so far this battery has lasted a full 24 hours and is not even HALF dead with moderate use.
side mentions:
NO BSOD
NO FREEZES
FAST DATA
WIFI TETHER WORKS
USB DATA WORKS
CAMERA WORKS
Every damn thing works lol thats what im trying to say. even if it has minor bugs which i have not seen yet, this setup and speed with battery life is the BEST, i dont even wanna risk something going wrong so i may leave this as my PERMANENT configuration.
*Edit* before you post saying the speed is slow, TRY IT OUT, Try the android ROM i posted with the set cpu settings i posted, and you will SEE for yourself* I tried the same settings on other android roms but they were just not good since battery was bad and data speed was bad so try that SPECIFIC ROM, see how you like it.
Thanks for the detailed info hakeem, I'm in Chicago too so I can use your exact configuration which is awesome.
Are you using PPP or RMNET build?
Which version of Miri rom? GTX/Max/CHT? Did you see Miri released a new Android launch Rom, here http://forum.xda-developers.com/showthread.php?t=778398. Wonder if that would give similar results with a quicker launch and more memory?
well considering you set the cpu to 1/2 what it's capable of, I'm not surprised you're getting longer battery life. At 600 mhz it runs like my Nokia N97; very poorly.
I've tried those settings before (minus the 600 mhz max) and they don't really give me much, if any real savings. I still get about 4 hours of heavy use or 8 hours of moderate. Not great but manageable.
I use Shubcraft 1.5 with 31 aug zImage on chuckydroid rom. It's the only setup that actually works for me. Data is intermittently flaky but it gets me 2000-3000++ kbps.
The only thing I would like to really have fixed is the G sensor and slightly more reliable data.
ounkeo said:
well considering you set the cpu to 1/2 what it's capable of, I'm not surprised you're getting longer battery life. At 600 mhz it runs like my Nokia N97; very poorly.
I've tried those settings before (minus the 600 mhz max) and they don't really give me much, if any real savings. I still get about 4 hours of heavy use or 8 hours of moderate. Not great but manageable.
I use Shubcraft 1.5 with 31 aug zImage on chuckydroid rom. It's the only setup that actually works for me. Data is intermittently flaky but it gets me 2000-3000++ kbps.
The only thing I would like to really have fixed is the G sensor and slightly more reliable data.
Click to expand...
Click to collapse
Try HyperDroid, Pongster just updated it. It's very similar to Shubcraft but I have the Gsensor on (and using it frequently) without a single screen freeze. Data has been solid and quick. I didn't like the Hi-res small image/text look that was built in but it was an easy fix to get that back to normal size, now the build looks and runs perfect.
Personally I like Sense, mainly for the email and agenda widgets, but the stock froyo builds are a lot more stable so I think I'm gonna stick with it for now.
"Sorry, not sure if this is int he right section but".....then why did you post it here instead of general section but thats your choice , second i would rather deal with a screen freeze here or there , than turn off auto sync and third that is really slowing your phone down with those setcpu settings , i agree with ounkeo thats half the phone speed...
but thanks any way
Thank you! I will follow your suggestion and feedback later.
Hey Im Chicago too!!! Well the burbs actually...
I solved my wake up issues by using setcpu and setting a profile for screen off 798 max 499 min scalingn demand and priority to 100
I know it high but from what I remember with the G1 and setcpu if you underclocked it it would freeze up. So thats what Im assuming with this as well. If its underclocked it will become non responsive eventually. I could be wrong but it my persoanl opinion and preference.
Well, you got lucky with 3-10ma on standby, so your battery doesn't suck. Try few reboots and come back with the same numbers - GL on that.
So far I've tried every trick to get the magic 3-10ma on standby, and sometimes I get it, sometimes i don't. Simple reboot screws it up, and when it goes up to ~60, goodbye every-day use of android
why bother ?
Might as well get a crap monochrome nokia then youll get 5+ days of battery life.
all you guys are doing is turning a smart phone into a dumb phone.
Do you have any issues with the internet on this setup?It seems on my set up the data indicator alternates between h and 3g all the time and can use any internet radio apps since it interrupts every few minutes.Also call quality would like to be a little louder.I have the stock radio 2.10.50.26,chuck rom lite for android and the latest 2.2 froyo stone 1.7.
Can anybody tell me what changes should i make ????
kardas666 said:
Well, you got lucky with 3-10ma on standby, so your battery doesn't suck. Try few reboots and come back with the same numbers - GL on that.
So far I've tried every trick to get the magic 3-10ma on standby, and sometimes I get it, sometimes i don't. Simple reboot screws it up, and when it goes up to ~60, goodbye every-day use of android
Click to expand...
Click to collapse
I am using shubcrafts 1.5 rmnet I get between 3-10ma while sleep. I wont except anything else. If i get the dreaded 40-60ma's I reset and I dont restart one its in the groove.
I noticed when I had the engadget widget going I would see 41ma in sleep mode.
I dont use auto sync because I can sync when I'm good and ready. I also dont turn off 3g anymore It isnt needed.
As far as the op's settings I think they are ok for him, I constantly clock my cpu at 768 as I have found it is responsive enough for me. I also use ondemand with a powersave bias of 500.
Hakeem5 said:
I also installed advanced task killer, not sure if it helps but my battery has been great since. Settings on there:
AUTO START checked, Show notification checked, Auto Kill Level: SAFE, AutoKill frequency when SCREEN OFF, Security level HIGH. OF COURSE you will have to put various apps on IGNORE so task killer doesnt kill them when the screen is off, so far i have ignored: App Brain, Advanced Task Killer(MAKE SURE TO PUT THIS ON IGNORE OR ELSE IT WONT WORK BECAUSE IT WILL KILL ITSELF lol), SetCPU, SUPERUSER, Google search, ad free, k9 mail and battery indicator pro.
All on ignore so they dont get killed, and i noticed ALOT of people use task killer but forget to put superuser, setcpu and advanced task killer on the ignore list so they may be getting closed out sometimes, which will make them ineffective for you.
Click to expand...
Click to collapse
Would someone please tell me how the f**k I could put apps o IGNORE?
the other battery thread found that having your keypad lights on before you boot into android and your sd card also impact heavily on your battery life.
vysus said:
Would someone please tell me how the f**k I could put apps o IGNORE?
Click to expand...
Click to collapse
when in the task killer app just hold down on the selected app to bring up menu
Thanx my friend
Good effort posting your findings, I'm sure it will help a lot of people...
I've played with SetCPU for a while trying a few things and found this setup to be the best for me:
I use the undervolted kernel from here.
I use SetCPU as follows:
Main Page
Max: 1113600
Min: 245000
Scaling: Interactive
Set on boot enabled
Profiles
Enable and Notifications checked
Screen off
max: 245000
min: 245000
scaling: interactive
Priority: 100
Charging/Full
max: 111300
min: 245000
scaling: interactive
Priority: 50
Battery < 25%
max: 652000
min: 245000
scaling: interactive
Priority: 50
Advanced tab
Min Sample Rate: 50000
I also have Autokiller installed with moderate settings. Remove all other task killer apps, including Advanced Task Killer...more info why HERE.
I use APNdroid to disable data connection when I'm not using it. But have wifi on all day.
kardas666 said:
Well, you got lucky with 3-10ma on standby, so your battery doesn't suck. Try few reboots and come back with the same numbers - GL on that.
So far I've tried every trick to get the magic 3-10ma on standby, and sometimes I get it, sometimes i don't. Simple reboot screws it up, and when it goes up to ~60, goodbye every-day use of android
Click to expand...
Click to collapse
I can confirm that having the keypad lights ON when starting up Android from WinMo does definitely keep standby at 3-10ma. The other thing you need to do to keep that level of drain is to switch off GPS unless you're using it.
My speculation tells me that there must be something wrong/missing with the gps and keypad light libraries after the dev's modified it to work on the HD2.
Oh yeah and this is on Darkstone's HD2Froyo v2.1
Hakeem5 said:
- Special settings in Android: Note: i turned OFF Auto sync, no gps, no facebook sync, weather or news sync.
1. Installed Set Cpu (Free to download on xda but i paid for the donate version to support the dev)
2. Set Cpu settings are in the PHOTO BELOW but as a recap
a. Click Autodetect
b. On MAIN tab, i set the max . . . .
Click to expand...
Click to collapse
nice try but with that "configuration" it would be better if i go back and use my
nokia of 4 years ago. thats no smartphone
Hakeem5 said:
Hakeem5 said:
- Special Settings in Windows Mobile: Turn off Auto backlight in windows mobile, turned of sync, weather, facebook, all that stuff that may secretly be on by default in windows mobile.
Click to expand...
Click to collapse
thats a better idea, this worked for me thanks for sharing us your discovery
Click to expand...
Click to collapse
kardas666 said:
Well, you got lucky with 3-10ma on standby, so your battery doesn't suck. Try few reboots and come back with the same numbers - GL on that.
So far I've tried every trick to get the magic 3-10ma on standby, and sometimes I get it, sometimes i don't. Simple reboot screws it up, and when it goes up to ~60, goodbye every-day use of android
Click to expand...
Click to collapse
hey bud, i was having the same issue as you. However, i'm pleased to say that doing the following has given me a 3-10ma standby over the course of a week with multiple reboots (just to check if it would work again). I pulled this from the "possible solution for heavy battery drain thread"
"If you start Android don't use WM at all, use auto-boot on 6 sec with Exceller Multiple Build Loader for Android/Ubuntu if you want to use windows, use it but reboot the phone before you start android."
I'm using this with an Energy Rom, 2.10 radio, and warrenb213's t-mobile us optimized build. Works a treat, hope you have the same experience
Ps... Doesn't matter if setcpu is enabled or not, I still get 3-10ma on standby, remember if you have autosync enabled you will occasionally get a spike while the phone syncs.
hazard99 said:
I am using shubcrafts 1.5 rmnet I get between 3-10ma while sleep. I wont except anything else. If i get the dreaded 40-60ma's I reset and I dont restart one its in the groove.
I noticed when I had the engadget widget going I would see 41ma in sleep mode.
I dont use auto sync because I can sync when I'm good and ready. I also dont turn off 3g anymore It isnt needed.
As far as the op's settings I think they are ok for him, I constantly clock my cpu at 768 as I have found it is responsive enough for me. I also use ondemand with a powersave bias of 500.
Click to expand...
Click to collapse
How can you see your power consumption in ma?
Well, it worked with three other testers, some friends of mine that found the same problem. If you're facing this, try and feedback me. Just want to make sure that I've helped someone.
This guide is for those who have the 0% battery issue, found the fix by Bazoocaze (thanks a lot !!!) and are experiencing some quick battery drain. If you're not, then you can go read something else In two or three weeks of testing, I believe that this does not have something related to the ROM that we're using. The processes on background and the use of CPU is relative, but maybe a process is using too much energy, and if we keep the energy level on a low status, I think this process won't have so much energy to use. And maybe the kernel, or the kernel's governors are affecting something, not sure of this last one. I've also concluded that this don't have anything to do with the Wi-Fi modules, because I've already tried that fix, and it drains pretty quick anyway, some believe that there is a bug affecting the Wi-Fi, and it doesn't turn off, even if we turn it off on the menu.
First of all, if you haven't find the fix, read this: http://forum.xda-developers.com/showthread.php?t=1312398
You can also use the DooMKerneL ICS v4 that DooMLorD developed, and it already has the patch built-in (I recommend for this guide): http://forum.xda-developers.com/showthread.php?t=1520654
1 - Flash the kernel, the one of Bazoocaze or the DooM Kernel
2 - Turn on your phone, normally, make all your configs, and do a little test, BEFORE following this guide. See how many time your battery can hold on. If you feel that it's going out too fast, keep going on the guide.
3 - For this operation, I suggest you buy or download the free version of SETCPU, never forget that name. NoFrills didn't work very well to me..
4 - Overclock, if you want and if you're using DooMKerneL. Keep the MHz min on 364 (will explain later)
5 - Go to the profiles tab and press the ''plus'' button. Change the MHz max to 768 and keep the min at 364. In profile, select Screen Off, and change the governor to powersave or smartass and set priority to 100%
6 - Save it, and press Enable and Notifications on the bottom of the screen.
7 - Now test it for some time. Try not to keep your screen always on, as it ''cancel'' the effect of this guide.
Explanations:
a) The reason to keep the min MHz at 364 is that you won't face stuttering in the screen on/off, because the app will only change the max value, and not the min value, which makes the system still work fine (I believe, if some dev could correct me..). It behave better in AOSP alike roms.
b) NoFrills didn't give me the same results as SetCPU, that's why I'm recommending SetCPU. Make some effort to buy the Pro app.
c) The main trick is to reduce the power usage and capacity when the screen is off, because you don't use your phone 100% of the day, and because the process that may exist (mentioned above) would not use the whole capacity of the energy and the CPU as well. That's why it works. At least worked for me.
d) There is absolutely no hardware of software issue if you try this guide, you can uninstall the SetCPU app and use kernel other than DooM's. It's safe and quick, if it doesn't work, you can always revert everything.
Please, if you want to try this guide, give me the feedback. As I've said, I just want to confirm that theory and make sure that I've helped someone.
Thanks Bazoocaze and DooMLorD for being life savers!!!!!!!!
Bye
Thanks for your help
Sent from my LT18i using xda premium
Hello.
Undervolting your CPU has always been a daunting task - there's so many CPU steps, if you pick say -100mV to all frequency steps and you get a reboot, how do you work out which step (or steps!) is causing the problem? If you undervolt -25mV on one frequency, then wait a couple of days to make sure it's stable, then reduce the same frequency by another 25mV.. you'll still be undervolting a year later.
This thread is my tutorial on how to do a best effort at quickly and safely undervolting your phone CPU.
First of all - is undervolting your CPU worth it?
Initially it was thought not to make much difference, but after some serious testing (thanks AndreiLux), "we" decided that it was a good idea. I also did my own basic testing, and it looks like it's worth it.
What are the advantages of undervolting?
Better battery life
Cooler phone, especially useful if you overclock your CPU
What are the disadvantages of undervolting?
That's the great thing! Really the worst that can happen is your phone freezes or reboots. The steps below should eliminate all of that. Once you have undervolted your CPU to just above its freeze/crash levels, there are no disadvantages!
Note: I have had some minor data loss (eg an app forgets a setting) after an undervolting related crash, but it was rare and I believe has to do with the Perseus kernel "Enable dynamic FSync" setting. I note below how to mitigate against this.
What do you need?
A rooted phone, and a kernel that supports undervolting. Perseus and Siyah will work, but any kernel should be fine that supports SetCPU's undervolting schema
SetCPU or you can use a combination of STweaks and Stability Test (use STweaks for setting the frequency and voltage, and use Stability Test's Classic Test for the stress test)
A paper and a pen - I used Sticky Notes as I was at a computer for most of the process
Some patience
Let’s begin.
Open SetCPU. You’ll be greeted by the Main screen which has the min/max CPU frequencies, the governor options, and the IO scheduler options. Reduce the max CPU frequency to the lowest step. On the SGS3 this will be reducing 1400MHz down to 200MHz, so you now have both the min and the max set at 200MHz. The phone will get pretty slow at this point. Ensure the Set on Boot option is unticked
Set the governor to Performance (note: you have to make sure all cores of your CPU are being used. In a complex kernel such as Perseus, you'll have to go into STweaks and set the CPU hotplug lock to 4 so all 4 cores are used. Also note there appears to be a bug in Perseus at the time of writing: you have to set the hotplug lock BEFORE you change the governor to performance)
Move to the Voltages screen
Ensure the Set on Boot option is unticked, and scroll down to the lowest setting, and change it to something low, like 700mV, and then apply it (click the third icon from the right at the top of the screen, a rectangle with a tick on it) . This first setting is always a bit of guess and check, and to be honest you’re hoping for the phone to freeze or crash on this first one. Has it frozen? If so move on to the next step. If not, reduce it by a further 25mV and apply again, repeat until your phone freezes or reboots.
So, you have undervolted too far. Reboot the phone, and perform steps 1-3 again. At step 4, use the voltage that crashed your phone +25mV (eg if it crashed at 675mV, this time set it to 700mV). Now, you have a very slow phone running a low voltage that doesn’t immediately crash it. Move on to the next step
An easy crash test I found was simply allowing the phone to go into deep sleep, and waking it up again. To do this, unplug your phone if it’s charging, and turn the screen off. At this point I usually wrote the time down on my piece of paper, as well as what frequency and voltage I was testing as I’m prone to forget these things. Wait 5 minutes with the screen off (and make sure no notifications have come in while the screen is off – this wakes the phone up and you’ll have to wait another 5 mins), then turn the phone on. You’ll know it’s gone into deep sleep as there’ll be a slight delay before the screen turns on as compared to no delay when turning it off and immediately back on again. If the phone doesn’t turn on, go to step 5. If your phone comes out of deep sleep OK, move on to the next step.
Now, we stress test. In SetCPU scroll over to the Info screen, and scroll down to the Stress Test option. Start it, and note down the time on your paper/Sticky Notes. Your CPU will now run as hard as it can at the current frequency. Let it run for 15-20 minutes. At the lowest frequency it will be pretty laggy and slow, if you think it has frozen always give it 30 seconds to see if it picks up again. If it gets stuck for over a minute, you probably have a crash. Go to step 5. If after 15-20 minutes it’s still running, you have found your first stable(ish) voltage for that frequency! At this point I saved the voltages in SetCPU by pressing the diskette icon. To ensure the changes are written to disk turn the phone screen off for 5 seconds then turn it back on again.
We are now ready for the next frequency. There’s pretty much no way a frequency will run stably on a lower voltage than a frequency below it, so our first voltage for the next frequency up should be the same stable voltage we found for the previous frequency. For example if we found a stable voltage of 725mV on the 200MHz frequency, our first test voltage for 300MHz should be 725mV. Write this down with the frequency on your paper. In the Main screen of SetCPU, change the max frequency to the next step up. Then, in the Voltages screen, adjust the voltage to be the same as the lower frequency, as discussed above. If your phone immediately freezes or reboots, move to the next step. If not, go to step 10.
So, you have undervolted too far, again! Reboot your phone, open up SetCPU, and in the main screen ensure the max frequency is set to the frequency we’re testing. Give the sliding bar things a jiggle to apply it. Ensure the governor is set to Performance by pressing it on the lower left part of the screen. Move to the Voltages screen, and you’ll either see your previous “saved” voltage values ready to be applied in dark grey under the “current” voltage settings, or you’ll have lost your “saved” voltage settings. If you have lost them, never fear; just restore the latest settings by clicking the first from the right icon at the top (a square with an arrow pointing outwards). Adjust the frequency we’re testing’s value to 25mV more than the value you last used when it crashed, and apply it. If it crashes immediately, repeat this step. If not, move on
We now start the two tests in steps 6 and 7 again, but this time if your phone crashes or freezes, go to step 9. If it completes the deep sleep and stress test tests, go to step 8 for the next frequency test.
Sorry for the complexity here, but it was the easiest way I could write it without repeating myself too much. The TL;DR version goes like this:
Pick the lowest untested frequency, set the max frequency to this and the governor to Performance, and find the lowest voltage that doesn’t immediately crash the phone
Put the phone into deep sleep, and see if it crashes. If it does, increase the voltage for the current frequency we’re testing by 25mV and test again. If not, move on
Run a stress test on the phone for 15-20 minutes. If it crashes, raise the voltage by 25mV and go to step B. If it doesn’t crash the current frequency is now tested. Go to step A
You now have a set of frequencies that shouldn’t immediately crash the phone. Set the min and the max frequencies back to normal, and set the governor back to your usual governor. At this point for me I was able to use the phone for about 2 hours before I had my first crash. How running a stress test on each frequency for 20 minutes didn’t pick up this crash situation I’m not sure, but it didn't.
After screwing around for a while I found the easiest solution was to just raise each frequency step by 25mV and then continue every day usage. That was enough to stabilise my phone. If it still crashes for you, keep raising all the values by 25mV until it settles down. After a day or two of no crashes you can start slowly one by one reducing each step by 25mV again to find out which step caused the crash.
After that, you should be done!
Ps I know there is another thread around here discussing undervolting, but I found it too vague on the details and sometimes wrong, so I thought I’d share my experiences in the hope it might help.
Good work!
Would you pls post your testing results for our reference?
Thanks.
Mod edit: please do not quote the OP.
A table with the running undervolting settings would be a great orientation help. Given that, people don't need to trail and error from scratch.
Sent from my Nexus 4 using xda app-developers app
me_max said:
A table with the running undervolting settings would be a great orientation help. Given that, people don't need to trail and error from scratch.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Under/over volting doesn't work that way. Each chip is unique, and chips are tested only on default voltage and frequencies, so each one's behavior on non-default settings is unpredictable. Some are able to work on 100 mV lower voltage, some can't handle even -25mV... Trial and error is the core of overclocking.
yep, that's one of the reasons i disagreed with the other UV thread - they list absolute voltage levels which are only applicable to the specific grade of chip in their phone (and yes, I posted some corrections in the other thread but they were ignored).
Have a look HERE if you'de like to see all the different possible default voltage settings for the i9300/i9305.
As a rough rough guide of a voltage level for the 200MHz step that will (hopefully) crash your phone, I'd start at 650mV.
i have tested my cpu
for stable values and i finished with these settings:
200Mhz - 0.775V
300Mhz - 0.800V
400Mhz - 0.825V
500Mhz - 0.850V
600Mhz - 0.875V
700Mhz - 0.900V
800Mhz - 0.925V
900Mhz - 0.950V
1000Mhz - 0.975V
1100Mhz - 1.000V
1200Mhz - 1.050V
1300Mhz - 1.100V
1400Mhz - 1.150V
1500Mhz - 1.200V
My exynos is stable for 2 months now, i play a lot of new games like most wanted etc.
In UV more important is leaving phone in idle, deep sleep on and off, or non demanding tasks, if i UV too much games were stable but i had random restarts when phone was in the pocket sleeping. But, as You mentioned, every cpu is different so everyone has to test it...
Thank you OP for this very, very useful guide. I am new to undervolting and even though I have a T999V north-american model with the Qualcomm SoC, this will prove very useful in my experimentation.
Only difference with the Qualcomm is that clock speed can go as low as 96Mhz, but you can't undervolt under 700mV - SetCPU just refuses to apply anything under that.
No probs
That's a kernel limitation, not SetCPU. Check with your kernel dev to see if they can allow further undervolting.
I tried to make the instructions as generic as possible so any stepping config could use them. good luck!
I'm doing my 96Mhz test and running a stress test.
The loading circle is still moving just fine (although a bit sluggishly) but none of my buttons are responding at all so I cant leave the test until I pull the battery. Would this count as a freeze/crash, or do you think this voltage is okay to stick at (or even go lower?!)
That's just the CPU bogging down, it's not a voltage issue.
hi guys. this might sound like a dumb question but i honestly looked everywhere but i cant seem to find the UV in setcpu. i'm i missing something?
Probably the kernel you're using doesn't support UV.
Hey
I find that 200 is stable on 687500
And then when I move to edit 300 it reboots
Then increased the number on both and still reboot.
I don't restart in between. Any idea??????
Sent from my GT-I9300 using xda app-developers app
tony1234567890tony said:
Hey
I find that 200 is stable on 687500
And then when I move to edit 300 it reboots
Then increased the number on both and still reboot.
I don't restart in between. Any idea??????
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
That means that 200 is NOT stable. Try using a higher voltage. 0.6875v is ridiculously low
TP.
What do you mean low he says in the op to reduse to 700
THC for fast answear
Sent from my GT-I9300 using xda app-developers app
tony1234567890tony said:
What do you mean low he says in the op to reduse to 700
THC for fast answear
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Default voltage for 200mhz step is 0.9v (for me on asv2). So 0.7v (which is still higher than what you have set) it a whopping 200mv less than stock which is like I said before, ridiculously low. It may run at this voltage for you for now(depending on your as level), but I can pretty much guarantee you that it will never be 100% stable
I'll take your THC ; ) lol
TP.
Thanks I'll give you feed back
Sent from my GT-I9300 using xda app-developers app
omniwolf said:
Probably the kernel you're using doesn't support UV.
Click to expand...
Click to collapse
i thought the matr1x kernel supports it. UV works fine in trickster mod. i don't even have a heading for 'voltages' in the the app like it's shown in the play store.
tony1234567890tony said:
What do you mean low he says in the op to reduse to 700
THC for fast answear
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
yep, as STAticKY says, if you get a reboot on a step, then it's not stable. raise the voltage on that step and try again.
STAticKY said:
Default voltage for 200mhz step is 0.9v. So 0.7v (which is still higher than what you have set) it a whopping 200mv less than stock which is like I said before, ridiculously low. It may run at this voltage for you for now, but I can pretty much guarantee you that it will never be 100% stable
I'll take your THC ; ) lol
TP.
Click to expand...
Click to collapse
This is only correct for your ASV value. Please edit this post, it contains incorrect information. Your default voltage for 200MHz might be 0.9v, but for other people it's likely different, as they have different quality chips. Read post 3, 4, and 5 in this thread for more info.
genericuser2013 said:
i thought the matr1x kernel supports it. UV works fine in trickster mod. i don't even have a heading for 'voltages' in the the app like it's shown in the play store.
Click to expand...
Click to collapse
possibly the matirx kernel does support UV, but it might not be exposed in the way that SetCPU is expecting. Does the Matrix kernel developer recommend a specific app to adjust the voltages? If so use that, you can still follow my guide.
Can anybody tell me how to determine ASV-level of my chip?