### Analysis & Opinion

#### Smartwatch Battle: Moto 360, Gear S2 Announcements & What to Know!

September 1, 2015

#### Which 2015 Releases Have Disappointed You?

September 1, 2015

#### The State Of The Internet Of Things

September 1, 2015

August 31, 2015

August 31, 2015
More XDA News

### Top Forum Discussions

#### Xposed Updated With Official Support For Lollipop 5.1

September 1, 2015

#### Samsung Gear S2 Forums Now Available!

September 1, 2015

#### How to Increase Your Microphone Volume on All Samsung S5 Variants

September 1, 2015

August 31, 2015

August 31, 2015

August 31, 2015

August 31, 2015

# DIY USB OTG CONVERTER FOR i9100! IT WORKS!

9 posts
Thanks Meter: 33

By redgreenlaser, Junior Member on 23rd May 2011, 02:18 PM
6th April 2012, 02:02 PM |#51
Member
Maasin City
Thanks Meter: 15

More
I have tried this and 100%works

10th April 2012, 09:33 PM |#52
Junior Member
Thanks Meter: 1

More
Quote:
Originally Posted by fduraibi

It is under section 6 in that document called "ASA", and i don't think it is a simple resistor but won't be very complicated also.
So would be cool if we can get some help and figure it out.

If it's not a resistor, then what do you suggest?

This thread seems to be the best piece of information on resistors, but none of them seems to be what we want.

---------- Post added at 10:19 PM ---------- Previous post was at 09:36 PM ----------

I've been digging a bit more in the datasheet, and the tables in chapter 6.5 and 5.3 gives us all we need. It seems to be nothing more than a 119 to 132 kΩ resistor and the phone will charge while still providing OTG functionality. I think i have a spare micro USB connector in a drawer somewhere, so i'll try this out ASAP :)

---------- Post added at 10:33 PM ---------- Previous post was at 10:19 PM ----------

The PDF says:

3) Nominal values for these resistors are RID_A = 124k, RID_B = 68k and RID_C = 36.5k.

The Fun with resistors thread says:
Code:
```RID_RESERVED_1,		/* 0 1 1 1 0 	28.7K		Reserved Accessory #1 */
RID_RESERVED_2,		/* 0 1 1 1 1 	34K 		Reserved Accessory #2 */
RID_RESERVED_3,		/* 1 0 0 0 0 	40.2K		Reserved Accessory #3 */
RID_RESERVED_4,		/* 1 0 0 0 1 	49.9K		Reserved Accessory #4 */
RID_RESERVED_5,		/* 1 0 0 1 0 	64.9K		Reserved Accessory #5 */
RID_AUD_DEV_TY_2,	/* 1 0 0 1 1 	80.07K		Audio Device Type 2 */
RID_PHONE_PWD_DEV,	/* 1 0 1 0 0 	102K		Phone Powered Device */
RID_TTY_CONVERTER,	/* 1 0 1 0 1 	121K		TTY Converter */
RID_UART_CABLE,		/* 1 0 1 1 0 	150K		UART Cable */```
It's pretty close, 121 vs 124 k, 64.9 vs 68 and 34 k vs 36.5 k, and actually quite weird the ACA modes arent listened in the source. Is this wrong? Is the 124 k resistor going to trigger TTY converter mode, whatever that is, instead? I guess i can find the answers in the kernel logs when i try it out.
11th April 2012, 08:12 PM |#53
Member
Baltimore, MD, USA
Thanks Meter: 11

More
Quote:
Originally Posted by fafler

If it's not a resistor, then what do you suggest?

This thread seems to be the best piece of information on resistors, but none of them seems to be what we want.

---------- Post added at 10:19 PM ---------- Previous post was at 09:36 PM ----------

I've been digging a bit more in the datasheet, and the tables in chapter 6.5 and 5.3 gives us all we need. It seems to be nothing more than a 119 to 132 kΩ resistor and the phone will charge while still providing OTG functionality. I think i have a spare micro USB connector in a drawer somewhere, so i'll try this out ASAP :)

---------- Post added at 10:33 PM ---------- Previous post was at 10:19 PM ----------

The PDF says:

3) Nominal values for these resistors are RID_A = 124k, RID_B = 68k and RID_C = 36.5k.

The Fun with resistors thread says:

Code:
```RID_RESERVED_1,		/* 0 1 1 1 0 	28.7K		Reserved Accessory #1 */
RID_RESERVED_2,		/* 0 1 1 1 1 	34K 		Reserved Accessory #2 */
RID_RESERVED_3,		/* 1 0 0 0 0 	40.2K		Reserved Accessory #3 */
RID_RESERVED_4,		/* 1 0 0 0 1 	49.9K		Reserved Accessory #4 */
RID_RESERVED_5,		/* 1 0 0 1 0 	64.9K		Reserved Accessory #5 */
RID_AUD_DEV_TY_2,	/* 1 0 0 1 1 	80.07K		Audio Device Type 2 */
RID_PHONE_PWD_DEV,	/* 1 0 1 0 0 	102K		Phone Powered Device */
RID_TTY_CONVERTER,	/* 1 0 1 0 1 	121K		TTY Converter */
RID_UART_CABLE,		/* 1 0 1 1 0 	150K		UART Cable */```
It's pretty close, 121 vs 124 k, 64.9 vs 68 and 34 k vs 36.5 k, and actually quite weird the ACA modes arent listened in the source. Is this wrong? Is the 124 k resistor going to trigger TTY converter mode, whatever that is, instead? I guess i can find the answers in the kernel logs when i try it out.

if you look at the pdf table 5-3 you will see the acceptable range:

RID_A = 119k ~ 132k (nominal is 124k)
RID_B = 65k ~ 72k (nominal is 68k) so 64.9k (from the other thread) is a bit below the range and i think it is saver to stick with the one suggested in the pdf
RID_C = 35k ~ 39k (nominal is 36.5k)

so we can use these resistors plus RID_FLOAT and RID_GND to switch between the modes of operation defined in the pdf table 6-2. So if we want the ASA to operate on more than one mode then I guess we will need some kind of a circuit to detect the attached devices in order to switch to the right RID. However, if we want a simple design for only 1 mode (or just as a prove of concept) then we can pick only 1 of them and have it hard wired to the OTG ID pin, (guessing again).

my only concern is what is going to happen if i hardwired only 1 mode but then had a different device setup, like no charger or more than 1 attached device (like if i used a hub and connected two flash drives)

i was able to connect a normal (un-powered) usb hub to my Galaxy Note using a normal OTG cable (ID=GND) and then i connected a wireless mouse dongle, wired keyboard and a 2GB flash drive in to the hub and my phone was able to provide enough power to all and i was using the mouse and keyboard while browsing files on the flash drive but everything failed as i plugged in a second flash drive (just to stress test it) since the phone couldn't provide enough current.
Maybe we can modify a powered hub to act as an ASA

by the way "fafler" did you get any results?
Last edited by fduraibi; 11th April 2012 at 08:15 PM.
11th April 2012, 11:10 PM |#54
Senior Member
Lisbon
Thanks Meter: 180

Donate to Me
More
Nice!
This is nice man thank you very much
12th April 2012, 06:36 AM |#55
Junior Member
Thanks Meter: 1

More
I haven't tried it out yet, as I haven't really been home. It has to wait to Saturday or Sunday.

Sent from my GT-I9100 using Tapatalk 2
12th April 2012, 03:21 PM |#56
Member
Thanks Meter: 1

More
I will try this. Thx for the info mate
20th April 2012, 01:17 PM |#57
Junior Member
Hong Kong
Thanks Meter: 1

More
thanks for sharing......
20th April 2012, 04:27 PM |#58
Member
Resen
Thanks Meter: 7

More
OTG cable recognizes only usb drives
Anyone having this problem. When i connect mouse or keyboard it is not recognized at all, and everything works fine with usb drives. Even tried with self powered usb hub so power is not an issue.
20th April 2012, 09:16 PM |#59
Member
Thanks Meter: 1

More
Thanks a lot!
Will try it.
24th April 2012, 08:06 PM |#60
Senior Member
Wonderland
Thanks Meter: 138

Donate to Me
More
Quote:
Originally Posted by imileimile

Anyone having this problem. When i connect mouse or keyboard it is not recognized at all, and everything works fine with usb drives. Even tried with self powered usb hub so power is not an issue.

Try another kernel like siyah. I had the same problem until i flashed this kernel.
27th April 2012, 02:06 AM |#61
Member
Thanks Meter: 3

More
I have used one of this otg adaptor from dealextreme to connect a 4g thumb drive to the s2. It works perfectly well, but when i attempt to connect the thumb drive back to my pc or my notebook, both can no longer accept the thumb drive format. Both cannot even reformat the thumb drive. Now the files in my thumb drive can only be managed via the s2. Does anyone encounter this strange prob? Is there a way to restore my 4g thumb drive? Thks for any advice.

Sent from my GT-I9100 using xda premium