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
Is there any way at all to disable the Fascinate from ever loading into safe mode again? It's really annoying when it happens because I have to reset all my widgets.
I've flashed my phone several times and it happens with every rom that I've had on it so is it part of the baseband kernel?
Get rid of the conflict that puts you in safemode. Safemode has to be better than your phone bricking.
johnnyplaid said:
Get rid of the conflict that puts you in safemode. Safemode has to be better than your phone bricking.
Click to expand...
Click to collapse
X2
List off the steps you used when flashing these last few roms (and what rom specifically) that you say are making you boot into safe mode...I've only seen it once on my phone and 1 reboot fixed it and I never seen it again, but that was months ago and I just chalked it up to me missing a step?! I have flashed many roms since and never see safe mode again.
Sent from my SCH-I500 using XDA App
Im starting to think that it's more a problem with my Fascinate than anything else. It usually happens when I have to pull the battery due to it locking up. Sometimes pulling the battery out a second time still doesn't get me out of safe mode and I have to continuously do it until it does.
For the past few months I've been using CM7 and updating with nightlies. On Monday I updated to the stable GLITCH kernel and so far it seems to be running much better. It's always had a problem with randomly bringing up my keyboard and backing out of apps and I have not had that problem yet since putting the GLITCH kernel on it.
Figured I'd also note in here that the GLITCH kernel is not currently working with the newest Cyanogen nightlies. It bootloops and I found that out the hard way.
For now im running GLITCH v11.1ML and CM7 Nightly 35 and it's been great so far.
so glad I havent run into safe mode
Updated the wife's phone to CM7 some time ago because stock was getting really sluggish and unreliable for her. Wanted to give it some new life. Been running ok (a bit better than stock) but still not great. Kinda flaky, she says. I haven't had a lot of hands-on with it since setting it up, but she says it has poor battery life, likes to freeze up, etc... But overall, an improvement.
Today, she gets up, and her phone won't power on. I know her charger can be a bit temperamental, so pull and replace the battery, then hook it up to mine to try and get it to boot.
It powers up long enough to show her she has a lost call, then spontaneously reboots again. Now it's stuck in a loop while plugged in. It boots, gets to the lock screen, reboots. I can get into recovery (but it looks like stock recovery, not clockwork, so I can't reflash CM7 to see if that helps).
I wanted to try flashing a stock SBF so I could get it booting again, (or at least take it into Verizon), but it doesn't even power up when plugged into a USB cable hooked up to the computer, only on the charger.
Any thoughts? I'm kinda stumped, and not as familiar w/ the Droid 2 as I am w/ my HTC G2.
*Edit*
Eh, after sitting on the charger for awhile while I typed this, it actually came up and seems to be staying up. I guess the battery was just very VERY low? Nevermind!
Sbf the phone back to stock and use a more stable rom. Custom roms from what i am noticing can have 2 installs of the same rom and give 2 completely different results. I had this problem with my current rom miui 2.2.10. On my first install it was complete garbage, crashing constantly even with system apps. Then i Sbf'd back to GB using the newly released GB sbf file you can find in this forum. Then re-installed miui and it works fine now. So it could just be you got a bad install. Try miui 2.2.10 over at rootzwiki, its a solid rom.
http://rootzwiki.com/topic/17285-ne...tt-charge-while-off-updated-bootmenu-scripts/
Hi there,
fascinated by CM, I installed it meanwhile twice on my 9505 using the new Installer.
For the first 2 weeks, everything looked fine, but after some time, the phone started to shut down at random more and more frequently, by now after approx 10 minutes of use.
After this shutdown, a restart is pretty difficult - when I simply start again, it freezes at the "Samsung 9505" Screen; forcing a new start then provokes and endless loop of newstarts initiated by the phone itself; only taking the battery off helps at this point.
I'm pretty despaired, because I learned to love CM and its endless possibilities during the first 2 weeks... as mentioned above, the situation didn't improve after a second installation via the CM-installer.
What could be the prob and how can I fix it?
THANK YOU so much 4 help!
CASE CLOSED: The prob seems to be absolutely independent of CM - my battery is slightly bloated and this prob is known to cause such strange behaviour... Samsung will replace it.
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.