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
Related
Hey all,
I recently upgraded my Kaiser from WM6 to 6.1 using the official upgrade tool Vodafone UK supplied me, and all went without a hitch, so much so that I think I'm gonna try out Hyperdragon III while I'm on the "doing funky things to my phone" bandwagon. I have noticed one problem though, and I figure it'll probably be a problem when I reflash too so I'm trying to solve it now.
When I imported all my contacts and SMS messages (which I backed up using sprite), I though it was all fine. I opened my SMS inbox and watched as it built the threaded list, etc, and everything was good until I received a new message. The sender was in my contacts list, and had previous messages in the threaded view, and as intended, the new message added to their "thread". But as soon as it did, the thread had their number instead of the contact name as the title.
I did some experimenting, and this happens everytime I get a message from someone who previously had a named entry in the inbox, but if I get a message from a newly created contact, it works fine.
If I go into a thread from someone who hasn't sent me a post-upgrade sms yet, their name is displayed properly, but when I click on it (which should bring up a screen displaying their details), I get a message saying the number isn't in my contacts and would I like to add it.
Sorry if this has been answered before, I had a look and couldn't see anything.
Any ideas?
same problem too
Hi, I am currently experiencing a wierd SMS issue on my Desire running Robo's HD rom 0.13. Lets point out first that my sms is fine, I can send and receive texts perfectly. Except for one contact.
Me and my girlfriend text a lot, and I believe my phone doesn't want me to. Whenever I text her, she texts back, and I go to text her back,it says message not sent. However, if I delete the thread (with two messages in) and create new message,it sends fine. Baring in mind we exchange around 100sms per day, I am having to delete the thread and create a new text message just to get one through, which is getting quite annoying. I shall just stress this is the only contact out of the 25-30 people I text regularly who I am having this problem with. The things I have tried are:
Deleting and creating new contact
Changing her number to various formats (+44, 44, 07 etc)
Reboots (many of them)
Changing her contact name
Different sms apps (chomp, stock, handcent)
Nothing has worked, and the problem still remains. I would really like this sorted, as it is getting quite annoying. Any help will be greatly appreciated.
tucka20 said:
Hi, I am currently experiencing a wierd SMS issue on my Desire running Robo's HD rom 0.13. Lets point out first that my sms is fine, I can send and receive texts perfectly. Except for one contact.
Me and my girlfriend text a lot, and I believe my phone doesn't want me to. Whenever I text her, she texts back, and I go to text her back,it says message not sent. However, if I delete the thread (with two messages in) and create new message,it sends fine. Baring in mind we exchange around 100sms per day, I am having to delete the thread and create a new text message just to get one through, which is getting quite annoying. I shall just stress this is the only contact out of the 25-30 people I text regularly who I am having this problem with. The things I have tried are:
Deleting and creating new contact
Changing her number to various formats (+44, 44, 07 etc)
Reboots (many of them)
Changing her contact name
Different sms apps (chomp, stock, handcent)
Nothing has worked, and the problem still remains. I would really like this sorted, as it is getting quite annoying. Any help will be greatly appreciated.
Click to expand...
Click to collapse
Tried another radio?
jmelhus said:
Tried another radio?
Click to expand...
Click to collapse
Yep, forgot to mention have used both 5.09.05.30 and 5.10.05.30 with the same results. She has no problem texting me (hero with cm 6 froyo), nor does her friend texting her (stock 2.2 desire)
tucka20 said:
Yep, forgot to mention have used both 5.09.05.30 and 5.10.05.30 with the same results. She has no problem texting me (hero with cm 6 froyo), nor does her friend texting her (stock 2.2 desire)
Click to expand...
Click to collapse
Well, I'm experiencing it sometimes as well on my phone, but not as frequent as you are describing here.
I had this issue once with a Sony Ericson. It dissapeared when changing carrier and sim. Maybe you can try a "pay as you go" sim card for one day?
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
Hello everyone, I would like to start by saying thank you to everyone here, all of your posts, info, etc has been excellent in helping me along my way to learning enough about this stuff to be dangerous to mine & my friends phones...we're all still using them so that's a "Win" in my book
Now, on to my problem. I've tried googling & searching posts here, and I don't know if it's just the terminology I've searched but I've found nothing similar to my problem except where a thread had to do with EMBS messages coming through incorrectly.
First off, I'm on a Sprint Branded Samsung Epic Touch 4g Galaxy S II (whew that's a mouthful already) It is on Verizon Prepaid Service.
When I first set this phone up, everything worked correctly - Talk, Text, Web, MMS, WiFi Hotspot, Etc - all working perfectly. I was able to send & receive picture mail through MMS, etc.
I am currently running CyanogenMod 9-20120416-SNAPSHOT-epic4gtouch-Alpha 3
Android Ver 4.04
Kernel Ver 3.0.15-SPH-D710.FD10-CL377892
This is the updates I installed to this phone originally:
gapps-ics-20120429-signed
StockCWM-EL26.tar.md5
update-cm-9-20120416-SNAPSHOT-epic4gtouch-alpha3-signed
mmsfix.zip (and made the correct changes for Verizon)
As I said, the phone was 100% functioning at this point for several days. The problem that came up happened out of nowhere, no changes were made to the phone whatsoever, not even a random app was installed from the market.
The only apps I have installed are
Wifi Tether (Rooted Users)
ES File Explorer
Facebook
GMail
Craigslist
Facebook Contact Sync
NFL Scoreboard
QR Droid
SuperUser
Rom Toolbox
Rom Manager
Terminal Emulator
Other than that, it's just what ICS & GApps Installed.
So here's the problem - whenever I recieve a text from anyone now, if it comes in multiple texts (ie 1/2, 2/2/ etc) it shows up as all special characters when I recieve it.
Here is the last one I got, I sent it from another phone on the same carrier - I just typed myself a message until I was sure it would be a 2 part message and this is what came through on my Epic
First Msg
ß<xp¿AcGÉ?üööysgOS&Læ;6lX9W/Ü<9rfEØΨ+FøÆ8xp¿A¥ìÅß<xqF<9$fÅz<EEggÜNixw¿
5¥rdåÆΩÖÅΠ'ålÄ3gF
3vø)rlyscW/Ü>ñzsbEKΨ/ÜÆ_gGEìgVLhurd1äñ2AÅZ#ΛC<z¡@@@@@@@
Second Msg
Ü=ävhPfOÉ?N3vlY1cnÖ<yreIΨ/Ü<9rfEØC¥ìÅÆ8xpaCì
Λ(XΔA$éZTGøΔHEwì/ÖrsOà#Ec=P
I put it in a hex/text converter and the text version came up all "?'s" so I'm pretty much at a loss at this point.
I apologize for a long winded message, but I wanted to include as much information about my phone, etc as possible to get the best answer I could.
Again, thank you all and if anyone has any insight to what might be causing this, I would greatly appreciate the info.
Oh, and in case I didn't make it clear - at this moment, text works fine (if its only 1 text at a time incoming) I can send multiple page texts & the recipient gets them no problem, and I can send/recieve pictures, etc as mms with no problems...the problem only exists if it's multiple pages of text coming in at once.
Thanks
What happens if you use a 3rd party messaging app like handcent?
someguyatx said:
What happens if you use a 3rd party messaging app like handcent?
Click to expand...
Click to collapse
I just tried a few diff versions of Handcent, with the settings Default, then again with the settings on "Default SMS/MMS App (Disables Stock & Other Messaging Apps) and got the same results...
The wierd character code that comes through is exactly the same, both with the stock app & handcent in case that might be a question...
**Update**
I have Google Voice number sending voicemail converted as text to my phone on a secondary number. I got one today, was 3 pages SMS and it came through perfectly, right after that, I got a reg text from someone elses phone that was 2 pages, and it was the same type characters, and a few more since that were all the same special characters.
I've tested the Google Voice translation a few more times, and it comes through perfectly. I also tested just sending a multi-page text to my google voice number, which just forwarded the texts to my phone via SMS and they also come through perfectly.
So SMS from Google Voice in multiple texts works great, but from another phone do not.
If anyone has seen anything like this, I would love to know I'm not alone.
I'm having this exact same problem too. I noticed multiple texts incoming from certain people are fine, but when I receive multiple texts from a few others or a group sms from an iphone I get this really wonky characters. Any help would be appreciated. I am using this phone through pageplus.
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