Bluetooth car kit problem with FLB and Oscillation 2.1ROM

[Guest topspinserve]

I am finding a frustrating problem and wonder if anyone else has a problem with bluetooth car kits?

Since upgrading to 2.1, I have not been able to get bluetooth working. The phone pairs easily enough, but though I can dial from the steering wheel, no audio comes through the car, but only through the Pulse's in built speaker. I have tried FLB and Oscillation ROMs. Can anyone help? Bluetooth worked with MCR1.7 ROM

[Guest Simon O]

Known issue with Android 2.1, I believe. Try changing your bluetooth settings in the phone.

[Guest topspinserve]

Known issue with Android 2.1, I believe. Try changing your bluetooth settings in the phone.

I've tried all conceivable changes to the phone's bluetooth settings. No luck! It just seems that the 1.7MCR's Bluetooth worked better. I've done a general search and find lots of users having this trouble, but some of them having the problem fixed after upgrading to Froyo!! Can't wait!

[Guest Azurren]

I've tried all conceivable changes to the phone's bluetooth settings. No luck! It just seems that the 1.7MCR's Bluetooth worked better. I've done a general search and find lots of users having this trouble, but some of them having the problem fixed after upgrading to Froyo!! Can't wait!

If it is really important to you then you could always downgrade to 1.5, install the RA recovery then flash the 1.7 rom.

Froyo may never come. I'll can give you very good odds

[Guest Zsolabola]

I have two different type of BT carkit, a Nokia and a LG. I'm using the FLB ROM without any audio problem

I've used the among others the factory TMO 2.1, the MCR, and FLB without any problems with BT carkits

[Guest HermanUser]

I also have several bluetooth problems with my 2.1 pulse.

While searching the net for informations about the bluez configuration files i found something that could be a solution to your problem:

This problem is caused by A2DP which cupcake enabled.

You need to disable A2DP in /etc/bluez/audio.conf.

If you can became root on your device this is easy.

If su doesnt work for you, "Google it", it is

probably possible :-)

[linux instructions]

1. install android sdk

2. connect via usb

3. Run

<sdk-dir>/tools/adb pull /etc/bluez/audio.conf /tmp/audio.conf

4. Edit local copy of audio.conf to change:-

Enable=Source,Control,Sink

Disable=Headset,Gateway

to

Enable=

Disable=Headset,Gateway,Source,Control,Sink

5. remount / on android read/write

From tools/adb shell

su

mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system

6. Copy new audio.conf onto system

tools/adb push /tmp/audio.conf /etc/bluez/audio.conf

7. remount / ro

mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system

8. disable/enable bluetooth

9. Ring up your wife from car and tell her you'll fix her android now and

all is good :-)

[Guest topspinserve]

I also have several bluetooth problems with my 2.1 pulse.

While searching the net for informations about the bluez configuration files i found something that could be a solution to your problem:

This problem is caused by A2DP which cupcake enabled.

You need to disable A2DP in /etc/bluez/audio.conf.

If you can became root on your device this is easy.

If su doesnt work for you, "Google it", it is

probably possible :-)

[linux instructions]

Hmm... I do have Ubuntu on a notebook, but will admit to be a complete novice! Can I do the above with windows?

[Guest Totyasrác]

I have two different type of BT carkit, a Nokia and a LG. I'm using the FLB ROM without any audio problem

I've used the among others the factory TMO 2.1, the MCR, and FLB without any problems with BT carkits

Mine is a SonyEricsson car audio kit and all ROMs I've tried (1.5: factory, dec. update, MCR 1.7/1.8; 2.1: factory+HUN update, Paul's WIP, FLB) are working seamlessly with it...

Edited June 14, 2010 by Totyasrác