Related
hey i've notice that whenever i received a text message, there would be times where the it would say that the message is from another contact in my phonebook. when i click on it, it would tell me that its from the person that did sent it. for example....
josh texted me a message, and when i slide down the notification bar it could say brett, then when i click on it, it would take me to the conversation i had or having with josh
do you guys know what i'm talking about?
Are you on froyo?
Sent from my Captivate
This happened to me a few times before updating to JH7, but hasn't happened since.
Sent from my SAMSUNG-SGH-I897 using XDA App
Has happened to me as well on a stock JH7 captivate.
This happened to me a lot when I first got the Captivate...turns out that I had some random contacts linked together, and once I took care of that it never happened again. It doesn't sound like this is the case with you, but I'd say just check it out in case.
i experienced that also before... im on stock jh7 right now. i noticed that when i ran task killers and terminating the messaging app it would mess up my messaging when receiving sms.
i tried excluding the messaging app from the task killer and everything worked fine ever since. try it it. might help you.
I'm on JH7 and am still getting that. I did have task killer, but I uninstalled it. I've checked all my linked contacts and they are properly linked. So I'm not sure what else is causing this.
DaveyBB said:
This happened to me a few times before updating to JH7, but hasn't happened since.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
what is the jh7? i'm really new at this. i have atnt and i updated the software to the latest version.
For those of you who are experiencing the random reboot issue on the stock rom, would anyone be willing to do a factory reset without installing any apps and testing for a while to see if they still have the reboot?
I want to find out if this issue is a problem related to specific g2x's, or is triggered by some kind of software installed.
The reason why I want to test this out is because I have gone through 6 phones(waiting for 7th), and I can not recreate this problem on any of them running the same restored nandroid backup.
Also, for those of you who have gone through multiple g2x's, have you had phones with reboots and also ones without the issue
Since it seems LG is not recognizing this as a known issue, it most likely won't be fixed in the update they announced. Therefore its up tous to try find the cause of this issue whether it is device specific or due to certain apps installed.
Sent from my LG-P999 using XDA App
xdmds said:
For those of you who are experiencing the random reboot issue on the stock rom, would anyone be willing to do a factory reset without installing any apps and testing for a while to see if they still have the reboot?
I want to find out if this issue is a problem related to specific g2x's, or is triggered by some kind of software installed.
The reason why I want to test this out is because I have gone through 6 phones(waiting for 7th), and I can not recreate this problem on any of them running the same restored nandroid backup.
Also, for those of you who have gone through multiple g2x's, have you had phones with reboots and also ones without the issue
Since it seems LG is not recognizing this as a known issue, it most likely won't be fixed in the update they announced. Therefore its up tous to try find the cause of this issue whether it is device specific or due to certain apps installed.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
6 phones? Did you ever once suspect the software?
Sent from my LG-P999 using XDA Premium App
I thougjt I clarified in my original post that none of mine had the reboot issue and I was not able to recreate it either.
Sent from my LG-P999 using XDA App
If it a software related issue, it couldn't be the ROM since some people have this issue on other roms. It could be the kernel but all g2x's come with the same kernel out of the box IIRC and only some people are having the issue.
EDIT: wow I'm really inaccurate typing in portrait mode
Sent from my LG-P999 using XDA App
I never had a reboot issue in Arizona and I just got back to Ohio today and i have randomly rebooted 4 times today and I had to do a battery pull this morning... crack that nut for me
I went through 2 G2x's.
First one stock, rooted, and CM7 - all ways would reboot.
Second one, stock, rooted and CM7, all ways would reboot, so I tried it stock and CM7 without any added on apps - same results both stock and CM7.
JWhipple said:
I went through 2 G2x's.
First one stock, rooted, and CM7 - all ways would reboot.
Second one, stock, rooted and CM7, all ways would reboot, so I tried it stock and CM7 without any added on apps - same results both stock and CM7.
Click to expand...
Click to collapse
It seems that people who are getting reboots, are getting reboots across multiple g2x's, while people who aren't getting reboots, don't have the issue across multiple g2x's. So there must be some kind of installed software related thing that is not playing nice and causing the phone to reboot itself. There isn't enough info in order to make a definite diagnosis to the source of the problem yet which is why I made this topic.
I feel that it's definitely software b/c I've been running the leak without any reboot issues. They still need to also fix the kernel too
Sent from my LG-P999 using XDA Premium App
philthyman21 said:
I feel that it's definitely software b/c I've been running the leak without any reboot issues. They still need to also fix the kernel too
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
what is confusing me is if it is software, why is it only affecting some people? the leak is running a different kernel so that could possibly be why you aren't getting reboots, but something must be triggering it that the people who have the issue have down/installed etc.
xdmds said:
what is confusing me is if it is software, why is it only affecting some people? the leak is running a different kernel so that could possibly be why you aren't getting reboots, but something must be triggering it that the people who have the issue have down/installed etc.
Click to expand...
Click to collapse
I don't think the LG kernel for the G2x has been released :-\ BUT I could be wrong
Sent from my LG-P999 using XDA Premium App
xdmds said:
It seems that people who are getting reboots, are getting reboots across multiple g2x's, while people who aren't getting reboots, don't have the issue across multiple g2x's. So there must be some kind of installed software related thing that is not playing nice and causing the phone to reboot itself. There isn't enough info in order to make a definite diagnosis to the source of the problem yet which is why I made this topic.
Click to expand...
Click to collapse
Orrrrr...perhaps it related to the network somehow? Strength of signal or need for the phone to switch between 4G/2G? Or perhaps trying to go to the ever elusive 3g (since I still haven't seen a report of someone actually seeing 3g in the notification bar). Maybe folks with reboots are in fringe areas and the phone oscillates between 4g and 2g and doesn't like it? Maybe those folks use their phones differently...leave BT on all the time and run apps that access GPS regularly. Or any other number of possibilities.
It's too easy to blame an app.
I know that one of the barcode scanning apps caused my phone to lock up, and sometimes reboot.
-bZj
bluemoon737 said:
Orrrrr...perhaps it related to the network somehow? Strength of signal or need for the phone to switch between 4G/2G? Or perhaps trying to go to the ever elusive 3g (since I still haven't seen a report of someone actually seeing 3g in the notification bar). Maybe folks with reboots are in fringe areas and the phone oscillates between 4g and 2g and doesn't like it? Maybe those folks use their phones differently...leave BT on all the time and run apps that access GPS regularly. Or any other number of possibilities.
It's too easy to blame an app.
Click to expand...
Click to collapse
Thats why I'm asking people to participate in this experiment. By eliminating variables one by one we can try to single out the cause.
EDIT: also, the 4g signal shows for both 4g and 3g. The only way u can tell which one you are on is by going to "about phone". UTMS is 3g then there hspa(+).
Sent from my LG-P999 using XDA App
xdmds said:
Thats why I'm asking people to participate in this experiment. By eliminating variables one by one we can try to single out the cause.
EDIT: also, the 4g signal shows for both 4g and 3g. The only way u can tell which one you are on is by going to "about phone". UTMS is 3g then there hspa(+).
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
check your pms xdmds
let me know if u need anymore help with tmobile
Mine actually rebooted randomly very often. It didn't matter what rom I had (Stock, Eagle, CM7). I tried everything.... factory resets, removed apps, etc. It's just very random when it decides to reboot. Sometimes when I'm using google maps, sometimes when I'm trying to text, or when I'm playing with an app. It got so annoying that I had to return the phone.
I noticed that the times my G2x has rebooted was when it got hot. For example, if I charge it, talk and surf at the same time it will start getting hot and either freeze or reboot. Sometimes just charging it will freeze it.
I'm trying out a new battery and so far the phone seems to run cooler...its 25.2c right now and I've been playing with the phone for a while...with the stock battery I dont remember the temperature below 27c ever...sometimes with heavy use I would see it go as high as 43c...
it's only been one day with the new battery but I'll let you guys know how it behaves the next few days.
Sent from my LG-P999 using XDA App
Well android leaves apps open. There is no exit button on the apps that kills it. I religiously kill tasks and check to see what's running. Is there any type of reporting app that will tell you what was running at the time of the reboot like maemo/N900 has?
As far as I know, I have not had one reboot. Has not been a full week though. If it was rebooting in the night, I guess I wouldn't know it.
Hell, I haven't had any real probs. My Gps was way off, but I rebooted it outside and it's been dead on since.
I love my G2X.
I just got an exchanged phone due to reboot/shutdown issues. I did not install any 3rd party software, and i had a shutdown that required a battery pull while it was on the factory charger.
Not sure if I should keep exchanging until I get one that works or not...
mapin0518 said:
I just got an exchanged phone due to reboot/shutdown issues. I did not install any 3rd party software, and i had a shutdown that required a battery pull while it was on the factory charger.
Not sure if I should keep exchanging until I get one that works or not...
Click to expand...
Click to collapse
Did you have anything installed at all?
Sent from my LG-P999 using XDA App
Getting tried of watching my phone reboot. If going back to stock would resolve the issue I would do it. I called big red today and the pinhead I spoke to acted like it was the first time anyone had called about the TB rebooting on it's own. I'm looking at going to a different phone. I really think at this point it is a software issue that they need to correct. Just like with most businesses things are not addressed until they become a problem. So my thought is we should set a date when every one calls in to report their rebooting phones. We do this every week until we get a resolution. Anyone with me?
Wait... You are rooted and getting reboots? Are you on gb? Did you root or install your rom properly? What kernel?
Stock I had no issues. Non-Gb I've had mostly no issues... Some kernels less reliable than others, of course. But to be honest it sounds more like a user issue than a tb issue
Sent from my ADR6400L using XDA App
Sent from my ADR6400L using XDA App
Are you near a Verizon store? Verizon is usually very easy to convince that you need your phone replaced. (Although I think they will only replace it with the same model. But I'm not sure.) My Thunderbolt never reboots on its own but I know it is a problem that many Thunderbolts are experiencing, so maybe yours (and many others) is/are defective. I'm 99% sure if you go into a Verizon store and tell them that it randomly reboots all the time, they'll replace it for you.
I reverted back to stock and haven't had a single reboot or loss of data on three days. Just sayin'.
Sent from my ADR6400L using XDA App
I have read posts where people who are not rooted are getting reboots after they took the update. Have never had an issue with my phone until I took the update. Am going back to stock for a week or so to see if that clears things up.
Funny how VZW is changing their stance on it, almost as if it never has happened. About a month ago I went into a store and they told me that Im not the only one experiencing problems and that there will be a fix within 2 months.
I called VZW tech support and they told me that no one else is having reboots.. . . . I dont get it.
Try flashing your radios, I put both of mine to .6 and the reboots stopped.
(there is a thread in teh development forum, with the packages)
Can you specify what you mean when you say "both"? I have been getting reboots too - approximately 1 per day - but is there a process to flash each radio independently?
Sent from my ADR6400L using XDA App
sethschmautz said:
Can you specify what you mean when you say "both"? I have been getting reboots too - approximately 1 per day - but is there a process to flash each radio independently?
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
No, but each flash has two radios
Sent from my ThunderBolt using XDA Premium App
Silvus said:
Try flashing your radios, I put both of mine to .6 and the reboots stopped.
(there is a thread in teh development forum, with the packages)
Click to expand...
Click to collapse
Any issues with tethering or gps using the old radios?
Sent from my ADR6400L using XDA App
Silvus said:
Try flashing your radios, I put both of mine to .6 and the reboots stopped.
(there is a thread in teh development forum, with the packages)
Click to expand...
Click to collapse
I still had reboots with both at .6, currently trying cdma.7/LTE.6.
Sent from my ADR6400L using Tapatalk
It is a hardware issue,that's where the few pricked phone came from,my original bolt had the reboot loop on stock but no one seems to want to hear that,it is a series of phones having the trouble and they are or have replaced most of them,as far as most of the other reboot go that is self made misery by not following directions or not reading to find the fix, this bolt I have now has no reboot issues and it has a mat finish to it,the other one and a few I have seen that had issues had a smooth glossy finish.
Sent from my ADR6400L using XDA Premium App
satseaker said:
It is a hardware issue,that's where the few pricked phone came from,my original bolt had the reboot loop on stock but no one seems to want to hear that,it is a series of phones having the trouble and they are or have replaced most of them,as far as most of the other reboot go that is self made misery by not following directions or not reading to find the fix, this bolt I have now has no reboot issues and it has a mat finish to it,the other one and a few I have seen that had issues had a smooth glossy finish.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I would love to think its a hardware issue, but my phone was solid from day one. Then I took the update and get these random reboot.
Sent from my ADR6400L using XDA App
It is not a hardware issue. It is a problem with the update and how certain phones installed it. Verizon is in the process of making a new update and has been working on it with HTC for a little while now & expect to have it going out this month. For some reason the software does not talk to the towers properly with some models & the hardware does not get the proper info which causes the reboots. Exactly how to tell which phones are affected, I don't know. My friend is trying to find out for me.
I can say that I ran my phone with rooted stock & moved up to the rooted update when it was available which I am still on and I have not had any issues at all besides the low recorded video audio which the update seems to have fixed for me.
My phone is:
Rooted stock & radios w/update
Adrynelynes 4.47 Kernal
I am telling you what HTC said they admit that a certain series is defective hence the snappy replacement. Just cause one Rom works and another doesn't isn't always the Roms fault,ever had a CPU that would run one OS and not another or RAM that worked fine on xp but not win 7 once the defective hard hits its limit it will fail. I have seen hardware work fine overclocked and the exact same hardware crash with half the settings,or a motherboard run suse fine but put Windows on it and it dies a week later. I didn't say they all were defective just one series of them and when they did the update a lot of the phones started to fail and some didn't,so does that tell you hardware or software,if one can run fine and the other fails its either a bad flash or bad hardware. Take your pick
Sent from my ADR6400L using XDA Premium App
I didn't do the update over the air on my other bolt, I downloaded it from HTC and it killed the phone,but the same download is on this phone and it works just fine,not one reboot, and its still stock and not rooted. The other one was dated Dec
10 and this one is dated Feb 11, I would just about guess they tweaked the update to weed out the bad phones faster,makes sense to me.
Sent from my ADR6400L using XDA Premium App
satseaker said:
I am telling you what HTC said they admit that a certain series is defective hence the snappy replacement. Just cause one Rom works and another doesn't isn't always the Roms fault,ever had a CPU that would run one OS and not another or RAM that worked fine on xp but not win 7 once the defective hard hits its limit it will fail. I have seen hardware work fine overclocked and the exact same hardware crash with half the settings,or a motherboard run suse fine but put Windows on it and it dies a week later. I didn't say they all were defective just one series of them and when they did the update a lot of the phones started to fail and some didn't,so does that tell you hardware or software,if one can run fine and the other fails its either a bad flash or bad hardware. Take your pick
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I wasn't aware of HTC stating there was some defective hardware. Never saw any references to it. If thats the case then glad they acknowledged it.
It's definitely not a hardware issue. Its a radio/ signal issue. Verizon does know about it, and is working on getting a new update out there. I know this, for a fact.
Sent from my ADR6400L using XDA App
jett2314 said:
I have read posts where people who are not rooted are getting reboots after they took the update. Have never had an issue with my phone until I took the update. Am going back to stock for a week or so to see if that clears things up.
Click to expand...
Click to collapse
My TBolt is not rooted and before the update I had no problems at all but after the update the random reboots started. Battery life is acceptable but could be allot better.
Called Verizon yesterday and they acknowledge the problem and actually said HTC is aware of the problem and are working on it but have no expected date as to when it will be fixed. I believe it is definitely is a software issue and will be fixed when the official Gingerbread is released. Just my 2 cents.
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
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.