I am using rooted Honor 8 b389 with Magisk 18.1.
I am not able to disable the foreground and background data of Android OS which is system app. All other apps including system app I can do that.
Can anybody disable that, because this Android OS is using background data when I am in mobile network and I don't have the bandwidth.
I tried a lot a thinks but seems like the Android OS and the Messaging services are white listed to run in background from Huawei. And there is no way to disable them doesn't matter which firewall you're using.
Maybe that's with every devices from Huawei doesn't matter from the build version. Everything is about privacy in this days
Unfortunately I wasn't able to restrict that with the netpolicy.xml Somethig which was working with other devices.
If there is no interest in this topic I will closed in few days.
Simply you can't disable it 'cause it is the core system of Android and it is forced white listed as I know
Related
I had given my old Android 2.3 phone and a fairly new Android 4.4 tablet to my kid.
Within about a month, both devices basically became non-functional on start up.
After some analysis, it became clear that all the games and recreational apps my kid installed was causing the problem: they were all built to auto-start on device boot up, and they lacked an option to tell them not to auto-start on device boot up.
Since both devices were rooted, I used a tool (Clean Master) that quickly identified the auto-start apps and stopped them from auto-starting.
My question is this:
Why would an app developer build an app that auto-starts with no option to disable that? Many auto start apps will just kill the usability of the device, and it isn't trivial finding out why.
If the device was not rooted, there's probably no way to stop these apps except to uninstall them. If Android allows a third-party app on a non-rooted device to auto-start, why isn't there an app that works on non-rooted devices to stop these apps from auto-starting?
Nate2 said:
I had given my old Android 2.3 phone and a fairly new Android 4.4 tablet to my kid.
Within about a month, both devices basically became non-functional on start up.
After some analysis, it became clear that all the games and recreational apps my kid installed was causing the problem: they were all built to auto-start on device boot up, and they lacked an option to tell them not to auto-start on device boot up.
Since both devices were rooted, I used a tool (Clean Master) that quickly identified the auto-start apps and stopped them from auto-starting.
My question is this:
Why would an app developer build an app that auto-starts with no option to disable that? Many auto start apps will just kill the usability of the device, and it isn't trivial finding out why.
If the device was not rooted, there's probably no way to stop these apps except to uninstall them. If Android allows a third-party app on a non-rooted device to auto-start, why isn't there an app that works on non-rooted devices to stop these apps from auto-starting?
Click to expand...
Click to collapse
Actually, there were non-root apps that could disable auto-start of other normal apps till JellyBean 4.2 I guess.
Then came the security enforcements which prevented this for non-root users.
Android assumes that an app necessarily needs auto-starting at boot for the smooth working of the app.
There's a reason behind that.
For example, if you disable auto start of FB messenger or WhatsApp, you won't automatically get notifications unless you open it one time so that certain services begin to run in background.
The same goes for your kid's apps like Talking Tom, which gives essential notifications (from a kid's point of view) like "I'm Hungry" or "I wanna pee" or something like that
But you have non-root apps too (you gotta dig a lil deeper to find them) which doesn't work like root apps, that is, doesn't disable them to start at boot. Instead, they stop the apps/services after booting that's disabled in that app.
Apps like CC Cleaner or the so-called antivirus apps work that way only
Until recently I used to be able to use Android Assistant to kill un-needed apps and so free up memory (and also preserve battery life, help phone run cooler, etc.). But recently -- not sure if it was after the OS update on the Idol 3 (6045I) or an update of Android Assistant itself -- the only process shown under the Processes tab is Android Assistant itself, so there is nothing to kill. The "quick boost" feature, which formerly seemed to close the same bunch of apps I would see listed under "Processes", now also seems to do nothing. I am thinking this is likely something to do with the phone's OS, as an app cleaner built into the 3rd-party launcher I'm using has a similarly changed behavior.
Anyone else observing this, and/or know of a solution that works, and/or know what might have changed with the most recent software update?
rhcohen said:
Until recently I used to be able to use Android Assistant to kill un-needed apps and so free up memory (and also preserve battery life, help phone run cooler, etc.). But recently -- not sure if it was after the OS update on the Idol 3 (6045I) or an update of Android Assistant itself -- the only process shown under the Processes tab is Android Assistant itself, so there is nothing to kill. The "quick boost" feature, which formerly seemed to close the same bunch of apps I would see listed under "Processes", now also seems to do nothing. I am thinking this is likely something to do with the phone's OS, as an app cleaner built into the 3rd-party launcher I'm using has a similarly changed behavior.
Anyone else observing this, and/or know of a solution that works, and/or know what might have changed with the most recent software update?
Click to expand...
Click to collapse
Google made some changes with the stagefright patch that prevents apps from getting certain info. Some developers have updated their apps with workarounds.
After upgrading my HTC One M9+ to Android 6 a year ago or so, two apps, SMS Backup+ and FolderSync, that I have been using since Android 2.1 no longer work in the background. Instead I have to manually launch them from time to let them perform their tasks (backing up SMS and syncing a couple of folders to Google Drive).
Does anyone know why?
Try older version. Some times your new android have background apps management option. Look your android setting and inbuilt apps
Sent from my SHV-E210S using Tapatalk
[email protected] said:
Try older version. Some times your new android have background apps management option. Look your android setting and inbuilt apps
Click to expand...
Click to collapse
I use the same version as the one that worked on Android 5. I have enabled all background options I have been able to found. Other apps, like Facebook, still updates in the background.
Hey guys, is there any efficient app which really closes any app - or avoid them to boot during the startup of the smartphone?
For example, Booking.com or Instagram — I absolutely don't need any notifications from them, and I want to keep those apps absolutely closed. Even the native "restricted background activity" on Android 12 seems not to be working, nor Servicely / Naptime / Greenify (I have root).
Any other suggestions?
Thanks
pulseg11 said:
Hey guys, is there any efficient app which really closes any app - or avoid them to boot during the startup of the smartphone?
For example, Booking.com or Instagram — I absolutely don't need any notifications from them, and I want to keep those apps absolutely closed. Even the native "restricted background activity" on Android 12 seems not to be working, nor Servicely / Naptime / Greenify (I have root).
Any other suggestions?
Thanks
Click to expand...
Click to collapse
So basically a startup manager. That would be pretty nifty.
Best I can suggest is disable notifications on those apps; with notifications disabled, I think Android system doesn't allow the processes to keep running. I could be wrong.
There's also some Developer Options that help reduce what you have running at any given time, although they're more of a global policy and not app specific.
V0latyle said:
So basically a startup manager. That would be pretty nifty.
Best I can suggest is disable notifications on those apps; with notifications disabled, I think Android system doesn't allow the processes to keep running. I could be wrong.
There's also some Developer Options that help reduce what you have running at any given time, although they're more of a global policy and not app specific.
Click to expand...
Click to collapse
Yep — I've disabled the notifications already of Instagram, but still appears to be having some background activity.
Startup manager - yeah, do you know any to suggest?
pulseg11 said:
Yep — I've disabled the notifications already of Instagram, but still appears to be having some background activity.
Startup manager - yeah, do you know any to suggest?
Click to expand...
Click to collapse
I mean, there's dozens of task managers out there, but honestly they're not really worth the trouble and don't do anything significant for battery life. With the exception of Magisk and a systemless ad blocker, I'm pretty much bone stock on my Pixel 5 with no management apps whatsoever, and I could probably go 2 days on standby.
pulseg11 said:
Yep — I've disabled the notifications already of Instagram, but still appears to be having some background activity.
Startup manager - yeah, do you know any to suggest?
Click to expand...
Click to collapse
you can disable it with app2sd pro , luckypatcher , my android tool , terminal .
@pulseg11
look inside here:
How do I stop apps from auto-starting on Android
With the ever-increasing size of apps, there’s a chance that you might be finding it hard to use your phone as these apps tend to hogs your phone memory as well as its battery. Not only do yo…
nerdschalk.com
On OOS 11 and 12 when I force close any app, it stays closed all the time. I have one or two apps that I don't need to run all the time, just from time to time, so I force them close usually.
But now I'm on OOS 13 and when I force close app it's re-run after some time. It looks like android "revives" app. And this app has unchecked "backgroud activity" and "auto lunch" of course.
Is this a new "feature" of android 13? Or OOS maybe?
The new "feature" you've said is actually "something normal all the time" form Android 4.0 +. This is something you can have on AOSP. What you want is actually something "dirty" made by the device manufacturer, which is a nightmare for Android developers. Those manufacturers don't follow the Android standard and prevent the software to be triggered under some circumstances, this breaks the functionality of the app.
For example, using the Android WorkManager can register a worker with a scheduled task. Developers can assign the task to be executed at a specific time or every a period of time. The WorkManager is a wrapper for Jobscheduler and AlarmManager. Depending on the Android OS version, the WorkManager automatically choose to use one of the above methods to run the scheduled task. If an app registers a PeriodicWorkRequest and assign it to execute every 2 hours, even the app is closed, the PeriodicWorkRequest still can be triggered and revives the app every 2 hours. The nightmare for developers is that OPPO, Xiaomi...etc, these manufacturers prevent the scheduled tasks to be executed if the app is closed(Hall of shame). They are not following the Android standard, so apps can not behave as expected. It is totally different from the documentation at developer.android.com, but every manufacturer is doing this under the excuse of battery optimization, so many users think this is normal. However this is actually some nasty customization to the OS made by the manufacturer to break many apps on the device. That's why apps with background services, such as, Tasker, Bitwarden can not work correctly on many devices if they're not excluded in battery optimization management apps made by the manufacturer.
Almost every Android developer has to tell users to visit https://dontkillmyapp.com/, because Chinese manufacturers like to kill app services and break all the apps with background services. And finally now Google is introducing CTS-D, to tell devs about how background services work on the device. I guess this is why things are finally moving back to normal in Android 13.
#The page https://dontkillmyapp.com/ is a website made by developers to teach users to whitelist apps after receiving a lot of complaints about apps not working correctly. Thanks to those manufactures created this mess.
evilhawk00 said:
The new "feature" you've said is actually "something normal all the time" form Android 4.0 +. This is something you can have on AOSP. What you want is actually something "dirty" made by the device manufacturer, which is a nightmare for Android developers. Those manufacturers don't follow the Android standard and prevent the software to be triggered under some circumstances, this breaks the functionality of the app.
For example, using the Android WorkManager can register a worker with a scheduled task. Developers can assign the task to be executed at a specific time or every a period of time. The WorkManager is a wrapper for Jobscheduler and AlarmManager. Depending on the Android OS version, the WorkManager automatically choose to use one of the above methods to run the scheduled task. If an app registers a PeriodicWorkRequest and assign it to execute every 2 hours, even the app is closed, the PeriodicWorkRequest still can be triggered and revives the app every 2 hours. The nightmare for developers is that OPPO, Xiaomi...etc, these manufacturers prevent the scheduled tasks to be executed if the app is closed(Hall of shame). They are not following the Android standard, so apps can not behave as expected. It is totally different from the documentation at developer.android.com, but every manufacturer is doing this under the excuse of battery optimization, so many users think this is normal. However this is actually some nasty customization to the OS made by the manufacturer to break many apps on the device. That's why apps with background services, such as, Tasker, Bitwarden can not work correctly on many devices if they're not excluded in battery optimization management apps made by the manufacturer.
Almost every Android developer has to tell users to visit https://dontkillmyapp.com/, because Chinese manufacturers like to kill app services and break all the apps with background services. And finally now Google is introducing CTS-D, to tell devs about how background services work on the device. I guess this is why things are finally moving back to normal in Android 13.
#The page https://dontkillmyapp.com/ is a website made by developers to teach users to whitelist apps after receiving a lot of complaints about apps not working correctly. Thanks to those manufactures created this mess.
Click to expand...
Click to collapse
I think the point rufik made is the opposite. It's not about android autokilling app.
Instead when he force closes the app, it starts again.
Check that Auto launch isn't enabled for the app. Settings>Apps>Auto launch
Rootk1t said:
I think the point rufik made is the opposite. It's not about android autokilling app.
Instead when he force closes the app, it starts again.
Click to expand...
Click to collapse
No, you don't understand my point. I'm talking about this under the view of an app developer. I mean auto killing app also has a feature that prevents Jobscheduler to be called.
What I meant:
Due to no app auto killing => system not preventing Jobscheduler to be executed after app force close => Jobscheduler executed after force close app(Jobscheduler task was created before force close app, and Jobscheduler is not the part of app, so it is not forced closed, it still execute, it should be cancelled by the app itself) => Jobscheduler task call codes from the app => the app starts itself.
More info : https://stackoverflow.com/a/63226260
With Jobscheduler, you can make a app to restart itself after forced close on AOSP. But this trick never works on manufacturer customized Roms with app auto killing feature.