Related
I see in the Dev forum that the first RC1 of Cyanogenmod 7 for Milestone is available, but when I go to download it here, it doesn't seem to be available. I guess it would be called update-cm-7.0.0-RC1-0.07-11.02.18-Milestone-signed.zip but that last one available was the 11.02.15 release. Does anyone know whether the RC1-7.0.0-11.02.18 has been withdrawn for some reason?
I've been testing each and every build with good success, so I'm really keen to try the new one. I would ask in the dev forum, but I'm relatively new at the XDA forum and am therefore not eligible to post in it.
SF
Well, I eventually found the correct download link at https://github.com/downloads/nadlabak/android/update-cm-7.0.0-RC1-0.07-11.02.18-Milestone-signed.zip
Thanks,
SF
How is it working out so far? I've recently just started using cm6 but I don't want to install too much / get invested in it if CM7 is solid enough to use day 2 day.
FANdroid said:
How is it working out so far? I've recently just started using cm6 but I don't want to install too much / get invested in it if CM7 is solid enough to use day 2 day.
Click to expand...
Click to collapse
I would stick with cm6 for now. CM7 could use many improvements and as of now is very memory hungry (I was on the feb.10 release). CM7, however, has many bug fixes that are not implemented in cm6, for example, the wifi fix (wasn't working with some n routers before I think [depending on the security type or something] ) and it seems as though there is also the random freeze + random reboot fix (using another, older kernel) I would not switch to CM7, until many bugs are fixed. Also some games don't work.
FANdroid said:
How is it working out so far? I've recently just started using cm6 but I don't want to install too much / get invested in it if CM7 is solid enough to use day 2 day.
Click to expand...
Click to collapse
It's great. But video playing not working for me.
So I installed CM7 to try it out, and on RC1 my videos play fine (widescreen) using the included "Video" app. Well most of them do, one of them is displayed 4:3 for some reason?
I'm finding that it works quite well. Battery life is good, but there are a few bugs that need working out. CM6 is probably better if you need your phone to be 100% reliable, but I like to push the boundaries and play around.
Bugs or missing features so far:
- Button lights and keyboard backlight not working properly for me (and at least one other user here)
- Auto backlight brightness not working for me at all
- Volume button swapping/remapping not yet implemented, so that in lanscape mode left means louder (which is the wrong way round for me)
- Memory usage is a problem, so that Launcher pro keeps having to re-initialise
- Camera is VERY unreliable
- Getting random reboots and lockups, especially in Google Maps
Still, things are getting better with every release and I can always go back to CM6 if I want, since I made a Nandroid backup in OpenRecovery before I installed the CM7 update. I've just installed the RC2 update, so lets see how that goes...
SF
Hi all, just wondering if anyone could provide/knows where I can find a comparison between different versions of android on the NC? Considering switching from cupcake to cyanogen or honeycomb, just wondering what the benefits would be. Thanks!
I would say Cyanogemod 7, based on the fact that everything literally works.
CM7 with the tablet tweaks, or honeycomb. Overall, I find honeycomb to be far more enjoyable on a tablet, but CM7 with tablet tweaks is close behind and, as Burnes says, is more functional in the sense that more apps work on it and you have more features eg. bluetooth and better video.
If you can't choose, dual-boot regular CM7 and honeycomb
Customized Nookie Froyo 0.6.8 image for sdcard (3/31):
http://forum.xda-developers.com/showthread.php?t=922324
It runs off the sdcard so I don't have to worry about BN update. Great battery life; it used about 5% over 16 hours; I did not turn OFF wifi when I put it to sleep, and when I woke up the NC the wifi came back by itself (i.e. I don't have to do anything) within a few seconds.
I have not tried CM7; from what I've read it's a great ROM, and the only major kink left is battery life at sleep. I have no doubt that the gurus here will iron out the kinks, and in a month I look forward to running rooted, OC BN 2.2 stock off emmc and CM7 off the sdcard.
Definitely CM7, especially considering that mad-murdock's tablet tweaks will be commited soon
I would have to say the CM7 tablet mod by mad-murdock is the best version to be using given all the tablet friendly features it has but Nookie Comb is nice though I didn't use it more then a few hours before going back to the CM7 mod. I liked honeycomb but it has some flaws and probably won't try it again till we get a source code dump from google.
Nookie Comb is the best, at least for me.
Madmurdocks CM7 RC4 with tablet tweaks
w/ dalingrin's 3/31 OC kernel
I Love It
I have seen no comprehensive comparison of the current versions of the available roms written up, sadly. I think for the same reason I have not done one:
I like what I am using and don't want the hassles of setting up all the others too.
So this isn't going to be an easy one...
It depends on your needs and desires- different strokes for different folks.
IF you want the most hardware working properly, best software compatibility and most intuitive tablet experience- CM7 with the Tablet Tweaks (Tweaks are not in full rom yet but will be soon. Download in first post- http://forum.xda-developers.com/showthread.php?t=1002000) CM7 is intended for internal (emmc) insatllation but folks have gotten it working from sd too, I believe.
If you want Honeycomb to experience a version of Android that Google intended for tablets, it is available in emmc and sd versions as well. Please understand that the actual source code has not been made available yet, so this version is a Preview and has problems that can't be easily fixed without proper source. From all reports it is pretty good though.
Nookie Froyo has fans as well and can be installed either way (emmc/sd) and I am sure there are advantages to be found.
Even stock has good reasons to be chosen: many people really LIKE the stock B&N app and some of its features. Root makes it better of course, adding a real market to the device.
Pretty obvious to tell what my choice is, but I really do think they are all good.
Maybe you can try the all and do the first comprehensive comparison.
^nicely put.
I run my installs off the SD, so i have a stock nook when i want by just popping out the sdcard.
i just picked up a nook and have been trying all sorts of various roms trying to find what i like. I like honeycomb but feel it isn't quite ready yet.
cm7 does seem to have the most working features. One thing that has held me back is that I've been told that sleep doesn't work which forces you to charge daily. I have yet to add the tablet tweaks so maybe i ought to try that.
i've chosen to run nookiecomb and like it except for no bluetooth.
Thanks everyone, this has been super helpful! I've been spending hours every day for the last week or so tweaking my NC, but I'm still pretty n00bish. I'm going to give cyanogen a whirl, as the votes seem to go that way (although the battery life of froyo is tempting...).
Frankly, i can't see why anyone actually chooses to use anything other than CM7 right now. It is more stable than the Froyo build, and more up to date in terms of code base. Yes, it drains battery faster, but it also doesn't have an SOD issue that Froyo has (which is FAR more annoying). CM7 right now has bluetooth working, and with the fully working hardware acceleration, there is no reason to choose the older OS...
Divine_Madcat said:
Frankly, i can't see why anyone actually chooses to use anything other than CM7 right now. It is more stable than the Froyo build, and more up to date in terms of code base. Yes, it drains battery faster, but it also doesn't have an SOD issue that Froyo has (which is FAR more annoying). CM7 right now has bluetooth working, and with the fully working hardware acceleration, there is no reason to choose the older OS...
Click to expand...
Click to collapse
what is the SOD issue?
SOD = sleep of death. Basically, your system can be locked up after putting it to sleep, and will not come on without long holding the power button and going through a full bootup.
Hi..
I Have a nexus one. My question is regarding the CyanogenMod Nighty and stable. whats the difference? Which one should i use? Which is better?
Thanks.
Nightly build = Work-in-Progress version. You can try new features, but it can be buggy and less stable. Besides, there's no support provided officially.
Stable = The 'Official' version.
great
Thanks a bunch, helped me out
FYI, the nightlies will also be the first to get major bugfixes like the wonk. That has been in the nightlies for almost a week, and they are still working on updating the stable to 7.0.4 to include it. The nightlies have also been running 2.3.4 for a couple of weeks, which was nice when the big security flaw came out that affected all versions except for 2.3.4.
Nightlies usually end up still being "stable", they just don't have any labels next to it, although occasionally there have been issues that will crop up that are usually resolved the next nightly (like earlier this week, a nightly caused the alarm app to FC whenever someone tried to set an alarm, this was resolved in the next release).
I usually stay behind on the releases, as I need my phone to be running and able to do the functions that I need. This way I can read what others are experiencing and see if it is worth upgrading to. Currently I am on #76 and I think #80 was just released.
Also, "stables" aren't always stables (which is the case in most programs). Just like with Windows, there are updates that need to be put out when security holes or major bugs are patched. But the smaller bugs will usually get fixed in the nightlies long before they ever make it to the stable.
Overall, I love the nightlies. I don't think I could go back to a stable build.
bassmadrigal said:
FYI, the nightlies will also be the first to get major bugfixes like the wonk. That has been in the nightlies for almost a week, and they are still working on updating the stable to 7.0.4 to include it. The nightlies have also been running 2.3.4 for a couple of weeks, which was nice when the big security flaw came out that affected all versions except for 2.3.4.
Nightlies usually end up still being "stable", they just don't have any labels next to it, although occasionally there have been issues that will crop up that are usually resolved the next nightly (like earlier this week, a nightly caused the alarm app to FC whenever someone tried to set an alarm, this was resolved in the next release).
I usually stay behind on the releases, as I need my phone to be running and able to do the functions that I need. This way I can read what others are experiencing and see if it is worth upgrading to. Currently I am on #76 and I think #80 was just released.
Also, "stables" aren't always stables (which is the case in most programs). Just like with Windows, there are updates that need to be put out when security holes or major bugs are patched. But the smaller bugs will usually get fixed in the nightlies long before they ever make it to the stable.
Overall, I love the nightlies. I don't think I could go back to a stable build.
Click to expand...
Click to collapse
I just checked the website and for the nighty it has #81. I understand the part of updating at night. My question is like how u said that you are on #76, so do you have to manually change to #81(by flashing and making a backup) or it automatically updates? Am confused.
You manually update like you would a normal release of CyanogenMod. If you have the premium version of ROM Manager, it can notify you of new nightlies and you can download them through it. If you don't have it, you would manually have to download the files from http://mirror.teamdouche.net.
And I ALWAYS recommend making a backup. That way, if one of the nightlies you install is all screwed up, you just revert to the last one and wait until it is fixed bfore you flash the next verison.
You don't really have to wipe when going to the next nightly. Just flash and all your data is in tact, just like a regular upgrade.
I suggest going with the latest nightly.
I just purchased a Nook Color from Ebay, and after
I initially followed several posts about creating a bootable SD card to test an alternate OS. The instructions were straight forward, and I was able to quickly create a boot SD. I booted, and things worked, but because my several Kingston MicroSD cards obviously have poor throughput, the performance on the NC was excruciatingly slow and rife with Force Close errors.
So instead of dropping more cash on a more compatible SD card, I decided to just install directly to the EMMC.
I installed the CM9 nightly, (yes, I like living on the bleeding edge) and I must say that I'm impressed. It is a bit sluggish at times, and the touch screen response and accuracy could be better, but overall, I'm pleased. I may revert back to a stable version of CM7 just to compare performance, but until then, I'm quite happy with the results.
Oh, and I set up my DROID Bionic as a WiFi Hotspot, and the NC connects to the Internet without any issue. Very nice!
Sounds like you're doing well.
I was a long term CM7 Nook user and got good value out of that, but switched to CM9 a couple of weeks ago.
Yes, I have lost a few things and the performance / touch response was a little better, but I am sticking with CM9 as it is significantly nicer to use and improving all the time.
Make sure you are over-clocked to 1200 and using Interactive governor to get the best out of it.
CM9
I have tested several nightlies of MC9,I love it except for two big problems
1.Touchscreen is not very responsive
2.Streaming video like Hulu,Netflix,HBO Go and internet TV do not work
So I keep going back to CM7.
Have you also noticed that you sometimes have to touch above and to the right of an icon to get it to work correctly?
It drove me crazy until I figured that one out.
Wow! Those are the EXACT issues I ran into. And so I decided to go back to the stable release of CM7. Performance is like night and day. I can't believe how fast CM7 is in comparison to CM9.
My only real complaint of CM7 is that many apps don't recognize it as a "tablet" so apps tend to look like they do on my DROID Bionic, just in higher resolution. I'm not seeing many apps that display tablet-specific display elements. Not a big deal but kinda disappointing.
I'm not giving up on CM9, though. I may try the dailies every few weeks or so to see how things have improved.
I'm using the "official stable" release of CM7. Has anyone have any good experience with the recent MiRAGE CM7 releases? I tried one from a couple days ago, and had problems connecting to the Market.
I am have those issues as well. However, I am going to stick it a bit longer with cm9 as the nook is not my primary tablet.
Sent from my Xoom using xda premium
Jim Barr said:
Wow! Those are the EXACT issues I ran into. And so I decided to go back to the stable release of CM7. Performance is like night and day. I can't believe how fast CM7 is in comparison to CM9.
My only real complaint of CM7 is that many apps don't recognize it as a "tablet" so apps tend to look like they do on my DROID Bionic, just in higher resolution. I'm not seeing many apps that display tablet-specific display elements. Not a big deal but kinda disappointing.
I'm not giving up on CM9, though. I may try the dailies every few weeks or so to see how things have improved.
I'm using the "official stable" release of CM7. Has anyone have any good experience with the recent MiRAGE CM7 releases? I tried one from a couple days ago, and had problems connecting to the Market.
Click to expand...
Click to collapse
I LOVE Mirage! It is so much faster than stock CM7.1.
FWIW CM9 seemed sluggish om my OC'd NC until I accidentally forced another reboot by running the battery down. The animations seemed smoother after that. It may just be perception though, as I wasn't really looking for it.
Installing using ROM Manager?
HI all,
I downloaded the CM9 nightly to update my Nook Color, which is currently running one of the CM7 nightlies, but an a little unsure on how to actually it. Are you using ROM Manager to install the updated ROM?
Currently running Rom Manager 5.0.0.6, which has Clockworks Mod Recovery 3.2.0.1 flashed.
And correct me if I'm wrong. This does include a kernel, right? I'm assuming I cannot run the 2.6.32.9 kernel I'm currently using in CM7 with this.
Later,
Robert
Which kernel you are going to use depending which cm9 build you downloaded. There are several modded versions of that kernel out there, and including the open-go drivers or not, etc. Every ROM will contain and run a kernel, and so it is automatically depending on which Cm9 ROM you choose. I believe that every build posted within the last three days or so obtains the newest modded kernel containing the experimental drivers and the patch that fixes the formerly prevalent SODs.
Since you have flashed the current stable CWR, I would flash through the CWR menu. Reboot into recovery, and make a backup. Wipe data, cache, dalvik and then choose zip on sdcard, and choosing your preferred cm9 build. Should be all set. Most flats the builds are basically great, but but if the nook isbyour primary tablet, and you may be glad you have a backup of your current cm7, as some bugs can make it hard to run the ROM daily. Battery issues and some laginess has been reported.
Cm9 seems to improve on an almost daily basis, so if you intend to switch permanently, you will probably want to reflashed to current build every several days. Once you have flashed the cm9 build, upgrading to a newer build only requires wiping cache and dalvik, and which is pretty easy and keeps your settings and data intact throughout. These builds are functional, and but meantnfor those who want tontry the most experimental ROMs and are willing to dream with the bugs and want to reflash the newest builds as they arrive.
Hi,
On a Nook HD+ 32GB CM10.1 (6/15) on emmc. I am getting random reboots, perhaps once or twice a day. Is this normal ?
Thanks
I ran that build for about 1 week and had 2 or 3 random reboots total. I am currently running killersloth's Carbon ROM for about 24 hours, and so far no reboots. Not a lot of data to go off yet. The devs are doing awesome and I can only think (hope) it will continue since there are so many Nooks flooding the market right now
I've had quite many android devices (all on customROMs), so I've seen many unexpected reboots.
But no reboot is considered normal.
I flashed the same ROM on six different HD+ (all 16GB, from 5 different stores. Three are mine and other three are for my friends).
I've never seen (or heard complains about) an unexpected reboot.
For my own HD+, I tried CARBON B1/B2 and now back to latest CM10.1 and still haven't seen a reboot.
Maybe some app you're running ?
Usually caused by being overburdened, out of memory. Unfortunately most people report this as "random"
I haven't experienced an unexpected reboot on the HD with verygreens cm10.1 or with my carbon build. However I never keep going if the device becomes sluggish, I let it finish whatever task I told it to do that's using up all the available memory.
Sent from my Galaxy Nexus using xda premium
I've actually switched from CM10.1 EMMC (last build I tried was early August) to CarbonRom (B11).
I don't know if my Nook HD+ was over burdened, but I've seen it charging on my desk and it decides to reboot. I started "tracking" the reboots and noticed that they happened fairly often (once a day or more some times). I'd open Chrome and Nook reader just so they would show up in my recent apps menu. Then I'd leave it and check it later, sometimes the recent apps would be empty which means at some point the tablet rebooted.
Regardless, Carbonrom works well for me since I'm not usually doing anything critical with my tablet just email, web browsing, and reading.
Occasionally I'll bust out FreeCell or Trapped as far as games go. The best part is that I'm not getting the reboots.
Not sure what was happening with CM10.1, but I'll probably give it a shot again when 10.2 isn't experimental because I do like the Trebuchet launcher (which I can put on carbon, but Trebuchet crashes when I try to change the number of screens and a few other settings).
My Nook also randomly reboots. Just lying on the table without me touching it, or when I read comics or surf the web. It does seem *completely* random. I am beginning to think it is a hardware issue B&N cannot fix.
I was using EMMC Carbon B11 for a time in my HD+ because it offered the Tablet UI among other features. I also experienced occasional unexpected reboots while using that ROM but their low rate was nothing that made the ROM unusable. A few weeks ago I switched from B11 to a 4.3 EMMC ROM from iamafanof that also offers the Tablet UI and seems in my experience so far to have noticeably fewer unexpected reboots or restarts. For anyone who is experiencing "excessive" reboot rates using another ROM, iamafanof's 4.3 ROM might be worth a try. He also has a 4.3 ROM for the Nook Tablet. His ROMs can be found at his WordPress.com page.
Hi All,
I was experiencing random reboot issue on my Nook HD+ for a long time.
Only thing that helped is rooting my device and installation of CPU with max frequency 1300 MHz. I haven't noticed degradation of performance but reboots went away.
I assume root cause was CPU overheating
Hope this will be useful for someone
Hi,
I have a NOOK HD+ (with CM 10.2 stable), my device reboot very very often, i don't think it is normal and would like if a expert check my last_kmsg.dat and tell me what is going wrong on my device.
I also set my CPU @1300MHz to avoid overheating but it doesn't helped
thanks in advance
btw. I don't use a SDCard
wahidx said:
Hi,
I have a NOOK HD+ (with CM 10.2 stable), my device reboot very very often, i don't think it is normal and would like if a expert check my last_kmsg.dat and tell me what is going wrong on my device.
I also set my CPU @1300MHz to avoid overheating but it doesn't helped
thanks in advance
btw. I don't use a SDCard
Click to expand...
Click to collapse
Yes. I was seeing this one a lot on CM10.1.3. Definite kernel bug.
I made some kernel changes to /drivers/mmc and haven't seen it since.
If you want to try it, check out my 'overclock omap4470' thread (use one of the last two kernels; I made the touchscreen I2C fixes and mmc fixes at the same time).
FWIW this morning I had a random reboot with ABE Power Management (first reboot in awhile though). So I'm trying to chase that one down.
Edit:
Also here's an example of omap thermal opp throttling.
http://pastebin.com/gA2vFt1e
(this was before I reduced the voltages)
Jon Lee said:
Yes. I was seeing this one a lot on CM10.1.3. Definite kernel bug.
I made some kernel changes to /drivers/mmc and haven't seen it since.
If you want to try it, check out my 'overclock omap4470' thread (use one of the last two kernels; I made the touchscreen I2C fixes and mmc fixes at the same time).
FWIW this morning I had a random reboot with ABE Power Management (first reboot in awhile though). So I'm trying to chase that one down.
Click to expand...
Click to collapse
Thx Jon for replay, i will try that and report how that gone
btw. can i use your kernel with CM10.2 or should i downgrade to CM 10.1.3 first?