Related
I've always read in the past that the app doesnt actually help with battery life because its purpose was for OCing and Android regulates the cpu clocks already.
So I'm wondering, for those currently using it, have you noticed any difference in battery life (without underclocking while in use)? and if so what profiles are you using?
regP said:
I've always read in the past that the app doesnt actually help with battery life because its purpose was for OCing and Android regulates the cpu clocks already.
So I'm wondering, for those currently using it, have you noticed any difference in battery life (without underclocking while in use)? and if so what profiles are you using?
Click to expand...
Click to collapse
I have just one profile, screen off= 216/216. I'm now on 14 hours with 30% left. Much better than before, when I was getting 11 hours at the most.
I also use the battery calibration app. But that's all I've done.
Just want to add I use wifi calling, and I run everything else, gps and syncing gmail and facebook is on. Screen is set to auto brightness. The only thing I have off is bluetooth.
Profondo_Rosso said:
I have just one profile, screen off= 216/216. I'm now on 14 hours with 30% left. Much better than before, when I was getting 11 hours at the most.
I also use the battery calibration app. But that's all I've done.
Just want to add I use wifi calling, and I run everything else, gps and syncing gmail and facebook is on. Screen is set to auto brightness. The only thing I have off is bluetooth.
Click to expand...
Click to collapse
I do the same.. just 1 screen off profile to underclock it to 216/216 when the screen is off
regP said:
I've always read in the past that the app doesnt actually help with battery life because its purpose was for OCing and Android regulates the cpu clocks already.
So I'm wondering, for those currently using it, have you noticed any difference in battery life (without underclocking while in use)? and if so what profiles are you using?
Click to expand...
Click to collapse
Android does regulate the cpu, but I don't think it will take advantage of more conservative governor modes unless you tell it to. That's only relevant if the kernel supports more conservative governor modes. And, as the other responses have pointed out, you can force Android to be more conservative by capping the max clock speed.
Hmm... Guess its worth a shot. Good lookin out guys.
when i go into setcpu there are alot of options to choose there is no auto detect like on my mytouch 4g. how did you guys get it to work. i picked the last option which was custom and it forced close on me.
charlieb620 said:
when i go into setcpu there are alot of options to choose there is no auto detect like on my mytouch 4g. how did you guys get it to work. i picked the last option which was custom and it forced close on me.
Click to expand...
Click to collapse
Yeah.. When I hit the tegra 2 option it wont let me change the governor.
You need to be rooted so that you can let set CPU have super user access. Are you rooted yet?
regP said:
Yeah.. When I hit the tegra 2 option it wont let me change the governor.
Click to expand...
Click to collapse
I think that that means that the kernel is not supported for the "automatic" governors. However, you can still create profiles to regulate the CPU based on perameters that you set, i.e. Screen off 216/216
jayohwhy said:
I think that that means that the kernel is not supported for the "automatic" governors. However, you can still create profiles to regulate the CPU based on perameters that you set, i.e. Screen off 216/216
Click to expand...
Click to collapse
So all G2x see the same in setcpu - no autodetect and only governor available is "driver"?
Will custom ROMs like CM7 change this?
SetCPU improved my battery life tremendously! Before I was losing about 15-30% and hour, since 8:30 this morning my battery only dropped to 73%. I set my active profile between 457mhz and 816mhz depending on remaining battery and it's still fast as hell.
rhinology said:
So all G2x see the same in setcpu - no autodetect and only governor available is "driver"?
Will custom ROMs like CM7 change this?
Click to expand...
Click to collapse
From what I've heard, yes, that is what every g2x setcpu user sees. I don't know whether CM7 will fix this, or maybe later versions of setcpu
jayohwhy said:
From what I've heard, yes, that is what every g2x setcpu user sees. I don't know whether CM7 will fix this, or maybe later versions of setcpu
Click to expand...
Click to collapse
Once we get some custom kernels, we should be able to change the governors in setCPU, dependent upon on what the kernel supports.
SetCPU Custom Frequencies for G2X
I got SetCPU today and was playing around with it and it looked like it was limiting my CPU all the time due to lack of profile, not just when I had the screen off per my profile so I looked into making a text file for custom frequencies and am posting it here since there doesn't seem to be any help for g2x with it.
This is a really simple file, tell me if you guys have any better ideas, I just put in:
216000,528000,712400,1000000
I'm attaching it. I put the file in my dropbox, grabbed it via the app and then moved it to /sdcard/setcpu.txt via astro file manager then loaded custom profile from within setcpu. Hopefully this saves someone some time or you can tell me if I'm going about this the wrong way
I'm sure it could be fine tuned more but I was getting irritated at how much of a pain it was to unlock the phone with it set too low, so for screen off I have it set to 216->528. You could add 254000 in or something. The phone seems to be as usable as before now with setcpu enabled like this while it should be limiting the cpu when the screen is off. It sucked (well not the battery) without a custom profile.
socalTNT said:
You need to be rooted so that you can let set CPU have super user access. Are you rooted yet?
Click to expand...
Click to collapse
rooted?????? what is that?
TheMightiest1981 said:
SetCPU improved my battery life tremendously! Before I was losing about 15-30% and hour, since 8:30 this morning my battery only dropped to 73%. I set my active profile between 457mhz and 816mhz depending on remaining battery and it's still fast as hell.
Click to expand...
Click to collapse
Yep, I agree. My phone has been off the charger for almost 9 hours, and I'm at 70%.
I have everything on, including wifi calling, and one profile in Setcpu for screen off 216/216.
Also used the battery calibration app.
Profondo_Rosso said:
Yep, I agree. My phone has been off the charger for almost 9 hours, and I'm at 70%.
I have everything on, including wifi calling, and one profile in Setcpu for screen off 216/216.
Also used the battery calibration app.
Click to expand...
Click to collapse
Im assuming u did little to no use. I did moderate use and im down to 52% after 4hrs
Sent from my LG-P999 using XDA Premium App
I tried that 216/216 profile and got the sleep of death followed by reboot loop every few minutes after the phone booted. wouldn't stop till I manually powered the phone down then back on. oh well... my phone idles fine anyway. wonder what clock speed android idles at by default.
charlieb620 said:
Im assuming u did little to no use. I did moderate use and im down to 52% after 4hrs
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
Actually, your assumption is wrong, as is often the case.
I'd quantify it more as normal use. Lots of texts, some games of Pro pool, a few phone calls, checking Pulse 3-4 times during the day for 10 minutes at a time, some mild web browsing and watching a few youtube videos.
I ended up at around 18-19 hours of of use.
Today, I'm off the charger for 8 hours, and I still have 45% left, and I would say that's with some moderate to heavy use.
regP said:
I tried that 216/216 profile and got the sleep of death followed by reboot loop every few minutes after the phone booted. wouldn't stop till I manually powered the phone down then back on. oh well... my phone idles fine anyway. wonder what clock speed android idles at by default.
Click to expand...
Click to collapse
Try upping it to 216/312 or a tad higher and you should be fine.
Has anyone else been using CPU Spy to monitor Deep Sleep? I haven't once seen my phone going in to Deep Sleep. Anyone else?
Yeah I used it since yesterday. I've frozen a ton of bloatware via TB and it went into deep sleep for 7.5hrs last night while I was asleep. I'm seeing a crazy amount of different CPU speeds in there too though. Very odd.
I actually removed all the damn bloatware instead of freezing them. But then I added my own apps that I normally use. But I think I have finally weed out the damn app that is causing my deep sleep issues. it's either FriendCaster Pro or Google Music Beta...
I gave it a try yesterday when I first picked it up. Seems to either idle really high, or low depending on what your doing. Hardly ever used the mid range cpu frequencies.
yes! Once the source code can be.... had.... Kernel development would begin. As anyone have seen using CPU Spy, the governor either MAX out the CPU or just lower it to the minimal, it "rarely" stays in the middle. With some "tweeking" how the CPUFreq works we can probably save battery
mbze430 said:
Has anyone else been using CPU Spy to monitor Deep Sleep? I haven't once seen my phone going in to Deep Sleep. Anyone else?
Click to expand...
Click to collapse
I have been using it for a couple of weeks now along with Antutu CPU Master. After charging, I usually reboot my phone and deep sleep kicks in. I use Antutu to lower the CPU speed to 192 mhz.
RAVEN6 said:
I have been using it for a couple of weeks now along with Antutu CPU Master. After charging, I usually reboot my phone and deep sleep kicks in. I use Antutu to lower the CPU speed to 192 mhz.
Click to expand...
Click to collapse
Are you having any problems with Antutu keeping the setting at 192, after I reboot my phone Antutu keeps changing the low setting up to 384? Yes I have it set to apply on boot. I sent the Antutu devs an email a few days ago asking them about this, but no reply?
Sent from, The Eclectic Chair.
I thought this was the deep sleep issue that people have with certain chargers?? plug charger in and let screen turn off then turn screen on and unlock, then unplug charger. Check to see if it goes into deep sleep then or just reboot the phone after charging....
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
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.
I am running cm9(beast mode wifi calling one ) atm but I have a heat issue with my phone around the camera and speaker area where the phone is really hot but by the battery n bottom half it is much cooler.
is this normal for you guys? N gals? And even if I turn of the phone n it cools to 91 is shoot back up again
Sent from my SGH-T959V using xda app-developers app
I'm running on demand btw and around of charge 98-113 charging 109-123
Sent from my SGH-T959V using xda app-developers app
idunno why but we have the same problem..
i think that the reason why it heat up is because you overclocking it?
when i set it max it really heat up quickly.
Install betterbatterystats and see how much CPU you are using and on what.
Sent from my SGH-T959V using xda premium
Sometimes I have this problem while charging my phone, it actually will not charge at all through the night. I think this happens when it is warm, because in the summer, the phone overheats in my pocket and dies out
dgmoodey said:
Sometimes I have this problem while charging my phone, it actually will not charge at all through the night. I think this happens when it is warm, because in the summer, the phone overheats in my pocket and dies out
Click to expand...
Click to collapse
i do that but it goes to 200 mhz never 100
xtrem88 said:
i do that but it goes to 200 mhz never 100
Click to expand...
Click to collapse
That's a 'feature' of the ICS+ kernels. While 100MHZ is the minimum, if it's actually set to that, the kernel is set to go back to 200MHZ anytime it gets the chance. You can watch this happen if your scheduler/governor app actually updates on current min/max speeds. ROM Toolbox PRO, SetCPU, ROM Control, and CM's Performance controls all display this shifting, though with luck you can sometimes get it to stick at 100MHZ. It just takes some persistence.
The modem on the phone isn't very good.
It even happens on stock where if you go in and out of dead zones, it will "SEARCH" for network and become burning hot, so it's a common problem that happens year round. It's a great way to kill battery. That's also why if you leave you phone in a sock drawer, it's going to last longer than if it's in your pocket walking around.
airfluip1 said:
The modem on the phone isn't very good.
It even happens on stock where if you go in and out of dead zones, it will "SEARCH" for network and become burning hot, so it's a common problem that happens year round. It's a great way to kill battery. That's also why if you leave you phone in a sock drawer, it's going to last longer than if it's in your pocket walking around.
Click to expand...
Click to collapse
well i left i think it was kj2 and flashed lb6 and i started using greenify hasn't really happened now
No to open another thread I have a Android backup issue any suggestions?
And power managed is on even though wifi is off
Sent from my SGH-T959V using xda app-developers app
I never got my phone to go into deep sleep when I selected ondemand (or maybe it was ondemandx). I would try a couple of the other governors & see if that would help.
Sent from my SAMSUNG-SGH-I547 using xda app-developers app
OndemandX gives me good sleep, but forces the phone to minimum speeds when the screen is off. That tends to cause issues if I'm trying to use GPS or music without the screen burning.
As to what will work best... that depends on unique your phone, its apps, any tweaks that have been made, and your specific combination of scheduler/governor settings. I'm a fan of SIO, but sometimes the tweaks make that (and deadline) stick at max MHZ, in which case noop is great. At various times, I go with any of the SA2-based 'intelligent' options (SavagedZen, brazilianwax, SmoothAss, or SmartAssv2) or the OndemandX/Conservative basic sets. The others have gotten stuck more often and tended to allocate more processor than I think it needs.
I've always had the best luck with smartassv2. I think it's a good tradeoff between good battery life and quick processor speedups in order to prevent lag, plus I haven't had the issue of the processor locking up while the screen is off.
FBis251 said:
I've always had the best luck with smartassv2. I think it's a good tradeoff between good battery life and quick processor speedups in order to prevent lag, plus I haven't had the issue of the processor locking up while the screen is off.
Click to expand...
Click to collapse
That's usually the one I always fall back on too despite new ones all the time and everything, it's my default now on any ROM.
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