TL;DR: I am looking for some info from developers on which Xoom tablets running which tablets *fully* support Android USB Host API and whether I can reflash a EU-shipped device with the these img's.
Can a kernel be patched to fully support USB Host API?
--
I have a Motorola Xoom tablet that was originally shipped with MZ601 software (EU). I am trying to get it to work with a USB HID device. My code works well until I want to transfer data using controlTransfer - it then returns -1 as if there was no device connected (although the USB device was detected before by my code, using Host API).
I did some research and it turns out that US-shipped Xooms support Host API and that there was a guy who flashed the device to US MZ604. I did the same but the software img provided by Motorola was Android 3.0 which doesn't support Host API by default. I then tried to update this to 3.1 and 3.2 but it didn't work (tried with many copies, hazard triangle appears in the middle of installation process). Tried with rooted device.
I am now looking for any other software/ROM that proved to support USB Host API.
I would also like to know if in general Xoom tablets have hardware USB OTG support (meaning: whether flashing my device with a specific ROM should work).
Here you can find list of Android devices that was checked if they support USB Host API:
usbhost.chainfire.eu (based on USB Device Info app that lets you submit info after checking for Host API support). Most of Xoom devices are fully supporting Host API.
Thank you very much for taking on this project. Looking forward to the first release.
Sent from my Galaxy Nexus
ews said:
TL;DR: I am looking for some info from developers on which Xoom tablets running which tablets *fully* support Android USB Host API and whether I can reflash a EU-shipped device with the these img's.
Can a kernel be patched to fully support USB Host API?
--
I have a Motorola Xoom tablet that was originally shipped with MZ601 software (EU). I am trying to get it to work with a USB HID device. My code works well until I want to transfer data using controlTransfer - it then returns -1 as if there was no device connected (although the USB device was detected before by my code, using Host API).
I did some research and it turns out that US-shipped Xooms support Host API and that there was a guy who flashed the device to US MZ604. I did the same but the software img provided by Motorola was Android 3.0 which doesn't support Host API by default. I then tried to update this to 3.1 and 3.2 but it didn't work (tried with many copies, hazard triangle appears in the middle of installation process). Tried with rooted device.
I am now looking for any other software/ROM that proved to support USB Host API.
I would also like to know if in general Xoom tablets have hardware USB OTG support (meaning: whether flashing my device with a specific ROM should work).
Here you can find list of Android devices that was checked if they support USB Host API:
usbhost.chainfire.eu (based on USB Device Info app that lets you submit info after checking for Host API support). Most of Xoom devices are fully supporting Host API.
Click to expand...
Click to collapse
Look in the Development section and you should find a number of possibilities. If you look in my signature you will see the configuration that I'm running with success and I have full USB host capabilities (must use proven OTG cable, usually need a third party app like Drive Mount to successfully mount my HDD, but thumb drives mount just fine automatically on the EOS roms). Check out the long and rambling guide in my sig. as there is a bit of info on why you kept getting the error when in process of flashing recovery...
Thank you. In the meantime I've found an easy solution which works just fine. AFAIK the best choice if you want to have USB Host API support is to install the original MZ604 Android Honeycomb 3.0 software (downloaded from Motodev) and then update it to ICS. Then root the device (after applying few software updates).
Hi all
Wondering if anybody else has noticed that OTG/usb host is not detecting devices in the latest CM nightly. "USB Host Diagnostics" app reports:
Android Api:
-Claims support: yes
-Classes found: yes
-Device detected: no
Rooted API:
-Claims support: N/A
Device detected: N/A
Kernel:
-Claims support: yes
-Device detected: no
Verdict:
-OS support: no
3rd party apps: no
I am currently running cm-10.1-20130713-NIGHTLY-evita.zip (kernel 3.4.10-g1cfaa2d). Do I need to install something else? I tried "USB OTG Helper" and "Stickdroid" but no joy.
I was using cm-10.1-20130304-EXPERIMENTAL-evita-M2.zip (kernel 3.0) last week and OTG was working just fine, but there were other issues that I was hoping would be fixed in the nightly. Also, i noticed that logcat does not appear to be written to at all. I installed aLogcat app and all it contains is:
---------beginning of /dev/log/main
W/InputEventReceiver(18566): Attempted to finish an input event but the input event receiver has already been disposed
I really like CyanogenMod, but am finding a number of issues with the 10.1 builds (I realise that they are unstable):
OTG not working in latest nightly
device encryption not working (apparently broken on all ROMs for now)
USB mount dialog window shows even when screen pin locked and allows full sdcard access
media player (winamp/apollo) works fine in foreground, dies within a few seconds of going background
My evita is hboot 2.14, S-Off, SuperCID, TWRP 2.3.0.0
Cheers,
Coffman
Sorry, just realised I posted this in the wrong forum. If a mod could move it to Q&A I would be most grateful.
Thanks and sorry for the slip-up.
Hi, I have an iPhone 5 clone which I cannot connect to my pc. (Win 7 64/32 bit) When I plugged it in, it detects as "Unknown Device" in USB controllers category in Device Manager. I've tried a bunch of MTK 65xx drivers, ADB drivers, Install from disk (.inf file), even tried Pda.Net but still can't install the usb drivers.
I've also tried to power it off then press Volume + then plugged it. (SD card removed, battery cannot remove because it's soldered) It detects as MTK USB Port but it never detects as MTK 65xx Preloader as to what I've searched.
I am so frustrated and I really really want to connect this to my pc so I can start flashing on it.
I hope you can help me with this guys.
model: MT6517
board: sanstar15_2006_p5_gb2
manufacturer: ALPS
CPU: ARM Cortex-A9
RAM: 233 MB
hardware: MT6575
Android Version: 4.1.2 (but I can tell it's Gingerbread)
Kernel Arch: armv71
Kernel Version: 2.6.35.7
Hello all, I've been trying to root my Droid Maxx 4.4.4 SU6-7 and was working fine until after bricking it, I was unable to run the RUN_Root.bat. I'm running Windows 7 64 bit. This is the error I would get in the command prompt after trying to run RUN_Root.bat .
C:\Python27>python qdloadRoot.py MPRG8960.bin -ptf _root/partitions.txt
QDLoad utility version 1.2 (c) VBlack 2014
Found TTY port: com9
Requesting Params...
Params:
Version: 8
Min version: 1
Max write size: 1536 (0x00000600)
Model: 144
Device size: Invalid or unrecognized Flash device, or Flash device programming not supported by this implementation
Device type: Intel 28F400BX-TL or Intel 28F400BV-TL
Requesting SoftwareVersion...
Version: PBL_DloadVER2.0
Requesting SerialNumber...
Serial number: 00,00,48,03
Requesting HW Id...
HW Id: 00,00,48,03,e1,10,7e,00
Requesting PublicKey...
PublicKey: 39,c4,ee,3e,b5,be,eb,87,8e,2f,e3,b8,53,4d,14,6f,91 ,ca,fd,bb,94,2a,0d,aa,d0,1e,b0,87,62,d4,b9,b8
Uploading file 'MPRG8960.bin' to addr 0x2a000000...
Executing...
Could not find Qualcomm device in Emergency download mode
Done, with errors!!!
C:\Python27>pause
Press any key to continue . . .
I can still use the USB I think. I see Qualcomm HS-USB Loader 9008 (COM9) in the device manager whenever I would plug in the USB and it was manually updated after I selected x64 folder from the windows_drivers_QHSUSB_DLOAD folder(windows would say it was up to date when selecting x64 folder). I tried different ports but the Port otion never shows up for them in the device manager. I'm also not using USB 3.0.
I believe I followed every other instruction as far as I know from this thread http://forum.xda-developers.com/droid-ultra/general/droid-mini-maxx-ultra-root-pogress-100-t3071609 I'd really appreciate if someone could help me out.
Phoop said:
Hello all, I've been trying to root my Droid Maxx 4.4.4 SU6-7 and was working fine until after bricking it, I was unable to run the RUN_Root.bat. I'm running Windows 7 64 bit. This is the error I would get in the command prompt after trying to run RUN_Root.bat .
C:\Python27>python qdloadRoot.py MPRG8960.bin -ptf _root/partitions.txt
QDLoad utility version 1.2 (c) VBlack 2014
Found TTY port: com9
Requesting Params...
Params:
Version: 8
Min version: 1
Max write size: 1536 (0x00000600)
Model: 144
Device size: Invalid or unrecognized Flash device, or Flash device programming not supported by this implementation
Device type: Intel 28F400BX-TL or Intel 28F400BV-TL
Requesting SoftwareVersion...
Version: PBL_DloadVER2.0
Requesting SerialNumber...
Serial number: 00,00,48,03
Requesting HW Id...
HW Id: 00,00,48,03,e1,10,7e,00
Requesting PublicKey...
PublicKey: 39,c4,ee,3e,b5,be,eb,87,8e,2f,e3,b8,53,4d,14,6f,91 ,ca,fd,bb,94,2a,0d,aa,d0,1e,b0,87,62,d4,b9,b8
Uploading file 'MPRG8960.bin' to addr 0x2a000000...
Executing...
Could not find Qualcomm device in Emergency download mode
Done, with errors!!!
C:\Python27>pause
Press any key to continue . . .
I can still use the USB I think. I see Qualcomm HS-USB Loader 9008 (COM9) in the device manager whenever I would plug in the USB and it was manually updated after I selected x64 folder from the windows_drivers_QHSUSB_DLOAD folder(windows would say it was up to date when selecting x64 folder). I tried different ports but the Port otion never shows up for them in the device manager. I'm also not using USB 3.0.
I believe I followed every other instruction as far as I know from this thread http://forum.xda-developers.com/droid-ultra/general/droid-mini-maxx-ultra-root-pogress-100-t3071609 I'd really appreciate if someone could help me out.
Click to expand...
Click to collapse
Besides manually update the driver.
First, you have to disable the mandatory use of signed drivers in Windows.
Why? The driver you are trying to install (or update) is not signed and windows by default only allows the use of signed drivers.
Search a tutorial on "how to install an unsigned driver Windows 7"
I send you some, but I am the translator of google lol ..
I had a similar problem for the driver and the solution I gave you, solved my problem.
The best of luck, a big hug!
I managed to fix my problem yeasterday following br0adband advice in this thread http://forum.xda-developers.com/showpost.php?p=62651329&postcount=1159 sorry I forgot to close my thread(if I can figure out how). Thanks for that helpfull tip though, I'll keep that in mind for later driver issues.
Hi,
I'm looking for a way to get support for an USB CDC ACM device on my OnePlus 6 with OxygenOS 9.0.9.
If I plug in the USB device it is correctly detected but the driver is missing. (On my linux box, the kernel module cdc_acm is loaded and I can connect via the device /dev/ttyACM0).
I did not find an offered kernel which supports my goal. So I suspect such a kernel does not exist. Perhaps some kernel provider could add this support?
Or would it be possible to compile the module on my own? Any help or link welcome!
Thank you very much.