I've been looking for a bit, but haven't yet found any summary of how all thse power-saving options in Advanced Config work. I was hoping for something that gave a roundup of :
1) How much each option really saves
2) What the performance tradeoffs are
For instance, if you turn on power saving for SD, does SD access slow down? Does battery life improve measurably? Is there a momentary lag on SD access but it's fine when it gets going. -- and that's just one option of many.
Or for some of the protocol power-saving options -- do any of them interfere with service or cause problems with apps that poll for updates/downloads (like mail)?
Hi, I'm not really happy about my Moto G LTE performance.
I keep reading everywhere that it's very smooth but this is not the case for me.
I notice quite a lot of scrolling slowing/lagging in almost all apps (even sometimes in the UI menus) I don't have any 3rd application installed (just WhatsApp) and completely stock 4.4.4.
For example, when I scroll through a Whatsapp group chat there are some little jitters, Scrolling the notification drawer lags almost every time but depends on the currently active app. If Chrome is active with some desktop site it can lag very badly.
Chrome performance are quite nice but again, random hiccups for no visible reason.
Interesting thing is that the lags are very random, It sometimes goes away by itself and gets back.
Tried deleting cache partition, tried factory reset, not working. I do notice improvement if I'm on WiFi and not HSPA/LTE.
I tried checking my CPU usage under Developer options and the load average for the system is never going down from 16. Even if I'm in airplane mode with no activity. Do you think it has something to do with my slowness? I'm quite familiar with Linux systems and know that 16 is extremely high for any desktop/server. Is android the same case or this loads are normal?
https://i.imgur.com/vam1Dx2.png
Also here is a screenshot of "Profile GPU rendering -> show as lines" under developer settings when scrolling in whatsapp.
http://i.imgur.com/t1BTNPQ.png
As you can see the framerate is not stable at all and many lags occur.
Would appreciate if someone could check his results with the profile GPU rendering and tell me if it's the same or much better.
Any help will be welcome, Thanks!
I got a little slow down but nothing mayor..howewer you can look my test in arr
Sent from my XT1032 using XDA Free mobile attachment
Are you in the stock or custom rom?
I notice very diffirent performance in many roms. The worst was the stock 4.4.4 of my company (with all the **** of Movistar) and the actuals versions of lollipop...
Recommended:
http://forum.xda-developers.com/moto-g/development/xperience-cyanogen-projectoverkill-t2949592
I seemed to get a lot more lag on 6.0 than from what I remember on 5.1.1. Tried multiple roms and they all felt the same. However after toggling in developer options "force gpu rendering" as well as "disable hardware overlays" on, this phone is like butter now smoother than ever. Hopefully this proves to help others.
Cool, I'll give.it a shot too
Sent from my XT1575 using Tapatalk 2
This did seem to make my phone faster it scores higher in quadrant too.
Still froze on game.
Sent from my XT1575 using XDA Free mobile app
I'm running stock (non-rooted) and I haven't had any lag issues (yet) since updating to 6.0. App transitions especially are incredibly smooth. Still all phones get laggy eventually (I don't care what chipset or software they're running), and this is certainly worth logging for when I do have problems. Thanks.
timde9 said:
I seemed to get a lot more lag on 6.0 than from what I remember on 5.1.1. Tried multiple roms and they all felt the same. However after toggling in developer options "force gpu rendering" as well as "disable hardware overlays" on, this phone is like butter now smoother than ever. Hopefully this proves to help others.
Click to expand...
Click to collapse
thank u sooo much bro now my phone is blazing fast!!!! hope their are no negative effects of these options
timde9 said:
I seemed to get a lot more lag on 6.0 than from what I remember on 5.1.1. Tried multiple roms and they all felt the same. However after toggling in developer options "force gpu rendering" as well as "disable hardware overlays" on, this phone is like butter now smoother than ever. Hopefully this proves to help others.
Click to expand...
Click to collapse
Have you noticed any negative effects on battery life?
Sent from my XT1575 using Tapatalk
Shishir Singhal said:
thank u sooo much bro now my phone is blazing fast!!!! hope their are no negative effects of these options
Click to expand...
Click to collapse
Well, if you force GPU rendering there is a possibility that battery life may take a hit. And if you disable HW overlays you open up the possibility of rendering errors that *may* affect performance in some circumstances.
These are tradeoffs you need to weigh to make sure this will be beneficial to you or not.
I'm running TruPure XMM 2.2 and haven't had any significant lags yet and for me the settings didn't make a real difference.
I don't want to lose extra battery life on something that doesn't change anything FOR ME (=doesn't apply to everyone!).
Thanks for sharing this information though
Why Lag??
timde9 said:
I seemed to get a lot more lag on 6.0 than from what I remember on 5.1.1. Tried multiple roms and they all felt the same. However after toggling in developer options "force gpu rendering" as well as "disable hardware overlays" on, this phone is like butter now smoother than ever. Hopefully this proves to help others.
Click to expand...
Click to collapse
Did we all get defective chipsets??? Why are we the only ones getting lag, but the majority of people are reporting "buttery smooth" performance on Marshmallow...?
Hi guys, I saw on reddit that if you have certain Accessibility services enabled, lag and stutters will occur. For example, Dashlane's Accessibility feature slowed my phone down like crazy. After disabling it, smooth operations persisted. It's weird. I'll get the reddit link.
Edit: somehow can't share the link but I'll quote what OP said.
"I've had the Moto X Pure for two weeks now, and have been experiencing excseive stuttering when doing just about anything. The strange part was some users where experiencing lag while others weren't. Well for those experiencing stuttering while scrolling lists, try this. Go to Settings, Accessibility, and turn off all accessibility services at the top. Should fix lag!"
Sent from my XT1575 using Tapatalk
Zero lag on my phone. I'm running stock, though.
Those two options will cause issue with some games.
Will these settings stick through a reboot, I know the Disable HW Overlays never used to stick. It does make it noticeably smoother. I was planning on returning to LP tonight, and flashing AICP LP to get some smoothness back. It always feels like Android moves backwards when they remove features and get more and more laggy with each rendition! lol
DroidOnRoids said:
Hi guys, I saw on reddit that if you have certain Accessibility services enabled, lag and stutters will occur. For example, Dashlane's Accessibility feature slowed my phone down like crazy. After disabling it, smooth operations persisted. It's weird. I'll get the reddit link.
Edit: somehow can't share the link but I'll quote what OP said.
"I've had the Moto X Pure for two weeks now, and have been experiencing excseive stuttering when doing just about anything. The strange part was some users where experiencing lag while others weren't. Well for those experiencing stuttering while scrolling lists, try this. Go to Settings, Accessibility, and turn off all accessibility services at the top. Should fix lag!"
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
thanks for the tip!
after switching off the accessibility service for lastpass the scrolling is much smoother again ?
nuumuun said:
thanks for the tip!
after switching off the accessibility service for lastpass the scrolling is much smoother again
Click to expand...
Click to collapse
I can attest to this as well actually I remember seeing that article when I was on Lollipop but I just forgot it. Appreciate the reminder it seems to have helped even further. I decided to turn off the hw overlays thing but the force gpu rendering and all accesibilty services off seems to be just as good.
I had horrible lag on everything I did on MM until I put on TruPureX rom. Now it's better than ever. Smooth as silk.
Disabling HW overlays prevents the CPU cores from assisting the GPU in rendering certain things on-screen. The build.prop already forces GPU rendering (as does stock Android) and some form of HW overlay setting.
debug.sf.hw=1
debug.egl.hw=1
debug.composition.type=c2d
These lines are in both 5.1.1 and 6.0 Pure Edition builds. Line 1 is GPU 2D rendering, line 2 is OpenGL ES HW rendering, and line 3 is Core2Duo compositing (using a multicore processor for composition, in addition to the GPU).
If you're rooted, bigger performance gains would be had by raising the throttling temps in thermal-engine-clark.conf in /system/etc. Don't go crazy, otherwise your hand or device may pay the price. Leave the 85C values alone, as the A57s will hit this quickly at 1.824GHz. But, CPU hotplug controls when the 2 A57S and 1 A53 get booted for thermal reasons. Quiet1 and Quiet0 control Cluster 1 (A57s) and Cluster 0 (A53s), respectively.
So ...
A quick test some may perform, so long as nova launcher is installed, is to open the app drawer, scroll or flick down and then immediately click home. Before these settings were applied, I constantly noticed stutter coming out of the drawer. This may seem like a silly test, but there are, in my experience, many moments of stutter in everyday use running the stock roms (my brief run of cm was noticeably smoother.)
I wouldn't say these settings insanely increased performance, but a few of the stutters I had frequently seen in the app drawer or recent menu have pretty much disappeared thus making it somewhat worthwhile.
Sent from my XT1575 using Tapatalk
Jason.DROID said:
Disabling HW overlays prevents the CPU cores from assisting the GPU in rendering certain things on-screen. The build.prop already forces GPU rendering (as does stock Android) and some form of HW overlay setting.
debug.sf.hw=1
debug.egl.hw=1
debug.composition.type=c2d
These lines are in both 5.1.1 and 6.0 Pure Edition builds. Line 1 is GPU 2D rendering, line 2 is OpenGL ES HW rendering, and line 3 is Core2Duo compositing (using a multicore processor for composition, in addition to the GPU).
If you're rooted, bigger performance gains would be had by raising the throttling temps in thermal-engine-clark.conf in /system/etc. Don't go crazy, otherwise your hand or device may pay the price. Leave the 85C values alone, as the A57s will hit this quickly at 1.824GHz. But, CPU hotplug controls when the 2 A57S and 1 A53 get booted for thermal reasons. Quiet1 and Quiet0 control Cluster 1 (A57s) and Cluster 0 (A53s), respectively.
So ...
Click to expand...
Click to collapse
Can you provide your settings? kinda scared to touch because idk which cpus are the a57 core0 core2 or core 4 5?
Hi fellow Mate 7 owners. I've seen mention of stuttering here before. The phone is reasonably powerful and it intrigued me as to why it stutters, especially when scrolling. It helped to remove the Huawei launcher after setting up Smart Launcher Pro and de-bloat system apps, but I still saw some stutter so turned animations to. 5, then off altogether. My phone runs quite efficiently but that minor jerkiness bothered me. I've now enabled the "force GPU rendering" setting in developer options and re-enabled animations. It runs a lot nicer. Smooth and fast.
I'm assuming the cause was just that where possible, it tries to run on the 1.3GHz economy processor which is not fast enough for frequent screen redraws where content has to be recalculated.
So, my question to those who are tech savvy with the more complex workings of Android is, can we edit something in the system that tells the phone how to control CPU governing so that it steps up to the 1.8GHz processor easier for a smoother operation?
I don't want to install an extra governor app from Google Play.
Edit:
I've ended up installing Kernel Adiutor (needs root) so that I can alter settings and see how it's affected in case it's possible to alter the kernel permanently.
Changed a few settings with CPU governor and I/O scheduler. Kept forced GPU setting in developer options and animations at 0.5.
Edit:
Uninstalled Kernel Adiutor as I had trouble with settings not all sticking and sometimes performance suffering.
I've now installed EX Kernel Manager and two good monitoring apps by same dev. Better result so far. Settings seem to stick and the phone is more reliable. It's smoother, snappy to use. Another thing this has also benefited is stable bluetooth streaming of music. I used to get dropouts, now it's like it's connected by aux cable. This is a big thing for me as I use it on BT for music a lot. It can multitask whilst streaming music and still not drop out momentarily.
https://play.google.com/store/apps/details?id=flar2.exkernelmanager&hl=en
I don't know if anybody else here has suffered this, but I've read several times when googling, that many XZP devices came with input lag out of the box. My device has always suffered with this, and flashing custom ROMs didn't seem to make a difference.
Input lag means that sometimes, keystrokes/touches are completely missed and sometimes scrolling misses too.
I unlocked my bootloader really early on, so I never wanted to send it back as I'm sure this voids my warranty.
I tested for a faulty digitizer using various screen input test apps from playstore, and they usually don't show any areas of the screen as faulty. This has always made me believe that it was most probably a software issue.
Today I discovered that yes indeed, my issue is definitely a software issue.
THE FIX:
Changing the screen resolution to 4k (3840x2160), and DPI to 821.
I've tried this before but never noted the difference in touch input. Perhaps because I wasn't looking for it.
Today I tried it again and much to my surprise, this time I noticed a HUGE improvement to input sensitivity and for now has 100% alleviated the problem. Typing, tapping and scrolling works perfect now.
This is most likely caused by the screen having to rescale pixels from 1080p to 2160p, making extra work for the CPU, but I'm no expert so I might be wrong. But it works for me.
I'll also note that I'm using Turbo ROM p75B now, and the input delay was still there until changing the resolution.
I'd like it if somebody who has suffered the same issue could provide feedback, I really hope this helps you too, as this was the only real issue that have me buyers regret, and it now works wonderfully.
Cheers.
Edit: I do believe this topic might be better recognised in the guides and discussions category. If so, could a mod please move it there.
Luckily I haven't had this input lag issue. However, I do get input lag if I have stamina mode turned on, and set to battery time preferred.
Just so you know, you do know that you're only emulating 4k, right? The only way to set the display to 4k is on AOSP.
@iKlutz I can't seem to find the resolution settings lol
Yes I understand that it's only "emulating" 4k and that it's not native 4k. It also uses more battery, which would suggest higher CPU usage, which in part contradicts my theory about rescaling causing input lag.
Perhaps it is something to do with the "touch map" (I can't think of the term), the software/grid that maps out the touchable area to the digitizer, having to resize from 1080p to 2160p, making the grid inaccurate? But it wouldn't make sense as to why it only affects some devices.
Also, I do not have stamina mode enabled as it's almost pointless in today's phones. I believe limiting processing speed only makes process queus take longer to finish, which means that CPU takes longer to idle. It only saves a negligible amount of battery unless your phone screen is off for 80% of the day. Almost as pointless as closing applications and cleaning RAM, as your phone will just use more battery rebuilding caches and restarting processes.
In any case this has completely alleviated the issue for me, so I hope someone on Google ends up here and this may be a solution for them too.
gavster26 said:
@iKlutz I can't seem to find the resolution settings lol
Click to expand...
Click to collapse
There are some threads here that explain various methods to change the VM resolution and scaling. If you're unfamiliar with ADB, I suggest you read very carefully and take precautions, as setting the resolution wrong could make it really difficult to reverse the procedure and we currently don't have a way to make TWRP backups.
i noticed this too.. but i enabled glove mode and things sorted by it self..
this kinda works, it happens very much less frequently but it does still happen