Related
So I just got a Nexus S 4g on Monday and my dad and I already rooted the phone and have been trying different roms. He actually rooted it and swapped out the stock rom before I even knew I was getting it.
So with both of the roms I have tried, whenever i recieve an incoming call the speakerphone automatically activates and I have to manually turn it off.
We already tried reflashing the rom and we have also tried replacing a lib***.so file (forget which one) and neither fixed the problem. I cant find any sort of setting for this.
Anyone else having this problem? Is there a fix available that someone can guide me? Very new to Android so I'm still learning the tricks of flashing etc.
Just curious...did you test the phone before it was rooted.
Sent from my PC36100 using XDA Premium App
I received the phone on monday evening and my dad had the phone all day and routed it etc.
I never handled the phone with the stock rom. Its not too big a deal since I don't use it for much calling but a fix would be greatly appreciated.
Sent from my Nexus S 4G using XDA App
webhead1994 said:
I received the phone on monday evening and my dad had the phone all day and routed it etc.
I never handled the phone with the stock rom. Its not too big a deal since I don't use it for much calling but a fix would be greatly appreciated.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
Well it seems like you don't know if this problem has always existed or if it is a result of flashing a custom rom. Best bet would be go back to completely stock and see if you still have the problem.
Sent from my PC36100 using XDA Premium App
Just flashed the new miui rom and it fixed the problem. Now I just have to redo my launcher lol.
Sent from my Nexus S 4G using XDA App
I'm having the same problem running a stock version of Android.
I started to have the same problem few days ago and my phone is all original stock, ,,
my wife just started experiencing this today. completely stock nexus s. we may try uninstalling the last few apps that had updates and see if we can trace it to one of those.
edit: are any of u using go sms (specifically version 3.66)? other users are complaining that recent update is causing this issue. im sending my wife a backed up version i have of 3.65 to see if its resolved
edit 2: rolling back to 3.65 did not resolve the issue, but rolling back to 3.64 did. good thing i have appmonster pro.....
I just started to have this problem today too. I did try to activate GoogleVoice yesterday but the calling issue did not begin until today. Running MATR1X v.6 and CM7 nightly #83. Didn't have this problem during stock.
Go sms's latest update is the culprit. The August 29 th update is responsible. Just uninstall that and put some other sms app.
Should solve it, It fixed my phone.
it happened to me twice yesterday, I answer the phone the screen went black and the sound routed to the speaker..can't go back to turn it off during the call as the screen has nothing. (stock rooted)...will uninstall GoSMSPro and see how it goes
If anyone needs/wants the 3.64 version of GO SMS, dm me you're email addy. (i'm assuming this would be ok on XDA since the app is FREE in the market?)
They (GoSMS) just released an update 3.66 to fix the problem
vennstrom said:
They (GoSMS) just released an update 3.66 to fix the problem
Click to expand...
Click to collapse
Its still exists on 3.66. My wife was using this version and it had the problem. We had to roll back to 3.64 before it went away.
u were right, Go SMS was the issue, they released an update today and solved the problem!
cheers everyone!
Glad I saw this thread... my G2 started doing this after not changing the ROM in months, at least now I know what caused it. I got my Nexus S yesterday and haven't answered any calls without the headset yet, lol, so I thought it was just my G2.
Ever since day one (start of August or so) I've been having a few problems with this phone. At first, I thought it was just the network or maybe the recipient's network. Then I realize it may very well be the Blaze itself.
The problem I'm facing is this...
Almost every time I try to make a phone call I can't hear anything. No dialing sound audio. No person on the other line... just nothing. The phone does go through, but I can't hear anything. I don't use any BlueTooth device. I have to wait several minutes or reboot my phone several times in order for the calls the work properly. This issues has been going on from GB (stock, no root) to ICS (stock, no root) until now that I'm flashing the phone to see if I can fix it (currently using PA's latest version as ROM). I thought the updated radio from ICS would fix it but to no avail. Goes to say, this issue happens to my father, too (same phone, got them for free when we started the contract).
This has caused an annoyance for both me and for friends.
Anybody else experiencing this? Any ideas as to why this happens?
IDK if this helps but I'm from Puerto Rico.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Same here!!!! I'm in California and on stock rooted ICS
Sent from my SGH-T769 using xda app-developers app
---------- Post added at 08:22 PM ---------- Previous post was at 08:13 PM ----------
It happens to me but not my brothers who have the same phone... They are on stock GB tho
Sent from my SGH-T769 using xda app-developers app
Tell you what, I have been having the same problem. Make sure you call tmobile and complain! They are telling me that this is not a known issue and there are no complaints on it. I had a detailed complaint filed. I sent my phone back, got another one and it is worse than the first with this issue! Another strange thing is that it will suddenly make doubles of my custom ringtones and one of the files doesn't work. It defaults to generic ringtone. Very glitchy. Sometimes, will still show that the custom notification tone is selected but will play default tone. I am sending this one back too. I am really bummed to hear that rooting did not fix the issue on the phone calls. I was actually considering doing this next...... Really hope the next phone doesn't have this issue. I like the Blaze and don't know of another tmobile phone that is comparable to replace it with.
ditto
I have the same problem I believe. I currently dorm near the Bay Area, California. I haven't been able to hear or reply through my calls even though they connect to the other person's phone. This isn't exactly a signal problem because the phone still has bars and I can still tell when someone is trying to call me. I still receive texts, use wifi, and sound is working perfectly fine. I am glad I am not the only one with these problems.
edit: This whole "unable to hear or speak" into the mobile phone problem began around November 22nd (thanksgiving overload?).
I am using CyanogenMod 9, rooted of course.
edit2: So I just tinkered around with the sim card and battery by taking it out and waiting for a minute or two before putting it back in. Voila! I can now hear my voice mail.
Sounds like Handset issues with me... send them back and have them send you new ones... that's some BS if it is doing that Stock.
Just my opinion... being through a lot of phone and that is what it sounds like. just one mans opinion... cheers
anoontm said:
I have the same problem I believe. I currently dorm near the Bay Area, California. I haven't been able to hear or reply through my calls even though they connect to the other person's phone. This isn't exactly a signal problem because the phone still has bars and I can still tell when someone is trying to call me. I still receive texts, use wifi, and sound is working perfectly fine. I am glad I am not the only one with these problems.
edit: This whole "unable to hear or speak" into the mobile phone problem began around November 22nd (thanksgiving overload?).
I am using CyanogenMod 9, rooted of course.
edit2: So I just tinkered around with the sim card and battery by taking it out and waiting for a minute or two before putting it back in. Voila! I can now hear my voice mail.
Click to expand...
Click to collapse
I live in the Bay Area too and I have the same problem. It has been gone gone since before Thanksgiving though. Any help would be great thanks.
Sent from my SGH-T769 using xda app-developers app
I would be better off getting a new, better phone, it seems. It is quite annoying. Either way I voided my warranty by flashing. I don't suppose I can actually return it back to stock (like, literally returning to stock and unrooting and wiping and formatting every data) so I can still give it back... can I?
PS: Thanks for the replies.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
DarkDragonPR said:
I would be better off getting a new, better phone, it seems. It is quite annoying. Either way I voided my warranty by flashing. I don't suppose I can actually return it back to stock (like, literally returning to stock and unrooting and wiping and formatting every data) so I can still give it back... can I?
PS: Thanks for the replies.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
See the 'return to stock Odin thread' in the dev section. You will also need to flash the flash counter reset from the themes section.
Sent from my SGH-T769 using xda app-developers app
eggytoasty said:
Sounds like Handset issues with me... send them back and have them send you new ones... that's some BS if it is doing that Stock.
Just my opinion... being through a lot of phone and that is what it sounds like. just one mans opinion... cheers
Click to expand...
Click to collapse
I got my third phone from tmobile the other day (all Blaze) and my very first phone call it happened on. To add to what someone else said. The phone shows plenty of signal strength and in fact, if I hang up and call right back the call goes through as it should. This from sitting in the exact same spot. I can't figure out what's going on? I had thought on this and realized that I had been turning off apps on the phone that I don't use (pre loaded junk). On the off chance that had something to do with it I turned them all back on. Still does it. I'd say it is a good 30-35% of my calls that this happens on. Very frustrating. I really like this phone but it won't function as a phone for me. I guess now they have to give me a different phone if I return this one too but I don't know what phone is comparable in size and function. I picked this phone specifically for the size. My wife got an s3 and I was not interested in it at all due to how big it is. This sucks.
I have to chime in. i just bought the blaze for my g/f, and i've using an sgh-t989 (galaxy s2), having the same issue you are describing. stock radio, stock ROM, just rooted.
Such a shame considering it is such a great phone for the price it is offered at. Safe to assume it is a hardware problem?
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
NetrixTardis said:
I have to chime in. i just bought the blaze for my g/f, and i've using an sgh-t989 (galaxy s2), having the same issue you are describing. stock radio, stock ROM, just rooted.
Click to expand...
Click to collapse
Are you saying that you are having this problem with the blaze or the s2? Both?
Both phone are having this behavior. new SIM used in both phones aswell.
Yeah, I went down and switched out my sim card as well. My wife has an s3 and has no problems so I don't know what's up? Shows signal but calls won't connect properly. Hang up and call back, it works. Huge pain when I am driving or short on time though.
Any fix this problem found? I talked to samsung and t-mobile today, samsung was no help at all and t-mobile asked me to master reset it. Once that didn't work they offered a warranty exchange. Any one have luck correcting the issue?
So far? No. But my phone seems to be behaving for the past few days (3). Which is weird. I'm probably jinxing it right now.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Restart during a call, the handset will not send sound.
Maybe they got a bad batch of Blaze 4G's. NOT making an excuse for them but I know it's happened in this business and others.... If I were u I wouldn't keep on dealing, hats to your patience. Let know where you're at. I've flashed to CM 10 nightly 20121207 and my Blaze is just damn sexy lmao, "figure of speech" good luck brought cheers
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
DarkDragonPR said:
So far? No. But my phone seems to be behaving for the past few days (3). Which is weird. I'm probably jinxing it right now.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
Same here
NetrixTardis said:
Both phone are having this behavior. new SIM used in both phones aswell.
Click to expand...
Click to collapse
Whas ROM are you using? ICS and gingerbread have a call preference switch in settings. Set it to data preferred. Cm 10 has a lte switch in settings use it. Battery apps can cause delay in data connect. Try these and let me know how it works.
Alright, to begin. About a month ago I lost my GPS. Meaning, my phone could not locate itself. Move up to the end of last week...I was unable to send text messages, call out or receive calls. I WAS able to receive text messages. Also, I could use my mobile data (i.e. Internet). Then, I lost ALL capabilities and the phone went to asking me if I wanted to switch to GLOBAL ROAMING. Still, at this point I could ODIN flash to stock. However, I could not ROOT the phone. Even with flashing back to stock (unrooting), the phone would not call, or text, etc...Okay, still with me? So, yesterday, I took the phone to the local Verizon Corporate store to have them look at it. A new SIM card did not fix the problem. In fact, when he booted the phone, the boot and splash screen both came up with a picture of a big LOCK (that was unlocked) and the word "CUSTOM". He looked at us and said, "That's not supposed to be there.". It never was until that time (mind you, I had unrooted). The phone wouldn't even boot to the VZW stock recovery. He was awesome to work with and we did so for over an hour. He was going to replace the phone with a new one under insurance (even though I don't have insurance on the phone). But the phone was not in the system. They couldn't find it. "Like it doesn't exist". So, today I am still messing with it and have been all over the internet looking for a solution. I've ODIN'd the stupid thing so many times in the last two days. NOW, I DON'T have the big un-locked LOCK or the "CUSTOM" anymore, but I can't get past the setup screen because the phone is ROAMING! It will ask which language, then, at the next screen, it tells me to wait while it connects to Verizon Wireless and activates itself. At this point, the phone will make a phone call, ON ITS OWN, and I listen to people telling me that I may be eligible for a $100 gift card as well as other advertisements. I used to be able to pull down the notification bar and setup my wifi. Now, I can't do that.
I've tried every stock ROM available all the way back to 4.0.4. At first, that's what I would do and then, just apply the OTAs until i reached 4.1.2. Now, I can't even get that far.
I'm sure I've forgotten some things, but please ask away if that will help clear anything up. I've never had any problems with this device. Could it be a virus? Or is it doomed for the recycler? I have no idea what to do. Thanks.
Also, I remembered, when I was able to see my phone's info it showed I was connected to the network and everything looked as it should and would, normally. I still couldn't send texts, call, etc...on Verizon's customer representative end, they would also say that it would look like the phone was trying to do something but never would.
When I would request my IMEI#, it checked out fine. However, when I would use the dialer for the IMEI check, I would get the IMEI# followed by a /01 or /02. Not sure what that means, but thought I'd throw that out there, as well. Thanks
Now, when I'm in the aforementioned set up screen, my phone direct-calls Alltel. "Thank you for calling Alltel". WTH.
Sent from my GT-P3110 using xda premium
just for a baseline where is the phone at now? As in what Rom, base(modem), bootloader locked/unlocked, kernel, prl, eri, imei still there not messed up?
Sent from my SCH-I535 using Tapatalk 4 Beta
Your phone is shot. Same thing happened to my original s3. Started with gps, then started losing internet, and messages not working then making calls started to go. I tried everything I could. I had to call Verizon and get them to send me a replacement.
Sent from my SCH-I535 using xda premium
bbolton_98 said:
just for a baseline where is the phone at now? As in what Rom, base(modem), bootloader locked/unlocked, kernel, prl, eri, imei still there not messed up?
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Hi. Unfortunately, I couldn't give the specifics because I don't really know. Other than, the last flash I did was Odin back to stock (un-root) and do all the OTA updates (up to 4.1.2). So, whatever all the stock, non-rooted S3s are running. Sorry I couldn't give more info. Thanks.
Sent from my GT-P3110 using Tapatalk 2
bbqsfire said:
Your phone is shot. Same thing happened to my original s3. Started with gps, then started losing internet, and messages not working then making calls started to go. I tried everything I could. I had to call Verizon and get them to send me a replacement.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Thanks. Yeah, I was on the phone from 11pm last night until 1am this morning with Verizon and they couldn't get it working. Put in another "network fix" ticket but haven't heard back. Looks hopeless. My contract is up and I am really looking forward to the S4, but money is tight and I was going to wait a bit before that purchase. I was using an old Samsung SCH-U900 Flipshot as my backup. I don't have to tell anyone, but that sucked. Now, I can't even use that because they need the line clear for the work order. So, I'm helpless. How the heck did I survive before cell phones?!
Sent from my GT-P3110 using Tapatalk 2
Welp, as a follow up, sent the phone off to Samsung. They sent it back with an updated PRL...and it WORKS!!! :good:
bbolton_98 said:
Thanks for the update, good to know to watch for prl. Glad you got it fixed.
Cruzin' tha GS3 w/Synergy Rom & Anthrax Kernel
Click to expand...
Click to collapse
Hey, no problem and thanks. I was going crazy with the old Droid X. Anyway, because of the outcome, I thought it would be a good reason to post and maybe help others. ORIGINALLY, when we first called Verizon, that's the first thing I wanted them to try. Or at least let me try. I just couldn't get past the language set up screen and the phone making calls on its own. All they would do is a factory reset. Still not sure why the phone went berserk and changed up on me. Oh well, it's back now and I couldn't be happier.
I got the 4.3 OTA update on 12.26.13, and was obviously excited. Sadly, whenever I remove the device from a charger and turn the screen off (not exactly a rare combination), the device will vibrate twice and reboot.
Things I've tried:
- Swapping out the battery
- Rebooting into safe mode
- Wiping Dalvik cache
- Factory data reset
- Factory data reset again
I spoke to Verizon, and they were of no use. They transferred me to Samsung, who said that my device is out of warranty, therefore I would have to pay for a repair. Really? From a software update while sitting on the nightstand? My argument fell on deaf ears.
I've already told them to eff off, and if I'm going to have to pay out of pocket to buy a new phone, I'm getting a N5 and going to ATT. Well, that's present tense now. Anyway, I'd love to fix the device to have it as a spare wifi device while traveling or to sell. Thoughts?
Plug it into the PC and run the installer that pops up. It will reload the 4.3 update and repair any issues.
Sent from my SCH-I535 using xda app-developers app
Hi Chatham7, were you rooted or 100% stock before taking the update? Did you have a custom rom or recovery before the update?
Sent from my Last Ever Samsung Device.
5ft24 said:
Plug it into the PC and run the installer that pops up. It will reload the 4.3 update and repair any issues.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
What installer? I've never seen one before. I have it in USB debugging right now, as I rooted it yesterday in attempt to try to resolve the issue.
0331 said:
Hi Chatham7, were you rooted or 100% stock before taking the update? Did you have a custom rom or recovery before the update?
Sent from my Last Ever Samsung Device.
Click to expand...
Click to collapse
100% stock with no modifications before the update.
If you prefer odin you can get the official tar now http://forum.xda-developers.com/showthread.php?t=2586319
Thanks, guys. I was able to re-install the update after some massaging of drivers and various other annoying hardware tweaks. However, it hasn't resolved the issue. My initial thought was that it was a hardware issue, but a hardware issue the very second after getting the 4.3 update? Just too coincidental for me.
chatham7 said:
Thanks, guys. I was able to re-install the update after some massaging of drivers and various other annoying hardware tweaks. However, it hasn't resolved the issue. My initial thought was that it was a hardware issue, but a hardware issue the very second after getting the 4.3 update? Just too coincidental for me.
Click to expand...
Click to collapse
It has to be hardware if you're 100% stock, your phone just isn't playing nice with the new update.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
It has to be hardware if you're 100% stock, your phone just isn't playing nice with the new update.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Agreed, sorry I wasn't being clear. I meant that it couldn't be a device issue caused by me (as Samsung and Verizon are implying), but rather a hardware compatibility with the new update. Their knee-jerk solution to everything is to use warranty and insurance. I'm not buying insurance to protect myself against them sending me software updates that will ruin my device. That's like paying protection money to the mob so that you don't get robbed.
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.