Hi,
Before creating this topic I tried to run some research but I haven't found anything useful that would explain my phones recent behavioural problems. The problem with my i9300 is that the phone freezes at random while Android is operating. This happens in settings, while apps get updated, when getting phone calls, when opening an app, when registering a google account (new setup), when opening SMS app... The sreen stops responding, none of the hardware keys do anything and all I can do is take out the battery. It's just crazy and does not seem to have any rules to this madness. The problem started after flashing a new version of Sentinelrom (and CMW supporting android 4.4.2 installations). This is what I already tried to troubleshoot/resolve:
- flashing another recovery (now on latest PhilzTouch)
- flashing other roms (UltimaAOSP Valhalla, latest CM11 nightly, CM10.2 stable, Slimkat ROM) with full wipes, dalvik cache cleanup etc.
- flashing boefla kernel (during Slimkat tests)
- formating \modem
- formatting externalSD (was and is on exFAT)
- taking out externalSD for a longer period
- restoring apps from google instead of titanium backup
- not restoring any apps and settings from google
- installing apps selectivly
Nothing helped although the phone was running most stable on UltimaAOSP Valhalla (3 freezes during one day). The freeze never happened during playing a movie or listening to music. The freeze never happened while in recovery mode.
Does anyone have any other suggestion on what I can do? Any input appreciated!
Maybe your device is affected of the Sudden Death Syndrome.
Try eMMC brickbug Check from Google Play.
mischa_martin said:
Maybe your device is affected of the Sudden Death Syndrome.
Try eMMC brickbug Check from Google Play.
Click to expand...
Click to collapse
Thanks for input. I run the check. The chip may be affected by sudden death, but all of the roms I've tested (now testing Android Revolution based on 4.3 stock - 3 freezes just today) have the fix implemented. Also I have had this phone for almost 2 years now. The internal memory check within this app also found no errors. So I guess it's not related to SDS.
Freezing is usually due to nand memory having bad blocks, read the freezing thread in general forum.
Sent from my GT-I9300 using Tapatalk
Related
Morning guys - i'm a sort of noob (go easy.!) that needs help with my HTC desire. I took plunge and decided to try rooting & applying custom ROM, but now have problems with the screen freezing completely at any point, then on restart the phone boots into the home launcher but screen does not respond or will not wake.
So far:
Rooted with unrevoked
HBOOT flashed to Cm7r2
Latest version of clockworkmod recovery via app
Aurora 4.1 (all dalvik caches wiped at correct points).
V6 supercharger applied on setting 5 (balanced).
Tried with kernel built in ROM (0.7) & gingercakes 0.9cfs no2way havs.
SD card partitioned with GParted (fat32 primary, 2gb primary ext4).
I've had the ROM working fine, the only other thing i can place it to is swapping the SD card, which i've changed from 4gb class to, to a samsung 16gb class 6. Does anyone think that this error could be anyway caused by the fact the card readers i've used (tried 2 different readers) both have had trouble recognising the 16gb card?? (Gparted still recognised it however)
Is it possible to be a hardware issue? Please note recovery works perfectly - wiping caches, reinstalling zip files, backups etc.....only problem is now this freezing of home launcher and no response.
Any help be greatly appreciated, give me a nudge if i haven't given enough detail.
Regards, Nick.!
Additional:- Tried unsupercharging & rebooting - no difference.
Only other thing i can think that i've done prior to the fault is attempting to install busybox for V6 supercharger - which failed every time and affected my root access on the phone. I've found that the Aurora ROM has busybox installed already. However, is it possible me trying that install has somehow affected the rooting of the phone?
So many questions, sorry guys!
Bump.....would ADAO file manager (which isn't on google market I notice) affect anything on ext4 perhaps? That was one app that i downloaded from net.
Have you tried reverting your busybox to the default version? Also, are you overclocking and or overclocking? Going to high or to low with CPU speed can cause problems like that. It has also been said that partitioning an SD card can damage them, which may be an issue you have now. You could try formatting the SD card to its default state and run like that for a while. I ran a 16gb SD card in a Droid Eris for months and it never caused a problem like that. Of course, I didn't have a partition set up on it.
Sent from my ADR6350 using Tapatalk
I've literally left the settings for speed in daemon controller alone, although i'm still learning and not sure if they are default overclocked or not?
Possibility with the SD card, i'll give it a try for sure, that'd mean i'd have to revert to an alternate ROM would it, as Aurora specifies an ext4 partition?
Thanks again though, it's a start at least
Do you set profiles in SET CPU?
Accidentally sent from my Google Nexus S using XDA Premium
Excuse noobie brain here, where will i find those CPU settings?
If so, fully wipe and install again. And what rom are you using currently that causes freeze?
Accidentally sent from my Google Nexus S using XDA Premium
Aurora V4.1 ROM i'm using. Don't think it's the ROM itself as i have had it stable for week or so, before swapping SD card from 4gb to 16gb.
I'm thinking this may be the root cause as i've just tried a complete fresh partition with Gparted & fresh install of literally just the ROM itself and on first boot it froze again. Rebooted and now seems to be stable with nothing reloaded back on it but we'll wait and see. If it freezes again i'll try my 4gb card. Didn't want to revert back to that as its only class 2.
[Q] Noob help - Rooted desire keeps freezing.! Update...!
UPDATED - Still getting same problems - have now tried a different SD card & alternative ROM (Cool3d v5).
Is it possible it could be heat related fault? The more i use the phone the more readily it happens - from the occasional freeze (okay after reboot) to complete freeze and no response on every reboot.
Does the CPU therefore have a cut out or could be freezing based on the settings that are initially loaded through daemon controller? What are safe settings for the min/max values?
Only other thing i've noticed is once fault starts to occur - clearing dalvik cache in recovery is quite unresponsive - menu holds before allowing me to clear.
Got to get to the bottom of this - don't want to revert back to original, or throw my phone in the river!!
Save clock is 1ghz. No over clock is the safest.
Do your phone wear case? If yes, it may be the caused of heat.
I'm sure the rom caused you the freeze. You can try to change a more stabler rom, eg aosp
Accidentally sent from my Google Nexus S using XDA Premium
Bit more progress - as my phone literally would freeze on loading home launcher, i connected it to pc and mounted via recovery - and deleted everything i could see for V6 SUPERCHARGER - and hey presto, very slowly, but phone booted up and is now working again.
I see the devs of V6 say about removing hardtokill if any lags occur - i think it's this portion of the script affecting my bravo.
SO, i'm going to run it totally without V6, and may try to just run the memory portion, but the instructions to disable hardtokill are a little unclear to me, could you guys tell me in simple terms how to acheive??
Thanks again for all your responses, a great help
V6 now off and all fresh re-installed with cpu max turned down also, and set to ondemand gov, will see how we go
[Q] Noob help - Rooted desire keeps freezing.! PT3.!
Still no joy with this issue guys - pulling my hair out now - after a few hours use (usually overnight) phone just freezes, then freezes on reboot, before getting worse and now will not pass alpharev's boot screen.
Installing fresh gets me into home launcher, but becomes unresponsive and freezes again.
I've tried different ROM's, different SD's, basic clean install, all without any luck. I'm thinking now it is more a hardware issue with the phone?
nikh667 said:
basic clean install
Click to expand...
Click to collapse
Did you wipe data/cache partitions/dalvik cache before flashing the rom? Did you wipe dalvik cache and cache partitions after flashing the rom?
Yep all wiped before and after.
nikh667 said:
Yep all wiped before and after.
Click to expand...
Click to collapse
Have you tried flashing a new kernel?
Yep fault happens with any kernel I've tried (so far 0.9c no2way havs cfs, also 2way version, 0.8f cfs havs, 0.7c)
nikh667 said:
Yep fault happens with any kernel I've tried (so far 0.9c no2way havs cfs, also 2way version, 0.8f cfs havs, 0.7c)
Click to expand...
Click to collapse
Has your device went through any physical damage (around the time the problem started)?
No physical damage apart from the battery cover being pulled off more than once(!) and a lot of obscenities being flung it's way, lol! But no, not dropped or damaged at all.
I've used the phone now all afternoon, longer than normally, with the same details on same hboot, but left some of the sense widgets off the home launcher, and it hasn't locked up once.
I have a problem with occasional hot reboots of my device.
Description of the device: international galaxy s3, omega Rom (from the day of purchase, now it's 33.3), siyah kernel (also from the very beginning, now it's 1.8), extsd2intsd mod. No OC or UV is required to replicate the problem.
Typical situation when it happens: I read news in flipboard, use touch translator to translate selected word, goldendic opens.I try to edit the word in the search bar of the dictionary (by pressing backspace), and at this moment device hot-reboots itself. Hot reboot also happened in other programs (one time I was also editing search bar when it happened, another time I tried to copy a text fragment).
I thought that Swype keyboard might be the cause. So I froze it in Titanium backup. However, reboot happened with Samsung keyboard.
It's important to mention that sometimes I can replicate the reboot (playing with flipboard and dictionary), but often device works perfectly despite my attempts to cause hot reboot.
Finally, the most important part: hot reboots do not happen when I have either V6 Supercharger or Bestmultitaskingfix working. That's why I think that it's a software problem. However, supercharger causes TW redrawals plus bad multitasking (at least the version which comes with omega Rom), and Bestmultitaskingfix causes lags on my device, so I don't find them to be a decent solution.
I tried to overload ram with opened apps, but nothing happened, old apps simply closed.
So, I think that the solution could be a bootable tweak which is used in both V6 Supercharger and BestMultitaskingFix. However, I'm not aware of the structure and tweaks used in these scripts. May be someone with experience in this area could suggest something?
I would like to hear your suggestions about the problem. Any ideas will be greatly appreciated!
Update: vibration is not the cause. Device rebooted even with tactile feedback turned off.
Make a nandroid backup, and flash stock rom + kernel and do a full wipe. Test it for a little while, and see if it persists.
xSpeced said:
Make a nandroid backup, and flash stock rom + kernel and do a full wipe. Test it for a little while, and see if it persists.
Click to expand...
Click to collapse
Flashed the stock firmware (ICS - I had nandroid backup), did full wipe. So far, no reboots were observed (intentionally played with flipboard and golden dictionary). Seems that it's a software problem. Still, I need to fix my omega rom somehow...
A clean flash for Omega might be a good idea.
Frequent random boots can be the beginning of "sudden death"... look for this thread in General section....
So the other day i flashed a new ROM i forget which one (flashaholic)
Anyway when it loaded the initial setup enter gmail etc.
The screen started flickering then turned off it done this each time i turned the screen on
I rebooted it done the same again
After i eventually got it setup it stopped
I have since flashed several other roms Dual boot etc.
Some of these roms i have used before with no problems BUT
Now the roms seem to run fine for the better part but become unresponsive for a few seconds when installing apps from market
I use go backup and phone screen has turned of in the middle of restore several time with several roms and wont come back on unless i reboot
I have tried alternative backup restore apps with the same outcome
It seems my internal memory has suffered some sort of problem as these problems only seem to occur when the internal memory is being written to
For the record i use superwipe script before each rom install
Anyone else experience anything like this
The short "stuttering" when installing an app from Play Store also happens to me, but well not really a big deal.
Did you try to flash a stock rom and stock kernel to start with? In addition maybe a mega wipe would also help to format all partitions (except the important once of course).
I believe it is the megawipe script i am using the problem persists when apps are updating phone becomes unresponsive
It reminds me of my HD2 days when the system was installed on both the internal and external memory
chrismast said:
The short "stuttering" when installing an app from Play Store also happens to me, but well not really a big deal.
Likewise over the last few versions of JB #Especially on multiple installs .
Same on Note 10.1 so it looks like a Google problem .
jje
Click to expand...
Click to collapse
Hi,
[Sorry for the long post, but please, bear with me. This issue needs a lot of explaining...]
It's been a few weeks since I have been experiencing this weird problem with my phone. It started when one day I picked up my phone and saw that process.android.gapps had stopped. So I did what everyone does and cleared the cache, wiped the data, but still nothing happened. I went over and cleared it for play services too and that reset my google account (no idea why) and everything came back to normal. Or as I thought it did. A few days later, I again had the same problem in front of me, except that it was not just gapps this time, it was a ****load of a few more apps, including process.???.acore, all giving ANRs. Plus my google account got erased somehow so play store won't login and all other unnecessary stuff.
So I got frustrated and went over to the recovery and tried to factory reset. And this is where I realized something. IT DIDN'T HELP! The phone started as normal and I saw the startup screen. But as soon as I started entering my details, all the ANRs came back simultaneously.
So I did a lot of other stuff to rectify this, all in vain. Skip to 8 hours later. This is where I realized, some of the apps in /data/data had got corrupted and hence nothing was happening. Also, formatting /data resulted in an error, which I HAVE NO IDEA WHY TILL DATE.
So I did a workaround and renamed /data to something so that the android OS could create a new /data, which IT DID on the next reboot! And all was working fine again.
FOR A FEW HOURS.
Again the same ANR, same everything, no access to /data to format it etc etc.
Again renamed and rebooted and reinstalled Blisspop and gapps and everything.
And this has been the scene ever since.
What aggravates the situation?
A REBOOT
Whenever I reboot my phone, be it soft or hard, It corrupts some or the other app in /data. If I'm lucky it's a non essential app. If not, xx.xx.xx has crashed and the phone is unusable. I usually use ES and try to rename for the non essential apps (as deletion isn't possible), but for the essential ones, a reflash with whole /data/data renaming has to be done.
So basically this is the problem. I have no idea why my /data/data corrupts randomly, or whenever I restart. Could it be because I greenify apps? I stopped using deep hiberation but still this occurs. Or could it be a failing internal memory?
Please Help! I am just frustrated. Might go over to G3 soon if this doesn't work out.
Specifications:
Phone: i9300
ROM: Blisspop-v3.2 12/05/2015 [Stable]
Android: 5.1.1
Kernel: 3.0.31-CM-g00ac77b
Recovery: TWRP (Latest Version)
Gapps: Minimal Gapps
Baseband: I9300XXEMA5
Bootl: I9300XXEMD3
Insane Chip: YES
xKGx said:
Hi,
[Sorry for the long post, but please, bear with me. This issue needs a lot of explaining...]
It's been a few weeks since I have been experiencing this weird problem with my phone. It started when one day I picked up my phone and saw that process.android.gapps had stopped. So I did what everyone does and cleared the cache, wiped the data, but still nothing happened. I went over and cleared it for play services too and that reset my google account (no idea why) and everything came back to normal. Or as I thought it did. A few days later, I again had the same problem in front of me, except that it was not just gapps this time, it was a ****load of a few more apps, including process.???.acore, all giving ANRs. Plus my google account got erased somehow so play store won't login and all other unnecessary stuff.
So I got frustrated and went over to the recovery and tried to factory reset. And this is where I realized something. IT DIDN'T HELP! The phone started as normal and I saw the startup screen. But as soon as I started entering my details, all the ANRs came back simultaneously.
So I did a lot of other stuff to rectify this, all in vain. Skip to 8 hours later. This is where I realized, some of the apps in /data/data had got corrupted and hence nothing was happening. Also, formatting /data resulted in an error, which I HAVE NO IDEA WHY TILL DATE.
So I did a workaround and renamed /data to something so that the android OS could create a new /data, which IT DID on the next reboot! And all was working fine again.
FOR A FEW HOURS.
Again the same ANR, same everything, no access to /data to format it etc etc.
Again renamed and rebooted and reinstalled Blisspop and gapps and everything.
And this has been the scene ever since.
What aggravates the situation?
A REBOOT
Whenever I reboot my phone, be it soft or hard, It corrupts some or the other app in /data. If I'm lucky it's a non essential app. If not, xx.xx.xx has crashed and the phone is unusable. I usually use ES and try to rename for the non essential apps (as deletion isn't possible), but for the essential ones, a reflash with whole /data/data renaming has to be done.
So basically this is the problem. I have no idea why my /data/data corrupts randomly, or whenever I restart. Could it be because I greenify apps? I stopped using deep hiberation but still this occurs. Or could it be a failing internal memory?
Please Help! I am just frustrated. Might go over to G3 soon if this doesn't work out.
Specifications:
Phone: i9300
ROM: Blisspop-v3.2 12/05/2015 [Stable]
Android: 5.1.1
Kernel: 3.0.31-CM-g00ac77b
Recovery: TWRP (Latest Version)
Gapps: Minimal Gapps
Baseband: I9300XXEMA5
Bootl: I9300XXEMD3
Insane Chip: YES
Click to expand...
Click to collapse
I think it would be painfull to pinpoint what is screwed on your phone. If i were you,i would flash stock firmware and start from the beggining.
Sent from my Nexus 4 using XDA Free mobile app
Stevica Smederevac said:
I think it would be painfull to pinpoint what is screwed on your phone. If i were you,i would flash stock firmware and start from the beggining.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah I guess that's what I'll do finally.
Although I'm still gonna try for a few more days to find something out If I can.
I'll post an update here if I do, in-case someone runs into the same problem as me and needs to find a solution later on.
UPDATE 1 - Okay so I reflashed everything to start over (everything same as before, no downgrading) and I think I may have found a solution. So rebooting the system corrupts /data right? Well, I tried powering off and starting instead of rebooting and that seems to work pretty well. No ANRs even after doing this more than 20 times. [NO IDEA WHY, but hey, it works, so good enough]
Although, I had greenify disabled.
Now, I'll try with it enabled and post an update soon.
As the title says, maybe this is why you're most likely here.
I have recently experienced this issue while using versions of android with ART (Android Runtime) for almost 3 years. I have a OnePlus 2 that I've purchased in September of 2015 and am now just experiencing this issue although after I've done some searching on google, apparently this has been happening ever since the release of ART.
The phone will eventually boot but I've only witnessed it taking up to an hour. Others around the net have reported up to 12 hours. It seems this can depend on the amount of apps in your phone since they're being optimized.
I've restored an older backup since at first I didn't know what the issue was but after 2 reboots the same issue happened again. This is when it took an hour to boot and I noticed most of my apps were gone although they were all there after the first boot. I'm now restoring my most recent backup which I made in recovery right after this issue first happened and am hoping it will eventually boot with all of my apps/data.
Edit 1: It has successfully booted with all of its data although it took 60 minutes. I rebooted again and now it says, 'Optimizing app 1 of 1' but it seems it will take a long time again.
Edit 2: It has taken exactly 60 minutes to simply reboot without any changes. All apps/data are still present with 18% battery discharge.
People have said this can happen while booting with the charger plugged in but I've tested both scenarios with the same result. Does anyone know what causes this issue? My mom has the same phone and it's not rooted and never had any modifications to the OS but it has also done the same thing without data loss not too long ago.
Edit: The description in this link might explain what's going on. I tried the app but it didn't work.
Android: 6.0.1 API:23
OxygenOS: 3.6.1
TWRP: 3.2.1-0 (https://dl.twrp.me/oneplus2/)
Magisk Root: v16.0
Xposed: 89.2 Systemless by Rovo89
I've found a fix although it takes a little time.
Using Titanium backup
Backup all user apps
Uninstall user apps
Reboot to recovery
Wipe dalvik-cache
Reboot
Restore user apps
I do not know how to properly debug so I used this method. When TitaniumBackup has trouble restoring an app or apps then that .apk(s) are/is the issue. I found out mine was ZEDGE because it was having trouble restoring. After it somehow installed I rebooted and the 'Optimizing app 1 of 1' screen appeared so I rebooted into recovery to delete ZEDGE from /data/app/. It rebooted in less than 2 minutes without ZEDGE.
I also noticed while trying to reinstall it through the Play Store it wouldn't load the downloading animation correctly unless I backed out of the app page then returned to it. If this happens to you then you can try uninstalling all updates for Google Play Store and see what happens. I tried this and eventually received error code 924.
The error is happening during the install process. ZEDGE was previously installed on my device without this issue until it was updated on 4/16/'18.
Not sure how the updated version caused this issue. After it was updated everything was normal until I tried rebooting with it. It seems this issue can happen on anyone's device using ART during the install process for any of your user apps. If anyone has had this happen do you know what causes this error?