Related
can automatically stop certain programs from auto-starting? I downloaded the wonderful Elixir 2 program and it showed me (and yes, I know that the OS would have showed as well), that apps like Stocks, First Aid, and Trillian were loaded/running even though I had not started these apps since the last reboot.
Is there a way to stop rogue apps from autostarting?
Why do you need to stop them? What makes you think that they shouldn't start?
???
Well, I am not sure WHY they need to start, but I am sure that they take up memory. "First Aid" is certainly an app that can start up when needed, no need to run in the background. Same for the others.
That said, the original question remains. Anyone know of an app that can adjust the autostart of apps that have no business starting automatically?
Haven't tried it but may be worth a look:
http://www.appbrain.com/app/autorun-manager/com.rs.autorun
Interesting
First - Thank you for responding to the question! I have downloaded and run the app. It certainly professes to do what I was asking. Stopped some apps from loading, but others seem to be more persistent (does Titanium Backup need to run on boot? MyBackupPro? Don't think so). Thank you!
Read the hundreds of posts on task killers. Unless you are having a problem with a particular app, it is best left alone. If the memory being used for the app in question is "needed", android will kill it on its own.
Deleted because I realized I do not need to stoop to respond to nonhelpful posts (but really, people. when is "read random amorphous posts which are not on topic" a response).
only came across 2 apps that run constantly in background vs cached like their supposed to. Fbook and okcupid. autostart managers sorta work but they break functions
In a perfect world, every app on your device would start at boot and reside in RAM. I've never understood this idea that killing apps somehow conserves resources or saves power, because it does neither. In fact, it does the OPPOSITE. For instance, Trillian: Do you REALLY want to kill it whenever you're not using it, only to reopen it the next time you want to use it? That eats about 4 times more power than just leaving it running. NOTHING your cpu does eats more power than reading and writing to NAND. RAM should be as full as possible all of the time with as many apps as are recently or likely to be used. RAM operations consume FAR less power than NAND operations. Unless the app is simply an abusive piece of crap, like Amazon's market and music apps, there's usually a reason for them to run. Titanium Backup never starts unless it's got a reason to, in my experience, such as scheduled auto-backup operations. The better question to ask is why apps are starting at boot, not "Where can I get one more resource-hogging app to whip bad behavior into shape?"
loonatik78 said:
In a perfect world, every app on your device would start at boot and reside in RAM. I've never understood this idea that killing apps somehow conserves resources or saves power, because it does neither. In fact, it does the OPPOSITE. For instance, Trillian: Do you REALLY want to kill it whenever you're not using it, only to reopen it the next time you want to use it? That eats about 4 times more power than just leaving it running. NOTHING your cpu does eats more power than reading and writing to NAND. RAM should be as full as possible all of the time with as many apps as are recently or likely to be used. RAM operations consume FAR less power than NAND operations. Unless the app is simply an abusive piece of crap, like Amazon's market and music apps, there's usually a reason for them to run. Titanium Backup never starts unless it's got a reason to, in my experience, such as scheduled auto-backup operations. The better question to ask is why apps are starting at boot, not "Where can I get one more resource-hogging app to whip bad behavior into shape?"
Click to expand...
Click to collapse
I agree with this 100%.
Yes But
Yes - I get all that, but it bugs the heck out of me that some of these apps feel the need to auto run and worse still, are classified as "self restarter" by the recommended app.
On a cold power-up (I charge with the power off), and without running any apps (in response to the Titanium reference above), the following apps not only started, but restarted when stopped: Appstore, Ebay, Elixir, Mortplayer Audio Book, MyBackup Pro, ROM Manager, Stocks, Titanium Backup, Trillian, Wordsmith, and XDA. Mind you, I am not including apps that SHOULD start up (swype, timeriffic, lookout, etc).
Why any of those apps start on power-on is beyond me, and why almost all of them are set by their respective authors to restart if they are shut down, is even more perplexing. Hence my desire to try to reign them in, especially since they are taking 20MB each of RAM. That's the story
jdmba said:
Yes - I get all that, but it bugs the heck out of me that some of these apps feel the need to auto run and worse still, are classified as "self restarter" by the recommended app.
On a cold power-up (I charge with the power off), and without running any apps (in response to the Titanium reference above), the following apps not only started, but restarted when stopped: Appstore, Ebay, Elixir, Mortplayer Audio Book, MyBackup Pro, ROM Manager, Stocks, Titanium Backup, Trillian, Wordsmith, and XDA. Mind you, I am not including apps that SHOULD start up (swype, timeriffic, lookout, etc).
Why any of those apps start on power-on is beyond me, and why almost all of them are set by their respective authors to restart if they are shut down, is even more perplexing. Hence my desire to try to reign them in, especially since they are taking 20MB each of RAM. That's the story
Click to expand...
Click to collapse
Got me on a few of those, but other ones make all kinds of sense. Any app store sort of app is going to start to authenticate with the service. Amazon is known to do this abusively. The same would probably apply with audio books. MyBackup Pro is probably assuming there's a scheduled function to perform. Stocks is just part of Sense and it doesn't go away. TiBU has never started on any device I've had it on unless 1 of 2 things was the case; I ran the widget or had something scheduled. Trillian SHOULD start up because it's a chat client. If it's not running, it's not much good as a chat client. Not sure what Wordsmith is. XDA will start because it's set by default to sync on a regular basis if you're signed into it.
I don't know what to tell you. You're probably never going to find a way of permanently killing an app connected to a market, and if you do, whatever you use from that market probably won't work right. The best I can say is figure out why those apps you listed do what they do. There's probably a reason that can be fixed or better understood. Some, like Trillian, will self-start no matter what because failure to do so is a MUCH more aggravating issue than the app starting with nothing to do.
only 2 I have that aggravate me is Fbook and okcupid. understandable if both run and autostart for push capabilities but I've disabled sync and push and still runs in background vs cached in background like it's supposed to
dyetheskin said:
only 2 I have that aggravate me is Fbook and okcupid. understandable if both run and autostart for push capabilities but I've disabled sync and push and still runs in background vs cached in background like it's supposed to
Click to expand...
Click to collapse
I don't think Facebook is worried about their app being accused of greatness or winning development awards!
loonatik78 said:
In a perfect world, every app on your device would start at boot and reside in RAM. I've never understood this idea that killing apps somehow conserves resources or saves power, because it does neither. In fact, it does the OPPOSITE. For instance, Trillian: Do you REALLY want to kill it whenever you're not using it, only to reopen it the next time you want to use it? That eats about 4 times more power than just leaving it running. NOTHING your cpu does eats more power than reading and writing to NAND. RAM should be as full as possible all of the time with as many apps as are recently or likely to be used. RAM operations consume FAR less power than NAND operations. Unless the app is simply an abusive piece of crap, like Amazon's market and music apps, there's usually a reason for them to run. Titanium Backup never starts unless it's got a reason to, in my experience, such as scheduled auto-backup operations. The better question to ask is why apps are starting at boot, not "Where can I get one more resource-hogging app to whip bad behavior into shape?"
Click to expand...
Click to collapse
True however some of the apps that are residing in RAM, pop up and do updates and checks that do eat data and cpu than if they were killed. Most apps don't do this and typically it's bad to kill apps because the act of killing it uses CPU and especially the act of that app starting back up uses more CPU.
----
RAM is not an issue so don't even consider it one, even if your RAM is full it doesn't matter. This doesn't run like Windows does where things slow down if you don't have enough RAM.
Most apps that use resources in the background I uninstall, but for others (I think I only do this to 1 app) you can use "autostarts" to disable them from starting upon launch, or stopping them from starting upon other events that may trigger an app to automatically start
https://market.android.com/details?id=com.elsdoerfer.android.autostarts&hl=en
It has much more control over when apps automatically launch than the other app I saw posted on the main page- also it doesn't kill them, just prevents them from starting so it's not like an app killer.
Hope this was what you were looking for.
Let it be
Just let the programs start to let the phone fully awaken
Then kill the apps with any klling apps app task killers and so on
gutiejor said:
Just let the programs start to let the phone fully awaken
Then kill the apps with any klling apps app task killers and so on
Click to expand...
Click to collapse
No. Don't do this.
POQbum said:
True however some of the apps that are residing in RAM, pop up and do updates and checks that do eat data and cpu than if they were killed. Most apps don't do this and typically it's bad to kill apps because the act of killing it uses CPU and especially the act of that app starting back up uses more CPU.
----
RAM is not an issue so don't even consider it one, even if your RAM is full it doesn't matter. This doesn't run like Windows does where things slow down if you don't have enough RAM.
Most apps that use resources in the background I uninstall, but for others (I think I only do this to 1 app) you can use "autostarts" to disable them from starting upon launch, or stopping them from starting upon other events that may trigger an app to automatically start
https://market.android.com/details?id=com.elsdoerfer.android.autostarts&hl=en
It has much more control over when apps automatically launch than the other app I saw posted on the main page- also it doesn't kill them, just prevents them from starting so it's not like an app killer.
Hope this was what you were looking for.
Click to expand...
Click to collapse
I use autostarts also on startup and when I'm running I use auto memory manager both great apps
I have been using Autostarts for a long time now and am very pleased with it.
gutiejor said:
Just let the programs start to let the phone fully awaken
Then kill the apps with any klling apps app task killers and so on
Click to expand...
Click to collapse
I read that this is a bad habit carried over from pre-froyo days where memory management was different and this was recommended then. I don't have a link but trust me and don't just kill stuff like that.
Sent from my ADR6300 using Tapatalk
I have found that my One X often kills apps I have running when I press the power button and put it away for more than a few minutes. I know Android will try to reclaim resources starting with background apps but this is killing the app I am currently looking at.
I have almost nothing else running and my system normally has 200-300 mb of available memory so it is a very unexpected behaviour. A typical example is I have something like firefox displaying a page. I read a bit then press off. I come back 10 minutes later and it needs to restart and reload the page. With previous phones the app would still be in the foreground the next time I turn it on and unless I navigate away it would stay that way.
I have a nexus s running ICS and that does not happen.
I have a desire running GB and is doesn't hapen.
I have a desire running Froyo and it does not happen.
Is there any way to force a less aggressive memory management on HOX?
There is an option for this, in settings > developer options, furthest down under apps section, first one; "Don't keep activities" check if it is enabled.
Sent from my HTC One X using xda premium
.. also beneath it, there is a restriction "Background process limit", it may also cause immediate kills if "no background process" is set
Sent from my HTC One X using xda premium
Thanks for the suggestions but those were set normally.
Tried using the built in browser instead of firefox and the problem was significantly reduced. It seems the system has a bias against non google apps. Even so - this HOX is behaving different in this respect to my other phones. It is my expectation as a user that if I am doing one thing, that thing should still be there the next time I look at my phone.
Something on the device may be leaking and the result is this need to stop stuff. My money is on sense ( mainly because of the observed ripple/flicker on the home screen ).
I've noticed same with my new one x it seems over eager killing all apps even sense launcher.
settings are correct but using chrome I don't dear open anything else for fear of it closing chrome and having to log back into everything, sometimes its as bad as just answering call or replying to a text message and its been killed
just as annoying it even kills launcher if I press home after using an app for more than a few minutes I get the please wait spinner while it has to load launcher
had ICS on desire HD and on zoom tab... this is not how it should work can't believe a phone with more memory and designed to run ICS is having to kill everything when DHD runs perfect
annoying little thing that is so far ruining what is otherwise an amazing phone
Seeing the same issue on my One S.
This happens with Dark Meadow. If the screen times out, or you hit the lock button, the game kind of "crashes". Not sure if this is the One X killing it or whether it's how the app is coded.
It's irritating anyway ><
Applications with a notification icon have not this behavior. Is there a possibility to set a higher priority to applications without root?
I'm having the same problem.
With cm9 @ Desire Z, I could, say, restore my 3000 sms within GoSMS (which takes a while) and meanwhile do whatever I wanted with the phone, eg. browsing, texting and so on.
With the H1X, after a certain time, the apps gets killed/suspended and therefore anything that happened within the app - which is pretty annoying. Any solution in sight?
H1X @ ARHD
I get this too. Annoying.
ViaraiX said:
I've noticed same with my new one x it seems over eager killing all apps even sense launcher.
settings are correct but using chrome I don't dear open anything else for fear of it closing chrome and having to log back into everything, sometimes its as bad as just answering call or replying to a text message and its been killed
just as annoying it even kills launcher if I press home after using an app for more than a few minutes I get the please wait spinner while it has to load launcher
had ICS on desire HD and on zoom tab... this is not how it should work can't believe a phone with more memory and designed to run ICS is having to kill everything when DHD runs perfect
annoying little thing that is so far ruining what is otherwise an amazing phone
Click to expand...
Click to collapse
Sense launcher closing is not cos of the over-aggressive app killing. It's cos the system needs more RAM, so closes Sense since it's not directly in use right now. I do notice that some apps are getting closed after a period of inactivity, probably a default ICS setting that we can tweak when kernels and ROMs get more mature releases
I'm suffering from this defect as well. It's frankly astonishing that this phone behaves in this way. Really makes you wonder if anyone actually uses the phones before releasing such junk. What use is such fantastic hardware if it performs so badly in real use conditions. Every time I press home, loading. Try to run some javascript Web pages then go send a text, then back to browser and all tabs have to refresh. Mine is going back if it doesn't get fixed pretty quickly as it's practically unusable in this state. Battery is unsatisfactory as well. 2 hours on battery, screen on for an hour, 57% left?! What are they thinking seriously
harryshepard said:
I'm suffering from this defect as well. It's frankly astonishing that this phone behaves in this way. Really makes you wonder if anyone actually uses the phones before releasing such junk. What use is such fantastic hardware if it performs so badly in real use conditions. Every time I press home, loading. Try to run some javascript Web pages then go send a text, then back to browser and all tabs have to refresh. Mine is going back if it doesn't get fixed pretty quickly as it's practically unusable in this state. Battery is unsatisfactory as well. 2 hours on battery, screen on for an hour, 57% left?! What are they thinking seriously
Click to expand...
Click to collapse
If your battery is that bad you have a bad app running rampant or your battery is faulty.
For everyone else, even in settings if "Don't keep activities" is unchecked, try checking it and unchecking it. I read that sometimes it is still set to "Don't keep activities" even if it is unchecked and checking and unchecking it could solve the problem if this is the case. Doesn't hurt to try.
Hopefully one of the devs will make a Rom/kernel with better oom adjustments... I'm hoping.
the multitask implementation on this phone is terrible. I was using runkeeper, stopped to check something in my settings during the ride, phone closed the runkeeper application deleting my ride. It is getting annoying ...
From my searching, even on other sites, supposedly this topic has been beaten to death, yet I can't seem to find much about it.
Basically, I would like to keep apps, like Facebook, Email, and Amazon Video, etc., from running until I start them up. Then I would like for them to close, and stay closed, when I'm not using them. In essence, act like a typical app.
All I have been able to find is that you can use a Task Killer to achieve this. But, the average opinion seems to be is that the TKs uses as much, if not more, resources repeatedly killing the constantly restarting apps as just letting the apps "run". Basically, I've yet to find out if it is or isn't possible to keep these apps from constantly restarting on their own.
The reason I want to make these changes is that when my memory gets full, my Fire will lock up, or slow down, for 30 seconds or so... sometimes longer. Supposedly, the O/S is designed to keep as much in memory as possible and it supposedly frees up memory quickly, from apps that you aren't using, when needed. In my experience this is definitely not the case... especially when I click the Task Killer button and my Fire instantly returns back to normal speed... and never did the CPU go above 600Mhz (which is the min I have it set to).... which means it wasn't an issue with the CPU being overloaded.
So does anyone know of a way to keep these persistent apps from being persistent?
BTW, I'm running a pretty standard rooted Fire that I just re-did using the KFU v9.6 and all the "goodies" with it, like the GoLauncher.
TIA
PBFred said:
Supposedly, the O/S is designed to keep as much in memory as possible and it supposedly frees up memory quickly, from apps that you aren't using, when needed. In my experience this is definitely not the case... especially when I click the Task Killer button and my Fire instantly returns back to normal speed...
Click to expand...
Click to collapse
It's true that, under normal circumstances, you shouldn't worry about it. It sounds like your system is simply lacking in memory because it has some high priority tasks eating it all away (Carousel + GO Launcher are probably hogging up a bunch already).
Seeing how you're running rooted Stock with Go Launcher and a bunch of other applications - have you considered switching to Modaco? It's based on Stock...
PBFred said:
So does anyone know of a way to keep these persistent apps from being persistent?
Click to expand...
Click to collapse
To answer this question, other than applying memory scripts, some task killers can be set to autoclose a pre-defined list of apps when you press a widget button - this may interest you. Look into the settings/options of the task killer you're using.
Maybe give this a shot?
https://play.google.com/store/apps/details?id=com.rs.autorun&hl=en
PBFred said:
From my searching, even on other sites, supposedly this topic has been beaten to death, yet I can't seem to find much about it.
Basically, I would like to keep apps, like Facebook, Email, and Amazon Video, etc., from running until I start them up. Then I would like for them to close, and stay closed, when I'm not using them. In essence, act like a typical app.
All I have been able to find is that you can use a Task Killer to achieve this. But, the average opinion seems to be is that the TKs uses as much, if not more, resources repeatedly killing the constantly restarting apps as just letting the apps "run". Basically, I've yet to find out if it is or isn't possible to keep these apps from constantly restarting on their own.
The reason I want to make these changes is that when my memory gets full, my Fire will lock up, or slow down, for 30 seconds or so... sometimes longer. Supposedly, the O/S is designed to keep as much in memory as possible and it supposedly frees up memory quickly, from apps that you aren't using, when needed. In my experience this is definitely not the case... especially when I click the Task Killer button and my Fire instantly returns back to normal speed... and never did the CPU go above 600Mhz (which is the min I have it set to).... which means it wasn't an issue with the CPU being overloaded.
So does anyone know of a way to keep these persistent apps from being persistent?
BTW, I'm running a pretty standard rooted Fire that I just re-did using the KFU v9.6 and all the "goodies" with it, like the GoLauncher.
TIA
Click to expand...
Click to collapse
Just let the OS do what it was designed to do, which is manage the apps and memory automatically. Any interference with that setup will only be a detriment to performance and battery life.
These are not full-featured Operating Systems like what is running on your desktop. Android (and iOS, and even Win8 Metro) automatically manages free memory, running processes, and stopping/starting of apps.
If you try to mess with this, it will cost you battery life and performance as the OS will continue to attempt to maintain it's designed status-quo by restarting apps that you've killed, and reassigning memory that you've freed up.
Task killers are only handy if you have an app that runs away and won't allow itself to be shut down (happens less often with every release/update), and even then, just cycling the device is more than enough to clean that up.
tl;dr Task Killers - Don't.
taskillers worked great in cupcake and donut... Using them In ics is just abusive.
PETA (peeps for ethical treatment of Android)
Sent from my HTC One S using xda premium
AlexDeGruven said:
tl;dr Task Killers - Don't.
Click to expand...
Click to collapse
This may be a dumb question, but I've read that kind of synopsis several times. With the release of ICS however, we have the option of killing previously running apps via the multitasking bar. What's the difference?
BleedsOrangeandBlue said:
This may be a dumb question, but I've read that kind of synopsis several times. With the release of ICS however, we have the option of killing previously running apps via the multitasking bar. What's the difference?
Click to expand...
Click to collapse
It's mostly in the way the OS talks to the task at hand. A Task Killer simply yanks the rug out from under the application in question, whether it's in a safe-to-stop state or not, and disregards any background services an app might be using. In many cases, the OS interprets this as a crash and attempts to get the app back into a 'normal' state.
ICS's task management politely asks (for lack of a better term) the app to stop and take any of its background processes with it. Sometimes, only the very foreground part of the app closes, sometimes the entire application and all services stop. But at the very least, you don't have the constant kill-recycle cycle that occurs with task killers.
ICS's method is much preferred, if not necessarily needed in most cases. I use it as a convenience to keep the list of recent apps clear.
androidcues said:
taskillers worked great in cupcake and donut... Using them In ics is just abusive.
PETA (peeps for ethical treatment of Android)
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
For memory management, yes. For killing wakelock abusers - they still have a reason for existing there.
Mainly Facebook. Facebook STILL holds excessive wakelocks on a regular basis (although it's not as bad as the perma-wakelock it held a year ago), and is the primary reason I keep Advanced Task Killer around.
Never use an autokiller though.
Only use a task killer for managing identified misbehaving apps that you just have to keep around for some reason (like Facebook). Never use a task killer for memory management reasons - only use it on apps that are using excessive background CPU or wakelocks. (usually, apps that are high on the ****list in Settings->Battery.)
There are programs like 'Gemini Task Manager" that will let you edit/modify the automatic startup settings for any particular app. At the very least it will let you see what apps may be causing problems on your device. As far as I know it only edits the startup to keep them from running in the first place rather than constantly killing them when they do like some task managers.
Thanks for all the info. It appears that just leaving it the way it is is what I should do... especially since 95% of what I use the Fire for is for reading books. But I am a Windows/Cisco Sys Eng, so I like to tinker with all my tech devices whenever I can.
That being said, it seems to me that if these "persistent apps" were on a Windows O/S, they would be running as a Service. And if you know Windows, you would know that Services can be set to restart if they are stopped by any means, except through the Service Manager Console itself (or the command line, if you really know Windows). But I have no clue if Linux/Android has the equivalent of Windows Services. I would have to believe that full-fledged versions of Linux/Unix does, but maybe not Android. Just a thought... and maybe it is something people have overlooked when trying to keep these "persistent apps" from being persistent.
Typically, in Windows, you would never ever think of running Facebook as a Service... but you easily could if you wanted to. And it appears that Amazon really wants Facebook, and several other apps, to be running at all times, for no apparent reason.
Oh well, if I had a 2nd Fire, I would "hack" the hell out of it. But since I don't, and I read a lot, I'll just be happy with what I got. And honestly, even after having the Fire since the first day it came out, I'm still loving it.
PBFred said:
Thanks for all the info. It appears that just leaving it the way it is is what I should do... especially since 95% of what I use the Fire for is for reading books. But I am a Windows/Cisco Sys Eng, so I like to tinker with all my tech devices whenever I can.
That being said, it seems to me that if these "persistent apps" were on a Windows O/S, they would be running as a Service. And if you know Windows, you would know that Services can be set to restart if they are stopped by any means, except through the Service Manager Console itself (or the command line, if you really know Windows). But I have no clue if Linux/Android has the equivalent of Windows Services. I would have to believe that full-fledged versions of Linux/Unix does, but maybe not Android. Just a thought... and maybe it is something people have overlooked when trying to keep these "persistent apps" from being persistent.
Typically, in Windows, you would never ever think of running Facebook as a Service... but you easily could if you wanted to. And it appears that Amazon really wants Facebook, and several other apps, to be running at all times, for no apparent reason.
Oh well, if I had a 2nd Fire, I would "hack" the hell out of it. But since I don't, and I read a lot, I'll just be happy with what I got. And honestly, even after having the Fire since the first day it came out, I'm still loving it.
Click to expand...
Click to collapse
It's still completely different system paradigms. In mobile OSes, background services are typically in a paused state when not actively in use, where in full-featured OSes, they can be in any one of several states.
As to the fb service running, that has nothing to do with Amazon. That's just the fb mobile developers not knowing what they're doing.
Sent from my Amazon Kindle Fire using Tapatalk 2
I've been noticing some slight lag in unlocking, the screen coming on, etc on my new Note 4 from time to time. I've found that going in the app switcher thing and clearing all remedies the issue for a bit.
I was curious recently and looked at the RAM usage in that screen and was surprised to see that ~2.1GB of RAM was being used, even after clearing all recent apps.
Is it normal for the thing to be using over 2GB of RAM at all times? This seems very strange to me.
Thoughts?
rmp5s said:
I've been noticing some slight lag in unlocking, the screen coming on, etc on my new Note 4 from time to time. I've found that going in the app switcher thing and clearing all remedies the issue for a bit.
I was curious recently and looked at the RAM usage in that screen and was surprised to see that ~2.1GB of RAM was being used, even after clearing all recent apps.
Is it normal for the thing to be using over 2GB of RAM at all times? This seems very strange to me.
Thoughts?
Click to expand...
Click to collapse
I'm pretty sure its normal because mine is also using 2GB after clearing all. After a reboot, it dropped to 1.6GB before manually launching any application. I'm pretty sure Android is designed this way.
The way android is made and runs, it uses almost all RAM at all times... Basically "unused RAM is wasted RAM." All of our phones have run this way since the time of I'm.
Now, with respect to lag, that's all the bloatware forcing itself to be the main process or close to it. Only way is to fully delete (not only disable) all of them and their underlying processes.
Sent from my SAMSUNG-SM-N910A
greekunit690 said:
The way android is made and runs, it uses almost all RAM at all times... Basically "unused RAM is wasted RAM." All of our phones have run this way since the time of I'm.
Now, with respect to lag, that's all the bloatware forcing itself to be the main process or close to it. Only way is to fully delete (not only disable) all of them and their underlying processes.
Sent from my SAMSUNG-SM-N910A
Click to expand...
Click to collapse
Thanks for the replies, guys. Just waiting on root, then bloatware will be gone.
greekunit690 said:
The way android is made and runs, it uses almost all RAM at all times... Basically "unused RAM is wasted RAM." All of our phones have run this way since the time of I'm.
Now, with respect to lag, that's all the bloatware forcing itself to be the main process or close to it. Only way is to fully delete (not only disable) all of them and their underlying processes.
Sent from my SAMSUNG-SM-N910A
Click to expand...
Click to collapse
Well said..
Only time I have lag on the lockscreen is with a sub par sd card. Once I got rid of that junker the lag went away. Try removing your SD card and see if that fixes the lag.
Hi All,
Anybody here with the same issue ?
Looks like a software issue/touch unresponsive issue because usually I find it coming back to normal once I press power button and unlock it again.
Sounds like RAM allocation issue, isn't ?
Thinking to sell it. Please suggest if you guys know a better way to deal with it !
Even if I go to SC, I cannot reproduce the issue at that particular time. They will just reset it and give me back, and that where I don't want to waste my time.
Does this looks fruitful to flash stock firmware again by the unbrick way ? I feel like that will be me last try.
You seem new here, so welcome on xda
One thing you should keep in mind is to be as precise as possible when presenting an issue, your description right now is not very clear, by the title it sounded like your phone actually froze, which could have been a ram or even a power management issue, but after reading your post it seems more likely that your display was wet, or that you were charging your phone, capacitive touchscreens are sensible to that.
Usually a frozen phone does not respond to the power button like yours did, and a ram issue seems very unlikely tbh
CriGiu said:
You seem new here, so welcome on xda
One thing you should keep in mind is to be as precise as possible when presenting an issue, your description right now is not very clear, by the title it sounded like your phone actually froze, which could have been a ram or even a power management issue, but after reading your post it seems more likely that your display was wet, or that you were charging your phone, capacitive touchscreens are sensible to that.
Usually a frozen phone does not respond to the power button like yours did, and a ram issue seems very unlikely tbh
Click to expand...
Click to collapse
My style of using I believe is the same and I had no such issues in my Cool 1 ever in an year. Was a lot better in every way. Picked it up because I loved the looks, but have lost my trust on Huawei. They really need a lot of improvement.
i am having the same issues as the OP (Although i don't know what he means by "going to the SC")
the phone just goes through moments of extreme lag for about 10-30 seconds, sometimes longer, and it makes the phone COMPLETELY unusable during those times. it happens at least once every other day or so, sometimes several times a day, and sometimes it only lasts about 10 seconds, although on a few occasions, it has lasted several minutes, the phone will "attempt" to respond to inputs, but it gets nowhere quick, opening apps i did not click on, closing apps that weren't open, black-screening, half-screening (app on half the screen), etc.. sometimes i have to just power cycle..
i have the exact same feeling as the OP in that i want to sell the phone. (although i type much better, i'll assume english is a second language for him/her)
i like EMUI a lot.. although i think i want a galaxy s8/s9 now.
BND-L24 HONOR 7X B140 no root
Tirken said:
i am having the same issues as the OP (Although i don't know what he means by "going to the SC")
the phone just goes through moments of extreme lag for about 10-30 seconds, sometimes longer, and it makes the phone COMPLETELY unusable during those times. it happens at least once every other day or so, sometimes several times a day, and sometimes it only lasts about 10 seconds, although on a few occasions, it has lasted several minutes, the phone will "attempt" to respond to inputs, but it gets nowhere quick, opening apps i did not click on, closing apps that weren't open, black-screening, half-screening (app on half the screen), etc.. sometimes i have to just power cycle..
i have the exact same feeling as the OP in that i want to sell the phone. (although i type much better, i'll assume english is a second language for him/her)
i like EMUI a lot.. although i think i want a galaxy s8/s9 now.
BND-L24 HONOR 7X B140 no root
Click to expand...
Click to collapse
Since yours is the us variant, I'm assuming you've got 3 gb of ram instead of 4 gb, in which case a ram issue seems much more likely.
Not much of an issue actually, just that you probably had lots of apps open at the same time, leading to almost full ram (so the system starts closing background and even foreground apps if needed, leading to the strange behaviour you noticed).
Just remember to close apps you don't use and you'll be fine
CriGiu said:
Just remember to close apps you don't use and you'll be fine
Click to expand...
Click to collapse
It's 2018 and I think the OP and I know how smartphones work. I am coming from a phone with 2GB RAM and it has no such issues, no matter how many apps and/or games are open. Google explicitly states that closing background apps is unnecessary, and I should think EMUI offers an improvement over stock Android, not a detrimental experience. However, if you are correct and it is the RAM, it is not acceptable and needs to be fixed or I'm buying a new phone from a different company. In today's world, phones will open links to Chrome and from Chrome open reddit, xda app, pinterest, link to Facebook, share to Twitter, etc etc.. every time I click on a button I should not be having to back track to make sure I only have a certain amount of apps open. Nougat limits max open apps to 20 BTW, marshmallow it was 30.. But RAM management CPU management should be better. If it's of any interest, my reported "free" ram always stays at or above 1-1.5GB so I don't think its ram.. CPU or software problem, possibly.. But my Temps are good as well. Yes it's the 3GB version
Just a quick thought of something you could check (I also have the US 3GB version and was experiencing the same issue). Open up Settings > Battery, and other the "Other" section click "Consumption". See if there's any apps there that are keeping the phone awake and preventing it from sleeping. I would get constant lag after only a few hours of use, and it was intermittent just like you're experiencing. I was about to send the phone back, but checked this setting first. Turns out, the CNN app was running the CPU at nearly 100% for hours on end and preventing the phone from deep sleeping. Once I uninstalled that app, I haven't had issues since then. Could be something similar, just a thought. YMMV.
And by the way, it's NOT the ram. 3GB is plenty. You can see how much is being used on the app select screen, and I've never used more than 1.5 with a ton of apps in the background.
Let me help you there guys....i got the US variant too and has these freezing and lags all over the place, what i discover and did was:
1- Not all the apps works well with the phone hardware(they told me that somewhere) so try to test the apps you put on the phone.
2-Delete all the unnecessary apps from emui, that will give you less lag.
3-Check the battery consuming apps like the guy said and if you want turn on the close apps on screen lock.
Now after all of these my phone have been moving better but the problem isnt the ram, is the software so wait a little more so they can fix this cause is really a good value phone
It has to be the RAM management. Huawei must have optimized the software for 4GB, and then released a US 3GB version without changing anything, so it's screwed up even though phone is showing lots of free RAM.
Wao man thats the best explanation for this problem thanks man
It isn't and never was a RAM thing. Android's memory management essentially force closes apps (but shows them in recents) if it needs more memory. Note there is no work involved in that and you'd never know it until you switch apps and it has to reload, shows logo, etc. Amazing how non-solutions we're brought up multiple times and even thanked. Insert that's-not-how-any-of-this-works meme.
deV14nt said:
It isn't and never was a RAM thing. Android's memory management essentially force closes apps (but shows them in recents) if it needs more memory. Note there is no work involved in that and you'd never know it until you switch apps and it has to reload, shows logo, etc. Amazing how non-solutions we're brought up multiple times and even thanked. Insert that's-not-how-any-of-this-works meme.
Click to expand...
Click to collapse
Well, yeah, ram issues nowadays should not be present, but I do speak on a basis, I have experienced bad performance and foreground apps getting killed on a nexus 5, which has 2 gb of ram and stock android. I have no idea what's emui's ram management policy, but on a scale, this would be the least likely cause for sure