Related
I didn't see any other threads on this and I'm not sure if it might be specific to the Verizon Galaxy Nexus or Lexus/Toyota cars. Since Jelly Bean, I've already had my car's bluetooth connectivity go into a weird state with the phone three times.
The car will be playing music (default music app) and the navigation app, playing just fine through the car's bluetooth, and then, both the car and phone will indicate connected, but the sound will stop. If I turn off the car, the bluetooth on the phone thinks its still connected. The only way to clear the condition is to turn off the bluetooth on the phone and turn it back on. So much for that "extra" Verizon testing. This all worked fine for me with ICS.
Anyone else see a problem like this?
Thanks!
I am having occasional problems connecting since jb. Was rock solid on ics. I am on sprint and have a Lexus.
This is my only issue with 4.1.
Sent from my Galaxy Nexus using xda premium
Samsung Galaxy S3 running Omega JB 4.1.1 - Driving a Toyota Prius
Greetings
I myself have experienced odd bluetooth issues with my Samsung Galaxy S3 running Omega JB 4.1.1 version 30 whilst driving my Toyota Prius.
Every 5 mins or 10 mins or so many minutes the audio from my podcast, for example, stops dead and I have to open up the app and hit play for it to continue.
Bizarrely I also experienced this the other day whilst driving a VW too.
Was fine on ICS.
I've you to find a solution.
I've been using Omega since version 25 and have also experienced the same issue on the Wannam custom stock rom.
Tonight I placed the device into Aeroplane mode and kept bluetooth running and the problem persisted.
I have no idea with regards I'm afraid.
Thanks
Dave
Update: I found that the audio issue I was experiencing was not bluetooth specific. I tried direct in to the car audio via the AUX jack and the problem persisted. But I also noted that after a clean install of a rom the issue did not exist so I worked my way towards the removal of the Deezer app and since then I have not experienced the problem. Go figure?
I am not having this problem with my Nexus and my myford touch sync setup. I do, however, get a lag between video and sound, where the sound is behind of the picture and out of sync. *shrug* Wish I could help more.
I can't even do more than phone on my 2012 BMW. No mobile office but calls work fine. When the CSR is turned off it doesn't switch to headset like it will of my wife's 2004 lancer.
Anyone else having issues with connecting the 7T to their car and getting audio going out of it? My OG Pixel didn't have a problem, but I have to toggle off/toggle on Bluetooth and then manually tap the car's bluetooth listing to get it to actually 'connect' the audio portion.
Rather annoying, considering I'm only in the car for a few minutes at a time, this either eats into the time entirely, or makes me sit in my car for a couple minutes before even driving to fiddle with the bluetooth settings.
Car has stock headunit, 2015 Evo X. Like I said, original Pixel XL had no issues, but this is annoying. I've tried changing bluetooth versions to no avail. I can see it connecting and dropping the bluetooth connection fairly frequently while staring at it and trying to 'get it going'. But once it connects, it stays there.
My bluetooth headphones (Some knock off cheap Chinese ones for $20) don't seem to have an issue.
My connection to my aftermarket stereo is fine. Just seems a little quieter than my last phone. Connecting is kind of slow too when I start my car but it is automatic.
I don't have any issues with connecting to all 3 cars (2014 Honda Accord, 2009 Pontiac G8 Gt and a 2018 Honda Fit) but I do agree that the volume seems a little lower than my previous phone (Galaxy S8).
Sent from my [device_name] using XDA-Developers Legacy app
Hmm. Weird. Is there anyway I can check for logs to find out what exactly is happening? I haven't rooted, just don't know if it's something I can naturally pull from Android as a whole.
I had the same issue, but when I made the phone discoverable and initiated bt from the car stereo it seemed to work.
I also set a custom pin , not the default 0000
My bluetooth is quiet, but its also static-y. I never had any issues with my G6 and now I get static clipping every 10 or so seconds. Its unbearable.
jagadeesh16 said:
I had the same issue, but when I made the phone discoverable and initiated bt from the car stereo it seemed to work.
I also set a custom pin , not the default 0000
Click to expand...
Click to collapse
I'm not really having an issue pairing it, but it's just connecting after pairing is the problem.
I have changed the default pin. I can see it popping up and down the car stereo a few times in the bluetooth settings before it just gives up.
As for the other issues, I'm not having a problem at all with audio volume, nor popping/static when it finally does connect.
My volume is super low when connected to Android Auto and streaming music. Have to turn the radio up to max. However, I'm assuming that's an AA issue or Android issue, as it seems many others are having the same problem with different phones. Been thinking of adding an aftermarket amp to the car. Maybe I should pull the trigger. Lol
Phreak411 said:
My volume is super low when connected to Android Auto and streaming music. Have to turn the radio up to max. However, I'm assuming that's an AA issue or Android issue, as it seems many others are having the same problem with different phones. Been thinking of adding an aftermarket amp to the car. Maybe I should pull the trigger. Lol
Click to expand...
Click to collapse
Be careful that a bugfix doesn't come and blow your eardrums out, lol.
Milkshakes00 said:
Be careful that a bugfix doesn't come and blow your eardrums out, lol.
Click to expand...
Click to collapse
LOL that would be my luck
.
My OnePlus 7t connects fine and phone works for calls on 2014 cts. The sound comes out of phone can change song on head unit but I can't get audio to play through car. Anyone else get this?
Yeah music stutters with car player... Only calls work. Music works on headphones etc. I couldn't find solution, did network reset, cleared cache. Nothing works.
Seriously!
I've wasted at least two hours already trying all the recommended steps: from flicking icons on and off to a full phone reset.
Still no connection to my Suzuki S-cross car. Multiple previous phones have connected effortlessly.
Even the $50 temporary five year old borrowed phone could handle it.
Anyone got any other suggestions? Yes, tried the AVRCP setting change from 1.4 to 1.6. That didn't work either...
Barebones system reset from scratch running O2 OS 10.0.6HD65AA
Any suggestions greatly appreciated.
I need to be able to talk and drive!
Reset the car radio and clear all pairing data if you can. Then try again.
autosurgeon said:
Reset the car radio and clear all pairing data if you can. Then try again.
Click to expand...
Click to collapse
Thanks for the suggestion.
Tried that.
Tried one other car - no problems.
Tried a tablet and a very old phone with the car and suprise - the car's bluetooth seems to be the problem.
I will try and find out if I can fix the car!
UPDATE: Morale of the story - read the car manual very very carefully and go though each tedious step = SUCCESS
mikefnz said:
Thanks for the suggestion.
Tried that.
Tried one other car - no problems.
Tried a tablet and a very old phone with the car and suprise - the car's bluetooth seems to be the problem.
I will try and find out if I can fix the car!
UPDATE: Morale of the story - read the car manual very very carefully and go though each tedious step = SUCCESS
Click to expand...
Click to collapse
Yep most have lots of tedious steps that are different model to model and if not followed exactly will cause this problem on occasion..
In my case music starts to be scrambled after 10 minutes or so of listening. When I take the phone (so the watch pops up) or turn on the screen it immediately works fine again, but when being put aside and the screen turns off, the issue starts again ..
Also in the early days of my previous 5t I had the same issues but some fix was delivered together with oxygen os update. And now the same story again
I have a different issue with Bluetooth:
- OP7T connects to car Bluetooth fine
- I can make/answer calls
- Bluetooth media works fine
The problem is with Google Assistant & car audio:
- it was working as intended until the latest update - 10.0.15 - I was pressing the button on the steering wheel the google assistant was answering questions through the car bluetooth, no need to switch to bluetooth media.
- after the latest update, when I press the button on the steering wheel, Google assistant pops on the phone , starts to answer question, but cuts off after 5 seconds. the command still goes through and Assistant still runs, but does not come up on the car audio.
- it looks like the Assistant is not connecting to the car as a hands free, but as to a bluetooth handsets.
Anyone experiencing this?
Hi everyone,
I'm having a problem that I think shouldn't happen on this phone.
I'm stock with the latest January update on Android 10.
Info: this problem was present before the update to 10.
Whenever I connect any Bluetooth device (airpods, car, moto intercom ,etc) I have to manually unpause the music to get it to start.
This happens on every player (Samsung Music, Google Play, YouTube premium, etc)
This is the first Android phone I have that doesn't do this and that shouldn't be seeing it's top tier.
I've looked online and it seems that all Samsung phones have this feature and the only topics I get are how to disable it !?
Can anyone shed some light ? Is it happening to you as well ?
Thanks
I may not have the answer that you want to hear but I did find a temporary solution. There's an app in the play store nRF Connect that works. Slide over to bonded, put devices in pairing mode and hit scan and wah lah. Any questions I'll do the best I can to help.
I've noticed the same on my galaxy buds, but when I connect another pair of wireless earbuds that i sometimes use they connect as soon as i turn them on when Bluetooth is activated, without me manually having to go into the settings and do it. Not sure the reason for this. Would've thought the earbuds that's actually made by Samsung would be the ones connecting right away.
hotshot646 said:
Hi everyone,
I'm having a problem that I think shouldn't happen on this phone.
I'm stock with the latest January update on Android 10.
Info: this problem was present before the update to 10.
Whenever I connect any Bluetooth device (airpods, car, moto intercom ,etc) I have to manually unpause the music to get it to start.
This happens on every player (Samsung Music, Google Play, YouTube premium, etc)
This is the first Android phone I have that doesn't do this and that shouldn't be seeing it's top tier.
I've looked online and it seems that all Samsung phones have this feature and the only topics I get are how to disable it !?
Can anyone shed some light ? Is it happening to you as well ?
Thanks
Click to expand...
Click to collapse
Hej...
I don't if this would help You...
When I got the Note 10+ there's Was, out of the box on initial settings, active few Bixby Routines... and that, till i figure out this, was driving me crazy... When I turn Bixby Routines off everything back to normal...
Well I've had a similar problem. For me the issue is that it always autostart even tho I have BT autoplay unchecked in the car. If I have listen to any music, audio books, podcasts and turn them of when I exit the car, not leave them in the background, they will start playing even if the cars media system is offline.
Works perfectly with my wifes OnePlus 6, but not for me. Extreamly annoying to noticed that the audio book is playing after a 60min drive and I haven't heard anything..
I tried the app Tasker, it was a compleat waste of $4 for me anyway, didn't work, will try nRF Connect now.
I don't want to have BT of due to that I aways have my Jabra buds with me so that I can talk while driving if needed.
I tried to see if anyone posted a similar question but haven't found anything. Is anyone else having issues with their Pixel 6 Pro while connected to Android Auto? I have 3 issues that are bugging the crap out of me.
1. Every time I connect my phone to the car, it always pops up asking permission to connect to this "new" uConnect device. Its been connected hundreds of times, and even adding it as a trusted device, it still pops up.
2. The sound quality is absolute garbage. Its muddy and heavy on the mid level. I have tried to compensate by adjusting the EQ in the head-unit, and Spotify. It helps, but not much. I have tried my old Note 10+ and the quality is perfect.
3. Often when receiving a phone call, I can answer and control the call using the head-unit, but the audio is going to the phone and not the car speakers.
I have been able to replicate this with both of our Pixel 6 Pro's, and in both of our vehicles (2019 Durango R/T, and 2020 RAM 2500)
Anyone have any ideas?
EDIT: this is wired using different cords for troubleshooting purposes.
I have none of those issues but my issue with aa is that it keeps turning off preview incoming message
Issue #3 I do get from time to time. Annoying AF. Also trusted device only last 4 hours I believe which I think is ridiculous.
imo... Spotify always sounds like crap.
Haven't had any of these issues at all. Everything works well for me on the December update.
I have none of these issues, but the issue I get is specific to Google Maps on Android Auto. When I'm navigating somewhere, often at the start of the trip Google Maps cannot get a GPS lock on me and the map skips all over the place, constantly rerouting me. After I continue to drive I eventually will get GPS lock and then everything works fine.
Using Waze on Android Auto, everything works fine. I get GPS lock instantly when I switch to the Waze app on Android Auto. So all I can conclude is the issue is specific to Google Maps... It's not that big of a deal but can be very annoying.
Edit: I'm on wireless with a Pioneer AVH deck.
My wifes Pixel 6 works fine apart from the battery icon constantly flashing on and off (on the car display)
I don't have any issues with Android Auto in my 2020 Subaru, and neither does my wife.
No, I don't have these issues either. Working fine for me on Lexus NX.
Edit: "wired" that is (to be clear).
I am not seeing any issues in my 2020 Kia Soul. I use the wireless android auto adapter (AAWireless from Indiegogo) so I do not have to plug it in though.
Could your uConnect system need an update? You can check here for one: https://www.driveuconnect.com/support/software-update.html
Caveman419 said:
I am not seeing any issues in my 2020 Kia Soul. I use the wireless android auto adapter (AAWireless from Indiegogo) so I do not have to plug it in though.
Could your uConnect system need an update? You can check here for one: https://www.driveuconnect.com/support/software-update.html
Click to expand...
Click to collapse
Great Idea, unfortunately they are already up to date on the software. That AAWireless thing is pretty cool, but plugging it in doesn't bother me that much, plus I know its charging.
GtarSkater said:
Great Idea, unfortunately they are already up to date on the software. That AAWireless thing is pretty cool, but plugging it in doesn't bother me that much, plus I know its charging.
Click to expand...
Click to collapse
I always have issues with cables that keep disconnecting and have to unplug and re-plug in (both my car & my wife's 2016 Hyundai Sonata). The AAWireless is very handy in that regards. It will occasionally freeze up, but very rarely after a few OTAs ago. The only downside that I have found is that if you get too close to the vehicle with BT Headphones (mowing or other yardwork typically), it will connect to the AAWireless and cut off audio to the BT Headphones. I just unplug the AAWireless from the car until I am done then.
I should mention all my issues only occur when I'm wireless in my car. When I use wired in my friends car, it works fine.
GtarSkater said:
I tried to see if anyone posted a similar question but haven't found anything. Is anyone else having issues with their Pixel 6 Pro while connected to Android Auto? I have 3 issues that are bugging the crap out of me.
1. Every time I connect my phone to the car, it always pops up asking permission to connect to this "new" uConnect device. Its been connected hundreds of times, and even adding it as a trusted device, it still pops up.
2. The sound quality is absolute garbage. Its muddy and heavy on the mid level. I have tried to compensate by adjusting the EQ in the head-unit, and Spotify. It helps, but not much. I have tried my old Note 10+ and the quality is perfect.
3. Often when receiving a phone call, I can answer and control the call using the head-unit, but the audio is going to the phone and not the car speakers.
I have been able to replicate this with both of our Pixel 6 Pro's, and in both of our vehicles (2019 Durango R/T, and 2020 RAM 2500)
Anyone have any ideas?
Click to expand...
Click to collapse
Personally, I do not have an Android Auto enabled car.
I can tell though that there were numerous reports in the past (XDA, Reddit, Discord, Telegram) of people having problems with Android Auto. Now the problem with that, is...
a) Android Auto has always been buggy - even with cable. I have friends that have been trying to get Android Auto to reliably work with their Samsungs (cable) for years, and their attempt are still a work in progress. It's a hit-and-miss. Sometimes it works, sometimes it doesn't.
b) Android 12 is extra buggy and has been known to cause problems with Android Auto (reports of Samsung owners upgrading to A12)
c) Pixel 6 Pro is extra special buggy and it's more or less unknown at this point, if Android Auto issues are caused by Auto Auto being a buggy mess, Android 12 being a buggy mess, Pixel 6 being a buggy mess or a culmination of the three together.
d) Plus, there is a massive difference in reliability between Android auto cable vs. wireless.
I did see some workarounds floating in the web, you might be able to find them in Reddits GooglePixel group.
In the end though, your best bet (longterm) would probably be: Go into settings, report the problem directly to Google and make sure that all your friends and family that also use Android Auto do the same.
Firstly, an enormous thank you to all the amazing Devs that are still building ROMS for this old (but great!) tablet! Your work and expertise are greatly appreciated!
I've acquired a Nexus 7 2013 Flo 16gb. I wanted to tether WiFi from my Samsung S9 phone via Hotspot and use this tablet for Sat Nav and music etc in my car, a 2011 Ford Grand C-Max. It isn't permanently mounted, just with magnets on the dashboard so I can use it for other things when I'm not driving.
Using the N7's Bluetooth, I can see "Ford Audio" and get a PIN to use displayed on the cars LCD screen when I tap "connect". Everything works fine until I leave the car and take the tablet with me...
The next time I get in the car, the tablet will still see Ford Audio, and the car still lists the N7 as remembered device, but it absolutely will not connect to it again.
If I try to connect using the car's aux button, it'll say "Activating BT Device" for around 30 seconds and then shows "Activation Failed".
If I tap connect on the N7, sometimes it says "connected for a split second and then disappears again as if I never tried to connect.
The only way to get them connected again is to fully debond the N7 from the car, then reconnect from the tablet by entering a PIN number again.
My Samsung Galaxy S9 phone, (and my old Samsung Note 3 phone) doesn't have this problem. I pair the phone once with a PIN, play music with no problems, leave the car, come back, press the Aux button and it immediately picks up Spotify from where I left off. It also displays the name of the song being played and the amount of time the track has been playing, this doesn't happen at all with the Nexus tablet.
I've tried removing all Bluetooth devices from the car, changing the display name of the N7 tablet, 3 new ROMS (Lineage 19, Resurrection Remix Q and RR Pie.) It did this on Stock so thought using a more modern custom ROM would fix this strange problem but 3 ROMs later it's still happening.
I've Googled, and read on XDA, seems a lot of people had Bluetooth problems with this tablet back in the day, but that was on Android 4.4.2... But I'm still feeling this on Androids 6, 9, 10 and 12 so far, was there really never a fix found for Bluetooth problems on this device?
Does anyone have any ideas of what may be going wrong? Or any trouble shooting steps to advise? It's too much fuss to remove and re-pair the tablet every time I leave the car so any help would be appreciated please!
I can now add LineageOS 14.1 (Android7) with the ElementalX kernal to the list.
It does the exact same thing as the other Roms, pairs and connects perfectly the 1st time... After that it stays paired but doesn't connect.
If music/Spotify is already playing on the N7 and I click to connect to Ford Audio in the bluetooth settings, the music will be played on the car speakers for around 2 seconds and then stop, and then start again for another second... And then be gone forever! So bizarre.
The only way around this I can see is to buy an Aux > Bluetooth adapter from Amazon, pair the N7 to it and use the Aux channel for Audio out from the tablet over bluetooth. But I'd lose the ability to skip tracks with the steering wheel controls.
Until recently I had a N7 (2013) as my nav tablet in my vehicle. It was running Lineage.
I didn't have it paired to my stereo system, but it was paired to my steering wheel controls.
I didn't take it in or out, so that simplified things. It had a battery-ectomy and ran on a 4V regulator.
I ended up replacing it with a Walmart Onn 8" $70 tablet.
The Bluetooth spec is 3700 pages so it's doubtful that anyone has ever implemented it correctly.