Sorry if this is the wrong thread to raise this topic, but didnt know whr else I shud put this.
I bought a sprint motorola photon few days back and programmed it to my CDMA operator (Citycell - Bangladesh). Everything is working fine, got EVDO to work etc.
BUT whenever I receive an SMS from ANYONE or any number, the "0" in sender number is shown as character "D". FOR Example if i get an SMS from 01199800570, it will show I received SMS from D11998DD57D > it has nothing to do with that number being in phonebook or anything. any "0" in sender is shown as "D". as a result i cant even reply to these SMS,
FUNNY thing is, when i click on the sms to read it, the ORIGINAL number with "0"s (01199800570) is shown in the last line as [CB# 01199800570]
I have inspected the mmssms.db. I found 2 fields - ADDRESS (which contains all the phone numbers' 0 replaced by D] and CALLBACK_NUMBER [which contains the actual number]
Now I was wondering -
1. IF thr is anyway to fix it by tweaking system settings or something so that sender's number is received correctly [so that ADDRESS field would have correct numbers]
2. OR if it cant be fixed, if there is anyway to force the SMS app (Conversation.apk) to read Sender's address from CALLBACK_NUMBER field instead of ADDRESS field ...
3. OR ATLEAST can someone kind enuf to provide me with a script that would (when run) access the mmssms.db and change all the "D" in values of address column to "0" ?
This is NOT a photon 4g problem - but with most SPRINT cdma phones. The same thing happens with ANY sprint android - when programmed in different country, 0 is replaced with D in received SMS
THEN again, this is a problem in android version < ics. THE ICS phones that are programmed shows sender's number correctly
AGAIN, this is NOT a problem ONLY with my operator, I heard about similar problem in other countries too
Since ICS shows it fine, that means, thr are work arounds in gingerbread too. OR atleast if we can force the SMS apps to read sender's number from CALLBACK_NUMBER, problems are solved.
I know you guys are the best and if u look into it, it would only take a min of ur time to find a solution ... :angel:
anyone ?????
I have the same problem - using an XT800 with the chinese 2.2 rom
most of the time it works ok but it goes haywire on its own without any apparent reason! having a hard time figuring out the sender of each and every message that comes in, some help/ guidance would be very helpful
TIA
Related
hi people,
recently I ve figure it that when I send sms, the person which get my sms dont recieve my GSM phone number as a sender number, the SMS show my home number as an origin of the sms.
Also in phone settings on the top of the screen is that phone number, the number of my home and not gsm number as it should be...
Probably I ve set it somewhere and sometime and I cant recall any more, digged thru the wallaby but couldnot find it, as far as I remember long time ago somewhere I clicked that number and mark it as "my number" but cant recall anymore was that on some other phone which probably put that in SIM or that was on the wallaby somwhere...
Please help, how can I change that number, its quite stupid to have that number as a senders number when no one can reply to it coz I have no SMS on the home phone and beside that I dont live with my familiy any more...
Just tested the sim in the other phone... Looks like its in the wallaby somewhere, when I send sms from my ancient nokia 5110 everything is fine :S
In the owner data of the wallaby is phone number from the place where I work, I really dont know the origin of that old home number reported in sms messages :S
Thanks ppl and BR !
ok im having problems with typing nos. apparently this only recently happened aft i installed the hotfix for sms and the sd card compression thingy from htc.
basically whenever i typed numbers, there will be an automatic spacing before the number. this is a big problem for me cus when im browsing the net and i need to log in into certain accounts, it will require me to type numbers, and due to the 'spacings', the numbers cant be recognised. so i cant log in.
for e.g., this is how it will turn out:
"hi my name is brad, you can get me thru this email laleutys 9 0 8 3 2 @blalla.com"
im from singapore so my set is installed with 1.48rom when i bought. any idea if the hotfixes caused the problem or i have to change sum settings. and just fyi, before installing the hotfixes, i didnt encounter any sms stuck in outbox issue. somebody pls help me!
I have exactly the same problem. I have also found that when I manually type in phone numbers to send SMSs, they won't send because the dialler things the spaces are real. Also, recipients (when I dial using my phonebook) just see "squares" in the recieved messages when I send numbers.
Did you ever figure out how to fix it?
Thread moved to Q&A.
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.
I have searched for this and found the same question posted in a HD2 Android category, but there were no responses... so asking for myself in here.
I have all my phone numbers listed in my contacts with the preceeding area code, as I often travel outside of the local area and need those area codes included in my contacts numbers..... ie: all my phone numbers are 10 digits in length.
However, there doesn't seem to be a requirement for the area code to be sent, when a caller has Caller-ID enabled. In other words, I receive some calls from contacts in my phone, but if their phone doesn't include the area code in their Caller-ID, then my phone doesn't recognise or identify the number. Consequently, when hanging up from those calls, it constantly asks me if I want to save the number.
Note - it isn't a permanent thing. Many incoming calls DO identify correctly, as the area code has obviously been sent with C-ID.
Does anyone have a solution for this?
Obviously I COULD go thru every contact and manually add another non-area-coded phone number - perhaps under an obscure phonebook entry, like "pager"... but surely this is something that one would expect be handled automatically by the phone... not by duplicating entries as a work-around.
What would happen for business-people who travel internationally - most of their contacts would also include the "+61" (or whichever) country code also.....
Nobody ???
Bumping again ????
Anybody have any clues to this?
Did you try disabling the Area Code Prefix setting in Settings -> Call Settings ?
kawazaki said:
Did you try disabling the Area Code Prefix setting in Settings -> Call Settings ?
Click to expand...
Click to collapse
Thanx mate for your reply.
Sorry took so long.... my phone has been in for warranty repair (unrelated matter to this) for the last 7 weeks, so I haven't logged onto xda in that time !!!
No..... I haven't tried disabling the AC Prefix setting. I will have a look at that and see if it makes any difference.
One additional comment..... I am also having the REVERSE problem.... in that SOME people who ring me on their mobiles, the caller ID is also sending the +61 (Australia) country code in front of their mobile number too.... so again, my phone isn't recognising them as being the "same" number as what is stored in my phonebook ????
Will try the disable thing you mention and report if it works.
Sorry mate... cannot find the setting you mention.
Could you explain please exactly where it is ?
spinifex74 said:
Sorry mate... cannot find the setting you mention.
Could you explain please exactly where it is ?
Click to expand...
Click to collapse
Or you could turn off having the phone ask to to add the number to your contacts.
On the US T-Mobile phone it is:
Activate phone screen
Menu
Options
Menu
Network Selection
Advanced tab
Turn off the feature to "Add new phone number to People at end of call"
I'm using the NRG ROM.
Thanks stevedebi.
Sorry - I mite not have been properly clear.
The issue isn't being asked to save a new number.
The issue is.... the phone does not recognise a number - mobile or landline - if there is an area-code or country-code prefixed to the number (or vice versa) with the entry in the phone book.
Eg: ALL my contacts saved in my phone have their mobile numbers WITHOUT the +61 country code.... and ALL landline numbers are saved WITH area-codes.
Now - depending on my contact's phone operators, they sometimes send with, or without, those prefixes in their caller ID's.
Consequently - on those occasions.... my phone does not recognise incoming calls or messages as having come from my contacts, due to the extra numbers at the beginning.
Surely this is a software issue from HTC? I mean, surely the software should be able to query an incoming called ID (either with or without prefixed-codes) with a saved number in the contacts/phonebook (with or without prefixed-codes)... ???
Bumping again ?
Sorry to be repetitive.... still looking for an answer to this ???
Check you registry setting for "HKCU\Control Panel\Phone\CalIidMatch" value=?!?
try to reduce the number for "Value" by 1 and try.
This is for the number of digits your phone will check when comparing incoming numbers with stored names.
Thanx Omar,
Will try that. Question though.... does it check the phone number (by number of digits) in reverse order? ie: setting a particular number will have no effect, if it checks in normal forward order, as it's PREFIXES that are making things wrong.... so the phone needs to ONLY check the LAST 10 digits.... not the first 10. This will eliminate the issue with any country-code added to the front of a number... but will not help with a local area code, as these are dependent on the callers' carrier, if they send the area code in the CID or not
From my experience with my HTC phones, it checks the last digits.
I have number saved with the +974 international code (for Qatar), & when local call come in, they only show the local format (without +974) & the caller ID still recognises the names. Our local numbers are 8 digits, so I have the registry value set at 7 or 8 & it works fine.
I have a Samsung Galaxy S2 which i am having a really irritating SMs problem with.
My dad lives in Cyprus, when he sends me an SMS i can not reply, when i try it just says 'sending' then 'failed' . In order to get the text SMS to send to him i have to delete the message thread, then start a new message and it will send. Now if he then replies, i will need to delete the message thread again in order to be able to send him a new message.
I do not have this issue with any other contacts that i am aware. The only difference with my dad is that he lives abroad in Cyprus, and all my other contacts are here in the UK. Has anyone else had this issue? Know what causes it? I have deleted and recreated the contact but still the same.
Many thanks.
Do you have your dad's number stored in contacts with country code or not ? I was on the verge of smashing my phone when i was abroad, trying to call persons in my native country and i couldn't because i didn't have numbers stored with country code. Maybe that's your issue too
I think the problem is related to what SMS server your dad is using, I had same issue with my X-girls phone, no one could direct reply to SMS...
Hi, thanks for the replies.
Sp1tfire, i have changed the number configuration around several times, all with no success.
Fritz, this sounds plausible, however this would surely affect other phones replying? I don't have this issue when using my iphone 4 so it only happens from the Galaxy2 at the minute. I will try and use a colleagues Android phone to text him and test it.
Somehow you, or TSP (Telephone Service provider), have inserted a sms mail server address that is not valid.
here in my country, there has been scams, "cheaper SMS, enter this server setting" and stuff like that, so there is a setting on you phone that is wrong.
FRlTZ said:
Somehow you, or TSP (Telephone Service provider), have inserted a sms mail server address that is not valid.
here in my country, there has been scams, "cheaper SMS, enter this server setting" and stuff like that, so there is a setting on you phone that is wrong.
Click to expand...
Click to collapse
Can't be cause of settings, if he can actually send new sms to that number, but he can't reply from the received sms. His settings are correct as long as he can send sms. Must be something else. Are you using default sms app or a third party software ?
Sp1tfire said:
Can't be cause of settings, if he can actually send new sms to that number, but he can't reply from the received sms. His settings are correct as long as he can send sms. Must be something else. Are you using default sms app or a third party software ?
Click to expand...
Click to collapse
I am using the stock SMS app. I have just wiped the phone and installed the KF2 firmware. Going to see if that helps.
Sp1tfire, thats right, i can only reply to him when i delete the existing thread. I can however send new SMS to him no problem, so long as the thread is deleted before hand. Very frustrating as i lose the history every time.
Update, exactly the same on KF2 Firmware.
Ok, so i tried with a friends HTC desire and he has the same issue. also found my brother who has an iphone 3gs is unable to reply to my Dads number. So at least know its no longer just my phone and that it must be something the other end. Many thanks for the help.
Same problem here
When I reply to my girl it says: failed, when i delete the whole thread it goes.
It's only when I text her, all the other contact go fine
On my old sgs I had it to, but only on stock, when I was on CM7 it was OK.
Cant imagine that its something with the other phone i'm sending it to though
Sp1tfire said:
Can't be cause of settings, if he can actually send new sms to that number, but he can't reply from the received sms. His settings are correct as long as he can send sms. Must be something else. Are you using default sms app or a third party software ?
Click to expand...
Click to collapse
I remember in all the previous phones I've had, there's been a setting in the SMSC Settings allowing the user to specify whether or not to "Reply using the same SMSC" (or something along those lines).
If the option is ticked, the phone attempts to reply to the message through the SMSC that the text originally came from (rather than the one set in your handset).
The cause of the error may be because the SMSC overseas does not recognise your phone/SIM and therefore won't allow the replying message to go through.
And perhaps this may explain why deleting the whole thread and restarting a brand new message works - that is, the new message will go through the SMSC that is set in your phone for your own network.
Although, I've had a look through the settings in my SGS2 and can't seem to find that setting anywhere... (doesnt mean it's not there - it could just be that I don't know my phone well enough because I've only had it for a few days ).
I think your dad's SMS configuration settings is forcing you (or any other person he is sending an SMS to) to reply through his operators message centre
Ask him to check his sms settings and disable any such message centre settings from his side. This should solve the problem.
Sent from my GT-I9100 using XDA App