i realized yesterday that after upgrading to dcds latest rom and radio when i add a couple recipients to an sms the only person who gets it is the first one on the list. this worked properly with sprints original rom. anyone know whats causing this and how to fix it
It works well for me. I am on Verizon too.
What I did was to start a NEW Message and then go to menu and add your recipients one by one and you should be fine from here.
I tested this right now by sending a friend of mine a text ( she was the first recipient) and the second recipient was my cell # and it worked.
if i go through the menu tab it works but when i go straight through the to line it doesnt add the necessary colan for it to distinguish theres more than one receiver automatically like it used
excess4 said:
if i go through the menu tab it works but when i go straight through the to line it doesnt add the necessary colan for it to distinguish theres more than one receiver automatically like it used
Click to expand...
Click to collapse
Trippy, I have never tried that method because I feel that I would have to insert more characters rather then just selecting them and letting the SMS program do it for me.
update
i tried it using your method and it worked
i entered ##########;########## and it worked.
just insert the areacode along with the number and if you are using the keyboard go into the symbols menu and select the colan and with out any spaces add the second number starting with area code.
or you can use the on screen keyboard.
I noticed the no semicolon thing too. Any fix we can do to make it do it automatically like it was before?
Related
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.
Has anyone noticed that when you put a pound key (#, aka number symbol, octothorpe etc) in a contact's number, it doesn't work? I.e. the # dtmf tone is not sent when you call the number, while other tones are sent properly.
For example, I set my voicemail number to *86,,5555# (the 5555 part is just for illustration, and should be filled in with the voicemail pin)
Whenever my phone calls voicemail, it says "Sending Tones 5555" but it doesn't mention the #, and I can tell that the # tone is not sent, because the voicemail system waits a few seconds after the password is sent, which is exactly what it does when I dial it manually and neglect to press #. When I do press pound manually, the system continues immediately without a pause.
Has anyone else experienced this? Or has anyone else been able to sucessfully send the # key?
hi, i haven't had this happen personally, but would puting space between the password and the # give the sytem time to receive it.? don't know if it will but i never had this happen either.hope this helps. hp
I don't think you can add spaces, but I added a comma (which indicates a pause) after the pin. That didn't help. Thanks for the suggestion though.
##7764726(spc=000000) and *#*#4636#*#* are hidden menus so the # may be handled special.
I actually noticed this today when I was trying to get through a damn automated menu. It kept asking me to hit the # key after things but kept telling me "Invalid Entry". I literally used every other button, to include * during the call and everything else worked. This is no bueno!
What version of Android and what Rom(if any) are you running? I am on 2.3.4 w/Eclipse v1.1
Thanks, AtLemacks, It's nice to know someone else has experienced the same thing (misery loves company I guess).
I'm using the same android version and ROM that you are. But I'm pretty sure I had the problem even back when I was using using P3Droid's Rooted Gingerbread without any ROM. I don't remember if I tried it when I was on stock Froyo.
I didn't have this problem before, I call/go through that menu fairly often.
did anyone figure it out?
I am suffering the same problem. Did anyone ever figure out how to send pound sign #?
Try a alternate dialer like Dialer One or the like.
Edit try voicemail *86, the # key skips to the next msg on my Milestone x2 port.
Found a solution
Found a solution, not sure if everyone can use it. I am using Motorola Photon with Sprint. My solution is to create a contact like this for google voice dial out
15125553010,,2,3235551110,#,,,1234,0118521234567,#
and it works for me. I can now use a direct dial icon on my home screen to call. The trick is the first pound sign. It needs comma before the pound sign and the three comma behind it.
Anybody else find a work around?
I am glad to hear that I am not alone, but a little dismayed to not see any answers to my days of searching for a solution. Has anyone else come up with an alternative work around? The direct dial method above didn't work for me.
Using a Galaxy S i9000 rooted with paranoid android 2.52 (although I did have this same problem with other mods as well)
Thanks!
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
I posted this in the Hyperdrive thread but thought maybe it should go here since my questions aren't all specific to the ROM..
I did some basic searching this weekend and was unable to find a definitive answer to these questions, and the few answers I DID find did not seem to work in my case, so I apologize if this is repetitive.*
-Wireless does not work for me- based on what I read, this is a kernel issue, and in order for this issue to be resolved, I have to use a different one. That being said, the one I tried installed successfully but the wireless still did not work. Does anyone have a suggested kernel that WOULD work and allow me to utilize my wireless? I'm on an AT*T Go plan so I'm burning through my 4g cap faster than I'd like because I cant get the wireless to take.*
-When I try to set a wallpaper, the home wallpaper works fine, but when I select 'lock screen' wallpaper or the combo of both, it freezes and then TouchWiz crashes.*
-And the most FRUSTRATING issue- and this is not ROM specific, I realize... but this phone when I purchased it(used) was used on Verizon. I was able to unlock/etc and get it to work with the AT&T Go network after manually entering the APN settings..however- any time an inbound call comes in, it puts a '+' in front of the number. The end result is none of my contacts names show because my contacts obviously do not have a '+' prefacing their number. I tried using an app called Prefixer and set up a rule for it but that did nothing, and I verified country etc is set correctly..does anyone have any clue why this is happening? Very frustrating.*
Bump...anyone? Am I in the wrong place maybe?
otownmarine said:
I posted this in the Hyperdrive thread but thought maybe it should go here since my questions aren't all specific to the ROM..
I did some basic searching this weekend and was unable to find a definitive answer to these questions, and the few answers I DID find did not seem to work in my case, so I apologize if this is repetitive.*
-Wireless does not work for me- based on what I read, this is a kernel issue, and in order for this issue to be resolved, I have to use a different one. That being said, the one I tried installed successfully but the wireless still did not work. Does anyone have a suggested kernel that WOULD work and allow me to utilize my wireless? I'm on an AT*T Go plan so I'm burning through my 4g cap faster than I'd like because I cant get the wireless to take.*
-When I try to set a wallpaper, the home wallpaper works fine, but when I select 'lock screen' wallpaper or the combo of both, it freezes and then TouchWiz crashes.*
-And the most FRUSTRATING issue- and this is not ROM specific, I realize... but this phone when I purchased it(used) was used on Verizon. I was able to unlock/etc and get it to work with the AT&T Go network after manually entering the APN settings..however- any time an inbound call comes in, it puts a '+' in front of the number. The end result is none of my contacts names show because my contacts obviously do not have a '+' prefacing their number. I tried using an app called Prefixer and set up a rule for it but that did nothing, and I verified country etc is set correctly..does anyone have any clue why this is happening? Very frustrating.*
Click to expand...
Click to collapse
otownmarine said:
-And the most FRUSTRATING issue- and this is not ROM specific, I realize... but this phone when I purchased it(used) was used on Verizon. I was able to unlock/etc and get it to work with the AT&T Go network after manually entering the APN settings..however- any time an inbound call comes in, it puts a '+' in front of the number. The end result is none of my contacts names show because my contacts obviously do not have a '+' prefacing their number. I tried using an app called Prefixer and set up a rule for it but that did nothing, and I verified country etc is set correctly..does anyone have any clue why this is happening? Very frustrating.*
Click to expand...
Click to collapse
This is about the only thing I do have an answer for... there is an app called Contacts Optimizer that will allow you to do a mass edit and add the leading + if you're interested in doing that... might help with this issue... https://play.google.com/store/apps/details?id=com.compelson.optimizer
I answered your first two questions in the hyperdrive thread
Sent from my SCH-I545 using XDA Premium 4 mobile app
I have a gear s tmobile. Up until this past week I've been able to use the gear to initiate texts and all of the sudden this function has stopped. When I go into messages, compose and try to send a message I get this phone icon with a half circle in front of it as opposed to the arrow like it's loading or sending but it doesnt move or change and the texts don't send. When i turn off bluetooth and try to use mobile network or wifi i get the red square icon with the exclamation point. I cannot use s voice to initiate texts either though other s voice functions - ie call bill - works fine.
I can reply to texts as they come in all day. I suddenly just cannot start them on my gear. I have tweaked every option i could think of, rebooted, reset the watch, tried to switch from primary textra to primary Samsung messages, removed the sim card and so far nothing. Something wrong with my sim card or what?
***update*** it was the sim card. Not sure why texting worked at first then didn't but I had to log in and input the # on the sim card and reboot.
i dont have a sim. im using bluetoth with the same problems any help?
I know for me, I can't have airplane mode on and send messages. I can still receive them with it on though.
*with bt connected
royorbs3 said:
***update*** it was the sim card. Not sure why texting worked at first then didn't but I had to log in and input the # on the sim card and reboot.
Click to expand...
Click to collapse
Thank you for the update. I am having the same issue except it affects calling only - I can not make any phone calls, and I can not receive any phone calls - I can text and use my data though like normal, but I can not make any phone calls nor can I receive any phone calls. You mentioned that you had to "log in" and "input the # on sim", and "reboot" -- would you please elaborate where you have to go to "log in" like on the: T-Mobile Website? Samsung Website? where do you "log in"?
XDAUserII said:
Thank you for the update. I am having the same issue except it affects calling only - I can not make any phone calls, and I can not receive any phone calls - I can text and use my data though like normal, but I can not make any phone calls nor can I receive any phone calls. You mentioned that you had to "log in" and "input the # on sim", and "reboot" -- would you please elaborate where you have to go to "log in" like on the: T-Mobile Website? Samsung Website? where do you "log in"?
Click to expand...
Click to collapse
Hey yes on T-Mobile website. My T-Mobile.. I forget the exact links but you click into your device and go from there.. Pretty sure there's a number on the sim and you input that and reboot. I called T-Mobile and they were pretty helpful if you get stuck.
royorbs3 said:
Hey yes on T-Mobile website. My T-Mobile.. I forget the exact links but you click into your device and go from there.. Pretty sure there's a number on the sim and you input that and reboot. I called T-Mobile and they were pretty helpful if you get stuck.
Click to expand...
Click to collapse
Ok, I went on to the T-Mobile website, then created an account for my T-Mobile Samsung Gear S phone number under "My T-Mobile". However, when I log in to "My T-Mobile" I do not see anywhere listed a place where I can input the number on my SIM card. I tried looking under the submenus of: Billing, Usage, Plan, Phone, and Shop, but was not able to find the place where I could input the number on my SIM card -- where do I find the place to input the number on my SIM card?
XDAUserII said:
Ok, I went on to the T-Mobile website, then created an account for my T-Mobile Samsung Gear S phone number under "My T-Mobile". However, when I log in to "My T-Mobile" I do not see anywhere listed a place where I can input the number on my SIM card. I tried looking under the submenus of: Billing, Usage, Plan, Phone, and Shop, but was not able to find the place where I could input the number on my SIM card -- where do I find the place to input the number on my SIM card?
Click to expand...
Click to collapse
Hey I poked around and nothing jumped out at me either. I'm currently using gear s2 so my settings may have changed (it has built in sim.) Give tmob a call and they'll help u. Sorry I couldn't be of more help