So up until I did the original 5.0 OTA update, I have metadata on my Civic 2012 coupes display. After the update, no information is displayed. I've heard there's an issue with bluetooth backwards compatibility in vehicles, but since it's just a software update that caused this, and not a hardware update, is there any way to fix this?
Related
Hi. I have a Nexus 5x with the latset Android O preview image.
Since I started to test this preview I have noticed that there is a problem with audio to my Kenwood car audio.
With Android 7.1.2 there was no problem. When i start my car the phone connects to the car audio via bluetooth and when I try for exempel Spotify there will come sound with no problem.
Now, when I try this with android O there will come no audio. The only fix for this is if I open up developer-settings and change soundcodec for bluetooth to SBC. Then the there will be sound from the car audio.
Ok, so now I have the fix for the problem. But this is only temporary. Everytime I leave the car and come back I will have to do the same change in the settings.
So, is there a way for me to change this for good? Like change a configfile or similar?
Do anyone know where the info is saved? If so I geuss I could try to change it that way and save the info.
Hope you have understood the problem and that my Swedish SchoolEnglish was understandable...
// Tommy
This is know issue on Android O. Google has already mentioned this in Bugs list or the release.
If you need Bluetooth audio, you should go back to Nougat.
Well. I know it's an known issue. Thats not the question. The question was if anyone knows how to make the settings permanent for the bluetooth audio codec.
//Tommy
I have a similar problem with my Moto 360 Gen 2 running Android wear 2.0
I do the initial setup and everything works great, but if the watch disconnects from the phone because of distance or whatever, it will start prompting for the PIN to re-pair, but it rarely works. I usually have to factory reset the watch, forget the watch in the Android Wear app and start over.
I found a nasty bug with the recent Nougat update for the A7 2017 (SM-A720F): some Bluetooth devices can't pair with the phone anymore. In my case, it was a Polar H10 HRM (BLE); other devices like my car and watch pair just fine. Researching on the topic a bit, it seems it's not something exclusive to Samsung phones: the Android 7.0 version is plagued with Bluetooth issues, which apparently have been solved in version 7.1.1 onwards.
I've tried about every solution and workaround I found: clear cache in recovery; clear Bluetooth data; perform a master reset; and even reflashed the stock Nougat ROM in Odin from scratch. I also tried pairing the HRM with several fitness apps, including Samsung Health. The ONLY thing that worked was downgrading to the stock MM ROM (6.0.1): pairing was instant.
Anybody else had Bluetooth issues with this Nougat update? Any other workarounds I could try? I just hope Samsung is aware of the issue, and release a fix soon.
Yes my Garmin 935 won't pair, tried to downgrade with odin but it failed so I'll try again tomorrow. Phone is frigging useless if I can't use it in conjunction with my watch.
yes me to..with jbl clip2 n level u music sound broken off
Sent from my SM-A720F using Tapatalk
Just rolled back to 6.0 and it paired immediately. A320FL
Hello,
I ave the same problem since I install Nougat, I have to pair everyday my Jabra Sport Pace. Someone have a solution ?
Thanks
Hi
I've purchased a PX5 MTCD based Dasaita 10.2" unit for my Peugeot 208 2016 to get Android auto.
Quite pleased with the design and features overall but had a show stopper when I realised that even if I set the unit to mph in the control settings app the car would flip back over to kph on my speedometer when it started up. This was even though the setting stayed as mph in the control settings app. Indeed I'd have to flip back to khp then back again to mph to rectify.
I tried first of all upgrading to the latest version of my DCU software (2.99MTCE) and updated and tried different ROM's to no avail.
Anyway. I've found a sort of workaround I think which is to disable the canbus app in Android settings. This has stopped the speedo from updating and the steering wheel controls still work. Have I broken anything else though? Does anyone know what force stopping this app does?
Thanks
Dasaita provided me with the fix today. If you PM me, I will send you the file and instructions. Note that you do the update at your own risk.
Fix= new firmware? Android or MCU?
Fix is an update for the canbus. It's not an android firmware nor MCU update.
Hi @jamesbruton, how/where do I turn off the Canbus app?
Following the update happened earlier this morning, the Bluetooth headset/speakers aren't working/no sound is passed through. Are there any solution for this as we had in 5th update of android Q
copstar said:
Following the update happened earlier this morning, the Bluetooth headset/speakers aren't working/no sound is passed through. Are there any solution for this as we had in 5th update of android Q
Click to expand...
Click to collapse
Haven't tried after the update
Try resetting Bluetooth Settings
i had the same problem, but after i turn off the disable bluetooth a2dp hardware offload, the bluetooth headphone worked (again)
Hi guys, hoping you can assist...I've had an Xtrons unit installed in my Audi TT for about a year now. One day as I was driving, I was listening to music from my phone via A2DP. Midway I switched my phone to my bluetooth headphones so I could listen on those in one ear. It seems the phone stayed paired to the head unit but the music was coming through the earpiece fine, no sound off the headunit.
Ever since that day, I've had no sound coming out of the head unit at all. I've done a factory reset, unpaired any bluetooth devices, and just tried listening to radio, but no sound comes out at all. I thought maybe the amp fuse was blown so checked that and it isnt that. I've pulled the unit forward and no cables are loose
I've contacted Xtrons to try and see if there's a new firmware in the hope that will fix it. My current build is shown below.
px5-userdebug 8.0.0 OPR5.170623.007 eng.hct.20181206.171300 test-keys
Has anyone else experienced this? I'm hoping its a software issue and something didnt blow inside the unit itself. Everything else works fine, just no sound
Here you are a complete repository for mtcd units.
Select px5 and android 8 (oreo). Select any manufacturer (all rom are compatible)
Яндекс
Найдётся всё
disk.yandex.ru
Perhaps you need to upgrade your mcu as well.
Check on the repository or on xda forum for your specific manufacturer mcu upgrade