Hi,
So I searched these forums, the issues on google's website, and another forum, and I have seen only one person or two talking about the issue on the galaxy nexus.
Issue: When texting, either by replying or creating a new text, if I put a contact in the "To" box, it will sometimes remove the area code of the text message, and I will not be able to send the text message.
Work around: In order to finally send the text, I have to write the number of the contact myself in the "To" box. Then, it "reassigns" the full contact number to the contact temporarily, until the problem randomly happens again. I don't know how to reproduce it at the moment.
More information: This seems to occur more with some contacts than others, and occurs randomly. Because I had a custom recovery, I had problems in the past getting the OTA updates, and they just wouldn't appear anymore. I went ahead and installed Jellybean using efrant's guide (here: http://forum.xda-developers.com/showthread.php?t=1626895)
Everything is working fine, except this bug, and the screen sensitivity bug described here: http://forum.xda-developers.com/showthread.php?t=1576739&page=2
Phone information: Samsung Galaxy Nexus on the Bell network
Android version 4.1.1
Kernel Version: 30.0.31-g6fb96c9
[email protected] ), etc..
Build number: JRO03C
Running stock recovery
Has anyone else experienced this bug? It never happened on Android 4.0.2.
The solutions cited for the other phone mentioned doing a factory reset, or switching to a custom ROM. I doubt a factory reset will fix it, but I will try it later this afternoon.
If you need more information, I'll be glad to provide it. Apologies if this was posted in the wrong forum.
C.
c0m3ng said:
Hi,
So I searched these forums, the issues on google's website, and another forum, and I have seen only one person or two talking about the issue on the galaxy nexus.
Issue: When texting, either by replying or creating a new text, if I put a contact in the "To" box, it will sometimes remove the area code of the text message, and I will not be able to send the text message.
Work around: In order to finally send the text, I have to write the number of the contact myself in the "To" box. Then, it "reassigns" the full contact number to the contact temporarily, until the problem randomly happens again. I don't know how to reproduce it at the moment.
More information: This seems to occur more with some contacts than others, and occurs randomly. Because I had a custom recovery, I had problems in the past getting the OTA updates, and they just wouldn't appear anymore. I went ahead and installed Jellybean using efrant's guide (here: http://forum.xda-developers.com/showthread.php?t=1626895)
Everything is working fine, except this bug, and the screen sensitivity bug described here: http://forum.xda-developers.com/showthread.php?t=1576739&page=2
Phone information: Samsung Galaxy Nexus on the Bell network
Android version 4.1.1
Kernel Version: 30.0.31-g6fb96c9
[email protected] ), etc..
Build number: JRO03C
Running stock recovery
Has anyone else experienced this bug? It never happened on Android 4.0.2.
The solutions cited for the other phone mentioned doing a factory reset, or switching to a custom ROM. I doubt a factory reset will fix it, but I will try it later this afternoon.
If you need more information, I'll be glad to provide it. Apologies if this was posted in the wrong forum.
C.
Click to expand...
Click to collapse
I'm seeing a similar issue on my Nexus 4. For example, place a call to 123 456 7890. End Call. Go to the call log and click on the number which brings up a contact screen showing the number and SMS icon to the right of that number. When you click on that SMS icon, it brings up 456 7890 as the so number. On two occasions I have seen the full number with area code appear for a split second but then the area code gets removed.
integramodder said:
I'm seeing a similar issue on my Nexus 4. For example, place a call to 123 456 7890. End Call. Go to the call log and click on the number which brings up a contact screen showing the number and SMS icon to the right of that number. When you click on that SMS icon, it brings up 456 7890 as the so number. On two occasions I have seen the full number with area code appear for a split second but then the area code gets removed.
Click to expand...
Click to collapse
I have the EXACT same problem on my Gnex on 4.2 stock. I don't understand it and i'm not finding a solution, I've asked on Reddit /r/Android with no answer. Is this issue really not that common? I see there hasn't been reply or anything on this thread since February
Related
I receive messages, the inbox show a number of messages between brackets, but when I open it is empty, it does not show any messages. Anybody got a clue why? :?:
Duplicate issue needs help
I am having the same issue. I have the ATT fuze, however this is my third one. The first one was perfect until there was a party foul that took it away. The second one had a typing issue so I replaced it. This third one is doing the same as the above poster mentioned. My today screen will show that I have text messages waiting to be opened but when I navigate to the folder there is nothing in it. Performed a hard-reset but the same thing happened. Installed third party software and now I can view the messages and reply. I am not happy with this "bandaid" but it will temporarily do till this can be resolved. Please help.
ROM version: 1.95.502.5 WWE
ROM date: 10/20/08
there may be something wrong with your storage card
the storage card can, by any means, have nothing to do with it. i personally never had such a problem, so i can just guess:
sample situation:
- i receive an sms, i see a notification, with the sender and the first few words.
- instead of clicking read, i press the hardware mail button to open messaging and read the sms
- while having it opened, i delete it.
- i go back to home screen and there is still a message and a notification
now i have confused my phone showing me new messages, although i already read and deleted them.
that is the only way i could think of to even get in that situation.
btw. that is the same thing with missed calls. if i have a notification of a missed call and instead of clicking the notification i open the phone manually and look whose call i missed, i will still have the message on home screen, telling me, there was a call i didn't know about, although i already checked.
please make sure that the description above is not the case.
because that is a general bug/user mistake, since the notification service is not fully integrated in pocket outlook, sometimes it gives out older data if you bypassed it to get to your information. that is normal. next time you get a message, try clicking the notification and click read or save as read, and look what consequences that has in your messaging folder.
if then still there is no message to be found, right after you read it once, it is still probably an error in the communication between notification service and pocket outlook, but then it is not your fault anymore you'd probably have to flash another rom then,
OR
it is something completely different and you need to contact your carrier, that receiving sms doesn't work out for you, that either you get a new sim or other network settings need to be changed.
my solution
I made some changes using advance config and changed portrait and landscape mode to cleartype. the fuze does not work with cleartype in landscape mode. Turn that off and it begins to work.
Text Messages not displayed
I know this is a very old thread but did anyone come out with a solution.
I'm still using my Blue Angel and it's come up with this problem.
I think it was after I received an MMS message (the first I received).
this is the first time ive ever had this problem. I can text everyone in my contacts fine except one person, even other people on metro.
Im on sprint, they are on metro.
the area code works when sending a new text message and if you keep the thread on the screen but as soon hit the back button it removes the area code and gives an error when sending.
I ran into a similar problem today at work , but that person is also on Sprint
my dad and coworker have this problem also, i have yet to see it
nobody has a clue on how to fix this still?
I had this problem one time, but i could never replicate it. I'd suggest trying a new messenger (go sms is amazing).
Not sure how well this pertains to your situation.....
Here is a solution I found that works for me, to prevent the stock Android messaging app from deleting the area code in a 10 digit phone when creating a new text message from within the messaging app.
In google.com/contacts my cell phone numbers were saved like this +1 (444) 555-1234 changing it to +1 444-555-1234 resolves the issue for me. Removing the () parentheses solved the problem.
I have flashed this custom ROM onto my new Defy+ as per Walter79s instructions and it is all working fine apart form a few small problems that I haven't been able to find a solution to. I have used search in both Walter79s thread with it's thousands of replies and in the defy forums search and drawn a blank in both.
1. My contacts do not seem to be synced with my SMS, instead of showing a contact it shows a number e.g. +447xxxxxxxxx instead of Boss or Wife or Mother-in-Law!!!. Quite annoying as barely anyone ever signs a text.
2. Any contact (synced from my Blackberry through google sync) who has a photo attached to their gmail account seems to have Chinese characters above their number when viewed in the dialer. Not really an issue just a funny little bug.
3. An aside to this Chinese characters is that when I first installed the ROM a few other things had these characters too. The only one I can remember off the top of my head is the calendar which had the dates both in numbers and Chinese characters. Went away after I reset the location.
Edit: 4. The SMS compose bar is tiny. Is this in anyway adjustable.
I am very new to android but Walter79s MS2Ginger installation guide and Zephyrot's All-in-One have got me through rooting annd flashing on my first custom ROM. Just hope that an ICS/CM9 stable ROM isn't too far away.
Thanks.
I have been searching high and low for this issue and it appears not to be uncommon but with out any definitive fix. I have played around with a number of things, changing all the 07s to +447s just meant that SMS contacts were recognised but callers were not. I also tried a couple of prefix apps, these did work but only showed you the caller in a 3rd party bubble not on the main display. Tried setting IP prefix to 0044 but this made no difference as I believe it is for outgoing calls only. I haven't managed to find a fix for it but there does seem to be a couple of work arounds.
1. You can double up on all your contacts e.g. have both 07123456789 and +447123456789 listed under the same contact. A right pain with so many numbers. Also tried exporting and "find and replace" 07 with +44, this lead to some interesting numbers where the 07 was in the middle!
2. Live with the prefixer app so you can see who is calling and SMS contacts. OK but not great for missed calls or call logs to clients or colleagues.
3. Live with it or go back to the original Defy+ ROM. Rather not as that MotoBlur thing got right on my wick.
Any ideas would be gratefully received.
Ta
Update: Using my Sherlock Holmes like powers of deduction I have managed to find the source of this problem. My contacts book only appears to be using a max of 11 digits to identify numbers. It will recognise 07xxxxxxxxx but not +447xxxxxxxxx. However if I change the number that is saved to 47xxxxxxxxx the contact is recognised. I'm going to try re-flashing the ROM to see if it's just an error that occurred during instillation. If this doesn't work I will try a different ROM.
I am wondering whether my baseband setting might have any connection to this? It is currently EPU93_U_00.60.00 but there are several UK specific options in my baseband selector. None for my provider (Vodaphone) so I am a bit cautious of changing this.
Once again any ideas would be gratefully received.
Flashed MS2Ginger2.1 with deblur patch. Working great. Thanks Walter79! http://forum.xda-developers.com/showthread.php?t=1140839
Hey everyone. I'm having a big problem w/ my 16GB GSM Galaxy Nexus running bigxie's rooted, deodexed 4.1 rom, and I'm hoping you guys can help me.
Whenever I send a message, I get a "Message not sent" error in the notifications bar, and a red triangle w/ an exclamation point appears under the text of the text message. I have T-Mobile and I have FULL signal bars. I can make calls and this texting issue is the only problem I'm having. I installed this rom a few days ago and this problem just suddenly started today. When I send a text with the "Messaging" app, the area code (I live in the US) of the phone number disappears. So if the number in my phonebook is stored as:
"1 (areacode) sevendigit-phonenumber"
It instead shows up like this after I select the contact:
"1 sevendigit-phonenumber"
If I try and send a text by selecting the contact from the "People" app, it works just fine.
Last night I flashed the Popcorn kernel, but I then I also sent a text and it worked. I thought maybe somehow this might have something to do w/ the kernel or a rom (both unlikely), so just in case I re-flashed the STOCK 4.1 this time (the first rom, the one that appeared on ROM Manager the day of the Google I/O). Now I'm back to stock Jelly Bean everything (including kernel, and also the Jelly Bean baseband) but I'm still getting the problem. I tried clearing the "Messaging" app's data and cache, but nothing fixes the problem. I have a strong feeling that the cause of the error is because the "Messaging" app removes the area code from in front of the phone number, but now I can't remember if that's normal (did that happen in ICS?, did it happen before in JB?, I don't remember).
Has anyone else encountered such an error? Please help me.
I too am experiencing this issue running bigxie's 4.1 ROM on my 16 GB Galaxy Nexus.
I hope someone has a solution!
I think I may have fixed the problem for myself. It seems like in both the stock JB and also bigxie's rom, the "Messaging" app is doing some sort of mishandling of the phone numbers. Try changing one or some of your phone numbers in your contact list to this format: "(307) 456-7895" <-- parenthesis around the area code, then a space after the parenthesis, then the seven digit number with a dash (-) after the third. Try changing this format on Google Contacts, not on your phone. Then sync the contacts on your phone.
Try this with just one contact that wasn't previously working and please let me know what happens.
I'm having the same problems with the same rom and tried the same steps to fix it but it didn't work for me. Also tried going back to cm9, no luck.
Search for the setting for something like ##info#* or whatever. I blew mine out when I flashed a new rom (not the roms fault i did it not knowing better). Don't have time now to look but there are important settings for sending sms.
Jeff
[email protected] said:
Search for the setting for something like ##info#* or whatever. I blew mine out when I flashed a new rom (not the roms fault i did it not knowing better). Don't have time now to look but there are important settings for sending sms.
Jeff
Click to expand...
Click to collapse
Thanks I figured it out. I had a hard time finding this info so ill re post it here for any one who needs it. It solved all my problems.
http://rootzwiki.com/topic/14916-howto-sms-centre-numbers-if-your-gnex-wont-send-messages/
Hi
This damned *#*#4636#*#* menu!!!
I know, I shouldn't be messing with what I don't know but I moved from an iphone so that I could 'fiddle' with a phone hence the GNex.
Anyhow. I have been having serious issues in sorting this out until I pieced the information together in this post. None of this I can take credit for - as it is built on others work - I just put it together in one easily accessible place.
The problem is that this menu somehow wipes the SIM card's record of the SMSC number.
You can't just enter the SMS Centre number as it is, you have to convert it into something called PDU format (no idea what this is)
I have converted a number of UK SMS Centre numbers into the correct format below.
Method:
1. Go to phone dialpad.
2. Enter *#*#4636#*#*
3. Scroll down to the bit that says SMSC
4. Type your sixteen digit number in from the table below.
5. Press Update
6. Press Refresh
7. Press Back button to exit the app.
8. Test by sending an SMS
Hope that helps. The GNex doesn't give an option which is easily accessible from anywhere to change the SMSC number, downright silly as my 10 year old Nokia would let me do that.
Click to expand...
Click to collapse
PDU Decoder
http://www.twit88.com/home/utility/sms-pdu-encode-decode
I couldn't quite follow those directions, but my problem fixed itself without doing any of that. It just suddenly started working after I changed the format of the numbers in Google Contacts.
i tried these steps but no luck.. its simply the format of phone numbers.
this format is no good: +1 (123)-456-7891
this format is good: +1 123-456-7891
another solution is just to manually update each contacts.. i wish there was an app that does it automatically
install handcent sms app...go to undelivered SMS in menu...delete in any undelivered sms is there...it worked for me...
u can uninstall Handcent post that
I had the same problem , Can't send but can recieve sms ,
the problem presents since updating to jb 4.2.2 ,but it was working in 4.1.2
I tried the smsc solution but no luck at all ,
I think it's not a carrier problem cause i can send from Moto Defy "CM7.2 " ,but no luck with JB
Plz help
Another Fix
Tried all the fixes I could find with no luck. Then found out that I had enabled Google Voice+ to send SMS messages through Google Voice. After I disabled this everything went back to normal.
Just another thing to try that worked for me.
I know this is somewhat old but wanted to say for me, that the messages were being sent but there was one stuck in the queue. I followed the directions of installing handcent and found the empty text sitting in the queue... like a draft message. Once removed the message went away. I uninstalled handcent and all is good. It sucks that the stock JB 4.2 messaging app doesn't have a outbox and draft box to find stuff like this. Thanks for the help!
hellandj said:
Tried all the fixes I could find with no luck. Then found out that I had enabled Google Voice+ to send SMS messages through Google Voice. After I disabled this everything went back to normal.
Just another thing to try that worked for me.
Click to expand...
Click to collapse
THIS all the way!! I was trying everything to get my sms to work but it ended up being google voice+
Thanks for the reminder
I'm hoping someone can help me out...
Late last week I changed my ROM to HenseMod7 (for VM) - to give it a try and because some of the other ROMs I had been trying were giving me issues with MMS, calls and other things. All was good - or so I thought.
A day or two after I made the change - I started getting text messages from 999-999-9999. These text messages are all gibberish - letters, symbols and numbers mixed together. They always come two messages together and about 12 hours apart (so about 4 per day). I delete them as soon as I see they are in my list.
I saved the contact to my phone and blocked it as a caller.
I went onto the VM website and logged into my account and blocked the "number" for text messages - but since I know it isn't a "real" number - you've probably guessed it - I'm still getting these messages.
Might this be something related to the ROM somehow? I mention that only because all the other ROMs I've tried since I rooted my phone have not had this particular issue. This is the first time I've gone back to a Sense-styled ROM (made particularly for VM) and it's the only time I've gotten these spam texts.
I hesitate calling VM about this issue if it could/might be related to the ROM since I know they are less than helpful when you root your phone.
Any thoughts, ideas, input or help would be so very much appreciated.
Thanks all!
Mamadanz said:
I'm hoping someone can help me out...
Late last week I changed my ROM to HenseMod7 (for VM) - to give it a try and because some of the other ROMs I had been trying were giving me issues with MMS, calls and other things. All was good - or so I thought.
A day or two after I made the change - I started getting text messages from 999-999-9999. These text messages are all gibberish - letters, symbols and numbers mixed together. They always come two messages together and about 12 hours apart (so about 4 per day). I delete them as soon as I see they are in my list.
I saved the contact to my phone and blocked it as a caller.
I went onto the VM website and logged into my account and blocked the "number" for text messages - but since I know it isn't a "real" number - you've probably guessed it - I'm still getting these messages.
Might this be something related to the ROM somehow? I mention that only because all the other ROMs I've tried since I rooted my phone have not had this particular issue. This is the first time I've gone back to a Sense-styled ROM (made particularly for VM) and it's the only time I've gotten these spam texts.
I hesitate calling VM about this issue if it could/might be related to the ROM since I know they are less than helpful when you root your phone.
Any thoughts, ideas, input or help would be so very much appreciated.
Thanks all!
Click to expand...
Click to collapse
Hi,
Your problem is very strange and honestly, I tried HenseMod and I didn't get this error. It is although true that this ROM has some problems with text messages as I couldn't send a long message (the ROM could not split the long message into several small messages of 160 characters).
I can see only two solutions : either you change of ROM (there are maaanny good ROMs for the Wildfire S) either you reinstall your ROM, verifying you have the good version for your phone model (marvel, marvelc, etc.). Maybe you can also update your radio if you can do it and know how to do it, but I guess it wouldn't be really helpful in that case.
Do you think these messages come from a real person ? Maybe there are some network problems, or maybe the ROM cannot read the message from a particular network / phone, I don't know.
Good luck
Mamadanz said:
I'm hoping someone can help me out...
Late last week I changed my ROM to HenseMod7 (for VM) - to give it a try and because some of the other ROMs I had been trying were giving me issues with MMS, calls and other things. All was good - or so I thought.
A day or two after I made the change - I started getting text messages from 999-999-9999. These text messages are all gibberish - letters, symbols and numbers mixed together. They always come two messages together and about 12 hours apart (so about 4 per day). I delete them as soon as I see they are in my list.
I saved the contact to my phone and blocked it as a caller.
I went onto the VM website and logged into my account and blocked the "number" for text messages - but since I know it isn't a "real" number - you've probably guessed it - I'm still getting these messages.
Might this be something related to the ROM somehow? I mention that only because all the other ROMs I've tried since I rooted my phone have not had this particular issue. This is the first time I've gone back to a Sense-styled ROM (made particularly for VM) and it's the only time I've gotten these spam texts.
I hesitate calling VM about this issue if it could/might be related to the ROM since I know they are less than helpful when you root your phone.
Any thoughts, ideas, input or help would be so very much appreciated.
Thanks all!
Click to expand...
Click to collapse
just another option it could be a service network message that is not coming through properly. in the uk when you activate your sim card in a new phone uk carriers send you a text message that contains the network settings to get online. if your access point is not already configured
it could be getting scrambled somehow. if you can you could try to contact your phone carrier. go into a hop if possible and ask them if they have kept any logs of sending you service messages. if so maybe try to cross reference them and see?
Thank you both Izzy and Heavy_Metal_Man for your thoughts on this.
Since I first posted the question, I have changed ROMs and the problem has stopped. This is the curious thing. I have been trying different ROMs on my phone since I first rooted it last winter and only with HenseMod have I had this kind of annoyance.
In searching the internet on this - I have found posts by other Virgin Mobile users about this same issue. At one point someone mentioned that it was some kind of message from "Telus" (which is a Canadian provider - but I live in the US - and quite a distance from Canada). Most of those posts were from non-US users.
I do receive updates from VM without issue - so I don't think it's that.
I have a Marvel C phone if that adds anything to the equation.
Thanks again for your input. Anyone else have thoughts?
Mamadanz said:
Thank you both Izzy and Heavy_Metal_Man for your thoughts on this.
Since I first posted the question, I have changed ROMs and the problem has stopped. This is the curious thing. I have been trying different ROMs on my phone since I first rooted it last winter and only with HenseMod have I had this kind of annoyance.
In searching the internet on this - I have found posts by other Virgin Mobile users about this same issue. At one point someone mentioned that it was some kind of message from "Telus" (which is a Canadian provider - but I live in the US - and quite a distance from Canada). Most of those posts were from non-US users.
I do receive updates from VM without issue - so I don't think it's that.
I have a Marvel C phone if that adds anything to the equation.
Thanks again for your input. Anyone else have thoughts?
Click to expand...
Click to collapse
So the problem really comes from the ROM and it isn't really strange because HenseMod is known to have some SMS bugs
My first thoughts were some kind of loopback error related to cell broadcasts and/or emergency message notifications. If you consider the times you mentioned, have some imagination, and throw in some cross-talk pollution it might even jive with what h_m_m (heavy_metal_man) was saying (in terms of it repeating); however, when I looked at the ROM, it's strictly GB/CM7 and those features weren't incorporated until ICS. So I'm gonna say that h_m_m has the most plausible reason. Thank goodness you found another ROM that works and can move on and leave the problem to those who want to keep trying to figure it out.
Ive had another thought about it. What base version is the Rom made from? If it's based from a carrier specific Rom and then "De-carrierized" it may have been conflicts left in the networking configuration that made the cdma/gsm believe it was in another country and needed roaming data settings. In any event I'm glad your sorted pal
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
Thank you!
Thank you all for your thoughts and comments on this matter. I truly appreciate it!
As I previously mentioned, once I changed the ROM - the annoying texts stopped. So perhaps (as others have mentioned) it may be a quirk of the ROM itself.
I do like trying different ROMs - makes me feel like I've got a new phone for a brief time, while I still have my little Wildfire S. Its a fun "exercise" for me. Wish some more developers would build for the MarvelC though.
Thank you all again!