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!
Related
OK, so I'm on GSB 3.4 (though this issue began with 3.3), and I'm having a problem with my phone rebooting (screen cuts off after about a second, and the phone immediately reboots to the skateboard screen) at the following times:
1. Whenever I attempt to wake the phone from sleep.
2. Whenever I hang up a phone call.
3. Whenever I get a phone call while the phone is asleep.
4. Whenever I plug the phone in to charge while the phone is asleep (be it a wall socket or PC) [see below].
These problems only occur when the phone is NOT plugged into a charging source; the problem appears to be nonexistent in this scenario. But as soon as I unplug, all 4 become auto-crash scenarios.
I tried going back to GSB 3.2, but no dice. I then resorted to the stock-ish XTRsense ROM, which fixed the issue, but going back to Froyo just was too big a downgrade for me.
Throughout this process, I full-wiped multiple times, hoping to track the issue to an app or setting, but even before restoring anything through TBU (I think I may have just let the phone go to sleep at the "Touch the Android" initial setup screen once), the problem persisted, eliminating apps, settings, or CM7 CPU modifications as possible culprits.
I've continued to play with CM7 CPU settings even up till now, but I'm not getting much of anywhere. I've now resorted to the "Caffeine" app, which just never lets the phone go to sleep, and I just turn the brightness down or activate the "Desk Clock" mode in the default Clock app to save battery.
HELP?
Have you tried Tazz's ROM or CondemnedSoul's ROM, just to see what happens with those? CS's ROM uses ADW as the default launcher (not sure about Tazz's) - perhaps it's something with LauncherPro?
Had this happen once
Sent from my Aosp Gin-Tazz using XDA App
My phones use to freeze on the unlock screen, it happened in multiple roms. i switched back to the "ondemand" governor and it hasn't happened since. not sure if it the same issue but it might help.
My last name is also Schultz ....
Sent from my Aosp-Gin-Tazz using XDA Premium App
Guys, just thought I throw out the idea that it might an overclocking (i.e., hardware) issue?
I see that the Conap's CFS kernel that GSB 3.4 uses is max clocked at 604 MHz, but maybe that's too high for your particular phone?
I also think that schultzmd's comment about the ondemand governor helping might point to the clock stepping to a higher speed when coming out of sleep (and being related to clock speed). Maybe try running the phone at a lower speed just to see if its better behaved might prove instructive.
Just a thought...
Cheers!
scary alien said:
Guys, just thought I throw out the idea that it might an overclocking (i.e., hardware) issue?
I see that the Conap's CFS kernel that GSB 3.4 uses is max clocked at 604 MHz, but maybe that's too high for your particular phone?
I also think that schultzmd's comment about the ondemand governor helping might point to the clock stepping to a higher speed when coming out of sleep (and being related to clock speed). Maybe try running the phone at a lower speed just to see if its better behaved might prove instructive.
Just a thought...
Cheers!
Click to expand...
Click to collapse
Sounds familiar: http://forum.xda-developers.com/showpost.php?p=14016867&postcount=5186
I'll try the changing the max, but I know I've tried as low as 604 max (19 min) with the problem persisting, and as high as 710 or 768 before GSB 3.3 (when the problem started) with no major issues. And I had already been using Ondemand when the problem started, having stopped using Smartass when I thought it slowing the performance down a bit. Any other governors I should try?
And does the overclocking issue not apply when a phone is charging?
doogald said:
Sounds familiar: http://forum.xda-developers.com/showpost.php?p=14016867&postcount=5186
Click to expand...
Click to collapse
lol, doogald...I had no idea .
I should know better than to come in to any thread you've already weighed-in on and know that you've already exhausted all the possibilities.
I'll leave the Op to your very capable hands.
Cheers and thanks for keeping an eye out here on XDA and over at AF too (and probably six or seven other sites ).
natemup said:
And does the overclocking issue not apply when a phone is charging?
Click to expand...
Click to collapse
Well, you are introducing some extra heat into the equation while charging, which might be enough to tip the balance against you if it is indeed an overclock issue.
scary alien said:
lol, doogald...I had no idea .
I should know better than to come in to any thread you've already weighed-in on and know that you've already exhausted all the possibilities.
I'll leave the Op to your very capable hands.
Cheers and thanks for keeping an eye out here on XDA and over at AF too (and probably six or seven other sites ).
Click to expand...
Click to collapse
You would have only seen that if you had seen the post in the GSB thread, of course.
I am still going to suggest trying Tazz or Condemned. From what the OP says, he should be able to see that it's having the same issue pretty quickly.
But, just to rule out the OC issue, you could try setting the max to stock 528 and see if it still happens.
doogald said:
You would have only seen that if you had seen the post in the GSB thread, of course.
Click to expand...
Click to collapse
lol...that post was on the 519th page of (currently) 530 pages! (I read the first page, does that count? )
Still crashing on 528 max / 19 min...
natemup said:
Still crashing on 528 max / 19 min...
Click to expand...
Click to collapse
How about on Tazz or Condemned? And, 19.2 is too slow for a minimum for this kernel. 245 should be the minimum.
scary alien said:
Well, you are introducing some extra heat into the equation while charging, which might be enough to tip the balance against you if it is indeed an overclock issue.
Click to expand...
Click to collapse
I was inquiring as to why the issue DOESN'T happen when I'm charging. I'm not sure if that's what you were saying, but I have no issues while the phone is charging; it's weird, because CM7's CPU governor doesn't allow profiles for "screen-off", "charging", or anything like that. It just seems to make my problem more random and untraceable. It literally is happening on EVERY CPU setting, even 480 max (which to me, is just pointless to actually use)
I've full-wiped so many times in the last few days, I'm wary to just try a different Gingerbread ROM when GSB is (was, for me) so stable and full-featured. I'm trying my darnedest to just stick it out and charge-charge-charge to avoid the issue.
One more thing: if, right after the phone reboots itself, I unlock it before the screen goes off and manually put it to sleep and quickly wake it back up, the issue usually doesn't occur (and I can keep doing this, putting it to sleep and waking it back up again, with no issue). But if I unlock it and let it sit and reach the screen timeout itself (or never unlock it after it reboots, then let it sit for a while), the problem reoccurs.
natemup said:
I've full-wiped so many times in the last few days, I'm wary to just try a different Gingerbread ROM when GSB is (was, for me) so stable and full-featured. I'm trying my darnedest to just stick it out and charge-charge-charge to avoid the issue.
Click to expand...
Click to collapse
I have used both GSB and Condemned and you will not be missing anything. I stopped using GSB because I could not get market updates to stick reliably. I do not have that issue at all with Condemned.
Right now the only issue with the latest Condemned is apparently a GPS issue, so I would go with V6 or V7 rather than V8 for now until CondemnedSoul gets an update. Or, if you don't navigate, go ahead with V8. It's just fine.
You're obviously having a stability issue with GSB now, so you have nothing to lose but about 45 minutes of time and a Nandroid Restore to go back to GSB if you don't like it.
So, I had a minor issue that was fixed by switching to a different ROM. It's worth a try.
I wish you luck finding a solution.
natemup said:
I was inquiring as to why the issue DOESN'T happen when I'm charging. I'm not sure if that's what you were saying, but I have no issues while the phone is charging; it's weird, because CM7's CPU governor doesn't allow profiles for "screen-off", "charging", or anything like that. It just seems to make my problem more random and untraceable. It literally is happening on EVERY CPU setting, even 480 max (which to me, is just pointless to actually use)
Click to expand...
Click to collapse
Nate,
Sorry about that ...I was confused from where you asked in post #8 about whether or not overclocking was in effect while charging (it can/could be, depending on the overclocking monitor/govenor I suppose) and I had lost that point from your original post.
I would say take doogald's advice and switch to at least some other ROM since that would help indicate if it is indeed a software issue or a hardware issue. Its sounding like its not clock-speed related given the things you've already tried. If you've still got issues on other ROMs, that would tend to point to some hardware issue (our Erii are getting a little long in the tooth at this point, after all).
You could even flash back to stock and see if the phone is still stable there since you can always re-root and re-restore your Nandroid backups.
Good luck...I hope you figure something out.
Problem is alive and well on Condemned GB. *sigh*
XTRsense was fine and flawless, but going back to Froyo after months on gingerbread was just too depressing for me...
Sent from my ERIS using XDA App
I'm going to make one more suggestion - not sure if you have tried this yet, but try flashing GSB from a full wipe. When you go through the setup, DO NOT LOG IN TO YOUR GOOGLE ACCOUNT. After the launcher starts, go into the market, let it log you in to your Google account then, and then install all of your apps and change all of your settings from scratch.
When you log in with your Google account when installing a CM ROM, it tries to restore your apps and settings from your last CM ROM install. It may be that you have some weird setting or app that is causing this that you just keep reinstalling when you flash the ROM and log in with your account.
If you've already tried this, then try running xtrSENSE or xtrROM instead. They are both excellent ROMs and clearly your phone likes them better.
[edit] Oh, and try leaving your min at 245 MHz for a while. See if that helps your phone run better. It should, and it should have the exact same battery life as 19.2, as nonsensical as that sounds.
It is literally happening as soon as I boot the phone after a fresh GB install. I four-corner the Android setup screen, let the screen time out, and boom I'm screwed.
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 just installed the new Siyah 3.2b1 kernel to run my ShoStock 2.2.2 ROM last night and everything was working fine. I didn't make many changes other than switching the governor to lulzactive and the i/o scheduler to noop.
It was running fine over night (lost 0% battery).
Then today after I used the phone for a few minutes the battery seemed to drain a little quicker. I know its too early to complain about battery life but I decided to investigate. When I checked cpuSpy it showed that all of the frequencies were barely used (mostly spent in deep sleep over night) but the 1200 mhz frequency was used most after that (significantly more than the others). When I went back into voltage control (same thing with setcpu) I noticed that it seemed to be stuck at 1200 mhz. The only thing that fixed it was changing the governor.
Does anyone have any ideas on whats causing this and how to fix it (I had great battery performance on lulzactive before so would like to use it again)?
Just try clearing app data rebooting and reinstalling the app. That problem has happened to me every once in a blue moon and that fixed it for me.
Sent from my SGH-I777 using Tapatalk 2
Thanks, I'll try reinstalling the kernel.
Which app are you referring to? because I had this problem no matter which app I used to change the governor (Extweaks, voltage control, setcpu).
Use Jivy's Kernel cleaning script prior to flashing, and try again.
http://forum.xda-developers.com/showthread.php?t=1428530
Ive used the kernel cleaner every time I installed a new kernel. It didn't seem to work this time. But thanks for responding.
bacon_n_icecream said:
Ive used the kernel cleaner every time I installed a new kernel. It didn't seem to work this time. But thanks for responding.
Click to expand...
Click to collapse
It's the lulzkernel for some-reason :|
I have problem goto smartassv2 it's ok just steps heavy
Thanks for your suggestion. I just moved over to ondemand and its been ok for me. Too early to make any judgments but I'll try smartassv2 next.
Not that I'm glad to that you're having problems, but I'm glad I'm not the only one with this issue. Thanks for the response
Winklie said:
Use Jivy's Kernel cleaning script prior to flashing, and try again.
http://forum.xda-developers.com/showthread.php?t=1428530
Click to expand...
Click to collapse
DONT use kernel cleaning scripts. They cause more problems than good.
Sent from my AT&T I777 running AOKP build 3X
I haven't had any issues with using the kernel cleaning script thus far.
What kind of harm can they cause? and do you have any recommendations on how to clean up before switching kernels or is just flashing them over ok? (A lot of people recommend the script cleaner and it seemed to have solved a lot of peoples issues kernel issues)
bacon_n_icecream said:
I haven't had any issues with using the kernel cleaning script thus far.
What kind of harm can they cause? and do you have any recommendations on how to clean up before switching kernels or is just flashing them over ok? (A lot of people recommend the script cleaner and it seemed to have solved a lot of peoples issues kernel issues)
Click to expand...
Click to collapse
Wipe cache, wipe dalvik. I've read more problems with the cleaning script than good.
Sent from my SGH-I777 using Tapatalk 2
thanks, I generally do that any way along with the script cleaner
K Rich said:
Wipe cache, wipe dalvik. I've read more problems with the cleaning script than good.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Lol what exactly have u heard? If it was causing problems it would get pulled. The only thing I can foresee happening is someone flashing it and then not flashing a kernel or something. Which would be user error.
Sent from my SGH-I777 using Tapatalk 2
CPU related as well...
Hi Guys,
My first post here. I am total noob. I rooted and installed the newest ShoStock2 on my at&t galaxy s2. Everything works perfectly. I couldn't be happier. I also went bought the setCPU for overclocking it. That too seem to be working fine.
My question is. I didn't set up any voltage requirements. The only thing I did was to set it to 1600 MHZ and 200 min and change the governor on the bottom to Lulzcrative. Will this work? Do I need to actually do something with the voltage? am I really on 1600 right now? I cannot tell.
I ran a quad test (I now it is meaningless in real world) it came 2818 yesterday. I ran it again this morning ..... It froze and took my battery from 45 to 9 in less than 3 mins!!!!!! The phone got really hot. I took out the battery right of way. The battery life showed 23 percent this time.
I got little afraid of the quadrant testing ... The phone seems to run good without that but I am not sure if it is set up how it is suppose to.
Could someone help me out please? I tried reading the forums and that is where I got the idea in the first place to overclock it.
So to summarize it, I guess phone is fine right now but I am not sure if I set up setcpu out properly.
I am on the newest shostock2. I have galaxy s2 on att. I am pretty good with computers and phones but not sure about voltage and other problems with relating to setCPU.
Thank you advance for helping me out.
kbulut said:
Hi Guys,
My first post here. I am total noob. I rooted and installed the newest ShoStock2 on my at&t galaxy s2. Everything works perfectly. I couldn't be happier. I also went bought the setCPU for overclocking it. That too seem to be working fine.
My question is. I didn't set up any voltage requirements. The only thing I did was to set it to 1600 MHZ and 200 min and change the governor on the bottom to Lulzcrative. Will this work? Do I need to actually do something with the voltage? am I really on 1600 right now? I cannot tell.
I ran a quad test (I now it is meaningless in real world) it came 2818 yesterday. I ran it again this morning ..... It froze and took my battery from 45 to 9 in less than 3 mins!!!!!! The phone got really hot. I took out the battery right of way. The battery life showed 23 percent this time.
I got little afraid of the quadrant testing ... The phone seems to run good without that but I am not sure if it is set up how it is suppose to.
Could someone help me out please? I tried reading the forums and that is where I got the idea in the first place to overclock it.
So to summarize it, I guess phone is fine right now but I am not sure if I set up setcpu out properly.
I am on the newest shostock2. I have galaxy s2 on att. I am pretty good with computers and phones but not sure about voltage and other problems with relating to setCPU.
Thank you advance for helping me out.
Click to expand...
Click to collapse
Lots of questions there. Phone overclocking is the same and at the same time different than PC overclocking. I too bought SetCPU and due to bugs and problems have completely abandoned it. Honestly with the exception of running an epeen benchmark there is little incentive to overclock. Find a newer Kernel (I use NEAK which has no overclocking ability) and install it, performance is stellar. You really have to ask yourself, is my phone slow enough that I need more CPU power to make it faster?
To see what time your CPU is spending at a given clock speed, download CPUSpyhttps://play.google.com/store/apps/details?id=com.bvalosek.cpuspy&feature=nav_result#?t=W251bGwsMSwyLDNd, you will be surprised to see your phone spend very little time at it's max clockspeed.
Due to the immaturity of the fab process for our CPU's (well SoC), what is a stable overclock for one person might not even load for another. These CPU's are not like an Intel Sandy Bridge, with 1Ghz of free overclocking, nearly guaranteed. You can certainly play with voltages to try and attain a higher overclock, but at the expense of CPU lifetime, as well as battery.
Additionally, it takes a new Kernel 3 or so full charge, discharge cycles on a phone to really 'settle in' and 'learn' a particular phones battery, while yours got hot, which to me indicates an endless loop of some kind running in the background.
My advice would be as follows: Choose a ROM you like, feel free to play with different Kernels, again, I use NEAK, which does not work for some folks, or crashes or whatever. Give it several days to 'settle in' and if your still not happy with performance or have stability problems, try a different governor/scheduler. You really need to establish a good, solid baseline of your phones performance and make small changes and give them long enough to establish any changes to your phones overall stability. Basically running cowboy through your phone and making changes will have a negative overall outcome. Make small, documented changes, test and see what overall effect this has to your phone's stability and battery life, and make another change.
bacon_n_icecream said:
I just installed the new Siyah 3.2b1 kernel to run my ShoStock 2.2.2 ROM last night and everything was working fine. I didn't make many changes other than switching the governor to lulzactive and the i/o scheduler to noop.
It was running fine over night (lost 0% battery).
Then today after I used the phone for a few minutes the battery seemed to drain a little quicker. I know its too early to complain about battery life but I decided to investigate. When I checked cpuSpy it showed that all of the frequencies were barely used (mostly spent in deep sleep over night) but the 1200 mhz frequency was used most after that (significantly more than the others). When I went back into voltage control (same thing with setcpu) I noticed that it seemed to be stuck at 1200 mhz. The only thing that fixed it was changing the governor.
Does anyone have any ideas on whats causing this and how to fix it (I had great battery performance on lulzactive before so would like to use it again)?
Click to expand...
Click to collapse
Lulz has known problem in 3.2b2-1
Gokhan has fixed it in 3.2b2 - 2
Wait for ktoonsez to update it for us
Sent from my SGH-I777 using Tapatalk 2 Beta-6
Thank you so much for the information. Could I simply uninstall the setcpu and go back to normal? Simply reflash the rom and/or kernel? I really like shostock2 with the cherry picker kernel for now. I want to give them a week of try to make my mind. Before the setcpu I think.I was better off
Thanks for the help by the way. I appreciate it.
Thanks for the update about the new siyah kernel. Glad it wasn't just me with the issue. I was going to post this question in the siyah thread but am new to the site so didn't have permission so thanks for finding me all the way over here
Phalanx7621 said:
Lol what exactly have u heard? If it was causing problems it would get pulled. The only thing I can foresee happening is someone flashing it and then not flashing a kernel or something. Which would be user error.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
I'm just going off what I've seen in the Siyah/NEAK threads. Most of the lock-ups/random reboots I've heard people having had used the cleaning script. Either that or its just coincidence.
I may be wrong but I think that using the kernel cleaning script actually solved most of the lockups. Perhaps I misunderstood the threads.
bacon_n_icecream said:
I may be wrong but I think that using the kernel cleaning script actually solved most of the lockups. Perhaps I misunderstood the threads.
Click to expand...
Click to collapse
Hmm, well I've just manually wiped cache and dalvik and have never had problems between roms/kernels.
Sent from my SGH-I777 using Tapatalk 2
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.
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 ..