I see a number of folks reporting varying levels of success/quality when using Skype.
What version of ROM and Skype do you use, have you 'overclocked' and what is the voice quality quality like?
I am using the latest Imate Rom with the version of skype that installed with it (V 1.1.0.15), overclocked to 240Mhz and the sound is a bit choppy and loses words.
So far I'm pretty happy with Froyo on my phone. I've got the barebones WM for droid rom, radio version 2.12.50.02_2and a FAT32 SD card I freshly formatted prior to installation.
It's great, save for the fact that my plantronics discovery 975 headset doesn't seem to play nicely with Froyo. It pairs just fine, but I don't get any audio and the phone app seems to lockup when I attempt to answer a call while paired. This is via either the button on the handset or the headset.
I know Android for HD2 is still in dev, so I"m willing to accept this is just a problem with no fix. However, if there is a bug out there I can fix to get my headset working, I would love to know about it.
Any help would be appreciated.
Mccm v.1.5 works nicely with my SE headset. It's the only android without sense build where Bluetooth is functional with my headset. Have tried them all.
If you're into sense, Froyostone build has Bluetooth perfectly functional.
Sent from my HTC Desire using Tapatalk
That's what I'm told, but...
....the MattC Froyo Sense is a slightly moded version of the stone, if understand the txt doc that comes with it.
I'll try the straight stone installation and let you know how it goes. In the meantime, if anyone has a suggestion as to why this would be flakey, I'm really curious what the issue is.
Hello, i am new in this Forum and i have a question about the original HTC Headset.
I tried a lot of Android Bults on my HD2 but there is not possible to use the headset buttons for music.
Now i am using this version and it is possible bus the G-Sensor is not working: mdeejay_froyo_sense_v2.5
Do any one now an other Build that works with the headset or must i install an app from market?
Thank You
Sry for my english. Its not the best
Umar786 said:
Hello, i am new in this Forum and i have a question about the original HTC Headset.
I tried a lot of Android Bults on my HD2 but there is not possible to use the headset buttons for music.
Now i am using this version and it is possible bus the G-Sensor is not working: mdeejay_froyo_sense_v2.5
Do any one now an other Build that works with the headset or must i install an app from market?
Click to expand...
Click to collapse
Unfortunately this is dependent on the kernel you are using.
With all evo-based kernels the headset-buttons are out of function.
They will only work with a nexus-based kernel, i.e. this one:
http://forum.xda-developers.com/showthread.php?t=756513
Of course, you then have all the disadvantages a nexus-based kernel has, like touchscreen freezes and so on...
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'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