I've been running CyanogenMod 7.0.3 on my Desire Z for the last couple of weeks but have been unhappy with the battery life, so thought I'd try installing the Pershoot kernel as it had been recommended elsewhere here.
I downloaded and installed Pershoot using ROM manager but the phone got stuck trying to reboot - I got the blue Android with the spinning arrow going perpetually I waited 10-15 minutes for it to complete, took out the battery, retried, waited another 10-15 minutes but it still wouldn't complete the boot process. In the end I had to restore to my previous backup.
Has anyone successfully deployed Pershoot on an existing CM7 setup?
itm,
I've been running Pershoot on both CM7 and MIUI on my Desire Z without issues. Might just have been a hickup with your handset.
I'd try it again. Just to see.
Cheers mate,
Hopefully you won't run into the problem again.
Thanks for your reply. As a matter of interest, what method did you use to flash the kernel? Did you use ROM Manager?
Hopefully your flashing straight through recovery and not RM. If your not, that might be the problem.
I downloaded Pershoot from Rom Manager and then used the Install feature from Rom Manager which then rebooted into CLOCKWORK RECOVERY and then installed the Kernel.
I didn't run into any problems.
Thanks for the replies. I tried installing a different ROM from a .zip on the SD card (Wildmonk's 2.6.38.8) and this time it worked.
The main reason for checking out alternatives is to compare battery life. How have you guys found battery life compared to the CM7 default kernel?
Also, which version of Pershoot are you running?
I just updated to the latest MIUI release earlier 1.8.19.
My battery life depends on how much I use it... I'm quite a heavy user and I'm getting a little over 24hrs. On the weekend I may get more as I don't use it often up to 30hrs.
I'm currently running on the following:
Related
i'm running cm7 nightly with latest radio, wimax, 1.90 pri and nv. everytime i flash a kernel my phone gets stuck at white screen and will not allow a nand restore whatsoever. my battery life is terrible even if i try pri 1.7 and nv 1.7.. wiping never helps.. why is this happening? any ideas???
Probably because you are doing something wrong. Just like this thread you felt compelled to start. You know you could ask this question in the CM7 thread or even the question and answer forum...
Ok now that that has been said what kernel are you trying to flash?
Sent from my PC36100 using XDA App
i placed the same question over on cyanogen forums and got no help. i was using cm7 nightly build 8. I wiped then flashed sz 0.0.9 no sbc kernel and 30 minutes later froze, rebooted and still stuck at white screen. Booted into recovery and only got amon_ra_1.8 never loaded. So i had to put the pc36 file on my sd card via laptop and managed to go into hboot that way. Let it update itself then reflashed cm7 nightly #8. Was working smoothly except for battery life which is why i did a back up and tried netatchy_toast_4.2.3. That worked a few hours and landed me back at frozen white screen with a nand backup that kept giving me a flash error. After 3 tries the backup loaded and thats where i'm stuck at. I think i'm about to flash cm7 build 12, the latest, see how it works, then give a shot to another kernel. Any ideas?
Yes. It's a nightly build. It's unstable, and no one is going to help because it's almost impossible to troubleshoot.
also netatch's kernels are for sense roms. Use an AOSP kernel.
Try the kernel in my sig. Seems to work pretty well.
tried to post in cm7 thread but got a "new user" warning saying i dont have enough posts to post in that area. so i had to start at the noob level..
HipKat said:
Try the kernel in my sig. Seems to work pretty well.
Click to expand...
Click to collapse
Im gonna give that kernel a shot if nightly 12 still sucks up my battery. Only thing is, thats the same kernel that got me frozen the first time lol. Maybe it will run better with nightly 12?
Do a full wipe of system, boot, data, and cache, then flash just the ROM and GApps package. If you still have issues, get a logcat, and post in the CM7 Nightly thread here.
sounds like a plan. just got done flashing #12. Colors in notification bar stay white sometimes now lol. I wiped first then flashed. Read somewhere you didnt have to wipe if flashing 12 over another nightly. Wiped regardless, just throwing it out there..
oh, do i need to reflash pri and nv or are they not an option for nightly builds? tried them once before and pri never showed up.
cm7 nightly #12 seems to have helped battery life alot. Taught my daughter to ride her bike, went to movies and saw "Rango", stopped by walmart, came home, battery remained strong. On nightly #8 it was dead in 3 hours. #12 seems like a winner so far!! Not sure what pri and nv come in #12 or if they need to be reflashed or which one i should flash if they remain old etc... etc... Thanks in advance for any help!!
quickstang1 said:
Not sure what pri and nv come in #12 or if they need to be reflashed or which one i should flash if they remain old etc... etc... Thanks in advance for any help!!
Click to expand...
Click to collapse
There are NO PRIs / PRLs/ NVs, or any of those things. Those are never part of any rom flash. Those are either flashed separately, or obtained through a sense ROM via profile or prl updates.
Also, even though you are thinking things are fine with your current build, I am curious what recovery you are using... and what is your HBOOT. are you forever S-OFF?
using amon_ra 1.8, unrevoked forever. Cm7 nightly #12 is kickin a$$!!! No reboots, no battery drain, no weird glitches.. Stock kernel, cpu set at "performance", unplugged from 8am to 4 pm, using internet all day, wimax on, 3 weather widgets running, made it all that time and still had 15% battery left... Not sure what was changed in 12, but its a definite keeper!!!
I am looking to start over from scratch. I have CM7 running off emmc with 7.1 but I just want to redo this from the beginning. The reason I want to do this is because the boot time on my Nook is like 2 mins 30 secs where my dads rooted nook color is on in like 30 seconds. So what is the best way to start this process over? Reboot to recovery and just wipe everything or should I write the clockwork image to the sd card and really start from the beginning. Will it make a difference? Thanks in advanced.
What version of CM7 are you using now? RC, nightly? Do you have ROM Manager? I am running one of the latest nightlies. While it doesn't boot in 30 seconds, it is no where near 2 1/2 minutes. If it were mine, I would download ROM Manager if you do not already have it. (Make sure you have a non bootable SD card installed as you generally need it anyway and will with ROM Manager.) First check that you have the latest version of Clockwork Recovery installed. ROM Manager will tell you if you do not and you can install it from there. Then pick a nightly in ROM Manager. 132 would be a good start as it has an OC kernel in it. Choose that along with the market (box to check), then install. Only check off the box to wipe Davlik cache. It will take a bit to download and install and much longer to reboot the first time. See if this helps before going through the trouble of a complete wipe. CM7 will take longer in general as it has much more to it than a rooted stock ROM. Also, if you do not yet have it, download and install Titanium Backup before you do any of this and back up your apps to your SD card.
I'm running the latest RC. I do have rom manager with the latest CW installed. I have titanium pro which backs up to my drop box account. So I guess I can do what you suggest. It just seems so painfully slow on start up, especially with SOD it gets annoying waiting so long to use my nook.
There were issues with nightly 132-134. I would suggest 140 as a good starting point as it fixed several wifi and SOD issues. Also the first few nights after combining with dals OC had some issues with slow graphics. All good now. Just saying.....
Sent from my Nexusone using Tapatalk
I just timed a reboot, I'm running n142 (today's).
After 30 seconds, the shutdown and u-boot are done and the boot animation starts.
About 40 sec after that, the animation brightens and stutters a little bit (this means something, but I don't know what).
Ten seconds after that, I get the home screen.
Overall, less that a minute and a half. Note that booting after a ROM flash will take longer because it has to recompile the system jars.
Good day all. I recently bought a Nook Color. I'm running CM7.0.2 along with gapps 20110613 from a 16gb SanDisk class 4 SD. When set up the apps (after enabling wifi) I got an error, due to the fact that my sucky router dropped the signal. As a result of this I was not able to download gmail, google maps, etc. My android market runs perfectly but I wanted to flash gapps so as to download gmail and the others. I went into ROM manager and updated to the latest CWM. However, no matter what I do I can't but into recovery. I tried n+power button, reboot into recovery from the power button menu, and from within ROM manager. All no go...it just booted into CM7, so I removed the SD card to boot into stock Nook 1.2 software. When I did this it brought me to the CWM recovery menu (SD card not in). Of course I could not select anything on the menu. Put back in the SD while still in the menu to try select an option but nothing. Shut it down by holding the power button and booted it back up and it went str8 into CM7. Shut down took out SD and it booted into stock Nook 1.2 software. What am I doing wrong guys? I'm trying to flash the overclock kernel and reflash gapps. THANKS
Could the reason gmail, youtube, googlemaps didn't install on setup be due to the fact that I'm not in the USA? If so I'd still like to know what the problem is so I can flash the overclock kernel.
No one has any idea? I know one option is to backup and redo everything, but I'd really like some troubleshooting ideas before.
Did you use the 1.3 image from verygreens thread? If so the old 7.0.* stables are not supported. You will need to back up and redo it either with the old image or a new CM7 version.
---
- Sent from my LG Optimus V using Tapatalk
Yea I used the 1.3 in the thread with 7.0.2. What version cm7 would I need to use with the 1.3? 7.0.3 or a nightly,? Where would I be able to find an older image to work with 7.0.2 and what version of the image should it be?
The 1.3 image won't work with any 7.0.* versions. You should upgrade to either a recent nightly or the 7.1.0 RC. You could find an older image somewhere but there isn't much of a point as you would have to redo it all anyway so why not upgrade? Plus your battery life will improve by a lot as 7.1 RC and the nightlys have deep sleep.
---
- Sent from my LG Optimus V using Tapatalk
As I said many times to newbie who runs CM7 off uSD that do not or should not mess up with ROM Manager. In fact, there are members also confirm that if booting off uSD, ROM Manager has no effect.
Based on what you, OP, described, you had flashed the CwM into the internal memory.
Keep your fingers crossed as I do hope you didn't screw up anything else.
Anyway, using verygreen's 1.3 image along with the latest nightly-built CM7 and the latest 06132001 gapps and boot it off uSD again. You should be fine.
Before that, fix your home wireless network first.
I decided to just go with 7.1RC1 since I wanted the better battery life. Is there a way to check about the CWM on the internal and how would I go about removing it if I did? I ask for warranty purposes ofcourse since I opted for the 2 year extended one. Also to flash upgrades and such, since you don't recomend using ROM manager then how should I go about doing it (i.e. overclocking kernel)?
dna59 said:
I decided to just go with 7.1RC1 since I wanted the better battery life. Is there a way to check about the CWM on the internal and how would I go about removing it if I did? I ask for warranty purposes ofcourse since I opted for the 2 year extended one. Also to flash upgrades and such, since you don't recomend using ROM manager then how should I go about doing it (i.e. overclocking kernel)?
Click to expand...
Click to collapse
1. I never have any issue related to battery with any nightly build that I've ever used. I am currently having the nb153 and it is fantastic.
2. Check CwM and how to remove off the internal memory? I don't know any quick way except restoring the original ROM.
Again, for warranty purposes, strongly suggest running off uSD
3. Updating by loading/copying/dragging the updated files onto the root folder (aka "boot" partition), then TRY loading into Recovery by:
a. combination of power/N buttons if you have skill or
b. let it boot normally into CM7, wait until completely loaded, then reboot and select "recovery" option. Keep yr fingers crossed. This is an easy method but if it doesn't work then option a is the only choice.
Sorry the battery issue was as compared to the current CM7 stable not the nightly. I got everything installed so far besides the overclock kernel. So I will try your recommendation for booting into recovery not using ROM manager.
You don't flash anything when running off an sd card you just boot into recovery and then reboot. Easiest way to get the overclock kernel would be to just upgrade to the latest nightly.
---
- Sent from my LG Optimus V using Tapatalk
I made the switch from CM7 (froyo kernel) to MIUI Gingerbread a few days ago.
The "cool factor" on my phone has definitely improved. MIUI is sweet! I've no idea why I held my nose up to it for so long.
Anyway.
It seems The DXC 1.9.23 MIUI that I flashed seems to have automatically updated me to CWM 5.0.2.0.
Bummer. My understanding is these backups aren't compatible with 2.5.0.7?
I THINK that may have something to do with my problem...maybe.
I can't seem to get the "Power Menu" to reboot me into CWM.
I wanted to flash my old BootAnimation back on now that I've decided to stick with MIUI.
Holding the power button and selecting Reboot into CWM brought up an expected SU dialog.
I accepted. I'll attach a screenshot of the package...as it just seems funny to me.
Nothing happens.
No reboot. Nothing.
All the other options work.
Hotboot...bootloader...stock recovery...reboot...
https://lh3.googleusercontent.com/-v...001_063054.jpg
Also, that file on my SD card that it's referencing to doesn't seem to exist.
But I've no idea if that is normal or not.
=] <----Noob.
Rebooting into CWM via ROM manager works fine, however. So I'm confused.
Any ideas?
Hey Jubakuba! I too recently installed MIUI on my Droid X over the Gingerbread kernel. After searching through multiple forums and posting all my troubles, I've come to the conclusion that MIUI and CWM don't play so nicely together. Apparently you must use ROM Manager for all flashing, backups, and recoveries. I was using Droid2Bootstrapper and it caused my phone to factory reset every time, the result being a loss of any settings I had on MIUI (it looked like I just flashed it), Torch not working at all, themes not working, and a factory reset on every subsequent reboot. Try using ROM Manager for all your backup/flashing needs. I'm putting MIUI back on my phone as we speak and I'll be testing ROM Manager out. If you need me to post my results, I will. Good luck!
Sometimes you have to reflash CWM after installing a new ROM. Do it through ROM manager and see if that helps.
All...
Looking for some guidance before I go complete wipe/reinstall.
After months of rock solid performance, I'm getting constant total freezes with CM7. I don't have a whole lot of apps, maybe 30, and don't use Beautiful Widgets (I believe I've seen that mentioned as a possible culprit.) It seemed to be somewhere around when I flashed the newest version of Gapps (0828,) but I can't confirm.
Just to try, I flashed the newest nightly of CM7 and reflashed the older (06xx) version of Gapps. Same problem. Thought it might be a bad SDcard, but removing the card still gets freezes.
Nothing consistent - sometime it'll go for hours with no problem. Sometimes it's 2 minutes after I reboot.
So I'm looking to clear and restart. Any suggestions? Should I backup and restore the apps from Titanium Backup, or is it safer just to reflash and reinstall everything fresh from the market.
Any other recommendations?
Many thanks!
Adam
Have you tried fixing permissions?
Sent from my LG Optimus V using Tapatalk
koopakid08 said:
Have you tried fixing permissions?
Click to expand...
Click to collapse
Yes, and should have mentioned that. Have also taken overclocking from 1200 On Demand down to 1100 Conservative, though 1200 was completely stable for quite a while. No dice.
Thanks.
Adam
Thought it might be a bad SDcard, but removing the card still gets freezes.
Click to expand...
Click to collapse
I assume that means you are running CM7 off the eMMC, correct?
How are you flashing? ROM Manager? Download the .zip to the SD card and boot into CWR? When you flash a ROM do you wipe Davlik? What version of CWR is on your device?
patruns said:
I assume that means you are running CM7 off the eMMC, correct?
How are you flashing? ROM Manager? Download the .zip to the SD card and boot into CWR? When you flash a ROM do you wipe Davlik? What version of CWR is on your device?
Click to expand...
Click to collapse
Yes, running of emmc.
Originally flashed a nightly (current as of, maybe, 2-3 months ago) using bootable SD card into CWM. I updated early last week using a flashed CWM but with CM7 image on a card. Also updated to the latest nightly yesterday using ROM Manager.
Current Version: 0930 (207, I believe)
Yes, wiped Davlik each time.
Thanks.
Adam
Actually, after many months of rock solid Nook performance using CM7 and Phiremod and MIUI I've experienced a lot of random freezes the past couple of weeks no matter what ROM I'm using. I wonder if my hardware is becoming unreliable. I've scrubbed and wiped every element of the device before doing new ROM installs, changed SD cards, re-downloaded ROMs. Installed CM7.03, CM7RC1, CM7 nightlies, various MIUI iterations, all to internal memory. My Nook will run anything smoothly for a few days and then start freezing no matter what I do. I do use Beautiful Widgets so I'm not running that right now, just in case. In fact at the moment I have NO widgets, shortcuts or anything else on my homescreens, just to see if that helps. Yes, I've tried fixing permissions too. A head scratcher.
lesdense said:
Actually, after many months of rock solid Nook performance using CM7 and Phiremod and MIUI I've experienced a lot of random freezes the past couple of weeks no matter what ROM I'm using.
Click to expand...
Click to collapse
Well that's not promising. Hopefully I don't have whatever syndrome you do.
I'm going to do the full wipe this afternoon and see what happens with a fresh install.
Adam
I have come to believe that my problem was NOT with whichever ROM I was using but with Beautiful Widget. Using the usual trial and error method I found that, if I did not install Beautiful Widget I didn't have a freeze problem either with MIUI 1.8.5 or CM7.1RC1. Its a shame because I like that widget but I switched to Fancy Widget (a lot less flexible but gets the job done) and I'm fine now.
For some reason certain apps just don't play well with the Nook. They will freeze it regardless whether they are running or not. Simply having them installed will cause frequent freezes from my experience. Everytime I encounter more than two freezes I will delete the last 5 or so most recently installed apps.
@stir fry alot,
Is there an app that keeps track of installs?
I had a similar freezing issue..I had to reformat my SD card and reload my apps...took care of it.
Thanks guys!
I'm running 7.1 stable that i installed from scratch on SD and kept getting freeze ups too and stumbled across this thread and wanted to say THANK YOU! I uninstalled beautiful widgets and no more freezing! Whoohoo!