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

Status
Not open for further replies.
Search This thread

tytung

Senior Member
Jun 21, 2010
3,574
15,005
0
sites.google.com
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
 

Attachments

  • initrd.gz_logwrapper_for_r8.1.zip
    199.9 KB · Views: 27
  • initrd.gz_logwrapper_for_r8.2-r9.zip
    199.9 KB · Views: 72
Last edited:

clio94

Senior Member
Jan 17, 2007
1,195
321
0
Kozani
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.
 

tytung

Senior Member
Jun 21, 2010
3,574
15,005
0
sites.google.com
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

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.
 

arifqur

Senior Member
Nov 12, 2005
3,603
1,036
243
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
 

f1ux

Senior Member
Jan 2, 2011
593
102
63
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!
 
Last edited:

daheufster

Senior Member
Mar 15, 2006
690
88
58
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
 

daheufster

Senior Member
Mar 15, 2006
690
88
58
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

side note:
a German driving a French car???? hmm :confused:
 

trilu

Senior Member
Apr 17, 2008
68
108
0
munich
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....
 

tyween

Retired Recognized Developer
Sep 12, 2010
1,135
2,706
0
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 :D

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.
 
Last edited:

felipemadox

Senior Member
Jul 13, 2009
530
56
0
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)
 

mzebrowski13

Senior Member
Jun 23, 2010
387
58
0
Warsaw
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)

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
 
  • Like
Reactions: felipemadox

tytung

Senior Member
Jun 21, 2010
3,574
15,005
0
sites.google.com
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

No idea how to port/use that modded BT stack to a CM7 rom.
 

tytung

Senior Member
Jun 21, 2010
3,574
15,005
0
sites.google.com
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!

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?
 

tytung

Senior Member
Jun 21, 2010
3,574
15,005
0
sites.google.com
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....

My bcm4329.hcd file has 17,684 Bytes and comes from Nexus One Gingerbread OTA.
 

tytung

Senior Member
Jun 21, 2010
3,574
15,005
0
sites.google.com
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 :D

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.

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.
 

tyween

Retired Recognized Developer
Sep 12, 2010
1,135
2,706
0
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)

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.
 
Last edited:

tytung

Senior Member
Jun 21, 2010
3,574
15,005
0
sites.google.com
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)

As mzebrowski13 said, I guess it's a hardware issue.
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 9
    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
    2
    Will this help solving the stereo Bluetooth thing on sense?

    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.
    1
    Will this help solving the stereo Bluetooth thing on sense?
    1
    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)

    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
    1
    Hi Tytung,

    Just tested all kernels:
    tytung_r9_beta
    tytung_r8.3
    tytung_r8.2
    tytung_r8.1

    they all work here BT Headset, A2DP, AVRCP, OPP/OBEX and HSP, PBAP
    BT headset: Sennheiser
    Laptop: HP
    Rom is UD
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone