I have been using a USB DAB module with my Klyde HU which has been working fine for several months, but recently it has started cutting out intermittently. At first I assumed it was a faulty module, but after testing on another stereo that seems to not be the case.
I set up tasker to periodically scan the USB bus and log the connected devices, and the DAB device disappears at the same time that the audio cuts out. Interestingly, I noticed that the built in wifi shows as a USB device and this also disconnects at the same time as the DAB. So the issue is definitely with the HU. Any tips for debugging further? Could it be a driver issue or is it more likely hardware?
RoboticBandit said:
I have been using a USB DAB module with my Klyde HU which has been working fine for several months, but recently it has started cutting out intermittently. At first I assumed it was a faulty module, but after testing on another stereo that seems to not be the case.
I set up tasker to periodically scan the USB bus and log the connected devices, and the DAB device disappears at the same time that the audio cuts out. Interestingly, I noticed that the built in wifi shows as a USB device and this also disconnects at the same time as the DAB. So the issue is definitely with the HU. Any tips for debugging further? Could it be a driver issue or is it more likely hardware?
Click to expand...
Click to collapse
I found the USB current limiting is not reliable, on one KSP the limiter burnt out leaving me with no usb power. In my case there was another available limiter, maybe for OTG. I would check the usb v+ voltage.
xdamember2 said:
I found the USB current limiting is not reliable, on one KSP the limiter burnt out leaving me with no usb power. In my case there was another available limiter, maybe for OTG. I would check the usb v+ voltage.
Click to expand...
Click to collapse
Thanks, yeah sounds like a good starting point. I tried plugging in my phone to one of the usb ports, only to find that my phone doesn't measure voltage.. Think I'll have to get out a multimeter to do some more testing. Interestingly though it carried on charging even when none of the usb devices were recognised by the stereo. The max current was around 140mA though which seems very low.
Related
Hello everyone,
A couple of weeks ago my USB data connection on my OnePlus One has stopped working.
This means that no connection is even detected on any computer.
This is not a driver issue as the computer doesn't even notice anything has plugged in.
I think it's not a software/ROM issue because the same applies to fastboot mode and recovery mode - no data connection, no "usb plugged in" sound on any computer, no device showing up.
It's also not a cable issue, as the same cable works on other OnePlus One's and I've tried many different known-to-be-working cables.
More facts:
1) When plugging to a computer USB port - the battery icon shows the charging (lightning) symbol for a half a second and disappears and it won't charge. The computer, of course, doesn't see a usb device plugged.
2) When connecting to an AC charger - it charges just fine.
3) I already tried replacing the dock connector and flat cable unit with a new one - did not solve the issue, which means the dock connector is fine.
Any insight on this will be greatly appreciated!
Thanks!
purpleman2k said:
Hello everyone,
A couple of weeks ago my USB data connection on my OnePlus One has stopped working.
This means that no connection is even detected on any computer.
This is not a driver issue as the computer doesn't even notice anything has plugged in.
I think it's not a software/ROM issue because the same applies to fastboot mode and recovery mode - no data connection, no "usb plugged in" sound on any computer, no device showing up.
It's also not a cable issue, as the same cable works on other OnePlus One's and I've tried many different known-to-be-working cables.
More facts:
1) When plugging to a computer USB port - the battery icon shows the charging (lightning) symbol for a half a second and disappears and it won't charge. The computer, of course, doesn't see a usb device plugged.
2) When connecting to an AC charger - it charges just fine.
3) I already tried replacing the dock connector and flat cable unit with a new one - did not solve the issue, which means the dock connector is fine.
Any insight on this will be greatly appreciated!
Thanks!
Click to expand...
Click to collapse
By dock connector, you mean the USB port? Typically, this issue arises when the pins in the USB port get damaged. I don't know how the rest works out, but if that particular section of pins have to communicate throughout the rest of the motherboard, perhaps the trail responsible for that may have somehow gotten damaged. This is a clueless theory, someone with more electrical/motherboard experience can verify this.
What I do know is that once the micro USB port has been replaced on the phone, the issue should be fixed. It happened to an S3 I still have and I got it replaced by a friend. Sadly, it happened to me at the wrong time since i had wiped the entire OS and internal storage and was relying on my USB OTG cable and a flash drive which contained a rare rom called Sonic Open Kang Project (SOKP).
DO NOTE that this has also been an issue with me on the software side of certain devices. I uave had practically every flagship device out there and have come across a point where this happens on both stock and custom roms. My Optimus G did it on custom roms, and my Nexus 7 2012 occasionally on stock. There were other devices I cannot remember but sometimes factory resets or replacing the rom helps. However, you did state that the result is still the same on fastboot/recovery, so this seems to be more on the hardware side.
I replaced the USB connector (including it's flex cable) entirely. Did not solve the issue.
What else could be wrong?
try again
purpleman2k said:
I replaced the USB connector (including it's flex cable) entirely. Did not solve the issue.
What else could be wrong?
Click to expand...
Click to collapse
Try another computer. See if you can get any response from adb.
pbergonzi said:
Try another computer. See if you can get any response from adb.
Click to expand...
Click to collapse
I tried a lot of different computers and cables. None of them detect a USB connection.
Again, to clarify - they don't even SEE a usb device has been plugged in.
recovery?
purpleman2k said:
I tried a lot of different computers and cables. None of them detect a USB connection.
Again, to clarify - they don't even SEE a usb device has been plugged in.
Click to expand...
Click to collapse
You running a custom recovery? If so, see if you can toggle the mtp on/off reboot with each back to recovery. Use the tools to check the filesystem, permissions, etc.
Could pins have damaged?
Well, I did replace the USB connector with a new one, so if pins are damaged it's gotta be on the motherboard side, and I can think of no reason why that would ever happen.
As for recovery, I'm running TWRP and I'm not sure I understand what you meant I should try. Can you elaborate?
Thanks
Hi, after reading a few threads about android auto compatibility with the essential phone, I have been put off purchasing as AA has become a pretty permanent fixture of my commute.
There have however been software updates I see by Essential, notably the latest firmware in the past few days. Just wondering if anyone has seen any improvement in android auto experience with any of the latest updates?
Thanks.
I havent had an issue. Im running AA on both my 2017 Audi and 2017 GMC. I had issues with my LGV20. With the LG, i would have to reboot the phone to get AA to recognize and even when it showed connected, text messages werent available. If i unplugged the phone and then tried to plug back in, i would have to reboot the phone if i wanted AA to work. With the essential, i can unplug the cable and plug back in and resume what i was doing seamlessly and all the alerts/texts come up no problem anymore
Same here no issues I use a couple of hours per day.
It works great with my modded Infotainment center in my 2016 Miata. However, it will not stay connected to my aftermarket 2016 Kenwood head unit in my other car more than 1-2 seconds constantly connecting and disconnecting. I've tried half a dozen different cables. Works fine with my Nexus 6.
elkay said:
It works great with my modded Infotainment center in my 2016 Miata. However, it will not stay connected to my aftermarket 2016 Kenwood head unit in my other car more than 1-2 seconds constantly connecting and disconnecting. I've tried half a dozen different cables. Works fine with my Nexus 6.
Click to expand...
Click to collapse
This was what I had heard of in the forums and gives me pause about purchasing. May I ask if you have tried with latest firmware which Essential says contains some bug fixes?
Thanks to the others with positive experiences. More encouraging!
Are the reported issues with the phone itself running Android Auto and just Bluetooth connecting to the car, or when the phone is linked to the head unit?
Seamonkey79 said:
Are the reported issues with the phone itself running Android Auto and just Bluetooth connecting to the car, or when the phone is linked to the head unit?
Click to expand...
Click to collapse
As I understood it, it was with the phone linked to the screen of the head unit. Mine is a 2016 vw. There was a similar issue with the Oneplus 3 which kept disconnecting for no apparent reason and Oneplus fixed this with a software update which is why I was enquiring about updates here.
No problem here, connecting to and staying connected to my wife's 2016 Ford Edge, and my 2016 Corvette.
I use AA everyday, in my 2018 Audi Q5. I've never seen it drop out once.
Sent from my PH-1 using Tapatalk
Thanks very much for the positive reports.
I had issues getting AA to work with my Essential phone, what solved the issue for me was disabling USB debugging. After that it worked like a champ.
elkay said:
It works great with my modded Infotainment center in my 2016 Miata. However, it will not stay connected to my aftermarket 2016 Kenwood head unit in my other car more than 1-2 seconds constantly connecting and disconnecting. I've tried half a dozen different cables. Works fine with my Nexus 6.
Click to expand...
Click to collapse
Exact same. My old Nexus 6 works fine but the Essential will not work with my Kenwood DDX9903. Currently I'm using my Nexus and tethering but due to Android Auto's (stupid imo) handling of calls through BT instead of USB, I can't accept calls over BT with the Essential while the N6 is in Android Auto mode.
dwj said:
This was what I had heard of in the forums and gives me pause about purchasing. May I ask if you have tried with latest firmware which Essential says contains some bug fixes?
Thanks to the others with positive experiences. More encouraging!
Click to expand...
Click to collapse
I'm all up to date and it still will connect and disconnect rapidly until my head unit restarts. It literally worked ONCE on the first night I got it. On my drive back home and up til now I only get the USB access error message.
Charlie_Don't_Surf said:
Exact same. My old Nexus 6 works fine but the Essential will not work with my Kenwood DDX9903. Currently I'm using my Nexus and tethering but due to Android Auto's (stupid imo) handling of calls through BT instead of USB, I can't accept calls over BT with the Essential while the N6 is in Android Auto mode.
I'm all up to date and it still will connect and disconnect rapidly until my head unit restarts. It literally worked ONCE on the first night I got it. On my drive back home and up til now I only get the USB access error message.
Click to expand...
Click to collapse
And same haha.. I'm using my Nexus 6 with hotspot thru my Essential for connectivity. And also same issue regarding calls. I was pondering cuttingthe proprietary USB cable and soldering it really close to the connector itself, thinking maybe if I get that cable as short as possible and then use a USB-C cable *just* long enough to reach the phone in front of the unit, maybe that will give the signal just enough boost to not keep failing repeatedly.
elkay said:
And same haha.. I'm using my Nexus 6 with hotspot thru my Essential for connectivity. And also same issue regarding calls. I was pondering cuttingthe proprietary USB cable and soldering it really close to the connector itself, thinking maybe if I get that cable as short as possible and then use a USB-C cable *just* long enough to reach the phone in front of the unit, maybe that will give the signal just enough boost to not keep failing repeatedly.
Click to expand...
Click to collapse
I swear I thought about doing the same thing but I think it might be a USB C issue in general. I have to test it with my mom's Nexus 5X. Worst case scenario I'll end up buying a replacement cable, cannibalizing the connector, and running a ~3ft USB C cable connected directly to the kenwood connector. That should tell me for sure if it's a cable quality/length issue. If I remember correctly, the cable from Kenwood is at least 2 ft. just by itself.
If you find any solution let me know because I have almost an hour commute and Waze's police alerts helps me big time.
My Prius was hellbent on grabbing my wife's iPhone instead of my SGS5 and the same thing happens with the Essential Phone. It always grabs her phone over mine. Otherwise, works fine.
elkay said:
And same haha.. I'm using my Nexus 6 with hotspot thru my Essential for connectivity. And also same issue regarding calls. I was pondering cuttingthe proprietary USB cable and soldering it really close to the connector itself, thinking maybe if I get that cable as short as possible and then use a USB-C cable *just* long enough to reach the phone in front of the unit, maybe that will give the signal just enough boost to not keep failing repeatedly.
Click to expand...
Click to collapse
I had it working tonight. I used a SUPER SHORT USB 2.0 Cable that came with my Anker PowerCore battery, then a samsung microusb to USB C connector.
It's so weird but I think going with the shortest cable possible, including the head unit cable might be a fix.
That sounds like a problem specific to Kenwood receivers then.
I've used my Essential with Android auto in four different cars with three different cables and I've never seen it disconnect once on any of them. But those were all Factory radios.
Sent from my PH-1 using Tapatalk
I just switched from an Xperia X and the PH-1 is significantly slower on AA. It works, but it's a slog.
This is on a 2017 Silverado
Just bought a 2017 Audi S3 and AA has been working flawlessly since day 1.
Weird, no slowdown or speed issues on AA in any of the 4 cars I've used it in. Guess I'm lucky. As long as it works in my Audi (and it does), I'm happy.
Sent from my PH-1 using Tapatalk
Just wondered if anyone has any suggestions.
I use DAB a lot but I have to keep the screen brightness on the lowest setting otherwise it kills the signal to the dab the more I increase the brightness.
I’m using a KGL px5 octo core, I’ve updated to MTCE firmware and the latest kgl mcu and I have tried with GS firmware before but still the problem is there. I have changed factory settings for screen brightness etc but still no luck. Today I cut a usb cable open and tested it with a multimeter when the screen was on full brightness with DAB on and the voltage was perfect and didn’t decrease when I turned the brightness up. I’m using the modded zoulou app and I’m pretty sure this problem was there when i used the standard app.
I’m out of ideas of what it can be.
The only thing I haven’t changed is the little DAB box, could it be this?
Could it be a software bug or could there be some other sort of hardware fault?
Anyone any ideas????
The question is what DAB+ receiver you're using. I personally ordered this black aluminum box with 8-pin connector along with my head unit. It never worked properly. Ended up replacing it with a Joying DAB+ USB stick which simply worked out of the box.
It's just wild-guessing why your reception is depending on screen brightness. There might be some interferences with the DAB+ box itself or the cable where it's connected. So another (shielded) cable might help. If you also got some DAB+ box with proprietary connector I recommend you to go for an USB one. I just glued my one on top of the head unit using some velcro tape so I can also easily remove it if required.
SkyBeam2048 said:
The question is what DAB+ receiver you're using. I personally ordered this black aluminum box with 8-pin connector along with my head unit. It never worked properly. Ended up replacing it with a Joying DAB+ USB stick which simply worked out of the box.
It's just wild-guessing why your reception is depending on screen brightness. There might be some interferences with the DAB+ box itself or the cable where it's connected. So another (shielded) cable might help. If you also got some DAB+ box with proprietary connector I recommend you to go for an USB one. I just glued my one on top of the head unit using some velcro tape so I can also easily remove it if required.
Click to expand...
Click to collapse
The dab box I’m using was supplied by erisin it is the right one it is a little square shaped box with a mcx connection for antenna and a micro usb connection for power from the headunit. I did wonder if this could be faulty but I don’t see how screen brightness could affect this box.
I have noticed sometimes that when I pull the headunit out of the dash that with the screen brightness on full sometimes the dab will work but as soon as i push it back in the dash it goes off again and I have to put the brightness back down to minimum and then it will work fine again. Because of this i have thought it could be a loose usb connection as the usb’s Are on the back of the unit and there can’t be much space behind there when the unit is pushed back in but if that is the case I don’t understand why it works when putting the brightness back down to minimum. Having said that I have tried making the usb connections tighter by raising the prongs inside the usb slots and I have noticed that they only have prongs on the top or bottom inside the usb slots whereas on my laptop and phone charger they have prongs on the top and bottom inside the usb slot therefore giving a much much firmer fit. Maybe that is the problem but I don’t know and I can’t get it working and I’m out of ideas.
Be interesting to hear from other users that are using dab on a px5 especially if you are using it successfully with a similar setup to mine.
I’m using a KGL with the little plastic square dab box and a glass mount antenna(I don’t believe the antenna is the problem as the signal is brilliant when the brightness is down and I bought a new alpine antenna.)
I am afraid that likely nobody can tell you for sure. I guess your DAB+ receiver then is USB-based, meaning power AND data over USB. So it only has an USB port and an antenna port.
So there isn't much which gan go wrong here. Just make sure your antenna cable is firmly attached and not "bent" in too tight angles which could cause the antenna to malfunction.
My recommendation: Try all USB ports. Attach an USB extension cord to the USB port and route it out to your glove box or similar. Then connect the USB DAB+ receiver to the antenna in your glove box etc. Just to rule out a couple of things:
USB cable dos not get bent or connector gets lose (maybe your DAB+ receiver has an indicator LED when it's powered, if not, then you can check your USB while the headunit is firmly mounted by attaching an USB stick or similar)
Your antenna cable is not squeezed or bent when you push in the head unit
Your DAB receiver box does not pick up radio enterferences from the head unit by being too close to it (yes, those units are often insufficiently shielded, so just some distance sometimes helps!)
SkyBeam2048 said:
I am afraid that likely nobody can tell you for sure. I guess your DAB+ receiver then is USB-based, meaning power AND data over USB. So it only has an USB port and an antenna port.
So there isn't much which gan go wrong here. Just make sure your antenna cable is firmly attached and not "bent" in too tight angles which could cause the antenna to malfunction.
My recommendation: Try all USB ports. Attach an USB extension cord to the USB port and route it out to your glove box or similar. Then connect the USB DAB+ receiver to the antenna in your glove box etc. Just to rule out a couple of things:
USB cable dos not get bent or connector gets lose (maybe your DAB+ receiver has an indicator LED when it's powered, if not, then you can check your USB while the headunit is firmly mounted by attaching an USB stick or similar)
Your antenna cable is not squeezed or bent when you push in the head unit
Your DAB receiver box does not pick up radio enterferences from the head unit by being too close to it (yes, those units are often insufficiently shielded, so just some distance sometimes helps!)
Click to expand...
Click to collapse
I’ve checked and changed cables etc, the cables are quite long though so there is a lot behind there which could get bent etc especially when the unit goes back. my feeling were that the usb cable were moving when im pushing the headunit back in but surely if this were the case then I’d struggle to use it all.
Your last point is interesting about moving the dab receiver box as I think I’ve always had it behind the headunit if I remember right so I might move that out of the way, but again why would screen brightness affect it?
ab1702 said:
but again why would screen brightness affect it?
Click to expand...
Click to collapse
Just a wild guess: It might affect reception by some interference (brightness is PWM-modulated pulsing). On the other hand it could also be related to power consumption. If voltages are not stabilized sufficiently it could affect USB voltage to an extent where your DAB receiver does not work any more, but then you would likely lose complete USB connectivity (and you could try to overcome this by using a powered USB hub).
My last advise to put the receiver away from the unit into the glove box war mainly to be able to debug the USB port and antenna connections while the unit is firmly put into the slot.
I don't have much more ideas to share currently
SkyBeam2048 said:
Just a wild guess: It might affect reception by some interference (brightness is PWM-modulated pulsing). On the other hand it could also be related to power consumption. If voltages are not stabilized sufficiently it could affect USB voltage to an extent where your DAB receiver does not work any more, but then you would likely lose complete USB connectivity (and you could try to overcome this by using a powered USB hub).
My last advise to put the receiver away from the unit into the glove box war mainly to be able to debug the USB port and antenna connections while the unit is firmly put into the slot.
I don't have much more ideas to share currently
Click to expand...
Click to collapse
I can’t say for sure but I don’t think the voltage is anything to do with it as I have cut the end off a usb cable and plugged it into the unit and then pushed it back in and tested it with a multimeter and it had 5.3 volts. I thought that when I turned the brightness up it could be taking power away from the usb but that doesn’t appear to be the case. I also tried a y shaped usb cable so it has double the amount of power so 10volts should be going through it. This didn’t make any difference to my problem but it does make the antenna perform better.
I think the next thing I’ll be trying is moving the dab receiver away from the headunit and see how i get on with that(although I do think I have already tried this). It definately appears to be an interference problem but from what is the question?!
Well I’m still scratching my head with this.
Tried moving the dab receiver away from the headunit last night and it makes little difference.
I’m thinking it has to be something to do with the usb connection although I still don’t understand why it is linked to the brightness of the screen.
I can take the headunit out of the dash and turn the brightness up full and it will lose all signal but then I could move the headunit a little while still out of the dash and it goes to full signal and will stay there but as soon as i go to push the unit back in the car it goes off again. The strange thing is if i then do put the unit back in the dash then lower the brightness to the lowest setting then signal is perfect again.
I’m ready for throwing it out to be honest!.!
Does anyone know anything about noise interference on USB ports?
I’m thinking this could potentially be the cause.
I’ve just been reading that electrical devices can cause high frequency noise interference to usb devices so I’m just guessing here that when I turn screen brightness up it is interfering and the dab receiver can’t cope with it.
Anyone for an opinion on this or know anything about it?
I’m going to buy a ferrite bead to put on the usb cable before the dab receiver and see if this helps.
ab1702 said:
Does anyone know anything about noise interference on USB ports?
I’m thinking this could potentially be the cause.
I’ve just been reading that electrical devices can cause high frequency noise interference to usb devices so I’m just guessing here that when I turn screen brightness up it is interfering and the dab receiver can’t cope with it.
Anyone for an opinion on this or know anything about it?
I’m going to buy a ferrite bead to put on the usb cable before the dab receiver and see if this helps.
Click to expand...
Click to collapse
you then solved, because I also have the problems problems
So I was all excited to get a pixel so i can use wireless Android auto, yes my stereo is compatible.
The problem is I can't even get it to work via USB cable. After a few seconds it keeps crashing and restarting. I've never had any issues with other phones and cables.
Any tricks or suggestions.
mpetruzz said:
So I was all excited to get a pixel so i can use wireless Android auto, yes my stereo is compatible.
The problem is I can't even get it to work via USB cable. After a few seconds it keeps crashing and restarting. I've never had any issues with other phones and cables.
Any tricks or suggestions.
Click to expand...
Click to collapse
Try another cable, it worked for me.
fiveplustwo1 said:
Try another cable, it worked for me.
Click to expand...
Click to collapse
Yep, I second this. I did a new head unit installation a year ago and was trying to install a nice USB flush mount cable to use with it. It was somehow causing problems and my phone connected to the head unit, the head unit saw it, but ultimately Android Auto didn't work and seemed like my phone was the problem. I removed the flush mount and just plugged in directly to the head unit and all was well. Try cables which are different brands.
So my wired headphones stopped working few days back. They were working fine a week ago but suddenly they stopped working. My usb type-c port is also fine. Charging with each and every cable perfectly. My wired type-c headphones are fine because they are working perfectly with other phones as well as 3rd party dongle which is working fine with "charging rapidly" as before but not audio output, "Disable audio routing from usb" under developer option is also fine. Its not showing any message like incompatibility but the sound is not playing from the headphones, the audio is routing from the phone speakers.
Mines the same with the USB pixel buds takes ages to get them to work again. Also noticed that when I charge the device it goes really slow until I twist round the USB c head and it will fast charge again with the same charging lead?? Think the USB c port is on its way pay out.
ttocs99 said:
Mines the same with the USB pixel buds takes ages to get them to work again. Also noticed that when I charge the device it goes really slow until I twist round the USB c head and it will fast charge again with the same charging lead?? Think the USB c port is on its way pay out.
Click to expand...
Click to collapse
I dont need to twist or something with the cable, it turns out with charging rapidly automatically, but today i also realize that pc connectivity is also not working with this. :crying:
luqman.mirza said:
So my wired headphones stopped working few days back. They were working fine a week ago but suddenly they stopped working. My usb type-c port is also fine. Charging with each and every cable perfectly. My wired type-c headphones are fine because they are working perfectly with other phones as well as 3rd party dongle which is working fine with "charging rapidly" as before but not audio output, "Disable audio routing from usb" under developer option is also fine. Its not showing any message like incompatibility but the sound is not playing from the headphones, the audio is routing from the phone speakers.
Click to expand...
Click to collapse
Had a similar problem. Needed rubber bands to hold the cable at just the right angle to charge or connect to PC - as long as I didn't sneeze.
Suspecting pocket lint I used Q-Tips, toothpicks, and compressed air to try to clean out charging port without luck.
I was ready to go to new device when I dialed it up to metal safety pin. Was last resort as you risk doing serious damage to your charging port, but either way the device had become useless to me.
I was amazed as the pocket lint just kept falling out and falling out - couldn't believe how much and how tightly it was packed in there. This method also worked for a friend who had given up on his Pixel.
Device works fine now but be aware that rooting around in the charging port with something metal could do serious damage.
That's why I always clean my pant's pocket. It also happened to me before with micro usb port of an older device.