I am using Carbon ROM 4.3 with Chronic kernal. The settings were at a min of ~1700mhz and a max of ~2200mhz. Before i set this I let the cpu temp cool to about 23 degrees Celsius. I then set the cpu governor to performance. Then I started running AnTuTu benchmark ver4. After the cpu integer test the cpu froze up. I was cooling my phone using a freezer with the phone on a paper towel which was on a bag of ice. The CPU crashed at the CPU float point test.
After another test I found that my CPU becomes unstable after 2160mhz.
The settings for the posted benchmark were CPU Min at 1674mhz and CPU Max at 2160mhz with the governor set at performance.
The minimum freq is mute when the gov is performance. Performance just keeps the cpu at the MAX freq.
Sent from my SPH-L720 using Tapatalk 2
Cloaker said:
The minimum freq is mute when the gov is performance. Performance just keeps the cpu at the MAX freq.
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
What he said.
Also you can just put the phone in the freezer for a while and let it cool way way down and then run the test while leaving it in the freezer.
Sent from my SPH-L720 using xda app-developers app
eskomo said:
What he said.
Also you can just put the phone in the freezer for a while and let it cool way way down and then run the test while leaving it in the freezer.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
I am aware of this. I did have it in the freezer until it cooled down enough. The problem was not overheating, it was the CPU becoming unstable at full load with the processor being overclocked. The phone was still cold but it went to a reboot or just turned off.
Gotcha. I missed that part. I wasn't fully awake yet at 4:30am.
Sent from my SPH-L720 using xda app-developers app
Ok buddy here is your issue buddy its all about volts and throttle limits ive been fine tuning oc steps on antutu, cf bench, geekbench2 and geekbench3. Im stable all the way up to 2106 so far I use ktoonzs kernel cuz it has more options in his app the control alot of the throttling and volts. Ok understanding what it means what the phone just shuts off or reboots when the phone shuts off and wont cut back on you either have to do pull the battery out or plug the charger in to get the phone to boot up that means you had a power overload it drawed to much power on the battery which means you neesd to drop volts on your max step. Now if the phone is just rebooting or if the app FC back to the home screen that means that you dont have enough volts for your max step you only have to add or substract volts on that one step not on the whole board the best way to do this is just by finding your volts for that max step first yes scores will be low but once you find the volts then you start adjusting the throttle limits that way you can control the heat of the cpu but once you find the sweet spot of that oc step move to the next one and start over again for the next oc step doing the steps I listed above I will post pics of what I gotten so far. On a further note I have found that the freezer trick hurts you more then gaining anything cuz if you cool the cpu and battery to much it will make the cpu run sluggish cuz its to cold to run and if the battery is to cold it makes the phone think it dont have enough power to run on that oc step and makes the phone reboot so bare in mine the freezer isnt always the best way to do this I found that if the battery is below 28c it will reboot the phone during benching and if the cpu is below 25c it sluggish as hell the best app to use is cool tool on the app store if you use kt kernel I can give you the direct path to monitor cpu temp like his app does hope this helps you understand alil better of whats going on if you need anymore info just pm me
The #1 misfit
of my crew of misfits
As you see in the 4 pic my score close to what the GT-I9500 are getting on antutu
The #1 misfit
of my crew of misfits
Related
What are the best settings to use on the droid 3 for overclocking?
Sent from my DROID3 using Tapatalk
I don't know the best settings, but I set it my SetCPU too low for my "ScreenOff" settings... So sometimes when I tried to turn my screen back on, my phone wouldn't have enough cpu power to turn itself back on... so make sure you don't set governors too low! easy enough fix though when you do.
don't think you can overclock until custom kernals are out.
Heelfan71 said:
don't think you can overclock until custom kernals are out.
Click to expand...
Click to collapse
Correct, but you can still set governors to under-clock and help battery-life.
I set my droid 3 to 800 mhz max, 300 mhz min, but the widget doesnt change, and if i open the app i can watch it jump to 1000 mhz. I have used setCPU on other phones, so I know how to work it.
Does setcpu not work with moto's hotplug governor? I've seen other forums say not to change that
If you set it to 300 and 800 or 600 using "ondemand" it works but the phone gets a little laggy.
Using "motplug" and trying to underclock freezes the device for me.
You can pull the battery to get it working again.
Sent from my rooted Droid 3 (Xda-Premium)
I looks like if you set the governor to anything but mot_hotplug the second core does not get deactivated with the phone is idle. So battery life may actually suffer.
*RETRACTED*
fotoingo said:
If you set it to 300 and 800 or 600 using "ondemand" it works but the phone gets a little laggy.
Using "motplug" and trying to underclock freezes the device for me.
You can pull the battery to get it working again.
Sent from my rooted Droid 3 (Xda-Premium)
Click to expand...
Click to collapse
I experienced this as well, but was using ondemand and 300-600 with screen off. Phone wouldn't turn on at all unless a battery pull was performed, scared me a bit to be honest until i realized what was happening. Decided to stick wit mot_hotplug until we get a custom kernel.
I've always been a big fan of undervolting. These are the lowest voltages I can get stable at these common speeds. I found I can underclock the Matr1x kernel further than some others I have tried for some unknown reason. How low have you been able to go? Also, what programs do you use to test stability? So far, I have been running Antutu test completion as a measure of stability. Any suggestions otherwise?
288MHz - 650mv
1.02Ghz - 800mv
1.51Ghz - 1000mv
ROM: Bionic AOSP V3
Kernel: Matr1x 6.5
Noob question~ Why do people undervolt?
WarToilet said:
Noob question~ Why do people undervolt?
Click to expand...
Click to collapse
To increase battery life,
The Long answer is that the CPU has a number of parameters where Clockspeed (MHz) and voltage (mV) are two. Clockspeed, well that is speed. Voltage is related to the amount of energy provided to the cpu, undervolting means that you feed the CPU less juice but demand that it runs at the same clocks. You are essentially starving the CPU,it uses less energy, but can become unstable if the voltage is insufficient to maintain operations. Manufactures always have extra voltage as a safety margin so power users can check their CPU bin (slow, normal, fast or faster) and lower voltages step by step until they crash the phone during a stress test, increase the voltage slightly and boom, your phone uses less battery power while being just as fast.
I undervolt to reduce heat. It makes a significant difference. The battery saving is minimal, but the temperature difference is VERY noticeable.
estallings15 said:
I undervolt to reduce heat. It makes a significant difference. The battery saving is minimal, but the temperature difference is VERY noticeable.
Click to expand...
Click to collapse
Took words from my mouth. This this and this. It reduces heat, which in turn reduces battery use. UV by itself doesn't save a lot of battery, it's the consequences of it. I'm normally not a fan of UV, but with current N4 sw/fw it NEEDS it. It's way too high.
Interesting observation. As of recently my phone jumps up by 3-5c from 37-38 hover. Never used to do it before, not until i got it up to 50c for about half an hour last week. Previously it would stay steadily at 37-38, now it spikes up now and again during use. What's interesting about is that once it goes over 40c battery use increases drastically. So i wonder if people that have really good battery life don't have phones that go over that temp often and vice versa.
I haven't played around with the values too much yet, just a -100mV across the board. This seems to work just fine, so I might experiment some more..
Using Franco test-r69 at the moment.
Sent from my Nexus 4 using xda premium
I undervolt to prevent heating like others say. My Antutu scores drop like a rock when I'm at stock clockspeeds mostly likely due to thermal throttling. Now I can run it repeatedly without having scores drop. It saves battery and runs faster while running games even for very short periods of time, so I am a big fan of undervolting. :good:
Undervolt to reduce power usage, think of the stock voltage as normally being more than is required, think of running for a bus yet you have 2 minutes why waste energy when you can walk and still make it .
Undervolt for less power usage and less heat produced meaning battery performance is better (cooler battery is a more efficient one) and performance is up as you avoid any thermal limits in place .
Great stuff undervolting, I have managed to get -150mV across the board ( 1.5ghz @ 1000mV) and 288mhz is 162.5mV .
I came from a nexus s ... And one member of xda went to amazing lengths to show that undervolting really made very little differences in battery life ... And it def wasn't worth the instability .
He did loads of tests and I mean loads and basically showed that in helped so little that if you had a reboot you would use more power in rebooting then saving via undervolt
However . it is worth it for the heat decrease for sure
Sent from my Nexus 4 using Tapatalk 2
italia0101 said:
I came from a nexus s ... And one member of xda went to amazing lengths to show that undervolting really made very little differences in battery life ... And it def wasn't worth the instability .
He did loads of tests and I mean loads and basically showed that in helped so little that if you had a reboot you would use more power in rebooting then saving via undervolt
However . it is worth it for the heat decrease for sure
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
The more the heat, the faster the battery drains. Since undervolting decreases heat, im sure it should increase battery life. Maybe not for browsing or calling, but playing a heavy 3D game.
is it normal that the higher the frequency the lower the voltage in setcpu?
screenshot: http://db.tt/k6r8c5oI
I'm quite new to nexus 4 undervolting, what's the average amount i can lower the voltages with? (i have a nominal CPU)
sent from my Nexus 4...
zakoo2 said:
how can you guys undervolt? is there an app for that? i bought Franco's kernel updater app, but there's no option to undervolt in there.
edit: just found an app called setcpu, is that it?
sent from my Nexus 4...
Click to expand...
Click to collapse
You can do it from franco kernel updater, from frequencies and voltages - voltages - cpu voltages
But i dont recommend you to undervolt if you dont know what you do.
Sent from my Nexus 4 using Tapatalk 2
aimcr7 said:
You can do it from franco kernel updater, from frequencies and voltages - voltages - cpu voltages
But i dont recommend you to undervolt if you dont know what you do.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I'm familiar with undervolting both on PC and on phone, but i had a Motorola defy before my nexus and undervolting there was a bit different.
sent from my Nexus 4...
zakoo2 said:
is it normal that the higher the frequency the lower the voltage in setcpu?
screenshot: http://db.tt/k6r8c5oI
I'm quite new to nexus 4 undervolting, what's the average amount i can lower the voltages with? (i have a nominal CPU)
sent from my Nexus 4...
Click to expand...
Click to collapse
How are you able to undervolt with SetCPU? I'm not seeing that option using CM10, and Harsh's kernel.
italia0101 said:
I came from a nexus s ... And one member of xda went to amazing lengths to show that undervolting really made very little differences in battery life ... And it def wasn't worth the instability .
He did loads of tests and I mean loads and basically showed that in helped so little that if you had a reboot you would use more power in rebooting then saving via undervolt
However . it is worth it for the heat decrease for sure
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Former nexus s user here, the reason nexus s didn't benefit in battery life much was that it only had 1 core, and used a higher nm manufacturing process, 65nm -> 28nm. Lower voltages in the 28nm means that it multiplies the heat/power savings more than a 65nm, and the 4 cores multiply the savings by up to 4.
FatalityBoyZahy said:
How are you able to undervolt with SetCPU? I'm not seeing that option using CM10, and Harsh's kernel.
Click to expand...
Click to collapse
don't know, it was just there. did you try to reboot after installing the app?
I'm on Franco's kernel btw.
sent from my Nexus 4...
Pls what are the right values for under volting Samsung captivate
Sent from my SGH-I897 using xda premium
I am new to this and my battery goes +40°C when I play simple games... I am running Franco's kernel r71 should I do UV? If so how much? Thanks in advance
Sent from my Nexus 4 using xda app-developers app
xtremer92 said:
Pls what are the right values for under volting Samsung captivate
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
this is the lg nexus 4 forum.
sent from my Nexus 4...
So when I first got the phone on Monday I noticed it would get a little warm. Everything seemed to run fine though.
My battery temperature has been hovering around 92 degrees f.
I ran an antutu benchmark and got a 28k. Ran it again right after and got a 22k.
I thought my phone must be throttling to reduce heat.
Here I shut off the phone for 20 minutes then turned it back on. Battery temp read 78 f. Ran antutu again and got a 34k.
So if I score 5 higher after letting the phone cool that means my phone is always throttling itself
Note: before all tests I ensured battery saver was off and I cleared the ram.
Anyone else have this issue?
Should I return it?
There is another thread I started about the same issue. Apparently it is happening to a lot of people.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
If you root and DL trickster mod you can turn off frequency lock which is more than likely causing all the heat. Benchmark scores actually go up with it disabled cause its causing less heat when the frequency lock is disabled. You can also control MP-decision (which it says to turn off unless your kernel has enabled alternative which I doubt the stock kernel has?) and read ahead buffer size can be controlled also, I seem to have the best scores with a 512 read ahead buffer size. just my 2 Cent
I used the benchmark score just as an example of performance degrading. My goal is not to have the highest score but to use it to create a baseline for performance.
I'm just trying to judge if any slow downs or stutters on my phone are a result of overheating and throttling on the cpu and if everyone else has the same throttling issue.
Thermal throttling. Present on all S600-S800 chips. It's a safeguard implemented by qualcom.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Although this might seem as a question. It really isnt.
What kind of battery life do you get on the First? Screenshots would be nice, but what is like the max time and min time you got and what kind of setting do you use, voltage, clock speed, usage etc.
Also has anyone been using the MSM-DCVS (dynamic clock and voltage scaling) CPU Governer? And if yes then have you gotten better battery life? I will do a test tomorrow and see how it goes.
My best stats.
Well before i got into cpu governors, by default the phone uses on-demand and i could max out 14 hours with variable usage. screen on maybe 50% of the time the phone was on and minimal gaming. texting. I dont have data so that didnt take any battery (i hear 4g and 3g take away lots of juice, is that true?).
Okay. So just did a quick test with msm-dcvs.
Basically for 5 minutes I tested each governed doing the same stuff.
Msm-dcvs utilizes deep sleep ALOT more. Almost 8 times more than on demand. And doesn't really use anything in between. So it goes from deep sleep to minimum 300mhz to get it going and then jumps to the max of 1.4ghz and if the screen is on it uses 700mhz.
So using deep sleep it saves batter.
On demand on the other hand tends to use 300mhz instead of deep sleep. It also jumps around a lot between all the various clock speeds using just about anything it can. So i guess on demand will get worse battery life but I will report my findings in a few hours seeing bow battery life goes with dcvs.
Sent from my HTC first using XDA Premium 4 mobile app
Just a quick update. On demand is crap. Performance is really good and dcvs is performance just more intelligent
Sent from my HTC first using XDA Premium 4 mobile app
My battery life is crap. I've tried to adjust clock speed & voltage but I don't believe JMZ's latest kernel supports it and I'm never able to get any governors besides stock to stick
abrahammmmmmm_ said:
My battery life is crap. I've tried to adjust clock speed & voltage but I don't believe JMZ's latest kernel supports it and I'm never able to get any governors besides stock to stick
Click to expand...
Click to collapse
Use performance. It has a really fast "rave-to-idle" speed. This means that the phone will finish tasks faster and go to idle/deep sleep. So it should save you batter. Unless you don't mind lag and use msm-dcvs which is performance just it takes time to ramp up the speed.
Sent from my HTC first using XDA Premium 4 mobile app
russian392 said:
Use performance. It has a really fast "rave-to-idle" speed. This means that the phone will finish tasks faster and go to idle/deep sleep. So it should save you batter. Unless you don't mind lag and use msm-dcvs which is performance just it takes time to ramp up the speed.
Sent from my HTC first using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What app do you use for this? All the ones I've tried don't make any custom settings stick
abrahammmmmmm_ said:
What app do you use for this? All the ones I've tried don't make any custom settings stick
Click to expand...
Click to collapse
CPU master by antutu. I've always used it. Best one there is
Sent from my HTC first using XDA Premium 4 mobile app
russian392 said:
CPU master by antutu. I've always used it. Best one there is
Sent from my HTC first using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Alright I'll try the app. BTW I'm pretty sure 918mhz isn't the stock minimum... Must explain my horrible battery. What do you have yours on?
Edit: so far so good. I'm feeling some better battery life even tho it might just be a placebo effect I know that the CPU will have less strain & rest more now that the minimum is at 384. And few more questions, what do you have set for your I/O scheduler and also did you configure the voltage?
It's important for battery life, that the phone goes into deep sleep while screen is off. Use this app to test whether thats the case: BetterBatteryStats
Also you can see which process "wakes up" the phone while it should sleep.
My First normaly runs about 2 days without charging. So battery is pretty good!
PS: I'm using deodexed rom with stock kernel.
G00fY2 said:
It's important for battery life, that the phone goes into deep sleep while screen is off. Use this app to test whether thats the case: BetterBatteryStats
Also you can see which process "wakes up" the phone while it should sleep.
My First normaly runs about 2 days without charging. So battery is pretty good!
PS: I'm using deodexed rom with stock kernel.
Click to expand...
Click to collapse
Wow that's great battery life.
I'm yet to test dcvs in my first and see how long that lasts me. I have Wi-Fi on all day. So I can get up to 14 hours max.
Sent from my HTC first using XDA Premium 4 mobile app
abrahammmmmmm_ said:
Alright I'll try the app. BTW I'm pretty sure 918mhz isn't the stock minimum... Must explain my horrible battery. What do you have yours on?
Edit: so far so good. I'm feeling some better battery life even tho it might just be a placebo effect I know that the CPU will have less strain & rest more now that the minimum is at 384. And few more questions, what do you have set for your I/O scheduler and also did you configure the voltage?
Click to expand...
Click to collapse
No I have yet to figure out io bit tinkering with voltage isn't a good idea since the battery is specifically set to a voltage the phone needs.
Sent from my HTC first using XDA Premium 4 mobile app
Okay I have some new findings. Idk about the custom kernel...bit with stock you only get 3 I/o schedulers. Noop, deadline, and cfq. Noop is first come first serve. Deadline reorders the task sequence and does what it thinks should come first...good for like gaming. And cfq. Which evenly distributes the power amongst all tasks. If you are using cfq make sure you kill unused tasks all the time. If you use a lot of things on your phone and multitask a lot use deadline. Noop is pointless unless you don't use your phone for anything. And cfq is just an alternative to deadline. So I/o won help much.
Then in CPU master. Go to advanced. And press "disable perflock". It will explain what it does. Hit set on boot. And reset you clock settings. Now we shall see what we get.
Sent from my HTC first using XDA Premium 4 mobile app
Okay guys. I used deadline to see if that would change anything. With the same dcvs setting with deadline I got 15% batter down in 2 hours. That's pretty good. That's 7.5% an hour.
And this is with screen on and wifi on about 70% of the time.
Sent from my HTC first using XDA Premium 4 mobile app
Okay this is my final say on how to get the most out of your battery life.
There are two set ups
1. Lag free/ smooth set up
Min 384mhz, Max 1080mhz
Governer: Performance
i/o Scheduler: Deadline
-This set up will save battery why? Because 1. You don not need your max 1.4 ghz to keep the phone running lag free, and in performance mode, the phone is LOCKED into 1.4ghz until you dim the screen and it goes into deep sleep. no inbetween. So clocking down will help save EVEN MORE battery. So unlike dcvs you will not have lag when you turn your screen on. It will jump from zero to 1ghz in a few milliseconds.
2. Inteligent
Min: 432mhz, Max 1.4ghz (default max. Dont over clock)
Governer: MSM-DCVS
i/o Scheduler: CFQ
-This set up will save battery, i go down about 1% every 6-20 minutes depending on usage. (6 being max usage and 20 meaning iddle). Once you turn the screen on your device will lag slightly and then will work just fine. This set up is good for those people who dont ALWAYS need max performance. Example: Reading an email doesnt require your phone to be locked at max frequency all the time so it will down clock the device. It simply takes time for it to rev the engine.
3. On Demand
Well this is simply absoule minimum to absolute maximum with NOOP as the i/o. This is the ultimate ondemand set up as it will do what you are currently doing first then do the rest while constantly changing clock speed.
Also...btw changing clock speed takes battery that is why performance saves batter not uses it. Its either deep sleep or max and thats it.
I will add screenshots to this soon once im done with all my tests.
Battery life today on msm-dcvs
I should be at 30% right now bit pretty good battery tight now
Sent from my HTC first using XDA Premium 4 mobile app
Tried today MSM-DCVS scheduler on my stock rooted firmware. Don't like it. Lags a lot when screen on (and CPU at max 1.4Ghz). And i do not see any significant battery improvements, instead it seems that it takes longer time for phone to do background tasks like mail checking etc.
Concerning battery life - in general I receive 3-3.5 hours of screen time. And it can be 1 day to 3. It all depends on usage, but screen on time never goes above 4 hours.
In attached file - Stats for my phone while traveling from the U.S. to Russia. As you can see, delivery does not take very much time And in standby mode phone can last almost two weeks (with wi-fi and nfc on).
Hulo_ said:
Tried today MSM-DCVS scheduler on my stock rooted firmware. Don't like it. Lags a lot when screen on (and CPU at max 1.4Ghz). And i do not see any significant battery improvements, instead it seems that it takes longer time for phone to do background tasks like mail checking etc.
Concerning battery life - in general I receive 3-3.5 hours of screen time. And it can be 1 day to 3. It all depends on usage, but screen on time never goes above 4 hours.
In attached file - Stats for my phone while traveling from the U.S. to Russia. As you can see, delivery does not take very much time And in standby mode phone can last almost two weeks (with wi-fi and nfc on).
Click to expand...
Click to collapse
Personaly i dont have NFC or 4g on at any time. 1. i dont have data and 2. i dont use nfc cause the so called "modern world" is still stuc on stupid apple devices.
I noticed the following issues with managing the cpu
1. When setting cpu clock speed, after about 5 seconds after you left the app it changes the clock speed back to how it was
FIX: in cpu master (or the app of your choice) go to advanced and turn perflock off. then go to the cpu settings and set the speed you want. you must do that every time though cause of the htc kernel
2. MSM-DCVS lags.
FIX: set your minimum to 450-500 mhz
3. 4g drains batter (or so i hear)
FIX: idk yet but if someone could show me their battery life with 4g on and normal daily usage i could try to figure something out.
Hulo. Try this set up
Performance, 300mhz - 1080mhz, deadline
IDK my phone syncs things quite well and lag isnt a big issue for me, i can deal with it because my old phone overclocked is 700mhz so lag isnt anything new to me. So i just notch up the minimum to reduce it.
MSM-DCVS saves batter when screen is off and when screen is on but idle. playing games or actively using the screen will drain battery no matter what setting you use. This is made for people who are constantly on their phones.
Performance saves battery when screen is OFF period. When screen is on its at its max. this is best used for people who dont use their phones alot.
With dcvs i got an extra 7 hours of battery life. usually i get 11. But i hear with 4g on your battery dies in about 6 hours? is that true?!
russian392 said:
Personaly i dont have NFC or 4g on at any time. 1. i dont have data and 2. i dont use nfc cause the so called "modern world" is still stuc on stupid apple devices.
I noticed the following issues with managing the cpu
1. When setting cpu clock speed, after about 5 seconds after you left the app it changes the clock speed back to how it was
FIX: in cpu master (or the app of your choice) go to advanced and turn perflock off. then go to the cpu settings and set the speed you want. you must do that every time though cause of the htc kernel
2. MSM-DCVS lags.
FIX: set your minimum to 450-500 mhz
3. 4g drains batter (or so i hear)
FIX: idk yet but if someone could show me their battery life with 4g on and normal daily usage i could try to figure something out.
Hulo. Try this set up
Performance, 300mhz - 1080mhz, deadline
IDK my phone syncs things quite well and lag isnt a big issue for me, i can deal with it because my old phone overclocked is 700mhz so lag isnt anything new to me. So i just notch up the minimum to reduce it.
MSM-DCVS saves batter when screen is off and when screen is on but idle. playing games or actively using the screen will drain battery no matter what setting you use. This is made for people who are constantly on their phones.
Performance saves battery when screen is OFF period. When screen is on its at its max. this is best used for people who dont use their phones alot.
With dcvs i got an extra 7 hours of battery life. usually i get 11. But i hear with 4g on your battery dies in about 6 hours? is that true?!
Click to expand...
Click to collapse
I'd just like to add that 4g actually consumes LESS battery than 2g/3g/3.5g only LTE tho. That's because it's more optimized and advanced I've read and experienced it in many occasions
abrahammmmmmm_ said:
I'd just like to add that 4g actually consumes LESS battery than 2g/3g/3.5g only LTE tho. That's because it's more optimized and advanced I've read and experienced it in many occasions
Click to expand...
Click to collapse
Alright then. Interesting. My friend on his s3 gets 6 hours of battery with 4g.
Sent from my HTC first using XDA Premium 4 mobile app
russian392 said:
Alright then. Interesting. My friend on his s3 gets 6 hours of battery with 4g.
Sent from my HTC first using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I should add that the optimized battery life for LTE is only true tho for new snapdragon CPU's including Apple's processors as well. I'm not aware of tegra or any exynos at the moment.
So, I overclocked my CPU frequency to 1836MHz and my GPU frequency to 450MHz and after playing a game for like 10mins, my phone gets really hot. I know its normal but I would like to ask, did I overclocked my phone too much that it can destroy my phone? And what is the overheat temperature for my phone(HTC One)? So I can monitor it.
Thank you
Sent from my HTC One using XDA Premium 4 mobile app
qwertyuiop404 said:
So, I overclocked my CPU frequency to 1836MHz and my GPU frequency to 450MHz and after playing a game for like 10mins, my phone gets really hot. I know its normal but I would like to ask, did I overclocked my phone too much that it can destroy my phone? And what is the overheat temperature for my phone(HTC One)? So I can monitor it.
Thank you
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes its possible to permanently damage your phone if your overclock is too much aggressive or your phone get to hot. Every chip is slightly different so you'll have to test your phone for each frequency steps you do. Like a computer, you should start overclocking in small increments till you reach a maximum stable config and then reduce it a bit for safety. And always monitor temperature, over-temping is your worst enemy when overclocking.
For the max temp question I don't really know, you might want to check qualcomm site for max safe cpu temps. Don't forget some other components doesn't like high temperature. Semi-conductors components life are reduced in high temp conditions and generally, lithium-ion battery doesn't like high temperatures...
alray said:
Yes its possible to permanently damage your phone if your overclock is too much aggressive or your phone get to hot. Every chip is slightly different so you'll have to test your phone for each frequency steps you do. Like a computer, you should start overclocking in small increments till you reach a maximum stable config and then reduce it a bit for safety. And always monitor temperature, over-temping is your worst enemy when overclocking.
For the max temp question I don't really know, you might want to check qualcomm site for max safe cpu temps. Don't forget some other components doesn't like high temperature. Semi-conductors components life are reduced in high temp conditions and generally, lithium-ion battery doesn't like high temperatures...
Click to expand...
Click to collapse
So basically, overclocking can really destroy my phone? So, i guess ill just switch back to the stock one. Thank you
Sent from my HTC One using XDA Premium 4 mobile app
qwertyuiop404 said:
So basically, overclocking can really destroy my phone? So, i guess ill just switch back to the stock one. Thank you
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That overclock is not going to hurt your phone but the temperature can if it gets too high which can happen at stock clocking. I keep my phone's cpu at 1.134 Ghz and games run great with minimal heat.
Sent from my HTC One using xda app-developers app
Found the information about the temp here