I rooted and installed setCPU. I did not overclock but setup profiles to underclock the cpu.
My phone started locking up and rebooting and crashing. So I stopped setCPU and uninstalled it. I then rebooted the phone. I installed Temp+CPU V2 app and the widget shows my processor speed ranging from 600mhz to 250mhz... Is that normal because I thought the droid 1 default speeds were 550mhz?
How do I get rid of setCPU? I did a factory reset and formatted my sd card. So what's the deal? Or is it normal? It's still locking up and crashing, so I think I may have messed up the phone.
Related
Hi all,
I found out that when I use kyrillos ROM 4.1 OC edition on my samsung galaxy apollo i-5800 then the phone sometimes freezes with only a reboot possible.
It occured to me this happened only in idle (no cpu intensive actions) mode.
With setcpu I raised the lower frequency limit from 83 to 166 Mhz (also in screen-off profile), because I thought the freezing could be related with lower 83 Mhz.
Since then I "never" ran into freezes anymore with my phone...no issues when cpu is between 166 and 1300 mhz (yes no issues even at high clock speed, against all laws ).
I just wanted to share this information for other people having the freezing issue, maybe also on other customized ROMS, just try this min cpu setting if it works for you
BTW I didnt really notice worse battery life with this 'remedy'
Enjoy your phone, it's made for you !!!
Br.
Michel
i5800 freeze
I'm new on this forum, but I'm used to flash my phone.
I got the next problem, I'm running Kyrillos'rom 9.7.1 (update) for 2 weeks.
On my first install of kyrillos my phone freezes when I was 2 minutes working, so I installed setcpu to lower the cpu-speed and It worked.
Now, I had to flash my phone again, because I did something wrong in the system file.
I re-installed the kyrillos 9.7.1 update with Odin, but then, when my phone boots, it almost immediately freezes when I do something.
I don't get the time to install setcpu to lower the freqency
I tried it almost 20 times...
Can anyone help me lowering the frequency?
Thanks!
UPDATE:
It worked, I finaly got into my files to install set cpu! After 30 times rebooting...
But My question is still there, because It's almost impossible for me to flash my phone again now!
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.
Since we've had root I have been running tiamat and using setcpu to overclock to 1500 and its been working great.
After the 3.2 upgrade to 2.6.36.4Tiamat_Xoom-V2.0.0 for 3.2, SetCPU has a habit of going to 216MHz even thought its set for 1500. If I open setcpu it says 216 but if I simply click on the Max bar it jumps back to 1500.
I have had setcpu on Performance and Interactive - Both do the same. It may keep 1500 for a few hours or only an hour - then the system gets slow due to the 216MHz clock....
Any ideas?
Never heard of such an issue on the Xoom until now...
Common sense I know, but... make sure you don't have any profiles set up to cause this. That is the only thing I can think of. Ex: It's set to clock to the lowest speed while AC charging, etc.
If all else fails... wiping data is your best friend to fix strange problems while flashing custom Roms. Back up all of your apps with their data via Titanium Backup, then wipe data, wipe cache, wipe dalvik cache, then restore all apps with data, but do not restore any system data or system apps. That's the best thing you can do, if you do not do this... you may experience problems like so. I've had strange issues before and doing this fixed it all up no problem.
PensFan66 said:
Since we've had root I have been running tiamat and using setcpu to overclock to 1500 and its been working great.
After the 3.2 upgrade to 2.6.36.4Tiamat_Xoom-V2.0.0 for 3.2, SetCPU has a habit of going to 216MHz even thought its set for 1500. If I open setcpu it says 216 but if I simply click on the Max bar it jumps back to 1500.
I have had setcpu on Performance and Interactive - Both do the same. It may keep 1500 for a few hours or only an hour - then the system gets slow due to the 216MHz clock....
Any ideas?
Click to expand...
Click to collapse
You can set the lowest speed higher. Use interactive and don't set on boot unless you are really sure that it's stable.
Speaking about SetCPU, on phones, there is the menu button which you can click but it doesn't seem to appear on the Xoom which basically allows you to autodetect speeds, are you guys able to access that other than only on the first launch of setcpu after installed?
Almighty1 said:
Speaking about SetCPU, on phones, there is the menu button which you can click but it doesn't seem to appear on the Xoom which basically allows you to autodetect speeds, are you guys able to access that other than only on the first launch of setcpu after installed?
Click to expand...
Click to collapse
I think it only works the first time on the Xoom.
okantomi said:
I think it only works the first time on the Xoom.
Click to expand...
Click to collapse
setcpu never worked right for me. use no-frills cpu.
I appreciate the guys here helping me install beastmode on my machine with viper xl but whenever I try to change the cpu settings they don't stick, and my battery is draining faster than it should. I flashed beastmode at 1.8ghz but I wont to be able to underclock back to 1512ghz when I'm not benchmarking or playing a game. I've tried venom tweaks cpu editor and setcpu and neither one are able to set the cpu permantly. Reverts back after about 2sec's or so. Anyone know whats causing this and how to fix it?
try no-frills
Ok i installed no-frills cpu, set the cpu to 1512, modified the thermald.config in system etc, changed permissions accordingly, restarted the phone and now I'm in a bootloop. I know I can do a nandroid but is there any other way to end the bootloop? Oh and I set no-frills to set cpu at startup.
I managed to get no-frills unistalled before it restarted again. No more bootlooping. One lesson I learned is never set a cpu to run at startup.
ImagioX1 said:
Ok i installed no-frills cpu, set the cpu to 1512, modified the thermald.config in system etc, changed permissions accordingly, restarted the phone and now I'm in a bootloop. I know I can do a nandroid but is there any other way to end the bootloop? Oh and I set no-frills to set cpu at startup.
Click to expand...
Click to collapse
More invalid configurations bro. Something the POST doesn't like and keeps you from booting to prevent damage to your phone
You probably did something in thermald.conf that your phone doesn't like
Sent from my One X using xda app-developers app
device: Yu Yutopia
problem: suddenly there was lot of lag in my phone, i checked the cpu utilization and cpu frequency numbers, 4 a53 cores were running at high frequency and 4 a57 cores were offline.
the device is root, but i didn't do anything with the kernal or the rom.
i have changed the performance profiles , but cores were still offline.
i have reset my device and started restoring apps using titanium backup and the problem repeated again.
i was using xposed framwork for more than 20 days without any problem and yesteray this problem suddenly started.
i tried uninstalling XF and uninstalling modules but nothing worked so far.
i am trying to reset the device again and install apps directly from play store now.
currently running official CM12.1
why did this happen?
how to solve it?
cpu frequency missing in cpu z app