Hello everybody,
I'm experiencing a strange issue with the new bluetooth handsfree system of my car. It's a Viseeo MB-3 that is very popular in Mercedes cars. It has Parrot CK5050+ chipset, so it is pretty standard.
I tried with my other phone, a HTC Desire and works perfectly, the same with an iPhone from a friend, but my Samsung Galaxy refuses to connect.
In this system is the handsfree set which stays visible and you have to connect from the phone. When I try to connect I get a message saying that there was an error when trying to connect to the MB-3.
I was with a custom CM rom (Insanity), so I wiped everything and went to stock 2.3.5 (JVT) but I got same error.
I went to Froyo 2.2.1 (JPY) and it worked perfectly.
Went back to GB 2.3.5 and the error came back.
I tried to put JPY radio over 2.3.5 but it didn't solve the problem.
So, it seems there is some change at certain point with Galaxy GB bluetooth that makes impossible to connect to the handsfree set (I haven't investigated all versions to check in which one the problem started).
The Viseeo MB-3 is totally updated with last FW version.
Any ideas?
Related
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.
Hi guys,
I am having problems with car BlueTooth hands free and Samsung Galaxy S:
With Eclair 2.1 it was working flawlesly, connected automaticlay after paired, I could make phonecals, receive phonecals, no quality issue, phonebook worked fine etc... The only problem was that once I did not swithced the BT on my SGS before starting to drive, for some security reasons the car was not searching for phones while driving, so I had to turn the BT in car off and on again and then it connected well. But overal problem free...
With latest 2.2 Froyo (i9000xfjp7) and also previous Froyo distributions (i tried JPA if I remember correctly), the phone can be paired, it connects to the car but after one phonecall it looses connection and works no more. The strange thing is, the BT icon on the phone shows brackets (like when connected) and also the car shows the phone is still connected. But phonecalls cannot be made via car HF and also cannot be received through it. Only by manualy accepting or dialing on the phone. And naturally the sound goes only via the phone, no HF.
The strange thing is, when I turn off the car and leave it, the phone says it is still connected to it, which is impossible.
Any ideas?
Thank you!
czechmate said:
Hi guys,
I am having problems with car BlueTooth hands free and Samsung Galaxy S:
With Eclair 2.1 it was working flawlesly, connected automaticlay after paired, I could make phonecals, receive phonecals, no quality issue, phonebook worked fine etc... The only problem was that once I did not swithced the BT on my SGS before starting to drive, for some security reasons the car was not searching for phones while driving, so I had to turn the BT in car off and on again and then it connected well. But overal problem free...
With latest 2.2 Froyo (i9000xfjp7) and also previous Froyo distributions (i tried JPA if I remember correctly), the phone can be paired, it connects to the car but after one phonecall it looses connection and works no more. The strange thing is, the BT icon on the phone shows brackets (like when connected) and also the car shows the phone is still connected. But phonecalls cannot be made via car HF and also cannot be received through it. Only by manualy accepting or dialing on the phone. And naturally the sound goes only via the phone, no HF.
The strange thing is, when I turn off the car and leave it, the phone says it is still connected to it, which is impossible.
Any ideas?
Thank you!
Click to expand...
Click to collapse
Had exactly same issue I changed to Doc Rom JP8, for last 3-4 days didn't face any issue.
Monu123 said:
Had exactly same issue I changed to Doc Rom JP8, for last 3-4 days didn't face any issue.
Click to expand...
Click to collapse
That is weird... When I switch back to Eclair, it works OK, back to Froyo, no HF after one phonecall...
I dont know how to work with ROMs, I managed to find out how to flash firmwares, I even handled many problems with Odin and its moods, incomplete flashes, etc... But I dont know how to use these custom ROMs...
Anyway, i would appreciate if someone told me how to resolve it without custom ROMs, as I plan to use offical Froyo when it becomes available, but with this issue, it is useless for me, as I travel a lot...
No one else?
I'm having a related problem.
I'm getting music stream cut outs (1 sec max) when streaming bluetooth to caraudio WHILE wifi on.
If i disable wifi, bluetoothaudio works fine. I know they share range bt/wifi, but this is unacceptable. They should negotiate. Everytime wifi scans, i get cutouts. Unusable. Only workaround is disabling wifi (and thats annoying because i have to be constantly activating/disabling it everytime i enter somewhere with wifi etc.
Using Docrom xxjpo v8 with voodoo.
Anyone has some software fix that makes wifi behave better when bluetooth musictream on?
There are some weird issues I have been noticing with my SGS regarding bluetooth.
At first, I got slightly irritated when I found out I was suffering what I thought to be this issue on my SGS (noticed after flashing to JP6, later on JPX and now also on JPY). But since, I have been carefully narrowing down the problem (there seem to be several variants of the issue bundled within the one linked) and have finally figured out how to reproduce the error (sort of, at least in my setting: SGS-I9000, BMW 1series car BT system).
After setting a custom BT device name and pairing to the car, the BT handsfree works flawlessly on spot and if disconnecting and reconnecting later. The problem starts after rebooting. Now, here's where I'm getting inconsistent results.
Most times the bluetooth info I entered is simply reset to factory defaults: the pairing list is empty and the device name is set to the standard "Galaxy S".
Some other times however, it gets much more annoying: all the settings seem to be intact (pairing and device name stay as set) but BT connection always drops after about 60s (regardless of wheather you start/receive a call or not).
Is this a known issue? Did any of you experience this behavior? Any known fixes?
Thanks!
Phil
What ROM are you running? Get yourself onto the newest Froyo and see if the problem goes away. I definitely don't have problems with mine going to headphones, ear headset, or in car system.
Doc kitchen (jan 3rd) + Hardcore kernel JPY (which means latest kernel/drivers). This has been happening to me all along though, despite of rom changes (also happened with stock JP6 and darky's JPX).
Sent from my GT-I9000
Hi,
same problem for me: the bluetooth connection to my Parrot MKI9200 car audio system drops after a few seconds. This was not the case with ROMS older than JPX/JPY.
Are you still having this issue? I just flashed Serendipity 6.2 and have the same problem. When I reboot the Bluetooth settings are reset to default.
goodolsen said:
Are you still having this issue? I just flashed Serendipity 6.2 and have the same problem. When I reboot the Bluetooth settings are reset to default.
Click to expand...
Click to collapse
The issue disappeared on flashing to a new rom. I'm soory not to be able to give you more details because I found out the issue was gone by surprise (I had stopped using the car handsfree alltogether because of the issue).
Right now I'm on a Doc rom (hardcore kernel, JPY radio, ext4 system & data, ext4nj cache) and it works perfectly!
Hi, I am new to the forum but need some help please.I can no longer get my contacts to display on the radio in the car after upgrade to 2.2 via Samsung kies. This feature worked fine before update but now I get the message that the phone is connected and a new phonebook is available but no contacts are there. I tried a HTC Legend and it paired and loaded the contacts no problem, running a custom 2.2 ROM. Any thoughts? Anyone know of a problem with Samsungs 2.2 for Rogers Capivate update and bluetooth?
Vehicle:2010 VW golf with 9W3 bluetooth kit.
Phone: Samsung capivate (I896) on Rogers
Thanks
Resolved
After trying a complete unpairing of phone and disconnect I repaired the phone and igorned the permissions and the phonebook loaded.
Hey gang,
Having a very strange issue. I was running 4.4.3 roms based on the stock rom for several months and then finally decided to try out some of the 5.0+ roms. I flashed the newest firmware (from 2/15) and was able to flash the roms without a problem, but then when I got in my car, the phone connected to my head unit via bluetooth, but it won't play sounds from music/YouTube. I looked under settings for bluetooth and it shows my device connected and paired but below the device is the message "(No Media)". When I click the gear for more settings it shows the Media box as checked. On my head unit, it also has the music symbol grayed out, as if to say it also knows that media is not working via bluetooth. All of the phone functions work fine through bluetooth as usual.
Thinking it might be the rom, I flashed back to the 4.4.3 rom I was using, but still get the same error. I have since:
Flashed a stock rom
Reflashed the 4.4.3 firmware
RUU'ed back to 4.4.3 stock
And I am still having the same error. At this point, I think I might have permanently messed up the bluetooth on my phone. There are very few settings in my head unit pertaining to bluetooth so I can't really troubleshoot that side. My friend was able to connect his phone to my car and play music via bluetooth so I think the problem is with my phone.
Any ideas?
Thanks in advance.