-
Notifications
You must be signed in to change notification settings - Fork 95
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
Flightmode not set correctly #318
Comments
Forgot to mention: It doesn't happen all the time. Only sometimes :-( |
Hi there, However, the behaviour on your case is quite interesting/strange. I thought it should either work or not work. |
It does happen on enabling and disabling. But when it happens seem to be random. Sometimes flight mode doesn't change for two or three "loops" of the script, then it works a while again. Too bad that it can't be fixed easily. I helped myself now by switching mobile data on and off instead of flight mode. Should be a standard Android feature in my opinion, because not being online all the time saves lots of battery power. BTW: What's the difference between exact and inexact timers? How more exact is the exact timer and is the battery drain much higher? |
Yes, that's very unconvinent but it's reasonable for the Android team to decide not allowing changing airplane mode (and mobile data actually) from a user app, in order to stop abuse. Exact should be perfectly exact, according to Android documentation; inexact is adjusted (aligned) by Android system and even the developers (i.e. me) have no idea how inexact it will be (but hopefully within 10 minutes?). |
By the way, you can have a look at #261 if you want some more information about how airplane mode is currently being handled. |
I try to write a script to deactivate flightmode every 30 minutes for 3 minutes. But Easer doesn't seem to set flightmode correctly.
As you can see flightmode is activated, but there is still data connection.
I'm using LineageOS 16.0 with microG on a LG-D802 and Easer 0.7.9.1
The text was updated successfully, but these errors were encountered: