Hi there,
I have a Samsung stock ROM still on 2.3.3 (rooted). Did not update since I need to test my apps on 2.3.x A while ago I played around with tegrak overclock and o'd the device to 1850 Mhz.. since then I notice the consequences - the device randomly reboots. There're between 3 and 20 reboots per day, the phone might reboot when it is lying with screen locked, it might reboot when I use it, it might reboot while making a call, it might reboot when disconnected from PC.. there's no regularity which I could notice. I suppose there's something wrong with CPU voltage which changes by itself. Was thinking about a factory reset but I'm not sure if that helps. Any suggestions?
Not all CPU's can handle the same level of overclocking and over/undervolting. You need to experiment with different levels to see which works, particularly if you're pushing to extremes as you have. Start with stock settings, then move in say, 100MHz steps with clock speed, and say 25-50mV with voltages until you find levels your CPU can function normally with.
When changing the cpu frequency it might not have enough voltage and cause reboot . Or it doesnt suport tht cpu speed
Sent from my GT-I9100 using xda premium
MistahBungle said:
Not all CPU's can handle the same level of overclocking and over/undervolting. You need to experiment with different levels to see which works, particularly if you're pushing to extremes as you have. Start with stock settings, then move in say, 100MHz steps with clock speed, and say 25-50mV with voltages until you find levels your CPU can function normally with.
Click to expand...
Click to collapse
the matter is that the device is NOT overclocked now, oc mode is disabled, voltage/frequency is reset to stock but the problem remained.
You sure there's nothing in init.d that might be set when it boots ? If there isn't, yep, factory reset. And if that doesn't help, do a clean install of stock.
try doing a clean wipe and reflash the rom if u still face the issue then try going back to stock and chk ..
Related
In my neverending attempt to extend my battery life, I installed SetCPU. The underclocking with profiles has extended my battery some, but Id like more.
I know very little about undervolting, its a new concept to me. Could someone elaborate on it, and may've suggest voltages for each speed setting? I hear it can do wonders for battery life.
Sent from my MB860 using XDA App
just experiment, start with small increments (don't save your settings!!!) see if it reboots, if its stable for a day or two, increase it, when it starts crashing dial it back a notch.
Just like overclocking except in reverse and with voltage basically.
note I'm not sure re: kernel requirements, I haven't tried it yet with my atrix, and my current ROM runs stock kernel I think.
its hit and miss, for example on my SGTab I can't undervolt at all or else it crashes all the time, others get away with -100mAh across the board (bastards), but mine is happy on 1.1OC.
WTFsandwich said:
In my neverending attempt to extend my battery life, I installed SetCPU. The underclocking with profiles has extended my battery some, but Id like more.
I know very little about undervolting, its a new concept to me. Could someone elaborate on it, and may've suggest voltages for each speed setting? I hear it can do wonders for battery life.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
If you like cars it seem this will be the best way to explain it
http://forum.xda-developers.com/showpost.php?p=15947019&postcount=643
That is an excellent analogy. Basically, trial and error?
Sent from my MB860 using XDA App
Yes, start conservative.
Another way to use setcpu to improve your battery life is to set a screen off profile to restrict the CPU speed to minimum when the screen is off.
I tried that one, but it kept stalling my phone when turning the screen back on when it was at the bare minimum.
EDIT: For anyone wondering, -75 seems to cause frequent freezes.
Sent from my MB860 using XDA App
mramirezusa said:
If you like phones it seem this will be the best way to explain it
Think of it as tweaking the CPU of a phone to use just enough power to prevent it from failing in order to conserve battery life without affecting it's normal operation.
Click to expand...
Click to collapse
Fixed that for ya!
WTFsandwich said:
That is an excellent analogy. Basically, trial and error?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Any overclocking or underclocking is always trial and error. Rule of thumb is to only ever change one thing at a time in small increments, then test before adjusting again. Your approach should be methodical and not haphazard, i.e. in a PC change cpu clock speed in small increments until you fail to boot or BSOD, then change voltage in small increments until you boot and are stable again. Monitor temperatures all the time, and add cooling if necessary. If you take a methodical approach, and don't rush things, you can achieve surprising results with hardware/software tweaking.
What would be a good way to test once I increment a voltage?
Sent from my MB860 using XDA App
A good test is to just use it as you normally would. If the phone doesn't reboot, you're good to go.
Sent from my MB860 using XDA App
edit: pls delete
So, I had checked off set at boot on the voltage screen. Unfortunately, this has rendered my phone to continually reboot and freeze, as one voltage is too low.
I do have a nandroid backup from right before installing SetCPU, and backups of working voltages, but I can't get the working ones restored before SetCPU starts and freezes my phone.
Is there a way I can default or disable the SetCPU settings without having to reflash the ROM or a backup of it?
WTFsandwich said:
What would be a good way to test once I increment a voltage?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Do something CPU intensive also to see if it crashes, like play a game. You want to stretch the phone to the limits to test it at the most extreme condition you will use it under.
WTFsandwich said:
So, I had checked off set at boot on the voltage screen. Unfortunately, this has rendered my phone to continually reboot and freeze, as one voltage is too low.
I do have a nandroid backup from right before installing SetCPU, and backups of working voltages, but I can't get the working ones restored before SetCPU starts and freezes my phone.
Is there a way I can default or disable the SetCPU settings without having to reflash the ROM or a backup of it?
Click to expand...
Click to collapse
Maybe a factory/data wipe?
Other than that I can't think of anything myself.
ddddddddddddd
you may try to use default stock kernel, on wich overcloking do not work.
re: setcpu, sorry I think you have to reflash... thats why you don't save the settings until you're sure
there is no shortcut way.... you may be fine for a day but next day it keeps crashing. Happened to me on my SG tab when I went to 1.2 for example, I thought it was hunky dory then a few days later crashing galore.
the longer you leave it for the better you are, its really your call to make. Some people prefer the extra speed and will live with a crash or two a week (not me, its my phone not gaming pc lol).
not sure how much stress testing you can/should do. Back when I was OCing PCs I would leave stress tests running overnight, but probably not a good idea to 100% CPU a phone overnight lol
I'm running prebeta 4 - and just wondering if anyone is having there phone heat up on them? It only takes about 5-10 minutes of use and it gets pretty warm? I have gone into the performance settings and lowered the cpu speed to 913mhz? That seemed to help a tad, but it could just be in my head.
Another thing i noticed is that copy and paste doesn't work. Is anyone else able to solve that issue?
Thanks!
jake.perkinsr said:
I'm running prebeta 4 - and just wondering if anyone is having there phone heat up on them? It only takes about 5-10 minutes of use and it gets pretty warm? I have gone into the performance settings and lowered the cpu speed to 913mhz? That seemed to help a tad, but it could just be in my head.
Another thing i noticed is that copy and paste doesn't work. Is anyone else able to solve that issue?
Thanks!
Click to expand...
Click to collapse
It does heat up a bit. You may want to try undervolting your phone. I've noticed that it doesn't get as warm. If you do a search there are a few threads on the topic. No C+P problems for me.
I installed CM7 yesterday too. Haven't had any issues with heating up yet. Idle is around 32C. Performance wise , this is the best ! as enomai said, you can under volt your phone by going to settings>cm settings>performance>"watch out for the dragons ahead! >CPU settings>change the min and max cpu frequency to your desire MHz.
You might need to reflash and wipe everything. Or find out what rogue app you got going.
I voided my warranty and your mum.
had a force close and notice that caused it to overheat, checked set cpu and noticed it sitting at 1300 constantly and not scaling or dropping at all.. had to reboot for it to cool down.
tonesy said:
had a force close and notice that caused it to overheat, checked set cpu and noticed it sitting at 1300 constantly and not scaling or dropping at all.. had to reboot for it to cool down.
Click to expand...
Click to collapse
AAhhh ok. Well in that case I would say if it's not a piece of software * like for example do you have TWO overclock softwares installed, like setcpu AND another?*, then it's probably a kernel problem. I would uninstall whatever software you have to overclock, reboot into fastboot, do a
fastboot erase boot
fastboot reboot
, and then reboot into recovery and try flashing the kernel again. wipe cache, see if this works.
Do I need to get Setcpu to undervolt my phone? I'm a bit nervous that the heat will damage my phone. I really love cm7, but I need it to not overheat. This never happened when I ran stock? What do you guys think?
Sent from my MB860 using XDA App
I havnt been running into any overheating issues at all, actually been running cooler on CM7. Im running Faux's 1.3 OC kernal instead of the kernal that came with it though. Try reflashing the kernal or flashing another one of Faux's kernals for CM7. I would definitely install Setcpu so u can moiter the battery and processer temps. Set up a few profiles and try undervolting some.
I installed cyanogenmod 7 on my Legend a few weeks back. It was running ok, today I thought about overclocking it. I had overcloced it before to 745 (or something) and it had worked fine so I thought about overclocking it to 850 (or something). As soon as I did that, it hanged for a while and then restarted.
Now everytime I start it, it restarts before I can do anything. All i managed was to enter the performance settings menu, but I cannot reach far enough to reset the CPU settings (it restarts)
Is there any other way I can reset the values, some file or something. I really don't want to reinstall everything.
What program are you using to over clock. Funnily this happened to me when I attempted to Oc (using setcpu) my legend to 864. However I installed the setcpu widget and I was able to change the speed asap. Maybe if you pressed fast enough then you might be able to restart before it restarts. But if all Is lost then factory reset is the way to go.
Sent from my Legend using xda premium
I was using the cyanogenmod 7 performance settings (settings>cyanogenmod>performance>cpu settings).
But I managed to reset it. I took out the memory card in hope that it will give me more time to reach the settings, and when I opened the CPU settings it was set to 600 MHz. looks like the settings were stored in memory card.
Hm
For future reference, don't check "restore on boot" until you know it's stable
Hi
In my case, overclocking is possible up to 844mhz, but I have reboot after few minutes. Max stable value is 806mhz (for me).
Maximal frequency depends of phone, every Legend are different. For one max is 768, for other maybe it 864.
Greetings
Sorry for my language
gosh... reading this post brings memory the last time i was messing with the performance thingy.... have to wipe my legend to get rid of the OC setting was my fastest option... but lost my unbackup data.
well you can try flashing your rom without wipe and hope things got back to normal.
on oc testing
my advice is this.... do your nandroid backup before doing OC testing...
if you have setcpu for OC testing... dont use the main bar to test oc...
but you can have setCPU to OC if certain condition like charging the phone is meet.
then if your system gone nuts just unplug the usb (not charging) and it will go back to main setting.
if you are using cyanogenmod performance setting.... do as TGF say.. do not set on reboot before you are sure that the system is stable...
plus you better nandroid backup first before messing with your phone...
My phone runs stable at 787............and I'm quite satisfied about the performance. But only because I have the power to, I'm thinkin about trying higher frequensies. Should I? Or it is an unnecessary risk?
Also, is there any preffered way to "try out" the performance once you set a new Max MHz?
I just installed CM9 beta1 and I'm having troubles with the overclocking. I tried the 768MHz but it freezes after a few seconds. Is there a way to overclock to a specific speed? I saw a while ago some guy saying that at aroung 728MHz it does a great job. I have kernel 2.6.35.13-htc-msm7x27-ics.
I got a bug, don't know if it's related to the ROM or the overclocking but when I set the minimum speed to 19MHZ, like on stock Legend, when I tried to wake my phone, it seemed to be stocked at 19MHz, so I couldn't do anything, had to take battery out. Happened to anyone else? It happened to me once since yesterday.
overclocking
I'm sure most of you probably know this but just in case..... If you get a program that allows you to see your logcat (google them) and clean the log of errors by removing problem apps or limiting their permissions. The result is you end up with a much more stable OS and you can then overclock a lot more heavy handed. With the changes, I very rarely have any problems and run at 864mhz. Hope it helps
Whip Jay said:
I just installed CM9 beta1 and I'm having troubles with the overclocking. I tried the 768MHz but it freezes after a few seconds. Is there a way to overclock to a specific speed? I saw a while ago some guy saying that at aroung 728MHz it does a great job. I have kernel 2.6.35.13-htc-msm7x27-ics.
I got a bug, don't know if it's related to the ROM or the overclocking but when I set the minimum speed to 19MHZ, like on stock Legend, when I tried to wake my phone, it seemed to be stocked at 19MHz, so I couldn't do anything, had to take battery out. Happened to anyone else? It happened to me once since yesterday.
Click to expand...
Click to collapse
What governor are you using? If your using power save or conservative that will defenitly cause it.
Sent from my Legend using XDA
I could never overclock my Legend. Always near-instant reboots . Consider yourself lucky if you can!
I have a weird situation with my Atrix. I unlocked and rooted the Atrix and installed CM10 with "those" libs and the CPU never ran higher than 456 mHz. I tried setCPU to make the miniumum 700-1000 to try and see if it would run at a higher frequency and it would just sit at 456. I then flashed the second CM10 with "those" libs after reset and wipe and still the CPU is just sitting at 456. I think this might be causing me to have mediocre battery performance. I wiped everything multiple times and flashed AtrICS rom and then fixed permissions but still the CPU was sitting at 456. I found this thread about pdsfix http://forum.xda-developers.com/show....php?t=1131649 and tried both methods and wiped the cache through fastboot but no change in the cpu max. I've wiped everything multiple times and no change has occurred. I also tried ramfix even though my ram was being reported correctly. I'm using the newest version of TWRP and everything on the phone seems to run well. I am just wondering if anybody thinks it is just a reporting issue for the CPU and that 456 really means 1000 mHZ or if there is something in the kernel that is screwy.
I have attached a screenshot of CPU speeds after I ran a benchmark test. Let me know if you have any ideas on this phenomena. Thanks
What happens with cm7?
Sent from my MB860 using Tapatalk 2
I'm currently running Neutrino 2.91 cm7. The processor is hitting 1000mHz and all frequencies in between. There is a post in the Q&A section which has some log information on the issue. http://forum.xda-developers.com/showthread.php?t=1942247. It looks like a kernel issue but it is odd only two or three people have commented on it.
I've been experiencing this as well, although it does get through all the frequencies. After awhile, around 20+ mins, it goes back to the same frequency. Kinda annoying when you need that extra boost.
Nevertheless, I really am waiting patiently fr the things to get sorted out. Ever since that "takedown", its kinda messy around
I wonder I'd the CPU has a safe mode that kicks in due to temperature. I guess it could be some sort of setting that turns on a governor (deep sleep) but it is activating at the wrong time.
Sorry to bump such an old thread but I believe the previous poster was correct. I just went back to ICSRom to investigate, and sure enough my CPU temp is reading 450°C! Now, since my Atrix hasn't turned into a puddle of molten plastic, I guess now I've got to try and work out how to correct/disable this reading without kernel source. Sigh.
Edit: /sys/class/hwmon/hwmon0... Can't change any parameters though
Edit 2: I may be wrong, it hasn't tripped any thermal alarms. I just think SetCPU is out by a factor of 10. Temp1 is currently reading 43000 (43°C?) And the critical threshold is 127000 (127°C?) which appears to be the maximum. It is possible to set it lower than the default, but not higher.
Some of you might have encountered this, and some of you possibly could in the future (let's hope not), but this will hopefully be of help. I once had a problem with my Live with Walkman in which it boots up until it reaches the homescreen before entering a bootloop. Strangely enough, it also happened to two of my friends who owned SE 2011 MDPI devices as well. These are some of my observations:
Bootloops when network is in GSM (2G) mode
If in WCDMA/GSM mode, phone bootloops the moment 3G signal is lost
Phone works without SIM card, but bootloops when a certain load is placed on the CPU (rebooted when I played Minecraft)
With that said, I've tried formatting my SD card and resetting factory settings a hundred times over; I was even in between firmwares, ROMs, and kernels, but to no avail. In my desperation, I tried using the battery from my then-girlfriend's Xperia X8 (my phone and hers have the same type of battery, EP400), and it miraculously cured the bootloop. I did buy a new battery, and my phone was as good as new. When the same thing happened to my two friends, using a new battery also did the charm. There were a few problems with the new battery though. I'll list the possible solutions I've found.
BATTERY MISCALIBRATION (sudden drop to 0 or misreading)
Reason/s: It may just be a kernel problem, or your phone might be adjusting to the new battery.
Solution/s: Try installing a different kernel. If it does not fix this, drain your battery to 0, then charge it fully offline. Keep repeating until battery is calibrated.
NOTE: Battery calibration apps won't really do much - you don't necessarily need them.
Click to expand...
Click to collapse
SUDDEN REBOOTS
Reason/s: You're probably putting too much weight on the CPU or GPU (more likely if you're a gamer), or you might have overclocked your device and is using a governor that hangs around in the higher frequencies.
Solution/s: If you really are a gamer, I'd suggest using GB - you won't really need to overclock as it's great performance-wise. If you must overclock, never go beyond 1.4 GHz (this is the default CPU frequency of the Xperia Arc S), as it may kill your new battery. Also, try to avoid gaming or using your CPU heavily for long periods of time. Our phones need to rest too.
NOTE: For help on kernel governors, check out THIS AWESOME GUIDE by zhanjia.
NOTE: The said problem is more likely to occur on higher versions of Android, as they naturally consume more power, CPU, and RAM.
Click to expand...
Click to collapse
Other than those two, I've had no other problems. If this ever happened to you (again, let's hope not), always check the software first. If it does not fix the problem, you can try doing what I did.
P.S. I'm not saying that you should stick with Gingerbread if you encounter the battery miscalibration and the sudden reboots. You are absolutely free to use any ROM (we have a handful here on XDA, and we have our fantastic developers to thank for that). Cheers!