Database Users

Does anyone have any Overclocking horror stories?

I've just begun overclocking my 8125. starting at 220 and i'll work my way up slowly to a maximum of 265 if possible.
I was wondering if anyone had any horror stories that would make me change my mind about overclocking. Like permanantly damaged devices. I've searched the forums and cant find a single one, which leads me to beleive that it truly is completly safe. But i thought i'd start this thread to make sure.

The worst that I've had happen to me (or heard of happening to someone else) with overdoing the overclock is the device showing the 'white screen of death' which just forces you to soft-reset your device. It's really not anything that bad ^_^

k2snowboards88 said:
I've just begun overclocking my 8125. starting at 220 and i'll work my way up slowly to a maximum of 265 if possible.
I was wondering if anyone had any horror stories that would make me change my mind about overclocking. Like permanantly damaged devices. I've searched the forums and cant find a single one, which leads me to beleive that it truly is completly safe. But i thought i'd start this thread to make sure.
Click to expand...
Click to collapse
i've been overclocking at 242 or 260 for over 2 months now and I haven't had any problems. My sweet spot is 242, it runs GREAT on this speed and it is a tad more stable than 260.

It is possible to brick your device if you try a speed to fast. 240 is perfectly safe, anything above that can be unstable.

I know its possible to fry a chip through overclocking. I remember frying one of my amd k6-2 processers awhile backl. I just find it odd that even though its possible to fry your wizard. and so many people overclock, that i haven't heard one story about a wizard being broken this way.

I know its possible to fry a chip through overclocking. I remember frying one of my amd k6-2 processers awhile backl. I just find it odd that even though its possible to fry your wizard. and so many people overclock, that i haven't heard one story about a wizard being broken this way.

Been running mine @ 240 for a while now and everything seems fine.
My phone is mainly on stand-by during the day, but when I do use it for extended periods (evenings and weekends) I use Wi-Fi a lot and read a lot of ebooks which can be quite power consuming - however, the overclocking seems to have no noticeable affect on the phone other than making it quicker...

afaik
MOST "PORTABLE" CPU'S CAN MUCH FASTER THAN THEY DO BUT AT THE COST OF POWER THE CPU'S ARE "UNDERCLOCKED" TO SAVE POWER
SORRY MY CAPS IS STUCK AND i JUST NOTICED IT...
BHANG

afaik
MOST "PORTABLE" CPU'S CAN MUCH FASTER THAN THEY DO BUT AT THE COST OF POWER THE CPU'S ARE "UNDERCLOCKED" TO SAVE POWER
SORRY MY CAPS IS STUCK AND i JUST NOTICED IT...
BHANG

overclocking after standy freezes for a while!
This query is not related to the thread, but forgive me as I didn't want to start a new one.
I've smarskey with the overclock feature enabled and omapclock.exe running nicely. It hasn't been giving me trouble at all. However, I've one problem..
After the phone goes in standby after a period of inactivity and when I hit the power button again to use the phone, I notice a freeeze in time display. It takes a while before time changes from say 11:30 to 3:30.
I know Smartskey 'wakes' up the overclocking process again and this maybe the reason why my phone somewhat freezes for a very brief period after I disturb the standby mode, but I was wondering if anyone has a solution to this, its kinda annoying.
Thanks

Does not sound that bad, I think your problem is that you can't just take your phone out to have a look at the time :wink: am I right?
Well perhaps that would really be kinda annoying.
But it also sounds like there is no real solution to this. Just try reinstalling the apps, certainly there is a software conflict (if this is not a normal effect).
Perhaps you can also use another possibility than smartskey. I think BatteryStatus and OMAPScaler also have options to overclock at wakeup.

thanks..
maati said:
Does not sound that bad, I think your problem is that you can't just take your phone out to have a look at the time :wink: am I right?
Well perhaps that would really be kinda annoying.
But it also sounds like there is no real solution to this. Just try reinstalling the apps, certainly there is a software conflict (if this is not a normal effect).
Perhaps you can also use another possibility than smartskey. I think BatteryStatus and OMAPScaler also have options to overclock at wakeup.
Click to expand...
Click to collapse
thanks for the advice, i'm thinking about using memaid.

issues with SetCPU

i had SetCPU installed on my phone, and when the phone would shut the screen off, by timing out or being locked, it wouldnt wake up from sleep.. i know at least one other person this has happened to, but removing SetCPU got rid of that problem.. does anyone know whats up?

You're lucky. SetCPU didnt even work on my SGS. It just FC'd everytime I loaded it. I didnt have root, which probably accounts for this issue, however it should still load up - just with locked speed setting bars.

I had the exact same problem you have mentioned below. I also get this issue with the autokiller app.
soraxd said:
i had SetCPU installed on my phone, and when the phone would shut the screen off, by timing out or being locked, it wouldnt wake up from sleep.. i know at least one other person this has happened to, but removing SetCPU got rid of that problem.. does anyone know whats up?
Click to expand...
Click to collapse
Sent from my GT-I9000 using XDA App

I'm pretty sure that SetCPU won't work with the SGS as things stand, root or not, for changing the clock rate (unless that built-in thingamagig for unlocking HTC phones' clock rates works).
Did you make sure no default profiles were set up when you installed SetCPU that were set to underclock the CPU or do anything else weird when the phone goes to sleep/is idle? That would be a good place to start.

If anyone could get me a log (force close/crash) or a /proc/last_kmsg (reset) that would be great.

coolbho3000 said:
If anyone could get me a log (force close/crash) or a /proc/last_kmsg (reset) that would be great.
Click to expand...
Click to collapse
You, sir, are a credit to this forum.

coolbho3000 said:
If anyone could get me a log (force close/crash) or a /proc/last_kmsg (reset) that would be great.
Click to expand...
Click to collapse
I'm sure someone's probably told me before, but how would we do this?
I installed SetCPU, I have root, but it just FC all the time

When rooted setup works fine as long as you just use it for monitoring and don't change the profile
Sent from my GT-I9000 using XDA App

Okay, that's odd. It's worked this time, although I did nothing different.
coolbho3000, tell me what I need to do to send a logcat and I'll use profile to see if it crashes. For me, profiles are rather important, when the screen is off I want to limit it to like 200mhz or something.

i figured out why SetCPU makes my phone never wake up, the settings i was using was ondemand 100 min 1000 max. SetCPU is set to 100 in standby and this is just too slow and puts the phone completely to sleep.
ive since moved up the phone to 400 min and ive gone a day without any sleeping.
and SetCPU works fine on my phone, and a few friends who have the phone aswell, this was our only problem, and i dont believe it was a problem, its just the way the app is designed, to give full control, leaving the only room for error on our hands..
but still an fyi would be nice lol.. i read the entire huge description of SetCPU, like a half hour read

Try setting the scaling to 'ondemand' or 'performance' if it was set to 'conservative' as default (mine was).

AndyCr15 said:
Okay, that's odd. It's worked this time, although I did nothing different.
coolbho3000, tell me what I need to do to send a logcat and I'll use profile to see if it crashes. For me, profiles are rather important, when the screen is off I want to limit it to like 200mhz or something.
Click to expand...
Click to collapse
Logs can be done by getting the Log Collector app from the Android Market. Or, you can plug it into a computer with ADB and run:
adb logcat
I'm interested in the FC crash and why it works for some and not others.
Thanks

In fact, everything seems to work for me too....

I'm especially interested overclocking this thing, as it's the 45nm ARM CPU released in an Android phone en masse. I might get myself a Vibrant if it gets rooted.

The whole problem is that the default is conservative... changing it will cause phone to freeze.
Sent from my GT-I9000 using XDA App

lgkahn said:
The whole problem is that the default is conservative... changing it will cause phone to freeze.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Then change the Freq Step in Advanced to 100%, should have the same effect as ondemand.

lgkahn said:
The whole problem is that the default is conservative... changing it will cause phone to freeze.
Click to expand...
Click to collapse
Ahh, I was getting the 'not waking' issue that was mentioned before.
coolbho3000 said:
Then change the Freq Step in Advanced to 100%, should have the same effect as ondemand.
Click to expand...
Click to collapse
This will fix it not waking? Is this better than making the minumum to be 400mhz?
When it was not waking, I changed all the minimums to 200mhz, but it was still dropping to 100mhz? Why would it do this?

With my phone rooted didn't work on first install, whenever I launched it, it kept crashing so I uninstalled and installed back and it works perfect

I went through the whole resetting to factory defaults several times until I determined not coming back from sleeping was setcpu.
I do not think it is a crash problem.
I had the scaling set to ondemand.
Do we know what the minimum CPU speed is for the samsung? I had it on 200 and still had a problem. If I have min at 400 is there a point in using setcpu, because the existing OS will scale for us?
I really loved the product, but I need to feel like we have a more confident answer to this problem.
Kudos to coolbho3000 for a great product. For the avoidance of doubt, I purchased the product.

I'm having a lot of trouble with this app too...
So I'm returning it until someone can post some settings that work flawlessly

We can now overclock our phones!

Couldn't really see any discussion on this yet, and personally it's in a location on the forum that I rarely visit but I've found an overclock tool that is slowly becoming very good indeed for our processors. Link to thread is here. I'm soo far up from 528Mhz to 748Mhz (been stable for the past 6 hours no problem). Just make sure to follow the thread (instructions are linked to ensure overclock remains applied through scripts and 3rd party apps). Should take no longer than 30mins for a well versed user to set up. Please don't try this if you haven't got a clue what you are doing as there is soo much scope for error and dead phones! You may also need to customise any scripts to your specific phone/software build. CDMA phones as usual are different from what I've heard. But anyway good luck, I'm gonna keep trying to push the Mhz up (aiming for 850Mhz ).

Not sure its a good idea to go past 700 mhz,our phones run hot as it is under capacity,as with gaming rigs heat is your Enemy,the cooler you keep it the faster.

It's actually remained pretty cool, and when it's in my pocket it's only running at stock clocks anyway. Only when I'm using it does it get to the full 748Mhz. Running wifi router and charger and temps are not noticeably hotter than usual...

um... ive been clocked up to 787 highly stable for the last like 2 weeks. No heat problems, no battery problems, just insane speed.
recommendations: Download v1, not v2. ESP if you dont know what you're doing. Then download the zip im attaching, there's 2 mortscripts in there and a registry addition, THESE MUST BE IN THE STORAGE CARD ROOT. use the regisitry addition FIRST (just associate w/e regedit software you use, then run the .reg file in total commander), then go back to total commander, edit the .mscr "Toggle_boost" and adjust the value boost = "x" to whatever value you want the phone to OC at, eg boost = 41 is 787mhz which is stable for me, test yours out.
THEN, open and install rhodiumkbdcontrol (attached), reboot, go to settings>system>keyboard config> add key
1st pick which key you want to be the OC boost swtich, I have it mapped to my PTT button. click the plus sign, drop down menu, run program, then highlight "run program" in the list then click "..." then type in
Program: \windows\mortscript.exe
Arguments: "\storage card\toggle_boost.mscr"
This time you wanna use the power key.
same general instructions except
Program: \windows\mortscript.exe
Arguments: "\storage card\boost_off.mscr"
then plus sign again, drop down menu, default key action, and click extended emulation. THEN hit update config. should work like a charm, also autoover clocks to 610, the boost button with send you up the w/e the boost = "x" is set to, and then back again, most find 710mhz to be the stable point, and feel free to ask questions

sorry, heres the zips

wouldnt overclocking also gives you a higher chance of frying your CPU chip? cuz ive seen it happened in PCs i just idk about PPCs

I agree that there are virtually no ill effects to this. When unlocked, I have my phone running at 787 mhz. While it is locked or sleeping it throttles down to 604 and eventually 528 mhz. I have noticed no extra heat nor extra drain on the battery. Just blazing fast speed! Sense 2.5 is virually not laggy at all! CHT 1.8.5 is so smooth and quick even with the aminations enabled!
If anyone is interested in the automated clocking process, I can help by giving my set-up that is working flawlessly on the ROM in my signature!

miked79928 said:
I agree that there are virtually no ill effects to this. When unlocked, I have my phone running at 787 mhz. While it is locked or sleeping it throttles down to 604 and eventually 528 mhz. I have noticed no extra heat nor extra drain on the battery. Just blazing fast speed! Sense 2.5 is virually not laggy at all! CHT 1.8.5 is so smooth and quick even with the aminations enabled!
If anyone is interested in the automated clocking process, I can help by giving my set-up that is working flawlessly on the ROM in my signature!
Click to expand...
Click to collapse
Yeah could you hook that up? I think posting it here would be best but pm'ing works just as well
Edit:
I just read threw the above links and guides and was wondering if there is a more automated way of setting this up rather than having to link it to a button press. I'm guessing this has not been figured out yet (or the guides would have mention of it ). Just curious.

dantegl36 said:
Yeah could you hook that up? I think posting it here would be best but pm'ing works just as well
Click to expand...
Click to collapse
Here is the best way I have found to do it. I take absolutely no credit for this:
http://forum.xda-developers.com/showpost.php?p=7354283&postcount=627

Check it!
Outlaw78a said:
Not sure its a good idea to go past 700 mhz,our phones run hot as it is under capacity,as with gaming rigs heat is your Enemy,the cooler you keep it the faster.
Click to expand...
Click to collapse
I have used this, NRG also does. I have NEVER had any problems and mine is as high as 787 as long as I'm running it which is constantly.
XITruthiX said:
um... ive been clocked up to 787 highly stable for the last like 2 weeks. No heat problems, no battery problems, just insane speed.
Click to expand...
Click to collapse
100% agreed. Been running at the highest speeds with NO problems, no batt drain, no heat probs, nothing.
XERO_Racer said:
wouldnt overclocking also gives you a higher chance of frying your CPU chip? cuz ive seen it happened in PCs i just idk about PPCs
Click to expand...
Click to collapse
Not unless you are having excessive heat problems. Since there are basically no people reporting these problems, I wouldn't worry.
miked79928 said:
I agree that there are virtually no ill effects to this. When unlocked, I have my phone running at 787 mhz. While it is locked or sleeping it throttles down to 604 and eventually 528 mhz. I have noticed no extra heat nor extra drain on the battery. Just blazing fast speed! Sense 2.5 is virually not laggy at all! CHT 1.8.5 is so smooth and quick even with the aminations enabled!
If anyone is interested in the automated clocking process, I can help by giving my set-up that is working flawlessly on the ROM in my signature!
Click to expand...
Click to collapse
Once again as stated earlier, 100% agreed.

Do I have to keep plugged in?

miked79928 said:
Here is the best way I have found to do it. I take absolutely no credit for this:
http://forum.xda-developers.com/showpost.php?p=7354283&postcount=627
Click to expand...
Click to collapse
I thank you for this, but I'm not sure how to implement it. I have installed Mortscript, I've copied the code into a file I called overclock.mscr and modified the code reflect the reg values on my Tilt 2. and I've placed the script on the root on my SD card. I've installed MSM7kCpuSpeed on to my SD card. How do I make the script run automatically?
Thank you!

I take no responsibility for w/e happens to your phone with this advice.
Try putting a pointer in your start up to the over clocking script. Its highly unstable and could brick your phone or require a hard reset... thats why I do it with a toggle switch, i dont mind manually applying the OC with a hard key knowing its safe, esp because the situations where I actually NEED 787mhz are less common than needing to just wake the phone to answer a call or make a txt message.

I just want to say that I have been running android on my tilt 2 overclocked at around 750 for a few months now with various builds and i know a lot of other users who have as well with no problems, i am going to try this out, thats what i pay for insurance for hehe
..and after reading more i may have spoken too soon because i missed the posts where i saw that you can brick your phone with OC in WinMo easily enough if you are not careful, so tread with caution

dirtypiratehooker said:
I just want to say that I have been running android on my tilt 2 overclocked at around 750 for a few months now with various builds and i know a lot of other users who have as well with no problems, i am going to try this out, thats what i pay for insurance for hehe
..and after reading more i may have spoken too soon because i missed the posts where i saw that you can brick your phone with OC in WinMo easily enough if you are not careful, so tread with caution
Click to expand...
Click to collapse
Just a note, I'm not sure the insurance would cover burning a custom ROM into the phone, or overclocking the CPU. And if the chip is fried you can't burn the stock ROM back in. But then, they probably couldn't figure out it was updated without in stalling a new CPU. Umm, it would probably work.

Would a .cab for this ever be conceivable?

At this point, we have finally got a script that will work for most Rhodiums, Topaz (Diamond 2), and a few guys with other phones seem to be having good luck.
The device has to have Mortscript installed, and nettrip's MSM7 v2.
It is a single script solution that requires no pre checks in the registry, no key/button assignment, and you can change the speed settings from the script instead of the registry.
It throttles the OC up and down for calls, lock, and sleep, to avoid freezing on wake up and in a call. Some problems that still need to worked out by nettrip in the script. I don't envy him the work as the script(s) were bad enough. Four of us have hit that original script (by jpc) from about page 13.
You copy the script to the SD or the device root, create a shortcut to the file, copy the shortcut to Windows\Startup directory, reset/reboot the device and you are off.
You can use the MSM7 app to read the OC, but you should make sure to exit the app before sleep, lock, or power off, as it will error on reboot if left open.
To be honest, you never have to open the MSM7 app, as the script controls it in the background.
I believe the script is set for a low over clock. 691. My experience has been a 710 average, but a lot get a stable OC at 750+. I am running 748 and I think I will stop there. A 200MHz overclock will just have to do.The phone does not get hot, though with intense use, it does get warmer. Never warmer than when the battery is charging, tho.
I am running the nrg Sense Reference ROM, 23xxx based on Sense 2.5. I added the CHT 1.8x and the editor to save a few MHz, no biggy.
The overclock allows the Sense to work MUCH smoother, actually noticeable as even the weather animation is smooth.
And all the vid players seem to work better.
I have noticed NO extra battery drain than usual.
The script is only a stop gap measure until nettrip finishes his app, but it does work well with little effort. WAAAAY better now than even last week.
However, use the script at your own risk, as you can get too Medieval on the OC. Some guys are running 800+, more nerve than I have.
Anyway, if interested in the script or want to read some more about the app, you can start here
http://forum.xda-developers.com/showthread.php?t=725290&page=89
post #882 has the script.
Plenty of instructions on how to use (and make changes to the settings) in the last 30-40 pages.

Sorry if this is already explained, but can someone tell me in simple details how to keep my overclock at 729mhz even after screen lock or sleep mode? I've tried to follow previous posts but it keeps reverting back to 528mhz after locking and sleep.

Ok so this seems legitamite,everyones checking in with no problems.
other than the increased risk factor that always accompanys speed,
it seems our ppc's cpu was underclocked beforehand ?
i will try this and see if i get a gpu boost as well.
but ivr already experienced my phone overheating to the point
of shutting itself down,and the god-damned orange light is permenantly on...

Two annoying problems on freshly rooted Aria (overclocking/wireless networks related)

Hi.
I just rooted my Aria and everything is going great. I installed an Overclocking widget that has a function to underclock when the screen goes off, but when it comes back on, the phone is so slow that the reset to proper clock speed takes forever - this annoyed me, so I removed the app.
The problem is, it still does it. Is there anywhere I can look to find out where this function resides and remove it so that the phone never changes its clock speed? I know its kind of a weird question. I went into Superuser Permissions and set the Overclock Widget to "DENY" hoping this would stop it, but it keeps it up!
Also, since installing the Liberated_Aria rom, my phone constantly disconnects from Mobile Wireless. If I go into settings and turn MW off and on, it works fine, until the next time the screen shuts off. Any ideas what might cause this? I doubt its related to the ROM, it just started happening around the time I flashed.
Sorry, Im pretty new to this stuff. I will clarify where needed if my explanations sucked.

Your not going to be able to underclock without a kernel that supports it.
Sent from my HTC Liberty using XDA App

ah ok, yeah, sorry, Im pretty new at this stuff and dont know much about it. Either way, it was setting it to 245mhz every time the screen shut off but I fixed it by removing the app, removing the privledges, and installing SetCPU which is maintaining the 600mhz the whole way through.
New question: can the Aria be overclocked? Is there any data available about what the acceptable thresholds are? Id like to get my emulators running a bit better. :O

mmazza said:
ah ok, yeah, sorry, Im pretty new at this stuff and dont know much about it. Either way, it was setting it to 245mhz every time the screen shut off but I fixed it by removing the app, removing the privledges, and installing SetCPU which is maintaining the 600mhz the whole way through.
New question: can the Aria be overclocked? Is there any data available about what the acceptable thresholds are? Id like to get my emulators running a bit better. :O
Click to expand...
Click to collapse
still need a kernel which supports clocking. doesnt exist yet for the aria/liberty

Doesn't the aria throttle itself anyways? I remember reading that it runs at ~480mhz when idle.
Sent from my HTC Liberty using XDA App

pcruz said:
Doesn't the aria throttle itself anyways? I remember reading that it runs at ~480mhz when idle.
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
yeah but he was trying to run it lower than 480.... which can still be done. just need a kernel.

Watchdog detects Base System @ 60% frequently?!

Heyo bros so I'm experiencing what I'm afraid might be a problem:
I've been getting watchdog alerts regarding the "Base System" process. It notifies me that the CPU % at the time of the captures range from 40% to 60+%. Coincidence or not, it usually happens when I wake my phone from sleep- not when I unlock it, just when I press the power button. The moment the lock screen pops up, the phone's already vibrating and the watchdog notification is up in the status bar.
Battery life so far is:
9h 22m @ 74%; Phone Idle- 56% | Cell Standby- 22% | Display 17% (40m) | Android OS 3% | Voice calls- 3%
Who knows, maybe this^ looks normal. I just want to be sure.
I've heard talk of 'wakelocks' but I don't know exactly what they are, what might cause them, and how I can track them.
I'm currently running:
Atrix 4G (not 2, just for clarification)
CM7 xB^xN
Baseband reads: N_01.77.30P
Kernel version reads: 2.6.32.39-MB860-GB-Faux123-v0.2.1 [email protected] #14
Build number: GWK74
Totally honest, I don't know if that might be able to help diagnose the problem, but for what it's worth, I want to check two things:
1) I flashed Faux's enhanced stock CM7 kernel, and am pretty sure it took, but does that look to be the proper kernel version? I just want to be sure.
2) While I also flashed the "latest radio" in the CM7 xB^xN thread, I was certain there was an xx.97 radio (vs the x.77 radio that mine appears to currently have). Am I indeed on the latest radio version?
Would it hurt to reflash these two? Could either one, or maybe both, be the cause of this?
It also occurs to me: I've been using SetCPU and have ONE profile set up that forces my CPU to min/max 216/216 when the screen is off. Could that be causing it?
Thanks so much for any and all insight bros. Also, please let me know if there's any more info you might want to help diagnose what the dealio is.

Heyo guys,
I hate to bump this kinda soon, but this is definitely a problem.
It's getting to be that I don't even have to wake the phone up for the Base System to spike. I was woken up a couple times in the middle of the night by notifications saying it was really high.
You guys have any thoughts? I'd really like to get this resolved as CM7 is AWESOME.
Yes, you guessed it- I'm not anal about the fingerprint scanner or webtop. Just a stable and fully functional release.
Thanks for any help bros I really appreciate it.

Hi, new member here.
I get the same weird spike to 50-60% (and was woken up too in the middle of the night by watchdog). I have narrowed this occurrence to when I have both Watchdog & Juice Defender enabled at the same time. (Yeah it took me a while to figure out)
When I disable Juice defender the problem seems to go away. So I'm thinking one of the power saving settings turns the radio off & a core system process really does not like that.
This is on a non-rooted Atrix, I have not tested on a rooted Atrix.
So far I had to turn off the watchdog alarm so I can sleep. If anyone can think of a solution it would be appreciated!

AX-MA said:
Hi, new member here.
I get the same weird spike to 50-60% (and was woken up too in the middle of the night by watchdog). I have narrowed this occurrence to when I have both Watchdog & Juice Defender enabled at the same time. (Yeah it took me a while to figure out)
When I disable Juice defender the problem seems to go away. So I'm thinking one of the power saving settings turns the radio off & a core system process really does not like that.
This is on a non-rooted Atrix, I have not tested on a rooted Atrix.
So far I had to turn off the watchdog alarm so I can sleep. If anyone can think of a solution it would be appreciated!
Click to expand...
Click to collapse
Thanks for the insight bro. For what it's worth, I'm not running Juice defender, or any other kind of battery saver app.
Looks like a couple of us are having problems then, though. We'd both really appreciate any info, advice, or help.

Ok, it seems it was just a coincidence with Juice Defender then.
The problem may be unrelated to power savings, but it is indeed a problem.

xyrovice said:
For what it's worth, I'm not running Juice defender, or any other kind of battery saver app.
Click to expand...
Click to collapse
AX-MA said:
Ok, it seems it was just a coincidence with Juice Defender then.
The problem may be unrelated to power savings, but it is indeed a problem.
Click to expand...
Click to collapse
It doesn't have to be unrelated to power saving just because xyrovice is not running Juice Defender, there is a option for power saving in the battery settings for the Atrix that does a similar function.. Before ruling out power savings as unrelated I would make sure xyrovice is set to "performance mode".

WiredPirate said:
It doesn't have to be unrelated to power saving just because xyrovice is not running Juice Defender, there is a option for power saving in the battery settings for the Atrix that does a similar function.. Before ruling out power savings as unrelated I would make sure xyrovice is set to "performance mode".
Click to expand...
Click to collapse
I'm running CM7 and skimmed through the settings menu and didn't find anything about 0ower features. I know that in Blue ROMs there's the battery manager section, but I don't think CM7 has this. Anything else I should look at, though?
Thanks for the insight too bro.

xyrovice said:
I'm running CM7 and skimmed through the settings menu and didn't find anything about 0ower features. I know that in Blue ROMs there's the battery manager section, but I don't think CM7 has this. Anything else I should look at, though?
Thanks for the insight too bro.
Click to expand...
Click to collapse
oIc, no I dont guess you will have those settings in CM, I should have thought of that. I wish I could help because I had the exact same prob with Watchdog constantly alerting for "Android Core Processes" and "Android Media processes", but I dont get those alerts anymore. I haven't changed ROMs or anything.. The only thing I can think of is I changed the MinFree values, I used the app "AutoKiller Memory Optimizer" to change them.

WiredPirate said:
oIc, no I dont guess you will have those settings in CM, I should have thought of that. I wish I could help because I had the exact same prob with Watchdog constantly alerting for "Android Core Processes" and "Android Media processes", but I dont get those alerts anymore. I haven't changed ROMs or anything.. The only thing I can think of is I changed the MinFree values, I used the app "AutoKiller Memory Optimizer" to change them.
Click to expand...
Click to collapse
Do you know why that seemed to solve the problem...or if it even WAS the problem, per se?
Also, is there any reason CM7 would have the minfree set to a default that causes this?
Lastly, what did you alter the minfree values to? You think ROM toolbox might have this capability?
Thanks so much for saying this bro. Who knows, this might be the problem.
PS: I just tried this and am going to see if it works. Post #13 is the one that would really sum up my reaction of successful.
Hopefully maybe this helps my other bros.

xyrovice said:
1Do you know why that seemed to solve the problem...or if it even WAS the problem, per se?
2Also, is there any reason CM7 would have the minfree set to a default that causes this?
3Lastly, what did you alter the minfree values to? You think ROM toolbox might have this capability?
Click to expand...
Click to collapse
1.) no I can't say for sure what the problem was or why I no longer get the Watchdog alerts. I was just trying to think what I have changed since they stopped because I haven't changed ROMs.. Since changing the MinFree has to do with how many or what apps are left running I'm just kinda throwing it out there as a possibility since your at a loss for things to try.
2.) no I can't think of any reason, and most with CM don't have this prob right..?
3.) It's posible it does have the capability because it does allot but I am not sure.
Foreground 12
Visible 18
Secondary 36
Hidden 121
Content 129
Empty 137

possible solutionary steps I've taken:
So Update:
I actually ended up checking out my (partial) Wakelocks with betterbatterystats, and I think I may have found a problem (diagnosed with alarmdump.txt from the Alarm Manager):
1) When I first flashed CM7 I thought, "Oh well why not really get comprehensive about keeping apps up to date" and I actually, for every single app, checked the "Automatically update" box in each one's market page. This led to a CATACLYSMIC wakelock that I'm now pretty sure could be the problem.
2)Google talk also seemed to be a little active with the screen off so I unticked the "sign me in auto..." box and made sure I signed out.
Lastly (not related to wakelocks), I checked on my TTS settings (see my last post about that).
Oh also LASTLY lastly I froze the modem fastdormancy manager in TiBU (kinda just for ****s and giggles). That said though, is the consensus on this that it's pretty harmless?
So, other bro who was having a problem, check and see if this might help you at all AYY
WiredPirate said:
1.) no I can't say for sure what the problem was or why I no longer get the Watchdog alerts. I was just trying to think what I have changed since they stopped because I haven't changed ROMs.. Since changing the MinFree has to do with how many or what apps are left running I'm just kinda throwing it out there as a possibility since your at a loss for things to try.
2.) no I can't think of any reason, and most with CM don't have this prob right..?
3.) It's posible it does have the capability because it does allot but I am not sure.
Foreground 12
Visible 18
Secondary 36
Hidden 121
Content 129
Empty 137
Click to expand...
Click to collapse
Thanks for posting this. I checked ROM toolbox and it does indeed have the capability. That said, if my aforementioned possible solutions don't work, I'm turning here. Thanks for the info bro.

Watchdog is flagging the "base process" app because IT IS using over 60% of your CPU BUT it is using 60% of your CPU that is running at 216MHZ.
It's your screen off setcpu profile of 216/216, if you bump up the max to 456 the alert will go away. When you have it set as 216/216 Watchdog (I believe) thinks that is the actual max cpu speed and bases its percentages off of that. I got that warning before and after a bit of troubleshooting (actually tried several different things) found that was the problem.
I am not sure but if you "whitelist" a app in watchdog it might ignore it as well. However my alert level was set at 80% and it would still set it off, so I think the higher speed might just be better.