Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] - Non-dismissable persistent notification #372

Closed
gabriel20xx opened this issue Sep 30, 2024 · 1 comment · Fixed by #490
Closed

[FEATURE] - Non-dismissable persistent notification #372

gabriel20xx opened this issue Sep 30, 2024 · 1 comment · Fixed by #490
Assignees
Labels
enhancement New feature or request

Comments

@gabriel20xx
Copy link
Contributor

Is your feature request related to a problem? Please describe.
On some roms it happens, that the background service that is intended to track the auto-tunneling state gets unresponsive or gets killed by the os even though the app is set to use unrestricted battery. For myself, I have the problem, that if I switch the wifi network from trusted to untrusted or to mobile data or vice versa it doesn't automatically and/or instantly toggle the vpn as it should with auto-tunneling enabled.

Describe the solution you'd like
I would think a possible solution would be to create a persistent, non-dismissable notification when auto-tunneling is enabled. This notification makes sure, that the background service, that is responsible for toggling the vpn on auto-tunneling does not get killed and is always listening to network changes.

Describe alternatives you've considered
I don't have any good alternatives.

Additional context

@gabriel20xx gabriel20xx added the enhancement New feature or request label Sep 30, 2024
@aqsede
Copy link

aqsede commented Oct 3, 2024

Please make an option also for current implementation which don't have it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants