TECHNICAL DOCUMENT

Huawei App Launch Management and Why It Stops Parental Control Apps

You set a 60-minute limit. Your child watched for 90. Nothing warned, nothing blocked. Then you opened the app to see what went wrong — and the number quietly caught up while you were looking at it.

That last detail is the tell. If the count only moves when you open the app, the app wasn’t wrong about the limit. It wasn’t running.

On Huawei phones this usually comes down to one setting called App launch, and to the fact that it is a completely different switch from the battery whitelist most setup guides walk you through. You can do the battery step perfectly and still have this problem.

This page is the Huawei-specific detail. The general version, covering eight brands, is why battery optimization keeps closing your parental control app.

The thirty-second version

There are two switches, not one. Battery optimization and App launch are separate. Huawei’s own support pages list them as two different steps for the same app.
App launch defaults to “Manage automatically”, which lets the system decide whether your app may start and keep running.
You want “Manage manually”, with all three switches on: Auto-launch, Secondary launch, Run in background.
The menu path depends on your version, and Huawei’s pages give several. Searching Settings for App launch is the most reliable route.
Check it afterwards. There’s a two-minute test below that doesn’t need any technical tools.

Two switches, not one

This is the whole point of the page, so it’s worth showing that it isn’t my opinion.

Huawei’s own support article for keeping an app running lists these as separate numbered steps:

Go to Phone Manager → App launch → Manage manually and turn on the switches for Auto-launch, Secondary launch, and Run in background.
Separately: open Settings, search for Battery optimization, tap the dropdown at the top left, select All apps, tap the app, and enable Don’t allow.

Two steps, two places, one app. Doing the second one — the battery whitelist — is what nearly every “keep my app alive” guide tells you to do, and it’s what our own setup flow used to walk parents through. It is genuinely necessary. It is also, on its own, not enough.

To be precise about how far this generalizes: Huawei documents these as two distinct steps that both need doing. What our own testing adds is a phone where every setting on the Android side looked correct — on the battery exemption list, standby bucket exempt, background execution unrestricted — and the monitoring service still stopped getting CPU time. Android’s APIs don’t report the state of Huawei’s App launch setting, so no app can check that switch and warn you it’s wrong. Which is why you’re reading a page about it instead of seeing a warning in an app.

What “Manage automatically” actually does

Huawei’s pages describe App launch in terms of three permissions: whether an app may launch itself, whether other apps may launch it, and whether it may run in the background. Leaving it on Manage automatically hands those decisions to the system.

On stock Android, a long-running app is normally protected by running a foreground service — the thing that puts a permanent notification in your tray. Google’s own documentation for Android’s app freezer says apps with visible activities or foreground services stay unfrozen. That’s the behavior a screen-time app is built to rely on.

What we measured on a Huawei device is that this protection did not hold. On a GFY-AL00 running EMUI 14.2 (Android 12), with App launch left on the default automatic setting, our monitoring service accumulated essentially no CPU time while a video app sat in the foreground — the process was still there, it just wasn’t running. Switching that one setting to Manage manually changed the same measurement to roughly 45 seconds of CPU time over three minutes, and the app’s remaining-minutes counter started dropping in real time again.

Two honest caveats on that measurement. It is one phone, one ROM version, one test — I’m reporting what we saw on the device we have, not a law about all Huawei phones. And this behavior isn’t misconduct on Huawei’s part: aggressive background management is a large part of why these phones get the battery life they do. The tradeoff is that apps you want running in the background need to be told apart from the ones you don’t, and that’s the switch you’re about to set.

How to change it

Huawei has moved and renamed this feature across EMUI and HarmonyOS versions, and its support pages genuinely disagree with each other about where it lives. Rather than print one path and hope it matches your phone, here’s the version-independent instruction, which comes straight from Huawei’s own wording:

Open Settings, search for App launch, and turn off Manage automatically for the app. In the dialog that appears, turn on Auto-launch, Secondary launch, and Run in background.

If you’d rather navigate than search, these are the paths Huawei documents, with the versions its pages state:

Path	Version stated on Huawei’s page
Phone Manager → App launch → Manage manually	EMUI 9.0 or later
Optimizer → App launch	HarmonyOS 2.0, Android 9.0 or later
Settings → Apps & services → App launch	HarmonyOS 2.0 (this one appears only on Huawei’s Chinese page; I found no English page that states it)
Settings → Launch manager	none stated
Settings → Apps & services → Apps → [app] → Power usage details → Launch settings	stated as unrelated to OS version

One correction worth making, because it’s repeated almost everywhere: Settings → Battery → App launch is the path most third-party guides give, and I could not find it on any official Huawei page. It may well work on your phone. It just isn’t Huawei’s own documented wording, so I’m not going to present it as such.

Then do the battery step too, since it’s the other half:

Settings → search Battery optimization → dropdown at top left → All apps → the app → Don’t allow.

Huawei documents two further steps, and both are worth doing. On the same Chinese page as the battery step above, there’s a third one: open Recent tasks and swipe down on the app’s card to lock it — those three are given as a set on that page. And on Huawei’s English battery-settings page there’s More battery settings → Stay connected while asleep, worth turning on for an app that needs to keep watching overnight.

How to check whether it worked

This is the part most guides skip, and skipping it is how people end up doing five settings and still not knowing if any of them helped. You don’t need any tools for this.

Note the remaining minutes your screen-time app shows.
Open whatever app your child actually uses — the video app, the game — and leave it in the foreground for three minutes. Don’t switch back and forth. Don’t open the screen-time app.
Now switch back and look at the remaining minutes.

It’s working if the number has gone down by about three minutes, and it was already correct the instant you looked.

It’s still being stopped if the number is unchanged, or if you can watch it jump to catch up a second or two after you open the app. That catch-up jump means the app wasn’t counting while your child was watching; it worked out afterwards what it had missed. A good screen-time app will backfill that gap so your child doesn’t get free minutes out of it — but backfilling is not the same as blocking at the right moment, and a limit that enforces itself ten minutes late is the problem you came here to solve.

If it’s still being stopped after setting App launch to manual, the next things to check are the battery optimization step above, and whether the app was ever force-stopped (see below).

What this does not fix

Three limits, stated plainly.

Force-stop is final. If anyone opens Settings, finds the app and taps Force stop, no app can bring itself back. This is Android working as designed, not a gap in any particular app: Google documents that a force-stopped app stays in that state until the user explicitly launches it again, and that it won’t even receive the “device finished booting” signal until then. On Android 15 the system additionally cancels the app’s pending alarms and greys out its widgets. There is no third-party workaround, and you should be suspicious of any app claiming otherwise — including, I’ll note, an older version of our own help page, which claimed the app restarts itself after a force-stop. It doesn’t. Nothing does.

Setting App launch correctly is not a guarantee. It reliably improved things on the device we tested. Aggressive power management varies by model, ROM version and regional build, and there is no setting that makes an Android app un-killable.

Apps can’t take you straight to this page, and can’t read it. If you’ve wondered why screen-time apps give you written steps for Huawei instead of a button that jumps you there, this is why. We tried both ways. Opening the App launch screen directly by name throws a security error, because the target requires a Huawei signature-level permission that only Huawei’s own system apps hold. Going in through the general intent lands on a chooser dialog that is empty, because the system filters the candidates by the caller’s permissions and filters all of them out. That’s on a GFY-AL00 running EMUI 14.2, tested twice. So the honest best a third-party app can do is send you to its own app details page and show you the written steps — which is why a page like this one has to exist at all.

Why battery optimization keeps closing your parental control app on Android — the same problem across eight brands, plus what Android itself does
How to keep the app from being killed by battery saver — the shorter setup-oriented version
How to make Android warn your child before screen time ends — once it’s running reliably, this is the next thing parents ask

Written by a parent who builds Tortoise Time, an Android screen-time app for kids aged 6 to 14. It nudges quietly at 60%, 75%, and 90% of the daily limit before blocking anything at 100%. It’s free, with no ads and no in-app purchases. Your child’s screen-time data stays on the phone by default — the only things that leave the device are anonymous crash reports and usage statistics, as our privacy policy says.

Sources

Retrieval level noted for each, because it changes how much weight the claim can carry.

“How Do I Keep an App Running in the Background.” Huawei Consumer Support, global English. (Full page retrieved twice for exact wording. Source for Phone Manager → App launch → Manage manually, the three switches Auto-launch / Secondary launch / Run in background, the EMUI 9.0-or-later scope, and the separate Battery optimization → All apps → Don’t allow step. This is the page that establishes the two switches as distinct steps.)
“Setting App Launch.” Huawei Consumer Support, global English. (Full page retrieved twice. Source for the search-based instruction — open Settings, search App launch, disable Manage automatically — and corroborates the three switch names. No OS version stated.)
“Launch manager.” Huawei Consumer Support, global English. (Full page retrieved twice. Uses the name Launch manager rather than App launch, with automatic and manual management. No OS version stated.)
“Protected background apps.” Huawei Consumer Support, global English. (Single retrieval. Source for the Optimizer → App launch path and the HarmonyOS 2.0 / Android 9.0-or-later scope. Note it describes “protected background apps” descriptively; the old Protected apps menu item from earlier EMUI versions is not documented as a current feature name.)
“Power usage details.” Huawei Consumer Support, UK. (Full page retrieved twice. Source for the Settings → Apps & services → Apps → [app] → Power usage details → Launch settings path, stated as unrelated to OS version.)
“Battery settings.” Huawei Consumer Support, global English. (Single retrieval. Source for More battery settings → Stay connected while asleep.)
“Cached apps freezer.” Android Open Source Project. (Full page retrieved. Source for the statement that apps with visible activities or foreground services stay unfrozen on stock Android.)
“Behavior changes: all apps” (Android 15). Android Developers. (Full page retrieved. Source for the force-stopped state persisting until the user explicitly launches the app, the boot-completed behavior, and Android 15 cancelling pending intents and disabling widgets.)
Our own device testing, Huawei GFY-AL00, EMUI 14.2, Android 12. (CPU-time comparison for the monitoring service before and after switching App launch to manual — approximately zero versus roughly 45 seconds over three minutes, alongside the remaining-minutes counter resuming real-time updates. Also the two failed deep-link approaches: security exception on the direct component, empty chooser on the general intent, reproduced twice. One device, one ROM version — reported as an observation, not as brand-wide behavior.)
dontkillmyapp.com/huawei. (Community-maintained, not official Huawei documentation. Referenced here only to note that the widely repeated Settings → Battery → App launch path originates outside Huawei’s own pages. Useful, but not a citable source for Huawei’s wording.)

Not verified: the Settings → Battery → App launch path; Power-intensive prompt as current official Huawei wording; Protected apps as a current menu item. The English equivalent of the HarmonyOS Chinese path Settings → Apps & services → App launch is a reasonable inference but appears on no English Huawei page I could retrieve.