I've been experiencing random freezes that kick in about two or three days after installing a new custom ROM. Freezes occur, followed by FC prompts, which can be "Wait"ed and the app works again, but after a day or two of use, it just becomes painful waiting for the apps to resume or phone to wake up.
In the course of backing-up I've noticed that TWRP Nandroid backups are running into read errors (code 255). These can be fixed by going through the recovery.log and deleting the files that cause errors and rerunning the backup, repeating until all the corrupted files have been deleted. The phone also runs better after these files have been deleted, but it eventually happens again until the phone is almost useless. What is feels like, is old-time Wintel bad hard drive sector errors and it looks like it too when you see these read errors in TWRP, but everyone assures me Nand/Flash drives don't work like that...are there any other possible hardware issues?
The trouble began after I installed the final Resurrection Remix 5.8.5 (5.8.4 bluetooth didn't work properly). I've now tried also Nougat versions of Resurrection, Lineage and Carbon. Can't bear going back to MM but it might be the only solution.
I've followed installation instructions to the T, installing stock ROMs with Flashtool and then installing ROMs as described in OPs. I've tried both Magisk 14 and SuperSU. I've avoided rooting at all. I've Formatted (rather than Wiped in TWRP) everything except the external SD card. I've restored apps through Titanium. I've fresh installed apps from the market. Nothing works. I haven't tried not installing anything but what's the point of a phone with no apps??
I've followed some solutions posted by others with the same problem but not everyone describes their problem all that well but I still run into the issue. BUT, I keep seeing threads that die and no one says they fixed their issue - common but I'm thinking they gave up.
I haven't tried MM, but I might try Oreo first, if it's stable enough to run. Support in ROM forums is pretty thin though nowadays... (check my other posts).
Anyone got thoughts on how changing kernels might help, and which kernel to use for Nougat?
Related
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
The AOKP build works great except for the constant disappearing keyboard that is about to make me kick puppies. I saw the note to install the wingray google apps to avoid the disappearing keyboard that is synonymous with the recommend gapps to use, but my dumb ass forgot and installed the recommenced apps and I surely do have the constant disappearing keyboard issue. I have flashed the "gapps-jb-20130129-P75xx" zip but still have the issue. Do I have to wipe everything and start over? Does flashing the new gapps zip not overwrite the "gapps-4.2.2-jb-3.4.2013-signed" I originally installed? It seems not to, but wanted confirmation before wiping everything again.
You should wipe everything and start over. IMHO.
Full wipe and used the "gapps-jb-20130129-P75xx". Disappearing keyboard will no longer boil my blood.
For reference, never use the "gapps-4.2.2-jb-3.4.2013-signed".
Glad I stumbled onto this thread. Exactly the problem, keyboard, (well one of them anyway) I am having.
Well for me I can't find anything to fix the disappearing keyboard issue. I tried using the suggestions above. No help. After finding more and more posts in the same subject on different boards it seemed only the Wingray gapps is the one that works properly. Just tried that one and it doesn't seem to fix the issue either. Tried several of the newer nightly ROMs too.
One suggestion was to download the Go keyboard. That didn't help either.
Dang how hard can this be? I have flashed and wiped cache so many times lately. lol
The problem why is exactly explained in nakedninja's 4.2.2 thread, you should read before you install anything
DefQoN_BE said:
The problem why is exactly explained in nakedninja's 4.2.2 thread, you should read before you install anything
Click to expand...
Click to collapse
Unfortunately that thread content has not helped in my case. I found that thread early on and have tried to follow the directions. So either I'm missing something or not doing something correctly it appears.
Someone in another forum suggested I try the free Jellibean keyboard.
I had this issue too with AOKP 4.2.2. I have not reflashed another new gapps yet, as I found re-installing a third-party keyboard which I liked from previous use solved the problem.
Andre
Well whatever I did I finally fixed it. I ended up simply formatting the internal SD card. Poof, everything gone. Had to restore from backup default ROM. Once the stock firmware was up and running I followed the procedures again. Wiped, cleared cache multiple times and when it was all done installing there is no more keyboard issue as of now.
I loaded the 4/08/2013 nightly ROM and Wingray gapps(which I've already tried multiple times). So all is well in Tablet land again.
I've been getting systematic breakdown of my device whereby processes and apps will suddenly for no reason on their own be forced to stopped unexpectedly. So for example Google Framework, gapps, acore, play store then apps will be unable to start and force close immediately e.g. swype, titanium backup etc etc. Now this has happened on many different ROMs e.g. DSC, Longhorn, PCM7, Mokee and now even on the AOPK CM9. So it isn't down to a particular ROM as they always flash fine and my device runs fine otherwise.
A complete data wipe and re-flashing of a ROM always restores the phone to "normal" but I fear my device is dying. Has this happened to anyone else?
try installing different launcher...
Really? Why should that make a difference? They mostly have different launchers though.
It doesn't.
Does it do this without any of your apps added?
SuperKeeper said:
I've been getting systematic breakdown of my device whereby processes and apps will suddenly for no reason on their own be forced to stopped unexpectedly. So for example Google Framework, gapps, acore, play store then apps will be unable to start and force close immediately e.g. swype, titanium backup etc etc. Now this has happened on many different ROMs e.g. DSC, Longhorn, PCM7, Mokee and now even on the AOPK CM9. So it isn't down to a particular ROM as they always flash fine and my device runs fine otherwise.
A complete data wipe and re-flashing of a ROM always restores the phone to "normal" but I fear my device is dying. Has this happened to anyone else?
Click to expand...
Click to collapse
+1 sounds so familiar its spooky.
Strephon Alkhalikoi said:
It doesn't.
Does it do this without any of your apps added?
Click to expand...
Click to collapse
Well it's very hard to say that because it generally progresses in how bad it gets. I've had ROMs working fine for a week or so before they give up the ghost. I'd be inclined to say it maybe a dodgy app but I've had a huge range of different apps because my knowledge and ability with Android has come on since I first started with custom ROMs.
Bump.
After reboots, I lose data of all my apps so they're like they've just been installed, e.g. Whatsapp asking to verify my number etc. Also after a reboot none of my installed apps are in the launcher but in the settings they are listed under their process name (e.g. com.adobe.flashplayer) with a grey SD icon next to them. Multiple reboots and wiping of Dalvik haven't fixed this. So I really don't want to wipe data but looks like I will have to.
Furthermore, an app can be "restored" simply by re-installing it, the device says that I am replacing an already installed application.
This is a huge problem because the pins in the device's port are bent so I have to charge batteries externally.
I'd spend a little bit of time and attempt to straighten out those pins, as it will help. However, while I do believe wiping data at the very least is in order, I'd be more inclined to go with the full factory reset and start over.
Yeah always happen to me too..
Can you try to check via Recovery Mode and see if Cache partition is OK?
Because I always get that error if Cache partition (innersd5) crashed..
and to fix that I must disassemble DS and takeout the internal SD card and mount it to PC..
Then you can format the Cache partition to ext3 (the partition is small size around 230MB)
Hope this help you
Hi, a few days ago my phone camera fault, I get a notice saying "error connecting to camera", so I did a logcat to see what happened but I honestly don't know how to read it and thus can not understand where is the reason for the problem so that's why I put this here so that any experienced user help me and tell me what is the problem... Here is the log http://pastebin.com/print.php?i=rXU9DwAc
Thanks for your time guys!
PS: the front camera and flashlight also don't work, I try flashing another rom but didn't work (CyanogenMod 10.1)
Well at face value, e.g. taking the error literally.. a bug caused a java error keeping the camera app from loading properly. Specifically an empty string value that throws an exception.
Now you have to place that in a context. If it was a one time error.. don't worry about it. If it is repeatable, it could be a bug, conflict, corrupted install, et cetera. A logcat is just a detailed log of what the OS and drivers were doing to provide clues for troubleshooting. Do a search for the CM build you have and see if anyone else is having issues. If so, that suggests a bug. Otherwise you can try disabling other apps that may be conflicting.
You implied that this is a recent problem.. so corruption or a conflict seem more likely. Did this happen after a recent flash or installing a new app? If you flashed a new CM build, did you wipe the cache? If not, I'd suggest that you If not, consider reflashing your ROM, ensuring that you wipe the cache data to see if that resolves the issue. It seems odd if you had a stable configuration and reflashing doesn't resolve the issue.. at least temporarily. Look for a pattern or missed step, like not wiping the cache.
HTH
fffft said:
Well at face value, e.g. taking the error literally.. a bug caused a java error keeping the camera app from loading properly. Specifically an empty string value that throws an exception.
Now you have to place that in a context. If it was a one time error.. don't worry about it. If it is repeatable, it could be a bug, conflict, corrupted install, et cetera. A logcat is just a detailed log of what the OS and drivers were doing to provide clues for troubleshooting. Do a search for the CM build you have and see if anyone else is having issues. If so, that suggests a bug. Otherwise you can try disabling other apps that may be conflicting.
You implied that this is a recent problem.. so corruption or a conflict seem more likely. Did this happen after a recent flash or installing a new app? If you flashed a new CM build, did you wipe the cache? If not, I'd suggest that you If not, consider reflashing your ROM, ensuring that you wipe the cache data to see if that resolves the issue. It seems odd if you had a stable configuration and reflashing doesn't resolve the issue.. at least temporarily. Look for a pattern or missed step, like not wiping the cache.
HTH
Click to expand...
Click to collapse
Well none of those, I was on a stock rom (I flash a few tweaks for improve the net speed and things like that) and suddenly the camera error starts so I flash a cm rom for try to solve the problem but seems to not work ( I make all the wipes correctly)
martin_carpio17 said:
Well none of those, I was on a stock rom (I flash a few tweaks for improve the net speed and things like that) and suddenly the camera error starts so I flash a cm rom for try to solve the problem but seems to not work ( I make all the wipes correctly)
Click to expand...
Click to collapse
The essence of troubleshooting is looking for patterns.. which point us towards the ultimate cause of a problem. If I had a java error, the first thing I would try is simply rebooting the phone. If it continued, I would suspect a conflict (if I had recently installed an app or changed some settings). So.. try reversing those tweaks and see if that clears that error. Less common would be corruption.. and you might test that by flashing back to the same stock ROM if it was working fine before you saw the issue.
Flashing to a different CM ROM wouldn't be a first step. It might work. But you don't gain much knowledge if it doesn't as a new ROM introduces a host of new variables as well. If the cause of the issue is unclear, you want to confront the most obvious suspects first and try to change only one variable at a time. In your place, i'd go back to the stock ROM.. confirm that the camera works properly again. Then restore your tweaks one by one watching to see when the problem recurs.
Good luck
.
Hello!
I have been encountering this problem for about 1 month now, but have not decided to fix it before since I mostly rely on my tablet, but it got pretty annoying now, since I often cannot be contacted because of it.
So the problem is that my phone freezes at random times. Sometimes just a minute after I reboot, sometimes it works for a while and then freezes.
I thought it might be a software problem, so I went ahead and installed a new rom (I went with Temasek's CM build), but the problems persisted. However, I noticed, since I used the phone for a while without GAPPS, due to having problems installing it, it worked fine at that time. Now that I have installed GAPPS however, the phone is freezing again.
I also tried removing my external SD card and it does not help.
I do not have much experience with mobile hardware, but could this be a problem with faulty RAM or internal storage? If so, what can be done?
Thank you in advance for your help.
Sick0ne said:
Hello!
I have been encountering this problem for about 1 month now, but have not decided to fix it before since I mostly rely on my tablet, but it got pretty annoying now, since I often cannot be contacted because of it.
So the problem is that my phone freezes at random times. Sometimes just a minute after I reboot, sometimes it works for a while and then freezes.
I thought it might be a software problem, so I went ahead and installed a new rom (I went with Temasek's CM build), but the problems persisted. However, I noticed, since I used the phone for a while without GAPPS, due to having problems installing it, it worked fine at that time. Now that I have installed GAPPS however, the phone is freezing again.
I also tried removing my external SD card and it does not help.
I do not have much experience with mobile hardware, but could this be a problem with faulty RAM or internal storage? If so, what can be done?
Thank you in advance for your help.
Click to expand...
Click to collapse
Try a full Mega wipe look here >> http://forum.xda-developers.com/galaxy-s3/general/tool-mega-wipesuper-wipefactory-t1832326 << Warning this is not a normal wipe make sure you read the thread and have a backup rom on your external sd card ready to flash after wiping