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.
Related
Recently my phone has been randomly crashing: i.e screen would lock, I would attempt to unlock it after x amount of time, and screen would not unlock. The home, menu, back and search 'buttons' on the bottom would light up, and I was still able to manipulate volume, but had to pull battery to reboot.
Attempted re-flash of Cyanogenmod 7.1 & titanium backup to restore apps / data. Crashes would still happen.
Attempted re-flash of Cyanogenmod 7.1 and left as 'stock' install - still crashed.
Attempted flash of Cyanogenmod 7.2 - crashes would still happen.
Tried above with no SD Card in - still crashed.
I read somewhere (forget where) that a dodgy battery could be causing this(?) so have ordered a new one.
Other than that, is there anything else that would cause this, and am I looking at getting a new phone or is there some other fix that someone else can recommend?
Cheers
Jeimuzu88 said:
Recently my phone has been randomly crashing: i.e screen would lock, I would attempt to unlock it after x amount of time, and screen would not unlock. The home, menu, back and search 'buttons' on the bottom would light up, and I was still able to manipulate volume, but had to pull battery to reboot.
Attempted re-flash of Cyanogenmod 7.1 & titanium backup to restore apps / data. Crashes would still happen.
Attempted re-flash of Cyanogenmod 7.1 and left as 'stock' install - still crashed.
Attempted flash of Cyanogenmod 7.2 - crashes would still happen.
Tried above with no SD Card in - still crashed.
I read somewhere (forget where) that a dodgy battery could be causing this(?) so have ordered a new one.
Other than that, is there anything else that would cause this, and am I looking at getting a new phone or is there some other fix that someone else can recommend?
Cheers
Click to expand...
Click to collapse
So just to make sure, you did perform a full wipe and not just cache and dalvik... right. Have you tried it with your phone plugged in? I'm not sure if this works, but with laptops you can run it without their battery as well if you have a bad battery.
Absolution 3.7 /Redemption A16, 17, 18, 19, 20. There now I'm covered for a few days
Yeh it was a full wipe!
I've resigned to the fact that's it a hardware issue, and managed to convince my provider that the phone is busted, they're sending me a replacement tomorrow.
Win.
Thanks for the advice.
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?
I installed Busybox odexed 4.2 stock image and noticed significant lag in gmail. I would change user and the selection menu freezes or lags by at least 1 second before performing the task. This is the same with when I'm opening a new mail or any other options.
Does anyone else experience this? Or did I have a bad flash? I dirty flashed it from 4.1.2 first, noticed the issue then wiped everything completely for a fresh install. Same thing happens.
No issues here. Then again, I flashed the official image via fastboot and a factory reset. Haven't heard of anyone else having this problem.
Hey,
I'm new to writing in the forum but have been viewing topics for quite some time.
In the past week I had my HTC One X crashing on me with 'com.google.process.gapps' / 'Android.process.acore' has stopped unexpectedly causign all the apps not to work.
I'm running Jelly beans (4.1.1) with Sense 4+.
I browsed the forums for a while and saw suggestions to cancel google internet sync and to clear to contacts cache.
I did both and after it did not help I tried factory reset and recovery boot.
Although things run a bit better i'm still encountering these errors every now and then (and I have to hard boot the device).
Any suggestions how to resolve this issue ? Could it be a hardware malfunction ?
Would love to hear any thoughts on the matter.
full wipe and reflash could solve the problem, or maybe you downloaded a corrupted zip but the ROM still managed to flash - happened to me before.
My phone is not rooted and does not use a custom ROM so I don't think a corrupted zip is the issue. Should I root it just for reflashing it ?
Hi all, I would like to have some feedback if some of you is experiencing the same issue as I am. My N5X is running Stock Marshmallow (latest release) and it's rooted (SuperSU v2.71) with Xposed (latest version for arm64).
Every now and then (usually with an uptime more than 80 hours) the device becomes very laggy and my usual solution for eliminating the lag is rebooting. It would be the ideal solution if only the device wasn't remaining stuck in bootloop after rebooting.
For now the only "solution" I have found is doing a factory reset from TWRP, after performing a backup of /data. Uninstalling from recovery Xposed or simply wiping cache/dalvik or even flashing separately the stock images (boot, cache, system, vendor) did nothing without a factory reset.
The first times I got bootloops on the device I knew why it was happening (one time I modified build.prop forgetting to change the permissions, another time a similar thing but with the transfer of an app in /system), but these kinds of bootloop remain a mistery for me.
It also occurred without Xposed installed and with both stock and ElementalX kernel.
A peculiar thing I noticed while in TWRP is that the Cache was displayed occupying 0 MB. Might it be related to this issue?
Now, I know now that I should probably reboot more often, but I still would like to know why this happens because it's being very annoying doing the restore procedure every damn week.
And so, while doing my research, I wanted to have some feedback from those of you who had similar issues with a similar setup.
Thanks and cheers!
A new kind of problem occurred. This time Telegram wasn't connecting to the net and so I rebooted. And BOOM, stuck at the boot animation (the four colored points) for no apparent reason.
If I only wiped Dalvik and Cache in recovery, the phone would go past the boot animation, but after the Android logo, it would display only a black screen.
This time, before doing a factory reset, I flashed via fastboot boot, cache, system and vendor, hoping that could solve something for the future.
I have no idea why this is happening. After the new reset, I will try to limit the modifications to /system by not installing Stericson's Busybox and GSam Root Companion app, but I'm still wandering in the dark. It looks like my 5X is possessed.
Please, if you have any sort of feedback or insight, I will gladly listen.
Update: today I had no issues but I rebooted anyway. Result: stuck at bootanimation.
As you English speakers say:"F*ck this sh*t, I'm out".
Yeah, I decided that I'm done with the stock ROM and decided to flash PureNexus ROM in the hope that the **** up I was doing with the stock ROM will never happen again.
Maybe now the mods can close this thread.