Related
Has anyone been able to figure out why the ATT roms are experiencing the numlock situation when on a phone call. This seems to be the only issue I have experienced on this ROM but is quickly becoming a showstopper.
Number keys stuck while in-call. Doesn't seem to be resolved yet per the Pro's
"8/04/2007 Originally Posted by schaps
Not yet, this problem also occurs on official WM6 ROMs so it doesn't help me to focus the problem.
But for sure this issue is not caused by the keyboard driver."
Put me in the list of people wanting a fix for this. I hope someone figures it out. I often like to text while using my bluetooth, and I don't enjoy having to pull out my stylus to do so.
Just wishing the talented developers some luck in figuring out the problem!
Add me to the list too ... i've looked all over but hadn't found the fix. I remember seeing it somewhere when doing my WM5 ROM upgrade (a long time ago).
Any progress on this?
I'm using Shamanix's Ultimate 1.0.
I don't need to send SMS while calling but I've got the device locked and if I need to check the Calendar during incomming call for example, I need to type my password. Would be really nice to type on QWERTY instead by stylus.
thx
This has been Fixed In More than One Rom....TNT,Vp3g's plus other Roms... I"m going to be Compiliing a List soon of Roms that do and Do not have this Fix.... Certain Schaps Rom also have this Fixed as well but not all...sometimes either he forgets or They Fix interferes with other things onthe ROM not sure....
I can definitely vouch that it works correctly in vp3g's rom.
Would be nice to know what is causing this and how exactly they managed to get it to work so we can fix this on our ROMs.
the fix is already there.
http://forum.xda-developers.com/showpost.php?p=1562185&postcount=63
Hi Guys,
I've just ordered 17 touch pro 2's for work and I'm very impressed with them so far. Absolutely awesome phone. We've just got one issue which is the fact that when the phone is locked (we used centralised policies with exchange) you can't dial from our Parrots. The phone says you must unlock the device to allow bluetooth connection.
Does anyone know a way around this without taking the locks off of the phone which is a big no no. Tested it with a collegue's Omnia and it works fine.
You can replicate this issue by using the Bluesoleil dialer which is what I've been doing for testing.
The parrot receives calls fine, just can't make them he the phone is locked.
TIA.
Same problem
Hi there,
I'm having the same issue for dialling out via bluetooth whilst the phone is locked. The TP2 says it needs to be unlocked before answering the call.
There MUST be some registry key to change to prevent this "feature" ... none of the previous HTC phones I have had have had this problem.
Thanks in advance for any help!
i have the same problem, i installed s2u2, which solves the not being able to dial out when its locked, but it's not the most reliable solution.
i'd rather have it working like it did on my kaiser before this phone.
hope someone helps us out.
I tried out S2U2, but the problem is it's only a keypad lock, so plug the phone in USB for example and you still have full access to the device.
S2U2 also does not stop you sliding out the keyboard and pressing the mail button to read the emails on the phone, so this isn't a solution we can use, it's not even a compromise
Haven't had much luck with HTC support either. They are very quick to respond but don't respond with anything of value.
I just wanted to bump this thread -- I picked up a Tilt2 and have the same problem -- really annoying when trying to dial from the car and having to unlock (didn't have this issue on my Fuze).
Yeah this is the most annoying thing I have ever seen. There must be a way to turn it off. I use Ford Sync and really don't want to have to worry about my phone being locked or unlocked. Seems like this goes against all those phone laws. You are making me look at my phone first to make sure it isn't locked before I can safely dial.
Wish I had found this thread before I went ahead with getting a Tilt 2. Didn't have this problem with my Tilt.
Is this a WM6.5 limitation? Hopefully there is an obscure setting that I'm too stupid to find.
Cheers
... and I was just about to ask on this thread whether or not this was still a problem in WM6.5 but I guess I have my answer now.
It's definitely an issue in WM6.0
I contacted AT&T and they said to contact HTC.
HTC gave me this answer:
Thank you for contacting HTC Technical Assistance Center. I apologize for the length of time it took me to respond to your email. I understand how important it can be to use Bluetooth from your device when your device is locked. I will be happy to address the concern for you.
There is not a setting on your ATT Tilt 2 for enabling Bluetooth when your device is locked. When pairing Bluetooth with your vehicle your device must remain unlocked to use the correct functionality. I would suggest placing your device into hibernation mode and keeping your device in a carrying case.
Hi,
I have upgraded by TP2 with the offical HTC rom for 6.5 and installed my blackberry connect 1.06 client. Now, even with the BB lock enforced, as it was with the TP2 using 6.0 and it is working perfectly handsfree in my CAR, locked or not. Previously the TP2 with the stock 6.0 ROM wouldn't make calls when locked.
If people are reporting here that is didn't work in 6.5, then there must be a registry setting somewhere to enable or disable it.
I am just happy that I can make a call in the car, without having to pull over and unlock my phone.
If someone can give me a hint as to where in the registry to look I can compare some settings?
I have a stock AT&T Tilt-2, I loaded loaded "smartlock 1.7" to autolock the phone at power off and also when "in-call" to avoid random dialing. I don't use the PIN for locking.
I can dial hands free BT in my car and with headsets with no issues, power on/off whatever.
Maybe it'd disabled when locked with the PIN?
I am seeing the same issue with two of my users:
One is using a Verizon Wireless TP2 with MW6.1 stock ROM
The other is using an Unlocked HTC touch Pro 2, on the AT&T wireless network (not a Tilt2) with the HTC WM6.5 ROM upgrade.
The Verizon users is using Sync on his Ford Vehical. The other is using whatever system is in his BMW.
Both can pair with the car's system, but if the phone is locked with a PIN the user is not able to place a call without first unlocking the phone.
Has anyone found any information on this?
If MSVC is an option then it has the ability to dial while password protected.
Just noticed this has been bumped. I upgraded all of our phones to the standard Windows Mobile 6.5 from Vodafone when it came out a month ago and this problem is now resolved you'll be glad to know.
I've got 25 handsets currently working fine with no real issues. All the niggles that I had have gone away with 6.5 so it's definately worth the upgrade.
6.1 was screwed and no use with handsfree dialing if you use windows lock which we enforce on our exchange server.
Seems like every provider is a little different.
I have the AT&T Tilt 2 which came with WM6.5, AT&T support claims its a Microsoft and HTC problem. HTC claims its a Microsoft problem.
Anyone have a good support link to Microsoft to get this problem resolved?
Can someone with a working 6.5 rom please post the following registry info to see if there is a way to enable the bluetooth dialing on the roms that are not working?
HKLM\Software\Widcomm\General
When you get the unable to dial message it puts a new key in there called DontAskHfpCallFailOnDeviceLock and I figure that the bypass might be in this same area.
Registry
Here is everything under the BTConfig\General section.
[HKEY_LOCAL_MACHINE\Software\WIDCOMM\BTConfig\General]
"StackMode"=dword:00000001
"DeviceName"="HTC-ST7377"
"BDAddr"=hex:\
00,23,76,37,a9,89
"BlockBTIfHopper"=dword:00000001
"SendCompressedTelProperties"=dword:00000001
"UsePocketPCName"=dword:00000000
"UnnamedDeviceName"="<No Name>"
"UartPriority"=dword:00000096
"TransmitPriority256"=dword:00000098
"SuspendWithScoConnected"=dword:00000001
"SuspendTimeout"=dword:00001388
"SndPriority"=dword:0000009b
"SecurityType"=dword:00000002
"SCODelayTime"=dword:000007d0
"ReceivePriority256"=dword:00000097
"RadioInitLibrary"="BRCMInit.dll"
"PowerControlLibrary"="Serial_BTUR_DM.Dll"
"PCRemoteAutoConfig"=dword:00000001
"OriginalAudioDriver"="wavedev.dll"
"KeepStackLoaded"=dword:00000001
"EnableAFH"=dword:00000001
"DiscoverableTimeout"=dword:0000003c
"DeviceInactivityDuration"=dword:0000003c
"ConnectRelatedDefault"=dword:00000000
"BIPEnabled"=dword:00000001
"AFHAvoidedChannels"=dword:00000014
black88mx6 said:
Can someone with a working 6.5 rom please post the following registry info to see if there is a way to enable the bluetooth dialing on the roms that are not working?
HKLM\Software\Widcomm\General
When you get the unable to dial message it puts a new key in there called DontAskHfpCallFailOnDeviceLock and I figure that the bypass might be in this same area.
Click to expand...
Click to collapse
erenken said:
Here is everything under the BTConfig\General section.
[HKEY_LOCAL_MACHINE\Software\WIDCOMM\BTConfig\General]
"StackMode"=dword:00000001
"DeviceName"="HTC-ST7377"
"BDAddr"=hex:\
00,23,76,37,a9,89
"BlockBTIfHopper"=dword:00000001
"SendCompressedTelProperties"=dword:00000001
"UsePocketPCName"=dword:00000000
"UnnamedDeviceName"="<No Name>"
"UartPriority"=dword:00000096
"TransmitPriority256"=dword:00000098
"SuspendWithScoConnected"=dword:00000001
"SuspendTimeout"=dword:00001388
"SndPriority"=dword:0000009b
"SecurityType"=dword:00000002
"SCODelayTime"=dword:000007d0
"ReceivePriority256"=dword:00000097
"RadioInitLibrary"="BRCMInit.dll"
"PowerControlLibrary"="Serial_BTUR_DM.Dll"
"PCRemoteAutoConfig"=dword:00000001
"OriginalAudioDriver"="wavedev.dll"
"KeepStackLoaded"=dword:00000001
"EnableAFH"=dword:00000001
"DiscoverableTimeout"=dword:0000003c
"DeviceInactivityDuration"=dword:0000003c
"ConnectRelatedDefault"=dword:00000000
"BIPEnabled"=dword:00000001
"AFHAvoidedChannels"=dword:00000014
Click to expand...
Click to collapse
erenken,
Thanks for the info. The only item different on my 6.5 Tilt2 is that I also have a key "DontAskHfpCallFailOnDeviceLock"=1. Sounded very promising.
Unfortunately, changing this key to 0 and even deleting it doesn't make a difference: I still cannot dial via bluetooth while the phone is locked with a pin. I tried these changes both with and without a soft reset between.
mnunes:
Were you able to find a fix for this? I am in the same boat.
DaBody1 said:
mnunes:
Were you able to find a fix for this? I am in the same boat.
Click to expand...
Click to collapse
No, so far no luck. I can't say I've been looking very hard, though. It's one of those things I've started to learn to live with, as annoying as it is.
I'm working with a Tilt2 running the stock euro HTC 6.5 rom
and I have an odd delay. once a call comes in and I either use
the "slide to answer" feature or if i just press the call answer button
there is a long...sometimes 10 second delay between my action and
the call actually connecting.
During this time i often miss calls and ive asked those who are calling me
what they hear and they say my phone goes silent for 10 seconds before i
answer. any ideas?
Someone else found this link, not me -- and I haven't tried it, but I have experienced similar (3 secs though and not often).
http://forum.ppcgeeks.com/showpost.php?p=458469&postcount=1
After doing this it does seem to pick up the calls a lot faster but now I'm getting a slew of various data connection errors. SOTI wont connect, my weather tab will not connect.
Thanks for the assist I'm going to try and find a happy balance between the two reg settings
Update: I was wrong initially about the reg edit fixing things. I had my wife call immediately after the edit and it seemed to fix it when I noticed the connection issues through various programs.
Well during work today I answered about 7 calls. The delay affected all of the and on all but 1 the call actually disconnected before it allowed me to speak. so i will be reversing the red edit to combat the connection issues.
So clarify a few questions I Got regarding this:
When the phone rings and I press the answer button or "slide to answer" the ringing does stop and the icon in the task bar shows a call connected. but for me and my caller we hear dead silence for 10 seconds until they either hang up or the call connections. Any ideas friends?
I'm having the same issue on my US AT&T Tilt 2. It is driving me crazy, the regedit did not fix anything for me either. Did you figure you this out at all?
Are you guys running stock or a custom ROM? I have had this issue in seven ROMS. In my case, it seems that my phone has to have the ATT Dialer to avoid this. Tried Energy Photon and Leo,Josh Koss, TPS, and Shadowline. All had this problem. I'm now on Fusion 6.0 with the ATT Dialer. Not one issue. Day before I flashed this one, I missed 19 calls at work because I couldn't get the slider to register. Tried TPC's latest last night(he uses the HTC Dialer), missed calls. Flashed ATT Stock no problem. Fusion is the only other ROM I found with an ATT Dialer.
It seems there is a conflict in the device when connecting.
Some things to try:
- remove the custom dialer (just use the WM6 dialer, but this will loose video calls)
- check if there is some call-recording software that kicks in
- does this happen when the device is off or also when it was already on?
I'm Using HTC's stock rom instead of the ATT rom. since I'm America I really would not be apposed to loosing video call from the dialer since Its not supported on my network but I'm really not sure how to change the dialer back to AT&Ts ...is this something that would have to be cooked into the rom because I cant stand AT&T's rom.
Flash a ROM that uses the AT&T dialer: problem solved.
Your options are: Stock AT&T, At0mAng, Arrupenthal, Twopumpchump roms.
So how do we go about getting a cab file of the AT&T dialer, video share and PTT packages that each individual user can apply as needed? Is this even possible and would it require uninstalling whatever dialer the chefs cooked in? I think it would be impractical to ask the chefs to make two versions of their ROMs (one for at&t tilt2 users and one for everyone else) as I have attempted to cook my own ROM and know how difficult it can be.
Thanks,
Stephen
hi
sorry. bad post
Bluetooth Voice Dialing is in the Froyo feature set.
I can't see this feature anywhere on the Desire after the 2.2 update. Anyone else?
I can't find it either...
really really annoyed about this!! when i bought the phone it was something I really needed! Was told it would be on the phone with 2.2 in a couple of months but now nothing!!! Grrrr!!!
I read somewhere that you can use the voice search do dial someone, and it actually works, but there are two problems:
1) Since the main objective of voice search is to search using google, you need to be on wireless or 3G to start using voice search, even if you don't want to use google at all. So if you don't leave your 3G active all the time, you'll have to activate it before launching voice search.
2) You can't launch voice search by pressing the action button on the bluetooth headset, so you still have to pull the phone out of the pocket to activate it and then give the command.
Those two problems pretty much makes voice search unusable as a replacement to a dedicated voice dialing dialog, because you always have to take the phone out of pocket and interact a lot with it to finally call someone. It's easier to just tap your contact's shortcut to call it.
It was in the leaked ROM that was floating around a couple of weeks ago too! My guess this will be coming in another update around the time that HTC release their car dock. Bloody gits.
in the prerelease 2.2 (LeeDroid) I am using if I press the talk button on the steering wheel it requests a voice command and then searches for whoever you said "call". But it its true that 3G MUST be activated.
Can anyone recommend a 2.2 ROM with HTC sense that has this feature? Is it a good idea for me to reflash do you think?
This was the one thing i was waiting for with the froyo release and it appears to be missing.
Im not seriously considering rooting my phone just to get this feature.
Can anybody recommend me a rom with this feature enabled?
I'm in the same boat, wasn't really bothered about rooting but now it looks like I'm going to have to!
I've emailed HTC on their support page, does anyone think I'm going to get a response?
Sent from my HTC Desire using XDA App
HTC replied to me saying "we can decide what parts of the system are used and which are not".
Removing this from the release is ridiculous. It's so common now for use of hands-free kits to be compulsory, if not the only legal option.
It was my main reason to debrand and upgrade, only to find that it's been omitted.
Maybe some kind soul can manage to knock up an APK from a release where it was included (fingers crossed)
Well here's the response from HTC!
Not good really!
Hi Dave, Voice to text is only available in North America due to the limitations of the voice recognition software database that our phone uses. We are researching the possibility of expanding the coverage of the Voice-To-Text feature but we are still analyzing
the feasibility and currently have no schedule to relay this to you now. We have your contact information on our system and will contact you when we have a solution. Kind regards, Tom HTC
Sent from my HTC Desire using XDA App
Don't tell me that HTC is not going to include this feature in Froyo! I bought my desire AFTER the announcement of Bluetooth voice dialing, and I thought I could wait for this to come in 2.2 update, and now they say they won't include it???? Are they crazy enough to omit one of the main features in Froyo??? What on earth are they thinking?!?!
Correct - they are NOT going to include it in Froyo 2.2
I have the official HTC version of Froyo that doesn't have it, and am rather upset as i would have rooted my phone to get this feature, but I was under the impression I didn't have to.
Now that I've updated to HTC's version not only do I still not have Bluetooth voice dialing, but I also don't have the option to root my phone anymore to get it.
Nice to see that they spent time on real things like a new android graphic, the way the lock displays and other useless but blingy stuff instead of items that were lacking that almost every other phone on the market has for granted.
The_real_dj said:
Well here's the response from HTC!
Not good really!
Hi Dave, Voice to text is only available in North America due to the limitations of the voice recognition software database that our phone uses. We are researching the possibility of expanding the coverage of the Voice-To-Text feature but we are still analyzing
the feasibility and currently have no schedule to relay this to you now. We have your contact information on our system and will contact you when we have a solution. Kind regards, Tom HTC
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
If voice to text doesn't work, how does Google Voice search operate?
This is complete arse.
I thought that in the announcement Google said they were expanding it to work with different accents and languages?
Sent from my HTC Desire using XDA App
might have a little ray of hope....
Search on the market for choice dialer plus
Ive tested it with out my hands free and it recognises my voice really well, apparently it works with bluetooth headsets hands free!
Ill give it a test and post back!!
cheers for that.. let us know..
The_real_dj said:
might have a little ray of hope....
Search on the market for choice dialer plus
Ive tested it with out my hands free and it recognises my voice really well, apparently it works with bluetooth headsets hands free!
Ill give it a test and post back!!
Click to expand...
Click to collapse
I tried it a few days ago and thought it was terrible.
I've tried it and seems to work well, I've emailed the dev as well about the last comment but he said it uses the in built speech to text library so it will be as good / bad as any other android dialer
Hope that helps!
Sent from my HTC Desire using XDA App
I haven't seen this mentioned but has anybody been able to use a BT headset to make, receive, and control calls? I can't. I get "this feature isn't supported on the connected phone" from my Blueant Q2. I know this was an issue with the Sensation and tried installing the voicedialer.apk but the phone won't allow it to be installed. I installed Vlingo but it crashes the phone and I have to do a reset to get it back. Thoughts? Experiences?
Update. We're apparently screwed. There's no native voice dialer included in ICS. I found one that installs but it loses its connection with the headset as soon as it starts. The folks on the Vivid forum are having the same issue. I tried the apps they discussed but they didn't work either. So I guess we wait for HTC to do something.
http://forum.xda-developers.com/showthread.php?t=1562886
BarryH_GEG said:
I haven't seen this mentioned but has anybody been able to use a BT headset to make, receive, and control calls?
Click to expand...
Click to collapse
Yes... ish
I posted the same question a few days ago, but I got no reply, so I bought the phone anyway and tried. Vlingo sort of works with my jawbone earpiece. What I do not like at all is the fact that it does not confirm the command before dialling, or at least I did not figure out how to set it up properly, with the result of dialing the wrong contact in case of a misunderstanding.
I am really missing the simplicity of the blackberry voice dialler, amongst other things (mostly due, I guess, to my being a newbie with android). It was a no-brainer, whilst all the solutions I have seen for android are slightly more cumbersome.
Thanks to the other thread you linked I think I am going to try cyberon voice commander. I could save a couple of dollars/euros buying their voice dialler, but as far as I can see it needs training to attach voice tags to contacts. I don't like the idea of spending time to do that.
This seems like such a basic feature these days, why the hell hasn't it got it?!!!
this is very disappointing news. all the reviews i looked at mentioned voice dialing as a feature. and i just ordered a blueant q2. just tried using voice dial on my phone menu. awful.
i found a retail site online that says the blueant q2 is not compatible with the htc one x and identified several other bluetooth items (including blueant) that are. i decided to try the jawbone era and have it on order. not as many desirable (to me) features as the q2, but if it works, it will be a step up from nothing.
online site is htcpediadotcom. i don't know how reliable it is; first time i've looked at it.
I only just noticed yesterday that the phone would not send the bluetooth connection to the head unit in my car, even though it was connected to it.
I had to use the phones loudspeaker....
All of the Android phones in the past 2 years have worked fine!