Sluggishness after 6.0.1? - Galaxy S 5 Q&A, Help & Troubleshooting

I installed 6.0.1 BTU on my 900f, It was a clean install and cleared the cache etc, it ran OK for a week now its sluggish and stuttering. I mean I can close active applications, open say 1 app, then hit the home button, the entire launcher redraws, You'd think there were half a dozen memory intensive apps running in the background.
Anyone else have this?

Related

Random applications opening?

I know its a general android problem that apps open themselves in the background, but ever since i updated to manups 2.1 1.5 it seems like more apps, aka all of them are doing that at bootup...
i open advance task manager and my mem is down to 15 right from bootup then i kill em all and its at 35...
is there anyway to make it so unless i allow an app to run in the background, it won't?
because it starts bugging me when i have to kill all these apps several times a day i never open (namely amazon mp3 store which keeps force closing and popping up windows even though i've never once opened it on my own) and everything else runs too...

Hardware vs. software

Hi there, on my second vibrant. I'm having some issues with this one and I need help determining if they are hardware related.
I'm running 3 homescreens with:
Beautiful widgets
Pure messenger widget
Switch pro
Pandora
I'm also running launcher pro.
I have some major lag problems when launching apps. It takes a minute or so to open most apps, plus I get a lot of black screens. I've factory reset the phone twice and the issues go away for a while on stock settings but the phone starts to lag a bit as I load apps.
Any ideas?
I might just return it....even though the phone runs ok on stock settings, might have a hard time returning it.
Sent from my SGH-T959 using XDA App
most likely software.. and related to one of the apps you have dl'd. as you said in your post, the phone works fine stock and doesnt start to act up until you load apps.
i would suggest you just install your apps one by one and have a small testing phase between each one. then when it starts lagging you will know what app to avoid.
Wait did this happen on both phones. Even if not, still sounds like something you've done to the phone. I would root and run autostarts to prevent certain items from opening. It's all in the sticky if you want to try.
Its both, look into the lag fix. Launcherpro + all widgets are running off the internal sd along with the appdata (thats moved in the lag fix) and with the poor performing I/O of the internal sd, it lags. The stock launcher + samsung apps is built into the system dir (internal nand) so doesn't lag as bad.
No, I returned the first phone because the homekey wasn't working.
Once the apps do manage to load, I notice that there isn't anything I can do to slow the phone down. Certainly seems more and more like a software bug...Maybe Launcher Pro isn't playing nice (even though I've reinstalled it a few times, and after factory reset). That or the Pure Messenger widget (scrollable) is what's screwing everything up. It worked fine on my Mytouch 3gs though...We'll see.
I'll add apps one by one until I find the culprit.
OK, thus far installed ADW instead of Launcher Pro...
Everything seems to work really well thus far. ADW seems to handle scrollable pure messenger widget much better than Launcher Pro. I think that was the source of my incredible lag.
Still testing, but has anyone else had issues with the scrollable pure messenger widget and Launcher Pro?

Atrix's (or Android's?) memory handling behavior -- auto shutdown of apps etc.

Hi fellas,
Something's been peeving me lately with the Atrix, and it's got to do with its memory handling & auto-killing functionality.
This particular situation has been driving me nuts:
I like to use both the native browser & and the Opera browser. Primarily I use the native browser, which is set as the default, and Opera when I want to check something and I want the full (non mobile) webpage layout and its superior (in my opinion) rendering quality and speed.
So, say I've got Opera open on Engadget or XDA, one or two tabs open. I hit the Home button and open Youtube to look something up. Finish the video, hit the Home button again, and launch Opera, and it has exited already and has to reload my tabs again. This of course can cause issues like losing my place in the page or a flash video I had paused, or a message I was typing and wasn't done with.
In this simple example, all I did was launch a browser, open 2 tabs (40-60 or maybe even 80 MBs of RAM usage, depending on page complexity), hit the Home button, launch the YouTube player (30 to 50 MBs RAM usage), hit the Home button again and Opera's already been killed.
OS Monitor shows there's about 470 MBs of RAM free.
What gives? Checking the autokill settings it shows that the OS will kill empty processes when free RAM hits 82 MBs of free RAM (default settings, haven't messed with them)
This behavior doesn't happen only right after a fresh reboot. Once I've opened a few apps, google readers, twitter, facebook, camera/gallery, browser etc., it happens every time. I say this because, while I'm not a programmer (beyond high school level C++ and general computer curiosity), from what I understand by watching the app life cycle videos on Google's Android programmer site, if Opera and YouTube were the last apps to be launched, they should have the highest priority in being kept in memory and not being killed, and previously open apps should be killed off to reclaim memory before them.
I found that using Gemini app manager I can set an app to not be killed automatically, and while I understand that it's not recommended that this is done by end users, it does work, and I use the Exit button in Opera to exit it once I'm done using it.
It just seems ridiculous that I always have between 350-450 of free RAM available to the system, while apps that I use often end up being killed in the background.
Before someone jumps on me, I understand that Android apps are designed to be shut down and reopened seamlessly. My annoyance stems from the behavior of a phone that has 836 MBs of RAM to work with, and about 570 available on startup (I've frozen several motorola processes I don't use, such as the social network integration and home launcher).
I just tried what you did (open opera, loaded bbc and endgadget, watch a youtube video than returned to opera) and opera retained everything including webpage, where I have scrolled to etc. I would suggest you to unfreeze the moto apps and try again, maybe that is what is causing the problem. Sorry I could not be of greater help =(
I'm not disagreeing with you -- like I said, it's not the case after a fresh reboot, or perhaps when not using the phone heavily. It had been a couple of days since rebooting the phone for me, and kept happening all evening long every time I switched apps.
Still, even when I force keep Opera open through the Gemini third party app manager, and while opening other apps, the RAM usage never goes below 300. The OS is overly aggresively in keeping RAM free, and considering it never falls below 100 MBs free of RAM, it shouldn't be shutting down apps EVER -- at least according to the autokill levels. Is there something else I should be looking at in determining when Android kills apps open in the background?
Was it just a fluke due to memory leaks, etc?
Edit:
Further research shows that Gemini app manager doesn't stop it from being killed, but rather removes it from its own auto task kill list (which I don't use). Seeing Opera stay open for a while after a fresh reboot shows that after two or three days of being used, the phone's memory management gets bogged down & that's what caused the very short app lifespan.
I wouldn't mind rebooting more frequently if it wasn't for that damned battery jumping issue.

RAM manager - clear memory??

Once in a while if I notice a slight lag, I bring up the task manager (bottom left when accessing recent apps), go to the "RAM" tab and tap clear memory. What's really confusing me is that it always closes a very high number of apps, even if it's only been a day since I've last cleared it. i.e. I just cleared it and it said "27 apps closed"! There have been times where it was even more...once it was almost 40.
I use the phone a lot, but it's always the same handful of apps... at most, even in a given week I don't exceed using about 6-10 different apps.
So can someone please explain to me what the hell are all these dozens of "apps" being closed? ??? I assume they're including system apps in with the regular apps, but what apps could they be? That's around 20 apps I had no idea were even running...
siciliano777 said:
Once in a while if I notice a slight lag, I bring up the task manager (bottom left when accessing recent apps), go to the "RAM" tab and tap clear memory. What's really confusing me is that it always closes a very high number of apps, even if it's only been a day since I've last cleared it. i.e. I just cleared it and it said "27 apps closed"! There have been times where it was even more...once it was almost 40.
I use the phone a lot, but it's always the same handful of apps... at most, even in a given week I don't exceed using about 6-10 different apps.
So can someone please explain to me what the hell are all these dozens of "apps" being closed? ??? I assume they're including system apps in with the regular apps, but what apps could they be? That's around 20 apps I had no idea were even running...
Click to expand...
Click to collapse
They're system apps, if you're rooted you could install an app like Clean Master and take a look at which system apps are running.

[Q] CM13 foreground apps closing

Hello!
I have a problem with CM13. Since I installed it, android became slower. It often feels like it has full memory and it cannot open new apps, aswell sometimes foreground apps are getting killed (lack of memory?). Going back to "desktop" makes it load again, as it was killed before.
Never had so much problems with memory on stock android. Lately it has even killed waze running foreground twice, while I was using it to navigate.
I dont have much of apps running (checked under developer options - services). Any idea what settings to change, so it doesnt behave as bad as it does?

Categories

Resources