Took me 2 hours to figure out why my phone was lagging out even more than it was prior to root. Slow dialing, lagged texting, lagged screen on, etc. Once I reverted back to "moto_hotplug" governor in SetCPU, everything is perfect.
Sent from my DROID3 using Tapatalk
That's strange my default setting in setcpu was ondemand and all is well
I was experiencing the same issue every time I turned my screen off, except my phone would completely freeze and my only option was pulling the battery. Finally I discovered it was the one profile in SetCpu that was set to clock down and scale to ondemand when the screen was off.
Can anyone confirm that clocking down with profiles works as long as the scaling is ondemand?
djdmbrwsk said:
Can anyone confirm that clocking down with profiles works as long as the scaling is ondemand?
Click to expand...
Click to collapse
I tried that out and it doesn't seem to work even if I leave the scaling as moto_hotplug. It takes a few minutes, but it definitely completely freezes up.
djdmbrwsk said:
I tried that out and it doesn't seem to work even if I leave the scaling as moto_hotplug. It takes a few minutes, but it definitely completely freezes up.
Click to expand...
Click to collapse
Same here, but others are still reporting that they are underclocking with SetCPU just fine. I'm leaving it alone for now, since I'd rather overclock to be completely honest with you. My battery life isn't a problem at all. 17-21 hours on average unplugged before 10%. Perfectly fine for me.
Lyxdeslic said:
Took me 2 hours to figure out why my phone was lagging out even more than it was prior to root. Slow dialing, lagged texting, lagged screen on, etc. Once I reverted back to "moto_hotplug" governor in SetCPU, everything is perfect.
Sent from my DROID3 using Tapatalk
Click to expand...
Click to collapse
I can second this issue. I played around with a bunch of different settings and found it was most stable when the max was no lower than 800, but it still froze on occasion even with hotplug selected. Overall it seems SetCPU is not really compatible with the Droid 3.
I switched mine to Ondemand as well and it was quickly obvious the phone didn't like it. Quadrant scores dropped to 1000-1500 range. Setting back to moto_hotplug and Quadrant scores back over 2200 and everything is running smooth.
I learned this the hard way as well. I had it changed to the settings I used on my thunderbolt back then, using ondemand screen off 300 max 300 min. When Handcent received a message, texting would lag, etc and once I changed back to moto_hotplug everything was great again!
Sent from my DROID3 using Tapatalk
Related
I just rooted my HTC Hero (Sprint) Stock 2.1 and now I notice my Cpu is running slow. If I install SetCpu it speeds it up right away...Upon opening SetCpu I notice my Cpu speed says 245 mhz max/min. When I the refresh it it says 480/528 but after my screen turns off and back on it slows down again and returns back to 245 mhz. I never had this problem until after I rooted the phone. Why does my phone keep reverting back to 245 mhz and slowing down after I turn my screen off? Also it seems like my Battery life has gone down drastically...
edit: I intalled overclock widget and when I open it it also says 245 mhz. When I then set it up to 528 it makes my phone run fast again. As soon as I turn my screen off and back on it automatically reverts back to 245...
fifedogg said:
I just rooted my HTC Hero (Sprint) Stock 2.1 and now I notice my Cpu is running slow. If I install SetCpu it speeds it up right away...Upon opening SetCpu I notice my Cpu speed says 245 mhz max/min. When I the refresh it it says 480/528 but after my screen turns off and back on it slows down again and returns back to 245 mhz. I never had this problem until after I rooted the phone. Why does my phone keep reverting back to 245 mhz and slowing down after I turn my screen off? Also it seems like my Battery life has gone down drastically...
edit: I intalled overclock widget and when I open it it also says 245 mhz. When I then set it up to 528 it makes my phone run fast again. As soon as I turn my screen off and back on it automatically reverts back to 245...
Click to expand...
Click to collapse
Your phone going to 245 is completely normal. It only gives your phone power when it needs it, and sitting on Setcpu screen isnt going to make it throttle up. You dont want your phone running at 528mhz at all times. It will KILL your battery. Our phones have a setting of "Ondemand", like gives the power on demand, if its not demanding a lot of power it will go back down saving battery life, CPU life and keeping temperatures down.
If you have problems with the phone running slow, i recommend checking out an overclocked kernel. You can run it at stock speeds, if you dont feel comfortable running OC. But if you want the extra power, the choice is always there.
Sounds like something to do with conserving battery by dropping the cpu speed.
-------------------------------------
Sent via the XDA Tapatalk App
Had thr same problem in the beginning way back idk how i guxed it i guess its the stock rom idk
-------------------------------------
Sent via the XDA Tapatalk App
Well on a stock rom setcpu cant do anything other then read the cpu and it will only update when it is force refresh. If you want setcpu to be able to control or change your cpu speeds this will require installing a rom that is overclock enabled. There are several located on this forum.
For some reason SetCpu was doing this. I just set it back to 480/528 and rebooted it and then uninstalled SetCpu and now everything is fine. For some reason SetCpu was the cause of this. I reinstalled to make sure and sure enough it was happenening again. I'm glad I figured it all out
Yeah, apparently you decided to create a new thread instead of utilizing the response I gave to your thread last night:
If it is not a ROM running an overclockable kernel apps like setCpu and OC widget will actually slow your phone down. If you would like to see your clock speed without this side-effect, I suggest SystemPanel.
Click to expand...
Click to collapse
For future reference, anyone not using a ROM based on Toast's kernel DO NOT install an OC program. This is the typical behavior and it is not fun to deal with because you will have to be patient waiting for the phone to start up and open the OC program to set it back and uninstall. I believe that just uninstalling and rebooting is sufficient, but am not 100%.
lineman78 said:
Yeah, apparently you decided to create a new thread instead of utilizing the response I gave to your thread last night:
Click to expand...
Click to collapse
I actually made that thread at the same time last night. I didnt know where to put it exactly...
fifedogg said:
I actually made that thread at the same time last night. I didnt know where to put it exactly...
Click to expand...
Click to collapse
Aw, this must be the one from the Dev section and got moved over here. I noticed it over there, but had already posted on the one in Q&A... So now there are 2 in Q&A.
I've done numerous tests with and without OC and on different kernels (both normal and custom). So far SetCPU have only given me headaches. Random crashes, unable to wakeup, kernel panics... The list goes on.
According to these tests I've come to the conclusion that SetCPU is very unstable on Galaxy S and should not be considered supported at all.
What's your experience with SetCPU on Galaxy S? Is it conclusive with mine? Do you experience the same problems with Overclock Widget, or is it more stable?
after using setcpu for a few weeks and getting similar problems, i removed it.
There is pretty much no use in it for this phone, they allready scale from 100mhz - max speed (even oc if you have one) automatically
mekwall said:
I've done numerous tests with and without OC and on different kernels (both normal and custom). So far SetCPU have only given me headaches. Random crashes, unable to wakeup, kernel panics... The list goes on.
According to these tests I've come to the conclusion that SetCPU is very unstable on Galaxy S and should not be considered supported at all.
What's your experience with SetCPU on Galaxy S? Is it conclusive with mine? Do you experience the same problems with Overclock Widget, or is it more stable?
Click to expand...
Click to collapse
Are you using a task manager? I had the same problem as you until I removed the auto task killer I had previously installed. Now I can set setcpu to 100000 min 1000000 max ondemand for main with a profile of screen off 100000 min 1000000 max conservative.
mekwall said:
I've done numerous tests with and without OC and on different kernels (both normal and custom). So far SetCPU have only given me headaches. Random crashes, unable to wakeup, kernel panics... The list goes on.
According to these tests I've come to the conclusion that SetCPU is very unstable on Galaxy S and should not be considered supported at all.
What's your experience with SetCPU on Galaxy S? Is it conclusive with mine? Do you experience the same problems with Overclock Widget, or is it more stable?
Click to expand...
Click to collapse
Yes. I have the same problem on my stock SGS.
Setcpu is not working good on sgs. Try to remove it, and you'll get better battery life.
Sent from my GT-I9000 using Tapatalk
I don't know of anyone who has tested it on the I9000 (and there may even be alternatives or the same thing floating around the development subforum), but they claim to have a 1.2ghz overclocked kernel here for the I9000. Maybe best to be avoided, but a 100% use at your own risk alternative, especially if you're a bit unsure on any of the translated steps, is available here.
http://translate.google.com/transla.../matpclub.com/board/index.html?id=tipn&no=144
been using it on a vibrant for about 10 days and had my first issue last nite - it froze the phone - had to remove battery to reboot, tried again, froze it again
i thought it was the last two apps i'd installed so i removed them, then there was an update, downloaded and installed, so i did a number of settngs changes, closing setcpu, running benchmark quad, reopening & changing settings etc
about half dozen times
and it's been fine so far -
I had the same issue. I would pull my phone out of my pocket and it wouldn't wake up. I could call my phone and it would ring but my phone would do nothing until I removed the battery and re-booted. This happened numerous times until I uninstalled SETCPU and it stopped doing that so I knew I found the culprit and haven't tried it again since (I need to receive calls as priority 1)
doesnt anyone search anymore i posted this issue over a month ago. setting cpu mode to anything on than conservative can cause freezes as the system doesnt get enough cpu to wake up.. it is even mentioned in set cpu to use conservative.
lgkahn said:
doesnt anyone search anymore i posted this issue over a month ago. setting cpu mode to anything on than conservative can cause freezes as the system doesnt get enough cpu to wake up.. it is even mentioned in set cpu to use conservative.
Click to expand...
Click to collapse
I have it set to Conservative on my Vibrant, and I'm having the same issues as the OP.
Edit: When I go into SetCPU after pulling the battery and resetting, it shows it's limiting my CPU to 19.2 MHz. Yes, 19.2. Insane.
tt4079 said:
Are you using a task manager? I had the same problem as you until I removed the auto task killer I had previously installed. Now I can set setcpu to 100000 min 1000000 max ondemand for main with a profile of screen off 100000 min 1000000 max conservative.
Click to expand...
Click to collapse
I killed my task manager service, and it didn't freeze up! I'm going to uninstall the task manager and see if I have any more freezing issues in the future.
Edit: Nope, didn't work. Removing SetCPU.
mekwall said:
What's your experience with SetCPU on Galaxy S?
Click to expand...
Click to collapse
I have the Vibrant version with T-Mo. After rooting, Titanium, Barnacle and Root Explorer all seem to be working fine.
After a few minutes of installing SetCPU, my phone wouldn't wake up. Rebooted twice, same results.
Removed SetCPU and the phone's working fine again. Maybe the minimum speed should be set at 250 or so?
George
To begin with, you don't even need SetCPU
SGS phone automatically regulates the speed of the CPU depending on your usage.
most of the time in Stock ROM it hover around 200 Mhz, very few times it uses the max 1000 Mhz
only when there are lots of background apps running
when you runt he CPU at 1000 Mhz it gets hot fast, and it consumes more battery
good thing is it drops back down to 100~200 Mhz as soon as it's done with the heavy tasks
so having the SetCPU installed will defeat the whole purpose of power saving and CPU cycle on demand
mekwall said:
I've done numerous tests with and without OC and on different kernels (both normal and custom). So far SetCPU have only given me headaches. Random crashes, unable to wakeup, kernel panics... The list goes on.
According to these tests I've come to the conclusion that SetCPU is very unstable on Galaxy S and should not be considered supported at all.
What's your experience with SetCPU on Galaxy S? Is it conclusive with mine? Do you experience the same problems with Overclock Widget, or is it more stable?
Click to expand...
Click to collapse
I don't even remember the last time where we had a fixed clock on a cpu Allgamer. The point of setcpu is to either downclock or overclock your cpu. You might want to limit your clock to 0.6GHz just to save some juice.
Anyway, after a few hours of head scratching and 2 reboots, I uninstalled and refunded it.
I agree. Setcpu is rather unstable. I have feeling lots of the kernel overclockers have problems but blame the kernel while they should blame setcpu
i have just installed setcpu. it's probably been about a day or so now and i have not experienced any problems?
i have an Australian model (I9000) just flashed to the canadian firmware for the 3br fix.
Is it just generally not recommended to use setcpu on my SGS?
please advise. Thanks
toansta said:
i have just installed setcpu. it's probably been about a day or so now and i have not experienced any problems?
i have an Australian model (I9000) just flashed to the canadian firmware for the 3br fix.
Is it just generally not recommended to use setcpu on my SGS?
please advise. Thanks
Click to expand...
Click to collapse
It depends on what you're using it for. If you know what you're doing, it can be a useful tool. If you want to overclock, you'll want setcpu. If you want to underclock (lets say you're out and about, with 40% battery), then you can set the maximum cpu speed lower so that the battery will last longer.
You don't need setcpu if you're simply going to tell it that you want your max speed to be 1ghz, with a min of 100mhz and you want it to be "conservative". Your phone does that by default, and frankly the SGS is pretty good on its own when it comes to battery management.
thanks reuthermonkey, i will keep that in mind.
What are the perfect setcpu 2.0.3 settings for froyo JP6 I9000 rooted? Thanx in advance
Telanis said:
I have it set to Conservative on my Vibrant, and I'm having the same issues as the OP.
Edit: When I go into SetCPU after pulling the battery and resetting, it shows it's limiting my CPU to 19.2 MHz. Yes, 19.2. Insane.
Click to expand...
Click to collapse
Menu and rescan the device should restore the normal values. those values are not the ones actually used!
Long time lurker, but 1st time poster.
I've noticed on my Revolution that the CPU always runs at 1ghz. I thought CPU throttling was a standard feature in android?
Anyhow I installed CPU tuner and I get much better standby battery life now (~2% drain/hr when not using phone vs. ~5% drain/hr on standby). The phone runs mostly at 124mhz w the screen off. My problem is my revolution reboots pretty frequently and sometimes even just completely shuts down w CPU tuner on. I still get reboots once in awhile w CPU tuner turned off, but much less frequently.
Anyone else having this problem? I also have green power running in the background to turn off the data connection w the screen off. Are you guys who use setCPU not getting reboots? If so I'll spend the $2 and give that a try.
hadookee said:
Long time lurker, but 1st time poster.
I've noticed on my Revolution that the CPU always runs at 1ghz. I thought CPU throttling was a standard feature in android?
Anyhow I installed CPU tuner and I get much better standby battery life now (~2% drain/hr when not using phone vs. ~5% drain/hr on standby). The phone runs mostly at 124mhz w the screen off. My problem is my revolution reboots pretty frequently and sometimes even just completely shuts down w CPU tuner on. I still get reboots once in awhile w CPU tuner turned off, but much less frequently.
Anyone else having this problem? I also have green power running in the background to turn off the data connection w the screen off. Are you guys who use setCPU not getting reboots? If so I'll spend the $2 and give that a try.
Click to expand...
Click to collapse
I honestly don't think anyone has been messing with the CPU until the CM ROM is released.
hadookee said:
Long time lurker, but 1st time poster.
I've noticed on my Revolution that the CPU always runs at 1ghz. I thought CPU throttling was a standard feature in android?
Anyhow I installed CPU tuner and I get much better standby battery life now (~2% drain/hr when not using phone vs. ~5% drain/hr on standby). The phone runs mostly at 124mhz w the screen off. My problem is my revolution reboots pretty frequently and sometimes even just completely shuts down w CPU tuner on. I still get reboots once in awhile w CPU tuner turned off, but much less frequently.
Anyone else having this problem? I also have green power running in the background to turn off the data connection w the screen off. Are you guys who use setCPU not getting reboots? If so I'll spend the $2 and give that a try.
Click to expand...
Click to collapse
As far as I've seen, the Revo's CPU does automatically speed scale to the necessary load.
If you're running lots of apps in the background, with the screen on Android will keep the cpu at full throttle to provide a smooth experience for you.
As soon as you turn off the screen, it will throttle it down as much as it can.
If the phone's rebooting on you, that's because whatever cpu tuner is doing may be keeping the cpu speed too low for the demand of the OS, then the watchdog kicks in when it thinks the cpu is stuck in a loop. (watchdog wants to be petted every 30 seconds, if the cpu misses that, the watchdog reboots the phone)
I use setcpu and have no reboot issues.
Sent from my VS910 4G using XDA App
throttle
I use android system info to show the CPU speed. It shows the % of time my revolution is running at each speed. W/o using a 3rd party app it always shows 100% at 1Ghz. W CPU tuner running it shows 50% at 122Mhz, 25% at 1Ghz, and 25% in between.
I don't think I'm running any apps thats sucking up a lot of CPU. I'm rooted w most of bloat removed.
Am I the only one not seeing any CPU throttle on stock?
i'm not seeing any throttling on stock.
setcpu drastically improved battery life when the phone's off, and no reboot issues.
some issues initially with the phone not throttling back up quickly enough when i got a call, making me unable to answer the call, but played with the settings and made it so it automatically throttles back up to 1024 when i get a call, and now it's fine.
Exactly Im much happier with my phone now. I had the same issue when I received a call but set up the profile as u did and have no problems at all
newkick said:
i'm not seeing any throttling on stock.
setcpu drastically improved battery life when the phone's off, and no reboot issues.
some issues initially with the phone not throttling back up quickly enough when i got a call, making me unable to answer the call, but played with the settings and made it so it automatically throttles back up to 1024 when i get a call, and now it's fine.
Click to expand...
Click to collapse
Sent from my VS910 4G using XDA App
I am using setCPU as well with no issues. I have mine set were the screen is off it goes to 124 and clocks back up to full 1GHz when it is on. Helps greatly improve my battery.
So what settings do you use? I get really bad lag when waking my Revo. Sometimes it will reboot after waking too.
Sent from my VS910 4G using XDA App
I don't know if this is a CPU throttling issue, or a general REVO issue, but I get horrible horrible lag sometimes trying to get any programs to respond. Like press the home key, or click send, or anything like that. I'm running Decrap 1.1, I don't know if I have too many processes running or what.
Interesting. The Thunderbolt has the same issue. Is it the same CPU in that phone?
Has anyone underclocked their O2X? I personally think that overclock is a bit of a placebo effect so I just want to know if anyone has underclocked their phone and if they can kindly share the performance of the phone as well as some benchmarks. I've seen people underclock their Galaxy S2 right down to 500mhz and performance is very smooth! Is O2X similar?
I didn't do any benchmarks (speaking of placebo effect ) but I use setcpu with vorkkernel so that my top frequency gets more and more limited with the battery level and overnight. This way I manage to only loose 1-2% during the night and the phone alive for a couple of hours when under 15%.
I noticed a certain UI lag when under 500mhz but not so much in the graphics department, I guess the gpu has it's own clock.
I have underclock/undervolt to 800Mhz/900mV and works very smoothly
just got setcpu... those profiles are awesome
Lg home is a memory hog and seems to be quite cpu intensive compared to most other home apps but if using a dif homescreen then maybe it will still perform smoothly otherwise i doubt it will perform good.
Hi... I have installed cynogenmod 7.1 Stable. In Performance > CPU Settings, it shows 216/1000MHz as the only available frequency. I installed SetCPU, it closes saying some error.
Can you please tell me what I have to do, basically I want to underclock it for battery issues.
Thanks
Just undervolted all default values by 100mV, stress test running perfect. CPU at 52C on a 18ish ambient day.
I have 3 setcpu profiles on stock.
In call : 312/216
Screen off : 216/216
Battery <100% : 760/216
Getting amazing stand by time, 2h 30m since I unplugged the charger and only 1% battery spent.
Getting decent results during use as well, or atleast thats what I call it. Earlier today I went through 400+ google reader articles over wifi and watch accompanying youtube videos and also checked some external links. After about 30 mins I lost 7-10% battery. I think thats good enough, unless someone here is about to blow my mind with their results
3h and 30m now still at 99%.
5 minutes of evernote and battery at 95% now. Sooo unsatisfying.
benchmark @800Mhz
what rom you using and what setting for oc
Kickasskev said:
what rom you using and what setting for oc
Click to expand...
Click to collapse
Topogigi v20 SP3.
Andrev OC 800MHz wake.
[email protected]
pretty smooth for daily use.
if play heavy games, I restore it back to 1GHz.
what kernel
Kickasskev said:
what kernel
Click to expand...
Click to collapse
Neoblaze, from SP2.
I need as stable ROM as possible, but fast.
all stock from Topogigi's built.
Do you have google video calling via front cam ? That's all I care about and I cant find the answer anywhere.
My lg might be getting decent battery life but the entire operation/daily use experience is very bad. Last night I used subsonic to stream my home library to my phone and while I listened to it I read stuff on google reader and then everything started to lag. Just setting the max and min isn't working well for me. I ran antutu last night and got 4500ish numbers with setcpu and juicedefender off and You are getting 6500+
quabrant 1580marks on 600mhz
after 3 hrs on 600mhz I'm impressed with the battary live!
3hrs wifi browsing, 2times quadtant test. battary dropped 12%
oleg1981 said:
quabrant 1580marks on 600mhz
after 3 hrs on 600mhz I'm impressed with the battary live!
3hrs wifi browsing, 2times quadtant test. battary dropped 12%
Click to expand...
Click to collapse
Post more info, what rom, kernel etc. I set my max to 600 and I get good battery but it takes all the fun out of using it, everything lags. You can still do things sure but I dont like lag.
---------- Post added at 04:16 PM ---------- Previous post was at 04:11 PM ----------
miina_tokiha said:
Topogigi v20 SP3.
Andrev OC 800MHz wake.
[email protected]
pretty smooth for daily use.
if play heavy games, I restore it back to 1GHz.
Click to expand...
Click to collapse
How is the battery life ? Also the 800mhz wake and undervolt are those part of sp3 or extra steps you did ?
retareq said:
Post more info, what rom, kernel etc. I set my max to 600 and I get good battery but it takes all the fun out of using it, everything lags. You can still do things sure but I dont like lag.
Click to expand...
Click to collapse
100% stock rom + over it.
the version is 2.2.2 v20b
nothing lags. the only diference i see is thet lock screen sart to respond about 1second after power button is pressed. before it was instant.
Thanks for the info. I'm on v21b rooted with setcpu max set to 600ish and there is noticeable lag everywhere. Feels like how the phone was when I first got it and had to replace the lg launcher to get rid of the lag.
retareq said:
Do you have google video calling via front cam ? That's all I care about and I cant find the answer anywhere.
My lg might be getting decent battery life but the entire operation/daily use experience is very bad. Last night I used subsonic to stream my home library to my phone and while I listened to it I read stuff on google reader and then everything started to lag. Just setting the max and min isn't working well for me. I ran antutu last night and got 4500ish numbers with setcpu and juicedefender off and You are getting 6500+
Click to expand...
Click to collapse
6500+ is when I overclock to 1,4GHz.
it's only for benchmark, and not for daily use.
retareq said:
How is the battery life ? Also the 800mhz wake and undervolt are those part of sp3 or extra steps you did ?
Click to expand...
Click to collapse
battery life is about 24h of normal use.
I always connected to wifi.
oh, and I replace LG Home Launcher with Xperia Launcer.
it's lighter, no lag even use lower clock speed.
Hey guys,
I just wondered if you guys have the same problem that you lose 1% battery every 2 minutes when you´re having your display on. I know it´s quite known that big screens suck the battery like a vampire but that´s just odd, because I don´t even have to do anything with the phone just staring at the activated display.
I´ve had these troubles from the beginning with FW 10G then updatet to 10H and did factory reset- nothing changed. I tried different brightness levels without any differences in battery consumption, which is totally uncommon. And the freaky thing is there is no difference whether I have airplanemod on, wifi turned off and so on. It is always the same... Although when the display is off there is as good as no consumption but really 1% battery per 2 minutes that´s just sick. I can´t believe it.
Now i wondered if this is normal or if I should turn it to the customers service to check it.
Please tell me if you explored the same things with your LG 4X HD
Well i found it odd too but if you would root the phone and install something like setcpu you would actually see
Min CPU Freq --------------- 1.5 GHz
Max CPU Freq -------------- 1.5 Ghz
Er yeah .... after saying that i think you know why its using the battery so fast. I rooted my brothers phone and changed the clockspeeds , but no matter how low i set the min freq on "no frills cpu control" it always shows on the toast message 750 Mhz or somewhere around that.
-Grift- said:
Well i found it odd too but if you would root the phone and install something like setcpu you would actually see
Min CPU Freq --------------- 1.5 GHz
Max CPU Freq -------------- 1.5 Ghz
Er yeah .... after saying that i think you know why its using the battery so fast. I rooted my brothers phone and changed the clockspeeds , but no matter how low i set the min freq on "no frills cpu control" it always shows on the toast message 750 Mhz or somewhere around that.
Click to expand...
Click to collapse
Well thank you... I´ve rooted it and thought it had something to do with apps running in the background but it didn´t help at all so I thought this can´t be, mine must be wrong somehow.
Especially because i haven´t heard anything in reviews or forums about this rapid battery drain. This is something I´m wondering most, how can a phone taking so much battery be rated so high It sucked 3% watching a 3 minute video on youtube...
I won´t think I´m going to be happy with this phone and the best is when I contacted customers service later today they told me to send it in because its not normal, but now that you said the cpu is set this high no matter what, I can just suggest they don´t know anything about their phones...
Bet the only reward I get sending it in is "all is fine our phone likes to suck your battery, so what? Just keep the display off"
Screen off "deep sleep" battery drain is quite bad too ..
-Grift- said:
Screen off "deep sleep" battery drain is quite bad too ..
Click to expand...
Click to collapse
For me. The battery says its fully charged after 1hr. But it actually takes 3-4hrs befire it reaches the absolute full capacity.
Battery lasts twice as long then...
Sent from my LG-P880 using xda app-developers app