Related
I've seen a few different posts in some of the kernel threads debating whether SetCPU is helping or hurting battery life. SO, I'm just kind of curious to see what results are on a larger scale? Based on your own experiences, do you have SetCPU installed and if so, does it help or hurt battery life generally? Also, if you do have it installed, do you use profiles? What are the most beneficial settings to use?
1. Not in right section
2. SetCPU not intended for battery life
3. It only adjusts CPU clockspeed
4. This thread is mostly meaningless
5. It's been discussed ad nauseam.
charnsingh_online said:
1. Not in right section
2. SetCPU not intended for battery life
3. It only adjusts CPU clockspeed
4. This thread is mostly meaningless
Click to expand...
Click to collapse
SetCPU is not intended for battery life? Go to the Market and look at the description. If I posted this in the wrong section I apoligize. But, I think you are mistaken with your comment about SetCPU not being intended to increase battery life or increase performance...
THATTON said:
SetCPU is not intended for battery life? Go to the Market and look at the description. If I posted this in the wrong section I apoligize. But, I think you are mistaken with your comment about SetCPU not being intended to increase battery life or increase performance...
Click to expand...
Click to collapse
SetCPU only sets clock speeds and governors already in the kernel. If you just install SetCPU and adjust no settings your battery life will not change. Thus, "does SetCPU help battery life?" is utterly and completely meaningless.
Discussion of different governors and clock speeds has occurred (and is still occurring) ad nauseum and is really more suited for the General forum.
Thread moved as it does not pertain to N1 development.
I see very little gains from setcpu but I use it because I purchased it from the market and why not use it if you bought it right?
This method does not apply to drug addiction LOL
-Charlie
bri3d said:
SetCPU only sets clock speeds and governors already in the kernel. If you just install SetCPU and adjust no settings your battery life will not change. Thus, "does SetCPU help battery life?" is utterly and completely meaningless.
Discussion of different governors and clock speeds has occurred (and is still occurring) ad nauseum and is really more suited for the General forum.
Click to expand...
Click to collapse
lol Why would you download an application, not use it, and expect results?
If you throttle your CPU down you WILL get better battery life. My phone is set to never go over 600mhz and I get bettter life with it than if I turn off setcpu altogether.
charnsingh_online said:
1. Not in right section
2. SetCPU not intended for battery life
3. It only adjusts CPU clockspeed
4. This thread is mostly meaningless
Click to expand...
Click to collapse
You have a lot of knowledge, this is obvious but you're unnecessarily harsh (mean).
It's boring but's it's a legitimate question because people still make inaccurate conclusions about CPU and battery life. Those of us with some knowledge can really help those that are trying to understand.
#2 above is correct. But the question remains, does a forced lower clock speed ceiling have an effect on battery life? It could do, of course it could, but without a baseline and a control environment it's impossible to prove either way. I suspect the OP is simply looking for subjective opinions.
And on this basis I offer:
The CPU only has a material effect on battery drain when it's being utilised.
When the Nexus CPU is not required to work it idles using the lowest power possible
The radio (network) interface is the second most demanding element of on your battery over time (next to the display). Although the CPU peak demand is higher than the radio.
SetCPU does not impact radio battery use.
SetCPU can not have a positive effect on battery usage if it's using more power to run it's clock cycles.
SetCPU can force the processor to use less power (wind down speed).
Slowing the processor means some tasks will take longer to perform.
If those tasks require a high-drain elements (display, radio, WiFi or BT for example) then it's counter-productive (battery wise) to slow them down.
However, because CPU power consumption does not have a liner relationship to clock speed, then some tasks that don't use high-drain elements will consume less power to complete.
So, whilst it's unlikely that your battery life will benefit from the use of SetCPU alone there is a chance that it will.
SetCPU is a fantastic app designed for overclocking, the profiles are niche facilities that may offer battery benefit to a narrow range of users.
Hey djmcnz thanks for the indept look at this app but more importantly thanks for showing respect to those of us who are just learning. We all have to learn information at some point and there are people that forget that at one point some one had to tell them.
Thank you for the clarification on that! Djmcnz-that was exactly what I was looking for in terms of an answer. I really appreciate you taking the time out to explain everything for me and anyone else that may have been curious.
charnsingh_online said:
1. Not in right section
2. SetCPU not intended for battery life
3. It only adjusts CPU clockspeed
4. This thread is mostly meaningless
Click to expand...
Click to collapse
Don't know why you're so pissed off by a thread...
1. Not a very big issue. We have mods here to take care of this.
2. I don't know if SetCPU affects battery life or not but similar thing on a PSP device does increase the battery life. I have tried it on my PSP and setting the clock speed to the lowest acceptable level (depending upon what you're doing) does help maximizing the battery life.
3. You're absolutely right here.
4. Don't know what to say man.. but being a little humble doesn't hurt....
I never meant to be rude. I always get pissed off when people post in wrong sections Seriously. If people post in right section it just frees up moderator time. And about CPU nexus CPU has same voltage for many frequencies like 998,960 have same voltage. Going so down doesn't mostly benefit. So setcpu is only good for overclocking IMO. Display uses most of the power along with radio n CPU is one of those in middle of usage maybe 3rd or 4th. So underclocking will give a big battery boost is just a placebo. Atmost 10 minutes more is what underclocking can provide. N its not worth sacrificing the performance. Go for something underpowered if u want to underclock IMO. So setcpu serves more purpose of power than battery
I use it for the cool widget and standby/idle profile. B-)
you know what?youre allright.i follow your threads and you explain things well for someone like me learning all this ****.i got no time for keyboard commandos.thanks for the explanation.
djmcnz said:
You have a lot of knowledge, this is obvious but you're unnecessarily harsh (mean).
It's boring but's it's a legitimate question because people still make inaccurate conclusions about CPU and battery life. Those of us with some knowledge can really help those that are trying to understand.
#2 above is correct. But the question remains, does a forced lower clock speed ceiling have an effect on battery life? It could do, of course it could, but without a baseline and a control environment it's impossible to prove either way. I suspect the OP is simply looking for subjective opinions.
And on this basis I offer:
The CPU only has a material effect on battery drain when it's being utilised.
When the Nexus CPU is not required to work it idles using the lowest power possible
The radio (network) interface is the second most demanding element of on your battery over time (next to the display). Although the CPU peak demand is higher than the radio.
SetCPU does not impact radio battery use.
SetCPU can not have a positive effect on battery usage if it's using more power to run it's clock cycles.
SetCPU can force the processor to use less power (wind down speed).
Slowing the processor means some tasks will take longer to perform.
If those tasks require a high-drain elements (display, radio, WiFi or BT for example) then it's counter-productive (battery wise) to slow them down.
However, because CPU power consumption does not have a liner relationship to clock speed, then some tasks that don't use high-drain elements will consume less power to complete.
So, whilst it's unlikely that your battery life will benefit from the use of SetCPU alone there is a chance that it will.
SetCPU is a fantastic app designed for overclocking, the profiles are niche facilities that may offer battery benefit to a narrow range of users.
Click to expand...
Click to collapse
djmcnz said:
You have a lot of knowledge, this is obvious but you're unnecessarily harsh (mean).
It's boring but's it's a legitimate question because people still make inaccurate conclusions about CPU and battery life. Those of us with some knowledge can really help those that are trying to understand.
#2 above is correct. But the question remains, does a forced lower clock speed ceiling have an effect on battery life? It could do, of course it could, but without a baseline and a control environment it's impossible to prove either way. I suspect the OP is simply looking for subjective opinions.
And on this basis I offer:
The CPU only has a material effect on battery drain when it's being utilised.
When the Nexus CPU is not required to work it idles using the lowest power possible
The radio (network) interface is the second most demanding element of on your battery over time (next to the display). Although the CPU peak demand is higher than the radio.
SetCPU does not impact radio battery use.
SetCPU can not have a positive effect on battery usage if it's using more power to run it's clock cycles.
SetCPU can force the processor to use less power (wind down speed).
Slowing the processor means some tasks will take longer to perform.
If those tasks require a high-drain elements (display, radio, WiFi or BT for example) then it's counter-productive (battery wise) to slow them down.
However, because CPU power consumption does not have a liner relationship to clock speed, then some tasks that don't use high-drain elements will consume less power to complete.
So, whilst it's unlikely that your battery life will benefit from the use of SetCPU alone there is a chance that it will.
SetCPU is a fantastic app designed for overclocking, the profiles are niche facilities that may offer battery benefit to a narrow range of users.
Click to expand...
Click to collapse
HUH English Please
Kidding
mikey1022 said:
huh english please :d
kidding
Click to expand...
Click to collapse
34567890
Personaly done many tests and the result was:
Test config: WiFi tethering all the way, screen 100% Playing video all the time 2G only
4:10 @ 245Mhz hard
3:30 @ 998Mhz hard
No use actually - using N1 on 245Mhz is impossible - too sluggish.
SetCpu is ussefull:
1) If u have OC kernel to set OC mode for games like Asphalt
2)For letting android vary frequence ondemand instead of 998 all the time
3)For downclocking while in sleep mode (why use full power when u dont use it?)
4)For using Failsafe profile, to prevent battery and hardware damage.
That's all.
No use trying saving battery setting profiles like 100% - 998, 50% - 576, 20% - 499. This is useless.
On UV kernels the same thing +\-30 minutes battery life. And UV kernels themselfs dont give segnificant battery life increase, only lags and unstability ti system.
Dont believe me try yourself - Create yourself some actions fo testing and repeat them 2 time (Min cpu and Max cpu) on any kernel. Results will be very close.
SeriousX said:
3)For downclocking while in sleep mode (why use full power when u dont use it?)
Click to expand...
Click to collapse
The CPU steps down to it's minimum speed by itself. It never uses more juice than it needs to.
As far as i know, it is always at maximum, but maybe im wrong and you are right - then theres even less sence in this app.
Hey,
So I'm on the fence about perma rooting and over clocking my G2, but i have a few questions:
1) Will my battery life suffer greatly due to over clocking say to 1Ghz or 1.4Ghz?
2) Are there any real world noticeable real world performance gains besides benchmark scores?
3) Will perma-Rooting it decrease performance? (Back when i had the mytouch 3g, the phone never felt as snappy after i rooted and installed custom roms, as compared to stock).
Thanks
1) battery life is the same if not better when overclocked with setcpu in ondemand mode at 245/1100mhz
2) there is a definite performance increase
3) custom roms can decrease performance depending on the rom and ui (sense is a bit heavy). Just simply rooting will not decrease performance. Also, CM6.1 is super snappy, especially using Launcher42
DO IT!
Sent from my T-Mobile G2
thedarkpassenger said:
1) battery life is the same if not better when overclocked with setcpu in ondemand mode at 245/1100mhz
2) there is a definite performance increase
3) custom roms can decrease performance depending on the rom and ui (sense is a bit heavy). Just simply rooting will not decrease performance. Also, CM6.1 is super snappy, especially using Launcher42
DO IT!
Sent from my T-Mobile G2
Click to expand...
Click to collapse
Launcher42? that's a heck lot of upgrade from Launcher2 I'd like to check it out
but he's right overclocking is not going to eat up your battery much. Heavy graphic ROMs do however suck up battery and performance. I personally like to stick to rooted stock roms and tune up here and there to fit my personal needs.
You should however read carefully and make sure to understand every steps you're doing if you want to root your phone.
androidtoy09 said:
Launcher42? that's a heck lot of upgrade from Launcher2 I'd like to check it out
but he's right overclocking is not going to eat up your battery much. Heavy graphic ROMs do however suck up battery and performance. I personally like to stick to rooted stock roms and tune up here and there to fit my personal needs.
You should however read carefully and make sure to understand every steps you're doing if you want to root your phone.
Click to expand...
Click to collapse
thedarkpassenger said:
1) battery life is the same if not better when overclocked with setcpu in ondemand mode at 245/1100mhz
2) there is a definite performance increase
3) custom roms can decrease performance depending on the rom and ui (sense is a bit heavy). Just simply rooting will not decrease performance. Also, CM6.1 is super snappy, especially using Launcher42
DO IT!
Sent from my T-Mobile G2
Click to expand...
Click to collapse
Alright I'm going to give it a shot later tonight probably, i forgot about the SETCPU profiles where you can have the phone under clocked while the screen is off. That should definitely give me better battery life. Ill be back to post results
kcm117 said:
Alright I'm going to give it a shot later tonight probably, i forgot about the SETCPU profiles where you can have the phone under clocked while the screen is off. That should definitely give me better battery life. Ill be back to post results
Click to expand...
Click to collapse
Good luck and I'm sure you will enjoy your G2.
Oh, and don't forget to show it off to your friends. Let them see how this thing "Fly"
I oc to 1.4+ with setcpu and a few profiles set up i get much better bat life then stock. Im also running a sense rom which feels sluggish until you oc. At 1.4 it runs smooth as can be with live wallpapers plus all the pretty sense animations. The only problem i have is i hate the sense dialer and msg system also i want to change the "personalise" tab....do people really change theyre settings everyday that they need a dedicated button for it? Anyway i digress
Sent from my HTC Vision using XDA App
Excuse me, since when does increasing the clockspeed of your CPU INCREASE battery life?!
convolution said:
Excuse me, since when does increasing the clockspeed of your CPU INCREASE battery life?!
Click to expand...
Click to collapse
No, that's not entirely true BUT with SetCPU you can profile it with different mode which can benefit the battery life.
kcm117 said:
Hey,
So I'm on the fence about perma rooting and over clocking my G2, but i have a few questions:
1) Will my battery life suffer greatly due to over clocking say to 1Ghz or 1.4Ghz?
2) Are there any real world noticeable real world performance gains besides benchmark scores?
3) Will perma-Rooting it decrease performance? (Back when i had the mytouch 3g, the phone never felt as snappy after i rooted and installed custom roms, as compared to stock).
Thanks
Click to expand...
Click to collapse
I don't notice any difference in battery and I have the 1.9ghz kernel. I normally keep it at 1ghz though. I enjoy it overclocked. My games run incredibly smooth, when navigating my phone it literally almost feels like it knows what i'm pressing a split second before i do and benchmarks rape the face off anyone else I know with an android phone. It's just sooo smooth. It really boils down to being the kind of person who likes to hold a powerhouse of a phone in the palm of their hand. (Literally) with even just the 1.4ghz OC you'll never have to ask yourself "can my phone run this without being sluggish?" because the answer is yes, it can probably even run two or three instances of whatever made you question yourself in the first place without being sluggish. Any if you're worried about custom roms from the past, just remember how outdated your old android is compared to this one. No offense because I can relate, I used to have a G1 that is now a hand-me-down to my brother and whenever he asks me to mod something on it, I'm just amazed at how slow it is and really don't know how I tolerated it for the last 2 years. I mean I'd score a 150 quadrant on the G1 (on a good day) but with my full OC on, the G2 scores 3000~3100. That's roughly 20 times faster...
Bottom line is that you won't need to worry about "will this make my device sluggish?" for quite some time.
Hey
Alright guys i got the phone perma rooted now, but i havent installed an OC kernel yet, two questions.
-Which kernal should i install if i want 1.4Ghz? there seems to be two threads with 1.4ghz kernels
-Do i need to install Bacon Bits for the kernel?
kcm117 said:
Alright guys i got the phone perma rooted now, but i havent installed an OC kernel yet, two questions.
-Which kernal should i install if i want 1.4Ghz? there seems to be two threads with 1.4ghz kernels
-Do i need to install Bacon Bits for the kernel?
Click to expand...
Click to collapse
just install cm6.1 and setCPU and you will be fine, then you can tweak it up to 1.42 if you like or whatever you want it at
Any heat related issues? Let's say I get into a zone and play some graphics intensive game 6 hours straight on USB power at 1.4Ghz? Wouldn't that put out more heat then the G2 was design to handle possibly shortening its life span?
convolution said:
Excuse me, since when does increasing the clockspeed of your CPU INCREASE battery life?!
Click to expand...
Click to collapse
It doesn't. However, overclocking is misnomer. What we really mean is over and UNDER clocking. For example with SetCPU is can create a profile that greatly slows down my CPU when the screen is off. This saves the battery a lot, since my screen is nearly always off.
Also, I can create profiles that slow down the CPU as the battery lowers in order to offset the fact that I overclock the CPU when the battery is fuller.
manvstech said:
Wouldn't that put out more heat then the G2 was design to handle possibly shortening its life span?
Click to expand...
Click to collapse
Probably could shorten the life span. I keep phones for a year or two, though, and shortened life span for me isn't an issue. The phone becomes outdated before the CPU gives up.
cparekh said:
It doesn't. However, overclocking is misnomer. What we really mean is over and UNDER clocking. For example with SetCPU is can create a profile that greatly slows down my CPU when the screen is off. This saves the battery a lot, since my screen is nearly always off.
Also, I can create profiles that slow down the CPU as the battery lowers in order to offset the fact that I overclock the CPU when the battery is fuller.
Click to expand...
Click to collapse
^This.
I've gone a full 10 hours with my battery still reporting 100%.
Sent from my HTC Vision using XDA App
my default sense rom does not feel sluggish at all.
this oc is not really required from my point of view. and it also does not increase battery. the thing what increased is the underclocking when screen is off.
and this you can do even without overclocking. and THEN it brings even more gain.
an example of "real world" for me is how well my g2 plays PSX games on the emulator. I have it overclocked at 1.5 on setcpu and it runs chrono cross pretty much flawlessly with no noticeable slow down.
i use setcpu for underclocking since i don't do enough just yet to overclock, i haven't noticed any battery increase just yet and i've been using it for a few days now. i almost questioned my self if i was losing battery life due to my system mhz always fluctuating? is this a possibility? i just added a profile for screen off 245/245 but i still had to choose on demand? what should i put there. thanks for ur help everyone
I installed the bacon bits 1.4ghz kernel and setup some setcpu profiles.....battery life is much better now.
Sent from my T-Mobile G2 using XDA App
screen off profile doesn't work with G2
noone has any proof it does change anything.
with or without widget running
Hi there many of you have thought about battery saving apps.
Do they really work?
Are there some apps that instead of saving battery just drain your battery even more?
Do you know any methods that really save battery?
Just post your oppinions about this subject.
nikeradsn said:
Hi there many of you have thought about battery saving apps.
Do they really work?
Are there some apps that instead of saving battery just drain your battery even more?
Do you know any methods that really save battery?
Just post your oppinions about this subject.
Click to expand...
Click to collapse
Battery saver apps are useless. just turn of data, sync,WiFi, Bluetooth when not in use. decrease screen brightness and screen timeout to 30 seconds. Use 245-806 with ondemand goveror for better battery.
mittalmailbox said:
Battery saver apps are useless. just turn of data, sync,WiFi, Bluetooth when not in use. decrease screen brightness and screen timeout to 30 seconds. Use 245-806 with ondemand goveror for better battery.
Click to expand...
Click to collapse
I've read many people saying that using the ondemand governor wouldnt save that much battery because of the continuous search for cpu activity, actually i'm using performance at 1024 and i also have another profile with 806 performance aswell.
I have to test it better in order to see which governor saves more battery.
I think a good set may useful
nikeradsn said:
I've read many people saying that using the ondemand governor wouldnt save that much battery because of the continuous search for cpu activity, actually i'm using performance at 1024 and i also have another profile with 806 performance aswell.
I have to test it better in order to see which governor saves more battery.
Click to expand...
Click to collapse
I used to use 806 on demand, 1024 ondemand and 1200 ondemand... now I'm using 1024 performance, and I dont see any battery difference.. damn thing still drains.
The battery lasts 4/5 days on idle, what more do you want? It's par for the course.
why do you need the phone to stay on idle? for that you could buy a 10$ one =S
nikeradsn said:
why do you need the phone to stay on idle? for that you could buy a 10$ one =S
Click to expand...
Click to collapse
Because it's an indicator of battery performance and proves there's nothing wrong with battery life on Aurora, despite what many believe. Having ~1 day of battery life with heavy usage and 4-5 days (or even more) on idle is on par with the battery specs.
faekplastik3s said:
Because it's an indicator of battery performance and proves there's nothing wrong with battery life on Aurora, despite what many believe. Having ~1 day of battery life with heavy usage and 4-5 days (or even more) on idle is on par with the battery specs.
Click to expand...
Click to collapse
Actually we all know that the battery life in aurora its not full optimized. what i mean is what can we do in order to get the best performance without having to spend so much battery life. maybe its not possible but who knows
Fact: ICS produces more traffic than GB. A lot of apps (like browser) use more memory, so background processes die more quickly. You cannot except to get the same kind of battery performance out of an ICS rom and that's the end of it. This has nothing to do with Aurora.
When I dont need to use the phone I put the governor in powersave with a low Mhz and the battery is more safe with little use.
Phone become a little more slow but work.
When I really need to use the phone I change the governor to Smartessv2
Guys, check out the new kernel here:
http://forum.xda-developers.com/showthread.php?t=1870259
It is written for the N8000 but I have run it on my 8013 without issues. The prior version of this caused flaky wifi but so far the newer version has been stable for me. If you do get a wifi crash, just turn wifi off then back on and it will reconnect easily. Up to you whether than small inconvenience is worth it for the extra speed.
Was able to use SetCPU to OC my SGN10.1 to 1704 at Performance and run some tests. Nailed a 6308 quadrant first try - wow!!! I have my SDcard OC'd to 4096 as well. Remember to always uncheck "Set at Boot" in SetCPU when testing out new speeds. You don't want to get stuck in a bootloop if you push things too far.
** One point. I found that OC to 1600 crashed my machine. Don't know why (dev bumped voltage to 1425 mv at 1704 - that's probably why), but for me anyway, 1704 seems stable for now.
I take no credit for this work (this is brieuwers doing) - simply passing the word along and letting 8013 owners no that, at least so far it has not melted my rig. Please do not thank me. Just passing along the word.
P.S., I got one bootloop after flashing with ODIN but then it booted fine.
** As always, if you brick your rig it's on you.
UPDATE - This is about 15% faster now and it feels it.
mitchellvii said:
UPDATE - This is about 15% faster now and it feels it.
Click to expand...
Click to collapse
Does that mean it's 15% warmer?
TonyBigs said:
Does that mean it's 15% warmer?
Click to expand...
Click to collapse
Honestly haven't noticed any heat increase.
Sent from my GT-N8013 using Tapatalk 2
Battery life reduction?
TheWerewolf said:
Battery life reduction?
Click to expand...
Click to collapse
Not that I've noticed but I typically use my tablet in my office where it is plugged in so hard to tell.
Sent from my SPH-D710 using Tapatalk 2
there will be a battery life decrease when using the tablet constantly at 100% cpu usage. bumping the voltage guarantees that. as for how much that is i can't tell you but under my normal use my tablet doesn't run full throttle all the time so the extra drain is negligible.
madsquabbles said:
there will be a battery life decrease when using the tablet constantly at 100% cpu usage. bumping the voltage guarantees that. as for how much that is i can't tell you but under my normal use my tablet doesn't run full throttle all the time so the extra drain is negligible.
Click to expand...
Click to collapse
What one has to wonder is does the very act of the cpu constantly throttling up and down and measuring what speed is best actually burn more fuel than just remaining at a high constant overclock? Think of it as city stop and go driving vs cruising on the highway.
If we are talking hours of difference then you have a point. But if we are just talking an extra 20 to 30 minutes of battery I would rather just have the speed. YMMV.
mitchellvii said:
What one has to wonder is does the very act of the cpu constantly throttling up and down and measuring what speed is best actually burn more fuel than just remaining at a high constant overclock? Think of it as city stop and go driving vs cruising on the highway.
If we are talking hours of difference then you have a point. But if we are just talking an extra 20 to 30 minutes of battery I would rather just have the speed. YMMV.
Click to expand...
Click to collapse
Well yeah,.going.faster means finishing quicker but generally you can expect higher levels of inefficiency at higher rigor... my somewhat educated opinion, without tossing around numbers, is that he effect on the battery life should be minimal.
Theres also the fact that with a 10 inch tablet, the screen takes up a clear majority of the current.. the processor, even while at 100% still pales in comparison.. and the processor is.not often at 100%.. you dont really flash the screen.on and off, you usually have it on for a block of time.. processor only really works during tasks and then idles.
Sent from my SGH-T959 running 4.1.1
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 ?