morning/afternoon/evening all
Recent got a Find X2 pro (had an S20 but was the worse phone i've had in years).... in general enjoying the phone but having issues with Android Auto (seen quite a few posts on AA but not my issue)
phone connects to bluetooth fine and makes/recieves calls without issues.... Plug my phone in to the cars usb (Citroen C3 18 plate) and it goes into charge only mode, maps then is offline but Spotify is online as normal , change the connection to file transfer/Android Auto it disconnects and relaunches AA but now maps is online and spotify is in offline mode.
Not had an issue with any other phone i've used with my car but this one is very temperamental.. i could switch to Sygic maps instead but rather carry on with the google maps.
Phone is updated to color V11 CPH2025CPW_11_c.68
any help would be great
have considered a factory reset as did a transfer from my Samsung last time
seem to have found the issue. done a factory reset
After being on wifi in my house, wifi is still in range when i plug into my car, once i drive off even though i usually have 3g/4g/4g+ signals it keeps offline until it seems i turn my screen on so might be another keep screen on job
Related
Whenever I plug my phone into my car stereo to use Android Auto I get the tell-tail single buzz of the S3 going into stand-alone mode. Which is bad enough, because while Android Auto can handle text messages, I like to be able to just glance at my watch for other notifications, but then when the phone is disconnected from the car, the watch will never automatically re-connect to the phone.
If I think about it I can use the pulldown access to the gear software on the phone (while still connected to the car stereo) and re-connect it. At this point it will stay connected to the phone unless I disconnect and reconnect Android Auto to the phone which will cause the S3 to disconnect from the phone again.
Does anyone know anyway to stop the disconnect, or at least some way to get it to auto-re-connect after?
Thanks!
tobiasj42 said:
Whenever I plug my phone into my car stereo to use Android Auto I get the tell-tail single buzz of the S3 going into stand-alone mode. Which is bad enough, because while Android Auto can handle text messages, I like to be able to just glance at my watch for other notifications, but then when the phone is disconnected from the car, the watch will never automatically re-connect to the phone.
If I think about it I can use the pulldown access to the gear software on the phone (while still connected to the car stereo) and re-connect it. At this point it will stay connected to the phone unless I disconnect and reconnect Android Auto to the phone which will cause the S3 to disconnect from the phone again.
Does anyone know anyway to stop the disconnect, or at least some way to get it to auto-re-connect after?
Thanks!
Click to expand...
Click to collapse
I just noticed this... 8 was wondering why I was always disconnected from my s3....
Sent from my SM-N950U using Tapatalk
Same **** happening here too with no solution in sight. This is pretty frustrating honestly.
Sent from my SM-G965U using Tapatalk
I never had the problem of disconnecting when plugging IN for Android Auto, but I did have the problem when shutting off the car, which always caused the S3 to disconnect. The solution for that I found in another thread; unplug the phone from the head unit BEFORE shutting off the car and the watch stays connected. Obviously this doesn't relate to your issue, but in case you get it working on the front end, but find the disconnect after shutting down, remember this fix. (same issue happened on both my Galaxy S8+ and now the S9+ on the Pioneer AVH-4200NEX)
The key is to plug in your phone only after it's connected to the car Bluetooth and then unplug it before you shut off the car. I do this every time and have never had to reconnect my watch.
I have the same issue. I've gotten around it using automate. There's a script specifically for it in the automate store. Just change the ID of the watch in the flow and it should work.
Hope this helps - this was annoying me for the longest time until I tried this.
Since the Oreo and Wear OS updates I've had severe connectivity issues which didn't exist beforehand. I thought I had cracked it with a factory reset of the watch and removal + reinstallation of the phone apps...
However for days now my watch hasn't been showing as connected in my phone's bluetooth settings but it has been showing as connected in the Wear OS & Huwaei Wear apps and I had been getting messages on the watch etc so I thought nothing of it. Just now I tried to make a phonecall using the watch and it said the call couldn't be made, check my bluetooth connection. So despite both phone apps saying that I was connected and the phone's BT saying that I was connected (*for a change!) there was some issue. I switched BT off & back on again on the watch and then I could finally make the call.
Buggy!
Is anyone else experiencing these phantom connectivity issues between their watch and phone since the latest updates?
I have the same problem, I did not come to the repair
I have the same problem and i found a temporary solution for it. Switch on and switch off aeroplane mode.
Same problem here. I have the 4G version of the watch and now am always connected in 4G, the bluetooth is indicated by the phone (Huawei Mate 10 Pro) as connected in the system settings, but is not connected neither on the watch nor on Wear OS app.
same problem here
Bluetooth losing connection
Here's the solution:
1) unpair watch from phone
2) delete Bluetooth app's cache on phone
3) reboot phone
4) repair watch with phone
Since I did these steps I have had no issues with Bluetooth connectivity...
Hope it helps you....
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've been keeping my battery alive by using Battery Pro app but you have to monitor it 24/7. So I bought a couple of CHARGIE devices - a hardware controller that goes between the cord and charge block to turns charging on and off via an app.
My phone connected to the device only once during many tests. I've been trying various settings and suggestions by the company. They insist it will work with Android v6 so maybe the phone is the problem. Device requires bluetooth "ble" so I turned on full location options (GPS, Wi-fi, bluetooth, cellular networks). I turned on setting to display all ble devices - shows a printer from a neighbour's house but not a Chargie 2 feet away! Ideas or information welcome...
Bluetooth is required for basic communication with the Chargie device, but if your particular phone's Bluetooth doesn't work, you can use another phone to configure Hardware Limiter and use it on the 1st phone without the app. Location Access is unfortunately required by Android's device scan library. Chargie doesn't use it (no purpose). iOS doesn't request that, for example.
If that particular Chargie doesn't work at all, on any phone, please contact [email protected] and it will be replaced for free.
Thank you so much for the info. The Chargies work (I have 3), just not reliably or quickly. I can plug in my phone right beside the Chargie and the app says it isn't in "range". Or it continually says the BLUE Chargie isn't in range even when plugged into the RED one! I had all radios including GPS on during the testing but GPS isn't needed. Still not sure how Airplane mode with Bluetooth turned on affects it. BTW my Oneplus One has Bluetooth 4.0.
Getting the phone connected takes so long, it's hardly worth the time to figure out the "hardware limiter" option with a Windows laptop. Not much documentation on it. I certainly don't want to leave my phone beside the device while charging. I was getting some answers via email until I asked how to return the devices. I may have to just accept that the device works 'sometimes'.
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.