Related
I've got the o2 version of the Artemis, had it for a few weeks now and very happy with it. The only problem I've found is that when the device is restarted it sets the default text input as the on screen keyboard and not Transcriber (which I prefer) Is there any way I can set the default method as Transcriber from start-up?
I would happily choose the transcriber each time but clicking the keyboard icon to choose the input from the menu causes a delay of 20-30 seconds for some reason. Does anyone know why this is?
because the OMAP sucks.
I'm not talkin about slight processor lag here tho, TomTom 6 and everything else runs fine with minimal slow downs. And once the menu has been displayed I'd expect it to be quicker the second or third time which it isn't. Could anyone else running the standard o2 build confirm if their's has any delays? As I suspect its a software issue rather than hardware.
I have the same trouble, although not to the extent that you have. I have the T9 input cab, and the text message input dfaults to the keyboard which I find useless as I can't use my finger to do it. I click on the select input icon and it can take 5-6 seconds before it opens.
bit annoying but I get used to it.
I don't have that delay - I use HappyTapping, and T9 input.
Search for a program called AC IMSelecter on here or on google. It lets you overide default keyboard choice, and has helped solve some problems I've had with non-standard keyboards displaying incorrectly.
I think I found it bundled in a HappyTapping keyboard zip.
markquinton said:
Is there any way I can set the default method as Transcriber from start-up?
Click to expand...
Click to collapse
Try this?
http://forum.xda-developers.com/showthread.php?t=289370&highlight=SIP+select
I've just installed the SIP Select program as I couldn't find the one you mentioned Squire. Have got to soft reset to see if it works but need to copy the shortcut into my startup folder first. Cheers for the help guys.
EDIT: SIP Select works a treat, cheers for the link to the file.
Those with the problems - have you installed the Microsoft Voice Commander? This is suspected of causing a massive SIP menu delay.
I've got a solution to improve the speed in switching SIP. Just try to export the registry of HKEY_CLASSES_ROOT_CLSID and import it again. And after that you'll feel much better when you switch SIP.
Don't ask me the reason, because I've no idea at all...
I did have it installed but quickly realised I hardly use it so uninstalled it. Perhaps its left some unwanted registry entries? Does anyone know of a program that can remove unnecessary registry entries for WM5?
EDIT: Talking to Leyton about MS Voice Commander btw
Can someone solve this situation - what is needed:
Hard reset.
Take an image using SKTracker
Install MS Voice Command
Uninstall MS Voice Command
Take an image with SKTracker
Compare the images
Whatever is left over will be the problem causing the slow SIP.
Anyone who does this - please post your results!!
(I would but can't afford a hard reset at the moment)
leyton01 said:
Can someone solve this situation - what is needed:
Hard reset.
Take an image using SKTracker
Install MS Voice Command
Uninstall MS Voice Command
Take an image with SKTracker
Compare the images
Whatever is left over will be the problem causing the slow SIP.
Anyone who does this - please post your results!!
(I would but can't afford a hard reset at the moment)
Click to expand...
Click to collapse
If you have the time, download the WM5 emulator stand-alone for PC, install it there and do all your testings.
leyton01 said:
Those with the problems - have you installed the Microsoft Voice Commander? This is suspected of causing a massive SIP menu delay.
Click to expand...
Click to collapse
I've installed Vocie Commander, only had the Orbit a few days and now this bug is apparent. It's a real pain!! Anyone got any ideas yet?
Edit: SIP Select startup link worked a treat!!
markquinton said:
I'm not talkin about slight processor lag here tho, TomTom 6 and everything else runs fine with minimal slow downs. And once the menu has been displayed I'd expect it to be quicker the second or third time which it isn't. Could anyone else running the standard o2 build confirm if their's has any delays? As I suspect its a software issue rather than hardware.
Click to expand...
Click to collapse
TOMTOM does not need speedy processor, but when you change sip, yes, the speed of processor counts. So just be patient, 5-10 seconds will be ok for you.
biranouran said:
TOMTOM does not need speedy processor, but when you change sip, yes, the speed of processor counts. So just be patient, 5-10 seconds will be ok for you.
Click to expand...
Click to collapse
It's a software issue not a processor issue...
Try Sipchange
URL : http://forum.xda-developers.com/showthread.php?t=271008
It sets the default SIP to whatever you wish.
shkeed said:
I've got a solution to improve the speed in switching SIP. Just try to export the registry of HKEY_CLASSES_ROOT_CLSID and import it again. And after that you'll feel much better when you switch SIP.
Don't ask me the reason, because I've no idea at all...
Click to expand...
Click to collapse
Has anyone tried this. Did it work?? I'm fairly new to the Ordbit/XDA and am not sure how I got about this.
Also, anyone experiencing this problem got any ideas?
If someone has the time and can identify the changed registry key(s) that is left behind using the steps above this can be solved for everyone.
@ markquinton,
I use SKTools/Inputmetodes.....I set tht letterrecognicer as default, deactiveted all other inputmetodes, so I havn´t any problems, ´cause I want to have just 1 inputmetode.
this way works perfect for me.
greetings
sonox
sonox said:
@ markquinton,
I use SKTools/Inputmetodes.....I set tht letterrecognicer as default, deactiveted all other inputmetodes, so I havn´t any problems, ´cause I want to have just 1 inputmetode.
this way works perfect for me.
greetings
sonox
Click to expand...
Click to collapse
That's fair enough, I use SIPselect to default the block recogniser, but the issue remains that if I want to swap between Block recogniser and T9 pad it'll take ages.
I dont know all the ugrade was fine, but now that i wanna set up my wifi in the place my password should go its impossible to type the letter A, any ideas how to fix it??
have you downloaded the keyboard map file and replace with the one on your phone?
download this...no need to replace files..just run this cab and restart
I think somebody played a practical joke on you and messed with your keymap file, switching the two keys around. Hmmm... I just got an idea.. LMAO!! .cab time!
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 have searched but not found any links to a fix, I really like using the stock WWE HTC ROM on my Tilt 2 but I am having problems answering calls with slide to unlock. When I slide it sticks and doesn't answer the phone. Is there a fix for this? I have read I need to use the att dialer but I can't find a cab for it or other patch.
Thank you
I too were having this problem and searched for the answer.
In order to fix it you need AT&T dialer not HTC dialer.
Ok, how do I get that dialer?
Thank you
Since your phone is stock, I don't know what "tweaking" tools come with a stock rom, but do a search for "advanced configuration tool", and inside that program, go to the phone menu and there will be an option for "PHONE SKIN", and it will most likely be enabled (by default). Disable it, and when it asks to reboot, the AT&T dialer will be back. You lose video calling, but I don't think at&t uses that anyway.
I personally like the at&t dialer anyway.
While that solves the problem it also removes the ability to use the speaker phone by placing it face down and also the mute button. From searching I see I need to use the att dialer (not the WM 6.5 dialer or the htc dialer). Anyone know how I can replace the dialer with the att dialer?
murchman said:
While that solves the problem it also removes the ability to use the speaker phone by placing it face down and also the mute button. From searching I see I need to use the att dialer (not the WM 6.5 dialer or the htc dialer). Anyone know how I can replace the dialer with the att dialer?
Click to expand...
Click to collapse
If it's a Tilt 2 - then is was supposed to come with the AT&T Dialer installed. If it's not running now then either it was flashed with the wrong ROM or you have altered the phone somehow. If you have run a COnfiguration Utility of some sort, go back and look carefully at what you altered and set them back to the original values.
You might try a Hard Reset. If it doesn't work after that - take it back for an exchange, either the ROM image or hardware are faulty.
Good Luck!
I ended up running the e2 sense ROM which works correctly.
I have the Sprint TP2 and i seem to have some problems with the internet sharing. I connect the phone to the computer and it just wont connect with it, it gives me this sprint error code. Is anyone else experiencing this problem if so is there a way to resolve it.
Its an easy fix you need to remove a reg key that forces the connection as "phone as modem". Then you can choose to use the sprint connection. I need to look for the reg key.
Edit.
HKEK_LOCAL_MACHINE -> Comm -> InternetSharing -> Settings
Then delete the key "ForceCellConnection"
Here is a reg editor if you need it, let me know if you need help using it. Be very careful not to delete any other keys.
Make sure the program is not running when you delete the key, if it is just restart it or it wont work.
yea sorry man i dont mean to sound like an idiot but this is all completely new to me so i am going to need your help fixing this problem if you dont mind