After unlocking you have to swipe again to show pin/pattern of the stock lockscreen

Question

After unlocking you have to swipe again to show pin/pattern of the stock lockscreen

wood-chris opened this issue 5 years ago · comments

I've installed acDisplay on a Sony XA2, and it seems to be working, but I've got the issue of the 'double unlock' others have reported. When I want to unlock my phone, I have to swipe up on acDisplay and then swipe up again to get to the pattern screen. Is there anyway to get to the pattern screen directly from acDisplay

Chris Wood · Answer 1 · Wed Jul 24 2019 17:54:19 GMT+0800 (China Standard Time)

I couldn't work out if this was more of an Android issue - I've asked on https://android.stackexchange.com/questions/215089/preventing-the-need-for-a-double-unlock-with-acdisplay instead

Artem Chepurnyi · Answer 2 · Wed Jul 24 2019 18:23:19 GMT+0800 (China Standard Time)

It is possible to work around by opening an empty activity, so the system knows that the user wants to go further than just a lockscreen.

Chris Wood · Answer 3 · Wed Jul 24 2019 18:43:00 GMT+0800 (China Standard Time)

Is this an option I've missed, or something to be added?

Artem Chepurnyi · Answer 4 · Wed Jul 24 2019 19:00:28 GMT+0800 (China Standard Time)

Is this an option I've missed, or something to be added?

Something that can be added.

Indrasen Pilankar · Answer 5 · Tue Feb 02 2021 21:00:04 GMT+0800 (China Standard Time)

@AChep But how to do it? Tried adding empty activity after swiping on acdisplay screen but nothing happens.

Artem Chepurnyi · Answer 6 · Tue Feb 02 2021 22:47:22 GMT+0800 (China Standard Time)

I don't really want to search for the exact solution, but there're two steps:

Use a new accessibility service's feature to correctly turn the screen off, and that will fix the inability to use fingerprint to unlock.
When you "unlock" the AcDisplay, ask the system to open another activity. This way the system will immediately show the pattern screen.

Indrasen Pilankar · Answer 7 · Thu Feb 04 2021 03:32:55 GMT+0800 (China Standard Time)

Any of these methods works with Tasker (logcat event trigger)? Or do I have to actually make changes into the code and compile it.

Artem Chepurnyi · Answer 8 · Thu Feb 04 2021 03:57:58 GMT+0800 (China Standard Time)

Any of these methods works with Tasker (logcat event trigger)? Or do I have to actually make changes into the code and compile it.

Second variant, unfortunately.

Indrasen Pilankar · Answer 9 · Thu Feb 04 2021 10:00:09 GMT+0800 (China Standard Time)

Thanks for your quick response. I'll try to have a look at the code and try to fix it as per your recommendation.

Just curious to know why you stopped working/updating this project (AcDisplay)?

Artem Chepurnyi · Answer 10 · Thu Feb 04 2021 13:12:57 GMT+0800 (China Standard Time)

Thanks for your quick response. I'll try to have a look at the code and try to fix it as per your recommendation.

Just curious to know why you stopped working/updating this project (AcDisplay)?

Three reasons:

Android started to remove/restrict a lot of APIs that made AcDisplay possible in the first place.
Android has a dumber version of AcDisplay (ambient mode) built in.
This app is free and although a lot of users did donate something (thanks guys!) this wasn't a lot and I had to find a job which reduced the time I'm able to spend on this project.

First is the biggest ones.

Indrasen Pilankar · Answer 11 · Thu Feb 04 2021 17:34:56 GMT+0800 (China Standard Time)

Understood, makes sense.

Talking over your point one, I think even Frank Monza (Kustom Industries) is facing issues with his KLCK project, but its accessibility and lock screen integration is solid but compared to AcDisplay which more stable and better performing even its a very old build till date.