Hi all,
I've been having an issue and I cannot figure it out. While using my phone the screen will freeze. On screen and physical buttons will not respond. The only way to solve this has been battery pull.
Its happened across different ROMs and kernels (all jelly bean based if that makes a difference) including aokp unofficial nightlies, cm10 official nightlies, and stock, air, and popcorn kernels. I have done factory reset to wipe data/cache and wiped dalvik (came from og droid and that's been my habit) but the problem persists. I read somewhere about reboots being caused by permissions issues, but I ran fix permissions in CWM to no avail.
Could anyone offer advice/suggestions/solutions?
Related
I have been getting random reboots since past 2-3 days. I tried flashing stock rom, wiping everything but no luck. Currently I am on "AOSP R11 Jelly Bean 4.2.2 JDQ39 + Kernel v3.0.70 Linaro" Kindly see the last logcat taken after the phone reboot. Anyone can tell me cause of problem I am having?
*Bump*
Anyone??
I'm currently running Cyanogenmod 10.1-20130403-Nightly with the 20121011 released of gapps for Jelly Bean (both flashed with TWRP with a davlik cache wipe) and I have a very odd issue. I've searched high and low and can't seem to find someone with the same issue. Basically, unlocking the screen with a custom shortcut (not the default unlock one) causes my phone to soft restart. I don't see the Samsung logo so I think it's not a full restart. Does anyone have any clue as to what could be causing this? I've made sure that this isn't a one time thing as it happens with every custom shortcut I add. I haven't done a factory reset since I haven't done a backup yet and I'd like to see if this could be fixed without having to do one.
I've recently had my notification LED stop working, the only time it lights up is when I receive a call. I'm running AOKP JB-MR1 milestone 1 with lean kernel, and when I attempt to test the LED in the rom settings, nothing happens. LightFlow doesn't work either (though it used to). Is anyone else having this issue?
Nope can't really say cause i'm not running aokp last time i ran aokp it was on ics you could try clearing caches and dalvik through recovery and trying again :-S or dirty flash your rom +gapps might be helpful
This issue has persisted through multiple factory resets and clearing cache, etc., never thought to dirty flash, but again it's still around after installing roms and factory resets
Hi,
I have been using custom roms for a while on my note II N7100. From my last rom my phone was restarting on its own at least once a day and complete freezing quite a few times. Only solution was to reboot the phone by holding the power button for few seconds, nothing else would work. Even tried leaving the phone for 10-15 minutes however it did not help.
I was using Carbon Rom earlier. I changed Liquidsmooth 2.9 however the same thing happened. In fact the frequency increased with Liquidsmooth. I was worried about a hardware problem as even after complete wipe and with different rom same thing was happening.
I decided to perform a complete factory reset, wipe cache/dalvik cache. After flashing liquidsmooth 2.9 I did not flashed the gapps, used the phone for couple of hours and things were fine. After I flashed the requied gapps - gapps-jb-20130301 - same thing started happening.
Somebody please let me know if I can flash the earlier version of Gapps or later version if available.
Regards
So I've recently been having an issue with my phone that I haven't been able to fix through various standard fix methods. I've tried searching for this exact issue but the only thing that seems to work for other people (albeit they were on different devices when they had this problem) hasn't fixed my issue.
Long story short, I went from SlimROM 2.2 (and many other 4.3 based ROMS) to ForkMyLife 4.4.2 to try out KitKat, and I eventually wanted to go back to SlimROM.
I always full wipe (System/Data/Cache/Delvik) and then flash my ROM (in this case it was Slim), a reboot netted me a bootloop/boothang on the bootanimation. Wiping Cache+Delvik cache will get me to Optimizing Apps, but then it hangs at Starting Apps. At which point I can battery pull, restart, and it will restart just fine (typically, I did have one time where this didn't work). But I'd have to do this series of events every single time I reboot. I've tried multiple ROMs, multiple kernels, but everything ends up doing the same thing after a reboot. I've even done a full Stock 4.2.2 Image flashing (full SDCARD/DATA wipe an everything) using mskip's Toolkit, re-rooted and re-did my entire phone to Liquid 2.37 booted up the first time no problems, but the boothang was back on the very first reboot.
What is somewhat odd to me, is that I can run a 4.4 based ROM with no boot issues though. I ran FML 4.4.2 for a few days and numerous reboots, and the same for OmniMetal 4.4.2 to see if it would lead to any boothangs and I had no problems with either.
Any ideas or thoughts from anyone on why reverting back to 4.3 after a 4.4 ROM would cause so many issues?