Database Users

<BUG> DamageControl v2.05 Bluetooth

I love the DCv2.05 ROM! However, every since I flashed it my Bluetooth will no longer work in my C300 Mercedes. The stock ROM does work perfectly.
The phone will pair with the car and connect; but it will disconnect itself several seconds later. It does this over and over and over. The phone says it is paired but not connected.
Any help?

Having the same problem with my Pioneer head unit. Same rom, same connect-disconnect for the phone, but the bluetooth audio function works fine. I can listen to music from the phone, but not make or receive calls...

A2DP has issues in Fresh 2.0d as well. I can pair and connect with my car stereo, but the bluetooth "hiccups" 2-10 times per minute.

danknee said:
A2DP has issues in Fresh 2.0d as well. I can pair and connect with my car stereo, but the bluetooth "hiccups" 2-10 times per minute.
Click to expand...
Click to collapse
As a datapoint I've been running this ROM for a week now and my Mazda3 has no problems connecting to my phone, both music, and voice.
I spent 20 minutes on the phone through the sound system on my way home from work.

smw6180 said:
As a datapoint I've been running this ROM for a week now and my Mazda3 has no problems connecting to my phone, both music, and voice.
I spent 20 minutes on the phone through the sound system on my way home from work.
Click to expand...
Click to collapse
Are you running any mods or just a straight copy of fresh? Maybe I will reflash today and see if my BT issue continues.

danknee said:
A2DP has issues in Fresh 2.0d as well. I can pair and connect with my car stereo, but the bluetooth "hiccups" 2-10 times per minute.
Click to expand...
Click to collapse
I have no idea what A2DP is.

danknee said:
Are you running any mods or just a straight copy of fresh? Maybe I will reflash today and see if my BT issue continues.
Click to expand...
Click to collapse
Straight copy of Fresh, with PlagaDeBuuf's theme.
I installed the lockscreen from Flipz' site earlier but my TWS problem came back so I removed it, and nandroided back to a copy I'd made this morning just before flashing, so it's essentially the same ROM I've been running for a week.

danieledwards1 said:
I have no idea what A2DP is.
Click to expand...
Click to collapse
A2DP = stereo bluetooth

This is an issue with all 2.1 ROMs. Pioneer is known for having the issue where it will pair up but only play media. I have not run into one 2.1 ROM which will work. I have seen some, non pioneer, which report that it works though. Let's just hope the official will have this ironed out or I will be keeping 1.5 around just for this reason. Darch has been working on this in his Legend ROM.

I'm having the opposite effect. The 2.1 leak has had the best Bluetooth implementation I've ever had. Works great on my Ford SYNC and Motorola S9-HDs.

working great in my grand cherokee

repair your bluetooth
I had the same problem in my Infiniti... I thought it was the rom because if I restored my previous rom it worked fine, but when I pair it with the new one it didn't work.
To fix it I had to delete the pair from the car's bluetooth and the phone and repaired them and it worked fine. This worked for both Damage and Flipz's rom. It was odd this was still a problem going from damage to flipz. So when I switched, I deleted the pairing and repaired them.
Hope that helps

I haven't been able to get any of these ROMs to connect to the cassette deck in my 1999 Saturn SL

thematrixkid17 said:
I haven't been able to get any of these ROMs to connect to the cassette deck in my 1999 Saturn SL
Click to expand...
Click to collapse
Did you try to sync the magnetic track? Maybe you need to flip over to the B side and try again?

diordnahero said:
working great in my grand cherokee
Click to expand...
Click to collapse
I too have the Uconnect in my Grand Cherokee, but can't get it to work. The phone pairs, but won't actually connect. What ROM are you running?

danknee said:
Did you try to sync the magnetic track? Maybe you need to flip over to the B side and try again?
Click to expand...
Click to collapse
I think my PRI is bad.... http://bit.ly/bi0Mzt

Pioneer Not connecting
I have a Pioneer Head Unit Premier - ONLY BT Audio - NO Handsfree working. w-damage and fresh latest.. Will try it with my Kenwood and let ya all know.

I haven't had any issues in my 2010 Mustang w/Sync.

atoy74 said:
I'm having the opposite effect. The 2.1 leak has had the best Bluetooth implementation I've ever had. Works great on my Ford SYNC and Motorola S9-HDs.
Click to expand...
Click to collapse
wow this is crazy . i have 2 s9-HDs and 2 heros wih dmage 2.1 rom and eithr of them work correctly ...i just dont get it ..how can some have issues and others dont ...i am going to try Fresh and see it is better ...
the headsets are great but they cut off every couple seconds and come back ...wonder if the Hero just doesnt have the power to do this ??? or maybe higher bitrate mp3s ? most of my MP3s are 128bit ...

rgildoss said:
wow this is crazy . i have 2 s9-HDs and 2 heros wih dmage 2.1 rom and eithr of them work correctly ...i just dont get it ..how can some have issues and others dont ...i am going to try Fresh and see it is better ...
the headsets are great but they cut off every couple seconds and come back ...wonder if the Hero just doesnt have the power to do this ??? or maybe higher bitrate mp3s ? most of my MP3s are 128bit ...
Click to expand...
Click to collapse
It's not the headphones or the Hero, it's 2.1!
I am having the exact same problems as you and finally went back to 1.5 and it's flawless!
Like I have said before it's seems to be 50/50 across the board, some work and some don't!

Senseless 2.2 builds with working BT car audio

Has anyone got a list of senseless builds at the title suggests!
Im currently running Dans froyo 1.1 which i love, and if it had BT support i would use without fail, but its kinda annoying me now !
Thanks guys

kiteboarderni said:
Has anyone got a list of senseless builds at the title suggests!
Im currently running Dans froyo 1.1 which i love, and if it had BT support i would use without fail, but its kinda annoying me now !
Thanks guys
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=756491

darkstone FroyostoneSeries V1 is working with audio Bluetooth, even A2DB stereo
Sent from my HTC Desire using XDA App

I am using Darkstone HD2Froyo V2 - Release Date: 16.Aug.2010
I have a Toyota Prius with bluetooth build in, I can connect the phone to the car, I can pickup and end calls, but I can't get audio. The other side hears me, but I can't hear them.
EDIT:
Found this, so it makes sense that it doesn't work (for now)
======================
Whats working:
- Wifi
- GPS
- 3G
- Camera with flash
- Bluetooth (No Headset in calls support)
- Everything thats working on other builds
- LED status notification
- Keypad LED control
Whats not working:
- Camcorder
- Bluetooth Audio in calls
- Compass is inaccurate, this is known.
- USB Storage mode is disabled, I have done this on purpose. File corruption seems to occur when using android to transfer files. Are you really suprised though? You're running the O/S off the memory card too remember...
======================

caedanne said:
http://forum.xda-developers.com/showthread.php?t=756491
Click to expand...
Click to collapse
Not senseless dude

kiteboarderni said:
Has anyone got a list of senseless builds at the title suggests!
Im currently running Dans froyo 1.1 which i love, and if it had BT support i would use without fail, but its kinda annoying me now !
Thanks guys
Click to expand...
Click to collapse
I'm also would love to see something like that, but for now I'm using mattc Leo + Froyo w/Sense and removing most of Sense stuff leaving only Gallery(it's fastest of all I've found) and Contacts(for providing "Search in contacts" as a direct app).

Bluetooth not working right with Pioneer and Android

I've been using Androind on my HTD for +/- the past month or so, and have yet to have stable bluetooth operation through my Pioneer AVH-3200BT which is enabled for BT phone calls (NOT A2DP). I've been through several builds, and currently am using shu8i's latest shubCRAFT 1.4d (23.08.2010 build). I'm got HPSL3 and Radio 2.12.
I get a lot of forced close app errors with trying to establish BT connection. Sometimes I get further, like the Pioneer can usually pick up my contact list after a few tries... But the worst happens when I try to make a phone call. The system hangs, the sound goes dead, the Pioneer cancels the call, and the HTC HD2 usually crashes back to the home screen. From then, I usually dont have any sound for anything until I reboot the HD2.
In WM6.5 Bluetooth works fine with the Pioneer.
Can anyone help me out with this? I'd be willing to pull some logs / demos / or get more vital information if I knew where to look. I'll be the geinea pig!
Thanks in advance

I'll add plantronics voyager 815 to list. maybe a list of working headsets might help if anyone has one.

my Jabra T3030 doesn't work either. It works great with A2DP and it even rings when i get a call. but it hangs the device if i try to answer and there's no audio in calls.
I tried every build possible

I cannot get my Bluetooth wireless headset to work also ,it works on phone calls but on media ,no sound is transferred ,Ian using Mattc 1.6b with sonyericsson headset ,that works more than perfect on windows
Sent from my HTC HD2 using XDA App

saabguy123 said:
I've been using Androind on my HTD for +/- the past month or so, and have yet to have stable bluetooth operation through my Pioneer AVH-3200BT which is enabled for BT phone calls (NOT A2DP). I've been through several builds, and currently am using shu8i's latest shubCRAFT 1.4d (23.08.2010 build). I'm got HPSL3 and Radio 2.12.
I get a lot of forced close app errors with trying to establish BT connection. Sometimes I get further, like the Pioneer can usually pick up my contact list after a few tries... But the worst happens when I try to make a phone call. The system hangs, the sound goes dead, the Pioneer cancels the call, and the HTC HD2 usually crashes back to the home screen. From then, I usually dont have any sound for anything until I reboot the HD2.
In WM6.5 Bluetooth works fine with the Pioneer.
Can anyone help me out with this? I'd be willing to pull some logs / demos / or get more vital information if I knew where to look. I'll be the geinea pig!
Thanks in advance
Click to expand...
Click to collapse
I got similar problem with my Motorola Headset too, it just keep hanging with the dialer, without bluetooth one, the dialer works flawlessly. Mine is Shubcraft

I think I figured it out... I set the pioneer to accept connections with pin 1234 instead of 0000 and it seems to be working alright now.
Sent from my HTC HD2 using XDA App

precsmo said:
I got similar problem with my Motorola Headset too, it just keep hanging with the dialer, without bluetooth one, the dialer works flawlessly. Mine is Shubcraft
Click to expand...
Click to collapse
I'm also having troubles with my Sony Ericsson MW600. I did get it going with I think ShubCraft 1.4b but now on 1.5 it won't have it...
It pairs fine, works fine with Media - AVRCP controls working, etc.
But the phone app just doesn't like it. I've tried to switch BT on and off whilst in call and most of the time get a force close on the phone app.
My libbluetooth.so files are dated 04/08/2010. Does anyone have later dated .so files I can try? Or earlier ones for that matter!?
Thanks all.

wheeliemonster said:
My libbluetooth.so files are dated 04/08/2010. Does anyone have later dated .so files I can try? Or earlier ones for that matter!?
Thanks all.
Click to expand...
Click to collapse
I've changed libbluetooth.so for this one:
http://code.google.com/p/androidobex/downloads/detail?name=libbluetooth.so
it work's but the hd2 ask for the bluetooth pass every time that connects.

magnus48 said:
I've changed libbluetooth.so for this one:
http://code.google.com/p/androidobex/downloads/detail?name=libbluetooth.so
it work's but the hd2 ask for the bluetooth pass every time that connects.
Click to expand...
Click to collapse
I can't even get the bluetooth radio to turn on using this file...
Not having bluetooth headset is the most frustrating thing. Well its a close second to nearly every android build claiming to have bt working in the OP but it doesn't work!!

bhilgeman said:
I can't even get the bluetooth radio to turn on using this file...
Not having bluetooth headset is the most frustrating thing. Well its a close second to nearly every android build claiming to have bt working in the OP but it doesn't work!!
Click to expand...
Click to collapse
I've tried changing the libbluetooth, libbluetoothd and libbluedroid files time and again with Shubi's build and nothing works.
I had some success today though. I'm currently using Shubi's build but with the michyprima r10 kernel.
I was trying a different kernel earlier - the huanyu OC kernel from here:
http://forum.xda-developers.com/showthread.php?t=777921
This got my BT headset working for calls and A2CP/AVRCP...
PLEASE NOTE: This kernel is in beta still, read the thread!
Unfortunately, it proved to be a little unstable for me, so I've had to go back to michyprima's kernel.
But it does seem that the problem lies in the kernel, rather than the bluetooth libraries.

bhilgeman said:
I can't even get the bluetooth radio to turn on using this file...
Not having bluetooth headset is the most frustrating thing. Well its a close second to nearly every android build claiming to have bt working in the OP but it doesn't work!!
Click to expand...
Click to collapse
A reboot is required after overwriting libbluetooth.so file
With some old android distributions I cant turno on the bluetooth radio, but it was a kernel matter. Maybe updating the kernel solves the problem.
Now I use FroyoStonev2 with this [kernel][.32.9](BFS+BFQ+AXI+OC+UV) build on 09.09.2010(version 0.2)
But every time that reboot the hd2 need to pair with the freehands.
Every time that reconnect it needs to reenter the code.

[ISSUE] Bluetooth and non-Sense builds

So I having a recurring problem with all of the non-Sense builds that I've tried here on the forum. The bluetooth would pair and connect perfectly in all the cases. However, the problem arises when I tried to make a call. The phone would freeze up or come to crawling halt. The dialing screen would go black, and then I would get the android.phone.process force close error. And I would need to pull the battery and reboot.
The issue has happened every single time with any of the non-sense builds I've tried so far: NexusHD2-FRG83, HyperDroid v1.6, Bangsters v1.5, and shubCRAFT v1.5.
I've tried with the included kernels with each build, and also with different combinations of kernels with the above builds as well, hasparin r4.1, r7.2, r7.4, r7.5 and michyprima r11. And still the same issue.
I'm certain there are other people with this same exact problem. So there has to be something going on with these non-Sense builds.
I have two bluetooth headsets, Plantronics 925 and 975. Same problems on both.
I don't like Sense, but I have to use a Sense build because bluetooth calling is very important to me. I hope some of you developers can come up with something to fix this.

Hi. I had exactly same problem.
Try to push play&pause music ,start&stop voice action
before start use bt.
Another solution is push bt call button immediate after make call
Sent from my Nexus One using XDA App

That didn't work for me.

I had the same problem as the OP and thats why i switch to a sense build also

Did you try this before?
http://forum.xda-developers.com/showthread.php?p=8348326

zoftdev said:
http://forum.xda-developers.com/showthread.php?p=8348326
Click to expand...
Click to collapse
Yes, I've tried that. But those files are for sense builds, and when I transfer them to a non-sense build, BT wouldn't even turn on.

See the FAQ in my signature. Some of the builders have BT working on CM6 with the EVO kernel so you should soon see builds that support it.
Sent from my HTC HD2

hastarin said:
See the FAQ in my signature. Some of the builders have BT working on CM6 with the EVO kernel so you should soon see builds that support it.
Sent from my HTC HD2
Click to expand...
Click to collapse
Wow! That's superb news.

BT Works
raysacr said:
So I having a recurring problem with all of the non-Sense builds that I've tried here on the forum. The bluetooth would pair and connect perfectly in all the cases. However, the problem arises when I tried to make a call. The phone would freeze up or come to crawling halt. The dialing screen would go black, and then I would get the android.phone.process force close error. And I would need to pull the battery and reboot.
The issue has happened every single time with any of the non-sense builds I've tried so far: NexusHD2-FRG83, HyperDroid v1.6, Bangsters v1.5, and shubCRAFT v1.5.
I've tried with the included kernels with each build, and also with different combinations of kernels with the above builds as well, hasparin r4.1, r7.2, r7.4, r7.5 and michyprima r11. And still the same issue.
I'm certain there are other people with this same exact problem. So there has to be something going on with these non-Sense builds.
I have two bluetooth headsets, Plantronics 925 and 975. Same problems on both.
I don't like Sense, but I have to use a Sense build because bluetooth calling is very important to me. I hope some of you developers can come up with something to fix this.
Click to expand...
Click to collapse
I have been running with BT on several builds for a couple of months now including the NexusHD2-FRG83 builds mentioned above. In fact if a build does not have working BT I skip it. I have found that the first time you install the build and try to use handsfree you need to do the trick of selecting/de-selecting and then selecting BT in the call screen before the actual connection. I use my phone constantly for work with speaker phone (Motorola EQ7) and my headset (BlueAnt T1). No problems making or receiving calls. I use the BT in both phone audio and media audio modes without any issues.

jinharry said:
I have been running with BT on several builds for a couple of months now including the NexusHD2-FRG83 builds mentioned above. In fact if a build does not have working BT I skip it. I have found that the first time you install the build and try to use handsfree you need to do the trick of selecting/de-selecting and then selecting BT in the call screen before the actual connection. I use my phone constantly for work with speaker phone (Motorola EQ7) and my headset (BlueAnt T1). No problems making or receiving calls. I use the BT in both phone audio and media audio modes without any issues.
Click to expand...
Click to collapse
before it's only supported on RMNET or non evo kernel.. the NEW NexusHD2 that was just released now supports BT on all currently available kernels... you don't even have to do the on, off, on trick anymore for the bluetooth to work.. i think it's the closest to being the perfect android build for our HD2.. everything just works including the MMS which i'm having problem with all the sense builds (low res image)..

I will load NexusHD2 1.5 tonight and see what I find

Finally a non-sense build with working bluetooth. I was able to bluetooth music and make a call using my car stereo. I just had to post this. http://forum.xda-developers.com/showthread.php?t=804210

Is There Any Fix for the Bluetooth Voice Dialing Crash Issue?

I've never seen a dedicated thread on this but I've seen people make off-hand comments about this issue from time to time. I think it started happening in Tytung R9 and higher kernels.
I am using a BlueAnt T1 Bluetooth headset. It pairs just fine and I can use it generally without any issue.
The problem comes when I use voice dialing to initialize a call from the Bluetooth headset. It connects to the phone and I get the normal Android "Speak now...." I speak my command "Call <person> on <service>...." It states the command back like normal and then _as soon as_ it switches to the phone app (eg, com.android.phone process) it locks up the phone and the only way to recover is to pull the battery.
If, instead, I go to the phone app, find the person, and call them that way (even with Bluetooth paired) it _always_ works without any problems. This isn't a long-term solution for me because I need to use voice dialing when I'm in my car.
Now that GPS looks to be fixed and CLK data over PPP is much more stable, this Bluetooth issue is the last thing standing between me and treating the HD2 as my full-time native Android phone (currently I tinker on the HD2 but use my Nexus One as my daily driver).
I've tried multiple different ROMs, from HyperDroid-CM7, HyperDroid-GBX, Typhoon CM7, and Nexus-HD2-Gingerbread. They all have the same issue though Nexus-HD2 appears to be worse than the others (that is, the problem happens more often there).
I've used the infamous audio.conf update as well as the various no-wonk and libaudio patches and none of them help this issue.
Anyone else experienced this and have any feedback on how you overcame it?

I have the same kind of problem and tried a lot of different ROMs - not help.
I tried Blueant ST3, Motorola t305.
Phone book copied to blueant very well, but voice dial has same simptoms like yours - even if phone does't hang sound goes away from phone permanently(needs reboot). Is there any other ROM which works well with bluetooth hadsfree?
Any one?
P.S. Looks like it is real problem, but non of developers pay attention to it - they just don't have handsfree maybe

Ι think that sense roms doesnt have this issue.But unfortunatelly they have other issues...

clio94 said:
Ι think that sense roms doesnt have this issue.But unfortunatelly they have other issues...
Click to expand...
Click to collapse
I've not actually tried a SENSE-based ROM but I understand from my research that they don't have the BT issue. Maybe it's possible to look into their architecture to understand what is different.
I expect that it's something in the kernel....

This is a very common issue. if it helps, BTvoice command works Fine in Froyo.. at least CM6 (I tested).

svet-am said:
I've not actually tried a SENSE-based ROM but I understand from my research that they don't have the BT issue. Maybe it's possible to look into their architecture to understand what is different.
I expect that it's something in the kernel....
Click to expand...
Click to collapse
I think it is not the kernel, same kernel will crash in CM7 but no in CM6. I think the problem is related to the libaudio.so and other libs in system/lib.

robrob777 said:
This is a very common issue. if it helps, BTvoice command works Fine in Froyo.. at least CM6 (I tested).
Click to expand...
Click to collapse
are the Froyo-based builds still being maintained. I ask that from the perspective of "could I just use a Froyo build as my daily driver instead?"

svet-am said:
are the Froyo-based builds still being maintained. I ask that from the perspective of "could I just use a Froyo build as my daily driver instead?"
Click to expand...
Click to collapse
I'm using it as my daily driver (CM6), I came back just bc of the calling issues in Gingerbread.
the build that I'm using has not been updated since Jan 7, however I applied around 10+ patches and now it works as good as the new builds.

I just tested again voice command.
No problems
During the voice command call I can switch from BT to speaker to audio piece, back to BT etc, no problems. Audio doesn't crash after call.
And no 60ma battery drain. it is around 5ma after the call with BT on.

robrob777 said:
I just tested again voice command.
No problems
During the voice command call I can switch from BT to speaker to audio piece, back to BT etc, no problems. Audio doesn't crash after call.
And no 60ma battery drain. it is around 5ma after the call with BT on.
Click to expand...
Click to collapse
just for clarity for other folks reading this thread, I assume that you're talking about a Froyo-based ROM.

i just verified the problem exists in MIUI as well. I tested MIUI since it's allegedly a "clean room" type of build environment.

svet-am said:
just for clarity for other folks reading this thread, I assume that you're talking about a Froyo-based ROM.
Click to expand...
Click to collapse
Yes, I tested successfully in a Froyo based ROM.
I went back for a moment to CM7 and tested...sound couldn't return to the phone after calling with BT, also during the call I was not able to switch to speaker phone like I do in the froyo based ROM.

Tested with Tytung 1.9G Froyo - BT works just fine in all ways. Just need to keep GPS off(when not used) to avoid 60 ma current draw.
Tytung says BT Voice dail is just GBread problem.

zcdg said:
Tested with Tytung 1.9G Froyo - BT works just fine in all ways. Just need to keep GPS off(when not used) to avoid 60 ma current draw.
Tytung says BT Voice dail is just GBread problem.
Click to expand...
Click to collapse
It works fine on my Nexus One on Gingerbread, so I don't see how it can be a "gingerbread problem." If it was a "gingerbread problem" other devices would be seeing this as well.

svet-am said:
It works fine on my Nexus One on Gingerbread, so I don't see how it can be a "gingerbread problem." If it was a "gingerbread problem" other devices would be seeing this as well.
Click to expand...
Click to collapse
Yes you are right. It is just what Tytung said(i asked in his thread). Probably he meant GB for HD2....Soon or later they will figure it out i think...
For now will use Froyo 1.9G....

tytung said:
I don't have any Bluetooth headset.
AFAIK, some people have the sound issues, e.g. causing the phone app FC, since using Gingerbread 2.3.4.
But it doesn't affect all people, I don't know why.
No solution so far. To use Gingerbread 2.3.3 instead if you are one of them.
Click to expand...
Click to collapse
I finally found Tytung's exact quote as to why he won't look into the issue. It can be seen in context over here: http://forum.xda-developers.com/showthread.php?t=905060&page=524#
So, it might not be Froyo that's the fix but rather older versions of Gingerbread as well.

i have found a workaround fix for this bug.I tried it in tytung`s v2.9 rom and in dorimanx cm7 light rom with driztee v2 libaudio file.For bt voice commands i am using cyberon voice commander because google app doesnt support yet greek language
i connect my bt headset (motorola h300) and then i use super bt mono froyo free app https://market.android.com/details?id=com.steven.supermonofroyofree&feature=search_result to send audio to bt headset.
After pushing the bt headset button cyberon voice starts and i can give the command i want.After giving the command, audio goes back to the phone (you will hear a beep from phone speaker).The weird thing is that the audio is in extremely low level for hearing music but when you receive a call it is in normal level.
If i close super bt mono froyo app,audio returns to phone in normal level.
But if i accidentally (after i close the app) push the button for voice bt command,audio will disappear.
If the app is on and you receive a call,all audio will go again to bt headset and to return it to phone speaker after end call, i push bt headset,cyberon voice starts and i dont give any comand.After cyberon ends,audio goes back to phone with low level for media hearing.
Sure this isnt the perfect solution,but the important thing for me is that with this way,audio is not go away and i can give bt voice commands.
Also i tried bt mono app http://forum.xda-developers.com/showthread.php?t=950472 and it have a little different behaviour.I cant start from bt headset cyberon voice comander,but only from the phone and after giving a command,audio returns to bt headset if you have enable the setting "restart after call".So i think it maybe be helpful to people who want to have audio all time in a bt carkit.

Tested all 2.3.3 from Tytung - last working with r8.3 kernel. r9 and up not working.
So NexusHD2 v2.5 NAND(GB 2.3.3) with r8.3 latest working with BT voice dial ROM.

zcdg said:
Tested all 2.3.3 from Tytung - last working with r8.3 kernel. r9 and up not working.
So NexusHD2 v2.5 NAND(GB 2.3.3) with r8.3 latest working with BT voice dial ROM.
Click to expand...
Click to collapse
thanks for that follow-up and testing. I was wondering if whether or not it might be a "fault" in the VoiceDialer.apk or even in the Phone.apk. I have been using my Nexus One for daily stuff. I might try replacing VoiceDialer and/or Phone.apk in a newer ROM (eg AOSP 2.3.5 or so) with the old version and see if it works.

Ive wondered about this as it is to me the last issue I have with my HD2. Here is a search link for some entries in Tytungs rom & kernal thread...
http://forum.xda-developers.com/search.php?searchid=86308155
Also here is a comment from the man himself...
http://forum.xda-developers.com/showpost.php?p=15996942&postcount=5953
and here is a post in reply that talks about the same issue being replicated using Bluetooth...
http://forum.xda-developers.com/showpost.php?p=15997234&postcount=5956
Some more chat about the sound issues...
http://forum.xda-developers.com/showpost.php?p=16113973&postcount=6045
Another thread with logcats on it...
http://forum.xda-developers.com/showthread.php?t=1060486