Database Info

USB Host?

I've read the following articles
http://adq.livejournal.com/95689.html
http://www.tombom.co.uk/blog/?p=124#googtrans/auto/it
They show how to implement usb host on Hero and Droid. It's possible to do the same thing on G1 and Magic 32B? What about usb host driver?
Thank you.

Yes, at least on the magic Andrew's patch works with minor changes. Watch the android-kernel list for a cleaned up patch in the next day or so.

A kernel source is available and appears that it is working on the G1.

USB keyboard for magic?this sounds soo fu iPhone. XD

Have things evolved since that day ?
http://adq.livejournal.com/96583.html

Seems like no, they haven't

We should get this rolling then, itd be sweet to have host mode

think so too. anybody is able to do it? (except firerat anderweb and cyanogen as it seems they are doing enogh other stuff)

Bump for that USB host

I'm not sure if you people realize this, but there is more to getting USB devices working than simply enabling "host mode". In fact, you need drivers for the specific hardware, and you need something to detect plugging and activate the drivers. Also FYI: You need to build an interface between android and those hardware drivers, otherwise you're stilll not getting anywhere.

Bump
I wish I knew about development enough to contribute. This seems like it would be top priority.

bump
does anyone know if this is stock on any of the froyo roms?

[Q] What will it take to make the new sixaxis driver work on the SK4G?

So sir_earl has done us all a great service by making it possible to use the Playstation 3 controller with Android phones. He posted about it in http://forum.xda-developers.com/showthread.php?t=1179929
But unfortunately for us, it's not compatible with the Sidekick 4G or several other recent Samsung phones. It sounds like our stock ROM doesn't give it the access it needs to the bluetooth hardware. What would it take to fix this? Is it something we can add with a custom kernel?
(BTW, I am the farthest thing from a software developer on the face of the earth, so sorry if I turn out to be Captain Oblivious.)

This is not an issue with access, but rather that certain protocols aren't built into our driver.
Think of it like this; you're trying to use an Xbox controller with a Playstation. They're both controllers, but they don't know how to talk to each other.
This would require either rewriting the bluetooth driver ( not feasible) or seeing if the driver is similar in our phones to that of one of the working phones.
EDIT: took a look in the kernel config, and found some bluetooth protocols that weren't enabled, that according to http://www.pabr.org/sixlinux/sixlinux.en.html are the same as the ones that the controller uses? not sure.
EDIT2: Tried enabling all the bluetooth options in the kernel config, couldn't get the compat checker to tell me anything good, still just says missing protocol, even though HID (what it should be) is enabled. I PM'd sir_earl to see what protocol is required and which phones it works on, perhaps I can see if their driver will build with our kernel, or if I can somehow mash together our sources to make it work.

That's a great start. I'd be really happy if we could make this work.
Our phone has all the power it needs to run things like N64 and PS1 emulators, and combined with the TV out cable, we've effectively got a dozen game consoles in our pockets. We just need a good way of controlling them.

Update: got a PM back from sir_earl, it's true that Samsung left out the BT protocol we need to use this, it's called "L2CAP via raw sockets" (from sir_earl). He suggested that using the AOSP/CM BT stack would be a good place to try, so I may give that a shot sometime later, as my list of projects is somewhat long right now.

Thanks for getting to the bottom of this. Here's hoping you get a chance to try it.

Did you have a chance to fiddle with this any more? I'd sure like to be able to use a proper gamepad with all the awesome emulators that run on these phones.

Tried looking at it, but the bluetooth stack that has proper support didn't work by just being added to our Kernel. I'm also kinda working on porting our kernel to be compatible with CM6/7, which would be easier to add the bluetooth stack to.

[2013.04.11][2.3.1+] USB Host Diagnostics v1.3

USB Host Diagnostics determines your device's USB host capabilities.
USB host is a very powerful feature of recent Android based smartphones and tablets, but on many firmwares (both stock and custom) the feature is somewhat broken.
For example, at launch the Galaxy Nexus told all the apps and the Market that it supported USB host, but USB host did not actually work (this was fixed in the Android 4.0.2 update). This broke several apps.
That is just one example of many. There are even cases where OEMs advertise USB host support, but the device does not support it at all. It appears as if USB host support isn't tested by Google or the OEMs when they push out new firmwares and devices at all.
As we cannot depend on Google or the OEMs to correctly provide information regarding USB host support, and the Android framework will regularly lie about it to both the Market as well as Android apps, this application was created so you can test your device's USB host capabilities for yourself.
If you allow it, the app will also submit your results to my website, so together we can create a complete database of devices and firmwares and their USB host support.
This tool may also come in handy for those porting firmwares.
Requirements:
- Android 2.3.1 or newer
- (Optional) Root
- USB OTG cable (unless your device has a fullsize USB port)
- USB memory stick, or another USB device to test the connection with
The result database is available here:
http://usbhost.chainfire.eu/
The download can be found on Market here:
http://pkg.to/eu.chainfire.usbhostdiagnostics
It is also attached: DO NOT REDISTRIBUTE
(v1.2: 9284)

Changelog for v1.3:
- Detects some common issues with firmwares that can cause apps to be unable to use USB host, and if you are rooted, offers to (try to) fix the problem
- Gives you a unique code that can be used to locate your result, if uploaded to server
- Added option to follow me
- Fixed some more crashes
- Disabled rooted API for Jelly Bean and newer
- API 14 and higher get Holo look now

FC on Samsung Note

cmloo said:
FC on Samsung Note
Click to expand...
Click to collapse
Should be fixed now

FC on GT-I9100 (GB, XWLA4) - detecting the flash stick through the OTG USB cable seems to work on that build

galaxys2 GT-I9100 IML74K samsung/GT-I9100/GT-I9100:4.0.3/IML74K/XXLPB:user/release-keys Custom 2 Yes Yes Yes Yes Yes Yes Yes Yes Full
USB Sticks fail to detect the only thing I can get working is your DSLR application.

Northern-Loop said:
galaxys2 GT-I9100 IML74K samsung/GT-I9100/GT-I9100:4.0.3/IML74K/XXLPB:user/release-keys Custom 2 Yes Yes Yes Yes Yes Yes Yes Yes Full
USB Sticks fail to detect the only thing I can get working is your DSLR application.
Click to expand...
Click to collapse
Try my StickMount app from the Market, it's actually for the G.Nexus. Your build just doesn't have automounting and such enabled... doesn't mean USB host isn't working

FCs in 9100 XWKK5 (CFroot kernel XWKK5)
http://pastebin.com/kVENXkx1

Chainfire said:
Try my StickMount app from the Market, it's actually for the G.Nexus. Your build just doesn't have automounting and such enabled... doesn't mean USB host isn't working
Click to expand...
Click to collapse
Sweet that works!! Detects FAT32 SD cards but didnt detect NTFS USB stick.
Is that something the CM9 devs can change to enable it by default?

Northern-Loop said:
Sweet that works!! Detects FAT32 SD cards but didnt detect NTFS USB stick.
Is that something the CM9 devs can change to enable it by default?
Click to expand...
Click to collapse
For NTFS the right module has to be loaded... ntfs-3g, from the top of my head. Automounting should also be fixable, several devices do it, but I have no idea where it would be configured.

OK sent stats
Huge thanks for the Stick mount app
Now I have pen drive support on cm9 sgs2
Sent from my GT-I9100 using Tapatalk

No on all device detection checks on galaxys2 on CM9 alpha, the rest were fine.

Nice job with the app works nice on xoom

installation fails on rooted Samsung GT-S5360 (galaxy Y).
great APK, anyhow !

no usb support on tbolt running eternity latest nightly

Great utility and it works great to jump start DSLR controller on ISC.

Cheers, gonna provide results soon. Any chance for a similar app checking for MHL (USB-to-HDMI) compatibility? Thanks anyway!

I noticed that some docks for Xperia phones have a full-size USB port that they say is for USB accessories. The dock with my Xperia PLAY 4G (R800at) only passes microUSB and audio, but I'll get the adapter and try anyway. With built-in gaming controls, I doubt I'll *need* USB host support anytime soon, but it will be nice to know!

So desire HD no this functionality not eaven app can fix this?
wanna know what HTC said about this?

any chance that xbox360 controller could work ? or usb mouse >?

[KERNEL][ICS][JB][v2.1] USB Ethernet, DVD, Voodoo, Kernel manager app!

2.2 released!
In the news!
Current features:
Based on Asus 9.2.1.27 WW kernelsources
Backported all Linux 3.2 USB LAN drivers (bandwidth up to 250 MBit/s! tested with a SMSC LAN7500)
ISO9660 (+Joilet), UDF, FAT12 and Apple HFS file system support (USB CD\DVD access! See notes)
Voodoo Sound support!
Turned a few unneeded kernel features off and compiled with Linaro GCC, it's smaller and boots quite a bit faster than other kernels!
Installable using your favorite recovery (tested on CWM v6.0.1.4 v2)
New versions of Tegra 2 codecs for ICS based ROMs (will be provided within a separate installable .zip)
Kernel manager application to manage loaded drivers and file system modules!
Supports almost all current ICS and JB ROMs
Compatible with:
[ICS] Asus official firmware (with root)
[ICS] Android Revolution HD
[ICS] Energy™
[ICS] Revolver
[JB] LiquidSmooth
[JB] RaymanFX's CM10
[JB] ParanoidAndroid:CM10 Hybrid
If you tested this with any other unlisted ROM, please drop some feedback!
Note 1: Some USB devices may need additional power, if so, get a Y cable from eBay so you can power a USB device using a external USB power source
Note 2: External optical drivers and floppy drives will not be mounted automatically, as Android doesn't officially support them
Note 3: CSS protected DVDs are not supported (e.g. Retail movies), due to Linux kernel limitations
Note 4: NTFS is not supported 'out of the box', please use Paragon driver from Google Play
Downloads:
https://www.dropbox.com/sh/gxi0gsl0tdfapgi/Ja19Exs4Sz
(PLEASE install Busybox 1.20.2 using one of the installer apps from Google Play, it is needed for the Kernelmanager application to function properly)
Source:
https://github.com/sander-ashwin/tf101-allinone-kernel
Please report if something does not work!!
Mounting optical drives:
1: First make sure your device is proper rooted (the "mount" command we'll use needs root)
2: Install Android Terminal Emulator from Google Play and open it
3: Type "su" and press enter, you should be asked if you would like to give root access, say Yes
4: Make a mountpoint directory, e.g. "mkdir /Removable/opticaldrive"
5: Mount your optical drive (make sure it gets enough power and something is inserted in the drive) using this command: "busybox mount /dev/block/sr0 /Removable/opticaldrive"
6: You're done! If you inserted a DVD movie, you might want to install Wondershare player or some other player that is capable of playing DVDs with menus
7: If you encounter any difficulties, please reply on this thread or send me a message
Connecting your TF101 to wired ethernet:
1: Buy a TF101 USB Host connector if you don't already have one (they are very cheap online, around 12-15 dollars)
2: Connect the adapter to your TF101, plug in your USB ethernet adapter
3: Android will display a message in the lower right corner of the screen that an ethernet adapter has been connected
4: Connect the LAN cable
5: Android will display a message that your device is connected using DHCP, you can now use internet using LAN
6: If you require manual IP settings, please go to Android's settings, there you can set manual IP or DHCP (OPTIONAL STEP)
Thanks to:
RaymanFX - for inspiring me with his own kernel, and for porting CM10
Asus - for making a pretty good device
prendomiao - for beta testing

Changelog
v1.0:
First release!
v1.1:
Removed some more junk from kernel
Now actually added new filesystem drivers!
v1.2:
Backport of Linux 3.6 I2C core
A little more cleanup of unneeded features
v1.3:
Backported all Linux 3.2 USB LAN drivers
Kernel now includes support for Voodoo Sound!
v1.4:
I2C fixes + Tegra I2C driver ported from kernel 3.6
Tweaked I2C timeout, hopefully our touchscreen won't lag anymore
(this may fix the problem that the touchscreen sometimes doesn't respond for a second, because of an I2C timeout)
v2.0:
Fixed sound
Now compiled using latest Linaro GCC 4.7.2 compiler
New kernel manager application to manage loaded drivers! You're in control, so the kernel doesn't load unneeded modules anymore!
Reverted I2C changes, as they didn't really help
v2.1:
Now compatible with ROMs based on RaymanFX's CM10
Updated BCMDHD WLAN driver for CM10 kernel
A little cleanup to synchronise both ICS and CM10 versions
Updated Linaro compiler to 2012.10
v2.2:
Added some new releases for more compatibility

i tried it. there is a little change, it is a bit speedly... i don't tried videos... but it is good good work

Thank you! Hope videos will play better as Tegra 2 is really picky with HD videos.
I'm now writing a tutorial for mounting optical discs, fortunately it's not really difficult.

but drivers must support them

Well, I included them already They are in your device if you still have my kernel installed.
But Android doesn't support automounting optical drives, so we have to mount the optical disc ourselves, until someone writes an app to do it (automatically).
EDIT: please install v1.1 if you would like to use your optical drive, as I forgot to include the drivers while compiling v1.0

Outstanding kernel. The first one I've run without SoD so far. I don't need OC, so the extra freq.'s are not important. Super quick, reliable so far for a few hours. I'll continue to report back, especially if I get SoD's. They are the bane of my existence. Keep up the good work.
Sent from my Transformer TF101 using xda premium.

Thanks! Hope you can enjoy your device again
I would like to implement overclocking though, but only if the kernel is still 100% stable for everyone.
Stil need to find out how, as I'm still learning C and kernel hacking.
The main problem at the moment is that all different hardware revisions have different issues.
Mine has touchscreen issues with a lot of kernels for example, your device may freeze when sleeping, but with a lot of testing and debugging we might be able to create a kernel that works for everyone.
When having any problems, please keep reporting!
poppajules said:
Outstanding kernel. The first one I've run without SoD so far. I don't need OC, so the extra freq.'s are not important. Super quick, reliable so far for a few hours. I'll continue to report back, especially if I get SoD's. They are the bane of my existence. Keep up the good work.
Sent from my Transformer TF101 using xda premium.
Click to expand...
Click to collapse

sainthout said:
Thanks! Hope you can enjoy your device again
I would like to implement overclocking though, but only if the kernel is still 100% stable for everyone.
Stil need to find out how, as I'm still learning C and kernel hacking.
The main problem at the moment is that all different hardware revisions have different issues.
Mine has touchscreen issues with a lot of kernels for example, your device may freeze when sleeping, but with a lot of testing and debugging we might be able to create a kernel that works for everyone.
When having any problems, please keep reporting!
Click to expand...
Click to collapse
To avoid SoDs, you need to set the lower voltage higher.

The standard voltages I'm using should be ok, but mine still SoD's sometimes.
With stock kernel as well as with other kernels, as well as with my own kernel..
Unfortunately it always happens when I'm not at home, so I can't directly debug using ADB (if possible at all).
So I can't easily find out wether it's a hardware issue, kernel issue or software issue.
If anyone has a clue about this, please reply!!
K900 said:
To avoid SoDs, you need to set the lower voltage higher.
Click to expand...
Click to collapse

sainthout said:
The standard voltages I'm using should be ok, but mine still SoD's sometimes.
With stock kernel as well as with other kernels, as well as with my own kernel..
Unfortunately it always happens when I'm not at home, so I can't directly debug using ADB (if possible at all).
So I can't easily find out wether it's a hardware issue, kernel issue or software issue.
If anyone has a clue about this, please reply!!
Click to expand...
Click to collapse
Is it SoD with dock connected or tablet alone? I'm sure you're familiar with the SD card removal thing from the dock to prevent SoD with guevors kernel? That wasn't my issue anyway, but it's just one I've heard of...
edit: you know, I didn't even think about the voltages being the issue with the other kernels... Is there an automated program to adjust voltages? I used QuickClock Overclock for my Droid X, but I'm not familiar with changing voltages on any other devices...
---------- Post added at 11:42 AM ---------- Previous post was at 11:33 AM ----------
I wouldn't MIND having OC, but I hardly use it. I got out of the OC game after watching it kill batteries on multiple phones and devices..
No one really NEEDS to OC, but for some reason people feel the need for it. The only phone I really NEEDED OC was my Droid Eris to play Angry Birds when that first came to Android... anyways, off topic...
I messed with the tablet last night, and still had no SoD.. I'll report back again tonight when I get home from work.

do you make it for jb please ?? we need it

Good to hear that the kernel works so far, hope it won't SoD.
I don't have the dock, the SoD's are just random it seems.
I'm also not working on overclocking anymore, too much files are involved which make it difficult to understand and fix.
It's also a pretty big risk, you could burn your CPU or GPU if using wrong values or something like that.
I'll leave the stock voltages and stock frequencies.
I'm now trying to fix the touchscreen issue that happens after some time. Not many people have the problem, so this won't do anything to other people.
Just updating the Linux I2C core to new 3.6 and backporting some newer touchscreen drivers.
Maybe I can also include some newer USB Ethernet drivers and backport other things.
When I implemented something that's worth trying out, I will put a new kernel version online
poppajules said:
Is it SoD with dock connected or tablet alone? I'm sure you're familiar with the SD card removal thing from the dock to prevent SoD with guevors kernel? That wasn't my issue anyway, but it's just one I've heard of...
edit: you know, I didn't even think about the voltages being the issue with the other kernels... Is there an automated program to adjust voltages? I used QuickClock Overclock for my Droid X, but I'm not familiar with changing voltages on any other devices...
---------- Post added at 11:42 AM ---------- Previous post was at 11:33 AM ----------
I wouldn't MIND having OC, but I hardly use it. I got out of the OC game after watching it kill batteries on multiple phones and devices..
No one really NEEDS to OC, but for some reason people feel the need for it. The only phone I really NEEDED OC was my Droid Eris to play Angry Birds when that first came to Android... anyways, off topic...
I messed with the tablet last night, and still had no SoD.. I'll report back again tonight when I get home from work.
Click to expand...
Click to collapse

Different JB ROMs may require different ramdisks, so it will take a little time to get it done properly and stable.
For which JB ROM would you like to use it? I might be able to take a copy of the ROM's kernel's own ramdisk and combine it with my kernel
I'm also thinking into making one for RaymanFX's new LiquidSmooth ROM, anyone interested?
prendomiao said:
do you make it for jb please ?? we need it
Click to expand...
Click to collapse

I am sorry if i sound stupid, but where do i extract files to? I have a flashing red light on my USB ethernet but no connection

Hi, does Android display a notification that you connected an USB Ethernet device?
And for which ROM are you trying?
mazimo said:
I am sorry if i sound stupid, but where do i extract files to? I have a flashing red light on my USB ethernet but no connection
Click to expand...
Click to collapse

USB Ethernet works on Android 2.3 with icon...

Ethernet doesn't have anything to do with Android at all.
The Linux kernel provides drivers which will provide Android a universal interface to control Ethernet devices.
When you plug in your USB ethernet device, the kernel will create an eth0 interface (first ethernet device interface).
Android sees that immediately and will show a little message that an ethernet device is detected.
With very old Android versions, Android doesn't really support ethernet, but some kernels do.. in that case ethernet support will be provided automatically without any notifications.
So for example, if Samsung want to support every USB ethernet device, they can, by building support into the Linux kernel.
If Asus doesn't, they don't build any support in the kernel, so the devices won't be recognised and so they will not work.
Except 1 or maybe 2 devices, the original Asus kernel doesn't support ANY Ethernet device, but my kernel supports them all
prendomiao said:
USB Ethernet works on Android 2.3 with icon...
Click to expand...
Click to collapse

new release
Everyone on older versions, please upgrade to v2.0 and try my new kernel manager application!
(Which is also my very first Android application)
Enjoy and please post feedback
If anyone would like to tryout a JB version of my kernel, please pm me!

I ran your 1.0 version, and it's great. I have MASSIVE battery life compared to before. The only issue I have noticed is with wifi reconnecting after deep sleep. It disconnects when screen is off (i verified the settings), but it has a difficult time reconnecting. I usually cycle the wifi toggle and it connects, or I click on my wifi and it connects. It's clearly not a major issue, just a little extra thought when I wake it up.
I read through and no one reported anything like this, so I figured it might be something to keep your eye out for in your later builds. I will install the 2.0 today and give feedback later. Thanks for your hard work!

Potential CM12.1 Official Support!

Check this out, whilst surfing the CMX Changelog for 12.1, I came across this:
Enable USB OTG (android_device_asus_fugu)
http://review.cyanogenmod.org/94378
It appears to be OTG support for Fugu (Nexus Player)! Also, after syncing CM12.1 source, "Fugu" is a valid lunch arguement! Looks like we may be getting official support!

Saw that as well, pretty interesting. :good:

http://download.cyanogenmod.org/?device=fugu
There are only nightly versions available right now but they'll reach stable status for this device at some point.

npjohnson said:
Check this out, whilst surfing the CMX Changelog for 12.1, I came across this:
Enable USB OTG (android_device_asus_fugu)
http://review.cyanogenmod.org/94378
It appears to be OTG support for Fugu (Nexus Player)! Also, after syncing CM12.1 source, "Fugu" is a valid lunch arguement! Looks like we may be getting official support!
Click to expand...
Click to collapse
OTG works out of the box. I don't understand the "OTG support" that you are speaking of.

QUEDRO said:
OTG works out of the box. I don't understand the "OTG support" that you are speaking of.
Click to expand...
Click to collapse
1. This was put up a while ago.
2. Yes, on STOCK OTG is supported, but this isn't stock. Read the dang commit. It specifically enables OTG support for CM ROMs for the Nexus Player (fugu). Some devices that CM supports DO NOT support OTG functions, therefore, CM has a flag to tell the system whether or not it can use OTG functions.
3. Actually, not all OTG functions work (correctly at least) on stock. Stock cannot mount an NTFS/Fat32 drive as internal SD Storage space, i.e. move your apps to the external drive. CM (thanks to that commit and several others) can.