Performance limited by heat - G2 General

We have smashed into the performance ceiling. Without active cooling or massive increases in efficiency through improved architecture, there is no way smartphones (or tablets) can become more powerful.
I can't use 75% of this phone's potential performance while playing San Andreas. With a custom kernel and thermal throttling disabled, the phone shoots up to 90c in minutes and then reboots; that is with 'On Demand' and max frequency at 1.73 ghz.
Coming from a gnex (max stock freq. could reach 80c), absolute performance has become meaningless. Maybe it has been for a while.

This is absolutely true. We need fans or cooling systems if we shall be able to take full advantage of the massive powers in our phones. For now, I think the only way is to play our favorite games in a freezer.
Sent from my LG-D802 using xda app-developers app

otherwise lg would melt ...

or, you can root your phone and disable thermal throttle. then you can use it at full performance up until you reach the thermal shutdown temp without worrying your cpu being thermally throttled
and i had a gnex as well, it could reach 110C. i always turned off thermal throttle, and always turn off thermal throttle on my nexus 5. you dont reach thermal shutdown without actively trying too, and the cpu doesn't get throttled.

crazysoccerman said:
We have smashed into the performance ceiling.
Click to expand...
Click to collapse
While that statement was not even close to being true when you posted it, tomorrow it'll be less true, etc etc.
If you build the exact same chip with a smaller die process, the smaller die process chip will be more efficient (cooler) and faster. Then there are of course other improvements that are continuously being made, more cores to spread the load, faster ram to reduce bottlenecks, etc, etc, again, all while getting faster and cooler because of improved production methods.
So no, phones will get more powerful, more ram, better screens etc.. Maybe someday we'll have another battery breakthrough, but right now with the massive push on efficiency we're getting some runtime back on batteries, etc.

khaytsus said:
While that statement was not even close to being true when you posted it.
Click to expand...
Click to collapse
Actually it is true. The performance on the G2 is limited by heat. You can't run the phone under load at or near its max specified frequency for any reasonable period of time. Try it yourself. To deny that is to deny facts.
Also, a smaller die reduces the surface area for the dissipation of heat.

crazysoccerman said:
Actually it is true. The performance on the G2 is limited by heat. You can't run the phone under load at or near its max specified frequency for any reasonable period of time. Try it yourself. To deny that is to deny facts.
Also, a smaller die reduces the surface area for the dissipation of heat.
Click to expand...
Click to collapse
Read the OP, it states "smartphones". Oh wait, you are the OP

vPro97 said:
This is absolutely true. We need fans or cooling systems if we shall be able to take full advantage of the massive powers in our phones. For now, I think the only way is to play our favorite games in a freezer.
Sent from my LG-D802 using xda app-developers app
Click to expand...
Click to collapse
Lol fans aren't a good solution
Sent from my VS980 4G using Tapatalk

Time ago a saw a cooling case. If i find the site again, i will post it.

Imagine the HTC One, but with a heat pipe transferring heat from the SOC to the aluminum case... That would provide more cooling, but I'm not sure of the size penalty of the heat pipe.
Also, more efficient chips CAN provide more power and generate less heat. A perfect example is Intel's pentium4 "netburst" architecture vs the newer and considerably more efficient "core duo" chips.
Take care
Gary
Sent from my Nexus 7 using Tapatalk

are there any phones out there that don't heat up while performing great in all demanding titles?
Sent from my LG-D801 using xda app-developers app

well yeah smartphones aren't designed to run at 100% of the cpu/gpu speed for long periods of time. If they were, they would have to be a lot bigger and/or have active cooling. I guess I never really noticed the "wall" because all the mobile games I play do not push the phone to the limit. When you are comparing it to the past though, remember the newest CPUs are significantly faster clock for clock. 1.5ghz is not the same for an A9 vs Krait 400.

So what iz the solution ? Do we have any modification or init.d script to disable that cooling system ?

Solution Is a thermal pad on CPU

Mantra96 said:
Solution Is a thermal pad on CPU
Click to expand...
Click to collapse
:V ...
---------- Post added at 10:41 AM ---------- Previous post was at 10:40 AM ----------
Vipxpert said:
:V ...
Click to expand...
Click to collapse
It's time to void warranty ! :V

Related

Stock kernal

Well I downloaded cpu master (free) to just mess around with my photon, and come to find out, the governor for the cpu is set to performance, but gave me the option to change it to powersave, so I switch it and I'll report back to you guys and see if I've found the holy Grail to even better battery life
Sent from my MoPho using XDA App
That's awesome
Sent from my MB855 using xda premium
Wait until I or another dev gets onDemand governor enabled...
I have SetCPU, and honestly, I haven't noticed a huge difference in battery life with powersave unless I seriously scale the CPU back to like 300 mhz. Then it'll last a while, if I don't do ANYTHING with it. For example, when I'm sleeping, otherwise, it just makes the phone laggy and doesn't seem to help enough to make it worth while. Just my opinion from screwing with it.
xTMFxOffshore said:
I have SetCPU, and honestly, I haven't noticed a huge difference in battery life with powersave unless I seriously scale the CPU back to like 300 mhz. Then it'll last a while, if I don't do ANYTHING with it. For example, when I'm sleeping, otherwise, it just makes the phone laggy and doesn't seem to help enough to make it worth while. Just my opinion from screwing with it.
Click to expand...
Click to collapse
The general consensus regarding over/underclocking when I had my HTC Hero was that overclocking would save battery because you could get what you wanted done faster. If you scale the CPU back massively while it is set to sleep, however, you will save a lot of battery.
xTMFxOffshore said:
I have SetCPU, and honestly, I haven't noticed a huge difference in battery life with powersave unless I seriously scale the CPU back to like 300 mhz. Then it'll last a while, if I don't do ANYTHING with it. For example, when I'm sleeping, otherwise, it just makes the phone laggy and doesn't seem to help enough to make it worth while. Just my opinion from screwing with it.
Click to expand...
Click to collapse
well, i don't know about your phone or what else you have setup, but my phone didn't lag and it seemed to help, i currently have my evo 3d active so my photon just sits there, so i can give a good feedback of idle time, but i can tell you after switching the governor, it went down 1% in 2 hours, now i say that's an improvement, so when i get back home i'll really give you guys some feedback
P.S. with any phone i had that had a fully custom kernal, i always used conservative governor
Well, perhaps it's just the apps I have running then. As I said, when it's set to sleep, it works pretty well with the powersave mode, otherwise, doesn't seem to make any real difference. Guess it's different for everyone cause of the **** they're running on their phone.
mrinehart93 said:
The general consensus regarding over/underclocking when I had my HTC Hero was that overclocking would save battery because you could get what you wanted done faster.
Click to expand...
Click to collapse
You know, I've never bought into this argument. To me, it is like saying that if I drive 100 mph I will get there faster, so I use less gas....which we all know is not how it works.
Maybe the physics are different for processors then they are for engines, but I think there is probably a happy medium somewhere. And I have a feeling that the manufactures really take this into consideration when they develop the kernels and ROMs. However, I might be wrong.
This is by no means an effort to discourage your awesome work. Everyone gets different results, but stock always seems to have the best battery life for me once all the bloat is gone. However, custom kernels do perform better. That is the trade off, in my opinion.
my2cents said:
You know, I've never bought into this argument. To me, it is like saying that if I drive 100 mph I will get there faster, so I use less gas....which we all know is not how it works.
Maybe the physics are different for processors then they are for engines, but I think there is probably a happy medium somewhere. And I have a feeling that the manufactures really take this into consideration when they develop the kernels and ROMs. However, I might be wrong.
This is by no means an effort to discourage your awesome work. Everyone gets different results, but stock always seems to have the best battery life for me once all the bloat is gone. However, custom kernels do perform better. That is the trade off, in my opinion.
Click to expand...
Click to collapse
Lol honestly I never bought into it either. I was just posting was the other devs at the time said. Even using an OC kernel, I never overclocked my phone.
mrinehart93 said:
Lol honestly I never bought into it either. I was just posting was the other devs at the time said. Even using an OC kernel, I never overclocked my phone.
Click to expand...
Click to collapse
Interesting...I hadn't thought about using an OC kernel and underclocking it back to stock. I wonder what that does, if anything, to performance.
The other concern that I have is that overclocking typically means more heat, which means more battery use... Just figured I would throw that out there too.
well, the results are in, now granted i already had the photon of the charge for more then 24 hours, so at 1d 15hr 57m and 10s i'm at 48%, but from the time i started the cpu test, 1:30pm, it was at 68% so in 8 horus there was only a 20% drop while idle, i say that's a good score , you guys tell me otherwise
A2CKilla said:
well, the results are in, now granted i already had the photon of the charge for more then 24 hours, so at 1d 15hr 57m and 10s i'm at 48%, but from the time i started the cpu test, 1:30pm, it was at 68% so in 8 horus there was only a 20% drop while idle, i say that's a good score , you guys tell me otherwise
Click to expand...
Click to collapse
and just an update, in another 4 hours, it's only gone down 2%!!!!!! come on guys, these numbers can't lie, but remember this is idle feedback, i'll re-activate my photon at the end of the week (missing the beast!) to give more detail feedback on heavy usage and most importantly 4g!!
Development. Development. Development.
Sent from my MB855 using xda premium
Not sure if this will help but let me explain the car analogy. All motors have an effeciency range at x amount of throttle. So same cars will get better gas mileage at a higher speed vs a lower one. Its getting up to that speed where most energy is used.
So let me move this over to electronics. If you run a faster clock speed while on, your apps will open faster so that ia less on time for the screen and other processes that have to run. So using more watts for less time does not always equal more than using less watts for more time. We just need to fill in those blanks and obviously overclocking will not benefit the nook or internet reader as it eould someone who opens a lot of apps for short periods. Same is true for a gamer .
Hope that makes sense and this is all IMHO of course.
Sent from my MB855 using XDA App
scoobdude said:
Not sure if this will help but let me explain the car analogy. All motors have an effeciency range at x amount of throttle. So same cars will get better gas mileage at a higher speed vs a lower one. Its getting up to that speed where most energy is used.
So let me move this over to electronics. If you run a faster clock speed while on, your apps will open faster so that ia less on time for the screen and other processes that have to run. So using more watts for less time does not always equal more than using less watts for more time. We just need to fill in those blanks and obviously overclocking will not benefit the nook or internet reader as it eould someone who opens a lot of apps for short periods. Same is true for a gamer .
Hope that makes sense and this is all IMHO of course.
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
Let me start this off by saying that I am an agricultural engineer by trade. With that said, I would agree that engines have an efficiency range. However, I would not agree that it is at x throttle. Rather, it is a x load. And most cars are designed to be at optimal load at about 60 mph (wind resist, weight, etc. play a role in this). You're right, it does require more fuel to get to that speed because the load is higher until that speed is reached. Furthermore, higher speeds (greater than 60 mph) do NOT translate into higher fuel mileages because the load increases to maintain the higher speed (because there is more wind resistance, among other things).
I know a bit about electricity too, but I don't fully understand the physics behind circuit boards. However, I think the analogy still holds. I can get to 60 mph as fast as I want, but the faster I do it the more energy is required. Therefore, even though it is done faster it still requires more energy, which also creates more heat, both of which use the battery. So, I continue to contend that there is a happy medium that most be found and I think electronic engineers aren't to far off.
Here is a little more reading about car efficiency, if you are interested: http://www.mpgforspeed.com/
I believe your confusing overclocking and overvolting. We are putting x volts into the processor so the more cycles we can get in x volts the better. If we have to overvolt to overclock then we see big battery hits.
Sent from my MB855 using Tapatalk
2cents, that link is interesting but real world examples have proven otherwise to me. Our saab will do better on mpg at 70 to 75 (30 on cruise control) vs 55 to 65(27 to 28 on cruise). Now the wrx is another story as well. With the old 3.9 final drive i would pull in more air at the airflow meter at 65 than i would at 70 with stoich as the target a/f ratio, and because that motor was doing under 2500 rpms the turbo was out of the equation further taking out efficiency with it. Now with the 4.44 and a better 1-2 gear ratio car gets better at the lower engine speeds and accelerates even better and that was before i retuned it.
Another misconception is bigger motors use more gas, one of the recent corvettes get 30 on the highway proving that there is more to this as well.
I think i have taken this off topic enoigh for now. But in general i think my formula still needs to be applied to see the results as a valid number to compare overclocking and underclocking to running stock.
Sent from my MB855 using XDA App
i'm surprised no one even thought of this topic, regardless if things are getting done "faster" you are overclocking the cpu, making it go faster then what it's suppose to, which makes it use more power i.e. more battery, every phone that i had when i overclocked it, the battery wouldn't last too long, even with my 3500mah OG evo, if i overclocked it, i couldn't get a whole day, so underclocking will have the same effect in a sense since the processor now has to work harder to do what it does at it's stock clocked speed, well, hope anything i said here makes any logical sense, but on another note, the photon has gone almost 3 days unplugged!!!
again it depends on how the overclock is achieved. In most cases overclock is achieved by dumping more electricity into the cpu this will impact battery life, however alot of chips these days can be overclocked at the same volts essentially upping the "MPG" or clocks per volt.
A2CKilla said:
i'm surprised no one even thought of this topic, regardless if things are getting done "faster" you are overclocking the cpu, making it go faster then what it's suppose to, which makes it use more power i.e. more battery, every phone that i had when i overclocked it, the battery wouldn't last too long, even with my 3500mah OG evo, if i overclocked it, i couldn't get a whole day, so underclocking will have the same effect in a sense since the processor now has to work harder to do what it does at it's stock clocked speed, well, hope anything i said here makes any logical sense, but on another note, the photon has gone almost 3 days unplugged!!!
Click to expand...
Click to collapse
I agree with this for the most part. When it comes to power the end result is watts, which is essentially equal to volts x amps. It is not perfect because of a power factor, but it is close. Therefore, if you lower the voltage, the amperage goes up because the same watts are required to run the processor. The inverse is also true. These processors have voltage ranges that they will safely run in, but in the end, they require the same energy (in watts) to function at a given load. Change one a little bit (the voltage for example) and the other (amperage) compensates. Change it a lot and it likely wont work. Again, this is how it works for your typical home appliances. For a circuit board, it might be a slightly different story, but I imagine the science does not change.
---------- Post added at 03:57 PM ---------- Previous post was at 03:47 PM ----------
scoobdude said:
2cents, that link is interesting but real world examples have proven otherwise to me. Our saab will do better on mpg at 70 to 75 (30 on cruise control) vs 55 to 65(27 to 28 on cruise). Now the wrx is another story as well. With the old 3.9 final drive i would pull in more air at the airflow meter at 65 than i would at 70 with stoich as the target a/f ratio, and because that motor was doing under 2500 rpms the turbo was out of the equation further taking out efficiency with it. Now with the 4.44 and a better 1-2 gear ratio car gets better at the lower engine speeds and accelerates even better and that was before i retuned it.
Another misconception is bigger motors use more gas, one of the recent corvettes get 30 on the highway proving that there is more to this as well.
I think i have taken this off topic enoigh for now. But in general i think my formula still needs to be applied to see the results as a valid number to compare overclocking and underclocking to running stock.
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
You may be right. Perhaps Saab designed their fuel efficiency at 70 mph. It's possible because many speed limits are now at or near that, but in general, optimal fuel consumption is going to be at or near 60 mph. Obviously gear ratios and such play a huge role in fuel economy. It is like using a custom rom, typically your mods will make it perform better, but the best fuel economy or battery life will come with a stock like setup.
Sure a corvette can have HP and economy. There is a power to weight ratio and lots of aerodynamics involved, which again is designed at a specific speed. But there is no way that a dragster will have a good fuel efficiency. To my point, there is a balance...
I agree, we are off topic a little bit, but the conversation is interesting, nonetheless.
By the way, can a mod move this to general, please?

Safeness of 1600mhz

Has it ever been heard of that someone killed their gs2 from using 1600mhz in daily use?
My gs2 likes to have 1475 as a minimum voltage for 1600.
sent from I9100 using Omega
Ever rev an engine into the red? Did the engine blow up on the spot? unlikely. However if you constantly KEEP the engine in the red it will eventually break down.
Same thing for OC phones. The processor in the SGS was designed for somewhere around the 1ghz mark. Pushing it 110% likely wont kill it, they build allowances and tolerances into these things to help them last longer. Push that processor to 150% and you are risking serious damage.
Monitor the heat, if you notice its getting HOT then you should really pull the battery and let it sit for a while. Nobody here can say its safe to OC your phone like that, its a calculated risk you obviously didnt spend a lot of thought into.
TLDR: Just because you CAN doesn't mean you SHOULD.
Actually its my thought the reason I haven't been using it on 1.6 yet, and why I'm asking. Iv been ocing my pcs since the late 90s
Now the reason I'm asking here is because the cortex a9 was designed for up to 2gHz operation, but this phones design may or may not provide adequate cooling, that's why I'm asking if other people have any negative experiences with this.
Were not actually over reving the chip its more of a environment issue with cooling/ventilation.
sent from I9100 using Omega
Visentinel said:
Actually its my thought the reason I haven't been using it on 1.6 yet, and why I'm asking. Iv been ocing my pcs since the late 90s
Now the reason I'm asking here is because the cortex a9 was designed for up to 2gHz operation, but this phones design may or may not provide adequate cooling, that's why I'm asking if other people have any negative experiences with this.
Were not actually over reving the chip its more of a environment issue with cooling/ventilation.
sent from I9100 using Omega
Click to expand...
Click to collapse
You do have to have in mind that PCs are much safer to OC, so we shouldn't really compare brtween them.
Regarding the Phone OC, I haven't OC'd mine and probably never will because I have all the horsepower I need, but I think the "safest" OC is between 1.3 and 1.4GHz, since that's a range that all CPUs are designed to overtake (max 200MHz range ).
mine's been oc'ed, uv'ed pretty much within the week I bought the phone in june.
I've got it set to clock between 500-1600Mhz on demand and I've not had a problem yet. Mind you, not many tasks you do on the phone will actually require 1600Mhz and my phone's CPU clocks mostly between 500-800Mhz.
Playing some games or doing quick video conversion will push to 1600Mhz but I rarely play games on my phone and video conversion is short process - burst of 90 seconds to 120 seconds at most. So I think you should be alright so long as you don't leave your phone CPU at 1600Mhz at all times.
Like you said, it is the cooling and ventilation system on the phone, which you can't modify.. Unlike PCs, where you can install bigger fans or water cooling systems. So if the phone isn't constantly cooking itself inside, should be alright.
You should already know that OCing anything is dangerous since you overclock PCs,so I'll skip that part.
Well,if it's dangerous for the phone...It depends.Yes,the processor will die sooner.Yes,you risk frying your device.No,you don't have to push it to the limit(don't push it more that 1450μV,that's the general advice for 45nm chips).However,my thoughts are:
-I won't still have the device when it's time for its CPU to get fried,so I don't actually care.
-Something else,probably the Amoled screen,will make the phone useless by breaking sooner than the CPU will.
-This winter here is really cold(for our standards anyway),so heating has been taken care of.During hotter weather,I kept multiple temperature profiles in SetCPU,so that frequencies get lower as temperatures get higher.
In the end,what matters most to me is to have the experience I want.And with OCing my phone I get it.I'm happy with it,that's all I wanted.So,it's personal preference.Some feel they don't need it,others feel they do.Decide for yourself,that's the best advice.
PS:In case you are using Siyah kernel or CF-Root with Tegrak overclock,try lowering your clock by small steps(8Mhz is the smallest step) for a sane voltage,say 1400μV.Sometimes small increments make big differences.
Thanks for the advice guys. Appreciated.
sent from I9100 using Omega
Don´t oc sgs2.
I got my mobo fried without oc.
Service center replaced everything else but housing and screen.
I used it 2-3 hours in a row, installed programs and put it in charger.
In the morning, it was completely dead.
Overheated because of the use and charging.
So think about twice before using oc 24/7.
Buffalee said:
Don´t oc sgs2.
I got my mobo fried without oc.
Service center replaced everything else but housing and screen.
I used it 2-3 hours in a row, installed programs and put it in charger.
In the morning, it was completely dead.
Overheated because of the use and charging.
So think about twice before using oc 24/7.
Click to expand...
Click to collapse
how can you tell, that its dead because of the use and charging, if you didn't even OC'ed?
Buffalee said:
Don´t oc sgs2.
I got my mobo fried without oc.
Service center replaced everything else but housing and screen.
I used it 2-3 hours in a row, installed programs and put it in charger.
In the morning, it was completely dead.
Overheated because of the use and charging.
So think about twice before using oc 24/7.
Click to expand...
Click to collapse
I bet you didn't know there are faulty products out there that show their faults during intensive usage,eh?Mine's running at 1.6GHz(give or take a few MHz ) for months.I've played games while charging countless times.And my phone is still here,intact,so that I can write this here.
Sent from my GT-I9100 using xda premium
Of course my sgs mobo could have been faulty.
When the mobo fried it was hot, i mean hot.
I didn´t look temperatures.
It didn´t wake up even using jig.
I sended it to service.
If they had succesfully woke it up, they wouldn´t fix it on warranty (rooted).
Normally oc would be fine because it´s using powersave and underclock it.
But if you play like 2 hours on 1,6Ghz it can get too hot (over 60c on cpu).
I can´t recommend that kind of temperature.
And nobody here knows what kind of vrm´s phone has.
Also cooling plates are not designed for massive oc/voltage.
Of course temperature depends on voltage more than the clock speeds.
It´s up to user if he want to use it that kind of voltages/speeds.
I would´t use it 1600Mhz/24/7.
Generally i know what i´m talking about (using water on pc...)
Just look for temperatures and don´t give too much voltage (as low as possible).
Of course you don´t know safe voltage limits, but try and look what other have been using.
Don´t oc much if you don´t know what are you doing.
@tolis626 Hi, I have oc'd to 1.4ghz for the last few weeks, and I have under volted it to 12.75mV, the same as you, have you had any problems at that voltage? Also, is your 1200mhz voltage stable as it seems very low, to say that it was, at stock, 13mV. Furthermore, have you ever tried to under volt 1600mhz please?
Buffalee said:
Of course my sgs mobo could have been faulty.
When the mobo fried it was hot, i mean hot.
I didn´t look temperatures.
It didn´t wake up even using jig.
I sended it to service.
If they had succesfully woke it up, they wouldn´t fix it on warranty (rooted).
Normally oc would be fine because it´s using powersave and underclock it.
But if you play like 2 hours on 1,6Ghz it can get too hot (over 60c on cpu).
I can´t recommend that kind of temperature.
And nobody here knows what kind of vrm´s phone has.
Also cooling plates are not designed for massive oc/voltage.
Of course temperature depends on voltage more than the clock speeds.
It´s up to user if he want to use it that kind of voltages/speeds.
I would´t use it 1600Mhz/24/7.
Generally i know what i´m talking about (using water on pc...)
Just look for temperatures and don´t give too much voltage (as low as possible).
Of course you don´t know safe voltage limits, but try and look what other have been using.
Don´t oc much if you don´t know what are you doing.
Click to expand...
Click to collapse
I know what I'm doing.I know the risks,that's why I don't encourage anyone to overclock as much as I do.I carefully monitor temperatures and voltages over long time periods.Rest assured,I won't come back here crying.
danielsf said:
@tolis626 Hi, I have oc'd to 1.4ghz for the last few weeks, and I have under volted it to 12.75mV, the same as you, have you had any problems at that voltage? Also, is your 1200mhz voltage stable as it seems very low, to say that it was, at stock, 13mV. Furthermore, have you ever tried to under volt 1600mhz please?
Click to expand...
Click to collapse
Well,since 1400MHz and 1600MHz aren't stock clocks,you don't actually undervolt them.You rather choose a voltage for them as there isn't a standard one.
My phone is stable with the voltages in my sig(I've only changed 200Mhz and 500MHz voltages a little but too bored to update my sig ) for months,so yeah,I'd say I don't have any problems.This doesn't mean that no one will.Your phone might need 1325μV or 1225μV for 1400MHz.Every phone's CPU is unique in its own way.
@tolis626 Thanks very much, one more stupid question please, will under volting from stock Samsung voltages, even if it's stable, decrease performance compared to stock voltages on an average exynos processor please, aslo will undervolting from original kernel clock speed increase the processors life span? I have researching this and came up with nothing.
Will it break your phone? Not directly. It will shorten the lifetime.
Besides that the heat can indirectly kill your device.
I'm just curious:
Why overclocking the device? I have mine underclocked to 1 GHz max. It still has enough power to handle everything.
Sent from my GT-I9100 using XDA App
I have just been messing around. I can get 1.6ghz perfectly stable at 1350mv, I tried 1325mv and it hung up after about 2 min of use. I can also get my 1.4ghz down to 1225mv's and 1.2ghz to 1.200 it is rock stable and I haven't tried lower voltages on 1.4 & 1.2.
I am going to keep [email protected] & 1.4 @ 1250mv & [email protected]
danielsf said:
@tolis626 Thanks very much, one more stupid question please, will under volting from stock Samsung voltages, even if it's stable, decrease performance compared to stock voltages on an average exynos processor please, aslo will undervolting from original kernel clock speed increase the processors life span? I have researching this and came up with nothing.
Click to expand...
Click to collapse
No,undervolting will in fact prolong your processor's lifetime,albeit negligibly,because with less voltage less heat is generated.It's plain physics.
Overclocking on the other hand will reduce your CPU's lifetime.The damage(mostly electromigration) is dependent on the CPU and how much you overclock.Quite frankly again,you won't still have the phone when enough damage is done for it to break.If the slightly lower battery life doesn't bother you that much,I say go for it.
danielsf said:
I have just been messing around. I can get 1.6ghz perfectly stable at 1350mv, I tried 1325mv and it hung up after about 2 min of use. I can also get my 1.4ghz down to 1225mv's and 1.2ghz to 1.200 it is rock stable and I haven't tried lower voltages on 1.4 & 1.2.
I am going to keep [email protected] & 1.4 @ 1250mv & [email protected]
Click to expand...
Click to collapse
Dude,that's some nice UV!Mine instantly crashes when I set it to 1375μV at 1600MHz.You're lucky.
Oh and,most probably your phone can handle 1200MHz at 1150μV.
Sent from my GT-I9100 using xda premium
tolis626 said:
No,undervolting will in fact prolong your processor's lifetime,albeit negligibly,because with less voltage less heat is generated.It's plain physics.
Overclocking on the other hand will reduce your CPU's lifetime.The damage(mostly electromigration) is dependent on the CPU and how much you overclock.Quite frankly again,you won't still have the phone when enough damage is done for it to break.If the slightly lower battery life doesn't bother you that much,I say go for it.
Dude,that's some nice UV!Mine instantly crashes when I set it to 1375μV at 1600MHz.You're lucky.
Oh and,most probably your phone can handle 1200MHz at 1150μV.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Thank you very much for all your help I tried undervolting 1200mhz more, I got to 1075mv and it was rock stable, I don't think I am going to try anything lower than that. Just for info, I'm on SiyahKernel v2.6.2 Thanks again
CPUs care a lot about voltage and don't give a rip about MHz except for the minor heat increase. The chip in my phone is a bad clocker though. If I could get 1400mhz to work at close to the stock 1200mhz voltage I would do it in a heartbeat. Sadly mine requires a healthy bump so I abstain. At least until I can afford to replace it
Number one rule of overclocking, don't push the voltage if you can't afford to replace it
I discussed the topic of overclocking processors with a friend of mine who design cellphone CPUs. He told me that over the lifetime of a CPU, the insulating oxide layers break down. This process is considerably faster at 40% extra power and frequency. So don't expect it to last as long as a normally clocked CPU. So the question is how long it would normally last.

Safe overclocking temps SGP5

I have my SGP5 overclocked to 1.5ghz at the moment via Tegrak. Everything is running smoothly but the spot on the back where the CPU is gets warm to the touch. Not hot or anything, but obviously warm.
Before I had it overclocked to 1.45ghz and it stayed a lot cooler, but to get to 1.5 I had to bump the core voltage to 1.35v. I also have the up-threshold set to 35% so it spends a good amount of time at max speed.
Since these things don't have CPU temp monitoring, how do you tell when it's too hot? My battery temp never goes much over 80*F, so that doesn't seem like a good indicator of anything.
Sitting here playing music with Mufin my IR temp gun reads a max of 100*F on the back of the case over the CPU. Battery temp is reading 77*. Is that too warm? How much of a temp differential can there be between the outside of the case and the CPU itself?
I'm no noob to overclocking PCs, but this is my first Android device so I don't really know it's limits as clearly.
Any help would be mucho appreciated!
DISCLAIMER - anything within this thread has the potential to do permanent damage.. I haven't had any issues yet but will not be held responsible for any damage!
So I just pulled the back cover off it. Running the same program for 10-15mins the CPU never exceeded 82.5*F which is well within safe limits imo.
I guess that goes to show how poor the cooling is in one of these things with the back cover on. I'm going to keep running 1.5ghz and report any issues. The difference in smoothness between 1.4 and 1.5ghz is pretty dramatic.. web browsing is very very smooth now. I probably won't be going any higher than 1.5, but for now it seems safe.
Tegrak Ultimate Profile -
Level0
1500mhz
1.350mV core
1.155mV internal
Level 2-4 untouched
Level 5 (undervolted for better battery life)
100mhz
850mV core
900mV internal
Using ondemand governor
35% up-threshold
exodus454 said:
So I just pulled the back cover off it. Running the same program for 10-15mins the CPU never exceeded 82.5*F which is well within safe limits imo.
I guess that goes to show how poor the cooling is in one of these things with the back cover on. I'm going to keep running 1.5ghz and report any issues. The difference in smoothness between 1.4 and 1.5ghz is pretty dramatic.. web browsing is very very smooth now. I probably won't be going any higher than 1.5, but for now it seems safe.
Tegrak Ultimate Profile -
Level0
1500mhz
1.350mV core
1.155mV internal
Level 2-4 untouched
Level 5 (undervolted for better battery life)
100mhz
850mV core
900mV internal
Using ondemand governor
35% up-threshold
Click to expand...
Click to collapse
Just tried your profile, and I have to say it works fantastic! The web browsing really is super fast.
Is there any major danger at this clock speed with On-Demand on? I mean, it'll only use 1.5GHz if it needs it right?
ZaIINN said:
Just tried your profile, and I have to say it works fantastic! The web browsing really is super fast.
Is there any major danger at this clock speed with On-Demand on? I mean, it'll only use 1.5GHz if it needs it right?
Click to expand...
Click to collapse
Ondemand from my understanding, scales processor speed using the values in the up/down (I believe System Tuner refers to down as "powersave bias") threshold. From my experience it's the best governor to use as far as customizing it easily and getting it to respond well.
Whatever you set the up-threshold to, when CPU load exceeds that value it bumps the speed up to the next "level" and ending in full speed. Then when CPU load falls below the down-threshold, it scales it back down to the next lowest level, so on and so-forth. You can also adjust the sampling rate too - lower frequency means it checks the CPU load more frequently and essentially makes the governor more responsive.
When I set mine to 35%, almost any program aside from stuff sitting almost completely idle will trip the CPU to hit 1.5ghz. This makes everything real responsive and may use more battery.. but I prefer having a more responsive device. You can also adjust the up-threshold to a higher number to try to lower temps and extend battery life. You can really play around with it to suit your needs, there's not really anything to screw up there.
There shouldn't be any danger using it with the ondemand.. but since I haven't tested this for more than a few days right now just keep an eye on temps (especially while playing games) and watch out for any "stuttering" out of the blue. Mine gets warm but nothing excessive. You'll be able to feel it on the back between the speakers.
I have to say though, even running such a high clock speed I'm not really seeing any negative effect on battery life so far.
Lemme know how yours goes!
How can it not have any risks? When the heat is too much somethig will explode wouldn't it?
No just kidding, but seriously. There is a risk of overheating a hardware and 'destroying' it, there should be!
Sent from my GT-I9000 using XDA
Well of course there's always some risk in overclocking! Especially when you don't know what you're doing.
As far as using one governor or another though.. when it comes down to it there shouldn't be a huge difference.
Sent from my YP-G70 using Tapatalk
I use SetCPU for root, but i don't see an option for more than 1200 mhz. How can I get it to 1500?
Rapydax said:
I use SetCPU for root, but i don't see an option for more than 1200 mhz. How can I get it to 1500?
Click to expand...
Click to collapse
Tegrak Overclock Ultimate
Sent from my YP-G70 using Tapatalk
exodus454 said:
Tegrak Overclock Ultimate
Sent from my YP-G70 using Tapatalk
Click to expand...
Click to collapse
you bought it?
i really want tegrak OC can you send me it in pm?
kfirbep said:
you bought it?
i really want tegrak OC can you send me it in pm?
Click to expand...
Click to collapse
Dude.
READ THE RULES!
XDA does not allow pirating apps or software to be discussed on the forums.
6. Do not post warez.
If a piece of software requires you to pay to use it, either pay or find your cracks and serials somewhere else. We do not accept warez nor do we permit any member to promote or describe ways in which Warez, cracks, serial codes or other means of avoiding payment, can be obtained.
9. Don't get us in trouble.
Don't post copyrighted materials or do other things that will obviously lead to legal trouble. If you wouldn't do it on your own homepage, you probably don't want to do it here either. This does not mean we agree with everything the software piracy lobby try to impose on us, it simply means you cannot break any laws here, since we'll end up dealing with legal hassle caused by you. Please use common sense: respect the forum, its users, and those that write great code.
If you want an app, why don't you just support the developer and buy it??

[Q] What benefits does UC\UV give you?

If someone would teach me that would be great!
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Better battery life. But be careful with undervolting. It can cause phone to be unstable. Under clocking is more forgiving. If you are going to do either I would suggest only making small changes and then use phone for several hours to settle in. If all good then try next step lower and test until you find the limit of your phone. Then bump it back up to last stable setting.
There are no noticeable benefits.
jimmer411 said:
There are no noticeable benefits.
Click to expand...
Click to collapse
I agree, its mostly the placebo effect regarding lag, a variable effect regarding battery life, due to user apps, and downright dangerous regarding overheating.
But many people whine when its not available for a kernel. I don't have a very high opinion of its necessity.
Battery life in our phones is dominated by the screen and radio (cell and wifi) but I find that undervolting at least reduces the heat when I'm doing something intensive like SNES emulation. Lag in our phones is also primarily a software issue (I have other Android devices with the same hardware running at the same MHz and it's a smoother experience).
Not that my Note got hot, it's just less warm.
ZacksBuilds said:
If someone would teach me that would be great!
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
There's no reason not to under volt.
UC=Under clock
UV=Under volt
OC=Over clock
OV=Over volt.
Newer generations of chips have tremendous tolerances. If you were to look at the S3, a Qualcomm built SoC that was a bit long-in-the-tooth by the time the Note was released, you'd see that in many cases, there were phones that featured the chip, but were clocked lower... I.E at 1,000 MHz.
Most chips are designed to run faster than they do, at least for short periods of time. Modern chips use temperature and load to designate the running frequency.
When Qualcomm releases a chip, they need to be sure that 99% of the units they produce, can run with a near-flawless level of stability. Because of this, they often run chips slower, and at a higher voltage than is actually needed. The result is, that Qualcomm or Samsung might design a chip rated for 2ghz, and release their first device with the chip running at 1.5ghz. This is common. Each piece of silicon is slightly different due to manufacturing differences. Chips are made on giant discs, with hundreds of chips on a single disc. The chips in the center are generally considered to be of a slightly higher quality, requiring less voltage, or capable of running at a higher frequency, sometimes both. Because of this, each device is capable of slightly more, or slightly less. The challenge is for Qualcomm to set the speed and power usage for every chip-- the challenge for us, is to see if we can run the chip at a higher frequency, while drawing less power....because power =heat, and power= battery life.
There are two different ways to approach customizing frequency and voltage to your needs.
One: If you could run your Note at 1,900mhz, instead of 1500mhz, and draw the same amount of power, that'd be considered a success case. Your device would be faster, without a hit in battery life.
Two: Or, if you could run the device at the same speed, and lower the voltage (saving battery life), this would also be considered a success.
Sometimes, but rarely in the mobile space, you'll get lucky and receive a prime piece of silicon, and you'll be able to over clock, WHILE undervolting...resulting in a faster phone that uses battery life.
Ranger was correct...clock speed changes on the order of +/-20 percent are hardly noticeable. However, power requirements grow exponentially at higher frequencies, and on a mobile device, they're noticeable. While a device might require 1.2 volts at 1.5 GHz, and 1.3 at 1.6ghz, it might also only require 1.05, or 1.0 volts at 1.4ghz. These numbers are theoretical, and shouldn't be used-they arent even close to correct. They're used merely to illustrate that to over clock, chips often require more power than over clocking is worth, in heat (and heat past a certain point will instantly fry your device, or will reduce the lifespan of the chip).
These are general ideas on over clocking. If you want to know something specific, ask away. When over clocking/underclocking, the governor used (a set of conditions that tells the CPU when to change from, say 300mhz (when the screen is off, and the device isn't being used), to 1.5ghz, when both cores are being used, and fully loaded.
If you want to save battery life, a combination of build.prop radio tweaks, modem tweaks, under clocking profiles, and using a custom governor can significantly increase standby time, and noticeably, but not too significantly increase usage time. Its important to know though, that the screen is the hungriest part of our device, and brightness is the the quickest setting to adjust to gain battery life.
The same is true for performance. Kernel, OC profiles, build.prop and launcher tweaks, GOU over clocking, etc. All in combination can have a noticeable effect, because performance is the net sum of dozens of moving parts.
Sent from my SGH-I717 using XDA Premium HD app
Jamesyboy said:
There's no reason not to under volt.
UC=Under clock
UV=Under volt
OC=Over clock
OV=Over volt.
Newer generations of chips have tremendous tolerances. If you were to look at the S3, a Qualcomm built SoC that was a bit long-in-the-tooth by the time the Note was released, you'd see that in many cases, there were phones that featured the chip, but were clocked lower... I.E at 1,000 MHz.
Most chips are designed to run faster than they do, at least for short periods of time. Modern chips use temperature and load to designate the running frequency.
When Qualcomm releases a chip, they need to be sure that 99% of the units they produce, can run with a near-flawless level of stability. Because of this, they often run chips slower, and at a higher voltage than is actually needed. The result is, that Qualcomm or Samsung might design a chip rated for 2ghz, and release their first device with the chip running at 1.5ghz. This is common. Each piece of silicon is slightly different due to manufacturing differences. Chips are made on giant discs, with hundreds of chips on a single disc. The chips in the center are generally considered to be of a slightly higher quality, requiring less voltage, or capable of running at a higher frequency, sometimes both. Because of this, each device is capable of slightly more, or slightly less. The challenge is for Qualcomm to set the speed and power usage for every chip-- the challenge for us, is to see if we can run the chip at a higher frequency, while drawing less power....because power =heat, and power= battery life.
There are two different ways to approach customizing frequency and voltage to your needs.
One: If you could run your Note at 1,900mhz, instead of 1500mhz, and draw the same amount of power, that'd be considered a success case. Your device would be faster, without a hit in battery life.
Two: Or, if you could run the device at the same speed, and lower the voltage (saving battery life), this would also be considered a success.
Sometimes, but rarely in the mobile space, you'll get lucky and receive a prime piece of silicon, and you'll be able to over clock, WHILE undervolting...resulting in a faster phone that uses battery life.
Ranger was correct...clock speed changes on the order of +/-20 percent are hardly noticeable. However, power requirements grow exponentially at higher frequencies, and on a mobile device, they're noticeable. While a device might require 1.2 volts at 1.5 GHz, and 1.3 at 1.6ghz, it might also only require 1.05, or 1.0 volts at 1.4ghz. These numbers are theoretical, and shouldn't be used-they arent even close to correct. They're used merely to illustrate that to over clock, chips often require more power than over clocking is worth, in heat (and heat past a certain point will instantly fry your device, or will reduce the lifespan of the chip).
These are general ideas on over clocking. If you want to know something specific, ask away. When over clocking/underclocking, the governor used (a set of conditions that tells the CPU when to change from, say 300mhz (when the screen is off, and the device isn't being used), to 1.5ghz, when both cores are being used, and fully loaded.
If you want to save battery life, a combination of build.prop radio tweaks, modem tweaks, under clocking profiles, and using a custom governor can significantly increase standby time, and noticeably, but not too significantly increase usage time. Its important to know though, that the screen is the hungriest part of our device, and brightness is the the quickest setting to adjust to gain battery life.
The same is true for performance. Kernel, OC profiles, build.prop and launcher tweaks, GOU over clocking, etc. All in combination can have a noticeable effect, because performance is the net sum of dozens of moving parts.
Sent from my SGH-I717 using XDA Premium HD app
Click to expand...
Click to collapse
So what I understood is this: instead of having let's say, your note running at 1.2ghz consuming 15% battery per hour you can have it at 1.5ghz consuming the same battery life?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app

How to check PVS bin of your Z2!!

So after screwing around for about an hour trying to find the PVS bin of my Z2, I finally found out how
1. You need root
2. Go to sys/module/clock_krait_8974/parameters
3. Open table_name and your PVS is shown right there!!
Well I think I got really lucky as I have the highest binned CPU, PVS 15!
What bin do you guys have?
edit: Also can you guys tell us if your phone overheats when recording 4k video? I still get the overheating after like 4 minutes despite having a high PVS
Got PVS 12 here
Sent from my D6503 using XDA Premium 4 mobile app
PVS 8 here.
PVS 14 here. Nice
Sent from my D6503 using XDA Free mobile app
cchant said:
PVS 14 here. Nice
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
Does your phone overheat when recording 4k video?
PVS 13, Telstra Z2 D6503, bought on pre-order
Turn off steady shot. I get 10min still alive. Pvs 10 here
crzykiller said:
So after screwing around for about an hour trying to find the PVS bin of my Z2, I finally found out how
1. You need root
2. Go to sys/module/clock_krait_8974/parameters
3. Open table_name and your PVS is shown right there!!
Well I think I got really lucky as I have the highest binned CPU, PVS 15!
What bin do you guys have?
edit: Also can you guys tell us if your phone overheats when recording 4k video? I still get the overheating after like 4 minutes despite having a high PVS
Click to expand...
Click to collapse
what's pvs bin?
PVS 13. Why is this important?
Not important. The process vary among different wafer lot. The process variations are identified during production test, supply voltage will be set according to different process.
dilema said:
PVS 13. Why is this important?
Click to expand...
Click to collapse
PVS 11
PVS 14 W14 18 here ..but can anyone explain me what's the benefit of having a higher number of PVS rating ?
Whats PVS?
Sent from my D6503 using Tapatalk
dilema said:
PVS 13. Why is this important?
Click to expand...
Click to collapse
It's really only important if you under volt
Sent from my D6503 using XDA Free mobile app
---------- Post added at 07:41 AM ---------- Previous post was at 07:40 AM ----------
crzykiller said:
Does your phone overheat when recording 4k video?
Click to expand...
Click to collapse
I dunno I never tried 4k. Takes up lots of space and I don't have a 4k monitor
Sent from my D6503 using XDA Free mobile app
PVS 15
Vietnam unbranded, 19W19.
What is the point of this? Can someone give us a clear answer? Does this help to reduce phone overheating.
Chips are not all equal for most all devices. Some are better than others. Typically the chips that are not as good require more voltage to keep them stable especially at their low frequencies.
When the phone starts it will read the setting set by the chipmaker, the setting determines what voltage table to use.
The phones that can run on lower voltages will have slightly better battery life and run slightly cooler.
twistedddx said:
Chips are not all equal for most all devices. Some are better than others. Typically the chips that are not as good require more voltage to keep them stable especially at their low frequencies.
When the phone starts it will read the setting set by the chipmaker, the setting determines what voltage table to use.
The phones that can run on lower voltages will have slightly better battery life and run slightly cooler.
Click to expand...
Click to collapse
Higher is better or lower is better then?
El.Guaje said:
Higher is better or lower is better then?
Click to expand...
Click to collapse
Higher is better, also with a higher bin, you can also overlook much more
In fact, this explains everything and helps you with voltages needed to overclock. http://www.xda-developers.com/andro...-guide-helps-you-make-the-most-from-your-soc/
Normally once the CPU is getting towards the top of its performance all chips will be set to "max voltage". Eg I doubt any of the z2's are any different with voltages from about 1.5ghz upwards.
So when the CPU is draining the most power and generating the most heat the devices will all start performing closer and closer. The biggest differences between the CPU's is at low frequencies and how far you can overclock. Also users might start under or over voltage, and the stability while doing that will vary.
So high performance things like 4k video are unlikely to be all that different, all CPUs all be at high CPU freqs so will all be at max voltage.
Does anyone actually have the voltage tables for the z2's?
twistedddx said:
Normally once the CPU is getting towards the top of its performance all chips will be set to "max voltage". Eg I doubt any of the z2's are any different with voltages from about 1.5ghz upwards.
So when the CPU is draining the most power and generating the most heat the devices will all start performing closer and closer. The biggest differences between the CPU's is at low frequencies and how far you can overclock. Also users might start under or over voltage, and the stability while doing that will vary.
So high performance things like 4k video are unlikely to be all that different, all CPUs all be at high CPU freqs so will all be at max voltage.
Does anyone actually have the voltage tables for the z2's?
Click to expand...
Click to collapse
Look at the thing i just posted above your post... the one for the M8 are the ones for the Z2

Categories

Resources