View Single Post
Old 07-15-2012, 09:48 AM   #11
PoP
 curly᷂͓̫̙᷊̥̮̾ͯͤͭͬͦͨ ʎʌɹnɔ
PoP ought to be getting tired of karma fortunes by now.PoP ought to be getting tired of karma fortunes by now.PoP ought to be getting tired of karma fortunes by now.PoP ought to be getting tired of karma fortunes by now.PoP ought to be getting tired of karma fortunes by now.PoP ought to be getting tired of karma fortunes by now.PoP ought to be getting tired of karma fortunes by now.PoP ought to be getting tired of karma fortunes by now.PoP ought to be getting tired of karma fortunes by now.PoP ought to be getting tired of karma fortunes by now.PoP ought to be getting tired of karma fortunes by now.
 
PoP's Avatar
 
Posts: 3,002
Karma: 50506927
Join Date: Dec 2010
Location: ♁ ᴺ₄₅°₃₀' ᵂ₇₃°₃₇' ±₆₀"
Device: K3₃.₄.₃ PW3&4₅.₁₃.₃
headphone jack

Quote:
Originally Posted by geekmaster View Post
AFAIK the headphone jack's only INPUT feature is "insertion" and "removal" events (which just happen to generate keycodes on a K3, according to the "waitforkey" program). Otherwise it is just analog sound output on that jack.[/COLOR]
I always wanted to be able to detect the jack. How? On my K3 cat /dev/input/event0 shows the keyboard cat /dev/input/event1 shows the fiveway cat /dev/input/event2 shows the volume but none of these events show insertion or removal ot the headphone jack.

And waitforkey just sits waiting as you plug in and out the jack. Different version? Bad doc?
Code:
[root@kindle root]# ls -all /usr/bin/waitforkey
-rwxr-xr-x    1 root     root         4604 Jul 31  2010 /usr/bin/waitforkey
[root@kindle root]# cat /usr/bin/waitforkey | md5sum
3d0e60680eba05a8f88667eb31b7c197  -
[root@kindle root]#
PoP is offline   Reply With Quote