Related
The problem is, no matter what program I use, if I set the Tab to downclock at 100/200 or even 100/400 when the screen is off, the phone will freeze in sleep and force me to reset the tablet pressing the power buttornfor 7 seconds.
Anybody else have this issue?
Sent from my Milestone
do you use SerCPU?
I set is 100/400, it sometimes work but my phone was getting random reboot.
So I disabled it...
Sent from my GT-P1000 using XDA App
same issue with me , if I set the cpu to 100 to 300 it would hang or crash coming out of sleep mode . I ended up removing setcpu and going back to stock . i expect the Cooked roms will resolve this later on .
Probably kernel related. If i select the Set On Boot option, after a reboot both min/max freqs will change to a min of 19 and max of 500. Probably best to leave it until we have devs working on it.
Sent from my GT-P1000
there's really no need to underclock when the screens off, you know that right?
infamousjax said:
there's really no need to underclock when the screens off, you know that right?
Click to expand...
Click to collapse
Get an app to graph the cpu use, and you will see the cpu spike when sleeping.
So, in short, yes: downclocking with the screen off really help the battery life
Sent from my Milestone
It doesn't make much difference as the cpu scaling does a more than adequate job, but whatever wets your whistle
Is there any particular reason the second core always drops down to 216mhz? This happens with any custom kernel I run, currently running moray with electra kernel at 1.5Ghz using pimp my cpy to OC.
ggrammer said:
Is there any particular reason the second core always drops down to 216mhz? This happens with any custom kernel I run, currently running moray with electra kernel at 1.5Ghz using pimp my cpy to OC.
Click to expand...
Click to collapse
when it's needed, it goes to the required frequency...
sounds reasonable but I will notice some lag and stuttering while I am using the xoom, i will open os monitor and the second core is sitting at 216, i move it manually to 1.5Ghz and the tablet is more responsive...
Edit
Sorry I should have been more specific about the situation. When I say the 2nd core drops to 216 I mean the max frequency drops to 216 so the 2nd core does not clock up any higher unless I manually intervene.
same on my xoom with tiamat 2.2.2 and setcpu. i have two profles , screen off with 216-456mhz and other with 216-1200mhz. only the first score is over clocked after switched on, the second stucks at 216-456mhz. i contacted the developer of setcpu someting around 2 weeks a go, but no solution till now.
okay i see wat u mean...i just checked and i'm getting the same results... it sits on the min freq, all laggy, then when i manually set the frequency, it's super responsive like it shud.... i'm over-clocking to 1.6 btw
burgi400 said:
same on my xoom with tiamat 2.2.2 and setcpu. i have two profles , screen off with 216-456mhz and other with 216-1200mhz. only the first score is over clocked after switched on, the second stucks at 216-456mhz. i contacted the developer of setcpu someting around 2 weeks a go, but no solution till now.
Click to expand...
Click to collapse
I don't think that it strictly a SetCPU problem. I also have an Advent Vega and have used SetCPU to overclock it. Had almost the same problem, except both cores were stuck at 216Mhz.
Tried multiple overclocking apps and have had the same problem with all of them. Device fine until it goes into sleep mode, CPU stuck at 216Mhz when brought out of sleep. Even setting the minimum setting to 456Mhz still resulted in the CPU being stuck at 216Mhz on wakeup.
so i guess the big question is whether it is the kernels (I've tried a few) or in the way these apps OC a dualcore processor...It makes me wonder about the OC apps though, they were all built for single core originally and in each of them you only set 1 max and 1 min speed. OS monitor is the only app that displays both cores, at least that I have used, but it doesn't set an OC value at boot. Maybe if one of the smart devs on here could comment maybe even just to shed some light on this
Is there no solution to this issue yet?
Is it a tegra fault/problem?
Is it a Kernel issue?
Would flashing back to a stock kernel fix it? (if that is even possible...)
Of all the issues that plague the tbolt the one that bothers me most is screen freeze (screen becomes totally unresponsive to touch while using the tbolt).
I'm currently using bamf cubed 1.0.9 but I've had the problem in every rom I tried including stock. I do find it is happening more frequently now though. Used to get maybe one freeze a week. Now about 2 per day.
I tried bamf's latest kernel but that didn't help.
Currently I'm back in stock kernel and I'm trying the performance.governor.
I find hit or miss approach I'm using stupid and unacceptable. Can someone suggest a more logical approach to my problem? I'm especially interested if you had the SAME problem and found a way to fix it.
Thanks!
recDNA said:
Of all the issues that plague the tbolt the one that bothers me most is screen freeze (screen becomes totally unresponsive to touch while using the tbolt).
I'm currently using bamf cubed 1.0.9 but I've had the problem in every rom I tried including stock. I do find it is happening more frequently now though. Used to get maybe one freeze a week. Now about 2 per day.
I tried bamf's latest kernel but that didn't help.
Currently I'm back in stock kernel and I'm trying the performance.governor.
I find hit or miss approach I'm using stupid and unacceptable. Can someone suggest a more logical approach to my problem? I'm especially interested if you had the SAME problem and found a way to fix it.
Thanks!
Click to expand...
Click to collapse
It looks like that most people that end up with this problem (sleep of death, blank screen of death, or whatever you want it to be called) were either underclocking to low or undervolting to low, some governors have also been the culprit on some devices. Not all of our thunderbolts are the same, guess solder joints are weaker or something that makes this such a random problem. Your best solution is to try different kernels, cpu settings, and governors to find out what your phone likes. I personally haven't had this issue with eternity. However, some others have! Good Luck
Yes, what the above poster said. Like for my phone it does not like smartass gov. It will work but the screen will freeze as you have experienced also. Also overclocking, i can overclock to 1.7ghz but will also freeze randomly as you experienced.
Sent from my HTC ThunderBolt using xda premium
I think (but could be mistaken) this is more like the opposite of black screen of death. I believe that is when the phone wont wake from sleep.
My problem occurs only when phone is awake and being used heavily. The screen isn't black nor blank - I see whatever screen I am on when it happens: lock screen, an app, home screen, keyboard, etc. I see all the icons but screen becomes totally unresponsive to touch. Wide awake.screen but no matter how you tap, slide, or use capacitive buttons nothing works.
Only way out is to pull battery or hold down up volume, down volume, and power key simultaneously to force a restart.
There is someone out there who understands this phenomenon better than I and can suggest approaches but I must be clear - this is.not a black or blank screen and doesn't occur when clock speed is low.
I would.guess cpu is operating at full 1 ghz when screen freezes occur in my tbolt. I am not overclocking at the moment but I do believe overclocking makes it worse but not sure.
Mine was doing that at being underclocked too low keep it at say, 368 mine never did it again, also don't undervolt too much it can cause phone to power down. I use ondemand and keep you lowest speed to 368 and you should be fine. Using battery saver mode for kernel in speedtweak may be undervolting your phone to much if you are using that.
Try this kernel working great for me. http://db.tt/QqkRvtjm jdk newest kernel.
Sent from my ADR6400L using XDA App
I was in smartass governor with low at 368 and high of 1.4when all this occured. I then dropped the highto 1.2 then finally back to 1. Now im back in Stock kernel. I don't see what difference the minimum makes in my case.
I guaranty you my phone is at 1 ghz when it freezes it only happens when I'm using the tbolt - never when sleeping. Anyway I did have it set to min. Of 368 all along. It was the first advice I got when I first tried 1.0.7 and I've stuck with it.
I had screen freezes in stock kernel ondemand governor 368/1ghz which is why I tried overclocking in bamf 3++ kernel smartass governor. It was even worse (more frequent) in smartass so went back to stock kernel ondemand 368/1ghz.
Tonight I'm in stock kernel performance governor (1ghz all the time). There's gotta be a better way than random trial and error.
Imagine if dell told you to try windows xp or windows me if your computer doesn't "like" windows 7?
recDNA said:
I was in smartass governor with low at 368 and high of 1.4when all this occured. I then dropped the highto 1.2 then finally back to 1. Now im back in Stock kernel. I don't see what difference the minimum makes in my case.
I guaranty you my phone is at 1 ghz when it freezes it only happens when I'm using the tbolt - never when sleeping. Anyway I did have it set to min. Of 368 all along. It was the first advice I got when I first tried 1.0.7 and I've stuck with it.
I had screen freezes in stock kernel ondemand governor 368/1ghz which is why I tried overclocking in bamf 3++ kernel smartass governor. It was even worse (more frequent) in smartass so went back to stock kernel ondemand 368/1ghz.
Tonight I'm in stock kernel performance governor (1ghz all the time). There's gotta be a better way than random trial and error.
Imagine if dell told you to try windows xp or windows me if your computer doesn't "like" windows 7?
Click to expand...
Click to collapse
That might be the case if we all used the exact same set up. We don't some change fonts, some use different apps, and there are so many variables.
Nothing unusual going on in my tbolt. 1.0.9 cubed with no unusual apps or settings. I seldom add.an app to my bolt unless it has 1000's of downloads in the market with high ratings. I learned that back before I rooted. I bet someone who writes.kernels understands this phenomenon and could point me in the right direction. Imagine if your computer was bonked up and advice was to randomly try changing settings?
recDNA said:
I was in smartass governor with low at 368 and high of 1.4when all this occured. I then dropped the highto 1.2 then finally back to 1. Now im back in Stock kernel. I don't see what difference the minimum makes in my case.
I guaranty you my phone is at 1 ghz when it freezes it only happens when I'm using the tbolt - never when sleeping. Anyway I did have it set to min. Of 368 all along. It was the first advice I got when I first tried 1.0.7 and I've stuck with it.
I had screen freezes in stock kernel ondemand governor 368/1ghz which is why I tried overclocking in bamf 3++ kernel smartass governor. It was even worse (more frequent) in smartass so went back to stock kernel ondemand 368/1ghz.
Tonight I'm in stock kernel performance governor (1ghz all the time). There's gotta be a better way than random trial and error.
Imagine if dell told you to try windows xp or windows me if your computer doesn't "like" windows 7?
Click to expand...
Click to collapse
That sounds more like your phone doesn't like whatever voltage is set for your top end frequencies. Might want to try IncrediControl from the market and increase the vdd levels a little. I think a lot of the kernels floating around are under volted a little. Could be the cause.
Sent from my ADR6400L using Tapatalk
Its worth a try. I never tried that. Thanks.
You say it only happens when using your bolt, maybe the processor is just maxed out. How long do you wait to see if it comes back around?
I have waited as long as 10 minutes but usually ibjust restart within 30 seconds based on experience. Once "frozen" it has never recovered on its own.
What's interesting is the processor is still working whilebthe screen becomes unresponsive. I know this because I was streaming a r radio into a jawbone earpiece and when I switched apps the screen froze yet the radio continued to play. I HAD to restart to stop the music since the screen wouldn't respond to touch.
I flashed Imo's lean Sense Kernel and haven't had a freeze yet. I hope this has solved the problem. There is a little lag now when I hit a widget or app shortcut but no more freeze.
Your lag is prob due to being in safe made, put in normal mode in speed tweak to rid yourself of lag.
Sent from my ADR6400L using XDA App
No, I'm in standard mode. I chose #1 in speedtweak. I varified at 1.4 ghz max/ 254 min
I couldn't figure out how to raise min value in speedtweak so I reinstalled set cpu and set min to 368. Seems to reduce the lag.
Still a slight lag but most importantly no screen freeze since installation.
This might be unrelated, but I've run into a situation where the touch screen is entirely unresponsive. I was running CM7.1.1 and the phone randomly restarted while sitting on the desk, after that it now claims to have no service and won't unlock because it won't respond to touch. Any ideas?
mkitchen said:
This might be unrelated, but I've run into a situation where the touch screen is entirely unresponsive. I was running CM7.1.1 and the phone randomly restarted while sitting on the desk, after that it now claims to have no service and won't unlock because it won't respond to touch. Any ideas?
Click to expand...
Click to collapse
Have you tried flashing a stock ruu in fastboot? You may try to go back to completely stock and then go from there. You could try a different rom too and wipe the system partition as well as the usual stuff first.
Sent from my ADR6400L using Tapatalk
I went back to the stock ROM using clockwork mod recovery, and the problem persists. I am wiping system partition now, but I did some of the stuff that has worked for me in the past such as dalvik, user data, and cache.
Wiping system may help but if that doesn't I'm not sure what else for you to try except fastboot flashing an ruu.
Sent from my ADR6400L using Tapatalk
Actually wiping system worked, I may have not done it in the correct order the first time I tried to flash back to stock. I really appreciate the help.
Yup its ya boy AGAIN with an issue lol. So I flashed the mikshifted Gv2.1 yesterday and everything seemed fine except this a.m I noticed my phone randomly rebooted it self and it's not a normal reboot that takes like 30seconds it starts to go through the boot animation and about 10seconds later my phone is booted back up only thing weird is my 4g stays stuck on turning on so I manually restart my phone and then it works fine im using setcpu its on the smartass setting 245mhz min 1420mhz max if that info is needed. So I guess my question is what the heck is the problem here?
Try backing down your SetCPU Max setting down. Maybe to like 1.2gHz (1200mHz) and switching to the interactive Governor. Not all devices can be OC'd past 1.2gHz . Also the Smartass Governor doesn't agree with all devices. After you reset the settings Reboot.
prboy1969 said:
Try backing down your SetCPU Max setting down. Maybe to like 1.2gHz (1200mHz) and switching to the interactive Governor. Not all devices can be OC'd past 1.2gHz . Also the Smartass Governor doesn't agree with all devices. After you reset the settings Reboot.
Click to expand...
Click to collapse
Yeah I believe the max "safe" speed is 1.5ghz. This is the max toastcfh's kernel will OC to. Other than that, make sure the min max aren't too far apart because sometimes the governor for the kernel will crash the phone if they are.
And to add on. What happened to device was a hot restart. I don't know exactly what triggered it, but i don't believe it was the clock speed. If you notice you can manually do a hot restart from the restart menu. The hot restart basically means it is just restarting all the software and keeps all the hardware on. Unfortunately triggering a hot restart breaks wimax on all devices until you manually do a full restart. As to what triggered your restart I have no clue with the info provided.
Hope this helped
Sent from my PG86100 using xda premium
Hello. I am having an issue. My mother was talking to me today, and she was complaining about how her phone was so hot. I checked it out, and it was definitely was. So I loaded up CPU Spy, and it is showing that it is running at 1200 MHz for over 10 hours. It is not lowering its frequency at all. I tried rebooting and it is doing the same thing. I am not sure how to handle this. I have never had this happen when I had it (this was my old phone before I upgraded to the Galaxy Nexus). Does anyone know what I should do?
stompysan said:
Hello. I am having an issue. My mother was talking to me today, and she was complaining about how her phone was so hot. I checked it out, and it was definitely was. So I loaded up CPU Spy, and it is showing that it is running at 1200 MHz for over 10 hours. It is not lowering its frequency at all. I tried rebooting and it is doing the same thing. I am not sure how to handle this. I have never had this happen when I had it (this was my old phone before I upgraded to the Galaxy Nexus). Does anyone know what I should do?
Click to expand...
Click to collapse
First off, try to check wich governor are u using. Something such as performance or interactive give the permission to the cpu to rank up faster even if the task is light weight.
Then try to install another kernel but before juast wipe dalvik cache
Cascabreu said:
First off, try to check wich governor are u using. Something such as performance or interactive give the permission to the cpu to rank up faster even if the task is light weight.
Then try to install another kernel but before juast wipe dalvik cache
Click to expand...
Click to collapse
Tried changing governors to everything, including conservative, and it still jumps up. I will try and flash a different kernel and see what happens.
stompysan said:
Tried changing governors to everything, including conservative, and it still jumps up. I will try and flash a different kernel and see what happens.
Click to expand...
Click to collapse
Try matrix or bedalus
I flashed the latest Trinity and it seems to have fixed everything. Thanks for the help!