Skip to content

[Bug] Container process gets killed in background even with battery optimization disabled #608

Description

@arinadi

Device Model

One UI 8.5

Operating System Version

16

Tiny Container Version

XFCE & GXDE

Is this the latest version?

Yes

If not using the latest version, you must explain the reason for not using the latest version

No response

Steps to reproduce the issue

First, thanks for this project — performance and stability in the foreground are genuinely the best I've tried among the proot-based Android launchers.

Issue: the container's process stops once the screen turns off, even after granting "ignore battery optimizations" for the app in Android settings. I've matched the settings as closely as I could to what Termux itself uses (which does survive screen-off), but the container still stops.

Environment:

Device: Samsung Galaxy S24 FE
Android version: 16 (One UI 8.5)
Battery optimization: disabled for the app (confirmed in Android Settings)
What I looked at (I'm not an Android developer, so please correct me if I've misread this — just sharing what I found):

AndroidManifest.xml doesn't appear to declare any component.
I couldn't find any WakeLock/PowerManager usage in the app's source.
By comparison, Termux itself stays alive in the background via a foreground service + PARTIAL_WAKE_LOCK (e.g. through termux-wake-lock).
My understanding (possibly wrong) is that "ignore battery optimizations" only stops proactive Doze throttling, but doesn't by itself keep a process alive under memory pressure — that normally needs a foreground service (with a persistent notification) and/or an explicit wake lock. Since I don't see either here, it would explain why the container process is reclaimed once the screen is off, independent of the battery-optimization setting.

Question: is this a known/intentional tradeoff (e.g. to avoid a persistent notification, or Play Store foreground-service policy concerns), or would a foreground-service + wake-lock option be something you'd consider? Happy to test a build on my device if you want to try something, though I can't contribute the Android-side implementation myself.

Thanks again for the great work!

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions