Auto redial through bluetooth headset is really a pain with new headsets with soft buttons.
When the earphone is in pocket many times the last call redial function is accidentally enabled.
Any chef any solution??
Thanks
I have no idea, but this isn't really a cooking question, as far as I can tell. It's probably better off in the Q&A forum, but I'll leave it here for now. Someone else may well have figured out how to do it (who doesn't cook roms).
EDIT: Wrong forum, ignore below unless you are on Android.
I too would like to disable last call redial on BT headsets. The best I have found is a program called "call confirm" which makes you confirm each time you want to make a phone call. Haven't tested it yet as it's actually for my father (I don't use a BT headset) but could be a good temporary fix. Otherwise I have not found any other solution.
http://www.appbrain.com/app/net.nanabit.callconfirm
Look at this: http://headsetbutton.com/
Maybe it could be an alternative while someone develops a free tool to manage that.
Trail is fully functioning for 21 days...but i think it's worth to pay 5.95 EUR for that.
Btw...thanks to funkwerk for the hint.
reallynotnick said:
I too would like to disable last call redial on BT headsets. The best I have found is a program called "call confirm" which makes you confirm each time you want to make a phone call. Haven't tested it yet as it's actually for my father (I don't use a BT headset) but could be a good temporary fix. Otherwise I have not found any other solution.
http://www.appbrain.com/app/net.nanabit.callconfirm
Click to expand...
Click to collapse
This application is for android only!
Thanks anyway
icke said:
Look at this: http://headsetbutton.com/
Maybe it could be an alternative while someone develops a free tool to manage that.
Trail is fully functioning for 21 days...but i think it's worth to pay 5.95 EUR for that.
Btw...thanks to funkwerk for the hint.
Click to expand...
Click to collapse
This is for wired headset.
Thanks anyway.
Farmer Ted said:
I have no idea, but this isn't really a cooking question, as far as I can tell. It's probably better off in the Q&A forum, but I'll leave it here for now. Someone else may well have figured out how to do it (who doesn't cook roms).
Click to expand...
Click to collapse
I agree with you.
There is a similar application editing the bluetooth drivers.
But this editing applies only for microsoft bluetooth not widcomm drivers that uses the htc.(i have the Leo)
Thanks for your message.
NIKOSXRI said:
This application is for android only!
Thanks anyway
Click to expand...
Click to collapse
Whoops, my apologies, I was just googling "android bluetooth last call redial" and didn't check which section I was in....
I can't believe neither platform has the ability to fix this. The only other option would be to find a different headset, like my father used to have a Motorola BT headset with a collapsable boom and when shut the buttons did not do anything though it would stay connected.
Well best of luck in your continued search.
Related
I know... there are some things written abt this earlier but I really need to sort this out now. As I understood I can use, for example Cyberon voice dialer with the magician/s100. Am I right to think that there is NO WAY that you can activate the voice dialer by pressing the button on the BT handsfree device?!?
This is the only thing that I still haven´t figured out abt this so PLEASE... enlight me! If there is anyway that this bug can be fixed, I would highly appreciate any tips regarding this!
Thanks a lot!
Re: Bluetooth and handsfree... sort this problem out for me!
emil73 said:
I know... there are some things written abt this earlier but I really need to sort this out now. As I understood I can use, for example Cyberon voice dialer with the magician/s100. Am I right to think that there is NO WAY that you can activate the voice dialer by pressing the button on the BT handsfree device?!?
This is the only thing that I still haven´t figured out abt this so PLEASE... enlight me! If there is anyway that this bug can be fixed, I would highly appreciate any tips regarding this!
Thanks a lot!
Click to expand...
Click to collapse
The MS Bluetooth stack is pretty primative and doesn't support this kind of stuff. The WIDCOMM stack is better, but no one has written a driver for the Magician.
I installed the Toshiba stack for a while, and it was wonderful - the rings came into the headset, for example. But while I could pair the headset, the phone would not answer a call. Sorry...
Ok, meaning there aren´t any known way that we can go around this small problem. Guess I have to take out the phone and say my nametag to the phone and then put it back and talk in the handsfree. Well, of course it works even though it is a bit annoying...
emil73 said:
Ok, meaning there aren´t any known way that we can go around this small problem. Guess I have to take out the phone and say my nametag to the phone and then put it back and talk in the handsfree. Well, of course it works even though it is a bit annoying...
Click to expand...
Click to collapse
Yes, that is exactly what I do. However I put the phone away when not dialing. The handsfree will answer the phone, just won't transfer voice dialing commands.
Ok exactly the same I do then. Thanks for your reply. At least I know there is no point in trying to get it work, as for now....
Have a read of this thread: http://forum.xda-developers.com/viewtopic.php?t=31515
i've been looking for the answer ( i think it should have been something that more people are suffering from but i was wrong )
i have a new headset. the sony hbh-ds970 nifty little thing. however when i'm receiving a call i only see the phone number on the screen. is there a way to display the name that the call is from when it is in my phonebook?
p.s. i'm using that upgrade to enable a2dp
Yes I know, it's really hard to find something here. Indeed there are more people than only you, who would like this feature to be supported! But bad news! Please read my little review of the headset in combination with the Magician in the A2DP thread: http://forum.xda-developers.com/viewtopic.php?p=337217#337217! So far only the point that MortPlayer does not support AVRCP is outdated.
The short conclusion, that matches also this thread is: "To sum up, the HBH-DS970 is a high quality product and the "Walkman" logo on it is justified. Only the Magician is not an equal counterpart to it."
well i'm willing to start on such an application. but i was looking yesterday, and since havn't found any sdk for the ppc2003se bluetooth stack. No api, actually finding info on a2dp or avrcd was pretty hard to come by.
Can anyone point me in the right direction (sdk for the ppc2003se bluetoothstack?)
i have some good ideas on how to implement the stuff.
That would be really nice! But I don't know if there is an SDK for the stack, maybe ask in a seperate thread!?
hmm why does the caller id sometimes work and sometimes not? i just got a call from a friend, and his name was in the screen, after the call i tried to phone and i got the right name in screen... pretty weird :S
Guys,
try this app (JETware Hands-free Extension for Windows Mobile phones) @ http://www.jetwaremobile.com/index.htm
It works!
The best option until M$ decides to implement it by their own in BT stack...
Conchas said:
Guys,
try this app (JETware Hands-free Extension for Windows Mobile phones) @ http://www.jetwaremobile.com/index.htm
It works!
The best option until M$ decides to implement it by their own in BT stack...
Click to expand...
Click to collapse
I mentioned this already and it does NOT work for me!
Unauthorized said:
I mentioned this already and it does NOT work for me!
Click to expand...
Click to collapse
Luckily, It work with my magician, Name of incoming call display correctly in Sony DS970 bluetooth
I am in the process of moving from a TP to a TP2, and am configuring the latter, however (and I have seen this problem elsewhere regarding this phone) I cannot get my bluetooth headset to play nice with MSVC. Specifically the button to initiate the call.
I have tried the steps listed by bengalih and all should work. From what I have read, they are using a different bluetooth stack for the TP2 which is the issue.
So I have a few questions.
1. Has anyone got the headset button to activate MSVC successfully?
2. Is there a way to change the bluetooth stack without changing the ROM
3. will changing the ROM fix this? Any way I can tell which ROMS will have a working bluetooth stack?
I have Vodafone UK branded model.
This is I think the last thing that I need to make the phone 'functional' for my daily use, and so would be really grateful for any advice.
crazyC said:
[...]
1. Has anyone got the headset button to activate MSVC successfully?
2. Is there a way to change the bluetooth stack without changing the ROM
3. will changing the ROM fix this? Any way I can tell which ROMS will have a working bluetooth stack?
[...]
Click to expand...
Click to collapse
1. Yes, with certain headsets that will allow a verrry loooong press without turning off.
2. I suppose it's theoretically possible, but I do not know for sure.
3. Yes. Some of the cooked roms work fine with MSVC and bluetooth headsets on the TP2.
Could you give examples of the cooked roms that work?
Cheers
C.
any trick or hack we can borrow from "bt-MSVCworking roms" and transplant in stock roms? maybe a skilled dev might try to do something.... PLEASE guys!
crazyC said:
Could you give examples of the cooked roms that work?
Cheers
C.
Click to expand...
Click to collapse
NRGs Genesis ROM works for me. http://forum.xda-developers.com/showthread.php?t=553506
Gordon
Flashing now and will confirm experience with my two headsets shortly.
EDIT:
Only had time to test the specific problem identified at the start - both headsets work fine now. Hurrah. I do not know the specifics behind why, or if this will apply to all 6.5 based roms. But for anyone desperately seeking a resolution the headset initiation of MSVC, using the ROM above does fix it. And so far the NRG ROM does seem good.
crazyC said:
Could you give examples of the cooked roms that work?
Cheers
C.
Click to expand...
Click to collapse
I currently use EnergyROM version 20090822 (Titanium) with MSVC 1.6.21040.
Thanks to those above for their help.
thank you for the contribution, but for who is keeping stock rom, any possible solution??? I would sell my soul for this...
A "stand alone solution" for Touch Pro2s with an original ROM would be great. Possibly one of the ROM cookers can extract it for us.
Thanks a lot in advance,
Klaus
that would be really appreciated!!!
Got it to work, but...........
Hi I have a TP2 with MSVC installed. I got it to work by editing the regsitry and swapping SDDialer.exe with voicecmd.exe. It works great. I press the button on my bluetooth headset and MSVC is invoked.
The only problem is that the voice commaned that i say has to go through the TP2 microphone not the bluetooth headset microphone. Any one knows how to direct the audio input to the headset microphone???
I am using Miri cooked ROM 23017 with manila v2.5
rgd
Raed
this bluetooth activation is a real bugger!! does the audio from VC go to the device loudspeaker, or BT headset? that would be a beginning, somehow...
any luck with cyberon voice commander yet?
cyberpunk627 said:
this bluetooth activation is a real bugger!! ...
any luck with cyberon voice commander yet?
Click to expand...
Click to collapse
Well I have the Voda version of the TP2 and I also have a spare to play with (I cracked the screen on my first one and got a new one but they never asked for the old one back - it works fine) so I loaded the EnergyROM from a link elsewhere on this thread on to it. My bluetooth headset does not work with the Cyberon Voice speed dial program which I prefer - although this ROM does alow you to put all sounds through the headset. It worked fine on my old TyTn from Voda. Like you said, this is a real bu**er!
Barry
mmmh I'm becoming more and more obsessed with this. I googled everywhere but found anything... someone reports msvc and cvc as working, someone else not.. but nobody says it's working from BT headset... blame on htc that forgot such an important thing!
cyberpunk627 said:
mmmh I'm becoming more and more obsessed with this. I googled everywhere but found anything... someone reports msvc and cvc as working, someone else not.. but nobody says it's working from BT headset... blame on htc that forgot such an important thing!
Click to expand...
Click to collapse
It's all true
I understand that on the Telus ROM MSVC works with Bluetooth out the box
MSVC and CVC do work, UNLESS you want to use Bluetooth, when they don't (with stock ROMS in the EU) ;-)
I'm using MSVC on NRGs Genesis ROM and it works from Bluetooth as it should. If I get a Chance I'll install CVC and give it a try and report back.
Gordon
it would be nice if someone can mange to transplant needed files... I like the bluetooth stack on TP2, really better than usual, but this thing needs more attention from HTC and the 3rd party developers.
msvc is 3 years old as of now, no newer versions, same as cvc... too bad, technology evolved a lot it 3 years, and these programs might improve really really much!! especially the recognition algorythm, and functions.
well, I hope the new wm6.5 will bring some BT improvements for TP2 then...do not want to stick with custom roms yet. keeping my fingers crossed!
should you manage to try, let us know about cvc and make a little comparison for us! you lucky! ;-)
cheers
I´m usign Smaberg´s Touch X "HERO" EDITION and VC works just fine.
GordonTGopher said:
I'm using MSVC on NRGs Genesis ROM and it works from Bluetooth as it should. If I get a Chance I'll install CVC and give it a try and report back.
Gordon
Click to expand...
Click to collapse
As my touch screen has died I am without a TP2, so I can't do this for the moment
Gordon
I've had this problem sometimes on my VZW CDMA Touch Pro 2. my solution has been to turn off the headset and turn it back on. It seems the problem starts for me when I have the headset on when rebooting the phone. Possibly MSVC doesn't detect the presence of the headset or something to that effect.
I used to use MSVC 1.6 on the Tytn2 on WM6.5 (see sig) and the confirmation notifications when you called someone always used the bluetooth headset. Since running it on the Leo MSVC seems to use the loudspeaker on the handset instead of the bluetooth headset even though every setting is marked as "Announce notifications using Bluetooth hands free only"
Anyone else having this issue as I did a search and couldn't find anyone.
Edit: Just had it working once but then the other end couldn't hear me when the call connected. Then I tried again and it had reverted back to not working.
I went to Bluetooth settings, Advanced, Audio and ticked the box then rebooted the phone...
I have this same problem! Its annoying... you want to make a call and the prompts/confirmation come from the phone... Please, can someone figure this out?
Bumping thread as it should be resolvable
Starfury said:
Bumping thread as it should be resolvable
Click to expand...
Click to collapse
IT isn't... I have done more research..
The Leo (and the TouchPro2) use a Widcomm BT stack as opposed to the usual MS stack. Sadly, this means the BT won't play nice with a lot of different apps/equipment. This isn't something that can be swapped out easily as NRG has pointed out. Touch Pro 2 users are still facing the same problems even though that phone was released much earlier. Some however have reported some success when using certain custom ROMS... how its working with some ROMS and not others is still a mystery it seems
I would watch the ROM Development thread carefully to see if a ROM what works with our MSVC shows up....
Hello,
Is there a workaround... ?
Thanks in advance for any info,
Jean-Jacques
I have the same problem. I'm using an old phone when I need to use hands-free. After spending a lot of money on my HD2, I'm not impressed.
I there a particular combination of headset and software that does work, especially for voice dialing?
have you tried this?
I would, but I don't know if I even have voice command on my phone.
http://forum.xda-developers.com/showthread.php?t=634494
DrATty said:
I there a particular combination of headset and software that does work, especially for voice dialing?
Click to expand...
Click to collapse
Does not work with my helmet bike with scala-rider Q2, but does with does with Philips SH9000 stereo headset...
Mono/Stereo seems to matter.
Any workaround would be veryyyy appreciated
Jean-Jacques
Workaround
Hi,
for this following workaround seems the only way to get it runnin:
My BT-Headset has the ability to be set as a Stereo-Device. When I establish a connection to this Stereo-Device, I can use it (my BT Headset) to give Commands and recieve "answers" from the VC. In case I want to start a phone-Call, my headset changes the connection automatically from "Stereo-Device" to "Handsfree-Device" and back, after finishing the Call.
This may be the Reason, why someone here already got it running with a BT-Stereo-Headset.?
Sorry for my bad english...
I have a problem and have't been able to find any information on it. I have a TMoUS HD2. I had an original Jawbone lying around so I paired it and it works perfectly. I decided to pick up a Jawbone 2. I paired it, but it developed a problem. While outgoing calls are no problem, I cannot answer calls with it, nor can I initiate voice dialing with it. Incoming calls are routed through the handset. I deleted the pairing, and re-paired it to no effect. I also tried the original Jawbone again and it again worked fine. What I don't understand is why it initially worked properly, then developed this problem (with no changes to the phone).
Any ideas?
me too
Same problem with Proplantronics headset, new to me handset formerly T-Mobile just loaded this ROM:-
RUU_Leo_HTC_WWE_1.48.405.2_Radio_Signed_15.28.50.07U_2.05.51.05_2_Ship.exe
If I find the answer I will let you know.
mcc2905 said:
Same problem with Proplantronics headset, new to me handset formerly T-Mobile just loaded this ROM:-
RUU_Leo_HTC_WWE_1.48.405.2_Radio_Signed_15.28.50.07U_2.05.51.05_2_Ship.exe
If I find the answer I will let you know.
Click to expand...
Click to collapse
well, it was probably me. I was answering with the handset rather than the earpiece. it didn't matter with the old one, but it does with this one. chalk it up to unfamiliarity with the newer unit. either that or the phone woke up in a better mood today.
sorted
Yes, thanks for that, pressing the call control on the headset is the answer, also found the autoanswer option which should also fix it. Lots of stuff seems to be hidden away on 6.5.
Still learning after all these years.
mcc2905 said:
Yes, thanks for that, pressing the call control on the headset is the answer, also found the autoanswer option which should also fix it. Lots of stuff seems to be hidden away on 6.5.
Still learning after all these years.
Click to expand...
Click to collapse
Glad my fumbling around with this thing was able to help someone.