SOLVED: defective otg cable
useful tools:
any android terminal emulator plus root
dmesg
lsusb
2nd otg cable
I cannot seem to get otg working with any of the various USB storage devices I have.
Any ideas on how I can debug this?
If it were normal Linux it would be easy enough, however it's not.
Any suggestions would be appreciated.
Running AOKP buttered right now but sentinel stock and paranoid all do not work either. So it might be a cable or the tablet even.
Hmm not sure but I wonder if the kernel with this rom is missing the fat kernel modules
Thanks
Sent from my Nexus 10 using xda premium
tazmeister said:
I cannot seem to get otg working with any of the various USB storage devices I have.
Click to expand...
Click to collapse
I had the same problems with rooted Stock and various custom ROMs. Try installing "USB OTG Helper [root]" then retest. This app helped get me RW access to OTG storage from SD cards to powered HDD drives in various formats (ext2,3,4 and NTFS).
It worked so well I paid for the donate version just to support the developer. It even has exFAT support although I never tried it. Personally I think it should be part of standard Android.
Have you checked "lsusb" or "udevadm" in terminal if the device recognizes anything?
KasF said:
Have you checked "lsusb" or "udevadm" in terminal if the device recognizes anything?
Click to expand...
Click to collapse
Thanks more commands to jog my memory and try
I installed a console app and can check dmesg and other stuff.
Lsmod and related seem to be mostly obsolete.
Dmesg shows something is seen but the system keeps failing after this.
I see the same messages regardless of which device I try, powered and unpowered.
<6>[ 6171.135316] s5p-ehci s5p-ehci: S5P EHCI Host Controller
<6>[ 6171.136622] s5p-ehci s5p-ehci: new USB bus registered, assigned bus number 1
<6>[ 6171.137173] s5p-ehci s5p-ehci: irq 103, io mem 0x12110000
<6>[ 6171.145031] s5p-ehci s5p-ehci: USB 0.0 started, EHCI 1.00
<6>[ 6171.145636] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
<6>[ 6171.146150] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[ 6171.146439] usb usb1: Product: S5P EHCI Host Controller
<6>[ 6171.146925] usb usb1: Manufacturer: Linux 3.4.5-gb44fbc0 ehci_hcd
<6>[ 6171.147202] usb usb1: SerialNumber: s5p-ehci
<6>[ 6171.150947] hub 1-0:1.0: USB hub found
<6>[ 6171.151298] hub 1-0:1.0: 3 ports detected
<6>[ 6171.153725] exynos-ohci exynos-ohci: EXYNOS OHCI Host Controller
<6>[ 6171.156783] exynos-ohci exynos-ohci: new USB bus registered, assigned bus number 2
<6>[ 6171.157031] exynos-ohci exynos-ohci: irq 103, io mem 0x12120000
<6>[ 6171.214330] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
<6>[ 6171.214522] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[ 6171.214630] usb usb2: Product: EXYNOS OHCI Host Controller
<6>[ 6171.214813] usb usb2: Manufacturer: Linux 3.4.5-gb44fbc0 ohci_hcd
<6>[ 6171.215052] usb usb2: SerialNumber: exynos-ohci
<6>[ 6171.220588] hub 2-0:1.0: USB hub found
<6>[ 6171.220946] hub 2-0:1.0: 3 ports detected
<6>[ 6171.225049] manta_otg manta_otg_work: b_idle -> a_host
<6>[ 6171.705161] usb 2-1: new full-speed USB device number 2 using exynos-ohci
<3>[ 6171.835100] usb 2-1: device descriptor read/64, error -62
<3>[ 6172.070121] usb 2-1: device descriptor read/64, error -62
<6>[ 6172.300093] usb 2-1: new full-speed USB device number 3 using exynos-ohci
<3>[ 6172.430142] usb 2-1: device descriptor read/64, error -62
<3>[ 6172.665754] usb 2-1: device descriptor read/64, error -62
<6>[ 6172.895140] usb 2-1: new full-speed USB device number 4 using exynos-ohci
<3>[ 6173.305043] usb 2-1: device not accepting address 4, error -62
<6>[ 6173.430032] usb 2-1: new full-speed USB device number 5 using exynos-ohci
<3>[ 6173.840038] usb 2-1: device not accepting address 5, error -62
<3>[ 6173.840490] hub 2-0:1.0: unable to enumerate USB device on port 1
Sent from my Nexus 10 using xda premium
None of the org helper apps have helped.
I don't think the org cable is bad though maybe this detail means otherwise
one device starts charging itself of the musb port when i plug it in.
Sent from my Nexus 10 using xda premium
KasF said:
Have you checked "lsusb" or "udevadm" in terminal if the device recognizes anything?
Click to expand...
Click to collapse
udevadm doesn't seem to be present but lsusb lists 2 devices when I have something plugged in.
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0001
Sent from my Nexus 10 using xda premium
ok problem solved.
The final debugging step was to "get another otg cable and test to make sure the first otg cable isn't defective"
Since I only owned a single OTG cable at the start, it was sort of difficult to perform this ultimate debug step.
But once I tried a different cable, almost everything worked just fine.
Only my 64gb micro-sd cards gave me a little trouble, but they all work now.
Related
Hi there,
I am trying to port this: engadget. com /2011 /09 /16 / brain-scanner-app-lets-you-show-off-your-smarts-on-the-go (I can't post links, sorry) to the Acer A500 with Android 3.1. This requires connecting the receiver to the tablet and reading raw binary data it feeds through the USB port.
The way it was done for the Nokia N900 was to compile the hidraw.ko kernel module and insmod it on the device. I thought it would be the same for Android. I did the following:
1) I downloaded the source code of the 2.6.36.3 kernel and the toolchains from github
2) I pulled the default config from the device
3) Changed
Code:
#CONFIG_HIDRAW is not set
to
Code:
CONFIG_HIDRAW=y
and
Code:
CONFIG_USB_HID=y
4) Compiled modules with cross compilation
5) got only usbhid.ko and some other irrelevant modules but no hidraw.ko
6) Could not even insmod usbhid.ko, because it is already loaded. Could not rmmod the current usbhid.ko (I do have root).
7) When I plug the receiver into the USB port it is recognized, but then the dmesg says:
Code:
<6>[ 1591.572355] usb 1-1: new full speed USB device using tegra-ehci and address 2
<6>[ 1593.633364] usb 1-1: New USB device found, idVendor=1234, idProduct=ed02
<6>[ 1593.634022] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 1593.634377] usb 1-1: Product: Receiver Dongle L01
<6>[ 1593.635002] usb 1-1: Manufacturer: Emotiv Systems Pty Ltd
<6>[ 1593.635350] usb 1-1: SerialNumber: SNXXXXXXXXXXXXXX
<3>[ 1593.651672] generic-usb 0003:1234:ED02.0001: claimed by neither input, hiddev nor hidraw
<3>[ 1593.662383] generic-usb 0003:1234:ED02.0002: claimed by neither input, hiddev nor hidraw
Finally the question is:
How to enable HIDRAW on the Acer A500 and get this thing to work?
Hi
I recently rooted and installed the CM9 based ICS ROM on Kindle Fire. It works very good. Now I am trying to get it working with the Android Accessory Development Kit (in either of the two modes - accessory or host). Unfortunately I havent been able to get it working. Can somebody confirm if the ROM has USB support enabled or is it still work in progress?
Thanks
Pankaj
The Rom has a bug that disables it...
You will need to mount it in TWRP to transfer files to the Kindle.
Everything else doesn't work, Including the aadk.
That is USB "client." Which as you said is broken in the current ICS ROMS.
USB "Host" is the ability to attach devices like drives and keyboards. This is not functional in Stock, CM7 and ICS.
jfb9301 said:
That is USB "client." Which as you said is broken in the current ICS ROMS.
USB "Host" is the ability to attach devices like drives and keyboards. This is not functional in Stock, CM7 and ICS.
Click to expand...
Click to collapse
USB Host is in ICS.
http://9to5google.com/2011/10/24/an...sb-hosting-brings-gamepadscontrollers-to-all/
engagedtosmile said:
USB Host is in ICS.
Click to expand...
Click to collapse
Yes, it is in ICS. Infact Host Mode support is there from HC 3.1 onwards. What I wanted to know was if its enabled in the CM9 based ICS ROM for Kindle Fire too. I tried but it doesnt seem to.
Kindle Fire OTG Working - First Signs
Hi
I can't post to the Dev threads but using the 17 Jan Kernel build by intersectRaven with the CM9 based ROM, this is what I get in dmesg finally. I have a powered USB hub connected using an OTG cable:
<6>[ 0.020874] usbcore: registered new interface driver usbfs
<6>[ 0.021209] usbcore: registered new interface driver hub
<6>[ 0.021423] usbcore: registered new device driver usb
<6>[ 0.076232] musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0
<7>[ 0.076538] musb_hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
<7>[ 0.076660] musb_hdrc: MHDRC RTL version 2.0
<7>[ 0.076751] musb_hdrc: setup fifo_mode 4
<7>[ 0.076904] musb_hdrc: 28/31 max ep, 16384/16384 memory
<6>[ 0.077056] musb_hdrc musb_hdrc: USB OTG mode controller at fc0ab000 using DMA, IRQ 124
<6>[ 1.704711] musb_hdrc musb_hdrc: MUSB HDRC host driver
<7>[ 1.710266] drivers/usb/core/inode.c: creating file 'devices'
<7>[ 1.716461] drivers/usb/core/inode.c: creating file '001'
<6>[ 1.722198] musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
<7>[ 1.730010] usb usb1: default language 0x0409
<7>[ 1.734680] usb usb1: udev 1, busnum 1, minor = 0
<6>[ 1.739776] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
<6>[ 1.746978] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[ 1.754730] usb usb1: Product: MUSB HDRC host driver
<6>[ 1.760009] usb usb1: Manufacturer: Linux 2.6.35.7+ musb-hcd
<6>[ 1.766113] usb usb1: SerialNumber: musb_hdrc
<7>[ 1.771240] usb usb1: usb_probe_device
<7>[ 1.775329] usb usb1: configuration #1 chosen from 1 choice
<7>[ 1.781280] usb usb1: adding 1-0:1.0 (config #1, interface 0)
<7>[ 1.787689] hub 1-0:1.0: usb_probe_interface
<7>[ 1.792236] hub 1-0:1.0: usb_probe_interface - got id
<6>[ 1.797637] hub 1-0:1.0: USB hub found
<6>[ 1.801727] hub 1-0:1.0: 1 port detected
<7>[ 1.805938] hub 1-0:1.0: standalone hub
<7>[ 1.810058] hub 1-0:1.0: individual port power switching
<7>[ 1.815795] hub 1-0:1.0: no over-current protection
<7>[ 1.820983] hub 1-0:1.0: power on to power good time: 10ms
<7>[ 1.826904] hub 1-0:1.0: 100mA bus power budget for each child
<7>[ 1.833099] hub 1-0:1.0: local power source is good
<7>[ 1.838378] hub 1-0:1.0: enabling power on all ports
<7>[ 1.843933] drivers/usb/core/inode.c: creating file '001'
<6>[ 2.309783] usbcore: registered new interface driver usbhid
<6>[ 2.315826] usbhid: USB HID core driver
<7>[ 4.811706] hub 1-0:1.0: hub_suspend
<7>[ 4.815551] usb usb1: bus auto-suspend
So these are definite clues that Kindle Fire has OTG working with the the custom kernel build. Unfortunately the last 2 lines above from dmesg are not good as both the hub and usb go to suspend state.
Can somebody help me get these findings over to the intersectRaven's Dev thread on custom kernel.
Can't really help anymore then to offer this note.
In my pursuit of full market access I stumbled upon these features.
<feature name="android.hardware.usb.host" />
<feature name="android.hardware.usb.accessory" />
You may need those in your /system/etc/permissions/tablet_core_hardware.xml at some point.
Is it possible to get this working on the Acer A500 with the ICS leak? I've been able to use it on all 3.2 ROMs and Thors ICS, but when moving to the leak it will not execute "usb_ethernet", it recognizes it as a command but no output is shown. system is set to RW but it still doesn't load.
Just curious.
Thanks everyone!
On the ICS roms, usb1 is not showing up as a network interface
When I look at my dmesg, it shows "USB Ethernet Ver .2" but never loads the ASISX driver.
On Thors ICS it registers "asix 1-1.0: eth0: register "asix" at usb-tegra-ehci.2-1, ASIX AX8877 USB 2.0 Ethernet"
Perhaps its due to the leaked builds using the stock kernel?
I'm using Flexreaper R10 and here is what I get
I flashed the zip provided HERE
I insert the USB adapter and dmesg shows
Code:
<6>[ 146.691880] usb 1-1.3: new high speed USB device number 5 using tegra-ehci
<6>[ 146.763606] usb 1-1.3: New USB device found, idVendor=13b1, idProduct=0018
<6>[ 146.691880] usb 1-1.3: new high speed USB device number 5 using tegra-ehci
<6>[ 146.763606] usb 1-1.3: New USB device found, idVendor=13b1, idProduct=0018
<6>[ 146.764309] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 146.764980] usb 1-1.3: Product: USB 2.0 Network Adapter ver.2
<6>[ 146.765345] usb 1-1.3: Manufacturer:
<6>[ 146.765721] usb 1-1.3: SerialNumber: 01E821 device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 146.764980] usb 1-1.3: Product: USB 2.0 Network Adapter ver.2
<6>[ 146.765345] usb 1-1.3: Manufacturer:
<6>[ 146.765721] usb 1-1.3: SerialNumber: 01E821
I try to manually load the module I need, "asix410.ko" and I get
Code:
<3>[ 463.740506] asix410: version magic '2.6.36.3 SMP preempt mod_unload ARMv7 ' should be '2.6.39.4+ SMP preempt mod_unload ARMv7 '
Any ideas?
I see that it says that the kernel is not the proper version, but I was under the impression that as log as the kernel is 2.6.39.x, this driver should work.
Thanks!
Try using a hex editor to change the version info in the .ko file to match what the system is expecting and give it a try. I've done that successfully before with a cifs.ko module.
saeba said:
Try using a hex editor to change the version info in the .ko file to match what the system is expecting and give it a try. I've done that successfully before with a cifs.ko module.
Click to expand...
Click to collapse
I did that, having seen you do that with cifs, but the kernel is was made for has like 6 characters whereas this one has 7, so because of that the kernel finds that there is a mismatch and STILL won't load the module.
Some times ago I bought a made-in-china usb to ethernet adapter for my Nexus 7 tilapia with CM 10, and it worked well.
Now it doesn't work anymore, and I supposed it's adapter fault. So I bought a usb-to-lan adapter by Lindy. It does not work as well.
How can I say for sure it's tablet or adapter fault?
up.
You'd probably get answers if you posted to your devices forums, this is for the N7 2013 (flo and deb).
As for how, I'd imagine you can see in the logs.
EDIT: It appears a helpful mod has moved it to the right section.
I can't find the tilapia section. Is there not one section for older models?
I get this log from dmesg. It seems that device is recognized. It doesn't report any error, but it don't work. Even the adapter leds doesn't light up.
Code:
tegra-otg tegra-otg: SUSPEND --> HOST
phy->instance = 0, phy->xcvr_setup_value = 58
create_regulator: fixed_reg_en_avdd_hdmi_usb_a01: Failed to create debugfs directory
tegra_usb_phy_open instance 0 MAX77663_IRQ_ACOK_RISING
tegra-ehci tegra-ehci.0: Tegra EHCI Host Controller
tegra-ehci tegra-ehci.0: new USB bus registered, assigned bus number 2
tegra-ehci tegra-ehci.0: irq 52, io mem 0x7d000000
tegra-ehci tegra-ehci.0: USB 2.0 started, EHCI 1.00
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: Tegra EHCI Host Controller
usb usb2: Manufacturer: Linux 3.1.10-g30c5396 ehci_hcd
usb usb2: SerialNumber: tegra-ehci.0
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
Wake39 for irq=52
Enabling wake39
INOK=L
smb347_charger: [cable_type_detect] Reg39 : 0x11
smb347_charger: [cable_type_detect] Reg3F : 0x00
USBIN=0
tegra_ehci_irq: no device connected before suspend
tegra-otg tegra-otg: HOST --> SUSPEND
Wake39 for irq=52
Disabling wake39
tegra-ehci tegra-ehci.0: remove, state 4
usb usb2: USB disconnect, device number 1
tegra-ehci tegra-ehci.0: USB bus 2 deregistered
tegra-otg tegra-otg: SUSPEND --> SUSPEND
INOK=H
========================================================
battery_callback usb_cable_state = 0
========================================================
Lucas Malor said:
I can't find the tilapia section. Is there not one section for older models?
I get this log from dmesg:
PHP:
tegra-otg tegra-otg: SUSPEND --> HOST
phy->instance = 0, phy->xcvr_setup_value = 58
create_regulator: fixed_reg_en_avdd_hdmi_usb_a01: Failed to create debugfs directory
tegra_usb_phy_open instance 0 MAX77663_IRQ_ACOK_RISING
tegra-ehci tegra-ehci.0: Tegra EHCI Host Controller
tegra-ehci tegra-ehci.0: new USB bus registered, assigned bus number 2
tegra-ehci tegra-ehci.0: irq 52, io mem 0x7d000000
tegra-ehci tegra-ehci.0: USB 2.0 started, EHCI 1.00
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: Tegra EHCI Host Controller
usb usb2: Manufacturer: Linux 3.1.10-g30c5396 ehci_hcd
usb usb2: SerialNumber: tegra-ehci.0
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
Wake39 for irq=52
Enabling wake39
INOK=L
smb347_charger: [cable_type_detect] Reg39 : 0x11
smb347_charger: [cable_type_detect] Reg3F : 0x00
USBIN=0
tegra_ehci_irq: no device connected before suspend
tegra-otg tegra-otg: HOST --> SUSPEND
Wake39 for irq=52
Disabling wake39
tegra-ehci tegra-ehci.0: remove, state 4
usb usb2: USB disconnect, device number 1
tegra-ehci tegra-ehci.0: USB bus 2 deregistered
tegra-otg tegra-otg: SUSPEND --> SUSPEND
INOK=H
========================================================
battery_callback usb_cable_state = 0
========================================================
It seems that device is recognized. It doesn't report any error, but it don't work. Even the adapter leds doesn't light up.
Click to expand...
Click to collapse
Looks like a mod moved it into the right section, your post is now in the correct area, for future reference this is the link to the N7 2012 section.
As for the issue at hand, it's possible the USB port is dirty or the cable is dirty or damaged.
mdamaged said:
for future reference this is the link to the N7 2012 section.
Click to expand...
Click to collapse
Good, thank you.
mdamaged said:
it's possible the USB port is dirty or the cable is dirty or damaged.
Click to expand...
Click to collapse
Well, it could be the cable, but it's a brand new item and the adapter is recognized. I think the port is ok, I can connect the device to my PC.
Lucas Malor said:
Good, thank you.
Well, it could be the cable, but it's a brand new item and the adapter is recognized. I think the port is ok, I can connect the device to my PC.
Click to expand...
Click to collapse
Assuming you know for sure your device has a driver for that adapter, maybe the adapter is just poorly made, or you may have to do some additional setup steps in a shell to get it to come up.
I don't know if there are no compatible drivers. The official site says the adapter is compatible with Linux, and it does not provide any drivers. And it says it can be used with tablets. But I just noticed it doesn't say it's compatible with Android. Yes, it's Linux, but it's a completely different implementation... and furthermore it doesn't say it can be used with smartphones. So I start to think this damned adapter is not compatible with ARM architectures...
USB debugging on Linux
Maybe it's just me being blind, but does anyone have `adb` working on Linux? Device ID shows up as 0fca, and I've added this to my udev rules, but still no device. Notification shows "USB debugging connected - Touch to disable USB debugging" with "Media device (MTP)" and "Camera (PTP)" USB connections.
Code:
07:32:04 ~$ lsusb |grep Research
Bus 001 Device 003: ID 0fca:8032 Research In Motion, Ltd.
Code:
[ 397.648593] usb 1-1: new high-speed USB device number 3 using ehci-pci
[ 397.920791] usb 1-1: New USB device found, idVendor=0fca, idProduct=8032
[ 397.920796] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 397.920798] usb 1-1: Product: BlackBerry
[ 397.920799] usb 1-1: Manufacturer: BlackBerry
[ 397.920801] usb 1-1: SerialNumber: <x>
Code:
07:39:49 ~$ adb devices
List of devices attached
Thanks!
Figured it out. My Linux environment (Ubuntu 14) had the package 'android-tools-adb' installed, but that version of `adb` doesn't seem to work. The `adb` binary with the SDK tools works fine. I removed the 'android-tools-adb' and all is well again. :laugh: