Hi all,
I'm using a GSM Razr XT910 with the CyanogenMod 9 customised ROM by J.Y. Daddy (RAZR-CM9-12.05.17-UNOFFICIAL-GSM-J.Y.Daddy) and I keep receiving duplicate SMS messages. I've changed to "Original timestamp" in SMS settings to see what's going on, and it seems I'm getting the same message up to 9 times.
It happens with multiple contacts, and I'm not sure how to fix it. I'm in the UK on O2 - does anyone have any ideas for how to fix, or has anyone else experienced a similar issue?
I had this issue too.
I live in Australia and have been using J.Y.Daddy's CM9 builds pretty much since he started porting them over to GSM. I tried to narrow the issue down to a few factors and the main causes I suspected were:
1) Different kernel version to your phone's "natural" one. Have you used RSDLite to flash any different fastboot files? Or are you on rooted stock initially?
2) Handcent. I began using this app after making the switch from GOSMS a while back and shortly before the duplicate message problem began. They have actually confirmed that there is some compatibility issues with some Motorola handsets, and this is reflected by Handcent's changelog. Are you by any chance using Handcent?
3) Finally, the last cause I come up with was a network issue which is refusing to send an 'acknowledgement' packet to the provider, essentially meaning the message is never marked as received and therefore, it keeps sending the message in an attempt to correct this.
In my experience, the problem was #3. I was on Optus for a long time (The 'second place' Australian telco), and recently made the switch to Telstra (#1 telco) and the issue has been resolved. If you are on stock kernel and do not use Handcent, then unfortunately I think it may be a network issue.
Don't take my word on this though, I'm not an expert. Just speaking from experience.
Thanks Mr. Ektid, I think in my case it's probably #1. I installed a different 2.3.6 rom over RSD in order to get the Bluetooth working without causing a bootloop, so I guess that must have messed things up. I don't use or have installed any SMS apps other than stock, and I don't think it's a network issue as texts were working fine before installing ICS.
I've rolled back to Arctic for now, seems to have sorted things again. I suppose the way to fix the issue in CM9 would be to RSD a stock UK 2.3.6 rom and then flash CM9 over that - but I'm not sure if that would mean I would still get Bluetooth bootloops, as it seems like a fairly specific 2.3.6 rom is needed for that to work.
Ah well. Back to Gingerbread for a while.
Related
Not sure if you guys want this here...just thought I'd post here...move if needed...
Ok, problem I've had for awhile now..
I was using Tazz 10 and Nonsensikal 7.0. They were both working perfectly then all of a sudden, I started to not receive txt messages. I can send, but not receive. So I wiped, re-flashed each ROM seperately, nothing. Wiped and nandroid to a ROM that was working, nothing.
I am now doing the Flashback 1.5 to get to Stock ROM. If still not working, gotta take to Verizon. But once it works...gonna Root again and put Tazz 12 and Nonsensikal 8.8. and see if the issue returns.
That's all, just wanted to post if any one else experiences this issue.
OK....flashed the Stock ROM...I am now recieving Txt messages...
Next...re-root and flash Nonsensikal, and see if I am still able to recieve Txts.
After flashing a stock ROM, you should back up your APN files. One way to do this is with a free app on the market called APN backup and restore. It will back up to an XML file on your SD card. After flashing another ROM, use that app to restore the APN files.
What are the APN files for? I am stuck at boot screen since updating OTA. Haven't had a chance to root yet. So I can still do it.
BlazinDANDAMAN said:
What are the APN files for? I am stuck at boot screen since updating OTA. Haven't had a chance to root yet. So I can still do it.
Click to expand...
Click to collapse
I believe they tell your phone which towers to connect to. So if you don't have the correct APN files, your phone has issues receiving messages. Some of the ROMS that are based on ROMs from other carriers may not have the right APNs.
synesthete said:
I believe they tell your phone which towers to connect to. So if you don't have the correct APN files, your phone has issues receiving messages. Some of the ROMS that are based on ROMs from other carriers may not have the right APNs.
Click to expand...
Click to collapse
Shouldnt a *228, option 2, update the PRL to current for Verizon?
Well, I went through everything and now I am NOT receiving messages again. I re-rooted and flashed Tazz 12 and now not receiving Txt messages again. Damn! I have to have an unrooted phone now? This sux. I can't be with out Txt messaging.
FYI...I restored APN's and did *228
Is it with your stock txt app or did you download one? I had problems similar to yours with ChompSMS on NonSensikal. Wiped and reinstalled rom but stuck with Stock messenger and the problem never returned. If you are on stock try a different txt app. Good luck!
It was with both apps...neither were recieving. I have since restarted and it seems to be working at the moment...
Could it be that your not popular?
jk, have you turned the Wi-Fi off, cause that has seemed to work for me
BlazinDANDAMAN said:
It was with both apps...neither were recieving. I have since restarted and it seems to be working at the moment...
Click to expand...
Click to collapse
I would have the problem with both apps as well but when I reinstall the rom it would work and then a little while after installing Chomp it would stop again. Finally did a reinstall and didn't install ChompSMS and everything worked and stayed working. Good Luck!
One of my friends was having this issue too and it was due to which radio version she was using. The radio included in Tazz, KaosFroyo, and Nonsensikal were all giving her issues. She switched to xtrSense and the radio with that played nicer with her phone and all was well. Check out which version each rom runs and then you can flash the other radio over whichever rom you'd want. With that being said, I should also point out that there is a small chance, were something to go wrong with the radio flash, of damaging your phone. Now I have flashed two or three different ones, and had another friend purposely try to brick his phone by flashing radios from different phones even as well as pulling the battery while flashing a radio, and did not brick his phone. Just like rooting your phone, there's always a chance something can go wrong, but at that stage it's all about weighing the pros and cons and if you have a back up plan. Hope this helps.
I'm having the same problem. I was running KaosFroyo then Nonsensikal with no issues. I switched to Tazz Froyo today and now I can't receive texts, only send them. I flashed back to Nonsensikal and it didn't remedy the problem. The radio is the same on Tazz and Kaos (didn't check Nonsensikal) so I don't think that's the issue.
I would like to point out that kaosfroyo doesn't include a radio it uses whatever you have
Sent from my FroyoEris using XDA App
Problem Solved
I found the solution here: http://forum.xda-developers.com/showthread.php?t=770879
Hopefully it works for you as well.
Hey guys. I looked all over and can't find anyone with this specific problem, so if this is a duplicate post I'm terribly sorry.
I'm running CM7 official, Glitch 13.1 with EH03 radio (not sure if that's important or not)
Problem is, my phone can't send or receive mms (sms works fine), and since receiving an MMS message, the Messaging app has been absolutely consuming my battery (screenshot attached) even after multiple resets.
I originally thought it might be a radio issue, since I was having trouble switching between 3G and WiFi, but since switching to the Glitch kernel, everything's been fine connection-wise, which is why I believe it's something else entirely.
Has anyone experienced similar problems?
MMS seems to be a sore spot with custom roms. Do you need MMS, or can you live without it? Also, can you just kill/freeze Messaging and use a third-party app?
Yeah, freezing the app solves the CPU problem.
If I freeze mms.apk and use handcent, it's generally more reliable. Why is this, though? What're these 3rd-party apps doing differently than the standard?
Sent from my SCH-I500 using XDA
I'm not a dev, so I really don't know.
Both are running latest Energy as it seems to be the most stable rom. We are having two issues.
First issue, we can not view or send text messages from a specific person. We have to delete the history and then we can view/send messages.
Second Issue, Same as above except the stock or any other text messaging up stop working, only through a wipe and reload can this be fixed.
Third, Both phones would not go passed the start up animation. Had to wipe and reload.
4rth, Phone will be on then turn off without any notification. Need to pull battery then it works.
There are more issues.
I'm sure this is nothing hardware related, more software related.
Is development for the Amaze dead? Most roms either still need a lot of work while others have not been updated in months.
I had an atnt S3, I loved not having any issues. ;,(
Soff?
What bootloader.?
Did you double flash? (some say it helps)
Here is my process
Super wipe
Flash
Fix permission
Boot
Boot
Flash again
Fix permission
Boot
All boots are cold full boots not quick etc
If you want to flash app data etc from another rom your asking for problems
If your on tmobile there are mms issues that some roms need a fix flashed too. (dunno which tho.. I'm on wind)
If you swap mms apk's some just don't work well with our phones.. Get/use/keep the right one (as system) then add chomp or gosms or whatever
e-Sex.. All of the carpral none of the tunnel
there's been lots of new rom releases for the amaze recently since CM10 got data working, and id say speed rom or fourth bar infusion are among the most "stable" and "best" looking roms out... personally i would get a superwipe that krook6023 posted earlier somewhere in the Q&A section, flash super wipe and flash a rom or flash back to stock and start over again because it sounds like you did something wrong and what recovery are we using to flash these said roms?
F9zSlavik said:
Both are running latest Energy as it seems to be the most stable rom. We are having two issues.
First issue, we can not view or send text messages from a specific person. We have to delete the history and then we can view/send messages.
Second Issue, Same as above except the stock or any other text messaging up stop working, only through a wipe and reload can this be fixed.
Third, Both phones would not go passed the start up animation. Had to wipe and reload.
4rth, Phone will be on then turn off without any notification. Need to pull battery then it works.
There are more issues.
I'm sure this is nothing hardware related, more software related.
Is development for the Amaze dead? Most roms either still need a lot of work while others have not been updated in months.
I had an atnt S3, I loved not having any issues. ;,(
Click to expand...
Click to collapse
I've been on NRG since I got my Amaze, and I don't have these issues. The only problem I have is an occasional lock up when using BT, but that is very rare. One thing you might do is a reset from recovery, and then do not restore the phone - manually reinstall all programs. It is possible that your restore is putting problems back into the device.
This would include not using Google to backup your settings before reset.
Dear Genius Developer Community,
First let me say thanks for the MOUNTAINS of information I have mooched from your collective brains over the last 5 or so years. From the time Android first launched you guys have made my whole experience more enjoyable.
I am using a Motorola Droid RAZR MAXX (XT912) on Verizon running Cyanogenmod 10.1.2 and the built in messaging application with Safestrap 3.11. Great phone made even better by a great ROM. The only issue I have had so far is a strange intermittent MMS problem: sometimes I just don't receive the message. Texting is fine and all other data access is perfect. Sometimes they come through, and sometimes they don't. When they don't, if I reboot the phone I can receive them again (at least for a time) but the ones that were sent during the down time never come through. Below are the things that I have tried and the effects they have had (if any). Any light you guys can shed here is greatly appreciated.
Wi-Fi
I read somewhere that MMS wouldn't send without a mobile data connection so I have tried completely disabling Wi-Fi - no effect.
Access Points
Everything I have found points to the Access Points being wrong and so I have messed with them for days going so far as to delete telephony.db and COMPLETELY removing all of the default access points replacing them with the EXACT APNs from the stock ROM - no effect.
Rebooting
Whenever I reboot my phone I can receive again. As previously stated, nothing sent before ever comes in but I can now receive new...for a time. Eventually I will get a text from someone "did you get that pic?" - temporary fix.
As an additional note, on the stock ROM I have never had an MMS issue of any kind so I know it's not a service or phone issue.
I to have been having issues with my MMS. But I run the newest nightly of avatar ROM. It is based off of Cyanogenmod from what I understand. Any who I'm having issues with my MMS not allowing me to send pics. This is only on this ROM. I had carbon and it seemed like it worked fine. Any way does anyone have a fix for this or is it a known issue with the Cyanogenmod at this point. And sorry, hope you don't feel I jacked your thread. We just both have a similar issue.
If you are running adblock plus turn it off. This fixed my issue
My MMS usually doesn't work on most custom ROMs, I switched to the handcent app and MMS always works.
So I posted this on the Paranoid Android thread, and I think that was the wrong place to post since I have no eliminated it as a ROM issue. Here is what has happened:
This is the reason I am posting here: today my text messaging has gone goofy. When I send a text message in the default, stock, PA AOSP app, the message says "sending" under it for a little while, then it says the "failed to send message" with the little red triangle on it. Meanwhile, the recipient has gotten 4 copies of the text. Yes, four. It has happened to literally everyone I have sent texts to today: iPhones, Droids, feature phones. I have clean installed the ROM and GApps 3 times today and it still happens. I wiped my internal and SD card from TWRP (got into a little issue there, had to figure out adb sideload, but we are all good now). Checked the MD5's before I installed. It's still happening. Other people with Verizon in the area that I know don't have this issue. Also, this was my 3rd day since installing the ROM, and it didn't happen the first two days, only today. Bottom line, I have no idea what's going on, and I need some help to fix it.
Update on the texting issue: I called VZW and went through their steps, and they said its almost certainly a device issue, and not a network issue. She said that my phone is having trouble contacting the SMS switch, and so it keeps trying to send the message, but it never hears back so then it reports that it can't be sent. The lady I spoke with did file a ticket for a "Network Technician" to take a look at the issue, but that will probably take at least 72 hours. I really hope this is either an issue with the ROM or with the network, because I really don't want to have to go through the process of unrooting and returning to complete stock to get one of vzw's crappy "like new replacements"
Update 2: Restores some of my backups from previous ROMs, including an AOKP 4.2.2 Milestone and an CleanROM VZW SE and the text messaging is still messed up. That pretty much eliminates the chance that its a PA issue, and it is most definitely either a device issue, or a Verizon Network issue. Cross your fingers that its a network issue so I don't have to go through the mess of returning to stock and all that.
Any possible fixes that you guys can think of?
Indeed its a device problem. I've got the reverse issue! I keep receiving the same copies of one message about 10 to 15 times a day. Due to this, the latest message from the respective recipient delays to the next day! I do have tried third party apps but still it doesn't work out... Need help!??
Sent from my A2 using Tapatalk 2