Database Users

XT1095 (Pure Edition) future updates

Supposedly the Pure Edition of the Moto X gets the updates earlier, and we're seeing other versions of the Moto X gets 5.0.2 and we're still in 5.0. Does anybody have some news on a new update? A soak test of 5.1 would be awesome now.
I started this thread because there's no other thread of this particular situation.
Sorry for my english.

I'm still on 4.4.4 be patient

I'm also on 5.0 isnt 5.1 already out?

I think that they are waiting for 5.1 release as it will come in March.

-iNSiGhT- said:
I think that they are waiting for 5.1 release as it will come in March.
Click to expand...
Click to collapse
I hope so! Maybe we can use this thread to comment this!

I keep getting notifications about the lollipop update(I'm on 4.4.4) on my phone I got a few days ago, going to root it in the next couple of days so I can stop the notifications.
I'm not touching lollipop until the problems are sorted out plus I hate the WiFi and signal icons in lollipop.

GTCC said:
I keep getting notifications about the lollipop update(I'm on 4.4.4) on my phone I got a few days ago, going to root it in the next couple of days so I can stop the notifications.
I'm not touching lollipop until the problems are sorted out plus I hate the WiFi and signal icons in lollipop.
Click to expand...
Click to collapse
I like the new icons, but the RAM management it's getting kind of annoying.

GTCC said:
I keep getting notifications about the lollipop update(I'm on 4.4.4) on my phone I got a few days ago, going to root it in the next couple of days so I can stop the notifications.
I'm not touching lollipop until the problems are sorted out plus I hate the WiFi and signal icons in lollipop.
Click to expand...
Click to collapse
Just go disable Motorola OTA under settings
Sent from my XT1097 using XDA Free mobile app

GTCC said:
I keep getting notifications about the lollipop update(I'm on 4.4.4) on my phone I got a few days ago, going to root it in the next couple of days so I can stop the notifications.
Click to expand...
Click to collapse
Just force stop Moto OTA in apps. Gets rid of that notification until you reboot the device.
Link_proxXP said:
The RAM management it's getting kind of annoying.
Click to expand...
Click to collapse
I agree. That and the horrible battery life associated with the way Lollipop currently is.

Uhhhhh, problems with 5.0? I don't get it. I've been running 5.0 since I got this thing, 2 weeks now, and its been amazing. Coming from a 2013 X, this thing flies. No ram issues that I have seen. Battery life, same as 2013 X for me, actually a little better with over 10hrs on Bluetooth headset. But then I was running Xposed so that might have caused some issues with my Old X.

overthatscreen said:
Uhhhhh, problems with 5.0? I don't get it. I've been running 5.0 since I got this thing, 2 weeks now, and its been amazing. Coming from a 2013 X, this thing flies. No ram issues that I have seen. Battery life, same as 2013 X for me, actually a little better with over 10hrs on Bluetooth headset. But then I was running Xposed so that might have caused some issues with my Old X.
Click to expand...
Click to collapse
The battery life could be better. The RAM management causes that some apps -like the launcher- keeps closing while you're using other apps.

The battery life is about what I expected for a screen the size it is with such a small battery, a decent improvement over my smaller N5 with same size battery, albeit over a year old. As for memory management, I had occasional launcher redraws and apps not staying in memory when when N5 updated to lollipop, but have not experienced this at all on my Moto X. I also essentially started fresh on 5.0, powered my moto x up, went through setup, updated immediately to lollipop, and went ahead and did a factory reset. So maybe the fact my phone wasn't used on KitKat at all before updating saved me some problems, don't know. All I know is I don't have memory issues, had my phone a little over 2 weeks now, and today was the first reboot (to apply a screen protector) I've done since day 1.
Sent from my Nexus 7 using xda premium

Moto X 2014 & Lollipop 5.0
95Z28 said:
The battery life is about what I expected for a screen the size it is with such a small battery, a decent improvement over my smaller N5 with same size battery, albeit over a year old. As for memory management, I had occasional launcher redraws and apps not staying in memory when when N5 updated to lollipop, but have not experienced this at all on my Moto X. I also essentially started fresh on 5.0, powered my moto x up, went through setup, updated immediately to lollipop, and went ahead and did a factory reset. So maybe the fact my phone wasn't used on KitKat at all before updating saved me some problems, don't know. All I know is I don't have memory issues, had my phone a little over 2 weeks now, and today was the first reboot (to apply a screen protector) I've done since day 1.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I agree with you, Battery life is ok and memory management also is ok, I also used my phone with Lollipop directly.
Battery performance was enhanced after checking which apps caused high battery drain and disabled it.

M3drvr said:
Just force stop Moto OTA in apps. Gets rid of that notification until you reboot the device.
Click to expand...
Click to collapse
Thanks for the tip, I don't reboot my phone very often so it is perfect for me.
Next thing for me is to unlock the bootloader and root for exposed, really liking this phone more every day although I have had it less than a week yet.

The first update released was 5.0 for pure edition. Then Motorola's developers went to work on bringing the update to other variants, and by that time 5.0.1 and 5.0.2 came out. Now that they're working on the xt1095 again, they'll be pushing the 5.1 update.
Basically, they're not going to halt all progress on bringing other updates just to keep pure edition on the cutting edge. It got the first spot on line, but once they finalized its 5.0 release it had to wait for its next turn in line. Also, it doesn't make sense to release a 5.0 update for the others when 5.0.1 exists just to make pure edition owners feel special about being the most up to date.
Full disclosure: I have the pure edition.

Skillinator said:
The first update released was 5.0 for pure edition. Then Motorola's developers went to work on bringing the update to other variants, and by that time 5.0.1 and 5.0.2 came out. Now that they're working on the xt1095 again, they'll be pushing the 5.1 update.
Basically, they're not going to halt all progress on bringing other updates just to keep pure edition on the cutting edge. It got the first spot on line, but once they finalized its 5.0 release it had to wait for its next turn in line. Also, it doesn't make sense to release a 5.0 update for the others when 5.0.1 exists just to make pure edition owners feel special about being the most up to date.
Full disclosure: I have the pure edition.
Click to expand...
Click to collapse
What's the source of that info?

95Z28 said:
The battery life is about what I expected for a screen the size it is with such a small battery, a decent improvement over my smaller N5 with same size battery, albeit over a year old. As for memory management, I had occasional launcher redraws and apps not staying in memory when when N5 updated to lollipop, but have not experienced this at all on my Moto X. I also essentially started fresh on 5.0, powered my moto x up, went through setup, updated immediately to lollipop, and went ahead and did a factory reset. So maybe the fact my phone wasn't used on KitKat at all before updating saved me some problems, don't know. All I know is I don't have memory issues, had my phone a little over 2 weeks now, and today was the first reboot (to apply a screen protector) I've done since day 1.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
RAM issue is a major problem! This phone won't allow you to drop below 450MB free of RAM i've noticed since going to lollipop. Quite an issue causing constant reloading of apps. the opposite really of whats supposed to happen with android. Its really making the CPU work a lot harder more often to completely reopen apps. With KitKat, never had this issue. Everything stayed in RAM and used no where near this amount actually, i typically had 750-800 free., but even if i dropped to 200 free it wasn't exiting apps and causing everything to reload. And its not like i've installed any new apps since.
Lets not even get me started on battery life as thats horrendous since going to lollipop.

GTCC said:
Thanks for the tip, I don't reboot my phone very often so it is perfect for me.
Next thing for me is to unlock the bootloader and root for exposed, really liking this phone more every day although I have had it less than a week yet.
Click to expand...
Click to collapse
Just a heads up, when you unlock the bootloader it will wipe your phone, so backup whatever you can before doing it.
Sent from my iPhone 6 using Tapatalk

Link_proxXP said:
What's the source of that info?
Click to expand...
Click to collapse
I mean, I don't have a source, I figured that's what makes sense. It would be unreasonable to expect Motorola to not update ANYTHING until the Pure Edition is up to date, and it also doesn't make sense for them to push an update that's outdated on release.
Motorola promised "fast" updates for the Pure Edition but it's not the only job their developers have. It was indeed the first they updated, but they also have to update the rest of their lineup, and they can't leave everyone on KitKat while continuing to give exclusive updates to the xt1095.

Considering how small of changes they'd have to do for all the other devices, I really don't think it's unreasonable to expect the pure edition to always get the updates first though and then the others. Really, you can install the pure editions software on other devices without issues other than the radio.

Having a hard time with my Moto Maxx

This device is amazing, or at least was supposed to be. Almost stock android, a good camera, a ridiculously strong chipset, gorgeous screen and tremendous battery capacity.
What could possibly make this phone be anything but awesome? The software!
Motorola may have been on the right direction with these almost pure Android devices and their smart and functional features, but they should urgently look out for some software issues.
1- KitKat on Moto Maxx have a huge battery drain problem when the phone is in stand by mode, never got fixed, and if you use art runtime you have to wait more than 3 minutes to have your devices booted up. Cyanogenmod developers could theach Motorola engineers how to resolve this. That's absurd to me.
2- I'm on the soak test, the super anticipated lollipop, I thought Motorola was leaving KitKat full of bugs to work better on lollipop, but now I have lollipop and things did not get better, I can't and I won't talk about it in details, but it is ridiculous. I had a Galaxy S2, a Galaxy S3 and after that I had a LG G2, though LG and Samsung used to make we wait a lot for updates I saw Cyanogenmod, paranoid, etc ROMs getting around bugs on their alpha and beta ROMs a lot faster then the official Motorola engineers, and I assume they are being well paid by Motorola to work on it.
Moto Maxx have no custom ROMs, no custom kernel, I wish I could do something to change this scenario, but I know nothing about programing. I'm trying hard to like this phone, but it is quite difficult right now, no community, no fast updates, lags, bugs, and the Snapdragon 805 hate the heat so much that the phone appears to be using a low cost processor when it gets hot even when it's not on heavy usage, and I'm not talking about the soak test, I experienced problems since KitKat, looks like they don't care at all. Right now I'm very frustrated, I regret a lot buying this phone and I can't even find anyone willing to buy it, Motorola needs a better development team, cause if things keep going this way, I'll never buy another Motorola device.

RaphaDL said:
KitKat on Moto Maxx have a huge battery drain problem when the phone is in stand by mode, never got fixed, and if you use art runtime you have to wait more than 3 minutes to have your devices booted up. Cyanogenmod developers could theach Motorola engineers how to resolve this. That's absurd to me.
Moto Maxx have no custom ROMs, no custom kernel, I wish I could do something to change this scenario, but I know nothing about programing. I'm trying hard to like this phone, but it is quite difficult right now, no community, no fast updates, lags, bugs, and the Snapdragon 805 hate the heat so much that the phone appears to be using a low cost processor when it gets hot even when it's not on heavy usage, and I'm not talking about the soak test, I experienced problems since KitKat, looks like they don't care at all. Right now I'm very frustrated, I regret a lot buying this phone and I can't even find anyone willing to buy it, Motorola needs a better development team, cause if things keep going this way, I'll never buy another Motorola device.
Click to expand...
Click to collapse
Sorry about your phone. That's not how my two Moto Maxx phones act.
* I don't wait 3 minutes to have my device boot up. Maybe you got a lemon? If your phone is taking over 45 seconds to boot, something is wrong with your phone. My main phone (on Dalvik) boots in 45 seconds with over 300 apps. I just timed it; and that includes the time it takes to unlock the security code.
My second Moto Maxx (on ART) boots in 20 seconds to desktop from the time I hit the power button. Here's a video proving it:
MOTO MAXX BOOTING ON ART
https://www.youtube.com/watch?v=7Swf3rS6-vc
Somebody asked me to make the video because the CDMA Droid Turbo XT1254 has some kind of ART problem, which the "international" Moto Maxx XT1225 seemingly does not. But this proves the Moto Maxx XT1225 boots extremely fast not only on Dalvik but on ART also.
One phone has all my apps installed (over 300), the other does not as I'm keeping it in "new in the box" condition to sell with even the screen protector on. I only take it out to compare to my first phone when necessary. But with two phones, neither even over a minute, shows something is wrong with your phone.
* My battery lasts so much longer than my Nexus 5. Well, it's a bigger battery! Haven't noticed any quick drain. But maybe that's because my Nexus 5 battery was too small and this one is great by comparison.
* Haven't noticed the heat of the Snapdragon 805, but I have heard complaints about the Snapdragon 810. I use a Tech21 case, so maybe I'm just not feeling the heat.
* A dev -- @Skrilax_CZ --in this forum is working on CM12 for us.
Until then, I'm running my daily phone on Dalvik with xposed/Gravity Box toolkit. There is the custom ROM you are looking for...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

1. Although standby drain could be better, mine isn't too bad. How strong is the signal in your area? Are you leaving Bluetooth, auto sync, etc on? Have you tried a factory reset as a last resort?
2. It's a soak test, not the final software. No one knows for sure the reason for the delay in rolling it out, but some of the bugs may be fixed or resolved in the official update (which could be 5.1).
3. I would never buy a phone on the premise that it would get strong developer support. It's something that's tough to guarantee unless you know for definite that devs are getting the phone. In this instance I agree that Moto take some of the blame here for not releasing the Maxx worldwide, but then again it's not their duty to ensure any device of theirs has strong 3rd party support.

RaphaDL said:
This device is amazing, or at least was supposed to be. Almost stock android, a good camera, a ridiculously strong chipset, gorgeous screen and tremendous battery capacity.
What could possibly make this phone be anything but awesome? The software!
Motorola may have been on the right direction with these almost pure Android devices and their smart and functional features, but they should urgently look out for some software issues.
1- KitKat on Moto Maxx have a huge battery drain problem when the phone is in stand by mode, never got fixed, and if you use art runtime you have to wait more than 3 minutes to have your devices booted up. Cyanogenmod developers could theach Motorola engineers how to resolve this. That's absurd to me.
2- I'm on the soak test, the super anticipated lollipop, I thought Motorola was leaving KitKat full of bugs to work better on lollipop, but now I have lollipop and things did not get better, I can't and I won't talk about it in details, but it is ridiculous. I had a Galaxy S2, a Galaxy S3 and after that I had a LG G2, though LG and Samsung used to make we wait a lot for updates I saw Cyanogenmod, paranoid, etc ROMs getting around bugs on their alpha and beta ROMs a lot faster then the official Motorola engineers, and I assume they are being well paid by Motorola to work on it.
Moto Maxx have no custom ROMs, no custom kernel, I wish I could do something to change this scenario, but I know nothing about programing. I'm trying hard to like this phone, but it is quite difficult right now, no community, no fast updates, lags, bugs, and the Snapdragon 805 hate the heat so much that the phone appears to be using a low cost processor when it gets hot even when it's not on heavy usage, and I'm not talking about the soak test, I experienced problems since KitKat, looks like they don't care at all. Right now I'm very frustrated, I regret a lot buying this phone and I can't even find anyone willing to buy it, Motorola needs a better development team, cause if things keep going this way, I'll never buy another Motorola device.
Click to expand...
Click to collapse
1) I'm agree with the battery problem, I come from a Nexus 5 who barely had 1%-2% battery drain over night, and then comes the Maxx with around 15% battery drain overnight, but I have discovered that this is because of the sensors and the GPS accuracy. The biggest drain here is "wave to silence" and "approach to display" functions, under the "Actions" on Moto application. When I disabled those, half of my drain was no more. Besides this, put the location on "Battery Saving", it makes a great difference with "High Accuracy". I'm always reaching around 40hrs on battery and at least 4hrs on screen with just this little changes, everything else is activated and synced all the time.
2) I can't talk about Lollipop, no idea when is coming to my device.
3) About ROM's and kernels, we should wait, there device is still "new" in the market and is not widespread, maybe the launch in India would give us more developers and people who want to participate on this device.
The device is really good, but if you are into customization and ROM's, maybe you should picked the Nexus 6. For me, stock ROM is enough.

About the heat, try to run any benchmark 3 times in a row. Or play a heavy game for more than 15 minutes. Or try to play a game while you charge the phone with it's fast charger. You feel your phone getting slower and slower.
About the battery, as I said, I used to own a LG G2, a 3000mah battery phone. And it's battery life was better on stand by. Overnight my Moto Maxx loses almost 10% of juice, while the G2 used to lose only 2% on the same condition. And I saw a lot of people with this same problem. Having in mind that the Moto Maxx has a 3900mah this is unacceptable.
About ART, well, I can't reproduce my tests anymore cause I'm on lollipop, but when I was using ART on KitKat my phone used to load up all my apps "Updating system" like on every single boot, and I asked other people to reproduce the test and their phone behavior was exactly equal, so maybe the fact that your phone is almost unused is causing you not to feel this problem.
About custom ROMs, I'm waiting for CM12! I emailed the dev already saying that I'm willing to give any help or donation he needs.

RaphaDL said:
About ART, well, I can't reproduce my tests anymore cause I'm on lollipop, but when I was using ART on KitKat my phone used to load up all my apps "Updating system" like on every single boot, and I asked other people to reproduce the test and their phone behavior was exactly equal, so maybe the fact that your phone is almost unused is causing you not to feel this problem.
Click to expand...
Click to collapse
Well, I posted a video to prove the fast boot time for ART. 20 seconds. True that phone only has stock apps.
My other phone with 322 apps takes 45 seconds to boot, and yes it's on Dalvik.
OK, here's what I will do. I will make a new TWRP backup. I will uninstall all my xposed modules, switch temporarily to ART, and boot. Not sure if I will be able to make a video here while at work, but I can time it. Will post results back.
Then, I'll restore my backup.

ChazzMatt said:
Well, I posted a video to prove the fast boot time for ART. 20 seconds. True that phone only has stock apps.
My other phone with 322 apps takes 45 seconds to boot, and yes it's on Dalvik.
OK, here's what I will do. I will make a new TWRP backup. I will uninstall all my xposed modules, switch temporarily to ART, and boot. Not sure if I will be able to make a video here while at work, but I can time it. Will post results back.
Then, I'll restore my backup.
Click to expand...
Click to collapse
Thank you, dude, but you don't need to go through all this trouble. I tested it on 3 Moto Maxx with KitKat and the 3 presented the exactly same problem.
And that's not much of a problem since Lollipop doesn't have this behavior and it uses ART. I just brought that up to illustrate how behind Motorola are when the subject is software.

RaphaDL said:
[B
About ART, well, I can't reproduce my tests anymore cause I'm on lollipop, but when I was using ART on KitKat my phone used to load up all my apps "Updating system" like on every single boot, and I asked other people to reproduce the test and their phone behavior was exactly equal, so maybe the fact that your phone is almost unused is causing you not to feel this problem.
.
Click to expand...
Click to collapse
ChazzMatt said:
Well, I posted a video to prove the fast boot time for ART. 20 seconds. True that phone only has stock apps.
My other phone with 322 apps takes 45 seconds to boot, and yes it's on Dalvik.
OK, here's what I will do. I will make a new TWRP backup. I will uninstall all my xposed modules, switch temporarily to ART, and boot. Not sure if I will be able to make a video here while at work, but I can time it. Will post results back.
Then, I'll restore my backup.
Click to expand...
Click to collapse
On ART (xposed apps disabled) my main phone with over 300 apps takes 30 seconds to boot to desktop. Something is wrong with your phone.
I'll make a video later.
_______
EDIT: I was still on Dalvik. ARghhh. ART will not stick. Trying to figure out why.

ChazzMatt said:
On ART (xposed apps disabled) my main phone with over 300 apps takes 30 seconds to boot to desktop. Something is wrong with your phone.
I'll make a video later.
Click to expand...
Click to collapse
On what country you bought your phone? Maybe that's something related to Brazilian Moto Maxx only. I really wish I have recorded in video the tests I made.

ChazzMatt said:
On ART (xposed apps disabled) my main phone with over 300 apps takes 30 seconds to boot to desktop. Something is wrong with your phone.
I'll make a video later.
Click to expand...
Click to collapse
Hmmmm.... I'm having a hard time making ART stick. I've uninstalled all my xposed modules, but every time I reboot it's back on Dalvik. Anyone have any ideas?

Art dont work well in kitkat, maybe you should try Lollipop, for custom roms, need found more devs with devices, cm 12 comes in some times, but of have more devs maybe we have some kernels

matheus_sc said:
Art dont work well in kitkat, maybe you should try Lollipop, for custom roms, need found more devs with devices, cm 12 comes in some times, but of have more devs maybe we have some kernels
Click to expand...
Click to collapse
Maybe we should gather some money and donate a device to someone. What you guys think?

ChazzMatt said:
On ART (xposed apps disabled) my main phone with over 300 apps takes 30 seconds to boot to desktop. Something is wrong with your phone.
I'll make a video later.
_______
EDIT: I was still on Dalvik. ARghhh. ART will not stick. Trying to figure out why.
Click to expand...
Click to collapse
OK, I was wrong. ART sucks on KitKat. I finally got ART to stick by flashing the xposed disable zip. Switched to ART, and it went through the initial several minute upgrade for 307 apps. (I had unintalled all my xposed modules).
But now when I turn off the phone and boot back up, still takes several minutes to "optimize" 180 apps. EVERY TIME. MORE than 3 minutes -- more like TEN MINUTES every time.
So, after this third time of ART boot up, when it finishes, I'm restoring my TWRP backup to go back to Dalvik so I can boot up in 45 seconds! :laugh:
Nothing is wrong with your phone for the slow boot up, except you are on ART...
If Lollipop is this way, I'm sticking to Kitkat 4.4.4 and Gravity Box.

ChazzMatt said:
OK, I was wrong. ART sucks on KitKat. I finally got ART to stick by flashing the xposed disable zip. Switched to ART, and it went through the initial several minute upgrade for 307 apps. (I had unintalled all my xposed modules).
But now when I turn off the phone and boot back up, still takes several minutes to "optimize" 180 apps. EVERY TIME. MORE than 3 minutes -- more like TEN MINUTES every time.
So, after this third time of ART boot up, when it finishes, I'm restoring my TWRP backup to go back to Dalvik so I can boot up in 45 seconds! :laugh:
Nothing is wrong with your phone for the slow boot up, except you are on ART...
If Lollipop is this way, I'm sticking to Kitkat 4.4.4 and Gravity Box.
Click to expand...
Click to collapse
Exactly.
Lollipop doesn't have this problem, relax. But I'm bringing this problem here just to bring attention to the fact that Motorola have awful software management.
Huge battery, but even bigger battery drain.
Smart features, but no flexibility, why can't we program the sensors to work only when there is a notification to be showed? Why we have to leave the sensors on ALL THE TIME even when we are not using it at all?
Updated software, but small problems that even independent developers are able to get around on other devices. And other than that we can see some incompatibilities, and I'm not taking about soak test, the Moto X 2014 Lollipop bring no integration between Lollipop lockscreen features and Moto benefits.
Motorola must urgently give more attention to the software on their smartphones.
And,guys,we have the same hardware as the Nexus 6, there's absolutely no reason for Motorola not take advantage of that.

RaphaDL said:
Exactly.
Lollipop doesn't have this problem, relax. But I'm bringing this problem here just to bring attention to the fact that Motorola have awful software management.
Huge battery, but even bigger battery drain.
Smart features, but no flexibility, why can't we program the sensors to work only when there is a notification to be showed? Why we have to leave the sensors on ALL THE TIME even when we are not using it at all?
Updated software, but small problems that even independent developers are able to get around on other devices. And other than that we can see some incompatibilities, and I'm not taking about soak test, the Moto X 2014 Lollipop bring no integration between Lollipop lockscreen features and Moto benefits.
Motorola must urgently give more attention to the software on their smartphones.
And,guys,we have the same hardware as the Nexus 6, there's absolutely no reason for Motorola not take advantage of that.
Click to expand...
Click to collapse
Just disable everything under Actions on the Moto app except for the camera, and you should be fine.
It will work as you wanted, just show the notifications where there is one. I have my Maxx since few months like that and it is much better than with those activated. It is annoying besides that everything would turn your screen on.
That would help with the battery drain also.
:fingers-crossed:

Galaxo60 said:
Just disable everything under Actions on the Moto app except for the camera, and you should be fine.
It will work as you wanted, just show the notifications where there is one. I have my Maxx since few months like that and it is much better than with those activated. It is annoying besides that everything would turn your screen on.
That would help with the battery drain also.
:fingers-crossed:
Click to expand...
Click to collapse
Thanks for the tip, but I already tried this.
The movement sensors still turned on all the time, it just disable the waving gesture features. When in a car the screen still turn on every time the car moves, even if there's no notification, also turn on when over a table and the table moves, or over my leg and my leg moves. My point is, sensors still on and for nothing. I would turn this completely off if we had a notification led, but we don't, so I can't.

RaphaDL said:
Motorola must urgently give more attention to the software on their smartphones.
And,guys,we have the same hardware as the Nexus 6, there's absolutely no reason for Motorola not take advantage of that.
Click to expand...
Click to collapse
RaphaDL said:
The movement sensors still turned on all the time, it just disable the waving gesture features. When in a car the screen still turn on every time the car moves, even if there's no notification, also turn on when over a table and the table moves, or over my leg and my leg moves. My point is, sensors still on and for nothing. I would turn this completely off if we had a notification led, but we don't, so I can't.
Click to expand...
Click to collapse
Yes, I greatly miss the notification LED from my Nexus 5.
But Nexus 6 is not an option for me. And thank you for reminding people we have the EXACT same hardware as the Nexus 6 and made by the EXACT same company. Motorola has no excuses.

RaphaDL said:
Thanks for the tip, but I already tried this.
The movement sensors still turned on all the time, it just disable the waving gesture features. When in a car the screen still turn on every time the car moves, even if there's no notification, also turn on when over a table and the table moves, or over my leg and my leg moves. My point is, sensors still on and for nothing. I would turn this completely off if we had a notification led, but we don't, so I can't.
Click to expand...
Click to collapse
Hello Rapha in below theme you can find how to make works the notification led that all we have on our moto maxx devices, Im using it right now
http://forum.xda-developers.com/droid-turbo/general/notification-led-t2960203/page2

Is it possible to go back to lollipop?

I'm sick of my Moto X Style not running smoothly on stock android 6.0.1. Some custom roms fixed that but had other problems like calling echoes, slow camera launching, not being able to playback videos on facebook etc... Will i brick my phone if i try to roll back, or can i actually do it?

At worst you will softbrick it... I doubt it would hardbrick, but most of the threads where people have tried to downgrade have not gone well but they eventually get it working. Moto's don't like to be downgraded, the big problem is the partition table changes from Lollipop to Marshmallow and it won't go back. Although I don't know about this device specifically, but several older Moto's would brick if you downgraded then took an OTA later due to the mismatch of bootload and gpt partition table versions.
I would try to find solutions to your problems with MM rather than downgrade... I don't have any issues with any of the problems you are stating with echo, camera launch (mine is ready to take pictures in less than 2 seconds from either lock screen or icon), and Facebook works fine. Guess I am a little puzzled, but then again I am on 6.0.0 on the Pure.

akeflo said:
I'm sick of my Moto X Style not running smoothly on stock android 6.0.1. Some custom roms fixed that but had other problems like calling echoes, slow camera launching, not being able to playback videos on facebook etc... Will i brick my phone if i try to roll back, or can i actually do it?
Click to expand...
Click to collapse
It is possible if you have a TWRP backup of lollipop. I have done it before and it does work.

!Iamdeath! said:
It is possible if you have a TWRP backup of lollipop. I have done it before and it does work.
Click to expand...
Click to collapse
It's possible even without a backup too.

Spasticdroid said:
It's possible even without a backup too.
Click to expand...
Click to collapse
It is possible, but as mentioned by @acejavelin, it could cause issues later. The better option is to try and work out the current issues. Since the OP obviously has TWRP installed, my recommendation for stock ROM is to possibly look at apps that may be the culprits. Other options can include custom kernels.

Thank you so much everyone! But then, how do i do it? Is there anyone who has done it before and could help me? I don't have a lollipop backup on my TWRP btw..

acejavelin said:
At worst you will softbrick it... I doubt it would hardbrick, but most of the threads where people have tried to downgrade have not gone well but they eventually get it working. Moto's don't like to be downgraded, the big problem is the partition table changes from Lollipop to Marshmallow and it won't go back. Although I don't know about this device specifically, but several older Moto's would brick if you downgraded then took an OTA later due to the mismatch of bootload and gpt partition table versions.
I would try to find solutions to your problems with MM rather than downgrade... I don't have any issues with any of the problems you are stating with echo, camera launch (mine is ready to take pictures in less than 2 seconds from either lock screen or icon), and Facebook works fine. Guess I am a little puzzled, but then again I am on 6.0.0 on the Pure.
Click to expand...
Click to collapse
On stock ROM everything works but lags, but for example on cm13 videos on facebook won't playback, switching to front facing camera takes maybe 10 seconds and the echo is there when speaking on the phone. What ROM are you using?

akeflo said:
On stock ROM everything works but lags, but for example on cm13 videos on facebook won't playback, switching to front facing camera takes maybe 10 seconds and the echo is there when speaking on the phone. What ROM are you using?
Click to expand...
Click to collapse
Stock, and I have no "lag" to speak of, but my point of references lately are the Moto G3, Nexus 4, and Lumia 640 LTE so by these standard the Pure is a Ferrari by comparison.
Sent from my Motorola XT1575 using XDA Labs

I'm using stock with no lag. I get the occasional stutter every now and then but that has been the case with every Android I have owned. Have you gone to developer options and changed the Windows animation scale and Transition animation scale to 0.5? This might help.

acejavelin said:
Stock, and I have no "lag" to speak of, but my point of references lately are the Moto G3, Nexus 4, and Lumia 640 LTE so by these standard the Pure is a Ferrari by comparison.
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
Haha i see! Well my comparison is with a Nexus 5x and an LG G2 and i hardly can't tell a difference between my moto and the LG G2 with a cyanogen based ROM. The Nexus is clearly the smoothest of all three.

aybarrap1 said:
I'm using stock with no lag. I get the occasional stutter every now and then but that has been the case with every Android I have owned. Have you gone to developer options and changed the Windows animation scale and Transition animation scale to 0.5? This might help.
Click to expand...
Click to collapse
Yes every android has some lag now and then but my Nexus 5X ran much smoother than the Moto X. It lags when i open the app drawer for instance which is the most simple task ever. It really pisses me off. I will try changing animation speed, thank you.

akeflo said:
I'm sick of my Moto X Style not running smoothly on stock android 6.0.1. Some custom roms fixed that but had other problems like calling echoes, slow camera launching, not being able to playback videos on facebook etc... Will i brick my phone if i try to roll back, or can i actually do it?
Click to expand...
Click to collapse
I flashed Android Lollipop many times but wifi doesn't work so I am not able to log in into Google account so I flash back marshmallow. I especially face serious lag when scrolling through YouTube in marshmallow.

[email protected] said:
I flashed Android Lollipop many times but wifi doesn't work so I am not able to log in into Google account so I flash back marshmallow. I especially face serious lag when scrolling through YouTube in marshmallow.
Click to expand...
Click to collapse
Are you clean flashing? I've flashed several different roms and none of them have lagged for me the slightest bit.
Sent from my XT1575 using Tapatalk

New Moto camera freezing up

I have notice the camera lag and freeze after taking so many pictures continuously. Last time it happened I was casting YouTube and then I went to take a picture and it was lagging. I switched the storage to internal memory, thinking it was the SD card, but it still lagged.
I also notice the phone freeze up when the battery gets to 15% or less. I am not sure if the issues are with the phone or because I am rooted, have Xposed install with mods, substratum theme, and Magisk.

Danny1976 said:
I have notice the camera lag and freeze after taking so many pictures continuously. Last time it happened I was casting YouTube and then I went to take a picture and it was lagging. I switched the storage to internal memory, thinking it was the SD card, but it still lagged.
I also notice the phone freeze up when the battery gets to 15% or less. I am not sure if the issues are with the phone or because I am rooted, have Xposed install with mods, substratum theme, and Magisk.
Click to expand...
Click to collapse
Are u on stock ???

Love Dhir said:
Are u on stock ???
Click to expand...
Click to collapse
Yes

This is happening to me also completely stock 7.0. there is a pronounced lag when using camera app. Once it's up and running seems to be ok but firing up taking forever.

I think I may be upgrading soon to the Nokia 6.1. I think the Moto G4 Is coming to the end of it's life. Nokia is providing updates quickly and are making some nice phones.

Danny1976 said:
I think I may be upgrading soon to the Nokia 6.1. I think the Moto G4 Is coming to the end of it's life. Nokia is providing updates quickly and are making some nice phones.
Click to expand...
Click to collapse
I'm hoping my carrier Republic wireless offers Nokia, though Moto G6 looks pretty nice also.

I have the same problem with the camera, it also happens when recording to 1080p the image is delayed with respect to the audio, this problem started from the update of the security patch in December. I am still in stock with elemental, magisk & Xposed

I was using an app to scan barcodes and the phone rebooted everytime. Sometimes it would crash after a couple pictures. Also when using the camera by itself to take pictures it takes a long time, as if it froze. This new camera update seems to be unstable and I am surprised, no many complaints from more people.
The stock camera is the best option and that's one main reason I am in stock. But now that this is happening, I may install an Nougat custom ROM. I would install an Oreo ROM, but they still have too many issues.

I think it is happening after april security patch update. corret me please if i'm wrong.

i_Amlesh said:
I think it is happening after april security patch update. corret me please if i'm wrong.
Click to expand...
Click to collapse
I was on the February security update, when I started having issues. I think it had to do with the new camera update.

I'm still having major issues with my camera apps. I have stock 7.0 rooted/unlocked and the device will get super hot. I've really only noticed this when the phone was in hot weather, or otherwise already warm from use. The camera will pause for seconds and is generally unusable. This happens with stock and Open Camera. Not sure what's causing this, is there any solution? Downgrade camera? It's not the kernel is it?

ldeveraux said:
I'm still having major issues with my camera apps. I have stock 7.0 rooted/unlocked and the device will get super hot. I've really only noticed this when the phone was in hot weather, or otherwise already warm from use. The camera will pause for seconds and is generally unusable. This happens with stock and Open Camera. Not sure what's causing this, is there any solution? Downgrade camera? It's not the kernel is it?
Click to expand...
Click to collapse
You could try to underclock the CPU/GPU to avoid some heat, but I think you can't really avoid the heat of the SD617 chipset.

thorin0815 said:
You could try to underclock the CPU/GPU to avoid some heat, but I think you can't really avoid the heat of the SD617 chipset.
Click to expand...
Click to collapse
What's causing it though? Is it the root, xposed, the kernel? This is why I wanted to keep on the stock ROM, so things like this wouldn't happen. The camera is virtually unusable in this state, so if it's not caused by my doing, then this is a major fault...

ldeveraux said:
What's causing it though? Is it the root, xposed, the kernel? This is why I wanted to keep on the stock ROM, so things like this wouldn't happen. The camera is virtually unusable in this state, so if it's not caused by my doing, then this is a major fault...
Click to expand...
Click to collapse
It's the CPU itself and only one major fault of many of this device.

Nexus 6P horrible lag issue when rooted

So I picked up a 6P again after I got rid of my original a couple years ago. It arrived yesterday and I got it all setup, but then it started having issues that night. So I did a factory reset. I should mention that the very first thing I did when I got it was root it and install elementalx. Didn't bother with a ROM since Pure Nexus hasn't been supported for awhile (which is what I installed on my old 6P) and I was already running Oreo.
Today was going great until about an hour ago. I unplugged it from charging and the same symptoms as last night happened. When this happens I have to hold the power button until the device reboots.
What happens is that severe lag happens. The screen turns on after a few seconds when I use the fingerprint scanner or power button, but it's very slow and glitchy. Like it'll show half the notification bar and below that there will be a 2 inch long by 1 inch long rectangle in the upper left corner that shows the bottom of my wallpaper. The rest of the screen will show my wallpaper but it'll be glitched, where like the bottom is actually a section of the top. And trying to pull down the notification shade is just impossible. It glitches big time but after lagging of course. I really wish I had pictures to better explain. If it happens again I'll be sure to take some.
From what I've said though, does anyone have any idea why this is happening?
I have a few days where I can still return the device, but I really would like to keep it since it's in mint condition. Battery life is great still and there doesn't seem to be any performance issues when it's working properly. I really don't want to keep doing resets, which if I'd have to then I don't see any point in keeping it since it basically won't be usable.
Edit: 9:37pm
Just had it happen again so I took some pictures. It got to the point the screen wouldn't come on at all, so I had to hold the power button again to reboot. But I found out it still registers the fingerprint to unlock (I hear the sound) and hitting the power button twice still launches the camera (the phone vibrates). When this first started happening this time, after waiting for a little bit with the screen on, I got the popup that the System UI wasn't responding.

Just wanted to update that I flashed the stock ota from Google's site for the October 2018 update. Since doing so the phone has been working fine *knocks on wood*. So right now I'm thinking there was an issue with rooting, elementalx, or magisk. I'll make a backup and do those things one at a time and see when/if my issues return.

Just another update for those who stumble across this topic from Google or whatever.
Things were working great for a few days so I decided to go ahead and root but not install elementalx or anything. Did so last night and upon waking up this morning the phone was having the lag issue again. So it seems rooting is causing my problem. I used magisk, so I'm going to try SuperSU and see if that causes my problem as well.

Switching from magisk to SuperSU did not solve my problem. The phone started freezing up and lagging bad again, requiring me to hold the power button and reboot. So I guess I'll just unroot again and leave it that way.
Unless someone seeing this has any other ideas.

I dont recommend oreo. Im having a lot of issues like the worst of all not being able to install TWRP, lag, screen stutters and excessive battery usage

I love Oreo. Have zero problems with it, my problems are this specific phone. Don't root it and it works flawlessly. Oreo runs better for me than any previous version of Android ever, especially on older lower spec devices. There is zero reason something as powerful as the 6P can't handle it.
TWRP installed without issue, never had an issue with it and Oreo shouldn't affect it anyways. I've got the phone running kind of stock. I installed TWRP and ElementalX and left it at that. Using other apps and adb commands I was able to install a bunch of "Pixel only" stuff and get what I wanted without root. So I'm happy.
The thing's just a side project next to my Note 9 anyways. So long as the hardware issues stay at bay that render the 6P worthless, I'll stay happy.
Sounds like to me you need to do a full re-flash from the stock files on Google's Nexus site and start fresh. Or yours is starting to show signs of the hardware defects.
Either way, this topic is moot to me now I guess. Mainly just left it here in case others find it through Google searches. Good luck!

Whenever I do a major android version upgrade I wipe internal storage. I found that if I didn't do this would get all kinds of little issues. Internal storage carries over files from one android version to the next.

My 6P is doing very similar as yours is. Extreme lagging, basically totally freezing and sometimes half the screen is visible just like on your pictures. I haven't find a solution to it, but you are saying not rooting it fixed it for you? Seems far-fetched but I guess I have no other option. I have been using Lineage OS.

Yeah, removing root instantly fixed the issues for me. I made sure to clear cache and everything like that from recovery too. I'm still unlocked and using TWRP with Elementalx, setup however I like. I just can't root. Soon as I do I can actually feel a little slowdown in using the phone, and then after a day or so the horrible lag with freezing and stuff starts.
Not sure about using a custom ROM since like I said I didn't try it on this phone. My original 6P didn't have any of these issues and I could root, ROM, and modify my heart out.
So to recap, currently and since my last actual update here basically, I've been unlocked, using elementalx and TWRP, but running stock October 2018 Oreo ROM and all that. I used adb commands to get Greenify setup as close to root settings as possible, and to install some Pixel stuff to get night light and whatnot. Got immersive mode by using systemuituner app. And a couple other things to get it as close to how my original 6P was on Pure Nexus.
Hope this helps. I'll be glad to provide anything else I can.

Oreo is crap on the nexus 6p. Seems.like google is slowing it down. Not only on the operating sysyem but also on its latest apps. The latest version of maps is too laggy but the one that comes with nougat is smooth. Thats why i went back to nougat is lile heaven and hell. Shame on goole being thay oreo runs very good on the 5x but not the 6p

survivor_evil said:
Oreo is crap on the nexus 6p. Seems.like google is slowing it down. Not only on the operating sysyem but also on its latest apps. The latest version of maps is too laggy but the one that comes with nougat is smooth. Thats why i went back to nougat is lile heaven and hell. Shame on goole being thay oreo runs very good on the 5x but not the 6p
Click to expand...
Click to collapse
Take your conspiracy theories elsewhere. Oreo runs smooth as butter on perfectly (or even in my case, not perfectly since it won't root) fine 6P's. Everything works as it should and I have zero issues and zero lag. All you're doing is cluttering up my topic on something that has absolutely nothing to do with Oreo. This topic is about the issues I'm having after rooting, nothing else. If you don't like Oreo, fine. If you think a device that's several years old at this point isn't running the newest OS as smooth as it ran older ones, that's fine too. Especially since Google has at this point completely disowned the Nexus nameplate. Just don't come into someone else's topic and run your mouth. I told you before I had no issues with Oreo and that it sounds like your device is showing odd behavior, if you didn't like that... well that's fine too. Why subscribe to this topic and keep coming back if it has nothing to do with you. Go away or contribute helpful info to the issue at hand here; rooting complications not Oreo.
Although at this point I'm not having any issues. My 6P has been running buttery smooth since I removed root on what, October 18th... that's about two weeks ago. And this includes installing and tweaking stuff on it that it's supposedly too obsolete to run and only Pixel devices can handle. It goes toe to toe with my Note 9 in daily activities, all while running Oreo.

RockwellB1 said:
Take your conspiracy theories elsewhere. Oreo runs smooth as butter on perfectly (or even in my case, not perfectly since it won't root) fine 6P's. Everything works as it should and I have zero issues and zero lag. All you're doing is cluttering up my topic on something that has absolutely nothing to do with Oreo. This topic is about the issues I'm having after rooting, nothing else. If you don't like Oreo, fine. If you think a device that's several years old at this point isn't running the newest OS as smooth as it ran older ones, that's fine too. Especially since Google has at this point completely disowned the Nexus nameplate. Just don't come into someone else's topic and run your mouth. I told you before I had no issues with Oreo and that it sounds like your device is showing odd behavior, if you didn't like that... well that's fine too. Why subscribe to this topic and keep coming back if it has nothing to do with you. Go away or contribute helpful info to the issue at hand here; rooting complications not Oreo.
Although at this point I'm not having any issues. My 6P has been running buttery smooth since I removed root on what, October 18th... that's about two weeks ago. And this includes installing and tweaking stuff on it that it's supposedly too obsolete to run and only Pixel devices can handle. It goes toe to toe with my Note 9 in daily activities, all while running Oreo.
Click to expand...
Click to collapse
It wasnt for you but in general, there are more users complaining about it. I tested oreo without rooting and it lags as hell. You can even check comparison videos too... this topic is about having lag issues so I gave you an answer, go back to nougat.

survivor_evil said:
It wasnt for you but in general, there are more users complaining about it. I tested oreo without rooting and it lags as hell. You can even check comparison videos too... this topic is about having lag issues so I gave you an answer, go back to nougat.
Click to expand...
Click to collapse
I told you the first time you mentioned that "solution" , Nougat isn't an option for me and shouldn't be because I'm pretty sure I made it clear Oreo wasn't the problem. I even made it clear I basically solved my issue before your first foray into this thread.
I made it clear again in my last post.
I really don't care if there are comparison videos, I have absolutely zero lag if I'm unrooted. That is what this topic is about, lag caused by root. Those who actually spend the time to read more than the topic title can understand that. I've been working with electronics for a long long time, I know how to diagnose everything and I think I made that pretty clear by providing updates as I did things. If not for the fact the thing is all setup and running great, I'd wager I could go back to Nougat and still have root lag issues. The 6P and the 5X for that matter, are ticking time bombs. They both have hardware defects that basically turn them into fancy paperweights. Those defects could be causing my issues, your issues, and edda's issues. No real way to tell that until the bootloops or early shutdowns start. I'm of course hoping this late in the game that maybe those of us with still functioning units don't have those issues, but my gut tells me it's always a "time will tell" issue.

RockwellB1 said:
I told you the first time you mentioned that "solution" , Nougat isn't an option for me and shouldn't be because I'm pretty sure I made it clear Oreo wasn't the problem. I even made it clear I basically solved my issue before your first foray into this thread.
I made it clear again in my last post.
I really don't care if there are comparison videos, I have absolutely zero lag if I'm unrooted. That is what this topic is about, lag caused by root. Those who actually spend the time to read more than the topic title can understand that. I've been working with electronics for a long long time, I know how to diagnose everything and I think I made that pretty clear by providing updates as I did things. If not for the fact the thing is all setup and running great, I'd wager I could go back to Nougat and still have root lag issues. The 6P and the 5X for that matter, are ticking time bombs. They both have hardware defects that basically turn them into fancy paperweights. Those defects could be causing my issues, your issues, and edda's issues. No real way to tell that until the bootloops or early shutdowns start. I'm of course hoping this late in the game that maybe those of us with still functioning units don't have those issues, but my gut tells me it's always a "time will tell" issue.
Click to expand...
Click to collapse
If that was a hardware issue Id be having it with other versions of android but no, only oreo. And everything points out that oreo is the issue. Not only me but all the users posting videos and on forums

survivor_evil said:
Oreo is crap on the nexus 6p. Seems.like google is slowing it down. Not only on the operating sysyem but also on its latest apps. The latest version of maps is too laggy but the one that comes with nougat is smooth. Thats why i went back to nougat is lile heaven and hell. Shame on goole being thay oreo runs very good on the 5x but not the 6p
Click to expand...
Click to collapse
I agree with you on that. I have had much better luck running Pure Nexus over any other rom.
Chris

RockwellB1 said:
Yeah, removing root instantly fixed the issues for me. I made sure to clear cache and everything like that from recovery too. I'm still unlocked and using TWRP with Elementalx, setup however I like. I just can't root. Soon as I do I can actually feel a little slowdown in using the phone, and then after a day or so the horrible lag with freezing and stuff starts.
Not sure about using a custom ROM since like I said I didn't try it on this phone. My original 6P didn't have any of these issues and I could root, ROM, and modify my heart out.
So to recap, currently and since my last actual update here basically, I've been unlocked, using elementalx and TWRP, but running stock October 2018 Oreo ROM and all that. I used adb commands to get Greenify setup as close to root settings as possible, and to install some Pixel stuff to get night light and whatnot. Got immersive mode by using systemuituner app. And a couple other things to get it as close to how my original 6P was on Pure Nexus.
Hope this helps. I'll be glad to provide anything else I can.
Click to expand...
Click to collapse
I had problems similar to this and found out it was the immersive mode causing it, activating it with any app caused problems. If you download terminal emulator and use some commands that can be found elsewhere in the Nexus 6p part of the forum it works fine. Hope this helps. Currently on Resurrection remix with magisk installed. Running smooth as butter. Just waiting for pie to be more stable now

faybarn said:
I had problems similar to this and found out it was the immersive mode causing it, activating it with any app caused problems. If you download terminal emulator and use some commands that can be found elsewhere in the Nexus 6p part of the forum it works fine. Hope this helps. Currently on Resurrection remix with magisk installed. Running smooth as butter. Just waiting for pie to be more stable now
Click to expand...
Click to collapse
Thanks but I wasn't even messing with immersive mode at the time. Or are you saying just having it present because I made uituner visible in settings that it might have been causing it?
My issue very much seems to be straight up linked to rooting. If I used magisk or SuperSU (really the only two I'm willing to trust) I'd notice the phone felt sluggish soon as it would reboot after rooting with them. It wasn't a huge slowdown though so I thought nothing of it, until the horrible lag/freezing issues started usually within the day. Remove root, and everything went back to normal.
I've since been using immersive mode without any issue, but of course I gave up on root.
And yeah, I hear ya on Pie. Soon as it becomes stable enough I'll be testing it out. I had 8.1 running on my Note 4, just sold it about a month ago, and it was running great. Only minor issues that were still being worked on. Being a Nexus though I have high hopes this'll be a bit easier to port to.

buchananchris said:
I agree with you on that. I have had much better luck running Pure Nexus over any other rom.
Chris
Click to expand...
Click to collapse
Im talking about pure oreo on the nexus 6p. Ive installed it many times thinking coukd be a bad installation but its just that oreo is crap on the nexus 6p. I went back to nougat and its working like a charm again.