Related
hey guys, just wondering will using a lower vsel damage my cpu and/or battery?
i have previously beein using milestone overclock on 1ghz and 60 vsel and am adding setvsel into the mix, also any ideas on starter settings? thanks
also could someone just give me a heads up on what vsel actually IS
I don't believe there are any studies that show effects of long term use of lowering the voltage, which is what you are doing with vsel in order to save battery juice...or you could increase the voltage but that defeats the purpose and also heats up the battery which leads to shorter life span. Many use it without reporting any damage to battery or cpu, I believe it's safe (however, if you are overheating you might fry the battery or cpu, so you'll need to moniter and play with settings to get the desired effect without any overheating issues).
With regards to setvsel, there are reported issues from users with different roms...from what I've read (and you can do your own research to see if this is what you are seeing...this is the conclusion that I've come to by reading a lot of threads), it is better to use milestone to overclock and setcpu to lower the vsel.
With that being said, I've used them all and like setvsel so keep going back to it...but I've been having some issues lately so I've removed setvsel to see if that is what is causing some problems (too early to tell).
Oh, and as for settings...pop on the overclocking/undervolting thread in the development section to see a lot of different settings and remember that what works for one user might not work for you...you'll have to experiment a bit to find your ideal setting.
oh okay i think i might go back to my old settings with milestone overclock and setcpu and just lower the vsel! i was under the impression for some reason that lowering the vsel would heat the battery. Thanks!
I'm no expert to be honest, I'm more of a research kinda person. From what I've researched, undervolting can help keep temps down, and may particularly help when you overclock (as overclocking is stressing the cpu to go beyond it's normal operating design hence it may heat up...supplying it with less power, or voltage, is what helps keep the temps down.
Of course, this is given you find the optimal setting for your phone, and as it seems from reading through these forums, many users have experienced completely different results using the same settings (i.e., one user will have a stable setting without any problems while another user on the same rom using the same settings will have crashes and/or issues like overheating). Doesn't seem right, but it is what it is
yeah ive read through most of that stuff too, i went down to 1ghz at 51 vsel, seeming stable, but i decided to go with 54 anyway
1.1 GHz @ Stock vsel for over a month without any issues...I hope it lasts.
Sent from my MB525 using XDA App
Hi,
I've also read a lot regarding the underclocking 'dangers' but couldn't find anything to prove that there is such an issue. I think that it is an urban myth spread everywhere by people asking if there is a danger with low vsel [but that are never getting a positive answer on it].
The only thing I found using setvSel is that I had to first install Milestone Overclock and load its module prior to start setvsel. There is a way around it, but requires you to copy files in the system folders and change their permissions. I find that my way is much easier.
As far as over-heating goes, it's an overclocking thing; not underclocking.
My Defy is set at 900Mhz and really, I don't see the point of going much higher: everything runs smooth and lag free already.
vsel: 21/300; 32/600; 43/900 - 90% up_threshold
Been like that for about a month now and never experienced any problem at all.
The underclocking is great for saving battery; no exact numbers to give here but it feels like my battery now last 2 times longer. I can easily get 4 days between charges with low/moderate usage and would get to 6+ days "IF" I could stay away from games and having the screen ON for long sessions of browsing/video watching.
I tried SetCpu before but I didn't like the interface; the simplicity of SetvSel is really nice.
i use setcpu for scaling and profiles, and run 18/300, 36/600, 50/1000 stable and smooth as
Undervolting is not a bad thing at all. It means less Watts consumed for running (Watts = Voltage x Amperage), less of your battery consumed.
Ussually companies test a large batch of components and how they react on different voltages and freqvencies, and then they decide for a voltage that works with all components and that is safe for all cases. Eg. when they have different CPU speeds and thus different options for CPU's this is one way to decide which one work at 3GHz and which one at 2.7 GHz (the other one is demand for components).
Phisically you will not have any problems and you can't damage your phone by undervolting, so no problem here, only possible software problems if you go too low.
Advantages :
+ Lower processor temperature
+ Lower phone temperature
+ Longer battery time
+ Longer components life
Disadvantages
- Stability issues (freeze, artefacts, slowness)
maxi2mc said:
Disadvantages
- Stability issues (freeze, artefacts, slowness)
Click to expand...
Click to collapse
You know, I was recording a video and when playing back noticed that there were squiggly lines that went through the video a couple of times (in a two minute clip). This was the first time I saw this...and have recently lowered vsel by 2 on vsel3...could that be the artifacts that you are mentioning?
I just figured it perhaps I was too bouncy with the phone while recording making it glitch...but now that I see this post I'm thinking maybe I undervolted too much...what do you think?
My settings: 54/1000 44/700 28/300
I know what people mean by same settings don't work for every phone even if it's the exact same model. My Defy won't underclock as much as others. I'm using SetVesel, and I've been able to drop 5 points from each, and that's about it before it reboots itself. I only tested undervolting, but I mainly overclock to get as much speed as I can, and give it enough juice to run super fast. I'm current running [email protected], [email protected], [email protected] Threshold at 75%. The highest the temp ever got was 112F, and that was after playing a game for about an hour. Usually it stays below 90F for normal use. I get around 17-20 hours out of it with screen on time at about 3 hours @ 50% brightness. I've been running these settings about a month, and have not had any issues.
If you put something like 100vsel will the phone accept and then burn? Is there any protection? Does anyone know what's the highest acceptable vsel?
Just for curiosity...
im pretty sure 80 is the highest you should EVER use and that'll significantly increase the chances of your phone burning out. @bobbyphoenix you should be able to lower your vsels a fair bit or your really unlucky! i run a lower vsel for 1ghz than u do for 700mhz smooth and stable
stewi21 said:
im pretty sure 80 is the highest you should EVER use and that'll significantly increase the chances of your phone burning out. @bobbyphoenix you should be able to lower your vsels a fair bit or your really unlucky! i run a lower vsel for 1ghz than u do for 700mhz smooth and stable
Click to expand...
Click to collapse
CM7, rather non-technical person here. I seem to have a very happy phone at setvsel settings of [email protected], [email protected], [email protected], 86%. Been running this for the month or so since I rooted and the phone feels like it was made for this config. I've never seen the temp above ~32c. My 2¢.
This is actually a copy of a (long) post reply I did in another thread a little while ago but heck, there are lots of posts and questions about battery life and I have 10 tips or things I do that maybe help to some so here it is...
( This was the original question:
What's a good figure for battery life on the GS3? The best I've got is about 31 hours using on demand and bfq. Any one got better life using other settings? I heard someone getting about 43 hours life but that seemed to be a little unbelievable.)
******************
What you reported is definitely "the average". Most actually only get a day, if they're lucky of moderate use and have to plug in before sleep every evening and get going on charge in morning. So its more like 15 hours actually. And your 31 max is a very common high end for people who've stretched it out.
I'm not sure if you're stock rom or not and if rooted either but that makes a big difference.
I'm rooted ( and would ALWAYS RECOMMEND ROOT FOR EVERYONE EVEN IF NOT FLASHING ANY ROMS AND STAYING ON STOCK. The ability to have full control is important.
Changing kernels and more importantly, undervolting, will give you that longer life you're looking for.
I'm currently on KyanROM with either Ktoonez or Faux kernel (heavily tweaking and testing both) and have this phone beautifully undervolted to exceptionally low and very stable mv numbers! Thus getting me that lovely 36-45hour average - on stock battery - (you mentioned you saw posted elsewhere - yes it is possible and many are doing it). I basically only need to plug in every OTHER EVENING or night between 6pm and midnight depending on usage and I'm a moderate to heavy user (with a lovely 3-5 hours of screen time as well) AND I also have my phone overclocked to 1.8Ghz! Surprisingly, the oc doesn't make much battery life impact at all because the phone isn't constantly having to run at high levels, only in short spurts. Actually, due to rooting and kernel change I'm able to have my phone run as low as 192Mhz (actually lower now - 96 - since latest Ktoonez kernel update) during much of its general activity and deep sleep ( which I get a ton of as my phone basically always goes into it when the screen goes off). This saves me A LOT of battery life.
I also use LTE, which is actually one of the biggest if not the largest battery hog, next to screen time of course. But with that being said I only use it when needed and have it turned off when not in use.
As for my peak I was able to squeeeeeze out 87 hours once, on my stock battery BUT that was with some abnormal(for me) measures that really help conservation. Ie, no LTE, under clocked to 1.2Ghz for good part of the three days, much less then normal screen time over the period of which I used it at lowest level with even further reduction via screen filter, I actually used airplane mode during my three overnight sleeps (which I seldom use but if you can hack it, do it! It can really save battery overnight. My current setup basically SIPS MY BATTERY AT 1% EVERY 3.5-4 HOURS OVERNIGHT WHEN IN AIRPLANE MODE), mobile data was off for most of time but did use my wifi at normal level (wifi uses less especially if good signal with few reconnects/scans), used my typical low UV numbers, kept my notification updates/syncs/wakelocks to a minimum and lastly kept my memory virtually clear if unnecessary background apps.
Doing ALL of this allowed me to get OVER THREE DAYS BATTERY LIFE. But keep in mind I seldom do many of these battery saving tips on a regular basis but some do and if you can, they WILL work to extend your life substantially!
I'll give you my general UV mv range numbers and the typical everyday simple battery saving methods I use.
1.My voltage at lowest clock of 192mhz=800mv with gradual (smooth and almost linear curve) increase up to a mere 1200mv at a whopping 1.890Ghz clock.
I use NOOP scheduler with ONDEMAND governor most of the time, sometimes SmartassV2.
My screen off and deep sleep use this lowest 192 clock speed and with no wakeup lag.
(Update - as mentioned, now on latest Ktoonez kernel which has lower min clock and higher max with mote voltage control too so my min is now 96Mhz at 770mv and max of 1998Mhz at 1235mv)
2. I use my screen at 0% brightness most of the time (except when outside or in high lighting environment). I use the brighrness widget app to control this as it is easier and works better then stock settings. I actually even further reduce my brightness with Screen Filter App. That app is awesome and often use it solely for brightness control because it has full control and can dim it to basically full black if wanted. Which is MUCH lower then stock control. Fyi I use my phone a LOT more at night or in dark environments thus allowing me to dim screen HEAVILY yet it still is actually plenty bright with ample contrast in dark environments to do everything. This saves on my battery HUGE!
3. I use LTE when needed and GSM/HSPA+ when not. Seldom turn off mobile data altogether. I do turn off wifi when out and only using mobile data but do remember wifi does use less battery then mobile and both work better and drain less with better signals. If your wifi or mobile signal is low or has to reconnect often that puts heavy strain on the battery.
4. I use Screebl app to have my screen turn off when not in use. Its a great liitle app. Basically let's you turn down screen timeout to 15 seconds or less so screen is never unnecessarily on but it always stays on when in use due to the accelerometer and it knows when the screen is not flat on table! Its very annoying when browsing or doing stuff where screen isn't touched for long periods and the screen goes to sleep! But this stops that! So its always on when upright or in use and when phone down it turns off immediately. But this does save battery by not leaving the screen on unnecessarily when not in use.
5. Very important step and can take some time and research but making sure to keep partial wakelocks and apps keeping device awake to a bare minimum! DEEP SLEEP IS VERY IMPORTANT TO SAVE BATTERY! You basically want it to go into that every time your screen goes off and to stay in it uninterrupted for as long as possible. And many users phones are NOT making it into deep sleep due to partial wakelocks and they don't even know it or how to fix it. Not getting deep sleep can unnecessarily kill your battery!
I use a few tools here: Better Battery Stats/GSAM Battery Monitor/Battery Monitor Widget from within System Tuner Pro (which is my also my main and highly recommended tuner app for CPU oc/uc and UV,etc.).
These apps really help to determine what, if any, apps are causing partial wakelocks ( displaying in wake number amounts and overall wake time) allowing you to determine what to do to fix the problem and let the phone gets as much battery saving deep sleep as possible. One other app that many use and is very popular and effective is Juice Defender. I recently started using it too and its quite powerful and customizable. Definitely another tool in the arsenal.
6.I'm not big on auto app killers and actually recommend against them as Android ICS does this already very effectively but do keep in mind that the more active background memory that is used, the more the battery is drained. So I personally kill unnecessary apps myself from the background whenever possible to save a little battery here and there. Using the apps listed above in #5 can really help to detect a nasty background app or service that is quite possibly unknowingly using a ton of CPU and/or memory, thus draining more battery and also often just slowing down your phone!
7. For those who can use it Airplane Mode is a big saver! Try overnights if wanted as long as missing notifications, emails, calls, updates, etc is alright for you. I seldom use it but it does help.
8. I almost never use my Bluetooth and GPS but when I do that is the ONLY time they are on. They get turned off immediately and really be careful with the GPS in particular because you might be surprised how many things on your phone will use it in the background, sucking your battery! Google Maps and "Network Location Service" can use your GPS or run often in the background waking up your device.
9. Be careful with sound and vibration levels. Haptic feedback too. I don't do much here but its another tip nonetheless.
10. Lastly is treating and charging your battery right! I found an amazing site linked down below in a couple of articles that really explains these batteries and how they work in a very in depth technical level this is still not too hard to follow. Aside from the two links I posted check out the others on the left menu as there is a ton of useful and educational info!
http://batteryuniversity.com/learn/article/how_to_increase_the_runtime_of_your_wireless_device
http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
Btw I've just received both my 3300mAh and 4400mAh capacity batteries. So I have much testing to do on those too and I plan on reporting back on them as well. Also with screenshots for data and proof...I can and will also post screenshots for all of the numbers and stats I've posted here today with my personal phone/battery accomplishments.
Hope this helps some of you out there because yes this phone can be known for terrible battery life but it CAN be tweaked to SUBSTANTIALLY IMPROVE that life to high standards and keep up with the best of them!
Sent from my SGH-I747M using Tapatalk 2
Here's a little update:
the latest Ktoonez kernel is absolutely amazing on many roms on this phone for both performance and battery life!
Here's some info on my setup and stats:
I can run the 2.1Ghz step but not yet 100% stable so I'm more then fine with 1.998 and every other clock works perfectly! And my battery life is just amazing with the UV I can do.
My levels are as follows:
96 min - 1998 max
780mv min to 1185mv max w/ variances of -55mv to -135mv below stock on all the steps in between. This = incredible! Sweet performance AND battery life =
I've got this thing as low as using only 14mA during deep sleep! I use a 4300 mAh battery now so that's only 1% every 3 hours. So I basically only use 2% when I crash at night and get up the next morning. And I now easily get 2-3 days with fairly heavy use and that includes 7-8+ hours of screen time. Heck, at these low levels I could technically be in standby for almost TWO WEEKS! (Actually 12.5 days or 307 hours). That's amazing!
I'm now getting the performance and life I should be and have always wanted on these things!
Sent from my SGH-I747M using Tapatalk 2
Are you using the ktweeker app? Care to post a screenie of your voltage settings?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I just did over in the KyanROM thread... here's the link.
http://forum.xda-developers.com/showthread.php?p=30897840
Sent from my SGH-I747M using Tapatalk 2
Wow I really need to try these tips, I'm nowhere near these numbers. I need to charge in the middle of the day usually. Thanks for the info!
Sent from my SGH-I747 using xda premium
EskimoRuler said:
Wow I really need to try these tips, I'm nowhere near these numbers. I need to charge in the middle of the day usually. Thanks for the info!
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Well doing some or all of these things should help a fair bit and on your STOCK battery (I assume) you should at least be able to get into the second day on regular basis.
When I used my stock (before getting 4300/4500 mAh batteries) I was finally able to get 35-45 hours out of it and usually only having to plug in to charge on the second late afternoon to evening before bed...
And now with (a good quality) extended battery I can push this thing heavily and get 2-3 days regularly but like stated, gotta have a good rom/kernel/UV/and a few of those battery saving habits.
Sent from my SGH-I747M using Tapatalk 2
Wow!! im going to try this thank you very much for sharing this my battery last 2 days with moderate use i have a extended batterry but i will love to extended more jajaja thanks again
question? what app do you use for undervolt?
Enviado desde mi SAMSUNG-SGH-I747 usando Tapatalk 2
any setcpu profiles? thanks
Enviado desde mi SAMSUNG-SGH-I747 usando Tapatalk 2
Mind sharing your voltages?
meaintsmart said:
Mind sharing your voltages?
Click to expand...
Click to collapse
Already did..in the link up above in the 4th post
Sent from my SGH-I747M using Tapatalk 2
CPU sleeper + juice defender ftw.
thanks will keep this in mind
I followed your UV settings and yes it works great.
One issue I found was that my mp3 ringtones, youtube, and flash video playing in a browser caused some serious audio distortion. Mp3's playing from my music player were fine and videos with my video app were fine too.
I was able to change my mp3 ringtones to ogg files and no more distortion, but youtube is a needed app.
Anyone else notice this issue?
The second I put my UV settings back to stock numbers the audio was fixed.
So after toning the voltage down some I've noticed much better battery life. But I have also noticed a bunch of screen flickering. I'm on task and kt's AOKP JB Rom. I OC to 1.890 and used the voltages that you posted from the kyan thread. I'm going to set voltage to stock and then work down from there to see where I have better performance.
Sent from my SGH-I747 using xda premium
Well if ur getting audio distortion or video issues then certain levels of UV are too low and not stable and must be adjusted.
All the levels I have even at the low levels are completely stable with no issues whatsoever and amazing battery life..this phones hardware is very robust...lucky I guess
Sent from my SGH-I747M using Tapatalk 2
Good post, thanks!
I don't want to be that guy that posts battery charts. Ktoons seems to believe that I have a bad phone since the battery drains quickly like in 3 hours with his kernel uvd. I have tried to battery stats but have not found any irregularity as far as rogue programs. Most of my cpu on regular AOKP is usually at 384 and 1.5
Ktoons says it is not normal. Can you guys affirm this. If so im refurbing on the quick .
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SGH-I747 using xda premium
Followed a lot of these tweaks and everything seems to be helping! With some light to moderate use on a qcell 4500mah battery I'm only down to 75%.
Sent from my Nexus 7
I thought fauxs kernel u can't adjust the voltages? My phone hates ktoonz kernel. If I lower it anymore then 384 I get bad audio distortion. Now with faux my phone is fine but I want to be able to undervolt it. Is there a way to do that?
Sent from my Galaxy Nexus using xda app-developers app
Any idea why my phone doesn't want to keep the overclocked/undervolted CPU settings ? It's not rebooting or anything, but after awhile I'll go into a CPU tweaking app (KTweaker or System Tuner) and everything will be back to stock settings.
I'm on AOKP with Ktoonsez kernel.
Hey all, this is a thread I saw on different forum and think it is would be good for noobs like myself to benefit from. How to undervolt your CPU and also post your Galaxy Note 2 specific results. I have tried these next steps, and so far I'm doing okay (can't give an accurate results on battery life yet). Like I said (I'm not ashamed to say I'm a noob) but if others can throw their two cents in, we can all learn and this thread can be useful. The next part was cut and paste d from other forum. And I deleted the url for the kernel and root
Prerequisites:
1. Must be rooted and recommended kernel
2. Download and install System Tuner
3. Download and install Stability Test
Steps:
1. Open System Tuner and select CPU
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Drag the slider shown in the picture to overclock or underclock CPU. In this picture we are overclocking to 1.8ghz
3. Select Voltage at the top to get to CPU voltage settings.
4. Ok, here select the buttons as they are in the picture.
a. Select the Green circled button to save current stock default settings.
b. Select the Yellow circled button 4 times exactly to reduce the millivolts by 100.
Stability Testing:
Now we really should make sure that it can handle it under load right? :silly:
1. Open Stability Test and select CPU+GPU Stability Test.
2. Select Full Details - Proceed.
3. The app will now start stressing your cores. I waited until at least 10 cpu passes before quiting the app...
Cliffnotes:
-By default, your settings will revert back after you restart your phone. You can set them to load at boot, but don't do this unless your absolutely sure that they're stable!
Open System Tuner - CPU - Menu key - Settings - Active Tweaks - Reapply CPU Settings - On Boot Completed
-Whenever i tried to lower the mv more than 100 below stock at 1.8ghz, my phone rebooted
-I am in no way responsible for anything that might happen after performing the above, even if you start your sentence with the word "but"
-here's stock settings in case you need to revert
[/QUOTE]
This is an interesting project but I would think that the average user would not need this as battery life is pretty good. Speaking for myself, I am able to get through the whole day without any issues.
Of course there might be other reasons why someone would want to do this.
Doc
Thanks
Sent from my SGH-I777 using xda premium
DocEsq said:
This is an interesting project but I would think that the average user would not need this as battery life is pretty good. Speaking for myself, I am able to get through the whole day without any issues.
Of course there might be other reasons why someone would want to do this.
Doc
Click to expand...
Click to collapse
from what i've read, undervolting save very little battery time as the processors are pretty efficient anyways. i don't have actual numbers, but i'd guess you'd get a few extra minutes - which some may really need.
it's that freaking gargantuan screen that sucks the most juice. there used to be a mod to undervolt displays. they had it working on an OG galaxy tab. i never really seen it used anywhere else.
I have an international version of galaxy note 2. I'm currently using AllianceROM and Perseus kernel. And my stock voltage is way way higher than yours. Like 1400mV mine, 913mV yours. Can I undervolt my note 2 to same specifications like yours? Thanks.
This is interesting but setcpu when I had it on my last phone worked awesome and was very easy to use.
Sent from my Amazing Galaxy Note 2!
rjisanandres said:
I have an international version of galaxy note 2. I'm currently using AllianceROM and Perseus kernel. And my stock voltage is way way higher than yours. Like 1400mV mine, 913mV yours. Can I undervolt my note 2 to same specifications like yours? Thanks.
Click to expand...
Click to collapse
You is 1400 mV on 200 MHz? It's probabky 1400 on 1.6 ghz.
Sent from my SCH-I535 using xda premium
I also have Perseus kernel overclocked but still have great battery life. Thanks for the tip though might try it and compare the difference just in case.
I agree with DocEsq.. It is interesting indeed, but is it really necessary?
Can you overclock it?
My note 2 seems to be charging forever after undervolting. I'm talking for about 6-7hrs charging time here. What seems to be the problem? I'm using Perseus kernel. TIA!
Sent from my GT-N7100 using Tapatalk 2
I once conducted a test with my evo3d. I basically ran an amp meter inline with the battery. Measuring the exact power consumption. I dont remember the exact specs, but undervolting and underclocking my phone compared to stock made a very minute difference in actual power consumption. A difference of about 8-15ma. This was during a CPU full load scenario for about 10 seconds. Even loading the CPU with the screen off to take as many variables out as possible it was very little difference. During normal operarion the power consumed was virtually identical.
So the 2 to 3% of the day (overall time) your phone is actually under HEAVY load, it won't make much difference. It did make a performance impact. So not much benefit, just reduced performance.
Now overclocking and/or overvolting did make a larger difference in consumption at high constant load.
Want to ACTUALLY make a large impact on your battery life? Make sure you don't have any apps preventing your phone from sleeping and run the absolute lowest screen brightness you can stand.
YMMV.
Sent from my Galaxy Note 2 using Tapatalk 2
The benefit I found from undervolting isn't better battery life, it's reduced heat which in heavy use provides better performance due to no cpu throttling. I'm running 1800mhz using less battery than 1600mhz and with same temps as stock. Very stable, been running this for a month now at least.
Action B said:
The benefit I found from undervolting isn't better battery life, it's reduced heat which in heavy use provides better performance due to no cpu throttling. I'm running 1800mhz using less battery than 1600mhz and with same temps as stock. Very stable, been running this for a month now at least.
Click to expand...
Click to collapse
What app did you use to undervolt?
Sent from my Amazing Galaxy Note 2!
yankees45us said:
What app did you use to undervolt?
Sent from my Amazing Galaxy Note 2!
Click to expand...
Click to collapse
I'm using the stweaks app that comes with perseus kernel.. I've undervolted quite a bit and I get better battery life.. Still not quite as good as I had stock, but definitely a lot better for being over clocked.. I just reduce each level to the level below it and run for a few to check stability and keep going from there.. So far I have had no trouble at all with undervolting.. Certainly nothing like I did with my elte.. Here's where I've been for almost a week as well as today's battery results so far with Pandora playing over 3 hours straight and moderate use..
Sent from my SPH-L900 using Tapatalk 2
Yeah, just to let you know that there certainly isn't a linear correlation between undervolting and underclocking and power usage. That might have been the case in simpler times, but with modern multi-core microprocessors, you might actually be decreasing battery life by screwing with your clock rate or voltage. Yes, the defaults err on the side of caution, but it's a whole lot of work for little to no gain.
For example, by reducing your phone's clock rate, you might actually be forcing your phone to be spending more time at load; thereby not allowing it to fallback to its sleep state. There is also something called the power wall, where an increase in operating frequency requires an exponential increase in power. However, the reverse is also true. It can be counter-intuitive to think of it this way, so a practical example is how on a 100 mile trip, a 25 mpg sedan saves 4 gallons of gasoline over a 12.5 mpg SUV. However, over the same distance a 50 mpg hybrid saves only 2 gallons over the 25 mpg car. By that same logic, a mythical 100 mpg vehicle would only save 1 gallon of fuel. It's the law of diminishing returns. Then of course, there are the stability issues that you should take into account.
There is a lot that happens behind the scenes regarding power management. Your phone is capable of intelligently scaling it's processors, voltages, and frequencies up or down all based on current and expected demand. There are people who spend a lot more time doing this for a living, and the idea that you can do it better is probably a falsehood. If you want MOAR POWER, by all means overclock/overvolt it (just don't fry it), but trying to get an extra couple minutes of run time is likely a waste of some hard work. It's the software that kills your battery, not the hardware.
Talking about computer architecture can be complicated and boring, but start with searches on "rise time" and "logic level transitions" if you want to want more background.
Action B said:
The benefit I found from undervolting isn't better battery life, it's reduced heat which in heavy use provides better performance due to no cpu throttling. I'm running 1800mhz using less battery than 1600mhz and with same temps as stock. Very stable, been running this for a month now at least.
Click to expand...
Click to collapse
Interesting... whenever I'm dling using a torrent client my phone gets a nasty fever and I've gotta set it down somewhere as it will literally make me sweat, lol. I do b there think I'll be undervolting just for that specific circumstance but that is a very interesting concept...
anishannayya said:
Yeah, just to let you know that there certainly isn't a linear correlation between undervolting and underclocking and power usage. That might have been the case in simpler times, but with modern multi-core microprocessors, you might actually be decreasing battery life by screwing with your clock rate or voltage. Yes, the defaults err on the side of caution, but it's a whole lot of work for little to no gain.
For example, by reducing your phone's clock rate, you might actually be forcing your phone to be spending more time at load; thereby not allowing it to fallback to its sleep state. There is also something called the power wall, where an increase in operating frequency requires an exponential increase in power. However, the reverse is also true. It can be counter-intuitive to think of it this way, so a practical example is how on a 100 mile trip, a 25 mpg sedan saves 4 gallons of gasoline over a 12.5 mpg SUV. However, over the same distance a 50 mpg hybrid saves only 2 gallons over the 25 mpg car. By that same logic, a mythical 100 mpg vehicle would only save 1 gallon of fuel. It's the law of diminishing returns. Then of course, there are the stability issues that you should take into account.
There is a lot that happens behind the scenes regarding power management. Your phone is capable of intelligently scaling it's processors, voltages, and frequencies up or down all based on current and expected demand. There are people who spend a lot more time doing this for a living, and the idea that you can do it better is probably a falsehood. If you want MOAR POWER, by all means overclock/overvolt it (just don't fry it), but trying to get an extra couple minutes of run time is likely a waste of some hard work. It's the software that kills your battery, not the hardware.
Talking about computer architecture can be complicated and boring, but start with searches on "rise time" and "logic level transitions" if you want to want more background.
Click to expand...
Click to collapse
Like the way you put that. Good analogies there it just seems like the other day that undervolting was the hip thing to do. Technology just moves at such a wonderful pace though. Just one little FYI though, since i do like you analogy i would like to point out that the law of diminishing returns actually refers to something else entirely. I know, I know, nitpicking, but it's just that everyone is always off the mark with that one and, well I guess I'm just an anal ahole (and an economics major, ,which I guess just overall makes me an a hole, ,lol)
If you have ever pulled apart a laptop and saw how much thermal paste the engineers at the factory "designed" for their to be on there, or seen the air/fuel ratio most cars roll off the lot with, or ever replaced an intake in a vehicle with a high performance unit I'm not sure you would feel the same way about you yourself not being to do a better job.
I get the point, and I believe often there is validity to that point, but sometime things just aren't that simple. This is where power gains come from in tuning a car (which i do). This is where efficiency is raised by removing restrictive components in a vehicle (intake, exhaust, etc) and where cooling performance is increased on a CPU with the proper application of a quality thermal paste.
Whenever time is money, and you are deciding between your bottom line and something that works and something that works as well as it can, shortcuts are made and corners are cut. Perhaps they could have spent another 200 hours for the team to absolutely optimize the processor for each device, but the cost would have been an additional $20,000 dollars. This is not always the case, but with processors I think it is. I will undervolt everytime and I do take objective measures for battery and I agree gains are relatively small. For cooling, I found the difference to be very significant at 1800, mhzI didn't check at 1600mhz, however. I can run a full Antutu benchmark as much as I want at room temperature and never exceed the throttling point (70 C if i remember correctly). Now, I am in no way saying these are facts, these are opinions, so I could be wrong of course.
Psychotic-Cerebellum said:
Interesting... whenever I'm dling using a torrent client my phone gets a nasty fever and I've gotta set it down somewhere as it will literally make me sweat, lol. I do b there think I'll be undervolting just for that specific circumstance but that is a very interesting concept...
Like the way you put that. Good analogies there it just seems like the other day that undervolting was the hip thing to do. Technology just moves at such a wonderful pace though. Just one little FYI though, since i do like you analogy i would like to point out that the law of diminishing returns actually refers to something else entirely. I know, I know, nitpicking, but it's just that everyone is always off the mark with that one and, well I guess I'm just an anal ahole (and an economics major, ,which I guess just overall makes me an a hole, ,lol)
Click to expand...
Click to collapse
The TIM wasn't put on there by the engineers who designed the chips; they are put there by workers being paid next to nothing.
Your phone doesn't have a CPU, it doesn't even use thermal paste; it's usually just a rubber contact patch and passive heat dissipation. This actually brings another point where overclocking can sometimes reduce performance due to throttling by thermal constraints (why our phone has such a low GPU rate than what it is capable of in other phones with better thermal envelopes).
You aren't replacing the SoC, you are changing the software that determines how to set the voltage/clock multiplier. The car analogy isn't valid.
And I stand corrected regarding the Law of Diminishing Returns; never paid attention in macro-econ. I think was because my prof. was more interested in forcing his political ideology upon us than actually teaching the subject. :silly:
EDIT: Keep in mind, the engineers rarely get what they want. The product the consumer ends up getting is usually dictated through a collaboration of what the business and marketing teams want. The engineer might request a large cooler clamp with a perfectly lapped surface and a carbon-based TIM. In reality, the consumer gets a dinky fan with melt-on TIM and retention springs. Money talks.
anishannayya said:
The TIM wasn't put on there by the engineers who designed the chips; they are put there by workers being paid next to nothing.
Your phone doesn't have a CPU, it doesn't even use thermal paste; it's usually just a rubber contact patch and passive heat dissipation. This actually brings another point where overclocking can sometimes reduce performance due to throttling by thermal constraints (why our phone has such a low GPU rate than what it is capable of in other phones with better thermal envelopes).
You aren't replacing the SoC, you are changing the software that determines how to set the voltage/clock multiplier. The car analogy isn't valid.
And I stand corrected regarding the Law of Diminishing Returns; never paid attention in macro-econ. I think was because my prof. was more interested in forcing his political ideology upon us than actually teaching the subject. :silly:
EDIT: Keep in mind, the engineers rarely get what they want. The product the consumer ends up getting is usually dictated through a collaboration of what the business and marketing teams want. The engineer might request a large cooler clamp with a perfectly lapped surface and a carbon-based TIM. In reality, the consumer gets a dinky fan with melt-on TIM and retention springs. Money talks.
Click to expand...
Click to collapse
1. The voltages are set by an engineer, that is what I was referring to.
2. The CPU thing was an analogy as was the car. Not a direct comparison. The analogy is referring to how there is set fuel and timing tables just like there is set voltage tables, both might not be the most efficient from the factory, tweaking them can improve things. How is this completely not valid?
Hi
so what are your undervolting results of your S4 Mini?
A quick test allowed me to go -200mv. (crashed at -225mv). Now I am running StabilityTest at -150mv @ 1728 MHz (performance governor), while charging and wrapped into a winter pullover
30 minutes have passed and still running. I guess I will go up to 2 hours before lowering to -175.
I wonder if you have big undervolt differences between lower and higher frequencies?
neustadt said:
Hi
so what are your undervolting results of your S4 Mini?
A quick test allowed me to go -200mv. (crashed at -225mv). Now I am running StabilityTest at -150mv @ 1728 MHz (performance governor), while charging and wrapped into a winter pullover
30 minutes have passed and still running. I guess I will go up to 2 hours before lowering to -175.
I wonder if you have big undervolt differences between lower and higher frequencies?
Click to expand...
Click to collapse
Did you set difference voltages for every frequenzy or did you use the two buttons at the top and lower every voltage the same? My device crashes if i go -200. My max freq. is 1566 and my min. freq. is 162. As governor I use smartmax and I/O scheduler is fiops I also underclocked my Gpu to 192 Mhz.
Not yet. I want to find a working global value and then tweak at 162MHz and 700MHz.
Did you limit your max frequency at 1566?
Flatric said:
I also underclocked my Gpu to 192 Mhz.
Click to expand...
Click to collapse
What app did you use for that?
neustadt said:
What app did you use for that?
Click to expand...
Click to collapse
Yes I limtited it at 1566, I used also Kernel tweaker to underclock my Gpu
Flatric said:
Yes I limtited it at 1566, I used also Kernel tweaker to underclock my Gpu
Click to expand...
Click to collapse
Oh, ok. So you limited your max gpu clock. Maybe I will try this out as well. But I would need to find out how far I can go down. Usually I dont play any games so I probably dont need the highest clocks on my gpu. But I do watch the occasional HD video.
In the end it might not help save batterylife, if my GPU doesnt clock that high anyways.
I would rather like to adjust the different speedsteps of the gpu just like on the cpu. ExTweaks looked processing, but doesnt seem to work with f4ktion kernel.
neustadt said:
Oh, ok. So you limited your max gpu clock. Maybe I will try this out as well. But I would need to find out how far I can go down. Usually I dont play any games so I probably dont need the highest clocks on my gpu. But I do watch the occasional HD video.
In the end it might not help save batterylife, if my GPU doesnt clock that high anyways.
I would rather like to adjust the different speedsteps of the gpu just like on the cpu. ExTweaks looked processing, but doesnt seem to work with f4ktion kernel.
Click to expand...
Click to collapse
Please tell me your result if you finished
neustadt said:
Hi
so what are your undervolting results of your S4 Mini?
A quick test allowed me to go -200mv. (crashed at -225mv). Now I am running StabilityTest at -150mv @ 1728 MHz (performance governor), while charging and wrapped into a winter pullover
30 minutes have passed and still running. I guess I will go up to 2 hours before lowering to -175.
I wonder if you have big undervolt differences between lower and higher frequencies?
Click to expand...
Click to collapse
I don't understand what you are trying to prove with wrapping your device in a winter pullover while undervolting.
When I have to apply tests at my job for simulating mobile applications, we undervolt (the solenoid of a valve) -30% and do test at very low temperature of -25'C. Then we overvolt with 30% and run '100% duty cycle' test at high temperature of +70'C. At low temperature there is a chance of not reacting anymore, at high temperature it is the latter: the coil could be toast since it can't radiate all the generated heat away.
With the undervolt test, you should put your phone in the fridge or freezer to really seeing it's behaviour at extreme circumstances. In my opinion you are now easing the pain on your phone during undervolting, by heating it from 2 sides, by charging and heat insulating it.
jake3317 said:
I don't understand what you are trying to prove with wrapping your device in a winter pullover while undervolting.
When I have to apply tests at my job for simulating mobile applications, we undervolt (the solenoid of a valve) -30% and do test at very low temperature of -25'C. Then we overvolt with 30% and run '100% duty cycle' test at high temperature of +70'C. At low temperature there is a chance of not reacting anymore, at high temperature it is the latter: the coil could be toast since it can't radiate all the generated heat away.
With the undervolt test, you should put your phone in the fridge or freezer to really seeing it's behaviour at extreme circumstances. In my opinion you are now easing the pain on your phone during undervolting, by heating it from 2 sides, by charging and heat insulating it.
Click to expand...
Click to collapse
Thanks for the info. I tried to apply what I knew about desktop CPUs and overclocking/undervolting to smarphones. Since people cant put their desktop machines into a freezer this was new to me.
I think I found my final settings now and attached them as a screenshots. Its really convinient to apply different voltages to different frequencies. If I look at my last 48 hours of regular usage (it was the weekend and I went biking with gps and stuff) I have still 55% deep sleep state and 30% 162MHz. So this state is clearly the most important for battery saving.
I found that google maps navigation is a good real life test for undervolting. It crashed my device once, where i didnt have any issues going through a scaled stability test. this is a nice feature of the StabilityTest app, where the the test goes periodically through all selected frequencies. Maybe the crash was also related to jake3317 comment, as I was outside at 10° C / 50° F. Anyways I gave the cpu a little more juice on the higher frequencies and I hadn't had a crash since then.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've been trying to undervolt my phone using SetCpu but nothing seems to work and my phone has recently started to have huge battery drain issues.
May I know the app you guys use to set voltages for your phone? And also to test for the stability of your phone after the voltage changes?
You can use Kernel Tweaker for adjustments and StabilityTest for testing.
Whosat said:
I've been trying to undervolt my phone using SetCpu but nothing seems to work and my phone has recently started to have huge battery drain issues.
May I know the app you guys use to set voltages for your phone? And also to test for the stability of your phone after the voltage changes?
Click to expand...
Click to collapse
I use the App "Kernel Tweaker" https://play.google.com/store/apps/details?id=com.dsht.kerneltweaker
Ah, finally a decent app that doesn't crash out of nowhere. I've spent the last night trying to undervolt using Kernel Tweaker and tested using the stability test.
Unstable at -200mV, rebooting after almost 2 hours. Gonna try -150mV now
Update: -150mV was stable up to 41mins where I had to stop the test as I had to leave for work. Will continue testing tonight
Update 2: -175mV & -150mV unstable, crashing and rebooting randomly. Running -125mV now
Whosat said:
Ah, finally a decent app that doesn't crash out of nowhere. I've spent the last night trying to undervolt using Kernel Tweaker and tested using the stability test.
Unstable at -200mV, rebooting after almost 2 hours. Gonna try -150mV now
Update: -150mV was stable up to 41mins where I had to stop the test as I had to leave for work. Will continue testing tonight
Update 2: -175mV & -150mV unstable, crashing and rebooting randomly. Running -125mV now
Click to expand...
Click to collapse
If you found a stable base voltage you can do two more things: 1st. lower your minimum cpu clock to 162MHz. 2nd lower the voltage of this frequency alone a little more. for me it can take 50mv less then my base voltage. and its my most used clock besides deep sleep.
Will keep that in mind. I'm still randomly rebooting at -125mV.. Bringing it up to -100mV. Hopefully it'll be stable at this voltage!
Whosat said:
Will keep that in mind. I'm still randomly rebooting at -125mV.. Bringing it up to -100mV. Hopefully it'll be stable at this voltage!
Click to expand...
Click to collapse
Thanks please keep us updated on results. Will use it as a base.
Sent from my GT-I8190 using xda app-developers app
It may be worthy to note that every device has different undervolting potentials so you should experiment on your own too!
But I'll keep posted here
Have yet to run a full stability test but I've had a pretty stable day of using the phone at -100mV.
Will probably test while plugged in tonight when I find a reliable power source
So I've got a steady 5 hour stability test going at -100mV, with the exception of 1728 set at -115mV and 162 set at -125mV.
I've now decreased an additional 10mV across the board to see how it goes for the next 5 hours.
I'm also now using the Trickster MOD kernel app instead of the open source kernel tweaker app as I found that the open source version sometimes does not set my settings at boot (Min/Max frequencies to be exact). And the trickster mod app has the bonus of being able to control fauxsound
Whosat said:
So I've got a steady 5 hour stability test going at -100mV, with the exception of 1728 set at -115mV and 162 set at -125mV.
I've now decreased an additional 10mV across the board to see how it goes for the next 5 hours.
I'm also now using the Trickster MOD kernel app instead of the open source kernel tweaker app as I found that the open source version sometimes does not set my settings at boot (Min/Max frequencies to be exact). And the trickster mod app has the bonus of being able to control fauxsound
Click to expand...
Click to collapse
Awesome im interested to see your final results in undervolting im looking to get some more battery power
Hi there.
I have my 10 for a day now and it's my first HTC phone. Because I love overclocking and stuff I've already installed Qualcomm Trepn Profiler even though I don't even have root yet.
The SD820 is a Quadcore BigLittle with core 0 and core 1 maxing out at 1.59ghz while core 2 and 3 go to 2.15ghz.
So I've used my favorite app called stability test v2.7 and did a short run.
To be fair I've been using the phone the whole time with "normal usage" so it was already pretty warm.
But yeah, I don't know the SoC temperature, the phone itself didn't feel more like 40c.
And it dropped to 1.3ghz pretty fast. Normalised CPU load is about 70%
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So yeah. Any experiences outside from Benchmarking? I doubt that a 1.3ghz Kryo core will slow anything down if all 4 of them are working, but still. 1.3 instead of 2.15 +1.6 is a little difference.
That is unfortunate, I have seen many places mentioning how hot HTC 10 can get specially during gaming. It could be due to metal frame or maybe a software optimization issue.
@Haldi4803
thanks for this thread, can you please try the Powersaver and lets us know what changes in terms of cores configurations and CPU clocks
with the M8 HTC almost half the clocks with powersaver while keeping the core count and full GPU speed, with the M9 HTC locks into the small A53 quad cluster (which is a very bad idea considering how slow these cores are) on the X10 devices like M9+ and M9S HTC locks into quad as well and reduces the clocks to 1.2ghz turning the super smooth UI into a laggy experience
also whats the point of doing this test on an already warm device? its not really fair, can you please redo from a idle state?
This is expected. I remember the m9 had a lot of heat issues along with other devices that came with the SD810. Which is why a lot of devices went with the 808 last year. So they may have played it safe and went with more thermal throttling this year.
_ray_ said:
That is unfortunate, I have seen many places mentioning how hot HTC 10 can get specially during gaming. It could be due to metal frame or maybe a software optimization issue.
Click to expand...
Click to collapse
Actually aluminum sheds heat outward faster than plastic, glass or any other type of metal which is it's used to make engine blocks.
What do you expect from a metal slab, folks? I think these tests are silly. All they are saying is "if you pass current through metal slab, the metal slab is going to heat"...well, duh!!
As long as the phone does not shutdown during normal game play for an hour, I am fine with it throttling down to keep the temps under control. Can someone confirm that its fine to game for an hour on this phone and it still keeps functioning as a normal smartphone (calls, videos, audio, gps etc. function normally)?
devsk said:
What do you expect from a metal slab, folks? I think these tests are silly. All they are saying is "if you pass current through metal slab, the metal slab is going to heat"...well, duh!!
As long as the phone does not shutdown during normal game play for an hour, I am fine with it throttling down to keep the temps under control. Can someone confirm that its fine to game for an hour on this phone and it still keeps functioning as a normal smartphone (calls, videos, audio, gps etc. function normally)?
Click to expand...
Click to collapse
Indeed.
Also, go ahead and game for a couple of hours. Sure it throttles, doh, but it settles down rather quickly in regard to performance/temperature.
http://anandtech.com/show/10252/htc-10-battery-storage-results
hamdir said:
@Haldi4803
thanks for this thread, can you please try the Powersaver and lets us know what changes in terms of cores configurations and CPU clocks
with the M8 HTC almost half the clocks with powersaver while keeping the core count and full GPU speed, with the M9 HTC locks into the small A53 quad cluster (which is a very bad idea considering how slow these cores are) on the X10 devices like M9+ and M9S HTC locks into quad as well and reduces the clocks to 1.2ghz turning the super smooth UI into a laggy experience
also whats the point of doing this test on an already warm device? its not really fair, can you please redo from a idle state?
Click to expand...
Click to collapse
So your saying battery life wise,it's a bad idea to use power saver mode on the m9 but a good idea on the 10?
Sent from my 0PJA2 using Tapatalk
Heisenberg420 said:
This is expected. I remember the m9 had a lot of heat issues along with other devices that came with the SD810. Which is why a lot of devices went with the 808 last year. So they may have played it safe and went with more thermal throttling this year.
Actually aluminum sheds heat outward faster than plastic, glass or any other type of metal which is it's used to make engine blocks.
Click to expand...
Click to collapse
This is what lead me to run away from the M9 and Snapdragon 810. The 820 is probably nearly identical to that chipset design one would assume.
Only once we had kernel source and could under volt the CPUs, or turn some cores off did 1) the heat finally start to go away on the M9, and 2) the battery would stop being eaten up by the processor.
Would barely make it 8-10hrs on full battery on the M9. But what did turning off cores/undervolting do? Reduced performance of course. So, kind of defeats the purpose.
Sad to hear this. But I think this is going to be a trend and normal comment from people about the M10/Snapdragon 820.
Was wondering in the back of my head about the M10 and processor if anything has changed. Looks like it hasn't.
Lol, HTC Software sure doesn't like Benchmarking.
You can see the cores throttling 20sec after the Benchmark starts. But then when I tab out and it runs in the bg you can see the spike to 2.2ghz at the end.
Oh yeah, and for this test I did activate the high speed mode in Dev options.
what are the name of the app that are you using for the cpu/gpu onscreen overlay? thanks
@51CK0F1T4LL
Trepn Profiler, made by Qualcomm.
Sadly you have to switch to estimated Battery Power because normal mode doesn't work.
Did another test with powersafe mode on.
Sticks to 1,32ghz all the time.
Currently trying to find out if GPU Clock is also limited
Okay.....
I can totally see why the Adreno 530 GPU is throttling...
That thing draws an easy 7W on 624mhz and even after throttling still eats 5W on 500mhz.
P.S yeah, the result is that bad because of the resolution. It's not offscreen.
Nope,
Powersafe mode doesn't touch the GPU.
Lol.
You know this app? Boost+ with the Smartboost and game battery booster?
The only thing it does is reduce screen resolution from original 2560x1440 to 1920x1080.
Powerdrain is still exactly the same XD
Guess Benchmarks just aren't made for power efficiency XD
For cpu/gpu throttling try to do gfxbench battery test, or run the 3dmark test 5/10 times
I will appreciate if you can do this test for me
If you get 35-40 fps with good battery life this more than enough, unless you don't know what you want from you device.
I heard you can optimize the screen for 1080p for gaming, is that true
That's mainly GPU bound, so CPU will have about 10-20% Load maximum.
The Adreno 530 is not a little dragon but a huge power hungry beast. I think anandtech did a pretty good longtime throttling test.
P.S I get better Random Write in Powersafe mode..... Wtf?
And yeah, check the macro bench. CPU performance is reduced....
Battery safe:
Normal:
Regarding the random write: That's just AndroBench 4 being silly. The power saver doodah didn't do that.
If you want and care and bother, change your settings and runthe Micro benchmark multiple times, at least 5.
And then report the average of those results. (probably better to post that to the benchmark thread??)
When I tested my sister's Z3 Compact before/after FDE, I ran it 10 times.
Settings I used (default):
256MB file size (64MB) (feel free to increase this to 512 (or heck even 1024) if you want more accurate sequential numbers)
256KB/4KB buffer size (32768KB/4KB)
threads 1 (8)
Here's the raw data from my testing, notice the variation. Before FDE random write min/max
https://docs.google.com/spreadsheets/d/1VCT4hbJItyGaCrzJKfDvQG3f9uQ2B6grRl3VDWHik1M/edit
Which just goes to show how important it is to run the micro benchmark multiple times and then using the average, just like Joshua from Anandtech has said.
More info
http://forum.xda-developers.com/showthread.php?p=66602020#post66602020
http://forum.xda-developers.com/htc...est-htc-10-t3364616/post66578426#post66578426
Ahhh right. I vaguely remember disliking androbench.
Now that explains why ^^