hey guys came across an interesting discussion! i cant post in dev boards yet... however, this guy provides some answers, maybe some of the elders may want to take a look. EDIT: i cant even post an outside link read code box i guess...
Code:
Hi All,
I've spent some time today dithering on the Nexus S and host mode and I think the way to approach this is different from the Nexus 1 host driver hack.
The Nexus S uses a Fairchild USB switch (fsa8480) to detect device connections. I believe the point is to allow the device to handle multiple functions like charging, UART and USB access simultaneously.
The Switch will detect OTG connections. Plugging in a microB to A convertor with pin 4 grounded to 5 causes the fas9480 driver to wake up and report an OTG attachment. It also calls into the S3C_UDC_OTG driver to configure it up and create a vbus session. (start charging)
The problem is that in the Nexus S kernel, this driver is device mode only. There is no code to put it into Host mode and the chip can only be in Host or device mode. It can't do both at the same time. Also, the few people that have tried to use host drivers have found that they must disable the device code (including charging capability) to get the hubs to enumerate.
It appears that the OTG core in the samsung part is from DesignWare. There are synopsis reference drivers up here:
*************check edit reason for driver link*****************
The register map appears the same, and the code supports host and device mode as well as dynamic switching based on HNP negotiation.
It seems like the best way to approach this would be to integrate this code and use the fsa9480 discovery as the hook to force host mode (when OTG is detected) or device mode when other devices are detected.
The demo we were under the gun to support will probably just use Nexus one, however I thought the rest of you guys would want to see this. I think if done right, you could have host mode, gadget mode and charging all in the same kernel.
Steve
--
Steve Modica
CTO - Small Tree Communications
---not my words, or even me. just though people may want to know!
Sorry 4 the prev thread in wrong section .. then .. One S ( stock rom or another custom rom - with or without Sense ) supporta the usb-host mode ?
I am reasonably sure that out of the box, on stock ROM it does not support the ability to act as an USB host. Additionally, the microUSB on the phone is an USB slave socket, so it would need an adapter to connect a USB slave device to it anyways. (At least I have not yet seen a native USB-Host device with a microUSB socket.)
I am pretty certain it can be hacked into a custom ROM or application, however there are limitations to this. Commonly a device that is designed as USB slave (like the One S) will not be able to power devices through the USB port as regular USB hosts have to.
So IMO, in order to get it to work as an USB host you would need an adapter to connect the devices properly, a modified firmware or specialized app AND a way to externally power the USB slave you want to connect to the One S acting as USB host. The external power might a portable USB charger battery (like the Gumpack) or an Y-cable which is connected to a "real" USB-Host device just for the power (or a car/wall USB charger).
So, theoretically it would be possible, but not very practical. To the best of my knowledge it has not been done in the past because there was no need to. This however might actually change with the current trend towards non-expandable memory on newer phones... if demand rises I bet manufacturers would come up with solutions. Think small USB storage sticks with regular USB plug on one side for use on Notebook/Desktop and a microUSB plug on the other which contain a tiny battery (think Bluetooth headset size) to power the stick while attached to the phone and are charged while connected to a real USB Host port which is designed to deliver juice.
Further reading: http://en.wikipedia.org/wiki/Universal_Serial_Bus#Connector_types
This tutorial is aimed to ones who wish to have USB OTG Capability within their
HTC Desire S ( Saga ).
1: what you need ( software )
A USB host capable kernel or your Android Must support USB Host APIs.
if you don’t have proper kernel you will not get USB OTG support, in my case
I flashed kernel 3.0.76 from Stefan on ics Final v2.0 ,Android version 4.0.4, sense 3.6, Now there is another kernel, I have Hboot 2.0******.
Available with USB Host capability the version is 3.0.89, I have not tried this kernel
Yet, you can if you wish, you can find both of these kernels at XDA.
If your rom or framework does support USB Host APIs then may be you don’t need to flash
The kernels.
With a linux patched kernel USB devices are detected under “ sys\bus\usb\*.* “.
If your android system and framework supports USB Host APIs, Android will detect USB devices
Under “dev\bus\usb\*.*”
Install USB Device info from google play store.
Install USB Host Diagnostics from Play Store.
Install USB OTG Helper from Play Store or any other software like Stick Mount to mount your USB STORAGE DEVICE.
You must have root access and super user installed.
Before flashing the kernel always make a backup of your current Rom.
As in my case when I flashed the kernel my wi-fi stoped working and then I had to manually push some wifi related files to system directory.
2: Hardware
You need a USB OTG Cable, unfortunately USB OTG cables available in Market are not suitable for Desire S, because Desire S does not Power the USB Bus within its own, to wake up USB Host Capability for Desire S we need to short Pin 4 and 5 at Micro B plug, Micro B female is incorporated within Desire S.
If a cable with shortened pin 4 and 5 is available then you don’t have to make a cable.
Its recommended not to short pin 4 and 5 at micro B plug, its good to sold a 10k resistor between pin 4 and 5. Get a standard charging cable for you Desire S with Micro B Plug, First of all check this cable by connecting it to your computer, if charge only and disk drive options appears at your phone the cable is good for our purpose.
Secondly get one Standard USB Extension cable, this cable has 4 pin Male at one end and 4 pin Female at the other end. Cut this cable from the center, remove the shielding plastic and uncover the wires.
You will find four wires,
Red = POWER ( Normally 5 Volts )
White = ( Data- )
Green = ( Data+)
Black = GND ( Reference Ground for 5 Volts )
Get a soldering iron and a piece of solder wire.
Now pick Male end, cut white and green wires ( we don’t need them because we only need power wires from this plug ).
Now pick Female one, uncover the wires from this also, Make a joint of Male “RED” with Female “RED”, and Also Make a Joint of Male “BLACK” to Female “Black”, don’t cut “WHITE” and “GREEN” wires.
Now cover “RED” and “Black” with some sort of Glue or Adhesive Tape, Glue is better choice because it will prevent the wires from getting short, or you can use heat shrinking sleeve.
Now pick your standard charging cable and cut it from the center and hold the end having small Micro B Plug, uncover plastic shielding, you shall find following wires,
RED
WHITE
GREEN
BLACK
Now get the cable you already mad having Standard Male and Female and Make joints as follows.
RED = RED
WHITE = WHITE
GREEN = GREEN
BLACK = BLACK
Double check all connections and now the important part comes
Gently remove the plastic from behind the Micro B plug with sharp knife or cutter, be careful and be patient here because in a hurry you can damage the plug or wires.
After you remove the covering Micro B plug you will find “ RED , WHITE , GREEN , BLACK “ wires soldered.
Notice that only one point at Micro B plug is Empty, There you go, it is pin No 4 of Micro B Plug.
You will also see “BLACK” wire there, Now get your 10 k resistor, sold one end of the resistor to where the “BLACK” wire is soldered and sold other end to pin No 4 which you have already found empty.
Be careful here not to short any pins, it may lead to a disapointment. Your USB OTG CABLE is ready, put some glue where you find its necessary to cover and also over the Micro B plug from where you remove the plastic.
Now run USB Host Diagnostics and when it says to plug in then plug your micro B connector to the phone, you don’t have to apply power through mail connector until. USB Host Diagnostics should show
As following picture, it will detect USB root hub of the phone, if it does not detect anything then
May be there your cable is not prepared properly, or just Restart your phone after installing USB HOST Diagnostics and check again, USB HOST Diagnostics needs root access if USB HOST APIs or framework is
Not supporting USB HOST MOD.
Now apply power through your charger to MALE connector, after 5 or 7 seconds your phone will indicate charging, means the cable is correct.
Put a USB stick in USB Female connector, open USB OTG Helper and hit MOUNT, it will mount your USB storage device and will create a directory at the root of your SD card named “UsbOtgDrives”.
You can brows the files and directories of your device in that folder.
Un mount USB Mass storage through USB OTG Helper and connect any USB mouse and you will see a small cursor, its very small and but you can locate it, if pointer does not appear remove the power plug and connect again, same way you can connect a USB keyboard, connect a USB keyboard and open any text editor in your phone and check by typing from keyboard or open your sms editor and check it there.
You can get your device info with “USB Device Info” if you installed it from play store.
Wow...now...
that is one of the great tutorials that were missed
in our forum
many thanks from saga community:good:
asgardr said:
Wow...now...
that is one of the great tutorials that were missed
in our forum
many thanks from saga community:good:
Click to expand...
Click to collapse
I wrote tutorial, but there was a question i did asked, "does viper saga supports USB OTG AND USB HOST API, BUT UNFORTUNATLY NOBODY REPLIED, SO I SPARED SOME TIME AND INSTALLED THIS ROM TO MY DESIRE S, IT WAS ACTIVATING CAR DOCK MOD AS SOON I PLUGGED USB OTG CABLE BUT WAS NOT DETECTING ANY USB DEVICES, I SPENT TOW HOURS ON THIS ROM AND NOW EVERRY THING IS WORKING " MASS STORAGE, CDC-ACM- PL2303 SERIAL CABLE, CH340, CH340, SERIAL CABLE AND ALL HID DEVICES. IF SOMEONE IS GETTING PROBLEM CONNNECTING THOSE DEVICES, PLEASE PM, I WILL TRY MY LEVEL BEST TO HELP.
Many Thanks
MNASWL said:
I wrote tutorial, but there was a question i did asked, "does viper saga supports USB OTG AND USB HOST API, BUT UNFORTUNATLY NOBODY REPLIED, SO I SPARED SOME TIME AND INSTALLED THIS ROM TO MY DESIRE S, IT WAS ACTIVATING CAR DOCK MOD AS SOON I PLUGGED USB OTG CABLE BUT WAS NOT DETECTING ANY USB DEVICES, I SPENT TOW HOURS ON THIS ROM AND NOW EVERRY THING IS WORKING " MASS STORAGE, CDC-ACM- PL2303 SERIAL CABLE, CH340, CH340, SERIAL CABLE AND ALL HID DEVICES. IF SOMEONE IS GETTING PROBLEM CONNNECTING THOSE DEVICES, PLEASE PM, I WILL TRY MY LEVEL BEST TO HELP.
Click to expand...
Click to collapse
I tried ur tutorial with SVHD 2.1.0 ROM on my HTC Desire S with kernel 3.0.76 and it is working superbly, my wifi stpped working after the kernel flash but after flashing the boot.img via fastboot solved the problem .. I did not try to make a usb cable as u narrated instead I am using Y cable for it which has a separate mini usb power adapter and USB slot for pen drives... Many thanks bro :laugh:
Is there any existing cable on the market now that I can buy? I'm low on time to make my own
cable
broucker said:
Is there any existing cable on the market now that I can buy? I'm low on time to make my own
Click to expand...
Click to collapse
no such cable is available in market for desire s,you can try y cable with standard usb to otg converter.
Please can some one get a video of his tutorial for me to take a close look at it to make my own. I really need it to work on ds. Thank u all. I would be very happy to see that video
Just try to closely see the pictures and read care fully what I have written, in case if you feel difficult let me know , will try to spare some time to make video. Any ways it's easy.
MNASWL said:
Just try to closely see the pictures and read care fully what I have written, in case if you feel difficult let me know , will try to spare some time to make video. Any ways it's easy.
Click to expand...
Click to collapse
I am using a custom viper saga Rom, i've install the Stefan kernel, and I have closely followed everything step as you said, but still can't mount any drive. My USB host diagnostic show exact as your in the picture, but my USB helper still can't mount drive..... Please I need help fixing the issue
This Rome will not work.
Install victims saga 2.0 rom.
That will work.
Sorry virtuous saga 2.0
Is there a similar interface to http://electronics.stackexchange.com/a/46918 to force charging while the device acts as a USB host?
Does anyone know which resistor value is required to otherwise enable charging?
Fr4gg0r said:
Is there a similar interface to http://electronics.stackexchange.com/a/46918 to force charging while the device acts as a USB host?
Does anyone know which resistor value is required to otherwise enable charging?
Click to expand...
Click to collapse
It should certainly work, as the phone should be able to act in OTG mode while being charged at the same time, when placed in Motorola lapdock.
There are (at least) some 100k and 200k (between pin 4 and 5, I assume) tests present in kernel (emu detection) that switch the behaviour, but I didn't need to look into it too closely so far. You'll have to study the source and experiment...
@Fr4gg0r
I have recently bought this USB OTG adaptor: http://www.ebay.com/itm/New-Host-OTG-Power-Cable-Micro-USB-Male-to-USB-Female-for-Galaxy-Note2-S3-S4-/191145599519?ssPageName=ADME:LCE:3160
It's the first OTG adaptor fully working for me. All my USB Flash drives are working without problem. It's also charging my Photon Q while using USB host.
I have a custom designed & built USB hub board, where multiple such boards have been working with multiple android devices for multiple years. One thing I can always do with a new USB device is plug my board into the Android device, then plug a USB thumb drive into one of my boards hub inputs, and then from the Android device use Google Files to view the contents of the "disk" (the USB thumb drive). Note that most times I must first go to Settings, turn on Developer Options, and change the Default USB Configuration to allow File Transfer.
Now I'm trying it out with the very inexpensive B130DL. I've changed Default USB Configuration to allow File Transfer. I plug a USB thumb drive into my hub board in advance, and I plug my usb hub board into the B130DL in advance. Then I power up the usb hub board. SUCCESS... a moment later the BL130DL shows that USB trident icon at the top. From Google Files I'm able to view the contents of this disk. UH OH... a moment later I get a message that the usb device has been ejected. (I believe this message comes from Google Files. If I'm not currently running Google Files, I don't see this eject message. I just see the USB trident icon go away.)
Note that the B130DL is [disliking] my USB hub, specifically. If I plug in both B130DL and USB thumb drive, then it takes about 6.5 seconds from powering on the hub board to when the B130DL shows the USB trident icon. Then it takes another roughly 9 seconds for the USB trident icon to go away again. If I do the same test, plugging in the USB thumb drive 3 seconds after powering on the hub board, then the same things happen based on timing from powering on the hub board. Also, once ejected, removing and replacing the USB thumb drive doesn't repeat the test. I must remove and replace hub board power to repeat the test. In essence, it seems like the B130DL is ejecting the hub and thus everything on it. Meanwhile, a separate USB OTG cable works indefinitely when plugged into the B130DL. Note as well that this very same usb hub board works great and continuously when plugged into a different phone (Samsung A01, Android 11). I've been swapping between phones (B130DL and A01) repeatedly to make sure I haven't broken my hub board in any way. Also, In the past, this usb board has worked with Android 9 and 10. The B130DL is Android 10.
So what about the B130DL is it that causes it to first work with my usb hub board and then eject it? Any good ideas? Again, note that the problem is NOT intrinsically with my custom usb hub board, because that works great with many other Android devices. It's this specific B130DL that has the problem. True, it might be customized by BLU to refuse a number of USB OTG devices. Or it might be customized by BLUE to do something else. This is my question.
Thanks!