Running cm7 off sdcard and just did something stupid.
I set the cpu speed up a notch (from 1200 to 1325) and raised the voltages up just one notch. And without setting it to go back to default on boot, I took the sd card out, loaded the nightly build (143), put it back into the nook and did a recovery boot.
It Applied the upgrade and I rebooted for a normal sdcard startup. After the home screen gets populated and all the routine icons appear (and looks normal) nothing more can happen. Touching any of the icons does nothing, and hitting the power button won't hide the screen. All I can do is press and hold the power button for about ten seconds to turn the unit off.
When booting to NC, all works as expected.
I really don't want to loose the other work I did over the last few days!!
Since it's the Nook Color Tweaks app that does the adjusting during boot, I'd pop the SD into some system that can handle a partitioned SD (Linux will absolutely work, Windoze probably not) and delete this folder and all contents:
/data/data/com.dalingrin.nookcolortweaks
This should blow away the settings. Put it back into your NC and try to boot. If that doesn't let you boot, do it all again (remove the above folder) but also remove
/data/app/com.dalingrin.nookcolortweaks-2.apk
You'll have to reinstall Nook Color Tweaks after this, but the settings should be back to default.
You may have to dig a bit to figure out the partitions, and their names probably won't make sense. For instance, on Linux it may be something like /media/sdc2/data or /media/B3-A7/data instead of /data/data. I forget how the SD install names the partitions, or if it names them at all.
If there's some recovery tool that'll let you do the above on the NC itself, somebody please post it here and let us all know.
Good luck!
Thanks for that info, it makes sense to me.
I don't have a Linux system handy but may just build one for the heck of it.I suppose that would take more effort than just re-doing my work on the sd card however, but it would help me REMEMBER to make changes with a backup plan
Cancel that previous idea! I don't have a spare system that contains an sd reader.
Perhaps a bootable cd/dvd that can access the sd partitions would be the right answer. If so, can anyone give me a 'shortcut' to build this or download a prebuilt iso image. Thanks.
I hear ya. I wouldn't've enjoyed my NC half as much if I'd been using Windoze to mess with it. I could just pop my SD into my office or home machine and have full access to everything. Very handy. Not being able to do that is the only downside to running from emmc that I've encountered so far. But I haven't had any disasters yet.
I downloaded an iso image for Slax V6. Unfortunately its for a cd, and all I have are dvds. I suppose that it isn't possible to burn this to dvd and have it work
If you burn the img to a DVD, it should work (Isoburner is free and does a good job for that).
Slax 6? Is that a live cd image? You don't have to install Linux, you can use the distros that boot off of the cd/dvd when you burn the image, like Puppy, Linux Mint, or PCLinuxOS. You can get links to those at
http://www.distrowatch.com
If you're familiar with Linux, Slax is great, but if you haven't done a lot with it, I'd go with Mint or PCLinuxOS. Those distros are easy to use, and should have the tools you need. You can also download DVD's of those, if you like.
While waiting, I found a flavor of slax to write to a thumb drive and make it bootable .
So I tried this out on a 4gb thumb. It boots fine, but when it runs startx, it just sits there . I can do a ctl-alt-del to reboot, but it is dead beyond that. I can boot it up to log on as root with just the cmd line input, but I am deperately lacking in the knowhow to navigate to access the sd drive .
And this is starting to look like it is becoming an 'off topic' thread, so I appologize to the subject gods.
[Solved] Thanks for helping
Finally bit-the-bullet and just rebuild the sdcard, etc.
Was spending more time trying to recover than it would have taken to rebuild.
griffinmt said:
Finally bit-the-bullet and just rebuild the sdcard, etc.
Was spending more time trying to recover than it would have taken to rebuild.
Click to expand...
Click to collapse
Lol, for future reference, www.pendrivelunux.com and make yourself a bootable ubuntu flash drive or something
Sent from my NookColor using XDA Premium App
Related
I have been wondering if it is possible to modify where programs store their external data on the SD card, but have not been able to find an answer yet.
Example...
I have the program "FolderOrganizer" and it stores it's backup data to /mnt/sdcard/FolderOrganizer. Now what I would like to do is to clean up my SD card a bit by moving all my program saves to the /mnt/sdcard/Android/xxxxx folders. This way I know where all my backups, skins and etc are located at while keeping my file structure clean.
I have been using Root Explorer to poke around and see if I can find any indication of where these programs set their external save directories at (xml files etc), but I have not been able to figure it out yet.
I bet it is something easy that I am just missing. Can anyone help out or point me in the right direction?
djstaid said:
I have been wondering if it is possible to modify where programs store their external data on the SD card, but have not been able to find an answer yet.
Example...
I have the program "FolderOrganizer" and it stores it's backup data to /mnt/sdcard/FolderOrganizer. Now what I would like to do is to clean up my SD card a bit by moving all my program saves to the /mnt/sdcard/Android/xxxxx folders. This way I know where all my backups, skins and etc are located at while keeping my file structure clean.
I have been using Root Explorer to poke around and see if I can find any indication of where these programs set their external save directories at (xml files etc), but I have not been able to figure it out yet.
I bet it is something easy that I am just missing. Can anyone help out or point me in the right direction?
Click to expand...
Click to collapse
No... it's not something you're just missing... there is no standard and as a result it's almost impossible to achieve what you're aiming for. I too wish for the same, everything simply under <sdcard>/android/ ...
Some apps are hard coded in their code, some allow the user to select, some store in /data/data/xxx/shared_prefs/ - it's a lottery.
djmcnz said:
No... it's not something you're just missing... there is no standard and as a result it's almost impossible to achieve what you're aiming for. I too wish for the same, everything simply under <sdcard>/android/ ...
Some apps are hard coded in their code, some allow the user to select, some store in /data/data/xxx/shared_prefs/ - it's a lottery.
Click to expand...
Click to collapse
Thanks for the response. That is a bummer though, I was really hoping to be able to tell everything where to write to. I currently have a ext4 partition on my SD and that is where all my apps install to... if I can't tell the apps where to save on my SD partition, it would be nice to at least move it all to the ext4 partition.
There is crap all over on my SD card and my OCD is starting to kick in!
Yeah, I know the SD card can get messy... it's really stupid and annoying... Unfortunately, there is no SD card data saving guidelines for developers... and writing to an ext partition is completely out of scope for market apps because not all users have ext partitions... it would be nice, though, to have apps save data under one common folder... say /sdcard/data or /sdcard/Android... maybe we need to petition developers or Google!!
I agree with the saving to and ext partition. I just think it is silly that you can't at least specify a directory to save external data. I know some apps allow this, but I guess that if Google forced a change then everyone would have to change their code.
I wonder what would happen if you took out your SD and tried running those apps. Where would they write to then?
djstaid said:
I agree with the saving to and ext partition. I just think it is silly that you can't at least specify a directory to save external data. I know some apps allow this, but I guess that if Google forced a change then everyone would have to change their code.
I wonder what would happen if you took out your SD and tried running those apps. Where would they write to then?
Click to expand...
Click to collapse
Apps that require the sdcard for storage will usually either give an error when run without an sdcard or just not work at all.
I am also pretty anal about my storage and neatness, and I have given up on my sdcard being organized. What I have done is create folders with capital first letters to bring them to the top of the listing when browsing by default sort, at least I can find what I want easily without sifting through all the data folders..
That is pretty much what I have done. I guess it it better than nothing. If I knew more about programming I would try and build something to look for and modify those paths. I just never really understood/got into the whole programming thing... that is why I ended up in Infrastructure. lol
djstaid said:
That is pretty much what I have done. I guess it it better than nothing. If I knew more about programming I would try and build something to look for and modify those paths. I just never really understood/got into the whole programming thing... that is why I ended up in Infrastructure. lol
Click to expand...
Click to collapse
I'm with you there, long time (20+ years) building and repairing pcs, 0- years programming.
As far as building something to modify the paths used by programs accessing the sdcard in Android, that seems a nearly impossible feat. Each program would have to be modified, requiring reverse-coding (baksmali) each one individually, modifying the code, and recompiling (smali). This would also require re-signing and reinstalling each application, making updating from the market impossible, and would take a lot of work.
Due to the fact that applications are "sandboxed" (so to speak) in Android, I wouldn't think there was a global %externaldata% path variable that can be modified from /mnt/sdcard to /mnt/sdcard/Android, I am pretty sure that path is set in each application.
Though, I could be wrong. However, it is worth noting that if it is a global variable, changing it would result in applications that are already properly coded to use /mnt/sdcard/Android/%appname% or /mnt/sdcard/data%appname% to instead attempt to write the data to /mnt/sdcard/Android/mnt/sdcard/Android/%appname% as they would append their string to the global variable.
I believe, all we can do is petition developers to use a more structured data path in their programs, and learn to live with disorder!
daveid said:
I believe, all we can do is petition developers to use a more structured data path in their programs, and learn to live with disorder!
Click to expand...
Click to collapse
lmao!
this is true though... at least I know that I am not alone. haha
I am definitely with you all on this. I found this post after having the same epiphany just now. There needs to be more structure to the use of external storage. These little things are what set our OS apart from say, the "forbidden" iphone...
I have actually tried digging into different apps to see where the store locations are set at and have had no luck. I guess if I knew how to program or at least modify that one part of the app I would have more luck.
Problem with that is if I modify something in an app and it gets updated, I would have to do it all over again. I guess that is the gift and curse of having such an open OS. I will post back here if I figure something out though. I have been digging into the Android OS a little more, but I am still having problems understanding how it all works underneath.
Is there a way to switch the sdcard / sdcard-ext folder names to make the external sdcard the primary one? Or is there any other way to set the primary sdcard?
Thanks!
I was disappointed to see the phone force you to use sdcard and then renamed my microsd card to sdcard-ext. It made it quite a bit of a hassle to restore programs or use the backup features of other apps.
I know its been done on some tablets running 2.3 (My old Viewsonic G Tab). On those you had to edit the vold.fstab to mount them the way you want.
I'd love to do this too. I made a lot of songs available offline in Spotify, synced some mp3s etc and it all ended up on the internal "sdcard", not my 32gb class 10 Patriot MicroSDHC (which works perfect with the D3).
The same goes for most apps.
If someone has experience doing that please tell us how to do, I'm not too experienced in such Linux filesystem things. THANKS!
+1 this is very annoying.
Sent from my DROID3 using xda premium
/etc/vold.fstab seems to be the right place to change it, like mentioned above. However I think the risks are little, I wouldn't be the first who tries out ... at least not before an SBF is available.
And I cannot fully assess what it means for future updates, if and how it has to be undone then. I'd rather recommend to live with this naming.
Thanks for explaining that und danke.
I'm more curious to see if we can remove the space allocated to "sdcard" and merge it back with the internal program storage, then when I drop my actual sd-card in, it mounts as "sdcard".
Possible? Or is that a rom only thing.
Does this link help?
Partitions for the x2
I'm afraid I'm not experienced enough to dare to try it ^^
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?
I'm a Noob and used Rack's thread in the development area to create my dual boot SD card. I just wanted to thank him and all of the developers here for their work. My install went smooth as silk and I am loving my new triple boot setup. Many thanks to all for making my NC a competitive little tablet!
I'm not quite a noob, but this looks like it would be easier than going from mirage to ics to miui in the span of two days
On my home pc I've got win7 and eight distros in a multiboot setup. Yes, I consider myself a distro whore
Been playing with Racks triple boot from SD for a while. Some things you might expect: Mirage CM 7 FCs both ADW and ADW Ex on me at intervals, and with no way to get back in to the system, I've had to reburn the whole business several times. Oddly, CM 9 still powers up when this happens -- I'd love to hear from someone on how to cross over from 9 to 7 installs to work on either. Also getting double entries for Gallery and several other installed apps. Mentioned in Racks thread, but couldn't make solution work (requires changing to rw and editing sys files).
Some other glitches, but if you like fooling around with your NC I'd still recommend the triple boot, as the less you use the weak SD gate on your device the less likely it will fail.
Anniraff said:
Been playing with Racks triple boot from SD for a while. Some things you might expect: Mirage CM 7 FCs both ADW and ADW Ex on me at intervals, and with no way to get back in to the system, I've had to reburn the whole business several times. Oddly, CM 9 still powers up when this happens -- I'd love to hear from someone on how to cross over from 9 to 7 installs to work on either. Also getting double entries for Gallery and several other installed apps. Mentioned in Racks thread, but couldn't make solution work (requires changing to rw and editing sys files).
Some other glitches, but if you like fooling around with your NC I'd still recommend the triple boot, as the less you use the weak SD gate on your device the less likely it will fail.
Click to expand...
Click to collapse
I'm not having any force closing issues with ADW or ADWex in Mirage. Mind getting me a logcat when this occurs? Also, what do you mean by double entries?
I'll be updating with an updated flashable zip for Mirage's latest build as well as ICS build. Hopefully by tomorrow and hopefully it will resolve the issues you are having.
Thanks,
Racks
Mirage and ICS have been flawless for me. Of course ICS still has it's quirks but that will improve with updates. This is a great setup for those who like to boot from SD and have the option of a fast, stable Mirage or boot into a not-quite-there but still useable ICS....
Sorry about my noobness, but I can't figure out how to get a logcat on the ADW & Ex FCs, as the only way I've been able to continue with your builds is by wiping the card and starting over; ergo, nothing's left over for breadcrumbs. The double entries business is two Gallery and two GMail side by side in my apps drawer. I read somewhere else in XDA the reason for this, and a fix by adjusting entries in the guts of the program, but I'm too new with Linux to try that (and too chicken).
Looking forward to your coming update. And a million thanks to you et al for all the hard work the rest of us are enjoying.
thecdn said:
I'm not quite a noob, but this looks like it would be easier than going from mirage to ics to miui in the span of two days
On my home pc I've got win7 and eight distros in a multiboot setup. Yes, I consider myself a distro whore
Click to expand...
Click to collapse
Do you have all 8 distros installed or are you running some of them from live CD/DVDs?! Either way, it sounds AWESOME!
I have win7 on my latest netbook, and I like it. I haven't yet loaded LINUX on it. I haven't decided which distro to use. My last netbook and my old laptop are XP/Ubuntu dual boots. I'm not too crazy about Ubuntu anymore. I'm not into Unity. What's your current favorite distro?
One problem I'm having is that Win7 doesn't see most partitions. That's why I need to get a LINUX distro installed.
I have Racks' multiboot on one uSD card, and Miui on another. Now, if Racks could just make it so we could add more ROMs to his set up, I'd be a happy camper. I think he might be working on a solution. I know I have Boot Manager on my Evo 3D. That works really great. It's nice to be able to change ROMs without having to reboot, or change my uSD card. Does that make me a ROM whore? Ugh, there must be a nicer name than that!
Hello all,
so I was living the life with my new rooted nook color, when suddenly i pulled it out of my pack and found the entire screen was dead. There is a black blotch at the bottom so i am quite certain the LCD is cracked and not coming back.
SO now I THINK I desperately need to unroot. I am VERY scared of doing this with NO screen though. Do you think I even need to unroot, as you can only really see splotches of color when the NC is turned on? Can anyone give me some advice as to a good SAFE way to get my nook back to a state that i can send it into barnes and noble (i have the extended warranty so they will cover ONE damage replacement)?
I wouldn't worry about it. Somebodies going to pull it out of the package, see the screen and toss it on the pile. *If* it is refurbed it'll be wiped and reloaded as a matter of course.
Thanks for your reply. Yeah its pretty hard ro tell that anything has been done to it. When it boots up a solid flickery green bar (which would have been the cynogen logo) goes across the whole screen. Other than that its basically just dark. I don't know, if I knew what cynogen mod looked like I would think it might be fishy, as the nook boot screen is all white.
I'm really not sure what to do. I suppose I could break it more so the screen is completely incomprehensible, but id really rather just unroot it, I'm just really not sure how to navigate clockwork without a screen
see if you can adb into it when its booted... if you can then there are options to install stock back.... let me know if you can adb... i'll give you links to images to dd back to eMMC.
Ok, after a good googling and an hour of tinkering with device manager got the usb drivers working and adb can see my nook color. What exactly did you have in mind to test the functionality of adb? should i try pushing files or something?
0point said:
Ok, after a good googling and an hour of tinkering with device manager got the usb drivers working and adb can see my nook color. What exactly did you have in mind to test the functionality of adb? should i try pushing files or something?
Click to expand...
Click to collapse
You can download 7zipped images of /dev/block/mmcblk1,4,5,6,7 and 8 from my depositfiles...
There is a md5mmcblk_md5's.txt to verify the downloads against.
There is also a partitions.txt files that describes how to image them to your device... the commands are available for you to copy and paste into a command window or terminal screen. It might work as a dos batch file if renamed .cmd... but I don't recall if the commands will run in the adb shell when executed that way.
extract them with 7zip or winrar... copy the .img files to the root of sd card... preferably one and 8 GB or larger... so you can put them all on at once... perform the commands you will find in the partitions.txt file.
Ok so,
not to be ungrateful, but is there anyway you could put these up on maybe mediafire or some other service where there isnt a free download limit? I'd really like to avoid paying 12 bucks just to get six files in under a day (it's probably just going to shut me out after a couple anyway)
If you can see the display well enough to see when it starts to boot up.......then you can always do the 8 interruped boots. This will take it back all the way back to 1.0.1 stock.
0point said:
Ok so,
not to be ungrateful, but is there anyway you could put these up on maybe mediafire or some other service where there isnt a free download limit? I'd really like to avoid paying 12 bucks just to get six files in under a day (it's probably just going to shut me out after a couple anyway)
Click to expand...
Click to collapse
Will setup account and upload to mediafire for you...
EDIT: I have to create a pro account to upload the files... since free mediafire has 200 MB size limit... and 8 of the partition files are MUCH larger than that.
EDIT2: Uploading to mediafire now... You will see the .7z files and files named mmcblk0p5-8.partX.rar... after you have all the rar's... they will extract to the .7z files for each partition... sorry... was just easier for me to split the .7z's I already created this way.
dparrothead1 said:
If you can see the display well enough to see when it starts to boot up.......then you can always do the 8 interruped boots. This will take it back all the way back to 1.0.1 stock.
Click to expand...
Click to collapse
That may or may not work... depending on recovery.img on the eMMC...depending on the condition of /dev/block/mmcblk0p3... these are a couple of reasons I made the recovery files available.
Just a Tip for DizzyDen:
I recommend a site called FileTrip for future uploads. It's owned by the guys that run GBATemp. For Personal Uploads you get 100gb of Storage and 4gb per file, all for Free!, No Upload Limits, No Download Limits, very few Ads(no Annoying ones), Viewing of Documents Online, Streaming of Web Browser(HTML5) compatible Media files, and more. Only Con I find with it is that You can't resume Uploads and it lacks Batch Uploading(Although you can open Multiple Tabs of the Uploader) but nothing that would annoy Downloaders.
@DizzyDan
you are a boss man. Thank you so much for throwing these on mediafire, and the fact that you split them up actually means that with my weak wifi signal i can still dl the whole thing without having to constantly start over.
you're a cool guy man :cyclops: