Hi all
I run Ambasadii nougat Rom (V.9) on my S7 G935F.
I have a (new) problem in my car : Phone pairs but won't let me stream any audio media. Calls work.
It used to work (!) but now streaming medias only works on other portable devices (like JBL Go)
Guess it's a car (French Renault Captur with R-Link system) problem with the recent Bluetooth norm, is it possible?
Any other possibilities?
Thanks in advance.
The software in your car is not compatible with nougat.
You will need to wait until your car device has a software update to use nougat in your car.
Cosmic Blue said:
The software in your car is not compatible with nougat.
You will need to wait until your car device has a software update to use nougat in your car.
Click to expand...
Click to collapse
I think you may be right, but it worked before, on previous versions of the rom, already on Nougat...
Previous versions were beta and not completely nougat in all respects.
I believe your updated rom is based on the office nougat base which has reported problems with wifi on certain devices.
Cosmic Blue said:
Previous versions were beta and not completely nougat in all respects.
I believe your updated rom is based on the office nougat base which has reported problems with wifi on certain devices.
Click to expand...
Click to collapse
Sent from my SM-G935F using Tapatalk
Related
For those anxious to get 4.4.4 you might try liquidsmooth which now incorporates it and runs on most if not all moto-x's. It's been upgraded to 4.4.4. Unfortunately, bluetooth is still not working correctly for me and if I try to pair the phone with my car, the car's system goes into a slow endless loop where the phone is connected and then disconnected. I am going to try to see if there is some way to get the phone working with my car....it's very frustrating because the moto-x has never connected correctly (galaxy nexus was flawless in this regard).
I am guessing that it isn't built on the 444 kernel, so, don't get too discouraged yet
Sent from my Nexus 7 using Tapatalk
ghstudio said:
For those anxious to get 4.4.4 you might try liquidsmooth which now incorporates it and runs on most if not all moto-x's. It's been upgraded to 4.4.4. Unfortunately, bluetooth is still not working correctly for me and if I try to pair the phone with my car, the car's system goes into a slow endless loop where the phone is connected and then disconnected. I am going to try to see if there is some way to get the phone working with my car....it's very frustrating because the moto-x has never connected correctly (galaxy nexus was flawless in this regard).
Click to expand...
Click to collapse
What year make and model do you have? I have a 2011 Ford Edge and 2011 Ford Fusion, both of which use Ford Sync (Suck), and I have no issues with either.
Also, are you stock, or running a custom ROM? You seem to be running a custom ROM, and in that case, all bets are off.
jaykresge said:
What year make and model do you have? I have a 2011 Ford Edge and 2011 Ford Fusion, both of which use Ford Sync (Suck), and I have no issues with either.
Also, are you stock, or running a custom ROM? You seem to be running a custom ROM, and in that case, all bets are off.
Click to expand...
Click to collapse
It is 4.4.4 kernel. I think I've found the issue and it's unique to "techies". I have a pebble smart watch which uses google...the connection to the car system (2014 MB) uses bluetooth. If I don't wear my watch, the connection to the car works...no loops/etc. When I wear the watch in the car, the car/phone link goes all screwy. I suspect that one of the bluetooth stacks doesn't like to share....and I'd bet it's the moto-x stack which can either use the bluetooth or the car link, but not manage both together, even though everything is paired correctly. I haven't checked to see if pebble and the MB use the same protocols...it may be that they both share txt even though I only need phone on the car link.
I'll post more when I get further into this....I just stumbled on the cause today when I didn't wear the watch and repaired the phone with the 4.4.4 kernel.
Next time, get a Cadillac.
FORD -Fix Or Repair Daily
abuttino said:
Next time, get a Cadillac.
FORD -Fix Or Repair Daily
Click to expand...
Click to collapse
I've heard them all, but we've had precisely zero issues with the Fusion, and one with the Edge that was fixed free of charge due to silent recall.
My only issue with Sync is that my Fusion has the Gen 1 version, and the most recent software update removed the key reason I chose this car over the then comparable Sonata. Without that feature, I would have gone with the Sonata.
I've read around, and multiple people are having this issue, without any real solution. Does anyone know of a rom with which bluetooth is stable (or do I have a hardware issue?)
When Bluetooth is connected to any handsfree car system , it cuts out for a few seconds before reconnecting. For example, If I am in a call, it will revert to the built in earpiece & disconnect from the car , only to reconnect seconds later. Same of Bluetooth audio (a2dp). It's fairly disjointed.
I've tried both stock android 4.4.4 & the lastest Cyanogenmod snapshot & nightlies.
Thanks for any help, and I will post back if I find anything useful.
Never happened to me, I've connected with jawbone FM music transmitter, and with several other Bluetooth peripherals including headphones, my smartwatch, and a mono headset and not experienced this. Maybe its a problem with the specific car your trying to connect to? My BMW 750li doesn't pair with the nexus 4, and even a bb z10
Edit: if multiple people are reporting this and multiple hands free car systems don't work then maybe is a hardware issue? Which revision nexus you have ?
Blazing angel said:
I've read around, and multiple people are having this issue, without any real solution. Does anyone know of a rom with which bluetooth is stable (or do I have a hardware issue?)
When Bluetooth is connected to any handsfree car system , it cuts out for a few seconds before reconnecting. For example, If I am in a call, it will revert to the built in earpiece & disconnect from the car , only to reconnect seconds later. Same of Bluetooth audio (a2dp). It's fairly disjointed.
I've tried both stock android 4.4.4 & the lastest Cyanogenmod snapshot & nightlies.
Thanks for any help, and I will post back if I find anything useful.
Click to expand...
Click to collapse
I suspect people are experiencing different issues, since no 2 cases appear to be the same. As for me, I have a 2008 Audi with integrated BT which worked fine with Gingerbread. 4.+ has been very different: the connection would often be lost and regained mid-trip and worst of all, 9 times out of 10 I couldn't initiate or terminate calls from the car. That last point is a deal-breaker for me...
Some early KK builds were fine, in fact I used Purity till March. Then a new build came along which returned the above issues. Since then I have tried virtually all the popular ROMs (I would create a Nandroid backup and reflash after a day or so - I still try new builds), and at least for me the AOSP ROMs all have the same issue, above.
I am currently using AICP ROM which is AOKP, nightlies are installed OTA and I don't have a single issue with the car BT any more. And it's a very stable ROM, I´ve been using the ROM for about 4 months I think.
Your mileage may vary, since I suspect we all have different issues, but the AOKP branch works for me. Dirty Unicorns works fo rme too.
BassBlaster said:
Never happened to me, I've connected with jawbone FM music transmitter, and with several other Bluetooth peripherals including headphones, my smartwatch, and a mono headset and not experienced this. Maybe its a problem with the specific car your trying to connect to? My BMW 750li doesn't pair with the nexus 4, and even a bb z10
Edit: if multiple people are reporting this and multiple hands free car systems don't work then maybe is a hardware issue? Which revision nexus you have ?
Click to expand...
Click to collapse
It is a rev_11
paul c said:
I suspect people are experiencing different issues, since no 2 cases appear to be the same. As for me, I have a 2008 Audi with integrated BT which worked fine with Gingerbread. 4.+ has been very different: the connection would often be lost and regained mid-trip and worst of all, 9 times out of 10 I couldn't initiate or terminate calls from the car. That last point is a deal-breaker for me...
Some early KK builds were fine, in fact I used Purity till March. Then a new build came along which returned the above issues. Since then I have tried virtually all the popular ROMs (I would create a Nandroid backup and reflash after a day or so - I still try new builds), and at least for me the AOSP ROMs all have the same issue, above.
I am currently using AICP ROM which is AOKP, nightlies are installed OTA and I don't have a single issue with the car BT any more. And it's a very stable ROM, I´ve been using the ROM for about 4 months I think.
Your mileage may vary, since I suspect we all have different issues, but the AOKP branch works for me. Dirty Unicorns works fo rme too.
Click to expand...
Click to collapse
Thanks for the responses. The cars work perfectly fine with galaxy phones & iphones, the issues lies with my nexus sadly. I will try the posted roms later on and update!
Also Paul, can you post a link to the rom you have installed? I've been out of the loop for a while and cannot find it !
Mine is also a rev11, 303k. I guess that rules out hardware issue
Blazing angel said:
It is a rev_11
Thanks for the responses. The cars work perfectly fine with galaxy phones & iphones, the issues lies with my nexus sadly. I will try the posted roms later on and update!
Also Paul, can you post a link to the rom you have installed? I've been out of the loop for a while and cannot find it !
Click to expand...
Click to collapse
Here you go: http://forum.xda-developers.com/nexus-4/orig-development/rom-aicp-3-5-kk-4-4-2r2-mako-t2632777 - enjoy!
This is the official download page, where you can get the gapps package you prefer, plus the release/latest nightly.
If you install the release you won't get the nightly updates. The nightlies are very stable, so I'd recommend the latest nightly.
I'm experiencing exactly the same problems than Blazing angel.
Bluetooth is unusable in my car, "Unfortunately, the process com.android.bluetooth has stopped" being displayed repetitively.
I suspect it's not hardware related as I do not have problem using the stock or paranoid ROMs. Unfortunately, my favorite ROMs (AOKP, CN or Carbon) are causing problems.
Do you think it's possible to pickeup some files in the paranoid files and inject them to Carbon to solve the problem ?
Thanks in advance for your help !
paul c said:
Here you go: http://forum.xda-developers.com/nexus-4/orig-development/rom-aicp-3-5-kk-4-4-2r2-mako-t2632777 - enjoy!
This is the official download page, where you can get the gapps package you prefer, plus the release/latest nightly.
If you install the release you won't get the nightly updates. The nightlies are very stable, so I'd recommend the latest nightly.
Click to expand...
Click to collapse
Great ! I was able to bypass my bluetooth problem using this Android 4.4.4 rom, without loosing great features of Carbon or Pac-ROM ! :victory:
Thanks for sharing this ROM Paul ! :good:
Hello,
I recently flashed from ITV MM to UK Nougat, beside Samsung Pass not working, notifications badges not showing on some apps, now I have found that I can't pair anything via bluetooth.
I have tried to pair my gear iconx, my monster elements over-ear and my monster elements on-ear headphones and I can't even find them in the available devices list.
My girlfriend's S7 Edge pairs with all the above bluetooth headphones with any problems.
Anyone else has this issue?
Can anyone help?
Thanks
blackfire2802 said:
Hello,
I recently flashed from ITV MM to UK Nougat, beside Samsung Pass not working, notifications badges not showing on some apps, now I have found that I can't pair anything via bluetooth.
I have tried to pair may gear iconx, my monster elements over-ear and on-ear headphones and I can't even find them in the available devices list.
My girlfriend's S7 Edge pairs with all the above bluetooth headphones with any problems.
Anyone else has this issue?
Can anyone help?
Thanks
Click to expand...
Click to collapse
Try a factory reset coz I am able to connect to Bluetooth devices just fine.
already did that yesterday
I have a problem with bluetooth doesn't work nought !!!
MonzerDroid2 said:
I have a problem with bluetooth doesn't work nought !!!
Click to expand...
Click to collapse
IMHO we should build a great wall and just make people like him pay it... :cyclops:
Your problem isn't Nougat's Bluetooth dude.
Nought
riklaren said:
IMHO we should build a great wall and just make people like him pay it... :cyclops:
Your problem isn't Nougat's Bluetooth dude.
Click to expand...
Click to collapse
Made my day ... THX
Hi,
After updating to oreo (clean flash) i have issues connecting to my car bluetooth (vw tiguan). it keeps disconnecting every 5 sec. randomly (very rare) it works without pb.
i tried changing bluetooth codec (sbc, aptx, aptxhd), or avrcp version (1.4, 1.5, 1.6) the pb still remains
any help? suggestion? or a way to post logs?
With Nougat it never happened
Thanks
Similar issue here. I have a fully clean flash of OOS5.0 (because I douched my storage the first time) and bluetooth seems fine sometimes, and other times it's totally borked. I listened to 2 hours of podcasts without issue, then it just constantly disconnected/reconnected. I tried rebooting, unpairing, changing codecs...same issue. Next day, it's totally fine again.
My seat Leon my 16 discover pro does mostly not connected automatically on Oreo.
Tried cleanflash of oreo, no change.
Back to 7.1.1 everything fine.
My case is similar but slightly different. My car is an old one (Seat leon from 2005) which Bluetooth connection is used only for phone calls. This seems to be working fine.
However I'm using an add-on to connect multimedia through Bluetooth to the radio, and this add-on is not working fine with my Oreo OP5.
So I guess the problem for the other reported issues should be related to the multimedia connection instead of the phone one.
Absolutely
Phone calls are working fine
On my VW Golf VII not connected automatically on Oreo. Works fine before. Clean Install... don´t help.
I must switch BT off and on and then connect to my car.
Oneplus 5 is my first Oneplus. And from beginn problems with BT. After some updates works fine. Now the same after Oreo.
Same here with parrot handsfree. Nougat was OK....
Same here with 2017 Audi A4. Bluetooth do not connect automatically.
Works fine with nougat before.
I use the app 'Bluetooth auto connect' to force OP5 to connect to Audi, when I turn on the screen. (little work around).
The OP3T from my wife (also with oreo) connect fine to my audi.
Gesendet von meinem ONEPLUS A5000 mit Tapatalk
I have switched off 'media audio' in Bluetooth Settings of OP5 and Bluetooth connect without any problem with my Audi. (tested it two times)
Will continue testing.....
Gesendet von meinem ONEPLUS A5000 mit Tapatalk
Switch of Car for <10 minutes and try and also only off for 10 seconds
I also thought this helps, next day not working....
For the last few days it has been working fine in my car (2016 BMW 340i), but in my wife's car (2015 BMW 328i) with the same media interface, it actually CRASHES the entire car's system and iDrive does a full reboot. Never seen that before with any device.
Anyone tried open beta 3 ?
My OP5 connects to the Anker SoundSync handsfree, calls and media are OK just as before, the only thing that have gone with the stable official Oreo update are the bluetooth control buttons.
Any idea would be appreciated
Uselessjunk said:
My OP5 connects to the Anker SoundSync handsfree, calls and media are OK just as before, the only thing that have gone with the stable official Oreo update are the bluetooth control buttons.
Any idea would be appreciated
Click to expand...
Click to collapse
I think it's related to avrcp
Try changing the version in the developer options
acentoo said:
I think it's related to avrcp
Try changing the version in the developer options
Click to expand...
Click to collapse
i will try. thank you!
I found a way to get bluetooth working on oreo.
Get a nandroid backup from your modem of Nougat and Oreo
Copy the Bluetooth file from Nougat to the backup from Oreo
Restore Oreo Backup
Thats all.
Attached the Nougat Bluetooth
acentoo said:
I think it's related to avrcp
Try changing the version in the developer options
Click to expand...
Click to collapse
I've just found this: https://forums.oneplus.net/threads/bluetooth-controls-issues-after-upgrading-to-oreo.695551/
Yup something is mess up with oreo i too upgraded to latest oreo so many bug and couldn't connect to any of my Bluetooth speakers i had to downgrade to nougat and now everything is fine guess i will wait a few months before upgrading to oreo this time way to go oneplus ..
Same bluetooth issues here with my 17 ram
henno88 said:
I found a way to get bluetooth working on oreo.
Get a nandroid backup from your modem of Nougat and Oreo
Copy the Bluetooth file from Nougat to the backup from Oreo
Restore Oreo Backup
Thats all.
Attached the Nougat Bluetooth
Click to expand...
Click to collapse
file is not working
Original file is bluetooth.emmc.win your is .rar but cannot be unziped
Hi guys hoping someone can help. I have an issue with my S10+ and bluetooth car kit, after the last update my phone keeps connecting and disconnecting my hands free kit, now an old 8.1 oreo phone is fine and my wife ios XS device with the latest software works it seems 9.1 pie doesn't want to play with Uconnect
fouros said:
Hi guys hoping someone can help. I have an issue with my S10+ and bluetooth car kit, after the last update my phone keeps connecting and disconnecting my hands free kit, now an old 8.1 oreo phone is fine and my wife ios XS device with the latest software works it seems 9.1 pie doesn't want to play with Uconnect
Click to expand...
Click to collapse
I have the same issue
Been forced to listen to the radio
Mate if you have a Chrysler Jeep or Dodge go to driveuconnect.com (on PC or mac not mobile device) I entered my VIN was able to find a firmware update, now all working again with no dropouts