Develop Bugs

3 seconds Phone ringer delay in Universal

Hello Everybody.Has someone come up with a tweak to get rid of the 3 seconds ring delay (alsmost 2 rings) on the QtekUniversal? i tried the tweak from Tweaks2net but doesn't have any effect on the phone even after resetting it;
Could someone help me out?
T5kanking you all in advance for your valuable inputs.
Brgds, Adhoc

upgrade your radio rom to version 1.06

Ringer delay
kevin666 said:
upgrade your radio rom to version 1.06
Click to expand...
Click to collapse
Hello Kevin.
Thanks but this is not enough.
Adhoc

TO BE DELETED
TO BE DELETED; SORRY FOR THIS DOUBLE MESSAGE

Re: Ringer delay
adhoc said:
kevin666 said:
upgrade your radio rom to version 1.06
Click to expand...
Click to collapse
Hello Kevin.
Thanks but this is not enough.
Adhoc
Click to expand...
Click to collapse
you can try radio 1.08.00 and/or search your registry for "AutoDPDMode" and set all of them to 0.
buzz

Hello Buzz,
What is AutoDPDMode for?

just upgraded to ver 1.08.00 works ok so far no delay in pick up...
http://wiki.xda-developers.com/index.php?pagename=Uni_Radio_1.08.00

Re: Ringer delay
buzz_lightyear said:
adhoc said:
kevin666 said:
upgrade your radio rom to version 1.06
Click to expand...
Click to collapse
Hello Kevin.
Thanks but this is not enough.
Adhoc
Click to expand...
Click to collapse
you can try radio 1.08.00 and/or search your registry for "AutoDPDMode" and set all of them to 0.
buzz
Click to expand...
Click to collapse
Thanks for your input, Buzz. I cannot find any entry encompassing AutoDPD in the registry. Could you please give me the registry path to the relevant section and keys?
Brgds, Adhoc

Mine always begins at the start of the second ring.
1. use the original phone, not the bloated one with video messaging (not as pretty, but saves 3.5mb on load up)
2. remove memory card readers that are present on the today screen (eg SPB and Resco)
3. delays are longer when the contacts list is longer for caller id (I have 80 not 800)
4. consider when pictures and ringtones are also assigned to the contact (just use the standard single ring tone for all contacts, no pictures)
5. if your ring tones are on your sd card, this will also slow it down (move to windows\rings)
6. i extended the ring period also to a full 30 seconds to ensure that I have enough time to get to the phone when it rings out (phone settings voice mail or contact the provider)
I cannot get it to ring at all ever on the first ring, its always at the very beginning of the second especially from sleep mode or suspended)

3s delay before first effective ringing
simon_darley said:
Mine always begins at the start of the second ring.
Mine Too
1. use the original phone, not the bloated one with video messaging (not as pretty, but saves 3.5mb on load up)
Noted
2. remove memory card readers that are present on the today screen (eg SPB and Resco)
Noted
3. delays are longer when the contacts list is longer for caller id (I have 80 not 800)
Noted
4. consider when pictures and ringtones are also assigned to the contact (just use the standard single ring tone for all contacts, no pictures)
5. if your ring tones are on your sd card, this will also slow it down (move to windows\rings)
noted, will try
6. i extended the ring period also to a full 30 seconds to ensure that I have enough time to get to the phone when it rings out (phone settings voice mail or contact the provider)
I cannot get it to ring at all ever on the first ring, its always at the very beginning of the second especially from sleep mode or suspended)
Click to expand...
Click to collapse
Thanks for sharing your experience with me.
Adhoc

I found the AutoDPDMode registry key here:
HKLM\Drivers\BuiltIn\TureFFS_G31 and
HKLM\Drivers\BuiltIn\TureFFS_G32
So, what are they? I guess there are related to ExtendRom and Storage Card.....
So, why disable it? Any effects afterwards???
Cheers,

Folloow up needed on this one!!
chris_khho said:
I found the AutoDPDMode registry key here:
HKLM\Drivers\BuiltIn\TureFFS_G31 and
HKLM\Drivers\BuiltIn\TureFFS_G32
So, what are they? I guess there are related to ExtendRom and Storage Card.....
So, why disable it? Any effects afterwards???
Cheers,
Click to expand...
Click to collapse
Yes, do please share your knowloedge with us regarding this matter!!
Brgds, Adhoc

simon_darley said:
1. use the original phone, not the bloated one with video messaging (not as pretty, but saves 3.5mb on load up)
Click to expand...
Click to collapse
How did you get the original phone?
I tried the suggestions on the other thread where you need to change something in the registry, but that just disables the video messaging leaving a blank part on the screen. I want what you have, the original phone skin when I first turned my Universal ON after a hard reset. This original phone skin disappeared after I performed a soft reset.

From the wiki:
To set or remove the operator phone skin
The setting is at 'HKEY_LOCAL_MACHINE\Security\Phone\Skin'
The 'Enabled' DWORD value can be set to '1' to show the operator skin or '0' to show the default skin

lbendlin said:
From the wiki:
To set or remove the operator phone skin
The setting is at 'HKEY_LOCAL_MACHINE\Security\Phone\Skin'
The 'Enabled' DWORD value can be set to '1' to show the operator skin or '0' to show the default skin
Click to expand...
Click to collapse
Thanks for the reply, I am not sure if this was the one I tried before from one of the threads. How about you? Have you tried this registry tweak?

I did it by not installing any of the extended rom except operator settings, and the bluetooth patch.
my device boots up with 31mb of RAM available if all start ups and today screens are disabled.
I dont know how to do it otherwise.
I believe the hack mentioned above or similar on how to do it is posted on WIKI.

What has all this chit chat have to do with RINGER DELAY?
cktlcmd said:
simon_darley said:
1. use the original phone, not the bloated one with video messaging (not as pretty, but saves 3.5mb on load up)
Click to expand...
Click to collapse
"How did you get the original phone?
I tried the suggestions on the other thread where you need to change something in the registry, but that just disables the video messaging leaving a blank part on the screen. I want what you have, the original phone skin when I first turned my Universal ON after a hard reset. This original phone skin disappeared after I performed a soft reset.
Click to expand...
Click to collapse
"
He guys this is not helping us a bit out of the problem. This has nothing to do with the problem some of us are facing regarding the ringer going off after a 2 to 3 sec delay, making you loose precious seconds to answer the phone before the call gets routed to your operator voice mail system.
And the suggestion that you have to alter the settings regarding the handover time for an unanswered call or the other advising to just cancel the handocer to voice mail is also not helping us.
Brgds, Adhoc.
Please focus on that one !!

Hi,
AutoDPD is Auto Deep Power Down for DOC. I think it takes longer to wake it up from this state and thus it takes longer to ring.
buzz

Radio Rom 1.08 Rings Quickly - but the person on the oher end can't hear you immediately
Rom 1.06 takes a bit longer berfore it rings but you can talk straigt away
The best enhancement if you are not going to use video or 3G speeds is to set you Band to GSM or WCDMA and NOT AUTO, in Phone Settings
Obvioulsy if you have it on WCDMA and there is no 3G coverage you wont get signal
Skillie

buzz_lightyear said:
Hi,
AutoDPD is Auto Deep Power Down for DOC. I think it takes longer to wake it up from this state and thus it takes longer to ring.
buzz
Click to expand...
Click to collapse
Thanks Buzz,
So, should I disable both registry for the two storage???
And why it is orginally "1" in the default setting??? What is it actually for?
Cheers,

video call function no where to be seen on my TP2

Hi,
Does anyone have the same problem as I do where it is not possible to do video calls? The option (as stated in the manual) can not be seen anywhere on my phone. Just wondering if it is something that is disabled in the ROM, and how to fix this issue?
ROM Version - 1.12.531.2 (49169) WWE
Radio - 3.44.25.17
Protocal Version - 61.24t.25.17U

Have you checked the toggle located at the bottom left of the dialer when you open the phone app?

When I press the button you mentioned, it would bring up call history page rather than toggle into video call mode. Forgot to mention though, my TP2 has T-Mobile logo all over it so it may not be generic?
Thanks for the reply!

dwbchen said:
When I press the button you mentioned, it would bring up call history page rather than toggle into video call mode. Forgot to mention though, my TP2 has T-Mobile logo all over it so it may not be generic?
Thanks for the reply!
Click to expand...
Click to collapse
I believe u don't have the front facing camera? If that's the case, then u won't have that function (cuz most of the companies remove the second camera and I don't remember whether T-mobile is one of them or not)

dwbchen said:
When I press the button you mentioned, it would bring up call history page rather than toggle into video call mode. Forgot to mention though, my TP2 has T-Mobile logo all over it so it may not be generic?
Thanks for the reply!
Click to expand...
Click to collapse
are you located in the United states or in europe?

Thanks for all your replies. I was deeply worried at first fearing that I may not have the second camera. It was a big relief to have finally found the second camera alive and working, which is making me thinking the ROM had the video call function disabled. Does any one know if T-Mobile in the US supports video call?
For all who are interested, I got mine from Asia and had asked for a English version rather than a Chinese version. What I got was a non-branded TP2 with what appeared to be a fully customised T-Mobile USA ROM. (Perhaps confirming that it will be available in the US?) The ROM version appeared to be quite old compared to others that are out there though.
I can not wait for the Hard SPL to flash mine to see if I can get the video call going, and perhaps getting rid of all the T-Mobile settings on the phone as I am in Australia.

Crikey so you're in Australia with an Asian TP2 running an American ROM?
Sounds like a recipe for disaster! Looks like your stuck til someone breaks the HSPL barrier.

same here
I got my TP2 in Taiwan (as I live in Taipei ) and they put the english Tmobile ROM in. Phone has both cameras (front/rear) but no option so I'm looking as well how to get it working.
I also got a problem with MMS (did all the phone company Chunghwa settings) but I can only receive MMS and I cannot send (it tries but stays in outbox).
Trying to figure out if there's a registry to fix these things.

Handsfree Dialing while phone locked

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.

Call answer delay?

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

Stop the Sprint programming tool?

So this is an odd question, but I have the first Samsung Epic working just fine. I dial *228 on that phone and no problem, programs just fine after I dial "1". Whenever I dial *228 on the Epic 4g Touch it goes through Sprint's "programming" screen and won't let me bring up the keyboard so I can "press 1". Is there some way to stop this from auto-poopping up and just have the normal dialer STAY on the screen (like the samsung epic)? Deleted SprintAndroidExtension.apk already, which is what I usually have to do on my first Epic.
Protip: I'm not programming the phone on Sprint's network.

Just tried it on my phone to confirm your symptoms. It seems that you're stuck going the ##MSL# and Service Programming in QPST route. If the phone is activated and Profile 0 properly configured, maybe you can use Update Profile and Update PRL in the settings?

I have an idea. If you really need to press certain buttons to navigate the menu this should work. Get another phone and set it to speaker or hold it up to the mic and press the numbers you need. You might be able to find a program online to do it also. Every number is just playing a certain frequency note. I use to record the number I was dialing with a tape recorder when I was a kid. I would then just play it again to call the number.
On my Epic mobile phone.

kc_exactly said:
I have an idea. If you really need to press certain buttons to navigate the menu this should work. Get another phone and set it to speaker or hold it up to the mic and press the numbers you need. You might be able to find a program online to do it also. Every number is just playing a certain frequency note. I use to record the number I was dialing with a tape recorder when I was a kid. I would then just play it again to call the number.
On my Epic mobile phone.
Click to expand...
Click to collapse
Heh, I tried this but it didn't work. Was a cool idea though. Looks like I'll have to do service programming, which I absolutely do not want to do for a simple VZW programming (since it works on EVERY other phone), but I guess I'll have to. SO stupid I have to go through this trouble just because I can't press "1".

You can program Tasker to send key presses on a delay...

I ended up just grabbing settings in QPST which I thought would never work...but worked just fine. Was weird. Back in the HTC Touch Pro days we were told to always do Verizon Programming.
Well, thanks guys!