If you are looking into a feature to create a custom locker for Android this solution on this repo doesn't work anymore due to updates on the newest Android API.

The ultimate solution for a custom way to lock the screen or create a kisok mode, is playing with the Device Owner Mode and and startLockTask more infor here:

• https://stackoverflow.com/questions/44151661/create-custom-lockscreen-for-android
• http://www.sureshjoshi.com/mobile/android-kiosk-mode-without-root/
• https://documentation.meraki.com/SM/Device_Enrollment/Enabling_Device_Owner_Mode_using_Android_Debug_Bridge_(ADB)
• https://github.com/thomasvidas/Simple-Lockscreen/tree/master

    Why write this log mainly do? Because there are different effects for different versions of the lock screen, the main is my code actually is not a problem     The method is to lift the system lock screen keyguard manager, regardless of version, either millet or android2.X 4.0 4.1 4.2 or more, is now     No problem, of course, because it is despatched, so some future version may useless, then there is a method which is now several city     Pitch lock screen software with it, let the user to cancel their lock screen, on the line.     Of course, another very important issue is the shielding home key, of course, this is resolved, the main thing is that locklayer use of,     The problem of course is limited, first you have to apply for permission, 4.0 & 4.1 you can directly apply for permission to use, but there are more than 4.2     The main problem is that users must manually give it permission, the next rights management software and the permission to add items that trust, you can, on millet     The permission name is allowed to open the floating window, android is similar, as long as the key permissions that allow on the line, can be the perfect home by masked     Key, I think the market is like this lock screen.

    Increase the optimization start lock screen, start faster     Increase the key listener, prohibit off other bad keys, such as home button     However, the existence of any problem that might occur toast sometimes show the wrong time, seemingly due to lock out     home button shield problems, solutions, modeled on the wording LockLayer class, add a privilege          While adding class LockLayer, last added lockLayer the logic code lock () unlock ()

    Implements almost all functions, change the UI and some logic, increased interactivity

    ----

    To achieve the most simple framework, built a gesture can monitor and communicate between the last two documents by the handler     A process, so now the functions are:     1.gestureListener achieve gesture listener and by handler passes the data to be processed inside Screen RelativeLayout     2.RelativeLayout realized related listens obtained depending on the direction, the next version to do is to listen for this event

    It implements a simple lock screen, but there is no logic to achieve unlocking