View Single Post
Old 11-27-2012, 11:09 PM   #175
twobob
( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Týr
twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.
 
twobob's Avatar
 
Posts: 6,586
Karma: 6299993
Join Date: Jun 2012
Location: uti gratia usura (Yao ying da ying; Mo ying da yieng)
Device: PW-WIFI|K5-3G+WIFI| K4|K3-3G|DXG|K2| Rooted Nook Touch
Here I realise that the injection into the /dev/input/event3 buffer isn't working as I might expect. So I abandon it in favour of native code
Spoiler:

Hokay.... I clearly have something else wrong...

on touch: [root@kindle input]# cat /dev/input/event2
(couple of home presses)
Quote:
���Pu�f���P�����Pr�f���P{�
In another shell:
[root@kindle bin]# keywriteEuroEvent2 (writes Euro Symbol to /dev/input/event2) well, it is supposed to anyway

Quote:
Starting the keyboard buffer writer/reader
The keyboard code is: 435
But the cat shows no activity. so it's obviously not doing what I expected.

Hmm..

But it doesn't "hang" like it does on the 3 ... oddness. I obviously need to know more about the locking aspect of this mechanism

Last edited by twobob; 11-28-2012 at 09:55 AM. Reason: I obviously need to know more about the locking aspect of this mechanism
twobob is offline   Reply With Quote