Develop Bugs

SetCPU for Kaiser

Hey everyone,
i just read about the SetCPU app on the front page of xda-developers.com
Does this work for Kaiser too? or would it be safe to use it on the kaiser?
thanks nick

the-nj said:
Hey everyone,
i just read about the SetCPU app on the front page of xda-developers.com
Does this work for Kaiser too? or would it be safe to use it on the kaiser?
thanks nick
Click to expand...
Click to collapse
No. Dont...really dont

I tried a few weeks ago, but instead of running my android freezes... :S

Does this overclock the CPU if so this was bad juju sometime last year was causing funky things to happen when overclocking was added to the default.txt

http://ponack.net/poly/oc/
Script must be run as root. 528 is the fastest stable overclock I can achieve. Sometimes OC lockups will corrupt all your data. I don't recommend OCing at boot/system load unless you're really sure about it. I am not supporting OCing or this file. Every system is different, OC your device at your own risk.

polyrhythmic said:
http://ponack.net/poly/oc/
Script must be run as root. 528 is the fastest stable overclock I can achieve. Sometimes OC lockups will corrupt all your data. I don't recommend OCing at boot/system load unless you're really sure about it. I am not supporting OCing or this file. Every system is different, OC your device at your own risk.
Click to expand...
Click to collapse
I've been running ahb_div=4 & a11=500 all day, and it seems to be alright... The only problems I've had is when it's plugged in, as soon as I unplug it while it's asleep it locks up. A soft reset fixes it just fine, but not sure how alarms/etc. will work while its plugged in. maybe just simply waking it before unplugging will be fine.
NOTE: Everytime I reboot the phone, I need to reapply those settings.

polyrhythmic said:
http://ponack.net/poly/oc/
Script must be run as root. 528 is the fastest stable overclock I can achieve. Sometimes OC lockups will corrupt all your data. I don't recommend OCing at boot/system load unless you're really sure about it. I am not supporting OCing or this file. Every system is different, OC your device at your own risk.
Click to expand...
Click to collapse
How do you run this as root? Do I just need to su, then ./oc.sh?

Pandemic187 said:
How do you run this as root? Do I just need to su, then ./oc.sh?
Click to expand...
Click to collapse
That sounds right. You might have to use chmod to make it executable, too.
Even so, I understand you can brick your device doing all this?
Doesn't sound worth the risk. A little bit more speed in trade for instability and risk of bricking your hard-to-replace Kaiser.

aikeru said:
That sounds right. You might have to use chmod to make it executable, too.
Even so, I understand you can brick your device doing all this?
Doesn't sound worth the risk. A little bit more speed in trade for instability and risk of bricking your hard-to-replace Kaiser.
Click to expand...
Click to collapse
Well, I can't flash to NAND - I'm still using HaRET, so I don't think that would be a problem for me.

If you put the script on your SDcard you don't have to chmod it since FAT partitions don't have permissions, the files are all 777. It'll only corrupt your Android data if it corrupts anything, so backup your Android data first. AFAIK no one has actually permanently damaged the Kaiser using reasonable overclocks.

polyrhythmic said:
If you put the script on your SDcard you don't have to chmod it since FAT partitions don't have permissions, the files are all 777. It'll only corrupt your Android data if it corrupts anything, so backup your Android data first. AFAIK no one has actually permanently damaged the Kaiser using reasonable overclocks.
Click to expand...
Click to collapse
After one lockup, my Android data was corrupted. I probably won't be doing this again.

How to use this script?
I copy it to SDCard and open via "Root Explorer" ("Execute" Command).
I see message "oc.sh executed" but in my opinion overclocking not exist.

DmK75 said:
How to use this script?
I copy it to SDCard and open via "Root Explorer" ("Execute" Command).
I see message "oc.sh executed" but in my opinion overclocking not exist.
Click to expand...
Click to collapse
I have to voice a second opinion on this.
I urge you not to do this if you need your phone as a daily user, Th effects of overclocking are minimal at best anyways, the phone not waking up is one of the reasons 99% of us quit using this a very long time ago. I dont think anyone has permanently bricked their phone YET but its bound to happen. I would think that continually reloading a data backup would get very annoying atleast it did for me. I havent overclocked probly close to a year now and see no reason too even running polymods eclair. If your running myns donut there is absolutley no reason to at all. But if you so desire then go right ahead and hope for the best. And to the one that metioned his phone locking up no your alarms won't work if you overclock your phone don't count on its reliability.

is anything dangerous on overclocking Kaiser?
and whaat is max frequency? 528MHz?
Default is 400MHz

garringm said:
I havent overclocked probly close to a year now and see no reason too even running polymods eclair. If your running myns donut there is absolutley no reason to at all.
Click to expand...
Click to collapse
I already use "polymod 2.1g" and this build need to overclock.
But this script cannot make it.
I seen real overclock only on previous versions mssmison`s eclair: system tools shows 507MHz and device works faster than usual.

The script works, your device needs to sleep and wake before it takes effect. If you want to see the quantitative difference download Linpack or CaffieneMark for Android Every device is different, I can OC and everything works fine (99% of the time) but almost everyone else has trouble. Vogues seem to have it easier -- YMMV.

how i can overclock myn donut?

I'm 90% complete on my Android application that overclocks and changes lcd density within Android. It also works on the Kaiser
Stay tuned.

polyrhythmic said:
AFAIK no one has actually permanently damaged the Kaiser using reasonable overclocks.
Click to expand...
Click to collapse
Once I get my native android device in a few months maybe I'll just have to see how durable the kaiser is. a couple more drops or dings in the touchsreen and itll be pretty much useless anyways

Root + OC widget = 2 days of battery??

Ok, I am suspicious of all things people post at first until its verified, but here is the link of someone who says its fact.
http://androidforums.com/all-things...clockwidget-insane-battery-life-40-hours.html
My question, is this legit and if so are there any potential pitfalls from setting the EVO like this?

Looks pretty interesting, hopefully some more people will test this out.

Is there a log to verify it is changing the CPU speed? I know there was something like that on the Pre, but it didn't always set the CPU speed down.

Testing
Just installed it. Will post my results in the next few days.

Did you use toast's method of rooting or unrevoked?

Ikyo said:
Is there a log to verify it is changing the CPU speed? I know there was something like that on the Pre, but it didn't always set the CPU speed down.
Click to expand...
Click to collapse
There is a notification option that tells you every time the CPU changes frequencies.

Which root method did you use?

I am also trying it out - I'll update you all in a couple days. I have it installed, it says that the frequency change was successful, so I guess we'll see...

Whats the app that tells him 21 HRS?

I am using toastch root with his froyo rom. Overclock widget doesn't officially support 2.2 yet, so my results might be worse than 2.1 stock. Worth a try anyways.

I might go ahead and install unrevoked on mine to try it. I am getting great battery life as it is now.

I believe that neither SetCPU or overclock widget will work properly unless you use a kernel with my patch.

WIthout the patches, what is the application actually doing if anything?

Ikyo said:
WIthout the patches, what is the application actually doing if anything?
Click to expand...
Click to collapse
It's setting the speed... Then the speed reverts itself immediately because of HTC's modifications to the kernel.

Okay, I will not worry about using it then. I guess the phone just has that good of battery life.

coolbho3000 said:
I believe that neither SetCPU or overclock widget will work properly unless you use a kernel with my patch.
Click to expand...
Click to collapse
How do you apply this patch

Shadow591 said:
Whats the app that tells him 21 HRS?
Click to expand...
Click to collapse
Battery Indicator...In the Market

hahah i got a pic of my hero on a 3days and some odd minutes off the charger.

So this app does help? Or does not? Using it I'm at 4 hours at 60%... Not much use, a few texts and a few phone calls, and like 3 webpages.

help a noob out?
Can anyone explain how one goes about installing this patch? And maybe use small words for us rookies?

[Guide] How to Root / Overclock T-mobile Official 3.6.390 Rom

Here is a simple step by step guide to rooting / overclocking your updated Defy. If you are like me you upgraded to the new OTA (over the air) firmware only to lose your root access / overclock
As with any free advice given out on XDA, if your phone gets borked and / or something goes wrong while you are trying to root / overclock, I do not work for Motorola and I take no responsibility for your $500 brick.
ROOTING PROCESS STEP BY STEP
1. Download and install the Motorola Mobile Phone USB Drivers (for Windows®)
http://www.motorola.com/consumers/v/index.jsp?vgnextoid=bda09ec8009a0210VgnVCM1000008806b00aRCRD
2. Download and Unzip SuperOneClickRoot (thanks to SteveChou)
http://forum.xda-developers.com/attachment.php?attachmentid=489694&d=1295035181
3. Make sure have usb debugging checked on your phone (menu - settings - applications - development - check usb debugging)
4. Plug your phone into your PC and put your phone's USB connection into "Portal and tools" mode. (After youplug your phone in, pull down the notification bar, click on USB connection then toggle Portal and tools.) and close any Motorola Portal Windows that pop up.
5a. XP USERS ONLY:
Make sure you are logged in with an administrator level user account and run the SuperOneClick.exe file that you extracted in step 2. Then Click Root (The whole process takes less than a minute.)
5b. VISTA/7 USERS ONLY:
Right click on the SuperOneClick.exe that you extracted earlier and click Run as Administrator. Then Click Root (The whole process takes less than a minute.)
OVERCLOCKING PROCESS (These are the setting I have been using for a few days with no lockups / force closes YMMV):
1. Go to Market on your phone and download SetVsel
2. Run SetVsel and input the following settings:
28 [email protected] MHZ
44 [email protected] MHZ
58 VSEL3 @1100 MHZ
Check Apply @ Boot Toggle
3. Click Apply+Quit
That's All Folks!

i use milestone to oc my defy is SetVsel any better? did a quad run at 1.3ghz got a nice score

S1dew1nder said:
i use milestone to oc my defy is SetVsel any better? did a quad run at 1.3ghz got a nice score
Click to expand...
Click to collapse
I tried milestone for a few days, but I've noticed better battery life with SetVsel. I was barely making it through the day (7am - 8pm) with Milestone, Setvsel seems to get me through the night. Then again, who knows maybe I was just using it more that week.

cheers dude think you maybe right looking at your settings the voltages are lower than the defults set by milestone think ill give it a go see how i get on

S1dew1nder said:
i use milestone to oc my defy is SetVsel any better? did a quad run at 1.3ghz got a nice score
Click to expand...
Click to collapse
What are your settings if you don't mind?

bobbyphoenix said:
What are your settings if you don't mind?
Click to expand...
Click to collapse
np I've got the vsel set to 65 for 1.3ghz that's the only setting i changed as i didn't know what the other 2 did lol

S1dew1nder said:
np I've got the vsel set to 65 for 1.3ghz that's the only setting i changed as i didn't know what the other 2 did lol
Click to expand...
Click to collapse
Thanks. The other two as I understand are like this: First one at 300 is for when the screen is off. It runs the lowest possible to conserve everything. The second one is when the screen is on, so the phone can do what it has to without lagging. The third one is the max the phone can run, so you can run whatever you want, and not worry about slowness or lagging as it will use what it needs up to the max setting. People I see do what you did and just overclock the max to get the full potential out of the chip. The ones that change the first two either want even better battery life, or a little more power midrange when the phone is just on doing its normal stuff. Me, I am using inteks settings on the first page in the screen shot, 300 @30, 700 @54, 1200 @70. Super smooth with heavy load. Scored 1218 on Quadrant. Very stable and I'm happy.

AWSOME
Did the rooting super fast got it under 20 sec lol but just installed SetVsel and app is force closing on me
Edit: Nevermind just rebooted the phone now its working very fast rooting and overclocking

Does rooting the phone this way require the 3G fix after root?

3g fix? ??? I havent had any problems since rooting and 3g is working like charm just like when i opened it brand new
Sent from my MB525 using XDA App

temp root + overclock
is it possible? use the temporary root option and then use it to overclock to 1ghz?
so that i can still unroot it in the future...

temporary root did nothing for me, had to use permanent root option
and u can stil unroot even if u use permanent option

which is better?
is this better than z4root? over 3.6.360 version?!
does it resets the phone or clear anything up after rooting?!
would you still be able to use tmobile's apps and features? like updates OTA in the future?!
thanks!

@lucid i have the same firmware version as you and it rooted fast and also dint erase anything from the phone left it as it is now from the ota updates i believe there not affected
Sent from my MB525 using XDA App

which one did you use? or would you say better? z4root or the superOneClick?
SuperOneClick v1.6.5 is the latest with "unroot" option right?!

I used superoneclick for 2.1 it says but I also have the new version that has the unroot option but havent tried it and z4root ive read that still doesnt work with the new firmware update
Sent from my MB525 using XDA App

rooted!
ok now i rooted my phone and it said SUCCESS in the end, that means it went OK right?
after this should i use milestone ot setvsel or setcpu? which one would you guys prefer?
i'm trying setvsel now nut it doest show me:
VSEL1
VSEL2
VSEL3
just the round lightning with slider bar and the rest of the messages
can i also uncheck the USB debugging now?
thanks!

Cool now your rooted the setvsel thing happend to me also just unistall and reinstall and that should fix it if not turn off phone and turn on again as i did and yes you can disable the debugging mode without problems
Sent from my MB525 using XDA App

hi again, how do you get the vsel set to 65 for 1.3ghz
all i'm getting aside from lower values of 800mhz are:
1000mhz, 74vsel
1200mhz, 80vsel
1200mhz, 80vsel (custom)
does vsel means the higher the value the more power it consumes compare to
yours set to 65?
oh btw, if i factory reset this, is it still rooted and overclocked?

The lower vsel value the less baterry ir uses bit might cause stabability issues and id you factory reset it stays rooted but overclocked i cant say cause the app is what controls the overclocking so i would guess it goes to factory clock
Sent from my MB611 using XDA App

[Help] Lots of freezes and crushes after updating to 4.0.5

Hi,
I've had my Archos G9 80 updated to the latest android official 4.0.5 from and since then i'm expriencing lots of crushes and freezes. I'm getting them randomly with no specific app working.
Also, i have tried to do full formats (Android + Data), and still having same issues.
Does anyone have any idea what else i can try?
Thanks.

I had lots of freezes too (not only with the latest firmware). They seem to be gone since I changed the CPU govenor from "hotplug" to "interactive". I'm not sure yet that it was the reason, but try it and let us know if it helps.

DeeDroid said:
I changed the CPU govenor from "hotplug" to "interactive".
Click to expand...
Click to collapse
how this is done? Ι have the same problem!

africa_twin said:
how this is done? Ι have the same problem!
Click to expand...
Click to collapse
Yes, can this be done from the phone itself? Within the ROM?

You can set this in any tool that is intended for overclocking. I don't overclock, I only changed the Govenor.
I use "SetCPU". ("No-frills CPU Control" should do the same.)

So does this have any other effects on the phone?

RichWPX said:
So does this have any other effects on the phone?
Click to expand...
Click to collapse
Nothing too serious. Your CPU is clocked dynamically so it doesn't run full speed when there is nothing to compute(save energy). To my understanding the govenor is basically a policy to manage how quickly the frequency steps up/down on changing CPU load. So "powersave" is supposed to save energy but make the system a little less reactive than "interactive" Governor for example. I think I read somewhere "hotplug" deactivates the second core on low load situations, I suspect for some strange reason my device might have crashed sometimes on trying to wake up the sleeping second core. Well maybe I'm wrong, that's why I'm interested if it helps others.
I didn't notice any change in battery lifetime, mostly it's the display anyway that drains the battery. Everything is running well, battery lifetime is great too and no crash/freeze at all since i changed that setting and it crashed almost every damn day before, no matter if it was Honeycomb or ICS.

I downgraded the device to 4.0.4 and since then, no crushes.. I guess for some reason 4.0.5 isn't stable on my device.. ill stick with this version unroll they get another one out..
To downgrade, just install official update file of the version you want to upgrade to..

DeeDroid said:
Nothing too serious. Your CPU is clocked dynamically so it doesn't run full speed when there is nothing to compute(save energy). To my understanding the govenor is basically a policy to manage how quickly the frequency steps up/down on changing CPU load. So "powersave" is supposed to save energy but make the system a little less reactive than "interactive" Governor for example. I think I read somewhere "hotplug" deactivates the second core on low load situations, I suspect for some strange reason my device might have crashed sometimes on trying to wake up the sleeping second core. Well maybe I'm wrong, that's why I'm interested if it helps others.
I didn't notice any change in battery lifetime, mostly it's the display anyway that drains the battery. Everything is running well, battery lifetime is great too and no crash/freeze at all since i changed that setting and it crashed almost every damn day before, no matter if it was Honeycomb or ICS.
Click to expand...
Click to collapse
Thanks! And I have notices ICS is not as snappy as GB was... I mean GB flew! Swiping the screen, it feels a little off now.

RichWPX said:
Thanks! And I have notices ICS is not as snappy as GB was... I mean GB flew! Swiping the screen, it feels a little off now.
Click to expand...
Click to collapse
GB? Gingerbread? Guess you mean Honeycomb. Anyway, I experienced ICS to be much better.

DeeDroid said:
I had lots of freezes too (not only with the latest firmware). They seem to be gone since I changed the CPU govenor from "hotplug" to "interactive". I'm not sure yet that it was the reason, but try it and let us know if it helps.
Click to expand...
Click to collapse
changing govenor from "hotplug" to "interactive" seems to help against random freezes. 4 days without problems until now i had freezes with ics, but never with honeycomb.
device: archos 101g9
[ROM] Archos ICS - Firmware 4.0.5(4.0.3) - ROOT & BUSYBOX , Only for SDE (thanks surdu_petru)

DeeDroid said:
I had lots of freezes too (not only with the latest firmware). They seem to be gone since I changed the CPU govenor from "hotplug" to "interactive". I'm not sure yet that it was the reason, but try it and let us know if it helps.
Click to expand...
Click to collapse
That seems to be my problem too. Setcpu requires root. is there a very easy way to do this, just to run this setcpu? There used to be a z4 tool, but can't seem to find it anymore.
Edit I see that I need superoneclick. Will temporary root suffice or will I need permanent root to change the governor setting.and keep it so.

Unfortunately all know temp root variants tend to brake things- im Honeycomb sound, in ICS 3d driver.
The only real option is to enable SDE and use custom firmware.
As for freezes- try reinstalling apps. Direct upgrade from Honeycomb does not work for all
tapatalked from Xperia Arc S

DeeDroid said:
GB? Gingerbread? Guess you mean Honeycomb. Anyway, I experienced ICS to be much better.
Click to expand...
Click to collapse
I have the same experience. Hc was laggy and slow. Ics is much faster and smoother.
Sent from my ARCHOS 80G9 using Tapatalk

gen_scheisskopf said:
Unfortunately all know temp root variants tend to brake things- im Honeycomb sound, in ICS 3d driver.
The only real option is to enable SDE and use custom firmware.
As for freezes- try reinstalling apps. Direct upgrade from Honeycomb does not work for all
tapatalked from Xperia Arc S
Click to expand...
Click to collapse
sorry for the n00b question, but SDE stands for ??? S ? Develeper Edition ?
Will "Superoneclick" not root my device ?

sbtwister said:
sorry for the n00b question, but SDE stands for ??? S ? Develeper Edition ?
Click to expand...
Click to collapse
Special Developer Edition
sbtwister said:
Will "Superoneclick" not root my device ?
Click to expand...
Click to collapse
No, it won't. Gen9 system layout is different than for most other devices

hey, back to topic
5 days without freeze with govenor "interactive". i witched back to "hot plug" this morning and had to reboot my tablet 2 times today. for my case, "interactice" seems to help against random freezes.

mines performance intstead of interactive... experienced some freezing n interactive..

Man I'm really pissed.
Yesterday I had to hard reboot 7 times
Sent from my X8 using xda premium

hmm,
sounds not good. archos stands not for high quality i guess. we get what we pay . i had an archos 101g8, now a 101g9 and trouble with hard-/firmwares since 2010. i think, this was the last one - no furthermore advantures
@IrishStuff09: you did reformat for ics or upgrade from honeycomb? the best way is to start from scratch and skip upgrades.

Benchmark problems

So just today, I realized I was under clocking my phone's CPU at 1920 mHz instead of the base clock speed of 2150 mHz which basically meant I was limiting its performance. Realizing this, I called myself an idiot and was also excited to see my benchmarks at base clock since its 165K using antutu when under clocked. So I changed my clock speed back to 2150 mHz and started benchmarking. All was going well until around 80% of the benchmark when the screen just instantly turned off and the notification light dimly lit up, no warnings, just instant. I can't interact with my phone until I forced restart it. I under clocked my phone again if it still has the same issue but benchmarking worked out just fine. Any idea why this happened and is there any fix? I really want to know my benchmarks at 2150 mHz ;-;
Ps: idk how to call website admins but please tell them to fix their website for PCs, can't even login since text boxes are missing, can't make a new thread since title input text box is missing when making new thread. Everything is fine on phone tho.

ZeeSmilez said:
So just today, I realized I was under clocking my phone's CPU at 1920 mHz instead of the base clock speed of 2150 mHz which basically meant I was limiting its performance. Realizing this, I called myself an idiot and was also excited to see my benchmarks at base clock since its 165K using antutu when under clocked. So I changed my clock speed back to 2150 mHz and started benchmarking. All was going well until around 80% of the benchmark when the screen just instantly turned off and the notification light dimly lit up, no warnings, just instant. I can't interact with my phone until I forced restart it. I under clocked my phone again if it still has the same issue but benchmarking worked out just fine. Any idea why this happened and is there any fix? I really want to know my benchmarks at 2150 mHz ;-;
Ps: idk how to call website admins but please tell them to fix their website for PCs, can't even login since text boxes are missing, can't make a new thread since title input text box is missing when making new thread. Everything is fine on phone tho.
Click to expand...
Click to collapse
Its kernel panic

JV Spartacus said:
Its kernel panic
Click to expand...
Click to collapse
Kernel panic? How can i fix it?

ZeeSmilez said:
Kernel panic? How can i fix it?
Click to expand...
Click to collapse
Reboot should fix it .If not install boot.img from the custom rom file u have installed or use custom kernel if u like

JV Spartacus said:
Reboot should fix it .If not install boot.img from the custom rom file u have installed or use custom kernel if u like
Click to expand...
Click to collapse
Im using nameless kernel. I now just remember having this same problem before and rebooting doesn't work, and i also remember that this problem is the reason why i underclocked my phone. The only thing that caused a kernel panic so far is antutu, probably geekbench too but i can't properly remember.

ZeeSmilez said:
Im using nameless kernel. I now just remember having this same problem before and rebooting doesn't work, and i also remember that this problem is the reason why i underclocked my phone. The only thing that caused a kernel panic so far is antutu, probably geekbench too but i can't properly remember.
Click to expand...
Click to collapse
If the phone temperature gets high it shuts itself to protect the device

JV Spartacus said:
If the phone temperature gets high it shuts itself to protect the device
Click to expand...
Click to collapse
Phone doesn't get really hot when benchmarking though