Database Info

HELP: buttons randomly pressed

Hi all,
Few days ago I used Odin to go back to the stock Rom.
Since then the buttons p, mostly the back button, are randomly pressed when I'm not touching them.
I tried to use Odin again, flashed other roms and even restored the system to a Rom that worked fine, but the problem repeats in all of them.
Any ideas?
Tnx
Sent from my SAMSUNG-SGH-I897 using XDA App

Bad Hardware= warranty replacement.

This isn't the right place for this, but you can emulate something like this for pointless fun. Try running this command:
adb shell monkey 3000
and marvel as your phone flips out.

I have the same problem I saw a thread a while back saying that the problem stems from moisture in the phone
Sent from my SAMSUNG-SGH-I897 using XDA App

Interesting thing about the moisture, would explain why my phones search button will do this for 1/2 - 2 days and then stop for 1-2 weeks at a time.

ridethelight said:
Interesting thing about the moisture, would explain why my phones search button will do this for 1/2 - 2 days and then stop for 1-2 weeks at a time.
Click to expand...
Click to collapse
ya I have the same thing with my search button. But it will press in storms of 10+ which is annoying but not as bad as home or back
Sent from my SAMSUNG-SGH-I897 using XDA App

I had it happen on my first Captivate with the back key, it actually freaked out so much the phone was unusable . As long as it can be reproduced they will replace it no questions asked. Just make sure you are on stock and have done a master clear.
Edit: this was without any moisture issues, before snow hit etc

I have the same problem when using 2.1 then flashed 2.2 and zero problem. you can try flash to fix it.

Hi, I started having similar problems. But with my Power button only. It doesn't press by itself, but when i press it sometimes it works, sometimes it doesn't. BUT it doesn't seem to be a hardware problem because the first time it happened, i tried reflashing the kernel and everything was back to normal again, after 2 months here comes the problem again. I was able to fix it after a Hard reset using *2767*3855#, but later on i decided to do a factory data wipe and the power button key started going bonkers again. So I tried doing the hard reset trick to try and fix it again, but sadly this time it didn't work. I also tried flashing back to stock, master clearing, wiping cache and dalvik cache, wiping data. Trying to bring everything back to stock. But the problem still persists, I can't find a solution. Is there some code that I can't seem to reset that's causing this kind of problem. Hope someone can help me. My phones unusable and it's making me go crazy trying to find the problem and fixing it

ckelvin87 said:
Hi, I started having similar problems. But with my Power button only. It doesn't press by itself, but when i press it sometimes it works, sometimes it doesn't. BUT it doesn't seem to be a hardware problem because the first time it happened, i tried reflashing the kernel and everything was back to normal again, after 2 months here comes the problem again. I was able to fix it after a Hard reset using *2767*3855#, but later on i decided to do a factory data wipe and the power button key started going bonkers again. So I tried doing the hard reset trick to try and fix it again, but sadly this time it didn't work. I also tried flashing back to stock, master clearing, wiping cache and dalvik cache, wiping data. Trying to bring everything back to stock. But the problem still persists, I can't find a solution. Is there some code that I can't seem to reset that's causing this kind of problem. Hope someone can help me. My phones unusable and it's making me go crazy trying to find the problem and fixing it
Click to expand...
Click to collapse
The fact that it comes and goes probably means it is a hardware problem and not a software problem
Sent from my SAMSUNG-SGH-I897 using XDA App

I was having the same problem with my home button. I tried everything above to fix it. The only thing that has worked so far is updating my phone to stock 2.2 using kies. My home button was acting up 2 to 3 times a day and now it hasnt acted once yet.

crystalhand said:
The fact that it comes and goes probably means it is a hardware problem and not a software problem
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
But sometimes it starts working flawlessly right after a flash or wipe. But goes bonkers again immediately after i flash or wipe again Making it seem software related

[email protected] said:
I was having the same problem with my home button. I tried everything above to fix it. The only thing that has worked so far is updating my phone to stock 2.2 using kies. My home button was acting up 2 to 3 times a day and now it hasnt acted once yet.
Click to expand...
Click to collapse
But wouldn't it make sense if the moisture also left the phone? The only thing that made up my mind of it being hardware was flashing to stock and having the search button click continuously immediately. I have had the problem on and since october. Usually once a month for a couple of days. I let it sleep in a rice bowl when it acts up
Sent from my SAMSUNG-SGH-I897 using XDA App

Ok so my phone just started doing this one day while I was running Cognition 4.x Don't remember the exact version. I then switched over to Firefly on version 2.7 and kept updating all the way through 3.0. It was doing it on firefly too.
It got pretty bad a few weeks ago so I started messing around with BLN and the haptic feedback. After cranking the haptic feedback up it seemed to quit doing it as much. For example before I started messing with stuff every time I turned the screen on the home button would go nuts till I pressed it several times. After I messed with the haptic feedback it would only do it about 1 out of every 5 times I'd turn the screen on.
Well tonight I flashed from firefly to 2.3, I'm running GR-9 and TalonDEV 0.1.3 and it hasn't done it at all tonight. It'll probably start after I post this, but so far so good on Gingerbread.
I don't know if any of that will help anybody else, but thought I'd throw my experience with it out there. If it starts acting up I'll post about it.

[Q] Legend 2 ICS Edition GPS Problem for Infuse

Hey guys, so I just finished up changing my infuse over to Legend 2 ICS edition and I've been playing with it for about a week and I'm having a rather large issue. Whenever I leave the gps ability enabled so that my apps can find where I am the phone has a tendency to dump battery life like there is no tomorrow but worse than that it stops sending and accepting text messages randomly while the rest of the phone continues to operate. There are no warning signs so that I know this is happening and I have to reboot the phone to get it to work again. If I leave the gps feature off this is not an issue however, this is rather useful to have running so that my apps all work. Any idea how to fix this problem?? Thanks for your time.

I've been running legend 2 for almost a couple weeks and legend before that, my gps was buggy at first-it wouldn't lock on to my location. I did a complete wipe and reinstall, then let the phone boot up and let it settle for a while before I did anything else. Haven't had any problems since
---------- Post added at 03:13 AM ---------- Previous post was at 03:07 AM ----------
http://forum.xda-developers.com/showthread.php?t=1318160
http://forum.xda-developers.com/showthread.php?t=1561463
use clean wipe, I run that a few times just before I flash a rom now, haven't had any problems since I started using that.

Thanks a bunch I'll try that out and get back to you on if it works or not in the next couple of days.

Thanks
Sorry it took me so long to get back to you, work had me pretty tied up for a while. Thanks for the help everything seems to be working fine for the most part now. I need to reboot every once and a while due to overheating but I think thats just the fact that the phone is adjusting to the new ROM. Thanks again for the help.

Klevin2011 said:
Sorry it took me so long to get back to you, work had me pretty tied up for a while. Thanks for the help everything seems to be working fine for the most part now. I need to reboot every once and a while due to overheating but I think thats just the fact that the phone is adjusting to the new ROM. Thanks again for the help.
Click to expand...
Click to collapse
Hmmm, the phone shouldn't be overheating at all, do you do any tibu system restores? I've had an app cause an overheating problem before. One thing I've learned is when you do allot of flashing, checking out different roms or themes, its good to just do an odin or hemdall flash back to stock that has repartitioning.
It gives you a fresh start.

TiBu
I have done TiBu on the phone however I did have to flash it back to stock with odin partway through flashing this rom the second time because I bricked the phone, I'm still at a loss because I need to restart the phone usually once a day because it stops accepting and sending text messages without warning while everything else still works. It's kinda weird, I've been chalking it up to the fact that its a new rom and the phone needed to get used to it but it doesn't seem that way anymore.

Klevin2011 said:
I have done TiBu on the phone however I did have to flash it back to stock with odin partway through flashing this rom the second time because I bricked the phone, I'm still at a loss because I need to restart the phone usually once a day because it stops accepting and sending text messages without warning while everything else still works. It's kinda weird, I've been chalking it up to the fact that its a new rom and the phone needed to get used to it but it doesn't seem that way anymore.
Click to expand...
Click to collapse
Have you tried the new version 3 to see if maybe that helps? This is first Ive heard anything like this. I guess it works fine using another rom?
Sent from my SAMSUNG-SGH-I897 using xda premium

I didn't even know there was a version 3. I'll have to go take a look at that and see what happens. Thanks for the help.
Sent from my SAMSUNG-SGH-I997 using xda app-developers app

Still having issues
Ok so I'm still having an over heating issue and my phone refuses to send or recieve texts for periods of time. I'm going to delete a couple of apps to see if they're causing the problem. If that doesn't work any chance that I'm having a hardware issue with the phone, it wouldn't be the first time I've had issues this would be my 5th replacement due to hardware issues in the phone.

[Q] Phone occasionally becomes completely unresponsive with non-stock ROMs

Quick background: I purchased a One X from AT&T a few weeks ago. It came with the 2.20 firmware, so I used the X-Factor Exploit and unlocked the bootloader via HTCDev. From there I flashed TWRP Recovery and then AOKP.
Pretty much everything was fine at that point, except for the fact that once or twice a day I would pull my phone out of my pocket and it would be completely unresponsive. None of the buttons would wake the phone up, plugging it in didn't do anything, and it wouldn't receive calls. I would then have to do a hard reboot (Power + Volume Down) to get anywhere.
I thought maybe it was an AOSP problem, so I flashed a Sense-based ROM (CleanROM 5). I experienced the same issue.
From there, I re-locked the bootloader and ran the latest RUU. That was 4 days ago and I have yet to experience the problem again.
Has anybody else experienced this, and is there any way to prevent it?

power + Vol down puts you into the bootloader. What do you do from there to get the phone booted? Have you tried just holding the power button for 5 seconds or so, until the capacitive buttons flash (same as a battery pull)?
GPS on, by any chance?

redpoint73 said:
power + Vol down puts you into the bootloader. What do you do from there to get the phone booted? Have you tried just holding the power button for 5 seconds or so, until the capacitive buttons flash (same as a battery pull)?
GPS on, by any chance?
Click to expand...
Click to collapse
I would just select reboot and it would boot normally. Power alone would also work, I believe. I usually just did power and vol down out of habit I guess.
GPS and WiFi were always on.

What radio/RIL were you running?
What hboot version?
You are on 2.20, did you flash the correct KERNEL manually and clear dalvik and cache?
Sent from my HTC One X using xda app-developers app

c5satellite2 said:
What radio/RIL were you running?
What hboot version?
You are on 2.20, did you flash the correct KERNEL manually and clear dalvik and cache?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
HBoot 1.14. Didn't mess with the radio, so the stock AT&T 2.20 one (0.19as.32.09.11_2_10.105.32.25L).
Yes, I flashed the correct kernel. It did it with both the plain AOKP kernel and rohan's kernel.
Cleared caches several times.

GPS on when this happens, by any chance?

redpoint73 said:
GPS on when this happens, by any chance?
Click to expand...
Click to collapse
I hardly ever disable it, so it was likely on. No idea if it was actually in use any of the times.
I can say one time it happened immediately after a call, one time it was immediately after a SMS notification, and the rest just seemed to be randomly in the middle of the day.

Try going straight to CR5 directly from the stock ruu rom and see if it persists. Maybe the aokp Rom borked something along the way and the ruu has restored it now. I have seen issues similar to this that only the ruu will fix.
Sent from my HTC One X using xda app-developers app

Have the same issue.Try going to ViperXl and see what happens.My phone constantly reboots and enters sleep of death.I always have the gps disabled.have 1.09 hboot.And currently I am on 1.85 stock at&t.This issue is kikling me

I only mention GPS, since my old phone (Desire Z) had an issue where leaving the GPS on, would make the phone shutdown, and only a battery pull would start it (never tried going into hboot). Which sounds similar to what you were seeing. In my case, no ROM, kernel, or radio flashing ever remedied it. And I could isolate the issue to the GPS being on. If the GPS was used, the phone was going to black screen within a couple hours, without fail. But rebooting the phone after using the GPS (and shutting off GPS) prevented it every time. A few other owners of the DZ had the same problem. One guy sent his into HTC, and they told him it was a defect of the GPRS module, and replaced the motherboard, which fixed the problem.
Hopefully, its not a similar hardware issue in your case. But the fact that you have the GPS on all the time, and the black screen hasn't cropped up like clockwork (like it did in my case) seems to point to the fact that it might not be the exact same issue.
These types of issues tend to be really hard to troubleshoot (and pinpoint the cause). In my case, it took me a couple months to realize it was the GPS, since I usually have it off, and don't use it all that often (usually just when travelling). And I also suffered a lot of "placebo effect" type incidents while flashing various ROMs and kernels trying to fix the issue. If the issue doesn't crop up again after running the RUU, I'd consider myself lucky, and leave it well enough alone.

No it is not the same problem redpoint73.This only happens on Custom ROMS.I have tried every combo on the 3 ROMS i flashed.Could it be an int.d problem???My only is this.

nighthawk696969 said:
No it is not the same problem redpoint73.This only happens on Custom ROMS.
Click to expand...
Click to collapse
Yeah, I already said its probably not the same problem. But it doesn't hurt to check everything. As I mentioned, its easy to get sucked into thinking you have the cause isolated, when you really do not.

I understand what you're saying but i have checked it,i'm sure..

nighthawk696969 said:
I understand what you're saying but i have checked it,i'm sure..
Click to expand...
Click to collapse
It also doesn't sound like your problem is exactly the same as the OPs. You mention reboots, while OP does not (just BSOD, or shutdown requiring rebooting in hboot).

No my main problem are the Sleeps of Death.There are no BSODs in android

nighthawk696969 said:
No my main problem are the Sleeps of Death.There are no BSODs in android
Click to expand...
Click to collapse
Some people have been calling this condition BSOD = Black screen of death. Yes, its a little too derivative of things like Windows blue screen, XBox RROD etc. But you get the idea.

Update: I re-unlocked the bootloader and flashed CM 10.0.0 upon its release. I've yet to encounter this issue, so I'm thinking my stint on CleanROM might have buggered something. I probably forgot to wipe something somewhere along the line. D'oh.
I am, however, having a pretty severe albeit unrelated problem with an app called Voxer. Every time I listen to a message it kills the microphone until I Force Stop the app. I guess I'll pop over to one of the other AOSP ROMs and see if it persists.

I was having a similar problem on king kang and pacman. I could turn the phone on and off with the power button, but the touch screen was completely unresponsive. Happened randomly, I would have to hold the power button down and watch the lights flash until the phone shut down, and would be fine after a reboot. When I tried installing viperxl, I had the same issue during the aroma installer, I had to try flashing it 7-8 times, because it kept freezing during the install. No issues running it after a successful install. I was using king kang and rohans b5 kernel when it was happening most often

Phone randomly rebooting in pocket

I never had a random reboot on ICS now on JB I'm having it at least once a week...not a lot, I know but still something is not right. The last time this happened I tried looking further into it and the only thing I see that may be causing the issue is signal loss. I am 100% stock and have maybe 25 downloaded apps, if that. Is there an app for STOCK that will backup some of my data? I really don't think a factory reset will help but I'll give it a shot. Any other ideas? I freaking love this phone and this is my only complaint....would love to fix the problem. Thanks.

Here's a shot of the signal before the reboot.

Is it worth trying a factory reset? I feel the chances of it doing any good are very slim. Switch to a different modem?
Sent from my SCH-I535 using xda premium

I'm having the same issue, and a reset did not help.
Sent from my SCH-I535 using xda app-developers app

Thanks for the reply. As long as it does not get worse it's not a huge deal. Maybe the next update will fix it?
Sent from my SCH-I535 using xda premium

Not sure what the right word is (hotboot?) but today my phone rebooted (not fully) while I was using it. No fc's or freeze ups, just the reboot. I'm currently on the no wipe leak which ended up being the official ota.... Since the no wipe was modified would it make any sense to install the full wipe version to see if the problem is resolved?
Sent from my SCH-I535 using xda premium

Flashed full wipe via Odin. In case anyone else has this problem I will post back with results in a week or so.
Sent from my SCH-I535 using xda premium

I'm having the same issue. It seems that something is causing JellyBean-enabled SGS3's to just jump into "interrupt heaven". It's always a quick boot, never resets the "Up time" counter, and only takes a few seconds to get back to normal, but it's a real pain in the arse!
Any ideas what the culprit is, guys? I'm running a newly replaced (ordered it on January 2nd and the first thing it does was download and upgrade to JellyBean "VRBLK3" before I could even start get it loaded, basically as soon as I activated the phone, it started to download the OTA before I could even get to anything else). I know in my case I have a couple of mods installed - maybe one or more of these is common amongst those of us having issues? I have the "4x5 scrolling" mod and the "BLK3 Logo fix" mod that removes the stupid VZW drum-beating and pulsating display on boot-up. Other than that, my phone is rooted (using method involving loading the older ICS bootchain so you can install the latest CWM recovery), has CWM Touch 6.0.2.3 and that's about it, other than your usual rooted toolkit programs. Anything common to the rest of you?
Oh, by the way - I've already tried reformatting the cache, blowing away the dalvik cache and even a complete factory reset, which seems to make it less jumpy, but it always comes back within a day or two if not just a few hours.

I had the same problem with mine rebooting when I had very bad signal. Last Friday I did a factory reset then Odin to 4.0.4 and let the phone update to 4.1.1 and the problem seems to have gone away. I am not willing to call it cured yet, but it hasn't rebooted since. This went from where I was rebooting constantly all day long at work and when on the road in bad signal areas.
So far so good.
By the way, I looked EVERYWHERE and couldn't find anyone complaining of this earlier so I figured it had to be a bad download of the update.

It's something in Jelly Bean update itself. I tried booting my phone in "Safe Mode" - which only loads factory programs, and it still happens. I sure wish I could put a finger on anything in the way of a pattern, but - so far there's nothing I can single out that seems to make any difference. I'll do the system/factory reset and re-install everything one more time just to see if it helps.
Weird...

Factory reset (and everything else) - it still reboots
ratledge said:
It's something in Jelly Bean update itself. I tried booting my phone in "Safe Mode" - which only loads factory programs, and it still happens. I sure wish I could put a finger on anything in the way of a pattern, but - so far there's nothing I can single out that seems to make any difference. I'll do the system/factory reset and re-install everything one more time just to see if it helps.
Weird...
Click to expand...
Click to collapse
Well, something in a factory reset helps, but it doesn't last. First, just to be thorough, I used "ROM Manager" to 'fix permissions', then I did a complete flush of the system, removed the micro-SDXC card, did a format of the cache partition, flushed the Dalvik cache, then did a factory reset and reinstalled everything. I seemed to help for a while, but eventually it started to reboot randomly - sometimes when it was just sitting idle not even being used at all.
That indicates to me there's something funky in the JB (VRBLK3) firmware, especially since I was seeing reboots even while I was booted in safe mode, where nothing loads except factory-installed programs.
Fortunately, it never reboots while it's in recovery or download mode... :silly:
Ah, I forgot to note: this is the second phone that acts exactly the same way with the VRBLK3 (Jelly Bean) ROM update. Symptoms of the problem are identical, down to the spontaneous combustion that started this thread. Mine's not "in pocket" as per the OP, but - I don't think that has anything to do with it.

ratledge said:
Well, something in a factory reset helps, but it doesn't last. First, just to be thorough, I used "ROM Manager" to 'fix permissions', then I did a complete flush of the system, removed the micro-SDXC card, did a format of the cache partition, flushed the Dalvik cache, then did a factory reset and reinstalled everything. I seemed to help for a while, but eventually it started to reboot randomly - sometimes when it was just sitting idle not even being used at all.
That indicates to me there's something funky in the JB (VRBLK3) firmware, especially since I was seeing reboots even while I was booted in safe mode, where nothing loads except factory-installed programs.
Fortunately, it never reboots while it's in recovery or download mode... :silly:
Ah, I forgot to note: this is the second phone that acts exactly the same way with the VRBLK3 (Jelly Bean) ROM update. Symptoms of the problem are identical, down to the spontaneous combustion that started this thread. Mine's not "in pocket" as per the OP, but - I don't think that has anything to do with it.
Click to expand...
Click to collapse
Thanks for thoroughly trying different things to try and figure out the issue. Your problem seems worse than mine... I was getting reboots every few days. All day today was fine after installing full wipe but that's not a thorough test for what I was experiencing.
Sent from my SCH-I535 using xda premium

Ryno77 said:
Thanks for thoroughly trying different things to try and figure out the issue. Your problem seems worse than mine... I was getting reboots every few days. All day today was fine after installing full wipe but that's not a thorough test for what I was experiencing.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
You could also try getting a new sim from Verizon to see if that helps with connectivity to towers. You've already Odin flashed stock images and wiped pretty much everything significant at that.

New SIM?
SlimSnoopOS said:
You could also try getting a new sim from Verizon to see if that helps with connectivity to towers. You've already Odin flashed stock images and wiped pretty much everything significant at that.
Click to expand...
Click to collapse
Well, unfortunately I've done that - twice in the past ten days, the latest one came Tuesday afternoon. No change, still just reboots while I'm not even using the phone, and it's not the phone, it's the software. I can't say for absolute certain that it is in the VRBLK3 / JB code, but I can say for sure it _is_ something I am running, but the fact that it does reboot in safe mode indicates it's not anything downloaded or added to the base system as shipped.

ratledge said:
It's something in Jelly Bean update itself. I tried booting my phone in "Safe Mode" - which only loads factory programs, and it still happens. I sure wish I could put a finger on anything in the way of a pattern, but - so far there's nothing I can single out that seems to make any difference. I'll do the system/factory reset and re-install everything one more time just to see if it helps.
Weird...
Click to expand...
Click to collapse
Irrelevant question -- can't help my curiosity. How is it that you're on your 6th GS3? You get a new one every month?

6 Pebble Blue 32MB phones in about 8 months
jaymattt said:
Irrelevant question -- can't help my curiosity. How is it that you're on your 6th GS3? You get a new one every month?
Click to expand...
Click to collapse
Heheh... Well, I got one on "day 1" by pre-ordering it from Verizon, after two months the power button fell off. They sent me a "CLN" one, it lasted ten days and started randomly rebooting (even if reloaded with 'virgin' unrooted OS), the third (another "CLN") was delivered with no power button and the volume rocker fell off while I was taking it out of the box. At that point, I got kind of pizzed and did the 'good customer for 10 years' and elevated it through three levels until I finally got them to ship me a brand new one. That one lasted two months until my wife left it on top of my car and I backed over it in my driveway. I used my Asurion (insurance) to get #5, which arrived rebooting from the moment I started it up. Within a few days after monkeying around with their tech support (they ain't the brightest bulbs - instructions include "remove the battery and dial yourself and hit the 'Send' key three times" - not kidding) I managed to get #6 shipped out, and it's first act of life was to suck down the VRBL3 (Jellybean) software update and I've mucked around with it for two weeks, tried loading it with various combinations of "No Wipe" and "Factory Reset" versions of VRBLK3, removed a bunch of programs I've had installed but never really used and it still just vibrates about once an hour (and it's totally random, sometimes lasts 6 hours, sometimes 6 minutes before rebooting), jumps to the "warm/quick start" and recycles without resetting the "time up" counter. I'm thinking it's something I fed it (i.e. a nasty program or interaction between programs) - but I've come up empty-handed so far as running it to ground.
Does anyone have any knowledge of known interactions or "bad programs" that just don't play well together under JB?

Sadly my friend, you need CLN #7. Nothing here is going to resolve that.
Sent from my SCH-I535 using xda app-developers app

SlimSnoopOS said:
Sadly my friend, you need CLN #7. Nothing here is going to resolve that.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Well, normally - I would agree. But this makes three phones that act exactly the same in a row. The first of which was my 2nd "New" GS3, updated OTA to Jellybean - which immediately started the rolling reboots. The problem with the "CLN" phones are that they were all defective in one way or another, or they wouldn't be recertified. I don't really think VZW does a good job recertifying these phones, there are just too many of them coming out every single day, and - lord knows Asurion probably is behind that curve. :silly:
All three phones have been identical in their behavior - "down to the letter" since VRBLK3 was released. :fingers-crossed:
Question: now that I've used my insurance, do I _have_ to go back to Asurion for replacement, or since I'm still in my first year, will VerizonWireless entertain sending me another? It seems like reading the information that comes with the Asurion phones, they are the ones that are now guaranteeing my phone for a full year from the time it was sent (that would be this past Monday).
The phone has an Asurion sticker inside it, not a VZW one...

And the winner is: battery replacement. Every single VZW marked battery causes it to reboot, but a plain old Samsung battery (made in Korea - I've noticed almost all the VZW branded SKUs are made in China) works 100% and gives me an average of 12 hours moderate usage. The batteries I had from previous phones, VZW and Asurion all have the Verizon markings on them, and every single one of them causes it to reboot. This new one I got today straight from Samsung does not.
Curious, huh? I have one out of five batteries with VZW markings, and it does the same as the other four "made in China" ones. You've gotta wonder...

Glad you found a fix. Is it possible the new battery is slightly larger? Wondering if the old batteries were maybe a bit loose.
Sent from my SCH-I535 using xda premium

[Q] Skyrocket freeze/shutdown on signal loss

Hi. Let's get right to it, shall we?
I was running a 4.3 Rom on my phone. Worked great while I was at my house though I did notice my signal seemed lower than before I installed it. But I didn't worry about it too much. Ran the Rom all weekend without any issues. Coverage in my city is pretty good, so I never had a signal drop.
I work in a pretty rural area of PA which causes me to lose my signal a couple of times while commuting there. So, on Monday when I got to work, I had a blank screen and all buttons were unresponsive. I did a hard reboot which went fine until the phone tried to reconnect to the network. Then it went back to the blank screen and forced another hard reboot.
Thinking this was an issue of cm10.2, I went home and reloaded a 4.2 Rom. Again, it worked great until the next day when I returned to work. Then the shutdown/freeze issue arose again. So I went to stock 4.1.2 with stock kernel and radio. No extra apps, nothing. The only thing custom on my phone was the recovery. Anyway, I still had the same problem.
As long as I don't lose my signal, my phone works awesome. And it's not the loss of signal that's bad, it's when the phone reaquires the signal that it breaks. I went to AT&T and discussed with a rep but I seemed to know more about phones than he did ( his words, not mine ) and I couldn't reproduce the problem because, of coarse, there was a perfect signal at the store.
So, I'm asking for thoughts, ideas, and suggestions on how I might fix this problem or what might be wrong. I respect and appreciate, any help I might get from this fine community. Thank you all in advance.

So when you say after you went to stock the only thing custom was a custom recovery ...
Odin a ucmc1 stock the one which also takes you to stock recovery and do your wipes from there.
See if this resolves the issue
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Commodore 64 said:
So when you say after you went to stock the only thing custom was a custom recovery ...
Odin a ucmc1 stock the one which also takes you to stock recovery and do your wipes from there.
See if this resolves the issue
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
How does the recovery effect the phone when it's on normal and not in recovery mode? Please ( and this isn't sarcasm ) Talk to me like I'm four years old.

Mine did something like that also, I was on CM10.2 20130920 Nightly clean install with TWRP 2.6.3.0 and everything was fine then phone froze and started vibrating, camera flashed, power button wouldnt do anything I pulled battery and reinserted it and same thing just vibrated. Finally was able to go to DL and reinstalled stock booted just fine I set up the phone and couple hours latter same thing phone locked up started vibrating and nothing.
I know it is recommended to use CWM 6.0.3.7 but figured the lates TWRP would work. Now I have a worthless Skyrocket that all it does is vibrate, I can take the battery out and use it as paper weight.