5.1.1 still aggressively kills common apps - Sprint Samsung Galaxy S6 Edge

This is super frustrating.
I knew that Android 5.0 had issues, because prior to 5.0, my LG G3 never ONCE closed out a chrome tab while I was playing podcasts.. After I got to 5.0.2, I had problems with the browser being closed when in the background AND I had about 5 other apps I was actively switching between... though I had to leave the browser in the background for a good 5-10 minutes before anything bad happened.
Things are quite different on the S6 Edge, and there's no improvement moving to 5.1.1 -- at all. In fact, it might be worse.
I've gotten in the habit of rebooting my phone every 4-5 hours to help combat this, but it's still infuriating.
Common examples:
- I get in my car, start Escort Live, start playing music on Spotify, then load up a route in google Maps. Within 3-5 minutes, Escort Live will close in the background without warning. Sometimes Spotify closes as well, simultaneously. Sometimes maps will close.
- Playing a podcast in Chrome, sometimes just hitting the home key will kill what I'm listening to.
I've exhausted my search efforts looking for some way to keep these apps alive. There's no legitimate reason to ever close Maps, Escort Live, Torque, Spotify, or a Chrome tab playing audio. What's going on here? I know that it was widely established that 5.0.2 still had this issue, but rumors were circulating that things were fixed after 5.0.3+. This is noticeably worse that my LG G3. It basically eliminates the ability to multi-task.
Does anyone have any tips to fixing this? Currently I am not rooted, because I wanted to see if 5.1.1 would help out with this issue.
Thanks!

wow...this is unfortunate news to hear. I was holding out hopes that 5.1.1 would finally allow the edge to shine as the phone it should have been. sounds like there's still a long ways to go. Wish I wasn't still waiting for the damn OTA....sigh..

Maybe you could use Smart Switch to upgrade? Not sure what version it provides...

We just need CM12 lol.
Sent from my SM-G925P using Tapatalk

jkt97401 said:
We just need CM12 lol.
Sent from my SM-G925P using Tapatalk
Click to expand...
Click to collapse
I'm wondering if I can create an init.d script to have an app stay running. I'd chkconfig on using tasker or whatever. Probably need root for that.

Try this
http://forum.xda-developers.com/showthread.php?p=63268027
Sent from my XT1033 using Tapatalk 2

Related

[Q] MultiTasking broken after day of use (or memory leak?)

Hello everybody.
first of all i just want to mention that im really happy with the phone, especially after moving from galaxy s3 with its horrendous memory tasker and RAM.
ive noticed a problem thats been really bothering me:
after a day of use , maybe more, there seems to be a lot less memory available for the device, resulting in chrome/chrome beta reloading every time that i go back to it, even without performing any actions or loading new apps - simply moving to whatsapp for example and back to chrome - Bang! the browser reloads. I want to emphasize that this is not the normal behavior for chrome, as this does not occur after a fresh restart.
When i go to services running, there is about 800mb of ram left, but when i go to ES task manager, there is only 400mb, i dunno the cause for this difference, but i do know that despite disliking task managers very much , Pressing "Kill ALL" will restore the desired behavior for a while (no reloads).
I tried to root the phone and install Greenify , but this doesnt seem to be helping.
did anyone notice any similar behavior? thanks.
In my experience, chrome and chrome beta are huge memory hogs and refresh quite often no matter what. For that reason, I stay away from it and stick with the aosp browser. It's fast and light.
Sent from my SGH-T999 using Tapatalk
i understand what you're saying - but im referring to the data displayed by es task manager (having a lot less memory than reported) and also to the fact that after a reboot , or closing all task, the phone does have enough memory to come back to chrome without reloading it .
notice im not complaining about the memory used by chrome, also having more than 500MB of RAM left should be enough anyway no?
also - as far as i know AOSP browser is no longer supported, no?
I've also experienced this on my N5. Sometimes when switching away from chrome and then back again, even briefly, will cause the web page to refresh. This is extremely annoying especially when you're on a internet banking page which will require you to re-login.
daisun said:
I've also experienced this on my N5. Sometimes when switching away from chrome and then back again, even briefly, will cause the web page to refresh. This is extremely annoying especially when you're on a internet banking page which will require you to re-login.
Click to expand...
Click to collapse
this is exactly what im experiencing.
however, since it doesnt happen after restart or killing all apps, it is somehow memory related, but with having 800mb free, i dont really understand the issue :/
Surely the Android devs at google use internet banking, hopefully a fix arrives soon...!
I nerfed chrome as its so messed I cant even use it also drains batter like no tommarow it was always reloading for me to I went to opera it has working word wrap and way less draw on batter.
This has anyways happened to me. Since gal nexus, n4, n5, and n7. /shrug. Maybe it's a nexus thing? I thought this happened on all devices with chrome.
Sent from my Nexus 5 using Tapatalk 2
I've had S4 and N4 and it certainly doesn't happen, at least not from switching away from chrome and back again within a few seconds. But those devices were on Android 4.3.
frigidazzi said:
This has anyways happened to me. Since gal nexus, n4, n5, and n7. /shrug. Maybe it's a nexus thing? I thought this happened on all devices with chrome.
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
It happens on galaxy s3 but that device has 1gb of memory with only 100mb or less available usually . nexus 5 even at its worst state has more than 500MB, so it def. shouldnt happen.
After side loading the 4.4.1 update (got tired of waiting for the ota) the chrome reloading seems to be fixed! I've only done brief testing but it looks promising.

Google Search keeping phone awake?

Google search seems to be keeping my phone awake and destroying my battery.
Using the GEL, my phone was awake any time my launcher was active. Switching to Nova, it seems this issue is mitigated, however if I ever go to use the search app (or Now), it initiates the battery rape-fest.
Just wondering if anyone else has had this issue. I know lots of people here have their data and/or wifi enabled/connected 24/7, so it may not effect them.
I'm linking photos stored in my DB account showing some of these battery drains.
https://www.dropbox.com/s/jhw1f4prbneyg45/2013-12-26 06.19.30.png
https://www.dropbox.com/s/gfhr2vf1z5kf4tw/2013-12-26 06.19.24.png
https://www.dropbox.com/s/0f506skwf26q3se/2013-11-27 01.43.17.png
https://www.dropbox.com/s/ky7yjo2628p1ngl/2013-11-27 01.43.22.png
https://www.dropbox.com/s/dr0e2jjswt52mce/2013-11-27 01.43.26.png
The periods of no signal is when I'm at work - there's no service out here so I might as well have it on airplane mode.
Unfortunately, I really like the GEL, and was hoping that there'd be an easy fix to this. Switching run times doesn't help. I'm currently on ART.
Any advice is helpful.
Do you have hot word detection on? If so then it off that could be triggering it it solved the issue I had with it
Sent from my Nexus 5 using Tapatalk
Once or twice Search would keep my phone awake and drain the battery. Something to do with toggling some Location settings on or off.
Force stopping the application fixed the issue for me each time once I noticed it on my battery list.
bblzd said:
Once or twice Search would keep my phone awake and drain the battery. Something to do with toggling some Location settings on or off.
Force stopping the application fixed the issue for me each time once I noticed it on my battery list.
Click to expand...
Click to collapse
Hmm I also had this problem and also was tinkering with location settings the other night... interesting. If it starts acting up I'll force stop it.
I wanted to disable or uninstall Google Now and Google search and it wiped my homescreen
kevtrysmoddin said:
Do you have hot word detection on? If so then it off that could be triggering it it solved the issue I had with it
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
This was the first thing i thought of. I turned it off, no change.
bblzd said:
Once or twice Search would keep my phone awake and drain the battery. Something to do with toggling some Location settings on or off.
Force stopping the application fixed the issue for me each time once I noticed it on my battery list.
Click to expand...
Click to collapse
My issue is that I shouldn't have to force stop it. Why is it running wild? This is a Google application, shouldn't this be near flawless?
Sent from my Nexus 5 using XDA Premium 4 mobile app
new ion? said:
This was the first thing i thought of. I turned it off, no change.
My issue is that I shouldn't have to force stop it. Why is it running wild? This is a Google application, shouldn't this be near flawless?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just know it's a pretty easy fix (force stop or reboot) so not a huge deal IMO.
If I had to guess Search is trying to look up some location information which it can't currently access. Instead of stopping it just keeps trying forever. I've yet to see the issue since disabling Locations completely and experienced the issue only with partial location services enabled.
My advice would be to leave Location services completely on or completely off. It may effect those with locations on, but either reporting or history (or both) off.
Sent from my Nexus 5 using Tapatalk
Oooo, apparently I had history on and reporting off. I'll try turning both off and letting search run for a bit tomorrow, I'll see what happens. If it comes down to it, I'll submit a bug report.
Sent from my Nexus 5 using Tapatalk
shouldn't be an issue
I have been having the same identical issue as you guys. I have found shockingly little in my searches, which I've been doing periodically for the last few months, really, since I've had the phone(12/5/13).
Now for the particulars :
I have a nexus 5. I'm running the stock ROM and kernel via OTA (4.4.2).
I am rooted (via wugfresh's toolkit) and I have the xposed framework installed along with only a couple of modules, (gravitybox, bootmanager).
Now all this means I am essentially bone stock which means since its a nexus 5 I have the GEL launcher by default and I love it and the setup in general, (my favorite setup so far of all my phones, nexi and other).
Now I've been fortunate and have never really needed to track down and eliminate software causing battery decimating "wakelocks" on any of my devices. And apparently the newer versions of KitKat make finding and solving wake lock issues difficult using apps developed for the purpose.
If I were to upload screenshots of my battery screen when the issue is presenting itself, Google search is up in the top five at least. And when I click it for details it shows similar readouts to what's been posted by OP in his screenshots.
I can't be the only one having serious issues with wakelocks cause by Google search on their nexus 5 and I'm baffled by the lack of discussion I've been able to find regarding this issue, (my google-fu is in my opinion at least up to par)
Whenever I notice my battery draining faster than normal without fail I go into my battery settings and discover that my phone is awake constantly regardless of screen-on time and the culprit is always exclusively Google search. Now its far from difficult to force stop the app and go about my business. And it usually doesn't cause me any issues for a time once that's been done. However, the unpredictability of the Google search app causing a crippling wake lock is for me the main issue as it means I cannot leave my phone unattended for more than a few hours without the possibility of coming back to my phone with my battery that's been molested. The battery in my opinion is more than acceptable and I quite like it. However the uncertainty is horrible.
I've read through the posts In this thread (regrettably few) and I have not been able to make a correlation between location services being on in any of the three modes and Google search wakelocking my ****. Also, I use Google Now all the time every day, and hotword detection is always on to call it up from the home screen by voice which i use even more so. So in my opinion while it is possible I'm sure that somewhere in all that there is a trigger for the issue, it is by no means predictable and in my experience never reproducible.
Now, for the "Google Search" app to cause a wake lock that will persist until the apps been manually force stopped, completely unpredictably represents a HUGE BUG that un-does all of the amazing work with our chipset and kernel and os that gives us such great battery life without having to sacrifice clock speed via custom min/max settings or governor controls.
I just don't get it. This is the first time I've ever encountered such a glaring problem/bug with so little complaint or even discussion.
I think we all should submit official bug- reports to Google about this issue and start being vocal in all of the android communities. I very very rarely comment or post as I am always able to make do by searching and reading diligently. But this blows my mind, the lack of posts and discussion would normally suggest this is a very limited problem affecting a very small minority. But I don't buy that. My set up is too stock, too close to the largest percentage of nexus 5 users to be so. Maybe people are just force stopping the app and forgetting about it, chalking it up to something they've personally done to their phone because "how could Google search be doing this to everyone else". I don't know. But this has to be more widespread of an issue than search results are indicating.
In summation: what OP said lol. But I don't think it has anything to do with what's been suggested by other posters on this thread. Their suggestions may work, and they may mitigate the issue. But if that is the case. Than this a very huge bug that threatens to undo all of the amazing work that's been done with aosp regarding battery efficiency and optimization.
- FerrousState
PS. Let's get some real discussion going in this community and all the others. Smarter people than us should be working on this - Top men guys, TOP MEN!
Hey guys I have this problem as well. I can't view the pics in OP but Google search is running at about 14%
Sent from my Nexus 5 using xda app-developers app
Brockg said:
Hey guys I have this problem as well. I can't view the pics in OP but Google search is running at about 14%
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Tap Google search in your battery and check how long it's kept your phone awake. Then back, and check again. If the seconds just got higher it's currently eating your battery and needs to be force stopped.
Any suggestions are just to mitigate the problem for now of course. Hopefully it's being worked on.
I've yet to see the issue again but I have Locations and Hot Word off, Google Now on. I strongly believe using either "device only" or turning off the 2 settings within Locations can act as a temporary fix however.

[Q] android lollipop keeps killing apps

Every test build, including the final release of lollipop had plagued me with a bug where it continuously oom kills apps, including the bluetooth service, music running in the nackground, navigation while im driving, or even my keyboard while im typing. It doesnt matter if its a background process or in the foreground, it will get killed eventually without any force prompt. I've tried lowering my oom values in 3c toolbox but that hasn't done anything. Anyone else having this problem or have a solution?
Well, I know that feel bro. LOL.
Check my post here for my experience.
b00bs said:
Well, I know that feel bro. LOL.
Check my post here for my experience.
Click to expand...
Click to collapse
I'm getting the exact same issue here. after using it for awhile (about 40 hours), i was getting launcher redraws constantly. I checked memory usage and system was hogging somewhere between 800MB to 1GB. I was reading on a reddit forum that this is due to a memory leak and that it could be a google play services issue and not a lollipop issue? I'm not a developer so really no basis for comment, but i feel you in that the phone definitely does start to get laggy. I'm really hoping google will address this, but in the meantime the fix has been to reboot.
I have the same problem. N5 is almost unusable on Lollipop. I will admit I have a lot of apps but not that many that are always running in the background.
The big annoyances are what OP said: Navigation getting cut off in the background, Music getting killed. I've noticed these two problems being more prominent when BlueTooth is turned on/connected.
makapav said:
I have the same problem. N5 is almost unusable on Lollipop. I will admit I have a lot of apps but not that many that are always running in the background.
The big annoyances are what OP said: Navigation getting cut off in the background, Music getting killed. I've noticed these two problems being more prominent when BlueTooth is turned on/connected.
Click to expand...
Click to collapse
Seriously, music getting killed with device like Nexus 5 is blow my mind.
Yup. Had Power Amp get killed today. Literally the first time I have EVER seen Power Amp killed. Thanks Lolliflop!
Yeah, this is extremely annoying! Have to restart the phone every 12-24h if I want some decent multitasking!
Please star this issue:
https://code.google.com/p/android/issues/detail?id=79729
My Nexus 5 has now become unusable. I can't figure out if it's because of encryption or just shiate multitasking in Lollipop.
<rant> Screw you Google for not having developers that actually use beyond 10 standard apps on their phones in your test group. </rant>
This has nothing to do with encryption .. I don't use this this feature.

Apps Being Unresponsive or Hanging

Hi guys. Everything is great with my v20. The problem is that there are certain apps or games which I use, although fully updated which stop responding after a few hours. There is this one game which I usually leave open to farm on its own on auto. Eventually it stops responding to touches on the screen even if the sprites on the app itself keep moving. It comes up with a notification prompt to close the app, wait for the game to respond, or send feedback I have to reboot the phone to get it to work. Anyone else experiencing this kind of behavior and how did you remedy it. I already tried turning off power saving mode and the game optimizer to no avail.
prinzhernan said:
Hi guys. Everything is great with my v20. The problem is that there are certain apps or games which I use, although fully updated which stop responding after a few hours. There is this one game which I usually leave open to farm on its own on auto. Eventually it stops responding to touches on the screen even if the sprites on the app itself keep moving. It comes up with a notification prompt to close the app, wait for the game to respond, or send feedback I have to reboot the phone to get it to work. Anyone else experiencing this kind of behavior and how did you remedy it. I already tried turning off power saving mode and the game optimizer to no avail.
Click to expand...
Click to collapse
Nothing can be done, you just have to wait for the app to update, although two apps I use xe.com and tsum tsum is having problem it's still usable.
It's a android 7 thing, so it's a waiting game.:fingers-crossed:
Most likely the Android 7 being the culprit, just watch for updates it would seem that there are some changes under the hood that are causing compatibility problems.
Sent from my LG-H901 using XDA-Developers mobile app
Yep. Probably nougat issue or memory leak problem. I'm leaning towards nougat. Luckily I've rarely had the problem.
Thanks guys. I kinda figured out it was a nougat problem since it's not consistent with all apps and just 2 apps in specific.
Sent from my LG-H990 using Tapatalk

Android Auto Problems

Hey guys
I'm having strange problems with Android Auto on Honor 8x.
Sometimes, it works great. The navigation bar shows up, and when I click the audio button, I can see Pocket Casts and Spotify as intended.
However, about 2/3rds of the time, Android Auto doesn't work properly. Either, the bar at the bottom is blank, or my audio apps are not recognized, and pressing the audio button gives the prompt 'Pull over and install android auto apps when it is safe to do so'.
I'm trying to figure out why it works sometimes and other times not, but I can't for the life of me figure it out. I've tried making sure spotify is open before connecting the phone, I've tried making sure it's fully closed, wiping caches of android auto and google apps doesn't seem to make a difference after the initial set up either.
Anyone else?
I'm having exactly the same issue except for me Google play music always appears; just Spotify is sometimes there/sometimes isn't
I initially thought it was a Spotify issue and downloaded Deezer which had exactly the same issue after a few days
I've found sometimes that rebooting the phone works but I've also resorted to reinstalling Spotify at times
I'm just sitting waiting patiently in a hope that it's some "feature" which gets fixed when pie is rolled out, but who knows!
Let us know if you find a fix! ??
I've given up
Mine was just weird full stop! Screen goes weird and kept locking up, half the time 'hey google' wouldn't work amongst other things. I ended up deleting it.
Glad to see it's not only me. It's great when it works, but it's always when I'm about to head out on a long drive that it ****s the bed. The 15 minute journey to town of course, everything's mint..... Having other problems with the phone as well with it's heavy-handed regulation of pretty much everything. No DNS-based or VPN-based adblock can seem to stay alive either. Tried them all! I really hope a decent custom ROM comes out one day, but if not I will probably cut my losses and head back to Moto. Shame really, because it's great value for money and an AOSP version of same hardware would be mint.

Categories

Resources