Well it seems as a new member I can't post in the Dev section yet, so I guess I will post it here:
I have been having issues much like others with this rom locking the phone completely up. Most of the time, when I wake the phone the screen is upside down and has graphic artifacts on the screen. This of course causes me to have to pull the battery. Once the phone comes back up, I can literally hit the power button on/off about 10-12 times and it happens again. I have reinstalled the rom and followed the instructions for flashing the ROM 31 times (i keep a journal of it). I am still having the same issue. I have tried Faux's LV and the SV version of his kernal and have even gone back 3 previous version (tried both versions so, 8 kernals in all) and still have the same issue. Now a buddy of mine suggested turning the "screen animations" off, and since I have done that I haven't had the phone lock up on me anymore, however the lockscreen does occasionally flip 180 degrees, but simply hitting the power button off then on and it is ok.
That seems to be my only issue with the rom. I really wanted to post in the dev section, but I guess I have to get my post count up before I can help contribute to the thread.
Thanks again TeamRoyal for another AMAZING release, and I also appreciate you folks assisting us with our minor issues. Keep up the good work, and thanks again for your folks assistance.
gitm said:
Well it seems as a new member I can't post in the Dev section yet, so I guess I will post it here:
I have been having issues much like others with this rom locking the phone completely up. Most of the time, when I wake the phone the screen is upside down and has graphic artifacts on the screen. This of course causes me to have to pull the battery. Once the phone comes back up, I can literally hit the power button on/off about 10-12 times and it happens again. I have reinstalled the rom and followed the instructions for flashing the ROM 31 times (i keep a journal of it). I am still having the same issue. I have tried Faux's LV and the SV version of his kernal and have even gone back 3 previous version (tried both versions so, 8 kernals in all) and still have the same issue. Now a buddy of mine suggested turning the "screen animations" off, and since I have done that I haven't had the phone lock up on me anymore, however the lockscreen does occasionally flip 180 degrees, but simply hitting the power button off then on and it is ok.
That seems to be my only issue with the rom. I really wanted to post in the dev section, but I guess I have to get my post count up before I can help contribute to the thread.
Thanks again TeamRoyal for another AMAZING release, and I also appreciate you folks assisting us with our minor issues. Keep up the good work, and thanks again for your folks assistance.
Click to expand...
Click to collapse
That's strange did you do a full wipe and format sd card along with boot and system and followed there instructions about not touching it on first boot and all. I did that and had no issues. I'm running RC2 because I just like it more and have no issues so thats something else you can look into
I've had the exact same issue when using RC2 with faux's kernel. I've tried the LV and SV versions and still had the same problem.
Finally I gave up and just reinstalled RC2 without faux's kernel and I have not had any issues.
Sent from my HTC Glacier using XDA App
Tazzaras said:
That's strange did you do a full wipe and format sd card along with boot and system and followed there instructions about not touching it on first boot and all. I did that and had no issues. I'm running RC2 because I just like it more and have no issues so thats something else you can look into
Click to expand...
Click to collapse
Yea I have wiped and formated everything. The install I am now on I actually waited a full 30 mins instead of recommended 5 min.Nothing against teamroyal as I have mad respect for what they do, but RoyalGinger has made me a pro at installing it
So far no kernal crashes, which has given me a perma-grin. I'm gonna flash back to the latest LV version of faux kernel (the one that came with it). I'm sure it will be fine as I think the whole problem has to do with the screen off animation. I'll report back with my results.
Update:
It is the screen off animation that is causing my issue. I have flashed the latest kernel and everytime I have the off animation on, it locks. On screen animation works when on by itself, but turn the off animation on, power on and off a couple of times, and it will crash. I'll try to grab the logs and submit them.
Well seems everytime usb debugging is on it simply won't crash, and I can't get emulator to record when the phone crashes. Sorry I can't get a logcat
Same here on my wife's phone. Had to restore a 2.3.2 nandroid because both (CM7 rc2 and RG 1.3) were freezing on wake. Dunno what the cause is because on my mytouch RG 1.3 runs fine since it dropped......
If u read thru the post for Royalginger 1.3 it says that the best kernel for the rom is the kernel that it comes with... it also says u will get best/smoothest response with it set at smartass... I'm not sure if its changed since I've read but give it a try...
Sent from my HTC Glacier using XDA Premium App
So the good news is I was able to get a logcat. I didn't realize that when the phone completely freezes (power on/off does nothing) you can still dump the logcat, hooooray for me. So here is my logcat file, and for the record this ONLY happens when I have the off and on screen animations enabled in the "CyanogenMod settings", with them off I can power on and off without the phone crashing.
[ROM] - RoyalGinger 1.3
[Kernel] - version 2.1.0 Low Voltage
[CPU Frequency] 245~1113
[Governor] Smartass
[Theme] - Honeybread (CM7 honeycomb theme)
[Live Wallpaper] - None
Update:
I did what was instructed in the dev section for flashing the latest Faux Kernel (2.1.2.1). I wiped the cache and delvikcache. I then fixed permissions and installed the kernel. Once the phone got to the lock screen, I waited 15 minutes for the kernel to "settle", immediately rebooted and let it sit for another 15 minutes.
Once that was I done, I enabled both the on and off screen animations, and after power on and off about 20 times, it crashed the phone again. So I am still having the same issue. Also as a heads up, I tried different themes just incase it was the theme, but that made no difference. So I reverted back to screen on/off animations as all off, and still no lockups. I have attached another logcat file, just incase there is some new data in it.
On another note, there simply isn't any last_kmsg file, so I'm sorry I can get you folks the file. It isn't on the phone when it crashes or even when the phone works correctly.
Have you done anything with spare parts?
Nope I haven't touched Spare Parts. I'm really trying to get this issue resolved before I setup anything on the phone. Maybe the 1.3.1 release will resolve the issue, but time will tell.
gitm said:
Nope I haven't touched Spare Parts. I'm really trying to get this issue resolved before I setup anything on the phone. Maybe the 1.3.1 release will resolve the issue, but time will tell.
Click to expand...
Click to collapse
gitm - 1.3.1 should be out by tonight, barring anything weird coming up last minute in testing
and this has the new 2.1.2.1 faux kernel built in but if you want to try in the mean time - go to his thread and flash that kernel (wipe both caches and fix permissions, then flash kernel, then settle for 5 mins on initial boot, reboot, settle another 5 min, then go)
can't remember, are you using stock launcher or a 3rd party?
Using launcher pro.
As for the new kernel, it is still causing the same issue. In my logcats, it says "cpu pegged", and that is pretty odd. Hopefully 1.3.1 will fix it, but I will keep testing and keep you posted
Hi
I'm on my 2nd N4 after the first one developed a case fault. I had no problems with that one when using Minco or PA.
However this one seems to have a habbit of becoming completely unresponsive at least once every couple of days. The only way to bring it back on is to hold the power button in for a few seconds and then reboot it.
I will be putting it back to stock tonight and giving it more of a chance. But I thought i'd ask and see if anyone else has experienced this type of issue or knows if it's a sign of a more serious problem such as the red light of death.
Thanks
Phils7 said:
Hi
I'm on my 2nd N4 after the first one developed a case fault. I had no problems with that one when using Minco or PA.
However this one seems to have a habbit of becoming completely unresponsive at least once every couple of days. The only way to bring it back on is to hold the power button in for a few seconds and then reboot it.
I will be putting it back to stock tonight and giving it more of a chance. But I thought i'd ask and see if anyone else has experienced this type of issue or knows if it's a sign of a more serious problem such as the red light of death.
Thanks
Click to expand...
Click to collapse
I did actually experience this when I'm on stock 4.2.1 out of the box state, rooted and custom recovery.
transfered to PA for a couple of days and reflashed stock images from google site. after going back from PA to Stock I haven't experienced the lock up/screen unresponsive yet. hopefully it flashing back from PA to stock fixed this.
I've been using my phone for a month with rooted stock rom, custom kernel, unlocked bootloader, custom recovery, busybox and there's no single lag or lockups. Maybe you got a bad phone. I hope it can be fixed though.
I have a rooted stock ROM, unlocked bootloader, I don't have busybox permanently installed because I use apps that require a 'unrooted' phone but I have Stephen Stericson busybox installer at the ready.
I've not had a single lockup since I bought this phone.
I recently rooted and unlocked the bootloader on my Razr M and installed a nightly build of CyanogenMod (I like to live on the edge, I guess.) The first week or so with it was going great, no issues as far as I could tell.
Then I installed a social application that requires GPS location. I noticed that the first time after enabling this the phone would freeze when plugged in to charge. It would freeze to the point where hitting the wake up button wouldn't even activate the screen. Not always, but it has happened on several occasions. So now whenever I charge it (daily), I have to force reboot (hold down Up, Down, Power in that order.) Sometimes it'll even go through the process of "Optimizing Apps" as if they were all just installed.
Firstly, has anyone else experienced this? And if so, is there an "easy" workaround? I can't quite pinpoint how to reproduce the bug, though I've got 3 different Cleaning applications installed that are used daily. That in mind, it's unlikely this is a memory leak bug.
Second, if there's no "easy" workaround, when can one expect the next Stable build of CyanogenMod, if ever? Is it still in development? I see that the last Stable release for this phone was in 2013. It seems like I'll have to downgrade to an earlier build, but just want some input before I do it.
Thanks much in advance
Sounds like an issue with the app, not the ROM. You said yourself that the issues started AFTER installing that app. So, delete that app and report back. Also, a lot of those cleaner apps out there will just bork your phone if you're not careful.
Sent from my Nexus 5
Recently I've been having a bit of issues with the Official MM RR rom, the BlackMix one. This happened after I decided to try a different kernel; I had been using the yarpiin kernel.
It started with apps slowing down and eventually crashing whenever I changed the volume with the volume keys. The app would freeze, and then eventually ask me if I wanted to close it. It went away after I changed the volume overlay dismiss time to a higher setting.
However, sometimes the device will just freeze for no reason, and refuse to respond to any inputs. It'll just hang at the screen I'm on, and then eventually the screen will just go black with the display still on. Then it will reboot. I think this is basically one of those random reboots people experience. Is this exclusive to RR? I had it back on my old Droid Turbo that was on RR too.
And then sometimes apps will also just freeze for no reason and refuse to respond to any navbar inputs. Pulling down the notification shade or locking and unlocking will fix it, but it happens frequently enough to be annoying.
So basically, my question is, is there another ROM similar to RR in terms of features and customization that I could try? Also, are there any fixes that I could try to alleviate these issues. My current ROM and kernel setup is absolutely perfect besides these issues and I would love to keep it this way if at all possible.
Latiken said:
Recently I've been having a bit of issues with the Official MM RR rom, the BlackMix one. This happened after I decided to try a different kernel; I had been using the yarpiin kernel.
It started with apps slowing down and eventually crashing whenever I changed the volume with the volume keys. The app would freeze, and then eventually ask me if I wanted to close it. It went away after I changed the volume overlay dismiss time to a higher setting.
However, sometimes the device will just freeze for no reason, and refuse to respond to any inputs. It'll just hang at the screen I'm on, and then eventually the screen will just go black with the display still on. Then it will reboot. I think this is basically one of those random reboots people experience. Is this exclusive to RR? I had it back on my old Droid Turbo that was on RR too.
And then sometimes apps will also just freeze for no reason and refuse to respond to any navbar inputs. Pulling down the notification shade or locking and unlocking will fix it, but it happens frequently enough to be annoying.
So basically, my question is, is there another ROM similar to RR in terms of features and customization that I could try? Also, are there any fixes that I could try to alleviate these issues. My current ROM and kernel setup is absolutely perfect besides these issues and I would love to keep it this way if at all possible.
Click to expand...
Click to collapse
Try Exodus. It's AOSP + CM based & the most stable MM rom I've tested.
B!Gguy said:
Try Exodus. It's AOSP + CM based & the most stable MM rom I've tested.
Click to expand...
Click to collapse
What kernel do you use for it? I'm gonna go ahead and try it.
Latiken said:
What kernel do you use for it? I'm gonna go ahead and try it.
Click to expand...
Click to collapse
No custom kernal. Stock one's good enough.
Hey guys,
I have rooted my device over two months ago. The first ROM I had flashed was running nice and smooth except for a few issues like the camera issue.
After a week or so, I've changed the ROM and since then, I've always had problems. The ROM runs nice and smooth at the beginning and later (between ten minutes and three hours) the problems start again.
It never got bricked but it always kept shutting down, freezing (short), lagging, overheating, not reacting untill pulling out the battery or all apps and services crashing and so on.
I then managed it to get working better than ever before running a custom ROM (don't remember which one).
But that didn't last long. After a day or so the phone started lagging again. I've booted into TWRP and wiped cache and dalvik. The next boot ended in a "encryption unsucesfull" and I had to reflash the ROM.
What I've noticed today was that it helped to wait abit before turning the phone on again after pulling the battery out.
Since then I'm trying to figure out how to fix that.
I'm waiting for the Oneplus 4/5 anyway, and I'm not sure anymore if I should root that thing too since I risk to go through the same (or worse) struggle all over again.
If you need any further information to help me, feel free to ask for it.
With my Note 4, I have waited till the warranty time was over.
Thanks in advance
PS: Heat seems to be a huge problem. I don't mean overheating, I mean usual working temperatures. That would explain problems like the massive drop in performance as soon as I got in to my car which was standing in the sun.
PS2: Kind of solved. Downloading the wakelock app and setting it on "partial_wake_lock" helped.