[Q] bluetooth auto connect differences between 4.2.2 roms - T-Mobile, Samsung Galaxy SIII

Hi. I'm loving Android 4.2.2. I've noticed one parity difference though when it comes to auto connecting to my car's bluetooth dongle (It's a belkin aftermarket one). I've tried LiquidSmooth, rootbox nightlies, DeviantXone, etc. I've probably tried 7-8 different brands of ROMs. I've noticed though that on 4.2.2, bluetooth auto connect isn't alike on all of them. For some of them, bluetooth always auto connects with my Belkin receiver in the car. On the other ones, maybe sometimes.
I'm wondering if this perhaps has to do with deep sleep because I've noticed that (perhaps not coincidentally) on the ROMs where it always auto connects just fine, battery life tends to be a lot weaker. For a given ROM, I've tried changing the kernel from Ktoonsez, Lean, etc...no difference. For me, it's the ROM that makes the difference, not the kernel.
I've looked in /system/etc/bluetooth and perused through the .conf files. I could have sworn there used to be an auto sync related parameter but can't seem to find it. I don't know if maybe it's some parameter in a conf file somewhere. It would make sense that attempting to always auto connect with nearby devices would result in more of a battery drain.
Any ideas? Is it a setting or something ROM specific? Can it be changed by the end user of a ROM? I am trying to avoid bluetooth auto connect apps on the market since I also don't want a kernel wakelock being used for a service that never sleeps. That may really hinder battery. Thanks!

davidisflash said:
Hi. I'm loving Android 4.2.2. I've noticed one parity difference though when it comes to auto connecting to my car's bluetooth dongle (It's a belkin aftermarket one). I've tried LiquidSmooth, rootbox nightlies, DeviantXone, etc. I've probably tried 7-8 different brands of ROMs. I've noticed though that on 4.2.2, bluetooth auto connect isn't alike on all of them. For some of them, bluetooth always auto connects with my Belkin receiver in the car. On the other ones, maybe sometimes.
I'm wondering if this perhaps has to do with deep sleep because I've noticed that (perhaps not coincidentally) on the ROMs where it always auto connects just fine, battery life tends to be a lot weaker. For a given ROM, I've tried changing the kernel from Ktoonsez, Lean, etc...no difference. For me, it's the ROM that makes the difference, not the kernel.
I've looked in /system/etc/bluetooth and perused through the .conf files. I could have sworn there used to be an auto sync related parameter but can't seem to find it. I don't know if maybe it's some parameter in a conf file somewhere. It would make sense that attempting to always auto connect with nearby devices would result in more of a battery drain.
Any ideas? Is it a setting or something ROM specific? Can it be changed by the end user of a ROM? I am trying to avoid bluetooth auto connect apps on the market since I also don't want a kernel wakelock being used for a service that never sleeps. That may really hinder battery. Thanks!
Click to expand...
Click to collapse
The audio.conf is no longer there in 4.2.2. I've read something about the BT stack being re-engineered. Someone on xda has released some replacement libraries for BT and I suspect compiling a new library might be the only way to make changes similar to the previoud audio.conf file changes. This really sucks and there are not too many people who know enough about this sort of thing. Also, the android documentation for bluetooth is not helpful.
As for me, I am trying to get by BT audio working well again. Right now audio is skipping pretty bad streaming to my Kenwood (Parot) Bluetooth headunit. I know what settings I need for audio.conf to make this work, but have no idea what to tweak in Android 4.2.2.
HELP PLEASE

gg48gg said:
The audio.conf is no longer there in 4.2.2. I've read something about the BT stack being re-engineered. Someone on xda has released some replacement libraries for BT and I suspect compiling a new library might be the only way to make changes similar to the previoud audio.conf file changes. This really sucks and there are not too many people who know enough about this sort of thing. Also, the android documentation for bluetooth is not helpful.
As for me, I am trying to get by BT audio working well again. Right now audio is skipping pretty bad streaming to my Kenwood (Parot) Bluetooth headunit. I know what settings I need for audio.conf to make this work, but have no idea what to tweak in Android 4.2.2.
HELP PLEASE
Click to expand...
Click to collapse
+1 I have the same problems with my head unit. I'm hoping someone can fix this

Related

Bluetooth A2DP on my Tilt2: WORTHLESS AS $H!T

Ok, so I finally got into the smartphone game to get a better music streaming experience. MFRadio and MFScorn just weren't cutting it for me anymore. I hated the skips and the ridiculously long (and repeated) buffering time. So I first looked at Android phones but went with WinMo because they say you can run both OS's with WinMo (and the only Android offering from AT&T has a 12-hour standby time before the battery dies, according to reviews).
I have a Bluetooth head unit and have had over a dozen phones paired with it. This phone however is a completely different story. I have installed the latest "release" from AT&T (from a thread on this site). At first I tried streaming with the bundled Windows Media Player which apparently doesn't stream anything at all (with both the bundled and downloaded releases of the OS), then downloaded TCPMP. TCPMP is everything I have ever dreamed of in a streaming media player, but the only problem I have with it is that it won't connect to a stream unless I have already opened up a browser window and went to a website. Not the end of the world.
So, I get in my truck and initiate pairing to the phone. It sees the head unit as a Hands-free and as Stereo Audio. I can get it to connect for a split second and then it dies. I get a popup notification that tells me that the phone cannot control volume when paired to the bluetooth device and audio must be adjusted from the device itself. Fine. But then it doesn't work at all. At first, I wanted to blame TCPMP until I realized that nothing at all was working with the head unit. I think I got it to work once but it never worked again.
So is there any way to fix this problem? This is the one thing I wanted working on my new phone. Yes, the notifications that my texts were successfully sent are very annoying (as well as the other notifications), and yes, Windows Media Player for Mobile is useless, but the fact that I can't stream Bluetooth audio on this phone really makes this phone worthless to me. Didn't anyone bother testing this stuff before releasing this garbage? The Tilt is a paperweight to me right now because it can't do the one thing I want it to do the most. I might as well go back to my Sony Ericsson W760a at this point!
What can I do? I have not yet unlocked anything (although I have a SIM unlock code waiting) and have not yet flashed Hard-SPL. My phone has Bluetooth for Windows Mobile Version 1.9.2 Build 600 HCI Version 4.84. I'd do anything at this point to get this working. Windows Mobile is not that precious to me either. PLEASE HELP!
e-thug said:
Ok, so I finally got into the smartphone game to get a better music streaming experience. MFRadio and MFScorn just weren't cutting it for me anymore. I hated the skips and the ridiculously long (and repeated) buffering time. So I first looked at Android phones but went with WinMo because they say you can run both OS's with WinMo (and the only Android offering from AT&T has a 12-hour standby time before the battery dies, according to reviews).
I have a Bluetooth head unit and have had over a dozen phones paired with it. This phone however is a completely different story. I have installed the latest "release" from AT&T (from a thread on this site). At first I tried streaming with the bundled Windows Media Player which apparently doesn't stream anything at all (with both the bundled and downloaded releases of the OS), then downloaded TCPMP. TCPMP is everything I have ever dreamed of in a streaming media player, but the only problem I have with it is that it won't connect to a stream unless I have already opened up a browser window and went to a website. Not the end of the world.
So, I get in my truck and initiate pairing to the phone. It sees the head unit as a Hands-free and as Stereo Audio. I can get it to connect for a split second and then it dies. I get a popup notification that tells me that the phone cannot control volume when paired to the bluetooth device and audio must be adjusted from the device itself. Fine. But then it doesn't work at all. At first, I wanted to blame TCPMP until I realized that nothing at all was working with the head unit. I think I got it to work once but it never worked again.
So is there any way to fix this problem? This is the one thing I wanted working on my new phone. Yes, the notifications that my texts were successfully sent are very annoying (as well as the other notifications), and yes, Windows Media Player for Mobile is useless, but the fact that I can't stream Bluetooth audio on this phone really makes this phone worthless to me. Didn't anyone bother testing this stuff before releasing this garbage? The Tilt is a paperweight to me right now because it can't do the one thing I want it to do the most. I might as well go back to my Sony Ericsson W760a at this point!
What can I do? I have not yet unlocked anything (although I have a SIM unlock code waiting) and have not yet flashed Hard-SPL. My phone has Bluetooth for Windows Mobile Version 1.9.2 Build 600 HCI Version 4.84. I'd do anything at this point to get this working. Windows Mobile is not that precious to me either. PLEASE HELP!
Click to expand...
Click to collapse
Hmmmm .... I don't believe you ever stated what type of headset you are trying to get working here? I find your problem to be very strange, even though WinMo does seem to be lacking in a lot of different areas, audio streaming via bluetooth stereo headset is definitely not a problem I have encountered. It even streams flawlessly through my 5.1 hooked to my pc via a crappy 8 buck bt dongle and still sounds excellent. Have you considered that the problem may lie with your bt headset itself?
Also, when you say that you installed latest "release" from AT&T (from a thread on this site), what exactly do you mean? I am running the "unofficial" leaked rom from AT&T on mine and I just paired my Motorola S9 stereo headset and it is playing great for me. You also may want to try using some different software, give S2P (Slide 2 Play) a try and see if you have different results. That's what I am using right now, but I have used TCPMP to play a few xVids through my headset and have had no problems.
The problem is not in the head unit. 25 other phones can't all be wrong. I have no problem using my bluetooth headset. That is probably why you don't see the problem. Anything more complex than a headset will not work with this release. The problem lies within the phone as soon as it displays a notification (which, of course I cannot disable) which reads, "The connected Bluetooth headset does not support volume adjustment from the device. Adjust volume on the headset itself."
That message is the kiss of death. So basically any Bluetooth head unit will not work with this phone? Sounds like shoddy programming to me. Yes, I am using the "leaked" release. I really don't think this release will ever see the light of day. Its horrible! You cannot disable notifications (I don't need to know when my text messages were sent successfully), and it looks like whenever I get a system notification, any program I am using crashes immediately. Like I said before, as soon as I get a notification, I lose the Bluetooth connection (which is like a split second before the notification comes up). I highly doubt this "leaked" copy will ever see the light of day, officially (unless AT&T and HTC do absolutely zero testing on it).
A little clarification for those who don't know... when I say "head unit" I'm talking about a Bluetooth-enabled car stereo and when I say "headset" I mean a Bluetooth headset
My Tilt 2 works absolutely fine with all my BT devices, including 2 Motorola headphone sets and my Sony Xplod head unit in my truck.
e-thug said:
A little clarification for those who don't know... when I say "head unit" I'm talking about a Bluetooth-enabled car stereo and when I say "headset" I mean a Bluetooth headset
Click to expand...
Click to collapse
I was mis-understanding you about the head unit, I did think you were talking about a headset. Sorry bout that, my Mustang doesn't have built-in BT so I have to use a Motorokr t505 for those chores. It works well but it does give me the same message that you are getting about "volume can't be cotrolled etc" but I can dismiss it and carry on without any problems.
but the fact that I can't stream Bluetooth audio on this phone really makes this phone worthless to me. Didn't anyone bother testing this stuff before releasing this garbage? The Tilt is a paperweight to me right now because it can't do the one thing I want it to do the most. I might as well go back to my Sony Ericsson W760a at this point!
Click to expand...
Click to collapse
Since you don't need your phone for calls, just get Sirius or XM. Ya know, considering you only stream music through the phone..
Did you try the BT headset or head unit with the original stock ROM before you flashed the "leaked official" ROM?
Seems like you might have a couple random issues, with the BT issues and the system notifications crashing programs. I haven't flashed the leaked ROM, but I do know that many random issues with cooked ROMs can often be cleared up by running Task29, which completely wipes the phone memory before you flash a new ROM. I think you will need to HardSPL before you run Task29. Might be worth a try, sometimes fragments of the old ROM interfere with the new one, and cause some bugs.
Bluetooth protocols can be implemented differently by different manufacturers.
I know of many people including myself who have NO PROBLEM with the tilt 2 and different Bluetooth products INCLUDING car radios.
I am using the "new" AT&T ROM and have no difficulties.
Clearly your pissed but your subject is wrong. I would suggest changing to "Worthless as $HIT to ME"
I think my problem is that I am getting notifications which seem to be killing my connection. Is there a way to turn all notifications OFF? The only ones I care about are missed calls, incoming SMS and maybe a birthday. I would like to try to kill the notifications first because I think this may solve my problem
You can get yourself a free reg editor (like Total Commander) and apply the following tweaks to modify the notifications:
SMS sent notification: http://www.mydigitallife.info/2008/06/24/enable-or-disable-the-sms-text-message-sent-notification-bubble/
Other notifications: http://www.mydigitallife.info/2008/06/24/tweak-and-configure-how-notifications-work-in-windows-mobile-notifications/
Although, this sounds like a band-aid just hiding a deeper problem. What you are describing is not typical behavior, and this is something else going on.
redpoint73 said:
You can get yourself a free reg editor (like Total Commander) and apply the following tweaks to modify the notifications:
SMS sent notification: http://www.mydigitallife.info/2008/...he-sms-text-message-sent-notification-bubble/
Other notifications: http://www.mydigitallife.info/2008/...cations-work-in-windows-mobile-notifications/
Although, this sounds like a band-aid just hiding a deeper problem. What you are describing is not typical behavior, and this is something else going on.
Click to expand...
Click to collapse
Thanks I will try these out and report back
For the record my head unit is a JVC KD-BT11 and I have never had any kind of problem pairing any other phone
Somebody else just posted a very similar issue, and found the app hAndyUtils to be helpful:
http://forum.xda-developers.com/showthread.php?t=741311
I think hAndyUtils might just be a app-based way to make the reg edits I posted earlier. But give it a try.
I scanned through the topic and did not see anyone mention this so I thought I would add my .02. The Tilt 2 is different than many other WM phones when it comes to bluetooth as it contains the Widcomm BT stack instead of the MS stack. (Just as an aside, on all my past phones, there were people bemoaning the the fact that it had MS, and trying to replace it with the Widcomm, so I am getting a real chuckle out of folks complaining about the Widcomm and wishing for MS )
In any case, the utilities (Blue music toggle etc...) that used to work for me to toggle between streaming in stereo and plain phone qulity no longer work. However, all my stereo headsets (I own three different brands/pairs) all work perfectly with the Tilt 2. And stay connected and streaming all day.
By the way, coming on a forum that is full of people helping each other and using profanity, anger and threats, is not the most conducive way to get your questions answered. The odds are that the problem you are having is already solved somewhere among the 6+ million posts in this forum. I do not know where or I would post it for you, but it is probably out there. Good luck. And if you find it, please post the link to the answer back here so that other serchers will find it too.
maybe it can come from the phone itself
i had a rhodium for almost a year and never got my motorola headset ht820 to work well enough for me to use it... (more skips than music...cant move my head without a skip)
i flashed to a NRG rom before trying my headset...i tried eveything as far as ref setting, different radios...even flashed my ht820...
no improvement...
then my phone fell in water not so long ago...got another rhodium same model (european)...and it worked perfect out the box on stock rom i can go in a different room than my device and still hear music with no skips...and it still does with nrg rom and latest radio...
so my guess is maybe some actual devices have bad bluetooth hardware ???
I have the Motorola S9 and the HT820 and both work absolutely fine on my Tilt 2.
yatrg said:
I scanned through the topic and did not see anyone mention this so I thought I would add my .02. The Tilt 2 is different than many other WM phones when it comes to bluetooth as it contains the Widcomm BT stack instead of the MS stack.
Click to expand...
Click to collapse
Can I change my Bluetooth stack to MS? I have installed Hard-SPL and have experimented with cooked ROMs to no avail.
I sent the phone back to AT&T, went to Trinidad & Tobago for a few weeks and came home to a new Tilt 2 waiting at my doorstep (which could have been stolen by anyone!) and I am still having the same problem. So I guess I sent back a perfectly good phone!
I would love to try some different Bluetooth stacks if possible. Where do I go from here?
e-thug said:
Can I change my Bluetooth stack to MS? I have installed Hard-SPL and have experimented with cooked ROMs to no avail.
I sent the phone back to AT&T, went to Trinidad & Tobago for a few weeks and came home to a new Tilt 2 waiting at my doorstep (which could have been stolen by anyone!) and I am still having the same problem. So I guess I sent back a perfectly good phone!
I would love to try some different Bluetooth stacks if possible. Where do I go from here?
Click to expand...
Click to collapse
Did you ever try the solution in this thread? It fixed a lot of issues people were having with bluetooth car kits. Maybe it will work for you: http://forum.xda-developers.com/showthread.php?t=591322
The solution source is here: http://www.everythingwm.com/forum/moto-q-9c/q9c-and-infiniti-g35x-bluetooth-problem-16833-4.html
And here is the solution. You need a registry editor to do this:
1. Modify the HandsFree plug-in:
HKLM\Software\WIDCOMM\Plugin\HandsFree
i. Change SupportedFeatures to 45 (default is 1135)
ii. Add value HFBDA binary, set to same value as LastConnectedBda
iii. Add value HFDeviceType decimal 2
2. Modify the WIDCOMM bluetooth general settings:
HKLM\Software\WIDCOMM\BtConfig\General
i. Change bdaddr to (no value)
ii. Change (or add if not there) DisableReopenAudio to 0 (default is 1)
3. Reboot device
You may also want to do the A2DP quality registry edit: Add a DWORD value of LineSpeed to HKLM\Software\WIDCOMM\Plugin\AV\ with a value of 320.
Give it a try, it may work for you.
I will give this a try and report back. Thank you very much for the response!
No luck. And my bdaddr keeps resetting to a binary value when I reset the phone

Bluetooth Connectivity With My Car

After searching this forum there is no thread on Bluetooth issues connectivity.
For a wile now i been searching the net and different sites for a fix between my phone and my car bluetooth. Before the epic i had a windows phone and the connectivity was fine including all the phonebook would load up and everything the system was build to do. With Android Epic i been having issues. Sometimes I cant connect to the car and other I am able to connect but phonebook wont load.
With all the Geniuses in the website i am sure someone can come up with a fix.
I figured i open this thread hoping we can find a final fix to retire this problem.
If it helps I am running the latest Viper Rom with Genocide kernel at 1.2ghz
However the rom did not change the statues of my issue.
Any help would be appreciated.
Thanks
I also have connectivity issues with bluetooth, in my case the car has A2DP allowing for music to be played over the car's stereo. It cuts out so much that it is completely useless for music. I mostly listen to podcasts but Pandora would be nice. However it cuts out so much that it isn't worth it. So if anyone does have a solution. To me though I've tried so many kernels, and roms to no avail that I'm pretty sure taht the software Samsung has shipped has faulty drivers. By the way it also seems that the cut outs occur when switching towers, however I could be wrong.
I use this in my car: http://us.kensington.com/html/14484.html
It may cut out every 45 seconds or so but it's the only thing I've used. Got it on sale for $20.
I've got a pair of a2dp bluetooth headphones that I use to listen to podcasts via my Epic. I've had zero problems with those (using DK28 atm, for the record). So I don't think there's a hardware problem with the Epic's bluetooth.
If we're going to get some troubleshooting done, we should get a bunch of details from everyone. Like exactly what bluetooth hardware they're using, and what roms they're running.
thezero4 said:
I also have connectivity issues with bluetooth, in my case the car has A2DP allowing for music to be played over the car's stereo. It cuts out so much that it is completely useless for music. I mostly listen to podcasts but Pandora would be nice. However it cuts out so much that it isn't worth it. So if anyone does have a solution. To me though I've tried so many kernels, and roms to no avail that I'm pretty sure taht the software Samsung has shipped has faulty drivers. By the way it also seems that the cut outs occur when switching towers, however I could be wrong.
Click to expand...
Click to collapse
Does everything cut out, or just Pandora? If it's just Pandora and other apps that need data connection, it might not be a bluetooth problem as much as a data connection problem.
I would suggest testing it by trying the car bluetooth with something that requires no data connection at all, like pre-downloaded podcasts.
I am talking about connectivity issues with in stock car bluetooths.
this problem is big many people been having this issue and there is a list of stock bluetooth cars that android wont pair with. I had the touch pro 2 for sprint with windows system and it worked fine in my car bought the epic and there we go. Now looks kind of bad that i would need to get an aftermarket piece to listen to bluetooth calls and load up the phonebook from android to my car.
Windows got it right even though i would never go back to a windows phone so i know there is something that android messed up here
Below i will put some links to show you how there is A LOT of people that been having this issue.
http://code.google.com/p/android/issues/detail?id=3960
http://www.google.com/#q=android+bl...start=0&sa=N&bav=on.1,or.&fp=3f40f95b1b9c7c0d
I have a 2006 Dodge Durango. It has Bluetooth. My old phone, a Samsung flip phone would connect without issue. My new phone, a Samsung Captivate, will connect most of the time, but often times, once it connects, it drops the call.
I understand this is an Epic thread, but I thought I would add my input as I am having similar problems (and this came up on my search).
If I understand you correctly, you connect some of the time and sometimes not.
Regardless, if your phone is rooted you might wanna try this.
I had a lot of issues with my bluetooth after upgrading to froyo and tried a lot of fixes including wipe3x and odin to stock....this is the one that worked for me.
http://forum.xda-developers.com/showpost.php?p=12120496&postcount=1392
Ensure that you first
- delete the car from your phone,
- delete the phone from your car,
- disable bluetooth,
- delete the file,
- CHANGE YOUR BLUETOOTH DEVICE name,
- restart,
- reenable bluetooth
- re-pair your phone with the car.

[DEV/Closed] TYTUNG Kernel's Compatible Bluetooth Headsets List [tytung_r9 kernel]

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.

[Q] A2DP bluetooth autoconnect immediately disconnects?

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!

[Q] TW vs. AOSP Bluetooth

I have been running SkyNote 8.2 for a while now and have really liked Sean's ROM. I flashed Liquid last week (also a great ROM) and noticed something that I found confusing. With the TW Bluetooth (including the stock ROM), my 2009 car didn't really react well to the Bluetooth in my Note II. The connection between the car and phone would constantly connect and then drop off, connect again then drop off. Once I was on the phone (call), after initialing disconnecting me, the connection would stay but once I hung up it would go back to the on off cycle. My contacts would not sync either and yes I did grant access to the contacts. I just assumed it was because the phone has a newer Bluetooth profile (4) than my car (3). But after flashing Liquid my Bluetooth connection was fine, never dropped off and my contacts were all visible. I don't know much about the inner workings of Bluetooth, is the difference a TW thing?
Just looking for some insight from folks smarter than me.
Bump.... I would also like to know
AOSP only has Bluetooth 3.0 right now, so that's probably why you get more information. I have a FitBit and it only works with TouchWiz since it uses Bluetooth 4.0.
This is a fairly well known issue, but I haven't see a good summary anywhere, so I'll try here.
The problem isn't so much TW vs AOSP, it is Jellybean versions 4.1.x vs 4.2.x. Touchwiz is 4.1.2 and most maintained AOSP ROMs are 4.2.x.
Google, though their ultimate wisdom, decided to effectively castrate 4.2 by switching the Bluetooth stack.
From Android.com
New Bluetooth stack
Android 4.2 introduces a new Bluetooth stack optimized for use with Android devices. The new Bluetooth stack developed in collaboration between Google and Broadcom replaces the stack based on BlueZ and provides improved compatibility and reliability.
Click to expand...
Click to collapse
So...
Jellybean versions 4.1.x use the opensource BlueZ stack
Jellybean versions 4.2.x use the quasi-opensource Broadcom/Google stack called Bluedroid,
4.2.x has documented issues with audio streaming which are attributed to A2DP, or the Advanced Audio Distribution Profile. Google has proposed a fix, but the community consensus is that the issue remains.
Another problem with 4.2.x is that it doesn't support AVRCP 1.3 like 4.1.x did. This means that track metadata is not available to devices on 4.2. This is bad for me since I like to see track information when I connect the phone to my BMW M3.
I'm sure there are some workarounds on this problem, but I am not aware of a single, silver-bullet solution to make BT work flawlessly on 4.2.x Roms.
In summary, if you want to use Bluetooth in any meaningful way, stick with 4.1.x builds until Google gets their **** together. This is a fairly large miss on their part and they have been slow to address it.
Anyone know of any updates to this? There are so many 4.2.x ROMs out there that i love, but without a good BT A2DP connection, i just cant use that as the regular ROM.
ZoinksS2k said:
In summary, if you want to use Bluetooth in any meaningful way, stick with 4.1.x builds until Google gets their **** together. This is a fairly large miss on their part and they have been slow to address it.
Click to expand...
Click to collapse

Categories

Resources