Database Info

[Q] Overclocking and battery life

This is a question for those who have overclocked their Xoom. How much is overclocking to 1.5Ghz affecting battery life?
Overclocking would be the only reason I would root right now, and I am trying to make up my mind on whether to do it.

My battery life is better after using setcpu to overclock. The reason is that the tegra2 chipset scales the performance based on whether it's needed(IE, when you're using your xoom) with setCPU you are extending the top end of how fast the CPU can go. The clever bit is you can also tell your xoom to slow itself down and go very efficient when the screen is off or if the chipset gets too hot (which it never has). If you do go for it I recommend using setcpu using interactive scaling (prioritising the user interface) and whack the max speed up to 1500 and the min speed down to 217 mhz

I wouldn't recommend setting screen-off profiles at the moment. It seems to lead to some strange issues once in a while.
That said, because you're only going to 1.5 GHz when needed, battery life doesn't really suffer. Additionally, at least in my usage, my screen uses ~70-85% of my battery. This is even during heaving gaming, where the Tegra 2 really has to work hard.
I wouldn't worry about its effects, personally.

MrGinger said:
The reason is that the tegra2 chipset scales the performance based on whether it's needed(IE, when you're using your xoom)
Click to expand...
Click to collapse
All CPUs do this, not just Tegras.

Re scaling, never said otherwise I've never had a problem with screen off profile. Maybe just lucky

[Q] SetCPU governors and best frquencies

Hey guys, i just rooted my phone, flashed LBC Mod 0.5.1 and installed SetCPU. I'm completely new to this and i tried googling about the governors, but couldn't understand a word. Now my question is - what do they do? Also, what are the best frequencies?

Basically put, a governor determines how quickly your CPU speed changes between your minimum and maximum frequency settings.
For example, try setting it to conservative. This will make the changes quite slowly, and you'll notice quite a bit of lag between home-screen and when scrolling quickly through lists. It will take a few seconds to realise you are putting more demand on the device and adjust the CPU frequency accordingly.
I think conservative is the slowest, and really only useful for low battery profiles. At the other end of the scale is 'Performance' which simply keeps your CPU maxed out at your top setting all the time. I can't recommend this one. Only really good for intensive games, but I think the Desire S can cope fine with any out there at the minute. This one will drink battery and cause your phone to run hot.
The best balance of reacting quickly and not interfering with performance or draining battery is the 'smartass' one, although some people prefer the 'ondemand' one.
I haven't a Scooby-do what 'userspace' does. I think it is for when you have another program to control CPU speed that reacts to parameters other than demand. Can anyone else confirm?
Try 'smartass' and 'ondemand' and see which you prefer for performance v battery life.
Edit: The best speed is up to you. I would not recommend going over 1.5GHz even if the kernel supports it. Your phone will not live very long. Personally I am waiting until an application comes along that requires I up the speed to run it properly. Everything I have thrown at it so far has been dealt with well leaving the CPU at 1GHz.
If you feel the need, when changing CPU speeds, do so in small steps. Don't just max out the slider. Find what is best for you with small adjustments. Your phone will become unstable if pushed too far.
The light that burns twice as bright, burns half as long.

@wnp_79
I hope that that lot goes into the new edition of your guide!

ben_pyett said:
@wnp_79
I hope that that lot goes into the new edition of your guide!
Click to expand...
Click to collapse
I think it just may do! I am thinking about doing an entire section simply for S-Off & rooted users, but I'm waiting to see what happens with this AlphaRev business first. Then the safe S-Off procedure can be included in the guide which is aimed at newcomers. Then we get them flashing ROMs!
Would do a separate one for more advanced users, problem is I'm still learning this stuff myself too.

Personally I’ve come to realize that 1.2~1.3 is the best top CPU speed for my usage. I do not play games but use internet a lot and generally interact intensively with the phone within the day. Only other profiles I have set is for screen off and <16% battery. Scaling is set on-demand.

245 ... 1200 MHz
smartass govenour
- good performance
- excellent battery life
- snappy from the verry start (lock screen) thanks smartass
profiles for
- bat<30%
- temp>40°C

axelpix said:
245 ... 1200 MHz
smartass govenour
- good performance
- excellent battery life
- snappy from the verry start (lock screen) thanks smartass
profiles for
- bat<30%
- temp>40°C
Click to expand...
Click to collapse
Have you tried the latest version of LBC ROM (v0.5.2) which has the new O/C Daemon? if yes, then what did you think when compared to setCPU.
I previously used settings through setCPU very similar to those you've written above (although I had a slightly lower top end) but, I didn't find it as snappy from the lock screen when compared to the new Daemon that comes within the Unity kernel, which I did have initial reservations about.....but can only see it getting better over time.

SetCPU with smartass feels faster to me. Absolutely no lag on lockscreen. You must not have a screen off profile. Or at least not one with a different governor.
Yes, the new OC daemon is a nice approach, but needs some interface to configure. Currently there's no way to have profiles for battery or temperature.
Sent from my HTC Desire S using XDA App

I use ondemand and have the screen off profile set into the 400Mhz Max, to allow for house keeping and music playback, that's it!

axelpix said:
SetCPU with smartass feels faster to me. Absolutely no lag on lockscreen. You must not have a screen off profile. Or at least not one with a different governor.
Yes, the new OC daemon is a nice approach, but needs some interface to configure. Currently there's no way to have profiles for battery or temperature.
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
Your right when I used setCPU my screen off profile was conservative, although the author of the daemon has promised a set CPU like gui to come, so lets hope that s soon and comes with some profile options (just charging, battery and temp profiles would do)
Sent from my HTC Desire S using XDA Premium App

I have used SetCpu with only smartass governor for a few days, compared to both smartass governor and screen-off profile(all 245MHz with ondemand).
I found it is more battery saving on both smartass governor and screen-off profile(lowest freq.). The reason is that the lowest freq.(245MHz) have been selected much more times according to the cpu used freq. stastics in SetCpu info menu.
I guess the auto screen-off profile in smartass governor may not work well or stable. so if I explicitly setup a screen-off profile with the lowest freq., the lowest freq. will be selected restrictly when screen-off.
Sorry for my poor english and hope u all know what I said.

ben_pyett said:
Your right when I used setCPU my screen off profile was conservative, although the author of the daemon has promised a set CPU like gui to come, so lets hope that s soon and comes with some profile options (just charging, battery and temp profiles would do)
Sent from my HTC Desire S using XDA Premium App
Click to expand...
Click to collapse
Ditto. I too want a GUI for easy use of the daemon. Until that comes, I'm using SetCPU.

allen oddest said:
I have used SetCpu with only smartass governor for a few days, compared to both smartass governor and screen-off profile(all 245MHz with ondemand).
I found it is more battery saving on both smartass governor and screen-off profile(lowest freq.). The reason is that the lowest freq.(245MHz) have been selected much more times according to the cpu used freq. stastics in SetCpu info menu.
I guess the auto screen-off profile in smartass governor may not work well or stable. so if I explicitly setup a screen-off profile with the lowest freq., the lowest freq. will be selected restrictly when screen-off.
Sorry for my poor english and hope u all know what I said.
Click to expand...
Click to collapse
Hm, on my device smartass always puts back to 245MHz in ScreenOff mode.

axelpix said:
Hm, on my device smartass always puts back to 245MHz in ScreenOff mode.
Click to expand...
Click to collapse
Remember that the phone needs to run @ a certain frequency to keep itself running even when the screen is off. Although Set CPU resetting itself is a new one on me. Have you ticked "run at boot"?

SetCPU modes?

What does it mean ondemand, performance, hotplug and so on? what is the diference?

vilks said:
What does it mean ondemand, performance, hotplug and so on? what is the diference?
Click to expand...
Click to collapse
Well, ondemand : cpu maxes only when is needed
performance: cpu runs always on max speed,and consumes lots of battery...
I don't know anything about hotplug

hotplug
Hotplug its the performence switching all the time like if u put it on 200mhz and 1000mhz it will be like this: 1000-200-1000-200-1000-200-1000-200
its switching every 1sec

This means a lot battery consumption, right?

mastaeit said:
This means a lot battery consumption, right?
Click to expand...
Click to collapse
Ya..hotplug using apparent juice aiming good performance side..if u want no compramis on battery choose ondemand..u can also use 'setxperia'(free from play store) by intek which working awsom on o3d..
Sent from my LG-P920 using Tapatalk 2

CPU Freq: How do you keep yours?

This is a question I've never seen asked, but it's an important one. What are you phones CPU Freqs? What Govs do they have, and what Profiles do you use?
Rom: PyroIce
Main: 192 Min, 918 Max. OnDemand.
Screen Off: 192 Min, 384 Max. PowerSave.
InCall: 192 Min, 540 Max. Interactive.
Time 11pm-7am: 192Min/Max Powersave.
Sent from my HTC myTouch_4G_Slide using Tapatalk

that's cool, i might start using profiles again. from fiddling around i've noticed the difference between the ondemand and conservative governors- with ondemand, the processor seems to go from min. to all the way to max. and back down to min, and doesn't use the middle frequencies as much, while on conservative, the processor doesn't shoot up to max. as easily and seems to meander thru the middle frequencies a lot more. it makes sense too, because i've noticed that the phone seems snappier with ondemand.
i noticed you're using some of the others... i'll have to check them out as well.

ondemand
Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see "up threshold" in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed. - SetCPU website
conservative
Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery. - SetCPU website
performance
Available in most kernels. It will keep the CPU running at the "max" set value at all times. This is a bit more efficient than simply setting "max" and "min" to the same value and using ondemand because the system will not waste resources scanning for the CPU load. This governor is recommended for stable benchmarking. - SetCPU website
powersave
Available in some kernels. It will keep the CPU running at the "min" set value at all times. - SetCPU website
userspace
A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor. - SetCPU website
Interactive
The 'interactive' governor has a different approach. Instead of sampling the cpu
at a specified rate, the governor will scale the cpu frequency up when coming
out of idle. When the cpu comes out of idle, a timer is configured to fire
within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer
fires then we assume the cpu is underpowered and ramp to MAX speed.
If the cpu was not 100% busy, then the governor evaluates the cpu load over the
last 'min_sample_rate' (default 50000 uS) to determine the cpu speed to ramp down
to

so, I bought set cpu about 3 phones ago, but I never really saw a differnence, can it be used with the stock kernel?

yellowjacket1981 said:
so, I bought set cpu about 3 phones ago, but I never really saw a differnence, can it be used with the stock kernel?
Click to expand...
Click to collapse
Yeah Plus there's a huge difference with the Battery. I you use my CPU Settings, you should gain 3 hours Min on your phone. Also dropping the CPU in call is great, helps for longer calls and less overheating. If your S-Off you should use a custom kernel. UV Kernels are great.

AgentCherryColla said:
Yeah Plus there's a huge difference with the Battery. I you use my CPU Settings, you should gain 3 hours Min on your phone. Also dropping the CPU in call is great, helps for longer calls and less overheating. If your S-Off you should use a custom kernel. UV Kernels are great.
Click to expand...
Click to collapse
I actually just got an uv kernel, I am about to flash it, I will use your settings too, thanks.

yellowjacket1981 said:
I actually just got an uv kernel, I am about to flash it, I will use your settings too, thanks.
Click to expand...
Click to collapse
If you run a Sense 3.6 Rom, boost the CPU to 1Ghz. 918Mhz Lags.
Sent from my HTC myTouch_4G_Slide using Tapatalk

yellowjacket1981 said:
so, I bought set cpu about 3 phones ago, but I never really saw a differnence, can it be used with the stock kernel?
Click to expand...
Click to collapse
Yes.
You cannot use anything the kernel doesn't already serve as an option, though.
SetCPU doesn't create options - it allows you user-level access to the ones already existing.
Normally you have no control over your clock speed but with it you can...say... limit the maximum clock speed to only be two-thirds of the stock speed.
Since it doesn't ramp up all the way, it doesn't drain as much power.
If you are playing games and stuff that needs a lot of resources, then the slower clock speeds cost you battery since it takes more effort to get the same work done. But if you don't do much with your phone, and don't need a lot of high-end CPU ability, why let it run flat out?
You can also set it to be like that only sometimes, and maximize battery savings by telling your device to chill out when it doesn't have to be awesome.
Now, if you get into custom kernels where you or a dev has opened up more options, SetCPU will again give you user level control over them.
Especially once you get into overclocking beyond manufacturer(s) recommendations, not having some end-user level control over the processor like this is irresponsible.
If you think I run a 1.7 or 1.9 or 1.5+anything on the device flat-out balls-to-the-wall all the time, I would ask you if you drive your car with the gas pedal smashed to the floor all the time. (it's a fitting analogy)
No, again, that would be irresponsible abuse of the hardware for no good reason.
If not SetCPU, then there would be something else to use, but SetCPU is a great interface that not only works well but is maintaned within the XDA community by a member here.
I will always go for the XDA community member version of any app first - it's usually a problem solved from a perspective very near the way I am perceiving the issue, supports the community, and is always easier to find help on if necessary.
What's even cooler is SetCPU is given away free by the dev to XDA members.
I did go ahead and buy it anyway to support the dev. It is a fantastic tool at my disposal, and I have come to realize just how much time and energy goes into making this kind of stuff.
Beyond all that, though, there are a ton of crap apps and software out there slapped together by people who don't care or didn't put the right level of effort into their work. When I find something that actually works and works well after sifting through a sea of garbage, if there is a paid version of the app i'll usually buy it not only as a thank you but also to encourage that particular person to keep working. They - unlike many, many others (in my opinion) earned it.
I know i'm drifting off topic a bit, sorry for that - I just really appreciate quality work and SetCPU falls in with that crowd nicely.
Even without a custom kernel providing options beyond stock, there is still a lot of value this app can hold for anyone with root level access to their device.

Blue6IX said:
If you are playing games and stuff that needs a lot of resources, then the slower clock speeds cost you battery since it takes more effort to get the same work done.
Click to expand...
Click to collapse
Is this true? in my mind, I feel like it will take longer/not be as smooth, but wouldn't necessarily be worse for battery than a higher clock speed.

On a one-for-one comparison it leans more towards an even playing field, until you add that it's a dual-core processor and it very heavily skews the results towards less battery at higher clock speeds for complex operations.
Faster CPU speeds process the actions more quickly, and when you have to crunch a lot of numbers real quick like you do for most games the higher clock speed (especially on the dual core we are using) will complete the act with less power used. It is able to keep up with and/or outpace the flow of data being thrown at it.
If you are just using a notepad or browsing some forums maybe...sending a few texts? Then the higher clock speeds show a negative return on battery usage - you don't need it and it's wasteful.
But when the data has to stay buffered because the CPU is taking it's time working with it, not only is there more electricity consumed by keeping the processor alive longer but also the juice spent on keeping the data buffered.
The data computed is the same data computed at any speed (unless you lose data along the way...) but the power spent on completing that operation is not equal - not by a long shot.
On single core older processors where you are talking about a couple hundred megahertz one way or another the equation is much different, significantly diminshed returns on electricity invested, but with higher quality and multi-core processors especially they can cut through the data with significant ease when sufficiently powered.
But this is on processor intensive activities, and gaming is the first thing that comes to mind. For most other use of the device it's worth underclocking it and you will see battery gains.

Adreno idler, an idling algorithm for devfreq-based Adreno devices

I'm here to introduce 'Adreno idler' to the world, and for kernel developers out there, how to apply and test.
So what is Adreno idler?
It is an idling algorithm,
an efficient workaround for msm-adreno-tz's overheads.
Main goal is to lower the power consumptions while maintaining high-performance.
Since msm-adreno-tz tends to *not* use the lowest frequency even on idle,
Adreno idler replaces msm-adreno-tz's algorithm when it comes to
calculating idle frequency(mostly by ondemand's method).
The higher frequencies are not touched with this algorithm, so high-demanding
games will (most likely) not suffer from worsened performance.
Click to expand...
Click to collapse
Why have I made it?
Because I don't like every, single, GPU governors out there for our Snapdragon devices.
Let me break it down for you.
msm-adreno-tz: default GPU governor for Snapdragon devices. It's interval/polling mechanism is very efficient, reducing the number of unnecessary frequency switches and maintains high performance. But, even on idle, it *tends* to not use the lowest frequency, resulting in higher power consumption and more battery drains on simple tasks such as watching video/YouTube or browsing the web.
Simple: a GPU governor made by faux123. I was using this on my older, non-devfreq-based devices but faux123's version of devfreq-based Simple GPU governor, it introduced a lot of weird switches and latencies resulting in a lot of lagginess and heat.
simple_ondemand: a devfreq governor made by Samsung, forked from ondemand cpufreq governor. It can be used as a GPU governor if your Snapdragon device uses devfreq governor for GPU frequency scaling. At idle, it goes all the way down to the lowest frequency, which is promising, but if it's under load, it continuously goes up and down, resulting in a similar behavior compared to Simple. Unnecessary number of switches, resulting in lagginess and heat.
So what's the answer?
None! Maybe the ideal solution is to modify msm-adreno-tz's algorithm to utilize the lowest frequency, but because msm-adreno-tz's algorithm is hidden under ARM's TrustZone technology, we can't tweak it much.
Hence, here comes Adreno idler.
Main goal is to lower the power consumptions while maintaining high-performance.
Adreno idler replaces msm-adreno-tz's algorithm when it comes to
calculating idle frequency(mostly by ondemand's method).
The higher frequencies are not touched with this algorithm, so high-demanding
games will (most likely) not suffer from worsened performance.
There are 3 main tunables for Adreno idler.
idleworkload for determining if the given workload is idle,
idlewait for preventing micro-lags,
and downdifferential for final calculation for determining if the GPU can go idle.
Logics are explained very well on the source-code. Go check if you're interested.
How to test and apply
Please go through the testing process.
If your device's stock msm-adreno-tz can go idle very well(it can differ from device to device since it's closed source), Adreno idler is not needed.
So far, it's working as advertised on Galaxy S4 LTE-A and Galaxy Note 3.
Use adb shell and type the following.
Code:
cd /sys/devices/*kgsl*/devfreq/*/
while true; do cat trans_stat; busybox sleep 0.1; done
If you can notice the msm-adreno-tz not using the lowest frequency even on idle, it's time to go try Adreno idler.
Your device MUST use devfreq msm-adreno-tz before applying Adreno idler.
AFAIK, Nexus 5 doesn't use devfreq, but more recent devices will use devfreq.
Go check if drivers/devfreq/governor_msm-adreno-tz.c exists.
I highly recommend to cherry-pick every devfreq/msm-adreno-tz changes on my Git repository to avoid inconsistencies which I did not intend.
Part of Adreno idler uses powersuspend by faux123.
Go apply it first before applying Adreno idler.
https://bitbucket.org/arter97/andro...mits/adebe9f7080df129d4cd5128fdbab2aeeba223b4
(powersuspend dependency. Just make sure to apply include/linux/powersuspend.h and kernel/power/powersuspend.c changes.)
https://bitbucket.org/arter97/andro...mits/79945454ce9c82afa9288ebf8250aa8de45cb217
https://bitbucket.org/arter97/andro...mits/573933b0606872729161321042e7fd35b1b268ad
https://bitbucket.org/arter97/andro...mits/522e2814fa84b5404de8f246ebe217346b1aa346
https://bitbucket.org/arter97/andro...mits/04113ad70a03ce05eb8e52b8ca5274db21a7fd51
https://bitbucket.org/arter97/andro...mits/bc40eaf6c9e17e8f47cb52f20a50a25638955b45
https://bitbucket.org/arter97/andro...mits/c0a48acef7a34c30cd3edc03e971bc1161efacbd
https://bitbucket.org/arter97/andro...mits/8996dbf8714866d325ecaef5489ded312c4ebe1c
https://bitbucket.org/arter97/andro...mits/3bce70ca80c1a095d3c644c14e8224a012e43138
https://bitbucket.org/arter97/andro...mits/123d953787a9e31830956a740415d0b82ec666e5
<-- The main party starts here !-->
https://bitbucket.org/arter97/andro...mits/22d0b352f54a00029cfa18c368e9d680e3aaf60a
https://bitbucket.org/arter97/andro...mits/28c79e6018fd761245303feb51b1ad684399290f
<-- More updates !-->
https://bitbucket.org/arter97/andro...mits/6a001e2993138a7e44371632ab623e07d78e1a8b
https://bitbucket.org/arter97/andro...mits/b75554aa37be5dce5a83974d362d58d4cb7991a6
https://bitbucket.org/arter97/andro...mits/72b75f62452486c482dfd009ad038b1fdaf6a941
https://bitbucket.org/arter97/andro...mits/423c55f7ef34f73c0913a70f5d1463d94b612de3 (This is a must-have commit)
https://bitbucket.org/arter97/andro...mits/c9fd20d3185ca0594c0175a3d1c8a6164e3956c2
https://bitbucket.org/arter97/andro...mits/d66cd80d6ca422fc1398bb0c821409e82bc0ba0d
That's it for Adreno idler 1.1.
I'll continuously update in the future.
Make sure to follow my Git and apply changes made to devfreq/msm-adreno-tz/adreno-idler.
After you've applied Adreno idler, turn it on from the defconfig and go through the testing process to check if the Adreno idler is working correctly.
It should ramp down the frequency to the lowest after about 200~500ms when system hits idle.
And you can turn Adreno idler on/off and fine-tune from /sys/module/adreno_idler/parameters.
Benchmark
Ahhhhhhh.. this will be interesting. And it is.
I've tested my ks01lte with watching a movie and playing a game.
1. 15 GB 1080p 2.5 hrs movie w/ HW decoder - Airplane mode ON/Brightness 25%
2. Casual game, leave it for 30 minutes on the same screen - Airplane mode ON/Brightness 100%
1.1. Adreno idler off - 46.3% battery drain, can expect approx. 6hrs 5mins of video playback on 100% battery charge.
1.2. Adreno idler on - 25.5% battery drain, can expect approx. 11hrs 2mins of video playback on 100% battery charge.
2.1. Adreno idler off - 13.4% battery drain, can expect approx, 3hrs 43mins of gameplay on 100% battery charge.
2.2. Adreno idler on - 11.7% battery drain, can expect approx, 4hrs 16mins of gameplay on 100% battery charge.
You decide if Adreno idler is awesome or not.
Enjoy
Huge thanks to hsk from Matcl for debugging, analyzing, and suggesting more efficient code.
This would be a piece of crap if it's not for hsk

Great. Those benchmark are from what phone?

@arter97 this advantage is only in gaming or heavy videos or also has effect in light usage?
Sent from my A0001

JMS74 said:
Great. Those benchmark are from what phone?
Click to expand...
Click to collapse
ks01lte = Galaxy S4 LTE-A(Snapdragon 800)

JMS74 said:
Great. Those benchmark are from what phone?
Click to expand...
Click to collapse
CounterC said:
@arter97 this advantage is only in gaming or heavy videos or also has effect in light usage?
Sent from my A0001
Click to expand...
Click to collapse
More likely in light usage.
I'd suggest you to read the OP again.

@arter97
How much is your web browsing time approximately?
Sent from my GT-I9506 using XDA Free mobile app

Thanks @arter97 added to my shamu source to test.

If I don't use "Force 2D GPU Rendering", is this idler still effective? I almost do light usage: facebook, web browsing, no games.

Kiryo24 said:
@arter97
How much is your web browsing time approximately?
Sent from my GT-I9506 using XDA Free mobile app
Click to expand...
Click to collapse
No idea. I haven't tested it scientifically.

freakingprime said:
If I don't use "Force 2D GPU Rendering", is this idler still effective? I almost do light usage: facebook, web browsing, no games.
Click to expand...
Click to collapse
Yes.

Arter just want to tel you that this is a big thing, am already testing and i think that iam seeing a difference in browsing battery life, anyway too early to tell...
We are so lucky to have a freaking genius developer for our note 3..

Thanks, im already testing !

How i test? Only for devs?
Sorry
Sent from my A0001

@arter97 ive added all the commits and compile just fine,the file (gov module) compiles but doesnt show in the availeable gpu governors to choose,can you give me a hint?

attack11 said:
@arter97 ive added all the commits and compile just fine,the file (gov module) compiles but doesnt show in the availeable gpu governors to choose,can you give me a hint?
Click to expand...
Click to collapse
This is not a governor.
It lives on top of msm-adreno-tz.
Sent from my Nexus 7 using XDA Free mobile app

arter97 said:
This is not a governor.
It lives on top of msm-adreno-tz.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for pointing out,i was going crazy !
Nice job btw, msm-adreno-tz now down to the lowest frequency available when is needed :good:

Temasek has implemented this in his latest ROM and I'm getting the best battery life on my phone that I've ever had.
Brilliant work, @arter97.
Sent from my SM-N9005

Is it possible that this gives advantage only on the Samsung devices mentioned and not on the OnePlus?
Sent from my A0001

CounterC said:
Is it possible that this gives advantage only on the Samsung devices mentioned and not on the OnePlus?
Sent from my A0001
Click to expand...
Click to collapse
Oneplus msm-adreno-tz governor correctly scales down to minimum frequency when idle.
So at least the difference should not be expected to be very big.
So far the theory ☺
Andi

Well only to touchwiz sucks?
Sent from my A0001