As the title says, does enabling forced 2D GPU in settings> development option decrease battery life?
alireza_simkesh said:
As the title says, does enabling forced 2D GPU in settings> development option decrease battery life?
Click to expand...
Click to collapse
I doubt it will make any difference; heck, it may even improve your battery life. The GPU is designed to take over for the CPU to render graphics, so I think it would take some of the strain off of your phone's CPU and save you energy. That's at least my line of thought on the subject. It may make some older apps run a little wonky, but for the most part you'll see little to no effect on battery life and improved performance all around.
I've used it for 2 weeks without, then 2 weeks with it checked, and I can say that it does make the overall phone snappier.
I haven't noticed much effect to the battery.
I see....cuz i rem i read somewhere on XDA that force 2d GPU rendering decreases battery life so i wanted to make sure.
Related
I remember there was an app like this for the HTC Touch, when the phone is idle the app will reduce the cpu speed thus save the battery - I noticed a huge increase in battery life with the touch back then and thought it was an essential app. Is there anything like this for the HD2? I think we all can save some battery life for our HD2's
freakflow said:
I remember there was an app like this for the HTC Touch, when the phone is idle the app will reduce the cpu speed thus save the battery - I noticed a huge increase in battery life with the touch back then and thought it was an essential app. Is there anything like this for the HD2? I think we all can save some battery life for our HD2's
Click to expand...
Click to collapse
Without an app to increase cpu speed and disable dynamic speed it already does this ...
LeoCpuSpeed3 will allow you to change the settings ...
first of all, the hd2 does run at 998Ghz at optimized speeds at heavy load, otherwise at idle its 700Ghz, unused. it already has this feature built in. increasing speeds arent safe especially where theres no coolant system or heatsink on these arm cpu. peeps can do whatever with their $500 dollar investment
aoakes said:
first of all, the hd2 does run at 998Ghz at optimized speeds at heavy load, otherwise at idle its 700Ghz, unused. it already has this feature built in. increasing speeds arent safe especially where theres no coolant system or heatsink on these arm cpu. peeps can do whatever with their $500 dollar investment
Click to expand...
Click to collapse
True I would not recommend overclocking the phone, but many many people, including myself, use it locked at 998 with no problems, it gets warmer using wifi than it does at 998 ...
Also really I do not get much more battery life out of it set to dynamic ...
any app can reduce cpu below 700Mhz?
thanks.
Guys, NetRipper created an app that provides all of this. It covers all your LEO CPU manipulation needs - underclocking/overclocking even static & dynamic speed setting. Conveniently, its called Leo CPU Speed! You really have NO EXCUSE for not finding it - just type the damn words in a search box "leo cpu speed".
Please, don't act like morons!
Devs invest their precious time to create apps for you, give them intuitive names, write up tutorials, answer your questions .... it is not their job to run a search query for you - use the SEARCH box BEFORE you start hogging attention UNNECESSARILY; it'll take you less time finding it than posting up new questions!
It would be good if there was an app that reduces cpu speed to under 700mhz when the phone is locked and as soon as the phone is unlocked it takes it right back up to the full 998mhz.
Would save more battery than using autoscaling cause it would reduce it to less and you'd get full speed when the phone is unlocked since it would be at 998mhz. Something like that would be quite good providing it actually would save any battery
aLlamaWithARifle said:
It would be good if there was an app that reduces cpu speed to under 700mhz when the phone is locked and as soon as the phone is unlocked it takes it right back up to the full 998mhz.
Would save more battery than using autoscaling cause it would reduce it to less and you'd get full speed when the phone is unlocked since it would be at 998mhz. Something like that would be quite good providing it actually would save any battery
Click to expand...
Click to collapse
i totally agree...
aLlamaWithARifle said:
It would be good if there was an app that reduces cpu speed to under 700mhz when the phone is locked and as soon as the phone is unlocked it takes it right back up to the full 998mhz.
Would save more battery than using autoscaling cause it would reduce it to less and you'd get full speed when the phone is unlocked since it would be at 998mhz. Something like that would be quite good providing it actually would save any battery
Click to expand...
Click to collapse
on my Leo - when locked - the battery current is around 4mA,
if its typical, then not much is to be gained by underclocking this particular state
p107r0 said:
on my Leo - when locked - the battery current is around 4mA,
if its typical, then not much is to be gained by underclocking this particular state
Click to expand...
Click to collapse
yeah, mine is at 4mA as well..
isn't it like when in standby/locked the hd2 automatically underclocks to somewhat around 200mhz??
so, no need for an additional app.
hebbe said:
isn't it like when in standby/locked the hd2 automatically underclocks to somewhat around 200mhz??
so, no need for an additional app.
Click to expand...
Click to collapse
You're actually right! Moreover, the instant you interact with the phone again the CPU will popup to 700+, and then if you push it a little, it'll go all the way to 998. All of this is OEM behaviour! So, these guys REALLY need to move on
Surely it makes little difference on a processor with dynamic clk freq scaling?
Assuming its always clocking at its slowest during idle, which your phone is by default, then reducing the max clock speed during activity just extends the time its chugging away at max speed.
Only way to improve battery life is to reduce the amount of work you ask of your phone, not the speed at which it gets on with it.
For example, if my Desire has to process an image, it can either do that in 1ms at 1GHz, or 2ms at 500MHz, using the same amount of battery, no? At all other times its idling at the same 250MHz.
So the way forward is to reduce tasks, not underclock? And if anything the profile conditions in SetCpu are just one more thread.
Anyone actually noticed better battery performance from SetCpu?
I noticed bader Battery Life! So i dont use it anymore!
I don't think it will give you more battery life to reduce the cpu speed. more important i think is to watch the tasks that run on the background. some apps can drain you battery really fast. i just use advanced task killer and set it to kill apps when i turn my screen off, for me it helps more then lower the cpu speed.
Those apps drain battery by not letting the cpu idle, hence lowering max speed could improve battery life.
Sent from my HTC Magic using XDA App
I read a lot of comments about the processor used by qualcomm being asymmetrical thus one core is doing the heavy lifting most of the time while the other is at a lower clock speed and it affects overall performance but enhances battery life. Now that this is a big factor on why the performance and benchmarks are lower than tegra and exynos because its running on one core most of the time.
NOW.... When we get s-off and are able to mess with the kernel, cpu speeds and such. Can there be the possibility where we can use a tool like setcpu to force both cores to run at the same clock speed always? This might level the playing field and show some drastic performance enhancements imo.
Theoretically... Is there a slightest chance something like this can be done? I suppose so since we can manipulate the cpu so easily with kernel access
Please input
nothing? lol
this might be harder than i thought...
mike21pr said:
nothing? lol
this might be harder than i thought...
Click to expand...
Click to collapse
I don't think gingerbread has the capability even if the kernel was modified.
We can only wait and see
IMHO, with proper kernel, system will manage cores better and there will not be any lag. Asymmetrical core scaling will yield much better battery life then symmetrical one, just need better implementation.
Finally figured out how to over clock my CPU/GPU on One X with CM11 KitKat rom. Bumped the CPU to 1809 (what I researched is stable) and GPU to 512. My Antutu benchmark score dropped from low 17k's to mid 13k?
Help please!! Could running Trickster Mod App interfere with Performance option in CM11....?
Trickster Mod isn't interfering with the performance, it just means your phone won't perform at its peak with those settings. Higher CPU/GPU clocks don't necessarily mean better performance, I've seen this through extensive personal testing. Dial the settings back to stock and increase the clock speed incrementally while testing after each increase, you'll reach a point where performance suffers, dial it back one notch and there you have your "peak" settings.
Unless you're doing some really hardcore gaming on your phone it's all pretty pointless. There's no advantage to overclocking in everyday use of the device other than to say it's overclocked, you just can't notice a difference, any noticed difference is more than likely a placebo. I actually underclock my CPU to 1242mhz to improve battery life and have zero negative response whosoever, no matter what I throw at it.
Sent from my Evita
I agree with Tim here. I'm running cm11 on power saver mode, and it runs just fine. A little slow opening and closing apps, but buttery smooth for everything else.
Sent from my One X using xda premium
Hello guys
I'm not a new user in kernels or ROMs .
I have a low-decent battery life ,and I'm sure there's a way to get a better battery life with undervolting .
I want to know
what is "undervolting" ?
What is the biggest damage it can cause?
What is PVS?
How do I know ,how much I can UV?
What are the steps to undervolt?
What I gain from UV (despite battery life)?
For your info ,I'm using AOSPAL ROM +FAUX's latest 16u kernel .
Thanks
Sent from my Nexus 5 using XDA Premium 4 mobile app
http://forum.xda-developers.com/showthread.php?t=2537000
Sent from my Nexus 5 using Tapatalk
Hi,
Most of your questions have a reply:
About undervolting: http://forum.xda-developers.com/google-nexus-5/general/nexus-5-undervolting-thread-t2537000.
CPU binning: http://forum.xda-developers.com/google-nexus-5/general/cpu-binning-nexus-5-t2515593.
The "risks" are instability like hard reboot, SOD, etc.... To find a "safe" value you will need to test by yourself to find what undervolting your CPU can handle, not all CPU's are equals.
Undervolt by steps like - 25mV, don't set your new values at boot unless your are sure it's stable (or you could encounter bootloop), test for a few days under different conditions (as your use).
The gain apart battery life (but you will not gain that much as people tend to think) is a little less heat, but again nothing huge..., better is to test by yourself and see what you will gain... or not.
Battery life depends mainly of your use, apps, signal quality and settings like, screen brightness, synchro, CPU governor, etc... In my opinion check first what could be the cause of your low battery life (and what is low battery life for you???) before play with undervolting.
As said above, undervolting will get you very minor battery life increases.
More than likely you have an issue, or its just your setup and usage giving you the battery life you are seeing.
Undervolting will not change any of this.... You'll gain only minutes of battery time.
Try some troubleshooting in the below thread to see if you have an issue, or how to setup for better battery life. Read through it a bit, from the last page and work back a bit. You can post meaningful screenshots there too. From gsam or BBS.... not the stock battery screen, it has no real useful info for finding issues. Good luck!!
http://forum.xda-developers.com/showthread.php?t=2509132
Nexus 5 Battery Results
I've been undervolting many systems for many years, primarily Linux desktops and some servers, and the primary benefit is that you get less heat output which means when running cpu-intensive tasks the temperature climbs slower so the throttling of the clockspeed kicks in later, so your phone will be faster in certain situations. If you take a phone which has been idle for a while and run a benchmark, and then immediately run that benchmark again, the 2nd time gets a lower result as the phone is still hot from the 1st. This makes drawing conclusions about settings really dificult but it illustrate that throttling from heat is affecting speed.
For most users their perception will be the phone runs cooler.
You do undervolt at each step in the processor's frequency, and each step is a trial+error activity, the throttling I mention means finding a stable under-volt at the higher frequency which is labour-intensive,i.e take the max clock, and undervolt it a little, run a benchmark which forces it to run at high clockspeed, and if it passes that test then run it again at the next step down in frequency. Once you've got the most stable top clockspeed, then do it progressively for all the other voltages on the way down.
In some platforms in Linux and Windoze, we wrote scripts which save the stable voltages and then undervolts a little and runs a stress-testing benchmark and if the system hung it wouldn't save the current voltages so the previous higher voltages were safer, stick that script in a startup script area and leave the compute to do many self resets, and you've calculated your device's voltage range. I wonder if someone has that done for Android??? For a laptop the FAN would run slower saving battery time and for laptops that would lead to say 20% better battery life but on a phone it won't make much saving as no fan.
Your phone will run most of its time (like 95%) at its lowest frequency, so for effort/benefit just focusing on dropping its voltage will gain the most in the phone running cooler.
Battery life improvement is marginal, if you look at your battery stats its down to your application settings and screen brightness, i.e. how you use and what you do with your phone. So if your battery life is bad, use your phone less!
I carry a slim USB battery, it is the $/effort/benefit the best thing you can do, $20 doubles your battery life, if you get one with a 1.5A-2A output in just a few minutes when the phone doesn't mind a battery attached, will dwarth every possible tweak and hack anyone can form in benefit.