|
2012-09-07
, 20:07
|
|
Moderator |
Posts: 2,622 |
Thanked: 5,447 times |
Joined on Jan 2010
|
#123
|
The Following User Says Thank You to qwazix For This Useful Post: | ||
|
2012-09-07
, 20:26
|
|
Posts: 1,637 |
Thanked: 4,424 times |
Joined on Apr 2009
@ Germany
|
#124
|
|
2012-09-07
, 22:11
|
|
Moderator |
Posts: 2,622 |
Thanked: 5,447 times |
Joined on Jan 2010
|
#125
|
|
2012-09-08
, 18:51
|
Posts: 203 |
Thanked: 445 times |
Joined on Mar 2010
|
#127
|
The Following User Says Thank You to foobar For This Useful Post: | ||
|
2012-09-08
, 19:38
|
|
Moderator |
Posts: 2,622 |
Thanked: 5,447 times |
Joined on Jan 2010
|
#128
|
sleep 0.2 sh -c 'echo "echo 1 > /sys/devices/platform/omap2_mcspi.1/spi1.0/disable_ts" | sudo gainroot'
The Following User Says Thank You to qwazix For This Useful Post: | ||
|
2012-09-08
, 22:21
|
|
Posts: 236 |
Thanked: 95 times |
Joined on Jan 2012
@ Ecuador
|
#129
|
I put 0.0.9 to a real-life test on my main phone today and, unfortunately, I have to report that the current behavior is not perfect. The problem is the unlocked touchscreen and the fact that the desktop is shown (and active) if the phone isn't locked (by lock code) yet. So sometimes I found various programs running that were started by 'accidental' taps inside my pocket or bag.
Obviously it would be ideal if only the lockscreen could be shown without the actual powerbutton actions. Does anyone have any idea what part of Memo listens to (and reacts on) powerbutton clicks? How does qtlockscreen do its job?
The Following User Says Thank You to D@vIcHoJD For This Useful Post: | ||
|
2012-09-09
, 19:29
|
Posts: 159 |
Thanked: 217 times |
Joined on Oct 2011
|
#130
|
The Following User Says Thank You to Kossuth For This Useful Post: | ||
missing executable bit!
chmod a+x powerbutton
my contributions:
Desktop Clock Widget|Calendar Home Widget|Lens Cover Reminder|ConnectNow|Scout|App Search Widget|ProfilesX|
Desktop-Switcher|SMS-Messageblocker
-Donate-