Since December 6th, I've had occasional difficulty receiving text messages in a timely manner. Believing it to be caused by an outdated CM10 nightly, I downloaded the latest (at the time December 10) and did a factory reset. Since then, the issue has been largely non-existant. However, today, I experience it.
I decided to do a little digging. Using an XML backup of my SMS messages, I decided to see how many messages have been delivered over an hour after they were sent. In the six months of SMS history, there've been only 30 messages delivered over an hour after they were sent, all after December 6th. On average, these messages are arriving 3.7 hours late, and only after I send a message first. (For example, I pick up my phone, send a message, and suddenly receive several messages.)
I've run my current build of CM10 for almost a week, and have only had noticeable issues today. (Keep in mind this issue doesn't seem to occur if I send texts on a regular basis.)
Anyone have an idea why this might be happening? Could this be caused by my ROM, and if so, should I try switching to another?
Have you tried a different radio?
dstaley said:
Since December 6th, I've had occasional difficulty receiving text messages in a timely manner. Believing it to be caused by an outdated CM10 nightly, I downloaded the latest (at the time December 10) and did a factory reset. Since then, the issue has been largely non-existant. However, today, I experience it.
I decided to do a little digging. Using an XML backup of my SMS messages, I decided to see how many messages have been delivered over an hour after they were sent. In the six months of SMS history, there've been only 30 messages delivered over an hour after they were sent, all after December 6th. On average, these messages are arriving 3.7 hours late, and only after I send a message first. (For example, I pick up my phone, send a message, and suddenly receive several messages.)
I've run my current build of CM10 for almost a week, and have only had noticeable issues today. (Keep in mind this issue doesn't seem to occur if I send texts on a regular basis.)
Anyone have an idea why this might be happening? Could this be caused by my ROM, and if so, should I try switching to another?
Click to expand...
Click to collapse
I'm stock rooted but you're not the only one having this issue. I was actually locked too when this was happening as well. The messages take a long time to arrive and when they do, they come in droves.
However, it doesn't happen to every person I know texting me. On Att as well.
Sent from my HTC One X using xda app-developers app
Genetic517 said:
Have you tried a different radio?
Click to expand...
Click to collapse
CM10 bundles the radios into the .zip, thus making it more difficult to flash radios. I'm running the only AT&T radio, but I might try flashing one of the few CM10 compatible radios tomorrow and see how much luck I get with it.
ToxicWaste said:
I'm stock rooted but you're not the only one having this issue. I was actually locked too when this was happening as well. The messages take a long time to arrive and when they do, they come in droves.
However, it doesn't happen to every person I know texting me. On Att as well.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I've been able to determine that, after an indeterminate amount of inactivity, the phone won't receive *any* text messages sent to it until you send one out. Today, happened after just thirty minutes in my pocket. Pulled it out, sent one, and then received five. Is your phone receiving them on its own, or are you only getting them after you've sent a message?
dstaley said:
CM10 bundles the radios into the .zip, thus making it more difficult to flash radios. I'm running the only AT&T radio, but I might try flashing one of the few CM10 compatible radios tomorrow and see how much luck I get with it.
I've been able to determine that, after an indeterminate amount of inactivity, the phone won't receive *any* text messages sent to it until you send one out. Today, happened after just thirty minutes in my pocket. Pulled it out, sent one, and then received five. Is your phone receiving them on its own, or are you only getting them after you've sent a message?
Click to expand...
Click to collapse
Now that you mention it, if I send a text, then I get everyone else's late and in bundles. However, I've had it be jus a couple people but mostly from just one person. That person also has a completely stock HOX. Mins was doing it too when it was completely stock.
from my HTC One X using xda app-developers app
Your post came through without any text from you btw
I've noticed the exact same prob on my phone as well. I'm running Nocturnal's Dirty Rom 2.3c hmmm interesting issue luckily it hasn't been a huge prob to me, yet.
WeWearFedoras said:
I've noticed the exact same prob on my phone as well. I'm running Nocturnal's Dirty Rom 2.3c hmmm interesting issue luckily it hasn't been a huge prob to me, yet.
Click to expand...
Click to collapse
What radio and carrier are you on?
It doesnt seem like this has been solved yet and I have been getting this issue,too! has anybody been able to fix this issue?
dstaley said:
CM10 bundles the radios into the .zip, thus making it more difficult to flash radios.
Click to expand...
Click to collapse
This I'm afraid is incorrect, if ROMs contained radio images then there would be quite a few more bricks.
They don't include them for this reason
The reason why you can't flash certain radios because the ones in the dev section include the ril. And because the sense ril is much different from a aosp one it causes issues when you flash a radio. Hense why there are separate versions for those who are running a aosp ROM
Sent from my One X using Tapatalk 2
superchilpil said:
This I'm afraid is incorrect, if ROMs contained radio images then there would be quite a few more bricks.
They don't include them for this reason
The reason why you can't flash certain radios because the ones in the dev section include the ril. And because the sense ril is much different from a aosp one it causes issues when you flash a radio. Hense why there are separate versions for those who are running a aosp ROM
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
h8rift said:
Yes, radio firmware currently is being set to 1.85 on boot.
Now, for those who are upset, and want 2.20.....note that I am right now working on updating our prop libs so it will be 'updated' to 2.20 att release radio. On boot, the radio firmware is updated to what the ROM has in it, for those curious about why it seems the flashable radios are not 'taking effect'. This will help reduce radio firmware outliers and keep the rom all together on the same versions of software.
Click to expand...
Click to collapse
CM10 bundles the radio into the .zip so that everyone is using the same, as there are like 17 variants of radios for the Evita. It loads it on boot from a location (/system/etc/firmware) different than the normal radio.img flashes, which is why even when you flash them, the ROM uses the bundled one.
This has been happening to me as well since about Dec 6 as mentioned in OP. I am rooted various roms, Original and Sense ICS or JB. Now I think this is an ATT issue. My other line on my account also a HTC OneX Virgin (Stock, NOT rooted, 2.20) used by a friend has the same problems. Sometimes its 20min late up to hours late. We both have issues where texts when they do finally come through like one other mentioned you get all at once. Time Received will show something like 8:00pm, sent 6:00pm...
jatipton said:
This has been happening to me as well since about Dec 6 as mentioned in OP. I am rooted various roms, Original and Sense ICS or JB. Now I think this is an ATT issue. My other line on my account also a HTC OneX Virgin (Stock, NOT rooted, 2.20) used by a friend has the same problems. Sometimes its 20min late up to hours late. We both have issues where texts when they do finally come through like one other mentioned you get all at once. Time Received will show something like 8:00pm, sent 6:00pm...
Click to expand...
Click to collapse
I agree with you 100%. I was posting here weeks ago when the OP created the thread. I was bone stock then and it was happening. Happening rooted with different Roms too. It has been happening to my brother and his wife with S3s and my fiance and I on HOXs. We are all on ATT.
I think ATT is putzing with something but unrelated to phones on Roms. Been happening for a while now. In fact, has anyone else just had LTE implemented? Went up here just over a month ago and seems ever since my texts aren't getting to people fast enough and vice versa.
ATT HOX Premium App--Stock is fine but modded is Creative
I find this happens on mine at times when I'm in a poor lte signal area.
I send a message to myself once a day to flush system an I see it at these times, if I turn lte off and go hspa they come through fast.
I don't think lte is culprit I believe its in the carriers hand off between lte hspa imo.
WR
Sent from my HTC One XL using xda app-developers app
IV had this issue and I have a temporary fix for it. I say temporary because if u turn your phone off you'll have to do it again. I had this issue for the longest with my one x I hope this works for you type this in your dialer *#*#4636#*#*. Once done goto phone information. Then scroll till u see something above turn off radio. It should say something like lte wdcma prl gsm... What u have to do is change it I use the PRL one... I hope this works
Sent from my HTC One XL using xda app-developers app
This often happens to me when I switch from a aosp rom to a sense rom. I often just wipe cache and than toggle airplane mode and all my messages catch up with everything.
Sent from my HTC One XL
Related
Sometimes when I click on "Messages" and then click on a thread I wish to view a totally different thread gets opened. I know it's not my finger because the thread that would open is oftentimes nowhere close to the one I clicked on. Several times I've inadvertently sent an SMS to the wrong recipient, which resulted in several comical situations.
Has anyone experienced this issue? I've tried to search the forum but didn't come up with anything.
My Bolt is rooted, running the leaked MR1 RUU
That happens to me constantly
Both pre and post ota update
Also post ota my messages app has been way slower and forces closes on a regular basis
Tho I'm stock and not rooted (don't flame me)
1st post
Sent from my ADR6400L
happens to me also and I am on stock....smh at this half ass phone verizon is selling to people I wish I was getting all these problems before the 14 days.
mbrown3460 said:
happens to me also and I am on stock....smh at this half ass phone verizon is selling to people I wish I was getting all these problems before the 14 days.
Click to expand...
Click to collapse
Calm yourself, this isn't Verizon fault it's googles. This happens on every android phone
Sent from my ADR6400L using XDA Premium App
anyone have a workaround? and different apps work?
odesskiy said:
Sometimes when I click on "Messages" and then click on a thread I wish to view a totally different thread gets opened. I know it's not my finger because the thread that would open is oftentimes nowhere close to the one I clicked on. Several times I've inadvertently sent an SMS to the wrong recipient, which resulted in several comical situations.
Has anyone experienced this issue? I've tried to search the forum but didn't come up with anything.
My Bolt is rooted, running the leaked MR1 RUU
Click to expand...
Click to collapse
joshnichols189 said:
Calm yourself, this isn't Verizon fault it's googles. This happens on every android phone
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
This is a Froyo (and maybe before) issue and not an issue on "every android phone". Once you upgrade to a custom Gingerbread Rom or the official Gingerbread update (as of today this isn't out yet) you will see this problem go away.
It seems to be a problem with all android phones no matter the rom. It did it on my rooted Droid 1 also. Go sms pro is a good replacement for stock. Rooted or not it fixes the problem and has a lot more options.
Sent from my rooted Thunderbolt!
Roger that, I have the same issue. Also, I moved to the T-bolt from an Evo and the Evo with Froyo had the same problem. As soon as I installed CM7 on the Evo, the problem was gone.
I'd say try using GO SMS Pro. Much better than the stock messaging application.
Hey guys, I've had my HTC One S for T-Mobile and ive had it for about 1 week and it has rebooted on me twice so far. not sure why. the first time it was in my pocket and i heard the T-Mobile boot up animation sound go off in my pocket and pulled it out my phone to see it was just booting up for some reason. then today i was going to look at my friendstream widget (on my home screen) and my phone locked up for a second and then rebooted itself. i'm not happy about it since i once owned a g2x which rebooted like crazy. i'm hoping it stops randomly doing this crap but i reported it to HTC since it gave me the option once it rebooted. my HTC one s is rooted with the stock rom with bloatware removed and carry IQ removed. i just wanted to see if i'm the only one having this issue.
It happens to me too :/ sometimes i wake up in the morning and i see the HTC error message. Maybe a software issue?
coronangel said:
It happens to me too :/ sometimes i wake up in the morning and i see the HTC error message. Maybe a software issue?
Click to expand...
Click to collapse
not sure why it does this. i just wanted to make sure i wasnt the only one having this issue. but i do hope its a software issue. i keep reporting it to htc when it ask me to send them the error or whatever it says. maybe htc will fix it
I had like two reboots, but then I updated the phone and the problems disappeared. Have you updated to the latest firmware ?
Sent from my HTC One S using XDA
Habarug said:
I had like two reboots, but then I updated the phone and the problems disappeared. Have you updated to the latest firmware ?
Sent from my HTC One S using XDA
Click to expand...
Click to collapse
i dont think there is an update for the tmobile htc one s.
Two days since I bought it and already rebooted two times when exiting the mail client while network was switching from H to 3G. I upgraded it to the latest firmware OTA just after putting the SIM card into.
My son had a problem with random reboots. After enabling Best Wifi Performance in Wifi, advanced settings, they went away. This is on a TMOUS version. Could be totally unrelated to your issue, but worth a try. I've noticed that the wifi has some weirdness to it, like hanging on to a connection long after it's out of range. I hope there is a software update soon.
Sent from my HTC VLE_U
well i hope htc can fix this issue. it hasnt happened again yet. i also have the tmobile htc one s.
s10shane said:
i dont think there is an update for the tmobile htc one s.
Click to expand...
Click to collapse
I don't have tmob version and mine is on 1.78. It was that update which fixed it, it seems. You did an update search right?
Sent from my HTC One S using XDA
Habarug said:
I don't have tmob version and mine is on 1.78. It was that update which fixed it, it seems. You did an update search right?
Sent from my HTC One S using XDA
Click to expand...
Click to collapse
Mine is also on 1.78 but had 2 reboots.
Habarug said:
I don't have tmob version and mine is on 1.78. It was that update which fixed it, it seems. You did an update search right?
Sent from my HTC One S using XDA
Click to expand...
Click to collapse
yeah i guess here in the US we havent got an ota update that i know of. i kept checking for updates but it said my one s is up to date.
Another reboot this morning. This time I received a txt thru Facebook Messenger. I saw it on my desktop and ear, exactly at the same time, the HTC One S rebooting. This might be app related this time.
My One S specs:
- EU edition
- Stock ROM, 1.78 OTA
- Wifi disabled
Yes my H1S reboots about 3 times a week, or the "Loading ..." window is seens 3 or 4 times a week as well.
one more time... I'm gonna consider switching to another ROM in a very near future.
rebooting on 1.78 stock and other custom roms too
Hi guys, I had this issue with stock rom on 1.78 and previous too, so it is probably a radio issue. If I am connected to my wifi network at home, then I go out, the phone switches to hsdpa (as it should) and then I come back home,the reconnection to the wifi network causes the phone to reboot.
I had this issue on all roms I used, both stock and trickdroid 3.1 / 4.3.
My wifi direct is already disabled, my location is Italy. I have seen also that people on the US T-mobile support webpage are complaining about something very similar, wifi related.
Thanks
I'm on tmous and have had two of these reboots since I got the phone on US release day.
As others have said, mine have only happened when I'm on the very edge of my WiFi coverage. It's like the phone can't decide which network to grab on to and freaks out. I don't have the issue when it's just normally switching from WiFi to data like when I go out and then come home. It only seems to happen when I'm right on the edge of WiFi for a few minutes.
Not a huge deal, since its only happened a couple of times. If I remember when I'm off this week, i'll try to get a logcat because I should be able to reproduce it at the edge of my back yard
that would be great, as it sounds like it is the same issue. I always found tricky to save logcats due to amount of information in them and spotting the exact reason for crashing.
I was just curious if anyone, other than myself, is having mobile network issues with there one x still even on the newest radio and software?
The issue I am talking about is when you go to use your phone and you pick it up and it has no service at all with a X on the signal bars until you turn it on and off again or in some instances you have signal bars but you can't make a call, send or receive a message, or surf the web until once again you reboot the phone or swap it in and out of airplane mode.
I was just curious if anyone has a solution for this or ideas... ironically when I updated to 1.85 it was fine for an entire day then the next day I rooted and installed a different ROM and the issue came back. Could be timing or not related but I have no idea.
Thoughts?
- Dan
Happens all the time on 1.73. I've held off upgrading because I've heard of people having fun (and by fun, I mean lotsaproblems) on 1.85.
AEDan1977 said:
I was just curious if anyone, other than myself, is having mobile network issues with there one x still even on the newest radio and software?
The issue I am talking about is when you go to use your phone and you pick it up and it has no service at all with a X on the signal bars until you turn it on and off again or in some instances you have signal bars but you can't make a call, send or receive a message, or surf the web until once again you reboot the phone or swap it in and out of airplane mode.
I was just curious if anyone has a solution for this or ideas... ironically when I updated to 1.85 it was fine for an entire day then the next day I rooted and installed a different ROM and the issue came back. Could be timing or not related but I have no idea.
Thoughts?
- Dan
Click to expand...
Click to collapse
Ditto, i got a new Sim card and thought that fixed it, i was wrong (1.73)
Xodium said:
Happens all the time on 1.73. I've held off upgrading because I've heard of people having fun (and by fun, I mean lotsaproblems) on 1.85.
Click to expand...
Click to collapse
Same here. Still on stock as well. Especially since I'm not experiencing any major issues with the phone.
Lilshaun said:
Same here. Still on stock as well. Especially since I'm not experiencing any major issues with the phone.
Click to expand...
Click to collapse
Only thing thats really starting to frustrate me are all the double texts/retry sending notifications.
I have had a problem where the phone thinks it has signal, data works fine but you cannot make calls or send texts until you reboot or go into airplane mode.
This happened on 1.73, 1.82 and now 1.85
Sent from my iPad using Tapatalk HD
It has happened to me on all versions. I was told I could exchange mine, but they have none in stock. Another pain in the butt is that I'm not receiving text messages at times. Really becoming a nuisance.
Sent from my HTC One X using Tapatalk 2
Happens rarely but all I do is toggle airplane mode and its fixed. Takes like 5 seconds. No biggie.
Sent from my HTC One X using Tapatalk 2
mobilehavoc said:
Happens rarely but all I do is toggle airplane mode and its fixed. Takes like 5 seconds. No biggie.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Same, just started today after I rooted. meh
Badger2point0 said:
Same, just started today after I rooted. meh
Click to expand...
Click to collapse
I believe mine started after I rooted as well... I wonder if the root is doing something that interferes with the radio working correctly or something along those lines.
Its the main reason I updated. Even when going from HSPA+ to LTE I would have to reboot the phone while stock. 1.82 did nothing to fix the issue but since I've been on 1.85 I've not experienced the problem. Multitasking is, imo, unchanged.
Yeah. Happens regularly when I am travelling some distance by car and occasionally in the city (maybe every two days while I remain in the city). I'm on rooted stock but it was happening even with un-rooted stock. I hope HTC fixes this soon and Rogers pushes out an OTA update as this is sh*tty. Funnily enough, going into airplane mode doesn't seem to fix the issue. Apps that access the Internet just report an error with the network connection.
davep1982 said:
Its the main reason I updated. Even when going from HSPA+ to LTE I would have to reboot the phone while stock. 1.82 did nothing to fix the issue but since I've been on 1.85 I've not experienced the problem. Multitasking is, imo, unchanged.
Click to expand...
Click to collapse
Same, I haven't experienced the issue on 1.85.
Hi. I was using my Sensation last night, went to bed and woke up the next day only to find that my 4G connection wasn't working! The signal bars were white and the icon (currently an H) is flashing. What does this mean? How can I fix it? I can only use Wifi at the moment, and I DO NOT pay an extra $10/mo to deal with this! How can I fix this? I've checked my data settings, rebooted my phone, scanned fir viruses, but can't figure it out!
Sent from my HTC Sensation using XDA
611
I don't follow you.
ClipTy said:
I don't follow you.
Click to expand...
Click to collapse
They are referring to the number you call for T-Mobile US costumer service.
At my house edge goes is and out..flashing E.. tmo must either know or are working on it
mulletcutter said:
At my house edge goes is and out..flashing E.. tmo must either know or are working on it
Click to expand...
Click to collapse
this happened to me the other day, even in 3G/4G mode my data would never connect and E would just keep flashing over and over again (in like 10 sec. intervals) thought it was a ROM problem so I restored a backup and sure enough, the problem was still happening. I could still make calls and send texts fine tho. its not happening to me anymore, but I found it weird. could it possibly be T-Mobile messing with their towers or something in preparation for LTE?
Well, I'm not sure what caused this very same issue for me a couple days ago. I can say that it ONLY effected my AOSP (CM9) rom, but my Sense rom was unphased. It seems to be a common recent complaint in the OpenSensation thread...
I've since then done a fresh install of CM9 RC1 with the addition of Tamcore's kernel. Although I'm not experiencing the described symptom any longer, I can say that my data speeds are far from exceptional. I'm not sure what is going on, but it does seem to be carrier related.
I experienced the same 1 day after flashing CM9 RC1. I re-flashed the Virtuous Inq. ROM I was using previously and the problem went away
My phone went back to normal later on. I think you were right mulletcutter, they might have been servicing it.
Sent from my HTC Sensation using xda app-developers app
Same data connectivity issue
I have two sensations, both shows similar data connectivity issue on TMobile. Data signal jump to connected and not connected for couple hours, and eventually problem will go away. I have both phones rooted running either CM9 or Kang. So far I have tried couple following things but no solutions. I believe its HTC Sensation hardware issue:
1. Flickering so far seen usually after night long charge in the morning. It will last couple hours, some time days.
2. Changing/reflashing ROMs did not help at all and saw same issue continued.
3. One of my friend has Sensation and he also has seen same issue.
4. Some time going into Phone application(Dialer) and then Settings/Advance settings and come back without doing anything helps but not always.
Please post here is you have temporary/permanent solution or even know the root cause of this data connectivity issue.
Also thinking to call Tmobile to get some kind of help but not expecting much as I bought phones more than year ago but less than 2 years. I don't want to give any more commitment/agreement with Tmobile as planning to move to value plans to save some money. If Tmobile does not help, thinking to try American Express to conver it under extentended warranty as I paid by AMEX credit card.
Thanks
Have you tried the application get ril? I was having some issues myself, I'm also T-Mobile. I tried get ril and found out my radio and ril we're not matching. The application suggested a ril for download and once I did that I went from one bar of connection to five bars of connection on H. It made a big difference for me. Perhaps it could also help you? You can download get ril from the market. It sure won't hurt to try. Best of luck.
Sent from my HTC Sensation using xda premium
Its a defect in the basic aosp framework. There is nothing you can do to fix it. There is also nothing your usage did to start it.
The good news is that it should disappear on its on after a few hours.
Check my threads started history. You will find a thread near the top of that list showing almost all there is to know about this issue. I think my thread might be linked in the first 2 posts of the cm10 faq thread too.
Sent from my HTC Sensation using xda app-developers app
Hello Internet, I just thought I'd chime in on the sms issue many seem to be having.
For me it started in the morning on the 21st. The day before everything was peachy. That morning I woke up and sent my normal texts that I usually do. The first text sent fine like usual, but anything after would fail to send. One quick-fix I found was to toggle airplane mode before sending a message, which would allow me to send another text or two before failing. The most interesting thing about this issue is that my brother, who is on cm 10.2 started having the issue at the exact same time and we aren't even running the same versions of android.
So I called verizon today and after about a half our I was able to get some information. I told the guy that I had tried rebooting, clearing cache, factory reseting, updating my SMSC number, etc. He said it's probably an issue in their end, which makes sense due to the timing of the issue occurring. He said he would do some behind the scenes stuff and call me back on Monday. I guess we'll see if the issue gets resolved. Keep me posted if you find a solution.
AnTiDoWn3r said:
Hello Internet, I just thought I'd chime in on the sms issue many seem to be having.
For me it started in the morning on the 21st. The day before everything was peachy. That morning I woke up and sent my normal texts that I usually do. The first text sent fine like usual, but anything after would fail to send. One quick-fix I found was to toggle airplane mode before sending a message, which would allow me to send another text or two before failing. The most interesting thing about this issue is that my brother, who is on cm 10.2 started having the issue at the exact same time and we aren't even running the same versions of android.
So I called verizon today and after about a half our I was able to get some information. I told the guy that I had tried rebooting, clearing cache, factory reseting, updating my SCSC number, etc. He said it's probably an issue in their end, which makes sense due to the timing of the issue occurring. He said he would do some behind the scenes stuff and call me back on Monday. I guess we'll see if the issue gets resolved. Keep me posted if you find a solution.
Click to expand...
Click to collapse
Not sure if I'm doing this right usually I use the app but since I can only text on touch wiz based Roms xda app keeps crashing. Anyway I have this issue too mine seems to have started on 2-20 but same thing reboot or toggle airplane mode and I can send one that's it till next reboot. Was running carbon kit Kat. Hopefully Odin tomorrow will fix it touch wiz sucks!
tonybahr said:
Not sure if I'm doing this right usually I use the app but since I can only text on touch wiz based Roms xda app keeps crashing. Anyway I have this issue too mine seems to have started on 2-20 but same thing reboot or toggle airplane mode and I can send one that's it till next reboot. Was running carbon kit Kat. Hopefully Odin tomorrow will fix it touch wiz sucks!
Click to expand...
Click to collapse
Odin does not fix...
Sent from my SCH-I535 using Tapatalk
Dex954 said:
Odin does not fix...
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Yeah I figured that out.
Having the same problem....just wondering if anyone tried unrooting and rerooting?
mamill66 said:
Having the same problem....just wondering if anyone tried unrooting and rerooting?
Click to expand...
Click to collapse
Yes doesn't fix anything.
Sent from my SCH-I535 using Tapatalk
Just kinda bumping to see if anyone found anything?
Sent from my SCH-I535 using Tapatalk
I talked to Verizon again yesterday night, my support ticket is still open, meaning they're looking into the possibility of it being an issue on their end, so nothing new. I'm convinced it's something with them, because of the timing. I'll keep you posted.
Sent from my SCH-I535
AnTiDoWn3r said:
I talked to Verizon again yesterday night, my support ticket is still open, meaning they're looking into the possibility of it being an issue on their end, so nothing new. I'm convinced it's something with them, because of the timing. I'll keep you posted.
Sent from my SCH-I535
Click to expand...
Click to collapse
Do they know you are running a form of CM? Or are you just saying your texts aren't working?
Just for my own info?
AnTiDoWn3r said:
Hello Internet, I just thought I'd chime in on the sms issue many seem to be having.
For me it started in the morning on the 21st. The day before everything was peachy. That morning I woke up and sent my normal texts that I usually do. The first text sent fine like usual, but anything after would fail to send. One quick-fix I found was to toggle airplane mode before sending a message, which would allow me to send another text or two before failing. The most interesting thing about this issue is that my brother, who is on cm 10.2 started having the issue at the exact same time and we aren't even running the same versions of android.
So I called verizon today and after about a half our I was able to get some information. I told the guy that I had tried rebooting, clearing cache, factory reseting, updating my SMSC number, etc. He said it's probably an issue in their end, which makes sense due to the timing of the issue occurring. He said he would do some behind the scenes stuff and call me back on Monday. I guess we'll see if the issue gets resolved. Keep me posted if you find a solution.
Click to expand...
Click to collapse
I'm having the same issue that you are. I've already posted a thread. http://forum.xda-developers.com/showthread.php?t=2657822
Are you on a version of CM? I was on mastamoon's 10.2 and moved to his CM11 and still have the problem. The only other fix I have heard/seen is that you can turn your mobile network to just CDMA and the problem goes away. (Its slow, but it works).
You are from Hershey Pa. I am in the Wilkes/Barre Scranton area. Anyone else experiencing this problem and in this area?
Do you have voice+ or google voice in your app drawer? I've seen some people who have had it in their app drawer who have been able to open that and select disable which remedies the problem. Hopefully Verizon gets back to you.
Whisk_33 said:
I'm having the same issue that you are. I've already posted a thread. http://forum.xda-developers.com/showthread.php?t=2657822
Are you on a version of CM? I was on mastamoon's 10.2 and moved to his CM11 and still have the problem. The only other fix I have heard/seen is that you can turn your mobile network to just CDMA and the problem goes away. (Its slow, but it works).
You are from Hershey Pa. I am in the Wilkes/Barre Scranton area. Anyone else experiencing this problem and in this area?
Do you have voice+ or google voice in your app drawer? I've seen some people who have had it in their app drawer who have been able to open that and select disable which remedies the problem. Hopefully Verizon gets back to you.
Click to expand...
Click to collapse
I'm in Hershey pa as well... interesting
Sent from my SCH-I535 using Tapatalk
Whisk_33 said:
I'm having the same issue that you are. I've already posted a thread. http://forum.xda-developers.com/showthread.php?t=2657822
Are you on a version of CM? I was on mastamoon's 10.2 and moved to his CM11 and still have the problem. The only other fix I have heard/seen is that you can turn your mobile network to just CDMA and the problem goes away. (Its slow, but it works).
You are from Hershey Pa. I am in the Wilkes/Barre Scranton area. Anyone else experiencing this problem and in this area?
Do you have voice+ or google voice in your app drawer? I've seen some people who have had it in their app drawer who have been able to open that and select disable which remedies the problem. Hopefully Verizon gets back to you.
Click to expand...
Click to collapse
Yes, I'm from Hershey PA, my brother and I both have GS3s, but he's running 10.2 RC2 and I'm on the latest D2 nightly. The issue started in morning on the 20th. From what I can tell, it's only Verizon customers in our area that have been affected, my buddy on AT&T with a CM Nightly hasn't had any trouble. I tried disabling Voice+ but it didn't help anything. As of this point, my ticket is still open, so no new news yet. I'll keep you posted.
Dex954 said:
Do they know you are running a form of CM? Or are you just saying your texts aren't working?
Just for my own info?
Click to expand...
Click to collapse
I haven't told them I'm running a custom rom and I won't unless I actually need to. They don't seem to take kindly to people who like to get the most out of their phones.
AnTiDoWn3r said:
I haven't told them I'm running a custom rom and I won't unless I actually need to. They don't seem to take kindly to people who like to get the most out of their phones.
Click to expand...
Click to collapse
That's why I think this is going to be a hard road..
Sent from my SCH-I535 using Tapatalk
This is actually quite fascinating. All of those who seem to be having this issue are in Central Pennsylvania, started having the issue around the 20th, and are running a version of Cyanogenmod. I'll be sure to bring that up in my next chat with Verizon. Stay posted.
Hershey PA here
Cm11 m3 d2vzw
I've been having the same problem since ~20th as well. In glad I found this thread as I couldn't find much else when searching. I've temporarily switched to a TW ROM and it worked fine but any aosp seems affected. I even got Verizon to give me a sim but it didn't help.
My cell number starts 570-57*-**** (Scranton area number ) though I now live in Hershey pa.
This is where I wish I knew someone who worked at vzw and was a reasonable person.
Sent from my SCH-I535 using Tapatalk
I am just outside Philly, I started having this issue on the 20th as well, occurred on both paranoid android beta 4 from notta and slim kat stable 3.0. Seems to be intermittent for me as there is times where it works freely and times I need to toggle airplane mode for every text
Edit: my number is from northeast pa (Hazleton Area). I'm wondering if it is an area code issue or something because I know people with s3s down by philly who don't have this issue with Verizon.
Sent from my SCH-I535 using xda app-developers app
bass0324 said:
I am just outside Philly, I started having this issue on the 20th as well, occurred on both paranoid android beta 4 from notta and slim kat stable 3.0. Seems to be intermittent for me as there is times where it works freely and times I need to toggle airplane mode for every text
Edit: my number is from northeast pa (Hazleton Area). I'm wondering if it is an area code issue or something because I know people with s3s down by philly who don't have this issue with Verizon.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Been having the same issue. I live in mountaintop so maybe you're right
Central PA 570 here as well. Both my mom and I's phones are experiencing the same. What baffles me is that it happened to be people who had already flashed the ROM prior to the 20th, which means it isn't an AOSP specific SIM activation issue, because that happens on first boot. Touchwiz works fine, although I can't stand it. Whatever it is, I desperately hope it's fixed soon.