Hey all,
My other half and I picked up a TF300 to use as our "away with work" machine. She's had it for the last 4 months, and as we high-5'd at the airport she gave it to me with a couple of snags. I'm away with it now, so would prefer not to RTM it if we can solve this here!
The screen portion is working just fine, the issue is with the keyboard. It won't take a charge at all. Software reports the battery at 0% for the keyboard, plus the flashing orange LED on the power port side. It will allow the screen to charge from the mains while the keyboard is connected, so the issue is probably not the lead/connector/port there. The screen recognises that the keyboard is connected.
Also the usb port on the dock is refusing to recognise HDDs, memory sticks etc. It will give power over USB but seemingly no data.
I've tried a factory reset and have also upgraded to the latest uk firmware, to no avail!
Thoughts?
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
Once the USB cable is connected to OP6 first and then car ignition is turned on, Android Auto is not coming up on head unit screen. If the ignition is turned on first, and if I insert the USB, it gets recognized properly and AA comes up. It seems OP6 with Pie relies on USB connection broadcast for kicking off AA. I verified that this is not an issue with car's head unit because my Samsung phone running Android Oreo behaves properly with the same head unit. This is either an OP/OxigenOs-specific or Pie-specific issue. The expected behavior is that AA should appear on head unit screen when car is turned on even if the USB cable is already connected. Also, this is a safety concern as well. Right now, you can't expect me to insert USB cable after I have started driving. Even if a I manage to do it initially, if I stop the car somewhere and turn it off and on again, I have to unplug and plug the USB cable back again now to make it work. Any help is appreciated. Device details are given below
Head unit: Alpine stock unit on Honda Jazz VX 2018.
Phone: OP6 with latest Pie, not rooted, USB debugging off
AA: 3.5
Already tried AA cache/storage reset, uninstall, etc.
Likely an issue with your phone or cable. I've never had any issues getting AA to activate no matter how I connect.
Try using a different cable, or a factory reset.
iElvis said:
Likely an issue with your phone or cable. I've never had any issues getting AA to activate no matter how I connect.
Try using a different cable, or a factory reset.
Click to expand...
Click to collapse
Thanks. Already tried 3 different cables including original OnePlus cable. Only thing remaining is factory reset, which I will try today. If that doesn't work, thinking of downgrading to Oreo. Then that doesn't work, thinking of switching to Samsung. Already have had a couple of bitter experiences with OP6 despite its other great features.
iElvis said:
Likely an issue with your phone or cable. I've never had any issues getting AA to activate no matter how I connect.
Try using a different cable, or a factory reset.
Click to expand...
Click to collapse
Tried factory reset and downgrade to Oreo today, but the issue persists. Samsung J7 Max works beautifully
negie said:
Tried factory reset and downgrade to Oreo today, but the issue persists. Samsung J7 Max works beautifully
Click to expand...
Click to collapse
May just be a conflict between your phone and head unit. AA can be weird. My HTC M9 was a huge pita with my VW, but when I switched to OP all the issues went away. ¯\_(ツ)_/¯
Hello everyone.
So I have a few issues which I am guessing are all somewhat related.
TL;DR
1) Android auto stopped working
2) if I reboot. It will just power off and needs to be plugged in to power back on
3) usb c to usb c only works one side not both sides. But usb a to usb c works both directions.
Note: my wife has the same phone and had none of these issues with the same cables and such. So it's not cables issues. We also have the same OS.
The longer detailed version.
First issue. Android auto stopped working. At first it told me that there may be an issue with the cable and that I should get another cable. I tried my wife's pixel 3 xl and it worked fine. So it's not the cable issue. I tried restarting. The phone did not. So I plugged it in and it powered on. Now the phone will only boot if it is plugged in. Plugging the phone into the car usb a to usb c it charges on both side of the cable but there's no longer any warning about the cable for Android auto. Again my wife's phone works with the same setup so it's an issue with my phone. Then when plugging my phone in using the oem cable I noticed it only chargers using one side. The other side fails. Tested my wife's phone and both sides work. I then test my wife's cable and same issue with her cable for my phone.
Pixel 3 XL
OS 11 RQ1A.210105.003
I did a factory reset but same issues remain.
I'm open to using a ROM if it will fix the issue.
I saw a few posts on google forums about this issue but not fix/solution so I was kind of wondering if a ROM would possibly fix this issue.
Thanks so much for any help.
Willing to try most items as phone is out of warranty and I really like Android auto and hate not having it.
Hello community,
I've a realy weird problem with my OnePlus 7 Pro. It started when I upgraded to Android 11 half a year ago, after that USB connection was only possible with this red OnePlus cable, but with this it worked always. After some time connections started to fail sometimes. Since a month or so it worked only when i charged to >90% and then did a reboot. 2 Weeks later a had do boot into recovery and wipe cache to make it work once. A week ago it stopped working indepented what I do. This morning I did a full wipe but still no data connection possible (charging works). To make this even more weird, the device charges using any USB-A to USB-C cable, but with a C to C it won't even charge
I tried mutliple cables, 2 computers with Windows 10 and even a live Linux to, so the problem must be the phone. EDIT: other Android devices works without any problems.
Any ideas what I can try to get it work again?
Perhaps due to the use of fast charging and an incorrect cable with poor amperage matching or poor heat dissipation, the USB-C socket in the phone, i.e. the contacts on the PCB or even its surroundings, overheated.
i won't deny this is a possible reason but this would not explain why 3rd party cables stopped working the minute I installed OOS11 or why I could make it work by wiping cache.
What is the device name print into your device manager console, when you plug in the phone in storage mode ?