On snapdragon 665, and 710 I felt cpu throttled on battery percentage of 10% even on custom from, Any ideas?
ht#ps://forum.xda-developers.com/nexus-6/general/mod-disable-throttling-battery-low-t3440814
Tried that guide, no results, any help?
I am currently making thermods so I am asking as how it should be fixed? or can it?
Related
Hi,
I have read in some threads about undervolting the phone. I want to know what exactly it means.
The default voltage for 200MHz is 950mV. Does this mean, if my phone is on 200MHz for one hour, it will consume 950mV charge from the battery?
This doesn't seem correct to me, because at this rate, the battery (100% is 4.2V) will be empty in (4200/950) hours, which is less than 5 hours.
Can someone explain how these voltages work?
Thanks
I've install Rom Toolbox,
and i saw there is a "CPU slider" where i control the clock speed.
i've put it to 1000MHz instead of 1200MHz and tested it for several days
i really dont feel any difference in performance.
browsing seems same, games like asphalt is equally smooth.
heating is similar, equally warm.
the only difference is quadrant benchmark.
1200MHz scores 3200-3400
1000MHz scores 2600-2900
frankly speaking, i'm not sure if there's any difference in battery life.
is there any way to accurately test whether the clock speed affects the battery life?
i've seen other threads, where there are very different opinions.
some say it will improve battery life, and some say its worst.
http://forum.xda-developers.com/showthread.php?t=726019
Quote: (SetCPU doesn't make a difference in battery life, it can only shorten it. The kernal already has the best settings for CPU speed built in.)
http://forum.xda-developers.com/showthread.php?t=1305465
Quote: (if you are able to stand the side effects of underclocking, it will surely boost your batery life.)
On my SGS2 program called CpuSpy shows that 1200MHz is about 1% of total cpu time (remember that governor is ondemand and CPU is at 1200 only when need it). If power consumption is directly proportional to clock speed by limiting it to 1000MHz you will get about 20% less power usage by 1% of time... looks like 0.2% power saved ? Soo if Your phone works for about 48h on one charging this way You can get about 6 extra minutes. It's just my guess...
Also have to consider if slower cpu causes screen to eat power for longer time... (because You have to wait longer for operation to complete)
slig said:
On my SGS2 program called CpuSpy shows that 1200MHz is about 1% of total cpu time (remember that governor is ondemand and CPU is at 1200 only when need it).
If power consumption is directly proportional to clock speed by limiting it to 1000MHz you will get about 20% less power usage by 1% of time... looks like 0.2% power saved ? Soo if Your phone works for about 48h on one charging this way You can get about 6 extra minutes. It's just my guess...
Also have to consider if slower cpu causes screen to eat power for longer time... (because You have to wait longer for operation to complete)
Click to expand...
Click to collapse
HI, thanks for replying. I understand what you mean. the phone dont operate at 1200MHz all the time. but when using browser, and playing games, such as asphalt, it runs at max CPU usage almost the entire gaming duration.
Anyway.....
the real question is whether the clock speed is directly proportional to the battery consumption.
while reading your post, i thought of a brilliant ideal how to verify this.
the CPU slider not only allows you to set the max CPU speed,
you can set the min CPU speed as well.
So, i thought of an experiment, lets set the min & max CPU to 1200MHz,
this way, the phone will be running constantly at max CPU even when its idle.
let the phone be turn on till it run out of battery, record the time, T1.
then repeat again with max and min CPU set to 1000MHz.
record the time it is turn on till it run out of battery, record time as T2,
then compare T1 & T2, this could certainly work.
it would be nice if any member here happens to have 2 sgs2, and tried them ;-)
There are two more things to consider
1. CPU is not the only element that consumes power.
2. SGS2's Exynos is always clocked at 200MHz when the screen is off - check if this minimum slider affects that too.
Please let know how your experiment goes.
Regards
when the screen is off, the phone will be in "deep sleep" state. i think thats less than 200MHz.
anyway, i wont be doin this experiment any time soon.
you see, this is my only phone, i need to use it.
i dont have much oportunity to leave it and wait for it to run out of juice.
still, i'll try it when i have the chance.
Hi, I've got an annoying problem...
As far as i know the first thermal threshold for kicking down the CPU freq to 800MHz is set to somewhere around 80oC in SGS3. But in my case it kicks in after achieving just 51-54oC which makes some games unplayable after 5 mins
I've read somewhere that the battery temperature (45oC or so) is also considered when throttling down the CPU frequency, but my battery hits just 41oC when it happens...
Could it be a faulty temperature sensor(s) or just faulty almost 2 years old battery? I have no more clues, could anybody help?
Thanks a lot!
flither said:
Hi, I've got an annoying problem...
As far as i know the first thermal threshold for kicking down the CPU freq to 800MHz is set to somewhere around 80oC in SGS3. But in my case it kicks in after achieving just 51-54oC which makes some games unplayable after 5 mins
I've read somewhere that the battery temperature (45oC or so) is also considered when throttling down the CPU frequency, but my battery hits just 41oC when it happens...
Could it be a faulty temperature sensor(s) or just faulty almost 2 years old battery? I have no more clues, could anybody help?
Thanks a lot!
Click to expand...
Click to collapse
That's tricky... Afaik you CAN change some system files to avoid throttling but I don't believe that that would be healthy... Your temperature sensors could also be faulty... I don't know
Sent from my toaster
yeah, but is it possible that it's throttling down on such normal temperatures? Or maybe there's another safety mechanism involved (dunno, maybe GPU temp sensor)? But my GPU runs on stock freqs and voltage...also it doesn,t matter if i'm undervolted on CPU or not, still the same
flither said:
yeah, but is it possible that it's throttling down on such normal temperatures? Or maybe there's another safety mechanism involved (dunno, maybe GPU temp sensor)? But my GPU runs on stock freqs and voltage...also it doesn,t matter if i'm undervolted on CPU or not, still the same
Click to expand...
Click to collapse
I don't actually know... I've never faced throttling problems so i don't know what else can cause this.. Perhaps there is something else involved...
Sent from my toaster
SOLVED
After a really deep search I found out that Sammy based roms have a CPU throttle after battery reaches 41oC...now to change it
Just picked up an XT1527 (full package, box, accessories, everything) from a craigslist seller for $40 - I figured it would give me something to play with until Motorola ships my "free" Moto X (32GB 2013 model) as a replacement exchange for my old Atrix HD which bricked when I installed the last update for it. For the record, this is the Cricket model.
Upon playing around with it for the past few hours, however, I've noted it tends to run just a bit warm even when I'm not really doing much of anything so I started checking into it - I'm still pure stock, mind you, 5.0.2 build LXI22.50-13.4) and I'm thinking about rooting it and perhaps checking out the CM12.1 build but there's no hurry at the moment.
Having said all that, I grabbed CPU-Z and took a peek at the SoC specs: it shows an idle speed of 800 MHz for all four of the cores even in spite of them having a 200 to 1.2 GHz range. One would think that the device would ramp down to 200 MHz when idle and not doing much of anything at all but, that's not the case so far.
So I grabbed System Monitor Lite to check just in case CPU-Z was reading things incorrectly and got the same exact results. Upon checking the pie graph it clearly shows a range of 800 MHz to 1.2 GHz and nothing below it.
Has anyone else noted this issue with the Moto E 2015 model or... am I just so new with this thing (having owned oh, maybe 200 other devices in the past decade and doing some rather intensive customizations on 'em) that I'm missing something here and just not even noticing it?
Had hoped to keep this device relatively clean and stock but, it appears that's not practical if this CPU speed situation can't be resolved. I see there's basically only the one custom kernel available so far (Squid) and while I'm not opposed to using it once rooted/etc I'm still curious as to know why this thing isn't ramping down the clock as it should. It's using the default interactive governor as well, would be nice to be able to alter that but again that's where it gets more complicated.
Anyone else noted this on their XT1527 (or any of them, really, just as long as it's a 2015 model) or would someone else that's running pure stock be willing to check their CPU usage with CPU-Z or System Monitor or something else and see if it's not ramping down below 800 MHz as it actually should? Obviously the battery life would dramatically improve if this thing would slow down as it should - there could be some new Qualcomm trickery at work here that I'm not aware of, but if it's capable of dropping back to 200 MHz, it damned well better.
Any comments and suggestions are appreciated...
ps
Also I've noted the GPU doesn't ramp down to 200 MHz as it should either, it hovers at 310 MHz almost constantly which again is just another waste of battery when staring at a static image on the screen (save for the info updates themselves but that's not really a thing that should or would trigger a big spike in GPU speed).
o.o thank you so much. You'd wonder why. Well, yesterday (I think) I made a topic about how my phone drains battery abnormally and I just checked with the app you said (cpu-z) and it seems I have the same problem. My phone feels warm almost all the time and it also keeps working up to 800 MHz in all cores. Also, I own the same model and someone in the other topic told me that battery should last 2 or 3 days without doing something. Oh anyway, thanks because now I have a hint about what's going on. Maybe its a manufacturer problem.
For some reason, Motorola set the CPU idle speed to 800 MHz. I don't know why. I lowered the idle speed to 400 MHz on my phone, and I'm not noticing any performance degradation. I haven't noticed any heat or battery issues though. My phone stays fairly cool, even under heavy load (like running benchmarks repeatedly). I've undervolted my phone slightly, that may reduce heat a bit, though I don't recall having any heat issues without the undervolt either.
Well squid, I'm guessing you are using a pretty customized setup at the moment including the kernel you've created so, I'll most likely end up getting a similar situation I suppose. Since the Snapdragon 410 can do 200 MHz to 1.2 GHz it damned well better do it; if Motorola for some reason chose to "hard lock" it at an 800 MHz idle speed that's a bit ridiculous and will only serve to hamper battery life overall.
Performance isn't the issue here since as soon as some CPU power is required it'll ramp up as expected - the issue here is the 800 MHz "bottom" which should actually be 200 MHz. That's a big difference in terms of overall battery life in the long run.
I owned an LG Tribute in late 2014 and was regularly getting 8+ hours of SOT with that which is powered by a Snapdragon 400 (1.2 GHz quad core) and that has a 2100 mAh hour battery - the Snapdragon 410 in this Moto E should be better for battery efficiency + we've got a 2390 mAh in it so, as long as it's ramping down to the 200 MHz "bottom" that it actually should be hitting then I, for all intents and purposes, should be able to expect or even exceed that 8+ hours of SOT without issues. The Tribute has an 800x480 panel in it, the E has the 960x540 so in the long run that increase in pixels should be covered by the increase in battery amperage (290 mAh more).
This Moto E 2nd gen model should be able to do 7 hours of SOT without breaking a sweat, even with cellular/Wi-Fi/Bluetooth/location services on and functional.
At least that's my goal with it... I'm on my first full charge since I bought it earlier today and currently at 58% with 3.5 hours of SOT and that's using Wi-Fi a lot with video playback as well. I've been keeping on top of the Baltimore riots that are happening presently and monitoring things using Scanner Radio Pro as well as a lot of surfing for info and news too. So far so good on the battery life, but obviously it can be much better as long as that CPU speed can be brought under better control.
As the title says, is it really worth? I mean, should i decrease my phone maximum clock speed of the cpu by, like, 100-200 mhz in order to notice less battery consumption?
thanks
You can decrease the cpu clock speed for better battery life. But don't decrease to 100-200 mhz. It can cause constant random reboots and make your device very unstable.
Really? I'm using my s3 neo with a clockspeed of 1.3 ghz instead of 1.4, and i'm rarely noticing strange things