Database Develop

No donut for Dream?

I wanted to throw this in the development forum as I feel it pertains to such but I didnt want to risk a ban
So MobileCrunch tells me that donut may not make it to the Dream. I feel it is safe to assume that the modders here would be able to make it fit, am I right?

chuckhriczko said:
I wanted to throw this in the development forum as I feel it pertains to such but I didnt want to risk a ban
So MobileCrunch tells me that donut may not make it to the Dream. I feel it is safe to assume that the modders here would be able to make it fit, am I right?
Click to expand...
Click to collapse
officially no, by the time it is out the g1 will be obselete and you will probably have a new phone however if i comes out any time soon the devs here will work their magic and port it over.

JJbdoggg said:
officially no, by the time it is out the g1 will be obselete and you will probably have a new phone however if i comes out any time soon the devs here will work their magic and port it over.
Click to expand...
Click to collapse
this was proven to be a false statement.. donut will still come to the g1... confirmed on tmobile forums... im looking for the link now
http://forums.t-mobile.com/tmbl/board/message?board.id=AndroidDev&thread.id=8520

we already have some of donut so honestly this isn't a big deal unless you don't root your phone

palosjr said:
this was proven to be a false statement.. donut will still come to the g1... confirmed on tmobile forums... im looking for the link now
http://forums.t-mobile.com/tmbl/board/message?board.id=AndroidDev&thread.id=8520
Click to expand...
Click to collapse
dosent say anyhing about dohnut here is what is there "We plan to continue working with Google to introduce future software updates to the T-Mobile G1. Reports to the contrary are inaccurate." im not saying there will be no updates but im not sure about dohnut according to this article they even had a hard time fitting cupcake on the g1 http://androidandme.com/2009/08/news/the-g1-storage-problem-in-charts-and-numbers/. Although i see your point

The issue seems to be that Android OS is becoming bigger and bigger, and non-rooted G1s are limited by the amount of onboard memory they have. Since most of us here on xda run A2SD ROMs, we will have no problems with Donut stuff. Heck, cyanogen has a lot of Donut stuff already included in his ROMs.
If you don't root your G1, your phone will soon run out of space for the newer versions of the OS.

derfolo said:
The issue seems to be that Android OS is becoming bigger and bigger, and non-rooted G1s are limited by the amount of onboard memory they have. Since most of us here on xda run A2SD ROMs, we will have no problems with Donut stuff. Heck, cyanogen has a lot of Donut stuff already included in his ROMs.
If you don't root your G1, your phone will soon run out of space for the newer versions of the OS.
Click to expand...
Click to collapse
yup, exactly

JJbdoggg said:
yup, exactly
Click to expand...
Click to collapse
Do you think its possible in the next release or update they would just force apps2sd to create the space they need and obviously create their own tools to maintain it.

xenoaurora said:
Do you think its possible in the next release or update they would just force apps2sd to create the space they need and obviously create their own tools to maintain it.
Click to expand...
Click to collapse
That's something that I've defintally pondered myself. But I don't think they should force, they should give the option. Because some people may not want to buy another SD card..

Best way for it to be done is give you options to install the components you want, i dont use music on my phone i have an mp3 play so would happily swap that for some amazing feature, or simply optimize and release applications

i guess this is on topic since it concerns dream and donut. but to anyone not following cyanogen on twitter. he is pretty damn close to a functioning donut. the last donut he did didn't have any kind of data or signal access and he said that he got mobile data working which is a huge leap forward so maybe we will donut on the g1 soon enough.
just a thought... i wonder if someone could make a spl that got rid of all the unneeded space in cache that is supposed to be for ota updates that would brick the phone? that would be great but i don't see that happening

xenoaurora said:
Do you think its possible in the next release or update they would just force apps2sd to create the space they need and obviously create their own tools to maintain it.
Click to expand...
Click to collapse
the problem is most people wouldnt be able to format to ext2 or 3 and if they remove their sdcard it could break their system (unless they alloww it on fat32)
which almost all other mobile operaing systems do so im sure they could.

JJbdoggg said:
the problem is most people wouldnt be able to format to ext2 or 3 and if they remove their sdcard it could break their system (unless they alloww it on fat32)
which almost all other mobile operaing systems do so im sure they could.
Click to expand...
Click to collapse
Yes good point.
My main thing was just that after reading some articles on the topic everything was so glum. Like saying there may not be many more updates. In which i think i would hesitate to buy another product from them if they offer that up as an excuse and quit supporting updates and just move on to the next/ better phone.
From what ive read it really seems like the options are 1. Quit Developing new stuff, or 2. Give root to everyone and move stuff over to the SD. (Maybe im wrong but i think they would need to give us root to move the stuff to the SD).
They could possibly do it by the size of the SD card for the normal user. If its one gig, maybe just apps. If its 8 then apps, cache, audio resources, etc. That would be accpetable IMO.
I need to read up up i have no idea what donut actually is, i have cyan 4.01 but never followed the updates so i have no idea what the features are, etc.
Good day!

Ext 2/3/4 whats best?

Ive been using ext3 for quite sometime
And recently decided to go back to ext2 because on certain ROM's
It doesnt utilize the journal node or some S**t like thats
Therefore making some loadtimes of Apps2SD faster.
Now im having regrets form doing so.
Im currently running Cyanogen 4.2.3.1
With an ext2 for apps
Ive noticed a little increase in speed for apps loadtime
But not much of a bigdeal
Right now im trying to find the out which is the best for all ROM's in the longrun. So that my card wont have cross link device errors as fast it usually would.
So im making a final descision today.
I was considering ext4 but its sorta new
and many Devs dont have support for ext4.
So who has any ideal on which is best, down the line i have a class 6 sd card.If that helps in anyway on the descision.

4 or at least 3. all devs have support for ext3 and it is the standard

Have you used ext4?? And in your opinion. You think its better.

I've tried all of them, and settled on ext4. None of the ROMs I've flashed were incompatible, didn't have any other issues with it. By the way, in theory journalling should make the filesystem more efficient, not the other way around.

Does cyan support ext4??
I looked but didnt search lol
i was thinking of staying stable for awhile
then when hero eclair drops and gets stablenessness or when cyan gets the source code decide to mess with eclair.
I guess ill go with ext4 for now any last opions??
lol

Yes, CM builds support ext4. When asked which filesystem Cyan used on twitter he said ext4...

Well thanxs Adrain
Your a real help

[Q] Why is switching from RFS to ext4 such a big deal for Samsung?

Just wondering. Switching from eg. FAT32 to NTFS is no big deal in Windows, and I just can't understand why it is a problem in this phone. Could somebody explain?

Been having the same question. I'm pretty sure Samsung engineers are browsing these forums for feedback about the leaked firmwares. Haven't they realized that RFS is the biggest issue the phone is facing?
P.S: Is it because its difficult to completely format the internal system to EXT2/4 and still preserve the existing data? Just thinking aloud!

They have invested money to develop it. They probably have a roadmap for it. They cannot dump it, just because its first version is underperforming. It is more possible that they will fix it than dump it.
I don't think its the biggest problem. We can replace the filesystem ourselves. The biggest problems are JIT and GPS.

huxflux2003 said:
They have invested money to develop it. They probably have a roadmap for it. They cannot dump it, just because its first version is underperforming. It is more possible that they will fix it than dump it.
I don't think its the biggest problem. We can replace the filesystem ourselves. The biggest problems are JIT and GPS.
Click to expand...
Click to collapse
Well in my case, Lag IS the biggest problem. I don't use GPS much, and JIT doesn't really show real life performance increase for day to day usage (

Simple.
Pride.

Karupan said:
Well in my case, Lag IS the biggest problem. I don't use GPS much, and JIT doesn't really show real life performance increase for day to day usage (
Click to expand...
Click to collapse
Install lagfix. Fixed.

huxflux2003 said:
They have invested money to develop it. They probably have a roadmap for it. They cannot dump it, just because its first version is underperforming. It is more possible that they will fix it than dump it.
I don't think its the biggest problem. We can replace the filesystem ourselves. The biggest problems are JIT and GPS.
Click to expand...
Click to collapse
If RFS is what I think it is (ReiserFS), then Samsung hasn't invested anything in it. It's an outdated formatting system that isn't in popular use in most modern Linux systems. Reiser4 is in development as it's successor and EXT3 and EXT4 are more far more widespread in terms of usage.
Clearly it's not very efficient for this phone since such a simple change as moving to EXT4 can more than double the speed of the phone. Boot times and turning off is so much quicker, as is the media scan that it would seem to be a no brainer to switch.
If Samsung releases Froyo with RFS and we continue to see such a huge performance jump by moving to EXT4, then I'm sure the majority of visitors to this forum will do so.

Ivegottheskill said:
If RFS is what I think it is (ReiserFS),
Click to expand...
Click to collapse
Wrong, no relation to ReiserFS!

Ask samsung
[email protected] - Madan Ankapura - Samsung Staff Engineer. Goto person for all technical issues related to Android within Samsung and interface for Google in the role of Technical Account Manager-Android.
[email protected] - Yanjun Huang - Smart Phone Product Strategy.

Ridiculous File System, then?

morvaeldd said:
Ridiculous File System, then?
Click to expand...
Click to collapse
lol, since it's based on fat32+journaling it may be true!

shivankit said:
[email protected] - Madan Ankapura - Samsung Staff Engineer. Goto person for all technical issues related to Android within Samsung and interface for Google in the role of Technical Account Manager-Android.
[email protected] - Yanjun Huang - Smart Phone Product Strategy.
Click to expand...
Click to collapse
Nice information.
Rather than flooding their mail boxes, why don't we write a formal open-letter in the name of XDA developers Community exposing our findings and suggestions?
Any volunteer? (my english is not so good)
Please note that I'd not approve a letter that is based on insults or describes this product as "rubbish"... I'd prefer they understand that we may have a win-win cooperation in order to make this (and others) product better. So if we're going to expose some problems we'll need to document every problem in a technical way.

borchgrevink said:
Just wondering. Switching from eg. FAT32 to NTFS is no big deal in Windows, and I just can't understand why it is a problem in this phone. Could somebody explain?
Click to expand...
Click to collapse
This is a very wrong statement. It took Microsoft 3 versions of Windows OS (NT 3.5, NT 4.0, Windows 2000) to get a stable NTSF and each NTFS is not compatible with each other.
Sent from my GT-I9000 using XDA App

morvaeldd said:
Ridiculous File System, then?
Click to expand...
Click to collapse
I believe this would be the official name

Nope.. The actual name is "Retarded File System"
True story!

Robust File System is the official name.
It is designed to minimize data loss on power failure and also prolong NAND life. NAND specific file systems are a big research topic at the moment, since depending on the file system design and operation the solid state elements can die earlier.
I sure hope we don't fry ours with the lagfixes we install.

Roy Ngan said:
This is a very wrong statement. It took Microsoft 3 versions of Windows OS (NT 3.5, NT 4.0, Windows 2000) to get a stable NTSF and each NTFS is not compatible with each other.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Cannot see why this is wrong. On a XP system there is no problem just switching to/fro NTFS/FAT32.

borchgrevink said:
Cannot see why this is wrong. On a XP system there is no problem just switching to/fro NTFS/FAT32.
Click to expand...
Click to collapse
Because XP had the "final" version of NTFS.
I guess Samsung is sticking to RFS because they don't want to compromise data integrity.

huxflux2003 said:
Robust File System is the official name.
It is designed to minimize data loss on power failure and also prolong NAND life. NAND specific file systems are a big research topic at the moment, since depending on the file system design and operation the solid state elements can die earlier.
I sure hope we don't fry ours with the lagfixes we install.
Click to expand...
Click to collapse
Good point. But so far we are using the Internal and External SD cards which use FAT32, so using ext2 or ext3/4 shouldn't be a problem, especially with ext2 which has no journalling.
I'm thinking that there must be some good reason why Samsung are using RFS, and maybe RFS is not as crappy as we think. Been tweaking the io schedulers and also the mount options to see if tuning can make RFS acceptably un-laggy.
I mean, Samsung are using the kernel default relatime mount option! Simple changing it to noatime would improve performance - I'm trying that now.

I think the main problem is the user being us.
The newer FWs work pretty smoth IMO, especially compared to the early / stock builds.
This IS enough for average joe. The difference is that many of us are power users, demanding more of the device than 80-90% of the rest of the people using the device.
Changing anything can cause new errors and furthermore takes focus off other things.
Take into account another issue: Shareholder value maximisation.
Many people forget this in light of IT perfection, I as an economist simply can't.
Looking at it from an economic perspective it makes perfect sense to focus on the GPS issue that applies to normal users probably as much as to power users than implementing JIT for higher scores as most people with a Galaxy S wont even know what JIT is.
Don't get me wrong. I am not denying that there is a problem, I am just saying that in a broader perspective it might not be as big a problem as many of us IT perfectionist might believe.

Nook color: worst of all worlds?

Came across a funny older article on a fruit based website about the nook color when it first came out. After reading it i couldnt help but chuckle.
This was the best part of it,
But unlike forthcoming Android tablets like the Samsung Galaxy Tab, this device is going to be locked down and will only be able to run a limited number of B&N-approved apps such as Pandora and Lonely Planet.
Click to expand...
Click to collapse
lol
Its a good read for a laugh.
I know that my nook color countinues to amaze me with more and more functionality everyday.
Its amazing what xda devs can accomplish. Take something and make it do something it was never meant to do and do it better than its competition.

That article is an unfortunate example of what a lot of tech journalists are doing these days. Hastily research a new product, then clip together a bunch of other coverage and bang out an article. By demonstrating his technical incompetence, sure he's got egg on his face now after the fact, however he also represents a large (the majority) percentage of B&N's customer base. The average purchaser would says "rooting what now?".
Amazingly, the NC has proven wildly popular and B&N's top selling item EVER, so obviously even with the limitations the author describes it's trouncing the competition. For those of use who know about ADB and scripts/img files, hey it's even better. Bought one for myself, then for my Dad (50's, tech savvy still). I rooted it, installed xeam and some apps then wrapped it back up and bang, best Christmas present ever!)

I've had a book 3g and then the NC which i rooted. Bottom line it rocks!!!!
Sent from my NOOTED NC using XDA App

I cannot wait for a fully functional froyo rom for the internal memory that will make this a true tablet
Sent from my DROIDX using Tapatalk

sp1kez said:
I cannot wait for a fully functional froyo rom for the internal memory that will make this a true tablet
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Forgot Froyo. Gingerbread CM7. It's going to be B-E-A-UTIFUL

nicbennett said:
Forgot Froyo. Gingerbread CM7. It's going to be B-E-A-UTIFUL
Click to expand...
Click to collapse
Name 5 things that Gingerbread does better than Froyo....
Anywho, I too look forward to a tablet-friendly custom ROM.. I still really like the status bar on the bottom of the screen, but the stupid B&N shortcut thing gets on my nerves when I'm typing.

khaytsus said:
Name 5 things that Gingerbread does better than Froyo....
Anywho, I too look forward to a tablet-friendly custom ROM.. I still really like the status bar on the bottom of the screen, but the stupid B&N shortcut thing gets on my nerves when I'm typing.
Click to expand...
Click to collapse
You mean aside from the better Dalvik VM, better battery management, improved UI, improved hardware capabilities (improved camera handling, gyroscope, NFC), improved game API, improved audio API, new media (audio/video) support, and a new linux base kernel? I guess if you don't count those, you still have the new/updated core libraries, updated bluetooth stack, improved text selection, built-in VOIP, and of course, the better keyboard...
Seriously, i mean, really seriously, why would ANYONE have anything against getting the NEWEST OS? All our efforts should be on gingerbread, since it offers the most compared to Froyo. Its not like moving to GB has any shortcomings, so why NOT want it?

I just got my nook color last night - I've found BBuy that had it in stock about 50 miles and drove there - sure enough about 20 were on the shelve - forgot to mention I traveled actually from one state to another (about 50 miles) to get it right of the shelve ... so anyhow, I am happy with "locked" nook color has to offer - I am even more thrilled about rooting it soon and unlocking the full potential. NC here I come

Yeah, a lot of the reviews bemoaned its alleged "doesn't know what it is" status. I've rooted mine, OC'd it, isntalled dozens of apps and games. Yet I still use it primarily to read novels, and do some light web browsing. And for that, it's dead perfect.
In other words, even an unrooted NC is an outstanding gizmo. I mean that screen is just to die for.

I definitely love my Nook. People are always surprised when I tell them it was only $250. Froyo on teh emmc via dd ftw! It's much better than the stock OS.

rjsmith2007 said:
I definitely love my Nook. People are always surprised when I tell them it was only $250. Froyo on teh emmc via dd ftw! It's much better than the stock OS.
Click to expand...
Click to collapse
IN regards to emmc Froyo - what about the lag? I guess it may just be my SD card, but every Froyo build i have tried, has been painfully laggy - not slow, but things like gmail can take 1-2 minutes to actually show the mail. The app drawer animations are also oddly slow. Does emmc really make Froyo more usable for you?

Divine_Madcat said:
IN regards to emmc Froyo - what about the lag? I guess it may just be my SD card, but every Froyo build i have tried, has been painfully laggy - not slow, but things like gmail can take 1-2 minutes to actually show the mail. The app drawer animations are also oddly slow. Does emmc really make Froyo more usable for you?
Click to expand...
Click to collapse
Oh GOD yes. There is no lag on eMMC. Typing this comment to you on my Froyo'd NC right now

Divine_Madcat said:
You mean aside from the better Dalvik VM, better battery management, improved UI, improved hardware capabilities (improved camera handling, gyroscope, NFC), improved game API, improved audio API, new media (audio/video) support, and a new linux base kernel? I guess if you don't count those, you still have the new/updated core libraries, updated bluetooth stack, improved text selection, built-in VOIP, and of course, the better keyboard...
Seriously, i mean, really seriously, why would ANYONE have anything against getting the NEWEST OS? All our efforts should be on gingerbread, since it offers the most compared to Froyo. Its not like moving to GB has any shortcomings, so why NOT want it?
Click to expand...
Click to collapse
No, I agree that Gingerbread has small incremental improvements, but nothing that'd cause me to say screw Froyo, wait for Gingerbread. Especially if Gingerbread on the NC is well off.

khaytsus said:
No, I agree that Gingerbread has small incremental improvements, but nothing that'd cause me to say screw Froyo, wait for Gingerbread. Especially if Gingerbread on the NC is well off.
Click to expand...
Click to collapse
I guess what i am thinking - given that Gingerbread is already being worked on, and our Froyo build doesn't actually work that well, why not just move ALL the resources out there to GB, and the most recent right away. Why go incrementally?

Divine_Madcat said:
I guess what i am thinking - given that Gingerbread is already being worked on, and our Froyo build doesn't actually work that well, why not just move ALL the resources out there to GB, and the most recent right away. Why go incrementally?
Click to expand...
Click to collapse
I'd agree with that.. If the effort is the same for both, go with Gingerbread. However so far we have Nookie Froyo which is "mostly" there and I haven't heard of Gingerbread on the NC at all.

Just to add how amazing this gadget is I'm typing this comment using SlideIT and it has taken mea fraction of what it used to.
Sent from my rooted Nook Color

khaytsus said:
I'd agree with that.. If the effort is the same for both, go with Gingerbread. However so far we have Nookie Froyo which is "mostly" there and I haven't heard of Gingerbread on the NC at all.
Click to expand...
Click to collapse
WEll, there is a gingerbread branch that is being worked on here: https://github.com/fat-tire/android_device_bn_encore
And there is plenty of talk that CM7 is on its way (though, i admit that i still fall into the see it to believe it camp). http://forum.cyanogenmod.com/topic/11127-nook-color/page__st__40
But regardless, the froyo build really isn't that usable - its laggy, market is like sludge, etc. I really think that the devs working on it, should take the froyo lessons, and focus totally on GB. Let froyo be the sandbox for others to learn on, and let GB be the first real OS upgrade for the NC.

[Q] Nook Honeycomb starter

Honeycomb on Nook is awesome, the work done here is impressive. Congratulations!
I want to try it out, giving a Nook Honeycomb, and use it instead of a Moto Xoom (it's impressive, but I doesn't need the big screen, HDMI, cameras, dual-core CPU...)
what I need is a small tablet so that I can:
# browse and read news etc.
# use Gmail
# watch a few videos (YouTube or files)
# maybe read e-books (Kindle, B&N)
# run various small apps (maybe some games) - from Android Market
And I want:
# 6" or 7" display
# low weight
# long battery life
# WiFi
# 3G through a Bluetooth connection to my phone
# and low cost
Thats not an 800 USD Xoom for that. But a Nook with HoneyComb!
I'm not a developer but a relatively technical user, so I'm not afraid of buying a Nook and try out some stuff.
But I have som questions and would like some input. I may have misunderstood things and I apologize for stupid questions.
First decisions/questions:
1; what is eMMC? I can see that I should choose between SD or EmmC, so this is probably a fairly basic decision.
2; I gather I need to choose which port of Honeycomb to use. Right? (I have listed a few below).
3; it appears to be possible to either boot Android Honeycomb from the SD-card. Does that mean I can use the Nook as it was delivered if the SD card isn't present?
4; Is there any other basic decisions I need to take?
There's lots of posts here, and I've been reading back and forth, and from what I see this is what I need:
# get a Nook
# get a microSD card. Is there any recommendations?
# get a Honeycomb image/build. Could be:
-http://forum.xda-developers.com/showthread.php?t=936995 by deeper-blue
-http://forum.xda-developers.com/showthread.php?t=925451 by dalingrin
-http://forum.xda-developers.com/showthread.php?t=954902 by phiredrop
# overclock the Nook to 1 or 1.1 GHz
# Disabling B&N OTA updates (or is this done automatically?)
# Dualboot?
# Installing various apps
# Network using Bluetooth - how?
Is this too deep water for me or should I plunge in?!

I personally think that you should dive in. Now first emmc is the name of the nooks internal memory.
I would recommend buying one and first using a micro SD to boot honeycomb and decide if you want to run it. It's a great port and great os but its not prime time yet on the nook.. I use it only, and even with its faults it is too 'tablet friendly' for me to switch.
YouTube is tricky at best. Ill let someone with more experience post about it. In my experience it's not real reliable for some reason
Sent from one of those missing Droids

I love my nook color, and it has a bright future. But u mentioned you wanted 3g and Bluetooth. Those are not available as of yet on nook color. I'm not sure if it has those internal components or not.
But it is a very capable device. Mine is setup comparable to the galaxy tab I would say, after rooting it and adding a custom rom.
Sent from my Droid using Tapatalk

Thanks for the answers so far!
I can live without 3G/BlueTooth.
And I can live without YouTube. That will probably fixed along the way.
Is the current Honeycomb builds based on a prerelease SDK or is considered a final release?

Caspar07 said:
Thanks for the answers so far!
I can live without 3G/BlueTooth.
And I can live without YouTube. That will probably fixed along the way.
Is the current Honeycomb builds based on a prerelease SDK or is considered a final release?
Click to expand...
Click to collapse
You can't use bluetooth for data, but you could certainly tether your nook to your smartphone. That's what I plan to do when I find myself without a wireless connection.
EDIT: Oh and you could visit the actual youtube website if you have flash installed (on a 2.2 or higher ROM).

Definately dive in. Buy a few microSD cards. Start by rooting the stock firmware and play with a launcher and the market. It's the most stable.
Install Honeycomb on an SD card and boot it. It's not bad but will be much improved in the next few weeks.
No bluetooth yet but you can wifi tether to your phone if your phone supports it.

BanditRider said:
Start by rooting the stock firmware and play with a launcher and the market. It's the most stable.
Install Honeycomb on an SD card and boot it. It's not bad but will be much improved in the next few weeks.
No bluetooth yet but you can wifi tether to your phone if your phone supports it.
Click to expand...
Click to collapse
"Rooting stock firmware"?
Does that mean sort of copying the firmware, so You can restore later?
Again: good replies, much appreciated

To get you started.
At $250, the Nook Color sucks as an eReader. But as an android tablet, its the best purchase you could make. Nothing else comes close. Some notes on your comments.
1. The Nook Color(NC) has a boot priority to the microSD card, making it nearly impossible to 'brick.' I'd reccommend having two sd cards. A good class 10 one for your daily use, and a cheap 1gb one to keep a copy of clockwork recovery for quick repairs.
2. The bluetooth doesn't work, even though the device has the hardware. At this point, there is no speculation of it working in the forseeable future. HOWEVER, it works great using the WiFi hotspot on my HTC evo.
3. The device will run android 2.1 (eclair), 2.2 (froyo), 2.3 (gingerbread), and 3.0 (Honeycomb). All four have their issues. I've tested them all thoroughly, and prefer the standard 2.1 (also called stock NC) build for its stability. Feel free to try them all.
IF YOU SHOULD BUY ONE:
Instructions to root
Instructions to build a recovery SD card
Instructions on how to make root stock NC work well for you
Remember these links. They'll save you the hours of time I lost.

YouTube and Flash work perfectly for me on the 2.2 phiremod beta2 rom. I would say it is pretty stable. But if one is new to root they should just get used to rooting first. We are also over at androidtablets if you need help http://www.androidtablets.net/forum/nook/
The above link for rooting seems broken. Here is the NookDevs links http://nookdevs.com/NookColor_Rooting *edit nevermind it's working sorry

Thank you
I've not yet done any recover steps after auto nootering a few weeks ago. This is going to help me go do these steps this weekend.
Tethering is going to be something i need come summer vacation where there's no connection any place, i have the MOTO Droid, and PDANet, so i'll try that some day soon, see if it holds up.
admiralnorman said:
At $250, the Nook Color sucks as an eReader. But as an android tablet, its the best purchase you could make. Nothing else comes close. Some notes on your comments.
1. The Nook Color(NC) has a boot priority to the microSD card, making it nearly impossible to 'brick.' I'd reccommend having two sd cards. A good class 10 one for your daily use, and a cheap 1gb one to keep a copy of clockwork recovery for quick repairs.
2. The bluetooth doesn't work, even though the device has the hardware. At this point, there is no speculation of it working in the forseeable future. HOWEVER, it works great using the WiFi hotspot on my HTC evo.
3. The device will run android 2.1 (eclair), 2.2 (froyo), 2.3 (gingerbread), and 3.0 (Honeycomb). All four have their issues. I've tested them all thoroughly, and prefer the standard 2.1 (also called stock NC) build for its stability. Feel free to try them all.
IF YOU SHOULD BUY ONE:
Instructions to root
Instructions to build a recovery SD card
Instructions on how to make root stock NC work well for you
Remember these links. They'll save you the hours of time I lost.
Click to expand...
Click to collapse

You need to use an Adhoc method to tether droid to autonootered nook I believe. It doesn't work as is right off the bat with a 2.1 nook color and droid1.

Caspar07 said:
....But I have som questions and would like some input. I may have misunderstood things and I apologize for stupid questions.
First decisions/questions:
1; what is eMMC? I can see that I should choose between SD or EmmC, so this is probably a fairly basic decision.
2; I gather I need to choose which port of Honeycomb to use. Right? (I have listed a few below).
3; it appears to be possible to either boot Android Honeycomb from the SD-card. Does that mean I can use the Nook as it was delivered if the SD card isn't present?
4; Is there any other basic decisions I need to take?
Click to expand...
Click to collapse
I was in the same boat... wanted a tablet to do pretty much what you are looking for... after reading the threads here, I got a Nookcolor...
1.. eMMC is the Nook's internal memory, where its current/stock B&N OS and apps are stored and run from. If you wanted to use a "custom rom" like Froyo, Gingerbread, Honeycomb, you could install it to eMMC, overwriting the stock B&N stuff... BUT you don't have to.
2. Right now, the honeycomb ports out there are based on the Pre-Release SDK (software dev kit), and made to work on an actual device, i.e. the NookColor. Because of this, it has some limits and bugs. The best HC Ports will come once HC goes AOSP (hopefully soon since the XOOM, which uses HC, is now for sale).
3. The NookColor is setup to try and boot from MicroSD card first, and if no OS on MicroSD, then boot off the eMMC. So, you could load up a card with another OS, play with it, and NOT TOUCH the stock B&N stuff... just pop the card in when you want to boot the other OS, and pop it out when you want to go "stock" (that is what I'm doing now).
This also means you can make up a MicroSD card strictly for the purpose of recovering/reloading the OS on your NookColor if something goes wrong when trying to install an alternate OS to the eMMC. (i.e. helps you "unbrick" your device).
Note: when getting a MicroSD card to boot an alternate OS from, its generally better to get a higher class card as they are usually faster (means the OS runs faster/smoother). But some of the lessor known brands often don't live up to their class ratings. And there have been issues with some people getting certain Class 10 (fastest) 16gig cards, so you'll have to do some home work, searching and reading the threads to decide on which card to buy.
4. You have many choices to make. Do you want to run stock B&N os/firmware (Eclair/2.1) as is out of the box? Do you want to root the stock OS and add your own apps? Do you want to try one of the Froyo (2.2), Gingerbread (2.3, the CM7 builds) or Honeycomb (3.0) ports and do you want to run them from MicroSD (slower) or eMMC (faster)?
While Wifi works with each Froyo and HC build I've tried, Bluetooth doesn't work with any of them.
Each port of Froyo, Gingerbread and HC has its own positives and negatives, so you have to investigate and figure out which one works best for you as a daily driver.
Me, I left the stock B&N NookColor OS and Apps untouched, and loaded up one MicroSD (Sandisk 8G class4) with Froyo following this thread -> http://forum.xda-developers.com/showthread.php?t=922324
And I loaded up another MicroSD card using the HC Preview v4, but it didn't meet my needs, so I'm waiting on the AOSP of HC to try again.

admiralnorman said:
...
3. The device will run android 2.1 (eclair), 2.2 (froyo), 2.3 (gingerbread), and 3.0 (Honeycomb). All four have their issues. I've tested them all thoroughly, and prefer the standard 2.1 (also called stock NC) build for its stability. Feel free to try them all.
....
Remember these links. They'll save you the hours of time I lost.
Click to expand...
Click to collapse
Great help - thanks.
Still one question:
Is lack of stability in Honeycomb due to the fact that it's still early and very new, or is it due to incompatible hardware?
This is getting increasingly interesting

Caspar07 said:
Great help - thanks.
Still one question:
Is lack of stability in Honeycomb due to the fact that it's still early and very new, or is it due to incompatible hardware?
This is getting increasingly interesting
Click to expand...
Click to collapse
Not really. Its kind of a developer's platform. So its made to run on a generic android device. As the programmer type people around here play with it, it gets better and better.
Sent from my HTC Evo 4g using XDA App

KidJoe said:
I was in the same boat... wanted a tablet to do pretty much what you are looking for... after reading the threads here, I got a Nookcolor...
...
And I loaded up another MicroSD card using the HC Preview v4, but it didn't meet my needs, so I'm waiting on the AOSP of HC to try again.
Click to expand...
Click to collapse
Thanks for the lengthy answer. That was a helpful explanation.

Caspar07 said:
Great help - thanks.
Still one question:
Is lack of stability in Honeycomb due to the fact that it's still early and very new, or is it due to incompatible hardware?
This is getting increasingly interesting
Click to expand...
Click to collapse
The devs currently do not have the Honeycomb source. What exists now has been pieced together from the emulator and is glitchy. Once they have the source (which should be soon as the XOOM is out now) we should begin to see improvements in HC roms.

Also, please recognize that not everyone has stability issues. I've been running the initial version of Sam's "flashable" Deeper Bulue image for 2 weeks, and don't have any stability issues.
It really depends on what apps you want to run. I have market working fine, with lots of apps downloaded. I did the ADHOC tweak early on, and can connect to wireless networks pretty much at will.
I read quite a bit, and spend a lot of "nook time" using it as an eReadr. I've worked my way through a number of books using the B&B Reader, Kindle, and Aldiko without any issues.
It's not a "production" image, but for me it works well.

admiralnorman said:
The bluetooth doesn't work, even though the device has the hardware. At this point, there is no speculation of it working in the forseeable future. HOWEVER, it works great using the WiFi hotspot on my HTC evo.
Click to expand...
Click to collapse
Just got an execuse to buy myself a new gadget - a HTC Evo or similar

"Is the Nook Color the right Android tablet for me?"
I think the easiest way to answer this question is by how much you enjoy tinkering with things. If you want a tablet that "just works" then you'll want a Xoom or Galaxy Tab. But if you love playing and learning about how your gadgets work 'under the hood' then the Nook Color will be the best gadget purchase you've made in awhile.
I've honestly spent more time "getting it to work perfectly" than I have actually using it, but I've loved every minute of it. I won't lie, Java and/or Linux experience is a big plus, but by no means necessary.

admiralnorman said:
At $250, the Nook Color sucks as an eReader. But as an android tablet, its the best purchase you could make. Nothing else comes close.
Click to expand...
Click to collapse
I just bought a Nook Color about a half hour ago and this post made me feel so much better about it. I've been debating it for some time and decided to take the plunge. I was worried that I might be late to the game but it has only been out for like 3 months.
Can anyone point me in the direction of Honeycomb for the NC? EDIT: Unless someone recommends a better ROM for now?
By the way, my name is Raj and I'll be spending lots of time here!