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.
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 just recently purchased the Desire and the same night I rooted my phone with unrevoked. Since then I have been unable to send and receive MMS. Some of my coworkers who got new phones the same day and didn't touch them are able to receive MMS. My question is, do you think that this is because I rooted it, or chance it is a problem with my phone? If it is a problem with the phone, do I have to unroot it before bringing it in to my service provider or do you think they wouldn't notice?
Prob be something to do with the root. Just flash a stock Froyo rom and it should be alright. Just make sure you do a nandroid backup first just to be safe
I had the same issue with my Desire, but managed to fix it just yesterday.
Find the homepage for your provider and they normally have a guide for setting up MMS, which is, normally in the case of HTC Desire, automatic. But if you try see the manual set-up for non-supported phones and you enter those values/data, it's all gravy again
Sounds like a pretty common problem with small providers. I tried looking around and was unable to find any settings on the website...
Try see if you can Google it. I noticed that there are sites which are dedicated to collecting all the settings of different providers (definitely here in DK) and making them accessible in tables.
Sent from my HTC Desire using XDA App
Man...I've been trying to find it but I can't....I have cellcom (usa-Wisconsin) maybe someone else can help me locate something.
Sent from my HTC Desire using XDA App
Okay, I also tried seeing if I could find the settings for cellcom in the States and no luck: just Israel. Also not a very informative webpage for cellcom either.
If you don't want to unroot your phone etc. I would think contacting the company by mail and asking for the manual settings might pay off. I'm pretty sure this is the issue as mms and internet settings are automatically set-up for each phone model in some providers and rooting might have removed the settings from identifying it as an HTC Desire, though I have no way to be sure.
So you should receive a reply with the MMS proxy and port, the MMSC and APN.
It definitely worked for me.
Hope it all works out!
Managed to get a HTC Desire for an absolute steal of a price as the seller had managed to forget his lock pattern and hadn't set up a google mail account to bypass the lock pattern. Having used Android phones before I knew that if I could just figure out the correct combination of buttons on startup I'd be able to reset the phones to factory settings and have a working phone.
So, I quickly bought the phone, figured out the "Power+Vol Down" combination and ran a factory reset from within that menu.
The phone restarted and I went through the setup and everything seemed fine, until I tried to send a text/make a call.
When I send a text message, I get the message sending failed error and it retrys various times before the phone finally gives up and stops trying.
When I try and make a call the phone just hangs for a couple of seconds on the dialing screen, beeps and cuts off (as though I have no signal).
I assumed that the phone had been blocked, hence the seller was selling it so cheap and he had come up with this story of locking it out, but after having a play I realised the internet was working perfectly and I had full HSDPA signal. Now correct me if I'm wrong but I'd have no sort of connection if the phone had been blocked by the carrier?
I assumed this was a software issue and have updated from 2.2 to 2.3 but still the same issue. After updating, I've also realised that I am unable to change network carriers (I'm on TMobile and they now share networks with orange).
My sim works perfectly in other phones and if I put another sim in the Desire, it still has the same issues. The phone is locked to TMobile (not that I think that would matter), running the official HTC 2.3 Gingerbread release and as far as I'm aware my APN settins are all okay.
If anyone could shed any light onto what is going on here, and hopefully to a fix then it would be greatly appreciated
Thanks in adavnce
Please use the Q&A Forum for questions Thanks
Moving to Q&A
my apologies, thanks for moving me to the correct forum
I followed all the steps that I could and am still unable to unlock: http://forum.xda-developers.com/showthread.php?t=2024514
my phone is originally kodoo (t989d)
The owner that gave me the phone claimed that it was unlocked but I am uncertain and am on the pessimistic edge of whether that is true or not. When I insert a SIM while the phone is off and then turn the phone on it does not ask me for an unlocked code, and never has even after starting up and using the phone, but the notificationas area gives me the message that 'network locked sim card inserted' .
Everything up to the point where I have to enter the #???# code works fine but when i input that code nothing happens ever, no menu opens up or anything. when I press call it says 'not registered on network.
The radio I have is t989uvle1 and the kernel is 3.0.8-perft989dtllg2.......
Honest to god I have been searching the forums since 12am (now 8 hours) and am just completely lost. I dislike posting like this because I have to wait for replies but in this case I really cannot find anything.
I have read recommendations of flashing a tmobile rom or changing the kernel or something but am really clueless on how to do this and have tried flashing random 4.1+ roms to no avail. can anyone shed some light and set my in a right (and very specific) direction. what the heck is going on???
Are you able to make phone calls with the new SIM card?
Sent from my Nexus 7 using xda app-developers app
Someone answered this in the other thread you copy pasted this to.
You need to have an ics rom and stock radio. Or something like that.
Sent from my cellular telephone