I've been using my Galaxy 3 for a couple years with my car's stereo to listen to MP3s and Audio Books and hoped to continue doing the same with my new Note 4 DE.
Previously, once everything was paired up and working fine, if I turned off the car to go into a store or work or whatever, when I got back in and started the car up, after a couple seconds the bluetooth device would just continue playing where I left off.
Now, when I start the car the stereo flashes "acquiring Bluetooth data" and then for like half a second it shows the normal screen with the info on what the phone is trying to play, like track listings and all that, then instantly flashes back to the "acquiring..." message, and repeats endlessly.
I have to turn off Bluetooth on the phone for a second to get it to stop, then I re activate Bluetooth and have to either re-pair, or change the stereo source to FM/CD/etc, then back to Bluetooth, and then it will start working as intended.
This thing is brand new, all stock software except the basic root done on it.
It's not a Bluetooth or note 4 issue and maybe more of an interoperability issue. I have a Rav4 with my note 4 stock retail and it functions like you describe with automatically starting when I enter the car. It starts where I left off.
Related
Got my AT&T Galaxy Note II. Have left the ROM, bootloader, etc. all stock.
Where my Galaxy Nexus would have trouble uploading my phonebook to my 2012 Honda CR-V car stereo without Navigation system, the Note II seems to pair without issue.
HOWEVER, if the phone is unplugged from power... about once every two minutes it drops the BT connection from the car stereo, and about 20 seconds later reconnects. I say if unplugged, because if I plug the phone into a cigarette lighter charger, the BT seems to stay up and stable.
I figure this could be a BT timeout issue, or perhaps some power setting we could adjust? I have disabled the power management functions on the Note 2, but that has not prevented the issue from occurring.
I also have a Sony SmartWatch that I have paired to the phone. The watch doesn't have any issues, but whether I have the watch on or off, I see the same functionality between the phone and the stock car deck.
I'm having the exact same problem, I thought it was an issue with my vehicle's Bluetooth antenna.
I tried calling Samsung about this issue and they were, as expected, pretty unhelpful.
I'm having a similar problem with my Ford Sync Bluetooth connection. Except I'm only using battery power.. The first time I connect for the day, all seems fine. Any subsequent connections during that day are problematic with connect failures or random disconnections.. Must be a gnote2 bug as my gnote1 (stock ROM) worked perfectly in my car.
As soon as I read this, I began to wonder if my issue is somehow related.
http://forum.xda-developers.com/showthread.php?t=2015748
same problem here with SGN2 and Veloster...I lose my connection after a few minutes. Before with my HTC, I had no problem .
BT works fine for me in my MDX stereo and on my BlueAnt device. I don't have to plug it in or anything... just turn it on, pair it and go.
My note 2 is bone stock - just rooted so I can use Titanium Backup.
My issue today is that my bluetooth will not pair properly and remember its configurations. My initial pairing on my phone with my car's flexsmart X3 works perfect, however when I turn off my bluetooth on the phone or turn off my car and turn it back on the phone will still see the flexsmart and it will say it is paired but I get no sound. Upon further investigating I find that in the options setting that neither the call nor music tick box is checked. If I try to tick them it will think for a few seconds and then gray out and do nothing again.
I never had a problem with my note 2 or my temp replacement evo 3d remembering these settings. All I would do with those phones was pair it once and then any time I hopped in the car I would just turn onm,y phone's bluetooth and go. Now with my note 4 I have to unpair and repair the devices each and every time which is a huge pain.
I have read a little bit that this is due to samsung note 4 using a newer bluetooth standard than its predecessors. Is there anyway to circumvent this issue by maybe rolling back the bluetooth drivers or something? I even thought about creating a tasker profile to help with this but still I would have to physically press the search button on the flexsmart eachtime.
Any and all suggestions would be great. Also right now I am on rooted stock 5.0.1
PS: I will try and post some photos to help when I get the chance to get to my car.
I've been start for a solution to this since the phone came out as well. I have the same Bluetooth issues with my phone in my car. Nothing more annoying than having to turn Bluetooth on and off for 10-15 minutes of your drive before you can use the damn thing. Oh wait, more annoying would be when it's been working for a solid 45 minutes or so and then suddenly, with no warning, the Bluetooth connection ends for no reason and your cars stereo comes on instead of what you were streaming only the volume on the cars radio is far louder and it scares the ever living crap out of you
flyhighx said:
I've been start for a solution to this since the phone came out as well. I have the same Bluetooth issues with my phone in my car. Nothing more annoying than having to turn Bluetooth on and off for 10-15 minutes of your drive before you can use the damn thing. Oh wait, more annoying would be when it's been working for a solid 45 minutes or so and then suddenly, with no warning, the Bluetooth connection ends for no reason and your cars stereo comes on instead of what you were streaming only the volume on the cars radio is far louder and it scares the ever living crap out of you
Click to expand...
Click to collapse
Odd....I dont seem to have that issue. Once I have initially paired the bluetooth it will stay connected without any interruptions. Also pairing for me is really fast and only takes a minute or so. My problem is that instead of my phone remembering the current device settings that it is paired with, it will forget to associate it with calls and data after I turn the bluetooth off and then later back on even though the phone will still remember it is paired with the car bluetooth.
First world problems I know but it gets a tad annoying having to unpair and repair my phone each and everytime I hop in my car to go somewhere if I want to listen to my music.
In the car I don't get a lot of skipping. But when connected to my BT speakers audio does skip a lot and starts playing in ffw then disconnects completely. It's driving me nuts. I've tried all the usual trouble shooting also. No help. Wtf Samsung/Google
I just bought a z2 about a week ago. Been a great phone so far. It updated to Oreo as soon as I turned it on.
There is one issue. Bluetooth. When I originally connected it to my Alpine cd-hd148bt, it would stream music, but the phone profiles would not load. So I updated the bt firmware on the headunit. Now if I restart the headunit, it will connect with all the appropriate icons for audio and phone. If I start an audio app, it says playing, the head says playing, but there is no sound. After a couple of minutes, the entire phone will disconnect from the deck. It won't come back until I pull the faceplate and reboot the headunit. Even turning off the car and powering off won't get the bt to work.
Does anyone have any ideas? I love listening to Pandora, and my city has a hand free law, so I would love to have the phone working also.
PLEASE HELP!! I will owe you a cookie.
Thanks
Edit: unlocked bootloader and magisk 15.2.
im also having issues with bluetooth, since headset will disconnect from time to time and while streaming music to a bluetooth speakers (bose, harman, jbl, chinese, etc) audio will cut from time to time, until bluetooth connection drops an will have to restart phone in order to connect again
I am also having Bluetooth issues, keeps disconnecting from my headphones, or connects and doesn't stream. Supposedly with Oreo Bluetooth had been updated to version 5.
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?
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.