Not liking the Nexus 5X because of lag

[Bob Garon]

Wonder when we'll get 6.1 to correct all these issues.

Posted via my Nexus 5X & T-Mobile Unlimited

 

[eaccentsac]

I have not really had any lag on mine (but I also have not used a 6p...so maybe it's a perception issue).

I will say this - people seeing issues on this device (and the 6p) is not surprising to me. Issues are pretty much a given when using the first major release of any software. This is something that people don't mention enough when it comes to Nexus devices. If you buy a Nexus out of the gate, you ARE Google's testing ground for the first few updates of a release. You are also acting as a beta tester for 3rd party developers who have not optimized their apps for 6.0 yet (see: facebook, snapchat, etc). I am confident this will get worked out as I have been through it before. But this is part of the tradeoff for being on the bleeding edge of software.

I don't have lag either on my 5X as a moderate user (no gaming, rarely watch videos) but totally attached to my phone

I think the biggest issue is not the OS, which in safe mode or out of the box should run fast and smooth, but more the fact that apps are not yet optimized for our version of the OS.

 

[eaccentsac]

Re: Laggy phone

Did you have a case? Without a case, a phone falling off a table on to a hard surface causing a cracked screen sounds right to me. With a case (a real one, not one of those slim cases that barely cover the back), then that may be a bit surprising.

As for the lag, I feel your pain. I came from the original Nexus 5 which could be left on for months at a time without any lag, but I find that if I don't reboot my 5x once a week, I get a lot of lag. It's not a big deal for me because rebooting once a week is not a hardship, but it was surprising at first. And I don't think it's Marshmallow, because my wife now has my original nexus 5 with Marshmallow, and she does not need to reboot.

So, is your phone laggy even an hour after a reboot, or after a few weeks of continual uptime? If the former, then it's not just you. If the latter...maybe just you?

I wholeheartedly agree. Expecting a phone without a case to come out unscathed from a fall is kind of unrealistic. We're talking about glass and sensitive electronics....

 

[ADufresne]

I'm a new arrival to Android today after many years on Windows Phone and had a question concerning the statement:

"apps are not yet optimized for our version of the OS"

How does one find out whether a given developer/publisher has optimized for the latest OS release, particularly as it might relate to something like power/memory management? Scour release notes in case they mention it?

 

[aysiu]

I think the biggest issue is not the OS, which in safe mode or out of the box should run fast and smooth, but more the fact that apps are not yet optimized for our version of the OS.

Really? I have lag switching apps, but not within the apps themselves. the only app that lags launching up fully or running well is actually Google's Camera app... and even that is only slower to resolve (or never resolves) if I launch it from the double-power tap instead of through the GUI.

 

[aysiu]

I will say this - people seeing issues on this device (and the 6p) is not surprising to me. Issues are pretty much a given when using the first major release of any software. This is something that people don't mention enough when it comes to Nexus devices. If you buy a Nexus out of the gate, you ARE Google's testing ground for the first few updates of a release.... But this is part of the tradeoff for being on the bleeding edge of software.

I fully realize this and embrace it, which is why I haven't come in here being all "Lag issues! What a piece of crap phone this is!" But I do believe there are more acceptable reactions than "Lag issues! What a piece of crap phone this is!" and "Lag issues? There are no lag issues... you're doing it wrong!"

There are lag issues. It may be a difference of perception or some faulty builds or just general your mileage may vary or whatever, but it's enough that it needs to be addressed at some point. I fully recognize it's essentially beta software, and I look forward to Google releasing updates to make this a smoother experience.

I still love my phone, despite the lag issues.

 

[Grabber5.0]

I personally think for most apps, that is a cop-out statement. If the OS is changing so radically with every release that apps have to be "optimized" then it's not a platform that is ready for widespread use. I'm sure there are specific improvements that can be taken advantage of, but as a dev, it could create a support mess or cut off previous Android versions for apps. In most cases, I think there are apps that perform poorly and create performance problems on the device.

 

[eaccentsac]

I'm a new arrival to Android today after many years on Windows Phone and had a question concerning the statement:

"apps are not yet optimized for our version of the OS"

How does one find out whether a given developer/publisher has optimized for the latest OS release, particularly as it might relate to something like power/memory management? Scour release notes in case they mention it?

Welcome to Android!

There is no obvious way to tell. I usually look for very high ratings (4 or more by several thousand), and very recent updates (since the last OS update for your device). In Google Play, when looking at reviews, there is a way to isolate "reviews for just this device." That's oftentimes helpful as well since all 5X are running essentially the same OS version.

Most GOOD devs are very responsive. If you are worried, send them an email.

Hope this helps!

 

[eaccentsac]

Really? I have lag switching apps, but not within the apps themselves. the only app that lags launching up fully or running well is actually Google's Camera app... and even that is only slower to resolve (or never resolves) if I launch it from the double-power tap instead of through the GUI.

Argh. That sucks.

Hate to say it, but my 5X doesn't have any issues switching apps either....

 

[eaccentsac]

I personally think for most apps, that is a cop-out statement. If the OS is changing so radically with every release that apps have to be "optimized" then it's not a platform that is ready for widespread use. I'm sure there are specific improvements that can be taken advantage of, but as a dev, it could create a support mess or cut off previous Android versions for apps. In most cases, I think there are apps that perform poorly and create performance problems on the device.

There were some important changes between 5.X and 6.X. If apps have not been optimized (updated) to work with those changes, it wouldn't take much to make them glitchy...either just for that app or how they interact with other apps and the OS in general.

Saying that the OS found on the Nexus line of devices is not ready for widespread use....? I'd say that it's ready since it runs great for the vast majority of folks using it, but remember that the app devs put their resources where they can get the best bang for their buck. At this point, with Marshmallow on less than 1% (January distribution numbers) of all Android devices, I think that it's safe to say that most devs probably aren't that concerned if their app doesn't work flawlessly on less than 1% of the Android devices in the world.

I do agree that some apps are definitely coded better than others. I have a calendaring app that pretty much never fails to work correctly. Anytime there is an issue reported, you see an update the very next day if not the same day (yes, that dev is that good).

 

[aysiu]

It's not like the apps that aren't "optimized" don't run and just crash on startup. I've been running all the same apps on my Nexus 5x that I ran on my Moto X 2013, and they all run just fine. I don't know that they've all been "optimized" for Marshmallow (in which case maybe they'd run even better?), but they work for sure.

 

[eaccentsac]

It's not like the apps that aren't "optimized" don't run and just crash on startup. I've been running all the same apps on my Nexus 5x that I ran on my Moto X 2013, and they all run just fine. I don't know that they've all been "optimized" for Marshmallow (in which case maybe they'd run even better?), but they work for sure.

Just wondering, ... are the same apps that you are running the 5X the same version of the app that you are running on the Moto X 2013?

 

[eaccentsac]

Just wondering, ... are the same apps that you are running the 5X the same version of the app that you are running on the Moto X 2013?

I remember when the Motorola Pure Edition was updated to Marshmallow--the Google Play Rewards animation that showed your balance after you answered their survey was really glitchy. It has now been remedied. It worked flawlessly when I had 5.X on my Pure Edition, but when I first updated to Marshmallow it was ugggggly.

 

[Jayus]

Re: Laggy phone

Nope i didnt have a case, i was about to get one but i thought it would be strong enough, wrong thoughts. However nothing is broken or scratched except the screen i hope i'm able to fix it somehow, i really like the design of the phone.

About the reboot thing, will try that tomorrow

 

[Grabber5.0]

My point wasn't that Android isn't ready - though it certainly has its problems. I'm saying in the majority of cases, certainly not all, app problems have less to do with OS updates and more to do with bad coding.

 

[eaccentsac]

My point wasn't that Android isn't ready - though it certainly has its problems. I'm saying in the majority of cases, certainly not all, app problems have less to do with OS updates and more to do with bad coding.

Oops. Sorry

 

[Grabber5.0]

Oops. Sorry

No problem.

 

[aysiu]

Just wondering, ... are the same apps that you are running the 5X the same version of the app that you are running on the Moto X 2013?

Some of them have been updated since, but, yes, as far as I can tell.

 

[aysiu]

My point wasn't that Android isn't ready - though it certainly has its problems. I'm saying in the majority of cases, certainly not all, app problems have less to do with OS updates and more to do with bad coding.

I think bad is a bit too evaluative instead of descriptive. The truth is any time you change something, something else can be affected—that's just how programming works, and even if you're a "good" programmer, you still make mistakes or have oversights. That's what patches and new versions are for. What matters the most is good testing, debugging, and then prompt fixes. You can't prevent incompatibility or lack of optimization by coding the "forever-will-work-with-Android" app.

 

[ADufresne]

Thank you. Very helpful response. I have plenty to learn about this platform.