Related
After I upgraded my ROM to DCD's latest, whenever I try dialing from contacts or speed dial, I get this error message:
"Press END key to stop intercept tone" and it never dials.
Anyone got any ideas?
which carrier?
never seen or heard of that, did you install the right rom for your carrier?
The carrier is Verizon and I chose Verizon from the kitchen when I created the ROM. I have made ROM's before on my 6700.
if I dial the number manually, it works fine. It's only when I dial from contacts or speed dial.
Strange.
Confirmed
I'm running the NexVision Hybrid ROM (based on DCD's ROM) on my XV6800, and I can reproduce this issue at will. I've narrowed it down (at least in my case) to the international dialing prefix being used. That is, if a contact's number is stored as (e.g.) "+1 212 555 1212", the dialer chokes on the "+1" - I hear a short beep, and then (usually) see the "Press END key to stop intercept tone" message.
If I edit the contact's phone number to remove the "+1" (or just the "+", leaving the 1), it dials just fine. Basically, it seems to always come down to the "+"...
The problem (for me, at least), is that I have a "+" prefix for most of my (many) contacts. Plus, most of the numbers in my employer's Company Directory (which I can search and dial from my device) have this prefix. I've had a few people ask me what the "+" prefix is all about, thinking the mistake is on my side for using some alien format for the country code prefix. Just to head that off, I'll point out that this format comes from the ITU-T Recommendation E.123, "Notation for national and international telephone numbers, e-mail addresses and Web addresses". So there. Plus, it's worked on every other phone I've ever used, including this one - at least I did, until I upgraded the ROM. ]
BetaMan, does this apply to your case at all? Either way, does anyone have any suggestions?
Thanks,
-roach
I find since the 2.1 update (Rogers/x10a) a lot of my SMS are not going through. I keep getting the "message not sent" notification. (THIS IS NOT THE SAME AS 160+ CHARACTERS PROBLEM)
Am I the only one with this problem since the update? If so, hopefully I can get a new phone from Rogers
Have tried the *#*#4636#*#* and looked at the SMSC. Is always blank. Even when SMS is working.
Help?
EDIT: The problem here is Task Killers (ATK, for me). If Auto Kill is set to Aggressive it interfere's with sending SMS. If set to Safe there is no problem whatsoever.
i have the same problem
my rogers canada x10a also has a tiny bit of trouble sending sms messages after the update. i was considering reflashing because of it. i have found that every time i try to send a message that it has to split in to more than one message it fails.
hope this might aid in diagnosis with someone that knows more about this issue.
i haven't tried to play with it enough to recreate the problem consistently but if their standard character cap is different that could cause problems i suppose.
Edit:
i just attempted to recreate my problem for sake of being constructive.
for curiosity sake i went into the 4636 menu first. i should have done this after.
my smsc was also blank so i hit refresh and the field populated with: "+17057969300",145
that doesnt make a lot of sense to me looking like a phone number with too many digits. i dont know what the 145 was about either
i then went on to send a text message to myself starting with 140 chars then 144, 145, 146, 150, 160, and 180
it did warn me after 150 that i was sending 2 sms messages but they all worked
results: inconclusive
gooph said:
my rogers canada x10a also has a tiny bit of trouble sending sms messages after the update. i was considering reflashing because of it. i have found that every time i try to send a message that it has to split in to more than one message it fails.
hope this might aid in diagnosis with someone that knows more about this issue.
i haven't tried to play with it enough to recreate the problem consistently but if their standard character cap is different that could cause problems i suppose.
Edit:
i just attempted to recreate my problem for sake of being constructive.
for curiosity sake i went into the 4636 menu first. i should have done this after.
my smsc was also blank so i hit refresh and the field populated with: "+17057969300",145
that doesnt make a lot of sense to me looking like a phone number with too many digits. i dont know what the 145 was about either
i then went on to send a text message to myself starting with 140 chars then 144, 145, 146, 150, 160, and 180
it did warn me after 150 that i was sending 2 sms messages but they all worked
results: inconclusive
Click to expand...
Click to collapse
Your problem could be because you're with a different carrier. Bell? I know bell has capped at 150 characters I believe. Also, if you are on a different carrier I'm assuming the SMSC are different.
However, I am able to send SMS over 160 characters. Never had a problem with that. It's more of an annoyance. 1/15-20 of my messages doesn't go through. It's just bloody annoying.
paulsandhu said:
Your problem could be because you're with a different carrier. Bell? I know bell has capped at 150 characters I believe. Also, if you are on a different carrier I'm assuming the SMSC are different.
However, I am able to send SMS over 160 characters. Never had a problem with that. It's more of an annoyance. 1/15-20 of my messages doesn't go through. It's just bloody annoying.
Click to expand...
Click to collapse
I have to apologize. i just haven't changed that in my account here yet. i just switched from bell to rogers.
also:
all the random test messages i sent to myself before i posted that worked but i still am having problems sending 2+ sms messages to other people consistently.
I think this issue is related to Rogers' crappy network. Everyone I know on Rogers right now (in London Ont at least) is experiencing the same problem regardless of the device they're using. Damn you ROBBERS!!
I'm having this problem since I updated to 2.1, I can't send more than 160 characters in SMS. If it's more than 160 it fails to send it. Is there any solution to this? TIA
gooph said:
i just attempted to recreate my problem for sake of being constructive.
for curiosity sake i went into the 4636 menu first. i should have done this after.
my smsc was also blank so i hit refresh and the field populated with: "+17057969300",145
that doesnt make a lot of sense to me looking like a phone number with too many digits. i dont know what the 145 was about either
i then went on to send a text message to myself starting with 140 chars then 144, 145, 146, 150, 160, and 180
it did warn me after 150 that i was sending 2 sms messages but they all worked
results: inconclusive
Click to expand...
Click to collapse
THANX I have had problems with sending large (above 160) sms's, after update to 2.1, but then i saw this, and gave it a try, and it worked, so for all others, try the 4636 menu, and hit refresh, helped for me
But But ..........after reboot the same problem again...........grrrr, then what to do!!!???
I know all providers have **** networks but I don't think that this is the problem. Since 1.6 I've NEVER experienced this issue with SMS. But dropped calls and **** reception? Yes.
I don't know if this is a firmware issue or not. Im thinking it is.
This is happening to many people in the UK too since the 2.1 update. So it's certainly not exclusive to your operator but something cocked up in the update.
I even had this problem on 1.6, it happens mainly between me and my girlfriend. Its a nightmare. Sometimes all is ok and others just won't send and sometimes it sends when it says can not send so god knows!!
Sent from my X10i using XDA App
**** sony ericsson .. and rogers
Hi all. I live in Denmark and have the same problem. I amusing CHOMPsms an belived that it was the app that was The problem but i dont think anymore. I can't enter that menu 4636. Help!
Regards Allan
Sent from my X10i using XDA App
I too had this problem on O2 Ireland after the 2.1 Android update.
Simple answer to the problem is that the update screws up one or two lines in the APN on the phone. All you should need to do to sort this out is find out your carriers APN settings and manually input them. As soon as I did this all worked beautifully.
Settings > Wireless & Networks > Mobile Networks > Access Point Names > "Carrier Name" (Internet)
Change this and in theory you should be working again.
DBSS said:
I too had this problem on O2 Ireland after the 2.1 Android update.
Simple answer to the problem is that the update screws up one or two lines in the APN on the phone. All you should need to do to sort this out is find out your carriers APN settings and manually input them. As soon as I did this all worked beautifully.
Settings > Wireless & Networks > Mobile Networks > Access Point Names > "Carrier Name" (Internet)
Change this and in theory you should be working again.
Click to expand...
Click to collapse
But doesn't this only affect the internet usage on the phone? I don't believe this is the same as the SMSC.
On another note, I happened to remove HTC Keyboard from my device as I thought this might be affecting the performance some how. And I don't know if it is a coincidence but my problem is gone.
Also, I noticed with the HTC Keyboard sometimes when I would send a message, the actual message would still be written on the "type message here" field.
2 birds, one stone ???
paulsandhu said:
But doesn't this only affect the internet usage on the phone? I don't believe this is the same as the SMSC.
On another note, I happened to remove HTC Keyboard from my device as I thought this might be affecting the performance some how. And I don't know if it is a coincidence but my problem is gone.
Also, I noticed with the HTC Keyboard sometimes when I would send a message, the actual message would still be written on the "type message here" field.
2 birds, one stone ???
Click to expand...
Click to collapse
If you delete the 145 in smsc and the , you Can send 2 messages but not 3 in one continous SMS. Do not go back when you have done it go directly to the homescreen. By the way I'm also from Denmark... Fu.... S/E
lucifax said:
If you delete the 145 in smsc and the , you Can send 2 messages but not 3 in one continous SMS. Do not go back when you have done it go directly to the homescreen. By the way I'm also from Denmark... Fu.... S/E
Click to expand...
Click to collapse
Hi
My problem was not sending SMS over 160 characters... It was sending them period. I would constantly get "Message not sent" notifications.
I realized the problem. It's not HTC Keyboard, but Advanced Task Killer. I had the setting for Auto Kill frequency set to aggressive. This somehow interfered with sending SMS for my phone. I set it to Safe and it is fine. But if I switch back to Aggressive there is problems.
Hi Everyone,
Quite a number of people, especially in Europe are experiencing caller id issues on the HTC Mozart, and some other HTC devices with WP7 (I can only be sure of the Mozart though). The issue is decsribed by many people here:
answers.microsoft.com/en-us/winphone/forum/wp7-wppeople/htc-trophy-caller-id-problem/90c3b4d2-b558-4e6e-aa91-2530285f302f
Basically, I have my Mozart getting the contacts from my Exchange mailbox via sychronisation. All the contacts are stored with the international prefix (+356 for Malta, +44 for UK etc. etc.) to have everything working while local or roaming. Everything works ok except caller ID. SMS are recognised with no exception while calls are not recognised, at least not all of them.
Depending on which provider the caller is, numbers sometimes come in with the international prefix and sometimes they are not (depending on the local provider the caller is subscribed to). Basically the Mozart does not recognise the caller ID if it does not find an EXACT match in the address book. Eg. If the call comes in with +356 123456 the caller is recognised, if the call comes in with 123456, it is not. SMS is not affected by this issue. All SMS are recognised as they all come in with the prefix.
And there is no workaround as if I remove the prefix from my contacts, the SMS will start not to be recognised.
In brief, the Mozart does not strip the international prefix or have some condition to recognise the number if it is not a perfect match (including the prefix). I did not see any mention on this in these forums, but have seen it elsewhere, and for sure it is a problem which affects some Mozart owners depending on their provider.
Have contacted HTC and and after some useless replies, I received silence.
After debranding my T-mobile Mozart, and running the RUU_Mozart_HTC_Europe_1.30.401.01_5.54.09.21_22.33 b.50, the problem remained exactly the same as before.
The same SIM card in my Mozart works ok on a Galaxy S of a friend or an old Nokia feature phone, so the issue is specific to the Mozart.
Can anyone provide any insight? Is anyone experiencing the same problem?
Thanks,
Stefan
Exactly the same here, I also debranded the same way and the problem remains the same.
I saw in some other forum that there should be a way to change a parameter in the registry to limit the lookup to the last 8 digits, which would fix it for me. Is there a way to do this on a Mozart?
quax 0815
I used hack from this thread http://forum.xda-developers.com/showthread.php?t=907971
look for -Caller ID issue fix in the first post.
I had the problem of having to save both numbers with and without the country code. (Country code for SMS, and no country code for calls).
Works like a charm My country code has three digits. If it doesent work try tweaking the number in registry hack.
the ultimate resolution
1- go to the following address to download registry editor:
touchxperience
.com
/en/applications/viewcategory/3.html
choose the file: Registry Editor Version:0.9 by checking the box next to it then click on download.
2-copy the downloaded file to your phone (probably to the storage card) and then install it.
3-go to applications and open the new application: Registry Editor.
4-go to the following:
HKEY_CURRENT_USER
then
ControlPanel
then
Phone
then
CallIDMatch
then choose the type to be " dword " and change the value to " 7 "
5- finally soft reset you phone or turn it off then on and BANG!
enjoy
How do you copy the downloaded file to the WP7 device?
Hello,
Just got my HTC Ultimate (Brazil's for Titan) and I'm experiencing some problems while dialing and returning calls...
For the details below I'll use a number (9999-8888) from Brazil (country code 55), with 31 as area code.
I store my numbers in international format (+55 31 9999-8888, for the number above) and Vivo (my mobile carrier) sends incoming calls identified as 03199998888 (same number).
I can't call none of them, as I need to dial (according to Brazil's standards) a number in the following format:
0 15 31 9999-8888
The leading ZERO identifies a long distance call, the following "15" tells them to use a especific long distance provider, 31 is the area code and the rest is the number.
In android I've used several apps to do this "translation" in real time, while calling, like "Operadora DDD", "Profiler" or Right Number...
Is there anything like this in Windows Phone 7?
I've checked the "International calling assist" thing too...
I believe it's good to match incoming calls with different number patterns from my contacts.
In fact, no matter where it's on or off, my phone matches 03199998888 for "+55 31 9999-8888", so I believe it would deal with more strange patterns...
While receive a call and match a contact is OK, calling is still a challenge...
Anyone with tips?
Hi, rgmarques. I'm from Brazil too. I have the same problem. Send email to [email protected].
Thanks
Antonio Marques
Hi guys, i'm a former owned of a HD7 and now I own a Ultimate too.
All my contacts use the pattern: +5511XXXXXXXX, for São Paulo as an example. All working now.
The fallowing patterns also works: 011XXXXXXXX, 0YY11XXXXXXXXX
As an example, if you use a TIM SIM, the match option when someone calls you will not work, at least never worked on any imported device I own previously. This is because when your recieve a local call, TIM does no put the DDD before the number! This is done nice by Vivo.
Please, don't keep information on your email, share it with forum. Since the Titan is a brand new device here in Brazil, more people will come to find solutions for their problems.
[]'s
Cris
---------- Post added at 09:50 PM ---------- Previous post was at 09:30 PM ----------
Try this: Go to Settings and then choose SIM application.
Click on "show application", click on "Facilidades" and then "Vivo DDD". Activate it.
Give feedback please.
[]'s
Cris
Well, seems like my SIM card doesn't have a "facilidades" option...
Here in minas Gerais, we've moved from Telemig Celular to Vivo 1,5 years ago and some stuff hasn't changed completely yet... SIM apps seems to be the case...
I've seen different behaviors in incoming calls matching on my Motorola Milestone,depending on the ROM I used. Never tried different carriers, as it was never an option. But I believe they might send different numbers as originator of the call, resulting in different results.
But my problem relates to originating a call...
Vivo won't let me call +5511XXXXYYYY... I need to call 01511XXXXYYYY...
Well, while no alternative solutions come up, I've changed my contact numbers to match our (Brazilian) pattern... Regular expressions made this reasonable while nothing else shows up... If anyone needs any specific help with the process, just let me know...
I'll keep looking and will report here if i find anything useful...
Thanks.
rgmarques said:
Well, seems like my SIM card doesn't have a "facilidades" option...
Here in minas Gerais, we've moved from Telemig Celular to Vivo 1,5 years ago and some stuff hasn't changed completely yet... SIM apps seems to be the case...
I've seen different behaviors in incoming calls matching on my Motorola Milestone,depending on the ROM I used. Never tried different carriers, as it was never an option. But I believe they might send different numbers as originator of the call, resulting in different results.
Well, while no alternative solutions come up, I've changed my contact numbers to match our (Brazilian) pattern... Regular expressions made this reasonable while nothing else shows up... If anyone needs any specific help with the process, just let me know...
I'll keep looking and will report here if i find anything useful...
Thanks.
Click to expand...
Click to collapse
Call VIVO and ask them to enable this for you. Or, if your have an old Nokia, try you SIM on it and see if the option appears there for you.
But can be different SIMs for each State.
When you DIAL without the DDD Operator, nor the AREA, does it completes the call? If not, this is the problem and this service from VIVO will 'add' the DDD Operator when you do a long distance call.
[]'s
Pimentel
Hi Cris,
I have a Titan with Tim, and I save the contacts with 04121XXXX-XXXX, so when I receive a call from my contacts I don't see the contact's photo or name, only the tel number XXXX-XXXX without area code. But when I save the number like XXXX-XXXX without area code and Tim code, the photo appears on screen.
I had a Htc Diamond with Tim and photos appears well.
Antonio
cpimentel said:
Call VIVO and ask them to enable this for you. Or, if your have an old Nokia, try you SIM on it and see if the option appears there for you.
But can be different SIMs for each State.
When you DIAL without the DDD Operator, nor the AREA, does it completes the call? If not, this is the problem and this service from VIVO will 'add' the DDD Operator when you do a long distance call.
[]'s
Pimentel
Click to expand...
Click to collapse
Well,
I used to save my contacts in the international format, +55 31 9999-8888.
With that, I'll need a transformation instead of a simple addition of the carrier code...
If I call 03199998888, the call completes when it's a local one. If it's a true long distance call, it will fail, requiring me to explicitly inform the carrier code.
Well, I will try to check if Vivo has any hint for me.
I'll call them tomorrow.
Thanks again.
Hello,
I hope anyone could help me, since I am beginner when it comes to Atrix and Andoid, but let´s go:
I have bought a At&t Motorola Atrix 4G, Android 2.3.6, system version:4.5.141 mb860.att.en.us
Once I arrived to Brazil, inserted my SIMnseveral contacts, everything ok... but, when I receive a call, the calling number shows up on the display, but not the name of the inserted contact. So, it is showed the number, but not the name of the registered contact. The phone is not matching the calling number with my contacts.
I have already created a motoblur acount, restored the phone to factory settings a several times, but nothing seems to solve the problem.
Altough the phone is now in Brazil, its IMEI continues linked to At&t and my carrier says that this has nothing to do with this problem.
My carrier in Brazil is "Oi".
I hope someone could help me here.
Thanks in advance!
Have you tried saving the number as it appears on caller ID? I've had this happen with text messages and it's due to the way the carrier sends out the caller id; for example, instead of (123) 555-5555, the network pushes it out as +1235555555.
Caller ID is an carrier service and in this case is irrelevant. Your carrier is right in saying this has nothing to do with them. The phone shows up names associated with phone numbers based on your local phonebook only.
Your phone being "tied" to AT&T is irrelevant too, you're out of their reach now so they can't do anything even if they wanted to.
I should know, I'm happily using an AT&T device even though I'm halfway across the world.
What kind of format are you using for the phone numbers in your contacts? I'd recommend you use the standard international format, even if most of them are numbers local to your country. Standard international numbers are of format +<country code><area code><number>. So for my country it would be for example +3851xxxxxxx. So try changing some number in your contacts to that and then tell them to call you and see if it helps.
That's very strange, because I've used the At&T rom on my brazilian atriz without any issue whatsoever.
What could fix your issue is what our buddies said above: try setting the contacts with the International number format (+55 21 9999-9999). All of my contacts are like that on my phone and caller ID has worked fine across multiple ROMs.
vladeco said:
That's very strange, because I've used the At&T rom on my brazilian atriz without any issue whatsoever.
What could fix your issue is what our buddies said above: try setting the contacts with the International number format (+55 21 9999-9999). All of my contacts are like that on my phone and caller ID has worked fine across multiple ROMs.
Click to expand...
Click to collapse
Same thing, brazilian atrix, AT&T rom.
I keep all my contacts in the following format: '011 9999-9999' and it's worked with pretty much every ROM I've tried.
MaxK47 said:
Same thing, brazilian atrix, AT&T rom.
I keep all my contacts in the following format: '011 9999-9999' and it's worked with pretty much every ROM I've tried.
Click to expand...
Click to collapse
I used the followin formart: 021 xxx-xxx and worked. I was using "0xx21 xxx-xxxx" format and it was not working, despite my others "dumbphones".
thank you all"