My phone is locking up when im playing music, when it happens the music begins to lag and the phone becomes unresponsive aside from the sleep button. I am running Aosp/cm7 3/10/11 build I know this is a beta rom but im wondering if anybody knows what this is, i thought it was the processor dropping too low but i changed minimum to 248 from 176 to no avail, it happens about once a day, what is this?
What governor are you running? Try ONDEMAND if you aren't already running it.
-----
Sent from my CDMA Hero. I got some hot Gingerbread-on-Hero action here!
That should fix it, but if not, 352 will do.
It was on Interactive, since i changed it ive had no problems, thanks a lot.
Related
I'm thinking about overclocking my Wizard beyond the stupid 195 mhz. How 'bout we all put down our clocks so we can have some suggestions on how to overload our Wizards to the max!
Good idea, go ahead and give it a start yourself;]
I've always heard/read that it's unsafe to overclok wizard beyond "the stupid" 240MHz, but i don't quite believe it. Feel free to try and inform me, what say you? ;]
I'm bringing it to 210 right now. Can't say I notice a difference, eh?
As was said by many people on this forum, you won't notice big difference below 240. most programs operate with similar performance, and battery life doesn't change much neither. Only skype is said to run better - personally i didn't feel anything while doing this, so i don't overclock myself after checking it out.
i use to run at 260 with no problems ever. but i decided to go to 240. since there wansnt a big change in preformance from 240~260.
240 is good for the wizzard. I play doom,quake,wolf3d,and skype with no problems.
Skype does make my device hot after 30min of use.
Agreed
Running mine at 240 according to Omapclock. No problems and alot faster.
Yep, been running it at 260 also. I did notice a change in performance with with my bluetooth headphones. Less music dropping out and Arvale I and II seem to catch up with the headphones on.
But yeah, 240 might be my next standard. But battery life wont change? Are we sure?
been running at 260 for a long time now. No problems.
I used to run 240 (24-7), but the phone would "reboot" when on phone calls sometimes. I moved it down to 228 and zero reboots, thus far.
A friend gave me his MDA today as he never used it. I will be doing some testing on that thing this week.
MDA Over Clocked
I have mine set to 252 for over a year without any problems.
--Rod
Im running 312 using the latest OMAP for Trion....it doesnt crash...it works great...I wonder if its actuaally 312 or just say sake..
shivam said:
Im running 312 using the latest OMAP for Trion....it doesnt crash...it works great...I wonder if its actuaally 312 or just say sake..
Click to expand...
Click to collapse
You are very brave. Search for the other threads on this topic. I run my at max 260 and use the scale function to "float" down to 143. Works very well.
--M
I've been actually floating myself from 260 and 195. I set it to 260 when I'm impatient waiting for thumbnails in pictures to load up or when I'm playing a heavy graphics game. I only get crashes when I switch from 195 to 260, but that's only when it hasn't been switched for a while.
312 is brave...
I've been at 260 for months, since 273 causes my system to hang / crash. I'd love to go faster...
I only overclock for watching videos or running my GPS software. . . and -- even then -- I limit to 240. Works like a charm and my GPS keeps up with my lead foot.
Limits
Hi,
I'm running 260, but haven't been long enough to see any damage, but the phone is much faster.
How much can these things take?
All my pc's are madly overclocked, but a busted cpu / mainboard are cheaper than a phone.
I've been running at 260 on various ROM's for over a year now. Haven't had any issues with rebooting and it does make a very noticiable difference compared to the standard 195Mhz. I have noticed recently that my battery is starting die big time so I am wondering if the overclocking has taken it's toll.
I run mine at 240 (as per the omap settings) 24-7.
I have just moved to the XM6r2a Lite Version from the standard o2 WM5 release ROM and have had no problems. I found that when I clocked at 260 it would occasionally hang. No problems at 240 though.
My device is the fastest I have ever known it running XM6r2a Lite clocked at 240.
...
I tried running at 312 just for the hell of it and found there to be no problems...
at least at first glance. After browsing the net for about 30 min, the screen started to frizz out on me and i couldn't click anything and I noticed my mda was getting quite warm (112 i think, hehe)...
Long story short, It worked well in short bursts..but for the long haul, 312 would have fried my cpu
im running 247 at the moment and i notice a difference
Well...tonight I was playing with my phone and decided to mess with Battery Status. I was checking out the temperature depending on the speed I over clocked it. I went to 247 and 260 and everything was running pretty smooth. I with to 273 and the screen flipped out. This had happened to me before with a previous rom at 260 so I wasn’t freaked out. I soft reset and I got some weird blue screen saying my phone had some sort of power failure. It asked me not to remove the battery and hit yes or no. I really don’t remember what it said. I hit yes and prayed and my phone came back up. What was crazy was that it had hard reset my wing all on its own. The setup screen came up and I was like wtf. This was pretty scary as I thought I had fried it. I’m just glad I didn’t f something up. Has this happened to anyone else?
Odd. Im running 273 constantly right now. All is good.
All I know is that it scared ish out of me. lol I wont be messing with Battery Status for a little bit. I've overclocked before but never had that problem.
off the wall CPU behavior
I received a replacement phone yesterday a brand new one not a refurbished I flashed it and as I do with all roms I over clocked it with BS I usually use 260 Mhz with 273 Mhz boost and cpu scaler, well as soon as I did that with this phone the screen started flickering, the more I used it the worse it got until the screen was no longer readable I soft reset and it flickers when it's booting up too, I managed to get back into BS options and lowered the speed to 247 Mhz and no boost, still same problem, I decided I wanna fry this thing now so I took it to 312Mhz to my shock it actually was more stable so I figured let's go all the way something I have not attempted before I went to 325 Mhz with 338 Boost and the phone was much more stable thenat 247 or 260 the screen flickers just a bit here and there and as soon as I touch the screen it stops and fonctions the way it should, the speed is sooooooo f^*&^ awesome it's hard to go back to 260Mhz. Anyway I tried this with 2 different rom to make sure the rom was not and issue. I know processors in same type of phones can behave differently, but did this happen to anyone, I am gonna test it for a few days and see what happens cause if i keep having problems and can't over clock the way i want I am sending it back for a replacement (after I have processor goo oozing out the sides of the phone..lol).
Each phone is different. My friend's Wing maxes out at 243 but my bro's maxes out at 273.
Wing OC'd @ 286MHZ most stable
FZZF said:
I received a replacement phone yesterday a brand new one not a refurbished I flashed it and as I do with all roms I over clocked it with BS I usually use 260 Mhz with 273 Mhz boost and cpu scaler, well as soon as I did that with this phone the screen started flickering, the more I used it the worse it got until the screen was no longer readable I soft reset and it flickers when it's booting up too, I managed to get back into BS options and lowered the speed to 247 Mhz and no boost, still same problem, I decided I wanna fry this thing now so I took it to 312Mhz to my shock it actually was more stable so I figured let's go all the way something I have not attempted before I went to 325 Mhz with 338 Boost and the phone was much more stable thenat 247 or 260 the screen flickers just a bit here and there and as soon as I touch the screen it stops and fonctions the way it should, the speed is sooooooo f^*&^ awesome it's hard to go back to 260Mhz. Anyway I tried this with 2 different rom to make sure the rom was not and issue. I know processors in same type of phones can behave differently, but did this happen to anyone, I am gonna test it for a few days and see what happens cause if i keep having problems and can't over clock the way i want I am sending it back for a replacement (after I have processor goo oozing out the sides of the phone..lol).
Click to expand...
Click to collapse
I run my wing at 286MHZ, and enjoy good stability. Really can't remember the last time I experienced a freeze. I experienced the same screen malfunction at 273MHZ, but didn't suffer an arbitrary hard reset. 299MHZ was very unstable for the Wing, and I'm unwilling to experiment with higher speeds.
hehe. I was messing with Battery Status tonight and unwisely selected the start over clock on reset, so now I am stuck at 273mhz and my screen is flipping out. I can't reset it from the on-screen obviously, so is there a way to restart it in some kind of safe mode and adjust the program??
Oh thank goodness, I just searched what soft reset is, LOL sorry. Stylus saved my phone.
Yikes! Just I'm using Open Touch 3.0 and just tried to overclock to 273. Screen started FREAKING out. Couldn't use the screen at all. Had to hard reset manually by holding the left and right soft keys and pressing the soft reset button. Thank god I did a backup before I messed with it.
I figured I'd give it another shot. Im using CPU scaler with a low of 156 and max of 247 and it seems to be running good. I like the fact that it only uses what it needs. I may bump the max to 260 but don't see the need right now.
FZZF said:
I received a replacement phone yesterday a brand new one not a refurbished I flashed it and as I do with all roms I over clocked it with BS I usually use 260 Mhz with 273 Mhz boost and cpu scaler, well as soon as I did that with this phone the screen started flickering, the more I used it the worse it got until the screen was no longer readable I soft reset and it flickers when it's booting up too, I managed to get back into BS options and lowered the speed to 247 Mhz and no boost, still same problem, I decided I wanna fry this thing now so I took it to 312Mhz to my shock it actually was more stable so I figured let's go all the way something I have not attempted before I went to 325 Mhz with 338 Boost and the phone was much more stable thenat 247 or 260 the screen flickers just a bit here and there and as soon as I touch the screen it stops and fonctions the way it should, the speed is sooooooo f^*&^ awesome it's hard to go back to 260Mhz. Anyway I tried this with 2 different rom to make sure the rom was not and issue. I know processors in same type of phones can behave differently, but did this happen to anyone, I am gonna test it for a few days and see what happens cause if i keep having problems and can't over clock the way i want I am sending it back for a replacement (after I have processor goo oozing out the sides of the phone..lol).
Click to expand...
Click to collapse
I am responding to myself here ..lol so after some testing and trial and error it turns out that cpu scaler cause the screen to flicker or go blank at all speeds, with cpu scaler off the phone runs very stable all the way to 325 Mhz so I have it set at 286 no problems at all and battery life is pretty good.
FZZF said:
I am responding to myself here ..lol so after some testing and trial and error it turns out that cpu scaler cause the screen to flicker or go blank at all speeds, with cpu scaler off the phone runs very stable all the way to 325 Mhz so I have it set at 286 no problems at all and battery life is pretty good.
Click to expand...
Click to collapse
Thats crazy...every phone is completely different. Mine is running great with CPU scaler.
Okay im pretty much going through the same thing. I went up to 263 from 247 and now my screen is all screwed up but the phone is still working. Just the screen is gone. What can I do to lower it back down to 247.
I've been experimenting with several new ROMs and have found in every case that when I install SetCPU (either choosing automatic/HTC Hero profiles) it causes dramatic slowdown on my device to the point where I just can't bear to use it. On some screens it takes 5-10 seconds to load and when I am typing a message it is often an entire WORD behind my pace and constantly trying to catch up - for the record I am no champion speed texter!
With SetCPU uninstalled my device goes back to normal.
I purchased SetCPU last year and have always enjoyed it, but it seems with the new 2.1 ROMs, it causes more bad than good. I was in the sprint store the other day looking at the EVO and I happened to use one of their stock Hero's and the difference in speed between that and mine was STAGGERING.
So is it SetCPU by itself or both it and 2.1 ROMs?
Are you using it on an oc'd rom? id not reccomend using a oc tool, manually throttle ot to where you want
this doesnt belong in dev
From what I understand is that you don't even have to use an OC tools such as OC Widget and SetCPU with Toast's kernel. I may have read this wrong so I'd ask someone else. It is built with the On Demand throttling, I believe. Therefore, if you use a 710Mhz one it will scale from it's lowest freq to it's highest when needed. But again I am not sure. Ask someone else.
Yeah Ive been using the 710 dam ker and I was fine for a week then all of a sudden lock ups and crashes when answering the phone etc I wiped and started over and its good I do want to clock it a bit though so any good recomendations would be great
I tried out the quickie kernels for the NC the other day and my typing became very laggy on both the 900 and 950 Kernels also with a general performance drop. i restored my nook to its default kernel and am still experiencing the lag... any advice?
Type slower?
Magically transmitted across the interwebs by my kickass NookColor!
Sorry, I have to bump this. I'm having this problem, too. I almost have to "long press" the keys to get them to register. This applies to any part of the UI. I have to long press to get it to respond, and REALLY long press to get it to do a normal long press.
My touch screen had a few minor sensitivity issues prior to the Screamer patch, but now it's honestly frustrating to use. I tried to recalibrate my screen using the guide found at NookDevs, but it did NOT solve the issue. Any ideas?
Wait, I think I fixed it...
Do you have SetCPU running? I just noticed that when the kernel changes set CPU resets to 300max/300min. I fixed mt setCPU settings and the lag is completely gone now.
Okay, somehow that only solved it for a few minutes. It's now just as laggy as before and all settings are correct in setCPU. Anyone else have any ideas?
It always restarts automatically, when i make a call, the call just freezes and when i turn the phone on from standby to see what happen, well you guessed it, it restarts! its pretty annoying i went through 2 batteries today in 8 hours, because of the restarts. please help!
If your using the stock kernel I think its overclocked to 768 not sure though. Try one of dec's 691 kernel the #589 is my recommendation. Hope it helps good luck.
Root-Hack-Mod-Always™
jlopez512 said:
It always restarts automatically, when i make a call, the call just freezes and when i turn the phone on from standby to see what happen, well you guessed it, it restarts! its pretty annoying i went through 2 batteries today in 8 hours, because of the restarts. please help!
Click to expand...
Click to collapse
There could be a lot of things happening. The most common is that your running a clock speed higher than that which your phone can handle. Not all heros are created equal, mine for instance starts rebooting at anything higher than 691. Try a different kernel or if using setcpu or over clocking widget to lower your upper end clock speed. Your phone freezing when coming out of standby can mean your lower clock speed is too low. ASOPGB has JIT enabled by default as well. Go into the settings and turn it off, then reboot. You will just have to play until you find out what works for you. Good luck!
runngwlf said:
There could be a lot of things happening. The most common is that your running a clock speed higher than that which your phone can handle. Not all heros are created equal, mine for instance starts rebooting at anything higher than 691. Try a different kernel or if using setcpu or over clocking widget to lower your upper end clock speed. Your phone freezing when coming out of standby can mean your lower clock speed is too low. ASOPGB has JIT enabled by default as well. Go into the settings and turn it off, then reboot. You will just have to play until you find out what works for you. Good luck!
Click to expand...
Click to collapse
Set cpu or similar will not fix the issue, laie was right a capped 691 kernel is needed and probably a capped recovery as well. Btw jit is no longer default in gb, and jit would not cause reboots anyway.
sent from my hero, which no longer sucks ass
il Duce said:
Set cpu or similar will not fix the issue, laie was right a capped 691 kernel is needed and probably a capped recovery as well. Btw jit is no longer default in gb, and jit would not cause reboots anyway.
sent from my hero, which no longer sucks ass
Click to expand...
Click to collapse
Ahh thanks for the info, I had not gotten through all the new posts on the other ASOP GB threads. Good to know though. I have no tried out the rom, I plan to this weekend and my phone does NOT like kernels that clock above 691.