I have a very weird problem on my S3 and I have looked everywhere and I can't figure out what's wrong.
I have a stock unrooted S3 on 4.4.2. Recently I took the phone overseas and had it unlocked, I don't know quite how the person unlocked it, but when I got it back it was having a lot of problems. All my Data was wiped, but still unrooted but showing many errors. I was having an error every time I opened my contacts saying android.process.acore has stopped. I was also having trouble getting signal with a local sim card, at the time I thought it was some setting I didn't know about or that it was the network that was messed up. Then when I got home I continued to have with my at&t network, always showing no signal and no data, when I did have signal it would cut out in a few min and when I got Data it was only 2g.
So what I did was install a stock rooted rom that I had been using before, this rom took care of a lot of the errors but wifi doesn't work on it, so I had to install a kernel which was verson 3.4.0-g2d4cae8 ktoonsez, this took care of the wifi problem.
Then I looked around a lot for reasons that my network wasn't working. One potential problem was APN, I checked that and mine was correct. There was also a problem listed with IMEI and that was fine on my phone too. Then I finally found that sometimes you can reinstal NV items and that can fix your network issues. So I found a site that had NV items to fix LTE and flashed that on my phone through odin. That actually took care of my network issue! I can get network now and get LTE, luckily saving my phone from being completely useless.
Now I have a completely diff issue and I don't know if I'm missing something similar to that to fix it.
What happens is that I constantly only have 1 signal bar, then when I start making a call or send a text I all of a sudden have 4 or 5 bars. So I have signal, but somehow its not registering properly. I would be okay with this considering my phone is at least letting me make calls even though it takes a bit longer to connect, but the problem is that it's been heating up a lot and the battery has been dying 3 times a day when it used to last an entire day. Looking up this problem I found that this problem is common when you have no signal. Also when I think when I am closer to a tower then my phone has 3 bars most of the time and the battery lasts longer, aka when I was in downtown Houston I only had to charge my phone once during the day as opposed to 2 times.
Anyone have any Idea how I might be able to fix this problem. My mom had her phone unlocked the same way but she is still on official stock rom with root, and is having the same problem, so I'm pretty sure it was the unlocking process and something similar to the NV items. Maybe I needed to install a whole NV items file instead of just the LTE segment? Sorry this was so long, and maybe rambling. Let me know if you guys need any more information.
Related
So I'm having an issue that is starting to drive me nuts. I have 2 Defys. One is my work phone, one is personal. My work one has been fine for 2.5 months. This prompted me to get one for personal use. However within the last week I have started having issues with both of them randomly rebooting. Always within 10-15 seconds of each other. Work one is original rom, factory reset, unrooted. Personal one is rooted, .360 update, and a bunch of apps. On my to work and back home I can always get them to do this. I get a beep, no service notification, and then approx 2 minutes later they reboot. during this time they are extremely unresponsive. Already called TMobile thinking it was a tower issue, but all checks out well on their end. It's driving me nuts. Has anybody had this issue, or know how to solve it. I don't think its the phones. On wifi they run fine all day long.
Have you tried the newer uicc SIM? Was told by the pda team I should switch over. I told them I was experiencing a reception issue. Since both your phones have gone nuts at about the same time it's either service or aliens. You might try one sim swap and see if it helps.
Both of them are brand new sims right from the box. From what I've gathered they already are the newer sims.
Let me share my experience about random reboots. I had also put it up in here but didnt get much response.
I narrowed down after a lot of experimenting that the reboot happens because of one issue - "The phone tries to reconnect to data network while there is very low signal and suddenly goes into a boot"
It somehow boggled me for months on how this could happen only to me when none of the users in this forum had anything like that. I changed the phone too. But the reboot continues. I got an app called Shutupbattery which can automatically switch off data network when network strength is below a certain limit (i set it at -102dbm). This seems to have slightly impacted the rebooting process. I see some improvement but also not satisfied with this app. It still does not completely shut off the data network on the cut off value and hence the phone does manage to reboot again.
I am trying a few combinations of values and seeing if I can arrive at a conclusion. Let me know if this was useful. For me this is something like a deal breaker and I am feeling of giving up the phone or changing the service provider.
I can tell you for a fact that it has to do with signal strength and data. However 4 days after I discussed this with TMobile Tier 2 support, they dispatched techs to the tower and since then...no more issues. The few other towers I have had issues with I've done the same thing and all of a sudden the problem disappears. I've been very happy with the support. Better than ATT ever did. I suspect it has to do with their implementation of 4G. I've noticed when it does this I get a momentary connection to HSPA before the phone drops back to UMTS then GPRS. You can get to this menu bu going to *#*#4636#*#* . Otherwise call Tmobile.
I've been seeing this problem for a few weeks now, with several different ROMs, including the original rooted stock ROM now. In nearly all of my recent calls, I get disconnected one or more times with the message "Call disconnected" and a "Dismiss" button. I'm thinking that this is because of my EVO and not the other side, since usually if they accidentally hang up or something the call just ends without a message box. As far as I can tell, I have good reception (at least according to the bars), and this is happening at home, where I've not had the problem before.
Does anyone know what could be causing this? My wife's EVO is not rooted, and she does not seem to be having this problem. But then again, I've not had the problem until fairly recently either. I've tried updating my profile and PRL with each new ROM, but it doesn't seem to have made a difference. Anyone have any suggestions as to how to stop this from happening?
Go into the settings menu andbupdate both your PRL and your profile. That *should* help with reception related issues.
posting & replying via the XDA Premium app.
Unfortunately, I've tried both of those things. I just did some testing today, and it seems that my phone is unable to stay connected during a phone call for more than five minutes before disconnecting, even if I don't touch the phone and just leave it sitting on a table.
Any other ideas? As far as I know, I haven't ever flashed my radio away from its default (2.15.00.11.19), and I'm currently using the leaked stock gingerbread ROM (build number 4.12.651.1 CL41771 release-keys and kernel 2.6.35.10-gaa602b7 [email protected] #1).
Maybe it's time to unroot and contact Sprint?
You can try downgrading from 2.15.00.11.19 to 2.15.00.09.01. You can download it from http://www.mediafire.com/file/jyedjkp1bm5amwm/EVO_Radio_2.15.00.09.01.zip
Afterwards, go into recovery, wipe cache & dalvik cache then flash the zip. You will be taken to the radio update screen and appear to hang. don't worry or get impatient. After it is finished, you will reboot into recovery and see the words "clearing cache" at the top of the screen. Simply select reboot and then you will boot to your homescreen. The initial boot will take a tad longer since it will be rebuilding the dalvik.
Hmm... I'm hesitant to downgrade my radio because my wife has an EVO with the same radio version number and hers doesn't have this problem. Granted, she is not rooted...
I understand. I've downgraded and upgraded everything several times for testing purposes and troubleshooting purposes and have never had a problem. The only hing about flashing radios is patience and not to pull the battery. Anyway, you can always call Sprint and see if they can troubleshoot it for you from their end.
posting & replying via the XDA Premium app.
I would contact sprint @ 877-809-6696 (advanced tech supp). Ask them to push a full reprovision to your device. See if that helps any. I was having issues when when on the airave, I was unable to receive incoming calls. This corrected it. I did try all the other steps listed above without any success.
This is interesting. I unrooted to test things out before calling Sprint, and the problem went away. I was able to stay connected for an hour (where before I couldn't last longer than 10-15 minutes). Yay, fixed, right? So, I rooted again and didn't install any ROMs or anything, just rooted, and the problem came back.
So, I have a solution, but I don't like it very much because it means I need to stay unrooted. Anyone have any idea why simply rooting the phone with Unrevoked 3 (and doing nothing else) could cause calls to disconnect? I'd love to be able to root again, but I can't deal with a phone that randomly disconnects all the time.
I am interested in this as well as I am rooted using unrevoked and get disconnected as well. I do find that it mainly happens though talking to people who have service on AT&T.. Quite wierd. All I hear is a beep then disconnected. This happens when I first place a call and it rings once or twice then beep, disconnected...
This may not be related to rooting. I'm still communicating with Sprint about this issue, and along they way they replaced my phone entirely, and the problem is still happening. Very frustrating, but it makes it very clear that the problem actually has nothing to do with the hardware. I'm pretty sure there is some network configuration problem on their end now. I'm waiting to root my new phone until this issue has been resolved. It is killing me!
KingFunderberk said:
This may not be related to rooting. I'm still communicating with Sprint about this issue, and along they way they replaced my phone entirely, and the problem is still happening. Very frustrating, but it makes it very clear that the problem actually has nothing to do with the hardware. I'm pretty sure there is some network configuration problem on their end now. I'm waiting to root my new phone until this issue has been resolved. It is killing me!
Click to expand...
Click to collapse
So whats the final call on this ..?
Is it Rooting , Is it network .. i am too getting psyche with this .
I'm pretty sure it is not rooting. But I don't yet know for certain what it is. Sprint thought there might be something wrong with the antenna on my phone, but they had already replaced the phone, so I think that is unlikely. They gave me a femtocell range extender to use in my house. Basically, I plug it into my broadband connection, and it is like having a mini cell tower in my house, giving me a very strong connection. Sure enough, when connected to that, I haven't had any calls drop. However, my phone still sometimes doesn't connect to the femtocell and instead connects to some other tower for some reason. My wife's phone doesn't do this, so I still think there is something wrong with my phone. I may contact Sprint again about this. ...sigh...
What is your area some area evo don't work properly like on rahim yar khan in this time connection don't work properly some signal drop and some time up i sure after few day signal work properly then problems will be solve.
My phone EVO is doing this now as well. Has anyone heard/read a solution?
greg_99 said:
My phone EVO is doing this now as well. Has anyone heard/read a solution?
Click to expand...
Click to collapse
I am having the same issue, out of the blue. No problems up until a few days ago. I'm wondering if it is maybe an issue with a certain version of the Evo. I have a version 002. Thoughts?
Greg_99 any progress on what might be causing this issue?
I've been having a problem with receiving texts sometimes and I recently noticed that it happens with call apparently. The issue is that I'm texting people back and forth and then all of a sudden I wont receive messages for a long time (couple hours). At some point, someone's text message will push through all of the other ones all at the same time. Sometimes when I assume i'm having this issue, I will send a text to myself and it will push the other ones through as well. Recently though I was made aware that during this "outage", I also was not able to receive phone calls at all. The signal is strong at all times (3-4 bars). Also happens when I'm home all day and not changing locations when it will suddenly stop getting texts and calls. Does anyone know how to fix this issue? I restarted the phone and changed cell towers with the Airplane mode many times and the issue continues to happen at random times. It is really inconvenient. Suggestions?
Technical details: I use the stock 4.1.1 Rom that comes with AT&T S3. I do have LTE in my area.
And now it has happened 3 days in a row but at different times of day. This is a huge problem for me as I use my phone a lot. Any help would be appreciated
You still have your IMEI number via settings -> about phone -> status?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
ARPLEMODE
TRy making sure yiur not in airplane mode. i was stuck in airplane for a week ._____________.:cyclops:
That's weird. Re-seat your SIM card, if that doesn't do anything then take a trip to your nearest AT&T store/dealer and have them swap out your SIM card and see if it still occurs after that.
I had a similar problem a while back and it happened to be a network problem with my carrier. Gave them a call and all is fine now.
Sent from my SGH-I747 using xda app-developers app
fafik90 said:
I've been having a problem with receiving texts sometimes and I recently noticed that it happens with call apparently. The issue is that I'm texting people back and forth and then all of a sudden I wont receive messages for a long time (couple hours). At some point, someone's text message will push through all of the other ones all at the same time. Sometimes when I assume i'm having this issue, I will send a text to myself and it will push the other ones through as well. Recently though I was made aware that during this "outage", I also was not able to receive phone calls at all. The signal is strong at all times (3-4 bars). Also happens when I'm home all day and not changing locations when it will suddenly stop getting texts and calls. Does anyone know how to fix this issue? I restarted the phone and changed cell towers with the Airplane mode many times and the issue continues to happen at random times. It is really inconvenient. Suggestions?
Technical details: I use the stock 4.1.1 Rom that comes with AT&T S3. I do have LTE in my area.
Click to expand...
Click to collapse
It happend to me too. I went to att store and get new sim. No problem for last 15-20 days. Looks like i got stronger signal too.
Just to give anyone interested in this an update:
I went to the AT&T store today and told them my issue so they told me to go to the nearest AT&T device support center (which was really far away). People over there told me they heard about this issue many times over the past couple of months. The guy working there had a S3 and said he has the same problem. They received an email from the higher-ups this morning specifically talking about this random outage thing I have and that they are currently working on it. They were told to not exchange phones or sim cards because of this since it wont help. The issue involves a combination of Network and Jelly Bean software problems and happens on all new LTE devices that have Jelly Bean from AT&T. They told me to check periodically if there is a solution.
I guess I just gotta wait. Unless someone recommends a ROM that is not based on the latest AT&T jelly bean?
Bumping it up, both me and my wife have had this happen. From what im read its a pretty widespread deal.
Anyone know of a work around at least until they fix it?
Keep us updated
Same problem here - switched from Verizon to AT&T last month and started noticing this problem a few weeks ago. Back then a Google search didn't find much on it, but this thread looks promising.
Just to add my two cents: I'm on a rooted S3 with task650's AOKP (4.2.1) build 12.23.2012 (link). Made sure to flash the modem for my phone (I747UCLI5 from here). Problem: phone randomly won't receive calls or texts. Sometimes calling someone will fix it.
I read somewhere that on AT&T, calls and texts are received over 3G and sometimes phones have difficulty switching from 4G. Anyone know if this is true?
Do a full wipe /system, /data, /cache, /dalvik cache. And your problems should be gone 9 times out of 10 that's usually everybodys problem
Sent from the scary door....
fafik90 said:
I've been having a problem with receiving texts sometimes and I recently noticed that it happens with call apparently. The issue is that I'm texting people back and forth and then all of a sudden I wont receive messages for a long time (couple hours). At some point, someone's text message will push through all of the other ones all at the same time. Sometimes when I assume i'm having this issue, I will send a text to myself and it will push the other ones through as well. Recently though I was made aware that during this "outage", I also was not able to receive phone calls at all. The signal is strong at all times (3-4 bars). Also happens when I'm home all day and not changing locations when it will suddenly stop getting texts and calls. Does anyone know how to fix this issue? I restarted the phone and changed cell towers with the Airplane mode many times and the issue continues to happen at random times. It is really inconvenient. Suggestions?
Technical details: I use the stock 4.1.1 Rom that comes with AT&T S3. I do have LTE in my area.
Click to expand...
Click to collapse
I had this same problem except it would only happen on WiFi.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
thatsupnow said:
Do a full wipe /system, /data, /cache, /dalvik cache. And your problems should be gone 9 times out of 10 that's usually everybodys problem
Sent from the scary door....
Click to expand...
Click to collapse
Tried that no go, plus its on 2 different phones.
Found some more info and ended up adding anothe APN and chaning some info in it seems good now.
mrmooney said:
Tried that no go, plus its on 2 different phones.
Found some more info and ended up adding anothe APN and chaning some info in it seems good now.
Click to expand...
Click to collapse
Care to share what you did that fixed it?
fafik90 said:
Care to share what you did that fixed it?
Click to expand...
Click to collapse
Yeah more info here.
http://forums.att.com/t5/Android-Di...ing-Calls-Phone-issue-or-Android/m-p/3404809#
Seems to still be working fine.
I started a thread on this also and just yesterday received some info from AT&T tech.
http://forum.xda-developers.com/showthread.php?t=2123974
guys,
it is an ATT issue,
here is a temp solution for a fix:
1) With phone on, take off back cover and press your SIM card so it releases from the spring. It won't come all the way out as it's blocked by the battery. This seems fine - I didn't bother trying to force it out as I didn't want to break anything...
2) Once you see the message that the SIM card is removed, go to the dialer and dial *#2263#
3) You should see a menu with band selections. The current setting is "Automatic". If you switch to "GSM All", you will be EDGE (2G). If you switch to "WCDMA All", you will be on HSPA+ (3G, though AT&T and others call it 4G).
4) Press the SIM card back into place until it clicks. For whatever reason the phone will not recognize it until you reboot. Upon reboot you should see your new setting in effect
please see, post, comment here:
http://forums.att.com/t5/Android-Di...ls-Phone-issue-or-Android/td-p/3270741/page/3
T mobile Samsung Galaxy Note 2 sgh-t889
I rooted and installed a jedi rom about a year ago. In December my cell signal started getting spotty. I reverted to stock 4.1.2. Thankfully I was able to use my phone on wifi calling and that worked for a while. I replaced my antenna cable because it had a kink. The cable I got came with a new charging port which oddly went bad shortly after changing the cable, so I replaced that too.
Later the phone started having other issues, trouble playing back audio, it started skipping like a cd player. Then wifi would work but if I left the wifi network it would freeze the wifi signal requiring reboot to disconnect from the old network, cycling wifi alone wouldn't work, didn't ever turn off. Somewhere near this time wifi calling wouldn't even produce enough strength to make a phone call. Would sound like bad signal.
Then yesterday wifi wouldn't turn on after a reboot. Looking it up I found a suggestion to take out battery, sim card and sd card then hold the power button for 30 seconds. This worked and the post said something about it being caused from undervolting. I decided to start hacking at the phone more figuring how much worse can it get?
I started with a benchmark test, and when I compared my results to noye 2 listed on antutu the only major difference was ram, which I scored 660 about half what it should be.
Everything else was within a few hundred.
I updated to 4.3 stock with firmware from samfirmware (something like that) and had my first phone call in months!
But then it lost signal again. Then wifi again.
Deciding to keep going I tried rerooting, failed, finally got philz bootloader and new jedi master x 4.3. Installed that and had selinux issue finally solved that now wifi juat stopped being able to turn on. Tried power button trick, didnt work. Wifi still wont turn on and mobile networks still dont work.
I wrote this offline then tried wifi again and it worked.
Anyone have any idea what's going on? Anything I could fry to fix this?
Ok so suggested posts when I posted is leading me to try things. I have an empty efs folder. I just wanted this posted due to signal issues atm.
I have an old old nandroid im going to try restoring atm
So my old nandroids didn't work, so I went to my backup after this happened. I still have an empty efs folder, and no backup. Wifi is more steady however. I've tried numerous things and cannot seem to recreate any of the files.
I found some random files in the efs folder when using root explorer, but no nv data.
Nothing is being generated on reboot or rom flash except the folder structure.
Under the status in my phone my IMEI number is intact.
I'm still under the impression it's missing files in my efs folder, but I've also come across some posts stating that some phones don't have an nv data bin file?
Can anyone point me in the right direction? It seems like every google search of a term ends in failure, and a new term to search.
Hello all!
I am having constant data issues all day where I go to use an app that needs it, it says that no data connection can be found or something. I turn the radio off, turn it back on and then it works. It's a good work-around but it does get very annoying. I've tried multiple 4.4.2 roms but no avail. I tried a different kernel but I couldn't even use the phone. Any ideas?
Same for me; I'm rooted now but it happened before root and after the JB ota updates. Annoying but otherwise I love this phone
I think this has been a known issue since ICS (I could be wrong though).
If anyone knows a fix that would be cool (I have GSM google play gnex)
My issues started late last night, lost data connection and it didn't come back. On my way home, it connected then lost again at home. Went to Verizon today and they couldn't figure it out, said possibly the radio is taking a crap.
On my way to work, it connects then gone. I tried flashing the radio, pulled battery, booted without sim, formatted cache and delvic. I have tried everything and think it's the end of the line for it
I've been rooted since the day I got it and had the issue once a while back but it straightened out and has been great since.
Certain CyanogenMod ROMs have trouble with the Network Modes sticking. Which carrier are you using? For my carrier, I had to have the correct APNs set to get 4G and MMS working. It might be that this is the problem in most cases, especially when the phone switches between 4G and 3G in spotty areas.