Had regular galaxy s4 from att since it came out, never did any rooting or anything, updating to kitkat Ota when it was released and had no issues until about a week ago. I did a factory data reset because of too much junk on the phone and wanted to reorganize a bit, backed up everything using kies 3 and ever since then my data/signal cuts out randomly everyday, all day long. The more I text I noticed the more it drops, and then goes from LTE to 4g and it'll stay that way until some random amount of time, disconnect again, back to LTE once in a while but mostly be 4G. I heard of some issues with the kitkat update causing various issues like this but don't understand how a simple factory reset and restore screwed it all up or if it's even that. Tried full format, reflashing entire stock firmware and has done absolutely nothing for remedying the problem. Is it possible it's a sim card issue?
dece870717 said:
Had regular galaxy s4 from att since it came out, never did any rooting or anything, updating to kitkat Ota when it was released and had no issues until about a week ago. I did a factory data reset because of too much junk on the phone and wanted to reorganize a bit, backed up everything using kies 3 and ever since then my data/signal cuts out randomly everyday, all day long. The more I text I noticed the more it drops, and then goes from LTE to 4g and it'll stay that way until some random amount of time, disconnect again, back to LTE once in a while but mostly be 4G. I heard of some issues with the kitkat update causing various issues like this but don't understand how a simple factory reset and restore screwed it all up or if it's even that. Tried full format, reflashing entire stock firmware and has done absolutely nothing for remedying the problem. Is it possible it's a sim card issue?
Click to expand...
Click to collapse
I have been having the same problems since I took an OTA update. LTE is very intermittent in places I know it is available and I randomly lose my cell connection for brief periods, which is a huge pain for SMS. I just flashed NB1 with ODIN and everything worked for the brief time before I updated to NC1 (LTE, no connection drop). When I updated to NC1 I started experiencing problems again. I subsequently tried flashing back to the NB1 modem to no avail
I tried ATT support at one point and they reset some stuff on their end (a while ago so I don't remember what) but that did nothing.
Anyone with any insight here would be my hero. This has been plaguing me since december.
Update: Tried re-flashing NC1 modem twice via ODIN with manual reboot. Still no LTE, not sure about connection drops yet.
Went to att store yesterday, thought maybe bad sim card, they replaced it and problem still persists... Looks like I'm getting the note 4 next month cause this is driving me crazy, so I guess I just need to put up with it until then.
dece870717 said:
Had regular galaxy s4 from att since it came out, never did any rooting or anything, updating to kitkat Ota when it was released and had no issues until about a week ago. I did a factory data reset because of too much junk on the phone and wanted to reorganize a bit, backed up everything using kies 3 and ever since then my data/signal cuts out randomly everyday, all day long. The more I text I noticed the more it drops, and then goes from LTE to 4g and it'll stay that way until some random amount of time, disconnect again, back to LTE once in a while but mostly be 4G. I heard of some issues with the kitkat update causing various issues like this but don't understand how a simple factory reset and restore screwed it all up or if it's even that. Tried full format, reflashing entire stock firmware and has done absolutely nothing for remedying the problem. Is it possible it's a sim card issue?
Click to expand...
Click to collapse
+2 to this issue. My wife and I both have the same problem as you've described, and it's gotten progressively worse with time. The worst part is that the phone seems to think that cellular connectivity is still there as I still have bars. However, data, phone and text capabilities are all dead. The only fix is a reboot, and it's short lived.
I've read on another forum that disabling 3G and 4G eliminates the problem, but then you're stuck with basically no mobile data...
Anyone with advice, I'm willing to experiment!!!
It's hard to believe no one else is seeing this problem, or attempting to resolve it...
Wiped x3, flashed MDB mode and Odin'd back to stock MDB ROM. Let sit for an hour, then flashed back to stock NC1 ROM & Modem. Modem hang in less than a day...anyone else have any ideas how to fix these modem hangs? I don't have any ideas left.
Got the same problem. Mine started happening on MK2, so I updated to NB1 then immediately NC1. No change at all. I was concerned that it was because I'd rooted and was running Xposed framework and a bunch of modules. I was about to flashback to stock, but after reading some of you folks issues, I won't bother.
Looks like an upgrade sooner than later is in order.
Related
Okay so I see reports spattered about the forum and I think we should gather them in one place.
I rooted my phone, flashed the new radio back to it, and then started experiencing a data lock - where my data would work for around 30 seconds and then stop - the only way to fix it was to make a phone call and get back off (which would earn me another 30 seconds or so) or airplane mode or a reboot. This happened with every ROM I tried.
I have a Revision 2 EVO, BTW.
So I flashed back to stock, did the OTA update... all was fine and dandy. Did the full root again today and now I have the same issue all over again.
I should note that I did not have this issue until doing the NAND and recovery flashes... basic rooting did not break my phone.
I do not have 4G in my area to comment on that but 3G is definitely breaking each time and I am wondering why.
So I recently updated to the OTA rooted 2.3.3 by clearing all data, sbfing back to 2.2 and then updating to 2.3.3 OTA rooted. I have noticed recently that every other morning or so my data connection is just gone. I can turn airplane mode on and off and it does not come back, wifi works fine. However if i disconnect from wifi I get no data and I can't make a call or send receive text messages until after I reboot, just wondering if anyone else has been experiencing this and if there is a solution or if I should just clear the data on the phone and see if the issue goes away.
That is not good. You may want to SBF again to see if that works
I have the same problem on my non-rooted droid x. data connection goes away and doesn't ever come back until you reboot. I've seen other people have this problem in a few other forums also...
Well I did a factory reset and install only launcher pro and google voice. Will use like that for a few days and see if it happens again.
HostileJava said:
So I recently updated to the OTA rooted 2.3.3 by clearing all data, sbfing back to 2.2 and then updating to 2.3.3 OTA rooted. I have noticed recently that every other morning or so my data connection is just gone. I can turn airplane mode on and off and it does not come back, wifi works fine. However if i disconnect from wifi I get no data and I can't make a call or send receive text messages until after I reboot, just wondering if anyone else has been experiencing this and if there is a solution or if I should just clear the data on the phone and see if the issue goes away.
Click to expand...
Click to collapse
I sorta had this issue last week -- mine was dropping from 3g to 1x in my daytime location --i am here everyday so I'm familiar with the speeds/signal strength for this area.
Also I had never had this issue... ever. I was on the .595 GB leak, but I sbf back to .340 (didnt root) and STILL had the issue. I did data and cache wipes in recovery while on .595 plus a factory reset even after the froyo SBF.
So nothing worked..... GB, Froyo, rooted, non-rooted, factory resets, data roaming disable ... it still would drop 3g for 1x. This was just out of the blue, I've had the phone since Dec. 2010
I thought it might be a tower issue, so I suffered with this nonsense for 3 days, knowing that VZW would likely fix tower issues in that time.
After additional research, I found those saying a battery pull would do the trick. Well heck, after all that angst and effort a simple battery pull did it !
Not one problem since. Try the Battery pull !
droidJW said:
I sorta had this issue last week -- mine was dropping from 3g to 1x in my daytime location --i am here everyday so I'm familiar with the speeds/signal strength for this area.
Also I had never had this issue... ever. I was on the .595 GB leak, but I sbf back to .340 (didnt root) and STILL had the issue. I did data and cache wipes in recovery while on .595 plus a factory reset even after the froyo SBF.
So nothing worked..... GB, Froyo, rooted, non-rooted, factory resets, data roaming disable ... it still would drop 3g for 1x. This was just out of the blue, I've had the phone since Dec. 2010
I thought it might be a tower issue, so I suffered with this nonsense for 3 days, knowing that VZW would likely fix tower issues in that time.
After additional research, I found those saying a battery pull would do the trick. Well heck, after all that angst and effort a simple battery pull did it !
Not one problem since. Try the Battery pull !
Click to expand...
Click to collapse
I'm having this occasionally as well.
Curious as to why a battery pull would do anything different than a reboot?
FWIW I'm on .596 rooted
Zaphod-Beeblebrox said:
I'm having this occasionally as well.
Curious as to why a battery pull would do anything different than a reboot?
FWIW I'm on .596 rooted
Click to expand...
Click to collapse
It isnt any different. I've had this happen a few times and it keeps coming back in normally bad signal areas, but not every time. I have also had random reboot when the phone is in my pocket, unlike froyo where the reboorts happened when I was doing something important. I suppose that is progress then.
Hello,
A few hours after I reboot my phone, it will act as though I've removed my SIM (emergency calls only, no text, no data). Restarting the phone fixes the issue for a few more hours, but it's quite annoying to have to turn my phone off and on so often. I'm rooted on MF3, and was running Google Edition 4.2.2 through SS when the issue first appeared, though I have since returned to stock and the issue still exists. Any suggestions?
Thanks,
DorkCat
I am having the same issue, did you ever get this sorted out? My phone is MDB running cm11. I hate to send the phone back... again. My camera crapped out on the first phone. I hate to send it back since I am sure I'll end up with MF3.
Thanks,
Travis
Hi guys, i know this is a common problem, but i have yet to find a solution to it. My S4 (Bell Canada, KOT49H.I337MVLUFNI2, completely stock unrooted) will drop the mobile network (both voice & data), and the only way to get reconnected to Bell is by rebooting my device. After a reboot I might be good for a few hours or for a few days but it always happens again. At first the mobile signal will grey out, then eventually turn to a circle with a line through it. In the network mode setting becomes blank and non-selectable.
Suggestions around the web include selecting WCDMA only, clearing the cache, factory resets, and reflash the full firmware package with Kies3 & Odin. Ive tried them all and the problem always inevitably returns.
Here are a few links to people with similar problems, but nobody seems to have a solution in any of these threads either:
https://community.sprint.com/baw/message/773419
http://forums.androidcentral.com/sa...fter-update-won-t-stay-connected-network.html
https://support.t-mobile.com/thread/68518
http://thedroidguy.com/2014/02/samsung-galaxy-s4-4g-wont-stay-connected-84465
http://community.koodomobile.com/koodo/topics/samsung_galaxy_s4_4_4_2_connectivity_issue
https://www.youtube.com/watch?v=GlHK11pE7kA
Other than returning it for a replacement under warranty, does anybody have any other suggestions to fix this? Thanks.
anyone?
Are you sure your problem isn't the same as the sim card removed problems? Because the symptoms sound the same in the effect they have, and what is required to temporarily fix it.
See here and here.
I've experienced the same problem, but it seems to have cleared itself.
It first started happening after the update to the latest Bell stock firmware.
I had read some people blaming it the Amazon app store as well as the Skype app. I had both installed, but have since removed Skype but can't say 100% that this is what solved the issue for me.
Sent from my SHIELD Tablet using XDA Free mobile app
I have the same problem, this is not the sim card removed problem, this is a bug in Android 4.4.2 because the problem was not present in 4.3 maybe the recent update to 4.4.4 solve this, has someone try out ?
FarmGeek4Life said:
Are you sure your problem isn't the same as the sim card removed problems? Because the symptoms sound the same in the effect they have, and what is required to temporarily fix it.
See here and here.
Click to expand...
Click to collapse
My SIM card is still in place and detected, the phone just disconnects from the network. After a reboot it will be fine sometimes for a few hours - sometimes a few days, but it always inevitably disconnects.
If you check any of the several links I posted you'll see there are hundreds (if not thousands) of people on all different carriers all experiencing the same problem.
emptyPD said:
I have the same problem, this is not the sim card removed problem, this is a bug in Android 4.4.2 because the problem was not present in 4.3 maybe the recent update to 4.4.4 solve this, has someone try out ?
Click to expand...
Click to collapse
I've had my device since Jan of 2014 and the problem only appeared in the last few months following the 4.4.2 update.
I'm having the same problem. It disconnects and reconnects again. Stays disconnected for about 2 mins. Happens like 12 times a day. I re enter the apn setting and still does it..it happens with every rom I flash. I've notices that it mostly happens when it switches from 4g lte to 4g. I'm on At&t 4.4.4
bump. anyone ever find a solution to this?
Edit 5: Gonna go ahead and declared this solved, the problem hasn't come back since I factory reset and reflashed MHC19I (not Q) from scratch. No more issues with wifi not autoconnecting or taking excessively long to connect, no more battery drain (got nearly 48 hours this weekend including a good amount of time spent in a poor/oversaturated service area at the Grand Prix), etc. Probably going to wait until the May update before flashing any OTAs.
Edit 4: Two days later and still seems to be working fine. I'm seeing some other issues on the April update (significant battery drain, slow wifi connect, etc.), so this morning I tried rolling back first to January (wouldn't get LTE) and now to March (fine so far). With the exception of keeping my media, I'm setting this up completely new, i.e. redownloading everything from the Play Store, to avoid any weirdness from restoring backups.
Edit 3: A factory reset done via TWRP (which retained my media) seems to have solved it for now. At any rate it's been acting normal longer than anything I've done before. This includes restoring my apps + their data via TitaniumBackup (but not system backups), reflashing SuperSU and otherwise getting my phone back to where it started. I've tested things that were known to cause it before like having wifi active but leaving my signal area and having it revert to cell data. The only issue I've noticed now is that wifi no longer seems to autoconnect when it's in range of my router. Not a huge deal but kind of annoying, if anyone has a fix for this I'd appreciate that too.
Edit 2: This issue is NOT resolved. The problem came back after working for a little while. Once the LTE fails the wifi will never reconnect on its own. It seems like everything still works except loading images from anything (reddit, instagram, etc.) and loading bookmarks. I can make google searches, download apps, go into reddit comments, go to instagram profiles I've never been to before, and so on. Is my device defective?
Edit: It appears that going through the motions of flashing the latest update (save for recovery.img and formatting userdata) has fixed the issue. This includes reverting to the stock kernel and flashing the vendor.img, which I hadn't done before. Wifi can be flipped off and on and will reconnect and there are no "!"s anywhere in sight. Strange considering I essentially went through the whole process minus the stock kernel and vendor.img, just out of order, with no effect.
Can anyone offer insight as to what piece of that process might have fixed this? It's not clear to me which pieces of the update are responsible for wifi and cellular connectivity besides the radio and kernel. Leaving the original post below in case anyone has anything to add or is going through this same issue. I'll update this post if the issue returns.
---
As of just this afternoon I'm suddenly getting a strange new issue that I can reproduce pretty consistently. I first noticed that my wifi signal was claiming to be connected but with no internet, and showed a little exclamation point next to it. I disabled wifi, and noticed the exclamation point jumped over to LTE. In both cases, I can still essentially use the connection. I disabled cellular data with wifi connected and could still browse the web, and likewise if I disabled wifi and the exclamation point was back on the LTE symbol. However, I notice some apps like Instagram will refresh posts but no longer load images, and reddit will load posts but not follow any links or load any images either.
Things I've tried:
-Flashed the 2.50 radio (down from 3.61)
-Flashed the MHC19Q system.img and cache.img
-Installed ElementalX kernel (at first it looked like it fixed the LTE issues, but really it just made the "!" go away; still seeing the same issues when I connect to wifi and then disconnect)
-Deleted and readded the nxtgenphone APN (I'm on AT&T)
-Tried to get into *#*#4636*#*#; I get "Connection problem or invalid MMI code."
-Cleared cache/dalvik in recovery (hey, you never know)
-Rebooted my router to make sure it's not an issue there; all other wireless devices on my router are fine
-Removed and reseated the SIM card
In all cases I can still send and receive texts and certain apps will continue to function about halfway, such as Instagram mentioned above. Switching airplane mode on and off doesn't help. Furthermore, once the wifi connection first gets the "!", it will no longer automatically reconnect as it doesn't find a working internet connection.
After an initial reboot it will appear to be fine; wifi connects automatically, no "!"s anywhere in sight, and everything seems to work. As soon as I disconnect from wifi, this issue starts. As mentioned, it will no longer reconnect to wifi and cellular data doesn't seem to work.
Anyone have any thoughts or suggestions as to what the issue may be? This started out of the blue this afternoon, I haven't made any changes to my phone since flashing the April image. My bootloader is unlocked and I'm rooted, and save for the ElementalX experiment (going to go back to the stock kernel) everything else is stock.
Any help is appreciated. If you need any more info, let me know.
Did your problem get resolved or did it come back. I'm having a number of problems on t-mobile since upgradingj to mhc19q
acathrow said:
Did your problem get resolved or did it come back. I'm having a number of problems on t-mobile since upgradingj to mhc19q
Click to expand...
Click to collapse
So far so good, the issue hasn't returned, although I'm really not liking the latest update. I'm considering rolling back (is that something I can do? I don't see why I couldn't) to January or so.
I'm still in limbo. T-mobile have been helpful but it's in Google Nexus support's hands and they have been less than responsive to say the least.
Next step is likely replacement device but in the mean time I just finished flashing 19i and will see if that has the same issues, then I'll try the previous build.
I'm kicking myself that I didn't check the version numbers I was on before applying April update. Ah well, lesson learned,
acathrow said:
I'm still in limbo. T-mobile have been helpful but it's in Google Nexus support's hands and they have been less than responsive to say the least.
Next step is likely replacement device but in the mean time I just finished flashing 19i and will see if that has the same issues, then I'll try the previous build.
I'm kicking myself that I didn't check the version numbers I was on before applying April update. Ah well, lesson learned,
Click to expand...
Click to collapse
Out of curiosity are you doing a full wipe before flashing different builds? I noticed in my case the issue didn't go away until I did a factory reset, which I think suggests something was corrupt or otherwise affected in the system partition. Since doing a factory reset (and now after doing a couple more) the issue seems to have gone away and I'm no longer having wifi/LTE issues - well, except for not getting LTE at all on the January update, so now I'm back on MHC19i.
Current status: My issue appears to be with t-mobile band 12, the new band that t-mobile is rolling out now.
It appears that the phone "prefers" band 12 to the older bands (like 4).
Rolling back to an image before band 12 was added (eg MDB08K from October) gives me back reliable LTE on band 4.
Sent logs to t-mobile and Google and waiting.