Database Develop

Bluetooth pairing issue Sennheiser MM400

When I last used these phones I was on enom's 1.9.2 rom and they worked jusr fine. Its been a couple of week, and I'm now on the Stock (rooted) FRF91 ROM
I can't get the headphones to pair. Is there some new magic I need to do? Phone pairs with car bluetooth OK (a bit crap quality??) and it pairs with some cheap & cheerful old bluetooth headset I have - but not with the Sennheisers. I rebooted the phone, and the headphones (taken the battery out!) - still no joy.
Is there some bluetooth version mismatch between froyo and the sennheisres? (I don't know what bluetooth version they use)
Any ideas.
Graham

Bluetooth nexus one connecting to Renault carkit

I recently got my new Renault Scenic car and discovered a rather strange situation.
The phone pairs with the carkit and connects the first time without issues and works like a charm.
But however when I start the car and thus also the carkit the phone connects also but no audio is heared trough the carkit when calling or getting called. The phone says it transfers the connection to the carkit but nothing is heared.
It only works when I have bluetooth off, starts the car and then turning bluetooth on the phone on. Wait till it connects and make a call. With this procedure the connection is good till I step out the car.
Its a work around but hmmm not the one i would love to.
I have a nexus one rooted with the latest MCR (21) and an intersect kernel. Though I tried different kernels also but no go.
Hopefully one of you guys have an idea

Ok I searched a bit and found out the Bluetooth is done with the opensource code Bluez. So I wonder which version of Bluez is in the froyo roms and how it can be updated if possible to a new version.
Anyone knows ?

I feel your pain, I have a Renault Grand Scenic III (purchased last December) and the hands-free is unreliable, but music streaming (A2DP) is even worse as most often than not it will fail to connect.
I have to say that the hands-free works fine most of the times (for the phone part, not for music), but some days it will refuse to work no matter what. Since it isn't working much better with my wife's Nokia (BTW, which I had to do a firmware update or else it went into a permanent reboot loop when connected to the car-kit), I assume the problem lies on the car, not on the phone. I have yet to see if my Hero, which has been recently updated to Android 2.1, behaves any better. A firmware update on the Bluetooth car-kit seems a better approach, but I'm unaware if one exists since after some digging it seems my car doesn't use the OEM Parrot kit that other earlier models carried.

igalan said:
I feel your pain, I have a Renault Grand Scenic III (purchased last December) and the hands-free is unreliable, but music streaming (A2DP) is even worse as most often than not it will fail to connect.
I have to say that the hands-free works fine most of the times (for the phone part, not for music), but some days it will refuse to work no matter what. Since it isn't working much better with my wife's Nokia (BTW, which I had to do a firmware update or else it went into a permanent reboot loop when connected to the car-kit), I assume the problem lies on the car, not on the phone. I have yet to see if my Hero, which has been recently updated to Android 2.1, behaves any better. A firmware update on the Bluetooth car-kit seems a better approach, but I'm unaware if one exists since after some digging it seems my car doesn't use the OEM Parrot kit that other earlier models carried.
Click to expand...
Click to collapse
Hi,
I've just come across your post. Did the situation improve ?
I'd just point out that for me it comes from the Android system : I own a Renault Mégane 3 and was able to fully use the bluetooth system with my HTC HD2 (Windows Mobile 6.5). Now, I've just installed Android 2.2 on it and I encounter a similar behavior... and the car can't connect to the phone directory either...
Looks like I'll boot back on Windows Mobile when driving...
Regards,
Stéphane

My Hero with the official 2.1 ROM is now 100% reliable. The Nexus One with Froyo isn't, A2DP is still hit & miss.

Well... I'm getting the same but not with Renault ones.
I have LiquidAUX on my car and to have both phone and a2dp synced, I have to restart phone BT and LiquidAUX every time I go into car. And most of the times I can only have 1 connection each time, or phone is on and a2dp is off or a2dp is on and phone is off. It's really annoying since I had an HTC Hero with Android 2.2 and it used to work with no problems...

Hello, I've the same issue with my new Renault and Nexus LG. The phone pairs with the carkit and connects the first time without issues and works like fine. Once someone calls, the connection is terrible or lost! I checked the phone compatibility list at Reanoult and the NEXUS LG is on that list. So it should work. Updated R-link2, same issue. I went to the Renault garage and they told me that this is a bug in the Renault software, they can't do anything about it. Can't believe this, there should be a solution or fix.

[Q] BlackBerry Remote Stereo Bluetooth Gateway

I'm having an issue with this otherwise excellent bluetooth sink. My Note pairs seamlessly with it and it connects to it without issue if done so manually (from the Note's bluetooth settings you select to connect the phone to the bluetooth device). The issue is my Note won't automatically connect to the bluetooth device when it is within range. If I bring the phone within range while I'm looking at the bluetooth settings on the phone I can see the phone try to connect to the device, but it is not successful. It connects automatically with no issues when I am on CM9. I suspect it's a bluetooth driver issue.
My ROM: Cleanote v6
My Kernel: Hydracore v4
Amazon link to the bluetooth device in question:
http://www.amazon.com/BlackBerry-Remote-Stereo-Bluetooth-Gateway/dp/B00170KUM0
Is anyone else using this bluetooth sink? If so, do you have the same issue?
Thanks!

Hooray! I've finally figured out the problem. The issue is with the kernel. I went back to ICS 4.0.3 (specifically LPY) with a kernel 3.0.15 that was built in May 2012 and the problem went away. All of the other ROMs I had used that had this problem was 4.0.4 with kernel 3.0.15 that was built around August or September (I forget which one). CM9 was probably built from this kernel since CM9 doesn't have this problem. Now I get to experience SMemo and SNote AND have fully working bluetooth. Hopefully Samsung won't release JellyBean with a bluetooth problem.

[BLUETOOTH] Help! Bluetooth is severely buggy!

Okay, so first things first:
My device is running OOS 3.5.4 and is rooted.
The issue I'm facing is that when I connect my 3T to my car (Hyundai Verna 2016 if it's necessary) via Bluetooth, the phone starts spazzing out and lagging like crazy until I switch off the Bluetooth. Also, when I try to play music from Spotify, it plays but no audio is heard from the car's system. I am 100% sure it's not my car's fault because my other phone (Asus Zenfone 5) connected just fine and played music from Spotify with ease. I'm extremely clueless as in what could cause this issue. Can my fellow XDA buddies help me out on this one? Any help is greatly appreciated!

Comment to resurface this post.

why aren't you running the latest version of oxygen os? 4.1.3?

You say you are using OxygenOS 3.5.4 and you are rooted. This makes me believe you are doing it because 6.0 is more "mod friendly", and you are probably using Xposed and/or Viper.
VIPER4ANDROID is known to cause the exact same behavior that you mentioned. Probably easiest to flash a custom ROM with it already built in like Freedom OS or Audax.

Update your ROM
You need to be running an updated version of OOS. There have been many fixes and improvements to Bluetooth connection and reliability and I haven't had any of the issues you describe. Below is the list of Bluetooth connections I make on a weekly basis and I haven't had any problems running OOS 4.1.1 and 4.1.3:
1. VW car stereo (phone and audio streaming)
2. Nissan car stereo (phone only)
3. Panasonic home phone system
4. Plantronics Voyager Bluetooth headset
5. Dell laptop computer (data transfer)
6. Sony portable speaker

Bluetooth and music track "remaining time"

XZ1 Compact (Android 8.0) in Bluetooth connection with 2017 Subaru Forester
All apps that play audio tracks show elapsed time, but remaining time is shown as -0:00.
Tried all sorts of permutations through the Developer Options, but none seemed to make a difference.
All previous Android phones, same setup, running Android 6.x through 7.x, don't have this problem.
Is this a known bug?
Thanks

I have the same issue with my phone (not the same car, just bluetooth media info not working on any device), and I think it has something to do with android 8.0, because google's Pixel also has this problem when updated to 8.0

yeah, not working great on my Hyundai i40 (with Navi unit) (dont see any song names or song duration & intermittent working of FF and Rev)
I changed the version of BT to 1.4 in the developer settings and it helped a bit

billbond4 said:
yeah, not working great on my Hyundai i40 (with Navi unit) (dont see any song names or song duration & intermittent working of FF and Rev)
I changed the version of BT to 1.4 in the developer settings and it helped a bit
Click to expand...
Click to collapse
The SPP Bluetooth profile doesn't seem to be supported in Android 8.0 running on the XZ1, XZ1C (and apparently the Pixel?).
The others, HFP,OPP,PBAP,AZDP,AVRCP,MAP are all present, according to my external BT devices.
Then again, this may have nothing to do with the BT bug we're discussing here.

Got the new update this morning and still Bluetooth bug, that SPP profile doesnt have anything to do with the music, but its good to know.

One appreciated improvement in the most recent (...12.34) firmware is that the long-standing Bluetooth bug, where connected BT devices do not show the remaining playing time of a media file, is fixed.