• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Wow, Lollipop 5.1/5.0 has been the worst experience by FAR.

Page 3 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
5.1.1 actually has 1 thing that I despise with a passion. Ever since the update appeared on my Note 4 after a call lasts for 5 minutes the screen locks and freezes when I try to unlock it to access the dialer, hang up or use the other functions. I have actually started using a Bluetooth Headset just to get around the issue.
 
sweenish said:
And you would be wrong. iOS is on a similar update schedule. One major version per year. Like I said, 5.1 was fast. It was also necessary because 5.0 was a joke.

It's on schedule. Previous release to next announce is a terrible measurement, and why am I even having to tell you that? It's release to release, because that makes sense, when discussing "quickly released."

Google used to release two major versions a year, now it's one. This is not slow.

I wasn't discussing the naming or numbering. Just the fact that you think a company that releases major updates annually releasing a major version one year later is somehow quicker than the schedule they've set for themselves.
Click to expand...

Then we're definitely talking about two different things 🙂

When I said 'M' was released quickly, I was specifically talking about the name change, not the actual updated codes or minor/major releases or whatever updates Google is scheduling for Android. I was arguing that 'M' was announced early so people can quickly forget about the name Lollipop and how bad the name got (because of the botched 5.0). The basis of my argument was that no matter what kind of minor/major updates Google has planned for Android, there is no pattern as to when the name change takes place (I gave you the example of the two JellyBeans as a proof of this, maybe I should also include that 2.1 to 2.2 is about 6-7 months, and they're Eclair and Froyo).

This is also why I counted the time from when Lollipop is released (when the public started to use Lollipop and found out how bad it was) to when 'M' was announced (when people are 'assured' that the next one would not be Lollipop anymore and it would be out soon). Because (what I believe to be) 'quick release' of M is necessary, as Google wanted to get the next name out to steer perception.
 
Last edited:
Okay, this makes a lot more sense.

I can get behind that thinking, but at the same time, a lot more changes have gone into Marshmallow than something like 4.1 to 4.2 Jellybean. And they were on a six month cycle at that time as well.

I think it's much more a bit of Column A, bit of Column B thing. They're moving past Lollipop due to 5.0 being a mess. But a lot has gone into Marshmallow, probably enough to justify the new name regardless of 5.0's initial impression.

I hope the rumors pan out and updates start rolling out tomorrow, though. My short time on the latest preview was great.
 
sweenish said:
Okay, this makes a lot more sense.

I can get behind that thinking, but at the same time, a lot more changes have gone into Marshmallow than something like 4.1 to 4.2 Jellybean. And they were on a six month cycle at that time as well.

I think it's much more a bit of Column A, bit of Column B thing. They're moving past Lollipop due to 5.0 being a mess. But a lot has gone into Marshmallow, probably enough to justify the new name regardless of 5.0's initial impression.

I hope the rumors pan out and updates start rolling out tomorrow, though. My short time on the latest preview was great.
Click to expand...

oye
 
Here's hoping my G2 gets Marshmallow, though since smartphone OEMs in general royally suck, My hopes aren't up too high.
 
Well, after poking around some more and looking at OS Monitor to see my CPU and memory usage, the culprit is Fallout Shelter. When you switch out of it the program continues to take up 250MB of RAM (but there is still ~275MB of free RAM) and the crazy slowdown occurs when kswapd0 is trying to free memory (writing stuff to ROM I'm guessing). After the slowdown Fallout seems to only take up 90MB and the system lag isn't *as* bad. But this swapping takes a while - more than enough time to miss many turns if you're using GPS and to make Web browsing and typing impossible for a solid 5 minutes or more.

So basically when I switch out of Fallout I have to remember to go into OS Monitor and kill the process manually *immediately* (if I switch to another program I'll get caught in lag/kswapd0 hell), which to me is kind of retarded, especially considering that an extra 250MB is all it takes to bring the S5 to its knees in terms of memory usage, and even with 275MB of free RAM the phone still goes kaput.
 
Last edited:
fuzzybabybunny said:
Well, after poking around some more and looking at OS Monitor to see my CPU and memory usage, the culprit is Fallout Shelter. When you switch out of it the program continues to take up 250MB of RAM (but there is still ~275MB of free RAM) and the crazy slowdown occurs when kswapd0 is trying to free memory (writing stuff to ROM I'm guessing). After the slowdown Fallout seems to only take up 90MB and the system lag isn't *as* bad. But this swapping takes a while - more than enough time to miss many turns if you're using GPS and to make Web browsing and typing impossible for a solid 5 minutes or more.

So basically when I switch out of Fallout I have to remember to go into OS Monitor and kill the process manually *immediately* (if I switch to another program I'll get caught in lag/kswapd0 hell), which to me is kind of retarded, especially considering that an extra 250MB is all it takes to bring the S5 to its knees in terms of memory usage, and even with 275MB of free RAM the phone still goes kaput.
Click to expand...

I have a local map app that ate up 12% of overall battery usage on my 5.0 Note 3 when completely left unused and while there is absolutely no network connection or location enabled. Sometimes I really wonder whether core Android was programmed by idiots.
 
fuzzybabybunny said:
Well, after poking around some more and looking at OS Monitor to see my CPU and memory usage, the culprit is Fallout Shelter. When you switch out of it the program continues to take up 250MB of RAM (but there is still ~275MB of free RAM) and the crazy slowdown occurs when kswapd0 is trying to free memory (writing stuff to ROM I'm guessing). After the slowdown Fallout seems to only take up 90MB and the system lag isn't *as* bad. But this swapping takes a while - more than enough time to miss many turns if you're using GPS and to make Web browsing and typing impossible for a solid 5 minutes or more.

So basically when I switch out of Fallout I have to remember to go into OS Monitor and kill the process manually *immediately* (if I switch to another program I'll get caught in lag/kswapd0 hell), which to me is kind of retarded, especially considering that an extra 250MB is all it takes to bring the S5 to its knees in terms of memory usage, and even with 275MB of free RAM the phone still goes kaput.
Click to expand...

Or properly exit from the app. I've never had issues with Fallout Shelter.

Something like a home button exit will naturally try to keep the game in RAM, it assumes you're coming back to it.

Ideally, it would behave better, but still. It treats the system just fine if you properly exit.
 
Zivic said:
I'm with you, kit kat was much better
Click to expand...

I downgraded to KitKat on my OnePlus One. Mostly because of the battery drain problems with Lollipop, but also the user interface problems and bugs.

Lollipop is the Vista of Android.
 
The memory leak seems to be gone from marshmallow, haven't experienced any webpages reloading at all.
 
shabby said:
The memory leak seems to be gone from marshmallow, haven't experienced any webpages reloading at all.
Click to expand...
Was Marshmallow just released? I'm not holding out hope that the TMO S5 will get it.

And I like the Samsung camera app way way too much to go with stock Android.
 
Zodiark1593 said:
Here's hoping my G2 gets Marshmallow,
Click to expand...

G2 owner here too, and honestly I don't give a rats ass if I get Marshmallow or not. I'm on kit kat and its perfect and I'm not upgrading until I get a new damn phone.

I was on LP for a month and I wanted to fling my phone against the wall
 
So the wife got a new LG G4, decided it was too big, and swapped me for my LG G2. Her previous phone was an LG G2. I had no problems with either of our 2's upon the initial upgrade to 5.0.

However when we made the swap last week, her new to her LG G2 that I gave her started having the infamous battery drain issue after it automatically updated. (We had to factory reset each phone to get the phone numbers to swap). I'm hoping it will get 6.0 sometime soon (supposedly it's coming for Verizon?) but now she is really ticked off, and I can't fix it.
 
Lat said:
I just upgraded to the LG G2, and it works great with Lollipop. You just have to install a CAF (AOSP) rom for 5.1.1 instead of relying on stock.

5.0 still has issues, many of which were corrected on 5.1. If you can live with slightly inferior camera software, CAF (AOSP) is definitely the way to go (or stay on kitkat stock).

http://forum.xda-developers.com/lg-g2/development/rom-dirty-unicorns-5-1-1-t3162408
I'm running this with the Render CAF kernel.
Click to expand...
What phone were you using before the G2? Seems weird you upgraded to a 3 year old phone
 
fuzzybabybunny said:
So I've been on LP for a few months. It is absolutely the worst Android OS in terms of speed since I don't know when.

It's the memory leak thing. And then the process kswapd0 goes insane trying to manage memory.

The user responsiveness basically grinds to a halt. You have to do a restart, probably multiple times a day, which is really super annoying if you're in the middle of something (which, by definition, you always are if lag is a problem).

I have an S5. It's not the newest phone but it certainly should not be this slow.

Is it possible to downgrade to KitKat after upgrading to Lollipop? I read somewhere that there were deeper processes that stick around after a Lollipop upgrade?
Click to expand...

Definitely possible!! I downgraded from lpop to kk 4.44 via this forum. Head to the forum and find ur phone. Following the downgrade, no probs at all.
http://forum.xda-developers.com/moto-x/moto-x-qa/guide-faq-how-to-downgrade-5-1-to-4-4-4-t3182118
 
Lollipop was my least favorite Android version by far. So glad to be running marshmallow on my nexus 6, it runs so much better
 
fuzzybabybunny said:
So what I'm getting from this thread is certain devices work perfectly with 5.1.1 while other devices, my S5 included, do not.

For some reason.
Click to expand...

Well, that "some reason" is not happening with my S5, so I'm gonna suggest that other variables are at play here. My S5 on 5.1.1 is rock solid with great battery life and as quick as the day I got it (4 months ago). Hard to explain, but there it is. If I am in the minority here, so be it, but I cannot imagine my phone running any better on Marshmallow.
 
Last edited:
Lollipop was just alright on my S4... google play services just loved to suck up the battery... google services was also sucking my battery up on my nexus 6 for the week I had it before I got the Marshmallow upgrade pushed with vastly improved the battery life.

After tinkering around with rooting and installing a fresh lean ROM with a lean set of GAPPS that only includes the basics I'll never go back to a bloated locked phone again much less even stock android which still has quite a few installed APPS I'd rather not have on there.

Combined with greenify, hosts file ad blocking, swipe navigation and disabling the navigation bar completely (adds screen space and eliminates navigation bar burn in) , and apps or browsers that allow a fullscreen mode like naked browser, I'm loving this new setup. That and the cobalt icon set and nova/apex launcher just make the thing look great too. Also "KCAL" app to calibrate the screen to remove the warmish tint it comes default with.

All this greatness for just $300 for a new phone and $35/month for cricket wireless. Seems like a steal.

Marshmellow is not perfect though... the battery status is a bit messed up.. it will say that wi-fi only used 1% of the battery when in fact wi-fi is probably the biggest battery drainer when I leave it on and go to bed... just have to learn what uses the battery and shut it off.. it's still not up to Apple's level where you never have to tweak any settings but it's a nice improvement and the freedom and customization along with the phones being half or less the price is worth the tradeoff.
 
Last edited:
The first version of Lollipop was not the greatest, but 5.1 became pretty good, just like Vista.

The first Vista version was terrible, but with the latest service packs it became a good OS, not the best, but good.
 
I don't know what version her S5 is on but it feels slow compared to my nexus 6.
I'm trying to get her to switch to a nexus 5x since she doesn't like the size of my nexus 6
 
http://www.ebay.com/itm/Samsung-Gal...k-Gold-G920i/231682765161?hash=item35f15e7169

As long as she is careful installing apps, e.g. avoid apps that constantly want to sync in the background, apps that like to phone home and let their servers know her whereabouts, the S6 might serve the purpose. The one linked above is unlocked version without carrier association and is relatively bloat free.

I have both the S6 and the 5X, and at the same price there just is no competition when it comes to hardware.

Alternatively you can find the Nexus 5 (not the 5X) for ~$180 brand new @Amazon.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top