You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My smartphone's screen just broke up (only the touch screen to be accurate), so I try to use AndroidScreencast (as it was previously rooted and adb ready).
Java program starts, all seems OK, but I can't unlock my phone (nexus 4, custom ROM Android 6) using pattern (3x3 grid), (error "Schéma incorrect", means wrong pattern). I can swipe it (to show the unlock pattern screen).
Of course, I'm 100% sure about the pattern I draw.
Maybe it's a timeout issue ? (as the delay is important, according to the screen's phone and the AndroidScreencast display.
The text was updated successfully, but these errors were encountered:
Hi.
The problem is that swipe gesture support only 2 points, it means that you can do swipe only straight.
It's limitation of adb - it doesn't support complex gestures
Just a quick reply :
I was able to bypass (more precisely remove) the lockpattern with this command (or change rm by mv if you want a backup) : adb shell rm /data/system/*.key
Then I reboot my phone, and it goes directly to my homescreen (without password or pattern)
Maybe it could be nice to add this to your app, as I think some usage of this app is to be able to use a android device even is the screen/touchscreen is broken (in order to make so backup).
My smartphone's screen just broke up (only the touch screen to be accurate), so I try to use AndroidScreencast (as it was previously rooted and adb ready).
Java program starts, all seems OK, but I can't unlock my phone (nexus 4, custom ROM Android 6) using pattern (3x3 grid), (error "Schéma incorrect", means wrong pattern). I can swipe it (to show the unlock pattern screen).
Of course, I'm 100% sure about the pattern I draw.
Maybe it's a timeout issue ? (as the delay is important, according to the screen's phone and the AndroidScreencast display.
The text was updated successfully, but these errors were encountered: