Related
What is the advantage of using android 3.0 have over 2.2. and 2.3?
Install all three and really see no difference beside the slight UI changes.
evilPERSOn,
I had not yet loaded HC, so my advice is pure speculation. HC has an entirely different interface which acknowledges the fact that a tablet is in essence a tablet and not an oversized phone. So, as such, it works a bit more like a computer with. The speed and streamlined interface of a tablet. As I write this I really wonder why I have not cobbled it up. Well, it is only a matter of time.
Have fun
~Leko
evilPERSOn2009 said:
What is the advantage of using android 3.0 have over 2.2. and 2.3?
Install all three and really see no difference beside the slight UI changes.
Click to expand...
Click to collapse
well for starters this should be in general not development
second HC isnt just a slight UI change, it was MADE for tablets so if you want your tablet to be a giant itouch running android than install 2.2/2.3 but if you want a tablet you should install 3.0
^My bad. I had two tabs open. General and Development. Must have started thread on the wrong location.
1. HC uses GPU interface rendering.
2. HC is meant for a system like a nook with few buttons (good for us)
3.But HC's source is not in the open (bad for us).
poofyhairguy said:
1. HC uses GPU interface rendering.
2. HC is meant for a system like a nook with few buttons (good for us)
3.But HC's source is not in the open (bad for us).
Click to expand...
Click to collapse
Hopefully the source will be released soon!
For me i thought i would try hc on the sd card and just go back to froyo. I was hooked. I used it for two days on a class 2 card then i flashed, and ive tried to go back to froyo and get flash but i cant. The UI is just perfect, the live app switcher key is wonderful and so great to use, probably my favorite feature. Not to mention i love that the task bar is on the bottom, reminds me of windows and keeps the clock and keys out of my face. Honestly i hate the top notification bar on other versions, ive always hidden it on my droid. Being on the bottom is so nice and out of the way.
Its got its downsides, but give it 2 months.. apps galore, source files..... it will be really good to run.
Edit: not to mention, ive never lost data like on my droid while switching apps. Ive come back to apps ive had open for over 24hrs and its still in the same state
Sent from one of those missing Droids
altimax98 said:
The UI is just perfect, the live app switcher key is wonderful and so great to use, probably my favorite feature.
Click to expand...
Click to collapse
i'm using the samuelhaff's eMMC HC and i noticed that i can't scroll the app switcher, so i don't have access to all my previously run apps. is this normal?
loving HC, so far. the fact that it's designed for no hard buttons is just awesome.
i don't think the app switcher even scrolls on the xoom yet.
I have only played with HC breifly. But from what i know about it these are the following reasons to use it.
1. Market. Honeycomb is the first android os that will support having the google market. This provides a few things. Any of us who have played with Ipods and ipads will know that there are specific apps built for ipad. Now that Android 3.0 is built for tablet form factor, and officially supports the market. We will now see Tablet applicatons that provide higher resolutions, or new features. These apps will be built around the 3.0 os, and may not work on older operating systems.
2. Built for tablets. Everything we have had up untill this has been a phone operating systme built for a 3" screen ported to something with a 7-10" screen. The os is clearly built for phones there are things in there that just dont work right, or should not be there, but are there, on a fundimental level in the operating system. By adding native support for larger screens, and removing the phone items, it provides for a cleaner higher performance interface.
3. Interface enhancements. The UI has been built to support the larger form factor. This will provide easier navigation as well as soft keys as mentioned above, since alot of tablets are just missing physical buttons.
Unfortunatly the OS has not been released to the public. My guess is there is some contract between motorola (xoom) and google for exclusivity on their tablet. but dont quote me on that.
1) The web browser is much improved - even over Dolphin
2) The email client is much improved - even over K9
3) Contacts sync seamlessly with Google contacts
4) The keyboard is much improved - has a TAB key, has a "handle" to move the cursor around in text, has cut and paste features.
All of this is enough to make me swich to HC.
Downsides:
1) Many of my favorite apps cannot be found or downloaded from the Market - even though they worked fine on 2.1.
2) From uSD card, runs a little slower than 2.1, but not enough to bother me.
is the video accelerated? I could not take cm7..so slow.
winkler1b said:
is the video accelerated? I could not take cm7..so slow.
Click to expand...
Click to collapse
No. Same problem effects both I think.
Well, I switched and got my nook to recognize the sd (Class 2) partition. I expanded the image to use the 16 gigs too. I love it. The Live App switching is nice. It actually feels more like true Linux (I am thinking KDE) than any other droid system. I just can't handle the lag when booting apps (probably a combination preview/sd card). I am a teacher and grade on my Nook, so I need speed. But, I am excited about this. Thanks a lot Deeper Blue. This will be stellar.
The true app switching is almost priceless as is the efortless interface.
~Leko
I'm looking for a fast ROM, battery is not so important, with JIT compiling that's stable....anything anyone can suggest?
Currently using Super AOSP (using it now, some apps don't run, otherwise stable). Radio=27.08, Haykuro SPL....
Most of the loads I've tried are either buggy or I can't load them for one reason or another (A lot of roms fail during load - is that my phone?)
I don't need a lot of bells and whistles, I do EMAIL, I do Web Surf and play an occasional game, but I don't really need lots of other things, I would gladly give up visuals for some increased speed - currently 2.6 MFLOPS (Linpack free).
Thanks.
best I can do for now....4 MFLOPS on G1
I think I found the best for me right now, Ginger Yoshi gives me 4 MFLOPS, which is not as good as I wanted, but I've set my sites lower.
It is very smooth - it does not feel refined, don't need it, everything works.
I can recommend SuperAosp, it is very refined, everything looks finished. It is not nearly as fast as Ginger Yoshi, but it is pretty and stable.
I did try several other loads, and I'm thankful that there are developers out ther, so I won't mention names, but at least one of these loads gets a lot of press on here and on my phone, I'd call it buggy.
Super Aosp and Ginger Yoshi are both stable.
It sounds funny, but try turning off JIT. It seems to make roms a lot more stable; I'd guess the G1 just isn't up to snuff for JIT. It makes benchmarks lower, but in practice it works much smoother.
Thanks for the reply!
I am turning off JIT...Then let the phone sit for a couple of mins to finish any housekeeping.
Ginger-Yoshi
JIT = Yes, Speed = 4.1 MFLOPS
JIT = No, Speed = 2.45 MFLOPS
Odd note, one of my non JIT runs ran at 1.6 MFLOPS, I didn't count it since it was so far out, not sure if there was housekeeping going on or what.
Second note, disabling JIT did make installations more stable - I was unable to install and sometimes download a specific application, disabling JIT allowed it to D/L and install.
Super-AOSP
JIT = Yes, Speed = 2.6 MFLOPS
1.6 Google - Rooted, speed to 528 MHz
2.4 MFLOPS
1.6 Google stock
1.4 MFLOPS
I've never run 2.0 or 2.1 so I don't know how they stack up, they do not have JIT, so maybe they are more efficient.
What I really wanted was a 1.6 OS with everything moved to the SD card AND JIT and CPU set to 528 MHz otherwise stock, I expect that is about as fast as this phone can go.
My limited experience:
I can't speak for anyone else but Super-Aosp and Ginger-Yoshi are very stable.
I tried several others that were not so stable, though they have lots of loyal fans, maybe their phones are better than mine.
I agree that we should be able to build a tight system without JIT that is faster, efficiency is the key.
A buddy of mine, has a very fast Android LG Optimus phone - it fly's he can run all sorts of animation, applications etc. and it doesn't seem to affect the speed of the phone...He runs 9 MFLOPS which is WAY above what everyone else with the same phone has...he told me that he isn't modifying the subroutines/calls, he's sort of linking scripts to make things run more efficiently. He's a physicist not a programmer.
He just constantly tinkers with it though - some bits are buggy, it's just a hobby for him, he has development tools right on the phone
My current Ginger-Yoshi runs just over 4 MFLOPS, which is less than I wanted but all I can find so far.
JIT is NOT a good match for this hardware, for the simple reason that JIT consumes more RAM.
What you have is a piece of hardware that is SEVERELY RAM LIMITED. Eating up even more of it causes necessary components to be booted out of memory, which ends up causing long periods of WAITING while those components RELOAD. It can also lead to instability, since the available memory will IN MANY CASES, be insufficient for loading even a single program into memory.
Counting FLOPS is a very poor measure of overall system performance. I would bet you that in terms of overall usability and wasted user time waiting, your phone will actually be FASTER with JIT DISABLED.
Ignore FLOPS. It is irrelevant.
dhkr234 said:
Ignore FLOPS. It is irrelevant.
Click to expand...
Click to collapse
I appreciate your argument and I 100% agree that the phone is ram limited, can you suggest another build that does not use JIT?
My current Ginger-Yoshi is faster and smoother than any 1.6 I've run (I have not run Super D, that was going to be my next target if G-Y was buggy).
That goes back to my original reason for this post...fast enough to play angry birds or whatever I'm doing.
You say to ignore FLOPS, that is the fairest test That I know for different phones,<Millions of> Floating Point Operations Per Second..that bypasses graphics co-processors and gets down the the meat of what's going on inside.
If you can suggest a ROM that runs better than G-Y I am very willing to try it, but right now the very best ROM I've tried is G-Y (not perfect but better than Anything I've run on this phone).
GolfnWrx said:
I appreciate your argument and I 100% agree that the phone is ram limited, can you suggest another build that does not use JIT?
Click to expand...
Click to collapse
I would expect that you can switch on/off JIT in your settings, so you can try if for you JIT helps or not. G-Y doesn't provide this? (Sorry for the question, but I've never tried it ...)
If there is no option within the ROM, you could add
Code:
dalvik.vm.execution-mode=int:fast
to you /system/build.prop to disable JIT, or
Code:
dalvik.vm.execution-mode=int:jit
to enable JIT.
Sent from my Gingerbread on Dream using XDA App
haha, sorry I guess I was not clear
yes, i can enable/disable JIT....what I was asking for though was a stable build that is faster than 2.5 MFLOPS.
There were some people last year that found a way to script one of the roms to be more efficient....IIRC they were able to get up to 3.7 MFLOPS....but I don't see them around any more....no JIT it was a rebuild of 1.6 I think..maybe 2.1, I just don't recall.
That might be the best way to go, or they might have hit an error...I didn't keep up with it.
Thanks for the reply though
So you want a script to spoof Linpack?
Sent from my Gingerbread on Dream using XDA App
dhkr234 said:
JIT is NOT a good match for this hardware, for the simple reason that JIT consumes more RAM.
Click to expand...
Click to collapse
Overall my opinion on JIT (vs. android version)
1.6 - caused some apps problems otherwise seemed the same w/ or w/o jit.. maybe more ram and slower
2.1 - extra ram caused problems with services and slow load times.. improvement at run time minimal.
2.2 - improvement at runtime noticeable but still high memory use and very slow load times
2.3 - incrreased memory use and loadtimes; but more minimal than earlier versions; with screen andimations off/fast perfomance may be acceptibal to many given the better performance of the browser and other higher processing tasks. [at least in a light weight rom]
(Of course this is my opinion durring use .. not a linpack score)
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?
Hello all, today I will be showing you how to speed up your Nook Color a bit... these methods should work for CM9/CM10/CM10.1/Paranoid Android/etc., but I personally found these out while running PA ICS. The apps you may need to make your phone faster are Ram Manager (Free OR Pro) and No Frills CPU Control (In the case that your ROM doesn't have overclocking in settings). Basically, using these "tweaks" (minus overclock, as whenever I flash a ROM the first thing I do is overclock it), I went from a painfully slow (as in, I was ready to go back to Gingerbread) device to a somewhat faster device. I've seen huge differences in launching games and apps especially, and opening to app drawer seems to be smoother also.
CPU Overclock
Either using No Frills CPU Control or the built-in overclock, set your max CPU speed to the highest on the list (not exceeding 1200, but it shouldn't show anything above that anyhow). Change your governor to either Ondemand or Performance (I personally use Ondemand and have no problems with it). Most of you are probably already overclocked though, so please don't look at me like I'm stupid.
Swap Space
Open up RAM Manager and there should be an option to change your swap space at the bottom. I changed mine to about 48 and am content with that, although I must add it may make your SD card's life shorter. This will increase your RAM, thus allowing you to have more apps open at once.
Force GPU rendering
Open Developer Options in your settings app and check "Force GPU Rendering"... I'm guessing this is one of the biggest factors to my tablet becoming smoother, as from research it helps lower end devices achieve a better framerate, although it may decrease your battery life. Also, I cannot guarantee every app will run great with this. I tested a game (Dynamite Jack) with this setting enabled and it wasn't too shabby at all! But yes, I can definitely see a difference in the overall speed of my Nook Color.
Please tell me how these work for you
I tried these settings, but unfortunately didn't perceive any performance improvement.
Good call on RAM manager. Hadn't seen that before, its going on my NC and RAZR now
Can anyone tell me a good reason for that RAM Manager app to have the permissions it does? Location, Identity, and full network access?
Does NOT work. All this app " no frills CPU" does is provide a GUI front end for the settings already found for our nook color using CM 10+ in its "performace" settings. Also this app does not provide over clocking above our set 1100 MHz. You will need a custom over clocking kernel for the encore for this. Check over on the CM 10 kernel thread n the development section.
I would like to know if CM is needed to do the following or if there is another way.
(Ive only had the Nook for a couple weeks, not sure whats out there)
1) Use a USB thumb drive for MP3 storage/playback. (found this)
2) Hooking the Nook HD to my TVs HDMI port.
3) Possibly use a blue-tooth keyboard
Currently i use:
- Google play for programs.
- Download ebooks and pdfs from alternative sources but do use the Kindle app from time to time (but have that installed on a PC along with Calibre),
- Dont think i have used the B&N app for anything yet, so if that is lost, it will not be that big of a deal (would be nice to have it though).
Alittle background:
I am not new to "flashing" a device, but is there is no need to then i dont.
Ive had an ipod for years running RockBox (and love it)
Been running a ubuntu based server and desktop for a few years.
Any suggestions or guidence would be great.
- thanks...
_
In case it helps others...
I installed CM 10.1.3
1) the USB storage worked great as per-link above.
2) have not tried
3) tried a Logitech MX5000 ("desktop") keyboard just to see what happens, they made the hand-shake but nothing after that... i did not try too hard.
Found a B&N Nook (the green N) app (.apk from an alternative site) and it seams work fine.
Dont know if you can get the USB working with-out CM, but it works great with it.
_
A key issue with stock Nook rom is performance. The library sync is a resource hog and randomly results in stutter for apps. Movies, games etc. it also results in battery drain.
For this reason alone, stock is best served a quick death. CM 10.1 and Nova is a good combo and then in performance settings: Turn on 16bit transparencies and set ram to "purge assets".
Added: Any other performance settings appear to actually downgrade performance.
rushless said:
A key issue with stock Nook rom is performance. The library sync is a resource hog and randomly results in stutter for apps. Movies, games etc. it also results in battery drain.
For this reason alone, stock is best served a quick death. CM 10.1 and Nova is a good combo and then in performance settings: Turn on 16bit transparencies and set ram to "purge assets".
Added: Any other performance settings appear to actually downgrade performance.
Click to expand...
Click to collapse
Where are these performance settings located?
You go into About device and tape the rom version several times. I think that is it to unlock it, but a quick search will get the right steps if wrong. Need a non stock rom to get the options.
rushless said:
You go into About device and tape the rom version several times. I think that is it to unlock it, but a quick search will get the right steps if wrong. Need a non stock rom to get the options.
Click to expand...
Click to collapse
Found them,, thanks
rushless said:
A key issue with stock Nook rom is performance. The library sync is a resource hog and randomly results in stutter for apps. Movies, games etc. it also results in battery drain.
For this reason alone, stock is best served a quick death. CM 10.1 and Nova is a good combo and then in performance settings: Turn on 16bit transparencies and set ram to "purge assets".
Added: Any other performance settings appear to actually downgrade performance.
Click to expand...
Click to collapse
Thanks for the tips, just tweaked them now, will see how it works tomarrow.
As for a launcher, ive been use the GO one but do have Nova installed.
_