Develop Bugs

[HOW-TO] Enable OTG(USB HOST) on Galaxy SII

So after painstakingly searching around for an answer on how to get OTG working on the galaxy s2 running a custom ROM and Kernal with little to no help i finally figured it out:
You will need:
OTG Cable ( Micro USB Host cable) (store bough or home made work, i followed this link: http://highonandroid.com/android-howtos/how-to-make-otg-usb-host-cable-for-galaxy-s2-or-xoom/ )
A Kernel that supports OTG ( I'm using { and could only find } http://www.gokhanmoral.com/gm/2012/05/06/siyahkernel-v3-2rc1/ , there is an update to this kernal , but i have not tested the OTG support yet (May/7)
And last but not least, USB Host Controller APP : https://play.google.com/store/apps/details?id=hu.sztupy.android.usbhostcontroller&hl=en
Procedures :
1. Install the kernel by flashing it through CWM
2.Install USB Host Controller App
3. Restart phone
4. plug in usb device into OTG cable
5. Plug in OTG Cable to phone
6. TADAA
if you have any questions feel free to PM me or post a reply...
i had to change the steps from the link to make the OTG cable to make it work!!!
Homemade Cable Troubleshoot:
my cable was a samsung USB U2 cable, i dont know if this makes the biggest difference. but you want to short ( connect) pins 4 and 5.. one of the 2 solder points is the black wire from the usb cable ( ground) and if yours doesnt work with the pin he says to use, you can try plugging in a usb device into the cable and have the wire connected to the ground and simply probe the other pins until you find the pin that works! ( DO NOT CONNECT BLACK AND RED I REPEAT DO NOT SHORT BLACK AND RED, YOU WILL FRY YOU PHONE AND I TAKE NO RESPONSIBILITY FOR THIS, THIS IS YOUR WARNING!!!)

This kernel can work with Galaxy s2 duos tv gt-s7273T ?
I,m trying enable the OTG to my s2 gt-s7273T
This is possible? Using Jelly Bean 4.2.2 stock rooted
With busybox installed .
Please if possible help me

WOW! I have a faulty micro sd card so I could only backup to internal storage. Saw your post which reminded me I have an OTG cable that I use for my Note 4, I'm using CM11 and "hey presto!" CM11 recognizes external USB, no apps needed, I could/can make backups, Love my CM11
Glad I saw your post, Many Thanks, and Kind Regards!!

[Q] Note II, adb and USB 3.0

Hello All,
I spend two days trying to connect my note 2 with my laptop via usb debugging mode. Unfortunately i always get information (after execute 'adb kill-server, adb start-server, adb devices') that my phone is unauthorized.
I read few articles with info that usb 3.0 doesn't work with usb debugging mode and more info that it is working fine... Now don't know where is the truth.
My laptop has only 3x USB 3.0. I connected my note 2 to my gf's laptop via USB 2.0 and everything was fine. Then I connected her galaxy s mini to my laptop via usb 3.0 and debugging mode and everything was fine too... I get rsa fingerprint popup which i didn't get on my note 2 via usb 3.0.
I have windows 7 x64, all newest drivers (samsung usb driver, adb, sdk etc) and on my note 2 i have Adnroid 4.3 JB.
Does anyone had this issue?
Regards.

OTG

Does Nokia N1 got OTG support? I have Tried to connect my USB Flash through OTG cable but doesn't work for me ....

Doesn't work for me either >_<

I don't have an otg cable myself (yet) but can you try to use USB Host Diagnostics (available in play store) and post the report?

FYI I got an OTG cable myself and it didn't work. I dug a bit deeper and found out that OTG is most likely not implemented because Nokia N1 is using legacy usb controller over usb C - see below:
Converting USB 2.0 OTG SoCs to USB Type-C
While existing Device, Host, and DRD devices can be converted to support the USB Type-C connection with some effort, it is not practical to convert existing OTG SoCs. OTG requires a new state machine using the configuration channel to support USB Type-C. Host Negotiation Protocol is used to swap host and device role for OTG, while Power Delivery communication is used to change roles for USB Type-C. Combined, these challenges preclude simple upgrades of OTC SoCs to USB Type-C. - See more at: https://www.synopsys.com/Company/Pu...esign-type-c-2015q1.aspx#sthash.Ri02Guwe.dpuf
Click to expand...
Click to collapse
The only chance to get otg to work is most likely preparing a kernel patch (are the sources even available?) to manually switch the connector to host mode and power the attached device externally

After a bit of hacking around I was able to enable usb otg on my N1!
I've had a look at kernel sources for device with similar SoC (Nexus Player) and saw an interesting debugfs entry. To my surprise it worked like a charm and immediately detected the attached usb hub with a thumb drive, it even powered the hub so I didn't have to use an external power source!
To enable host mode, the following command has to be enterted in root console:
echo A > /sys/kernel/debug/usb/dwc3_debugfs_root/otg_id
Caveats (will try to find a way to resolve them):
- after enabling host mode N1, won't charge from the usb port - a reboot is required to enable the charging again
- probably same is true for pheripherial mode (connecting n1 to a pc). In theory, changing a to b in the above echo command should bring the tablet back to normal mode but for some reason it won't charge without a reboot so I'm assuming that same is true for non otg usb connectivity. Will have a look at the sources and debug messages to find out what's going on

wodz69 said:
After a bit of hacking around I was able to enable usb otg on my N1!
I've had a look at kernel sources for device with similar SoC (Nexus Player) and saw an interesting debugfs entry. To my surprise it worked like a charm and immediately detected the attached usb hub with a thumb drive, it even powered the hub so I didn't have to use an external power source!
To enable host mode, the following command has to be enterted in root console:
echo A > /sys/kernel/debug/usb/dwc3_debugfs_root/otg_id
Caveats (will try to find a way to resolve them):
- after enabling host mode N1, won't charge from the usb port - a reboot is required to enable the charging again
- probably same is true for pheripherial mode (connecting n1 to a pc). In theory, changing a to b in the above echo command should bring the tablet back to normal mode but for some reason it won't charge without a reboot so I'm assuming that same is true for non otg usb connectivity. Will have a look at the sources and debug messages to find out what's going on
Click to expand...
Click to collapse
Thanks for your hard job.
I have tried on my N1. It is amazing that otg did work. However, the otg can not coexist with charging function as yours. Hope someone could find a solution.

adagiov said:
Thanks for your hard job.
I have tried on my N1. It is amazing that otg did work. However, the otg can not coexist with charging function as yours. Hope someone could find a solution.
Click to expand...
Click to collapse
Hey,
Are you on Android 5.1.1 or 5.0 ?
I've had a look at the code of the usb driver of the a phone with similar chipset (asus zenfone 5) and it seems that the source of the problem is that the tablet fails to detect an appropriate charger type, which could mean either that the otg cable does not support this or the code of the driver does not work properly with usb C. Was wondering if something changed around this after the update?

wodz69 said:
Hey,
Are you on Android 5.1.1 or 5.0 ?
I've had a look at the code of the usb driver of the a phone with similar chipset (asus zenfone 5) and it seems that the source of the problem is that the tablet fails to detect an appropriate charger type, which could mean either that the otg cable does not support this or the code of the driver does not work properly with usb C. Was wondering if something changed around this after the update?
Click to expand...
Click to collapse
Hi, mine N1 is still running the android 5.0.
I am afraid Root is the prerequisite to hack otg. Unfortunately, root is not available on android 5.1.1 till now, so even the android 5.1.1 driver support it, that won't help.
Thanks,dude.

Yeah exactly for that reason I haven't upgraded my tablet yet

PS4 controller on S4 Mini Duos problem

Hello everyone!
I have got a Galaxy S4 Mini (I9192) and I try to connect my PS4 controller to it, in order to use PS4 modded remote control app, but the phone does not recognise it. I use CM13 latest build by @csendre , custom kernel by @DarkFrenzy and TWRP 3.0.2-1 by @ne0zone75 as well, but I cannot control the phone through my controller. Inside TWRP, in mount option, I cannot enable USB OTG, and using OTG Troubleshooter app, it has crosses on two last lines (not recognized by Linux and not recognised by Android). I have also connected USB flash drive without any luck... So, is there any way to use USB OTG or is it a hardware limitation of the phone?
Thank you a lot!

bobo1704 said:
Hello everyone!
I have got a Galaxy S4 Mini (I9192) and I try to connect my PS4 controller to it, in order to use PS4 modded remote control app, but the phone does not recognise it. I use CM13 latest build by @csendre , custom kernel by @DarkFrenzy and TWRP 3.0.2-1 by @ne0zone75 as well, but I cannot control the phone through my controller. Inside TWRP, in mount option, I cannot enable USB OTG, and using OTG Troubleshooter app, it has crosses on two last lines (not recognized by Linux and not recognised by Android). I have also connected USB flash drive without any luck... So, is there any way to use USB OTG or is it a hardware limitation of the phone?
Thank you a lot!
Click to expand...
Click to collapse
I did not use a controller with the S4 mini, however I used USB OTG functions with no issues, but you need to supply power so use a Y cable. Our hardware can not supply power through the USB port

[SOLVED] help resetting back to stock (flo) (Q)

hi, I just installed the beta build of the AOSP Oreo Rom and soon after finding working-ish gapps twrp was gone, and I hadn't had a chance to root yet, and so i went to my computer to manually flash recovery but my device refuses to get recongized, i have installed latest google and universal drivers, but they dont show up for me to set them to my nexus. Im running Latest win10 on my desktop, using a known good usb cable and have switched between the only usb 2.0 ports i have (2) i've tried in normal boot state and in fastboot, but the drivers wont match up to proceed. does anyone know anything about this, is this an issue with win10 or is it something else?

Do assuming that no one has encountered this before I guess I'll just wait until a app that can root comes out for Oreo and hopefully that can get me fixed up but if in the meantime someone comes across this and actually has some insight any help would be very much appreciated.

deathblade said:
someone comes across this and actually has some insight any help would be very much appreciated.
Click to expand...
Click to collapse
Since fastboot does not work then do the following:
win10 may be broken, check for flo ID = 18D1:4EE0 using alternative OS - if it still does not work then...
repair broken N7 USB port or re-seat the wide silver cable to fix USB data lines
:good:

Thank for your suggestion, I'm downloading the iso right now, will post back after following instructions, hope this works

ok, just followed your instructions, and this is what i got
[email protected] ~ $ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 13fe:5500 Kingston Technology Company Inc.
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 004: ID 04f2:b40e Chicony Electronics Co., Ltd HP Truevision HD camera
Bus 002 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[email protected] ~ $
I dont see the ID you are referring to

Also I reseated the cables with no change and visually inspected the port and solder joints and all seem ok, here are a few pics ( I apologise about any quality issues, I'm not a photographer) EDIT: so I verified the data connection works just fine, was able to view contents on an otg flash drive, is there anyway to use an otg flash drive to force auto install a custom recovery?

deathblade said:
EDIT: so I verified the data connection works just fine, was able to view contents on an otg flash drive
Click to expand...
Click to collapse
I see that your laptop has both USB2 and USB3 ports. Please boot N7 in fastboot mode, connect it to USB2 then USB3 while checking lsusb for the ID. Note that the ports use different PC hardware and drivers and one of them appear to be either unsupported or faulty.
Also "a known good usb cable" may be good for charging but not for data transfer so just try another one.

Had a comparable issue recently due to win10 preferring some default driver over Google driver for fastboot.

k23m said:
I see that your laptop has both USB2 and USB3 ports. Please boot N7 in fastboot mode, connect it to USB2 then USB3 while checking lsusb for the ID. Note that the ports use different PC hardware and drivers and one of them appear to be either unsupported or faulty.
Also "a known good usb cable" may be good for charging but not for data transfer so just try another one.
Click to expand...
Click to collapse
Ok just tried with usb 2 and 3.0 ports same result, but oddly the listing does differ from my previous, it is now show an Intel device (I assume my CPU or a chipset) that wasn't listed before. But still no Nexus. Will try with a different cables later today as I have to hunt one down (just moved)

ok, so i just found another cable (with builtin otg usb port ) and even in windows 10 it worked just fine, thank you so much for your help. the cable i was using before was an anker gold tipped nylon braided 10ft usb cable, my guess is that at 10ft it has too much resistance to actually work properly for such data based tasks. I will at some point get another (smaller) anker cable to test this theory