Data doesn't come back on even after leaving a dead zone

Data doesn't come back on even after leaving a dead zone - Verizon Samsung Galaxy S III

So where I live has solid 4G, but, once in a while, I'll go into an area with no data. When I leave the dead zone and come back to my house, the data stays cut off. I've tried dirty flashing the ROM over it again, but that doesn't help. The only thing that has worked so far is to reflash the ROM after wiping everything. If it only happened once in a while, it'd be fine, but I go into the dead zone approximately once a week, so it becomes a real hassle.
Is this common? It's been happening on the Synergy ROM. I would just use Hyperdrive since it has almost the same features, but I've just been getting much better battery life and charging times with Synergy.
Is there a way to fix this? I've been thinking and the only thing I can come up with is when I flash a ROM after wiping, it takes a few seconds to activate my LTE. If there was a way to repeat that process without wiping, I think it'd work.

Related

[q] no signal!!!

Guys I'm having an extremely frustrating issue. Anytime I flash a ROM, it'll work great for a little while, but then sometimes when i reboot, it'll say no signal, and then my phone thinks it's in airplane mode. I try to get out of it, but it won't. Then randomly it'll get signal, but the phone will be so slow and laggy, and then it goes back to no signal and no more lag. I've been using Infused ROM and usually that one is okay, but sometimes I've had to reflash to get it fully working. Lately I switched to SensatioN ROM using Hellraiser, and this one has given me trouble every single time. I've reflashed about 5 or 6 times, and even went back to stock. Any idea what is going on?!?

bgree15 said:
Guys I'm having an extremely frustrating issue. Anytime I flash a ROM, it'll work great for a little while, but then sometimes when i reboot, it'll say no signal, and then my phone thinks it's in airplane mode. I try to get out of it, but it won't. Then randomly it'll get signal, but the phone will be so slow and laggy, and then it goes back to no signal and no more lag. I've been using Infused ROM and usually that one is okay, but sometimes I've had to reflash to get it fully working. Lately I switched to SensatioN ROM using Hellraiser, and this one has given me trouble every single time. I've reflashed about 5 or 6 times, and even went back to stock. Any idea what is going on?!?
Click to expand...
Click to collapse
My first guess would be a hardware defect. Try a complete return to stock (and STAY stock), including a wipe/factory reset from the Settings screen and see how it performs. If the signal is still wacky - time for warranty service.

Hey everyone, thanks for looking at this and hopefully helping me out. I'm new to rooting my phone and installing new roms and stuff, but I researched about as much as I could for about a week before I even rooted.
Now I've moved on and installed a new rom (CM7). Before installing I used clockwork and formated the /system, /data, /cache, and dalvik. At first everything was ok, but after about 15 minutes it turned off. I read up on battery problems, so kept my phone plugged in all weekend (got up to 4.196V-ish, with 0mA in or out) then deleted the battery file, rebooted, unplugged the phone and let it drain completely (even while it still had a charge it would turn off randomly but I figured it would be ok). After it was completely drained I completely charged it again and it still randomly turns off.
At first I thought maybe it was just the rom, but no one else seems to have the same problem as me (that I can find), so I downloaded an ICS rom to try that. Same problems. So far I have done the following to try and find out WTF is going on...
Installed Elixr to see battery drainage (sitting at main screen doing nothing its roughly -8mA, but right after boot or opening a program it jumps to -300mA to -480mA)
Done NUMEROUS battery pulls (with and without deleting the battery config file)
Switched ROMS
Any help would be amazing
PS: Before rooting or flashing a new mod my phone would shut off on its own, but only once a week, maybe. Now it turns off as soon as I unlock my sim card. However, it doesn't turn off at all if I have it plugged in.

spcclark said:
Hey everyone, thanks for looking at this and hopefully helping me out. I'm new to rooting my phone and installing new roms and stuff, but I researched about as much as I could for about a week before I even rooted.
Now I've moved on and installed a new rom (CM7). Before installing I used clockwork and formated the /system, /data, /cache, and dalvik. At first everything was ok, but after about 15 minutes it turned off. I read up on battery problems, so kept my phone plugged in all weekend (got up to 4.196V-ish, with 0mA in or out) then deleted the battery file, rebooted, unplugged the phone and let it drain completely (even while it still had a charge it would turn off randomly but I figured it would be ok). After it was completely drained I completely charged it again and it still randomly turns off.
At first I thought maybe it was just the rom, but no one else seems to have the same problem as me (that I can find), so I downloaded an ICS rom to try that. Same problems. So far I have done the following to try and find out WTF is going on...
Installed Elixr to see battery drainage (sitting at main screen doing nothing its roughly -8mA, but right after boot or opening a program it jumps to -300mA to -480mA)
Done NUMEROUS battery pulls (with and without deleting the battery config file)
Switched ROMS
Any help would be amazing
PS: Before rooting or flashing a new mod my phone would shut off on its own, but only once a week, maybe. Now it turns off as soon as I unlock my sim card. However, it doesn't turn off at all if I have it plugged in.
Click to expand...
Click to collapse
Well, if you were having this issue before the rooting took place, this very well may be hardware related. There are a few things I recommend before the dreaded unroot and send back to manufacturer route (assuming the phone is under warranty still). It's been proven or at least shown that battery calibration (the whole charge to 0Ma and then fully discharge and then recharge) is a pipe dream.
I would first say find out if the CM7 ROM you're using is OCing or UVing, while you may see some people OCing to 1.3 or higher and UVing -75, not all phones are created equal in capabilities and some phones will randomly freeze/turn off if they don't like your OC and UV settings. I would also suggest flashing a different ROM to see if this problem persists. Cleardroid is what I recommend just to get an idea if it is in fact a OC or UV problem as I believe cleardroid is set up to default stock settings.
You can also try a new battery, I have heard/read/seen that bad batteries can cause reboots. Again though if this was an issue you were sometimes experiencing before, you may have hit the tip of the iceberg on a hardware issue and its finally starting to show now. Hope this helps.

Leave the charger plugged in. If it doesn't reboot then that will let you know most likely it is the battery.

Agoattamer said:
Leave the charger plugged in. If it doesn't reboot then that will let you know most likely it is the battery.
Click to expand...
Click to collapse
That was my thoughts exactly. However, if the ROM or kernel or whatever is set to shut off the phone at a certain reading of discharge from the battery, ie -500mA, this could also be the problem.
I thought it could have been a problem with the phone as well, but before it would shut off on its own MAYBE once a month. 90% of those I attributed to overloading the phone, closing facebook, opening the internet, starting to load a webpage then open a new txt I just recieved while the phone was still vibrating type things.
Now it still feels like it's just quitting on me, it never turns off while the screen is locked or while its charging. So far after the new ROM it has shut off when I place a call, when I receive a call, clicking on a notification, opening the messaging app, clicking download in the market, and my favorite when I unlock it from sleep.
I will download a different rom right now and try it. Just to double check this is what I've been doing to install a new rom... I boot my phone into recovery (vol- and power), go to recovery from the boot screen (opens clockworkmod), scroll down to mounts and storage, have it format /system, /data and /cache, go back to wipe data/factory reset, then install zip from sdcard, select the rom and go... I know some roms require inspiremod, should I still install this if I'm USING an inspire??
Thanks for the input guys, I really appreciate it

If it does turn out to be the battery or you just decide to get a new one to test it out. I recommend these, they are awesome and the only thing anyone should try besides HTC factory replacements. Good luck and I hope this works out for you.
Anker Batteries

i only skimmed this. but cleaning battery contacts can help also check the side door, sometimes that can cause issues as well. air can out everything and clean metal contacts with rubbing (ipa) alcohol.

So I installed cleardroid. Once again everything worked fine for the first 10-15 minutes and then the shutdowns started again, always when making the phone do something (unlocking, clicking a notification, opening a program, etc) but never when the phone is charging.
I'll clean off every bronze or gold contact I can find but I think I might be fighting a lost cause lol. Three different ROMS, all with the same problem leads me to believe its a hardware issue. Since all the chips in these phones are all small and use multilayer boards I won't be able to replace anything myself so I see a new phone in my near future.
Thanks guys!

If it doesn't do it when its chargeing then it is the battery. I had bought my inspire from someone and it was having those issues ordered a new HTC stock battery from newegg for like $12 and has been working perfectly since then and honestly if you want the best battery rom absolution is the rom you should check out. It's a non sense rom but again I'd just buy a new battery. I had mine timed it'd reset at 92% 74% and 49% xD
Sent from my Inspire 4G using xda premium

spcclark said:
So I installed cleardroid. Once again everything worked fine for the first 10-15 minutes and then the shutdowns started again, always when making the phone do something (unlocking, clicking a notification, opening a program, etc) but never when the phone is charging.
I'll clean off every bronze or gold contact I can find but I think I might be fighting a lost cause lol. Three different ROMS, all with the same problem leads me to believe its a hardware issue. Since all the chips in these phones are all small and use multilayer boards I won't be able to replace anything myself so I see a new phone in my near future.
Thanks guys!
Click to expand...
Click to collapse
hmm, I would say try a new battery before getting a new phone. Worst case scenario is that you spent $15 to learn you need a new phone as opposed to spending $100+ on a new phone...this is of course assuming you want to keep the inspire and not just looking for a reason to get upgrade ahaha

I agree. It still sounds like a battery issue.

I would agree this definitely sounds like an internal short in the battery. Sounds like it's shutting off whenever it gets a significant load on it. Try a new battery first.

I had a similar issue though I was tweaking the CPU. Learned my lesson.
Sent from my Inspire 4G using XDA App

Yeah, Id bet money that its a bad battery. I had this same exact issue with my Inspire. If it shuts off more in low reception areas but it isn't shutting off when plugged in, its definitely the battery. I would try to find someone with an Inspire and try switching them batteries and see if it stops.

If I tried to use the flash with my camera, the phone would shut off. My phone would randomly reboot or turn off. ATT told me they had "some" bad batches of batteries. My phone was still under warranty so ATT sent me a new battery. All the problems went away!

The battery door on the Inspire becomes wonky the more you open it, I was having a problem like yours, new battery and new door has me going good.

Mobile data failures, but IMEI is fine!

This started when my phone wouldn't come on when pressing the power or home buttons. I pulled the battery, put it back in, and mobile data didn't work. About Phone showed an IMEI and everything else, but didn't know my phone number.
Reinstalling, everything seemed fine. It knows my number every time now, at least. This is where the problem has been each time. It'd be fine, but each time I put CM10 on it seems to gradually break again.
When I went back to my stock Nandroid backup, restored to "out of the box" stock, and then put it through all the paces again to get to CM10, everything was fine from last night up to midday today. LTE went, then 3G went. Now I'm going back to my stock Nandroid.
Where should I look to start debugging this? Everything seems fine when I go through About; the IMEI and everything else are there, and so is my phone number.
Thanks!
Edit: A last ditch fresh install of CM10 didn't work, but the stock rom does. This seems to place it on CM10, as long as data on the stock one doesn't go out.

coldcaption said:
This started when my phone wouldn't come on when pressing the power or home buttons. I pulled the battery, put it back in, and mobile data didn't work. About Phone showed an IMEI and everything else, but didn't know my phone number.
Reinstalling, everything seemed fine. It knows my number every time now, at least. This is where the problem has been each time. It'd be fine, but each time I put CM10 on it seems to gradually break again.
When I went back to my stock Nandroid backup, restored to "out of the box" stock, and then put it through all the paces again to get to CM10, everything was fine from last night up to midday today. LTE went, then 3G went. Now I'm going back to my stock Nandroid.
Where should I look to start debugging this? Everything seems fine when I go through About; the IMEI and everything else are there, and so is my phone number.
Thanks!
Edit: A last ditch fresh install of CM10 didn't work, but the stock rom does. This seems to place it on CM10, as long as data on the stock one doesn't go out.
Click to expand...
Click to collapse
Im currently running CM10 and expereiencing the data drops as well though it only happens when I am at work in a low signal area. Once I walk outside into 4g I am fine and it does not drop data.

The data drops on CM10 are normal, I have read about them in earlier unofficial builds of it, but the nightlies we have now do in fact have a much better connection than prior builds. It is just something that the CM team has been working on and improving and probably will until a stable build is released. Most of the time though a data drop or signal drop (I have had a couple of these) can be fixed by turning airplane mode on and off or simply by rebooting the phone.

[Q] Screen randomly goes black

I've been having this problem starting the last couple of days. I'll be using my phone, and all of a sudden the screen turns off and nothing short of a battery pull will turn it back on again. Sometimes it happens when I'm not using it at all too. I'll pull it out of my pocket and get nothing. Do a battery pull, and everything's fine again until the next time it happens. Never had this problem before, but in the last two days it has happened 7 times. It even happens when it's plugged in. The LED indicator that is normally lit up when it's charging will go out. Unplugging it and plugging it in seem to have no effect. No sounds, nothing.
I'm running Jellybeans 4.1.2 Rom, with TWRP. Today I ran a backup, cleared and wiped data, fresh install, recovered backup and still having the problem. Should I try a clean install without recovering the backup? Could that have anything to do with it? Any other ideas on what to try or what the problem could be?

If you've been running the same ROM this whole time and it just started out of the blue, I don't really think it would be ROM related. It might be hardware related.
I suppose the only real way to test if it is ROM related is to ODIN back to stock and see if it still happens. If it does keep happening once returning to stock you could probably get it swapped out by Verizon.

BattsNotIncld said:
If you've been running the same ROM this whole time and it just started out of the blue, I don't really think it would be ROM related. It might be hardware related.
I suppose the only real way to test if it is ROM related is to ODIN back to stock and see if it still happens. If it does keep happening once returning to stock you could probably get it swapped out by Verizon.
Click to expand...
Click to collapse
I've been running the ROM a lot longer than I've been having the problems, so I suspect you're right. I've had the phone for over 2 years now, so there's no warranties anymore. If it really is a hardware problem I'm probably looking at a new phone.
I'll try going back to stock though and seeing if it changes. Thanks!
Update: I just flashed did factory reset and flashed back to stock, but can't even get through initial setup before it goes black...guess it is hardware.

Frequent Reboots. Please Help

I have been using Cyanogen for at least the past year. In the past I have had trouble with things like random reboots, maps crashing during navigation, etc. Because of this I switched to just running the milestone releases for the past six months or so, and that has worked reasonably well. Its still way buggier than stock, but I put up with it for all of the nice features and what not.
Lately though reboots have become more and more frequent even though I hadn't changed anything. I had been running M9 for the past month with no real problems and then last night it decided to just go into a boot loop. I tried pulling the battery, clearing the cache, clearing dalvik, nothing worked. Eventually I just let the thing boot loop all night long and when I woke up it was finally booted.
Then this afternoon it did it again for a short period of time (3 or 4 minutes). When it came out I decided to download the newest, M10. It took several tries to actually flash it because the phone would reboot iself while in the middle of the wipe, or the flash, etc. But I started the wipe/flash process from the beginning every time to make sure I had a clean flash and eventually I got all the way through. But now it is at a point where it will boot, sit there for 2 or 3 minutes (I don't even touch it), and then reboot.
I'm hoping someone can help. I'm holding onto my unlimited data for dear life... I don't want to have to get a new phone. But re-flashing doesn't fix the problem so I really don't know what to do.

I
demarcmj said:
I have been using Cyanogen for at least the past year. In the past I have had trouble with things like random reboots, maps crashing during navigation, etc. Because of this I switched to just running the milestone releases for the past six months or so, and that has worked reasonably well. Its still way buggier than stock, but I put up with it for all of the nice features and what not.
Lately though reboots have become more and more frequent even though I hadn't changed anything. I had been running M9 for the past month with no real problems and then last night it decided to just go into a boot loop. I tried pulling the battery, clearing the cache, clearing dalvik, nothing worked. Eventually I just let the thing boot loop all night long and when I woke up it was finally booted.
Then this afternoon it did it again for a short period of time (3 or 4 minutes). When it came out I decided to download the newest, M10. It took several tries to actually flash it because the phone would reboot iself while in the middle of the wipe, or the flash, etc. But I started the wipe/flash process from the beginning every time to make sure I had a clean flash and eventually I got all the way through. But now it is at a point where it will boot, sit there for 2 or 3 minutes (I don't even touch it), and then reboot.
I'm hoping someone can help. I'm holding onto my unlimited data for dear life... I don't want to have to get a new phone. But re-flashing doesn't fix the problem so I really don't know what to do.
Click to expand...
Click to collapse
I don't know why your having such an issue with cm. Which is odd because I'm running a rom that's CM based and works fine. I'd say maybe try another rom if for nothing other than to see if CM is truly the issue.
I praise you for having the unlimited data still, I wish I would be been smarter and kept mine because there are months where I'm a little too close to that sad but lack of data with 2gb
And my hometown is Syracuse NY as I see your city is there. I miss the cuse but not the loudness of the city
From my Wicked S3 on SOKP

Pull a logcat or use a tool like https://play.google.com/store/apps/details?id=com.tortel.syslog to do this for you. then after the phone reboots itself, run syslog and examine the last_kmsg and logcat to see what the obvious errors/issues are.
I too have noticed google maps crashing, camera unable to connect, random reboots, file system errors, sluggishness, etc more lately with my G3 too. Wonder if some aspects of the hardware are failing...

BSOD2600 said:
Pull a logcat or use a tool like https://play.google.com/store/apps/details?id=com.tortel.syslog to do this for you. then after the phone reboots itself, run syslog and examine the last_kmsg and logcat to see what the obvious errors/issues are.
I too have noticed google maps crashing, camera unable to connect, random reboots, file system errors, sluggishness, etc more lately with my G3 too. Wonder if some aspects of the hardware are failing...
Click to expand...
Click to collapse
I solved the problem on my S3 with the camera. Freeze the system. Default and run another app, I'm on 4.4.4
From my Wicked S3 on SOKP

ShapesBlue said:
I solved the problem on my S3 with the camera. Freeze the system. Default and run another app, I'm on 4.4.4
Click to expand...
Click to collapse
You mean freeze the stock camera and use the Google camera instead?
Yea, when the camera is broken, neither app can connect until phone rebooted. Already tried many a time.

BSOD2600 said:
You mean freeze the stock camera and use the Google camera instead?
Yea, when the camera is broken, neither app can connect until phone rebooted. Already tried many a time.
Click to expand...
Click to collapse
Yes freeze stock camera. I'm using focal and it works fine but the stock camera won't work at all
From my Wicked S3 on SOKP

demarcmj said:
I have been using Cyanogen for at least the past year. In the past I have had trouble with things like random reboots, maps crashing during navigation, etc. Because of this I switched to just running the milestone releases for the past six months or so, and that has worked reasonably well. Its still way buggier than stock, but I put up with it for all of the nice features and what not.
Lately though reboots have become more and more frequent even though I hadn't changed anything. I had been running M9 for the past month with no real problems and then last night it decided to just go into a boot loop. I tried pulling the battery, clearing the cache, clearing dalvik, nothing worked. Eventually I just let the thing boot loop all night long and when I woke up it was finally booted.
Then this afternoon it did it again for a short period of time (3 or 4 minutes). When it came out I decided to download the newest, M10. It took several tries to actually flash it because the phone would reboot iself while in the middle of the wipe, or the flash, etc. But I started the wipe/flash process from the beginning every time to make sure I had a clean flash and eventually I got all the way through. But now it is at a point where it will boot, sit there for 2 or 3 minutes (I don't even touch it), and then reboot.
I'm hoping someone can help. I'm holding onto my unlimited data for dear life... I don't want to have to get a new phone. But re-flashing doesn't fix the problem so I really don't know what to do.
Click to expand...
Click to collapse
These symptoms could indicate a sticky power button. Try knocking it lightly against the corner of a table to jar whatever is making it stick loose.
It doesn't sound software related, especially since it rebooted while in recovery. If you hold the power button down long enough in recovery it will reboot, which makes me think you just have a sticky power button. It's happened to me before.

BattsNotIncld said:
These symptoms could indicate a sticky power button. Try knocking it lightly against the corner of a table to jar whatever is making it stick loose.
It doesn't sound software related, especially since it rebooted while in recovery. If you hold the power button down long enough in recovery it will reboot, which makes me think you just have a sticky power button. It's happened to me before.
Click to expand...
Click to collapse
I think you might be right. Even when it is up and running, I have been noticing lately that I get the power menu popping up sometimes when I wasn't even touching the power button. So last night when it was in one of its constant boot loop fits I took it apart a bit (took the back off, took out the battery sim and sd, and unscrewed the shell) and blew some compressed air all around the power button. It had been rebooting for about an hour at that point and then as soon as I put it back together it came up on the first try. So far so good.

Database Info

welcome