Develop Bugs

[Q] restart

hey, i have had my Galaxy S3 sence black friday of 2012, and it is not rooted or anything. but just recently within the last few weeks, it has randomly restarted, like im texting or playing on FB and then screen goes black then i see samsung logo. any sugestions on how i can fix this?

Mine recently started doing the same thing. After being rooted about a year ago, and being stable on the same ROM for the last 6 months or so, it randomly started rebooting itself 10-20 times a day.
I tired installing a stock ROM, stock kernal, etc. but nothing helped. I eventually unrooted it using QBKing77's video (on this site) and used Odin to install the stock tar image. This was in preparation to take it back for what I could only assume was a hardware issue. After a *lot* of automatic OTA updates (maybe 8 -10 or more!) it seems to have solved the issue. The phone has been stable without a restart for the last 48 hours.
In addition to that, I also pulled my sd card and ran it through the windows disk tools which said it found a few errors and corrected them. So at this point I don't know if it was ROM/kernal related, card related, or a perfect storm of a combination of each. I'd suggest you pull your sd card and use windows to check it 1st since that'd faster and easier. If that doesn't work, unroot.
I plan on waiting another day or two before I unroot again, just to be sure it's still stable. Hope this helps.
** Just saw that you're unrooted. If you're still in warranty, take it back. If not, try rooting it, and installing a new kernal or ROM and see if that helps.

i am not in warrenty, i wish but im not. i dont want to root it,

Check if your battery is swollen, the spin test works pretty well if you're unsure just by looking at it. A swollen battery is one of the most common reasons for frequent reboots if you're running stock.

Power button failure known defect with S3. They replace them at Sprint. It's referred as Sudden death syndrome.
Sent from the future via Tapatalk 4

[Q] Epic 4G in Recurring Sloth Mode

What could possibly poison an Epic 4G's system speed across the stock ROM and 2 custom ROMs?
Like this...
I'm on my second Epic 4G, got a used one off eBay about a month ago when the screen on my first one died.
On my first one, I rooted it, upgraded to Clean GB, then eventually moved it to cm-10.1.3.1.
The used one came stock, but ran extremely slowly. No problem - I've seen that happen before with my old phone (I call it sloth mode) and knew that installing a new ROM would resolve it. Just to be conservative, I bumped it up along the same path I did before, Clean GB, then cm-10-1.3.1.
Here's the thing. After installing a new ROM, both phones would operate normally. But no matter which ROM ran on the old phone and the replacement, *eventually* it would slip back into sloth mode. I don't mean sluggish, I mean crawling, even during the bootup animation. Even the CWM recovery menu was sluggish.
When I ran Clean GB on the replacement phone, I didn't add more than 2 or 3 apps to it after installing. But it still fell back to sloth mode after about a week of use. After installing cm-10.1.3.1, it only lasted a 3-4 days before sloth mode returned.
Before changing ROMs, I routinely did a factory reset, cleared cache and Dalvik cache.
Of course a virus is a possibilty, but having security apps installed and running didn't seem to make any difference. Could this be a rootkit-class issue?

DeafScribe said:
What could possibly poison an Epic 4G's system speed across the stock ROM and 2 custom ROMs?
Like this...
I'm on my second Epic 4G, got a used one off eBay about a month ago when the screen on my first one died.
On my first one, I rooted it, upgraded to Clean GB, then eventually moved it to cm-10.1.3.1.
The used one came stock, but ran extremely slowly. No problem - I've seen that happen before with my old phone (I call it sloth mode) and knew that installing a new ROM would resolve it. Just to be conservative, I bumped it up along the same path I did before, Clean GB, then cm-10-1.3.1.
Here's the thing. After installing a new ROM, both phones would operate normally. But no matter which ROM ran on the old phone and the replacement, *eventually* it would slip back into sloth mode. I don't mean sluggish, I mean crawling, even during the bootup animation. Even the CWM recovery menu was sluggish.
When I ran Clean GB on the replacement phone, I didn't add more than 2 or 3 apps to it after installing. But it still fell back to sloth mode after about a week of use. After installing cm-10.1.3.1, it only lasted a 3-4 days before sloth mode returned.
Before changing ROMs, I routinely did a factory reset, cleared cache and Dalvik cache.
Of course a virus is a possibilty, but having security apps installed and running didn't seem to make any difference. Could this be a rootkit-class issue?
Click to expand...
Click to collapse
Could it be a failing processor? I had one that went into that mode and never came back...no matter what it would take 20 times longer to boot...boot animation was like beyond slow motion. Best thing to do at this point is to just odin stock and leave it that way for a week...no extra apps or restore and see how it does.

Worth a try...
KennyG123 said:
Could it be a failing processor? I had one that went into that mode and never came back...no matter what it would take 20 times longer to boot...boot animation was like beyond slow motion. Best thing to do at this point is to just odin stock and leave it that way for a week...no extra apps or restore and see how it does.
Click to expand...
Click to collapse
Yeah, it's worth a try. I've also wondered if I slipped up and installed a version of Clean GB or cm-10-1.3.1 that jumped betweeen MTD and BML file formats. I know it could cause problems, but I don't know if it could cause the specifc trouble I had.
Phone's been parked in a drawer for a month since I posted the question. Will odin back to stock and see how it works out.

DeafScribe said:
Yeah, it's worth a try. I've also wondered if I slipped up and installed a version of Clean GB or cm-10-1.3.1 that jumped betweeen MTD and BML file formats. I know it could cause problems, but I don't know if it could cause the specifc trouble I had.
Phone's been parked in a drawer for a month since I posted the question. Will odin back to stock and see how it works out.
Click to expand...
Click to collapse
I just hooked one of my old ones up to freedompop through the BYOD program. Nice to see the old girl getting use at least as an emergency phone.

Super Unstable

Hey guys, i need some help. Recently I Odin the latest Tar OG1, and used the debloated OG1 stock Rom that is in the Developer Forums. Everything was going well and after a few weeks I started noticing that my phone would start to lag really bad and then just freeze for long periods. I can't do anything while it's frozen and more than often it will restart on it's own. I've wiped everything and restored it using the Tar and even on complete stock it does this. I'm starting to think it has something to do with my actual phone but I don't know how to make sure. I had twrp and even that lags and freezes sometimes. I don't know what I could have done to make this happen, I had xposed installed, and i was running the beastmode kernal as well. Anyone have thoughts on this?

Update: so now my phone just cut and restarted again out fo the blue (I was trying to set an alarm) and my screen went black with fading lines on it, then suddenly it started vibrating nonstop., had to yank the battery. turned it back on and now it just restarts when idle.

One of my Note 4's started lagging real bad, locking up (requiring battery pull), and constantly restarting. Its completely stock, I've read around online that its likely an issue with the onboard eMMC memory on the motherboard dying. Only cure is to replace the motherboard.
I found a work around though, download an app called Wake Lock (or something like that), start it and set to partial wake lock. Phone basically runs like nothing is wrong with it now. Have about 6 months before I can upgrade so hopefully it holds out until then.

FanOfSkynyrd said:
One of my Note 4's started lagging real bad, locking up (requiring battery pull), and constantly restarting. Its completely stock, I've read around online that its likely an issue with the onboard eMMC memory on the motherboard dying. Only cure is to replace the motherboard.
I found a work around though, download an app called Wake Lock (or something like that), start it and set to partial wake lock. Phone basically runs like nothing is wrong with it now. Have about 6 months before I can upgrade so hopefully it holds out until then.
Click to expand...
Click to collapse
Dude you are awesome!!! I managed to odin the stock tar again, went through setup at super slow speed just to be sure, and then installed the app. As long as i take some caution it is running like normal again! With the Note 7 recalls this really help buy the time I need before i can get one. Thank you so much!

HunterKiotori said:
Dude you are awesome!!! I managed to odin the stock tar again, went through setup at super slow speed just to be sure, and then installed the app. As long as i take some caution it is running like normal again! With the Note 7 recalls this really help buy the time I need before i can get one. Thank you so much!
Click to expand...
Click to collapse
No worries, I did lots of reading online and banging my head against the wall when it started acting up. It was really weird, it was acting fine one day, then the next slow, lagging, locking up, and restarting. I tried factory resets, reinstalling old stock ROMs, taking the sd card out. Finally stumbled onto a post in another forum where a guy mentioned that app. Since installing it, as long as I keep it running, phone acts like normal, that's about a month now.

FanOfSkynyrd said:
No worries, I did lots of reading online and banging my head against the wall when it started acting up. It was really weird, it was acting fine one day, then the next slow, lagging, locking up, and restarting. I tried factory resets, reinstalling old stock ROMs, taking the sd card out. Finally stumbled onto a post in another forum where a guy mentioned that app. Since installing it, as long as I keep it running, phone acts like normal, that's about a month now.
Click to expand...
Click to collapse
Im not gonna lie, i don't know exactly what it does. Does it drain your battery quick by chance? Mine dripped from 79% to about 40% in the span of an hour. Not sure if its because of the fresh flash or not

The Note which has issues is my wife's phone and she is a "power" user, lots of screen on time (think her timeout is set to like 2 minutes or something like that). I dont think she has seen any appreciable difference in battery life, but I'm sure it does drain a little bit as the partial wake lock never really allows the phone to enter into a true sleep/battery saving mode.

I had freezes and boot loops, and it turned out to be a bad battery. Strange, right? But it's true. I replaced the battery with a new one and everything worked fine again.
The battery had just started to swell, which is a sign of a failing battery. So, even if the battery isn't your problem, it's always good to check it now and then for changes in thickness.

Official random rebooting fix

I've read 10 pages on this subforum, random talks about updates, LTE fixes, etc...I've yet to find a single thread giving an official fix for random rebooting? I get this at least 4x a day...regardless of charging or not, SD card installed or not, all the latest updates are installed. I can't be the only one and if so, why isn't this a Sticky issue at the beginning?

I and few have others have the unpleasant experience with rebooting. But it was a little relief that this issue is not just with my Note4.
Laughter is the key to happiness

I had this problem with the early 6.01 stock roms, but it eventually calmed down. Now I get a reboot about once a week. I just assumed the first couple 6.01 stock roms were buggy.
I suppose lots of hardware issues could also cause it.

I bought this phone used for $140, I don't know how long it's been running 6.01, but I'm guessing he knew it had this issue. It happens 3-4 a day for the past two weeks. It'll do it while at rest on or off a charger, middle of use, etc. Aren't they're apps that can log what's going on when it fails so this can be resolved, like acatlog? These phones aren't new anymore, it seems there should be a fix out by now...root and overclock while undervolt, remove bloatware from Sprint Normal Apps or whatever it's called, etc

m5james said:
I bought this phone used for $140, I don't know how long it's been running 6.01, but I'm guessing he knew it had this issue. It happens 3-4 a day for the past two weeks. It'll do it while at rest on or off a charger, middle of use, etc. Aren't they're apps that can log what's going on when it fails so this can be resolved, like acatlog? These phones aren't new anymore, it seems there should be a fix out by now...root and overclock while undervolt, remove bloatware from Sprint Normal Apps or whatever it's called, etc
Click to expand...
Click to collapse
So, what rom is the phone running?

Bone stock at the moment. I'm going to let a Sprint store give it a looking over, but I'm not hopeful as they're usually useless vs what I can find here myself. At minimum I'm going to root it and remove bloatware, but I haven't reviewed roms yet. Unless this thing stored it in memory, but I was doing a copy and paste last time it froze and rebooted, yet I was still able to paste when it came back on...safe to assume that means it's only a soft reboot?

m5james said:
Bone stock at the moment. I'm going to let a Sprint store give it a looking over, but I'm not hopeful as they're usually useless vs what I can find here myself. At minimum I'm going to root it and remove bloatware, but I haven't reviewed roms yet. Unless this thing stored it in memory, but I was doing a copy and paste last time it froze and rebooted, yet I was still able to paste when it came back on...safe to assume that means it's only a soft reboot?
Click to expand...
Click to collapse
What version of stock? If it's old, some of the early 6.01 roms were pretty buggy. The current stock rom is QC1, which just began to roll out this week. Make sure you are on the most current rom.

Last update I received was this week which turned out to only be a security patch.

So, you're on most recent rom. Only suggestion I have is full reset. If that doesn't do it you've got a hardware problem.

So I hope I don't jinx myself, but I think a new battery has solved my issue...with some extra steps Let me explain.
Bought the phone used, it'd reset about 3-4x a day...being charged, being used, whatever. It'd reboot anywhere from 80% down to 40%, no rhyme or reason. Sometimes it simply wouldn't allow me to turn it back on, the light would flash blue while dimming in and out, but wouldn't power up the screen. Plugging it back in and it'd be at 30%-45% no matter what. I downloaded an app called Battery Calibration from Meza (sp?) that had a little Android logo with a % on his chest. Resetting may or may not have completely solved the problem had it not soft reset when trying to get battery stats to refresh themselves. It's my understanding that if it reset, it rewrote a battery stat upon reboot, making this step useless.
I got two new batteries from eBay (http://www.ebay.com/itm/112344168032?_trksid=p2057872.m2749.l2649&ssPageName=STRK:MEBIDX:IT), I charged one in the phone and one on an external charger. Even after running with the new battery, it still reboot once and shutoff around 43% reported on the phone itself. Once plugged in and phone still off, it said it was at 15%. I swapped in the other new and charged battery, powered on the phone, plugged it in until it read 100%. I fired up the Battery Calibration app, unplugged the phone as directed and then to force the battery to drain faster, I let YouTube play uninterrupted for about 4hrs. NOT A SINGLE REBOOT!! For the first time with this phone, it actually stayed on and dipped below the 30%'s and gave me a warning when the battery was getting low (yellow icon) and getting critically low (red icon) before it finally powered itself off at 1%. The phone is now charged on the factory fast charger, this time playing Pandora with the screen off and uninterrupted as well...it's currently sitting at around 57% last I checked.
Once it's fully charged, I'll run it like any normal user (texting, music, etc) without being plugged in and if all works well, it won't reboot.
Hopefully this helps someone with the same issue and is a $8 fix since I bought two batteries.

poit said:
So, you're on most recent rom. Only suggestion I have is full reset. If that doesn't do it you've got a hardware problem.
Click to expand...
Click to collapse
I reset the phone the day I got it.

if your phone often reboot many times in a day, make sure that you don't use Ram kernel V6 or v7 for your Rom, V5 is only version that not make your phone randomly reboot. I try Ram kernel v6 and v7 in Note 7 port rom, note 5 port rom and stock either, and this kernel version always make my phone reboot many many times, unless i flashed v5 or stock kernel, the problem had gone.

I had this problem. I replaced the battery with an official Samsung battery I ordered from Sprint, and the problem went away. Simple as that. No reboots ever since.

Purchased a new battery from Amazon, Samsung OEM, problem solved. Put back old battery guess what it started again but only when battery reached 70% of the original charge. So it must be the battery memory problem.
Sent from my SM-N910P using Tapatalk

Four batteries later and this still happens. Can this be addressed via rooting and then undervolting? I remember phones of the past where people would overclock for speed and undervolt for battery life, but one way too high or too low and you'd either get random rebooting or freezing. This is so god damn annoying!!!!!!

:) PLease help ME i would like for my phone to work again :)

Okay, so I have no idea what is wrong with my att note 4.This thing has always been kept in an otterrbox.It has been kept in perfect condition until an ota forced its self upon the phone. After that it started acting weird. Reboots, freezes, black screens, and sometimes something would get corrupted and the phone wouldn't boot at all. Sometimes the phone would make a constant buzzer or it would go straight to recovery but say sbl1 partition doesn't exist. Flashing stock worked for a while, but the problems would come back shortly and have gotten much worse.I just bought a brand new battery fully charged it and flashed stock 5.0, 5.1, 6.0. It doesn't matter i have tried it with the pit, without the pit same things happen. I have tried both batteries, fresh wipes, different firmware's, and now I can't even get it to boot at all no matter what I Try.
What do you guys think my problem could be i have no idea what it could be
I WOULD APPRECIATE ANY HELP

Same Issue
Hello,
After the marshmallow update I am facing the same. but i kept it running by downloading wakelock app from playstore . It somehow helps I am not sure the reason. Please select PARTIAL_WAKE_LOCK option once you download.
Try to not to shut down the phone because of any reason.
I hope this helps! and do let me know if it does.

my phone has been doing this for the past year after the update to 5, I purchased it on ATT Next in december 2014 so I think i have 1 more next payment. thing is it was the BEST phone prior to the update to 5 then it has been hell. i've purchased 5 batteries which someitmes helped for a short period but currently i can't even use any of my tricks to get it to boot.
I have came so close to crushing the phone so many times. thank goodness ii'm older and wiser or else it would be long gone

jammer8 said:
my phone has been doing this for the past year after the update to 5, I purchased it on ATT Next in december 2014 so I think i have 1 more next payment. thing is it was the BEST phone prior to the update to 5 then it has been hell. i've purchased 5 batteries which someitmes helped for a short period but currently i can't even use any of my tricks to get it to boot.
I have came so close to crushing the phone so many times. thank goodness ii'm older and wiser or else it would be long gone
Click to expand...
Click to collapse
I have read many sources available online. These updates sometime is not compatible with our phones. In case of note 4, certain model's CPU faces shutdown trouble due to update the moment we lock the screen or in standby mode. To keep them running there are apps like wakelock. Download that and select option Partial_wake_lock. This will help a bit hopefully. Worked for me. But this isn't a permanent solution.
Apologies in advance if my terminologies aren't correct or the solution doesn't work.