I have the Motorolla S9 bluetooth A2DP stereo headset.
I also have the Hero currently running VillainROM 3.4 but I've been trying to run a bt connection for A2DP media playback with almost all Android 2.1 ROMS with same results.
The phone pairs fine but once I start playing any mp3 headset disconnects and reconnects at random.
I should mention that bluetooth works great in my car with the stock stereo system for simple phone calls.
I searched the entire forum but couldn't find anyone else with this issue ... Modaco 3.1 people report bt stereo playback to be working fine .. I think this is a 2.1 issue as VillainROM 3.3 and 3.4 and BeHero and other 2.1 based roms have this issue.
please HELP
Hello rafynet
i had same problem and i have solved with this method:
your phone must be rooted
there is a file in /etc/bluez/audio.conf
copy that to your pc.Change the lines
from
-----------------------------
Enable=Source,Control,Sink
Disable=Headset,Gateway
-----------------------------
to
-----------------------------
Enable=
Disable=Headset,Gateway,Source,Control,Sink
-------------------------------------------
save it.
copy the changed file back to /etc/bluez/
I have tried this solution in all rom that i have tested and all work well for me, watch the entire article:
Issue 3960: Bluetooth issues with car systems in Android 1.5 / 1.6
I'm sorry, i can't post this link on forum!!
search it in google.
sorry for my english!
I'm waiting your feedback!!
I hope this solution works well for you. Try this!
your solution helped a little bit ... but bluetooth connection still drops and re-connects all the time ... it's very annoying.
I'm fairly sure this will be fixed when we get the official Hero 2.1 update.
I had noticed the same thing with my Motorola T505 ROKR handsfree adapter. Worked fine in 1.5, but in 2.1 it would disconnect every 30 seconds or so, then reconnect.
However... I've just got a new car stereo (Pioneer DEH-P6100BT) and it actually works *BETTER* in VillianROM 4.0 than it did in Modaco 3.2. In Modaco, it would only connect to "phone audio" and not "media audio," and I had to go into the Android settings and enable "media audio" each time I got in my car. With VillainROM, it connects automatically and it doesn't disconnect. Also, I've found that in 2.1, when listening to BT Audio, the music doesn't get interrupted by notification sounds, which I hated about 1.5.
I've had nothing but problem with a2dp on the hero, and it's probably the feature I need to work the most. I tried a whole host of 1.5 and 2.1 roms but none of them would consistantly connect to my pioneer deh-p700bt. I read somewhere that it's been a problem for lots of people since the 2.73.x series of updates, so I downgraded to the T-Mobile 1.76.110.6 stock rom and it's worked perfectly for me ever since! I'll have to stick with that one for now and hope it gets fixed in the upcoming 2.1 update
Hi,
I have a question about this subject :
i have a bluetooth car stereo with phone handfree inclued.
With all ROMs I tried (and a tried a lot...)
the phone handsfree always worked
Depend of the ROM, some items were available or not : (battery indicator or signal level indicator for example)
With only one ROM (and I don't remember which one), I could transfer my contact list from the phone to the car stereo system (with bluetooth).
Does someones knows if this feature will be again available into the next ROM (official or not) ?
Thx
PS : sorry for my bad english
yan74s said:
Hi,
I have a question about this subject :
i have a bluetooth car stereo with phone handfree inclued.
With all ROMs I tried (and a tried a lot...)
the phone handsfree always worked
Depend of the ROM, some items were available or not : (battery indicator or signal level indicator for example)
With only one ROM (and I don't remember which one), I could transfer my contact list from the phone to the car stereo system (with bluetooth).
Does someones knows if this feature will be again available into the next ROM (official or not) ?
Thx
PS : sorry for my bad english
Click to expand...
Click to collapse
The Android SDK did not include a bluetooth API in 1.5, but it is included in 2.1. I would guess we'll see a big improvement with the official 2.1 update.
Apr. 15 update:
Thanks for all feedbacks.
I have made sure all changes of Bluetooth code in the recent kernel releases are alright.
Please install the latest tytung_r9 kernel for Bluetooth compatibility testing.
And flash audio.conf_update.zip to see if changing Bluetooth settings in ROM will improve the stability or not.
End of testing below:
Hello Everyone:
We have changed something in Bluetooth related source code in recent kernel releases. (Thanks all devs.)
Each kernel has different changes, and I would like to collect the info about which kernels can support your Bluetooth devices (headsets, car kits, or any devices) or not.
These info may help me develop the next kernel.
These four kernels may have different behaviors when using with your Bluetooth devices.
Apr 03: tytung_r9_beta
Supported unique Bluetooth MAC address.
Supported Bluetooth auto-reconnect.
Supported two-way call recording.
Included my modified initrd.gz (modify init.htcleo.rc to support unique Bluetooth MAC address)
Mar 27: tytung_r8.3
Updated Bluetooth stack from AOSP.
Mar 25: tytung_r8.2
Fixed Bluetooth 60mA battery drain (i.e. support Low Power Mode) (Big thanks to Trilu and Charansingh)
Included my modified initrd.gz (add --enable_lpm to support Low Power Mode)
Mar 24: tytung_r8.1
It represents all previous kernels which have Bluetooth 60mA battery drain.
For me, they all work with my Bluetooth enabled PC. (Acer Aspire Z5710)
And I can also use another native Android phone to transfer files to/from HD2 via Bluetooth by using ES File Explorer.
If you would like to help test tytung_r9 kernel, please flash it and give me the report.
Remember to make a nandroid backup before testing, to restore back after testing or if anything goes wrong.
You can replace /boot/initrd.gz in zip file with logwrapper version in attach files to output the detail log to ddms/logcat.
Before every kernel testing, please delete Bluetooth devices in Bluetooth settings on your phone, and then rescan, repair, and connect to your BT devices again.
Kernels tytung_r9 include initrd.gz which is optimized for an AOSP ROM (i.e. NexusHD2-Gingerbread) and may be not compatible with other ROMs (e.g. CM7 or MIUI).
For example, if tytung_r9 causes any problem, please replace /boot/initrd.gz of kernel_tytung_r9_update.zip with your original ROM's initrd.gz and then flash it again.
Besides, make sure you have the following lines in init.htcleo.rc located in initrd.gz to support the unique Bluetooth MAC address fix in r9.
Code:
# bluetooth MAC address programming
chown bluetooth bluetooth /sys/module/[COLOR="Red"]board_htcleo[/COLOR]/parameters/[COLOR="red"]bdaddr[/COLOR]
setprop ro.bt.bdaddr_path /sys/module/[COLOR="red"]board_htcleo[/COLOR]/parameters/[COLOR="red"]bdaddr[/COLOR]
Report format:
ROM that you are using:
Kernel version:
Bluetooth Headset/Device (brand):
Stereo music (A2DP):
Remote control (play/pause/skip music) (AVRCP):
Phonebook access (vCard exchange) (PBAP):
Files transfers (OPP/OBEX):
Personal Area Networking Profile (PAN):
Make or answer a call (HSP):
Detail description:
You can reply here and/or post in Google Docs: TYTUNG Kernel's Compatible Bluetooth Headsets List to be more organized.
I hope your time and effort for testing and sharing the results to XDA will help others purchase their next Bluetooth headset/device.
Thanks
--tytung
Will this help solving the stereo Bluetooth thing on sense?
white-energy said:
Will this help solving the stereo Bluetooth thing on sense?
Click to expand...
Click to collapse
Even a native Android phone cannot also support all brand of Bluetooth devices.
So this's mainly a compatible Bluetooth Headsets List, and maybe it will help develop the kernel.
i have typhoon 2.9.3
your kernel r9 works ok with motorola h300 bt headset.it is not stereo headset but with supermonofroyo bt app i can hear music from the headset.
boba23 said:
Hey tytung,
gonna give your new kernel a try, since I am also having BT issues with my car handsfree unit. I can't pair it with any gingerbread rom yet. The Pairing/PIN dialog to enter the pin code just doesn't come up.
But I don't think it's a kernel issue for me since I tried imilkas 2.3.3 Sense 2.1 rom and with that I can pair my device perfectly fine.
Right now I am playing around with the bluez config files (auto_pairing.conf etc) to see if that fixes anything for me.
What is more with froyo roms I never had trouble with my car handsfree, worked perfectly fine.
boba
Edit: back to your question, 8.3 BT is working with the following devices for me: Jabbra BT250 headset, FM9 BT TMC Receiver, Lenovo T60p Bluetooth - But NOT working, not pairing with my built in Parrot handsfree/headunit in a Peugeot 207cc.
boba
Click to expand...
Click to collapse
Sense ROMs and AOSP ROMs use different Bluetooth stack, so that'll be the cause.
In other words, HTC uses a modified BT stack in their Sense ROMs.
ROM:Typhoon2.9.4
BT Headset:SE MW600
Kernel:r9
Everything works. Good call recording sound even via BT Headset although it is louder via Phone.
A2DP and AVRCP all work.
Reconnects perfectly
Tytung,
Thanks so much for working on this!
Just tried with hyperdroid v11 and it boots ok and Bluetooth appears to have a full mac address now.
But, it still doesn't work properly with wireless tether in Bluetooth PAN mode to my iPad or Macbook Pro in OSX or Windows 7.
Wireless tether still says error :SIOCSIFFLAGS (cannot assign requested address)
So for some reason it isn't assigning an IP to the ipad/laptop.
Could be a problem with the app itself but others reported it was the mac address causing the problem so I'm not sure.
I'm very grateful for your effort in looking at this though so thank you!
Tytung,
despite the heavy battery drain r8.1 was working very well with my parrot ck3400 carkit (carkit and gps mouse).
kernel r8.3 (among in Tyween Typhoon cLK versions) was giving a lot of problems to connect and reconnect when making a phone call or connecting the gps mouse trough bluetooth. I always have to flash your cLK_tytung_bt fix for a working bluetooth connection. i don't know what kernel this is.
Will test r9 beta on Tyween Typhone 2.9.4 and report back to you asap
boba23 said:
Hey tytung,
gonna give your new kernel a try, since I am also having BT issues with my car handsfree unit. I can't pair it with any gingerbread rom yet. The Pairing/PIN dialog to enter the pin code just doesn't come up.
But I don't think it's a kernel issue for me since I tried imilkas 2.3.3 Sense 2.1 rom and with that I can pair my device perfectly fine.
Right now I am playing around with the bluez config files (auto_pairing.conf etc) to see if that fixes anything for me.
What is more with froyo roms I never had trouble with my car handsfree, worked perfectly fine.
boba
Edit: back to your question, 8.3 BT is working with the following devices for me: Jabbra BT250 headset, FM9 BT TMC Receiver, Lenovo T60p Bluetooth - But NOT working, not pairing with my built in Parrot handsfree/headunit in a Peugeot 207cc.
boba
Click to expand...
Click to collapse
side note:
a German driving a French car???? hmm
white-energy said:
Will this help solving the stereo Bluetooth thing on sense?
Click to expand...
Click to collapse
What problems do you have with sense ???
What i have also found - The pairing issue is also influenced by the bt firmware.
You know, that is the bcm4329.hcd file in /system/etc/firmware
With the latest htc sense firmware i can pair with my bluetooth devices, but i cant get any audio transmission.
BCM4329B1_002.002.023.0511.0538.hcd
Currently i use the bcm4329.hcd file with 14.172 Bytes.
What i have also seen, that the newer files saves some power....
Hi tytung, I don't have a log file for you unfortunately. I have personally had no problem with my bluetooth headset with any of your recent changes. However, with tytung r9 I think this is related to the callrecording patch, as I don't see how anything changing in bluetooth would affect this. With v2.9.4 yesterday I was testing with tytung r9... At work I need to use airplane mode because I get no signal in the office, only when I go to the restroom I can get signal. Upon leaving airplane mode, in 2 out of 8 times yesterday of turning airplane mode off, I was unable to get a data connection upon getting a signal. Switching data on or off did not help, only a reboot did. This is why I have decided to keep tytung r8.3 as the kernel used in the latest version of my ROM. Maybe I can do some more testing and try to get some logs for you, but I rolled back to r8.3 for now. Has anyone else experienced this? Thanks for your work on what I think is the best kernel for our phones currently
Edit: It may have been because I overlooked the requirements in initrd.gz but I am unsure. I saw the lines but mine say board_bravo instead of board_htcleo, and I thought I had what was required as the lines were very similar. I will begin testing again tonight and let you know if I experience the same problem I had before.
Touchscreen Frozen
Something weird is happens with my hd2.
When i longpress the redbutton to shutdown or reboot i cant touch the options (shutdown, reboot, profiles etc).
The bizarre is that happens with all roms with your newst kernels
Maybe a kernel related?
(all them has the tytyng 8.3 and 9.0b)
felipemadox said:
Something weird is happens with my hd2.
When i longpress the redbutton to shutdown or reboot i cant touch the options (shutdown, reboot, profiles etc).
The bizarre is that happens with all roms with your newst kernels
Maybe a kernel related?
(all them has the tytyng 8.3 and 9.0b)
Click to expand...
Click to collapse
Unfortunately I have the same problem for a few days, sometimes helped re-pressing the red button and after unlocking screen reacted normally. The problem is already present on all OS, and regardless of the kernel on Android builds. I suspect that is a hardware malfunction and my poor Leo soon will die. Actually i'm on CoreDroid 1.6 and i noticed that the problem doesen't appear as often as on tytung kernel.
Sent from my HTC HD2 using XDA App
boba23 said:
Yea, that's what I figured as well. You think it's possible (if everything else fails for me) to port/use that modded stack to a CM7 rom?
If you look at the files (bluetoothd, libs and so on) it's definately still bluez based. Question is what does HTC modify and what other files are needed ...
boba
Click to expand...
Click to collapse
No idea how to port/use that modded BT stack to a CM7 rom.
crunchie-uk said:
Tytung,
Thanks so much for working on this!
Just tried with hyperdroid v11 and it boots ok and Bluetooth appears to have a full mac address now.
But, it still doesn't work properly with wireless tether in Bluetooth PAN mode to my iPad or Macbook Pro in OSX or Windows 7.
Wireless tether still says error :SIOCSIFFLAGS (cannot assign requested address)
So for some reason it isn't assigning an IP to the ipad/laptop.
Could be a problem with the app itself but others reported it was the mac address causing the problem so I'm not sure.
I'm very grateful for your effort in looking at this though so thank you!
Click to expand...
Click to collapse
Wireless tether can run correctly in my ROM, and I don't see any SIOCSIFFLAGS (cannot assign requested address) error.
What steps will reproduce the problem?
trilu said:
What i have also found - The pairing issue is also influenced by the bt firmware.
You know, that is the bcm4329.hcd file in /system/etc/firmware
With the latest htc sense firmware i can pair with my bluetooth devices, but i cant get any audio transmission.
BCM4329B1_002.002.023.0511.0538.hcd
Currently i use the bcm4329.hcd file with 14.172 Bytes.
What i have also seen, that the newer files saves some power....
Click to expand...
Click to collapse
My bcm4329.hcd file has 17,684 Bytes and comes from Nexus One Gingerbread OTA.
tyween said:
Hi tytung, I don't have a log file for you unfortunately. I have personally had no problem with my bluetooth headset with any of your recent changes. However, with tytung r9 I think this is related to the callrecording patch, as I don't see how anything changing in bluetooth would affect this. With v2.9.4 yesterday I was testing with tytung r9... At work I need to use airplane mode because I get no signal in the office, only when I go to the restroom I can get signal. Upon leaving airplane mode, in 2 out of 8 times yesterday of turning airplane mode off, I was unable to get a data connection upon getting a signal. Switching data on or off did not help, only a reboot did. This is why I have decided to keep tytung r8.3 as the kernel used in the latest version of my ROM. Maybe I can do some more testing and try to get some logs for you, but I rolled back to r8.3 for now. Has anyone else experienced this? Thanks for your work on what I think is the best kernel for our phones currently
Edit: It may have been because I overlooked the requirements in initrd.gz but I am unsure. I saw the lines but mine say board_bravo instead of board_htcleo, and I thought I had what was required as the lines were very similar. I will begin testing again tonight and let you know if I experience the same problem I had before.
Click to expand...
Click to collapse
Well, in my ROM, r9 kernel will write unique BT Mac address into /sys/module/board_htcleo/parameters/bdaddr file.
You can read its content.
Then ROM will get BT address from bdaddr when booting. (via /system/bin/brcm_patchram_plus)
If your ROM has different condition, please change board_htcleo to something else.
tytung said:
Well, in my ROM, r9 kernel will write unique BT Mac address into /sys/module/board_htcleo/parameters/bdaddr file.
You can read its content.
Then ROM will get BT address from bdaddr when booting. (via /system/bin/brcm_patchram_plus)
Click to expand...
Click to collapse
Thanks for the information. Has anyone else experienced what I did with tytung r9 in regards to no data connection upon turning off airplane mode? I am going to begin my testing again with tytung r9 beta today after I update the initrd.gz used in my build. I did not experience this with any previous tytung kernels, and think that the cause may be the call recording feature.. I am unsure and have not done any serious analysis on it, just wanted to let you know what I have experienced.
felipemadox said:
Something weird is happens with my hd2.
When i longpress the redbutton to shutdown or reboot i cant touch the options (shutdown, reboot, profiles etc).
The bizarre is that happens with all roms with your newst kernels
Maybe a kernel related?
(all them has the tytyng 8.3 and 9.0b)
Click to expand...
Click to collapse
As mzebrowski13 said, I guess it's a hardware issue.
Hi, I've got a small issue with my bluetooth a2dp device. The device is this one:
BlackBerry Remote Stereo Bluetooth Gateway. It is made by RIM, but works with any device supporting a2dp. My issue with the Galaxy Nexus is that it no longer auto connects.
My setup is in my vehicle, I keep the bluetooth receiver connected to the aux power jack and aux audio in in the center console. This way, when I start the car, the receiver powers up and tries to auto-connect to the last device. On my vibrant with Android 2.1/2.2 this worked fine. When I dabbled with CyanogenMod and some other custom roms, it stopped working but I chalked it up to some problem with the custom rom.
Now, I'm seeing the same sort of problem: if I keep the screen of my nexus on, I can see the bluetooth icon change blue, and then immediately change back to gray. To me, this indicates that the receiver succeeds in connecting but is then disconnected for some reason. The device only supports a2dp, not the handsfree profile. When I looked into the Android kernel code, I found a place where the kernel will try to connect the handsfree profile if the a2dp profile is auto-connected, but it wasn't clear if that was the actual problem or not.
Anyone else have any similar experiences?
I have the same device in my 2008 Accord coupe which is placed in the center arm console. I had an Evo 3D that would automatically connect when I would start the car and BT was already enabled on my phone. I too switched to a different ROM and would have issues auto connecting so I switched back to a different ROM. Now on my stock GN, I have to manually go into settings and click the device to connect. I see no settings about auto connecting when in range. I will have to see if the BT icon turns blue and then back to gray... haven't looked for that. If anyone has thoughts on this, I'm all ears!!
bigdawgr6 said:
I have the same device in my 2008 Accord coupe which is placed in the center arm console. I had an Evo 3D that would automatically connect when I would start the car and BT was already enabled on my phone. I too switched to a different ROM and would have issues auto connecting so I switched back to a different ROM. Now on my stock GN, I have to manually go into settings and click the device to connect. I see no settings about auto connecting when in range. I will have to see if the BT icon turns blue and then back to gray... haven't looked for that. If anyone has thoughts on this, I'm all ears!!
Click to expand...
Click to collapse
I suspect it has something to do with Android's attempts to auto connect to the headset profile when a A2DP profile is connected.
See:
# Automatically connect both A2DP and HFP/HSP profiles for incoming
# connections. Some headsets that support both profiles will only connect the
# other one automatically so the default setting of true is usually a good
# idea.
#AutoConnect=true
Click to expand...
Click to collapse
from https://github.com/android/platform_system_bluetooth/blob/master/data/audio.conf
I have seen the code where this happens and it seemed that if the headset profile failed to connect, the A2DP connection was also disconnected. Though, I can't recall what file it was.
jjohns63 said:
I suspect it has something to do with Android's attempts to auto connect to the headset profile when a A2DP profile is connected.
See:
from https://github.com/android/platform_system_bluetooth/blob/master/data/audio.conf
I have seen the code where this happens and it seemed that if the headset profile failed to connect, the A2DP connection was also disconnected. Though, I can't recall what file it was.
Click to expand...
Click to collapse
Strangely enough, the phone paired with the device twice without issue yesterday and failed once later on that same day. I'm toggling BT off and then on to get connection for now.
It seems like the phone and device are connecting without issue but I know I haven't done anything to change it. I'm on AOKP M3 and Leankernel V1.8 if that helps. When I first flashed those two, I still had connections issues, so switching to them wasn't a resolution.
I am not sure this really helps your issue but it is related. I wrote an app that will auto-connect Bluetooth devices. It is free on the market and is called A2DP Volume. The current implementation of auto-connect looks for one device connection and then connects another. I started another widget that will simply connect a Bluetooth device but I have not finished that one. A2DP Volume is free, open source, and ad free. You can find the open source project on Google Code. Just search for A2DP Volume.
I have been trying this for weeks and this app solved it!!! Thanks for making the app!
jroal said:
I am not sure this really helps your issue but it is related. I wrote an app that will auto-connect Bluetooth devices. It is free on the market and is called A2DP Volume. The current implementation of auto-connect looks for one device connection and then connects another. I started another widget that will simply connect a Bluetooth device but I have not finished that one. A2DP Volume is free, open source, and ad free. You can find the open source project on Google Code. Just search for A2DP Volume.
Click to expand...
Click to collapse
jjohns63 and bigdawgr6,
Any update on this problem? I don't have the Nexus, but I have Droid Incredible 2. I also run into the same problem when I use CyanogenMod 7.2, which is a AOSP based ROM. The connection is fine with the stock ROM. I have tried to change things in the audio.config but it does not seem to help. I think I ran into a post somewhere saying HTC stock ROM uses a propietary bluetooth stack and AOSP and CyanogenMod uses BlueZ open source stack, and that is where the problem is.
Anyway, it would be nice if you guys can share some info.
Thanks!
Hi guys,
Do any of you use an AVRCP capable bluetooth device (headset, iPod docking station bluetooth adapter, car bluetooth kit, etc.)?
I have a Belkin AirCast that works without any issues with an iPhone 4S but when paired to my note 2 it works ok except next causes the volume to go down instead of changing to the next song.
I have tested this with stock ROM and also ARHD 3.0 (first was on ARHD then flashed back to stock with complete wipe).
I have also checked /system/usr/keylayouts/AVRCP.kl for the keycodes and they are identical between stock and ARHD3.0 ROM and the same as what I have found on the internet.
What do you guys think the problem might be? And do you think there is a solution trying to tweak the .kl file until all commands work correctly?
Is there an event dumper that can dump to a logfile all the input events the device receives?
Thanx,
No problems with any of the 3 BT devices I use. (Mini boom box, Jaybird Freedoms, and car head unit)
Sent from my GT-N7100 using Tapatalk 2
Hello there. I've been experiencing a problem with my OP3, regarding the BT connection to my car stereo.
I recently bought a new head unit for my car, a Pioneer MVH-X580BT unit, it Works fine. However, when i connect my phone to it, it allows me to playback áudio, but i won't allow me to use it for hands-free calling. The Bluetooth menu on the phone says "MVH-X580BT - Connected (no phone)". It happens with any CM-based rom that i've tried so far.
However, when i install a stock rom (Oxygen OS, Freedom OS also works), it works just fine, both audio and phone mode.
Is there something in custom roms that changes some sort of parameters in the ROM that makes the phone refuse a phone mode connection from the radio?
Any tips i can use?
Thanks!
logcat of the incident:
Here.
Hope it helps.
I've had the same problems. It's an issue with the LOS BT stack. I've created several unofficial versions of my favorite ROMs using a different BT stack that fixes this problem for me. Let me know if they work.