Hello everyone,
I'm writing this topic because I've an annoying problem with my OnePlus One, which is a wonderful compagnion fr everyday life.
Recently I bought a brand new Seat Ibiza, loaded with an infotainment system, with Android Auto, MirrorLink and Apple Car connectivity. Android Auto works greatly BUT from the beginning, I've got an issue with this. When I plug the OPO to the car via USB, all works great, and randomly (but often after 30 minutes), the OPO seems to shutdown the USB port. I think the problem is on the OPO side because when I unplug the USB cable on the car side, that have no effect, but when I do the same on the OPO, the connection restart and Android Auto start again.
I've tried with USB Debugging, Charge mode only, MTP mode, with another cables ... Many things but nothing that really works fine, with COS 12.1 and now with COS 13. Sometime, the headunit display a message "verify your smartphone, it seems that the device is locked" but all the screen locks are OFF, and in the Automobile system profile, I've told him to NOT lock the phone.
Anyone have an idea of the problem ?
Thank you for your answers :good:
I'm seeing the same issue...
Cookie83610 said:
Hello everyone,
I'm writing this topic because I've an annoying problem with my OnePlus One, which is a wonderful compagnion fr everyday life.
Recently I bought a brand new Seat Ibiza, loaded with an infotainment system, with Android Auto, MirrorLink and Apple Car connectivity. Android Auto works greatly BUT from the beginning, I've got an issue with this. When I plug the OPO to the car via USB, all works great, and randomly (but often after 30 minutes), the OPO seems to shutdown the USB port. I think the problem is on the OPO side because when I unplug the USB cable on the car side, that have no effect, but when I do the same on the OPO, the connection restart and Android Auto start again.
I've tried with USB Debugging, Charge mode only, MTP mode, with another cables ... Many things but nothing that really works fine, with COS 12.1 and now with COS 13. Sometime, the headunit display a message "verify your smartphone, it seems that the device is locked" but all the screen locks are OFF, and in the Automobile system profile, I've told him to NOT lock the phone.
Anyone have an idea of the problem ?
Thank you for your answers :good:
Click to expand...
Click to collapse
I'm seeing the same issue with my OPO, and I have not yet been able to fix it. I've read threads that said turn on USB Debugging and turn Battery Optimization off for Android Auto. The best I've come up with is using the original OPO USB cable and leaving it loose, but even this has only minimized the issue.
Got my Pixel 3 XL yesterday and absolutely love it...
Just in case anyone else experiences issues I thought I would post this - did an online chat with Google and they think it might be a bug in the OS.
Connecting to my PC or Car, the device was showing the USB options when you swipe down for notifications permanently on Charging Only. Even changing this from that drop down had no effect. I could see the device on my PC but unable to view files/folders and unable to copy anything to the device. Similar symptoms in my car, the device would charge fine but no matter what I did it wouldn't connect to my Infotainment System.
To fix this I had to enable Developer Options, scroll down to Networking and there is a "Default USB configuration" setting. This was set to "No data transfer", I changed it to "File transfer" and rebooted and now everything works fine.
Hopefully this might help others :good:
Does your phone fast charge while using Android Auto?
I don't think so, how can I check that.
I've only had the device a couple of days now but have noticed that when I'm using it in the car running Google Maps and streaming music via AA it still seems to charge.
Doing the same on my original Pixel XL I would loose 1-2% over about 30-40 mins, not sure if that's just because the battery was starting to deteriorate.
Thanks, but for some reason that didn't work for me. Tried this with and without USB debugging and car is just not seeing the phone for AA, but charges it fine. Also tried 4 different cables just in case, if I plug in an S8+ to any one of those cables it works perfectly with the car.
[deleted, "wrong thread" mistake]
I have OP7 PRO running android 10 and stock Oxygen OS (not root).
When I pair my device to my car bluetooth set everything works fine, but once the connection is lost it will not auto-reconnect the next time i'm in my car.
Moreover, in order to connect again i need to do the pairing again (not just select the device from the existing devices list).
I saw tons of threads online about this with no solution, some mentioned they think it's an issue with android OS and not the phone itself (this is supported by the fact that my wife just got a new Xiaomi and have the exact same problem).
Does it make sense that this is a global Android issue and has no fix for such a long time? did anyone experience it and managed to fix it?
I would guess at an issue with the car Bluetooth. May be theres a firmware update for that ?
UrbanBushman said:
I would guess at an issue with the car Bluetooth. May be theres a firmware update for that ?
Click to expand...
Click to collapse
That was my first thought, but it seems that the issue is on the device side as i can see that after connecting the device doesn't appear in the previously connected devices list.
As if the phone forgets it for some reason.
I've had occasional problems too. I'm using Launcher 10. Just last week, I turned on my wifi before starting my car as usual. It connected, then disconnected 2 times and then was stable. There's been times where I'll restart my car to fix it. It's irritating but who knows what can be done about it.
I have a rooted stock op7pro and I have a Samsung active2 watch that randomly disconnects and reconnects once or twice an hour. I have battery set to all Samsung apps on my phone to not optimize battery usage and I have no idea why it does this.
Sent from my OnePlus7Pro using XDA Labs
I have understood that it's also possible that it depend on the order in wich you connect.
You should first have to connect the car to the phone instead of the phone to the car.
Iow have the car lookup the phone
Yes, i head a lot about people with flaky connection but i hope that was the situation, for me it won't reconnet 100% of the times.
Changing the order of connections didn't work.
I have been experiencing issues connecting to devices over Bluetooth. Sometimes it just works, other times it doesn't work at all, and some times it kinda works but not right.
All of these issues are resolved by restarting the phone, but that isn't a solution because the issue comes back.
3 Devices I have been having issues with
1. S Pen - Sometimes it won't connect to the phone, I get an "S-Pen Missing" message and it will not connect. If I t ry to connect to it manually via nRF Connect (The Nordic Semiconductors Bluetooth App) it tells me that the BLE device has a GATT error. It happens semi-randomly but I can always make it happen by doing #2
2. Car Stereo - This is the weird one, it will connect and play music, but it will not do "calls" if I connect to Discord it won't recognise the car as a Bluetooth device it can route to.
3. Raspberry Pi - This one it appears it will connect to ONCE, and then after a disconnect it will not connect again.
Again, each of these can be fixed by restarting the device, but they happen again after a while. The pen & RPi use BLE, I don't know what the car uses for calls.
Turn off global power management completely in Device Care.
Network reset, reboot and clear system cache from the boot menu.
Ok, I've done a network reset, and cleared the cache partition. I checked Device Care for something like global power management, and I couldn't find anything. Most of the pwm settings are off except the "optomise daily" setting.
I'll let you know later if I have the same issue again.
These, this is a N10+ running on Pie.
To check if you have disabled global power go to Developer options>standby apps, all buckets should show as active otherwise power management is enable.
KindarConrath said:
I have been experiencing issues connecting to devices over Bluetooth. Sometimes it just works, other times it doesn't work at all, and some times it kinda works but not right.
All of these issues are resolved by restarting the phone, but that isn't a solution because the issue comes back.
3 Devices I have been having issues with
1. S Pen - Sometimes it won't connect to the phone, I get an "S-Pen Missing" message and it will not connect. If I t ry to connect to it manually via nRF Connect (The Nordic Semiconductors Bluetooth App) it tells me that the BLE device has a GATT error. It happens semi-randomly but I can always make it happen by doing #2
2. Car Stereo - This is the weird one, it will connect and play music, but it will not do "calls" if I connect to Discord it won't recognise the car as a Bluetooth device it can route to.
3. Raspberry Pi - This one it appears it will connect to ONCE, and then after a disconnect it will not connect again.
Again, each of these can be fixed by restarting the device, but they happen again after a while. The pen & RPi use BLE, I don't know what the car uses for calls.
Click to expand...
Click to collapse
Are those the only three devices you connect via BT? What other apps do you use that need to use BT (i.e. Galaxy Wear, Apple Music, etc.).
You mentioned "Nordic Semiconductors Bluetooth App." I looked it up. Why do you need a third party generic BLE connecting app? It seems to me that could be the problem. You shouldn't need a third-party app to connect your BLE devices. The S22U's native pairing will work with any BT device that adheres to BT standards.
Try uninstalling the nRF Connect app and see what happens.
The only other Bluetooth devices I have are other in-house hardware, running on SiliconLabs BGM13P chips or NRF52840 chips...
The NRF app isn't a replacement for your bluetooth pairing app, its a debugging app... it can connect to BLE devices and show their GATT profiles, update devices that have Nordic's OTA update code and copy a devices GATT profile to act as a BLE Server.
We use it for testing and debugging.
KindarConrath said:
The only other Bluetooth devices I have are other in-house hardware, running on SiliconLabs BGM13P chips or NRF52840 chips...
The NRF app isn't a replacement for your bluetooth pairing app, its a debugging app... it can connect to BLE devices and show their GATT profiles, update devices that have Nordic's OTA update code and copy a devices GATT profile to act as a BLE Server.
We use it for testing and debugging.
Click to expand...
Click to collapse
Ok. I recommend uninstalling nRF Connect anyway. If anything, to rule out the app. How old is your car and the Raspberry Pi? Even though BT 5.2 is backwards compatible, sometimes older BT devices won't work with newer devices. That doesn't account for the S Pen issue though.
I uninstalled nRF connect, and changed all the settings you both recommended. Exactly the same behaviour when I went to leave work. My car stereo would do music but not calls, then when I restarted my phone, it worked. Then when I got home, my S Pen would not connect to my phone, then I restarted my phone and it worked.
Its not a problem of not being compatible, its a problem of something stops working.
Please also note that these devices worked fine together in the past. I am concered that it is either a change made by an update or a Bluetooth chip that is faulty....
OP- Have you debloated at all and if so maybe you've removed something relevant that might be causing these issues?
No, stock image, no OS modification beyond the things that Samsung offers (GoodLock and Stock customisation)
I have our in-house apps for interacting with our equipment (over Bluetooth) installed, but #1 they shouldn't affect anything if they are not open and #2 they don't do this to ANY of our other test equipment.
I would just like to say, that I appreciate the assistance that you are all offering! I have used many forums over the years when looking for support on things and I rarely find a place that is more ready to try and help than XDA forums!
KindarConrath said:
I have been experiencing issues connecting to devices over Bluetooth. Sometimes it just works, other times it doesn't work at all, and some times it kinda works but not right.
All of these issues are resolved by restarting the phone, but that isn't a solution because the issue comes back.
3 Devices I have been having issues with
1. S Pen - Sometimes it won't connect to the phone, I get an "S-Pen Missing" message and it will not connect. If I t ry to connect to it manually via nRF Connect (The Nordic Semiconductors Bluetooth App) it tells me that the BLE device has a GATT error. It happens semi-randomly but I can always make it happen by doing #2
2. Car Stereo - This is the weird one, it will connect and play music, but it will not do "calls" if I connect to Discord it won't recognise the car as a Bluetooth device it can route to.
3. Raspberry Pi - This one it appears it will connect to ONCE, and then after a disconnect it will not connect again.
Again, each of these can be fixed by restarting the device, but they happen again after a while. The pen & RPi use BLE, I don't know what the car uses for calls.
Click to expand...
Click to collapse
I've seen the issue of the spen disconnecting but only a couple of times and the issue worked itself out within a couple of minutes with me not having to do anything.
I've also have had a couple of wonky issues when connecting a new Samsung phone to my car. I've narrowed down my issue to the fact that when I transfer my data & settings via Samsung smart switch, it includes the details of my Bluetooth pairings. To fix it, I have to go in and delete my Bluetooth phone settings from the car and from my phone and re-pair them.
Rubby1025 said:
I've seen the issue of the spen disconnecting but only a couple of times and the issue worked itself out within a couple of minutes with me not having to do anything.
I've also have had a couple of wonky issues when connecting a new Samsung phone to my car. I've narrowed down my issue to the fact that when I transfer my data & settings via Samsung smart switch, it includes the details of my Bluetooth pairings. To fix it, I have to go in and delete my Bluetooth phone settings from the car and from my phone and re-pair them.
Click to expand...
Click to collapse
As cool as I think Smart-Switch is as a program, I actually never use it when moving from one phone to another. The junk that Google drags with me from one phone to the next is already too much, I like to use a new device as a chance to do some housecleaning. So no old-data oddities here.
KindarConrath said:
I uninstalled nRF connect, and changed all the settings you both recommended. Exactly the same behaviour when I went to leave work. My car stereo would do music but not calls, then when I restarted my phone, it worked. Then when I got home, my S Pen would not connect to my phone, then I restarted my phone and it worked.
Its not a problem of not being compatible, its a problem of something stops working.
Please also note that these devices worked fine together in the past. I am concered that it is either a change made by an update or a Bluetooth chip that is faulty....
Click to expand...
Click to collapse
Hmmm.. Ok. You're probably right about the suspect causes. I know there is a code you can dial to get into diagnostic mode, I just don't know what it is.
The only other option you can try (as a last resort) is to factory reset it. If it is update caused, a factory reset MAY fix it. If you take it to a service center, send it in for repairs, or do a warranty replacement, they're going to factory reset it, or have you reset it.
have you tried running diagnostics in device care ?
or check with this dc
android
Bluetooth test*#*#232331#*#*
samsung
Bluetooth Test Mode*#232331#
I still haven't done a factory reset, but I continue to have the issue.
I have run the BT Test in device care, it always reports good.
I tried the codes, neither of them work as the first one is for vanilla android and the second is for older versions of Samsung firmware.
I've tried completely unpairing from the car radio and re-pairing, disconnecting and connecting from the other device to no avail.
KindarConrath said:
I still haven't done a factory reset, but I continue to have the issue.
I have run the BT Test in device care, it always reports good.
I tried the codes, neither of them work as the first one is for vanilla android and the second is for older versions of Samsung firmware.
I've tried completely unpairing from the car radio and re-pairing, disconnecting and connecting from the other device to no avail.
Click to expand...
Click to collapse
I'm not entirely sold on the idea that it is a hardware fault. It could be a hardware limitation; meaning you cannot connect to more than a certain number of devices simultaneously. I don't know how many BT devices you can connect to at once. I know at least two simultaneous connections (I've only had two simultaneous connections at a time).
You said you have other BT devices in your house other than those three your having issues with. How many are there? How many are you connected to at any given moment?
Is it possible that you have too many simultaneous connections?
When you try to connect to your car.. Did you check under BT connection (your vehicle) to make sure both audio and calls are checked..
doubledragon5 said:
When you try to connect to your car.. Did you check under BT connection (your vehicle) to make sure both audio and calls are checked..
Click to expand...
Click to collapse
Yes, and I've disconnected, reconnected and even unpaired and re-paired the phone to the car.
gernerttl said:
I'm not entirely sold on the idea that it is a hardware fault. It could be a hardware limitation; meaning you cannot connect to more than a certain number of devices simultaneously. I don't know how many BT devices you can connect to at once. I know at least two simultaneous connections (I've only had two simultaneous connections at a time).
You said you have other BT devices in your house other than those three your having issues with. How many are there? How many are you connected to at any given moment?
Is it possible that you have too many simultaneous connections?
Click to expand...
Click to collapse
Unless having multiple connections causes the BT to fail completely, no. Even after turning the car off and walking away, it still will not connect to the S Pen. The only BT devices I use with that phone regularly are:
S Pen, Car (Music & Calls)
At work I develop devices that use Bluetooth and I sometimes connect to them, but only ever one at a time.
Hi,
I just updated to the Android 13 OTA on the S22 Ultra (VZ, USA). All of a sudden my android auto stopped working. Wireless completely. Before AA wireless would connect to my car within a few seconds of my head unit booting up. Now it just waits at "Connecting". It knows my phone is available, but doesn't seem to want to connect.
If I plug in the phone, it works for all of ~20 seconds before disconnecting. If I just simply reconnect the cable it works again, 20-30-40 seconds before disconnecting.
Before the 13 OTA, it was working perfect, no disconnects on wired or wireless. So I 100% know it's not the cable or my headunit. Literally last night it was working, now it's not.
I checked sleeping apps on the phone and AA or Maps is set to never sleep/not optimized. Not sure what else might have changed.
I've uninstalled/reinstalled/cleared cache etc of AA on my phone. still nothing.
I fully reset my headunit to factory settings, I've done the network reset on my phone multiple times. I'd -really- like to avoid having to fully wipe my phone and try from there...
Has anyone run into this on their newly updated S22? Tips?Suggestions?
Thanks!
Me too. S22 ultra. Car is Mercedes A250 e. It's only a few days I have the car and I was able to connect only with usb cable in Android 12. I don't know if it is a limitation of the car not to be able to connect in wireless mode. Yesterday after OTA upgrade to android 13 I get the error unable to connect to android auto in the MBUX of the car.