My device supports OTG but OS doesn't - Android Q&A, Help & Troubleshooting

Hello,
I was trying to develop an app that uses USB Host/Accessory mode to communicate with a python script on another linux device (for now it's my PC). I noticed that getAccessoryList() and getDeviceList() both return null/empty and after searching a lot I came across USB Host Diagnostics from chainfire.
And when I tried it this was the result: usbhost(dot)chainfire(dot)eu/?search=1382824
As you can see, the kernel supports OTG while the OS doesn't. My devices are Samsung S5 and Note 8.0 and both gave the same exact results. My devices are rooted but that was the only modification i've done to them.
So is there a way to fix this issue ?
Thanks in advance.

Related

[Q] OTG USB not working on a supported Oppo phone

First let me say that I am not permitted to post this question on the thread that relates to custom roms for the Oppo Muse Find R821, since I am not a developer .
The named phone has hardware capability to act as USB host but USB Diagnostics report that the kernel (I am using the original ROM) does not support it.
Is there any way to modify the rom to get it to recognize USB devices, as a host?
Or any patch/addition to the ROM that will enable this function?
Perhaps something I can install as a zip in recovery mode.
Or maybe there is a custom rom for this phone that activates the OTG capability?
I know that the phone will automatically recognize a USB stick if the hardware can do it, if the kernel allows it and if the correct OTG cable is used.
The only thing lacking now is the software.

[Q] USB Device not recognized (CM13 - CM12.1)

Hey,
I have been using CM12.1 Nightlies since January, and I've been experiencing bugs related to USB recognition. Yesterday I've updated to CM13 thinking that it would solve this issue, but it haven't.
What happens is that I can't use USB storage/MTP/Odin/direct plug adb because my phone doesn't get recognized by the OS. I think that the USB port is not damaged because I can charge it when connected to my PC . I used to have CM11 and it worked fine, I think that maybe it is something related to the build itself..?
I have already tried a lot of methods, USB debug on/off, different cords, OSes (Tried on Windows, Mac, Linux), multiple adb/samsung drivers, apps.. nothing has worked so far.
I can only access the internal data using an external SD card or through network adb.
I think that the USB module was overwritten, because it looks undentified in every device that I've tested.
Has anyone experienced something like that? any tips, tests, or patches that I've missed?
Thanks.
Did you install Google USB Driver? I had to install this one to get my device on CM 13 recognized. It should work "out-of-the-box" on Linux distros though if you've got libmtp installed (for MTP browsing).
matee89 said:
Did you install Google USB Driver? I had to install this one to get my device on CM 13 recognized. It should work "out-of-the-box" on Linux distros though if you've got libmtp installed (for MTP browsing).
Click to expand...
Click to collapse
The device doesn't get recognized by Windows, it doesn't even show up on the connected devices list. The funny thing is that the phone actually charges, so it is not a dead usb connection...
I think that I'll have to replace the USB PCB...
Hello,
i tried to flash twrp to my i9100.
I had cm12.1 with cyanogen recovery and tried to apply update for :
"recovery-Lanchon-IsoRec-TWRP-2.8.7.0-20160113-i9100-(by-arnab)"
and
"kernel-Lanchon-TRIM-IsoRec-20160207-cm-13.0-i9100"
but know my phone is not starting anymore.
I already know that i used 13 kernel for 12.1 system and that was wrong.
I can access ODIN Mode but my pc (win10) and Odin v.3.10 don´t recognize my S2.
Can you tell me how to solve my problem?
i9100cm said:
Hello,
I can access ODIN Mode but my pc (win10) and Odin v.3.10 don´t recognize my S2.
Can you tell me how to solve my problem?
Click to expand...
Click to collapse
Try reinstalling Samsung USB drivers. If that didn't work then try it on another computer.
Now my S2 is getting recognized again.
But i geht the error code 43.
The device description is failured.
Kevin3014 said:
Try reinstalling Samsung USB drivers. If that didn't work then try it on another computer.
Click to expand...
Click to collapse
Kevin, how to flash lanchon kernel without recovery?
because my recovery is cyanogenmod recovery cm13 it cannot update from sdcard..
Abdullah Yusoff said:
Kevin, how to flash lanchon kernel without recovery?
because my recovery is cyanogenmod recovery cm13 it cannot update from sdcard..
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...es/guide-want-to-update-to-cm13-read-t3313978
Read this thread, it has the answer to your question.
Hey, OP here.
So just updating my status, I bought and replaced the Micro-USB connector and everything is working now, the device is recognized by the OS and I'm able to use use Odin/ADB normally.
If anyone out there is having the same issue, I recommend buying a new Micro-USB PCB. This phone is from 2011, batteries and connectors might stop working...
Thanks everyone for helping me out!
Thyrr said:
Hey,
I have been using CM12.1 Nightlies since January, and I've been experiencing bugs related to USB recognition. Yesterday I've updated to CM13 thinking that it would solve this issue, but it haven't.
What happens is that I can't use USB storage/MTP/Odin/direct plug adb because my phone doesn't get recognized by the OS. I think that the USB port is not damaged because I can charge it when connected to my PC . I used to have CM11 and it worked fine, I think that maybe it is something related to the build itself..?
I have already tried a lot of methods, USB debug on/off, different cords, OSes (Tried on Windows, Mac, Linux), multiple adb/samsung drivers, apps.. nothing has worked so far.
I can only access the internal data using an external SD card or through network adb.
I think that the USB module was overwritten, because it looks undentified in every device that I've tested.
Has anyone experienced something like that? any tips, tests, or patches that I've missed?
Thanks.
Click to expand...
Click to collapse
hey..if no method works for you i have simple way..to turn on usb debugging and for odin (means from this way odin will recognose your mobile)...just flash the new simple custom rom with lower android versions and then turn on usb debuging mode....thats all ...i also strucked in this problem but i did this and all works fine...sry for my bad english and typing

[Q] Please Help! USB OTG Not Working on Blackview Ultra A6

So I tried using OTG devices with the Blackview Ultra with both the stock rom and CyanogenMod 12.1 installed but it just doesn't work. I have tried multiple USB OTG cables and none have worked, I know it is not the cable because it works fine with my friends phone. I have also run USB Host Diagnostics on the phone and it says that the OS supports OTG but simply no device is detected.
The bizarre thing is that the Ultra itself claims OTG support. It even comes with an OTG cable included in the box!
So if anyone could give me some insight on this it would be greatly appreciated. I really want to see some USB devices working with my phone. Thank you!
Bump
Anyone?

S6 Edge USB problem

Hi everyone,
Had this problem for a while now, my Samsung S6 Edge performed an overnight update to Android 7.0 and ever since the USB port does not work for data transfers. Charging works fine. Also Samsung GEAR VR doesn't work.
I had the port replaced twice, no change. I tried three different windows based PCs different cables everything reinstalled the driver, even tried a Mac computer, and still not working
OTG devices also don't work.
I think its a corrupt android partition maybe but the problem is I can't flash another android ROM onto it because ODIN doesn't see the phone either (lol)
Is there any way of getting android flashed on it another way? I would be happy to try a custom ROM if I could figure out how to flash it
Also the phone isn't rooted unfortunately
Many thanks Paul
paulds3uk said:
Hi everyone,
Had this problem for a while now, my Samsung S6 Edge performed an overnight update to Android 7.0 and ever since the USB port does not work for data transfers. Charging works fine. Also Samsung GEAR VR doesn't work.
I had the port replaced twice, no change. I tried three different windows based PCs different cables everything reinstalled the driver, even tried a Mac computer, and still not working
OTG devices also don't work.
I think its a corrupt android partition maybe but the problem is I can't flash another android ROM onto it because ODIN doesn't see the phone either (lol)
Is there any way of getting android flashed on it another way? I would be happy to try a custom ROM if I could figure out how to flash it
Also the phone isn't rooted unfortunately
Many thanks Paul
Click to expand...
Click to collapse
Go to developer options and then change USB configuration. Try that see if it helps.
I'm at the same boat pls if you solve this problem tell me how

HDX 7 TWRP, no os, no ADB access [Lineage OS]

Ok, I need to load an OS back to the device ( wiped data/system because girlfriend enabled encryption.....) anyway I've tried the same computer I rooted the thing 2 years ago, installed new drivers and also am in test mode, however
the hdx (when booted into TWRP) never shows up in device manager, and "adb devices" is always empty. I've tried several USB cables, and even a mac computer, anyone lose access to their device and got it back? Any hints?
cq_ said:
Ok, I need to load an OS back to the device ( wiped data/system because girlfriend enabled encryption.....) anyway I've tried the same computer I rooted the thing 2 years ago, installed new drivers and also am in test mode, however
the hdx (when booted into TWRP) never shows up in device manager, and "adb devices" is always empty. I've tried several USB cables, and even a mac computer, anyone lose access to their device and got it back? Any hints?
Click to expand...
Click to collapse
First verify drivers are working. For whatever reason legacy composite drivers from Motorola seem to work best with this device regardless of platform or host OS. Install the Motorola Device Manager from this page and then switch drivers. No need to launch the utility.
TWRP must be at v2.7 or above for ADB support. If below 2.8.6.0 you should consider updating via fastboot assuming bootloader has been unlocked. See: https://forum.xda-developers.com/kindle-fire-hdx/development/recovery-twrp-3-0-0-0-t3322547
If still no joy you will have to erase/replace aboot and rebuild the device from scratch. Data loss is likely.
hmm yeah, the main problem seems to be the tablet never shows up in device manager as any device... thanks for the hints though, will try the motorola device manager drivers...
cq_ said:
Ok, I need to load an OS back to the device ( wiped data/system because girlfriend enabled encryption.....) anyway I've tried the same computer I rooted the thing 2 years ago, installed new drivers and also am in test mode, however
the hdx (when booted into TWRP) never shows up in device manager, and "adb devices" is always empty. I've tried several USB cables, and even a mac computer, anyone lose access to their device and got it back? Any hints?
Click to expand...
Click to collapse
Where'd you get the drivers from? Can you share a link to the ones you installed on your PC? In control panel devices have you tried enabling show hidden devices to see if the tablet is detected but not enabled? What version of Windows?
I haven't tried this yet personally yet but I'm wondering if a live Linux (e.g. Mint) booted on USB thumb drive might be an option. I don't know enough about using a Mac to access the Kindle to offer much in detail there. Have you tried different USB ports on each of these computers? Do other USB devices show up okay?
fufu508 said:
Where'd you get the drivers from? Can you share a link to the ones you installed on your PC? In control panel devices have you tried enabling show hidden devices to see if the tablet is detected but not enabled? What version of Windows?
I haven't tried this yet personally yet but I'm wondering if a live Linux (e.g. Mint) booted on USB thumb drive might be an option. I don't know enough about using a Mac to access the Kindle to offer much in detail there. Have you tried different USB ports on each of these computers? Do other USB devices show up okay?
Click to expand...
Click to collapse
Read here literally two posts above yours. Where was Linux/Mac ever mentioned? Connectivity on Windows almost always boils down to procedures, drivers and/or USB cable integrity. Assuming the device itself is not toast.
fufu508 said:
In control panel devices have you tried enabling show hidden devices to see if the tablet is detected but not enabled?
Click to expand...
Click to collapse
Oh snap, this is a good idea - will try when I get home.
TWRP 3.1.1-1, Win 10 64bit - yeah tested several usb ports on my computer - I originally rooted the HDX with this computer and windows 10 install about 2 years ago [side note do you guys remember reformatting every 6 months because windows was such a pos, I'm really glad those days are long gone!]
LOL yep Windows 10 nowadays does seem a lot more stable than the earlier stuff.
---------- Post added at 06:14 PM ---------- Previous post was at 05:50 PM ----------
Davey126 said:
Read here literally two posts above yours. Where was Linux/Mac ever mentioned? Connectivity on Windows almost always boils down to procedures, drivers and/or USB cable integrity. Assuming the device itself is not toast.
Click to expand...
Click to collapse
Hi Davey oops somehow I missed that you had already replied a few days ago . cq_ did mention a Mac computer. I suggested testing with a live Linux thumb drive boot in case they have an extra thumb drive kicking around to find out what that OS sees as compared to the Windows and Mac already tried. When reviving my Thor, part of the process I tried was draxie's 1-click, which required Linux and access to the device to do its work, so it seemed like a good to me to try to boot the PC that cq_ is using into Linux. In my case I have Linux Mint installed on a separate SATA hard drive but not everybody has that type of rig, hence the live Linux USB thumb drive boot suggestion.
fufu508 said:
Hi Davey oops somehow I missed that you had already replied a few days ago . cq_ did mention a Mac computer. I suggested testing with a live Linux thumb drive boot in case they have an extra thumb drive kicking around to find out what that OS sees as compared to the Windows and Mac already tried. When reviving my Thor, part of the process I tried was draxie's 1-click, which required Linux and access to the device to do its work, so it seemed like a good to me to try to boot the PC that cq_ is using into Linux. In my case I have Linux Mint installed on a separate SATA hard drive but not everybody has that type of rig, hence the live Linux USB thumb drive boot suggestion.
Click to expand...
Click to collapse
Fair enough; I may have been a bit harsh in my response. I now see the passing reference to an Apple rig and appreciate the unfiltered perspective often obtained via Linux. That said, there is new info on the table that suggests the OP has access to a Win10x64 box which should connect effortlessly/reliably with Moto drivers and a quality USB cable. Mucking with drivers can be a PiTA on Windows; the Moto variants remove much of the pain - although you still have to select the proper driver after tethering in the target mode (adb or fastboot) as Windows will typically default to Microsoft/stock variants which rarely work with HDX devices.

Categories

Resources