I have done my NC and a couple of others, here are the steps I am using for IMHO the ultimate NC setup, FYI. This guide is adapted from the guide posted for installing CM7 http://forum.xda-developers.com/showthread.php?t=1030227 with many of my own extra steps. I recommend reading the original guide first.
I get an average of >12 hours battery life with very stable performance with these settings on my NC.
In short, this is how I think the Nook Color should have been done from the beginning. I have attempted to balance some goals that are pretty common to other users. This guide walks you through steps that will accomplish all of these goals, but you may decide to keep some and skip others.
Here is what this will do:
Root your Nook Color and put a variant of CM7 ROM on it. This is an "AOSP", or "generic Android" installation. Nook Color comes standard with Android under the covers of B&N's launcher and suite of apps. Many of the tweaks and advantages in this guide cannot be had without first abandoning B&N's standard OS in favor of CM7.
Enhance performance by overclocking. The Nook Color is 800MHz max clock rate from the factory, and this guide will allow it to run at 1.2GHz (50% faster), along with tweaking the governor settings to ensure you do not sacrifice battery life.
Improve battery life. My goal was to have a device that I can use on flights between Austin, TX and Europe to read books or watch movies without access to a power outlet. I believe I have achieved that goal.
Enhance stability. While many ROMs (such as the new ICS work) may favor bells & whistles and tinkering over stability, I want my device to be rock solid and never, ever crash. The goal here is a device that *just works*, much like Apple devices are known to *just work*.
Smooth and responsive UI. One common complaint of Android devices vs. Apple stuff is on smoothness and responsiveness of the UI, in particular scrolling, screen switching, etc. Glitchy or erratic movements, abrupt or stuttery scrolling, etc. all gives a feeling of poor quality or lack of "polish" IMHO, and I have made an effort to fix this flaw in Android on the NC, mostly because the hacky feel distracts from my enjoyment of the device.
Flexibility and efficient use of storage. My guide will swap the /emmc and /sdcard mountpoints as well as repartition the internal memory of the NC, with the goal of efficiently utilizing the internal storage space, and allowing the SD card to be used in a more portable fashion, not required for operation but interchangeable. Mostly this is because for me, I have a LOT of music and limited space on my 32GB SD card for other media. But on long trips, I may want to bring along movies to watch and they are far more portable when put on tiny microSD cards. So I want to be able to change SD cards and change the media content on my NC, without having to reboot or lose access to some apps.
NOTE
These instructions will root your device and install a variant of CM7 onto your Nook Color in the internal memory, EMMC. This will destroy the original (stock) Operating System and you will lose whatever you had in your Nook Color before the install. It is destructive and likely difficult to reverse. If you have reservations about changing it or wish to change back, don't use these instructions. Try someone else's less-permanent means of doing so. You may screw up a step or I may have missed something, or your NC may not respond like I expect, so if you brick your Nook, then you are on your own. There is no warranty included with these instructions.
These instructions are for those of you who want a smooth, fast and stable NC Android experience, with exceptional battery life as well as efficient usage of internal and external storage. IMHO, this is how they should have done it from the factory. Someone else likely figured out a better way, but this is my way, and it works for me. You do this at your own risk.
This is not for those of you who want the Barnes & Noble experience. And this is certainly not for those of you who are on the fence about whether to re-flash. As far as I know, there is no going back, or if there is, it probably is hard to do. I don't know, because I never considered it.
There. Now you're on your own
Also NOTE
I am not the developer of the ROMs, image files, tools for repartitioning, or any of the other stuff mentioned here. I simply am noting my method for doing the installation and settings. Full credit and thanks are due to all of the original developers of this content.
mr72's setup guide:
Power up your brand new Nook Color and register the device. Note: I have seen a few refurb NCs that needed to be returned... don't skip registering it! Might save you some heartache.
You will need two SD cards: the "boot SD", which will be used to install clockworkmod, the OS, and google apps; a "data SD" which will be used to install the repartitioning scripts and then can be used for data storage. You can use the same SD card for both, but you may want to reformat it after using it to install the OS. IMHO, 1G and 2G microSD cards are cheap and it makes sense to make the "boot SD" on one of these and keep it around for recovery, using a much larger microSD (16GB or 32GB) for data storage later.
Use Win32DiskImager to write the 1gb_clockwork-3.2.0.1-eyeballer.zip image to the boot SD. You must run Win32DiskImager as administrator!
Copy the following files to the "boot SD" which you prepared with Win32DiskImager (Note: do not unzip them.):
A. The CM7.20 Stable ROM
B. gapps-gb-20110828-signed.zip
Copy the following files to the "data SD" card (Note: don't unzip these either.):
reformatData-v1.zip
repartition2GBdata-v1.zip
Power off your Nook. Put the "boot SD" card in (the one with the 1gb_clockwork image), and then power it back on. It should boot into ClockworkMod Recovery ("CWM").
Navigate in CWM using the volume up/down keys to go up and down, N button to accept, power button to go back.
Optional: Now is a good time to back up the factory OS. Use "Backup" from the ClockworkMod menu.
Go back and navigate to "Install .zip from sdcard", then "Choose .zip"
Flash the files in this order:
1. update-cm-7.1.0-encore-signed.zip
2. gapps-gb-20110828-signed.zip
Once you've flashed the files, in the ClockworkMod main menu select "wipe data/factory reset"
Go back to the main menu, remove the "boot SD" card and put in your data SD card. Choose "Reboot system now", which should boot into CyanogenMod (CM7). Note, it requires an SD card to boot at this time.
Once you boot into CM7, you must add your Google account, which will require wifi access. You can set up wifi by using the menu on the status bar. It may be kind of tricky to set up the wifi and get through the wizard. But it will eventually work.
Go to the market and search for "ROM Manager", and install the latest version.
Then just open up Rom Manager from the app drawer and hit "Flash ClockworkMod Recovery" and choose "Nook Color". It's on the list, even though the list may not be in any discernible order.
Optional: While in the market, you probably want "ES File Explorer", makes life easier when trying to navigate files.
Reboot into recovery, and back up the current ROM. Seriously, now make a backup. This is a basic starting point before you add apps and do a lot of tricky stuff, so this is an excellent place to make a backup that may save you later.
Install the reformat/repartition using precise instructions in this thread
Follow the instructions to use custom 1.96GB "/data", 4+GB "/media" partitioning to the precise detail.
This process is destructive and may feel quite risky. I suppose it is! So be careful and don't make a mistake here. It is worth it. By repartitioning you will wind up with 2GB of space for apps (vs. 1GB stock) and the other 4GB is usable as temp storage (like an SD card). This will also allow you to run your Nook Color with no SD card installed, plus hot-swap SD cards with no effect on running apps.
Now, back to Menu -> Settings -> CyanogenMod Settings
Application
- uncheck "Allow application moving"
- Install location: "Internal"
- check "Use internal storage"
- uncheck "Permission management"Note: This will cause the SD card to be mounted at /emmc and the internal 4G partition will be mounted at /sdcard. The result of this is your actual SD card does not have to be installed in order for the NC to work, apps that require /sdcard for storage will use the internal memory. This also means your SD card can be "clean", with only media on it, and interchangeable so you can have more than one SD card with content. The 2GB partition will be used for apps. You will have a hard time running out of application storage space with 2GB.
If you didn't repartition, then you will have 5GB for apps and only 1GB will be used for /sdcard stuff, which IMHO, is too little space for the /sdcard temp/settings storage, and way more than you can ever use for apps (certainly if your apps require sdcard space). So the repartition is IMHO necessary to make the sd/emmc swap feasible.
Install the V6 Supercharger script, update 8. Download it and use ES File Explorer or other tool to move it to the root level of the SD card partition (/mnt/sdcard). You will have to run the script in Terminal Emulator with the following commands:
su
cd /mnt/sdcard
sh V*
0
9
16 Note: this changes the way apps' memory is managed and results in more available memory for the active app more often. This makes things faster. However, you may find that it winds up killing background apps more frequently, so there is a tradeoff. So if you pause your Angry Birds game and go do web surfing for a couple of hours, Angry Birds may have to restart when you return to it rather than staying in memory the whole time. FYI.
Also Note: There are some other tweaks floating around that are said to improve performance; in my observation, they do not really improve it, and they are not necessarily persistent across boots. The V6 Supercharger does the trick, and doesn't require anything else to get the job done, IMHO.
Some performance tweaks, if you want iPad-like scrolling and smoothness and 12+ hours of battery:
Menu -> Settings -> CyanogenMod Settings
Performance (say OK to the "Dragons ahead" warning)
- CPU Settings
- Governor: InteractiveX, min 300, max 1200, set on boot checked. Note: the Conservative governor may result in better battery life, InteractiveX will result in a more responsive device. I switch between the two depending on whether I need long battery life, such as on a long flight where I plan to read or watch movies. - Use JIT - checked
- Enable surface dithering - checked
- Use 16bit transparency - checked
- Allow purging of assets - checked
- Lock home in memory - checked
- Lock messaging app in memory - unchecked (there is no messaging on a NC) You will have to reboot for these to take effect.
Undervolt/Frequency settings (this improves battery):
Run the Nook Tweaks app
CPU Settings
Clock Settings
CPU Stepping 1: 350mhz
CPU Stepping 2: 600mhz
CPU Stepping 3: 800mhz
CPU Stepping 4: 1000mhz
CPU Stepping 5: 1200mhz
Set on boot: Checked Voltage Settings
Stepping 1: 0.925v
Stepping 2: 1.05v
Stepping 3: 1.2v
Stepping 4: 1.275v
Stepping 5: 1.325v
Note: you can set the CPU minimum to 300 MHz to eek out a tiny bit more battery but when I do this, I get occasional SOD that are alleviated completely by using 350 MHz min.
I continue to update this whenever I have something meaningful to report. The truth is that for months now I have just basically been using my Nook Color regularly with no problems whatsoever, so this doesn't really require regular attention. Once ICS is fully-baked, I am sure I will come up with an alternative using ICS. For now, this setup appears to be rocking.
With this setup, with wifi disabled I achieved over 17 hours of battery life while reading ebooks with Moon+ Reader and the screen on (not night mode, this is white background, black text, and brightness about 10%). I also got about 10 hours of battery while watching movies. I think this is pretty great battery performance.
UPDATES CM10!
I have completed my experiments with CM10 and CM10.1 and (drum roll!)... they are not good choices IMHO for NC.
Battery life was about 1/2 on CM10 or CM10.1 what it was with CM7.20 and performance was very sluggish. Web browsing in particular is almost useless. I found I ONLY used my NC for reading books (since Moon+ Reader worked just fine) and I seriously hated having to use it for anything else.
The battery would not last throughout one overseas flight just reading books.
Just not nearly enough battery and performance for me, and while I like some of the UI enhancements (and particularly the ability to use Chrome browser) with CM10/10.1, they were in no way worth the extreme tradeoff in performance.
In the meantime I also dropped my NC and crunched the corner on it, so while it works, it does need to be replaced.
So, back to CM7.20 for me on the NC. I'm actually following my own guide right now to get it rebuilt the way it was. I'll be shopping for a new tablet to get maybe this summer that will run CM10+ with performance like I was getting from my lowly NC. Long live CM7.20 on NC!
Great!
It's very detail but some miss
If you put all 4 .zip files into ONE bootable CwMR uSD, step 9 you remove the uSD, insert the new one in, assuming it is blank then jump to step 14, you wont have the format file if you not re-insert the first usd back.
Also, flashing CwM into eMMC very convenience, yes, but it is a pain if you want to go back to stock ROM. I always preferred boot into CwM R via a bootable uSD card.
Your note in step 15, I personally do not believe it is 100% true. In my case, without an external uSD card plugged in, Aldiko Reader won't work. And yes, my system set up is like what you said.
votinh said:
Great!
It's very detail but some miss
Click to expand...
Click to collapse
Thanks, I updated it. Maybe didn't catch everything.
Also, flashing CwM into eMMC very convenience, yes, but it is a pain if you want to go back to stock ROM.
Click to expand...
Click to collapse
IMHO, if you have reservations and think you might want to go back to the stock ROM, then my instructions above are not for you.
Your note in step 15, I personally do not believe it is 100% true. In my case, without an external uSD card plugged in, Aldiko Reader won't work. And yes, my system set up is like what you said.
Click to expand...
Click to collapse
I have not tried Aldiko but I have probably 100 other apps and none of them require the SD to be installed. IIRC Aldiko does require you to tell it where the library is located; maybe this is the problem? I don't remember.
I switched to Moon+ Reader for my books, which I wholeheartedly recommend over Aldiko. I found Aldiko was crashing and causing my whole NC to crash/spontaneously reboot, etc., when you leave it running in the background for a long time. I think Aldiko likely has a memory leak.
While I am talking about app recommendations, I also suggested Go Launcher EX, which I really like. It feels faster and is more configurable in ways that improve responsiveness for my tastes compared to ADW. I have some theme preferences that I could share, which I think are optimal for the NC given the screen size, but I have found that most other people I know who are over 30 tend to think my settings for screen sizes of icons and controls are too small, so I didn't bother. Normal Tablet Tweaks and the default CM7 setup may be ok for you. I do prefer Dolphin HD browser over the stock browser, and I also tried Maxthon, Firefox Mobile, and Opera Mobile as well as Opera Mini. I like features of all of them, but on balance Dolphin HD is the winner.
votinh said:
Also, flashing CwM into eMMC very convenience, yes, but it is a pain if you want to go back to stock ROM. I always preferred boot into CwM R via a bootable uSD card.
Click to expand...
Click to collapse
I've tried a few of the new posts about returning to stock ROM and found it was really easy myself. YMMV
Thanks for the guide mr72.
The one thing I'd recommend to people who haven't done the cpu frequency / voltage tweaks before is to set it and test it out for a while without making it set on boot. The frequency settings are quite safe / standard, but the voltage settings vary a little more from person to person. If you've used it that way for a few hours without issue, then make it set on reboot.
insz said:
Thanks for the guide mr72.
The one thing I'd recommend to people who haven't done the cpu frequency / voltage tweaks before is to set it and test it out for a while without making it set on boot. The frequency settings are quite safe / standard, but the voltage settings vary a little more from person to person. If you've used it that way for a few hours without issue, then make it set on reboot.
Click to expand...
Click to collapse
Good point.
Also note, my settings are quite conservative. I have run them much lower and the NC was still stable, for at least a few hours. However, I figured I'd err on the side of stability.
Also note the impact screen brightness will have on battery life. While it may be second nature for some of us to turn down the brightness we might want to point out that it is the single biggest drain on the battery,
--------------------------------
Sent from the Center of my Mind
Nice work! I just updated Nook Tweaks with those settings. I updated to the SKANG RC-2 Mirage and so far the Nook is much speedier than stock CM7 RC1.
Will post back after I test these settings a bit.
MISRy said:
Also note the impact screen brightness will have on battery life.
Click to expand...
Click to collapse
That's true. Mine is normally about 40%. However, in my e-reader app (Moon+) I tend to adjust it to about 15-20% when reading with the lights on, and about 6% when reading in the dark. But the whole screen is mostly white so this is really a worst-case battery drain app for screen usage.
I managed to watch HD movies with wifi enabled but not streaming for 7 hours and the battery was maybe 30% afterward. So I think it has 10 hours of movies in it. With wifi disabled, it is better.
mr72 said:
I have not tried Aldiko but I have probably 100 other apps and none of them require the SD to be installed. IIRC Aldiko does require you to tell it where the library is located; maybe this is the problem? I don't remember.
Click to expand...
Click to collapse
Back to your "previously step 15", which probably a step 17 now, external uSD related. I just glanced through one of my previous post that talking about the requirement of an external uSD.
Can you do a quick test? Remove uSD off your NC, then capture the screenshot using the built-in feature (press and hold power button to bring up the menu).
See if it let you save the image or not.
votinh said:
Back to your "previously step 15", which probably a step 17 now, external uSD related. I just glanced through one of my previous post that talking about the requirement of an external uSD.
Can you do a quick test? Remove uSD off your NC, then capture the screenshot using the built-in feature (press and hold power button to bring up the menu).
See if it let you save the image or not.
Click to expand...
Click to collapse
Next time I have my SD card removed, I can try that. I'm not going to do it today. But trust me, it works just fine. The Android OS doesn't know there is no physical SD. You just have to make sure the internal partition is mounted at /sdcard. No part of Android OS can write to the partition without going through that mountpoint.
http://forum.xda-developers.com/showthread.php?t=1030227
Nice re-iteration of eyeballers thread..
Although I didn't use this post to setup my nook. It confirms some things. Also it said in the op and even links to eyeballers thread that this is how mr72's setup went and how he used settings to optimize his nook. I kinda like having the changes in one place.
khaytsus said:
http://forum.xda-developers.com/showthread.php?t=1030227
Nice re-iteration of eyeballers thread..
Click to expand...
Click to collapse
Sent from my NookColor
I've seen votinh talk about not wanting to install CWR to emmc, and have wondered why. I kinda just assumed it was some ethical dilemma concerning the warranty. It is pretty easy to wipe, in my experience at least.
One note to mr72. The V6 supercharger script is used to change the minfree values, and locking home in memory can conflict with its operation and cause lag. If you run the script in a terminal you can see it explained right beneath the script’s 17 option menu.
Just a note.
mateorod said:
I've seen votinh talk about not wanting to install CWR to emmc, and have wondered why. I kinda just assumed it was some ethical dilemma concerning the warranty. It is pretty easy to wipe, in my experience at least.
Click to expand...
Click to collapse
Maybe because I'm a bit of paranoid but since joining the forum and helping others, the most itchy issue that I've seen so far is restoring back to stock and a lot of people suffering the hiccup due to CwMR flashed into eMMC using ROM Manager.
In order to get out of it, they have to perform 8-boot ??? or whatever it is.
While w/o CwMR installed in eMMC, restore back to stock is just simply as re-flash a ROM.
Again, NOT ALL people hit the head-scratching issue but some did.
hhmm ... I wonder how this setup would work on ICS?
Once we get fully-functional, stable builds of ICS then I am sure I will do the same kinds of experiments as I have with CM7+ and wind up with a similar set of recommended tweaks and settings, if I have success running ICS and don't go back.
FYI, regarding battery life:
I got a PM asking for a little more detail. I am getting >12 hours of battery with the screen on while reading ebooks. This was on a series of flights overseas wherein I used the NC with Moon+ Reader, and wifi disabled.
I just got finished watching a movie for pretty much right at an hour, with wifi enabled, here at my house. MX Video Player, a DVD-rip of a movie, with the brightness on about "3" (set on MX Player). Battery went from 91% when I started to 80%. If it is linear, that's 9 hours of battery watching movies.
IMHO, this is pretty great. And it matches my rough experience from the previous experience watching movies.
Of note:
in MX Player, XviD movies play far better and consume less battery than x264. I got more like 15% per hour with x264 (BRrip, 720p) and frequently had to resync the audio and video. And also I have switched to the InteractiveX frequency scheduling, using the "SW Fast" decoder for MX Video Player, as an experiment to see if it improves video playback (it doesn't). But it doesn't seem to adversely affect battery life.
@mr72
I've been using Go Lancher EX on my CM7.2 NC (and Galaxy S2) and prefer it to AWD EX's features and performance. You mentioned earlier that you had some GO-specific tweaks that you'd be willing to share. I'd love to see how they compare with mine if you're still willing.
Thanks!
I just installed to and am running CM 7.2 from an SD card. Last night I full charged and today I noticed that my battery says that its at 15%, but the voltage is at 3693 mV. I know the max charge is around ~4200 mV, so the percentage seems very low considering the voltage value. Anyone help?
Related
I have the CyanogenMod and It comes with 5 screens but I cant use advantange of it because my phone gets so slow.. I use like 5 widgets and everytime I go to my home its frozen for like 10 seconds untill eveything is loaded again. I have apps2sd so im wondering is their a way to make the G1 lightning fast because its acting so slow it was like this in the stock rom also
What 5 widgets? Have you experimented with disabling them? What other apps do you have installed? Some wait in the background and use up memory / CPU. CM is pretty much the fastest ROM, so you need to look at the apps if things are slow.
You can also try the links in my sig for info on using compcache or swap to reduce the delays when you switch back home or in and out of the browser.
Well I have the free weather widget, retro time, retro date, and a battery widget and a few other application shortcuts on the home screen and it still lags when I go to home and its always like this and what does a swaper do?
blackfire1 said:
Well I have the free weather widget, retro time, retro date, and a battery widget and a few other application shortcuts on the home screen and it still lags when I go to home and its always like this and what does a swaper do?
Click to expand...
Click to collapse
I would activate your linux-swap partition or use the compcache userinit.sh. I wouldn't use swapper, its out-dated.
Basically what swapper (and linux-swap) is, is like creating extra memory for your phone to use, but places it on the sdcard. The increased memory allows for you phone to do more at once without having to constantly close programs left and right, speeding it up. But, the constant read/write of the sdcard wears it down quicker (don't worry, you'll still get about 2yrs of life out of that sdcard) and can become slow if it is writing/reading to the memory at the same time is it reading an app or file from the sdcard. Not noticeably slower, but slower nonetheless.
Compcache is a better solution IMO (its the new thing haha). What happens is that whatever RAM stores is compressed instead. Because its compressed, you can store more stuff on it. so like 24MB of RAM would be extended to 72MB of RAM and then you wouldn't have to read/write to the sdcard so often, saving its life and allowing for a small speed boost compared to a swap file.
There are threads on how to do both of these things in the development thread. The compcache is pretty easy, all you have to do is copy userinit.sh to your /system/sd/ and your pretty much done. Linux-swap requires you to create a 3rd partition in addition to the FAT32 and ext2/3. A little extra work, but well worth it. Most ROMs will automatically activate the linux-swap partition if you have it.
Note: Compcache can also use linux-swap as a backup, allowing for an even faster phone. I'm using jacHEROskiv1.4C_a2sd and it works pretty fast IMO. Certainly not as fast as Cyanogen's but fast enough for day-to-day use.
If you really really really really, don't want to mess with any of that, I would just use swapper. Its like linux-swap (follows the same principle), but its not as fast. If you do choose to use this solution, make sure you place the swapfile on /system/sd/ so that when you mount your SD you won't mess up your phone.
Can you please show me a link of how to do the Compcache because ive searched and only found nothing yet.
blackfire1 said:
Can you please show me a link of how to do the Compcache because ive searched and only found nothing yet.
Click to expand...
Click to collapse
Link: http://forum.xda-developers.com/showthread.php?t=537236
Also, the command to include linux-swap as a backup (if you choose to) is on page 14, last post on the page. Good luck
Does having 5 home screens use more memory than the original 3?
slightly, but not enough to make the kind of differences that the OP is describing. I know cyanogen and dude's builds both have 5 home screens, not sure about the rest, but this is the first slowdown complaint I've really heard.
The two questions I would ask to the OP is this: 1. how many applications do you have installed? 2. What size and class SD card are you using?
Hopefully there is someone out there who is smart enough to fix my issue!
I have a htc G1 rooted running the latest Cyanogen rom and i have a SanDisk micor sdhc 8GB class 6 card. Ok my issue: It seems like for the past 5 or more roms that cyanogen has put out every now in then when i go from like say a game or contacts to the home screen it lags for say 5 sec. During this lag i notice that my icons are visible on the homescreen but the widgets are missing and i only have like 3 widgets on the screen. I dont know if my SD card has taken a crap or what? Please help
dasoccerbomb said:
Hopefully there is someone out there who is smart enough to fix my issue!
I have a htc G1 rooted running the latest Cyanogen rom and i have a SanDisk micor sdhc 8GB class 6 card. Ok my issue: It seems like for the past 5 or more roms that cyanogen has put out every now in then when i go from like say a game or contacts to the home screen it lags for say 5 sec. During this lag i notice that my icons are visible on the homescreen but the widgets are missing and i only have like 3 widgets on the screen. I dont know if my SD card has taken a crap or what? Please help
Click to expand...
Click to collapse
You were doing something that was memory intensive, gmaes (especially 3d) tend to do that. They used up too much memory sot the system pushed the home out of memory. When you go home that means it has to reload everything, hence the lag
JAguirre1231 said:
You were doing something that was memory intensive, games (especially 3d) tend to do that. They used up too much memory sot the system pushed the home out of memory. When you go home that means it has to reload everything, hence the lag
Click to expand...
Click to collapse
@ Op, if your playing a game on i dont know, Xbox or Ps3 when you exit wouldn't be slower then lets exiting the browser or being in a chat?
Similar on Pc, closing browser is quicker then exiting a game like crysis or maybe flashpoint.
JAguirre1231 said:
You were doing something that was memory intensive, gmaes (especially 3d) tend to do that. They used up too much memory sot the system pushed the home out of memory. When you go home that means it has to reload everything, hence the lag
Click to expand...
Click to collapse
But it seems like even just from bouncing back and forth from contacts every now and then it lags and when its lags the phone is basically frozen until it starts to respond again.... Is there anything i can try to counter this issue
dasoccerbomb said:
But it seems like even just from bouncing back and forth from contacts every now and then it lags and when its lags the phone is basically frozen until it starts to respond again.... Is there anything i can try to counter this issue
Click to expand...
Click to collapse
Are you using 10MB hacks?
No i am not
dasoccerbomb said:
No i am not
Click to expand...
Click to collapse
Well if you don't play to many 3d games, then I would suggest using it. It takes away from the graphics to add 7.5mb more of memory for apps
i once had this issue (slowness, lagging), and i did the following, now the device is zippier and faster than ever:
Decide to do a complete make-over (reflashing the ROM)
0. backup your apps & files, copy SD to harddrive, in order not to lose data
1. reboot into recovery screen, WIPE
2. flash the ROM, reboot, flash the theme you like (and that fits to the ROM), reboot, flash AdvancedLauncher 2.1 if you like (i use it for its certain functions), reboot
3. if you can live without 3D-games, you can use the 10MB RAM-hack; in terminal emulator flash RAM-Hack image (boot.img) (IMPORTANT: it needs to be the boot image that fits to your ROM!
3. reboot
4. reboot recovery; in console or adb shell: fix_permissions
5. reboot
6. install "user.conf Creator" app, READ THE INSTRUCTIONS (inside the app), open it and:
--> enable permission_fix
--> enable compcache (i use 64MB)
--> enable ccbackinswap (i use swappiness 50)
--> enable linux-swap (my linux-swap partition is 128MB; i use swappiness 50)
--> backup files
--> push files
--> reboot
(i experimented with different "swappiness" values, 50 worked out best for me, but it may be different for you. at swappiness 80 loading of apps is really fast, but scrolling and going back to home screen is really slow. 50 seems a good middle value.)
7. done
this can easily take up to 1 hour. After applying user.conf it may take a while on first reboot until the phone is fully loaded, but it's well worth the effort.
i also use SetCPU, to set CPU clock to 528/528 when charging, 384/245 when sleeping, and 128/128 when power <10%
good luck
I've seen some comparison made in threads, but most are partial, and while I've looked into Froyo quite a bit, and even made a hack at it, I haven't come to fully understand why I should. So I thought it might be helpful to have a Pro/Con differentiation between the two; why did you go through the effort to Froyo? Why didn't you? I know some have gone Froyo and then back to Eclair. I'll try to edit this post into a list once we have some good comparisons thrown out here.
Alright, after playing with the latest Froyo and looking at this thread so far, the tentative list for newbz0rz to consider is here.
The List:
Froyo 6.6
+Flash (!)
+Higher Benchmark scores, possibly faster in certain ways
+Higher compatibility with certain apps
+Potentially more configurable
+Cut and paste
+JIT compiler (potentially increases speed)
+Launchers behave properly (i.e. add shortcuts)
+Text-to-Speech
-Choppy Flash (!)
-More effort and time (lots more) to setup equivalently capable features
-Higher risk of Nook destruction (although still low)
-Higher risk of lots of work rescuing Nook from the grave/brickyard
-No Nook Color features (i.e. B&N apps, in store access, reader, magazines, etc)
-Buggy-ish sometimes (Unstable) :-(
*-Different users seem to report very different experiences; thus, we'll just call Froyo Inconsistent
-Ignores internal 5GB storage
-Ugly notification bar mis-sizing
1.1.0 Rooted
+Stability (Consistency in a stable experience, compared to Froyo)
+Some claim smoother overall
+B&N "experience" (FWIW)
+magazines, built-in reader for those who prefer it (hint: Aldiko is better)
+Status/Notification bar at bottom with back/menu keys
-Ye Olde Android 2.1
*-No JIT
*-No Flash
-Incompatible with shiny new 2.2+ apps (not very many of those, but still)
-Possibly slower, benchmarks lower
-Dialogs don't display correctly due to B&N system configuration
-Many alternative keyboards don't work properly
-No Cut and Paste
*Evernote was a dealbreaker for me, oddly enough. I use it all the time. Also, 6.6 Froyo broke my ADB somehow, and was a huge pain for very little gain. Gotta love Nandroid. 1.1.0 rooted does 95% of what I want, while Froyo does the 5% it can't do and breaks another 10% of what already worked. But that's just me. I can wait for CM7/ a more stable Froyo before I get flash. Honestly, what flash content do I want to watch on my tablet that I cant use my netbook/desktop for? I'll stop asking questions I don't want the answer to.
The biggest plus for froyo for me was flash content. The negative is Thai it is not as smooth as 1.1.
haven't tried 1.1 yet, but froyo+launcherPro+dolphin browser is as smooth as a phone. also, plus flash content
It really comes down to this:
Rooted 1.1.0 is for people who want to have the basic(older, no flash) tablet expirence, on a platorm which runs well and requires little to no cmd-line/linux/etc. knowledge.
Rooted 1.1.0 OC'ed to .950/1.0/1.1ghz only requires a couple hours of development forum reading, a little bravery, and a NC that can handle it.
Nookie Froyo 6.6 OC'ed to 1.0/1.1ghz ON SD CARD again, only forces you to read the respective threads(twice) and have an available micro SD card(at least class-4 4gb). This is a good method to start out with because if you mess it up, just reflash the SD card.
Nookie Froyo 6.6 OC'ed 1.1ghz INSTALLED TO EMMC is not over-the-top hard. It just requires a lot of dedicated hours understanding what exactly the flash images are doing to your device. Being comforable while working in cmd-prompt/linux/android-system is a must. Acceptance of the fact that, doing so *can* break your $250 toy.
knaries2000 said:
The biggest plus for froyo for me was flash content. The negative is Thai it is not as smooth as 1.1.
Click to expand...
Click to collapse
agreed Flash was upsetting otherwise i would of kept it as 1.1 right now i dual boot w/ 66 and 1.1 but using froyo i really only go back to read my magazine subscriptions, and i like the back and menu softkeys setup on the bottom in teh 1.1 not so much in froyo
woot1524 said:
It really comes down to this:
Nookie Froyo 6.6 OC'ed 1.1ghz INSTALLED TO EMMC is not over-the-top hard. It just requires a lot of dedicated hours understanding what exactly the flash images are doing to your device. Being comforable while working in cmd-prompt/linux/android-system is a must. Acceptance of the fact that, doing so *can* break your $250 toy.
Click to expand...
Click to collapse
I've yet to see anyone break their $250 doing so. (In fact I don't see how it could break it). Also it doesn't require being fluent in any of those. Can you copy and paste? Okay well then youre set. Also, with people posting builds coming preinstalled with needed apps makes even using the command prompt almost uneeded (the only thing that needs to be pushed is the market).
The real downside to froyo is the lack of the B&N soft-keys on the bottom, meaning there isn't always a back and menu button on screen.
To Sum:
Froyo = Lack of softkeys permanetly there
Eclair = Slower, Lack of Flash
I tried NF for a little bit. I still have the card sitting somewhere.
For some reason, I don't feel the need to get Froyo on here until I can easily flash it like any other Android device.
I seem to remember there were certain compatibility issues along with slower benchmark results on Froyo. Is this no longer true?
vapor63 said:
I seem to remember there were certain compatibility issues along with slower benchmark results on Froyo. Is this no longer true?
Click to expand...
Click to collapse
Not that I know of. Froyo Quadrant scores are a full 400 or so points above eclair.
I've got rooted/OC'd 1.1Ghz 1.1 on mine.
I don't feel the need to go to Froyo.
Once Honeycomb is perfected, though, I am SOOOOOOOO there.
MattJ951 said:
I've yet to see anyone break their $250 doing so. (In fact I don't see how it could break it). Also it doesn't require being fluent in any of those. Can you copy and paste? Okay well then youre set. Also, with people posting builds coming preinstalled with needed apps makes even using the command prompt almost uneeded (the only thing that needs to be pushed is the market).
The real downside to froyo is the lack of the B&N soft-keys on the bottom, meaning there isn't always a back and menu button on screen.
To Sum:
Froyo = Lack of softkeys permanetly there
Eclair = Slower, Lack of Flash
Click to expand...
Click to collapse
True, the chances of bricking the nook color are remote. But as you can see from the dev threads, even they have warnings. Because the odds dramaticaly increase when one starts messing with system and boot mounts, or over-clocking the hardware.
The reason why I stressed the understanding of what exactly your doing, when you flash the emmc or uImage, is there are many conflicting/confusing instructions involved If you take things verbatum from threads. I just don't think it's something a novice user should try at the moment. Especialy with the loss of the abilty to do a CWM recovery(I know about the sd images and swaping the cards out to do a backup, others don't, nor have more than one sd card)
Froyo does infact have Back and Menu buttons in the status bar.
you just need to push a couple files found in this thread: http://forum.xda-developers.com/showthread.php?t=932631
The real problem with nookie Froyo is that it's still not a daily driver. It's buggy(to an extent), it's always being updated(annoying, but part of the fun), and frankly 1.1.0 just runs better.
I am surprised that nobody bothered to mention that with Froyo, currently, you lose the ability to veiw kids picture books, newspapers, and magazines. If you care about any of that stuff, you have to stay with 1.1.0
waiting for guys at Cyanogen to release the nightlies for NC
i tried froyo last night since you can now flash through recovery.
it was a painless install but then i had to get adb running to install gapps and sdcard fix.
after running it for awhile it isn't bad but still not as smooth as 2.1. not sure why people are posting that its faster as it is not. it's little more choppy overall and has hardware acceleration problems when playing movies. as some have mentioned it is annoying not having the navigation buttons without the nook bottom bar.
i am also just waiting for cm7 and i'll say goodbye to eclair forever. it was a breeze restoring back to stock through recovery and will probably try the next update of froyo now that I know what I'm doing.
jblues1969 said:
I've got rooted/OC'd 1.1Ghz 1.1 on mine.
I don't feel the need to go to Froyo.
Once Honeycomb is perfected, though, I am SOOOOOOOO there.
Click to expand...
Click to collapse
This is my exact standpoint.
If a Honeycomb (That isn't just the SDK preview) is made for the NC, I will be downloading it.
So we've got a working list running for reference; I'm sure some people have more to add? This kind of thing would have saved me a lot of time a few months ago, let alone now with the increase in crazy options.
Thanks for this list, its awesome. It helps address the questions.
I am ofcourse going to try froyo since its so easy to do so but I wanted to help decide what was going to be my daily driver, etc.
CM7 is built on 2.3 AOSP right? I am excited to read above that nightlies are coming soon?!?!?
woot1524 said:
True, the chances of bricking the nook color are remote. But as you can see from the dev threads, even they have warnings.
Click to expand...
Click to collapse
The warning are there as a just in case. These roms won't short out any circuits (short of the Overclocking one) and are just standard warnings. Since the NC boots to the SD card first it shouldn't be bricked. In fact if you wish to claim it can brick it then I can equally make a claim nooter will.
woot1524 said:
(I know about the sd images and swaping the cards out to do a backup, others don't, nor have more than one sd card)
Click to expand...
Click to collapse
You don't need more than one sd card. I only have one and have successfully recovered when I was trying to do some edits myself.
woot1524 said:
Froyo does infact have Back and Menu buttons in the status bar.
you just need to push a couple files found in this thread: http://forum.xda-developers.com/showthread.php?t=932631
Click to expand...
Click to collapse
That is actually glitchy and if you read the developer even stated it himself later on. He said instead of releasing a custom ROM to fix the problems he'll just release the source code in case anyone really wants them
woot1524 said:
The real problem with nookie Froyo is that it's still not a daily driver. It's buggy(to an extent), it's always being updated(annoying, but part of the fun), and frankly 1.1.0 just runs better.
Click to expand...
Click to collapse
Eclair is buggy to an extent as well and on the issue of which runs better we'll have to agree to disagree since we can only have it based on opinion. Froyo has higher quadrant scores, and runs much smoother for me. As for compatability I'll test evernote later, but I dont know of any apps I've tested that don't work in froyo but do in eclair, while theres quite a few 2.2 exclusive apps that obviously won't work in eclair. But for those who can't get apps to work in 2.2 that did in 2.1 might be worth more than those 2.2 exclusives
In the end I would suggest just dual-booting Froyo and Eclair. Theres a simple download over the developers forum's that allows this. You just put it on an sd card, then type one line on your nook and you can test both of them and decide for yourself, while always having one for backup
How is the 1.1 g?
I feel quite the opposite, I think the B&N 2.1 experience is horrible.
B&N 2.1
- Dialogs don't display right due to B&N system configuration
- Keyboards don't work properly and if the keyboard does not have the settings in the UI there is now way to configure it due to B&N config
- No Cut and Paste. The work around are horrible.
- Default B&N Apps are horrible by far the worst apps in every field.
- System settings are non standard and accessing app configurations is very difficult.
- No JIT compiler causes apps to run slower.
- Launchers do not work properly because of missing
- No Text-to-speech.
- Random reboots multiple times a day.
- Games are sluggish, basic games are just fine.
Froyo 2.2 (0.5.8)
+ JIT compiler
+ Can get the nook 4 android app (which I think is better than their stock reader)
+ Cut-n-paste
+ Text-to-speech
+ More Stable( reboots on me twice a week)
+ Default Android back end so configuring keyboard apps and other apps is possible.
+ Launchers behave properly.
+ Access to more Market apps.
+ Game experience is much smoother(thanks to the JIT).
What bugs do you see on the Froyo that you don't see on the Stock nook. If anything I've seen more issues running stock nook than foryo?
I'm sure this has been asked and answered, but everything I find when I search for it is in regards to the Nook app in the Marketplace. If I root the stock ROM (not flash CM7), can I launch the Nook software that the Nook shipped with? I.e., instead of a dual boot, I'm launching the Nook software from the menu. I understand that I could install and use the Nook app from the Marketplace, but the native/stock software (I think) is nicer.
Ya the Nook would not be much different, you would just have super user privileges, as well as be able to run a custom kernal.
Sent from my MOTWX435KT using Tapatalk
Confirming you can run the Nook as before, with some minor changes to the launch menu.
As the previous poster indicated, you can also put a custom kernel that allows you to change the CPU speed and governor settings, and in general tweak the interface. Some annoyance with being pushed to the Nook menus (such as settings) means it is harder to find some of the other rooted facilities but I am sure there are other apps you can install to get some of that functionality.
I have the nook manualnooter'd and prefer using it simply for the apparent lag i get with the other SD card based options, but thats card speed, not having time to sift through the many ideas and solutions others have spent time on and just enjoying the basic interface as still an easier run for reading and minimal "other stuff". YMMV of course but i recommend it!
This is essentially the final thing I'm wondering in this Nook HD(+) development world. It seems that the two main options are opening up the stock Nook by enabling the Play store and all the benefits that go with that or CM10 which is essentially turning your Nook in to a Jellybean device.
For me, the clear winner is rooting Stock. For one, I have an HD which means 8gb of storage. I really don't want to tie up my Micro sd slot with an operating system. Also, it's nice to be able to get back to the Nook screen simply as I think its default library function is great for books.
I know CM10 is very popular, and since I am still figuring it out I'd love to hear which method people are using and why.
For me, so far, rooted is better. However, CM is quite feature rich, and once completely stable I suspect I might switch over. I'm interested in more file systems and overclocking for instance.
I've used both to date, and everything you can do on stock+ you can do in CM, except the built in reader (although the Play version is very close) and the app drawer widget. Profiles are nicely implemented on stock too, so that might be important for some family uses.
As for the internal memory, you can get to that now with CM10. And SD cards are fast enough you don't notice any lag. Also, with stock there's always the chance you'll bork something in /system and enter the bootloop issue without a CWM recovery nearby...
dbh369 said:
For me, so far, rooted is better. However, CM is quite feature rich, and once completely stable I suspect I might switch over. I'm interested in more file systems and overclocking for instance.
I've used both to date, and everything you can do on stock+ you can do in CM, except the built in reader (although the Play version is very close) and the app drawer widget. Profiles are nicely implemented on stock too, so that might be important for some family uses.
As for the internal memory, you can get to that now with CM10. And SD cards are fast enough you don't notice any lag. Also, with stock there's always the chance you'll bork something in /system and enter the bootloop issue without a CWM recovery nearby...
Click to expand...
Click to collapse
Great points all around. What do you mean that I can "get to internal memory on CM10"?
My goal would be to be able to use the portion of an SD card that's not tied up with CM10 as EXternal memory.
I haven't played much with CM10 as it runs poorly from my SD card.
One more thing to note, stock+ isn't recognized by android file manager. I'll have to see if CM10 is.
captainmccool said:
Great points all around. What do you mean that I can "get to internal memory on CM10"?
My goal would be to be able to use the portion of an SD card that's not tied up with CM10 as EXternal memory.
I haven't played much with CM10 as it runs poorly from my SD card.
One more thing to note, stock+ isn't recognized by android file manager. I'll have to see if CM10 is.
Click to expand...
Click to collapse
My take on the situation is that rooted stock is nice (ESP the reader app), but it will not run everything. One case in point, Google Voice. I use it for free texting over wifi. It will not run on rooted stock.
And what he meant about get into internal memory is the media partition (called sdcard in stock) shows up as emmc media storage in CM10.
And what you want is already implemented in CM10. It partitions what it does not need for itself to operate and makes it available for sdcard media. It usually reserves about 3GB for itself and makes the rest of the card available as media space for CM10 use. And it is possible to have stock see that too with the right modifications to stock configuration. But it does you no good since you cannot boot to stock with the CM10 SD in the slot anyway.
What is stock+ that you want recognized? And what is android file manager?
Sent from my Nook HD+ Running CM10 on SD
I have a short brief on CM10, and here is my take.
both:
have bugs, some apps working well on one but not another.
CM10:
More freedom, a lot more apps open up and works, and no need to worry about apps that mess with /system.
You lose some sd spaces, and inability to swap sd.
stock:
Required a lot of mod just to get 80-90% of what you can do with cm10
sd card swapable
doesn't work with cm10 sd card, I guess it can but you do need to mod.
Most of the pros and cons have been covered above and my experience is that both can get you to the features most important to you one way or another so it comes down to personal preferences and usage patterns.
For me, the difference came down to keeping stock clean and getting CM10 separate on an SD card. I can pop the SD card out and use my Nook in BN store or sell it without any issues. I did plenty of rooting and re-imaging on my Nook Color before this and I could never get it to a clean factory state again. Even when I cleaned everything and installed stock, Cyanogen logo would still show up on boot.
With my Nook HD I decided to keep the stock image clean.
I'd like to add on CM10, I haven't been able to transfer any programs to the internal sd. Used titanium backup and the os option for it. No go. If anyone knows a way let me know but I had an easier time installing everything with my rooted Nook HD than on CM10.
Diogenes5 said:
I'd like to add on CM10, I haven't been able to transfer any programs to the internal sd. Used titanium backup and the os option for it. No go. If anyone knows a way let me know but I had an easier time installing everything with my rooted Nook HD than on CM10.
Click to expand...
Click to collapse
I don't think that option is available for any device to move an app to internal SD. They always have to be an external SD (apps2SD). And you can install them to the external SD with CM10. So I don't know what you mean by easier on rooted stock.
Sent from my Nook HD+ Running CM10 on SD
leapinlar said:
I don't think that option is available for any device to move an app to internal SD. They always have to be an external SD (apps2SD). And you can install them to the external SD with CM10. So I don't know what you mean by easier on rooted stock.
Sent from my Nook HD+ Running CM10 on SD
Click to expand...
Click to collapse
I meant to external SD. I tried the moving to SD options on both titanium pro and within the is and it doesn't do it despite saying that it does. I am stuck on the 2gb partition that cm gives me.
Sent from my Barnes & Noble Nook HD using Tapatalk HD
Diogenes5 said:
I meant to external SD. I tried the moving to SD options on both titanium pro and within the is and it doesn't do it despite saying that it does. I am stuck on the 2gb partition that cm gives me.
Sent from my Barnes & Noble Nook HD using Tapatalk HD
Click to expand...
Click to collapse
How do you know it does not do it? Mine does. I used the settings/app to do it. They are no longer in /data/app they are in /mnt/asec which is the new way of storing on SD.
And 2GB is not enough? You must have a lot of very large apps.
Sent from my BNTV400 using Tapatalk
I'd go for rooting the stock. CM10 works great but its reader lacks the funtion of Nook's original. I read a lot of PDF textbooks and there's just no good PDF reader, yes, szpdf included that can render as fast and stably as Nook's, not to mention the built in dictionary function.
In my experience, the stock PDF reader falls way short in zooming department. If you use ezPDF, you can double tap the text and it zooms the text perfectly cutting off the margins. Stock does something random altogether. That is a small problem though. Bigger problem is that you have to repeat zooming on each page. ezPDF remembers your zoom and then you can easily go through the rest of your PDF at the same zoom setting. This allows me to read a lot of my PDF's in portrait mode. If you use landscape then you don't really need zooming but it does come in handy.
And for my PDF's I have not noticed a speed difference between stock and ezPDF.
Also, I did not know there was a dictionary in the stock PDF reader app. I will have to try it sometime.
Stock
stock is better in my opinion. I just bought a Nook HD like a week ago and compared to other android devices, it seems faster. I got it rooted and everything and i started thinking about CM 10. I have CM 10.1 on my Samsung Fascinate, and I love the features but its always got a very low battery life and I also did not know how to unbrick a Nook. I read many comments about CM 10/10.1 for Nook HD and the battery life was an issue. So in conclusion I decided to stay on stock with root and GApps and all.