Effin Battery! - Moto X General

It's the 4.4.2 upgrade. Ever since it went on the phone I have to keep location services off or Android OS will eat my battery.
I wouldn't be worrying about this if there was an active CM dev effort for this phone, but it really looks like this phone is (already!) being dropped. Nobody's worked on the X8 unified build in a month. Starting to think this phone was a mistake.
I remember reading some of the blogs looking for a flagship phone with a mid-size screen. All the "mini" versions are dual core 1.7GHz systems. It's not that nobody would build a midsize with a hot quadcore, it's just that you can't fit enough battery for a hot quad behind a medium display. And by the time I went through all the available dual-core phones (at Verizon, anyway), really nothing comes close to the Moto X.
But I think this could be a dead end. The last three days or so I've been reading how Google's wrapping up 4.4.3, and it looks like these battery leaks are one of their priorities. But without CM, I wonder how long it will take to get that build through VZW and the other carriers.

Cm and what not aren't too popular, as you lose all those nice moto features.
And flip through this thread a bit and you'll see a lot of battery issues solved or worked around.
http://forum.xda-developers.com/showthread.php?t=2418077
But yes...depending what else is on your phone and accessing location services....location services can be a battery drain. Toggle when needed is usually my advice. But....there's ways to get it under control. Check out the thread I linked. Massive amounts of good info in there.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....

CM nightlys here http://download.cyanogenmod.org/?device=moto_msm8960dt. I flashed one a couple builds back just check it out, I'm on Verizon (xt1060) unlocked with china code. Flashed back to stock just for moto features but all seemed well on CM. Didn't use it long enough to test battery. I believe they've unified the builds to work with all variants.

ConstantHero said:
CM nightlys here http://download.cyanogenmod.org/?device=moto_msm8960dt. I flashed one a couple builds back just check it out, I'm on Verizon (xt1060) unlocked with china code. Flashed back to stock just for moto features but all seemed well on CM. Didn't use it long enough to test battery. I believe they've unified the builds to work with all variants.
Click to expand...
Click to collapse
Yeah, the nightlies are generated automatically, and I imagine they include incremental CM changes. But like I said, it's been about a month since the last device-specific check-in, and the feedback I'm hearing is that the speaker phone is broken ever since then.

If you use the snapdragon battery guru app it helps soooo much I get 24 hours of battery daily . Make sure you turn your screen brightness down as much as possible also . Try OSE it was amazing on my atrix HD you can find the builds at Dr.devs website .
Sent from my XT1058 using Tapatalk

I found the BBC Weather was keeping my phone awake all the time. Only worked that out after a factory reset. I'd suggest giving your phone a wipe, it's not ideal at all but it sorted mine out. I reckon the 4.4.2 update has screwed up location somewhow.

Go to play store.
Check all your installed apps and uninstall any that have not been updated since kit kat release.
Restart phone
Worked for me, working for others, should work for you.
Moto X developer edition

They stopped working on individual devices, And are now doing Unified builds. MSM8960dt works on all Moto X phones, and I believe RAZR MAXX phones as well.Why do the same thing 8 times when it can be done once? Try PAC ROM. 8960DT, use it all day, and battery rarely dips below 60%.

Snaipersky said:
They stopped working on individual devices, And are now doing Unified builds. MSM8960dt works on all Moto X phones, and I believe RAZR MAXX phones as well.Why do the same thing 8 times when it can be done once? Try PAC ROM. 8960DT, use it all day, and battery rarely dips below 60%.
Click to expand...
Click to collapse
I don't think that is what the poster above meant when he was talking about device specific builds.
By that he meant Moto X specific and not all individual moto x models.
Current nightless are adding new stuff that is getting added to all cm builds. But not fixing any known issues with our phone like the speaker phone issue. To fix that, some developer will have to work on Moto X specific code which will probably work on all Moto X models.
This is the main reason I am not running cm. ( That and active notifications. But I can live without active notifications if all basic functions are working properly including speakerphone and camera) . love the performance, but I need to use speakerphone a lot when speaking and working on my computer at the same time or when my hands are dirty.
From my Moto X, in your face!

Related

Incredible user

So can I get some info on the X because I currently own an Incredible but have about a week now to switch. How do the two phones compare? Exactly how much can I do to the X? Currently my Incredible is rooted and using custom ROM and theme.
Thanks for the help in advance.
(Oh and is it true you can get rid of the UI on the X? I have a friend claiming he did)
CHPunk said:
So can I get some info on the X because I currently own an Incredible but have about a week now to switch. How do the two phones compare? Exactly how much can I do to the X? Currently my Incredible is rooted and using custom ROM and theme.
Thanks for the help in advance.
(Oh and is it true you can get rid of the UI on the X? I have a friend claiming he did)
Click to expand...
Click to collapse
you can get rid of about 95% of the blur, some has to stay but its being worked on, custom roms are just starting to roll out. However the kernel is locked so no major tampering with the cpu yet.
I had the inc for about a week or two, X is a big upgrade. I wouldnt switch back.
The Droid X wins in every category you can think of but UI(senses). Custom roms/themes are being worked on, and since we rooted and have deodex'd we are fastly moving foward....
So you guys think I should switch? And would you say it's easier or harder to root than the Inc?
Sorry for all the questions, I just want to make sure I have the best phone possible for the next 18 months lol.
Droid X is easy to root on 2.1 just use Universal Androot Beta 1.6.2(Link is clickable) for easy installation of apk for phone for a 1-click root solution. but if you want root on 2.2 require a bit more work but its still easy.
Well looks like you convinced me to get the Droid X!
CHPunk said:
Well looks like you convinced me to get the Droid X!
Click to expand...
Click to collapse
if you have any problems, visit Droid X Wiki
dr154 said:
if you have any problems, visit Droid X Wiki
Click to expand...
Click to collapse
That's how you get the wiki out there!! LOL
But I came from the INC and I can basically do EVERYTHING that I coulddo with the INC on the X... except kernal modding.. obviously.
MrDanger said:
That's how you get the wiki out there!! LOL
Click to expand...
Click to collapse
You know it MrDanger...
only issue you may have, well 2. When taking pics you will think they are horrible when looking at them on the phone, but when you look at them on a comp they are better than the inc. Just something i noticed when switching. And if you frequently use the speaker, (music or voice) the volume is stupid low...
Just thought i would give you a heads up on the only things i have noticed.
Thanks for the help guys, only problem is after going to verizon today I kind of want the Fascinate
I suppose the screen is a big plus, but I hear it feels cheap when compared to the build quality of the X.... not that I beat my phone up on purpose...
I have both (got my X today). Sense and it's quirks are vastly superior to Blur, but I won't keep a phone stock if I can find a real vanilla build. I do miss things like having a dialer that doesn't suck and some of the skins for sense. I could use Sense builds, but I can tell there is no way I'll want to use any of the Blur crap (except DNLA, which looks neat).
The device itself the X wins hands down. The look and feel of the actual device is just.. better. It's faster overall (I get quad scores about as fast as my SkyRaider build without OC) and the screen looks great and it doesn't ever lag for me. The downside is that it's huge and I don't use a case. One slap in the junk with this thing from my pocket when I was trotting down some steps had me thinking twice.
But the INC has lots of customizations and badass devs (SkyRaider/Cyanogen/Virt/Redemption and now Ruby), and I'm kind of just checking out how active it is over here to see how much support it will get. I know the Ruby guys just got an X so that would satisfy me pretty well and they seem to have 2 or 3 devs that seem dedicated.
In a few weeks/months I think the X will have some good things coming. Once they do, I will like the phone more than the INC.
Just remember the Fascinate does not have a LED notifier but there are some hacks around. There is no HDMI out either. I have to admit the screen colors are amazing as well as the form factor, but it almost feels cheap. I love the screen size on the DX, its fast, ruins cool and the developers are flocking to the device since Koush made the Bootstrap recovery. Some of the developers already are, Pete(BB), Koush, ChevyNo1, Birdman, P3, cvpcs(Sapphire), the guys behind Rubix, JRummy was talking recently about getting one and I am sure I missed a few. I would also like to see the UnRevoked team get their hands on a DX to work their bootloader magic.
New Roms on their way are FlyX 1.0 and Obsidian(cvpcs) said he only needs a week from delivery of his X for release which means it could be by next weekend.
Sent from my DROIDX
I'm in the same boat as the OP. I have the incredible for a few weeks now, a few days left in my 30 day window (like 4 haha). I like the device, but the battery life irks me (which is kind've silly since I'm not a heavy user and have had no issues making it through a day with the stock battery. still, I'd like a device that I can use without watching the percentage drop in a few minutes). My two brothers got the X, I went with the incredible as (mostly) I was impatient and liked the hackability it has. Having actually used the device, the ability to load custom roms is nice and all, but using a stock rom isn't really much of a difference for my use. Of concern to me is primarily dumping the Verizon trash but as long as the phone's rootable it's doable. I use Skyraider vanilla but I don't have any real reason that I couldn't use a stock rom.
I've spent many hours trying to come to a conclusion and I've not gotten anything conclusive from online posts and such, everyone seems to get caught up in the 'omg its sooooo big', followed quickly by their gripes with the 'blur-but-not-blur' implementation. I use LauncherPro anyways so much of Blur's issues are not a concern. My only reasonable complaint is the hardware buttons on the X's face vs the touch ones on the incredible, but this is minor imo.
I hate having to babysit my phone to get the best of the battery and the bump charging stuff rubs me the wrong way. I'm coming from an iphone 3g and the widget capabilities are so great, but to save battery on my incredible I have only one auto updating widget, despite desiring more. Separate concern is how Verizon would handle the return since I'm near to my 30 days and the X wouldn't ship for a handful of days, and returning the incredible before that time would render me without a phone. I'm probably going to call them tomorrow and see what they'll do. Perhaps I can get the phone and see how it fares in my normal usage patterns.
If anyone has any input I would much appreciate it as I need something to push me over the edge. Granted, this is the X forum so I doubt anyone will give the incredible much love.

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

Wanting KitKat on N6. Crazy?

I can't be the only one not enjoying lollipop. I feel like it's been dumbed down, had features scrubbed, just horrible experience.
Google and AOSP thrived on customization and user experience. I feel that 5.0 and 5.1 are a step away from that. I'm not even an "early adaptor" this far into the release, yet I feel like a beta tester. Random reboots, Webview crashing tons of apps, I can't use Firefox or Chrome for 10 minutes without a crash, Xposed being dysfunctional. The "interruptions" function is unintuitive. Aesthetically I feel JB and Kk were superior in almost all regards.
I support developers when I can, I want to do nothing but further the Android cause. I can't code so I "buy a beer" for the guys that can occasionally. But each day I'm less and less optimistic about androids future.
Idroid, here we come.
Am I crazy or does anyone else want their 4.4 back as much as I do?
I haven't had any of those problems on 5.0 or 5.1. Are you using a custom ROM or just stock?
ffchampmt said:
I can't be the only one not enjoying lollipop. I feel like it's been dumbed down, had features scrubbed, just horrible experience.
Google and AOSP thrived on customization and user experience. I feel that 5.0 and 5.1 are a step away from that. I'm not even an "early adaptor" this far into the release, yet I feel like a beta tester. Random reboots, Webview crashing tons of apps, I can't use Firefox or Chrome for 10 minutes without a crash, Xposed being dysfunctional. The "interruptions" function is unintuitive. Aesthetically I feel JB and Kk were superior in almost all regards.
I support developers when I can, I want to do nothing but further the Android cause. I can't code so I "buy a beer" for the guys that can occasionally. But each day I'm less and less optimistic about androids future.
Idroid, here we come.
Am I crazy or does anyone else want their 4.4 back as much as I do?
Click to expand...
Click to collapse
The hell you talking about? Lollipop has been rock solid for me. What features were removed? And if you're using Xposed, that's probably your problem-- it's an ALPHA.
These are from a mix of stock and Euphoria. It seemed like the amount of work by devs that went into 4.0+ OS was incredible. Now it's echo chamber reassurances of its better, it's better, so smooth, look at material design. *sip green koolaid*
It feels as if the blind notion of "if it's apple it's great" is engulfing android. I want more devs, more AOSP projects, originality.
I am soapboxing a little here but I digress.
I am dissatisfied with the visual and functional direction android is going and want to head back to Kitkat.
Sent from my Verizon Nexus 6 running Euphoria
Jaspah said:
The hell you talking about? Lollipop has been rock solid for me. What features were removed? And if you're using Xposed, that's probably your problem-- it's an ALPHA.
Click to expand...
Click to collapse
One example. My vibration strength for hepatic feedback and phone ring are linked. I'd like my phone to vibrate on 100% but my key presses to be about 40%. Quick toggle shortcuts are mangled. Lockscreen notification is not on a per app basis.
Forced encryption is an unnecessary tool for most users. If your phone gets turned off after being lost a person who finds it has no owner information. Would device manager even be able to remote lock and erase?
The reason I threw in Xposed dysfunction is because it worked on 4.4. It was a reason I wanted to retreat back to my Kitkat.
Sent from my Verizon Nexus 6 running Euphoria
ffchampmt said:
One example. My vibration strength for hepatic feedback and phone ring are linked. I'd like my phone to vibrate on 100% but my key presses to be about 40%. Quick toggle shortcuts are mangled. Lockscreen notification is not on a per app basis.
Forced encryption is an unnecessary tool for most users. If your phone gets turned off after being lost a person who finds it has no owner information. Would device manager even be able to remote lock and erase?
The reason I threw in Xposed dysfunction is because it worked on 4.4. It was a reason I wanted to retreat back to my Kitkat.
Sent from my Verizon Nexus 6 running Euphoria
Click to expand...
Click to collapse
For the encryption, your owner info appears on the password/pattern page when the device is turned on. I can't comment on the vibration cause I can't even feel it at 100%.
ffchampmt said:
One example. My vibration strength for hepatic feedback and phone ring are linked. I'd like my phone to vibrate on 100% but my key presses to be about 40%. Quick toggle shortcuts are mangled. Lockscreen notification is not on a per app basis.
Forced encryption is an unnecessary tool for most users. If your phone gets turned off after being lost a person who finds it has no owner information. Would device manager even be able to remote lock and erase?
The reason I threw in Xposed dysfunction is because it worked on 4.4. It was a reason I wanted to retreat back to my Kitkat.
Sent from my Verizon Nexus 6 running Euphoria
Click to expand...
Click to collapse
A lot of your complaints in this post also are not addressed in stock KitKat. Sounds more like you miss a particular custom experience.
I've heard of these webview crashes but not once had one. Which seems weird because as a software developer I abuse my phone regularly.
The encryption is more useful with malicious software or network attacks.
ffchampmt said:
One example. My vibration strength for hepatic feedback and phone ring are linked. I'd like my phone to vibrate on 100% but my key presses to be about 40%. Quick toggle shortcuts are mangled. Lockscreen notification is not on a per app basis.
Forced encryption is an unnecessary tool for most users. If your phone gets turned off after being lost a person who finds it has no owner information. Would device manager even be able to remote lock and erase?
The reason I threw in Xposed dysfunction is because it worked on 4.4. It was a reason I wanted to retreat back to my Kitkat.
Sent from my Verizon Nexus 6 running Euphoria
Click to expand...
Click to collapse
Well seems like you are the only one missing kitkat so if anything sell your nexus 6 and get you an older phone that's still running kitkat while the rest of us enjoy our lollipop.
Jaspah said:
The hell you talking about? Lollipop has been rock solid for me. What features were removed? And if you're using Xposed, that's probably your problem-- it's an ALPHA.
Click to expand...
Click to collapse
Lmao only reason i would want kit kat is for the roms.......miui for example
adrynalyne said:
Sounds more like you miss a particular custom experience.
Click to expand...
Click to collapse
Exactly my point. Lollipop ain't cutting it in terms of customization.
I guess it is just me then. [emoji58] I'll just have live with it until gravity box or something of its sort comes along.
Sent from my Verizon Nexus 6 running Euphoria
ffchampmt said:
Exactly my point. Lollipop ain't cutting it in terms of customization.
I guess it is just me then. [emoji58] I'll just have live with it until gravity box or something of its sort comes along.
Sent from my Verizon Nexus 6 running Euphoria
Click to expand...
Click to collapse
Or you could customize it yourself. Thats how most rom modders get started. What it comes down to is not that you miss Kitkat, but that you want years of development in a shorter time.
I would also like to try a kitkat rom as i still have multiple apps and games that are not compatable with Lolipop.
Surprised we haven't seen a rom. Since certain (rare) N6 actually shipped with 4.4.4
Hand76 said:
I would also like to try a kitkat rom as i still have multiple apps and games that are not compatable with Lolipop.
Surprised we haven't seen a rom. Since certain (rare) N6 actually shipped with 4.4.4
Click to expand...
Click to collapse
Yeah and they didn't work because they had been flashed with the wrong image.
http://www.droidmatters.com/news/at...ne-running-android-kitkat-wrong-model-number/
See the baseband unknown and no signal bars? Thats why nobody bothered. It wasn't Kitkat built for the Nexus 6. XT1080 is the Droid Ultra. This was an early early testing build.
adrynalyne said:
Yeah and they didn't work because they had been flashed with the wrong image.
http://www.droidmatters.com/news/at...ne-running-android-kitkat-wrong-model-number/
See the baseband unknown and no signal bars? Thats why nobody bothered. It wasn't Kitkat built for the Nexus 6. XT1080 is the Droid Ultra.
Click to expand...
Click to collapse
Interesting that explains that. So guess it's not going to happen
Hand76 said:
Interesting that explains that. So guess it's not going to happen
Click to expand...
Click to collapse
Probably not. The early debug build found would have worked, if the binaries were correct. As you could see in the video and pic, the binaries were not correct. Without that as a starting point, it gets really hard to port it. Its one thing to use Kitkat binaries in Lollipop, but another to use Lollipop binaries in Kitkat.
I honestly think in every aspect, Lollipop is so much better than previous versions of Android. For once, most things follow a specific design, and even apps are following it. That is the one thing I hated about owning an Android phone, one app looks this way and another looks that way, menu coming from the left, some have a menu coming from the right, it was just all over the place. I love how sleek Lollipop looks and honestly, the stuff CM12.1 has right now is great. Maybe I'm not into customizing the crap of the phones like I used to be, maybe that's why I'm satisfied. I remember when I owned a Vibrant I'd even change the bootsounds, boot animation, font, and all this other stuff. Now, I'm content with having some customizations but having a stable ROM with great battery life is priority for me.
Lollipop blows KitKat away...
Sent from my Nexus 6 using XDA Free mobile app
ffchampmt said:
I can't be the only one not enjoying lollipop. I feel like it's been dumbed down, had features scrubbed, just horrible experience.
Google and AOSP thrived on customization and user experience. I feel that 5.0 and 5.1 are a step away from that. I'm not even an "early adaptor" this far into the release, yet I feel like a beta tester. Random reboots, Webview crashing tons of apps, I can't use Firefox or Chrome for 10 minutes without a crash, Xposed being dysfunctional. The "interruptions" function is unintuitive. Aesthetically I feel JB and Kk were superior in almost all regards.
I support developers when I can, I want to do nothing but further the Android cause. I can't code so I "buy a beer" for the guys that can occasionally. But each day I'm less and less optimistic about androids future.
Idroid, here we come.
Am I crazy or does anyone else want their 4.4 back as much as I do?
Click to expand...
Click to collapse
Those issues are definitely not normal, and I'm betting you have hardware issues as the root cause. Bad RAM, the "hard drive", or something is causing it. 5.1 has been perfect for me with none of those issues.
Hardware issues can be just as common as software. I don't know why people always blame software without even considering it to be hardware. The manufacturing process is not perfect either.
Stock is stable and user experience is what Nexus are meant to be.
I'm enjoying it. I've found cyanogenmod based roms seem to have the most customization. Benzo is really stable. I haven't owned anything besides the Turbo and the N6 since the original droid incredible days so maybe I missed the glory days of kitkat.

May Security update..

I must say I'm rather impressed being the X is an older phone yet it receives the new security updates rather quickly.. Just got May's update..
yes sony , for unknown reason included X on android 8 project
lilbrat said:
I must say I'm rather impressed being the X is an older phone
Click to expand...
Click to collapse
Everything is fine, welcome to Extended support cycle from Sony. Its hardware is still great, so why not update it?
YasuHamed said:
yes sony , for unknown reason included X on android 8 project
Click to expand...
Click to collapse
What unknown? What? Is this device have some problems? Maybe its CPU overheats? Maybe it has bad drivers? Maybe it's running on MTK?
There's everything obvious - Xperia X is still a great device, and it SHOULD get every security update.
Gray47Maxx said:
Everything is fine, welcome to Extended support cycle from Sony. Its hardware is still great, so why not update it?
What unknown? What? Is this device have some problems? Maybe its CPU overheats? Maybe it has bad drivers? Maybe it's running on MTK?
There's everything obvious - Xperia X is still a great device, and it SHOULD get every security update.
Click to expand...
Click to collapse
Initially X was never part of ANdroid 8 when sony released software binaries. however it was last minute include. the line was drawn at X-perf
It feels good how finally Android 8 is running stable on X however as daily driver and with burden of social apps. X starts lagging and overheats as you said! , many functions and camera don't work.
X is not MTK device
YasuHamed said:
Initially X was never part of ANdroid 8 when sony released software binaries.
Click to expand...
Click to collapse
Lies. It was obvious from the start that it will get Oreo. Software binaries? Do you mean SODP ones?
YasuHamed said:
It feels good how finally Android 8 is running stable on X...
Click to expand...
Click to collapse
It was running great from the start. Maybe only camera was a little worse.
YasuHamed said:
...however as daily driver and with burden of social apps. X starts lagging and overheats as you said! , many functions and camera don't work.
Click to expand...
Click to collapse
That's only a problem of YOUR PERSONAL device. My X is neither lagging nor overheating even in a hot situations (tested in my bathroom with 41 gradus temperature, runs great). I don't have any problems with my X, neither all my X users I know from 4PDA. So stop telling people that Oreo is bad when YOUR device overheats and lags, please.
I suggest you to visit some local repair shops and ask them for checking your cooling system.
Gray47Maxx said:
Lies. It was obvious from the start that it will get Oreo. Software binaries? Do you mean SODP ones?
Click to expand...
Click to collapse
personal attacks aside!
on this road map xperia X and X performance was added later, sony had cut-off taken for OREO for XZ PROJECT ONLY! however later two X devices added, A post was on xda did mention last year how Sony has announced to discontinue X and Xc when it was just on 7.0 only! back then everyone was hoping that it should get atleast 7.1, if not Oreo!
https://forum.xda-developers.com/xperia-x/how-to/futur-x-t3614147 <------check yourself
also sony added X, Xp and Xc later in 2017 for Oreo! the original cutoff was til XZ project only! X family was not part of it inicially
https://blogs.sonymobile.com/2017/08/31/xperia-android-8-0-oreo/
Gray47Maxx said:
It was running great from the start. Maybe only camera was a little worse.
Click to expand...
Click to collapse
the Camera still cant record hd video more than 40 secons and shuts down due to heat.
Gray47Maxx said:
That's only a problem of YOUR PERSONAL device. My X is neither lagging nor overheating even in a hot situations (tested in my bathroom with 41 gradus temperature, runs great). I don't have any problems with my X, neither all my X users I know from 4PDA. So stop telling people that Oreo is bad when YOUR device overheats and lags, please.
I suggest you to visit some local repair shops and ask them for checking your cooling system.
Click to expand...
Click to collapse
I own two Xperia X, Black and Lime, so there goes your argument.
also its not my personal opinion and as Hardware there is NOTHING wrong with Xperia X. we are talking about software part.
I have tried my Black X with Omnirom 7.1.1 and 8.1 and the same X has
1. Amazing Batter Life
2. No overheating
3. no Lagging
4. Camera works perfect and records 4K
since you are using my modded kernels and ROOT ACCESS allows you to modify Oreo by having different modes in Magisks and/or control bloatware etc.
I would suggest you to flash oreo .2.70 right-away and use untouched for one weak with all the bells ringing and we will see
YasuHamed said:
personal attacks aside!
on this road map xperia X and X performance was added later, sony had cut-off taken for OREO for XZ PROJECT ONLY! however later two X devices added, A post was on xda did mention last year how Sony has announced to discontinue X and Xc when it was just on 7.0 only! back then everyone was hoping that it should get atleast 7.1, if not Oreo!
https://forum.xda-developers.com/xperia-x/how-to/futur-x-t3614147 <------check yourself
also sony added X, Xp and Xc later in 2017 for Oreo! the original cutoff was til XZ project only! X family was not part of it inicially
https://blogs.sonymobile.com/2017/08/31/xperia-android-8-0-oreo/
the Camera still cant record hd video more than 40 secons and shuts down due to heat.
I own two Xperia X, Black and Lime, so there goes your argument.
also its not my personal opinion and as Hardware there is NOTHING wrong with Xperia X. we are talking about software part.
I have tried my Black X with Omnirom 7.1.1 and 8.1 and the same X has
1. Amazing Batter Life
2. No overheating
3. no Lagging
4. Camera works perfect and records 4K
since you are using my modded kernels and ROOT ACCESS allows you to modify Oreo by having different modes in Magisks and/or control bloatware etc.
I would suggest you to flash oreo .2.70 right-away and use untouched for one weak with all the bells ringing and we will see
Click to expand...
Click to collapse
So do you mean nougat has much better battery than Oreo?
coconutxyz said:
So do you mean nougat has much better battery than Oreo?
Click to expand...
Click to collapse
Due to the following features I am using Oreo (XGEN) build on .2.50
1. Better Screen Resolution/Tone ( the tint in Oreo on screen is soothing to eyes as compare to N)
2. Cleartype ScreenFonts
3. Nighlight
4. Notification settings options and panel
5. Setting Menu simplified (a bit better than Nougat)
-- however these are all UI and cosmetic affects
I was happier and relaxed on the final build .252 (came dec17) android 7.1.1. I kept switching back to .252 after trying first two Oreo builds which I found horrible in terms of battery life & overheating; and its not just me, many user reported the same on various posts (in and out of XDA forums) about how after upgrading to Oreo they are facing overheating and battery drain issues. when X overheats it starts lagging.
10April18 build .2.50 (third attempt) has been quite better than its predecessor builds but still can't compete with dec17 build .252.
REMEMBER, my comparison / observation is on ROOTED Xperia-X
YasuHamed said:
Due to the following features I am using Oreo (XGEN) build on .2.50
1. Better Screen Resolution/Tone ( the tint in Oreo on screen is soothing to eyes as compare to N)
2. Cleartype ScreenFonts
3. Nighlight
4. Notification settings options and panel
5. Setting Menu simplified (a bit better than Nougat)
-- however these are all UI and cosmetic affects
I was happier and relaxed on the final build .252 (came dec17) android 7.1.1. I kept switching back to .252 after trying first two Oreo builds which I found horrible in terms of battery life & overheating; and its not just me, many user reported the same on various posts (in and out of XDA forums) about how after upgrading to Oreo they are facing overheating and battery drain issues. when X overheats it starts lagging.
10April18 build .2.50 (third attempt) has been quite better than its predecessor builds but still can't compete with dec17 build .252.
REMEMBER, my comparison / observation is on ROOTED Xperia-X
Click to expand...
Click to collapse
Yea I will for sure root all my android device so I needed some opinion on rooted device. Guess I might go back to nougat sometimes
coconutxyz said:
Yea I will for sure root all my android device so I needed some opinion on rooted device. Guess I might go back to nougat sometimes
Click to expand...
Click to collapse
i feel the same! i will go back to nougat once sony discontinue supporting X
YasuHamed said:
A post was on xda did mention last year how Sony has announced to discontinue X and Xc when it was just on 7.0 only! back then everyone was hoping that it should get atleast 7.1, if not Oreo!
https://forum.xda-developers.com/xperia-x/how-to/futur-x-t3614147 <------check yourself
also sony added X, Xp and Xc later in 2017 for Oreo! the original cutoff was til XZ project only! X family was not part of it inicially
https://blogs.sonymobile.com/2017/08/31/xperia-android-8-0-oreo/
Click to expand...
Click to collapse
I can't remember the original roadmap, but I can't trust XDA as well. So there you may be right.
UPD: You are wrong. It was included in the list from the start: proof, not updated. Wayback Machine link provided as well.
P.S. What a ridiculous source of the info - just a random guy.
YasuHamed said:
the Camera still cant record hd video more than 40 secons and shuts down due to heat.
Click to expand...
Click to collapse
Do you need my FHD 60 FPS video recorded on X without any additional cooling systems? I can provide one.
YasuHamed said:
I own two Xperia X, Black and Lime, so there goes your argument.
also its not my personal opinion and as Hardware there is NOTHING wrong with Xperia X. we are talking about software part.
I have tried my Black X with Omnirom 7.1.1 and 8.1 and the same X has
1. Amazing Batter Life
2. No overheating
3. no Lagging
4. Camera works perfect and records 4K
Click to expand...
Click to collapse
I have the same on stock Oreo, everything except the first point. OmniROM (and k4.4 in general) are more optimized.
YasuHamed said:
since you are using my modded kernels and ROOT ACCESS allows you to modify Oreo by having different modes in Magisks and/or control bloatware etc.
I would suggest you to flash oreo .2.70 right-away and use untouched for one weak with all the bells ringing and we will see
Click to expand...
Click to collapse
Nice challenge!)
I'd like to accept it, but since I was already using Oreo on locked bl (before your kernel was released for 5121), I can share some thoughts. It was running stable, maybe camera was a little bit worse than I expected. No overheat (was it because of a winter?), no lags, no anything. It was a clean and stable ROM. So...
But thanks for the idea of challenge like this. I have a guy with untouched X, so maybe he will tell something there.
over-heating
Hi Guys,
My Xperia-X is replaced in this may month in warranty.
After replaced I am feeling too much overheating.
From the first day, I have an update to latest may security update.
Now I don't know this over-heating is due to may update or again I got faulty hardware by Sony.
What about you guys do you feel over-heating especially after may update?
Hey folks, heads up June update is out and about..

Categories

Resources