Which builds currently have Bluetooth working? - Touch CDMA General

I did a search in here but there are so many results...
I have been playing with the 1.5 build DZO posted on his page. Bluetooth seems to work, but I am having a hard time synching my contacts. Anyone know other builds with functional Bluetooth?

have u tried to
is ur data the problem or is it just ur contacts?

I actually got the contacts synched after a bit of tinkering. Still, I am wondering what other builds have the working bluetooth. I am assuming this is a different beast than the xROMs of a few months ago as it was taken directly from DZO's site.
Does that mean limited bluetooth drivers have been developed for the touch? I was playing around with mine tonight and it was working. If I can have bluetooth on say a 1.6 or a 2.x version of Android, then I may really give up win-mo for good.

yea
I dont believe there is a working 1.6 or 2 with bluetooth.. for now at least. Ur best bet is that build. Its also one of the fastest (if not the fastest) and stable around.

lgevo said:
I dont believe there is a working 1.6 or 2 with bluetooth.. for now at least. Ur best bet is that build. Its also one of the fastest (if not the fastest) and stable around.
Click to expand...
Click to collapse
I'm pretty sure a 1.6 build (like Donut AOSP by plemen) flashed on NAND with dzo's latest kernel will have bluetooth enabled...along with GPS and usb headset audio

Related

What are the Differences between 1.5, 1.6, 2.0, 2.1

What Is the Difference between each of these? I would like to know why I would want to upgrade from 1.5.
Oh boy.. lol.
1.6 and up do qvga resolution very well, but do not have working bluetooth yet
2.0 and up don't sleep properly because of the audio driver (which we are working on) unless you use a hacked kernel (which I don't recommend) and have a newer interface/livewallpapers etc..
I would suggest to try donut for now if you're thinking of upgrading.
dzo committed a change the other day that supposed to enable bluetooth in 1.6 - i didn't test it with a headset but I was able to pair it with my pc. Although no one has posted a build with that change included yet.
If that helps.
mrkite38 said:
dzo committed a change the other day that supposed to enable bluetooth in 1.6 - i didn't test it with a headset but I was able to pair it with my pc. Although no one has posted a build with that change included yet.
If that helps.
Click to expand...
Click to collapse
Do you have a link to that. Where did you read that? I would like to check it out.
http://androidhtc.git.sourceforge.net/git/gitweb.cgi?p=androidhtc/bootenv.git;a=summary
It's currently the most recent commit.

Using HD2 Headset remote with Android ROM

Searched but can't find an answer.
How does every one else dealing with this situation? Is there a work around to make the remote button work with different Android builds?
Would it work if I use a matching OEM headset? For example, get the OEM EVO headset to use with EVO based build?
what is it ur specifically trying to do
hey what is it u wanna do bc I have the desire build and I use the headphones that came with my hd2 to control my music thats about it u can do with it and u know the basic use it to talk and what not but even than u have to have winamp installed on ur phone which u can get from the android market for free or it also works as a music controller on the htc music on android idk if it works for the other builds tho, hope this helps
Try the headphone come with iphone, it,s work!
silvscorp said:
How does every one else dealing with this situation? Is there a work around to make the remote button work with different Android builds?
Click to expand...
Click to collapse
What are you talking about? Headsets have been working properly almost since the start of Android porting.
Fedr0 said:
What are you talking about? Headsets have been working properly almost since the start of Android porting.
Click to expand...
Click to collapse
I think he means for controlling music. It may be a non-sense build issue. My original HD2 headset buttons don't work for skip forward, back or play/pause. This is on Bangsters V1.5. My bluetooth headset does work for these functions though. When I used desire builds the headset buttons would work, but only if the screen was on.
trmacdonal said:
I think he means for controlling music. It may be a non-sense build issue.
Click to expand...
Click to collapse
That's strange, I've never had that problem and I never use Sense builds. This with the screen either on or off, it doesn't make any difference.
Anyone solved this problem after NAND builds were released?
Somehow I managed to get my headset working just after flashing new build, but next morning I found no music control from headset whatsoever. Really annoying this is because I use them a lot when I go to work or enywhere else :/
npocmo said:
Anyone solved this problem after NAND builds were released?
Somehow I managed to get my headset working just after flashing new build, but next morning I found no music control from headset whatsoever. Really annoying this is because I use them a lot when I go to work or enywhere else :/
Click to expand...
Click to collapse
yes me too and I have found any solution the call/answer button enable only Voice Recognition and the (next/back) button enable nothing
@npocmo: I think that dosent work with the desire HD build portage. Did you tried with a nand Desire ?
i flashed MDJ's CyanogenMod 7 v. 2.6 [A2SD+][GRH78C][RMNET][Kernel: MDJ S10.4 OC] and face the same problem.
is there any solution?
wow this thread is so old !! has anyone found the solution ? i flashed [Feb 02][DL DesireZ v3.4][DL Data2SD/Ext4 v2.7][Nand/SD/MAGLAR] yesterday and have the same problem, the remote doesn't do anything other than make the music player go crazy. solution please ? should i try with another android build ?
I have the same problem with this build!
actually these devs were saying that it was infact gingerbread who wasnt supporting the headset controls.. but now most of them do.. only thing you can do is thoroughly search the build thread to make sure that they work before flasshing them unto your phone so you know exactly what your getting into
Try changing kernel to gauner
Yes, the problem on kernel mdj.If you change kernel on to gauner it will works.
soberlam said:
i flashed MDJ's CyanogenMod 7 v. 2.6 [A2SD+][GRH78C][RMNET][Kernel: MDJ S10.4 OC] and face the same problem.
is there any solution?
Click to expand...
Click to collapse
I changed the kernel and it working
Can someone explain how to fix it? I did not understand..
I have on my Leo's -= MDJ CyanogenMod 7 v. 2.6 [+ A2SD] [GRH78C] [RMNET] [Kernel: MDJ S10.4 OC]. Excuse my English but I'm Italian
Anyone can help me?
mylove299 said:
I changed the kernel and it working
Click to expand...
Click to collapse
so can i use NAND MDJ but use gauner kernel ?
How do I change only the kernel? without losing data?
where can i get gauners kernel please

[Q] AVRCP doesn't work on none Sence ROM's

Hi all,
I wonder why no one is asking or investigating the AVRCP issues on ROM's without Sense? It looks like something is missing in those roms that can be found inside Sense ones.
The bt call function is working as designed but play/pause/next/prev doesn't.
Any ideas?
The issue is that HTC have used their own bluetooth stack in their Sense based roms.
This stack supports the features that you are talking about.
Unfortunately, stock roms use a different stack which do not have the same features as the Sense stack.
This isn't an issue only on the HD2.
Can we get that stack and put it to nonSense roms?
AVRCP has been working on every CM6 build I've tried until recently. Just over the last week or so since I've updated to more recent nightlies I've found its stopped working. I'm currently using ginger_hd2 and it doesn't work. Also the mdj aosp gingerbread doesn't work and mdj streak ram v0.5. All the builds I've tried today!
I was using passion nightly 270 (or bravo, can't remember) and that worked fine.
Sent from my HTC HD2 using XDA App
Never worked for me since I tried HyperDroid and other roms.
I'm going to revert back to my old build later today to see if it still works. I thought it might be a problem with my headset as I dropped it the other day but I tested it last night with Windows Media Player on my PC and it worked OK, switching tracks, play, pause, etc.
Will let you know how it goes.
Sent from my HTC HD2 using XDA App
OK - It definitely works with my previous build.
This build is based on the Passion nightly CM6.1 v270
As I say, I've had it working on pretty much every build since the beginning of Android on the HD2 - it's only stopped working on the Gingerbread-type builds.
ie. It doesn't work on MDJs actual 2.3, or the Ginger_HD2 based on 2.2.1 with Gingerbread-style notifications, etc.
I can't work out if it's coincided with me using builds which have the newer initrd.gz...
Let's hope someone who knows about this stuff reads this thread!
What is this build with CM 6.1? Can you link it?
http://www.multiupload.com/FQCU3UV070
Try this... this one's based on 293 nightly.
Mine was a hybrid I kinda created myself using michyprima's nightly build v4, then incorporating the passion 270 files. If you look at this thread:
http://forum.xda-developers.com/showthread.php?t=824601
It'll explain how to do it...
OK, well I did some trying to fix it using MDJs Gingerbread v0.8 but no joy.
I tried replacing the three bluetooth libraries (libbluedroid.so, libbluetooth.so and libbluetoothd.so) with the working ones from my build but that didn't work.
I also tried replacing the AudioBTID.csv file as it had some slight changes and whilst it didn't fix the issue, it doesn't seem to have broken anything.
I'm currently looking at the bluetooth conf files in /system/etc/bluetooth to see if there's any differences there... think we need some dev help on this one though - I'm pretty much at the limit of what I can do....
Nope, no difference in the conf files. Also changed over the two .so files in /system/etc/lib/bluez-plugin
Again, this didn't work but didn't seem to break stuff!
That's bad. Even Sense roms has problems with media controls profile such as connecting automatically to Phone Audio only.
I feel like 1 from 1000 use it, so nobody cares
Just in case anyone finds this thread again...
MDJs NAND CM7 builds now have AVRCP working again. If you want a build without sense but with this working I suggest you try them! I'm a happy camper again!
Sent from my HTC HD2 using XDA App
Any updates on AVRCP on our devices? I am on CM7 (BoyPPC HoneyComB v31), and AVRCP does not work Do the GB sense ROMs have AVRCP capability?
I tested a few SD ROMS and AVRCP works with:
RAFDROID_HD_SD_4_2 (Sense)
AmeriCanAndroid (Gb)
JaguarMIUI-V11 (Gb)

ASOP Bluetooth Driver in Sense ROM

Been lurking around this forum for a few months now, but only decided to post now, lol.
So we all know that the bluetooth drivers for ASOP and Sense ROMs are from different. There are quite a few threads on this forums and others regarding the issues that people have with the Sense BT driver, which range from low quality audio output to inability to pair with certain devices.
The problem that I have with all the Sense ROMs (from the older MikFroyo to the newer Synergy Sense ROMs and MikG) is that the BT connection between my phone and my car (an 09 BMW 3-series) continuously drop and reconnect whenever the phone attempts to transfer the contact list to the car. But in all the ASOP roms I have tried (CM7, Deck, SalvageZen), the phone and car paired perfectly and all the contacts transferred to the car without any issue.
I attempted to fix this issue myself. So I simply switched the bluetooth.apk file in system/app folder of the downloaded zip file for the Sense ROM with the one from CM7. And I also replaced bluetoothd file in system/bin and all the .conf files in system/etc/bluetooth with CM7 counterparts. This actually worked with the older Froyo based Sense ROMs, namely MikFroyo, which I used for the longest time.
However, when I tried to same thing with newer GB-based Sense ROMs. This method no longer work. The phone either drop connection and reconnect repeatedly like before (which was seen with Synergy, Kingdom, Virus's ROM). Or the bluetooth can't be turned on at all as in MikG ROMs (which I suspect is because the conflict between the apk and odex files).
Anyway, I am just wondering anyone can take a look into this problem and see if there is a way to replace the Sense driver with the ASOP one. I think this would solve the majority of BT that people are experiencing with all the sense roms.
Need some help here, bump!
As I understand it, you can't just replace the BT stack in a Sense ROM with the stack from an AOSP ROM because they're too integrated into the frameworks.
Also note: A-O-S-P = Android Open Source Project. ASOP wrote fables. (I know, I know, don't bother pointing out the misspelling.)
Well I figured that the BT stack is integrated into the frameworks. And I didn't really expect that simply replacing some files from AOSP stack can work in froyo based sense ROM. But it did work nonetheless.
So I figured it probably won't be too difficult to replace the BT stack in the GB based sense ROM. Maybe someone with experience can change framework a little to make this work.
shameless bump
guess no one cares enough...
No, it's not that nobody cares. It's that it wouldn't be that easy. I know you said you just dropped a few files in and boom, AOSP BT stack on FroYo. I'm not saying your wrong or making it up...but several people have tried swapping the AOSP stack in and weren't successful. It might have still worked, but it wasn't the AOSP stack (i.e., A2DP still sounded like crap). I really don't think it's as simple as just swapping a couple files, though that doesn't mean it's impossible either.
Cloud9Blue said:
guess no one cares enough...
Click to expand...
Click to collapse
Or maybe people who want AOSP Bluetooth are just using an AOSP ROM.
If you get this to work definitely let me know. I've been looking for the same thing.
swapping the kernel + .so modules may do the trick
arent the bluetooth drivers in the kernel? or as separate .so modules? how about someone trying swapping the kernel in addition to the modules.
The bluetooth stack is in the kernel. You can not use an AOSP kernel on a Sense ROM so that will not help you.
You may want to check out the Freedom kernel. This is a Sense Gingerbread kernel by lithid. He is in the process of swapping out the bluetooth stack for the AOSP stack. The kernel itself is pretty stable but the BT stack work is still very early in development. He wants to be able to support bluetooth controllers (like the PS3 and Wii) but this may also solve the problems that you are having.
The test version with the AOSP stack is Test v0.9.5 and the discussion starts in the middle of page 289 of the thread.
hootnath said:
arent the bluetooth drivers in the kernel? or as separate .so modules? how about someone trying swapping the kernel in addition to the modules.
Click to expand...
Click to collapse
Thanks for the suggestion but this doesn't work. I tried exchanging all of the related bluetooth files with the ones in Deck's rom.
---------- Post added at 05:49 PM ---------- Previous post was at 05:48 PM ----------
m20120 said:
The bluetooth stack is in the kernel. You can not use an AOSP kernel on a Sense ROM so that will not help you.
You may want to check out the Freedom kernel. This is a Sense Gingerbread kernel by lithid. He is in the process of swapping out the bluetooth stack for the AOSP stack. The kernel itself is pretty stable but the BT stack work is still very early in development. He wants to be able to support bluetooth controllers (like the PS3 and Wii) but this may also solve the problems that you are having.
The test version with the AOSP stack is Test v0.9.5 and the discussion starts in the middle of page 289 of the thread.
Click to expand...
Click to collapse
Hopefully this works. Thanks for the heads up!
Unfortunately the kernel did not solve me issue. I tried to combine the kernel with the zip mijjah74 created but this didn't work either. I think lithid-cm is on to something with the kernel, but I think modding the kernel isn't enough. I think the AOSP Bluetooth files have to be incorporated some way.
jpflaw00 said:
Unfortunately the kernel did not solve me issue. I tried to combine the kernel with the zip mijjah74 created but this didn't work either. I think lithid-cm is on to something with the kernel, but I think modding the kernel isn't enough. I think the AOSP Bluetooth files have to be incorporated some way.
Click to expand...
Click to collapse
Basically, yes. Lithid-cm is going to try to integrate the ASOP bluetooth stack into the next version of his kernel. The current 0.9 version does not include any kind of support for the ASOP stack and you are advised not to attempt the swap yourself. It requires code changes to the kernel and is not as simple as swapping the .so module.
MultiDev said:
Basically, yes. Lithid-cm is going to try to integrate the ASOP bluetooth stack into the next version of his kernel. The current 0.9 version does not include any kind of support for the ASOP stack and you are advised not to attempt the swap yourself. It requires code changes to the kernel and is not as simple as swapping the .so module.
Click to expand...
Click to collapse
Sounds good. I know that swapping files randomly wouldn't work but I decided to try it anyways. Thanks for the reply.
I'm still working on it. This is a first since currently I have not seen any other sense kernel with an aosp modified bt stack. Let's hope I can figure it out. Boy I would love to play emulations with my ps3 controller over hdmi.
Sent from my PC36100 using xda premium
lithid-cm said:
I'm still working on it. This is a first since currently I have not seen any other sense kernel with an aosp modified bt stack. Let's hope I can figure it out. Boy I would love to play emulations with my ps3 controller over hdmi.
Click to expand...
Click to collapse
I wish you the best of luck, but one thing at a time buddy
getting a ps3 controller to work is also going to require enabling usb-host in the kernel too(right? or do we need a dongle to do that like other phones?) as well as finding a male mini usb to male micro usb cable (do they make those?), as a ps3 controller has to be paired over USB before working wirelessly.
Honestly I don't understand what HTC did to muck up BT so badly. If everything works in plain ol' AOSP android then what the hell did they do to cripple it?
lithid-cm said:
I'm still working on it. This is a first since currently I have not seen any other sense kernel with an aosp modified bt stack. Let's hope I can figure it out. Boy I would love to play emulations with my ps3 controller over hdmi.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Thanks for taking on the challenge. Hopefully you can get this working!!

[Q] Bluetooth update for Jaguar DHD

Hi,
I´m using the Jaguar DHD Image on my HD2 WM6.5 for a long time.
It works very well.
The only problem that I have is that sometimes I get a connection with my Bluetooth devicese and somtimes not. Then I have to switch blutooth off an on a sveral times.
Is it possible fix this problem?
Bluetooth update for Jaguar DHD
This post is just 1 day old and 144 clicks.
I think there are more people who have the same problem.
Is it posible to contact Jaguaralani direct?
My build is an SD Build WM 6.5
Kernel 2.32.15_r9-gd0fb339
tytung
Build No 1.83.415.4 JaguaralaniDHD-ARA
It would be nice to get some help.
Thanks
Tar_zan said:
This post is just 1 day old and 144 clicks.
I think there are more people who have the same problem.
Is it posible to contact Jaguaralani direct?
My build is an SD Build WM 6.5
Kernel 2.32.15_r9-gd0fb339
tytung
Build No 1.83.415.4 JaguaralaniDHD-ARA
It would be nice to get some help.
Thanks
Click to expand...
Click to collapse
Try a different build. Bluetooth is worrking well on every rom i have tried, both nand and sd builds.
Bluetooth update for Jaguar DHD
Hello evilbarcode,
bluetooth is working on my device ,too.
But the "autodetect" is not working stable.
Sometimes it connects automaticly sometimes you have to start bluetooh several times or push the connect bottom a few times.
So on other builds there is no problem, you switch bluetooth on...and the devices are conected.
Tar_zan said:
Hello evilbarcode,
bluetooth is working on my device ,too.
But the "autodetect" is not working stable.
Sometimes it connects automaticly sometimes you have to start bluetooh several times or push the connect bottom a few times.
So on other builds there is no problem, you switch bluetooth on...and the devices are conected.
Click to expand...
Click to collapse
Yes, that is correct. I've recently installed a sense 3.5 nand build, but when I first put android on my hd2 (about 2 months ago) I used sd builds and I am pretty sure my bluetooth devices connected straight away (after I had connected them the first time). If your keen to stay on sd builds try this one. It was the first sd build I used, an older version but still good. Should be much better now though.
Cheers,
Evil.
Bluetooth update for Jaguar DHD
Thank you for that link.
That build looks good.
Last week I tryed the EVO HD2 V6 (Nexus) Build.
I like it, but there are some bugs.
But mr evil is working on V7.
But I also like my JaguarDHD (Desire HD) Build. It works almost perfect for me for about one year. Onyl this little Bluetooth thing is disturbing.
I don´t know anything about creating builds, but perhaps it is possible to create an update file with the bluetooth part of one of the other builds?
Bluetooth update for Jaguar DHD
Does no one have an idea how to do that?

Categories

Resources