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

[wood-chris]

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

[wood-chris]

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

[AChep]

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.

[wood-chris]

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

[AChep]

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

Something that can be added.

[varunpilankar]

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

[AChep]

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

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

[varunpilankar]

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

[AChep]

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.

[varunpilankar]

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)?

[AChep]

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:

1. Android started to remove/restrict a lot of APIs that made AcDisplay possible in the first place.
2. Android has a dumber version of AcDisplay (ambient mode) built in.
3. 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.

[varunpilankar]

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.