Hi all,
I installed CM7 on my TP a ways back but never really used it and stuck with WebOS. I decided to upgrade to CM9 Alpha2 yesterday and did without any issues. I then got curious about CherryKang and decided what the heck. I was able to install CherryKang but now I am having a few issues:
1. When booting CM is still listed in MoBoot and CherryKang is not. If I select CM, then I get the CM boot screen for a sec and then CherryKang boot screen comes up. Not that big of a deal, just hoping to get it setup right.
2. The Gallery force closes every single time.
3. Occasionally unresponsive when trying to wake it up. I always put it to sleep when I am done by pressing the power button, but I have to reset it to wake it up about 30-40% of the time.
Those are my only issues so far. Other than that I'm diggin' ICS.
1. CherryKang is based on CM9, if you don't like it change the name to cherrykang. Or something that suits you.
2. Reflash?? I had CherryKang before and I had no issues, try gallery++cm from market or play store whatever
3. Reflash?? + maybe wipe everything??
svenerator said:
1. CherryKang is based on CM9, if you don't like it change the name to cherrykang. Or something that suits you.
2. Reflash?? I had CherryKang before and I had no issues, try gallery++cm from market or play store whatever
3. Reflash?? + maybe wipe everything??
Click to expand...
Click to collapse
I tried wiping the cache, dalvik cache from CWM but no luck. Then re-downloaded and reflashed but still no luck. Ended up going back to CM9 Alpha2 and so far has been stable. I've been able to wake it up without issue far....
You may want to try and restall CM9 with the Acmeinstaller2 method. I read that although you can use CWM to go from CM7 to CM9, you can get leftover files/directories that could may or may not cause issues in CM9.
after using Acmeinstaller2 to get to CM9, you can safely use CWM to flash other CM9 roms. Also, before you flash, use classicnerd's moboot uimage and tga cleaner to wipe out previous boot images left by other roms.
Many people just wipe the cache and dalvik caches before flashing, and don't do the factory reset. I always do, because the roms seem to have less issues if I do the factory reset.
I've had a couple of instances in more than one rom where the lock screen doesn't respond (touch screen doesn't work) and I have to reboot, so I just disable the lock screen all together.
Gallery is currently working on my install of cherrykang, but I prefer Quickpic from the market, and usually install it right away.
I believe the boot option issue is because it uses the standard CM kernel, so that's what it boots up. If you flash the Bricked kernel, and entry will appear for that, even though you're using the CherryKang.
I too was getting the problem where it became unresponsive. What seemed to mostly work was setting the minimum clock up to 384mhz. You can use SetCPU from the market, or CPU Master (free in the market -- that's what i used). I had some problems again last night, but overall it seemed to help. His latest version did set the min clock speed to 200-something.
Thanks for all the tips guys. Still running strong with no lockups after going back to the original Alpha2.
I actually tried setting the min CPU higher prior to going back to [email protected] but that didn't work either. I still have my kids TP to install CM9 on so I might try CherryKang on that.
Related
Any benefit in updating revolution? I used the second release. I have to figure out why I fc all the time. Didn't happen until root. Also stick with twrp or load clockwork?
Finally any way to go to recovery from android, like clockwork does? Great feature.
I picked the wrong week to stop sniffing glue!
Try quick boot from the market. And see if that helps
Locked & Loaded
" Shooter on Deck"
TWRP for sure, +1 for quick boot from the market, right to bootloader or recovery. As far as the force closes, try a full wipe, reformat boot, data, system and cache. then install a rom fresh (no extras just a good base rom) and see if you have the fc's if not then add your apps, if you get fc's you will have to go back and start from scratch loading an app at a time untill you find the culprit. Also some kernels don't play nice with some phones so you can try different kernels and OC speed (provided you are using an OC kernel).
Good luck.
I found the issue. I had the stock voice mail app frozen, since I use google voice. After enabling it, the FC issues went away.
I can't seem to find a stable release, yet a lot of youtube videos show people using it?
I've tried the nightly versions and for some reason it just hangs at the samsung load screen.
Anyone know what's happening with it? are we waiting on CM9+ICS instead of CM 7.1 now?
richfreestone said:
I can't seem to find a stable release, yet a lot of youtube videos show people using it?
I've tried the nightly versions and for some reason it just hangs at the samsung load screen.
Anyone know what's happening with it? are we waiting on CM9+ICS instead of CM 7.1 now?
Click to expand...
Click to collapse
I've installed a couple of the nightlies and not had major issues. There were indeed bugs, which made me move on to other ROMs (among other reasons, including the fact that my old HD2 had CM7 and it got a bit old).
As far as my experience goes, the nightlies have been quite stable. As mentioned, there were bugs here and there, and a force close from time to time. But I didn't have the problem you've mentioned with hanging at install.
They did take a while to load the first time, longer than I remember was the case on my HD2. Did you wait long enough? Delvic/cache cleared?
EDIT: I also found a CM9 around New Years, but it wasn't as stable and had charging issues. But I think it's out and the waiting's over, really.
EDIT AGAIN: The other option would be to try out the official ICS release, which can be found at samfirmware.com. That's my plan for the weekend.
like the previous...Sounds like your flashing over existing roms without wiping everything first...From recovery mode after backing up, the best way I find is to wipe data/clear cache and wipe dalvic cache from advanced menu before flashing any roms...that way your starting with a clean slate and will be less conflictions from old to new.
for me CM7.1 not stable
I'm waiting a stable CM9 its promising
If you follow the instructions on how to install it, it's stable for everyone. I'm using it for many many months now, and it's stable.
If you're coming from other ROM's, make sure you do a FULL wipe, and flash the rom TWICE in a row, without rebooting recovery.
And yes, we're waiting for CM9. CM7 is not supported anymore for SGSII.
I cleared the data, the cache, went into advanced and cleared the dalvik cache.
Installed the nightly, which I thought was trange was only 100mb, normally ROM's are like 300mb.
I'll try flashing the ROM twice as TheSaw has said. However, after seeing that CM7 isn't supported, I may think twice, i'm just getting bored of the stock.
Might also be worth noting, i'm using [email protected] #k2-18 kernel.
Also, by the way Sean is here, did you know you've got a USA flag in your mini profile under your username? will the official release be a odin flash? or can I just use a .zip through CWM to flash it? and would I still be able to use the speedmod kernel with ICS?
Always working for me and thousands of others .
Usual story is wrong install .
jje
I managed to get this working, by installing the ROM once, and then installing it again straight after.
I was just wondering, is there a way to move the lock screen lock down to the bottom of the screen, i.e. above the unlock and camera buttons? and is there a way to change the clock?
Hi all,
Lately my tab is freezing at random moments. When opening gmail, youtube, browsing, settings, .. I can't use it longer than 5min or it will crash.
I'm running CM 10.1 nightly 20130118, Kernel 3.1.10-cyanogenmod (never upgraded this).
I have also tried older CM versions (CM 10, older CM10.1's, CM9) and AOKP -> same problem.
When I install a new rom I always wipe cache partition, wipe data/factory reset, wipe dalvik cache first.
I'm running CMW Recovery v6.0.2.7. Today I also installed a new bootloader (US_LPL_4.0.4_bootloader) but still the same issue.
Any ideas? Is it possible to do a harder reset than I already do? Should I maybe install a kernel update?
Thanks!
either you are overclocking and not stable, keep installing back the same bad app which is wreaking havoc, restoring from an old TB backup which is not playing nice on current stuff, installing some hack/mod which is wreaking havoc, or you have a hardware issue.
odin back to stock ics (this will completly wipe the whole tab out) and observe for a few days.
pershoot said:
either you are overclocking and not stable, keep installing back the same bad app which is wreaking havoc, restoring from an old TB backup which is not playing nice on current stuff, installing some hack/mod which is wreaking havoc, or you have a hardware issue.
odin back to stock ics (this will completly wipe the whole tab out) and observe for a few days.
Click to expand...
Click to collapse
Never overclocked so I'm afraid it's a HW issue.
Just installed stock ics and it still freezes after a few minutes (without installing any apps).
Guess I'm gonna try to put everything default again (I still have those 0/0/0 folders from JB) and return it to the shop..
lolsnorz said:
Never overclocked so I'm afraid it's a HW issue.
Just installed stock ics and it still freezes after a few minutes (without installing any apps).
Guess I'm gonna try to put everything default again (I still have those 0/0/0 folders from JB) and return it to the shop..
Click to expand...
Click to collapse
Jeps... Sounds like a hw issue if it is still causing the crashes on stock, how long do you use your tab now? maybe it has nothing to do with time, but just want to know..
DefQoN_BE said:
Jeps... Sounds like a hw issue if it is still causing the crashes on stock, how long do you use your tab now? maybe it has nothing to do with time, but just want to know..
Click to expand...
Click to collapse
I have it for about 9 months now but never really used it alot. I think in total maybe 40-50hours (watching movies on holidays etc).
I did leave it on the table once while the sun was shining through the window so that might have overheated the tab a bit.. Not sure if the issues started right after that. I could still watch a movie on it etc, now it crashes after 5min max.
lolsnorz said:
Hi all,
Lately my tab is freezing at random moments. When opening gmail, youtube, browsing, settings, .. I can't use it longer than 5min or it will crash.
I'm running CM 10.1 nightly 20130118, Kernel 3.1.10-cyanogenmod (never upgraded this).
I have also tried older CM versions (CM 10, older CM10.1's, CM9) and AOKP -> same problem.
When I install a new rom I always wipe cache partition, wipe data/factory reset, wipe dalvik cache first.
I'm running CMW Recovery v6.0.2.7. Today I also installed a new bootloader (US_LPL_4.0.4_bootloader) but still the same issue.
Any ideas? Is it possible to do a harder reset than I already do? Should I maybe install a kernel update?
Thanks!
Click to expand...
Click to collapse
I have the same setup as you and my tablet starts to crash this week. Gmail won't stay for 2 mins
Try this!
You need to wipe it clean and make sure your 16G is not getting full. You can use any file manager ap to start your clean up, which is all you need if the hardware is not damaged. Ok, so go to root and remove any excess file you might have, this will eliminate memory issues. Next, reboot into recovery, hope you are rooted, then wipe everything including delvic. Install your ROM [INFAMOUS_2.2], the best I have tested, and reboot your system. If you can't do this you need to reinstall CWM, I use 5.5.1.7, and then reflash your rom. If this doesn't get you back in the clouds contact me.
I was listening to music on my Evo 3D over bluetooth today, when I put it in my pocket and paused the music. After going back to my phone, I noticed it had reboot itself, and now it's stuck on a boot loop. Does this sound familiar to anyone? I can't think of any reason why it would boot loop like this. Wiping cache+dalvik doesn't fix the boot loop. After clearing cache+dalvik and booting the phone, it does go to the screen saying that Android is updating apps, but as soon as it finishes it goes right back to the boot loop. I'd appreciate any assistance in figuring this out. Thanks!
it happened to me the other day. i was using CM10.1 Wild for the night along with Saring Gas Kernel. i managed to fix this by wiping everything manually instead of using a superwipe, and then flashing again. and then i had this issue with MidNight Rom CM10.1 where whenever i turned bluetooth on, after turning it off the phone would freeze, reboot and then bootloop. however the Dev had specified that bluetooth was broken.
if the boot loop is at the Rom's boot animation, and you cant fix this by deleting Cache, Dalvik and Data, then you will certainly have to wipe it all and flash again. hopefully you had all you data backed up.
Kite-G said:
it happened to me the other day. i was using CM10.1 Wild for the night along with Saring Gas Kernel. i managed to fix this by wiping everything manually instead of using a superwipe, and then flashing again. and then i had this issue with MidNight Rom CM10.1 where whenever i turned bluetooth on, after turning it off the phone would freeze, reboot and then bootloop. however the Dev had specified that bluetooth was broken.
if the boot loop is at the Rom's boot animation, and you cant fix this by deleting Cache, Dalvik and Data, then you will certainly have to wipe it all and flash again. hopefully you had all you data backed up.
Click to expand...
Click to collapse
Yeah, I ultimately had to restore from a backup. This is an almost stock ICS rom, deodex plus a few other apps baked into the ROM, and the stock kernel.
Now this doesn't happen every single time I turn the screen off with bluetooth turned on, or every time I turn off bluetooth. This is just a random boot loop that hits out of nowhere. Since I can't figure out what causes it, I was hoping someone who had encountered it would know.
while i cant point out the exact cause, these random bootloops happen due to file system errors, or namely the kernel. but you say you had stock kernel, so if it was not overclocked or tempered with then that cant be it.
in my case, for example, last night i overclocked my phone to 1.8GHz and set the governor to performance, I/O to vr. turned the phone off and forgot to lower the settings or to increase voltage, and then when i turned it on the phone was in a bootloop. went to recovery and it said that cache was unreadable, suggesting a full wipe. what happened here was that the kernel settings i had used were saved in cache, so when i tried to boot with such high settings without the proper power for the cpu, the phone just couldnt boot. i wiped cache and the kernel settings got restored to default. so it booted.
another example was that i flashed an update.zip that was corrupted. the phone booted and behaved normally. then when i loaded any of the apps from the update.zip the phone would freeze, reboot and boot loop.
and then theres this one, my EVO could run every ICS rom perfectly, but every single 4.1+ rom i used had bugs, lag, visual glitches, and whatnot. i tried wiping multiple times, redownloading the roms, etc. in the end nothing helped. then i tried a superwipe which checks the filesystem for errors and optimizes it. after using that superwipe, every 4.1+ rom ran smoothly, and the ICS roms i had used benchmarked better than before
so if you say you got that boot loop randomly, and using stock kernel, i can safely assume that either the rom did not flashed properly, or that your EVO has some file system errors. you could try either a new fresh install or using a superwipe and flash your Nand, but if it was me, i would use superwipe, then manually wipe everything, and fresh install the rom. if the nand backup you installed after the bootloop was from the same install as the one who gave you the bootloop, then its a safe bet that it could happen again. i would backup all my apps and data, and do as i said earlier.
hopefully this info helped you a little.
in case you would want to give it a shot, here is the superwipe i used.
like i said, just flash the file on recovery, you dont need to wipe beforehand. and after its flashed, i recommend you wipe but its not necessary. then just flash your rom, and other files if any, and boot. hope it helps.
(i was gonna link to the thread where i got the super wipe, but i forgot where i found it. anyways, credit goes to author)
Kite-G said:
while i cant point out the exact cause, these random bootloops happen due to file system errors, or namely the kernel. but you say you had stock kernel, so if it was not overclocked or tempered with then that cant be it.
in my case, for example, last night i overclocked my phone to 1.8GHz and set the governor to performance, I/O to vr. turned the phone off and forgot to lower the settings or to increase voltage, and then when i turned it on the phone was in a bootloop. went to recovery and it said that cache was unreadable, suggesting a full wipe. what happened here was that the kernel settings i had used were saved in cache, so when i tried to boot with such high settings without the proper power for the cpu, the phone just couldnt boot. i wiped cache and the kernel settings got restored to default. so it booted.
another example was that i flashed an update.zip that was corrupted. the phone booted and behaved normally. then when i loaded any of the apps from the update.zip the phone would freeze, reboot and boot loop.
and then theres this one, my EVO could run every ICS rom perfectly, but every single 4.1+ rom i used had bugs, lag, visual glitches, and whatnot. i tried wiping multiple times, redownloading the roms, etc. in the end nothing helped. then i tried a superwipe which checks the filesystem for errors and optimizes it. after using that superwipe, every 4.1+ rom ran smoothly, and the ICS roms i had used benchmarked better than before
so if you say you got that boot loop randomly, and using stock kernel, i can safely assume that either the rom did not flashed properly, or that your EVO has some file system errors. you could try either a new fresh install or using a superwipe and flash your Nand, but if it was me, i would use superwipe, then manually wipe everything, and fresh install the rom. if the nand backup you installed after the bootloop was from the same install as the one who gave you the bootloop, then its a safe bet that it could happen again. i would backup all my apps and data, and do as i said earlier.
hopefully this info helped you a little.
in case you would want to give it a shot, here is the superwipe i used.
like i said, just flash the file on recovery, you dont need to wipe beforehand. and after its flashed, i recommend you wipe but its not necessary. then just flash your rom, and other files if any, and boot. hope it helps.
(i was gonna link to the thread where i got the super wipe, but i forgot where i found it. anyways, credit goes to author)
Click to expand...
Click to collapse
Just FYI, the Wild For The Night OP specifically says do NOT use superwipes. Superwipe scripts and AOSP Roms don't always play together nicely. That's and CM Rom. Factory reset wipe in recovery is fine.
I am aware of that. But thanks for pointing it out. Althought I haven't had any problems with AOSP roms & superwipes when I wipe manually after the superwipe, only when I don't. But then again results may vary. At least in my case, I'm pretty satisfied with the results.
Sent from my HTC EVO V 4G using xda app-developers app
Hellybean is by far the best ROM I've used yet on my Note. It runs almost perfectly. I did have to reboot because my bluetooth wouldn't come on (reboot always fixes that). However, when I rebooted it, the phone tried to restart, I saw the Samsung SGH-I717 screen, and then it went black. It never brings up the Hellybean ring of fire. If I pull the battery I see the ring of fire for about 5 seconds, then it reboots, then black screen.
At this point, the only thing I can do is force the phone into TWRP and restore a previous backup. Does anyone have any idea what could cause the phone to not want to reboot back into the system?
I was on the latest Hellybean build and TWRP is up-to-date as well. I had to revert back to the October 10 build though. I just tried rebooting it after a restore and the same thing happens (so it's not specific to a certain date of ROM). As long as I don't reboot I don't have a problem.
Thanks
Chris
MI_SS_IL said:
Hellybean is by far the best ROM I've used yet on my Note. It runs almost perfectly. I did have to reboot because my bluetooth wouldn't come on (reboot always fixes that). However, when I rebooted it, the phone tried to restart, I saw the Samsung SGH-I717 screen, and then it went black. It never brings up the Hellybean ring of fire. If I pull the battery I see the ring of fire for about 5 seconds, then it reboots, then black screen.
At this point, the only thing I can do is force the phone into TWRP and restore a previous backup. Does anyone have any idea what could cause the phone to not want to reboot back into the system?
I was on the latest Hellybean build and TWRP is up-to-date as well. I had to revert back to the October 10 build though. I just tried rebooting it after a restore and the same thing happens (so it's not specific to a certain date of ROM). As long as I don't reboot I don't have a problem.
Thanks
Chris
Click to expand...
Click to collapse
have you tried any other roms?
I have ran every update of Hellybean since its arrival here. I had made a backup and flashed another rom, didn't like so I went to install back up.
it would not install, just kept looping in the boot screen. had to fresh flash the rom. didn't matter which, just had to reflash. screen never went black though. you issue sounds more similar to a stuck power button, which is why I ask if you have had same problem with another rom.
I find it hard to believe this rom wont restore a back up. others have not chimed in with that specific issue. but you and I may just be 2 that have voiced the issue. wasn't that big of issue for me as I thought it more an oddity. my back up wouldn't install at all in 3 attempts, so again, whyi question your power button.
try another rom real quick if you can. don't have to like or want it, but this is a test right?
let us know what happens
captemo said:
have you tried any other roms?
I have ran every update of Hellybean since its arrival here. I had made a backup and flashed another rom, didn't like so I went to install back up.
it would not install, just kept looping in the boot screen. had to fresh flash the rom. didn't matter which, just had to reflash. screen never went black though. you issue sounds more similar to a stuck power button, which is why I ask if you have had same problem with another rom.
I find it hard to believe this rom wont restore a back up. others have not chimed in with that specific issue. but you and I may just be 2 that have voiced the issue. wasn't that big of issue for me as I thought it more an oddity. my back up wouldn't install at all in 3 attempts, so again, whyi question your power button.
try another rom real quick if you can. don't have to like or want it, but this is a test right?
let us know what happens
Click to expand...
Click to collapse
Let me clarify ... I'm not having a problem restoring or installing Hellybean or any other ROM. It's after I install or restore and the ROM is running fine (for days even) ... at some point I have to reboot for some reason and it's then that it won't boot back into the ROM. In other words I can't reboot my system because it never comes back to the ROM. I have to then boot to TWRP, restore something else and then that will boot to the ROM. If I reboot again after the ROM is up and running, I get the same thing, it won't boot back into the ROM, I have to restore again. That rules out a power button ... if it was stuck I would never get back in.
I've tried most of the ROMs out there, but since Hellybean I haven't tried any others (because this is the best one). You think there's any possibility dirty flashing all of the Hellybean builds over top of each other could cause it? Maybe I'll try installing the latest one from a full wipe.
Thanks
Chris
MI_SS_IL said:
Let me clarify ... I'm not having a problem restoring or installing Hellybean or any other ROM. It's after I install or restore and the ROM is running fine (for days even) ... at some point I have to reboot for some reason and it's then that it won't boot back into the ROM. In other words I can't reboot my system because it never comes back to the ROM. I have to then boot to TWRP, restore something else and then that will boot to the ROM. If I reboot again after the ROM is up and running, I get the same thing, it won't boot back into the ROM, I have to restore again. That rules out a power button ... if it was stuck I would never get back in.
I've tried most of the ROMs out there, but since Hellybean I haven't tried any others (because this is the best one). You think there's any possibility dirty flashing all of the Hellybean builds over top of each other could cause it? Maybe I'll try installing the latest one from a full wipe.
Thanks
Chris
Click to expand...
Click to collapse
I have dirty flashed every one. the only thing I try to do when gong dirty is to still give it that 10 settle time. no particular reason other than my OCD
Okay, thanks for the replies. I'll play around with it some more, maybe try a fresh install and see if that changes anything. I'll let you know if I figure it out.
Chris
I figured it out. Not Hellybean at all. It was TWRP. I reverted back to an early build and then reinstalled 2.6.3.0 and now it reboots fine.
Chris
I guess I can't edit the title to reflect the correct issue? Thread can be deleted if the moderators want. Hellybean is running strong ... it's the first ROM I get 0 random reboots.
Thanks for the help captemo and to the makers of Hellybean.
Chris
beanstalk
I got exactly same problem with beanstalk 4.3.
I tried reinstall recovery but no luck. Every time powering off or rebooting need a fully wipe and restore.
Do you think other or older recovery will work?
hotgly said:
I got exactly same problem with beanstalk 4.3.
I tried reinstall recovery but no luck. Every time powering off or rebooting need a fully wipe and restore.
Do you think other or older recovery will work?
Click to expand...
Click to collapse
Same issue. Any of the 4.3 ROMS.
MI_SS_IL said:
I figured it out. Not Hellybean at all. It was TWRP. I reverted back to an early build and then reinstalled 2.6.3.0 and now it reboots fine.
Chris
Click to expand...
Click to collapse
So did you:
1- restore a stable backup
2- boot to recovery and flash TWRP (which version?)
3- Boot back into recovery
3- wipe and flash HellyBean
Is this correct?