I just got my new civic 2016 EX-T (in sexy blue) 2 days ago, but I've yet to get my phone to work properly with it.
I'm using Jedi rom, and have no issues connecting with either of my other 2 bluetooth devices. (a speaker and a radio transmitter)
The issue is that the phone will connect for a couple seconds, then disconnect and repeat ad-nausium every thirty seconds.
I re-paired them and they connected for the whole ride, but then when I turned it on today they refused to stay connected again.
Any ideas?
P.S.
Are any good note 2 roms out based on 5.0 so I can get android auto?
Related
I have a Sprint Touch Pro2 running stock 6.5 ROM and a 2005 Acura TL. When I got the phone a few weeks ago, I was able to pair the two without problems and it persisted reliably. I was able to shut BT off and turn it back on and the pairing would take place immediately.
Four or five days ago, though, the pairing would drop periodically, forcing me to re-pair, and now, the pairing will disappear almost immediately if I'm able to get them to pair at all. Most of the time I can't get the phone to 'see' the car.
FWIW, I use my own 4-number PIN, and when the phone sees the car, I'm able to enter that PIN and pair them.
I of course was installing a lot of stuff on the phone, although nothing that one would expect might affect the BT, so I flashed back to the stock 6.5 ROM last night to see if it helped (it didn't- same prob today).
Before I take this thing back to Sprint and smash it on their counter, anyone have any ideas about settings I might not be aware of that could affect this?
Thanks in advance for any help.
PS: I'm going to be testing my old phone (Treo 800w) on the car later to see if it still pairs to eliminate the car as the problem.
I've had the lg g3 (verizon, rooted) for almost 4 months. The phone has worked flawlessly with my car bluetooth until the past week or so. Now it, randomly disconnects from the car. I recently added clean master and cm security to my phone, but I deleted them to see if they were the problem and I am still getting random disconnects. Any ideas? Is there some type of app I can use to monitor (log) processes during the course of the day to try and identify what is causing the disconnect? I have tried unpairing and re-pairing the phone. The first time I used the phone after the re-pairing, there was no disconnect, however, in subsequent trips, the disconnect issue reappeared. Any suggestions appreciate, thanks in advance!
Has anyone else experienced frequent disconnects between the watch and the phone?
It was happening with my modded Note 3, which had a custom kernel so I was thinking it may be that. But now (for 2 weeks) I've been on a stock Note 4, and it keeps happening. Every once in a while, once a day or maybe once every two days, the phone and watch disconnect.
Android Wear says "connecting" but never does unless I click on Disconnect and then click on Connect, at which point it connects immediately.
I had "Find My Phone" installed, which would notify me when I got disconnected, so I thought it may be that. Uninstalled it a few days ago. Still happens. It's not a huge deal, but it's annoying and I don't see why it should happen.
Any idea?
Noticed the same with my 360 and Nexus 5. Both on stock latest versions.
Issue with mine is that the Moto360 constantly says Disconnected when trying to connect to my Note4. I click connect, it says connected and then quickly changes to Disconnected.
Been trying to figure it out for 3 days now.
I think I realized that the issue is in reconnecting.
I still don't know why sometimes it disconnects, but disconnecting itself wouldn't be an issue if then it proceeds to reconnect on its own.
But I realized that when I'm at home, I leave my phone by the computer and walk around. If I walk outside of the bluetooth range, then it disconnects. That's fine. But then it should reconnect when I come back into range, and it never does. It says "Connecting" and never reconnects unless I do it manually as I said in the OP.
So I guess the question becomes: why does it get stuck on "connecting" when it's in range and should be connected? Is this a Samsung issue or a Moto360 issue?
I have seen the same issue with my Moto 360 and an original Moto X. It normally reconnects but then once in a while it just won't. The easiest solution I have found is to turn bluetooth off and then on again on my Moto X. That always brings it back, a reboot of the 360 does not.
Well as I said in the OP, if I go into Android Wear, click Disconnect and then click Connect, it works. But there is absolutely no reason why it shouldn't auto-connect. If it disconnects, and I don't notice, the rest of the day I go without notifications until I realize the watch has disconnected. That's not how this should work.
Max_Pain said:
Has anyone else experienced frequent disconnects between the watch and the phone?
It was happening with my modded Note 3, which had a custom kernel so I was thinking it may be that. But now (for 2 weeks) I've been on a stock Note 4, and it keeps happening. Every once in a while, once a day or maybe once every two days, the phone and watch disconnect.
Android Wear says "connecting" but never does unless I click on Disconnect and then click on Connect, at which point it connects immediately.
I had "Find My Phone" installed, which would notify me when I got disconnected, so I thought it may be that. Uninstalled it a few days ago. Still happens. It's not a huge deal, but it's annoying and I don't see why it should happen.
Any idea?
Click to expand...
Click to collapse
Hi, i have the same problem, my watch always disconect to my phone (moto x), and then the bluetooth system never start again. When I enter in setup ---- bluetooth---- the bluetooth switch doesn t turn on again until phone reboot.
this is so annoying. and it seems like there's a few people experiencing the same thing but nobody seems to have hit a solution. I have yet to come up with one. if I do, i'll post on here.
Same happens with mine. It just prompts me with a "connect" screen on my phone once in a while. After connecting 2-3 times, it won't appear until next time I turn off Bluetooth.
I get this problem about 2 times per day...running with a Note 2 running 4.4.2 stock but rooted....
Sometimes when my Smartwatch 3 loses the Bluetooth connection to my phone, reconnecting takes minutes or doesn't work at all unless I'm disconnecting and connecting it manually in the Android Wear app.
Moreover, when Cloud syncing is deactivated, it just won't connect via Bluetooth at all.
I'm using the latest version of Android Wear, Play Services and CM12.1 on my Nexus 6. Is this a common issue? Is it normal to take several minutes for the devices to pair again?
Gesendet von meinem Nexus 6 mit Tapatalk
I have had similar problems which turning bluetooth on/off helps. This normally coincides with a battery drain but doesnt happen often. You can always try a factory reset of the watch
I have had the watch for only two days - just bought one from the $99 sale at Verizon. During these two days, there have been at least four times where it would randomly disconnect from my stock Nexus 6 (6.0.1) and will not reconnect. The Nexus 6 shows up under Bluetooth devices, but when I click on the connect button, it will not reconnect. I have turned Bluetooth off and on the phone, and still will not connect. I have had to go in and remove the device and set it up each time to get it connected again. Any help in getting this resolved would be appreciated.
My pixel 3 xl will connect to Android auto via USB.... Work for a few minutes then randomly disconnect. Never happened with my pixel 2.
Any suggestions??...I have tried new USB cable.... Still does same thing.
Sent from my Pixel 3 XL using Tapatalk
I have had occassional issues with Android Auto as well -
When I first got the Pixel XL I was able to connect fine via USB and even wirelessly to my Kenwood headunit - but the other day, after connecting to Android Auto, when I tried to make a phone call, Blue Tooth was not connected and I could not get it to connect. I eventualy toggled on and off Airplane Mode - and after that
it connected fine. Havn't had an issue since (knock on wood)
for your situation, have you made sure that USB Debugging i turned off? It won't work with that turned on....
Same problem here.
Never had an issue with my Pixel XL, Pixel 2 or Pixel 2 XL. Yesterday I received my new Pixel 3 XL and Android Auto keeps disconnecting. Sometimes it does last a few minutes, sometimes it does so after a few seconds. It doesn't matter if an app like Spotify or Maps is being started or if I just connect the cable. Android Auto doesn't stop on the phone but only disconnects.
As you can't deinstall Android Auto I already tried wiping cache, wiping data and deactivate. I even tried three different cables.
When I connect my work phone Pixel 2 I don't see this problem. The connection is kept as usual.
I'm getting grey hair over this.
Has anyone found a solution or workaround for this issue?
I've tried absolutely everything, even rolled back to a nano SIM after started with an eSIM.
Gonna RMA this week and cross my fingers.
I wonder if it's a hardware issue or software. Unfortunately I don't have another phone that runs pie so I can't test it. My v30 running nougat works fine. I'm kinda waiting for the next pixel update to see if it fixes it.
If you do rma your phone let us know if that fixes the issue.
Turn off adaptive battery and see if that helps you
Nope, that doesn't help. As I mentioned I have every previous Pixel and all of them work flawlessly with my head unit. All preferences are the same.
There's only one obvious difference: Android Auto is pre-installed on the 3 XL.
Unfortunately I don't know anybody with Android Auto in the car nor owning a Pixel 3 XL to check out if it's something with my head unit.
In a German forum 2 people say they have it working properly...
One of the most frustrating parts is that - for me - it sometimes it works 10 minutes. After I switched back to nano SIM yesterday on my drive home I connected, listened to great music, whatsapped my wife that it is working and boom...disconnect and from then on the known behavior started again.
Did the new rma device fix the issue?
Just send it today and because I bought from provider I've a couple of days for the new one. Used my good ol' Pixel XL today working like a charme...
I'll update when the replacement has arrived.
Experiencing same issue with Pixel 3 non-xl and 2016 Honda Accord. Android Auto disconnects anywhere from 20 minutes to just seconds after I've connected.
I've tried the following:
-Variety of brands of USB-C > A cables
-Disabling all power saving options (whole phone, specific apps)
-Setting screen to stay on when charging (solved AA disconnect issues on my LG V20)
-Re-pairing bluetooth with car
-Re-pairing AA with car
-Resetting car head unit
-Resetting phone
I've had no issues with disconnects, but I use wireless connection with Pioneer headunit.
I got my replacement today and for now the problem looks to be solved but I only sat 20 minutes in the garage messing around with it but that are 19:50 more than my last attempt with the old one.
But I already installed both Android Auto app updates that came in the last couple of days.
/me is crossing his fingers
I'll drive about one hour in the evening and hope everything stays how it is now
It's a pixel 3 software issue. Big thread in the Android Auto support forums. Google doesn't seem to be in a hurry to fix it. Said the November update should, it did not.
Anyone ever find a fix for this? I'm having the same issue, but now cannot connect at all. (Was working. Stopped the car, went into Starbucks, came out and AA won't connect.) My Pixel 2 XL works fine, but I want to sell it.
Like I said I RMAd it and it works flawlessly ever since.
Android Auto Closing Out on Pixel 3
Did anyone find a fix for this? I'm having same problem with a new Pixel 3 (not XL). It will project to the car screen/monitor temporarily, but then disconnect and close out of Android Auto. Sometimes it will automatically switch back in a few seconds. Other times I need to disconnect the USB cable from the car and reconnect to get it to project the screen again. It closes out Bluetooth and stops playing from the phone too. This seems to be an issue with the phone, as I've had this problem in multiple cars. My only solution is to run AA on the phone and not project it. Is Google doing anything about this?
Wahoodean said:
Did anyone find a fix for this? I'm having same problem with a new Pixel 3 (not XL). It will project to the car screen/monitor temporarily, but then disconnect and close out of Android Auto. Sometimes it will automatically switch back in a few seconds. Other times I need to disconnect the USB cable from the car and reconnect to get it to project the screen again. It closes out Bluetooth and stops playing from the phone too. This seems to be an issue with the phone, as I've had this problem in multiple cars. My only solution is to run AA on the phone and not project it. Is Google doing anything about this?
Click to expand...
Click to collapse
My phone connects fine to AA. It stays connected with the cable. Perhaps try a new cable to connect it. I'm on stock rooted.
Sent from my Pixel 3 XL