All of my background apps get killed when I turn off the screen. This is particularly annoying for my most-used messaging app, **WhatsApp**. I've looked at the obvious "**Battery Optimization**" option: Based on advice found elsewhere, I've checked that the background process limit in **developer options** is the default (I've never changed this AFAIK): And yet, it gets killed in the same manner as battery optimization would. If I look at running background processes: **Before Poweroff** When I then press the power button, and power it back on after < 10s, the list is the same. But if I wait longer than that: **After Poweroff** ...whatsapp has disappeared. This happens for all apps I install that have some sort of useful background feature - the Battery Optimization setting doesn't seem to do its job anymore. What else can I try to diagnose this? **NB0**: Android 7.0 on DOOGEE S60 **NB1**: This just started happening some time ago, i.e., it _did_ work propertly when I got the phone. **NB2**: I know how to use adb **NB3**: I'm also fond of trying new apps and have ~400 apps installed. Ideally, I don't uninstall/disable _all_ of them 1-by-1 to see which one is the culprit...

I am having Huawei Honor 6X in which if I open any app and minimize it, after 1 minute it automatically closes. For example, I want to download using ADM (Advance Download Manager) where I plan download to automatically start at night, but as soon as I minimize it, it closes. How to fix this?

I’ve got an android mobile phone. It’s a Xiaomi Redmi Note 9 Pro, with MIUI Global 12.0.1 (Android 11). I installed 3 applications for global position background tracing: - OruxMap - Komoot - View Ranger Only for OruxMap, in AppInfo, under the option “App permissions” > “Geolocalization”, I’ve got 4 options: - Allow always - Allow while the app is in use - Ask every time - Deny But **for the other apps I can’t find “Allow always”** and I’ve got only the other 3 options. I compared my situation with two friends with the same 3 apps on their smartphones. One friend never sees “Allow always” option. The other sees “Allow always” option for different applications. In order to grant background geolocalization for tracking purposes to the application of my choice, how can I visualize the “Allow always” option in the App Info for a specific application?

I have a PGD Smartwatch running Android 8.1. Apps like WhatsApp, Telegram, Signal - all of them - kind of turn off after some time and stop receiving messages/calls. When you open them again - they say like you have missed calls. How to keep messenger apps running? I turned off battery saver for those apps completely. What else can I do? Is there a way I can receive messages all the time, like on a phone? Any messenger will work; I need at least one.

I have a Huawei P20 Lite with Android 9, EMUI 9.1.0 and WhatsApp 2.19.253, which is the latest version. As I wrote in the title, I can't receive WhatsApp messages, after many hours of researching I didn't find any solution for my problem. This is the first time I face whit this problem, because I managed and configured variues P20 Lite but none of them gave me that headache. The things which I did: * Turn on every single option for WhatsApp's notifications; * Uninstall the application and install it again; * Remove the app from the battery optimization process; * Clear the cache; * Enabled automatic start, secondary start and running in background, following this steps Settings -> Battery -> app launch -> 3 vertical dots -> manage manually; * No limit for internet traffic and allow background data, following Settings -> networks and wireless -> data usage -> select WhatsApp -> enabled the varius option. Any idea or solution for this problem? EDIT When I send a message from my phone to this P20 Lite, on the message appears only 1 tick, such as the P20 is disconnected from wifi/mobile data, but the wifi is enabled and connected, the same behaviour with mobile data.

* Samsung phone * Android 12 * One UI core 4.1 Whenever I reboot my phone, the camera indicator shows up in the status bar, there’s no camera-related app open in the foreground and I have not enabled background permission to any app (except for system apps which have the option greyed out) When I tap the camera indicator, it shows me that *com.sec.android.app.camerasaver* is using the camera. It happens for an instant. Camera permission for this app is “only while using the app”. What is this package and is this a security issue?

I am talking about services. But some apps run in the background even when you "Close All". Some examples - Parallel Space - Email / Message Apps - Apps with widgets installed I am using Samsung Note 20 with Android 13. Its not rooted and I can't enable developer mode (as some security conscious apps will not run and I need to use them). **Is there a way to look at these and possibly close selected ones?** Asked why I wanted to do this - two reasons - For privacy, for example Parallel space is still running after I have finished using it. - I have almost 400 apps, and the phone gets sluggish unless I can manage them. The included software (Android or Samsung) does a reasonable job putting apps to deep sleep etc., but it doesn't get all of them.

I am running Kali NetHunter on my Android 12 with rootless installation. Every time I connect the KeX client, my Android 12 kills the background Termux. How can I stop it?

Is there an audio app that will play a stereo file in the background, even if I start playing audio in another app? In other words, when I try this using Google play music and Poweramp, Google play will do it but pauses itself when I start a new track in Poweramp. I would like it to continue playing as background to everything I'm doing. Thanks!

Bringing my question over from stack exchange as it was suggested I ask here instead. I'm developing a personal project app (NOT for Play Store) to run on an old pixel phone I have. Here are my requirements 1. On boot, I want to automatically launch my app 2. The app should open a live camera feed and collect images at some interval 3. The app should stay alive indefinitely until a user explicitly kills it 4. All this needs to happen with NO user input Nice to haves, but NOT required 5. The app should be able to function without the screen on Now, I've successfully rooted my device to remove as many hurdles as I can. I got my app to launch on BOOT_COMPLETED, etc. But I'm hitting walls with the camera. I know the camera is not allowed to run in a background service. I was considering trying to force my app to be a system app, but I'm not sure if that let's me use the camera in this way either. The other option is to run the app in the foreground, but that requires a user to explicitly allow it to run continuously or else the OS kills it. But this will potentially trigger and run when I'm away, so I won't be there to hit play. This is all like "spying app 101" stuff so that's probably why Android has put up so many roadblocks. But this isn't for other people. I have complete control of my device and will use it on my own property. I can do whatever custom ROMs people suggest, but I've not worked on any Android OS system code before so I'm hoping not to do that. However, if that's the only way, please let me know if you have any suggestions on where to start. What is best way to achieve my high level goals here? Literally any architecture or strategy to do this is fine so long as it meets my requirements above.

I have a rooted Android 10. And I've written a service which I want to run under too, in background. A service uses a microphone and location. I've not found any information of how to run a service on a rooted device **under root.** I've found some about running some commands in a service under root, though, but it may be only a part of what I need. How to do it? *update #1* * By "service" I mean "a class inherited from Service" * I am not aware about the differencess **in my case** in regards to an init service, a framework service, or just a normal background process. However, I need it to run forever. I guess that it'd be an init service. * It should be be restarted if it fails, or it it gets, for some reason, killed by the system. * It's written in Kotlin. Which is to say, in Java * As I've mentioned, I've rooted my device

I need an **automatic brute-force method** for unrooted Android devices to kill selected apps that keep restarting in the background, i.e. an appropriate "automatic task killer". Ideally, such method entails a kill command running inside an indefinite loop. Two illustrative examples: 1. In Windows, you can run the following batch script from the command prompt: > :start > taskkill /f /im "process_name" > goto start 2. In Linux, you can run the following bash script from the terminal: > while true > do > pkill -f process_name > done What I need is an equivalent for Android, but unfortunately, I do not have any experience with programming Android applications yet. I have tested several "task killer" apps such as [SuperFreezZ](https://f-droid.org/packages/superfreeze.tool.android/) , but you can only terminate processes manually with those. If Android decides to restart a terminated or frozen process against your will, the new instance is not automatically terminated, rendering all these apps useless. Are there any apps out there that can get the job done? If not, is there a simple way to implement a background script for Android and have it run permanently? IMPORTANT NOTE: I do not - I repeat - **I do not** care about CPU/memory/battery usage or any overhead caused by the task-killing app. The sole purpose is to kill selected background apps as soon as they get (re)started, be it by Android or user action. A small app or script that just keeps sending appropriate kill commands every few milliseconds would do the job (hence "brute force"). The assumption here is that one cannot prevent Android from restarting apps in the background without rooting the device, but one can keep force-closing them the moment they are launched. For better motivation, one (out of several) use cases for me is terminating Samsung's infamous [Game Optimizing Service (GOS)](https://arstechnica.com/gadgets/2022/03/samsung-says-app-throttling-is-for-heat-management-will-let-users-disable-it/) , which cannot be uninstalled even via adb as it gets immediately reinstalled (reminiscent to malware). When terminated by the user, it gets restarted after several minutes. An appropriate task killing app would automate the termination process for the user and ensure that GOS is running only for a miniscule fraction of system run time. There are several more reasons for me to desire such solution, which I do not want to get into here as it is irrelevant to the question.

I have a Redmi 10 Pro phone. There is an image of Google Maps that remains permanently behind any image in front, no matter the application. That image is about 90% fade from a normal image. It does not appear on a screenshot action. Restarting or shutting down does not help. Also changing the background image does not help. Any suggestion on how I can erase that image?

I recently bought an Android 13 phone *(Ulefone Armor 24 if that matters)*, and I stumbled upon a problem that oftentimes I stop getting notifications from Telegram about new messages. Judging by my research that might affect other apps. But I don't have any other app whose notifications I heavily rely upon to confirm or disprove that. Further research showed that most of the times when that happens, if I go Settings → Applications → Telegram, I see that the Stop button is grayed out, which implies the Telegram background service got stopped. At first I was blaming Duraspeed, which is default-enabled on this phone and presumably might cause such problems. But after I added Telegram to Duraspeed exceptions nothing changed. So apparently that is not it. Today that problem got repeated, so I tried to peek at system logs with adb logcat, and found this hint:

12-16 03:01:01.577  1458  1489 I ActivityManager: Start proc 27895:com.pri.morning.kill/1000 for service {com.pri.morning.kill/com.pri.morning.kill.service.MorningKillService}
12-16 03:01:01.616  1458  2488 V ActivityManager: New death recipient com.android.server.am.ActivityManagerService$AppDeathRecipient@ffe6c1f for thread android.os.BinderProxy@33fab6c
12-16 03:06:58.537  1458  2790 D CompatibilityChangeReporter: Compat change id reported: 171306433; UID 1000; state: ENABLED
12-16 03:06:58.537  1458  2790 D CompatibilityChangeReporter: Compat change id reported: 218533173; UID 1000; state: ENABLED
12-16 03:06:58.541  1458  2790 V SettingsProvider: packageValueForCallResult, name = null, value : Bundle[{_track_generation=android.util.MemoryIntArray@bd, value=null, _generation_index=3, _generation=825}]
12-16 03:06:58.563  1458  1487 W UsageStatsService: Unexpected activity event reported! (ru.perekrestok.app/ru.perekrestok.app.presentation.MainActivity event : 23 instanceId : 37428045)
12-16 03:06:58.564  1458  2488 D WindowManager: setParent old=Task{a725e80 #844 type=standard A=10182:ru.perekrestok.app U=0 visible=false visibleRequested=false mode=fullscreen translucent=true sz=0},new=null,this window=ActivityRecord{a4602 u0 ru.perekrestok.app/.presentation.MainActivity} t844 f}},callers=com.android.server.wm.WindowContainer.removeChild:772 com.android.server.wm.TaskFragment.removeChild:2592 com.android.server.wm.Task.removeChild:1499 com.android.server.wm.Task.removeChild:1482 com.android.server.wm.WindowContainer.removeImmediately:828 com.android.server.wm.WindowToken.removeImmediately:350
12-16 03:06:58.567  1458  2488 D WindowManager: setParent old=DefaultTaskDisplayArea@84346286,new=null,this window=Task{a725e80 #844 type=standard A=10182:ru.perekrestok.app U=0 visible=false visibleRequested=false mode=fullscreen translucent=true sz=0},callers=com.android.server.wm.WindowContainer.removeChild:772 com.android.server.wm.TaskDisplayArea.removeChildTask:359 com.android.server.wm.TaskDisplayArea.removeChild:350 com.android.server.wm.WindowContainer.removeImmediately:828 com.android.server.wm.TaskFragment.removeImmediately:2672 com.android.server.wm.Task.removeImmediately:2587
12-16 03:06:58.578  1458  1478 I ActivityManager: Killing 23027:ru.letobank.Prometheus:pushservice/u0a184 (adj 920): remove task
12-16 03:06:58.579  1458  1478 I ActivityManager: Killing 22707:ru.letobank.Prometheus/u0a184 (adj 910): remove task
12-16 03:06:58.595  1458  2488 D ActivityManager: Calling pid 27895 killed pid 26945
12-16 03:06:58.601  1458  2488 I ActivityManager: Force stopping org.telegram.messenger appid=10181 user=0: from pid 27895
12-16 03:06:58.602  1458  2488 I ActivityManager: Killing 24470:org.telegram.messenger/u0a181 (adj 700): stop org.telegram.messenger due to from pid 27895
12-16 03:06:58.610  1458  2488 W ActivityTaskManager: Force removing ActivityRecord{8102054 u0 org.telegram.messenger/.DefaultIcon} t846 f}}: app died, no saved state
12-16 03:06:58.611  1458  1487 W UsageStatsService: Unexpected activity event reported! (org.telegram.messenger/org.telegram.ui.LaunchActivity event : 23 instanceId : 221610919)
12-16 03:06:58.613  1458  2488 D WindowManager: setParent old=ActivityRecord{8102054 u0 org.telegram.messenger/.DefaultIcon} t846 f}},new=null,this window=Window{1ea58b4 u0 org.telegram.messenger/org.telegram.messenger.DefaultIcon},callers=com.android.server.wm.WindowContainer.removeChild:772 com.android.server.wm.ActivityRecord.removeChild:4475 com.android.server.wm.ActivityRecord.removeChild:388 com.android.server.wm.WindowContainer.removeImmediately:828 com.android.server.wm.WindowState.removeImmediately:2514 com.android.server.wm.WindowState.removeIfPossible:2704
12-16 03:06:58.617  1458  2488 D WindowManager: setParent old=Task{ded0031 #846 type=standard A=10181:org.telegram.messenger U=0 visible=false visibleRequested=false mode=fullscreen translucent=true sz=0},new=null,this window=ActivityRecord{8102054 u0 org.telegram.messenger/.DefaultIcon} t846 f}},callers=com.android.server.wm.WindowContainer.removeChild:772 com.android.server.wm.TaskFragment.removeChild:2592 com.android.server.wm.Task.removeChild:1499 com.android.server.wm.Task.removeChild:1482 com.android.server.wm.WindowContainer.removeImmediately:828 com.android.server.wm.WindowToken.removeImmediately:350
12-16 03:06:58.620  1458  2488 D WindowManager: setParent old=DefaultTaskDisplayArea@84346286,new=null,this window=Task{ded0031 #846 type=standard A=10181:org.telegram.messenger U=0 visible=false visibleRequested=false mode=fullscreen translucent=true sz=0},callers=com.android.server.wm.WindowContainer.removeChild:772 com.android.server.wm.TaskDisplayArea.removeChildTask:359 com.android.server.wm.TaskDisplayArea.removeChild:350 com.android.server.wm.WindowContainer.removeImmediately:828 com.android.server.wm.TaskFragment.removeImmediately:2672 com.android.server.wm.Task.removeImmediately:2587
12-16 03:06:58.625  1458  2488 I ActivityManager:   Force stopping service ServiceRecord{ec3cd7a u0 org.telegram.messenger/.NotificationRepeat}

So apparently some MorningKillService appears and just kills everything on left and right. And there is no matches on the internet for that word ATM. Any idea what is this about?

On Android 11, I am able to run text-generation-ui under Termux, with 3b models. I've got a Samsung A53 phone, with 6GB RAM & 2GB swap (by default). However, on Android 13, I'm currently running LineageOS 20 GSI (Android 13), installed over stock Android 12. (with some custom kernel from Andi Yan), the OS is killing Termux processes. When I start server.py, it goes just "killed" with no messages at all. In the developer options, I've turned off the feature flags monitor_phantom_procs. I also ran these commands in adb: 1. adb shell /system/bin/device_config set_sync_disabled_for_tests persistent 2. /system/bin/device_config put activity_manager max_phantom_processes 2147483647 What can I do to stop the OS from killing procs?

I can't find a clear answer as to what "Lock app" on the recent apps list actually does, other than prevent apps from being killed or swiped away from the recent apps list. Does it also prevent an app from being killed by Android? I.e. if I lock an app, will it be running indefinitely in the background, no matter what? Or could it still be killed by Android, just not by using "Clear all" on the recent apps list?

I have a non-rooted phone. I just realized why Android is bad at memory management. I'm monitoring running progress in ADB shell with top. I can see the memory is about 100% used. Image resized. Click for full-size How do I stop unnecessary processes with ADB shell? Also, I can't scroll down top command. It shows weird char ^[[b. I think that's because the shell uses sh instead of bash. Any idea how to free up memory with ADB? Maybe pkill or what.

I like Samsung's power saving option "Limit apps and home screen", but 4 apps is just not enough. As a result, some apps shut off when you close which I would like to keep running. Can you add more than 4 apps to the set of apps that are allowed to run in the background somehow?

I have an old (but rooted) phone running Android 5.1.1 (Lollipop). I realized it runs many background processes which I absolutely don't need. I can stop them manually via Settings > Apps > Background processes, however I wish to keep them disabled: they slow down the cold-start of the phone which I don't like. So I'm looking for a way to not just disable but completely ban certain processes (i.e. ban them from starting). How can I do this on these old versions of Android? Unfortunately Google is quite blurry and noisy for these search terms.

I installed some alarms, then I configured them... then I configured the phone settings the standard wake signal for a long music. I ended up that something is playing music in my ear, in the background, and I have no way to know, which app is doing it.