Hi all,
Got a bit of a random problem here. In the last couple of days my Tytn II stopped recognising the USB (wired) handsfree kit. It would simply continue to play sound to the normal speaker, rather than through the headphones.
Fairly simple issue, you might think - either the handsfree or the USB port. Except that the phone will connect to my PC via USB, and recognise that it's connected. And when I connect a friend's working USB handsfree kit (from an Orange SPV phone), I have the same problem on my phone.
Anyone got any ideas as to what the frig is going on and how I might fix it?
Thanks!
your device's usb port has crapped out...
from what i've read on countless other threads in this section of the kaiser forums, the usb port on your device has TWO sets of connections...
...the pins along the top and the pins along the bottom...one is for usb syncing and the other is for audio input/output...
...put your device under a strong light and (use a magnifying glass?) to check for bent pins or other wear and tear
...search for the threads i've mentioned for more insight and how to find a replacement part if it is needed in the worst case
good luck!
Ah, gotcha. That sounds more plausible than a driver issue, and would explain the disparity in hardware issues. I'll take a look!
Hello...
My Note 5 Keeps Disconnecting & Connecting rapidly Via USB Cable? I have tried to seek solutions by disabling power management in USB Control but to no avail. Does anyone ever have this same issue & share how to fix this? Thanks in advance
Ihad this problem before. And i found that the problem caused by the cable itself . The note 5 cable is so thin and as you moving it , it will disconnect. I tried to connect my note 5 with old s5 cable . (Thicker one ) and the problem never appear again . Hope that help .
I agree, I had the same problem and found out it was the USB cable itself..
Denim Guy said:
Hello...
My Note 5 Keeps Disconnecting & Connecting rapidly Via USB Cable? I have tried to seek solutions by disabling power management in USB Control but to no avail. Does anyone ever have this same issue & share how to fix this? Thanks in advance
Click to expand...
Click to collapse
Hi,
Firstly, i agree with other posters that it could be Usb cable. However in my case with my old Note 4 I had similar issues with connecting /disconnecting.. rapidly (same as you stated in your post)
I found in my case it was the Note 4 fast charger plug (Not cable.)
If i changed the fast charger plug it would stop disconnecting /connecting. In fact it made a loud
noise /sound in the process that drew my attention as to what was happening. (the phone was making the connection /disconnection noise)
If i changed the charger with my old Note device's charger/ plug it would work correctly. Also if i change
Note 4 fast charger with my Note5 fast charger it would also work correctly.
Good luck
Well...it's getting quite weird actually. Yes i think the problem is actually from my USB cable here, it used to be fine but problems only arose after i upgraded my PC OS from 8.1 to Windows 10 and Note 5 firmware to Marshmallow at the same interval. In my case the charging process with its fast charger adaptor works fine, but not with the data transfer when connected to PC. Since i only have other USB cable from Samsung Tab S, thus what i can conclude is that by using said USB cable, connection to PC was more stable but still sporadically undetected or stopped during data transfer here. And it did not support fast charging despite plugged to Note 5 fast charger adaptor. I suppose not all USB cables support fast charging at all. And there are reports indicating several USB problems conflicting with windows 10 as well. Meanwhile i am still trying to figure this out, i'll keep updated when new progress comes up ok. Thanks for all your attention & inputs, really appreciate it here.
Just bought a new USB data cable for Samsung Note 4, the cable is indeed thicker. Conclusively yes the culprit was the USB cable as no said problems occur anymore while using new cable here.
Hi to everyone. Sorry if I will not be brief, but this problem makes me going crazy.
My previous phone died prematurely, so I bought a shiny Oneplus 3T and I'm very satisfied with it. Problem is, that this new piece of technology has an USB-C connector instead of the good old microUSB one.
In my car (Opel) I put an USB extension cable from the Android Auto unit (Intellilink r4.0) to the inside of the center arm, and since now I used that cable to connect my previous phone to the unit. Cable is 1.8 m long (about 5 ft for English people) and worked very well.
Now there goes the trouble: to connect my new OnePlus, I bought a simple microUSB to C adapter... it works very well at home with my PC but... Android Auto unit doesn't recognize the phone.
It says "connect the USB cable". At the same time, phone is charging, so power is connected to it.
Ok, maybe there are inconsistencies with the USB converter, I thought.
So I purchased a USB A to C cable, 1.8 m long (just like my previous normal microUSB one).
No way. Unit insists to not recognize the connection!?
Now, to cut this long thing out... I tried any combination of things, extenders, adapters... the only way to make things work is to use max a 1 m (3,3 ft) long USB A to C cable. No longer than that. Neither with a short extension cable.
But with 1 m I can't reach the center arm! I need at least 1.2/1.4 m (4-4.5 ft) cable lenght.
So, this is it. Who can be the culprit? AA head unit? Or perhaps Oneplus 3T has a "weak" USB?
I wonder if anyone has experienced issues like this... and if there are workarounds. :fingers-crossed:
jonsat said:
Hi to everyone. Sorry if I will not be brief, but this problem makes me going crazy.
My previous phone died prematurely, so I bought a shiny Oneplus 3T and I'm very satisfied with it. Problem is, that this new piece of technology has an USB-C connector instead of the good old microUSB one.
In my car (Opel) I put an USB extension cable from the Android Auto unit (Intellilink r4.0) to the inside of the center arm, and since now I used that cable to connect my previous phone to the unit. Cable is 1.8 m long (about 5 ft for English people) and worked very well.
Now there goes the trouble: to connect my new OnePlus, I bought a simple microUSB to C adapter... it works very well at home with my PC but... Android Auto unit doesn't recognize the phone.
It says "connect the USB cable". At the same time, phone is charging, so power is connected to it.
Ok, maybe there are inconsistencies with the USB converter, I thought.
So I purchased a USB A to C cable, 1.8 m long (just like my previous normal microUSB one).
No way. Unit insists to not recognize the connection!?
Now, to cut this long thing out... I tried any combination of things, extenders, adapters... the only way to make things work is to use max a 1 m (3,3 ft) long USB A to C cable. No longer than that. Neither with a short extension cable.
But with 1 m I can't reach the center arm! I need at least 1.2/1.4 m (4-4.5 ft) cable lenght.
So, this is it. Who can be the culprit? AA head unit? Or perhaps Oneplus 3T has a "weak" USB?
I wonder if anyone has experienced issues like this... and if there are workarounds. :fingers-crossed:
Click to expand...
Click to collapse
Some of the specs for USB-C cables are less than 1m, depending on what the other connection/adapter is. I guess your PC & car outlets are different specs.
See
http://www.cypress.com/knowledge-ba...ngth-cables-usb-type-c-applications-kba204034
Or maybe your cable is not certified so may be more sensitive to outside interference eg from ignition system.
Uhmmm... very interesting information. I'll try to borrow a "certified" cable. Since now, I tried with normal cables (4 different sizes and brand) to no avail (more than 1 m lenght).
Thanks!
jonsat said:
Uhmmm... very interesting information. I'll try to borrow a "certified" cable. Since now, I tried with normal cables (4 different sizes and brand) to no avail (more than 1 m lenght).
Thanks!
Click to expand...
Click to collapse
Check what is the spec of your USB outlets on car and PC, are they different? Then cable may not make any difference to your result.
I'd think that if you have a will known brand cable it would be certified. The "full feature" cables have a chip inside that the device reads, it then sends data etc to that spec. I'm not really up to date with this stuff anymore.....
By the way, my new phone is a Oneplus 3T and I discovered that has many problems with AA in general. And (perhaps) even an USB-C port not completely complying to the standard.
Still, I will try other brands of cables in search of the good one.
Thanks again
Hi,
I had exactly the same issue as you but with the One Plus 3. Had a couple of aftermarket cables (USB - A to C). Sometimes, it connected for about 1-2 minutes but then i had to disconnect and reconnect the cable. Not fun when you are driving.
Also have an Opel (2017 Astra Sports Tourer K) with the Navi900. The only way i found out to solve this issue was to use the original, red cable that comes with the phone. Since i didn't want to lose the Dash charging or, everytime carry the cable with me, i bought a second cable (1,0m) from Oneplus store.
After i did that, i never had disconnections or problems recognizing the phone. 2 weeks driving with various amount of driving time and so far, zero issues.
Also helps if you are using any battery saving apps like greenify or droid optimizer, that you whitelist the android auto app from the auto closing ( i know there's a better name for it).
Hope it helps.
Thanks for your contribution, inccubbus. I think I read a post from you in Oneplus forum, perhaps.
Fact is that 1 mt cable to me is short, I was using 2 mt with my previous phone (LG with microusb port) and no problems at all! Perhaps I may try with the new 1,5 mt red cable from Oneplus store.
But all of this is just ridicolous. Adapters won't work... in example I tried a 20 cm microusb cable with adapter to usb-c and (guess what) no connection!? I start to think that Oneplus is the culprit.
No problem mate. Sorry to hear that you need a longer cable. Before I bought the OnePlus "official" cable, I bought a total of 4 cables from different brands and lengths. 50cm, 1m, 1,8m and 2m. Total of about 60€ to find out that I needed the one cable I already had.
This is borderline ridiculous. Never tried the original because... No fast charge in the car. Duh.
Hope that the official cable works for you. Fingers crossed!
I must add that, even with a short cable, connection drops every now and then with AA freezing.
Another known Oneplus 3T issue...
One thing that occurred to me: do you also have turned on the "automatically connect with Bluetooth" option? I did a test with that option on and the cable connected and, almost like clockwork, every 3-4 minutes I'd lose the connection. Turned that option off and everything came back to"normal".
Did some research and that option is only for cars that don't have a display/Android auto compatibility so the phone screen is the interface.
Sorry if I am writing something that all knew but, in the options doesn't say anything. I was under the impression that I could "cast" the phone to the display without needing the cable. Like Chromecast
@inccubbus, I noticed that issue... but nevertheless I have trouble of disconnections even without checking "automatically connect with BT". However, I have also a BT headset, and if that BT setting is enabled it will disconnects the headset too every few minutes. AA software is very rough.
@jonsat @inccubbus
Just come across this browsing, interesting
https://www.gizmodo.com.au/2016/02/cheap-usb-c-cables-could-kill-your-phone-or-laptop/
Not sure if this will be applicable to anyone else, but just in case. I started to get connection issues between my Nexus 6p and Pioneer stereo via the cable. Tried multiple cables, but all had the same issue to differing degrees. Then realised there was some lint in the phone USB c port, so cleaned it out with a tooth pick. That seems to have fixed it.
Sent from my Nexus 6P using XDA-Developers Legacy app
IronRoo said:
@jonsat @inccubbus
Just come across this browsing, interesting
https://www.gizmodo.com.au/2016/02/cheap-usb-c-cables-could-kill-your-phone-or-laptop/
Click to expand...
Click to collapse
Yes, very interesting although not directly related to topic. Thanks anyway.
Very interesting indeed. Even though the prices of the "aftermarket" cables I purchased were even more expensive than the OnePlus originals, I see what the article mean. Most people think they are just cables but, capacitance, impedance, amperage... All of these things usually are not "copied" from the original and can cause serious damage, since they need to be "universal" and suit different brands/models with different needs.
Thanks for sharing the article! I almost see the link with the issue discussed here.
Btw, I had one random disconnection on Sunday in the final 5 minutes of a 1 hour drive.
Disconnected the cable, reconnected it and, since then, 2 hours of driving with zero disconnections. I really can't find a pattern for these things.
jonsat said:
Hi to everyone. Sorry if I will not be brief, but this problem makes me going crazy.
My previous phone died prematurely, so I bought a shiny Oneplus 3T and I'm very satisfied with it. Problem is, that this new piece of technology has an USB-C connector instead of the good old microUSB one.
In my car (Opel) I put an USB extension cable from the Android Auto unit (Intellilink r4.0) to the inside of the center arm, and since now I used that cable to connect my previous phone to the unit. Cable is 1.8 m long (about 5 ft for English people) and worked very well.
Now there goes the trouble: to connect my new OnePlus, I bought a simple microUSB to C adapter... it works very well at home with my PC but... Android Auto unit doesn't recognize the phone.
It says "connect the USB cable". At the same time, phone is charging, so power is connected to it.
Ok, maybe there are inconsistencies with the USB converter, I thought.
So I purchased a USB A to C cable, 1.8 m long (just like my previous normal microUSB one).
No way. Unit insists to not recognize the connection!?
Now, to cut this long thing out... I tried any combination of things, extenders, adapters... the only way to make things work is to use max a 1 m (3,3 ft) long USB A to C cable. No longer than that. Neither with a short extension cable.
But with 1 m I can't reach the center arm! I need at least 1.2/1.4 m (4-4.5 ft) cable lenght.
So, this is it. Who can be the culprit? AA head unit? Or perhaps Oneplus 3T has a "weak" USB?
I wonder if anyone has experienced issues like this... and if there are workarounds. :fingers-crossed:
Click to expand...
Click to collapse
I don't have a OnePlus 3T, but my phone has a USB C connection (I have a ZTE ZMax Pro) and I haven't had any issues with the connections to AA (other than USB C is harder to plug in and unplug than before). I have a couple different USB C cables - one about 3-5 feet long, and the other about one foot - and both work fine. I'd guess your cables were the culprit. Hope this worked out for you!
EDIT: Oops, didn't read the replies so I see that my post was absolutely non-helpful. Sorry!
So I seem to have a very weird issue with the USB connection on my Sony Xperia XZ2 running Android 8.0.0 with the build version 51.1.A.11.51. It refuses to connect or charge on almost any computer. The phone doesn't seem to recognize that it's connected to a computer. The computer doesn't see that my phone is connected either. I tried different USB ports, different computers, and different cables and they all won't connect to the phone. The exception is my laptop, which has a dedicated fast-charging port. When I connect my phone to that port, the phone charges, but it doesn't recognize that it's connected to my laptop and the laptop doesn't see a device connected either. Enabling ADB on my phone doesn't seem to do anything.
The strange thing is that almost all other USB functionality works fine on my phone. The phone charges fine from both a normal power brick and a fast charging brick. Both analog and digital based audio adapter dongles works perfectly fine too. USB based Android Auto does not seem to work, but it still charges the phone when I connect my phone to the car.
I also noticed that if I plug my phone into a computer while the phone is off, it would briefly wake up to the Sony logo and have the charging light come on for a few seconds until the screen changes to the battery percentage. Booting up my phone while plugged in doesn't seem to fix the issue.
The bootloader is locked and it has the stock recovery, so I don't think fastboot works (but I'm willing to try if it fixes the issue).
I've already tried spraying electrical contact cleaner into the USB port and also tried cleaning the port with a small plastic zip tie. I don't know how long my phone has been like that since it's been over a month since I last connected it to my computer. I don't know anything else I could do besides resetting the firmware, doing a firmware update, or sending in my phone to Sony for repairs. If anyone has any suggestions, I'm willing to try it.
patx35 said:
So I seem to have a very weird issue with the USB connection on my Sony Xperia XZ2 running Android 8.0.0 with the build version 51.1.A.11.51. It refuses to connect or charge on almost any computer. The phone doesn't seem to recognize that it's connected to a computer. The computer doesn't see that my phone is connected either. I tried different USB ports, different computers, and different cables and they all won't connect to the phone. The exception is my laptop, which has a dedicated fast-charging port. When I connect my phone to that port, the phone charges, but it doesn't recognize that it's connected to my laptop and the laptop doesn't see a device connected either. Enabling ADB on my phone doesn't seem to do anything.
The strange thing is that almost all other USB functionality works fine on my phone. The phone charges fine from both a normal power brick and a fast charging brick. Both analog and digital based audio adapter dongles works perfectly fine too. USB based Android Auto does not seem to work, but it still charges the phone when I connect my phone to the car.
I also noticed that if I plug my phone into a computer while the phone is off, it would briefly wake up to the Sony logo and have the charging light come on for a few seconds until the screen changes to the battery percentage. Booting up my phone while plugged in doesn't seem to fix the issue.
The bootloader is locked and it has the stock recovery, so I don't think fastboot works (but I'm willing to try if it fixes the issue).
I've already tried spraying electrical contact cleaner into the USB port and also tried cleaning the port with a small plastic zip tie. I don't know how long my phone has been like that since it's been over a month since I last connected it to my computer. I don't know anything else I could do besides resetting the firmware, doing a firmware update, or sending in my phone to Sony for repairs. If anyone has any suggestions, I'm willing to try it.
Click to expand...
Click to collapse
Upgrade to the newest stock version.
I recently got my USB-C port replaced by Razer because it was charging right and it out of nowhere stop syncing to Android auto. Now it charges fine but my car still won't recognize the phone, it will for a sec and then it disconnects. Also when I plug my earphones in, the audio still plays through the speakers, in option pops up to change the USB preference but it won't do it.
Dapper Dan66 said:
I recently got my USB-C port replaced by Razer because it was charging right and it out of nowhere stop syncing to Android auto. Now it charges fine but my car still won't recognize the phone, it will for a sec and then it disconnects. Also when I plug my earphones in, the audio still plays through the speakers, in option pops up to change the USB preference but it won't do it.
Click to expand...
Click to collapse
One thing is that some USB-C headphones don't have a AMP/DAC built-in. This is a common problem with Razer Phone 2 users, as it doesn't have one inside. So, if your headphone adapter or USB-C headphones don't have one built-in it won't work. 2, seems like Android Auto doesn't like some USB cables. Try some troubleshooting from at the "My Android Auto app isn't working" page on the Android Auto help page.
I was experiencing relatively the same thing. I tried cleaning and tightening the usb-c port on my phone. Didn't help. So I tried cleaning out the usb-c charging cable, the end that plugs into the phone. Problem solved. It works fine now, for the most part. Still will disconnect from Android Auto if I move the phone around to bunch. Or put the cable in a bind near the end that plugs into the phone.
AshtonGamer said:
One thing is that some USB-C headphones don't have a AMP/DAC built-in. This is a common problem with Razer Phone 2 users, as it doesn't have one inside. So, if your headphone adapter or USB-C headphones don't have one built-in it won't work. 2, seems like Android Auto doesn't like some USB cables. Try some troubleshooting from at the "My Android Auto app isn't working" page on the Android Auto help page.
Click to expand...
Click to collapse
Android auto and the adapter for the earphones used to work fine, it just happened out of nowhere before way before I sent the phone to get fixed like 2 weeks ago, the problems started last year but i think there was an update of some sort. It still won't connect, even when using the original adapter and my pc doesn't even pick up that the phone is even connected, it will just charge. I've already check the device manager to see if it was a bad driver but nothing. no matter what device i connect, it will just say "Charging connected device via USB". ive Already tried USB debugging, disable USB audio routing, cleaning it, and apps to manually control it.