View Single Post
Old 05-27-2016, 10:02 AM   #102
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773670
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Quote:
Originally Posted by knc1 View Post
It is the conflict between USBnetworking and VoiceView that needs to be found and fixed.
I also experienced a conflict between VoiceView and USB mass storage, so I hope amazon will eventually notice that problem and fix it with their own firmware update. But even then it might not fix the conflict with USBnet, which may need to be a bit smarter in its assumptions made when swapping USB gadgets.

It is possible that the problem described is caused by a generic USB dongle, in some OTG device detection code, so perhaps NiLuJe may benefit from a generic sound dongle (which I offered in a PM, in request for a shipping address) as well. However, a quick viewing of the USBnet scripts shows that they could use some updates to prevent "bit-rot" in USB gadget handling logic, and that alone may fix the conflict between VoiceView and USBnet.

Last edited by geekmaster; 05-27-2016 at 10:43 AM.
geekmaster is offline   Reply With Quote