yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) General] timde9:
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.
[X Style (Pure) General] Cowbell_Guy:
Cool, I'll give.it a shot too
[X Style (Pure) General] mirrin:
This did seem to make my phone faster it scores higher in quadrant too.
[X Style (Pure) General] chindynasty:
Still froze on game.
[X Style (Pure) General] EdCarden:
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.
[X Style (Pure) General] Shishir Singhal:
thank u sooo much bro now my phone is blazing fast!!!! hope their are no negative effects of these options
[X Style (Pure) General] mademan420:
Have you noticed any negative effects on battery life?
[X Style (Pure) General] hbar98:
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.
[X Style (Pure) General] noneandnonly:
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 :)
[X Style (Pure) General] enlight311:
Why Lag??

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...?
[X Style (Pure) General] DroidOnRoids:
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!"
[X Style (Pure) General] MattBooth:
Zero lag on my phone. I'm running stock, though.
[X Style (Pure) General] max1001:
Those two options will cause issue with some games.
[X Style (Pure) General] HikingMoose:
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
[X Style (Pure) General] nuumuun:
thanks for the tip!

after switching off the accessibility service for lastpass the scrolling is much smoother again ?
[X Style (Pure) General] timde9:
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.
[X Style (Pure) General] bw03:
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.
[X Style (Pure) General] Jason.DROID:
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 ...
[X Style (Pure) General] kvlt:
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.
[X Style (Pure) General] george241312:
Can you provide your settings? kinda scared to touch because idk which cpus are the a57 core0 core2 or core 4 5?
[X Style (Pure) General] Jason.DROID:
Yet nothing helps the poor JavaScript performance in Chrome when running 64-bit Android builds and a 32-bit browser.

Disable JavaScript in Chrome and browse the web. Yes, some things will be broken, but visit your favorite sites. Then, do the same with JS enabled. It's a HUGE difference in performance, and I don't doubt that it affects Java-based apps (versus native).

Something isn't quite right in 64-bit Android. Performance, for me, with those developer settings on or off doesn't really change. What does change is performance in warm or cold environments. It's 36F outside right now, and my phone flies when I'm out there. Come back into my warm room, and throttling hits it.

---------- Post added at 09:29 PM ---------- Previous post was at 09:21 PM ----------

The file tells you.

Cluster0 is CPU0-3 (4 A53s)

Cluster1 is CPU4-5 (2 A57s)

Raise them only a few degrees at a time, as increasing temps also increases voltage requirements. Instability can creep in if you let them run too hot.

Look at HOTPLUG_CPU5. This is the first A57 to get booted at 44C. The disablement clears at 42C and CPU5 is again allowed to be used by the system.

Other values control when the clusters are throttled to frequencies based on temperatures. A57s always get kicked down first on Cluster1.
[X Style (Pure) General] Jason.DROID:
Duplicate ... grr

EDIT: Might as well make this useful. Here's an untested and somewhat aggressive thermal config file that I made. Ensure you have a complete backup, and I'm not responsible if it fries your hand, burns out your SoC, or any other such damage. Use at your own risk.

This file has conservative clear temps, so once the CPUs hit a target, they'll go offline or throttle until they cool to the set clear temperature. This is to prevent severe overheating. Actual thermal limits are increased, however, so there's a bit more processing power UNTIL you hit the limits.

Recommended usage:

Web browsing

Email

Picture taking

etc.

NOT recommended:

Intensive CPU/GPU usage from 3D games or prolonged usage in benchmarks; it WILL run hot and may crash

As I said, it's untested. You can fine tune as needed for your usage patterns.

Be sure to remove the .txt from the filename.

You can also do something completely different as well, and boot 2 CPUs from Cluster0 long before Cluster1. This would keep the A57s active longer, while turning off 2 A53s to stay within the thermal envelop the SoC is designed for. The file I made probably exceeds TDP in very intensive situations, so be careful. Unfortunately, only 1 A53 is designed to shut off. I'm not sure if you can add in a HOTPLUG for the other A53 cores, but if you can, you could run 2 A53s and 2 A57s at full speed for much longer. Nothing wrong with a quad-core, IMO.

For example, you'd change HOTPLUG-CPU4 and HOTPLUG-CPU5 thermal to high limits (say 60C), so they don't go offline quickly. You'd then boot CPU2 at a low temperature to keep it offline, and try to boot CPU3 as well via HOTPLUG (create a new HOTPLUG-CPU3 field mirrored off of CPU2). That way, you have CPU0-1 (A53s) and CPU4-5 (A57s) active and can set thermal limits for them. I don't know how well this would work, but you want the A57s to stay online longer for better performance, and without 2 of the other cores, the SoC wouldn't get hot as quickly.
[X Style (Pure) General] Shishir Singhal:
it seems that after enabling these setting battery life is hit significantly and MXS is not known for its battery life its a huge letdown.

for now disabled these settings and looking for any other solution.
[X Style (Pure) General] drivenby:
I have no lag on MM, performance I'd slightly better as compared to LP
[X Style (Pure) General] george241312:
Thanks for the info.

Well what i did is completely remove all of the hot-plug entries and put monitor quiet 1 and 0 to start throttling at 70c 72c 74c and setpoint clr at 65c. Since qualcomm made it so 85c is the limit before the cpu turns off id say its pretty safe to run it at 70c.

Im not really noticing any difference in heat coming from the phone in benchmarks compared to stock. With regular usage it performs snappier.

With the testing i did last night the temps do go a little high with my config 70c average temps and 80c on just one temp sensor at full load non stop bench marking. The reason why i made it so all cores would throttle at the same temperature is so that the workload can be divided evenly and in the end produce less heat. My theory is that if there is a huge workload on the CPU with stock conf the temperatures wont differ compared to only throttling at 70c because with stock conf Cores will start to turn off midway and therefore increasing the workload to the 2 or 3 Cores that haven't throttled yet and therefore increasing the heat to only those cores in the end the phone would reach the same temps compared to only throttling at 70c. with my config i got a better score on antutu 65k but the phone was not as hot compared to stock conf maybe because it finished the workload faster?

Anyways since qualcomm set its limit at 85c i think its safe to run it at 70c. maybe the cpu can withstand even higher temperatures than 85c but it is not safe for the materials around the cpu like plastic and other stuff. Dont really care for the CPUs Life longevity since most people get a new phone within a year to two years if it lasts that long. but i don't think there is any repercussions from letting it get to 80c.
[X Style (Pure) General] Jason.DROID:
Interesting. Those are high limits. 85C refers to the active temp sensor on each core, while the other cluster temps are overall averages. It's similar to a PC CPU. The A57s hit 85C very quickly at max speed. I've seen it in CPU-Z while running Geekbench, but average temperatures rarely rise above 40-45C. What you've done is raise the average thermal limit to above 70C, and I do think that will ultimately be harmful to the battery and other components. The battery shouldn't see temps above 50C. With it in close proximity to the SoC, your battery could catch fire if the SoC goes nuts.

The HOTPLUG entries control thermal core parking to remain within TDP. The S810 is a 10W+ SoC, but is throttled to stay within bounds. I think the S808 is around a 7.5W TDP SoC. So, the SoC needs to dissipate 7.5W of heat energy at full bore. IMO, it's not wise to remove the HOTPLUG entries.

EDIT: Look at the attached screenshot. tz_sensor13 and 14 are the A57s internal temperatures (not outside skin). They hit 85C at 1.824GHz, but quickly drop from it too once load is removed.
[X Style (Pure) General] TigerCourage:
Just restart your device once in a while and it will run blazing fast. I checked the memory and at some point of doing just easy tasks for a week I was left with 149mb free ram. I restarted the phone and now it has 493 and it's blazing fast and smooth again.
[X Style (Pure) General] pradeepvizz:
Quite interesting tweaks and that was what i wanted to do with my phone after unlock.. still on stock at the moment now.

can you post your thremal config? i guess many other ppl would be interested.

Edit: didn't see the later posts :)

Can i suggest moving the conversation to a new thread so that we can discuss and make a optimized thermal config for the Moto X Pure?
[X Style (Pure) General] timde9:
So after a while I got really sick of having to enable these hacks just to get good performance and so I switched from trueputex 2.2.1 to a stock rooted odexed rom and the improvement is Massive. Perhaps deodexed isbwhats causing lags
[X Style (Pure) General] HikingMoose:
Deodexing always decreases performance. Odexing is optimizing the apps. They load faster and run better. So removing the odexing, is de-optimizing it. But good luck telling developers that.

Just a follow up for people with media issues. I could not play Pandora or watch videos (youtube) on my phone with the "force GPU rendering" enabled. So I turned it off, and kept the "disable HW Overlays" on, and it's still smooth-ish, but now Pandora can play, and I can watch vidoes!! I was about the throw my phone into the street before I figured out the issue! I hope it helps someone.
[X Style (Pure) General] kiefferbp:
I shouldn't have to do this crap for a 2015 flagship running Marshmallow.
[X Style (Pure) General] HikingMoose:
I couldn't agree more! While it's my favorite phone I've owned, I'm also very let down. I come from a long time Samsung user, which have their own problems and lack of development, buy at least they're the most feature rich phones out there.
[X Style (Pure) General] erikiksaz:
This MM bug affects all phones running accessibility services. Look up the bug reports, it affects Samsung's to the Nexi phones.
[X Style (Pure) General] kiefferbp:
My Nexus 5 has no lag issues whatsoever on 6.0.1 with several accessibility services enabled (and the same ones I would use on my Moto X). I just put in an order for a 6P. This is what I get for betraying the Nexus line. Screw this Lenovo crap.
[X Style (Pure) General] erikiksaz:
Well, I'm too lazy to look up the bug reports on google's site again, but the 6P and the Note 5 were definitely affected by this bug.

Good luck.
[X Style (Pure) General] HikingMoose:
Crap, I spoke to soon. I returned to stock LP tonight, and let it update to MM. I'm on stock MM, no root, no exposed, Pandora still can't play. I hope they come up with a fix soon.

And before the accessibility thing comes up, the only feature enabled is auto-rotate. So that blows the accessibility theory out of the water. lol
[X Style (Pure) General] jcasares:
Coming from a One Plus One it's quite a disappointment the lag that shows this phone at some times.

What I am able to reproduce every single time and helped me pointed out the origin of the issue is when playing for a long time at Hay Day game. This one has a lot of graphic detail and activity so with a QHD display it was no wonder it will be stressful to the processor (both CPU and GPU). The problem is that the phone starts to get extremely hot and at that time I believe Qualcom's throttling starts to act and impairs the fluidity of the game. I tried the recommended developer settings from this post but they don't help that much; they reduce the occurrence but don't remove the lag.

I believe that the recommendation about adjusting the throttling posted here might be better but I wonder if it's good to do that. It is already hot like "can't hold the phone" with the standard settings. Changing that might crash the phone/game or even worse I think. Any experiences with that anyone can share?

I wasn't able to reproduce it at many other places so that might be why some people don't see any lag. If you're not a heavy user this phone might be nice for you but for me it's quite a disappointment so far (not that the One Plus One was perfect either).
[X Style (Pure) General] HikingMoose:
I don't even have a game installed on mine, and it is very laggy. It has choppier scrolling than a 7 year old device on Froyo. It's par for the course though, android always regresses, never progresses. They take features away, instead of adding. Once they get it performing somewhat well, and scrolling smoothly - they go and ruin it. lol

I think the lag might be what causes Pandora to skip several times until it's at the end of the song - then it starts playing for the last 20s of the song. Pandora does this even after a fresh, clean, install. So it's not an app, root, or xposed issue. It has to be just the poor performance of MM.
[X Style (Pure) General] trojan92:
This hasn't worked for me. I've been experiencing lag on my X Style since installing M and nothing, including this, has fixed it :(
[X Style (Pure) General] kcipopnevets:
I know nobody's happy about the Lenovo acquisition but can we just think rationally before blaming EVERY flaw with this phone on Lenovo themselves?
[X Style (Pure) General] kiefferbp:
I'll blame the ghost of Christmas past for this problem then since they clearly made the phone. Thanks!
[X Style (Pure) General] kcipopnevets:
It has been pointed out multiple times that this is not exclusively a Motorola issue.
[X Style (Pure) General] kiefferbp:
I've found another way to reproduce lag that occurs with no accessibility services enabled and with these developer options checked. Open Sync for Reddit and open a reddit post. Click on someone's profile from the post and then click on a post/comment that redditor has made. From there, repeat the process to make Sync for Reddit go several layers deep in posts and comments, so that you have to swipe a bunch of bunch to be able to pull out the sidebar again. After enough layers, the app will lag like crazy until you swipe away a lot of layers.

This lag is not reproducible for me on Lollipop, and the same goes for my Nexus 5 on Marshmallow, so it appears to be a MXPE + MM problem.

EDIT: I am actually able to reproduce this on my Nexus 5, but I have to go a lot deeper than my MXPE to get lag. My MXPE starts lagging after only a few layers (not too bad, but definitely noticable, with it getting significantly worse after several more layers), but the Nexus 5 only lags after around 15 or so.
[X Style (Pure) General] erikiksaz:
I don't believe any QHD phones equipped with 2015 snapdragon processors were any better off than their 2014 counterparts running 1080p screens. We would all have been better off had Motorola + LG + Google chose SD805s instead of the stupid 808 this time around. The only reason why the Nexus 6P gets decent battery life with its power-hungry SD810 is because it has a huge battery. If given a 3000ma battery, it would be just as poor at battery life as the M9.
[X Style (Pure) General] jcasares:
I was quite happy with the One Plus One 801 processor. It was fast enough and even when it was warm while playing Hay Day it never slowed down.

I didn't change for speed or screen quality, I changed because of the instability with the OS mainly. CyanogenOS is a mess in this device.

I never got a perfectly working compass. Radio was quite unstable (dropping signal every now and then). Camera crashed all the time. WiFi had an issue with DHCP that they didn't fix in more than 6 months and caused me issues at work. Bluetooth had some instability issues as well. On top of that I had to cope with a barely usable screen for months until they fixed the touch panel issues.

I can't blame all on Cyanogen but I know them from previous phones and their roms are all but stable. In this case it was an official phone with the official rom. So, not working properly wasn't out of their hands (liek with Samsung phones).

Standard Google OS has now many features I looked for in CyanogenMod so I don't see a compelling reason to use an unstable OS anymore.

I believe Qualcom has issues with new processors; they run too hot and don't perform much better. I might look different to Intel processors in the future. The ASUS Zen Phone has impressed me while being a relatively cheap phone. I wonder what they can do with a top of the line unit.
[X Style (Pure) General] max1001:
This is the price you pay if you want fast update. 6.0 wasn't ready for this point but they pushed it out anyway. My bigger beef is the new adoptable storage.
[X Style (Pure) General] patt2k:
Using vaidms kernel makes huge difference maybe not batterybeise but performance wise. And yes odexed roms seem to be little faster even though roms can be heavier by 1+gb
[X Style (Pure) General] HikingMoose:
I bet there are build.prop edits we could make that would speed things up. I raised the dalvik heapsize, but didn't improve the scrolling :(
[X Style (Pure) General] kiefferbp:
It has been a while since I have posted, but my 6P has no issues whatsoever with accessibility settings.
[X Style (Pure) General] max1001:
6.0.1 fixed the lag on Nexus device from what I noticed a least on Nexus 9. 6.0 was a complete disaster for the N9. It was using a single core soc from Android 4.
[X Style (Pure) General] relikborg:
Works!

Thanks so much, has really helped my moto x pure!
[X Style (Pure) General] nativedroid:
Thanks helped my phone run better :):good:
[X Style (Pure) General] rehpyc:
A big part of the lag is the kernel/governors used. A custom kernel like Frankenclark should reduce or eliminate the lag, but the kernel can be tweaked even further for complete smoothness.
[X Style (Pure) General] SenK9:
I used to have wakeup lag and notification dropdown lag (when pulling down the shade). Even after turning on GPU rendering and checking accessibility access, still existed. However, as crazy as this sounds, I found that after changing the CPU governors (for both big/little) to 'intelliactive', instead of the default interactive, and messing around with CPU hotplugs a bit, lag is completely gone, going on close to a week now, fingers crossed. Using MHC19Q (6.0.1) on Temasek's CM13 for reference.
[X Style (Pure) General] benjmiester:
It may help standby... I mean only 2% lost in 7.5 hrs and in a crappy signal area is waaaaay less than usual for me. Latest DU 10.2.

I haven't noticed any additional drain in during usage battery life either. If anything, it seems slightly better but hard to measure for me as I have to GPS 100% of the time I'm at work (that's why the high GrubHub app usage)

Moto X Pure Rooted & Rom'd
[X Style (Pure) General] quakeaz:
I'm curious, what did you change as far as CPU hotplugs? Which CPUs, the "BIG" A57 cores? Change hotplug thresholds, clear threshold, etc?
[X Style (Pure) General] jahciple:
Anyone try this app?

https://play.google.com/store/apps/details?id=com.lucky.one
[Nexus 5X Q&A, Help & Troubleshooting] rskyline:
I'm having too slow speeds over T-Mobile on DFW area. Tried another sim card and I got the same issue. Apparently other phones in my area are OK. Anyone have a clue? Or I have to get a replacement? TIA
[Nexus 5X Q&A, Help & Troubleshooting] EeZeEpEe:
The only real way to kind of prove that it's your phone and not your service is to do speed tests with a few other T-Mobile phones along with your 5X. And if the other are consistently higher, then maybe it's possible its your 5X.

Also, did you get 6.0.1 which give you band 12 LTE?
[Nexus 5X Q&A, Help & Troubleshooting] rskyline:
I'll try to do that whenever I'm getting slow speeds again because unfortunately I never have another tmo phone with me to test when it happens. And also after 7-8pm the speeds gets high again. Weird.