[Q] USB host (OTG) flashdrive intermittent connection - Galaxy S II Q&A, Help & Troubleshooting

Hi all,
I am experiencing intermittent USB host (OTG cable) connection on Samsung Galaxy S2, Android 4.0.3 (stock unrooted but exotic brand).
I've spotted this when trying out Helicon Remote app with a Nikon D90 camera. Connects and shows live image from the camera and other signs of operation for a few seconds, then disconnects, connects again, disconnects etc, then the app complains over connectivity and suggests to restart the camera...
Similarly, flashdrives are first mounted, then unmounted unexpectedly, then reported as damaged (though still fine on a PC and chkdsk finds nothing).
I believe it is not cable-related because I've tested 3 different OTG cables for the S2, two of them new, and one of them had once worked fine with flashdrives. But that was with Android 2.3.6 before upgrade to ICS, and I also had to replace the USB&MIC board in the phone due to a charging problem (both rev.2.2) in between.
USB Host Diagnostics says GT-I9100, IML74K/XWLPD, verdict Yes/Full. But the test is not long enough I guess.
Normal USB storage connection to PC still works fine (normal cable not OTG for this one).
Should I try another USB&MIC board, or is this more likely a software issue? I've managed to google up a couple of similar case with flashdrives, with no solution, maybe didn't use good keywords. Any suggestions?

---

_sem_ said:
Hi all,
I am experiencing intermittent USB host (OTG cable) connection on Samsung Galaxy S2, Android 4.0.3 (stock unrooted but exotic brand).
I've spotted this when trying out Helicon Remote app with a Nikon D90 camera. Connects and shows live image from the camera and other signs of operation for a few seconds, then disconnects, connects again, disconnects etc, then the app complains over connectivity and suggests to restart the camera...
Similarly, flashdrives are first mounted, then unmounted unexpectedly, then reported as damaged (though still fine on a PC and chkdsk finds nothing).
I believe it is not cable-related because I've tested 3 different OTG cables for the S2, two of them new, and one of them had once worked fine with flashdrives. But that was with Android 2.3.6 before upgrade to ICS, and I also had to replace the USB&MIC board in the phone due to a charging problem (both rev.2.2) in between.
USB Host Diagnostics says GT-I9100, IML74K/XWLPD, verdict Yes/Full. But the test is not long enough I guess.
Normal USB storage connection to PC still works fine (normal cable not OTG for this one).
Should I try another USB&MIC board, or is this more likely a software issue? I've managed to google up a couple of similar case with flashdrives, with no solution, maybe didn't use good keywords. Any suggestions?
Click to expand...
Click to collapse
As you have tried with 3 different cables I guess it's a software issue, most probably the usb host driver's settings must be corrupted , try a factory reset, and if that doesn't work flash with a stock firmware, try upgrading to Jelly Bean or if you like ICS getting the same firmware and re flashing ain't a bad idea, also since you are rooted try flashing through Mobile Odin if you don't want to go through the hassle of flashing through the computer.
Edit : I don't think it could be a hardware problem as the device when it becomes a slave device works normally and is only having this issue when it becomes master device, only after trying above things you need to think about a replacement.
Sent from my GT-P6200 using xda app-developers app

---

king_below_my_lord said:
As you have tried with 3 different cables I guess it's a software issue, most probably the usb host driver's settings must be corrupted , try a factory reset, and if that doesn't work flash with a stock firmware, try upgrading to Jelly Bean or if you like ICS getting the same firmware and re flashing ain't a bad idea, also since you are rooted try flashing through Mobile Odin if you don't want to go through the hassle of flashing through the computer.
Edit : I don't think it could be a hardware problem as the device when it becomes a slave device works normally and is only having this issue when it becomes master device, only after trying above things you need to think about a replacement.
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
Tnx. I thought that'd be one way to start. But I'm not so proficient in this flashing business. I think the ICS update brought me less good than hassle, I've wasted a couple of days fixing things. I'm not rooted yet and I was also considering warranty service, but that'd mean trips to the centre and a week without the phone, and I'd want a thorough backup first and that'd require rooting and unrooting AFAIK... ugh. They're probably better for flashing than me, but I guess they might have not tried OTG in their lives
I was wandering if somebody here knows something about the cause of such specific issue, where a working connection drops after a few seconds.

---

_sem_ said:
Tnx. I thought that'd be one way to start. But I'm not so proficient in this flashing business. I think the ICS update brought me less good than hassle, I've wasted a couple of days fixing things. I'm not rooted yet and I was also considering warranty service, but that'd mean trips to the centre and a week without the phone, and I'd want a thorough backup first and that'd require rooting and unrooting AFAIK... ugh. They're probably better for flashing than me, but I guess they might have not tried OTG in their lives
I was wandering if somebody here knows something about the cause of such specific issue, where a working connection drops after a few seconds.
Click to expand...
Click to collapse
Flashing a stock rom of the same region of your device won't actually void your warranty, you don't need root for that if you are doing it via PC Odin, but since you're not sure I won't recommend it, and I had something similar with my Galaxy Tab 7 plus with stock honeycomb, the connection flickers the first few attempts (I have tried more than 10 time's), first time connected and BAM suddenly some weird error, then it always on connection showed device corrupted, then after some time BAM!! Connected, then normal use, my God!! I also had to face the write_media_storage permission problem too, but all in all I upgraded, then flashed and flashed and finally reached JB aah smoothness bonanza USB OTG works like a charm.
Edit : and for the record Galaxy Tab 7 Plus is S2 with a large ugly screen.
Sent from my GT-I9100 using xda app-developers app

---

king_below_my_lord said:
Flashing a stock rom of the same region of your device won't actually void your warranty, you don't need root for that if you are doing it via PC Odin, but since you're not sure I won't recommend it, and I had something similar with my Galaxy Tab 7 plus with stock honeycomb, the connection flickers the first few attempts (I have tried more than 10 time's), first time connected and BAM suddenly some weird error, then it always on connection showed device corrupted, then after some time BAM!! Connected, then normal use, my God!! I also had to face the write_media_storage permission problem too, but all in all I upgraded, then flashed and flashed and finally reached JB aah smoothness bonanza USB OTG works like a charm.
Edit : and for the record Galaxy Tab 7 Plus is S2 with a large ugly screen.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
I'm not sure if stock JB is ready at my operator. I've had second thoughts about updating via cable when the USB port is under suspicion. And I hear about nasty developments from Google in recent updates. Since which version is the write_media_storage permission issue?
Btw I've just read in another thread someone found root was required for USB OTG in stock JB?
Is it possible that some odd permission thing would kill USB host comm only after a few seconds?

---

_sem_ said:
I'm not sure if stock JB is ready at my operator. I've had second thoughts about updating via cable when the USB port is under suspicion. And I hear about nasty developments from Google in recent updates. Since which version is the write_media_storage permission issue?
Btw I've just read in another thread someone found root was required for USB OTG in stock JB?
Is it possible that some odd permission thing would kill USB host comm only after a few seconds?
Click to expand...
Click to collapse
No, you don't need root for USB OTG in S2, in some devices yes but S2 no... Because it was one of the widely announced feature during it's release and you don't need to concern about the permission issue.. it's honeycomb only lol.
Edit : I mentioned the permission issue just to show you that I had to go through a lot of trouble connecting OTG with my Tab and on upgrading it with JB everything became smooth as butter. The S2 has never had or never will have this problem.
Sent from my GT-P6200 using xda app-developers app
---------- Post added at 02:48 AM ---------- Previous post was at 02:31 AM ----------
Since you're reluctant to flash via a micro usb port under suspicion I have an idea to flash without touching the computer.. It's actually safe I guess in comparison. It's actually like this :
1.Root device using Exynos Abuse App(I guess you will trigger the counter though)
2 .Install Mobile Odin App
3.Flash your stock firmware via Mobile Odin.
4.Done and Done.
Sent from my GT-P6200 using xda app-developers app

---

king_below_my_lord said:
No, you don't need root for USB OTG in S2, in some devices yes but S2 no... Because it was one of the widely announced feature during it's release and you don't need to concern about the permission issue.. it's honeycomb only lol.
Edit : I mentioned the permission issue just to show you that I had to go through a lot of trouble connecting OTG with my Tab and on upgrading it with JB everything became smooth as butter. The S2 has never had or never will have this problem.
Click to expand...
Click to collapse
I see that was actually an S2 plus (minus?) :laugh:
I'd assume the phone would first check permission, then start talking. This here looks so weird, like it starts normally, then does some periodic check and kills it, reminds me of one piracy protection scheme

---

_sem_ said:
I see that was actually an S2 plus (minus?) :laugh:
I'd assume the phone would first check permission, then start talking. This here looks so weird, like it starts normally, then does some periodic check and kills it, reminds me of one piracy protection scheme
Click to expand...
Click to collapse
Ah lol now I understand what you're referring to about that root requirements I saw your other post, in JB one thing was removed that is not USB OTG the thing that needs root is UMS or USB Mass Storage, ie if you have tried connecting to a computer in GB or ICS you can either connect via MTP or UMS for file transfer Samsung removed USB storage mode in JB update.
Sent from my GT-P6200 using xda app-developers app

---

I tried a couple more things, without changing anything.
The USB Host Controller app. I'm not sure if it is supposed to work correctly without root. On the Info tab it says
S3C USB host driver NOT found
Root hub present, USB host mode is active.
On the USB tab it does shoe the Nikon D90 camera when connected.
I've also tried an USB mouse but it doesn't show it, nor does the mouse light up, nor there is any mouse cursor.
Googling around I understand the mouse does not show up because of a Samsung "whitelist" blocking it. I gather more USB devices used to work earlier but the whitelist leaving only flashdrives mainly came with 4.0.3 update? I could only find hearsay, is there an official Samsung policy regarding this?
And there was a reference to a Siyah kernel which should restore this... or there are perhaps other popular ones that fix this?
And, since the mouse doesn't show up at all, I assume this whitelist has probably nothing to do with my original problem?

---

_sem_ said:
I tried a couple more things, without changing anything.
The USB Host Controller app. I'm not sure if it is supposed to work correctly without root. On the Info tab it says
S3C USB host driver NOT found
Root hub present, USB host mode is active.
On the USB tab it does shoe the Nikon D90 camera when connected.
I've also tried an USB mouse but it doesn't show it, nor does the mouse light up, nor there is any mouse cursor.
Googling around I understand the mouse does not show up because of a Samsung "whitelist" blocking it. I gather more USB devices used to work earlier but the whitelist leaving only flashdrives mainly came with 4.0.3 update? I could only find hearsay, is there an official Samsung policy regarding this?
And there was a reference to a Siyah kernel which should restore this... or there are perhaps other popular ones that fix this?
And, since the mouse doesn't show up at all, I assume this whitelist has probably nothing to do with my original problem?
Click to expand...
Click to collapse
Typing this using a mouse in stock rom.
Edit :As you can see that above statement is written using a mouse in pure stock JB, so I don't think Samsung has blacklisted anything and and the mouse used is some unknown weird brand. Since your mouse didn't even light up, I'll say it may be something other than host driver issue, because the host device will always provide the power, you may possibly be facing a hardware issue, the only thing that can assure that it's not a software issue is a flash using a stock rom, or try cm9 stable I recall that OTG worked perfectly in it. Since you're afraid of flashing via a computer, I'll tell you certain steps which will help you flash without using a cable or a computer :
1.Root using Exynos Abuse App (preferably chain fire's app) (search, read and download)
2 . Install Mobile Odin and set it up.
3.Download a stock rom or custom rom(you must read very carefully) , preferably JB.
4.Flash via mobile Odin.
5.make sure you read all related threads several times.
Sent from my GT-P6200 using xda app-developers app

---

king_below_my_lord said:
Typing this using a mouse in stock rom.
Edit :As you can see that above statement is written using a mouse in pure stock JB, so I don't think Samsung has blacklisted anything and and the mouse used is some unknown weird brand. ....
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
So you think these are nonsense?
http://forum.xda-developers.com/showthread.php?t=1768119
http://poke64738.iphpbb3.com/forum/...-galaxy-s2-gt-i9100-usb-hid-support-t105.html
http://techblog.goelite.org/kernel-modifications-for-usb-client-devices-of-samsung-galaxy-i9100-s2/
http://forum.xda-developers.com/showthread.php?t=1246116
Notice it is SGS2 specific, not Samsung or ICS general. You are using a Galaxy Tab I gather?
I've tried three Logitech mice and one Labtec.
Not that I'd want to use a mouse (a keyboard might be more useful), just want to see what's going on with USB host.

---

_sem_ said:
So you think these are nonsense?
http://forum.xda-developers.com/showthread.php?t=1768119
http://poke64738.iphpbb3.com/forum/...-galaxy-s2-gt-i9100-usb-hid-support-t105.html
http://techblog.goelite.org/kernel-modifications-for-usb-client-devices-of-samsung-galaxy-i9100-s2/
http://forum.xda-developers.com/showthread.php?t=1246116
Notice it is SGS2 specific, not Samsung or ICS general. You are using a Galaxy Tab I gather?
I've tried three Logitech mice and one Labtec.
Not that I'd want to use a mouse (a keyboard might be more useful), just want to see what's going on with USB host.
Click to expand...
Click to collapse
Lol friend, I use a s2 also but also have galaxy tab 7+ which is just like a galaxy s2 but with a huge screen, like I was saying, Samsung may have created a whitelist with ics, but not in JB as I clearly used a mouse in JB, in my s2 I am using a custom kernel so I am not sure about stock in s2 but since now stock JB in my tab support it then stock JB in s2 should also support it. I am suggesting that Samsung must have removed the whitelist limitation in JB.
I am saying this whitelist thingy might be ics specific because in GB stock mouse used to work in my s2, I would have tested it out for you if it weren't ics, ics 4.0.4 stock kernel contains a dangerous brick bug and I don't wanna go anywhere near an ics stock kernel (even though there are other version's which are said to be safe, my heart ain't strong enough to take a risk with stock kernels)
Sent from my GT-I9100 using xda app-developers app