Difference between revisions of "Patch WebOS Bypassing Lock Screen"

From WebOS Internals
Jump to navigation Jump to search
(Undo revision 5997 by Jsblair17 (Talk))
Line 1: Line 1:
The 1.1 update allowed me to connect to Exchange (EAS) with a policy enforced.  Of course, having my screen lock every single time I turn off the screen seems a little harsh.  The policy asks for a 10-minute timeout, but the way it's implemented in WebOS, the screen locks whenever the screen turns off.   
+
The 1.1 update allowed me to connect to Exchange (EAS) with a policy enforced.  Of course, having my screen lock every single time I turn off the screen seems a little harsh.  The policy asks for a 10-minute timeout, but the way it's implemented in WebOS, the screen locks whenever the screen turns off.  Note that this same hack appears to work with WebOS 1.2.0 as released on 9/28/2009, but has to be reapplied after you upgrade.
 
 
This hack needs to be updated to work with WebOS 1.2.0 as released on 9/28/2009, pin-assistant code has changed from 1.1 .
 
  
 
Below is a very insecure hack to automatically unlock the screen by faking the key presses for your actual passcode.  It's insecure because you actually have to put your real passcode into the code.  Still, here it is.
 
Below is a very insecure hack to automatically unlock the screen by faking the key presses for your actual passcode.  It's insecure because you actually have to put your real passcode into the code.  Still, here it is.

Revision as of 19:22, 29 September 2009

The 1.1 update allowed me to connect to Exchange (EAS) with a policy enforced. Of course, having my screen lock every single time I turn off the screen seems a little harsh. The policy asks for a 10-minute timeout, but the way it's implemented in WebOS, the screen locks whenever the screen turns off. Note that this same hack appears to work with WebOS 1.2.0 as released on 9/28/2009, but has to be reapplied after you upgrade.

Below is a very insecure hack to automatically unlock the screen by faking the key presses for your actual passcode. It's insecure because you actually have to put your real passcode into the code. Still, here it is.

Edit

/usr/palm/applications/com.palm.app.phone/app/controllers/pin-assistant.js

After line 71 "this.controller.listen('password', ..." add the following lines, replacing 1,2,3,4 with your own passcode digits.

this.updatePinFields('1');
this.updatePinFields('2');
this.updatePinFields('3');
this.updatePinFields('4');

What you've done is edit the "setup" function to do everything it already does to prepare the screen unlock application, then automatically key in your passcode.

Reboot, and your screen should automatically unlock as soon as you slide it open.

Should work like a charm!