Develop Bugs

[Q] 3g connection will not stay up

So for the past 2 weeks I am having issues that basically render my phone unusable for 99% of the reasons I bought it. Posted a thread before but I think it got lost when the forums were having some instability around that time...
My 3g connection will NOT stay up. I did nothing to provoke this. No system changes. The sequence of events:
-Went out of the country with my phone on airplane mode the whole time
-Got back, a day or two later had an incorrect timestamp on my incoming SMS (they were showing up +3 hours)
-Called customer service, she activated a tester phone and confirmed that it was a system-side issue on the incoming SMS (somehow they were getting a timestamp from the system where my number is located, in Eastern time, while I am actually located in Pacific nowadays).
-Put in a trouble ticket after 2 hours trying to solve the SMS issue over the phone.
-Next day, my 3g connection begins dropping CONSTANTLY. As it stands, it won't stay connected more than 30 seconds. It will cycle to 1x sometimes, and then drop to a basic-service-only.
-Tried reinstalling my ROM several times to no effect.
-Started experiencing some very strange noises in SOME calls, such as it sounding like a chainsaw when the other person is talking. Happens very sporadically.
-Just today I found some instructions here for correcting my NAM settings, which were actually messed up as it turns out, but didn't fix anything.
At this point I actually have the phone unrooted and back to factory default everything, with no change. I've got a warranty replacement phone coming in shortly, but I'd still rather keep this one if I'm able to.
Is there anything I haven't tried that might be the case on my end? Has anyone seen this problem before? Has my phone antenna simply gone belly-up, or is this something that might still be fixed at some deep system-setting level, or with further calls to tech support?

So... I guess that's a no?

Gornul said:
So... I guess that's a no?
Click to expand...
Click to collapse
Had the same problem with my phone before I rooted my phone and starting to apply ROM's. I havent had a problem since. But when I had that problem, I would just keep turning on and off the 3g and it would stay for a while. It was just a quick fix but it worked. Off subject how did you unroot your phone and put it back top stock?

My phone just started doing this this yesterday. Whenever I reboot it, it'll come up, switch to 1x mode. After a while it'll try to switch to 3g mode, fail, switch to no service, and then either go to just basic voice with no data or back into 1x mode. I've tried updating the radio, switching roms, dialing *228, nothing seems to help.

Jager, instructions on a full reset are right here under section 6. I'm not sure why it's struck out. Definitely suggest poking around more first.
New phone's in and still having major connectivity issues. The SMS timestamp remains as it was, and I can't get (steadily) more than like 35kbps. I'll occasionally bump to 500kbps for a quick spurt, and then my connection will drop entirely and struggle to get back up to 35kbps. My wife's Incredible works perfectly fine in the exact same locations, too, so this is something that absolutely has to be on Verizon's side, specific to my line.

Me too
My phone has also been experiencing the loss of 3G service as well. I checked my wife's Moto Droid 1 and it was also having difficulty connecting as well. I called Verizon and they were absolutely no help whatsoever. I am either getting nothing or 1X in places where I have always had 3G. This is very frustrating. I have flashed 3 different ROMs (all of which have worked fine in the past), but the result always seems to be the same. Anyone else out there with this issue?

khukman said:
My phone has also been experiencing the loss of 3G service as well. I checked my wife's Moto Droid 1 and it was also having difficulty connecting as well. I called Verizon and they were absolutely no help whatsoever. I am either getting nothing or 1X in places where I have always had 3G. This is very frustrating. I have flashed 3 different ROMs (all of which have worked fine in the past), but the result always seems to be the same. Anyone else out there with this issue?
Click to expand...
Click to collapse
Someone help! Same issue! I can no longer get data....PERIOD. I have to stay connected to wifi, or I don't get my emails, internet, etc.
Need to fix this!

3G connection issues
I just got off the phone with Verizon Tech support. They are CONVINCED that it is an issue with my phone (and my wife's). Gee, how can 2 different phones, from different manufacturers have the SAME issue at the SAME time? Hmm, doesn't sound very promising to me.
They are sending out a replacement for my wife's Moto Droid to see if it is a phone issue (she has been having other issues with it anyway...). If hers improves, I may send mine back, but I don't want to have to unroot, etc. Plus I like the Super-Amoled screen . When did trouble-shooting turn to "replace the hardware first" ???
Regards!

This happened to me recently as well and was fixed with a factory reset.
I am rooted with S-off, so a normal factory reset via Menu->Settings->SD & Phone Storage-> Factory Data Reset didn't go well for me. Not sure of the exact reason, but I just followed the instructions in this post to restore: http://forum.xda-developers.com/showthread.php?t=786436
Programming your phone by dialing *228 is necessary afterwards as well, as khukman states below. Thanks for pointing that out.
After I completed this, I redid root, restored my nandroid backup and didn't lose a thing, plus my 3G is working again!
*A fair warning: Doing this formats the internal storage (emmc). I'd recommend backing up any photos, music, etc that you have stored on emmc before doing this!
Sent from my Droid Incredible

So I tried the above suggestion about going back to completely stock 2.2 and I have the same results. On one hand, I am now back to S-ON and stock Froyo, so if I want to send it back to Verizon, they are none the wiser that I was rooted, but on the other hand I STILL HAVE CRAPPY 3G SERVICE!!! Man, I feel like I'm on AT&T or something LOL! I'll keep an eye on it for the rest of the day and see how it does and report back.

Back in 3G!!!!!
After getting back to stock Froyo, as described in the previous post, I was still unable to get a good 3G lock. I read in another thread where someone did a 'Factory Data Reset' and it took care of it. When you do this, you have to dial #228 and let it program your phone as it did the first time when you got it. Once I did this, I had (and still have) a solid lock on 3G like I used to. I think that it was one of the Sprint ROMs that screwed this up in the first place (the OP states that you have to backup your PRLs, etc. before installing, then re-install them afterwards). I can't remember if I did this or not, so it may be my fault after all, but regardless, I am thrilled that once again I have a connected smartphone thanks to the resources contained on XDA!
Regards!

I myself am now rocking a refurb that has no trouble at all... A complete revert to stock did absolutely nothing to resolve my trouble.
Though I didn't try doing a factory reset AFTER reinstalling the stock ROM. Hmm. Maybe there was something in the cache still. I suppose in my case I'll never really know, but I'm glad you guys were able to resolve the situation with your original hardware.

Gornul said:
I myself am now rocking a refurb that has no trouble at all... A complete revert to stock did absolutely nothing to resolve my trouble.
Though I didn't try doing a factory reset AFTER reinstalling the stock ROM. Hmm. Maybe there was something in the cache still. I suppose in my case I'll never really know, but I'm glad you guys were able to resolve the situation with your original hardware.
Click to expand...
Click to collapse
Did you follow the steps in the thread I posted above? Doing that should completely format and re-image your phone. Much more than just installing a stock ROM. I myself tried so many different variations of ROMs, radios, etc and nothing did the trick until I followed that thread.
Sent from my Droid Incredible

BIG PROBLEMS, no 3G/4G mobile service since yesterday, tried EVERYTHING

Need some help here. I never usually need help, been modding everything possible on Android for years now. But can't figure this one out, getting worried.
Had my LTE Nexus since launch day. No issues like this before.
Been on all Team Kang AOKP toro ROM updates since release, always on the latest. Stock kernel. Was on build 20 since it came out.
Yesterday at work, had a few bugs from probably not data wiping from build 19, so I wiped it all and re-flashed 20 again. Restored Titanium and started re-setting things up, I believe these are the only things I did. I was at work where I would normally have minimal, but some, service.
Ever since around there, I have not once had a bit of 3G or 4G service. I have not seen the 3G logo for even an instant, only few, gray bars. Wifi works fine of course. It's possible I even lost service before wiping and re-flashing, but I can't recall or didn't notice.
I tried all the usual stuff, wiping everything again, re-flashed AOKP 20, re-flashed other/older ROMs, re-flashed latest radio, restored old Nandroid backups, pulled battery and sim card and put back/rebooted...NOTHING IS WORKING. Also, I have driven through several towns since yesterday so I know it's not a local outage. Also, other people with Verizon phones here have service fine.
I have basically torn the phone down software-wise and nothing has fixed the issue. I still have no service. Each time I re-flash a ROM, it always makes me go on Wifi when it wants me to sign into Google...it never picks up mobile service then or after.
The About>Status screen says:
Network: Verizon Wireless
Signal Strength: shows an actual number reading that changes
Service State: In Service
Roaming: Not roaming
Mobile network state: Disconnected
Please suggest things I can try, but I guaranteed I have already tried them. Can't understand or imagine what is causing this, because I did nothing different than I normally do.

Also, I posted this on Rootz as well, and many replies so far. Still no luck though.
If you have an idea I can try, maybe post there instead at this point for me?
Thanks guys in advance.
http://rootzwiki.com/topic/16407-bi...ile-service-since-yesterday-tried-everything/

It seems a radio problem. Try to flash the stock ROM from Google.

tigajr said:
It seems a radio problem. Try to flash the stock ROM from Google.
Click to expand...
Click to collapse
Well I did go back to many random earlier, more stock custom ROMs in hopes of a fix, but nothing so far. I am currently back on the stock 4.0.2 ROM that is rooted and deodexed by Bigxie, but I guess I can go all the way back to stock 4.0.1 or 0.2. Will try now.

Went to Verizon and it looks like the sim card swap did it. The girl there was nice and did it without hesitation for me.
She showed me in her computer how under my family account, it wasn't even fully showing my device or something like that. Not sure if it wasn't there at all or if it just didn't show that I had a 4g phone activated on the account...but I'm sure it was related.
Sucks to have to get a swap and still don't know what caused it or if its related to flashing roms, but at least it works! No issues since...

It is possible, but unlikely and no reasonable explanation, that your sim somehow got affected doing all the flashing and stuff.
Sent from my Nexus in Texas.

Galaxy S III fails to sent long SMS

Well, this is an odd issue and i'm sure many other have it because all of my friends with GS3's have this problem. I have a rogers GS3, my friend has a Telus and other videotron and multiple times a week, when we try to send a moderate or long sms (3 lines and more) the phones fails to send the message. This is very odd because i've tried everything from a factory reset, full odin wipe, different roms, and nothing works. I'm on CM10 M2 now and the problem is also there.
When i try to send a long sms, it fails, then i sent a short one right after, it works, then i copy and resetn the original one that failed and it faisl again. I pretty sure many of you have it because we have 3 different GS3 on 3 different networks and it happens to all of us
I tried looking around, i have not found much, maybe somebody has such problem and perhaps a solution?

This happened to me earlier this morning. No idea what can even cause an issue like this.

nobody??? im sure many people have this

I think this is based on all aosp roms.
I don't know if it's fact or opinion, but I always get the "sent" message after receiving the "not sent" error.
In other words, it seems like it still sends the whole text, but just throws you an error initially.
Can someone correct me if I'm wrong?

Well i can correct you wrong because i've tested it it does not sent the messages nor does it have anything to so with AOSP roms because i've used both AOPK and they both have the issue,

I send long sms no problem.. some in fact so. Long it automatically breaks them into two. What firmware are you on.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

First off this belongs in Q&A so I will move it
Second AOKP is also considered an AOSP type ROM
There should be an option in your mms app to split messages over 160 characters. Make sure it is checked.
On the Touchwiz ROMs that came with the SIII and all TW custom ROMs this is not an issue. This is a Touchwiz phone so changing your ROM to anything but that will have some bugs and require fixes and workarounds.
Friendly Neighborhood Moderator

Contact your carrier
Especially if you're having this issue on and off

Do other apps work? I use ChompSMS (fixes lots of annoying bugs in the TW SMS app) and I can send long messages fine.

kennyglass123 said:
F
On the Touchwiz ROMs that came with the SIII and all TW custom ROMs this is not an issue. This is a Touchwiz phone so changing your ROM to anything but that will have some bugs and require fixes and workarounds.
Click to expand...
Click to collapse
i have to disagree. I had like i said in OP, i tried ALL roms, stock, stock rooted, cyanogen and many other, this was an issue in all roms.

polish_pat said:
i have to disagree. I had like i said in OP, i tried ALL roms, stock, stock rooted, cyanogen and many other, this was an issue in all roms.
Click to expand...
Click to collapse
are you using a mms app other than what's provided with the rom? And are you able to send any messages at all? or does it fail to send only on long ones?
If you were on stock and still can't send any/long messages, check your apn settings and make sure it's correct for your provider, especially if you are installing roms (stock or custom) that are specifically developed for AT&T phones. From your profile I'm assuming you have a Canadian version.
Check the APN settings. If that's all correct, return the phone for a new one

all apn settings are fine and this is not an issue with the phone because like i said, it would be one hell of a coincidence if this happened to both of my friends with gs3s on different providers. Also i am using stock sms app and this only happens with moderately long sms, it doesnt always ahppen, its random

If it's intermittent, and it's not just you but also your friends, it sounds like a provider problem. From what I have been reading on different forums, it seems service in Canada has been sketchy because they're adding LTE towers everywhere.
I don't know if that's really the case, but all I can say is texting works well for me down here on the AT&T network, both on AOSP (which also includes AOKP as you were mistaken earlier) and stock-based ROMs, although I do get the error on AOSP based roms for long messages. I've asked my friends and they say they receive the whole message just fine.
Last thing I can think of is if you flashed a custom kernel and it messed with some of your drivers. I know KToons kernel has modified drivers, and you're supposed to flash the stock kernel provided in that thread if you're going back to stock. Try that and see if that fixes your problem.

yup, i've flashed ktoon kenel as i had major issues with faux kernel as per this thread: http://forum.xda-developers.com/showthread.php?t=1937476
i'll report back in a week to see if any different
thanks for you help

[Q] LTE Trouble with ATT after root/flash

Let me begin by saying that I've looked far and wide for answers, and solutions, but haven't found any that work yet. So I'd like to go through the process of what happened, and what my fix is really going to be.
- ATT GSIII Stock 4.1.2, was rooted using the CF Auto-Root Method.
- We installed CWM Touch recovery, and flashed the rooted stock image.
- This is immediately where we started seeing issues with LTE, etc. in a known-good LTE area. We were getting "G" and "E" from that point on.
- From here, I noticed that we had lost the IMEI (was set to 0), so I followed the process to get that restored using QPST.
- After the IMEI was back to normal, nothing got better. LTE wouldn't show up, etc.
- I checked into the APNs, and there were several, so I removed the ones not needed, and kept only the one that was correct. STILL no LTE.
- At this point, since we were going to AOSP anyway, we decided to flash Slim 4.2.2 Build 8. Had the same issues, so I verified APN, Network Modes, IMEI, etc. Everything is there that needs to be.
- Once in a WHILE, we get LTE in a known-good area for a few minutes, but most of the time it's "G" or "E". Calls drop, sound is bad, etc. We tried several of the baseband modems with no desired results.
What part of this process causes this to happen to the ATT GSIII? Is it the root method? Because we had this issues so early in the rooting/flashing process, I would think whatever happened there is still an issue with the phone.
The IMEI is correct, so I don't think that can be it.. or can it? Would calls, texts, data work with an IMEI that isn't correct?
Network Mode is correct: LTE/GSM/WCDMA
CDMA Subscription is set for NV (I know this is RUIM/SIM in VZW GSIIIs). Is NV Correct? I've seen some posts about fixing NV Data.. might this be the issue?
I really have nothing else I can think of. I've been a rooted-flasher for a few years now, and root a lot of phones. I had issues with my d2vzw along the lines of the issue I'm having with the d2att phone, but I was able to fix those fairly easily.
Now I've been reading an I know these issues occur when you flash a 4.2 AOSP build.. so maybe that's when it got really bad for us? But agian, I've gone through all of the check points, and it looks as if everything is in order.
I'm flat out of ideas..
Help? I'm willing to donate, compensate, etc. And if you happen to be in NYC, could even pay someone to help fix.
Many many thanks and internets ahead of time.

I am having the same problem as yours. Been a flashaholic since the beginning of this year. Tried various custom ROMs (CM, AOKP, PA, Rootbox, Revolt, PACman, JellyBAM, Carbon, Slimbean, LiquidSmooth; you name it). Currently I'm using (and happy with) Dirty Unicorn, however earlier last month I noticed that I have not been receiving LTE. Even worse, I can't get a better data speed than EDGE. I have to mention though that I have unlocked my phone and switched to T-Mobile. I'm not sure when I started experiencing this problem since I am very sure that I had LTE on my phone two months earlier. Like you, I also had to restore my IMEI after it turned to 0. I've tried going back to stock and unrooted but that also did not help. I really hope we can find what's wrong with our phones.

Can't Send SMS; Can Receive SMS/MMS & Send MMS

Hey guys,
I think I've reached the point where it's time to call in the cavalry and see if anyone around here is having the same issue; there appears to be a plague going around on the Verizon network, specifically in the Pennsylvania area, preventing people from sending SMS, but still receiving fine (and 4G works fine too, for the record). MMS still sends / receives fine, but I'm unable to send SMS. There are tricks to allowing a single SMS message to go through which involves toggling Airplane mode on / off every. Single. Time. People have also had success with turning 4G off completely, using the CDMA band after a reboot at which point they can send *several*, but still end up with the same issue.
The only solution I've read about that FIXED it is by reverting back to complete stock from VZW. Performing factory resets, using other ROMs, etc etc...doesn't work. I'd REALLY rather not do this and, frankly, would rather use 3G / toggle Airplane mode for texts than use Sense and get off of my ROM (http://forum.xda-developers.com/showthread.php?t=2560831).
People from other device forums on XDA are having the same problem; the ones I've seen that are active discussions are the Samsung Galaxy S III & IV. They're mostly CM ROMs *as well as* AOSP ROMs in general.
http://forum.xda-developers.com/showthread.php?t=2532414
http://forum.xda-developers.com/showthread.php?t=2658572
SIM card replacements are a no-go, and the recorded instances seem to be in the 717 / 570 area codes, mostly. Now I DO know that VZW released an OTA update for the One recently, and I'm relatively confident that would fix the issue, but I've no idea why. I'm thinking perhaps they dispatched new radios? I looked around a bit and couldn't find any flashable zips of radios extracted from the latest OTA, that's the next step I'll be trying once that download finishes.
So is anyone else having this issue? Any word on fixes?

The newest firmware from the latest OTA can be found in the 2nd post in this thread: http://forum.xda-developers.com/showthread.php?t=2485319
If you've already flashed the latest firmware then I'm not sure what to tell you... maybe ask your favorite rom developer to take a look at the latest OTA in regards to this issue?

If it has the stock rom and OTA update why not take it to the store and let them look at it. Something might be wrong with your account.

movieman999 said:
Hey guys,
I think I've reached the point where it's time to call in the cavalry and see if anyone around here is having the same issue; there appears to be a plague going around on the Verizon network, specifically in the Pennsylvania area, preventing people from sending SMS, but still receiving fine (and 4G works fine too, for the record). MMS still sends / receives fine, but I'm unable to send SMS. There are tricks to allowing a single SMS message to go through which involves toggling Airplane mode on / off every. Single. Time. People have also had success with turning 4G off completely, using the CDMA band after a reboot at which point they can send *several*, but still end up with the same issue.
The only solution I've read about that FIXED it is by reverting back to complete stock from VZW. Performing factory resets, using other ROMs, etc etc...doesn't work. I'd REALLY rather not do this and, frankly, would rather use 3G / toggle Airplane mode for texts than use Sense and get off of my ROM (http://forum.xda-developers.com/showthread.php?t=2560831).
People from other device forums on XDA are having the same problem; the ones I've seen that are active discussions are the Samsung Galaxy S III & IV. They're mostly CM ROMs *as well as* AOSP ROMs in general.
http://forum.xda-developers.com/showthread.php?t=2532414
http://forum.xda-developers.com/showthread.php?t=2658572
SIM card replacements are a no-go, and the recorded instances seem to be in the 717 / 570 area codes, mostly. Now I DO know that VZW released an OTA update for the One recently, and I'm relatively confident that would fix the issue, but I've no idea why. I'm thinking perhaps they dispatched new radios? I looked around a bit and couldn't find any flashable zips of radios extracted from the latest OTA, that's the next step I'll be trying once that download finishes.
So is anyone else having this issue? Any word on fixes?
Click to expand...
Click to collapse
Those area codes for all phones on aosp roms are not working right now. Since 2/20/14. Has nothing to do with HTC or their firmware. I'ts a bizarre Verizon 4G issue. I am in the 717 area code with a Note 2 with the issue. I have seen others with S4 and S3. Verizon is aware of the issue and is working with another XDA member to fix it. To date it's not resolved.

DreamFX said:
Those area codes for all phones on aosp roms are not working right now. Since 2/20/14. Has nothing to do with HTC or their firmware. I'ts a bizarre Verizon 4G issue. I am in the 717 area code with a Note 2 with the issue. I have seen others with S4 and S3. Verizon is aware of the issue and is working with another XDA member to fix it. To date it's not resolved.
Click to expand...
Click to collapse
Thanks DreamFX; I've been following this thread (http://forum.xda-developers.com/showthread.php?t=2658572&page=6) lately as they seem to be the most on top of it. I can't believe Verizon has let this issue go on for so long, but given that it seems to only be relevant to those of us with AOSP ROM's, I guess it makes sense. At least I'm still able to send texts, if not only through a silly process of toggling airplane mode on / off. Hopefully it gets resolved soon...

DreamFX said:
Those area codes for all phones on aosp roms are not working right now. Since 2/20/14. Has nothing to do with HTC or their firmware. I'ts a bizarre Verizon 4G issue. I am in the 717 area code with a Note 2 with the issue. I have seen others with S4 and S3. Verizon is aware of the issue and is working with another XDA member to fix it. To date it's not resolved.
Click to expand...
Click to collapse
movieman999 said:
Thanks DreamFX; I've been following this thread (http://forum.xda-developers.com/showthread.php?t=2658572&page=6) lately as they seem to be the most on top of it. I can't believe Verizon has let this issue go on for so long, but given that it seems to only be relevant to those of us with AOSP ROM's, I guess it makes sense. At least I'm still able to send texts, if not only through a silly process of toggling airplane mode on / off. Hopefully it gets resolved soon...
Click to expand...
Click to collapse
I'm getting this too, just started for me today from what I can tell. Driving me bonkers but, Airplane mode toggle totally works for me. :cyclops:
VZW SGS4 running AOSPA with 804 area code operating in Oregon.

dickenam said:
I'm getting this too, just started for me today from what I can tell. Driving me bonkers but, Airplane mode toggle totally works for me. :cyclops:
VZW SGS4 running AOSPA with 804 area code operating in Oregon.
Click to expand...
Click to collapse
Whoa, that's weird. I really thought it was isolated to the 717 area code. It's getting pretty crazy...I've been dealing with this for a few weeks now and my patience is running thin. Unfortunately it's not like we can just report this to VZW because all anyone would tell us to do is "restore to factory", which simply isn't a solution.

movieman999 said:
Whoa, that's weird. I really thought it was isolated to the 717 area code. It's getting pretty crazy...I've been dealing with this for a few weeks now and my patience is running thin. Unfortunately it's not like we can just report this to VZW because all anyone would tell us to do is "restore to factory", which simply isn't a solution.
Click to expand...
Click to collapse
Yup, I thought so too. Just cropped up between 10a and 11a PDT. Like you said MMS is fine, simply affects SMS. And yes, restoring stock is simply not an option. Going to TMobile, however, is totally an option that I'm considering more and more often......
EDIT: AND SMS began sending properly (without workaround) for me around 8p PDT last night, just tested and still ok. RESOLVED!
EDIT EDIT: Issue now persists....sadface =[
Sent from my SCH-I545 using Tapatalk

dickenam said:
Yup, I thought so too. Just cropped up between 10a and 11a PDT. Like you said MMS is fine, simply affects SMS. And yes, restoring stock is simply not an option. Going to TMobile, however, is totally an option that I'm considering more and more often......
EDIT: AND SMS began sending properly (without workaround) for me around 8p PDT last night, just tested and still ok. RESOLVED!
EDIT EDIT: Issue now persists....sadface =[
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
IM getting it now. but not exactly the same. phone freezes without warning and I have to toggle airplane mode and restart to get it to unfreeze. this happened after the last OTA update. I am going to a custom ROM until I don't read anything about this for a while