yashsingh1/xdaforums huggingface dataset:
[Nook Color General] Jimbo67:
Please clarify your statements! It is Impossible to install a Rom to the EMMC of a newly partitioned NC! Don't generalize all of us with new nooks into a catagory of Lazyness!

Also, 2 days ago you post this--Quote

I'll be honest. The NC confuses me slightly when it comes to how to root, flash ROMs, etc. compared to my Incredible, it feels like day and night.

I made a thread about a month ago about wanting to learn the process but since then it has changed greatly with the 1.2 update.

I would really like if someone could detail out to me the steps I need to root and have CM7 on the NC.

I have questions that are probably answered right in front of me but they get lost in the vast amount of posts.

•Since the eMMC is pretty much canceled out for the time being, I want to run CM7 off the SD card, I've already read a Sandisk Class 2 8 or 16GB is the right card for this, how the hell do I put CWM, CM7, etc on this one SD card or am I supposed to use 2-3 different cards for the process? Then what do I do from there?

•What is the most stable, but feature packed release of CM7 at this point in time, like what build, which kernel, etc.? Market and GAPPS working?

•Assuming the SD card is good, does running off the SD card impact performance or is it as slick as running off the internal?

Pretty much I'm starting from dead scratch when it comes to the NC and I feel the guide threads don't do enough justice to explain certain questions fully enough or at all?

If it helps at all, I just plan to download apps, internet browse, stream music from Mougg, little or no game playing, and overclock.

So someone please help me out? It's not like I know nothing, as I have a rooted and kept up to date phone but for some reason, the NC confuses me and I may be overthinking.

If I remember any more questions, I'll list them. Thanks.

Sounds like to me, you are a Bit Hypocritical!!!!
[Nook Color General] I Am Marino:
What did quoting me prove?

Nothing.

I said the new partitioned NCs may lead to people not wanting to root because those people may be scared of going through the trouble to try to learn how to do root stuff otherwise or people too lazy to work around it. Had nothing to do with generalizations, before you try and make me look foolish, stop doing it to yourself.

By no means am I an expert at the content on this website and I'm quite new to the NC scene but that doesn't make me stupid and doesn't give you the right to try and throw me under the bus for some e-cred.
[Nook Color General] ramiss:
Besides all of the reading, like how hard is it to root a NC really?

Step 1. Put file on SD Card

Step 2. Boot up

Step 3. Um...like thats it!

I've had a harder time opening the front door when I've had a few drinks :D

*Just to clarify...the above was an attempt to difuse the situation with brevity*

Carry on!

Richard
[Nook Color General] lesdense:
I thought I was keeping current on Nook Color issues (rooting, ROMs, etc) but this is the first I've heard about changed partitions and how it may effect rooting the device. I'm running CM7 stable on internal memory and love it. I've got a microSD that boots the Nook into clockwork recovery or whatever that's called, I wipe everything and then install CM7 and gapps from the SD card, reboot and I'm done. I've installed the same setup on Nooks for two friends who envied my tablet. A third is about to go buy a Nook so I can do the same. if the Nook she buys has these new partitions will this process NOT work?
[Nook Color General] jb7038:
If you guys get the new partition, give this a try. I've done it myself since I had the new partition.

http://xdaforums.com/showpost.php?p=13971291&postcount=110

Works perfectly :)
[Nook Color General] cheez99:
So I got my refurbed Nook today and it has the changes to the partitions (blue sticker on box). I tried to load CM7 via CWM on the SD card and it won't boot at all. Is this because of the changes to the partitions?
[Nook Color General] ramiss:
Yes....and see the post right above yours on how to solve it.
[Nook Color General] schaan383:
I just bought a nook yesterday; It was an older one still running the 1.1 upgrade. If I upgrade to 1.2, will my nook be repartitioned automatically?
[Nook Color General] Gin1212:
As far as I know, No, it will not be.
[Nook Color General] Deegan87:
I don't understand why B&N is putting so much effort into this. Rooting doesn't violate any carrier agreements, since this is a wi-fi only device, and their store is still available for use after a root. If they're worried about book piracy, that can be done without root. Any insights?
[Nook Color General] ramiss:
B&N discourages rooting for many reasons, including the fact that they only paid Google specific licensing fees and now most of us are running the full OS.

There is also the fear that we will damage the device and return it, which will directly affect their bottom line.

Whether or not WE think rooting is good may have nothing to do with how B&N and its investors thinks this affects their image.

No matter what, rooting is an out of control rogue operation in the eyes of any company. That lack of control scares them.

Secretly they may be fine with us rooting, but they are under a business obligation to their partners to protect the original design specs.

Sent from my rooted Nook Color acting as a Galaxy Tab.
[Nook Color General] tbXDA:
Well for me, I would not have bought the Nook Color unless the root and full android install was an option.

I think there is probably a lot of people in the same boat that bought the device because it was primarily a nice way to get into a tablet with the added bonus it is a very good size for an e-reader.

Bottom line, there probably is a substantial increase in sales because of what people have done here making this a full android tablet. :D

It would be ill-advised for BN to impact this capability.
[Nook Color General] I Am Marino:
I don't know about that.

Remember although like 9/10 of the people here root and mod things, we're still a very small minority, most people probably actually did buy the NC for the e-reader, only as people keep word of mouth going do they figure out more about what they can do.
[Nook Color General] ramiss:
Absolutely right. There have been over 3 million sales of the Nook Color so far. We may be a very large community but we are a drop in the profit bucket, and most likely considered a risk in comparison.
[Nook Color General] foobster:
I just got a new blue sticker nook color and am having some issues. I understand that the software for installing images hasn't been modified to reflect these partitions yet but does it make sense that running from sd shouldn't work? I've been following verygreen's guide and using the exact versions and links that he has there but it hangs on "Loading...". If I try to use the nightlies instead I can sometimes make it to the cyanogenmod animation but every one I've tried freezes either there or earlier. Has something changed with the blue sticker nooks that would make us expect either generic-sdcard-v1.2.1 or update-cm-7.1.0-RC0-encore-2.6.32-beta3.1 to no longer work properly? I thought that this might be relevant to post in verygreen's thread but I haven't made enough posts to do that yet.
[Nook Color General] radrobe:
Help Please

Ok, so I've had a rooted NC since February and have ran most everything at one point or another thanks to the good people at XDA. I currently have CM7 .32 on mine.

My buddy saw my system and decided he liked it and bought one. I ran clockwork mod and flashed CM7 .32 on his NC. There was no notification bar on his and the cyanogen settings were force closing. I think he may have had the partitions on his. I'm trying to create an SD card CM7 for him, but I would like to fix his emmc as well. The adb partition fixes are really above my head as I have never been able to get adb to work.

Any help is greatly appreciated.

Thanks.
[Nook Color General] wpbear:
My use for the NC is the reason BN wants to discourage hacking. I had no intention of ever buying a BN ebook. I am actually using the Kindle app on it. So BN is not getting any residuals from my purchase and the hardware is priced at barely not a loss. I have a great 7" Android tablet for $250!
[Nook Color General] Taosaur:
For those who get the newly partitioned tablets, it may be worth calling up a B&N store and asking if they can revert it to the old scheme.

Personally, while I have not yet bought anything from B&N (got my NC at Staples), I don't feel like I got anything over on them by replacing their software. I suspect they knew exactly what they were doing in releasing such a flexible device and cashing in on the development community to give it the "iPad killer" reputation. They definitely have my respect for being the ONLY old media book retailer to make a half-bright transition into the 21st century.
[Nook Color General] I Am Marino:
I think B&N do realize that people are starting to buy the NC only for the ability to turn it into a full fledged tablet and I'm thinking the repartition was a last minute change to try and fix it.
[Nook Color General] ChrisDDD:
Same here, had the Nook not been so easily hacked to put full Android on it, I'd have never bought one in the first place, so even if they didn't make a huge profit on the hardware, they still came out ahead. And I have their Nook app installed and may purchase books or magazines in the future.

And I agree it's nice to see companies making open (or relatively open) hardware. I will not buy any device that's totally locked down.
[Nook Color General] cheez99:
Can anyone here explain to me why the partition change prevents loading a different rom to the device? Isn't the change just to the storage partition that holds media? I was under the assumption that the rom ran on a totally separate partition. If it does run on this now 1gb partition, why is that not enough storage for a custom rom?
[Nook Color General] Taosaur:
It's definitely still too early to tell what impact this change will have on the ROMs and disk images on this site. Verygreen says it shouldn't impact SD installs using his image.
[Nook Color General] cheez99:
Yes, SD installs still work, but are a huge PITA. Plus, for me, CM7 running on an SD card is really slow.
[Nook Color General] Taosaur:
Verygreen's SD install is about as easy as it gets. I would suggest WinImage over Win32DiskImage, but after you get the image written, both initial installs and updates are just drag-drop-reboot, drag-drop-reboot. You need a suitable SD card from the outset, but if you have that much, it's equal or better to running from eMMC.
[Nook Color General] d.v:
I thought Android was free, open source. What license fees does BN pay Google?
[Nook Color General] BonkyMoon:
Android the operating system is open source, but Google's apps and the Android Marketplace aren't. If you (as the manufacturer) want your device to use Google's apps or its marketplace, you have to get the appropriate licenses.

That's my understanding anyway.
[Nook Color General] Taosaur:
I've never heard of an instance of B&N discouraging rooting or other mods, or even being sticklers for the terms of the warranty. It's entirely possible the new partitions are as stated: an attempt to provide more space for apps and B&N content.

Someone also stated in another thread on this topic that a B&N employee said they would repartition in either direction upon request.
[Nook Color General] foobster:
I don't see how the partitions should effect an SD boot but radrobe's friend and myself have both found that that verygreen's image is not working successfully with our blue sticker nook colors. Is there any chance that something other than the partitions has changed? Has anybody with a blue sticker nook successfully used verygreen's image?
[Nook Color General] ramiss:
Of course they have discouraged rooting. They have actively stated that doing so will void your warranty!

Now...if someone wants to test that and try for a hardware replacement on a NC running CM7, then I would love to l know the outcome.
[Nook Color General] dlinfiniti:
Not that us rooting the nook color changes this from BN's perspective, but just because something is open source doesn't automatically make it free.

google may give it away for free under open source but for manufacturers like BN, samsung, LG, HTC, motorola etc, it is very much not free. Google just passed the burden of paying for the IP claims and external license challenges from companies like microsoft onto the android device manufacturers.
[Nook Color General] Taosaur:
Well, I'm not sure I would call a legally necessitated statement of the obvious 'discouragement,' but it's at least a mixed message when they include a safety net for rooters in the form of stock recovery, and a boot configuration that offers a back door into the system no matter how badly you scramble it. The main disincentive to rooting in these warranty clauses is the prospect of bricking a device while attempting a root, a risk which the NC's design reduces to near zero.

I would sidestep the issue entirely and, if you don't intend to load up on B&N apps, take the NC into a B&N store and have it repartitioned. It would be nice to see confirmation that they're willing and able to do so, too. If you've tried to put a new ROM on the eMMC but stock recovery is still intact, interrupt the boot 8 times to flash back to recovery, or hopefully you made a back-up and can reinstall stock from that.

Verygreen has said that his images use the internal cache partition, and he's looking into moving that element to the SD card as well. He doesn't see how the repartition would cause his images any problems, but that change may solve the issue.
[Nook Color General] hoteladriano:
Your problem with verygreen's instructions seem to be similar to what I encountered on a non-blue sticker Nook. On the off chance that you haven't already tried, the following suggestions got me past being stuck at the blue "android" text:

-format the SD card with the SD Formatter 3.0

-switch to WinImage from Win32DiskImager (or vice-versa)

-try using a SanDisk class 2 or 4 card

Sorry if you've already tried these steps, just trying to help! Good luck.
[Nook Color General] FRSP:
They probably do (or more realistically do not disable what TI built in) these things because they are to their own benefit, not ours. I shipped an embedded system in a product and slept very well at night knowing it was unbrickable - regardless of what state it got into it could be UART booted and reflashed by any PC with a real (or USB-adapter) serial port using our firmware update tool. At one point I was looking into using a different processor, and though it wasn't the reason we didn't switch, the fact that closed-box system maintenance would now depend on a UART boot routine in flash rather than absolutely immutable mask rom was a downside in my eyes.
[Fascinate Q&A, Help & Troubleshooting] mjobailey:
I want to try KAOS' Gingerbread ROM but need a VooDoo Kernel. Just curious if a VooDoo Kernel will work with the stock EDO1 ROM and if so what is going to be the best Kernel? Thanks!
[Fascinate Q&A, Help & Troubleshooting] kidserious:
Nevermind

Sent from a depraved XDA junkie and flashaholic
[Fascinate Q&A, Help & Troubleshooting] kidserious:
Flash jt's gingerbread cm7. It's WAY less buggy and you don't need a voodoo kernel to flash it. Jt's rom mounts both rfs (non-voodoo) and ext4 (voodoo). So you're good to flash it from stock or a voodoo converted custom rom. Just wipe EVERYTHING first!

Sent from a depraved XDA junkie and flashaholic

Sent from a depraved XDA junkie and flashaholic
[Fascinate Q&A, Help & Troubleshooting] mjobailey:
Thanks for the fast response. One last question, where can I find these kernels at? I looked but not sure what's what. Thanks again.
[Fascinate Q&A, Help & Troubleshooting] kidserious:
Nitsuj17 has a sticky in the development section. All the kernels (with the exception of otb 1.5 for tw and gb) are listed there.

Sent from a depraved XDA junkie and flashaholic
[Galaxy S I9000 General] well.heeled.man:
Hi Folks,

For those who are interested, I have modified the 90screenstate_scaling script used in Zach's (and now Glitch's) kernel for use with other CM7 compatible kernels. The aim is to create a very simple script that can easily be read, modified and improved upon by non-coders, such as myself.

I have retained only the code that will read the screen state, set the governor appropriately and set the scaling threshold, giving users complete control over the scheduling behavior of their CM compatible kernel.

I am not a coder and all credit goes to FloHimself and zacharius.maladroit for the original content. all I have done is (hopefully) simplify the script and make it easy for non-specialists to read.

If you would like to try it out, copy the script in to /system/etc/init.d and modify the values to your liking. If you are already on Zach's kernel there is nothing new here, as you already have this script.

The script currently includes kernel defaults from Glitch for the smartass governor, from Zach for the conservative and ondemand governors, a few experimental settings, and of course, the ability to modify them yourself.

If you add anything or make any modifications (particularly in relation to your specific usage pattern) you would like to share, please post them and I will update this thread. If you make modifications, comment them appropriately and explain your usage pattern for which the settings work best so that people know if it would work for them.

The experimental conservative settings that I have made (that are currently in use on Glitch kernel) for the screen off state are designed to aggressively keep the frequency very low, almost like a 100mhz frequency cap, while still allowing them to scale up under considerable load. They are (hopefully) ideal for background screen off behaviour such as listening to music, exercise applications or aggressive sync and push/pull email behavior (like in an office).

The experimental smartass settings are designed to test the hypothesis that quick downscaling may cause as many lags as as slow scaling up behavior. The goal is to create a more linearly scaling version of smartass which is slower to upscale or downscale (only a matter of milliseconds difference). These are still under testing.

With one of the main reasons for using smartass as a single governor, the min/max frequencies for the screen on/off state no longer applicable with the governor changing in relation to the screen state, I have moved to ondemand settings, which may have battery implication while the screen is on, but they are VERY smooth.
[Galaxy S I9000 General] zacharias.maladroit:
*subscribes*

we could probably make conservative governor more aggressive

with the settings that laststufo used on his kernel but I'm not sure if it would scaled up fast enough if you used e.g. some DSP settings on sound while the screen is off

worth as shot

if I don't forget it - I'll post the settings later
[Galaxy S I9000 General] Tk-Glitch:
Subscribes too :D

I like the idea and the simplicity of this. And with Zach's help, also known as "F*ckin scripts master" (almost a private joke :p), it can only be great.
[Galaxy S I9000 General] well.heeled.man:
I'm a big fan of simple, though as a user of Arch Linux on the desktop I have no choice (BSD style init scripts a boot - beautiful simplicity)! ;)

It's great you lads are watching this! Hopefully the thread will grow in to something, even if it is just an sandbox for users to experiment with the settings they prefer. If nothing else, hopefully you guys get some useful info!
[Galaxy S I9000 General] well.heeled.man:
I just added a bit of an experimental version that moves away from the default smartass values.

I am hypothesizing that the very accasional lags in the smartass governor might be related to the governor scaling down too fast, rather than it not scaling up fast enough.

I changed the default down threshold from 40 to 35 and the default up threshold from 60 to 65. Hopefully this will scale up and down a little more linearly and this will make the GUI even smoother. I am still testing this theory at the moment, but thought I might post it (on the first post) if anyone wanted to have a go.
[Galaxy S I9000 General] zacharias.maladroit:
well.heeled.man,

you need to test your conservative settings while the screen is on

they're way too aggressive (at least the up threshold, down threshold may be ok)

also the freq_step at 10% should be at least at 15%

if we compare it with laststufo's kernel (he almost had 100 MHz steps everywhere: 100, 200, 400, 600, 800, 900, 1000 MHz)

so that needs to be compensated to get smoother & similar behavior

I'll take a look & see how the new smartass settings work out

:)

my new conservative settings are:

echo "76" > /sys/devices/system/cpu/cpufreq/conservative/up_threshold # 50 # 76 # 76

echo "30" > /sys/devices/system/cpu/cpufreq/conservative/down_threshold # 35 # 12 # 30 (higher will lead to noticable lags) # 35

echo "15" > /sys/devices/system/cpu/cpufreq/conservative/freq_step # more aggressive ramping up (50)

this currently keeps the cpu between 100-200 MHz while playing MP3s for me (screen off) - mostly 200 afaik right now

but I'll try your conservative settings, too, when I find time - let's see how they are in terms of "smoothness" (I'm sure they're not too usable with the GUI but could be great for background tasks while the screen is off)
[Galaxy S I9000 General] well.heeled.man:
Hi Zach, indeed, I would say that the conservative settings are completely unusable with the screen on. I would not recommend these with the screen on.

However, with music (DSP manager too) GPS and Cardio Trainer all running (my cycle home), it seems to work fine (screen off). Every km, Cardio trainer speaks the time taken over the music (two audio streams). With many kernels this becomes slow, or slurred, but sounds perfect with these settings.
[Galaxy S I9000 General] zacharias.maladroit:
awesome !

so it still raises the frequency when needed ?

100 -> 200 (or more)

you checked via e.g. CPU Spy ?

thanks !
[Galaxy S I9000 General] well.heeled.man:
Yes, it still goes up when needed (confirmed via CPU Spy), but it needs to be really pushed. It seems like good behaviour in the screen off state.

EDIT: something in the region of a 66%/33% 100/200mhz split at these settings.
[Galaxy S I9000 General] well.heeled.man:
I am struggling to confirm that my settings are being applied as I would like in the screen off state. I can read off the values in /sys/devices/system/cpu(/cpu0)/cpufreq/conservative if I manually set conservative in Pimp My CPU with the screen on, but the behaviour seems at odds with the values i.e. not as laggy as one would suspect.
[Galaxy S I9000 General] well.heeled.man:
As (a variation of) this script are now used in Glitch's too, I have changed the comments to allow people to very easily see which settings are from kernel devs (which should probably be left alone should you wish to return to their defaults) and experimental settings (which I would suggest you change, if you change any). If you want to use parts of it in Zach's, I would suggest cutting and pasting the experimental part into the appropriate part of Zach's script as overwriting any part of it would remove much of his additional functionality.
[Galaxy S I9000 General] jeebspawnshop:
This is great guys - thanks for this ;)
[Galaxy S I9000 General] well.heeled.man:
With one of the main reasons for using smartass as a single governor, the min/max frequencies for the screen on/off state, no longer applicable with the governor changing in relation to the screen state, I have moved to ondemand settings by default. This may have battery implication while the screen is on, but they are VERY smooth.
[Galaxy S I9000 General] calebv2:
wrong spot
[Galaxy S I9000 General] zacharias.maladroit:
screenstate_scaling_V49.zip

that's the current version of my screenstate_scaling script that I offer as an option with Neo 17 r7

most of the stuff moved into the S98system_tweak script that now is shipped with the kernel