[BUG] : Bypass app restrictions

[KishkaCat]

Description

A short summary of what is not working as expected.

The running background apps can be used to force stop the app and bypass restrictions.

Steps to Reproduce

Google Pixels:

1. Open Zenith (to start service).
2. Enable bedtime and have it go until a few hours after the current time(or make it day round).
3. Go to system notification menu.
4. Click the bubble that says "(i) x apps are active >" where "x" is a number or it may be a small circle that has a number in it.
5. Click the button that says "Stop" next to Zenith.
6. Try to open and interact with an app that you have configured to be blocked during bedtime.

Samsung devices:

1. Open Zenith (to start service).
2. Enable bedtime and have it go until a few hours after the current time(or make it day round).
3. Go to the open the overview or recent apps screen.
4. Click the bubble that says "x active app[s]" where "x" is a number.
5. Click the button that says "Stop" next to Zenith.
6. Try to open and interact with an app that you have configured to be blocked during bedtime.

Expected vs Actual

• Expected: (e.g., "The goal should be saved and visible in the list") Zenith would turn it's self back on and prevent apps to be used during bedtime.
• Actual: (e.g., "The screen closes but the list remains empty") Zenith stays closed and restrictions are bypassed.

What I've tried so far

Did you try anything to fix it? (e.g., restarted the app, toggled permissions, cleared cache)

N/A - This is not something that can be fixed without changes to the code.

Screenshots / Videos

Drag and drop images or videos here to help us see what's happening.

Google Pixel 9:

Samsung Galaxy A15 5G

Device Information

• Device: Google Pixel 9, Samsung Galaxy A15 5G
• OS: Android 17, Android 16
• App Version: v1.5.7, v1.5.7

Optional: Technical Info

If you have any error logs or specific details (like specific apps affected), paste them here.

N/A - There are no meaningful logs for this problem.

---

Checklist

• I am using the latest version of the app.
• I have checked that necessary permissions (Usage Access, Overlay) are granted.
• I have searched existing issues for a similar report.
• I have tried basic troubleshooting (restart app/device or clear cache).
• I have verified this isn't caused by battery optimization or system restrictions.

[1372Slash]

Hello, hmmm.... it seems like this is related to force stop right?, it seems like I don't have any control there because it's already related to the user who consciously does it. I might be able to add zenith as an admin application but it seems like a bit to much, so I'll leave it alone, it has to be the user who consciously doesn't force close.

if you mean to remove it from actives app, it seems like I can do something to remove it from there, but wouldn't it be more transparent to keep it displayed there?. whatever it is, thank you for the issue

[KishkaCat]

Hello, hmmm.... it seems like this is related to force stop right?, it seems like I don't have any control there because it's already related to the user who consciously does it. I might be able to add zenith as an admin application but it seems like a bit to much, so I'll leave it alone, it has to be the user who consciously doesn't force close.

if you mean to remove it from actives app, it seems like I can do something to remove it from there, but wouldn't it be more transparent to keep it displayed there?. whatever it is, thank you for the issue

I do believe that you may be able to disable the stop button, but adding admin app permissions would probably fix the issue.

I would prefer to have admin permissions as an option.