Related
After reading through the Thread for the Pre Release of FuguMod Ultra in the development section of this forum I thought I would post some info up for people who are wondering why it doesn't work with their phone, and just some general info on overclocking.
- First off, not all phones will be able to run at 1366MHz. Every CPU made has a range of freuqencies it will work at, and it is different for every single one. So some may be able to handle 1366MHz and above, others may max out at 900MHz. If you are getting black screens, freezes, or random behaviour, then your CPU doesn't like the frequency you have it at, try a lower frequency.
- Always keep an eye on the temp of the CPU when testing overclocking, if the CPU gets too hot, and fail safes don't work, there is a chance you could fry your CPU.
- With the FuguMod Ultra kernel, you must also be aware that gpu bus frequencies have been changed, so if your phone is not happy with that it will black screen. (as bus speeds are like cpu speeds, every different device can handle different clock speeds)
- plls values have been changed, and these may cause problems on your phone.
So if you want to have a go at overclocking your phone, back it up, and then give it a go. Select a frequency, and test with something pretty cpu intensive (3d game, multiple quadrant passes) and see if there are any bugs/overheating during a 15min time period. If you notice any problems/too much heat, try a lower frequency, and try again. And if for some reason your phone doesn't like the kernel, you can reflash with your previous kernel or a new ROM as you have already backed up your data.
If you have any other questions about overclocking, feel free to post here and I will try my best to answer them.
--- Samsung G3, InDroid 4.3, FuguMod 2.4 B3 800MHz ---
How can you check the CPU temperature? I thought it was only battery temperature.
Sent from my GT-I5800 using XDA App
dilzo said:
How can you check the CPU temperature? I thought it was only battery temperature.
Sent from my GT-I5800 using XDA App
Click to expand...
Click to collapse
The battery temp is a good representation of how hot the processor is getting as it is right next to the battery (only a thin sheet of metal seperating it) If the battery rises in temperature by a few degrees, then you can summize that the cpu is probably getting a few degrees hotter than that. I really wouldn't recommend letting the battery get above 55degrees (celcius) as this means the CPU may be getting up close to 65degrees (celcius) which is a very bad thing.
Good post.
Note that if you want to make some stress-tests, you have to put "PERFORMANCE" governor and set the max freq you want to test.
marcellusbe said:
Good post.
Note that if you want to make some stress-tests, you have to put "PERFORMANCE" governor and set the max freq you want to test.
Click to expand...
Click to collapse
Yes, Very true!!
Must also say, Your kernels are pretty legendary! Waiting patiently for the offical release of your FuguMod Ultra
m not able to see time in state with both setcpu and cpuspy and it seems deep sleep is also not working.
Piyush Rawal said:
m not able to see time in state with both setcpu and cpuspy and it seems deep sleep is also not working.
Click to expand...
Click to collapse
How have you got your phone set up? i.e. what ROM are you using etc.
I am using stock jpq with app2sd, swap, zipalign, ramhack and stuff. Setcpu is installed with default min/max freakquency, No profiles in use and undervolt a bit.
Ok,
This may be an issue caused by XXJPQ, as it is a new release there may be some sort of conflict. Have you tried asking if anyone else has this issue in this thread? http://forum.xda-developers.com/showthread.php?t=1132697
I haven't played around with JPQ yet so don't know what the bugs are yet.
Also, are you running a stock kernel? Have you confirmed that the phone has been rooted properly as well?
It's definitely a bug in Kernel. I tried three different roms and i wasn't able to check time in state in any of them (I am talking about fugumod ultra prerelease kernel here).
With previous versions of fugumad kernel everything is fine. So definatly a bug in kernel.
Piyush Rawal said:
It's definitely a bug in Kernel. I tried three different roms and i wasn't able to check time in state in any of them (I am talking about fugumod ultra prerelease kernel here).
With previous versions of fugumad kernel everything is fine. So definatly a bug in kernel.
Click to expand...
Click to collapse
Ok cool, I'll report the bug to the developer so that he can have a look into it. Thanks for testing and proving to the kernel.
Little bit of info some might find helpful. After some recent testing, I have found that some people might experience a black screen freeze when phone is in standby for a while with 83MHz min setting and on demand governor. I am not sure of the exact reason for this, whether it is a bug, or that the processor just doesn't like going that low for extended periods of time. If you experience this type of error, just hard reset the phone then open setcpu after phone has loaded and change the "standby" profile minimum to at least the next step up on the slider. Personally I use 223 setting as it provides a smoother lock screen animation, and no significant difference in battery drain.
Sent from my super smooth GT-I5800 using XDA App
OK for those that boast supreme bat life and performance please share your "EXACT" setup for set CPU, rom, kernel etc. Pretty please.
btucker2003 said:
OK for those that boast supreme bat life and performance please share your "EXACT" setup for set CPU, rom, kernel etc. Pretty please.
Click to expand...
Click to collapse
I'm guessing you're looking to underclock your CPU right?
Because "supreme bat life" and overclocking in the same sentence is an oxymoron.
The best thing I did was uninstall setcpu and let the custom kernel work,
Sent from my Nexus S 4G using xda premium
Currently running Taboonay 2.1b with rtrip's custom kernel 3.4 - it had issues with setcpu so I uninstalled it and am letting the kernel do it's thing - OC'd t 1.4 and it's smooth and fast but still has a decent battery life despite running a bunch of stuff, games, music, email and navigation - wifi on always...
Standby is about 3.5 days / on constantly about 7.5 hour life, so..yeah...Me likey..
YMMV
kjy2010 said:
I'm guessing you're looking to underclock your CPU right?
Because "supreme bat life" and overclocking in the same sentence is an oxymoron.
Click to expand...
Click to collapse
LOL, I was wondering the same thing about "boast supreme bat life and performance". This reminded me of my days of tuning cars and we we used to say "Fast, cheap, and reliable. You can have 2 of the 3."
OP, all machines won't react exactly the same way and people use their tablets for difference purposes, so having others post exactly what they have setup probably isn't the best way to go. First, you need to find a kernel that works and is stable for everything you need. Kernels are changing all the time, sometimes they move two steps forward and 1 step back before they are stable again and support everything a user needs (docking, NTFS mount, cifs, 3G etc.). After you find a kernel that is stable and suits your needs using the defaults, then you can take it a step further if you wish.
If you want a performance minded setup, setup a profile (in setcpu or one of the others) using the desired clock speed. Try 1.4 or 1.5 Ghz to start as that seems to work for most. Use the governor recommended by the kernel developer for best results. The more you over-clock, the more battery you will consume.
If things are stable with the default voltages, then experiment with under-volting to get the best battery life you can for your performance profile. Start with the recommended voltages with your kernel and adjust down -10uV at your max CPU frequency to find out how much voltage you can reduce and still have a stable system. Make sure you run through all the things you typically do and give it a good workout before moving down to another voltage. Using benchmarks can be helpful for finding stability, but may not match how you use the tablet in the real world.
If you want the best battery life, then experiment with under-clocking to 912MHz and then try under-volting that clock speed to find your stable point. You could then setup a setup "battery mizer" profile for that.
If this sounds too difficult and time consuming for you, then do as the others have stated and just install a custom kernel that does what you need and let it work for you. It should give you a good "in-between" setup. For me, I am addicted to 1.5GHz as the increased smoothness from stock is very noticeable for me. I can recharge every night after 6 hrs or so, so this works great for me. If I go on the road and need to take it easy on the battery, I use another profile to get better battery life for the time being.
Hope this helps you out.
kjy2010 said:
I'm guessing you're looking to underclock your CPU right?
Because "supreme bat life" and overclocking in the same sentence is an oxymoron.
Click to expand...
Click to collapse
_motley said:
LOL, I was wondering the same thing about "boast supreme bat life and performance". This reminded me of my days of tuning cars and we we used to say "Fast, cheap, and reliable. You can have 2 of the 3."
OP, all machines won't react exactly the same way and people use their tablets for difference purposes, so having others post exactly what they have setup probably isn't the best way to go. First, you need to find a kernel that works and is stable for everything you need. Kernels are changing all the time, sometimes they move two steps forward and 1 step back before they are stable again and support everything a user needs (docking, NTFS mount, cifs, 3G etc.). After you find a kernel that is stable and suits your needs using the defaults, then you can take it a step further if you wish.
If you want a performance minded setup, setup a profile (in setcpu or one of the others) using the desired clock speed. Try 1.4 or 1.5 Ghz to start as that seems to work for most. Use the governor recommended by the kernel developer for best results. The more you over-clock, the more battery you will consume.
If things are stable with the default voltages, then experiment with under-volting to get the best battery life you can for your performance profile. Start with the recommended voltages with your kernel and adjust down -10uV at your max CPU frequency to find out how much voltage you can reduce and still have a stable system. Make sure you run through all the things you typically do and give it a good workout before moving down to another voltage. Using benchmarks can be helpful for finding stability, but may not match how you use the tablet in the real world.
If you want the best battery life, then experiment with under-clocking to 912MHz and then try under-volting that clock speed to find your stable point. You could then setup a setup "battery mizer" profile for that.
If this sounds too difficult and time consuming for you, then do as the others have stated and just install a custom kernel that does what you need and let it work for you. It should give you a good "in-between" setup. For me, I am addicted to 1.5GHz as the increased smoothness from stock is very noticeable for me. I can recharge every night after 6 hrs or so, so this works great for me. If I go on the road and need to take it easy on the battery, I use another profile to get better battery life for the time being.
Hope this helps you out.
Click to expand...
Click to collapse
Hah! Well thanks but I'm pretty sure I didn't say "overclocking" but gotcha thanks for the feedback and answers. I was merely looking for setups compared to what I'm running now. TIA
Having read over the numerous lengthy JB kernel threads, and not seen any similar asked and answered, here's one question I expected to see here already.
Simply, disregarding settings like wifi or background syncing or apps, which existing kernel should I select strictly for best battery life?
Ideally it should:
1) Underclock
2) Undervolt
3) Use most efficient scheduler
4) Leverage deep sleep mode
Thank you in advance for ny feedback!
Cool so no opinions or anecdotal evidence out there?
try them and find out how your device reacts to them. there is no best kernel. there is only the kernel that your device(and you) like the best since every device will react differently to any given kernel. try out a few, it only takes 2-3 minutes to flash and boot a kernel. you dont have to wipe anything when flashing a kernel, wipe nothing. take a day or two to flash different kernels. for battery life comparisons, give the kernels 2-3 cycles before judging battery life. btw, i use trinity kernel, and i thoroughly enjoy it
mp3sum said:
Having read over the numerous lengthy JB kernel threads, and not seen any similar asked and answered, here's one question I expected to see here already.
Simply, disregarding settings like wifi or background syncing or apps, which existing kernel should I select strictly for best battery life?
Ideally it should:
1) Underclock
2) Undervolt
3) Use most efficient scheduler
4) Leverage deep sleep mode
Thank you in advance for ny feedback!
Click to expand...
Click to collapse
And dont really look for "most efficient scheduler". Custom kernel all have numerous schedulers and governers. Most all use the same selection, with a few exceptions, and you can change it to the scheduler/governer combination that best suits your needs. But first, it is all aboit trial and error on which those may be for you. I am partial to motleys or m kernel by metallice. Best of luck! And most of all, have fun on the journey.
Sent from my Nexus 7 using xda premium
Hello!
My "Cpu Type" is Slow and I want to undervolt it (to get better battery and less heat).
What are the best undervolting for keeping the device stable and with better battery and less heat?
Thanks!
Every chip is different, regardless of bin type. You'll have to experiment and see for yourself. Drop it a notch and use your phone to test for stability. If it seems stable, drop it one more. Keep going until you find the place that causes freezes. Then bump it back up and use the "set on boot" option all performance apps have.
estallings15 said:
Every chip is different, regardless of bin type. You'll have to experiment and see for yourself. Drop it a notch and use your phone to test for stability. If it seems stable, drop it one more. Keep going until you find the place that causes freezes. Then bump it back up and use the "set on boot" option all performance apps have.
Click to expand...
Click to collapse
I undervolted to 50, will it do what I want or should I undervolt more?
I heard that if I undervolt too much the device won't turn on, how can I avoid that?
Thank for the answer!
Wassupdog said:
I undervolted to 50, will it do what I want or should I undervolt more?
I heard that if I undervolt too much the device won't turn on, how can I avoid that?
Thank for the answer!
Click to expand...
Click to collapse
Don't set the voltage settings to stick on boot until you find your lowest stable voltage.
Sent from my Nexus 4 using xda app-developers app
Wassupdog said:
I undervolted to 50, will it do what I want or should I undervolt more?
I heard that if I undervolt too much the device won't turn on, how can I avoid that?
Thank for the answer!
Click to expand...
Click to collapse
I thought I explained this already, but I'll try it a different way. I can't answer the question because your chip is different from mine, along with everyone else's. The voltage will not be set until after the boot process is complete, which is why I told you to determine the lowest stable voltage and THEN use the set on boot option. That way you don't get an immediate freeze on every boot. Make sense?
Again, you still need to determine what your optimal voltage change is. We cannot tell you that.
Also, undervolting changes your battery life VERY little. It will likely not even be noticeable. Where you'll see the real benefit is in the area of heat. Even the 50 you've already done should make a noticeable change. On a device with a lot lower throttling point than most, this is a good thing.
Harry GT-S5830 said:
Don't set the voltage settings to stick on boot until you find your lowest stable voltage.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
estallings15 said:
I thought I explained this already, but I'll try it a different way. I can't answer the question because your chip is different from mine, along with everyone else's. The voltage will not be set until after the boot process is complete, which is why I told you to determine the lowest stable voltage and THEN use the set on boot option. That way you don't get an immediate freeze on every boot. Make sense?
Again, you still need to determine what your optimal voltage change is. We cannot tell you that.
Also, undervolting changes your battery life VERY little. It will likely not even be noticeable. Where you'll see the real benefit is in the area of heat. Even the 50 you've already done should make a noticeable change. On a device with a lot lower throttling point than most, this is a good thing.
Click to expand...
Click to collapse
Thank you both!
What can I do to increase battery life?
Wassupdog said:
Thank you both!
What can I do to increase battery life?
Click to expand...
Click to collapse
Play around with different kernels. They will all give you different performance vs. battery life. Use the one that suits you. Personally, I go back and forth between hells core and semaphore.
You might also check out greenify. It will hibernate apps that you tell it to instead of letting them suck up resources in the background.
estallings15 said:
Play around with different kernels. They will all give you different performance vs. battery life. Use the one that suits you. Personally, I go back and forth between hells core and semaphore.
You might also check out greenify. It will hibernate apps that you tell it to instead of letting them suck up resources in the background.
Click to expand...
Click to collapse
I have no problem to move between kernels but just if they have Franco's colors tuning option.
The Nexus screen looks wayyy better with it.
Wassupdog said:
I have no problem to move between kernels but just if they have Franco's colors tuning option.
The Nexus screen looks wayyy better with it.
Click to expand...
Click to collapse
This should help with semaphore. It uses Franco's values, but in a different order.
http://forum.xda-developers.com/showpost.php?p=43828267&postcount=2035
estallings15 said:
This should help with semaphore. It uses Franco's values, but in a different order.
http://forum.xda-developers.com/showpost.php?p=43828267&postcount=2035
Click to expand...
Click to collapse
Semaphore is good for battery life?
And I ran antutu with -75 UV and it is very not stable.
I can stay at 50 .
Wassupdog said:
Semaphore is good for battery life?
And I ran antutu with -75 UV and it is very not stable.
I can stay at 50 .
Click to expand...
Click to collapse
It is for me. That's why I recommended it.
You might take note of those voltages that work for you. I can't remember, but Semaphore might have lower values right out of the gate.
Now stop asking questions and start trying things out If you're scared, make a backup. No matter what you do with the voltage settings, you can always restore the backup.
Happy flashing!
estallings15 said:
It is for me. That's why I recommended it.
You might take note of those voltages that work for you. I can't remember, but Semaphore might have lower values right out of the gate.
Now stop asking questions and start trying things out If you're scared, make a backup. No matter what you do with the voltage settings, you can always restore the backup.
Happy flashing!
Click to expand...
Click to collapse
Thank you very much !
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 ?