Related
For the pass week I have been experiencing screen freezes / screen lock ups......to the point I have to do a battery pull....I never had this issues before til recently I've tried every rom and it does the same thing after a few days or so I've even ran roms that I've never had any issues with before but i still get lock ups....any ideas!!! I don't wanna take it in cuz I don't want to do the HTC unlocking once they send me a refurb!!
Sent from my PG86100 using Tapatalk
Could it be heat related? Mine is.
I am going for a second refurbished e3d and hitting it with a hairdryer first thing out of the box to see if I can get it to reboot due to moderate heat.
A month ago, refurbished phones were 1.4 hboot.
Can't be heat related I watch movies just to burn my battery dry and nothing goes wrong but idk but it possibly could be heat related
Sent from my PG86100 using Tapatalk
M phone was horribly hot this weekend and was perfectly stable. What the heck?!?
Heat is either a necessary precondition or it is humidity related. Those (and updated apps, as they hit the market) are all that have changed between stability and the previous rebooting abyss.
Maybe random really is random.
Oh, I still can't use the walts kernel that comes with CR 2.5. Something about it hates my phone and causes massive random rebooting.
Freeza's stock kernel is a million times more stable, only leaving me with the more minor rebooting topic we are posting about here.
Try this... http://forum.xda-developers.com/showpost.php?p=18246407&postcount=2861
I'm getting freezes also, anytime my phone screen times out. The phone will lock up and you have to hold power button plus volume up and down to reboot or battery pull.
I just did this fix and testing now, not sure if it fixes it yet...
Sent from my PG86100 using Tapatalk
^^^didn't work for me... Getting the lockups.
Sent from my PG86100 using Tapatalk
Questions - Just trying to help
OP :
Are you using any 3rd party roms - mods - themes- etc.
?
If so, I can tell you , from personal experience, that ViperRom seemed to affect my phone (stock kernel, last version, not the latest) in this way. I was not overclocking, nothing special just the basic rom and it seemed to randomly lock up, and get quite warm. Many, many others however are quite happy with his rom without any issues.
Me personally, I have moved to Virus'es (lol) infected rom, Im loving it, stable, fast, beautiful theme, and it seems like the developer is a little more involved than Viper was.
Just my 2c, Not trying to trash any of the dev's I appreciate all of the hard work hobbyists put into this, once again, just trying to be helpful.
--DT
deathtech said:
OP :
Are you using any 3rd party roms - mods - themes- etc.
?
If so, I can tell you , from personal experience, that ViperRom seemed to affect my phone (stock kernel, last version, not the latest) in this way. I was not overclocking, nothing special just the basic rom and it seemed to randomly lock up, and get quite warm. Many, many others however are quite happy with his rom without any issues.
Me personally, I have moved to Virus'es (lol) infected rom, Im loving it, stable, fast, beautiful theme, and it seems like the developer is a little more involved than Viper was.
Just my 2c, Not trying to trash any of the dev's I appreciate all of the hard work hobbyists put into this, once again, just trying to be helpful.
--DT
Click to expand...
Click to collapse
I'm running virus news rev and I'm getting the lockups...
It happens while I leave phone idle and freezes screen up and requires battery yank or power down and volume button reset.
I just flashed back to virus airbourne and no lockups.
Seems to happen on 2.3.4 roms only.
Sent from my PG86100 using Tapatalk
If you are running any of the roms that change the automatic dimming settings than that may be your problem. For some reason, anytime Steel would add that feature to his rom everyone would start having the lockups and screen freezing. Check to see if your rom has altered these settings and if it has remove that update and you should be fine.
Every single kernel I have tried with the exception of netarchy's silverneedle on 2.3.3 has given me random lockups after about a day of use.
I have since reverted back to the Stock kernel on 2.3.4 and all is well.
Yea i have used vipers newest and even went back to the good ol decks ROM and had lock ups I'm on deck now with no custom kernel so i will do more testing then slowly add things to see what the culprit is
Sent from my PG86100 using Tapatalk
Chauleyboii said:
Yea i have used vipers newest and even went back to the good ol decks ROM and had lock ups I'm on deck now with no custom kernel so i will do more testing then slowly add things to see what the culprit is
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Keep us updated, want to figure these lockups out...
I think its probably more hardware related. I'm stock everything and have had this almost catch fire 3 times now. Not like a little hot, but hot to where I have to put it down. I too have had a bunch of screen freezes lately, only a few force restarts. The high temp thing is random. First was taking video. Second time was uploading a few pics to facebook, third time....this last sunday was a good one. Had it plugged in for about 2.5hrs. My dad grabbed it and threw it down because he didn't expect it to be as hot as it was. I was like WTF? He gave me the phone and it was on fire, with only 25-30 charge. This was using the HTC charging stuff that came with the phone. I keep deleting the battery temp app so i didn't get actual temps at the time. I'm gonna try for a new one tomorrow, hopefully get upgraded to 1.40 from 1.50.
gokart2 said:
I think its probably more hardware related. I'm stock everything and have had this almost catch fire 3 times now. Not like a little hot, but hot to where I have to put it down. I too have had a bunch of screen freezes lately, only a few force restarts. The high temp thing is random. First was taking video. Second time was uploading a few pics to facebook, third time....this last sunday was a good one. Had it plugged in for about 2.5hrs. My dad grabbed it and threw it down because he didn't expect it to be as hot as it was. I was like WTF? He gave me the phone and it was on fire, with only 25-30 charge. This was using the HTC charging stuff that came with the phone. I keep deleting the battery temp app so i didn't get actual temps at the time. I'm gonna try for a new one tomorrow, hopefully get upgraded to 1.40 from 1.50.
Click to expand...
Click to collapse
That's crazy I never had heating issues like that before!! But maybe ill do everything to get my phone working harder to see if I can create that issue
Sent from my PG86100 using Tapatalk
Hey I was just wondering if anyone had the same problem as me or if its been asked before. But my battery gets hotter than usual now when I'm doing things such browsing or playing a game. It didn't do this is CM7.2 and I didn't know if this was a known problem with cm9.
minimeofctown said:
Hey I was just wondering if anyone had the same problem as me or if its been asked before. But my battery gets hotter than usual now when I'm doing things such browsing or playing a game. It didn't do this is CM7.2 and I didn't know if this was a known problem with cm9.
Click to expand...
Click to collapse
Some people have mentioned that their phones got warmer. I would check out the running processes that you have...I went back to cm7.2 for now.
Alright thanks. I think I might switch back until another beta comes or it becomes stable.
Try rebooting a couple times. Mine got hot after initial boot up but was fine after a couple reboots.
Mine stays warm with cm9. I went back to lokos rom. Its killer. CM9 has just not worked well for me. Freezes and reboots. Random force closes without the fc notification. Odd stuff. And I've installed all the different ways ya can. And the ICS update for the mopho isn't scheduled till the 3rd quarter. So don't expect a perfect ICS till the leaks start for that update. Fortunately we have devs like Joker on it and we might just get lucky enough to have a stable build before the ota rolls out in the fall.
Sent from my MB855 using xda premium
Mine doesnt seem any warmer than usual unless I'm going non stop with it plugged in or something. Battery life is pretty tremendous on Beta too
I've not noticed any excessive heat. Been running this pretty hard since installing the from yesterday.
Sent from my CM9 Motorola Electrify
Ive been running CM9 and constantly keeping up with new releases since the first few Alpha builds. Mine gets relatively hot(45 degrees Celsius give or take) when doing something like gaming for a while or downloading large files over 3g. Other than that i have no heat issues, and i haven't had a single force close or random reboot on the latest Beta builds. If you go to it make sure to full wipe everything the first time and you should have little, if any, issues.
I'm running the 0.1.0 beta and the camera is supposed to be working right? I'm unsure if I have to do something. Because for me as of now it is not working. Any help?
minimeofctown said:
I'm running the 0.1.0 beta and the camera is supposed to be working right? I'm unsure if I have to do something. Because for me as of now it is not working. Any help?
Click to expand...
Click to collapse
I would try rebooting the phone a couple times. Some people ran into this issue and suggested it. Otherwise, I would wipe cache/dalvik and reflash the ROM and gapps and reboot.
Best
K
minimeofctown said:
Hey I was just wondering if anyone had the same problem as me or if its been asked before. But my battery gets hotter than usual now when I'm doing things such browsing or playing a game. It didn't do this is CM7.2 and I didn't know if this was a known problem with cm9.
Click to expand...
Click to collapse
If you go into the settings you can adjust how fast you will allow the processor to run. If you reduce this then you will have less heat from it working so hard. They are running a bit hot because CM9 unlocks alot of their true power.
minimeofctown said:
I'm running the 0.1.0 beta and the camera is supposed to be working right? I'm unsure if I have to do something. Because for me as of now it is not working. Any help?
Click to expand...
Click to collapse
How did you install? Try wiping dalvik and cache and fixing permissions. If this doesn't work, do a clean install.
What's up with the "gapps"? Apparently I've been gone too long.
Sent from my Photon via XDA
Google addon package. Includes market, gmail, search and several others.
Roger. Thanks.
Sent from my Photon via XDA
I wanted to see if I can post something without getting ridiculed. Seriously doubt that now cause I accidentally posted this in the general Q&A first and did not know how to move it or delete it so i am posing again here. Hopefully a moderator can just take care of that stray posting I made in the general area.
I am on my second ATT SGS2. First one had a GPS issue. Tried everything and finally convinced ATT warranty services that the problem was hardware. They said they would advance replace the handset. So I got it back to stock in every way except the flash counter,this was in December so long before I was aware of mobile odin. Flash counter was at about 12 when I was done trying different ROMs,mostly just try to get the GPS to work. It was in perfect shape, bone stock except for the counter. I cannot imagine I will have an issue, but has anyone ever heard of someone getting charged on a return to stock phone that had a flash counter above stock? Ill update once I know for sure the outcome.
My real question, does everyones SGH-I777 crash on occasion? If so how often? I so happy with the current code that is running on the phone with the exception that it sometimes sleeps and wont wake up, and sometimes it just plain crashes hard, locks up and has to be hard rebooted. Usually this happens about twice a day one or the other. I wiped before installing current kernel. The only reason I am not stock is cause I wanted the CKK6, 2.3.6 update to work and to keep root privaledges, but also needed my wifi cause ATT is throttling me down to dial up speeds when I reach 2GB. So wrong!!! Anyway thats another thread.
I loaded shostock with siyah kernel 2.6.35.14. after wiping everything including both caches. The GPS is solid now, phone is fast, battery is egh, I keep a charger with me... but it crashes hard from one to three times a day. Locks up playing tunes, or wont wake up with out being plugged in or hard booted. Do I have another defective handset or should I just go back to 2.3.4 and UKH7 or should I just deal with it and consider the crashes, "excellent opportunities to reboot."?
Thanks for the all the hours of fun, u know who you are.
I honestly don't remember my phone crashing at all. If it's crashing, it aint stable. Did it crash when it was stock?
yeah I mean duh right? The new handset was updated, rooted, downreved and flashed with the custom rom before it was put under any load, so I do not know if it would have crashed before. I have wiped, re downloaded, checked with hashtab and re flashed my current kernel, so it seems like it has to be hardware, again... ugh. Especially since no one else is having issues with shostock and siyah. I wonder how hard it is going to be to get warranty services to replace the second phone in 3weeks!? Lol.
Try going back to stock and run it for a couple hours to see if it still crashes. If it still crashes then more than likely hardware issues.
Sent from my SAMSUNG-SGH-I777 using xda premium
If it's crashing on stock without SetCPU to set a screen-off profile, you have a hardware problem.
I haven't had a crash, freeze, or spontaneous reboot in ages - despite running kernels that a few others have reported stability problems with (and I have effectively halted my kernel until I can get to the bottom of those reports...)
Too often is when it happens regularly, period.
I'm running CyanogenMod 9 and have almost no crashes, despite it being experimental.
Sent from my GT-I9100 using XDA App
I reverted to stock last night shortly after posting this. Ran fine until re loaded SHOstock v1.9.2-UCKK6. It is not "crashing" but it will go to sleep and not want to wake up again. I can sometimes plug in the charger and that will wake it up but other times I have to hard reboot. So no more crashing, but will not wake from sleep about 10% of the time. Not a huge deal, but its a bit weird because I know that the code I am running is ok, and it seems the hw is ok, so... not sure why this is happening. Anyway thanks all for your suggestions etc.
silashj said:
I reverted to stock last night shortly after posting this. Ran fine until re loaded SHOstock v1.9.2-UCKK6. It is not "crashing" but it will go to sleep and not want to wake up again. I can sometimes plug in the charger and that will wake it up but other times I have to hard reboot. So no more crashing, but will not wake from sleep about 10% of the time. Not a huge deal, but its a bit weird because I know that the code I am running is ok, and it seems the hw is ok, so... not sure why this is happening. Anyway thanks all for your suggestions etc.
Click to expand...
Click to collapse
This sounds like SoD (sleep of death) to me. I would recommend reading through Entropy's kernel thread (yes, it is a LOT of reading) but it might give you some insight into possible causes and/or solutions, and you'll get a great feel for where development on this device has come from, from the beginning...
I had the same problem using the latest siyah kernel, but never with entropy's. I would suggest flashing a new kernel.
Sent from my GT-I9100 using Tapatalk
1. To answer the OP question, I have experienced ONCE that was when I tried to run the Andy's TI-83 emulator on my virgin stock ROM. The result is either my fault or the application isn't compatible with the running OS.
2. With bone stock, it shouldn't crash at all. If it does, RMA.
3. If the owner(s) have "some fun" around it such rip it off, hack it up, install different kernels, different ROMs, ...... then please DO NOT complain the device is suck.
I've seen a lot of knuckleheads who tried to mod their devices, screw them up then claim "they're suck".
dandrumheller said:
This sounds like SoD (sleep of death) to me. I would recommend reading through Entropy's kernel thread (yes, it is a LOT of reading) but it might give you some insight into possible causes and/or solutions, and you'll get a great feel for where development on this device has come from, from the beginning...
Click to expand...
Click to collapse
Thanks this sounds like a plan. I have to do something things have gotten worse. About 3 out of ten times I go to put the phone to sleep now, instead of blinking out the phone takes a screen shot. My fingers are no where near any of the other buttons and it takes a screen shot over and over when I press the power button. I have to move around from screen to screen, hit the home button and then hit the power button to put it to sleep. Weird stuff, could be worse though. Did I say that I thought the phone sucks? I thought I read in one of the replies up there something like that. Aside from the GPS issue that was hardware related, and problems I have brought on myself because stock wasnt good enough, this is hands down the most awesome piece of electronics I have ever owned. iPhone smyphone. I just need to find the perfect turbo charged, rooted but as stock as possible configuration that is stable and I will be set. I really like where I am, hopefully the kernel you suggested does not change much but fixes the problems. Thanks again all.
Grab one of Entropy's DD Kernels and flash it with CWM. I'd suggest getting one from Jan or earlier. His latest ones are trying to track down a issue.
dandrumheller said:
This sounds like SoD (sleep of death) to me. I would recommend reading through Entropy's kernel thread (yes, it is a LOT of reading) but it might give you some insight into possible causes and/or solutions, and you'll get a great feel for where development on this device has come from, from the beginning...
Click to expand...
Click to collapse
axis01 said:
Grab one of Entropy's DD Kernels and flash it with CWM. I'd suggest getting one from Jan or earlier. His latest ones are trying to track down a issue.
Click to expand...
Click to collapse
Ok the noob is going to shine through here... but you say to flash with CWM. With my current config, when I enter recovery mode I am taken to the siyah kernel recovery console. Are we talking the same difference here, and when I go to flash as you mentioned can I do so with Siyah recovery or shall I flash with something that will give me back cwm first and then flash the config that you mentioned in your reply?
silashj said:
Ok the noob is going to shine through here... but you say to flash with CWM. With my current config, when I enter recovery mode I am taken to the siyah kernel recovery console. Are we talking the same difference here, and when I go to flash as you mentioned can I do so with Siyah recovery or shall I flash with something that will give me back cwm first and then flash the config that you mentioned in your reply?
Click to expand...
Click to collapse
That recovery will work. After installing the DD kernel, CWM will change.
Sent from my Galaxy SII
I get a crash here and there everyday...
Sent from my SGH-I777 using xda premium
Have only ever crashed while messing with voltages or clock speeds. if it's crashing something is wrong.
A few people's phones just do not play well with Siya kernal. Most of those people flash Entropy's DD and the sleep deaths go away... give it a try, I bet it will help!
Mine crashes a few times a day if I'm cycling through a lot of apps or installing things. (Stock+root) the other day my phone would crash anytime I tried, to watch a video in web browser. (Either mxplayer or phone)
Sent from my SAMSUNG-SGH-I777 using XDA App
T90 said:
A few people's phones just do not play well with Siya kernal. Most of those people flash Entropy's DD and the sleep deaths go away... give it a try, I bet it will help!
Click to expand...
Click to collapse
With Siyah I crashed more often than I do know with DD...
Sent from my SGH-I777 using xda premium
Ok flashed the DD from 01-30-2012
Thanks for all the help. I will post again when I know if things are better.
Currently on Rootbox 6.18b build. I get quite a few SoD but I can't figure out why. Anybody know the best way to monitor for it? It's not undervolting because I'm on stock kernel at stock voltages and all that jazz. The weird thing to me is that it happens while my phone is plugged in. My Atrix would give me SoD but not if it was plugged in. I can't figure out why my OG is SoD me. Any suggestions or tips appreciated.
Thanks.
SoupySauce said:
Currently on Rootbox 6.18b build. I get quite a few SoD but I can't figure out why. Anybody know the best way to monitor for it? It's not undervolting because I'm on stock kernel at stock voltages and all that jazz. The weird thing to me is that it happens while my phone is plugged in. My Atrix would give me SoD but not if it was plugged in. I can't figure out why my OG is SoD me. Any suggestions or tips appreciated.
Thanks.
Click to expand...
Click to collapse
Those of us getting them are still trying to figure out why. I haven't had one on the newer builds...
Sent from my Optimus G using Tapatalk 4 Beta
Thanks, I appreciate the response. Glad to know I'm not the only one lol. I mean I guess it could be that I am dirty flashing each build, but I have my phone set up perfectly to me and I don't know how to back up home screens and too lazy to restore apps and all that junk lol.
After you have one you can pull a log to help.
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
Sent from my LG-E970 using xda premium
SoupySauce said:
Thanks, I appreciate the response. Glad to know I'm not the only one lol. I mean I guess it could be that I am dirty flashing each build, but I have my phone set up perfectly to me and I don't know how to back up home screens and too lazy to restore apps and all that junk lol.
Click to expand...
Click to collapse
Actually, I think I've only had one or 2 actual BSoDs on houstonn's RootBox (I've been running it exclusively for quite a while...since early to mid April or so) and those were pretty early on. My main issue is hot reboots (which are MUCH less of an issue, more like just an annoyance really). I typically was getting hot reboots approximately every 40 hours of uptime or so, but occasionally in shorter timeframes. They were also most frequently happening when the device was idle, but occasionally it would lock up and reboot while in use.
Since roughly a week or so ago, I have not had a single one - since the update houstonn put out that fixed the issue with changing pages on the lockscreen triggering hot reboots. However, due to a couple rogue wakelocks (caused by apps) requiring reboots, plus houstonn's insane release cycle, I don't think I've gone over about 30 hours of uptime at a shot since then. FWIW, I've only clean flashed 3 times since I've been on RootBox - initial install, probably 3rd or 4th revision, and then around 6/16. I've had hot reboots after every clean flash, so I'm not convinced that's a fix. Every other update I've done (almost all of them) have been dirty flashes.
A few people have been able to grab logs of events close to the times they've gotten reboots, but to my knowledge, so far, they haven't included any info that has been useful to houstonn in tracking the issue. If you are going to be chasing the issue and trying to get logs, you should probably stay updated to the latest build...this will eliminate logs showing problems caused by issues that have already been fixed. I believe houstonn, like most other devs, only provides support for whatever the current build is.
I think most of us who are having these issues on this ROM (and it appears we're a fairly small percentage of the userbase) are getting hot reboots, rather than full-on BSoDs.
dandrumheller said:
Actually, I think I've only had one or 2 actual BSoDs on houstonn's RootBox (I've been running it exclusively for quite a while...since early to mid April or so) and those were pretty early on. My main issue is hot reboots (which are MUCH less of an issue, more like just an annoyance really). I typically was getting hot reboots approximately every 40 hours of uptime or so, but occasionally in shorter timeframes. They were also most frequently happening when the device was idle, but occasionally it would lock up and reboot while in use.
Since roughly a week or so ago, I have not had a single one - since the update houstonn put out that fixed the issue with changing pages on the lockscreen triggering hot reboots. However, due to a couple rogue wakelocks (caused by apps) requiring reboots, plus houstonn's insane release cycle, I don't think I've gone over about 30 hours of uptime at a shot since then. FWIW, I've only clean flashed 3 times since I've been on RootBox - initial install, probably 3rd or 4th revision, and then around 6/16. I've had hot reboots after every clean flash, so I'm not convinced that's a fix. Every other update I've done (almost all of them) have been dirty flashes.
A few people have been able to grab logs of events close to the times they've gotten reboots, but to my knowledge, so far, they haven't included any info that has been useful to houstonn in tracking the issue. If you are going to be chasing the issue and trying to get logs, you should probably stay updated to the latest build...this will eliminate logs showing problems caused by issues that have already been fixed. I believe houstonn, like most other devs, only provides support for whatever the current build is.
I think most of us who are having these issues on this ROM (and it appears we're a fairly small percentage of the userbase) are getting hot reboots, rather than full-on BSoDs.
Click to expand...
Click to collapse
I thought hot reboots was when the phone actually rebooted itself and did not get stuck at a black screen. I'd much rather have that than bsod. I'll probably update to the latest rootbox and see if anything changes. I should probably look into whether or not I'm getting these hot reboots.
SoupySauce said:
I thought hot reboots was when the phone actually rebooted itself and did not get stuck at a black screen. I'd much rather have that than bsod. I'll probably update to the latest rootbox and see if anything changes. I should probably look into whether or not I'm getting these hot reboots.
Click to expand...
Click to collapse
You are correct. BSoD will have you stuck at a black screen (sounds like that's your issue). A hot reboot, the phone will freeze up for maybe 5 seconds, then drop to the boot animation and re-boot - more of an annoyance, and something to make a user mildly concerned about stability.
Good afternoon-
Great phone, but has anyone else had bad operating system luck? Seems like my phone is freezing and/or locking up daily, and needs to be re-booted. If it were windows I'd call it a BSOD incident. My S3 running Paranoid Android nightlies was even more stable than this.
Tim
I am not having problems like you report at all. The only lockups I had were during the brief period when I ran under ART, and they went away completely after I switched back to Dalvik. Note that under ART my G3 got really hot...
That is what I think is causing most of these phones troubles. I think they were designed in a way that is prone to overheating issues. I also think the designers tried their best to avoid overheating through throttling - which causes some performance degradation, and doesn't always work anyway.
Minor assembly differences could be causing major differences in how different G3s heat-load. This could explain why some owners who have reported lockup issues like yours have gotten much improvement by exchanging their phone, which is what I suggest you do if you can.
moonfarm said:
Good afternoon-
Great phone, but has anyone else had bad operating system luck? Seems like my phone is freezing and/or locking up daily, and needs to be re-booted. If it were windows I'd call it a BSOD incident. My S3 running Paranoid Android nightlies was even more stable than this.
Tim
Click to expand...
Click to collapse
I agree with Trent. Seems some G3s just don't run well. Mine runs great. I have it rooted with xposed and have removed the bloat and no issues at all. I couldn't be happier.
I've even played some games for the first time on my smartphone including Asphalt 8 and I've played it for about an hour non stop the other night while I had time to kill and still no issues, the game played great, phone didn't heat up and get laggy.... Nothing. It just played.
Hard to say really what's causing the issues for some, could be a funky device, maybe a factory reset would help... Maybe people also should take a look at what apps and widgets they have running as well prior to thinking the phone is junk lol not saying that's you, just an idea
- Tapatalked from the G3
moonfarm said:
Good afternoon-
Great phone, but has anyone else had bad operating system luck? Seems like my phone is freezing and/or locking up daily, and needs to be re-booted. If it were windows I'd call it a BSOD incident. My S3 running Paranoid Android nightlies was even more stable than this.
Tim
Click to expand...
Click to collapse
No problems with mine.
What apps and widget are you using?
tech_head said:
No problems with mine.
What apps and widget are you using?
Click to expand...
Click to collapse
It's a pretty random problem, hasn't happened for a couple of days. I run a pretty lean system, not a lot of apps or widgets. Maybe getting rid of some bloat would help. Thanks all, nice to know it's not something everyone is going through. I'm enjoying the phone more than I thought I would, been on the S series since the first Galaxy Fascinate, so this was a bit of a leap. The combo of Knox and Touchwiz did me in...
Tim
I'm wondering if the accessibility service has anything to do with these random shutdowns. I've never turned on ART, but with several xposed mods, tweaksbox, and some debloating, my phone seemed stable for the first few weeks I owned it. One day I had a random reboot. It didn't happen again for a week or so, and then it happened once more. A few days later I noticed one of my tasker scripts (which reroutes gmail notification sounds through the headset iff the headset is connected) wasn't working. I checked the tasker accessibility service and it had turned itself off. After re-enabling it, my random shutdowns soon returned.
Anyone care to try ART with all accessibility services uninstalled? This would include talkback.