Related
As we know, overclocking MSM is possible now. Just check :
http://forum.xda-developers.com/showthread.php?t=725290
Click to expand...
Click to collapse
But the thread is over 1400 post & most of them are about blackstone, Rhodium, etc.. I think it's about time we make a thread about overclocking our Touch Pro(s)
I use GSM unbranded TP100 & TAEL v.5 ROM.
I'll start with my experience :
What Works
Click to expand...
Click to collapse
1. grab the v.2 file from the thread above. (1st page)
2. Install it to phone Memory.
3. Open the Msm7kCpuSpeed & You can see the current CPU speed in Real Time.
4. Whatever speed you select when on Battery Power, it will revert back to 528Mhz because of the Windows component that make sure the clock speed is 528 Mhz every (xx) second.
5. The only way you can overclock is when u plug your USB to Laptop / Stock Charger. Only then you can move the slider to any speed supported by your device.
6. Every device's speed are varied from the ROM used & quality of the MSM in your device. Try what speed are the best speed in your phone before it locks up. I use TAEL v.5 & I can achieve 768 Mhz in AC (original Charger / USB in Laptop/PC) on 787 i get random lockup
7. If you unplug your Raph from USB / Charger on ANY freq other than 604.8 Mhz, your raph will LOCK UP. So, when unplugging / pressing power button make sure u change the freq to 604 Mhz first. (604 Mhz is special Freq that don't Lockup our device)
8. A couple of seconds after we unplug our Raph in 604 Mhz freq it will revert back to 528 Mhz freq.
What almost works
Click to expand...
Click to collapse
From the explanation above we can use Overclock in Our Raph, but only when plugged into a charger / laptop / PC.
In this
PHP:
http://forum.xda-developers.com/showthread.php?t=725290&page=120
thread Qzytor in post 1191 found a way to overclock our MSM devices when using battery power. But in my experience, it ALWAYS lockup a few seconds after opening the phone dialer, coreplayer (playing video for a few second the lockup), SMS messaging, and Teeter (lockup when level up)
I'll write my experince using above method :
The method is : (Credit goes to Qzytor)
Code:
Install NetRippers Msm7kCpuSpeed V.2 App. in your Device
Install SetCpuSpeed v1.0d on SD card. --get it @ http://forum.xda-developers.com/showpost.php?p=7426966&postcount=1000 --
Take SD card out and soft reset the phone.
Open registry.
Go to HKLM\Software\Msm7kCpuSpeed.
Edit the values as below:
BootTime = 90000 (This is important. This value gives enough time for the
phone to fully boot up. The phone has to fully boot up
before the OC kicks in)
CheckTime = 20 (Stable at 20, otherwise yoyos between base and OCed
cpu speed)
Command = 0
PerfomanceLevel = 35 (This speed is stable for me without SOD)
ScreenOffPerfomanceLevel = 27
SettlingTime = 10
Close Registry editor, insert SD card in the phone and soft reset the phone.
Once the phone has fully boot up, give it a minute before opening NetRippers Msm7kCpuSpeed and you should see your OCed cpu speed.
If your OC cpu speed isnt stable then take your SD card out,soft reset the phone and registry edit PerfomanceLevel to a lower value.
To restore back to phone default speed:
Open File Explorer.
Go to Windows\Startup folder and delete SetCpuSpeed.
Soft reset the phone and phone default speed will be restored.
Before deleting SetCpuSpeed from Windows\Startup folder , save it in Documents folder so if you want to overclock again, copy and paste it from Documents folder to Windows\Startup folder.
1. Performance Level 35 is overclocking @ 672 Mhz
2. Add 1 level means add 19.2 Mhz in clock speed
3. The best speed i reach in AC power (USB / Laptop) is 768 Mhz = performance level 40
4. I change my performance level into 40 & I can see in MSM7kCpuSpeed that i'm running 768 Mhz after 90 seconds from the bootup as written above.
5. a few programs can run ok in 768 Mhz or any speed in that matter, but most causes lockup. This does NOT happen in Blackstone / Rhodium
6. Even on performance level = 35 (672 Mhz) or even in Performance level = 27 i still got a lockup opening phone, SMS, coreplayer, teeter, & FPSECE (only when exiting). they work fine on AC power.
7. I dont know if it's because of my ROM (TAEL v.5) or if all RAPH experience the same Issue.
I hope we can continue to improve overclocking our RAPH to the point it can perfectly works ^^
Another OC program
There is also this Overclock Tool:
http://forum.xda-developers.com/showpost.php?p=7463284&postcount=162
I haven't tried it yet, but it should work with our Raphael, and also on battery power.
I'm using touchpro and newest energy cookie rom.
Tried the method mentioned by b0z0k. Set level 35 for the 1st trial
Apps tried list:
Youtube
Opera
text message
File explorer
excel mobile
google mpas
teeter
window media player (not the music tab in sense)
lockup when playing teeter and music (the sense one). However, for other programs, it was just working brilliantly.
Really hope my experience can help.
After turning it to level 35, the device looks quite stable but i haven't tried any levels upper than that.
zai_hkman said:
I'm using touchpro and newest energy cookie rom.
Tried the method mentioned by b0z0k. Set level 35 for the 1st trial
Apps tried list:
Youtube
Opera
text message
File explorer
excel mobile
google mpas
teeter
window media player (not the music tab in sense)
lockup when playing teeter and music (the sense one). However, for other programs, it was just working brilliantly.
Really hope my experience can help.
After turning it to level 35, the device looks quite stable but i haven't tried any levels upper than that.
Click to expand...
Click to collapse
Yes, i just tried Energy ROM 1-2 days & Overclock works like a charm. Don't hestitate to use higher freq.. i found out that the best stable freq in my device are @ 748.8. 787 will instantly freeze my TP, 768 works but many apps crashing, 748.8 works very well with FpseCE
What i did, is try the newest energy ROM (rel. 23673, GTX, dinik version) & it all work like a charm. Sure, i still got occasional SOD but it's waaaaaaayyyyyy better than having to OC in Laptiop USB only..
So i think the issue i had earlier is definitely with the ROM (I think TAEL rom has some kind of energy saving script that keeps telling the CPU what clock it's running -- even when setCPUspeed already installed)
After i change to Energy Rom rel. 23673, on battery power, MSM7kCPUspeed+setCPUspeed v1.0d runs just as smoothly as AC power. I get occasional SOD only when exiting Fpsece (it makes the CPu drop to 384 Mhz then it froze). Using WMP, TCPMP, & other apps that usually crashes on TAEL v5 did NOT give me the "freeze"
@ 748.8 Mhz FPSEce gives me 5-8 fps boost with no frameskip , with frameskip i can play Final Fantasy Tactics @ 50 fps with no noticable errors (about 29 fps in landscape no frame skip)
And that makes me...
--> very happy TP owner
p.s. a little trick when having a non OC applicable ROM is to use your GPS programs (garmin, sygic, etc), minimize them, & run MSM7kcpuspeed to OC your device. this usually works ok.. Just a very bad battery consumption
& dont forget to change back to 604 Mhz before shutting down your GPS program & then u can power off the screen -- or else u get the SOD.
An update on usage:
I've just flashed to the updated rom for energy(Aug18 Cookie 23678)
After that, I overclock the device by the previous method.
I found that the device freezes everytime when i receive calls. Therefore,I have to remove the setcpu.ink in the window to stop overclocking. Anyone has figured out why the device freezes on some program but behave normal for the most of the time?
zai_hkman said:
An update on usage:
I've just flashed to the updated rom for energy(Aug18 Cookie 23678)
After that, I overclock the device by the previous method.
I found that the device freezes everytime when i receive calls. Therefore,I have to remove the setcpu.ink in the window to stop overclocking. Anyone has figured out why the device freezes on some program but behave normal for the most of the time?
Click to expand...
Click to collapse
This is the biggest problem I have. Theres certain parts of the day while working that I use my phone a lot, and the SOD's with phone can cause me to miss calls or be unable to place a call (SOD while dialing).
Im still waiting for some sort of option to totally disable itself when a named program is run.
hartleyshc said:
This is the biggest problem I have. Theres certain parts of the day while working that I use my phone a lot, and the SOD's with phone can cause me to miss calls or be unable to place a call (SOD while dialing).
Im still waiting for some sort of option to totally disable itself when a named program is run.
Click to expand...
Click to collapse
Just about 2-3 days now i have SOD while dialing too.. I don't know what's causing it, but i can confirm that after a fresh ROM flash (energy build 23673) i CAN dial in my phone while overclocked @ 768 Mhz.. After a lot of install, trial, etc now i have SOD EVERYTIME i dial in phone dialer.
p.s. before SOD's occured i just set up my GPRS/3G connection for my carrier.. i wonder if this is the cause?
b0z0k said:
Just about 2-3 days now i have SOD while dialing too.. I don't know what's causing it, but i can confirm that after a fresh ROM flash (energy build 23673) i CAN dial in my phone while overclocked @ 768 Mhz.. After a lot of install, trial, etc now i have SOD EVERYTIME i dial in phone dialer.
p.s. before SOD's occured i just set up my GPRS/3G connection for my carrier.. i wonder if this is the cause?
Click to expand...
Click to collapse
Maybe.. I do the carrier auto-setup once i boot a new rom. (AT&T USA). It might be some settings in there messing with it.
The test I do to see if it freezes is this: Call my voicemail (google voice) and just keep hitting "7" a bunch of times and see if it freezes.
Ive also tried various phone canvases. Have tried the new one currently being cooked into NRG roms (aug 18th) before it was cooked in, will try again now to see if anything has changed.
edit: I have also been following and trying all versions of iwfratz's overclock tool, and compatibility actually seems to get worse with each new release. the original version would crash after a while at the stock 650, which on my TP its much more stable at 633. But with current versions (1.5) it crashes immediately after setting the overclock, a version or two ago it would run, but would still crash when using the phone app.
i use nrg rom 21914 and overclock with msm7kcpu speed +setup cpu 1.0d.
4 "bugs/[email protected],6Mhz":
-phone works great, untill i receve a call, than the phone hangs.
-also the phone hangs, when i will use nitrogen 1.1 to listen to music.
-and the phone hangs, when my alert goes on and i have the lockscreen activatet.
-when i receve a mms and downloaded it, the phone hangs also
after the hang, i need to put the batterie out of the tp to restart....
@ ~746 the phone starts but sense restarts again and again...but in the 6.august of nrg rom, i thought this speed works also ...
maybe someone know an answere.
I love the speed i wouldn't miss it...i already sold my Acer s200, because it is crap
New Method, No Freeze in Phone dialer, but battery more inefficient
New Method, No Freeze in Phone dialer, but battery more inefficient
I have tried SetCPUspeed v1.0d & it made the Overclock working BUT i dont know why every time I open dialer screen or an SMS came, it always freezes.
I think it has to do with the fact that WinMo in our TP consistantly checking the speed/ frequency of our MSM.
The only way we can bypass this :
1. When we connect to our laptop (activesync) -- when we connect Raph to PC & it starts sync-ing in activesync, the speed/ freq check disabled, this is an exploit that we can use to overclock safely. BUT..
We do need our laptop / PC to do this (we can't overclock when we're traveling & want to play FpseCE in full speed ^^)
2. THE NEW METHOD -- more battery draining though.. We can bypass the freq check using GPS module. When the GPS is ON, the speed check is disabled. This way, even when we're traveling, we can still Overclock our Raph safely (wont freeze when opening dialer / receivinf SMS.
But, it's still opening GPS module, it's a battery drainer. In my experience it's about 20% faster draining the battery. Use HTC GPS tool & choose "open port"
What i do is :
when the phone is not used (deep sleep), i don't use the Overclock. When i want to use something in my phone & i want to boost it's speed i will turn on HTC GPS tool & overclock my phone to 729,6 (the most stable for me). When i'm done & want to put my phone to sleep, i made my MSM7kCPUSpeed to 604 Mhz (safe speed, wont freeze) & i turn off the GPStool.
When i press the power button the freq will change to 528 Mhz again & the battery consumption became normal again. ^^
It's a turn around from the problem we're facing.. but Hey, i got to play Final Fantasy Tactics @ nearly full speed ^^
After a little testing, no freezes anymore.^^
However, if we disable the frequency check, we are not able to stablize the frequency.
What I mean is that sometimes after a call or running some programs, the frequency will drop to about 355 and I have to open MSM7kcpuspeed again to adjust the frequency.
Anyway, this is really a breakthough for overclocking out TP.
still got bugs
I love the increase of speed, when the device is overclocked.
But i got still bugs.
When i want to listen to music, it hangs after about 1-2 secounds. i don't know why.
Maybe you can help me with this problem, because i dont want to have only 527mhz.
my settings:
my BootTime = 90000
CheckTime = 20
Command = 0
PerfomanceLevel = 38
ScreenOffPerfomanceLevel = 27
SettlingTime = 10
best regards
i know it's an old thread, but is any new way public to overclock the touch pro?
atm i need to use it @ normal speed, because it is really buggy @ overclocked=/
As we know, overclocking MSM is possible now. Just check :
http://forum.xda-developers.com/showthread.php?t=725290
Click to expand...
Click to collapse
But the thread is over 1400 post & most of them are about blackstone, Rhodium, etc.. I think it's about time we make a thread about overclocking our Touch Pro(s)
I use GSM unbranded TP100 & TAEL v.5 ROM.
I'll start with my experience :
What Works
Click to expand...
Click to collapse
1. grab the v.2 file from the thread above. (1st page)
2. Install it to phone Memory.
3. Open the Msm7kCpuSpeed & You can see the current CPU speed in Real Time.
4. Whatever speed you select when on Battery Power, it will revert back to 528Mhz because of the Windows component that make sure the clock speed is 528 Mhz every (xx) second.
5. The only way you can overclock is when u plug your USB to Laptop / Stock Charger. Only then you can move the slider to any speed supported by your device.
6. Every device's speed are varied from the ROM used & quality of the MSM in your device. Try what speed are the best speed in your phone before it locks up. I use TAEL v.5 & I can achieve 768 Mhz in AC (original Charger / USB in Laptop/PC) on 787 i get random lockup
7. If you unplug your Raph from USB / Charger on ANY freq other than 604.8 Mhz, your raph will LOCK UP. So, when unplugging / pressing power button make sure u change the freq to 604 Mhz first. (604 Mhz is special Freq that don't Lockup our device)
8. A couple of seconds after we unplug our Raph in 604 Mhz freq it will revert back to 528 Mhz freq.
What almost works
Click to expand...
Click to collapse
From the explanation above we can use Overclock in Our Raph, but only when plugged into a charger / laptop / PC.
In this
PHP:
http://forum.xda-developers.com/showthread.php?t=725290&page=120
thread Qzytor in post 1191 found a way to overclock our MSM devices when using battery power. But in my experience, it ALWAYS lockup a few seconds after opening the phone dialer, coreplayer (playing video for a few second the lockup), SMS messaging, and Teeter (lockup when level up)
I'll write my experince using above method :
The method is : (Credit goes to Qzytor)
Code:
Install NetRippers Msm7kCpuSpeed V.2 App. in your Device
Install SetCpuSpeed v1.0d on SD card. --get it @ http://forum.xda-developers.com/showpost.php?p=7426966&postcount=1000 --
Take SD card out and soft reset the phone.
Open registry.
Go to HKLM\Software\Msm7kCpuSpeed.
Edit the values as below:
BootTime = 90000 (This is important. This value gives enough time for the
phone to fully boot up. The phone has to fully boot up
before the OC kicks in)
CheckTime = 20 (Stable at 20, otherwise yoyos between base and OCed
cpu speed)
Command = 0
PerfomanceLevel = 35 (This speed is stable for me without SOD)
ScreenOffPerfomanceLevel = 27
SettlingTime = 10
Close Registry editor, insert SD card in the phone and soft reset the phone.
Once the phone has fully boot up, give it a minute before opening NetRippers Msm7kCpuSpeed and you should see your OCed cpu speed.
If your OC cpu speed isnt stable then take your SD card out,soft reset the phone and registry edit PerfomanceLevel to a lower value.
To restore back to phone default speed:
Open File Explorer.
Go to Windows\Startup folder and delete SetCpuSpeed.
Soft reset the phone and phone default speed will be restored.
Before deleting SetCpuSpeed from Windows\Startup folder , save it in Documents folder so if you want to overclock again, copy and paste it from Documents folder to Windows\Startup folder.
1. Performance Level 35 is overclocking @ 672 Mhz
2. Add 1 level means add 19.2 Mhz in clock speed
3. The best speed i reach in AC power (USB / Laptop) is 768 Mhz = performance level 40
4. I change my performance level into 40 & I can see in MSM7kCpuSpeed that i'm running 768 Mhz after 90 seconds from the bootup as written above.
5. a few programs can run ok in 768 Mhz or any speed in that matter, but most causes lockup. This does NOT happen in Rhodium (Touch Pro 2)
6. Even on performance level = 35 (672 Mhz) or even in Performance level = 27 i still got a lockup opening phone, SMS, coreplayer, teeter, & FPSECE (only when exiting). they work fine on AC power.
7. I dont know if it's because of my ROM (TAEL v.5) or if all RAPH experience the same Issue.
I hope we can continue to improve overclocking our RAPH to the point it can perfectly works ^^
Im happy that there are people that want to work on oc project for touch pro..I want to help even i dont know much..
I dont get the disconnect ac issues at all, but definitely get the freezing on the phone app, but apparently other phones do as well.
Im waiting for somesort of blacklist option that can actually close the overclock *and not just revert back to 528*.
Have done tests with netrippers app, setcpuspeed 1.0d, iwfratz oc tool, and oc auto 4.1 (this doesn't work with mine, I use the latest Energy rom, and Im part of the "1%" that doesn't have certain registry settings, and it doesn't work by adding them.)
hartleyshc said:
I dont get the disconnect ac issues at all, but definitely get the freezing on the phone app, but apparently other phones do as well.
Im waiting for somesort of blacklist option that can actually close the overclock *and not just revert back to 528*.
Have done tests with netrippers app, setcpuspeed 1.0d, iwfratz oc tool, and oc auto 4.1 (this doesn't work with mine, I use the latest Energy rom, and Im part of the "1%" that doesn't have certain registry settings, and it doesn't work by adding them.)
Click to expand...
Click to collapse
Yes, I agree, Iwfratz's OC tool are NOT WORKING on other device other than RHODIUM. So the best option i have is NetRipper's App + SetCPUspeed 1.0d. Can't work OC auto for some reason (no key binding App to bind mortscript down.mscr to power button).
What i did, is try the newest energy ROM (rel. 23673, GTX, dinik version) & it all work like a charm. Sure, i still got occasional SOD but it's waaaaaaayyyyyy better than having to OC in Laptiop USB only..
So i think the issue i had earlier is definitely with the ROM (I think TAEL rom has some kind of energy saving script that keeps telling the CPU what clock it's running -- even when setCPUspeed already installed)
After i change to Energy Rom rel. 23673, on battery power, MSM7kCPUspeed+setCPUspeed v1.0d runs just as smoothly as AC power. I get occasional SOD only when exiting Fpsece (it makes the CPu drop to 384 Mhz then it froze). Using WMP, TCPMP, & other apps that usually crashes on TAEL v5 did NOT give me the "freeze"
@ 748.8 Mhz FPSEce gives me 5-8 fps boost with no frameskip , with frameskip i can play Final Fantasy Tactics @ 50 fps with no noticable errors (about 29 fps in landscape no frame skip)
And that makes me...
--> very happy TP owner
p.s. a little trick when having a non OC applicable ROM is to use your GPS programs (garmin, sygic, etc), minimize them, & run MSM7kcpuspeed to OC your device. this usually works ok.. Just a very bad battery consumption
& dont forget to change back to 604 Mhz before shutting down your GPS program & then u can power off the screen -- or else u get the SOD.
b0z0k said:
Yes, I agree, Iwfratz's OC tool are NOT WORKING on other device other than RHODIUM. So the best option i have is NetRipper's App + SetCPUspeed 1.0d. Can't work OC auto for some reason (no key binding App to bind mortscript down.mscr to power button).
What i did, is try the newest energy ROM (rel. 23673, GTX, dinik version) & it all work like a charm. Sure, i still got occasional SOD but it's waaaaaaayyyyyy better than having to OC in Laptiop USB only..
talled)
After i change to Energy Rom rel. 23673, on battery power, MSM7kCPUspeed+setCPUspeed v1.0d runs just as smoothly as AC power. I get occasional SOD only when exiting Fpsece (it makes the CPu drop to 384 Mhz then it froze). Using WMP, TCPMP, & other apps that usually crashes on TAEL v5 did NOT give me the "freeze"
@ 748.8 Mhz FPSEce gives me 5-8 fps boost with no frameskip , with frameskip i can play Final Fantasy Tactics @ 50 fps with no noticable errors (about 29 fps in landscape no frame skip)
Click to expand...
Click to collapse
Im getting with the newest nrg rom the same problems..new calls or sms and the phone needs reset..
The best trick of all its just to overclock your phone to max mhz your phone can stand unlagged and move the shortcut from startup to start menu..So you can use it from start menu only for the programms you want to use..When you finish you make a reset..And everything goes to normal again..In my "normal mode" im using nuedynamicclock for max performance of cpu..From "Battery life" side - nuedynamicclock(max performance)+timolols rom it stands <> 2 days..
New Method, No Freeze in Phone dialer, but battery more inefficient
New Method, No Freeze in Phone dialer, but battery more inefficient
I have tried SetCPUspeed v1.0d & it made the Overclock working BUT i dont know why every time I open dialer screen or an SMS came, it always freezes.
I think it has to do with the fact that WinMo in our TP consistantly checking the speed/ frequency of our MSM.
The only way we can bypass this :
1. When we connect to our laptop (activesync) -- when we connect Raph to PC & it starts sync-ing in activesync, the speed/ freq check disabled, this is an exploit that we can use to overclock safely. BUT..
We do need our laptop / PC to do this (we can't overclock when we're traveling & want to play FpseCE in full speed ^^)
2. THE NEW METHOD -- more battery draining though.. We can bypass the freq check using GPS module. When the GPS is ON, the speed check is disabled. This way, even when we're traveling, we can still Overclock our Raph safely (wont freeze when opening dialer / receivinf SMS.
But, it's still opening GPS module, it's a battery drainer. In my experience it's about 20% faster draining the battery. Use HTC GPS tool & choose "open port"
What i do is :
when the phone is not used (deep sleep), i don't use the Overclock. When i want to use something in my phone & i want to boost it's speed i will turn on HTC GPS tool & overclock my phone to 729,6 (the most stable for me). When i'm done & want to put my phone to sleep, i made my MSM7kCPUSpeed to 604 Mhz (safe speed, wont freeze) & i turn off the GPStool.
When i press the power button the freq will change to 528 Mhz again & the battery consumption became normal again. ^^
It's a turn around from the problem we're facing.. but Hey, i got to play Final Fantasy Tactics @ nearly full speed ^^
b0z0k said:
2. THE NEW METHOD -- more battery draining though.. We can bypass the freq check using GPS module. When the GPS is ON, the speed check is disabled. This way, even when we're traveling, we can still Overclock our Raph safely (wont freeze when opening dialer / receivinf SMS.
But, it's still opening GPS module, it's a battery drainer. In my experience it's about 20% faster draining the battery. Use HTC GPS tool & choose "open port"
What i do is :
when the phone is not used (deep sleep), i don't use the Overclock. When i want to use something in my phone & i want to boost it's speed i will turn on HTC GPS tool & overclock my phone to 729,6 (the most stable for me). When i'm done & want to put my phone to sleep, i made my MSM7kCPUSpeed to 604 Mhz (safe speed, wont freeze) & i turn off the GPStool.
When i press the power button the freq will change to 528 Mhz again & the battery consumption became normal again. ^^
It's a turn around from the problem we're facing.. but Hey, i got to play Final Fantasy Tactics @ nearly full speed ^^
Click to expand...
Click to collapse
Ive played around with the gps issue before. Silly me forgot about simply opening the port in gpstool. I was using google maps till the gps would time out on me.
Without the constant cpu checking, I can safely go up to a much higher speed now! (710. 729 makes sense start to crash occasionally)
Now a few questions I will probably answer myself in the next few hours. Will the gps port ever turn itself off? even when going to sleep? Is there a way to open the gps port at start up? will setcpuspeed work better with this? (turn the check time up to 500, or 1000, not 20 like we were working with earlier?
And the big one.. can we use mortscript to enable/disable the gps port? we could just use our own script to overclock our phones. will look more into mortscript later.
edit: this makes me begin to think this might be a rom issue. what is causing the cpu checks? can anything be done to disable it? i know the blackstone users have a similar issue to us with the cpu checking. any chefs/programmers want to shed some light on this?
Motorola Xoom Wifi Only, 1.4.4 3.1
I just popped Set CPU back on my xoom after putting on 1.4.4 and set it to "interactive"
I cranked the max up to 1.7ghz and checked set on boot.
It restarted and now, it boots and then crashes every time I get to the pattern unlock screen and then reboots.
I cant seem to stop this reboot cycle. Is there any way to stop it from crashing repeatedly?
My Sunday morning is a mess indeed!
yanic123 said:
Motorola Xoom Wifi Only, 1.4.4 3.1
I just popped Set CPU back on my xoom after putting on 1.4.4 and set it to "interactive"
I cranked the max up to 1.7ghz and checked set on boot.
It restarted and now, it boots and then crashes every time I get to the pattern unlock screen and then reboots.
I cant seem to stop this reboot cycle. Is there any way to stop it from crashing repeatedly?
My Sunday morning is a mess indeed!
Click to expand...
Click to collapse
OK...first rule. NEVER select Set On Boot for JUST THIS REASON. It just isn't worth it, unless you have a set up that you are absolutely certain is totally stable and the extra 15 seconds at boot up to overclock it again is just too much of a bother for you to bear.
I know there are some scripts that can be run from Recovery to clear overclocking, but I don't have the technical bones to direct you to them, or even the knowledge if they would work on the Xoom.
Personally I would try installing a lower frequency Tiamat kernel or the stock kernel and then rebooting. When SetCPU cannot achieve the frequency you have it set for now, it will either FC, just overclock the device to the kernel maximum, or bootloop you. Therefore, I doubt it would hurt and may solve your problem pretty easily.
yep, just flash a different kernel.
just flash tiamat 1.4.3
Sent from my Xoom using XDA Premium App
thanks guys! really glad you lot are here to support
Yeah, for anyone else reading this... I had the exact same problem with the never ending boot loop.
I just flashed tiamat 1.4.3 through cwm. It then booted correctly, so I reflashed 1.4.4 but this time I got rid of SetCPU in favour of 'No Frills'. It doesn't have the profiles I was used to with SetCPU, but it does seem to do a much better job with the xoom.
It's still a bit unstable at 1.7, but runs beautifully at 1.6.
Good times!
Wish I had seen this 15 minutes ago
I had the same issues and did a factory reset. Oh well I guess that is what backups are for
I did the following on my MyTouch 4G, but it should work for the Xoom if you have ClockworkMod Recovery and Android SDK on your PC.
1. Boot into CWM recovery.
2. adb pull /data/data/com.mhuang.overclocking/shared_prefs/setcpu.xml D:\setcpu.xml
3. I opened D:\setcpu.xml and set the following:
- startBoot setting from "1" to "0".
- max setting to equal min.
4. adb push D:\setcpu.xml /data/data/com.mhuang.overclocking/shared_prefs/setcpu.xml
5. Unmount data and reboot.
guys...my phone sometimes freezes on the lockscreen....and I have to pull out the battery...the problem is that this happens with all roms, sense or not based....
what's going on?!
You may get more help if you provide a little more info, ie:
-Are you using a specific 3rd party launcher with roms?
-Are you using a custom kernel, and if so what are your settings?
-Have you tried running in safe mode to rule out 3rd party apps?
-Did this problem begin after anything in particular you can think of?
-etc....
Maybe too low CPU values?
Undervolt can cause this as well.
It happened to me while using APEX on ARHD.
But indeed more info is needed.
this started a week ago...with miui official/faux kernel and now with aokp b38/tamcore kernel....I know tamcore kernel is undervolted, and don't know nothing about faux's one...
I use nova launcher, setcpu is set at 384/1188 and I have a profile screen-off at 192/432...
uh, forgot, I use SIO scheduler...I set it with no frills and uninstalled it after, to have just one cpu control app (setcpu)...
this morning my alarm didn't ring! then I had to pull out the battery because it was freezed...luckily I woke up by myself this morning XD
I recommend to use a higher off-screen value (384 MHz) as a first try. See how it reacts and also use an app to check the current voltage (like system tuner / st pro).
If this does not helps then start isolating apps.
I have NOOP sched and 384-432 Off-screen and had no issues far, but I remember that with 192 Mhz a while ago the screen did not wake up a few times (on ARHD 6.3.x).
I updated to b39, nothing now....if it freezes i'll try setting a higher minfreq...
thank you all! thx+1
Hello. I have been a "lurker" on these boards for roughly 2 years. I have rooted, flashed and installed custom ROMs, bootloaders, recoveries and radios on the following devices:
Samsung Vibrant (original samsung galaxy S)
HTC Amaze (a.k.a Ruby.... wire trick and all)
ASUS Transformer 1 WiFi Only model ( a.k.a TF101)
Anyway, I am posting for the first time. Because of this, I cannot post directly to the development thread involved with my issue. Never the less, here it is:
I am running RaymanFX's JellyBean Cyanogen 10 V6 (STABLE) with Rayman's custom kernel on my TF101. I was running a Revolver ICS ROM prior to installing this JB ROM.... or Revolution HD, I can't remember... anyway
I am having an issue with the TF101 either 1) involuntary reboot or 2) freeze/lockup/crashing after wakeup from sleep mode and complete loss of WiFi radio.
Yes, I have extensively searched the development threads and I found posts related to this one, but none of them solve the issue and I also noticed a few people have this same problem but have no known solution.
I have wiped and done clean install of this ROM several times always with the same result. I also flashed LiquidSmooth (Rayman worked on this ROM and his kernel is cross compatible) to see if it was ROM-related and discovered it is not.... this is a kernel issue. My wipe procedure is:
Factory Reset (cache/data wipe)
Run Superwipe script for TF101 from Android Revolution HD thread (format cache, data, etc...)
Wipe Dalvik Cache
Flash ROM
Reboot
Flash GAPPS (latest version linked on Cyanogen thread from goo.im)
Reboot
Everything runs buttery smooth and flawlessly, HOWEVER.... "Wake on WiFi fix" solution on RaymanFX's post does not work for me.
The "fix" is to designate WiFi Always On during Sleep. Changing this setting doesn't stick... WiFi still sleeps even with this setting corrected. With one caveat... Changing the setting to "Never" and then modifying WiFi Idle Timeout to "3 hours" and then changing the Keep WiFi on During Sleep to "Always" will delay the WiFi from idling out temporarily unless the tablet is in Sleep longer than 3 hours.... at which it idles anyway and causes a crash or reboot.
Secondly, I have discovered that the CPU Frequency setting under Performance could be part of the reason it crashes. I have "Set on Boot" enabled. Setting a CPU Frequency, regardless of governor, above 1408 Mhz WILL cause tablet to lockup/crash upon wakeup from Sleep as the processor jumps to maximum set frequency. If maximum frequency is set to 1408, it will stutter and lag out the system forcing it to become unresponsive to touch commands but "stable" and useable.... albeit very laggy. If the Max Frequency is set to 1200, it will NOT reduce the maximum frequency set for the CPU unless tablet is put into Sleep mode and then woken again.... it will constantly cycle between the "old" maximum frequency setting and the "new" maximum frequency setting (observed by monitoring the frequency in the Performance setting screen after changing from a higher max frequency to a lower max frequency and staying on the menu screen and allowing the CPU to "settle" without any user input).
I really like this ROM and I hate to give up on it, so I'm hoping someone out there will have an idea about what I can do to make this work... or at least recommend a different kernel that will work with this ROM and also has a way to change CPU frequencies and governers.
Any ideas?