DIY Kindle voice control (simulating key presses)

[knc1]

If using the Netcat (nc) built into Busybox, you will need to adjust the following nc command to match its limitations.

Objective: Send strings via network to /proc/keypad
Kindle: Listen on all interfaces, using some port number of your choosing (12345)
Remote machine: Assume Kindle appears as 192.168.2.1 on that machines network

Using a full copy of Netcat (nc) and assuming you haven't blocked new UDP connections in the Kindle's iptables setup (that is, open your above choice of port for UDP, state:new).

On Kindle:
(Listen, IPv4, re-start a new connection, no DNS lookups, UDP)
nc -l -4 -k -n -u 12345 >/proc/keypad

On remote machine:
echo "send 104" > nc -4 -n -u 192.168.2.1:12345

The Kindle end will auto-restart its listening for the next connection when it finishes receiving the above UDP packet.
I.E: You don't have to repeat the Kindle nc command, it will continue until you kill it.

Embellish as desired.
Such as start the Kindle nc command "on demand" using inetd and inetd.conf (in which case you don't need the "-k" - inetd will take care of start/stop of nc).

[nick-tech]

arecord -c 1 -r 16000 -f S16_LE test.wav

gives pretty good results, I'm quite impressed by the quality of that microphone. Perhaps one day we'll have a skype app for the androidized kindle...

[knc1]

Originally Posted by knc1

If using the Netcat (nc) built into Busybox, you will need to adjust the following nc command to match its limitations.

Objective: Send strings via network to /proc/keypad
Kindle: Listen on all interfaces, using some port number of your choosing (12345)
Remote machine: Assume Kindle appears as 192.168.2.1 on that machines network

Using a full copy of Netcat (nc) and assuming you haven't blocked new UDP connections in the Kindle's iptables setup (that is, open your above choice of port for UDP, state:new).

On Kindle:
(Listen, IPv4, re-start a new connection, no DNS lookups, UDP)
nc -l -4 -k -n -u 12345 >/proc/keypad

On remote machine:
echo "send 104" > nc -4 -n -u 192.168.2.1:12345

The Kindle end will auto-restart its listening for the next connection when it finishes receiving the above UDP packet.
I.E: You don't have to repeat the Kindle nc command, it will continue until you kill it.

Embellish as desired.
Such as start the Kindle nc command "on demand" using inetd and inetd.conf (in which case you don't need the "-k" - inetd will take care of start/stop of nc).

I seem to be having trouble, following my own directions.
Some versions don't know about -4/-6 (IPv4 / IPv6 selection).

Note: You can test the two nc ends by "talking" over the local-loopback (127.0.0.1)
No need to trash up your Kindle until you get what you want working locally.

[Nyoxi]

Originally Posted by knc1

I seem to be having trouble, following my own directions.
Some versions don't know about -4/-6 (IPv4 / IPv6 selection).

Unfortunately there is a dozen of different netcat variants. But for the purposes of this thread anything should be good enough. Anyway if you find yourself compiling your own netcat somewhere you may as well consider using socat instead (much more powerful).

[twobob]

Originally Posted by bubnikv

If you want a voice control on Kindle, why don't you do it on the Kindle itself.
The Kindle has a built in microphone, which is accessible on Kindle using the alsalib. Porting a simple phrase recognition software from Linux to Kindle is not a big deal. A good candidate may be

http://www.kiecza.net/daniel/linux/

Vojtech

libncurses4 (>= 4.2-3.1) required for this.
(sadly I have ncurses-5.9, so possibly some hackery required)

Thanks for the tip. I will put it on my list to try.

[twobob]

Ncurses library and header files
Pthreads library
OSS sound library (sys/soundcard.h)

Humph. sounds like a job for buildroot. Will move to other pile. : )