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.
Related
Hi,
hopefully anyone has an answer to the strange bluetooth behaviour of my X1.
The first device is a bluetooth headset from Sony. It works good, if bluetooth is activated. But after some time of not using the headset, the phone just switches off bluetooth. Sometimes after a few minutes, sometimes days after my last use of the headset. I tried all settings of the bluetooth-settings with no change. And it sucks if with the next phone call the headset cannot connect anymore because bluetooth was switched off.
The second device is a GNS TrafficBox Plus FM9BT-Y. Somehow MN7 does not detect the device directly, so I have to use the workaround with the serial port and outgoing connection on COM1.
The initial minutes the connection works fine, but then stops and is not restored.
Here as well trying different settings changed nothing.
How can I find out the address of the bluetooth devices?
Is there a tool to further test bluetooth connections (like what speed can be used, the address of the device, etc)
Regards
pt
Im using Itjes Touch 7 final & i have the same problem - infact i've had it with the last 3 of his roms with my blutooth to SEAT car. I'll be on a call in my car & it switches the blutooth off without warning. generally after about 10 minutes of actual call time. But it doesnt disconnect unless during a call ? There is no rhyme or reason to it, it just sometimes happens?
So any further info will be appreciated
Im using Itjes Touch 7 final & i have the same problem - infact i've had it with the last 3 of his roms with my blutooth to SEAT car. I'll be on a call in my car & it switches the blutooth off without warning. generally after about 10 minutes of actual call time. But it doesnt disconnect unless during a call ? There is no rhyme or reason to it, it just sometimes happens?
So any further info will be appreciated
I have Ra2generic DE with the 1.10 radio ROM on it.
At the beginning it was fantastic not having the bluetooth issue. Everything was working so extremely goood... no switching off, no disconnecting of and from the bt headset,, etc...
After a while the issue was here again...damn! So the bt became not very useful in its functionalities.... then I saw that it was not possible to see through my bt freespeech device in the car the last calls on the phone... hm, ok I said. There were lot of calls (incoming, outgoing, missed, etc) on the list...I erased them all...
Now it is working in a perfect way.... no disconnecting, no switching off..and this with the stock ROM and Radio ROM.
I tried it a few months before posting it here... now I'm cleaning up my calling list every 2nd day (I really call a lot) and I have no problems..
Hope it works for you..
i have the same problem, the bluetooth disconect without any reason, i have tried more than 10 Roms and i dont have any solution
¿is so dificult for Sony to repare this problem?
zagito said:
There were lot of calls (incoming, outgoing, missed, etc) on the list...I erased them all...
Now it is working in a perfect way.... no disconnecting, no switching off..and this with the stock ROM and Radio ROM.
I tried it a few months before posting it here... now I'm cleaning up my calling list every 2nd day (I really call a lot) and I have no problems..
Hope it works for you..
Click to expand...
Click to collapse
I hardreseted the device, installed the newest official firmware, deleted the calling list and with great expectations checked bluetooth behaviour.....nothing changed for me
But great it works for you and thanks for the tip
Come on people..... please someone help us with this
Bluetooth with clarion mind
Am having trouble connecting with my new Clarion MIND - is seems the phone does not see the profiles (very similar to the phone adding the older SE Bluetooth Watch, the 100). Has anyone built a .cab to sort this out?
I tried different roms curently using hyperdroid/ Miri with no success the phone always crashes when i pair/connect my bluetooth and try to make call. I followed directions of a poster to pair/connect and unpair and reboot. It worked once and then same problem again.
I want to use android on a regular basis but cant use it without bluetooth. Can anyone help ? Thank you !! I searched this forum and on the web for a while before posting this. If you have a solution please help.
cmboud said:
I tried different roms curently using hyperdroid/ Miri with no success the phone always crashes when i pair/connect my bluetooth and try to make call. I followed directions of a poster to pair/connect and unpair and reboot. It worked once and then same problem again.
I want to use android on a regular basis but cant use it without bluetooth. Can anyone help ? Thank you !! I searched this forum and on the web for a while before posting this. If you have a solution please help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=780020
Well I tried that without any success, anyone else has another solution ? let me know i cant use the HD2 without bluetooth. I live in CA mandatory bluetooth in the car and i drive a lot.
cmboud said:
Well I tried that without any success, anyone else has another solution ? let me know i cant use the HD2 without bluetooth. I live in CA mandatory bluetooth in the car and i drive a lot.
Click to expand...
Click to collapse
Try different kernels. I've found that even though I continue to use the same build (ShubCRAFT 1.5), when I swap kernels I get differing results with the BT headset.
Media Audio tends to work whatever, I've had no problems with that, but phone audio is a different matter.
I've been using michyprima's r11 kernel lately (noAXI) and that seems to just about work but I do have to make a call and press the Bluetooth button immediately initially to get it to work.
Even then, it's flaky, as when the phone rings and I press the answer button on my BT headset, it brings up the Voice Dialer dialog over the top of the phone app and doesn't answer the call. I've resorted to only connecting BT to media and not using it for the phone.
I appreciate that doesn't solve your problems - I've simply decided to try each and every kernel until it's fixed! I'm sure the wonderful devs here will get round to fixing it soon but I think they've probably got other things higher up on the priority list right now!
I'm using a Sony Ericsson MW600 BT headset btw.
hello sorry for my English
my jabra bt hyperdroid on 1.2 works, but sometimes there is more sound for the march to re-I does not restart it by pressing the restart button, but I removed the battery!
For me works like that
success
I forgot to tell you that I deactivated the sound of media
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
I know complaining about that is almost ridiculous but I thought there might maybe be a solution or at least an explanation for this problem. I tried to connect the Android HD2 to my BMW and it worked in the first place. Also Bluetooth Audio connection works which gives me the option to listen to my music while the phone still is in my pocket.
But when I try to make a call or answer a call (which is shown on the display) nothing happens. Is there any idea to fix that?
More info needed....like android build etc etc....
Sent from my HTC HD2 using XDA App
Sounds like your running a cm based rom. Download and apply one of the sense builds. try this one: http://forum.xda-developers.com/showthread.php?t=791835
I'm not using a Cyanogen ROM since I need to use HTC Sync as I'm using the phone for business. I'm using the new 3.2 FroyoStone ROM which is very fast and stable and stock.
Today I had a minute or two of hope when I was making a call from my car using bloototh. But after around three minutes of speaking to the other person I could only hear him while he was obviously not hearing anything from me.
I then tried to stop and start the bluetooth in the properties section of android again which caused a total system crash...
Until the problem is solved completely I will continue to write my expiriences, experiments and disappointments here even if nobody gives me any response to it.
I've had loads of problems with Darkstone 3.2, you can try a different build and see if that works...
Sent from my HTC HD2 T8585 using XDA App
Now I found a midtime solution. When using the buildby Mdeejay (FroYo HD v.3.6 / kernel:hastarin R7.2) the bluetooth handsfree device in my car works just perfectly. Unfortunately the DesireHD build doesn't support the camera yet and the disconnects are out to happen much more frequently than in the other builds.
I will try to run this build using the newer kernel V7.6 and see if the bluetooth device is then still working.
Pairing Problems with BMW iDrive (525d 2005)
Hi,
I've been having this issue with my BMW iDrive and HTC Desire HD, it keeps constantly connecting and disconnecting the bluetooth on HTC stock ROM and ARHD 6.3.1, but with the Custom ROM (CM7.1) I keep getting connection prompts and keep going around in loops without any success in pairing.
I have tried the suggestion from the forum topic below with regards to the audio.conf mod and see if it has any success. This failed.
forum cyanogenmod #entry85118
Push to /sdcard/ and then run in sh
cd /sdcard/
cp /system/etc/bluetooth/audio.conf /sdcard/audio.conf.bak
mount -o remount,rw /system
cat audio.conf.txt > /system/etc/bluetooth/audio.conf
mount -o remount,r /system
Then reboot.
/system/etc/bluetooth/audio.conf amended with the following parameters
# Configuration file for the audio service
[General]
Enable=
Disable=Headset,Gateway,Source,Control,Sink
# Do not require master role for incoming connections
Master=false
# Automatically connect both A2DP and HFP/HSP profiles for incoming
# Maximum number of connected HSP/HFP devices per adapter. Defaults to 1
MaxConnections=3
BMW iDrive version 1-04-09-500 0 (BMW 525d E60 2005) Build July 2004
I've tried a few custom ROMs now without success, if the bluetooth itself could be patched up that would be nice, if I need to downgrade the bluetooth please let me know where to begin as I have only just begun tinkering with Rooting and Custom ROMs.
I'm now thinking I'll have to get the BMW iDrive software updated to see if this resolves my issue.
Regards
M
Bluetooth in car
Someone related to bluetooth to in the car, for those that don't have it an easy solution is Flexsmart X2. It works just fine, almost an alternative to their real thing, please check it out.
Jimmy4485 said:
Someone related to bluetooth to in the car, for those that don't have it an easy solution is Flexsmart X2. It works just fine, almost an alternative to their real thing, please check it out.
Click to expand...
Click to collapse
I don't like the idea of tuning into the radio to hear the phone call, I tried one of those MP3 things with mixed results.
I've found a much simpler solution, iPhone 3gs pairs/connects, syncs address book and works!!!
So clearly the Bluetooth is junked in HTC/Android phones, we tried a HTC Magic running an older Android version which had the same problem.
I'm back to the Stock HTC ROM until I find a solution for the existing phone or eligible to upgrade my contract.
Update iPhone 4 also works so that settles it, now need to get hold of someone with iPhone 4s for the sanity check.
HTC Desire HD now syncs/connects fine.
Had to also rename the blacklist.conf and auto_pairing.conf.
Stop and clear data for Bluetooth share service.
Initiated call from phone call successful after a few mins the address book was up on the idrive and was able to start the call from there.
Currently using ARHD 6.3.1 with recommended radio file.
Sent from my Desire HD using XDA App
arfie_don said:
HTC Desire HD now syncs/connects fine.
Had to also rename the blacklist.conf and auto_pairing.conf.
Stop and clear data for Bluetooth share service.
Initiated call from phone call successful after a few mins the address book was up on the idrive and was able to start the call from there.
Currently using ARHD 6.3.1 with recommended radio file.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
I spoke too soon, lol. Back to square one.
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