I have a 16GB International Samsung Galaxy S3 (XEF) running the latest firmware, 4.1.2 (yes, the Premium Suite update, I was thinking that this would've fixed it but it seems not) with baseband XXELKB. Over the last week and a half, I've noticed my phone randomly freezing and/or restarting itself. I investigated further. At first, I thought it was to do with apps on the device, so I started recklessly uninstalling apps, to the point where I factory reset the device. No dice. Even with not a single non-stock app installed, it still managed to randomly freeze after a few hours of use. I went googling and discovered that my device is likely suffering from Sudden Death Syndrome, and I'm willing to think maybe I have that. Went through XDA forums, and found eMMC Check . According to that app, I have the affected 'insane' chip. There's a few quirks that I have, however: 1. Is this consistent with the Sudden Death Syndrome (SDS) that people are reporting? 2. Wasn't this bug supposedly fixed with the Premium Suite update? 3. How do I go about fixing this, for someone who has never rooted/flashed a Android device before? 4. How do I go back to stock firmware/kernel after it has been fixed by Samsung? Any help, even if it doesn't solve my issue, will be much appreciated. Cheers in advance.

I've installed Android 4.1.2 on the Samsung Galaxy S Advance. I cope with a problem that more Android users have to deal with. The well-known android.process.acore force-closing (FC) or something similar. The constantly appearing FC notifications would be caused by your crashing contact list. However, I cannot find a solution for this anywhere while many users have this problem. It is really annoying when you have to open WhatsApp 3 times because the whole system freezes. I've tried the options they give in [force-close tag-wiki](https://android.stackexchange.com/tags/force-close/info) , but rebooting and resetting obviously wouldn't help, and deleting contacts isn't the solution. When I really can't use those FCs at the moment, I just temporarily freeze my contact list, but it is such a hassle to do every time. I also tried to avoid the FC, but logcat is turned off and it doesn't help. Isn't there a way to hide those notifications?

So, the battery on my Samsung Galaxy A3 drained completely. Then I plugged in USB cable, and the empty battery logo appeared - and nothing else, to graphics to indicate it was charging: I left the USB plugged in for some 15-20 minutes, then I unplugged it. Now the screen STILL shows an empty battery logo, even after some 15-20 minutes after unplugging. I had kept power button pressed for more than 30 seconds, nothing happens. I had kept Volume Up + Power button pressed for more than 10 seconds, in hopes it would reboot to recovery, nothing happens. I would have taken out the battery at this point, but this damn phone does not allow the battery to be replaced. What do I do now to get this phone working again?

I'm a Samsung S3 user. After I updated the OS to 4.1.2 (official release), my screen keeps on freezing. I'm fed up with those freezing situations. Any solutions for that? Thank you.

My Samsung Galaxy S7 is completely unresponsive for day and a half, black screen, only blue LED is shining with a slight pulse. According to [this guide](https://www.samsung.com/uk/support/mobile-devices/what-do-the-notification-light-colours-mean-on-my-samsung-galaxy-smartphone/) , it means "the device is turning on or off". For a day and a half already! So I tried this advice: > Press and hold the “Power” and “Volume Down” > buttons for eight to twenty seconds and the device will eventually > turn off. Then I tried [this advice](https://forums.androidcentral.com/ask-question/992633-galaxy-s7-wont-turn-wont-force-restart-blue-led-solid.html) : > Try pressing and holding Power and Vol Down for about 30 seconds, then > wait a few seconds, then press and hold Power again for another 30 > seconds. Then I tried different sequences [as advised here](https://www.youtube.com/watch?v=LP4sD3AAWEA) : > up+power 20 secs > down+power+home > up+power+home Nothing worked. Charging didn't help. Before this happened, my phone was gradually slower and slower in the last month, until it became super slow, as I [asked here](https://android.stackexchange.com/questions/247038/what-to-do-when-phone-is-super-slow) . Some time before the freeze happened, I also removed the SIM card and micro SD card from the tray. Now I put back the SIM card, the system still stuck. PS: 10 minutes after the key combo attempts I noticed the battery and display is heated. Interesting. PS: after 2.5 days the battery finally died and the blue light stopped pulsing. I charged it a little, but now it doesn't even turn on. No response whatsoever.

First of all, no root since I didn't want to mess with knox bricking my phone. The problem started tonight when I wanted to buy PlayStation Plus from the PlayStation App. For some reason, the app hung my entire phone so I had to do a soft reset. After that, it would boot up, but before everything would load up, it would freeze and then restart again. I tried to figure out what process was doing this by going into the running applications, but I could only get there sometimes before it froze, and the times I did get there I couldn't get any worthwhile information. Next thing I tried was a factory reset by holding the power and volume down button during boot and it sat there for about an hour stuck at installing system update. The animated Android had stopped moving and the phone was basically melting the table it was on, so I soft reset it again. After that I booted into the Android system recovery to try a factory reset from there so I wiped the cache partition and went to "wipe data/factory reset" the readout looks like this. #MANUAL MODE# -- Appling Multi-CSC... Applied the CSC-code : VZW Successfully applied multi-CSC --Wiping data... Formatting /data... Formatting /cache... -- Set Factory Reset done... -- Copying media files... -- preload checkin... E:failed to mount /preload (No such file or directory) Data wipe complete. Also the recovery freezes up after a while as well... I tried just a normal boot again and it seems like the phone has been reset to factory but the phone freezes during the setup and then resets. I am at a loss of what to do next I can't really be without a phone for a long period of time as I need it for my job. Any help would be very much appreciated.

I have a Medion P5015 and I've tried rooting it with Kingroot and Kingoroot together with the PC and Android versions but to no avail. Now when I try to connect my phone to my PC with the provided data cable, the screen freezes as soon as I plug it in. Soft buttons & hard buttons do nothing. After a few seconds, it reboots to the boot screen but goes to a black screen and goes back to the boot screen, and goes on. When I unplug it during this stage, it cuts off then I have to manually power it on with the power button, quite absurd if you ask me.

Sometimes my Sony xperia z5 just start freezing, clicking on apps, turning drawer's pages and doing things like that without me doing anything . In my opinion it looks like a problem with the touchscreen and the display because it's like if someone touches it but nobody is actually doing it, I am also pretty sure that there isn't any virus . Do you have any idea about the causes of this? Ps: My phone got the latest firmware and not a modified rom

I have a very annoying problem with my phone's Google Apps, which I cannot resolve or even diagnose. It affects Google Play, Google Maps, Chrome, YouYube, Google Settings, Account managing, and probably other apps. All of these freeze when I try to access them and after a while the message "(App) isn't responding" appears. Interestingly, the Google app (the search engine), the Gmail app, and Google Translate function properly. At first, I though I got a virus or some new update caused the problem, so I cleared the data of Google Play and restarted the phone. Unfortunately, for no avail. Next, I thought it's an Internet connection problem, however, other apps which need web access work fine (e.g. Evernote, Duolingo, a racing game /Top Drives/ that I play from time to time, and even my secondary browser /UC Browser/). For this reason, I took drastic measures and reset my phone to its factory settings (without restoring any previous data). Again - nothing. On top of everything, my battery suddenly started draining away faster than usual and I suspect Google Play services to be the cause of that. When I checked my Battery history, I saw that even under idle mode, Google Play is using CPU for something. I should point that after I reset the phone, I entered *play.google.com* from my other browser and noticed that the site still thought that my old apps (the ones which I used to have before formatting my phone) were still installed on my device. Clearly, this means that Google Play and my phone don't synchronize properly. At this stage, I'm left in the dark. I have no idea if the problem is software, hardware, or authorization related. I should point out that I borrowed an old smartphone from a friend of mine and was able to load a functional android configuration on it with my Gmail. Does anyone know what may be the cause of this issue or who has experiences something similar? I already read all standard solutions listed on the Google Support forum and none of them worked. PS My phone is Lenovo P1 Vibe, less then 2 years old. My Android version is 5.1. Last time I could use the phone normally was 2 days ago, when I watched a show on the Internet before going to bed. I noticed the problem after I charged it the next morning.

Recently my LG Volt has started to freeze on my home page when I turn my phone back on. Will not open when I swipe or tap. I have to do a power off-restart in order to get it to work, and sometimes I have to do this several times before the swipe function will respond. I've tried removing the battery but even this only helps for a short time. Any suggestions on a fix or has anyone else experienced this?

I have an Allwinner A10 tablet clone. While working the tablet "freezes" regularly but not too frequently for a strech of time between 2 and 15 seconds. Described differently: the tablet is useable but the nice "fluid" workflow is abruptly interrupted once in a while... Situations: - e.g. when opening an additional tab in firefox when already having a few open, - when working with the tablet while downloading a file, these freezes are more frequent - etc Using the process overlay option from developer settings I realised that during this time the "nandd" process is consuming CPU almost exclusively. It does not appear to max out the CPU but during this time none of the other processes consume more than minute amounts of CPU time. Can somebody tell me: 1. whether this is "normal" behaviour 2. whether an update to CyanogenMod 10 is likely to help 3. where issue is likely to lie: with slow nand hardware or poor nand driver implementation. Many thanks.

On Linux: All fastboot commands lock. Particularly fastboot oem unlock or fastboot flashing unlock. After removing and re-attaching the phone to the usb port (without turning it off), the phone becomes detectable on the usb, thus the usb connection handshake runs, but it is not listed in fastboot devices any more. The only way to fix the phone at this point is removing-reattaching the battery into it. I believe, it might be a full system freeze. The usb id of the device is "fastboot Gadget", with the google vendor id. On Windows, no fastboot driver was working (not the google and neither the mtk). They simply did not find the device. I've seen also multiple limitations in the (not yet rooted) phone: for example, adb shell gets the shell as usual, but /dev is already forbidden. I suspect, maybe the manufacturer has a dislike of rooting and it is a low-cost attempt to make it impossible. Is it possible? Where could I even start to find the cause of the problem? *Extension:* I could make the ADB fastboot driver working on Windows (with the Google driver in the the latest Android Sdk), and also the device was visible in fastboot mode. The result was essentially the same: usb-level lock requiring battery removal to make the phone usable again. I tried it on multiple machines, and on multiple OSes, and the problem was always the same. *Extension #2:* To be clear: the device shows an mtk driver in adb mode, and a spreadtrum driver in fastboot. fastboot oem unlock locks the phone on a way that only removal of the battery can fix it. It happens on multiple machines, with multiple OSes. However, Wiko's own update tool, downloadable from here , works. It is a windows-only tool, capable to install only the Wiko's own updates. I am now playing with this tool, what it does and how. Maybe it can flash also a custom firmware. If it won't work, I will forever blacklist the company and throw the phone out.

Recently I updated my device from android 9(one UI 1)to android 10(one UI 2) After updating to android 10 it freezes again and again,not the whole phone freeze, only display hangs but background working properly, when i push power button and lock device, and after unlock by power button it works normal, but after sometime it freezes again. I repeat this task again for unfreezing. I checked device logs for hangs reason, where I found EGLNativeWindowType 0x79466cd890 disconnect failed It looks like openGL problem, is some driver corrupt or missing in new update, Samsung block downgrade from bootloader,So I have no choice, Note:*I updated with latest ota update,there is no new update from Samsung, *Device was working well with android 9 one ui1(means there is no hardware fault) * Model: samsung sma750f

I have a TB-X304L. I rooted this guy with magisk and whenever I try to write or try to change permissions of the /system directory, the tablet just freezes and I have to reboot it with long pressing power and the volume up button. I can't even make changes to the build.prop file. The same happens when tried with adb. I could get root access in adb shell. when I try,

cat > testfile.txt

it says read only partition. So, I mounted it with rw permission command

mount -o remount,rw /system

it runs smoothly. But when I try

cat > testfile.txt

again and type some text for the test file and press Ctrl+D, it freezes. I am new to all these please help me guys.

Since some time my Samsung Galaxy 9+ sometimes freezes. I have the impression that this is somehow related to Chome but I am not sure (maybe it is just because I spend there more time than on other apps and statistically am on it when the freeze happens) This is a total freeze for ~10 seconds, then everything works again. The screen is on, the phone is just not reactive. Would there be a way to monitor the phone and pin point the app which makes the phone freeze? (due to overuse of some resources)

I have a Nexus 7 2012 wifi. With the latest version of Lollipop it has really become unusable, freezing for a minute or more, or even rebooting while loading a page in Chrome. I did a system reset, but that did not change much past the few first minutes. What is the recommended version to have again a usable tablet? Is anyone having a "runbook for dummies" to install Android 4.x (or CM or whatever works fine) ? Most of the tutorials I found on the Internet are for geeks wishing to experiment. I just want a running system with minimal fuss/risk.

I recently made the mistake of rooting my Galaxy S4, accompanied by a few more customizations. Problems that occur: - TouchWiz freezes. One way to unfreeze is to hold down the Home button to see recently opened apps and then go back, so that Touchwiz wakes up. The other way is to pull down the Notification bar and click Settings or anything else from there that'll send me to a different app so I can avoid it. If I don't do any of these within 5 seconds the freezing occurs, the device restarts. - The device also restarts when the CPU is *suddenly* expected to work hard. For instance, within the first minute of a call, or when the screen is locked/unlocked, a couple seconds after opening a music file. This happens 3-5 times a day, depending on usage. The restart is not always preceded by a freeze, but often there's a freeze before the restart. Recent changes that may be causing such behaviour: - Rooting using AutoRoot by Chainfire. - Giving CPU Master root permissions after SuperSU is installed. - Installing busybox. - Patching modded Google Play Store (involves patching Core.jar package) What I did so far: - Uninstall CPU Master. - Delete cache and data of Touchwiz - Remove busybox - Remove all custom patches from core.jar - Install the original Google Play Store and update to latest version I don't think Touchwiz is causing the crashes because somethimes the phone restarts while an app is in use. Thanks in advance. EDIT: I removed the original Samsung ROM altogether and switched to Cyanogenmod. Thus I may not be able to upvote/tick the replies from then on.

Phone is Oneplus One running Cyanogenmod (usure about the version but it should be the latest released to OpOs) It all started after a metal detector scan - the phone would work for 20-30 seconds fine and then the screen would freeze indefinitely. Upon restart you could see the same behaviour. Once I was back home I plugged it to my laptop to try to retrieve some of the data and noticed that while connected the phone was absolutely fine. This led me to believe the issue is software related so I did a factory reset. Unfortunately, after that the issue remained so I decided to try to flash the ROM. Started by turning off my phone so I can go into the fastboot menu but now after turning it off it won't turn back on. I'm certain that it isn't a battery issue but I'm running out of options. Neither power + vol up or power + vol down work at the moment and connecting it to the laptop does nothing. Any suggestions what to do next?

Is there any reason a programmatic or command-line shutdown (or reboot) process in Android 7.1 might randomly result in a hard freeze-up, requiring a long (~8 second) press of the power button to force the shutdown? It doesn't happen every time, but seems to randomly happen infrequently, but frequently enough to be a problem. ***Background Info...*** I'm developing a "kiosk" style tablet, which runs 24/7. It's rooted and I have full control over it. It also has a customization from the supplier to automatically turn on when power is connected. To keep things fresh and responsive, I want to issue a nightly reboot command. The reboot command was originally just a call to /system/bin/reboot -p via my own app "watchdog" kind of service that always runs in the background. *(Yes, I know the -p causes the tablet to turn-OFF, but then our custom auto-boot will turn it back on immediately, if power is connected, resulting in a reboot situation... doing a pure reboot without the -p causes more problems)* Anyway, I've since moved on to experiment with all of the following commands to cause a shutdown/reboot, and none really fix the problem. - /system/bin/setprop sys.powerctl shutdown - /system/bin/svc power shutdown - /system/bin/am start -a android.intent.action.ACTION_REQUEST_SHUTDOWN - /system/bin/busybox poweroff -f - /system/bin/busybox poweroff -d 10 -f One more bit of info... I made an app to shutdown/reboot the device every five minutes. I've been running it on about a dozen devices, and have about 4 or 5 failures every 24 hours.

The other day I woke up, my Android phone was frozen and only removing the battery helped to reset it. It looks like overnight something terribly went wrong as the memory card was not readable anymore and even after formatting it, it got a few bad sectors in the report. I have about 150 applications installed and some of them which were moved to the memory card obviously do not work anymore. I had backup of my data but not the apps, as I thought I could always download them again. However, I can not find an easy way to do it. First of all, the corrupt applications still show up under settings/applications/manage applications, but the only way I can tell if they are missing or not is that their icon is some default Android robot with an SD card next to it and the names are not human friendly but more like com.biggu.shopsavvy. I tried different apps to solve the problem, but I could not find any which would be better than doing it manually. What I need is to either reinstall all apps with a tap of a one button or install a list of apps in batch from the market.