Accessibility bug

Porkchop

I like to use the double tap feature to lock screen. I currently use Lawnchair but this issue goes for any other launcher I've tried as well. The double tap to lock screen feature requires accessibility access. When I attempt to flip the toggle on to allow accessibility control, it refuses to turn on. I have also given it restricted permissions access by tapping the 3 dots within the apps settings page in GOS settings but the issue persists. GOS is not allowing me to turn this on for any launcher regardless of giving the apps restricted perms. When I click the toggle to on, it pops up and asks do I want to allow, deny or disable the app, I click allow and the popup disappears and the toggle remains off.

other8026

Porkchop GOS is not allowing me to turn this on for any launcher regardless of giving the apps restricted perms.

What you're describing isn't something that was added to GrapheneOS by the GrapheneOS developers. It's a security feature / change in how the security feature works in AOSP.

Are you using the owner profile or a secondary profile?

Porkchop

other8026 its a secondary profile. Could have sworn I was able to before in a past version, am I incorrect?

other8026

Porkchop I don't recall where I saw this and I haven't tried it, so I'm not sure if it's correct, but I think it's an upstream profile issue. I recall reading that if the same app is installed in the owner profile, you can trigger the app to request the permission, then go to Settings > Apps > All apps > *app name* > *3 dots in upper right-hand corner*. From there (if I remember correctly) you can enable something? Then after doing that in the owner profile, I read you can do the same in the secondary profile.

Curious if this works or not.

Porkchop

other8026 thank you, I will try this and see if that works and I will report back the result.

Porkchop

other8026 so it worked. Giving the lawnchair app full access on owner profile, allowed me to give it full access on secondary and double tap to sleep now works. Thanks for that suggestion.

other8026

Porkchop thanks for reporting back. I wasn't sure if what I thought I remembered would work or not!

Thimble0548

Is there a possibility that this issue can be fixed? I like to keep my owner profile as empty as possible. I would be interested to find where I can raise this issue

de0u

Thimble0548 If the workaround works for you (which would confirm the details of the bug), you could create an issue on the GrapheneOS issue tracker on GitHub and report your experience (and reference this discussion thread).

But because there is a simple workaround I would say there is a fair chance that a filed issue would be marked "bug" and "upstream" and might not be fixed until Google gets around to it themselves. It's not a security issue or a privacy issue and it's not clear it's making trouble for a lot of users. The GrapheneOS team already has a lot of issues that are security issues or privacy issues, and some things that affect many users.

One thing that would improve the likelihood of this particular glitch being fixed would be finding where in the code the bug is.

Please note that I do not speak for the GrapheneOS project.