• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Weird thing since updating to marshmallow...

Murf1

Android Enthusiast
Boost version.
Since my update, often in the morning when I tap an icon on my home screen, nothing happens. I can rapid-fire the icon - any icon and phone just sits there. It is not locked up, but also won't start an app. I have a PowerClean widget to "boost", memory cleaner, and it will do it's thing, but still no app launches. I wondered if Greenify was causing issues with marshmallow "Doze" so I unistalled Greenify. Still had the issue this morning.
I discovered this morning if I press the virtual "Square" button (to right of virtual "circle" button - "Home" I think that one is called) that brings up the all the recent programs you have ran to scroll thru, and press "Clear All" - after that the icons start responding again. So far I have really only experienced it when I first started using it in the morning I think. So that is why I wondered if Doze feature was doing it. I guess I need to "Clear All" at least each morning.

Anyone know what causes that?

thanks
 
I think the update requires to much processing,since the MM update my lg stylo has responded differently as well,icons don't respond for a few seconds,screen animation slows down,and right now while i was typing and this is the most irritating flaw;the keyboard closes randomly on its own no matter if you tap the text cursor,it pops back up randomly on its own,i dont know about the other variants of the lg stylo but i know this version ran ok till the update and the companies just wanted to push 6.0 update that they didn't bother to get all the bugs out.sorry no solutions yet but i am pretty sure its the update not integrating with the device in the right way.
 
I think my issue could be the "Google Opinion Rewards" program. It often seems to happen after I open and close that app. Maybe it doesn't play well with MM.

I use the SwiftKey keyboard and have not had any issues with it.
 
I think the update requires to much processing,since the MM update my lg stylo has responded differently as well,icons don't respond for a few seconds,screen animation slows down,and right now while i was typing and this is the most irritating flaw;the keyboard closes randomly on its own no matter if you tap the text cursor,it pops back up randomly on its own,i dont know about the other variants of the lg stylo but i know this version ran ok till the update and the companies just wanted to push 6.0 update that they didn't bother to get all the bugs out.sorry no solutions yet but i am pretty sure its the update not integrating with the device in the right way.

I too am having very similar issues since the update. Videos on Youtube and Facebook randomly restart. Flipping through the app drawer is slow and tedious OR choppy. Buttons randomly decide to lag or not work at all. I too believe ram is being unnecessarily eaten up as well. Clearing the recent apps SEEMS to temporarily help, but that's short lived. Now AVAST Cleanup has been the biggest help, tried that on a whim because I've used it extensively on my Lg G4. So far on day 1 the phone is back to being responsive. PS anyone have issues with the screen flickering very fast(like watching an old crt tv through a camera) on the Stylo BEFORE the Marshmallow update?
 
I too am having very similar issues since the update. Videos on Youtube and Facebook randomly restart. Flipping through the app drawer is slow and tedious OR choppy. Buttons randomly decide to lag or not work at all. I too believe ram is being unnecessarily eaten up as well. Clearing the recent apps SEEMS to temporarily help, but that's short lived. Now AVAST Cleanup has been the biggest help, tried that on a whim because I've used it extensively on my Lg G4. So far on day 1 the phone is back to being responsive. PS anyone have issues with the screen flickering very fast(like watching an old crt tv through a camera) on the Stylo BEFORE the Marshmallow update?

(On Boost version) I've noticed lag too and like you said, clearing the recent apps helps temporarily.
 
I had several issues with the T-Mobile 6.0 update. From apps not opening up right away to wifi randomly turning off on it's own and several other smaller issues. And as much as I know people do not want to hear it, I did a factory reset and re installed all my apps and all my issues disapeared. So my best advice is to factory reset after you recieve the update. My thoughys are that is is because it is such a big updatewith so many changes being made by only using patch files in the update.zip it causes random issues. If you factory reset it allows the system to properly set everything up on first boot.
 
Stay away from Cheetah Mobile apps. All of them.



As far as Marshmallow or any other major update, it's always recommended to do a factory reset before or after an update. It's a PITA because you have to backup up your whole phone before a factory reset but it's worth it if you need a clean running phone.
 
As far as Marshmallow or any other major update said:
Hmm, I wonder if that would fix the issue where I can only "move to SD" 500MB worth of apps to a 32GB SD and it says the SD doesn't have enough space (yet the SD works fine for everything else).
 
Probably not. However if your rooted you might be able to force adaptable storage. It's turned off in the build.prop and I know you can enable it through ADB. There's also apps like Apps2SD and Link2SD however they were made for older android versions so you'd have to research an try.

Do you think they intentionally put a cap on how much you can "move to SD" or is it a defect in the Boost Mobile jank version of MM?
 
Probably not. However if your rooted you might be able to force adaptable storage. It's turned off in the build.prop and I know you can enable it through ADB. There's also apps like Apps2SD and Link2SD however they were made for older android versions so you'd have to research an try.

In the build prop is this line #simulate sdcard on /data /media cant we change this to make aps download to the sd card instead of internal memory?

edit in my build prop adoptable storage is set to true what would we change it to
 
Back
Top Bottom