Develop Bugs

stop apps auto starting on boot?

as title really.
some apps i only use every other day auto start. there's no need for it and i have to kill em off.
is there a way yet of preventing them from starting automatically?

tommo123 said:
as title really.
some apps i only use every other day auto start. there's no need for it and i have to kill em off.
is there a way yet of preventing them from starting automatically?
Click to expand...
Click to collapse
Try Autorun Killer, it's in the market
Sent from my HTC Desire using XDA App

Market -> Startup Manager
;-)

be careful though, stopping the wrong things from starting up can bork your phone

tommo123 said:
some apps i only use every other day auto start. there's no need for it and i have to kill em off.
Click to expand...
Click to collapse
Q. Why do you have to kill them off?
Regards,
Dave

they use memory and use the cpu from time to time. for things i only use on occasion it doesn't make sense for them to run all the time.
same with windows, programs add themselves to the startup list. it's pointless if you use those programs only once a week or so

anyhoo, tis working now.
ta all

tommo123 said:
they use memory and use the cpu from time to time. for things i only use on occasion it doesn't make sense for them to run all the time.
Click to expand...
Click to collapse
IMHO, not enough to make any serious difference.
If the apps are not being used, they will consume little to no CPU cycles, and if memory becomes tight the system will automatically kill them off.
same with windows, programs add themselves to the startup list. it's pointless if you use those programs only once a week or so
Click to expand...
Click to collapse
Yes, but the task management on Windows is vastly different to Android, so I don't think you can draw direct any accurate conclusions from the comparison.
My experience with Android stretches back to the US release of the G1 (~ October'08), and so I've been through all of these "performance enhancements" before (autostarts, task killers etc etc) on the G1, and then later the Hero.
In the long term, I've found leaving the system alone to do its own thing improves the experience and I regularly get 30+ hours usage from a single charge (heavy user) and absolutely zero issues with lag - your mileage may vary of course!
Regards,
Dave

i get that, i also (as a bit of a e-control freak) can't stand things running when they have no need to. i have the paypal app, and even though it's something i would probably use every few weeks, runs all the time. it would be more efficient to have power user disallow these from running except when needed. it's annoying really since i want control of what happens on my phone
i did say i was a control freak

my concern is if the app is killing my battery ? I notice even with the task killer , I kill all apps (running ) but it appears again later on the list.
Will Autorun Killer stop the apps completely when not in use ?

[Q] Task Killers/Freeing Memory Question

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

What are the cons of having only 1 app background process at a time?

Answers below....please....
Sent from my SPH-D710

if u go to option on the phone and development u see kill all background or 1 or 2 or 3 etc i choce to close the aplication right after i use cuz i think running in the background kill the battery idk that just me

I would leave it alone
I don't have any evidence supporting my claims so I won't say them but this phone is awesome
No need to play with hose settings
Sent from my SPH-D710 using xda premium

It uses more cpu power to open frequently used apps after you "kill" them rather than leave them running suspended in the background. More cpu usage = faster battery drain.
Sent from my E4GT via CM9

Everything about it is a con. When you close out an app it takes more battery power to reload it from a dead stop than to just continue it from it's previous state. There's no 'gain' by killing it. Sure, you get more RAM but this isn't Windows so having more RAM isn't a necessity. The phone will kill an app as needed when the RAM runs low. Normally when it kills it all it does is cache it so while you have to 'restart' it, the app usually continues from it's previous state. It just takes slightly longer than when it's in the RAM.
Yes, there may be some apps that will continue to run at full speed as opposed to a suspended state but you have to figure out which of your apps do that and kill them accordingly. Most however, do not act like that.
When it comes to Android/Linux you have to take what you know about Windows and scrub it. They are polar opposites on how they handle memory.

Phone freezing twice or thrice a day ! Tried all reset options !

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

aggressive task killer / memory management

I've been using this phone for about 3 weeks, and I've noticed it seems to have a very aggressive low memory killer or a rogue task killer. I haven't installed any task killers or battery savers that should be doing this, so it seems to be system behavior.
If I airplane mode my phone, by the time I reconnect it, it has almost always killed DNS66. I can pause Pandora and just leave the phone laying on my desk. When I come back it will have killed Pandora. The last straw was today when it killed Rocket Player while it was actively playing.
The only device I've ever seen kill an active app only has 1 GB RAM. The last phone I used only had 2 GB RAM and it handled background apps way better than my Nokia 6.1 is.
Has anyone else seen this, or better yet, do you know how to stop it?
I have a TA-1045 running Pie on the Dec 2018 security patch. No root, no mods, no task killers - just bone stock behavior. The only non-Play store app I have is DNS66.

Have a look at
https://dontkillmyapp.com/

runekock said:
Have a look at
https://dontkillmyapp.com/
Click to expand...
Click to collapse
Excellent! Just killed that battery protection app. Can't wait to fire up adb and get rid of it entirely. I can't believe Nokia thought end users would desire this kind of behavior.
If this works out, you just saved me a phone. I was not going to put up with this much longer.

runekock said:
Have a look at
https://dontkillmyapp.com/
Click to expand...
Click to collapse
Well that didn't work. Force closing the battery protection app like suggested in that link didn't change aggressively killing off idle apps. The package manager adb command exits with success, but the battery protection app is still on the phone ruining its memory management.
Have you managed to get this phone to work properly with respect to background apps? Did you make any other modifications or do any other debloating?
Otherwise this is a pretty decent phone. Smooth enough and plenty fast for everything I use it for. The camera is a little sub-par, but no complaints for what I paid for it. Gotta skimp somewhere for a price point that low. However, sometimes it feels like this thing has a mind of its own, and its mostly due to how aggressively it kills off tasks. They aren't even always what I'd call idle, like a paused media player or a DNS server not currently in use. It is really disappointing. This isn't what I expected out of an Android One device.

The Nokia 6.1 belongs to my father, and this problem hasn't bother him, so I haven't tried anything myself.
Maybe you need to be rooted to uninstall the task-killer? But then, I don't know a way to root the phone, either.

runekock said:
The Nokia 6.1 belongs to my father, and this problem hasn't bother him, so I haven't tried anything myself.
Maybe you need to be rooted to uninstall the task-killer? But then, I don't know a way to root the phone, either.
Click to expand...
Click to collapse
You're probably right since it is installed as a system app. It is just odd that the package manager command exits with Success. You'd think it would throw a Permission Denied or Only Root can do that error.