Database Info

[Q] DVB-T dongle through OTG on eos 2

Just flashed eos 2 upgrading from a 4.0.3 nightly
(UK Wifi-Only XOOM with ClockWork)
I got a question for you: I tryied to attach a DVB-T dongle, through an OTG
cable, without any expectation.. in dmesg there are references to USB devices,
but all related to the USB hub:
Code:
[14033.728916] cpcap-otg cpcap-otg: SUSPEND --> HOST[14033.734381] tegra-ehci tegra-ehci.0: Tegra EHCI Host Controller
[14033.735207] tegra-ehci tegra-ehci.0: new USB bus registered, assigned bus number 2
[14033.814996] tegra-ehci tegra-ehci.0: irq 52, io mem 0xc5000000
[14033.837508] tegra-ehci tegra-ehci.0: USB 2.0 started, EHCI 1.00
[14033.837722] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[14033.837814] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[14033.837966] usb usb2: Product: Tegra EHCI Host Controller
[14033.838050] usb usb2: Manufacturer: Linux 2.6.39.4-Tiamat-3.0.15-gpuoc-00001-gde1b8c2 ehci_hcd
[14033.838202] usb usb2: SerialNumber: tegra-ehci.0
[14033.840005] hub 2-0:1.0: USB hub found
[14033.840108] hub 2-0:1.0: 1 port detected
There is no mention of the attached device, but it seems that the kernel
recognizes some USB activity. The cable is working (I tryied it with several
USB keys) and the DVB-T dongle too. Here's the dmesg log of a linux
machine (ubuntu) when I attach the device:
Code:
[ 58.029317] usb 1-1: new high-speed USB device number 2 using ehci_hcd
[ 58.807095] IR NEC protocol handler initialized
[ 58.908150] IR RC5(x) protocol handler initialized
[ 58.974855] dib0700: loaded with support for 21 different device-types
[ 58.983660] IR RC6 protocol handler initialized
[ 59.003086] dvb-usb: found a 'Compro Videomate U500' in warm state.
[ 59.003229] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 59.006471] DVB: registering new adapter (Compro Videomate U500)
[ 59.089976] IR JVC protocol handler initialized
[ 59.103600] IR Sony protocol handler initialized
[ 59.116159] IR MCE Keyboard/mouse protocol handler initialized
[ 59.141967] lirc_dev: IR Remote Control driver registered, major 250
[ 59.144610] IR LIRC bridge handler initialized
[ 59.658663] DVB: registering adapter 0 frontend 0 (DiBcom 7000PC)...
[ 59.742154] MT2060: successfully identified (IF1 = 1220)
[ 60.688569] Registered IR keymap rc-dib0700-rc5
[ 60.689296] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:0b.0/usb1/1-1/rc/rc0/input6
[ 60.689778] rc0: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:0b.0/usb1/1-1/rc/rc0
[ 60.710720] dvb-usb: schedule remote query interval to 50 msecs.
[ 60.710725] dvb-usb: Compro Videomate U500 successfully initialized and connected.
[ 60.712443] usbcore: registered new interface driver dvb_usb_dib0700
I would like to recompile the proper driver for tiamat kernel 3.0.15,
if possibile, but is an OTG cable enough to support this device ?
thanks guys ! :-D
(maybe this is not the right thread, feel free to move my post !)

[Q] Minix Neo x7 USB<->Serial adapter issue

Hello,
I have an issue I can't resolve by myself. I would like to use Prolific pl2303 usb<->serial adapter. I can't make it work. I see /dev/ttyUSB0 but it doesn't work as serial port. In dmesg I see:
<6>[ 1844.751839] usb 2-1.4.5: new full speed USB device number 10 using usb20_host
<6>[ 1844.853186] usb 2-1.4.5: New USB device found, idVendor=067b, idProduct=2303
<6>[ 1844.853292] usb 2-1.4.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
<6>[ 1844.853395] usb 2-1.4.5: Product: USB-Serial Controller C
<6>[ 1844.853462] usb 2-1.4.5: Manufacturer: Prolific Technology Inc.
<6>[ 1844.855524] option 2-1.4.5:1.0: GSM modem (1-port) converter detected
<6>[ 1844.856420] usb 2-1.4.5: GSM modem (1-port) converter now attached to ttyUSB0
Obviously it should be handled by pl2303.ko, but it seems it's not so.
How to make pl2303.ko handle the device?
Thanx in advance.

OTG cable + Card reader = not working.

Hey Im running US retail on my XT 1032, with root and unlocked bootloader. I have the last OTA update with OTG fix.
Since I updated I've been trying to connect my Card reader to my moto g with the OTG cable, but it doesn't work, it doesn't recognize it. I tried with two differents readers and two micro sd, both in NTFS, FAT and FAT32.
I tried a pen drive and it works fine. Its weird because meenova its a card reader too and it works perfectly (I havent got one, and its really hard to buy it in my country because of the costumes policy).
I have a Sandisk 16gb Ultra, so, I really want to fix this.

Any idea?

tatitar said:
Any idea?
Click to expand...
Click to collapse
If you have root, try run the following command from a shell after pluging in the usb device
Code:
echo -n 1 | tee /sys/bus/usb/devices/1-1/bConfigurationValue
I used to have a problem with my HP TP, some USB devices asked to much juice and the default settings reject the device.
Have a look at the following post for more info.
http://rootzwiki.com/topic/33033-otg-usb-insufficient-available-bus-toolthingy/
A "dmesg" output will help you to identify why the device is not been detected.

dubidu said:
If you have root, try run the following command from a shell after pluging in the usb device
Code:
echo -n 1 | tee /sys/bus/usb/devices/1-1/bConfigurationValue
I used to have a problem with my HP TP, some USB devices asked to much juice and the default settings reject the device.
Have a look at the following post for more info.
http://rootzwiki.com/topic/33033-otg-usb-insufficient-available-bus-toolthingy/
A "dmesg" output will help you to identify why the device is not been detected.
Click to expand...
Click to collapse
I tried that and got "tee not found" Maybe I'll sell my microsd and buy a pendrive with that money, I tried almost everything

tatitar said:
I tried that and got "tee not found" Maybe I'll sell my microsd and buy a pendrive with that money, I tried almost everything
Click to expand...
Click to collapse
you don't really need tee, an echo will also change the parameter.
post a dmesg output when you plug the device, that may tell us why is failing to mount

dubidu said:
you don't really need tee, an echo will also change the parameter.
post a dmesg output when you plug the device, that may tell us why is failing to mount
Click to expand...
Click to collapse
http://www.sendspace.com/file/fhj00w There's my dmesg

Can't see anything related to been rejected due power, so the bConfig trick will not work in this case.
Code:
<6>[64952.092782,0] msm_otg f9a55000.usb: USB exited from low power mode
<6>[64952.151006,0] healthd: battery l=96 v=4229 t=27.4 h=2 st=3 c=136 chg=
<6>[64952.182920,0] healthd: battery l=96 v=4224 t=27.4 h=2 st=3 c=188 chg=
<6>[64952.206377,0] msm_hsusb_host msm_hsusb_host: Qualcomm On-Chip EHCI Host Controller
<6>[64952.206931,0] msm_hsusb_host msm_hsusb_host: new USB bus registered, assigned bus number 1
<6>[64952.238571,0] msm_hsusb_host msm_hsusb_host: irq 166, io mem 0xf9a55000
<6>[64952.258317,0] msm_hsusb_host msm_hsusb_host: USB 2.0 started, EHCI 1.00
<6>[64952.258647,0] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
<6>[64952.258750,0] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[64952.258924,0] usb usb1: Product: Qualcomm On-Chip EHCI Host Controller
<6>[64952.259099,0] usb usb1: Manufacturer: Linux 3.4.0-gc6fc9e1-00001-gf3bf628 ehci_hcd
<6>[64952.259197,0] usb usb1: SerialNumber: msm_hsusb_host
<6>[64952.261601,0] hub 1-0:1.0: USB hub found
<6>[64952.261731,0] hub 1-0:1.0: 1 port detected
<3>[64952.518160,0] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[64955.061905,0] msm_otg f9a55000.usb: USB in low power mode
I guess that reader is not supported by the current kernel. It looks like it is detected as a USB Hub, not as a simple USB storage device.
Code:
<6>[64952.261601,0] hub 1-0:1.0: USB hub found
Get a cheap one (e.g: like this http://www.ebay.co.uk/itm/OTG-USB-M...aphy_MemoryCardReaders_RL&hash=item5d46cbed5b
I have a couple and they do the job fine.

http://forum.xda-developers.com/moto-x/general/otg-supported-4-4-2-unrooted-via-t2709553
My fix for the X.

Question related to OTG, for Moto G running Kitkat is it safe to directly unplug the OTG cable with the USB?

hypertx said:
Question related to OTG, for Moto G running Kitkat is it safe to directly unplug the OTG cable with the USB?
Click to expand...
Click to collapse
I do it all the time, BUT IF YOU FORGET YOU HAVE A WRITE OPERATION IN PROGRESS IT WILL TRASH the card.
Btw do all the G's have /storage/usbdisk on 442?http://forum.xda-developers.com/attachment.php?attachmentid=2675348&stc=1&d=1396975449

dubidu said:
Can't see anything related to been rejected due power, so the bConfig trick will not work in this case.
Code:
<6>[64952.092782,0] msm_otg f9a55000.usb: USB exited from low power mode
<6>[64952.151006,0] healthd: battery l=96 v=4229 t=27.4 h=2 st=3 c=136 chg=
<6>[64952.182920,0] healthd: battery l=96 v=4224 t=27.4 h=2 st=3 c=188 chg=
<6>[64952.206377,0] msm_hsusb_host msm_hsusb_host: Qualcomm On-Chip EHCI Host Controller
<6>[64952.206931,0] msm_hsusb_host msm_hsusb_host: new USB bus registered, assigned bus number 1
<6>[64952.238571,0] msm_hsusb_host msm_hsusb_host: irq 166, io mem 0xf9a55000
<6>[64952.258317,0] msm_hsusb_host msm_hsusb_host: USB 2.0 started, EHCI 1.00
<6>[64952.258647,0] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
<6>[64952.258750,0] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[64952.258924,0] usb usb1: Product: Qualcomm On-Chip EHCI Host Controller
<6>[64952.259099,0] usb usb1: Manufacturer: Linux 3.4.0-gc6fc9e1-00001-gf3bf628 ehci_hcd
<6>[64952.259197,0] usb usb1: SerialNumber: msm_hsusb_host
<6>[64952.261601,0] hub 1-0:1.0: USB hub found
<6>[64952.261731,0] hub 1-0:1.0: 1 port detected
<3>[64952.518160,0] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[64955.061905,0] msm_otg f9a55000.usb: USB in low power mode
I guess that reader is not supported by the current kernel. It looks like it is detected as a USB Hub, not as a simple USB storage device.
Code:
<6>[64952.261601,0] hub 1-0:1.0: USB hub found
Get a cheap one (e.g: like this http://www.ebay.co.uk/itm/OTG-USB-M...aphy_MemoryCardReaders_RL&hash=item5d46cbed5b
I have a couple and they do the job fine.
Click to expand...
Click to collapse
Thanks, Im from Argentina and I couldn't find a micro usb card reader, and if I buy it in ebay I should wait 3 - 4 months because of post office delay, maybe I'll buy a pendrive. My reader is similar to yours, but with usb not micro

I have this problem too... Any other ideas?

[Q] External Wi-Fi USB adapter

Hello, guys!
I got Nexus 5 running vanilla AOSP Android 4.4.3 compiled by myself. It works like a charm. I would like to use external Wi-Fi USB adapter with my Nexus 5. I've tried to use AWUS036NHA (with Atheros AR92721 chip) and two other models from different vendors. Every time I get the same error.
So, what have I done? I've rebuilt kernel to add support for my devices (in usual Linux way) and added firmwares they need to /vendor/firmware. When I plug AWUS036NHA into my phone I get the following (dmesg):
Code:
<6>[ 1587.856305] usb 1-1: new high-speed USB device number 2 using xhci-hcd
<6>[ 1587.887070] usb 1-1: New USB device found, idVendor=0cf3, idProduct=9271
<6>[ 1587.887129] usb 1-1: New USB device strings: Mfr=16, Product=32, SerialNumber=48
<6>[ 1587.887221] usb 1-1: Product: UB91C
<6>[ 1587.887273] usb 1-1: Manufacturer: ATHEROS
<6>[ 1587.887365] usb 1-1: SerialNumber: 12345
<4>[ 1587.887857] usb 1-1: ep 0x1 - rounding interval to 32768 microframes, ep desc says 0 microframes
<4>[ 1587.888693] usb 1-1: ep 0x82 - rounding interval to 32768 microframes, ep desc says 0 microframes
<4>[ 1587.888968] usb 1-1: ep 0x5 - rounding interval to 32768 microframes, ep desc says 0 microframes
<4>[ 1587.889115] usb 1-1: ep 0x6 - rounding interval to 32768 microframes, ep desc says 0 microframes
<6>[ 1587.890044] usb 1-1: ath9k_htc: Firmware htc_9271.fw requested
<6>[ 1588.180755] usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
<6>[ 1588.416902] ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 33 credits
<6>[ 1588.644279] ath9k_htc 1-1:1.0: ath9k_htc: FW Version: 1.3
<7>[ 1588.644345] ath: EEPROM regdomain: 0x833a
<7>[ 1588.644351] ath: EEPROM indicates we should expect a country code
<7>[ 1588.644360] ath: doing EEPROM country->regdmn map search
<7>[ 1588.644367] ath: country maps to regdmn code: 0x37
<7>[ 1588.644374] ath: Country alpha2 being used: GB
<7>[ 1588.644379] ath: Regpair used: 0x37
<6>[ 1588.648677] ieee80211 phy3: Atheros AR9271 Rev:1
<7>[ 1588.650804] Registered led device: ath9k_htc-phy3
It seems to me that everything here is ok. But when I try to switch on the adapter (ifconfig wlan1 up) I get an error (dmesg):
Code:
ADDRCONF(NETDEV_UP): wlan1: link is not ready
By the way, "ifconfig" command shows no error, but certainly it doesn't swith my device on.
So, I got the same error with 3 different adapters. I got no idea about possible ways of solving this problem.
Please, share your ideas, I'm really stuck Looking forward for your help. And thanks in advance!

MT65xx Preloader keeps reconnecting a powered USB port instead of charging

Hello,
I am using ThinkPad with three USB v3 ports running Linux 4.14. When I try charging my MT6572 device turned off (its battery is not replacable), the result depends on which USB port it is connected to. It charges fine (but probably slow) if connected to one of my two regular USB ports:
Code:
kernel: [192220.220540] usb 2-3: new high-speed USB device number 22 using xhci_hcd
kernel: [192220.369801] usb 2-3: New USB device found, idVendor=0e8d, idProduct=2000
kernel: [192220.369806] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
kernel: [192220.369809] usb 2-3: Product: MT65xx Preloader
kernel: [192220.369811] usb 2-3: Manufacturer: MediaTek
kernel: [192220.432288] cdc_acm 2-3:1.1: ttyACM0: USB ACM device
mtp-probe: checking bus 2, device 22: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-3"
mtp-probe: bus: 2, device: 22 was not an MTP device
upowerd[829]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.0
upowerd[829]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.1
upowerd[829]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-3
kernel: [192223.020572] usb 2-3: USB disconnect, device number 22
upowerd[829]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.0
upowerd[829]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.1
upowerd[829]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-3
but when it is connected to the powered USB port (the one with a battery icon carved next to it, it stays powered even if laptop is off) it goes in a loop like this:
Code:
kernel: [192371.848349] usb 2-1: new high-speed USB device number 24 using xhci_hcd
kernel: [192371.997647] usb 2-1: New USB device found, idVendor=0e8d, idProduct=2000
kernel: [192371.997649] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
kernel: [192371.997650] usb 2-1: Product: MT65xx Preloader
kernel: [192371.997651] usb 2-1: Manufacturer: MediaTek
kernel: [192372.059915] cdc_acm 2-1:1.1: ttyACM0: USB ACM device
mtp-probe: checking bus 2, device 24: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
mtp-probe: bus: 2, device: 24 was not an MTP device
upowerd[829]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0
upowerd[829]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.1
upowerd[829]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1
kernel: [192374.648476] usb 2-1: USB disconnect, device number 24
upowerd[829]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0
upowerd[829]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.1
upowerd[829]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1
kernel: [192384.960396] usb 2-1: new high-speed USB device number 25 using xhci_hcd
kernel: [192385.109725] usb 2-1: New USB device found, idVendor=0e8d, idProduct=2000
kernel: [192385.109731] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
kernel: [192385.109734] usb 2-1: Product: MT65xx Preloader
kernel: [192385.109737] usb 2-1: Manufacturer: MediaTek
kernel: [192385.172204] cdc_acm 2-1:1.1: ttyACM0: USB ACM device
mtp-probe: checking bus 2, device 25: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
mtp-probe: bus: 2, device: 25 was not an MTP device
upowerd[829]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0
upowerd[829]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.1
upowerd[829]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1
kernel: [192387.760370] usb 2-1: USB disconnect, device number 25
upowerd[829]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.1
upowerd[829]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0
upowerd[829]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1
kernel: [192398.032318] usb 2-1: new high-speed USB device number 26 using xhci_hcd
kernel: [192398.181511] usb 2-1: New USB device found, idVendor=0e8d, idProduct=2000
kernel: [192398.181516] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
kernel: [192398.181519] usb 2-1: Product: MT65xx Preloader
kernel: [192398.181521] usb 2-1: Manufacturer: MediaTek
kernel: [192398.243803] cdc_acm 2-1:1.1: ttyACM0: USB ACM device
mtp-probe: checking bus 2, device 26: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
mtp-probe: bus: 2, device: 26 was not an MTP device
upowerd[829]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0
upowerd[829]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.1
upowerd[829]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1
kernel: [192400.831870] usb 2-1: USB disconnect, device number 26
upowerd[829]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0
upowerd[829]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.1
upowerd[829]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1
on every "USB disconnect" a battery logo shwos up on the device's display, on every "new high-speed USB device" the display goes black
can this reconnecting loop be prevented somehow? I just want to charge my device, no intention to use preloader