-
Notifications
You must be signed in to change notification settings - Fork 31
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
Doesn't run in background #46
Comments
@atavism and @oxtoacart what's the expected behavior here? |
@myleshorton The current behavior is to stop Lantern when you swipe and close the app from the open apps list, but we could definitely run it as a background task unless/until the VPN service is disconnected (and we already have that functionality available). |
Thanks, @quantum1423! I checked this is standard behavior with a few VPN apps (looked at TunnelBear and Betternet). Should be a quick fix on our side.. @myleshorton, I added it as a task to 2.1.1. Sound good? |
Perfect @atavism! On Thu, Mar 3, 2016 at 10:17 AM, atavism [email protected] wrote:
President |
Ideally this could be made into a switch in the settings; for example when I just need to occasionally quickly log into and check an unencrypted http website on open wi-fi I might want the current behavior, but when I'm visiting China and I want all my traffic to be proxied over hours or even days, it'd be much better for it to run almost invisibly. |
@quantum1423 Since the app allows you to turn easily turn Lantern off, do you think that's enough or do we really need an option to toggle background vs foreground? |
Oh yeah, herp derp, sorry |
@quantum1423 No need to apologize, I was just trying to clarify your need. Really appreciate the feedback! |
I'm using Sony Xperia Z3 compact with Android 5.1.1. When I turn on Lantern, it works, but as soon as I swipe it away from my open apps list, Lantern closes and doesn't proxy my traffic anymore.
Is this normal behavior? I find that a few apps seem to misbehave in this way with my phone, perhaps Sony's particular build of Android handles app closing differently? Or is this a bug with Lantern?
The text was updated successfully, but these errors were encountered: