Quote:
Originally Posted by dhdurgee
Assuming that full BT audio support is present I would expect you to be able to install the mplayer built for kindle on it. I used it on my K3, which does have an earphone jack and speakers, but don't have a newer model to test this on. The mplayer build comes with a launchpad profile, but you should have no big problem creating a KUAL menu entry instead.
With mplayer installed you should be able to play any supported audio file. You can even use it to play internet audio streams, as that was my major use of it on my K3.
I would suggest having kterm installed first so that you can attempt to use mplayer first from a terminal window. That way you can see any error messages and find out if you need additional command line options to specify output via bluetooth.
Dave
|
I SSH'd into the Kindle and played around a bit. It doesn't seem that the mplayer binary will run correctly, alsa tools can't find any sound card through SSH?
The only useful thing I was able to glare out is that on reconnecting BT the files in /chroot/dev/shm change...
[root@kindle shm]# ls -lah /chroot/dev/shm
drwxrwxrwt 2 root root 100 Dec 15 19:44 .
drwxrwxr-x 3 root root 1.0K Sep 20 11:36 ..
-rw-rw-r-- 1 root root 37.4K Dec 15 19:44 mstream1510_2094
-rw-rw-r-- 1 root root 152.9K Dec 15 19:23 mstream17956_2986
-rw-rw-r-- 1 root root 152.9K Dec 15 19:44 mstream21457_3718
Also looks like Kindle has built-in mplay that seems to be capable of playing .wav, but executing it just gives back a status code 1.
This is output from trying to use the mplayer binary:
https://haste.rys.pw/raw/otocokiqod
Would love some pointers.