Hello,
I own a Hyundai I35 2014,
I have the phone connected via Bluetooth, and i can make and receive calls just fine, all is loud and clear.
But it will not play Music (not from YouTube, not from google Music) when i hit AD2P
I checked some forums and other sites, i tried unpairing, i tried force stop and remove data and clear cache, i tried to do almost anything - nothing worked.
i also do not have the "Media Audio" option under options in Bluetooth device properties (when you click the round icon next to the car device name) - but also ,
My brother has LG G3 (android 5.0) and he is ABLE to play music just fine - He also do not have the "Media Audio" option in bluetooth device properties.
Both phones properties look the same, but only the LG G3 is playing music once AD2P is chosen in the Car.
any help would be much appreciated.
thanks !
Sounds like a vehicle issue - most phones will not stream audio to a device which doesn't present it with the A2DP profile. Maybe you need to master reset your car's stereo or check with the dealership for a stereo FW update.
Ford just recently released an updated firmware for Sync and now I get mp3 metadata on the display and it auto-reconnects to BT after shutting the truck off.
I`v actually done that, but how can i blame the car when my brother's LG G3 works great with it, and my Wife's iPhone 6Plus works great as well ?
Just from a quick Google search it seems the bluetooth in that car (I'm gonna assume you have a Hyundai ix35, since no "i35" exists) is flaky and problematic.
I would call the dealer and ask if there's a system update to fix BT issues.
I've had an ongoing issue with my Pioneer head unit where it will stop working with Media Playback and continue to connect for call audio. Each time it does this I have to clear the Bluetooth memory on my Pioneer unit. Perhaps your Hyundai has a similar option? They you can repair the device and it should work.
Edit: I should add that this was never an issue with my previous 2 phones (a Samsung Captivate and Nexus 4).
I have just got my P20 Pro, it seems like a great phone so far, but I have one nagging issue.
When I connect my phone to my car's (2015 BMW 3 Series) Bluetooth the now playing metadata of the audio being played is not being passed correctly. So if I play audio from Google Play Music or Pocketcasts the head unit on my car will show either Unknown Track or the track data of the first item on the album or the playlist. The audio itself sounds fine and I am able to skip tracks, select new albums from the car's controls, so it seems some information is being passed correctly, it is just that the info of the track that is currently playing seems to not be working.
Has anyone else encountered this?
At this point I have to assume it is the phone, as my Galaxy S6, S7 & S8's all worked, but I guess it is technically possible that could have been a workaround put in by BMW as they were such popular phones. Hopefully Huawei will sort this out, it may be an underlying Oreo issue as threads like this suggest that Bluetooth issues were around when 8.0 launched https://productforums.google.com/forum/#!topic/nexus/E9Q2lyFYRgI
I have done some more digging on this issue and I suspect that is might be something to do with the Bluetooth AVRCP version that the phone is using. Normally in Android (since 8.0) you could adjust the AVRCP version from within Developer Options, but for some reason this is not available on this phone. My Galaxy S8 was using AVRCP 1.4, so I suspect that this phone is using 1.5 or 1.6 and my car does not like it.
I have emailed Huawei to ask for clarification. At this point it is the only real issue I have with the phone, but it will annoy me if it isn't resolved quickly. I'm going to pester BMW too to see what versions of AVRCP they officially support.
Don't have these issues in the car, head display current track etc via Bluetooth ... Use this in a Nissan
Everything works as it should with my Pioneer headunit using Spotify
I just posted something related (possibly) in the RAM/Battery Management thread - I have issues with the Audi MMI Connect app, losing connectivity and so on.....does seem that the P20 Pro handles Bluetooth (no rsap?) and background process management quite differently to my previous phone (Galaxy S8+)....also hoping quick resolution, as love the phone!
Search facility not working in car
Hi
I've just put music onto my P20 pro and it plays fine on the device and the car, however, I can't use the search facility on the car (BMW, 3 series, 2017) to change track. I can do this on the phone. Any suggestions? I put the music onto the 'Music' app (dragged and dropped from my iTunes folder- don't know if this is relevant. Any help would be greatly appreciated as without being able to use the car's search facility and come in and out of albums/ artists is useless. Should I have put the music into somewhere else?
JQ
P20 PRO and BMW - bluetooth issue
Bojanglez, did you find a solution? I got the same issue with P20 PRO and BMW X4... so it seems a problem linked to that phone connected to the BMW multimedia system.
With my previous phone, an ASUS Zenfone, everything was fine.
It may be a BMW issue to, maby P20 pro isn't compatible with BMW or Audi. I know that some manufacturers put all in to be compatible with ios and some larger manufacturers of phones. It could be that car manufacturers don't test Huawei phones and don't support them.
Skickat från min CLT-L29 via Tapatalk
No Huawei Garbage bloatware issue, my is random something is normal, most times it plays music but gets stuck on providing music playing info.
Same issue here with my 2016 Toyota rav4. It plays the first track and shows the metadata but then as the tracks keep playing the metada remains the one of the first song. Definitely an issue with Huawei. Their music player works just fine. I think it has to do with the poor Google integration and their need to force that half baked apple wanna be emui down our throats. It should be Oreo but looks and feels like gingerbread.
Hi all, I have an update. I have resolved the issue, but not quite sure which of the following specifically fixed it.
Huawei software update
Renamed by phone in Bluetooth settings
Updated to the latest BMW firmware (from their site)
Messed with some of the Bluetooth settings in Developer Options on the phone
Unfortunately I did all these at pretty much the same time so I can't say for certain which one fixed it, I think it was the Huawei software update as after I updated my BMW firmware I still had the same issue and also in other BMWs I tried. I also noticed that the Bluetooth was dropping constantly in my wife's Puegeot 3008 so that's why I played with the Developer Options. For anyone interested I havethe following now set:
Codec: SBC
sample rate: 44.1khz
channel mode: Stereo
LDAC playback quality: 990kbps/909kbps (optimised for connectivity quality)
HWA playback quality: Best effort (400KB Optimised for connectivity)
HWA Latency: 50-100ms
So I now have track information and basic controls using Google Play Music and Pocketcasts. It does not seem to like letting me browse my library though, but it is at least functional.
Also I changed my car, this was not because the BT didn't work It worked in my 2015 3 series before I changed it. I now have a 2018 4 series and the behaviour is the same, track listing and skip functionality but no browsing.
I have installed the most recent firmware update on my 2 Series 2017, I see two fundamental issues. One is, by using your phone normally, no issues should arise most of the time but still random sync issues with metadata can occur. The second issue is, no matter how good your phone behave and how well synchronized the metadata is, once you open Android Auto app, everything goes to hell and you are back in square one.
To fix it, you should deactivate auto start when connected in the app (or not using it at all), erase your car from devices in bluetooth config within your phone. Erase your phone from the list in your car. Change the phone name. Start over with the synching process. Check for correct metadata in the car. If not working repeat. That should fix the problem eventually.
If you like very Android Auto very much, get used to see the songs information in your phone screen rather than the car.
I am also having the same problem, Huawei P20 Pro and Sony XAV-601BT head unit. I've tried enabling all the permissions in Spotify, cycling the connections, renaming the phone.
i have Pixel 3xl with Android 10, - Bluetooth connects fine there is no metadata - song info. this problem started with 8.1 Android version and I have not been able to get it to work. I really cant believe google cant fix this issue or even aware of it. plenty of threads on google. I think they all use Iphone, i am guessing ...this is very annoying. I have change the avrcp version from 1.4 to 1.6. no luck, also I read that turn off battery optimization on Bluetooth. no luck. anyone else here having similar issue??
This is a long shot.
I have a pair of Bluetooth 4.1 Minirig speakers that can be set in stereo mode. However when in stereo mode one channel experiences dropouts. Running in mono mode is fine.
The issue is with the Nokia 7+'s Bluetooth transmission as when using other Bluetooth enabled devices to power the speakers the issue does not occur.
Anyone else had this issue when connecting stereo speakers or headphones and know of a solution?
I have checked: System > Developer Options > Bluetooth Audio Codecs and tried changing these setting but the changes did not "stick" and problem remained.
Maybe there is an alternative setting somewhere that can be tweaked.
Thanks in advance.
doowoppa65 said:
I have checked: System > Developer Options > Bluetooth Audio Codecs and tried changing these setting but the changes did not "stick" and problem remained.
.
Click to expand...
Click to collapse
I'm also having this issue: whenever I'm connecting my N7+ onto the car's audio system via Bluetooth I have to change the codecs to the correct one every single time to make it properly work (have sound/audio at all). The settings also don't stick or are not being saved. Also looking for a solution for this, unless an update miraculously fixes it.
Same problem here when connected to my car by bluetooth. Occasionally there is a dropout. This does not happen when my friends connect with their phones (oneplus 5, samsung, allview. or my old lg g4).
Changing the bluetooth audio codecs does not work as it does not remain selected and it switches to default. This, as i understood, happens on android 8 and has been resolved in the Pie beta and should be ok in the final Pie release.
When I raised the issue with the superbly talented nokia tech support they either act surprised as if its an unique issue to you or send you a list of compatible bluetooth protocols. Are we expected to change our cars and speakers to make the phone work?
I had this issue after installing garmin connect. Theres a thread over in the garmin forums (forums.garmin.com/forum/into-sports/garmin-connect-mobile-application/garmin-connect-mobile-android/1375800-audio-streaming-issues) about it. Also on the nokia forums (community.phones.nokia.com/support/discussions/topics/7000022239/). Seems to affect some phones on 8.1
Anyway, I'm on Pie beta now and the problem has gone away.
Was wondering if anyone else had this issue, in my Audi using Bluetooth the music will play but I can't skip tracks using my card controls until I skip tracks manually on my phone,only after that can I change using my cars controls, ive been using Samsung since s5 and never had this issue, any ideas?
Shuthefrontdoor said:
Was wondering if anyone else had this issue, in my Audi using Bluetooth the music will play but I can't skip tracks using my card controls until I skip tracks manually on my phone,only after that can I change using my car's controls, I've been using Samsung since s5 and never had this issue, any ideas?
Click to expand...
Click to collapse
I have recently experienced that too. I noticed this problem when I updated the Samsung buds to the latest firmware. The first problem I noticed was that when the update finished it disconnected my Galaxy watch and made me reset it. I will do a factory reset on my phone and hopefully, that helps it.
Try to lower the AVRCP version in Developer settings in the Bluetooth section. Worked on my '13 Seat Ibiza with a portable Garmin system. After set it to 1.3, turn bluetooth off and on again.
If the AVRCP, which is set to 1.4 by factory, is too high, the music playback works mostly, but things like music controls and title information not.
I set it to 1.3 and it works for me now. I don't know if new devices are backward compatible, especially the Galaxy Buds.
Btw, I had similar issues with my old Huawei P10 on Android 8.0 (EMUI8). Google didn't implement the option to change the AVRCP version so I couldn't use my phone on the cars at work or rental cars - mostly VW and Mercedes.
I thought it was a hardware issue, but then I installed a 8.1 rom, where this option was enabled and from then it worked.
And with my iPhone 6S worked everything great 3 years ago under iOS9. 3 weeks ago I needed to use it again, updated to iOS 12 and it didn't work at all with my cars system. In iOS you don't have the ability to change the AVRCP version, so I guess Apple wants you to buy a new car, as Huawei does with EMUI8.
My Xperia XZ1 Compact has a strange problem: Both of my BT devices (Jabra Evolve 65, Denon Envaya Mini) work well with my phone if I answer phone calls. But playing audio files does not work. I tried two audio players (Mort Player and the lineageos music app) and played a MP3 file from Youtube. On another phone both devices play music perfectly. So it is obvious that my devices are not the problem. It is definitively the phone.
In the bluetooth settings of both devices, media is on. I also tried to deactivate phone call in the settings but it did not help.
I tried to change the protocol version to 1.4, I deleted the bluetooth cache and resetted the bluetooth settings.
Please have a look at my Logcat attached. What I basically did while it ran is: Click the volume button, select the bluetooth symbol and changed from one device to the other.
I can't tell you which firmware I have. I did not find any information about it.
It seems like in 18.1 this has been fixed. But is there a quick way fixing the problem without upgrading to 18.1/2.0? Perhaps by changing a few values somewhere?