This question was closed Aug 11, 2015 at 01:33 AM by Eric5h5 for the following reason:

Question is off-topic or not relevant

Question by orangeflame · Aug 11, 2015 at 01:19 AM · android detection connection unity remote usb

ANDROID: Why are my new phone cables bad but my old ones good?

Still an unity issue but I found a working cord. If anyone can figure that out it would be nice.

Okay so, for some reason, unity never detect my Samsung galaxy s5 when I used any cable other then this old damage one that I had to plug in at weird angle to even use as a charger. I was fine with that until someone decided this cord was no good and threw it out. Now I have no working cord to connect my phone to test out my mobile games on.

All I want to know is why did this old cord work so I know what to buy to replace it.

Also, if I haven't made it clear, I know everything is set up right and has worked before with the old cord and if you still don't believe me. I have debugging mode on, I make sure my phone is connected with unity remote 4 on and running before I start unity on the computer, I have the editor set to use any device, I have the build set to android, and, if you for any reason you still think it is not the cord, I will say it again I have been able to connect with the old cord before and I have all the same settings except the old cord. So the issue has to be the cord.

Add comment · Show 4

Eric5h5 · Aug 11, 2015 at 01:33 AM 0

If it's the cord, then this isn't a Unity question.

orangeflame · Aug 11, 2015 at 02:16 AM 0

This is a unity issue because everything detects my phone but unity. So why is unity being picky about my cord?

Cricroo · Sep 18, 2015 at 01:05 PM 0

I had the same issue and I resolve it in exiting and relaunching Unity each time I change my cable :S

Bunny83 · Sep 18, 2015 at 02:15 PM 0

It's still not a Unity question as Unity simply uses the ADB (Android Debug Bridge) that comes with the Android SD$$anonymous$$. If Unity can't detect it properly then ADB most likely wouldn't either.

Try executing the "devices" command manually on the windows console. If it lists your device, try "logcat". If that works as well, make sure your Unity installation uses the correct AndroidSD$$anonymous$$.

If those commands do not work, there's a problem with either your device, your cable, your USB driver, your SD$$anonymous$$ installation or your USB connection in general. $$anonymous$$ake sure your devices is switched on and unlocked. Also make sure you enabled USB debugging in the developer settings.