I have been using Blisspop since early December with frequent [dirty] flashing to latest versions and occasionally get kernel panics or OOM issues causing the phone to go to a Green or Blue screen that only goes away by holding the "Down" volume and hard rebooting it.
I recently wiped my phone completely (apps, data, dalvik, etc) and flashed the latest ROM with (Blisspop 2.0; Build Date Feb. 7, 2015) with hope that the issue I thought was there would be corrected but the issue still persists through the new ROM.
This issue continuously plagues me and mostly get the Green screen with it saying "Apps Watchdog Bite!". This isn't a huge deal from me and I don't ever plug it into a laptop/desktop to debug the issue or find the root cause. I have just attempted to change the OOM Kill and Kernel Panic settings in sysctl.conf in hopes that the phone would just auto reboot instead of hang on the green/blue screen.
Is there any way to disable this debug mode and force the phone to auto-reboot instead? or has anyone experienced this issue on a consistent basis and has an alternative fix?
Thread with ROM and Gapps: http://forum.xda-developers.com/sprint-lg-g3/development/rom-rating-5-12-18-14-t2977726
Related
Hi, I'm having a curious problem with my S3 and I've been unable to solve it. I watched the "noob" video and tried searching these forums as well as a google search with various combinations of the wording for my problem. Nothing matching my issue turned up, I hope I didn't miss anything.
I recently bought a S3 second hand (yes, i know, i should have known better). It was rooted and running some kind of custom ROM when I first turned it on, but I was willing to deal with it until I double checked the procedure for getting it back to stock and starting again myself (nothing against the original rooting and flashing, just like to know exactly what I'm running).
When I purchased the phone I obviously checked that all of the main things worked - calling, texts, mobile data, wi-fi etc. I get home and connect to my home wi-fi and start checking things out and setting stuff up. The phone randomly rebooted. I carry on after the reboot and about 10 mins later, another restart.
To cut a long story short, there is something wrong with the wi-fi. If I turn off wi-fi in the settings menu and reboot, everything works great. No crashes, no reboots. If however I enable the wi-fi about 50% of the time it will crash while wi-fi is activating. The other 50% of the time, it will crash as it goes into the screen lock (either via timeout or pressing the button).
I've re-flashed to it's stock version of Android (using the 'Samsung GS3 Toolkit and Odin), same problem. Anyone got any ideas?
Thanks in advance
You can try updating the modem and RIL to the right version for your country, search in general forum. If it still reboots then try with another wifi source - I've seen some routers cause problems on client machines.
If you do a factory reset when you flash the modem, plus you have the latest stock ROM on board, then any remaining problems are probably hardware.
Test it fully after the factory reset, before you add any apps etc.
boomboomer said:
You can try updating the modem and RIL to the right version for your country, search in general forum. If it still reboots then try with another wifi source - I've seen some routers cause problems on client machines.
If you do a factory reset when you flash the modem, plus you have the latest stock ROM on board, then any remaining problems are probably hardware.
Test it fully after the factory reset, before you add any apps etc.
Click to expand...
Click to collapse
After much experimentation and flashing of various files to my phone I have further narrowed the problem. I've still not solved it, but getting closer I feel.
After a clean ROM flash it works like a charm regardless of how much i use the wifi etc. It's only after the first reboot that the trouble starts. It will begin randomly restarting. If I perform a factory reset from recovery mode, it works again, but starts resetting again after a reboot.
Any ideas?
Hi,
I'm on PA 3.56, Baseband 1545VRUAMDK, kernel 3.4.0-cyanogenmod-gba 15d0b, build pa_jfltevzw-userdebug 4.2.2 JDQ39
My Full Screen mode becomes disabled whenever i enter into any app, and then back to enabled when returning to the home screen (details below). I understand the ROM is still in development, but if anyone can advise a fix to this prior to the next release it would be greatly appreciated.
Three days ago I installed PA version 3.56 on my Verizon Galaxy S4 via clockwork recovery. I had been using the Pie controls without any bugs for about 24 hours and then I began to notice that the full screen mode would disable when I enter into any application, then back to enabled when I return to the home-screen. I know it is not the specific application that is incompatible with pie because i can enable full screen while in the app and it works. I've ruled out any frozen applications by defrosting and the problem persists.
Additionally, this may or may not be related, but when i reboot, re-start launcher, or restore hybrid preferences, i can then not go back into hybrid properties until i restore paranoid preferences via titanium. I am prompted 'unfortunately settings has stopped.' Occasionally the same thing happens to system UI, and always to the camera. I can not use camera on PA 3.56
After this happened, i noticed also that even when I checked 'enable search button on pie controls,' in the toolbar settings, the search button would not be present until i restored hybrid preferences, and then disappear again after some time. When I restore hybrid preferences and reboot, startup occasionally hangs at samsung galaxy. I have to do a battery pull to reboot.
Any insight appreciated
My i9300 seems to have lost control on (soft?) boot:
- I flashed a 5.1 omni ROM that made me very happy because really stable enough for me to use multiple apps at same time.
- One week after, I started getting unwanted soft reboots (skips Samsung boot screen), leaving me approx 40s of system use before 5s freeze followed by reboot.
- These soft reboots are weird: if I force shutdown (power menu OR removing battery), the phone boots anyway, by itself!! And I think this is still soft boot because it still skips Samsung boot screen.
Additional info:
- I wondered if my power button was messed up but I don't think so: I would not have this freeze before reboot, plus I have no reboot while in recovery.
- I saw some SMS problems: received one from my provider, and I kept receiving it again at each reboot (same one 50+ times). Any link possible?
What I tried without success:
- Remove SIM and SD card
- Remove battery for a day
- Change battery
- Re-flash recovery
- Wipe System + Data + Dalvik/Cache then install paranoid android (now I can't even boot in anything else than recovery btw)
I'm lacking android system knowledge but it looks like there is a location in "soft reboot zone" that is locked, and the phone keeps reading it and rebooting infinitely. Is there a way to clean this? To forbid soft reboot maybe? Note that I've been flashing various roms for 3 years on this phone and I never saw anything alike.
Any advice is welcome, thank you for caring !
blint6 said:
My i9300 seems to have lost control on (soft?) boot:
- I flashed a 5.1 omni ROM that made me very happy because really stable enough for me to use multiple apps at same time.
- One week after, I started getting unwanted soft reboots (skips Samsung boot screen), leaving me approx 40s of system use before 5s freeze followed by reboot.
- These soft reboots are weird: if I force shutdown (power menu OR removing battery), the phone boots anyway, by itself!! And I think this is still soft boot because it still skips Samsung boot screen.
Additional info:
- I wondered if my power button was messed up but I don't think so: I would not have this freeze before reboot, plus I have no reboot while in recovery.
- I saw some SMS problems: received one from my provider, and I kept receiving it again at each reboot (same one 50+ times). Any link possible?
What I tried without success:
- Remove SIM and SD card
- Remove battery for a day
- Change battery
- Re-flash recovery
- Wipe System + Data + Dalvik/Cache then install paranoid android (now I can't even boot in anything else than recovery btw)
I'm lacking android system knowledge but it looks like there is a location in "soft reboot zone" that is locked, and the phone keeps reading it and rebooting infinitely. Is there a way to clean this? To forbid soft reboot maybe? Note that I've been flashing various roms for 3 years on this phone and I never saw anything alike.
Any advice is welcome, thank you for caring !
Click to expand...
Click to collapse
That SMS thing is strange
Have you tried another recovery version? Or perhaps changing recovery? This isn't a normal issue, since you already tried installing another ROM.... You can try another Kernel either
If none of this works, consider flashing the original Samsung's ROM or some samsung-based ROM (they usually do a nice clean-up, at least for me these ROMs fixes the majority of my problems)
@blint6:
1. Maybe the hardware though. This you can test by flashing actual firmware and running it under normal conditions for 1d.
2. Reboot is a known reaction to RAM-lack on LP, too. Flash Omni cleanly and run it for 1d without GApps and bigger apps.
I've been having many software issues with my M4 E2303, ll try make this as short as possible:
I keep on having issues with every firmware I flash. A problem will go away after flashing, but a different one will pop up.
Please note all these firmwares are STOCK.
Issues include:
- Very poor wifi signal (Marshmallow ONLY)
- Wifi "freezing" (Seems like a wifi driver crash) (Lollipop only, fixed after reflash)
- OS Crash with soft reboot (lollipop, happened alongside previous wifi freeze, is still occurring on new firmware)
- Bluetooth not function (seemingly fixed)
The issue im currently experiencing is the OS crash, which occurs randomly with no discernible cause.
From what I can see, flashing with flashtool may well install a new OS, but it seems like it doesnt completely remove elements of the previous firmware. Is there any way I can flash and make sure all my system files are completely replaced by the new firmware?
UPDATE:
I installed stock android 5.0 and booted successfully, WiFi had an issue. I turned off the phone to let it charge and.... it won't turn on. Gets stuck in a infinite bootloop from which I cant recover. I've flashed it twice with different firmwares on the Xperia Flashtool and used the PC companion to do a software repair twice. Still dead... Left it overnight turned off and booted it in the morning, reached the purple waves and froze. Thats the furthest its ever got into a boot.
Don't soft reboot the phone, it's not recommended
Well my phone is actually Rebooting it self for no reason RANDOMLY i don't know why but it happened to me more than 5 times
Now this is the weirdest thing I've ever encountered! I have a Samsung Galaxy Note 8.0 tablet (n5110) which runs TWRP recovery and Resurrection-Remix-5.7.4 (CM13 based). Everything used to work beautifully until the end of July when an app called “EPB DVR Manager” (in the Play store) received an update. My tablet had to do a whole bunch of updates, so I gave it the “go” and Play Store started doing its thing, updating one app after the other.
At some point the tablet froze. Dead. Even the clock in the status bar stopped. I had to reset the device by pressing and holding power until it rebooted. The next thing was ... boot loop. It seemed to finish the boot animation and at the point when the main screen is supposed to show up it rebooted!
Tried to wipe dalvik & cache. No go, still boot loop. Had to format data to get the device back to life. From there it took me quite some hours of repeated tries of restoring 100+ apps and crashing the device all over until I figured out that it was this specific app - the “EPB DVR Manager”. After figuring out that this app causes the problem, I did two more attempts to confirm what is going on:
First, I did a wipe of dalvik, cache & data, reboot, android setup wizard (setup Google account). Then, as the first action at all, I tried to install the “EPB DVR Manager”. Boom - device messed up again.
Second, I reverted back to stock firmware (kitkat) and installed the “EPB DVR Manager” - no problem at all. So it has something to do with the Resurrection-Remix ROM, but here's the thing:
I have 3 different devices (a Moto G 3rd Gen, a LG GPAD 7.0 and that Samsung Note 8.0) and all three of them run Resurrection-Remix 5.7.4 and the Samsung is the only device which all in a sudden has these catastrophic problems with the latest version of this app (earlier versions installed/updated fine).
Now I understand that my devices run different kernels with different hardware drivers despite all of them running RR-5.7.4.
I would really like to get a clue about what the heck is going on here. Now before y'all are telling me that RR-5.7.4 is dead because it is based on CM13 - I know that. Still, RR-5.7.4 is a way better daily driver than the newer Nougat builds. So how should I try to get “live logs” because the problem always ends in a crashed installation and Android needs a full wipe to recover. I would like to find out what is going on to be able to let the app developer know about the problem (if the app's apk is at least partially to blame).
Even if it turns out that it is RR's fault (and therefore the bug will not be fixed because RR-5.7.4 is dead) I would still want to learn how such a simple transaction like installing an app can cause such a dramatic (and 100% reproducible) crash of Android's data partition.
Thanks for any suggestions on how to catch logging information for this kind of mystery.
Markus.