I am having some screen issues with my doubleshot. Basically my screen would not turn on but I know everything still works. I am able to listen to music, pick up calls, unlock the phone, etc.
It seems to happen randomly. Pressing the middle button or the power button only makes the buttons glow but doesn't turn on the screen.
Pulling out the battery and forcing the phone to restart solves the problem. Is there a solution or a more graceful way of getting the screen to come back on?
Edit:
Forgot to mention that it happens to my on JellyBean DS and KitKat DS by Emmanuel U.
Was using CM 9.1 by scverhagen and the issue doesn't happen as often. Once a week where has the JB and KK happens atleast once a day.
I have the same problem too. For awhile thought it was to an app I moved to sd card (walgreens). Wasn't as often moving app off sd card.
Sent from my MyTouch 4G Slide using Tapatalk
m3gz said:
I am having some screen issues with my doubleshot. Basically my screen would not turn on but I know everything still works. I am able to listen to music, pick up calls, unlock the phone, etc.
It seems to happen randomly. Pressing the middle button or the power button only makes the buttons glow but doesn't turn on the screen.
Pulling out the battery and forcing the phone to restart solves the problem. Is there a solution or a more graceful way of getting the screen to come back on?
Edit:
Forgot to mention that it happens to my on JellyBean DS and KitKat DS by Emmanuel U.
Was using CM 9.1 by scverhagen and the issue doesn't happen as often. Once a week where has the JB and KK happens atleast once a day.
Click to expand...
Click to collapse
I've seen this happen as well with various roms as well (including 9.1). I currently am using tbalden's 10.1, and haven't seen it in forever. I don't know if he fixed it, or I've just been lucky.
I have a feeling that it might be the minimum frequency processor settings. The default settings that Emmanuel set seem pretty aggressive.
I am going to:
increase my minimum frequency to 540MHz (and incrementally lower it until it becomes unstable)
keep my maximum frequency at 1512 MHz
set CPU governor to ONDEMAND
Battery shouldn't be too much of a problem for me since I upgraded to 3500 mAh.
daswerk, have you tried playing around with your processor settings?
m3gz said:
I have a feeling that it might be the minimum frequency processor settings. The default settings that Emmanuel set seem pretty aggressive.
I am going to:
increase my minimum frequency to 540MHz (and incrementally lower it until it becomes unstable)
keep my maximum frequency at 1512 MHz
set CPU governor to ONDEMAND
Battery shouldn't be too much of a problem for me since I upgraded to 3500 mAh.
daswerk, have you tried playing around with your processor settings?
Click to expand...
Click to collapse
540 minimum sounds a bit high to me unless your phone wasn't stable on stock ROM either. Maybe try 192? You could also try lowering your max to the stock 1.2ghz
I keep mine at 1512 too. Low at 192, going to try 384 for a bit. I have not had the problem for awhile though.
Sent from my MyTouch 4G Slide using Tapatalk
Ziida said:
540 minimum sounds a bit high to me unless your phone wasn't stable on stock ROM either. Maybe try 192? You could also try lowering your max to the stock 1.2ghz
Click to expand...
Click to collapse
Thanks for the advice.
I remember having my max frequency at 1512 MHz before so I thought that wasn't a problem.
So far 540 MHz minimum has kept my phone from going blank. I'll try 192 Mhz next
I've tried to set 192 Mhz as a minimum rate - and got black screen anyway.
Saem persun said:
I've tried to set 192 Mhz as a minimum rate - and got black screen anyway.
Click to expand...
Click to collapse
192 MHz worked for me. You can try doing something extreme like what I did to see if it's the minimum frequency. It may decrease battery a bit but it's better than having the annoying black screen. I tried 540MHz as a test frequency.
Not all processors are the equal. So what may work for some may not work for others.
Same problem here. Black screen on Doubleshot with CM 10.1. Made me really concerned when it happened, as I was was reading the hardware maintenance thread earlier today (for fun) so I thought the LCD went.
This is the first time this has happened in the three weeks I had this phone, and I've been on 10.1 for almost a week now.
Because battery life[1] is an issue for me as well, I edged things up only slightly (from 96 MHz to 128), hopefully that will do to the trick. If not, I will try 192 MHz.
[1] Speaking of which, any tricks on keeping battery usage low? I use Deep Sleep Battery Saver which helps out a lot. And I'm selective about my apps (removed Songza because it was hanging around while closed, eating up battery life). GPS stays off, although I keep Wi-Fi and 3G on. It looks like the screen becomes the biggest draw at this point. Any advice would be appreciated.
Since the problem in March, I have upped the minimum frequency to 192mHz. For the longest while I haven't had any issues.
But since I installed my new Anker battery (was on a half-in-the-bag EZO Power 1900mAh), the problem came back, happened twice now, a week apart.
I'm trialing KitKatDS right now, but will probably go back in a week or less due to wakelock (Android OS) issues. Judging by above, when I do I will bump up the minimum even higher. Hard to see the correlation with how the battery will be causing it, but I see no other change.
Upping the lower end frequency seemed to work for a bit but i'm still getting the screen issues. I'm using a 3500mAh battery from China but I'm just doubting that the battery affects the screen.
The correlation of frequency to screen issues could also be coincidental.
m3gz said:
The correlation of frequency to screen issues could also be coincidental.
Click to expand...
Click to collapse
I wonder if the scheduler has anything to do with screen as well, that is, if CM uses a different one from stock?
Sent from my MyTouch 4G Slide using XDA Free mobile app
Related
As the thread states, I obviously have a question about SetCPU and processor settings.
Is it better to have the processor underclocked and almost always using 100% to use programs, or it better off to overclock and have more processing power without using 100% or close to that mark.
And what would be more beneficial for battery life.
Edit: And if mods could move this to Q&A. Clicked the wrong forum.
Thanks,
Cyanide
Cyanidex00 said:
As the thread states, I obviously have a question about SetCPU and processor settings.
Is it better to have the processor underclocked and almost always using 100% to use programs, or it better off to overclock and have more processing power without using 100% or close to that mark.
And what would be more beneficial for battery life.
Edit: And if mods could move this to Q&A. Clicked the wrong forum.
Thanks,
Cyanide
Click to expand...
Click to collapse
Actually we could use some hard evidence regarding this. Theories are theories, but actual experience is golden. Maybe you could try some various processor settings are report back?
Well, before I posted this I was using 245/886 underclocked with 245/245 screen off profile. At the end of the day I had an average about 75-80% percent battery life with pretty moderate to heavy usage.
I'm current using 245/1574 overclocked and will report back, with same screen off profile.
And yes, I did wipe battery stats before I started this.
Cyanidex00 said:
Well, before I posted this I was using 245/886 underclocked with 245/245 screen off profile. At the end of the day I had an average about 75-80% percent battery life with pretty moderate to heavy usage.
I'm current using 245/1574 overclocked and will report back, with same screen off profile.
And yes, I did wipe battery stats before I started this.
Click to expand...
Click to collapse
Cool, thanks for that info. Are you finding that forcing a 245 mhz screen off speed is impacting any apps running while your screen is off (e.g. music playing apps)? A couple of weeks ago I tried forcing the screen off at 122 mhz to see if that would help battery life, but I had big problems with music apps stuttering. I didn't play around with the speeds to see if raising the forced minimum to 245 would have fixed the problem. Some kernels advertise as a feature "Max speed - screen off 576MHz" or some other speed, but I don't know if it needs to be that high or not, for app stability.
I personally haven't tried any music or apps running while screen is off, I'll give it a whirl when I get home from work.
I know this obviously will vary from phone to phone, and how the user uses the phone. I'm pretty moderate to heavy usage daily. Hopefully maybe we can compile some data on what works for people.
I have my screen off profile set at 245 and have no problem streaming music from my SD card with the screen off. When streaming from the cloud, I sometimes get a very long pause between songs that isn't there with the screen on. I will try raising my screen off speed to see if that changes anything.
Sent from my Desire HD using XDA Premium App
henrybravo said:
Cool, thanks for that info. Are you finding that forcing a 245 mhz screen off speed is impacting any apps running while your screen is off (e.g. music playing apps)? A couple of weeks ago I tried forcing the screen off at 122 mhz to see if that would help battery life, but I had big problems with music apps stuttering. I didn't play around with the speeds to see if raising the forced minimum to 245 would have fixed the problem. Some kernels advertise as a feature "Max speed - screen off 576MHz" or some other speed, but I don't know if it needs to be that high or not, for app stability.
Click to expand...
Click to collapse
I noticed this yesterday. My screen off is also 245. My music stuttered, but only once (and it was fairly brief).
I raised the screen off speed to 368 and have not had any sputtering or long pauses between songs, even when streaming from the cloud.
Sent from my Inspire 4G using the power of the dark side.
biglittlegato said:
I raised the screen off speed to 368 and have not had any sputtering or long pauses between songs, even when streaming from the cloud.
Sent from my Inspire 4G using the power of the dark side.
Click to expand...
Click to collapse
Good to know, thanks!
Cyanidex00 said:
As the thread states, I obviously have a question about SetCPU and processor settings.
Is it better to have the processor underclocked and almost always using 100% to use programs, or it better off to overclock and have more processing power without using 100% or close to that mark.
And what would be more beneficial for battery life.
Edit: And if mods could move this to Q&A. Clicked the wrong forum.
Thanks,
Cyanide
Click to expand...
Click to collapse
I use SetCPU at 460/1152 brazilianwax, screen off 122/537 conservative and have good battery life and no issues when playing music w/ screenoff....
Overclocking is almost guaranteed to worsen battery life compared to say if it was at stock 1 ghz or a little less.
With a governor like on demand, its gonna scale from the lowest to to highest allowed as soon as it gets some load on it, eg from 245mhz to whatever Max is (1017, 1075, or 1920 etc), without stopping in between.
Even conservative with fast scaling will probably scale close to Max clock speed pretty quickly under load, so theoretically this should be a /little/ better for battery than on demand, but will not seem as fast and could possibly make the phone seem more laggy. Smartass is very similiar to conservative as it scales depending on a preset % of CPU load. If its set to 70%, when CPU reaches 70% load, it scales to next frequency, when that frequently hits 70% load, its scales again. The version of the on demand governor most of us have in out kernels is the fastest scaling option, which goes from min CPU - straight to max
So yeah, just what the title says.
I'm running a T-Mobile NS with a CM7 nightly build (#212) and the stock kernel in said build. No matter what I do, my audio will briefly skip from time to time when playing MP3s with the screen off. I can't figure out why or how to stop it.
It doesn't seem to matter which governor I have set. It skips on ondemand. It skips on interactive. It skips on smartass. It skips on conservative. I haven't tried performance, because I need my phone to actually last the whole day. It doesn't seem to be related to clockspeed. It just skips no matter what I do.
Even with Voodoo Sound, there's no way the music player should need more than 1GHz to play audio. My last Samsung device, a Vibrant, and the phone I had before the NS, a mytouch 4G, never once had this problem.
So yeah, it's annoying. What gives? No matter what I do--short of reverting to stock (I haven't tried that yet, and I like CM7 too much to give it up)--it doesn't seem to help.
I can tell you I get the same issue with mine on 199. Which app do you use? I use mixzing
Same here with power amp, nexus nv rom.
What do you guys have set for your min cpu. I would guess 100. Change it to 200 and see if that helps. I am an avid runner and this is what I have found to help me.
Sent from my Nexus S 4G
I'll set it to 200 and see what changes I get. The skips are so brief and intermittent it may just get hung up at 100MHz and can't jump to the next frequency before it falls behind for just a split second.
synaesthetic said:
I'll set it to 200 and see what changes I get. The skips are so brief and intermittent it may just get hung up at 100MHz and can't jump to the next frequency before it falls behind for just a split second.
Click to expand...
Click to collapse
What governer are you guys using? I used to get this with smartass. Try ondemand /something else
Same issue with the Sirius app...
kinda weird.
Also tried all governors...
On NSCollab 1.0.42
bringonblink said:
What governer are you guys using? I used to get this with smartass. Try ondemand /something else
Click to expand...
Click to collapse
I've been using ondemand, 1000 max 100 min, 30000/85. Bumping it to 1000/200 seems to have solved the problem.
I'm guessing that the MP3 player can deal with running at 100MHz most of the time, but it's really close, and if CPU usage spikes a bit (due to background processes, updates, syncs, notifications) it can't bump up to the next step before the MP3 decoder falls behind.
Max clockspeed doesn't seem to affect it at all. As an experiment I capped my clockspeed at 400MHz (ondemand 400/100) and it didn't skip any more than usual, so it may end up working with smartass as long as the screen off max is set to 400 or higher.
Does anyone else think the CPU running at 480Mhz-800Mhz screen on is a bit too high? It's more than capable running at a 122Mhz minimum - heck, even 19Mhz, although it doesn't spend much time at 19Mhz. Also, if perflock is enabled, it locks itself to 245Mhz only when screen off - still seems a bit too high for me, considering there's lower selectable frequencies.
Anyone who's temprooted their device: Are you using SetCPU to change the CPU frequencies/disabling perflock? I have my Chacha running at 800Mhz max / 122Mhz min perfectly fine (running my battery down for a while to see if the battery life benefits) - although occasionally, it still locks itself to 122Mhz even after turning the screen on for about a minute, which I believe is a kernel issue
For reference, the frequency options are: 19Mhz, 122Mhz, 128Mhz, 245Mhz, 480Mhz and 800Mhz.
128Mhz doesn't actually work, and if it's selected, it uses 245Mhz instead even though SetCPU says "128 min"
Unfortunately I can't help you, but I'm totally interested on the subject!
As far as I know and tested on other android devices, setting the CPU freq too low will cause some unwanted behavior like being unable to power up the screen. Happened on a Galaxy S, where I've set the freq to 19Mhz (or something similar) and I've locked the screen. Pressing the power button did nothing so I had to re-flash the rom.
really need low cpu frequency?
low frequency is certainly not good. For chachar, I just hope 600 frequency could be done the hardware itself(not by setcpu). I hate the power consumption is too big, and the machine is easy to get hot.
Alex C. said:
As far as I know and tested on other android devices, setting the CPU freq too low will cause some unwanted behavior like being unable to power up the screen. Happened on a Galaxy S, where I've set the freq to 19Mhz (or something similar) and I've locked the screen. Pressing the power button did nothing so I had to re-flash the rom.
Click to expand...
Click to collapse
True, setting the frequency too low is bad for some devices, but in my personal experience with my Chacha, I can actually run mine at 19Mhz min/800Mhz max and have little to no problems, since it doesn't spend much time at 19Mhz anyways. (I use no SetCPU profiles, as I feel they have little to no benefit on battery life.)
All of this is just a thought though, since HTC set the minimum to 480Mhz with the screen on which seems way too high to me :/
Also, locking the CPU to a single low frequency was actually a bad thing on one of my old devices, a Desire Z, which usually caused wake problems, etc.
semanty said:
low frequency is certainly not good. For chachar, I just hope 600 frequency could be done the hardware itself(not by setcpu). I hate the power consumption is too big, and the machine is easy to get hot.
Click to expand...
Click to collapse
600Mhz is possible indeed - the MSM7227 processor that the Chacha uses is actually rated at 600Mhz, but HTC factory overclocked it to 800Mhz. It would require a custom kernel to have 600Mhz added back in
anyone thought of a way to undervolt???? i mean use less voltage for each frequency..am trying to search for kernels to flash but cudnt find any
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.
Hey XDA,
I'm running PixelRom 1.7.2 and Trinity TEUV and my phone is almost always running at 1000Mhz, which is causing terrible battery life. Even if I'm just idling at my launcher, it will go that high... Anybody know how to get it to stay at lower frequencies? Oh and my governor is Ondemand and scheduler is Deadline. Hope someone can help...
FirePoncho86 said:
Hey XDA,
I'm running PixelRom 1.7.2 and Trinity TEUV and my phone is almost always running at 1000Mhz, which is causing terrible battery life. Even if I'm just idling at my launcher, it will go that high... Anybody know how to get it to stay at lower frequencies? Oh and my governor is Ondemand and scheduler is Deadline. Hope someone can help...
Click to expand...
Click to collapse
teuv runs at 880mhz.
its possible that an app or a background process is active. try this free app from the market, its called diagnosis https://play.google.com/store/apps/details?id=eu.thedarken.diagnosis&hl=en
I thought it did too, but NsTools and CPU spy both give me: 100Mhz, 200Mhz, 400Mhz, 800Mhz, 1000Mhz, and 1096Mhz. I will try the tool from the market (yes, I still calls it the market)
FirePoncho86 said:
I thought it did too, but NsTools and CPU spy both give me: 100Mhz, 200Mhz, 400Mhz, 800Mhz, 1000Mhz, and 1096Mhz. I will try the tool from the market (yes, I still calls it the market)
Click to expand...
Click to collapse
1096... thats not teuv, that the t11 kernel. heres the latest teuv http://goo.gl/5JwMT im using this one at the moment
My thanks good man, that was the one I was looking for, now I feel quite silly :3
Right now, just at my launcher, cpu is switching from 92% to 100% usage :s
FirePoncho86 said:
My thanks good man, that was the one I was looking for, now I feel quite silly :3
Right now, just at my launcher, cpu is switching from 92% to 100% usage :s
Click to expand...
Click to collapse
if you just booted, it should(for about 2-4 minutes) then it should drop. unless you have an active live wallpaper, an app thats not written very well, or a process thats gone wild. try that app i linked, let it run for a few hours, maybe you can find the cause.
My phone had been on for a few hours...
Also, I flashed TEUV, and I don't think my phone handles it very well (TEUV has GPU overclock). Once I booted, it gave me a black screen and said: (Application) has stopped working for every app on startup. This happened twice, so I went back to Matr1x and battery is still terrible...
FirePoncho86 said:
My phone had been on for a few hours...
Also, I flashed TEUV, and I don't think my phone handles it very well (TEUV has GPU overclock). Once I booted, it gave me a black screen and said: (Application) has stopped working for every app on startup. This happened twice, so I went back to Matr1x and battery is still terrible...
Click to expand...
Click to collapse
sounds like a bad download of teuv.
Bad download? I flashed it properly and it booted fine, until after the "optimizing applications" screen
is this the first charge since you flash the kernel? If it is, let the battery run out, charge it full and take a look at it again. I find that ICS really take a full charge to stablize its battery... my first charge after flashing a new kernel has always use a lot more battery than the second charge.
Alright, I'll try that... Also I went back to aosp+ because I really like it.
Also, android system is always using 20% cpu, even on idle..
I remember performing some tests with frequencies and deep idle - I wanted to find out the minimum frequency required to run music player screen-off with few concurrent processes. I remember reading how 400mhz is the optimal frequency for deep idle but cpu spy would always report it cruising at 1ghz and cross referenced with nstools DI stats, it was supposedly in deep idle. With DI off and bumping up the frequency to 800mhz, 1ghz took up the majority of operation time. Long story short, whatever combination I tested did not garner desirable results. That was a couple weeks ago, though. I've since given up on figuring it out.
Wait, are you having the same problem as me?Ive lost 5% battry just by having the screen on for 9 minutes...