-
Notifications
You must be signed in to change notification settings - Fork 18
[SOLVED] Freeze on Android 6.0.1 #2
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
Comments
Freeze meaning only the UI unresponsive or meaning totally dead? When that condition existed was it possible to connect with ADB and get a logcat? On reboot after deleting the app was there anything in dmsg or elsewhere that can give a clue to what was happening? Without more information, and being unable to duplicate, it will be difficult to determine the cause. |
I'm running more tests right now : only the UI is frozen. I can |
Found something !
|
Also, this :
and
I guess the UI gets caught in something when trying to display LineageOS' Privacy Guard or Android window requesting access to my location. |
Looks like when the backend was selected in the microG settings it was not given the permissions it asked for. I think you are in a "catch-22" situation here as you will need the UI to grant permissions but the UI is not available to you. I think you can get out of this by:
I thought I'd properly coded the back end to fail in a soft way when it was not granted permissions but it seems not from your logcat snippets. I'll investigate further. |
In addition to request to permission on initial setup, added checks that permissions were actually granted in various places to avoid crashing microG. |
Thank you for your reply. I'll wait for a newer release to pop up on F-Droid and give it another try. I'm pretty satisfied with the behaviour on Android 7 devices. :-) BTW, I understand that Déjà Vu allows to "remember" where I've been, but I also use your other LocalGSMBackend for coarse location where I haven't been (yet), by downloading the cells database in advance. |
There is no conflict using multiple backends: It appears that UnifiedNlp/microG uses the location that reports the best accuracy. |
That's what I thought. Thank you for your confirmation. |
@n76 : My guess is that Déjà Vu locks because of that :
Since permissions were previously refused (How ? When ? No idea…), they seem not to be asked again. Is there any way to make Android forget about that ? EDIT : |
@breversa: Try to disable the backend and press OK, then re-enable the backend and press OK. |
I just did it, but sadly it doesn't change a thing. |
Same, no luck. :-( I also tried the following, with the same result :
|
SOLVED ! :-D This seems to be a LineageOS 13 issue : I had Settings/Privacy/Data protection turned on by default, and it prompts another location permission window, usually after Android's. And sometimes, for some reason, that LineageOS permission window might get stuck under another UI element, while blocking all screen interaction until it's been answered ("catch-22", for english speakers, like @n76 said). From what I understand, this issue has been solved in LineageOS 14. I solved the issue by doing the following :
|
Hi !
When I install Déjà Vu Location Service 1.0.2 from F-Droid on my LG G4/H815 running LineageOS 13/Android 6.0.1, my phone freezes as soon as I activate the backend in MicroG UnifiedNlp settings. After about two minutes, the phone will reboot and freeze again as soon as it has finished booting. Same if I reboot it beforehand.
I need to reboot to recovery (e.g. with
adb reboot recovery
) and delete/data/app/org.fitchfamily.android.dejavu
for my phone to stop freezing.The text was updated successfully, but these errors were encountered: