Develop Bugs

Question: WM6 have issue dialing long numbers?

I don't know if this is a known problem, but I'll post it for everyone.
With T-Mobile UK, their voicemail number (when you press "1") consist of 15 digits, with the last 10 digit being your mobile number.
For example:
- Your number is 079 0123 4567
- T-Mobile UK VM: +44 012 79 0123 4567
So when you press "1", the device will show that it's dialing +440127901234567.
Now note the "0" above, in red font. I have 2 8525, one running WM5 and the other WM6. When I dial the VM, this is what happened:
- WM5: +440127901234567
- WM6: +44127901234567
For some reason, WM6 ALWAYS dropped the number 0 between +44 and 12, even if I dial the number above one by one using the keypad (not pressing and holding keypad "1" for VM). This cause the connection to the VM system to fail, because T-Mobile doesn't recognise the number since it is now only 14 digits instead of 15 digits.
I tried the following:
- Swapped SIM card
- Changed "Area Code" under "Contacts" (put blank, put city code, etc.)
- Checked if any PIM application (Pocket Informant) is forcing some sort area code setting
But nothing worked. ONLY with WM6 that the number "0" from the above is dropped, no matter what I do.
If you with T-Mobile UK or have to dial 15 digits number with your provider for VM or even making other calls, please let me know if you have similar issue.
The problem I am having now is making my phone useless because I cannot check my voicemail at all.

Anyone with T-Mobile UK using WM6?

I'm using WM6 with T-Mobile UK. The voicemail number I'm using is +447987627762. Which has nothing with my mobile number. Try that...

the_invisigoth said:
I'm using WM6 with T-Mobile UK. The voicemail number I'm using is +447987627762. Which has nothing with my mobile number. Try that...
Click to expand...
Click to collapse
I have 3 SIM cards:
2 - PAYG (both on the TyTn)
1 - Pay Monthly (on the MDA Compact III)
If I use the number you gave, the error message ("The number to this call has been barred") also applies to ALL SIM card.
If I use the one that came from the SIM card, the error ONLY appear in the device that have WM6. I tried all SIM card on the WM6 device and the same error message appear, but not on the WM5 devices.

I have installed different kinds of WM6 ROMS (LSWV, Black, XDA) and tried this with 3 different TyTn and 3 different SIM card. Same problem.
I think I can safely say that if you use T-Mobile UK, do not upgrade to WM6 otherwise you can NOT check your voicemail.

Look at my post below. Previous idea not worth trying.

I have another idea! Try this
+4400127901234567 ADD an extra 0. I tried calling this number +440127901234567 and my phone would show +44127901234567 but when I put an extra 0 my phone showed this +440127901234567 and that is the number you want. Hope this solves it??

ANY LUCK with adding a extra ZERO to your VM number?

Yes, this works
Just add the extra zero to the number (after the +44) and it works a treat!
Cheers!
Smiffy.

Dude... you ROCK! It works!!

lanwarrior said:
Dude... you ROCK! It works!!
Click to expand...
Click to collapse
Glad I could help.

number format

another little annoyance.
sorry about all these but I think I've finally got everything installed the way I like it and now trying to iron out a few niggles.
is there any way to change the format of a phone number shown when I get called.
it always seems to be in the US format of xxx-xxxx-xxx-xx or something like that.
I always remember numbers as dialling code then number as in xxxxx-xxxxxx (UK format) 5 digits in the prefix and 6 in the number
which works for mobiles 07xxx-xxxxxx or (most) landlines 01xxx-xxxxxx
is this a change in the registry perhaps??

ID dealear doesn't appear

When I receive calls the dealer name doesn't appear, just the telephone number.
I am absolute sure that I don't have the same number with two different names in my list of contacts.
How can I solve this problem?

Is there Maybe a Country ID at the front of the submitted phone number which you don't have in your Contactlist, or maybe the other way round?

Hi
Are you using a customised ROM. If so you can try changing the amount of digits that the caller ID recognises in the Advanced settings.
Depending on what ROM you are using this can be in different places. But of the ones i have used it will be in either Start>Settings>System, or Start>Programs>PDA Settings
Cheers Dave

Caller ID Format Problems

Hello everyone, I installed RUU_Excalibur_WM61_Kavana_080408_WWE on my phone and it is workig great. The problem I am having is that in my country phone numbers consist of only 8 digits fotmated XXXXXXXX or XXXX-XXXX y my contacts list BUT when someone calls me his/her name does not come up, instead I get for example: (XXX)XXX-XX because the caller ID format seems to be (XXX)XXX-XXXX (expecting an area code) So I never get to se de name of the caller, instead I get a poorly readable number. How can I fix this?
TIA!

LOL, Try Moving to America, where we use these style phone numbers!
TheMasta said:
Hello everyone, I installed RUU_Excalibur_WM61_Kavana_080408_WWE on my phone and it is workig great. The problem I am having is that in my country phone numbers consist of only 8 digits fotmated XXXXXXXX or XXXX-XXXX y my contacts list BUT when someone calls me his/her name does not come up, instead I get for example: (XXX)XXX-XX because the caller ID format seems to be (XXX)XXX-XXXX (expecting an area code) So I never get to se de name of the caller, instead I get a poorly readable number. How can I fix this?
TIA!
Click to expand...
Click to collapse

TheMasta said:
Hello everyone, I installed RUU_Excalibur_WM61_Kavana_080408_WWE on my phone and it is workig great. The problem I am having is that in my country phone numbers consist of only 8 digits fotmated XXXXXXXX or XXXX-XXXX y my contacts list BUT when someone calls me his/her name does not come up, instead I get for example: (XXX)XXX-XX because the caller ID format seems to be (XXX)XXX-XXXX (expecting an area code) So I never get to se de name of the caller, instead I get a poorly readable number. How can I fix this?
TIA!
Click to expand...
Click to collapse
Did you try changing your Regional Settings to match the country you're in ?

Store all phone numbers in international "+" format
The key is to store all your numbers in full international format.
+CCCAANNNNNNNNNN
where CCC is the country code, AA is the area code (omiting any leading zeros in most countries) and NNNNNNNNNN is the local phone number.
For ease of use in your address book, you can space the digits out, or add parentheses or dashes, as these are ignored at dialing/matching time. It makes the numbers easier to read.
Eg. +CCC-AA-NNNNN-NNNNN, +CCC (AA) NNNNN-NNNNN would be treated the same.
All GSM phones receive the complete international designation phone numbers on incoming calls - so it will match on the full number always.
Based on your SIM, and your country's dialing rules built into the SIM, it will also match on numbers that have no country code, but have a complete local area code (including leading zero if appropriate) and complete number. This is to allow it to match on non mobile phone originated calls. I believe it will assume your local country code based on your SIM, and apply the appropriate zero stripping rules to the received caller ID to create a fully qualified international number to match on.
This also takes all the guess work out of making calls should you ever roam into another country. For example, if you live in the USA and store a number for Ireland as 01135312345678 - this will work from the USA. But, if you travel to Ireland, where the international access code is not 011 - but rather 00 - that number will fail. Storing the numbers with the "+" prefix instead of the local international access prefix allows the SIM card to do the work. The SIM card registers on the roaming provider's nerwork, and "asks" that network how to dial a "+".
Finally, the presentation of the number on screen is just a factor of the application that is displaying it. If you use the international format for your numbers, they will successfully match, and will display the number in the format in which you have stored them in your address book. If they don't match, they will display using the default number interpreting logic of whatever ROM you have loaded. For most of us here, that would be the Brighpoint USA ROM or the T-Mobile ROM - both of which try to format numbers as USA style AAA-XXX-NNNN
Hope this helps

Thank you, I entered +COUNTRY_CODE in the phone settings call options and it is working now.
Thanks a lot!!

TheMasta said:
Thank you, I entered +COUNTRY_CODE in the phone settings call options and it is working now.
Thanks a lot!!
Click to expand...
Click to collapse
How to go the phone settings call option

Solved.

phone number matching bug?

Hi all,
I posted somethinig similar to this a while ago. I am using my Diamond to call VoIP numbers, i.e. call a landline then wait for a few seconds and enter the destination number followed by hash #. The landline number is the same for all destinations and only the second part differs, which is the destination number. The numbers look like:
0123456789, 00447890123456#
Now, if I store two or more such contacts in the address book, e.g.
Bar: 0123456789, 00441234567890#
Foo: 0123456789, 00447890123456#
Joe: 0123456789, 00445678901234#
the, regardless which one I call, say Foo, in the call log it will always list "Bar" as having been called. The same happens if I replace the comma with a "p". The number however is stored correctly, i.e. if I redial it, it will call the number for Foo which is what was dialed in the first place.
It appears as being a bug in WM6.1. I haven't tried WM6.5 (anyone?).
How in the world can I fix this?
Cheers for any help

foo? bar? linux-user? i google your text for translaiting but nothing understanding.
do you mean that the order is not correct?
(if you can give an example with more friendly-understanding/windows-user than you can get earlier response from other forum-users.)
hope, you not so much angry

okokur said:
(if you can give an example with more friendly-understanding/windows-user than you can get earlier response from other forum-users.)
Click to expand...
Click to collapse
I understood perfectly. Perhaps it is a english as a second language barrier. I will try to restate the issue. (I wish I knew the answer.)
When you have a extra long number stored to a contact (as you might when you dial a AT&T toll free number with some pauses, then a passcode, then a number.) And you have more than one contact stored with this long number... they all have the same first 10 or so numbers. So regardless of which one was called last, when you look up the call history log, it displays the first one.
It would appear the call history only looks at the first 10 or so digits to find a match.

misfitflt said:
I understood perfectly. Perhaps it is a english as a second language barrier. I will try to restate the issue. (I wish I knew the answer.)
When you have a extra long number stored to a contact (as you might when you dial a AT&T toll free number with some pauses, then a passcode, then a number.) And you have more than one contact stored with this long number... they all have the same first 10 or so numbers. So regardless of which one was called last, when you look up the call history log, it displays the first one.
It would appear the call history only looks at the first 10 or so digits to find a match.
Click to expand...
Click to collapse
if this is the case, you can use advanced config or diamond tweak (forgot which one had the option) and from there you can set how many numbers it should check

@misfitflt: Thanks for rephrasing the problem .. I was just about to post. Cheers!
Prewien said:
if this is the case, you can use advanced config or diamond tweak (forgot which one had the option) and from there you can set how many numbers it should check
Click to expand...
Click to collapse
I forgot to mention I already played with the number of trailing digits in AdvConfig (that's what apparently the option is called) ... I tried values from the default 6 to 20 and nothing changed. The buggy behaviour persists.
I recently tried a new dialer with address book application that replaces the TF3D dialer; it is called Inesoft Phone v4.5 (it's actually pretty cool). This one does differentiate between numbers with pauses or commas correctly!
I'll try switching off the dialer completely and use the built-in WM6.1 dialer to see if that works fine. If so then the bug is in TouchFlo (?).
Anyone knows of other good dialer software that I could try?
Cheers,
p.s. I'm surprised this hasn't surfaced until now though ... anyone out there with the same issue? Or maybe I need to give the thread a more appropriate title.

i have the same issue but learnt to live with it as i didnt want to shift to another dialer.
tried playing with the number in adv config but of no avail
lemme know if you find anything