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.
Related
Hey all, i just flashed my T-Mobile Dash with the latest WWE 1.33.422.1, and i have a couple of issues that i am unable to solve.
1) Why does the carrier name say "Get More...", and is it possible to change this?
2) Is there any way to enable alphanumeric dialing like there was on the t-mobile rom? Not with the call screen background hack, i mean true alphanumeric dialing. (registry edit or something)
Help is greatly appreciated
glitchman said:
Hey all, i just flashed my T-Mobile Dash with the latest WWE 1.33.422.1, and i have a couple of issues that i am unable to solve.
1) Why does the carrier name say "Get More...", and is it possible to change this?
2) Is there any way to enable alphanumeric dialing like there was on the t-mobile rom? Not with the call screen background hack, i mean true alphanumeric dialing. (registry edit or something)
Help is greatly appreciated
Click to expand...
Click to collapse
I tried using an original Dash homescreen and it displayed as T-Mobile. I'm guessing it's hidden in the home screen XML.
I tried dumping the registry from the Dash ROM and the new ROM but there are too many differences between the two for me to figure out if it's a simple registry change. (At least not without a guide).
hmm, using a home screen from another one did it for you? thats weird... im using the same home screen i was using on the T-Mobile firmware and it still isnt displaying properly....
glitchman said:
hmm, using a home screen from another one did it for you? thats weird... im using the same home screen i was using on the T-Mobile firmware and it still isnt displaying properly....
Click to expand...
Click to collapse
I wonder if it's location based, but it did say T-Mobile when I was using the blue T-Mo homescreen.
I would check, but I flashed back to T-Mobile's ROM, I didn't like the quirks in this one.
I agree, my only big complaint about this rom is the lack of alphanumeric dialing.
I've installed the cab that puts the image up with the letters, but it DOESN'T SHOW DURING INITAL DIALING, only during a call.
WTF?
Anyone have any idea how we can figure this out?
with theh htc rom there's two images you have to overwrite, not just one.
HTC_BrandingBrickImg_320x27.bmp
and
HTC_CallProgressBkg_320x186.bmp
replacing (or editing) those two images will give you the button image (or whatever you want to call it) for a regular phone.
Hey everyone, got a quick question.
I just finished installing the WM6.1 ROM for my T-Mobile dash, and it looks really nice. Everything is working fine, but I have two small problems.
The first thing is that for some reason, my phone wants to put a + in front of all outgoing calls. So if i make a contact in my address book with the phone number of 212-555-1212 and try to call them, the phone places the call as +2125551212 and I get an error from tmobile saying that 'The international phone call you are trying to make cannot be completed...' I realize that + denotes the international dialing prefix, and I can get around it by setting up all my contacts with a '1' before the area code, but there has to be a simpler solution as this was not the case with the original rom. If I dial a number normally, it doesn't put the + before it. Any ideas?
Lastly, I am having a hard time finding out how to disable the JOGGR from doing in-call volume adjustments. While I like it for scrolling, I find it really annoying in phone calls as it is constantly missreading my face as my finger and adjusting the volume up and down. In the original t-mobile rom there was an option under settings for it, but I can't see it in the new rom. I went into the registry editor and tried disabling one function that looked like what I wanted to turn off, but it didn't work.
Any help would be greatly appreciated. Thanks!
-James
No idea about the + but the JOGGR disable is still in the Settings. It is on the 3rd page, #3 JOGGR.
choekstr said:
No idea about the + but the JOGGR disable is still in the Settings. It is on the 3rd page, #3 JOGGR.
Click to expand...
Click to collapse
Thanks for the reply. Yeah, I am able to disable the JOGGR completely using that, but I was hoping for a way to use it for scrolling, but not for volume control.
In regards to the + problem, I went through every option in Settings and couldn't find anything. All the Regional information is correct. I even used the RegEditor to search for + in the entire registry, and it came up with nothing relevant.... Weird. Especially because even if this is an international version, there shouldn't be a + in front of all calls by default, because that would force an international call no matter what country you are in...
Well, I think that it fixed it self in regards to the + problem. Even though I had done so before to no success, figuring that it is running a Microsoft product, a couple of reboots later and it seems to have gone away. Hopefully this isn't a bug that will continue to resurface or is the tip of a larger iceberg.
Just FYI, the + is the prefix for international dialing. If you input all your contacts as +1-404-555-1212 you won't have the problem (1 is the country code for the USA). Another plus to this method is that, if you should go outside the US to a country that uses the GSM network, you can dial your contacts directly via whatever carrier you're on there.
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
Hi All,
I looked thru 160 pages of searching with different keywords, and didnt find answer. I have the stock ATT rom, hard spl to add the 4.49 radio, have personalizer and Photo Contacts Pro 5.5 on it. Nothing else except to the two cab fixes to reduce ram useage.
The problem is at times when I get a txt msg and I hit reply the txt opens up and when I slide the phone to expose the keyboard to reply, the phone will freeze up, the cursor is still blinking to input but the buttons and the touch screen is not responsive, I have to hit the reset button on the side of the phone to regain control. Anyone else having this problem and is there a fix for this?
Check the hot fix on HTC's site
I have had the same issues and HTC recomended installing both hotfixes as they fix alot of other isses other than what is shown. I will let you know how they work as I am installing them now.
i have the att tilt 2 and tried to install the hotfix to stop my phone from freezing but when i tried to run the installer its said not compatible for this phone??? what is the deal?
kenyaata said:
i have the att tilt 2 and tried to install the hotfix to stop my phone from freezing but when i tried to run the installer its said not compatible for this phone??? what is the deal?
Click to expand...
Click to collapse
Yep had the same problem when I tried to install the caller ID fix. the sms fix installed fine no issues there. I think the reason why it might have said its incompatible is because it might have been for the WinMo 6.1 not for the 6.5 version. I read somewhere (sorry who said it) that it checks against the loaded rom. and my feeling is the sms fix wasnt corrected in the 6.5 version but the caller id was, possibly. I have Tilt 2 from ATT and it has WinMo 6.5 on it stock, just hardspl-ed it to add the newest radio to it, which is 100x better then the stock version that came with the ATT rom.
The hotfixes only work on the stock ROM. Not sure if the fact that the OP changed the Hard SPL and the radio would prevent the hotfixes from installing. And the stock ROM for the Tilt 2 is WM 6.5, not 6.1.
I know the tilt 2 comes with 6.5 I stated that already but I tried the caller id fix before I hard spl when I had it only couple of days ago and still wouldnt update on the stock att rom with no tinkering.
The hotfixes will work on HardSpled phone as long as rom is original. I did mine when they first came out with no issues.
I also looked a little more closely at this, I installed the rom 1.86.401.0 that comes with the radio 4.49.25.14 and the date of this is new compared to the hotfixes, with that said would it be safe to assume the hot fix is already implimented? Cause ever since I dumped the ATT stock rom and add this htc original rom, and the tweaks I wanted to add, I have had no issues with the phone and have not installed the hotfixes except for the keyboard which seems to have come out after this rom update.
Any word on how we can get it to work on the phone with other roms?? or if I go back to th eoriginal will it work... I am basically stuck in limbo every time i go into sms now and i am about to drop kick the phone.