Related
You can overclock n1 only to 1.190ghz, while desire hd 1.9ghz and the htc desire Z (G2) 2.0ghz. Does N1 has to old cpu?
-------------------------------------
Sent via the XDA Tapatalk App with my Sexy Nexy
Yes. 1st Gen snapdragon
Sent from my Nexus One using XDA App
if you want to OC you N1 go and OC you Desktop is the best choice
Why would you wanna over clock your phone? I have my N1 clocked @ 691 and works really fast with the MIUI rom and battery performance is better than stock. I'm not a fan of custom rom & rooting but I been pretty pleased so far. overclocking the nexus one will drain your battery like crazy plus the 1st Gen of snapdragons weren't as good with graphics as the A4chips and humming birds.
i have mine underclocked too and it works fine. try going a step further and underclocking it to like 422 when it's sleeping/standby. it'll help your battery
josemedina1983 said:
Why would you wanna over clock your phone? I have my N1 clocked @ 691 and works really fast with the MIUI rom and battery performance is better than stock. I'm not a fan of custom rom & rooting but I been pretty pleased so far. overclocking the nexus one will drain your battery like crazy plus the 1st Gen of snapdragons weren't as good with graphics as the A4chips and humming birds.
Click to expand...
Click to collapse
The connection between clockspeed and power consumption is not as strong as you think. But without a doubt it has an influence. Much more important is the voltage. If you "undervolt" the Nexus One CPU you can even get better battery live with higher clockspeed.
And if you use a tool to change the clockspeed depending on the situation (display on/off, battery % left, workload) and undervolt the cpu you can safe A LOT of juice.
With Wildmonks kernel, MIUI and SetCPU I get a much better lifetime than ever before even though my Nexus runs at 1152MHz.
Actually, the frequency makes a BIG difference in power consumption. Think of it this way - each clock causes changes propagating in transistors, which are the actual power draw. More clocks = more changes = more power drawn. As easy as that.
So, having 10% higher frequency and 10% lower voltage compensates each other.
Nexus has examples that overclock to 1.5GHz when overvolted, like Desire Z and Desire HD (both of those have to be overvolted to go up stable from 1.2GHz). Most of Nexus Ones fail when overclocking and don't reach higher than 1.2GHz, but it might be not because of the CPU, but because of other devices on system board.
Generally, it is only when you change the voltage (which is required to stabilize the higher frequency) that you see noticeable differences in battery life.
Jack_R1 said:
Actually, the frequency makes a BIG difference in power consumption. Think of it this way - each clock causes changes propagating in transistors, which are the actual power draw. More clocks = more changes = more power drawn. As easy as that.
So, having 10% higher frequency and 10% lower voltage compensates each other.
Nexus has examples that overclock to 1.5GHz when overvolted, like Desire Z and Desire HD (both of those have to be overvolted to go up stable from 1.2GHz). Most of Nexus Ones fail when overclocking and don't reach higher than 1.2GHz, but it might be not because of the CPU, but because of other devices on system board.
Click to expand...
Click to collapse
willverduzco said:
Generally, it is only when you change the voltage (which is required to stabilize the higher frequency) that you see noticeable differences in battery life.
Click to expand...
Click to collapse
Ok, some additions required.
Leakage is also dependent on power, and the dependency graph isn't linear - and starts breaking upwards at some point, usually being a tad above the max designed voltage.
Going down in voltage makes leakage change approximately linear, and doesn't affect nearly as much as going up.
Overclocking will draw power just as I noted above - exactly with the same percentage difference - only when the clock is reaching the overclocked area, which happens only when you're playing games or doing CPU-intensive tasks.
Undervolting will affect leakage, which happens 100% of the time.
So yes, when running in dynamically scaled environment, undervolting has more effect than overclocking. On desktop PC, running the same clock frequency constantly, the effect is the same.
Very True. And I wasn't saying that overclocking, while at the same voltage, didn't draw ANY more power... I just am trying to say that (for example in this graph) overclocking only has a small effect on power draw until you actually change the voltage. In that same example, going from 3.4 to 3.8 GHz only adds about 6% current draw while at the same vCore, while going up a similar amount in clock speed.
I'd even wager to say that if you're slightly under-volted and as heavily overclocked as you can go at that given voltage, you'll save some trivial amount of power versus stock because of the fact that voltage affects power draw significantly more than clock speed. I would also wager that if you are at an overclocked speed and are at stock voltage, the amount of current and power draw will be almost indistinguishable to the end user, since things like display will almost always use much more power if the display is on for any appreciable amount of time.
Jack_R1 said:
Ok, some additions required.
Leakage is also dependent on power, and the dependency graph isn't linear - and starts breaking upwards at some point, usually being a tad above the max designed voltage.
Going down in voltage makes leakage change approximately linear, and doesn't affect nearly as much as going up.
Overclocking will draw power just as I noted above - exactly with the same percentage difference - only when the clock is reaching the overclocked area, which happens only when you're playing games or doing CPU-intensive tasks.
Undervolting will affect leakage, which happens 100% of the time.
So yes, when running in dynamically scaled environment, undervolting has more effect than overclocking. On desktop PC, running the same clock frequency constantly, the effect is the same.
Click to expand...
Click to collapse
Jack_R1 said:
Actually, the frequency makes a BIG difference in power consumption. Think of it this way - each clock causes changes propagating in transistors, which are the actual power draw. More clocks = more changes = more power drawn. As easy as that.
So, having 10% higher frequency and 10% lower voltage compensates each other
Click to expand...
Click to collapse
I wouldn't call 10% more peak power consumption big if you take in account that the cpu is only running at the max clock speed a very small amount of time. 90% of the time the device is sleeping anyway and even if it's not you barely need the max clock speed. But if you do you will recognize the difference.
On the other side the reduced voltaged can safe you power all the time.
willverduzco said:
I'd even wager to say that if you're slightly under-volted and as heavily overclocked as you can go at that given voltage, you'll save some trivial amount of power versus stock because of the fact that voltage affects power draw significantly more than clock speed. I would also wager that if you are at an overclocked speed and are at stock voltage, the amount of current and power draw will be almost indistinguishable to the end user, since things like display will almost always use much more power if the display is on for any appreciable amount of time.
Click to expand...
Click to collapse
That's exactly what I experienced.
Pommes_Schranke said:
I wouldn't call 10% more peak power consumption big if you take in account that the cpu is only running at the max clock speed a very small amount of time. 90% of the time the device is sleeping anyway and even if it's not you barely need the max clock speed. But if you do you will recognize the difference.
On the other side the reduced voltaged can safe you power all the time.
Click to expand...
Click to collapse
Yes, you're right, and that's why I corrected myself in my second post. I totally forgot about the frequency scaling.
Off topic, but this is why I love XDA. Rational debate over a subject by intelligent people, where there usually isn't flaming. Thanks added to the two of your posts.
Just wondering if the screen is the major battery draw like battery stats show or if the CPU uses the most and if under volting makes a difference.
Sent from my Nexus 7 using Tapatalk 2
maybe a little,
#1 battery drainer is screen brightness...
Personally I don't think so. Just my opinion tho I'm no expert.
Sent from my Nexus 4 using Tapatalk 2
The power dissipated by a chip is calculated by C*V²*f (V = voltage, f = frequency)
So undervolting will lower the power consumption a bit, but not much in comparison to the screen. Real life difference will be minimal.
Undervolting the 1.3Ghz step from 1.075v to 1v will theoretically lower the power consumption at that step by 15%. But the tablet spends most of its time in the lower cpu steps, where undervolting much is not that simple to accomplish. Don't expect huge differences.
no
I think it does a bit plus it reduces the heat a bit .
Sent from my Nexus 7 using xda premium
The big battery eater on the nexus7 is the screen, not the cpu. You will save way more juice by setting your screen to not be maximum brightness than you will by hacking up the kernel and undervolting.
Think I've read somewhere you may save 3% or so, the real saving is the reduction in temperature
Sent via TCP/IP
I can give a similar general consensus as the others. On smaller devices like my old evo 4G, Undervolting, especially at the lower end of the frequency chart, made a very noticeable improvement, but on a tablet device or device with a larger screen, the quantitative difference quickly dissipates. Undervolting may still help a decent bit in standby time (which I'd argue tablets spend in than phones) but screen on will make only a minimal change.
spankmaster said:
I can give a similar general consensus as the others. On smaller devices like my old evo 4G, Undervolting, especially at the lower end of the frequency chart, made a very noticeable improvement, but on a tablet device or device with a larger screen, the quantitative difference quickly dissipates. Undervolting may still help a decent bit in standby time (which I'd argue tablets spend in than phones) but screen on will make only a minimal change.
Click to expand...
Click to collapse
Actually there is no saving while in standby; the cpu goes into the deep sleep state which already uses very little power. While I can't say I've seen battery life improvements from undervolting, it sure keeps the device cooler.
Sent from my SGH-I777 using xda premium
Hello Guys, i registered to XDA developers to ask this question so please reply. i heard many say GPU of Nexus 4 is very bad because after 20 mins of gameplay the phone gets heated and the GPU performance is Dramatically Reduced to cooldown. I am going to buy Nexus 4 thats y im asking, i didnt hear this from my neighbours..., i saw someone say this in youtube comments. Anyone Experiencing this Issue? or its a defective product?.
This is a good thread to read about Thermal Throttling: http://forum.xda-developers.com/showthread.php?t=2144652
I am not sure about the GPU actually reducing it's power when the nexus is getting hot. I know the CPU will clock lower when it has reached 70 degrees so it can cool down. Most kernel's have the ability to up this to about 100 degrees so you won't have the thermal throttling as fast. You are also able to remove the throttling completely with a commando.
I've played alot of Dungeon Hunter 4/GTA Vice City/Real Racing 3 and I have never experienced severe FPS drops because of it getting hotter. The only thing you will experience is a battery that will be empty within 2 hours.
PS: This is based on what i've read on the forums, I do not have my nexus 4 for that long and I am not a developer, someone might be able to give you more accurate information.
The thermald.conf sets the battery threshold to about 40-41C before it begins to underclock aggressively (hence why it feels sluggish). I forget the exact number. It starts reading "Overheating" status when it reaches about 46C. Max rated temperature for the battery is 60C.
At that battery temperature ~41C, the CPU is no more than about 50C, so it's not the CPU overheating.
If you feel so inclined, you can modify the thermald.conf with root to modify how aggressive the thermal throttling acts, within reason. Otherwise you'll cook your phone.
desynch- said:
The thermald.conf sets the battery threshold to about 40-41C before it begins to underclock aggressively (hence why it feels sluggish). I forget the exact number.
At that temperature, the CPU is no more than about 50C.
Click to expand...
Click to collapse
or you can run a custom kernel(like trinity) that disables the battery thermal throttle and not worry about it.
simms22 said:
or you can run a custom kernel(like trinity) that disables the battery thermal throttle and not worry about it.
Click to expand...
Click to collapse
YMMV with that. My nominal binned SoC overheats really easily. With the way I use my phone, it'd be overheating way too often.
I modified my thermald.conf so it's less aggressive. It's not that hard to figure out.
The phone throttles its clock speed like a PC. It's not a big deal.
Hello!
I heard about the term "UnderVolting" and I heard it would give me better battery life.
I want to do it but I have few questions before.
1. Is undervolting affects the CPU , GPU or Battery?
2. Can It damage the device?
3. Can it decrease the device performance?
Thanks!
Wassupdog said:
Hello!
I heard about the term "UnderVolting" and I heard it would give me better battery life.
I want to do it but I have few questions before.
1. Is undervolting affects the CPU , GPU or Battery?
2. Can It damage the device?
3. Can it decrease the device performance?
Thanks!
Click to expand...
Click to collapse
1. It effects the cpu. When you undervolt you are reducing the amount of power that is supplied to the cpu depending on what speed the cpu is running at.
2. It is unlikely to damage the device physically but if you undervolt too far the cpu can start failing actions resulting in corruption, but the most common symptom is that it will reboot itself if you go too low.
3. Undervolting can reduce performance but going down -100 mv across the board is usually stable for most.
Sent from my Nexus 4 using xda app-developers app
Alex240188 said:
1. It effects the cpu. When you undervolt you are reducing the amount of power that is supplied to the cpu depending on what speed the cpu is running at.
2. It is unlikely to damage the device physically but if you undervolt too far the cpu can start failing actions resulting in corruption, but the most common symptom is that it will reboot itself if you go too low.
3. Undervolting can reduce performance but going down -100 mv across the board is usually stable for most.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thanks!
Is it recommended to undervolt?
I just want a better battery and around the same performance as it now.
You are confusing undervolt with underclock. UC is a proven way to increase battery, but it directly makes the CPU run slower. UV will make the CPU/GPU/RAM receive less milivolts, and it will only increase battery, and not decrease performance. The thing with UV is that if the CPU at any given time does not get enough power, it can't perform a given task, and your phone will reboot.
Sent from my LG-P760 using xda app-developers app
In a nutshell UV will not destroy your phone and is it recommended? If you are in xda then you know the risks or at least should read up on the risks. I would say 90% of the custom kernels are undervolted out the box and yes its a great help. I have been UV, UC and sometimes even OC for years now with no negative effects. Give it a shot and if you are worried start slow like -25.
Try mathkids kernel(JSS roms only) which is undervolted -100 and if you read the thread its never been an issue for anyone. I have heard that UV may cause some issues with Maps locking fast
Dr.Molestratus said:
You are confusing undervolt with underclock. UC is a proven way to increase battery, but it directly makes the CPU run slower. UV will make the CPU/GPU/RAM receive less milivolts, and it will only increase battery, and not decrease performance. The thing with UV is that if the CPU at any given time does not get enough power, it can't perform a given task, and your phone will reboot.
Sent from my LG-P760 using xda app-developers app
Click to expand...
Click to collapse
I'm not Confusing undervolt with underclock.
Undervolting can and does reduce performance if you go too far. (Not far enough to cause reboots)
Underclocking is not a proven way to increase battery, in fact it's quite controversial.
It's called race to idle.
Pretty much all processors have great power savings at idle speeds.
By lowering the clock speed common tasks and background processes take longer to perform. Thus keeping the cpu at a higher clock rate (using more mv) for longer and overall using more battery than what it would have done at a higher speed.
From my own tests -150 mv undervolt resulted in slower and sometimes even laggy performance. -100 is great
Underclocking to 1ghz shortened my average daily battery life by nearly 2 hrs compared to running at stock 1.5
Say what you like about stats but these are the results I found from actual usage
Sent from my Nexus 4 using xda app-developers app
UV will reduce how hot your phone gets.. and if your phone gets too hot thermal throttling will reduce the cpu speed.. and thus if u UV it will reduce thermal throttling and will increase performance..
Thanks to everyone !
To the extent that flickering and low charging is related to Sony thermanager, here is the permanent fix for AOSP/CM based roms. While the idea of thermal manager is good and we should credit Sony for doing it, the implementation kind of s*cks. For example, the manager kicks in when CPU/GPU temperature rises to 44 degrees. Also, several triggers are set between 54-56 degrees. This is plain wrong, because 44, 50 and 55-56 are all perfect numbers for an active device and at these temperatures, thermal manager should not be active. I have adjusted trigger numbers so that there will be no mitigation until at least 60 and surprise surprise, all screen flickering is gone away....
Attached is thermanager.xml which should be put in /system/etc/ with 644 permissions. Reboot is required. UNZIP FIRST. Also, backup your current file just in case.
A word of caution on undervolting: keep in mind that when you undervolt on high frequencies, you make your CPU work harder, as it requires more cycles to do the same task. As a result, you have overheating. So, undervolting is counter-intuitive..
Does it also will solve the touch freeze problem on cm12.1?
Gesendet von meinem Xperia Z1
sgspluss said:
Does it also will solve the touch freeze problem on cm12.1?
Gesendet von meinem Xperia Z1
Click to expand...
Click to collapse
Any touch issues related to thermanager kicking in early could be resolved. But lollipop has overheating issues related to art, which can't be solved by thermal management. That's why strictly speaking, lollipop has to be recalled. In my view it can't be fixed.
A little question
Hello optimumpro
I only need put the thermanager in the path system/etc to make it work? or need something else?. Sorry by the queastion I noob an recently I repair de display and touchscreen for my xperia z1 C6902 and a have the flickering problem.
Thanks for your help.
optimumpro said:
A word of caution on undervolting: keep in mind that when you undervolt on high frequencies, you make your CPU work harder, as it requires more cycles to do the same task. As a result, you have overheating. So, undervolting is counter-intuitive..
Click to expand...
Click to collapse
I think you have a misconception about undervolting , undervolting does not make your CPU work harder , instead it makes your CPU unstable .
so no, undervolting does not makes your cpu overheat , only overvolting does.
This works for me!
before flash this file, my Phone only receives 90ma from any changer, and now reciving 1080ma. Thanks a lot!
Room: Ressurection Remix
Android version: 5.1.1, Xperia Z1 C6943
Sent from my Xperia Z1 using XDA Free mobile app
Hi
My phone in stock rom recieves 800ma
Does it normal??
I think it charges late,from 0 to 100 it takes about 3 hours 45 mins
Do i need flash this file??
Does my charger or battery have any problem?!
Thank you so much
Here is my screen shot
Sent from my C6903 using Tapatalk
agha_jo0n said:
Hi
My phone in stock rom recieves 800ma
Does it normal??
I think it charges late,from 0 to 100 it takes about 3 hours 45 mins
Do i need flash this file??
Does my charger or battery have any problem?!
Thank you so much
Here is my screen shot
View attachment 3434889
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
I don't think that app is accurate tbh with the fix it says no higher than 300ma for me and my phone is charging pretty well I'm using 2100ma charger as well
Sent from my Xperia Z1 using Tapatalk
Sorry bro but i don't have this file in system /etc??? Wtf???
ninjasoft said:
Sorry bro but i don't have this file in system /etc??? Wtf???
Click to expand...
Click to collapse
You are probably on kitkat. If that's the case, you don't need thermanager. If you are on lollipop, look again, the files are not necessarily in alphabetical order...
And remember, this one is for custom roms: CM and/or AOSP based. I just looked at your signature, you have stock...
zhuoyang said:
I think you have a misconception about undervolting , undervolting does not make your CPU work harder , instead it makes your CPU unstable .
so no, undervolting does not makes your cpu overheat , only overvolting does.
Click to expand...
Click to collapse
You are wrong. When cpu is unstable, it can't do the job. When it can't do the job it jumps to higher frequencies and then plugs in additional cores, which causes overheating.
optimumpro said:
You are wrong. When cpu is unstable, it can't do the job. When it can't do the job it jumps to higher frequencies and then plugs in additional cores, which causes overheating.
Click to expand...
Click to collapse
Explain why that a phone reboots automatically when you underclock too much, if your concept is correct then it should just run at higher frequencies instead of just reboot.
And also what's the purpose of overvolting?
What's the purpose of per frequency voltage table?
zhuoyang said:
Explain why that a phone reboots automatically when you underclock too much, if your concept is correct then it should just run at higher frequencies instead of just reboot.
And also what's the purpose of overvolting?
What's the purpose of per frequency voltage table?
Click to expand...
Click to collapse
Easy: when you under volt over a certain level, the cpu just shuts down, because it does not have enough energy to jump to higher frequencies. So, in that case, instead of jumping and overheating, it just dies. However, when you under volt to a lesser degree and cpu has just enough (not to die), then you will have jumping and overheating.
There is no purpose in overvolting, other than returning to your prior levels or correcting wrong default values if you don't want to fix those in kernel source.
What's the purpose of per frequency voltage table? If you adjust, you want to do it on global level, because cpu has different frequencies. There is no other way...
However, if you put your phone on performance governor, you won't need per frequency voltage. By the way, in my experience, performance governor causes less noise and overheating, because it does not spend time and energy on jumping, and it could go to idle immediately.
optimumpro said:
Easy: when you under volt over a certain level, the cpu just shuts down, because it does not have enough energy to jump to higher frequencies. So, in that case, instead of jumping and overheating, it just dies. However, when you under volt to a lesser degree and cpu has just enough (not to die), then you will have jumping and overheating.
There is no purpose in overvolting, other than returning to your prior levels or correcting wrong default values if you don't want to fix those in kernel source.
What's the purpose of per frequency voltage table? If you adjust, you want to do it on global level, because cpu has different frequencies. There is no other way...
However, if you put your phone on performance governor, you won't need per frequency voltage. By the way, in my experience, performance governor causes less noise and overheating, because it does not spend time and energy on jumping, and it could go to idle immediately.
Click to expand...
Click to collapse
__________________________________________________________________________________________________________________________________________________________________________
http://bigfatreality.blogspot.com/2012/04/complete-android-undervolting-guide.html
Advantages of undervolting Android
Thank God for Android where we can easily modify and customize our lovely Android devices to the way we want. Being said this, undervolting is one of the biggest attraction for Android! Simply by undervolting an Android you will or might experience:
A longer battery life
More responsive smartphone
Less heat produced by the phone
Super-charge your Android to go further than what it can do (overclocking Android)
Click to expand...
Click to collapse
http://techglen.com/2014/01/16/what-is-undervolting-how-to-undervolt-your-android-phone/
Note: UnderVolting is widely used as a cooling solution and in my opinion more effective than any other cooling solution available for free. Results can will show decrease in the temperature of smartphone. I recommend undervolting to anyone with enough confidence and knowledge to do so. The benefits easily outweigh the risks. I dont see why one shouldn’t do this for a cool and better smartphone experience.Undervolting will NOT compromise performance at all.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1956346
Undervolting is actually a very good thing for your smart phone when you do it correctly. Undervolting has one major positive effect on your CPU: it will extend the life of your processor by allowing it to do demanding things with lower heat generation
Click to expand...
Click to collapse
zhuoyang said:
__________________________________________________________________________________________________________________________________________________________________________
http://bigfatreality.blogspot.com/2012/04/complete-android-undervolting-guide.html
http://techglen.com/2014/01/16/what-is-undervolting-how-to-undervolt-your-android-phone/
http://forum.xda-developers.com/showthread.php?t=1956346
Click to expand...
Click to collapse
Maybe or maybe not. Blogs, especially by those who don't know what they are talking about (isn't it the purpose of blogs anyway? ) is not proof of anything.
However, you asked me to explain myself and I did. Why don't you put cpu info on the screen and experiment (so you can see live frequencies and temperature). You'll be surprised...
The point stands: when your cpu does not have enough juice, it spends more efforts to accomplish the task. If it manages not to shutdown, then it spends more cycles to do the job, thus causing overheating and excessive battery drain. And it does not matter how you call that state: unstable or whatever...
The reason I said it was counterintuitive is that people think if you provide less energy to cpu, there will be less noise and heat. The most energy is spent when cpu jumps back and force or plugs in/out cores and that's exactly what cpu does when you reduce voltage. If it is locked at the highest frequency, you eliminate jumping and extra plugging. When your phone is active, it accomplishes tasks faster. When it is done, it rushes to idle immediately and in idle state it virtually does not make any difference which frequency you are on, especially it does not matter when your phone is in deep sleep. Also, at higher frequencies cpu is often able to do the task using one core, again resulting in battery savings.
optimumpro said:
Maybe or maybe not. Blogs, especially by those who don't know what they are talking about (isn't it the purpose of blogs anyway? ) is not proof of anything.
However, you asked me to explain myself and I did. Why don't you put cpu info on the screen and experiment (so you can see live frequencies and temperature). You'll be surprised...
The point stands: when your cpu does not have enough juice, it spends more efforts to accomplish the task. If it manages not to shutdown, then it spends more cycles to do the job, thus causing overheating and excessive battery drain. And it does not matter how you call that state: unstable or whatever...
The reason I said it was counterintuitive is that people think if you provide less energy to cpu, there will be less noise and heat. The most energy is spent when cpu jumps back and force or plugs in/out cores and that's exactly what cpu does when you reduce voltage. If it is locked at the highest frequency, you eliminate jumping and extra plugging. When your phone is active, it accomplishes tasks faster. When it is done, it rushes to idle immediately and in idle state it virtually does not make any difference which frequency you are on, especially it does not matter when your phone is in deep sleep. Also, at higher frequencies cpu is often able to do the task using one core, again resulting in battery savings.
Click to expand...
Click to collapse
You're the one who don't know what you yourself is talking about.
Someone need to prove your concept right, I can't find anything about saying under clocking makes your cpu overheat.
Try find someone who agree with your concept or at least prove yourself right.
If you're able to prove yourself right I'll do you a favor and submit it to the news portal.
zhuoyang said:
You're the one who don't know what you yourself is talking about.
Someone need to prove your concept right, I can't find anything about saying under clocking makes your cpu overheat.
Try find someone who agree with your concept or at least prove yourself right.
If you're able to prove yourself right I'll do you a favor and submit it to the news portal.
Click to expand...
Click to collapse
"You're the one who don't know what you yourself is talking about"
No need to get personal. And I certainly don't need any "favors" from you.
If you need proof, just do a search anywhere including XDA where it would tell you that there is growing evidence that performance governor where your cpu is set at the highest frequency reduces "race to idle" and therefore causes less noise (jumping) and therefore better on performance and battery.
http://forum.xda-developers.com/nexus-4/development/guide-android-governors-explained-t2017715 That's just one example.
You won't find much more for several reasons: linux does not care about smart phones and only they know enough about kernels, but in the context of PCs they are not concerned about governors. They only have performance and ondemand (for laptops). Google does not deal with kernels (except for nexus) and they have no qualified engineers. Manufacturers do, but they have no incentives to invest more millions in research and development so that you can keep your device longer.
But as I have already said, do it yourself. Set cpu data on screen and experiment with performance vs other governors while watching the temperature. My experience has been that there is obviously no jumping and very little core plugging/unplugging, because 2.2-2.4 core can do a lot alone without extra efforts...
If you can't behave and maintain an intelligent conversation without resorting to personal attacks, then there is no point for me to talk to you. .
optimumpro said:
"You're the one who don't know what you yourself is talking about"
No need to get personal. And I certainly don't need any "favors" from you.
If you need proof, just do a search anywhere including XDA where it would tell you that there is growing evidence that performance governor where your cpu is set at the highest frequency reduces "race to idle" and therefore causes less noise (jumping) and therefore better on performance and battery.
http://forum.xda-developers.com/nexus-4/development/guide-android-governors-explained-t2017715 That's just one example.
You won't find much more for several reasons: linux does not care about smart phones and only they know enough about kernels, but in the context of PCs they are not concerned about governors. They only have performance and ondemand (for laptops). Google does not deal with kernels (except for nexus) and they have no qualified engineers. Manufacturers do, but they have no incentives to invest more millions in research and development so that you can keep your device longer.
But as I have already said, do it yourself. Set cpu data on screen and experiment with performance vs other governors while watching the temperature. My experience has been that there is obviously no jumping and very little core plugging/unplugging, because 2.2-2.4 core can do a lot alone without extra efforts...
If you can't behave and maintain an intelligent conversation without resorting to personal attacks, then there is no point for me to talk to you. .
Click to expand...
Click to collapse
I am not attacking you tbh.
Governors doesn't do anything besides controlling the frequencies of cpu. CPU uses correct amount of voltage according to the voltage table.
If what you're saying is correct, doesn't overvoltage makes your phone cooler? It has more energy to process things and doesn't need to jump to higher frequency right?
Kernel developers implement features for reasons. If your theory is correct, why does voltage control exist? Does kernel developers write a thousand lines of code just to do nothing?
zhuoyang said:
I am not attacking you tbh.
Governors doesn't do anything besides controlling the frequencies of cpu. CPU uses correct amount of voltage according to the voltage table.
If what you're saying is correct, doesn't overvoltage makes your phone cooler? It has more energy to process things and doesn't need to jump to higher frequency right?
Kernel developers implement features for reasons. If your theory is correct, why does voltage control exist? Does kernel developers write a thousand lines of code just to do nothing?
Click to expand...
Click to collapse
"I am not attacking you" Yes you were, I said that some bloggers don't know what they are talking about and you replied that I didn't know what I was talking about. Anyway, I accept your veiled apology.
Neither overvoltage nor undervoltage makes the phone cooler. There is an optimal regime for each cpu and if you go outside of it (in either direction), you are inviting trouble. You are not going to destroy your cpu by either under or over voltage, as there is protection in kernel. The phone runs cooler when cpu works less and the optimal regime causes the cpu work less. If you are reducing juice (voltage), you make cpu work longer, which results in overheating.
I gave you an example of performance governor to make a point that this is counterintuitive: while cpu is set at the higher frequencies, it actually performs the tasks and rushes to idle faster, which results in cooler condition. When the same cpu is set lower (and especially if it is under volted), it works longer, jumps to different frequencies, plugs/unplugs cores, which all contributes to overheating....
What is normal values for this phone ? I have diferent chargers, Samnsung - around 600mA, one HTC - around 400mA and another one with 200mA according to that app. Wich one should i use ? So far i used samsung one because it charges fast...2 hours or less, but the battery dies also fast ....so it may be because of the charger ?