Develop Bugs

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

Nexus 5X - included USB 3 cable only for charging??

I have a brand new Nexus 5X, a brand new high-end laptop with a USB 3 port with a fresh installation of Windows 7 Professional onboard.
I CANNOT get any of the drivers I have tried (all fresh downloads - Google, universal, etc.) to work with my phone. When plugging in the cable, phone to PC, I get an error Code 10 - "Cannot start the device".
I see in Heisenberg's guide for unlocking and rooting the 5X this post from user AquilaDroid - http://forum.xda-developers.com/showpost.php?p=63080921&postcount=9
Saying "Might want to point out the cable /adapter required to connect to pc. (I just saw that it's not included with the phone.)"
Does this mean the cable included with the phone is not sufficient for data transmission?? Does this correspond to my Code 10 error?

I bought an iOrange and it works great for my charging, data transfer, and app development
Sent from my Nexus 5X using Tapatalk

Code 10 is not a cable problem but rather a driver installation issue. Did you install try to install unsigned drivers without disabling signature verification?
Install the ones from Google or the full SDK. Also try to change the more to MTP on the phone.

Alferboy said:
Code 10 is not a cable problem but rather a driver installation issue. Did you install try to install unsigned drivers without disabling signature verification?
Install the ones from Google or the full SDK. Also try to change the more to MTP on the phone.
Click to expand...
Click to collapse
I did try the drivers from Google and from the SDK; still got the Code 10. I said OK to the unsigned driver message and still got the error. Is there something else I must do for the unsigned driver verification?

If you get code 10 the device is seen. Can you check with which hardware ids?
Also you can try uninstalling all drivers. Try usbview.
Sent from my Nexus 7 using Tapatalk

If you pull down the notifications on the N5X it should say USB Charging, click on it and change it to MTP.
Sent from my Nexus 5X using Tapatalk

are you using a USB C to USB A cable? Or does your laptop actually have a USB C port on it?

Thanks for the responses, but I have been thorough to the extent of my knowledge. To outline my situation:
- brand new laptop with USB 3 port and fresh Win7 Pro
- brand new Nexus 5X with included USB 3 cable
- Developer options - OEM locking and USB debugging ticked
- USB configuration as MTP, also tried PTP - this is also in Developer options; I get no pull-down or choice when plugging in
- Tried drivers from Google, from the Extras folder in SDK, Universal - uninstalled and removed driver files between each attempt
- Turned off Unsigned driver verification in BIOS
I get Code 10 error every time.
In USBview nothing indicates that anything is connected when plugging in phone.
I don't know what to make of the hardware ids.
I'm still curious about this cable, the one that came with the phone from Google, and AquilaDroid's comment indicating that it is not the one required to connect to a PC....
Any other ideas, given all this info???

sordup said:
Thanks for the responses, but I have been thorough to the extent of my knowledge. To outline my situation:
- brand new laptop with USB 3 port and fresh Win7 Pro
- brand new Nexus 5X with included USB 3 cable
- Developer options - OEM locking and USB debugging ticked
- USB configuration as MTP, also tried PTP - this is also in Developer options; I get no pull-down or choice when plugging in
- Tried drivers from Google, from the Extras folder in SDK, Universal - uninstalled and removed driver files between each attempt
- Turned off Unsigned driver verification in BIOS
I get Code 10 error every time.
In USBview nothing indicates that anything is connected when plugging in phone.
I don't know what to make of the hardware ids.
I'm still curious about this cable, the one that came with the phone from Google, and AquilaDroid's comment indicating that it is not the one required to connect to a PC....
Any other ideas, given all this info???
Click to expand...
Click to collapse
Please help.

Included cable IS only for charging
Well, since my questions seemed to have stumped folks here - no doubt the newness of these phones have people a little in the dark still - and for the benefit of others with the same problem, I have discovered a solution here.
The included USB 3 type C cable that comes with the Nexus 5X apparently is only for charging. As my issue outlined above showed, I could get no connectivity to my computer for file transmission with it. Upon getting a USB C to USB A cable, however, plugging into my computer worked as it should: device recognized, choice offered in the phone's pull-down menu for USB connection type (charging, MTP, or PTP), and flawless connection and file transmission.
There you have it.

metpage said:
are you using a USB C to USB A cable? Or does your laptop actually have a USB C port on it?
Click to expand...
Click to collapse
The OP has not responded to this question...
Inviato dal mio Nexus 5X utilizzando Tapatalk

I think there is a problem with USB 3 type A - type C cable. I have one ( my N5X is from LG distribution, we don't have gplay for devices) and he is works only as charging cable. I tried USB 2.0 , USB 3 even USB 3.1 and still only charging. According to my knowledge N5X have USB 2.0 with type C connector.
Odesláno z mého Nexus 5X pomocí Tapatalk

I had the same issue as you. I have a method for you to try, as it worked for me!
Hook your Nexus 5X to your computer
Go into your System / Device Manager
You should now see a device listed with an ! or something (will be your 5X)
Ok, now right click the unknown device (5X) and update driver. Click the select file manually option. Direct it to your android-sdk\Extras\Google. No further. It should now install your USB driver. This is what I had to do to get mine to work. First I tried pointing it further and closer in the SDK file but it didn't work. When I pointed it to the google folder, it installed an boom.

My computer reads a device connected, but then immediately freaks out and shuts the USB3.1 port off. I'm thinking it's expecting a 3.1 device, but it's getting a 2.0 device. Or even possibly that the USB3.1 card doesn't supply enough current to satisfy the N5X's thirst. I dunno, maybe it's just a Windows 10 bug. A USB-C to USB-A (A Host USB2.0) works just fine.

Nexus 5X USB Device Not Working Please Help

Hello, whenever I plug in my Nexus 5X to my computer, it says that the USB device is not working properly. When I check my installed USB drivers it shows:
USB Device Not Recognized (Device Descriptor Request Failed)
Can someone help me? I would like to do USB Debugging

rpalmon said:
Hello, whenever I plug in my Nexus 5X to my computer, it says that the USB device is not working properly. When I check my installed USB drivers it shows:
USB Device Not Recognized (Device Descriptor Request Failed)
Can someone help me? I would like to do USB Debugging
Click to expand...
Click to collapse
If you are on win10 the builtin drivers and drivers you ask win10 to download are all you need. If you are on older platform like winxp or vista, try these:
http://forum.xda-developers.com/nexus-5x/general/psa-fix-adb-doesnt-winxp-t3403955

sfhub said:
If you are on win10 the builtin drivers and drivers you ask win10 to download are all you need. If you are on older platform like winxp or vista, try these:
http://forum.xda-developers.com/nexus-5x/general/psa-fix-adb-doesnt-winxp-t3403955
Click to expand...
Click to collapse
It was working before but now it says USB Device Not Recognized (Device Descriptor Request Failed) when I check the installed USB Drivers.

rpalmon said:
It was working before but now it says USB Device Not Recognized (Device Descriptor Request Failed) when I check the installed USB Drivers.
Click to expand...
Click to collapse
Try different cable and/or different port.

rpalmon said:
It was working before but now it says USB Device Not Recognized (Device Descriptor Request Failed) when I check the installed USB Drivers.
Click to expand...
Click to collapse
Is there a driver that I could install to fix it?

rpalmon said:
Is there a driver that I could install to fix it?
Click to expand...
Click to collapse
The error you listed doesn't sound like a software problem. It sounds like there is a USB communication issue.
Even with no drivers installed, your PC should be able to get the USB device descriptor, otherwise it couldn't figure out which driver to use.

sfhub said:
The error you listed doesn't sound like a software problem. It sounds like there is a USB communication issue.
Even with no drivers installed, your PC should be able to get the USB device descriptor, otherwise it couldn't figure out which driver to use.
Click to expand...
Click to collapse
The thing is that I have other Android devices and when I plug them in USB debugging works fine. I think that it has to do with the Android N update because ever since I updated it never worked.

rpalmon said:
The thing is that I have other Android devices and when I plug them in USB debugging works fine. I think that it has to do with the Android N update because ever since I updated it never worked.
Click to expand...
Click to collapse
It's possible or it could be coincidental. My Android N update didn't affect my USB operations or USB ID at all though.
It could also be something went bad with your USB port on the phone.
See if there is any lint inside the port using bright pencil flashlight.
Also try different USB A to C cable if that is what you are using, sometimes cables go bad.

sfhub said:
It's possible or it could be coincidental. My Android N update didn't affect my USB operations or USB ID at all though.
It could also be something went bad with your USB port on the phone.
See if there is any lint inside the port using bright pencil flashlight.
Also try different USB A to C cable if that is what you are using, sometimes cables go bad.
Click to expand...
Click to collapse
what do you mean by lint?

sfhub said:
It's possible or it could be coincidental. My Android N update didn't affect my USB operations or USB ID at all though.
It could also be something went bad with your USB port on the phone.
See if there is any lint inside the port using bright pencil flashlight.
Also try different USB A to C cable if that is what you are using, sometimes cables go bad.
Click to expand...
Click to collapse
I also tried factory resetting the phone and that didn't work.

rpalmon said:
what do you mean by lint?
Click to expand...
Click to collapse
Lint/dust. Sometimes it gets into the port and interferes with the connections.
Airblow sometimes helps.
Just a shot in the dark.

USB 2.0 vs USB 3.1 Type C cable

Now I have several Type C cable including two 3.1 (Belkin and Anker) cable.
All charge fine, but I realized 3.1 cable has problem on file transfer (computer cannot recognize), but all 2.0 type C cables work 100%.
It's probably H918 isn't compatible with USB3.1.
---- update ----
Install latest USB driver fixed the problem
http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425

mingkee said:
Now I have several Type C cable including two 3.1 (Belkin and Anker) cable.
All charge fine, but I realized 3.1 cable has problem on file transfer (computer cannot recognize), but all 2.0 type C cables work 100%.
It's probably H918 isn't compatible with USB3.1.
Click to expand...
Click to collapse
Is there a question you're asking or is this just an observation?

sanjsrik said:
Is there a question you're asking or is this just an observation?
Click to expand...
Click to collapse
My opinion.
The phone only works with USB2.0

mingkee said:
My opinion.
The phone only works with USB2.0
Click to expand...
Click to collapse
I can confirm. However USB 3.1 cables work for transfers in TWRP.

I figured out why.
Make sure you have latest USB driver.
If you have LG Bridge, update to the latest driver.
If you installed LG United Driver, make sure it's 4.2.0
http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
After updated the driver, both 2.0 and 3.1 cable work properly.

I have 4.1.1 and it won't recognize my USB 3 cables, both from Anker... well, it won't recognize properly if I choose file transfer, but it works fine if I choose picture transfer or use them on USB 2.0 ports. any suggestions?

dimm0k said:
I have 4.1.1 and it won't recognize my USB 3 cables, both from Anker... well, it won't recognize properly if I choose file transfer, but it works fine if I choose picture transfer or use them on USB 2.0 ports. any suggestions?
Click to expand...
Click to collapse
Try LG Bridge
BTW, the latest United Driver version is 4.2.0

Some crap with windows. It took me hours but I finally was able to get the usb 3.1 cable to transfer files. I couldn't tell you what I did though. It wasn't drivers though. It was all windows.

Is there any difference in charging times between USB 2.0 and 3.1, if you're using a type-C QC3.0 power adapter?

weirdg said:
Is there any difference in charging times between USB 2.0 and 3.1, if you're using a type-C QC3.0 power adapter?
Click to expand...
Click to collapse
I'm also interested in this. I don't think there should be a difference.

Galaxy A5 2017 USB 3.0 support

I have a replacement cable.
I tried plugging in my device in my laptop using USB 3.0 port but it only charges my phone, it doesn't detect the MTP to transfer files. But when I tried plugging it in in the USB.. 2..0 port, MTP works.
My question is, is this because of the cable? Or is the A5 not supported by USB 3.0?

patz0110 said:
I have a replacement cable.
I tried plugging in my device in my laptop using USB 3.0 port but it only charges my phone, it doesn't detect the MTP to transfer files. But when I tried plugging it in in the USB.. 2..0 port, MTP works.
My question is, is this because of the cable? Or is the A5 not supported by USB 3.0?
Click to expand...
Click to collapse
Mine works on a USB 3.0 port.
USB 3.0 should be backwards compatible to USB 2.0, so I think it's the cable. Maybe you could try again on a different pc? Just to be sure.

If you're using Windows check your device manager to see what it says, maybe a specific usb driver is needed?

i have same problem.
many time ago my phone (A5 2017) recognize with my laptop but after some update its not recognize in laptop but detect in office PC.
i do some work like change windows , reinstall add driver, use linux but not work in laptop. its now just work with one PC in office and other PCs not work. (

visit this site for your question " https://www.gsmarena.com/samsung_galaxy_a5_(2017)-8494.php "