Hello
Can someone kindly tell me what difference does enabling GPU UI rendering make? From the name I can understand that the UI will be rendered using the GPU and not the CPU. But what are the advantages/disadvantages of this? What changes can I expect upon enabling it? And how does it, if at all, affect battery life?
Thanks in advance =)
Most of the apps now use GPU rendering (app packages for ICS, etc). Some apps don't(old apps). Force GPU UI rendering switch forces those apps to use GPU.
Pro. much smoother UI in apps that don't enable GPU rendering by default.
Con. Some visual bug may appear on some apps.
and what about battery life?
gannjunior said:
and what about battery life?
Click to expand...
Click to collapse
Theory 1; since the GPU is having some work right next to CPU it is an additional burden to battery to feed them both
Theory 2; Since they share the load they both can run at lower clocks so this means less voltage needed. Less voltage means less energy consumed.
So I guess there is no exact way to measure but nowadays most of the apps are already using that option default so it must be a good thing. At least the device does not have to run the CPU at max speed and heat up.
'Disable hardware overlays' what does this mean and should I enable it
Sent from my GT-I9300 using xda app-developers app
mohnim said:
'Disable hardware overlays' what does this mean and should I enable it
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Read this:
Without a hardware overlay every application that is displaying things on the screen will share video memory and will have to constantly check for collision and clipping to render a proper image, this can cost a lot of processing power. With a hardware overlay each application gets its own portion of video memory, getting rid of the need to check for collision and clipping.
Basically, using hardware overlays can reduce CPU usage by quite a bit
Click to expand...
Click to collapse
Source: http://rootzwiki.com/topic/28977-disable-hardware-overlays/#entry778564
thanks for the explanation
gannjunior said:
thanks for the explanation
Click to expand...
Click to collapse
Not to be "that guy", but there's a button for that.
Related
Before I start credit belongs to eL_777 for posting this in the asus prime thread.
I read that enabling the "Force GPU Rendering " in the developer options would increase the speed of apps. I so I gave it a try and it has definitely increased the overall smoothness for me. I also what to add that it may cause some apps to force close but the only issue I noticed so far is launcher pro not displaying properly. I just switched to adw ex so that is no longer an issue. I opera, browser and tapatalk seem to be faster. It also seems to have an impact on the YouTube app. Hopefully this info helps some people out.
I didn't come across this yet in the xoom forum so I thought it I would share. Sorry if it is common knowledge.
Original post:
eL_777 said:
Hey guys I noticed earlier that my Netflix app was ALOT smoother than it used to be before the ICS update but several others disagreed with me so I was confused. Then I remembered that I enabled this setting in the developer options menu in the android settings, "Force GPU Rendering". Make sure you enable that, close Netflix and start it back up and it should be a million times smoother after you do that. Hope this helps.
Click to expand...
Click to collapse
runhopskipjump said:
Before I start credit belongs to eL_777 for posting this in the asus prime thread.
I read that enabling the "Force GPU Rendering " in the developer options would increase the speed of apps. I so I gave it a try and it has definitely increased the overall smoothness for me. I also what to add that it may cause some apps to force close but the only issue I noticed so far is launcher pro not displaying properly. I just switched to adw ex so that is no longer an issue. I opera, browser and tapatalk seem to be faster. It also seems to have an impact on the YouTube app. Hopefully this info helps some people out.
I didn't come across this yet in the xoom forum so I thought it I would share. Sorry if it is common knowledge.
Original post:
Click to expand...
Click to collapse
I had tried it and thought that there was an improvement in smoothness, but it seems that as you say, it can break some applications. But thanks for the reminder.
Enabling this preference in developer options offloads task of rendering window components like buttons, text and complex 2d graphics calculations to GPU. This often results in much faster UI rendering including animations.
On one side you will definitely achieve better frame rate (and hence smooth experience) throughout system, but you may end up using more battery. On certain devices, GPU consumes more power the CPU, hence you may observe 5-15% lower battery life with option enabled.
offloading UI rendering to GPU has obvious benefits so that CPU can work on other important tasks like database IO, data manipulation, layout calculations and responding to other user inputs.
I would recommend having this option enabled on devices with weaker CPUs e.g. You should seldom need to enable this on dual-core 1.4ghz ARM CPU.
Odp: Enabling "Force GPU Rendering " for more speed in some apps
taranfx said:
Enabling this preference in developer options offloads task of rendering window components like buttons, text and complex 2d graphics calculations to GPU. This often results in much faster UI rendering including animations.
On one side you will definitely achieve better frame rate (and hence smooth experience) throughout system, but you may end up using more battery. On certain devices, GPU consumes more power the CPU, hence you may observe 5-15% lower battery life with option enabled.
offloading UI rendering to GPU has obvious benefits so that CPU can work on other important tasks like database IO, data manipulation, layout calculations and responding to other user inputs.
I would recommend having this option enabled on devices with weaker CPUs e.g. You should seldom need to enable this on dual-core 1.4ghz ARM CPU.
Click to expand...
Click to collapse
I finally gave up GPU rendering as it crash the tab many times. Ie google maps hang the tab after 10-15 min time of usage to such extend that it bootlooped over and over till battery is dead. Also browsing web cause same crashes. If you face many random crashes-you know what to do.
Wysyłane z mojego XOOM 2 ME za pomocą Tapatalk 2
I noticed this juts few days ago and did this on all my family's Nexus S.
Install Chainfire3d
from the market and then open the app and tap to install the driver. I used the normal method not the advanced. Don't set any other settings after your phone reboots. You can if you want to but a lot of aps won't work with those settings.
What this app does is it installs an intermediate open GL driver between the apps and phone GPU driver to give you better performance.
Just figured I'll share it with everyone. It really made a difference for me on ICS speed. The way I see it it should be baked it to all ICS ROMs.
isnt this just used for games?
that's why its called chainfire3D
the whole point is to trick proprietary games "apps" into thinking you have GPU that you don't
so you are able to play tegra adreno..ect games on other devices
dont think its works on anything other than games so i don't se how its helping make overall ICS faster.
ICS is already using our sgx540 just fine
Well, it does and it makes a difference. Try it and see for your self. Chainfire3d is not just for games.
Thank you for pointing out this tweak. I too was under the impression that chainfire was just for games.
Both tapatalk and the browser feel much smoother.
Thanks
Sent from my Nexus S using Tapatalk
obsanity said:
Well, it does and it makes a difference. Try it and see for your self. Chainfire3d is not just for games.
Click to expand...
Click to collapse
im eating my words sorry i was under impression was games only
im trying now you're right things are even smoother now thanks for the tip
As advertised. Nice find obsanity, it does make things noticeably smoother on general.
Noticed speed improvements thank you man
Nexus S - CyberGR Hybrid ICS (5), Matrix Kernel (15)
Chainfire dev recommends disabling all driver settings unless being used by a specific applications, per his xda thread:
" I strongly advise that when you are NOT using Chainfire3D for something specific, you disable all the options. This is better for system performance."
Anyone know why? Is he talking about the non-default options?
I don't know exactly, but it seems like it is just to do with the specific settings (inside the default settings section). Using the driver is fine, but any of the options being ticked has the ability to make some applications go awry depending on the device. Those options, i assume, are only meant to be used when you want to use a specific app that requires or benefits from them.
Also, i've noticed great improvements in ES File Explorer scrolling. It would lag a fair bit scrolling through long folders, but now it's nice and smooth.
Harbb said:
I don't know exactly, but it seems like it is just to do with the specific settings (inside the default settings section). Using the driver is fine, but any of the options being ticked has the ability to make some applications go awry depending on the device. Those options, i assume, are only meant to be used when you want to use a specific app that requires or benefits from them.
Also, i've noticed great improvements in ES File Explorer scrolling. It would lag a fair bit scrolling through long folders, but now it's nice and smooth.
Click to expand...
Click to collapse
That's what I was thinking as well. Thanks.
I'm installing this now... Have you guys noticed any decline in battery life?
Hopefully not :3
Does anyone know if this has the same downside as forcing gpu acceleration in the developer setting? I remember reading the Googler's post on G+ on how it increased the memory overhead by 8mb per app, reducing the memory available for other apps and processes.
Sent from my Nexus S using Tapatalk
It doesn't force GPU rendering. Alot of the Android UI is already using GPU rendering, using this intermediate driver just somehow makes it more fluid.
Trying it now, though I don't notice much improvements in scrolling.
I use force GPU setting on my phone. With the live OC in Matr1x at 111% (max my phone can handle) it does make a bit of difference in UI. But this Chainfire3D driver makes the most difference for me.
Also, in case you are on a ROM which doesn't let you change min memory settings, I'm using MinFreeManager which is a small app that just does that. The default settings which it comes built in are for GB but you can just change them manually. I don't touch the top 3 and just tweak the bottom 3. I'm currently on:
14,19,24,32,64,128
Does it effect battery drain?
Will this eat more battery juice?
Highly doubt it, and so far havn't noticed anything particularly different on my end. You can uninstall it anyway if it does cause trouble (though might be wise to perform a nandroid backup while initially installing).
Thx man, now trying it!!
Greetzz Jojoost
Sent from my Nexus S using XDA App
What are the additional features in the pro version?
What are the additional features in the pro version?
They are not described in the market.
Anti-Aliasing features and per-app settings are the main features in the pro version. More info here.
sorry for this noob question, but i never really knew what it was. what are the pros of this? does it fix the choopy video on most all ics roms? i saw qualcomm released official drivers but what will they fix?
Truth is somewhere here!!
hey,
well it simply does what it says, lol it accelerates your hardware making it run fast, smoother, better, and it does many great things for your phone!
Hardware acceleration means that certain things will be done by the GPU instead of the CPU. THe GPU has more cores and is made to process graphics and UI's. the Acceleration on ICS is suppsoed to use the GPU for the UI and for apps. Taking the strain off the CPU and theoretically providing a better power management since the GPU will do it faster. Flipping from screen to screen should be more fluid as should scrolling etc.
stevovanburen said:
hey,
well it simply does what it says, lol it accelerates your hardware making it run fast, smoother, better, and it does many great things for your phone!
Click to expand...
Click to collapse
are you trying to be funny? or is that really what you think hw acceleration is?
deathsled said:
are you trying to be funny? or is that really what you think hw acceleration is?
Click to expand...
Click to collapse
Hey,
I was just trying to leave it simple for others,
I guess that was not a good way to put it though..and if you want me to put in the tech specs I shall fix it
Hardware acceleration To be simple and sweet:
System with out h/w accel
cpu is what is going to be running your task and ui,
gpu is your graphics core in charge of changing things such as the window overlays,
Problem
Issue cpu is limited and can be strained a lot,
The gpu which is made specifically to handle graphics could take a bigger load,
Solution
Hardware acceleration
Which will run task and so forth on the system's gpu
This shall be freeing up your cpu allowing it to perform better
This allows your phone to run faster, smoother, better *in theory anyways*, and as I said does many great things for your phone.
It's not like older versions of Android don't have hardware acceleration, ICS will just have better hardware acceleration.
thanks guys helped alot
cmsjr123 said:
Hardware acceleration means that certain things will be done by the GPU instead of the CPU. THe GPU has more cores and is made to process graphics and UI's. the Acceleration on ICS is suppsoed to use the GPU for the UI and for apps. Taking the strain off the CPU and theoretically providing a better power management since the GPU will do it faster. Flipping from screen to screen should be more fluid as should scrolling etc.
Click to expand...
Click to collapse
Do older Android versions have HWA?
te45a said:
Do older Android versions have HWA?
Click to expand...
Click to collapse
I don't think so but pb5-7 I guess of Deck's , HWA is pretty awesome.
Sent from my HTC Evo 4G using xda premium
stevovanburen said:
Hey,
I was just trying to leave it simple for others,
I guess that was not a good way to put it though..and if you want me to put in the tech specs I shall fix it
Hardware acceleration To be simple and sweet:
System with out h/w accel
cpu is what is going to be running your task and ui,
gpu is your graphics core in charge of changing things such as the window overlays,
Problem
Issue cpu is limited and can be strained a lot,
The gpu which is made specifically to handle graphics could take a bigger load,
Solution
Hardware acceleration
Which will run task and so forth on the system's gpu
This shall be freeing up your cpu allowing it to perform better
This allows your phone to run faster, smoother, better *in theory anyways*, and as I said does many great things for your phone.
Click to expand...
Click to collapse
Originally you said "it accelerates your hardware making it run fast". A statement like that implies something being done to the hardware like overclocking the CPU for higher performance. If you were trying to dumb down what HW acceleration was you got it completely wrong lol.
But, as you've come back and elaborated further now you've got the right idea. The point of HWA in any situation is to leverage existing hardware to perform certain operations/rendering that otherwise would be done in software by the main CPU.
So I recently changed over to the nexus 4, and I say, it is AMAZING. I just got to the point where the SGS just didnt cut it anymore. It has hung in there for a long time, but its starting to become under-powered for new versions of Android.
So in this guide, I am going to show you how to speed up your Galaxy S, and push it to its max performance.
You will need a custom kernel like Semaphore. I made this guide with no regard to battery life, but i did avoid using un-necessary power.
1. Live OC
- This increases the Bus, Ram and GPU speeds.
- This is very good because information can only be transferred as fast as the bus can transfer it. So if your CPU is fast, but your bus is to slow, it creates a bottle neck. So upping bus speed as well as CPU/GPU/Ram speeds can drastically increase performance.
- Find settings that are stable for your phone. For me this was 123%.
- Note that this will change the CPU clock speed choices that you have. Normal.
Click to expand...
Click to collapse
2. CPU Clock Speed / Governor
- Increasing Clock Speeds allow your processor to calculate more per second, therefore increasing performance.
- Start by finding the maximum frequency that your device is capable of handling, while still keeping stability. For me, this is 1400MHZ.
- Set lowest clock speed to 200 or 400. 200 is the best all-round, and actually uses less power than 100MHZ due to faster race to idle. I use 400 for performance.
- Use a snappy governor. Min/max is great, it is what i use.
- For more battery. lulzactive, ondemand, and smartass are all good.
- Enable smooth UI tweak.
Click to expand...
Click to collapse
3. RAM settings / management.
A. MOAR RAM.
- The Galaxy S has very limited ram, so we must make the best of it.
- It has 500mb, but some is allocated for the camera and GPU, so we only get ~400 in the end.
- Use the Bigmem option. Around 400mb, but breaks 720p recording. Its a good sacrifice.
- Also, Un-install any apps that you are not using! This can free up cache space and leave it for important processes. Go to settings/running/caches for more info.
- Go to settings/developer options/background process limit, and set this to keep more ram free. I use 3.
Click to expand...
Click to collapse
B. Enabling Swap
- Enabling swap allows the kernel to use specially allocated memory (on your SD card) to store cached pages that aren't currently being used, instead of storing them in RAM.
- Frees RAM for foreground or heavy processes.
- Make sure you use a fast SD card, and do not set the swappiness to high, both of these can slow your phone down.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
4. CM Performance Settings.
- Setting these properly can also increase performance on your device. It will not create any instabilities.
- I/O schedulers are all very similar. I personally prefer SIO, CFQ, or VR
- Under Memory management, Allow purging of assets and enable Kernel same page merging. Both use more clock cycles, but free needed RAM.
- Avoid ZRAM. Performance gain is not enough for the number of clock cycles needed to compress and decompress the RAM.
- Enable 16 bit transparency. Lighter load on the system when drawing graphics, and has never causes visual artifacts for me.
- Disable surface dithering. One less thing for your device to do, equals more performance.
Click to expand...
Click to collapse
5. Animation Scales (not necessary)
- This simply makes your device LOOK faster buy increasing the speed of the animations.
- Go to developer options and find Window Animations scale, Transition Animation Scale, and Animator Duration Scale.
- Turn them all to 0.5 for a faster UI.
Click to expand...
Click to collapse
Questions? Feel free.
But OC my phone will make my phone die faster yea?
Because I afraid to destroyed my phone
Sent from my GT-I9000 using xda app-developers app
It does reduce life for sure. As does live OC.
I over clocked my phone for a long time, and it has had no bad effects. It works great to this day. It reduces, but not significantly that you should worry about.
Most CPUS are designed to last for 10+ years, and you may take a year or two off. Nothing major!
Sent from my Nexus 4 using xda premium
AlwaysDroid said:
It does reduce life for sure. As does live OC.
I over clocked my phone for a long time, and it has had no bad effects. It works great to this day. It reduces, but not significantly that you should worry about.
Most CPUS are designed to last for 10+ years, and you may take a year or two off. Nothing major!
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I think even less, Ive never heard of anyone suffering at anything from oc anything.
This is an amazing guide and it has everything explained in one place thank you!
Sent from my GT-I9000 using xda app-developers app
Where/how do you enable swap?
good guide but currently not necassary to do,more and more roms are made with enough to tweak the perfomance already done,ive not found anything that has pushed my phone while on a decent custom rom
beardedwonder said:
Where/how do you enable swap?
Click to expand...
Click to collapse
Try this. I never used this guide myself, i just searched it up. Maybe ill add it to the OP if you have success with the guide.
http://forum.xda-developers.com/showthread.php?t=1610835
friartuckme said:
good guide but currently not necassary to do,more and more roms are made with enough to tweak the perfomance already done,ive not found anything that has pushed my phone while on a decent custom rom
Click to expand...
Click to collapse
it is not necessary at all, but there is nothing wrong with getting as much bang for your buck as you can!
AlwaysDroid said:
Try this. I never used this guide myself, i just searched it up. Maybe ill add it to the OP if you have success with the guide.
http://forum.xda-developers.com/showthread.php?t=1610835
Click to expand...
Click to collapse
This thread isn't really a guide then, it doesn't look like you can use swap with semaphore.
beardedwonder said:
This thread isn't really a guide then, it doesn't look like you can use swap with semaphore.
Click to expand...
Click to collapse
I'm abit out of the loop. I used devil kernel and it had it. I know cyancore kernel has it!
Sent from my Nexus 4 using xda premium
AlwaysDroid said:
it is not necessary at all, but there is nothing wrong with getting as much bang for your buck as you can!
Click to expand...
Click to collapse
very true,i agree
Just wondering if this is common or not, mainly PUBG runs sluggish even on the lowest graphics setting.
Isopropil said:
Just wondering if this is common or not, mainly PUBG runs sluggish even on the lowest graphics setting.
Click to expand...
Click to collapse
maybe because of the 2k?
I also tried pubg and yes, it's too damn laggy. lowering the resolution to 720p didn't help much. i guess i have to see how it runs on another device to be sure it's not a crappy app (Even though it looks like it)
I though the same thing, wish there was a easy way of lowering like on Samsung roms.
Isopropil said:
I though the same thing, wish there was a easy way of lowering like on Samsung roms.
Click to expand...
Click to collapse
if you're willing to use the navbar (or mipop if you're on stock), it's as simple as making a couple of shell scripts that change density and resolution, then adding widgets for them. Since probably nobody is looking at the capacitive buttons bug this will probably be the only way to do it
The main problem for gpu intensive games is that they start to lag more the longer u play. Its because (at least on stock roms) the kernel throttles the cpu and gpu way too aggressively at a certain temperature. Same happens to hearthstone.
At beginning i can play a few rounds with 40-60fps, but after some time the kernel throttles the cpu and gpu down by alot even though the device itself only just got a bit warm. Main issue is throttling happens way too soon by way too much. And well some games are not well optimized and dont clear graphic cache often enough. Hearthstone for example has this issue, even if device is cooled, the game drops fps (not as much as with throttling tho) if too many graphical stuff loaded into the graphical ram over time (at least thats how i think it is)
Sent from my ZTE A2017G running V1.2.0B08 using XDA Labs
GodOfPsychos said:
. And well some games are not well optimized and dont clear graphic cache often enough. Hearthstone for example has this issue, even if device is cooled, the game drops fps (not as much as with throttling tho) if too many graphical stuff loaded into the graphical ram over time (at least thats how i think it is)
Click to expand...
Click to collapse
I play PUBG on stock ROM after basically disabling CPU GPU thermal throttling and adjusting the governors to use the full frequency range accordingly. Having a fan of any sort, even a small usb powered one blowing air on the back up to a meter will keep the battery under around 50degC. The aluminum unibody cools effectively and efficiently with the help of a fan. I use a Tasker task to change the CPU limits and other optimizations before playing.
After eliminating the processor bottleneck the game can run on high settings smoothly. However the game uses 1GB of RAM on high settings that I've tested and the device lags under around 500Mb of free RAM on stock's OOM configuration. So free RAM needs to be able to reach at least 1.5Gb to not cause slow downs. Having already debloated and using greenify with and root commands to disable background user processes, I can play without RAM being an issue. I monitor free RAM and other hardware in real time to check these function without issue.
Having now removed both those bottlenecks I found there's still some lag that can develop after the phone has been playing for a few games or after standby overnight uptime. I've only just started testing changes to Virtual Memory thinking it might be a delay caused there. But the post quote above gave me the thought it could be GPU video memory related. Anyone know where to check in the kernel for how much RAM is reserved for GPU on the Axon 7?
I also gave the resolution lowering trick a little try and that didn't seem to improve performance at all. I'm still on B32.
Sent from my ZTE Axon 7 using XDA Labs
Mind explaining how to get rid of the CPU/GPU throttle? I just haven't bothered with those kind of things since my Galaxy Nexus days ;_;
Isopropil said:
Mind explaining how to get rid of the CPU/GPU throttle? I just haven't bothered with those kind of things since my Galaxy Nexus days ;_;
Click to expand...
Click to collapse
The background I posted ages ago is here https://forum.xda-developers.com/axon-7/how-to/stock-cpu-gpu-throttling-performance-t3716060
That way doesn't fully disable throttling and just enables a different higher one. I could update the thread if people are interested
Sent from my ZTE Axon 7 using XDA Labs
Infy_AsiX said:
The background I posted ages ago is here https://forum.xda-developers.com/axon-7/how-to/stock-cpu-gpu-throttling-performance-t3716060
That doesn't fully disable throttling and just enables a different higher one. I could update the thread if people are interested.
Click to expand...
Click to collapse
Tbh thats quite an interesting thread for ppl that have either heating issues and want to lower voltages and edit throttling levels or for ppl that would like to have a more consistent performance when gaming. As you mentioned in that thread, i too renamed the 2 thermal config files with .bak at the end. Will test later to see the results.
But i think you could maybe update the thread with a guide for like:
-ppl that want to preserve battery life
-ppl that want to get more consistent performance
-and ppl that want to have a good mix between performance and battery life.
Also in that thread you mentioned disabling vdd restriction (like through kernel adiutor i guess). Is this necessary to really see the full effect of renaming the thermal engine files to .bak? I ask because i saw that inside the thermal engine files, there are also entries for vdd monitoring. So in the end would disabling vdd restriction actually do something? (Since the values from thermal engine files won't be applied at boot anymore after renaming them)
Sent from my ZTE A2017G running V1.2.0B08 using XDA Labs
I get some lag even in Angry Birds 2, never had this on my Sony Xperia XZ Premium. The reason is due to throttling from over heating.
The phone does indeed get hot after some heavy gaming and this is when throttling starts and causing some lag.
GodOfPsychos said:
Tbh thats quite an interesting thread for ppl that have either heating issues and want to lower voltages and edit throttling levels or for ppl that would like to have a more consistent performance when gaming. As you mentioned in that thread, i too renamed the 2 thermal config files with .bak at the end. Will test later to see the results.
But i think you could maybe update the thread with a guide for like:
-ppl that want to preserve battery life
-ppl that want to get more consistent performance
-and ppl that want to have a good mix between performance and battery life.
Also in that thread you mentioned disabling vdd restriction (like through kernel adiutor i guess). Is this necessary to really see the full effect of renaming the thermal engine files to .bak? I ask because i saw that inside the thermal engine files, there are also entries for vdd monitoring. So in the end would disabling vdd restriction actually do something? (Since the values from thermal engine files won't be applied at boot anymore after renaming them)
Click to expand...
Click to collapse
That's some useful suggestions. For each point
- I've already shared that function. Just modify to a lower voltage you prefer. In terms of using it in combo with throttling disabled, that can be more advanced.
- Consistent like powerful? Need to tweak values in the file for full performance. Personally I've edited several profiles of various CPU GPU configs to range from light games to heavy executable from Tasker.
- Really a matter of preference. There isn't really a perfect middle ground. That's why vendors are offering power mode switches for normal use and gaming. Problem there is ZTE's is shipped broken and others still have decided limits. Which as my previous point, I use a basic profile for normal use and switch to suit based on the gaming demand. The method in that thread alone is inefficient as it's moderately powerful but isn't power saving for example.
Yeah I meant in a kernel configuration app like Adiutor. It's rather confusing but IIRC switching on VDD is it's own set of restriction different than unmodified. Removing the files by renaming .bak falls back to some hidden profile as described in that thread. Now I just edit the file for no limits instead and use Tasker to change parameters when needed.
I may post a guide. But I'm not sure how much interest or benefit there is. Hardcore tweakers aren't on stock, it's probably only a small group that prefer stock for particular reasons and are still advanced tweakers. One factor against AOSP though is I've heard repeatedly in the past the GPU driver gaming performance is lacking, don't know if that has changed. I'm all for helping out though, just unsure about useless effort. I welcome questions to get anything working and it's more direct than writing up a whole guide.
Sent from my ZTE Axon 7 using XDA Labs
Infy_AsiX said:
That's some useful suggestions. For each point
- I've already shared that function. Just modify to a lower voltage you prefer. In terms of using it in combo with throttling disabled, that can be more advanced.
- Consistent like powerful? Need to tweak values in the file for full performance. Personally I've edited several profiles of various CPU GPU configs to range from light games to heavy executable from Tasker.
- Really a matter of preference. There isn't really a perfect middle ground. That's why vendors are offering power mode switches for normal use and gaming. Problem there is ZTE's is shipped broken and others still have decided limits. Which as my previous point, I use a basic profile for normal use and switch to suit based on the gaming demand. The method in that thread alone is inefficient as it's moderately powerful but isn't power saving for example.
Yeah I meant in a kernel configuration app like Adiutor. It's rather confusing but IIRC switching on VDD is it's own set of restriction different than unmodified. Removing the files by renaming .bak falls back to some hidden profile as described in that thread. Now I just edit the file for no limits instead and use Tasker to change parameters when needed.
I may post a guide. But I'm not sure how much interest or benefit there is. Hardcore tweakers aren't on stock, it's probably only a small group that prefer stock for particular reasons and are still advanced tweakers. One factor against AOSP though is I've heard repeatedly in the past the GPU driver gaming performance is lacking, don't know if that has changed. I'm all for helping out though, just unsure about useless effort. I welcome questions to get anything working and it's more direct than writing up a whole guide.
Click to expand...
Click to collapse
Well a guide might be useful for many users. Maybe also what your setup in tasker is.
Personally im usually not that into graphic intensive mobile games (except for like shadowgun legends, cool game imo).
I mean i play games while watching youtube or any series sometimes. But its still annoying when games start to lag after like 10 minutes already.
I also play hearthstone alot on my axon 7 since i used to play it alot on my laptop (sadly the game lags way too much now on my laptop due to weak hardware, hence why i play it on mobile now).
About the consistent performance i mentioned earlier, yes i meant as in powerful which keeps the performance without dropping down.
Sadly the performance governor isnt a big help since the aggressive throttling is still active, which makes the governor quite useless if it cant keep up the cpu clock at max.
Anyway, from what i noticed after renaming the 2 thermal files, shadowgun legends for example runs better for a longer period of time than before (it takes longer before the game starts to drop frames significantly)
Sent from my ZTE A2017G running V1.2.0B08 using XDA Labs
With most GPU intensive apps and games like PUBG and Daydream View, I have to disable the Night Light. It provides a noticeable difference in performance.
@ Isopropil,
Hi,
Would you like to post your screenshot here? I experience the same problem and we probably help each other. My phone is A2017U, what about yours?
Thanks in advance!
Hope to hear you soon!