Kindle USB Audio Adapter

[knc1]

Originally Posted by Doitsu

I used this method, but unfortunately got the same results as geekmaster.
It looks like the PW2 doesn't see my usb audio card.

OK, thanks for trying it out.

The system action to auto-magically reconfig itself when a new device is hot-plugged does not lend itself to simple monitoring.
I.E: Not anything I could easily write a button for.

So we wait until someone can do some hands-on testing and then write it up here.

[JSWolf]

Originally Posted by knc1

OK, thanks for trying it out.

The system action to auto-magically reconfig itself when a new device is hot-plugged does not lend itself to simple monitoring.
I.E: Not anything I could easily write a button for.

So we wait until someone can do some hands-on testing and then write it up here.

The problem is that the voice needs 512MB ram and the PW2 only has 256MB ram. So it won't work on a PW2.

[geekmaster]

Originally Posted by JSWolf

The problem is that the voice needs 512MB ram and the PW2 only has 256MB ram. So it won't work on a PW2.

Unless you add a swapfile...

[geekmaster]

Originally Posted by JSWolf

The problem is that the voice needs 512MB ram and the PW2 only has 256MB ram. So it won't work on a PW2.

Unless you add a swapfile and/or use a smaller (custom) voice...

[Mr.Husky]

Anyone tried to add custom language files?

[knc1]

Originally Posted by JSWolf

The problem is that the voice needs 512MB ram and the PW2 only has 256MB ram. So it won't work on a PW2.

Please provide your references, not just a pronouncement.

[AnemicOak]

Originally Posted by knc1

Please provide your references, not just a pronouncement.

I assume he was referring to this...
https://www.mobileread.com/forums/sho...&postcount=123

[knc1]

No News Is ....
Well, still it is information.

Plug in Amazon adapter (Device: PW-3, fw-5.6.1.1) -
Kernel does not recognize the addition of a device (I.E: nothing put into kernel's message buffer - zip, zero, nada, ....)

Meanwhile -

[root@kindle root]# cat /lib/udev/bin/notifyheadset

#!/bin/sh
if [ "$ACTION" = "add" ] ; then
        /usr/bin/lipc-send-event -r 3 com.lab126.hal audioHS -i 1
elif [ "$ACTION" = "remove" ] ; then
        /usr/bin/lipc-send-event -r 3 com.lab126.hal audioHS -i 0
fi

exit 0

It looks like the code to be called when the device is hotplugged is present.

Hmm....

[root@kindle root]# ACTION=add sh -x /lib/udev/bin/notifyheadset 
+ [ add = add ]
+ /usr/bin/lipc-send-event -r 3 com.lab126.hal audioHS -i 1
+ exit 0
[root@kindle root]# dmesg
[root@kindle root]#

The doorbell is present but evidently nobody is home with this firmware version.

Since I have no burning need to have my PW-3 talk to me (other than to use it as an alarm clock, sometime in the future) -
I do not intend to update my firmware in the PW-3 just for this dongle.

But those which do not have an Amazon dongle, might plug in the one that they do have and try the example 'add' command above, just to see what dmesg has to say.

[geekmaster]

Originally Posted by knc1

No News Is ....
Well, still it is information.

Plug in Amazon adapter (Device: PW-3, fw-5.6.1.1) -
Kernel does not recognize the addition of a device (I.E: nothing put into kernel's message buffer - zip, zero, nada, ....)

Meanwhile -

[root@kindle root]# cat /lib/udev/bin/notifyheadset

#!/bin/sh
if [ "$ACTION" = "add" ] ; then
        /usr/bin/lipc-send-event -r 3 com.lab126.hal audioHS -i 1
elif [ "$ACTION" = "remove" ] ; then
        /usr/bin/lipc-send-event -r 3 com.lab126.hal audioHS -i 0
fi

exit 0

It looks like the code to be called when the device is hotplugged is present.

Hmm....

[root@kindle root]# ACTION=add sh -x /lib/udev/bin/notifyheadset 
+ [ add = add ]
+ /usr/bin/lipc-send-event -r 3 com.lab126.hal audioHS -i 1
+ exit 0
[root@kindle root]# dmesg
[root@kindle root]#

The doorbell is present but evidently nobody is home with this firmware version.

Since I have no burning need to have my PW-3 talk to me (other than to use it as an alarm clock, sometime in the future) -
I do not intend to update my firmware in the PW-3 just for this dongle.

But those which do not have an Amazon dongle, might plug in the one that they do have and try the example 'add' command above, just to see what dmesg has to say.

I was about to try this, until I realized I cannot use usbnet ssh and usb audio at the same time. My PW3 touchscreen has been getting much less relaible, almost unusable, and tapping the power button now rarely fixes it. I mostly use it as a test devive under ssh.

To do this test, I would have to switch to ssh over wifi so I can do sound over usb. Perhaps a usb hub could allow both, but that complicates things when we are not sure it will even work in the simplest case.

ssh over wifi, later... then usb sound test. Or... background the command with a sleep, then switch usb devices devices?

[knc1]

Don't go to any bother - -
The PW-3 has been out a long time before the SW jailbreak -
I am sure there are people here with a serial port connection to their PW-3.

[geekmaster]

Originally Posted by knc1

Don't go to any bother - -
The PW-3 has been out a long time before the SW jailbreak -
I am sure there are people here with a serial port connection to their PW-3.

I ran a looping script in the background:
/mnt/us/notifyheadset &

PHP Code:

#!/bin/sh
LOG="/mnt/us/documents/$0.txt"
echo Logging to $LOG ...
while true; do
  sleep 1
  date >> $LOG 2>&1
  ACTION=add
  sh -x /lib/udev/bin/notifyheadset >> $LOG 2>&1
done 


I cleared dmesg "dmesg -C". I unplugged USBnet, and plugged in and removed USB dongle from USB OTG adapter, and USB OTG adapter from PW3, and plugged them in, with PW3 in and out of screensaver mode, with multiple variations and repetition. Then I restored USBnet. Then I killed the background script, and did "dmesg > /mnt/us/documents/dmesg.txt.. I usually log to .txt files in /mnt/us/documents so I can view them on the device. The log output is just a repetition of what you showed (no extra data). Here is dmesg output:

[15803.097245] KERNEL: I pmic:charger chgina::charger disconnected
[15803.103000] fsl_gadget_disconnect_event: udc enter low power mode
[15818.640850] KERNEL: I pmic:onkey::wario button online event
[15821.389932] KERNEL: I pmic:onkey::wario button online event
[15825.766586] KERNEL: I pmic:onkey::wario button online event
[15830.645083] KERNEL: I pmic:onkey::wario button online event
[15848.497307] KERNEL: I pmic:charger chgina::charger connected
[15848.518239] otg udc vbus rising wakeup
[15848.518969] try_wake_up_udc: udc out low power mode
[15849.041636] g_ether gadget: high speed config #2: RNDIS

[geekmaster]

Originally Posted by knc1

Don't go to any bother - -
The PW-3 has been out a long time before the SW jailbreak -
I am sure there are people here with a serial port connection to their PW-3

I still can't find any of my multiple usb serial adapters, so serial is not yet an option. That is a problem with organizing and put like things together -- they all get lost together. With distributed storage, a search finds at least one of them much more quickly...

However, I did run the test, and as reported above, no response. Also, my USB dongle has a power and/or access LED which did not turn on. It blinks and flickers "randomly" while initializing after plugin on a PC. Nothing on the PW3. Perhaps a kernel module gadget needs loading? Or perhaps the USBnet RNDIS kernel module is in the way, and the script does not unload it? Not sure yet...

My previous testing was on a PW2. Perhaps I could try this script on that, without RNDIS loaded (a KUAL extension, perhaps)... For that matter, I have KUAL on this PW3, and unlike yesterday, the touchscreen seem somewhat stable tonight.

Though in reality, what we really need, at least for now, is somebody with a REAL amazon USB sound adapter to try this command on a PW3...

[jhowell]

@geekmaster, I have have the same question for you as I did for Conan46 in this post.

[geekmaster]

Originally Posted by jhowell

@geekmaster, I have have the same question for you as I did for Conan46 in this post.

Ahh... Thanks! I only did that on my PW2!

I will try again after the update, tomorrow. Thanks for the tip...

[encol]

Originally Posted by geekmaster

Though in reality, what we really need, at least for now, is somebody with a REAL amazon USB sound adapter to try this command on a PW3...

or somebody with a generic USB dongle and a PW3 with the latest firmware...

i have the second one, and i ordered the dongle from china but it takes too long to arrive