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
Related
i rooted my HTC TB. now the phone indicates i have two sms/mms messages. trouble is i dont see that i have any messages. i checked the various folders where they might possibly be, i powered on/off, powered down and removed battery and sim, and still the message bubbles indicate two messages.
any thoughts?
thanks
mark
That happened to me even before I rooted. It still happens sometimes, but eventually goes away on its own. You still having a problem?
issue resolved, i received some text messages today. deleted them and now everything is as it should be. kind of weird.
thinking about it... i did have a few unread t-messages prior to rooting. thinking somehow that was preserved in memory.
markkal123 said:
issue resolved, i received some text messages today. deleted them and now everything is as it should be. kind of weird.
thinking about it... i did have a few unread t-messages prior to rooting. thinking somehow that was preserved in memory.
Click to expand...
Click to collapse
VZW and HTC are releasing an update that helps fix an issue like this (As well as GPS, etc). Currently, sometimes the messages are improperly stored in the Messaging application, causing problems like this.
The rollout for this update started yesterday.
I'm having a problem that has me stumped.
YouTube
Earlier in the week, I noticed that I was unable to stream YouTube videos over mobile data. I could launch YouTube and it would bring up the top videos. I could search and it would get me results. I could not however get anything to actually play, when I choose a video it will just sit at the loading screen, and my bars will turn grey. I will not get a mobile data connection back until I back out of Youtube. I confirmed this issue with several different videos while in different parts of the state, so it isn't limited to a certain video or tower.
Google Talk
If I am at the main screen that shows who is online/offline, usually this will display properly. However as soon as I pick a name and go to send a message, my bars will turn grey and I will lose my data connection. It will not come back until I back out of Talk. Sometimes after this happens I can reopen talk and it will sit at the main screen for a while, get mobile data back, and display who is online and who is not. Most of the time, Talk will not work again until I force close it.
Edit: Talk will not disconnect until I actually send a message. The message makes it through most of the time, but then I lose mobile data. This results in Talk saying "Lost connection to Server. Messages will be sent when online."
I am on CM7 Nightly 20 with the stock CM7 kernel since the day Nightly 20 was released. Just to be safe, I did a full wipe in Fastboot erasing the following partitions before re-flashing: userdata, cache, webtop, system, boot.
I am unsure when this problem started. I know that YouTube worked last weeks, but when I think back, I can't remember the last time Google Talk worked while I was on mobile data. Note though, that while on Wifi everything works just fine.
I'm at wit's end here. I'm going to wipe the phone again and install stable Ba2tF and just Google Apps, and see what happens (after I flashed Nightly 20 earlier today I had the Market start spam reinstalling my apps before testing Google Talk - though I did get to test it and have it lose data after just a few apps were installed).
I'm on 30P for the radio, AT&T, Western Massachusetts, any help would be greatly appreciated!!!
I was going to post the same exact problem. The problem only appears over cellular. Over WiFi, everything works fine. Also, I just reflashed stock and it works. So it would seem to be a problem with CM7 and/or AT&T.
I'm going to get a good logcat of what's going on after I narrow it down a bit more... my current log is 1MB, which as about 2 minutes of info. I'm going to try to narrow it down to just the few seconds from when I hit "send" to when I get disconnected.
Hopefully at that point someone smarter than I can figure out what's going on.
DK
DeathKoil said:
I'm going to get a good logcat of what's going on after I narrow it down a bit more... my current log is 1MB, which as about 2 minutes of info. I'm going to try to narrow it down to just the few seconds from when I hit "send" to when I get disconnected.
Hopefully at that point someone smarter than I can figure out what's going on.
DK
Click to expand...
Click to collapse
Just thought I'd chime in and give some feedback. Tested this out on Weekly #2 both with wi-fi and regular data and everything was working as it should. I've been through a few different versions of CM7 and have not run into this.
Have you been using the same gtalk .zip each time? Maybe try re-downloading it along with your fresh install? Also, have you re-flashed your radio?
And here is a logcat capture. I force closed Talk, started the capture, launched talk, connected, pressed on my roommate's name, and lost my connection. The part that says "<SNIP>" is where my email address was.
I'm going to upload it here, then start to go over it myself.
DK
ghost_og said:
Have you been using the same gtalk .zip each time? Maybe try re-downloading it along with your fresh install? Also, have you re-flashed your radio?
Click to expand...
Click to collapse
Yeah, the GAPPS package ROM Manager lists as newest is still 20110828, which is also listed as newest on the Cyanogen Wiki. I never re-downloaded it, I've always used the same .zip everytime I've needed it... which is since Pre-Beta1.
I didn't flash my radio up to 36P when it came out since some people reported issues with it, and 30P had been working fine for me since June/July.
I am going to try to re-flash Google Apps now, this time without using the new version of talk that supports the front facing camera... since I never used the functionality anyway. I will report back in a few minutes.
DK
I tried reflashing both AT&T radios and both versions of Talk (w/ and w/o video chat).
For me, I get disconnected as soon as I open Talk. Happens every time. I froze Talk and I was disconnected when I got a Gmail notification. Maybe it was a coincidence but either way I was disconnected so the problem isn't limited to Talk. Maybe it's a problem with the Google Services Framework.
Here is what I think is a better logcat of what happens. This time, I setup CM7 to have long press back kill the currently active process, so that I could kill Talk right away.
I started the logcat from killing Talk and hitting the home button while it was restarted. I sent one message that said "Son" to my roommate, and lost my data connection. I then waited 20-30 seconds, killed Talk, it restarted, I got data back, I sent another message to my roommate that said "disconnect", and I lost my data again.
NOTE: This is with the Talk from the newest GAPPS (fresh download with ROM Manager), but not the one with the camera support (camera crap was cluttering the logcat anyway).
Anyone who is smarter than I able to see what's going on here?
DK
Same problem with CM7 Beta so I'm guessing there's some problem between CM7 and AT&T. I'm on AT&T in NYC.
I have a list of ROMs this does NOT happen on. I went back and restored to several points trying to figure out exactly where the problem started, and while I didn't find that, I do have a list that it does and does not happen to.
Talk Works on:
Prebeta2
Prebeta3
Prebeta4
Stopgap
Ba2tF
Weekly1
Nightly8 (likely it works on Nightlies 1-8, I just never made a backup after that and went right to 20 so I dont know exactly where the issue started with nightlies)
Talk does NOT work in:
Weekly3
Nightly20
So at some point between Nightly9 and Nightly20 (which includes the commits for Weekly3), something happened with Talk that is causing it to drop your data connection when you send message or refresh the friend list.
If any Dev happen to stumble upon this thread, I did take a logcat dump and linked it above as a txt file called "betterlog.txt" which clearly shows two disconnects while using Talk without having a lot of other "noise" in the logs from other things happening on the phone.
DK
Same problem, only I have this in Ba2tF. Odd thing is, I was running Ba2tf for some time, then all of a sudden this issue just appeared. I couldn't get it to clear, even after wiping data, caches, re-flashing etc...
Looks like this is nothing new. Check out CyanogenMod issue 3557.
---------- Post added at 02:52 AM ---------- Previous post was at 02:38 AM ----------
Same problem in Ba2tF. I was running Ba2tF for several weeks, then this problem just popped up. Couldn't get it to clear.
Looks like an old CyanogenMod issue. Issue #3557.
I don't know if it's AT&T that changed or CM7 but the problem's gone since I started using weekly #4.
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.
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.
Hey folks. So I finally took the leap to root and flash a custom rom (Lineage 16.0). I started on VS996 and had to cross-flash to US998 with the Frankenstein method. From there, I installed TWRP and rooted. Upgraded to US99820h before jumping to Lineage and even ran with it for a bit. Everything was going very well. I got through the set up, logged in to Google and started getting things synced, but soon discovered that my cellular abilities are dead. I have no ability to send or receive calls or texts from within the rom, but have a signal and curiously even internet over mobile data. The real problem is that it's not just limited to Lineage.
I reflashed the stock image and tried a new version of Lineage first. Same issue. Then I tried AOSiP. No luck. Here, the research I was doing was getting me worried that maybe my SIM died somewhere in this process. I tried out an old AT&T prepaid one, but it gave me no service whatsoever, not even the normal bars I had with the other SIM. I decided to go back to US99820h to see if I could still get texts on stock firmware. I could! It was good to feel connected and catch up on my texts from the past day. But this is far from over.
I did more research online, looking into ways to check on my APN settings. Compared to various sources online, they all seem good. I tried to add another APN, but have had no luck with that. I tried Havok out too. I really don't know what else I can do. Am I just doomed to live in the stone ages of Android 8? I can't really afford to give up telephony. I know there are other people here that came from VS996 too and seem to be running well. Or at least I think so. Is there something else that I can try? Any fixes or convoluted steps that I can take to get past this?
Any help, ideas, support, encouragement, or points in a good direction would be deeply appreciated.
This is a common issue. There is currently a small group trying to figure out how to get Sprint/Verizon services to work without any issue on AOSP/custom ROMs. I'm anticipating a release sometime as well, but it's been quite a while.
Until then, if you have a copy of Tasker installed, you can run a custom script to make a phone call to voicemail upon boot to "activate" service, then end the task 7-8 seconds in. However if your phone dozes then you may lose push notifications until you open your phone or messaging apps again.
TheCoryGuy said:
This is a common issue. There is currently a small group trying to figure out how to get Sprint/Verizon services to work without any issue on AOSP/custom ROMs. I'm anticipating a release sometime as well, but it's been quite a while.
Until then, if you have a copy of Tasker installed, you can run a custom script to make a phone call to voicemail upon boot to "activate" service, then end the task 7-8 seconds in. However if your phone dozes then you may lose push notifications until you open your phone or messaging apps again.
Click to expand...
Click to collapse
Hey, thanks for the idea! I've not had time to try that until this weekend, but it seems that it's not going to be an option. Unfortunately every time I try to make a call, my phone freezes and I have to reboot. I don't know what to do from here.
UPDATE: Flashed the newest version of Lineage (the 06/10 build) and the voicemail thing works! We're up and running for now.