yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] leapinlar:
CM10 uses uImage and uRamdisk to load CM10. And uRecImg and uRecRam should load CWM. And uAltImg and uAltRam should load B&N stock. These are all files that are in your emmc boot partition. You can look at your boot partition by getting the NookColorUMS app from my tips thread linked in my signature. Use the CM9 version, it works on CM10. Instructions are on my thread.

Installing a new ROM on primary replaces your normal boot files (uImage and uRamdisk), but does nothing to the other boot pairs. Putting a new CWM on emmc will have no effect on booting to your alternate partition. It puts the new CWM on the recovery position (uRec). Your alternate files (uAlt) should remain unchanged.

The boot menu that comes with CM10 looks different than CM7, but works exactly the same way. Just select position 1, 2 or 3 for what you want.

So I don't know what you mean when you say you cannot use the boot menu to get to CWM.

Edit: I think I now know why you have a problem with getting to your alternate. If you look at taosaur's thread you will see there are instructions for renaming his boot files so they work with the new boot loaders.

Sent from my Nook HD+ Running CM10 on SD
[Nook Color Android Development] Dave08:
@WoodmanMN, does your NC have an ES1.1 CPU revision? You and I seem to be the only ones currently reporting SODs. I have an ES1.1 device and after fixing permissions it ran without any SODs under steven676's 1217 test kernel for about 36 hours, going through multiple sleep cycles of varying lengths. I started thinking my NC was cured until 2 SODs occurred this evening. Loving CM10 on my NC, so I wish I could figure this SOD issue out!

Running 1216 nightly.

QIOCM9DXBED; 12/19/2010

ES1.1

cyttsp

Interactive / BFQ
[Nook Color Android Development] pastordl:
Fixing permissions, best way?

A number of times in this forum we are instructed to "Fix permissions" I know how to do it. My question is this: Is one way better than others?

I know of the following ways:

1. In rom manager detailed listing of what it does but requires a reboot.

2. In CWM no detail and again requires a reboot.

3. In TWRP/ADVANCED goes faster than CWM, requires reboot, & goes do fast i wonder if it is really doing anything..

4. Fix Permissions app. Only set up to do one app at a time. Great if you know which app is messed up, otherwise not much help.

5. Busybox fix permissions script, a little faster than rom manager, no reboot required, does provide a log afterwards.

Is one way better?

Do they "Fix" them differently?

:confused:

Puzzled
[Nook Color Android Development] bobdole:
16gb sandisk micro sd for $10

Any one who's have problems because of inferior sd card, here's one day only deal to get sandisk class 4 micro sd for $10 (free shipping)

1saleaday.com/flash/tbf-16gb

You may have to create an account to see this deal.
[Nook Color Android Development] grayfoxmg1:
Now I'm not sure if I'm right. And the only thing I have to base my answer on is my personal experiences and what I took away from them. I've always felt that when 'fixing permissions' within a recovery (CWM/TWRP) it was more efficient at things related to the booting of the ROM. However on the other side of the coin, an in ROM method (rom manager, an app, or a script) was better at dealing with how apps run on your ROM. An example is, whenever I get bootloops I tend to run 'fix permission' from within twrp. If I am having FC's than I do it within the ROM. Now I've never sat down and looked to see if one way was better than they other, or even better for the things I've talked about. It's just how I've always done it, granted I could've been doing it wrong the whole time. If someone else knows than I would listen to them over what I've said.
[Nook Color Android Development] hwong96:
To isolate the cause of sod install cm10 with just GApps and let it cycle through a few deep sleep cycles. If no sod add one app and let it cycle through a few deep sleep cycles. Repeat process for each app you have. It is a lengthy process but you will find the cause.
[Nook Color Android Development] Dave08:
Fix permissions in recovery so messing with running processes is avoided. TWRP is faster than cwm because it's been rewritten in c++.
[Nook Color Android Development] leapinlar:
I've looked at the log that CWM leaves behind when it is fixing permissions and it looks like it works on the files in /data/data which is where all apps (including system apps) store their settings and files they need to operate. So basically I think it is making sure those files are readable and writable by the right groups. So if an individual app is acting up, it might not have its file permissions set right. And when apps load at boot time those files are read and permissions matter then too.

So, I don't know which is the best, but I would think in recovery would be best because those files are not open or being used then.

Sent from my Nook HD+ Running CM10 on SD
[Nook Color Android Development] steven676:
That's unlikely to help -- crashing the entire system or failing to resume from sleep is by definition a kernel bug, not a userland one.

We're examining ways of potentially being able to get more information off (the small minority of) SODing devices -- in the meantime, sit tight. Sorry, don't have anything better to offer at the moment.
[Nook Color Android Development] pdahiker:
I did a CyanDelta (great tool, by the way) update from 20121219 to 20121220 yesterday, and it seems to be OK. I sense a "slight" bit of sluggishness compared to 20121219, but it may be my imagination. CyanDelta reported minimal changes to this build. I am going to run with this for a few days before moving to a newer daily.
[Nook Color Android Development] skwalas:
I'm getting a bit annoyed by all the different setting suggestions flying around for performance. So... I have a week offline coming up and thought I'd do a bona fide experimental design to actually answer this. So I'm putting out a request for any all suggestions on settings to evaluate (i already have a list of 16 of them) and more importantly suggestions for measuring performance. Benchmarking apps seem to focus on CPU speeds etc. anything out there that can measure latency and such?
[Nook Color Android Development] newellj79:
Building question.... I build for my nexus 10 based on what in learned in this thread when I used to build for my nc. I recently started using the use_cache=1 option too. This changes by build time from 4hours (made clean) to about 10 minutes. Is this normal? And two, the output .zip is always named with the date of my first build and does not change like when I build from scratch. Example, I built today (22nd), and the output is called cm-10.1-20121219-UNOFFICIAL-manta.zip, is this normal? Thanks!

PS... I can't find any build help in the nexus 10 forums :(
[Nook Color Android Development] webyrd:
Running cm-10-encore-kernel-v3.0.8-4066-g845dfa4.zip flashed over the 12/20 nightly, no SOD's or problems since the evening of 12/20.

MSBN QI0CM9PJ23L

DATE 12/25/2010

CODE OMAP3630 ES1.1

CYTTSP

OMAP3ISP REVISION 15.0
[Nook Color Android Development] WoodmanMN:
How do I find out which revision on on? I'll look out up and post.
[Nook Color Android Development] webyrd:
See the 4th post for this thread

http://xdaforums.com/showpost.php?p=32905957&postcount=4
[Nook Color Android Development] WoodmanMN:
Thank you. I did do a search and found it. I am on es1.1

---------- Post added at 09:53 AM ---------- Previous post was at 09:48 AM ----------

I have a nexus 7 under the Christmas tree, so I am using the nook as my only tablet. My dog dumped coffee in my laptop, so until I build up a new one from a few spares I have in the office, my only large internet device is the nook. Thus I roll back to 7.2 when I start having issues and upload a more recent nightly when I read about big changes.

Once I open the nexus, I can devote the nook to testing purposes.
[Nook Color Android Development] unicyclingEMT:
All you need to do is delete the build.prop file from your $OUT/target/product/manta/system/ directory before building.
[Nook Color Android Development] Kaptinkrunk:
All is good on this current build

Nook Color CM10 Dec 21 Inverted Everything!!
[Nook Color Android Development] steven676:
The changes in this kernel should be included starting with the 12/22 nightly -- there's no need to flash this over a 12/22 or later nightly build.
[Nook Color Android Development] meteorrock:
My build is still holding up good, no SOD to report. Just some slight lag on opening apps, but its not too bothersome. Thinking about flashing another nightly just to see how the builds are coming along, kind of worried with the reports in here. Might flash here in a day or two to the most recent CM 10 nightly.

Got tons of apps loaded up now on this nightly I listed below, got most apps blocked for internet access and other network access for the apps that do not need internet access to function. There is some sort of correlation with apps calling up internet access for ads, and other permissions that is bogging down CM 10 from my understanding and experience.

No other outstanding bugs to report on my nook using CM 10. Noticed the screen brightness will not adjust in settings, but that is about it.

NOOK COLOR:

ADW EX 1.3.3.7 Launcher

Here is my specs on the motherboard: QI 11M98TD6K

Date of manufacture: 01/18/2011

OMAP: OMAP3isp : Revision 15.0

Touchscreen: FT I2C Touchscreen driver

Governor: interactive

I/O scheduler: noop

Kernel sampage merging

OC 1100MHZ

CM 10 12-10 V6 supercharged, Lucky patcher for apps.
[Nook Color Android Development] FloydF:
That might explain why my nook became completely unresponsive while reading wired this morning, 12/22 nightly. It did get worse over time as well as with more tabs. Tried stock, chrome, dolphin and opera. Didn't seem to matter. After a while it became so bad I had to reboot. Certainly could be ad related, wired is packed full of them.

Any tip on most stable cm10 nightly? Leaving for 3 weeks in Australia, need something reasonable for the flights. Real books are way too heavy and I haven't been able to sleep on a plane since I wrecked my neck 20 years ago...
[Nook Color Android Development] grayfoxmg1:
download either aurora, firefox, or firefox beta and install adblock in the add-ons menu, it seems to help with my internet usage on PA.
[Nook Color Android Development] lollyjay:
X scope pro seems very responsive.

QI0CM787SV, 12/11/2010

ES1.2, cyttsp

PA Encore 2.99 16DEC2012 nightly
[Nook Color Android Development] stolenmoment:
I've observed this in a few apps; judging by a performance change after buying the paid version, I suspect that the simplest way to add ads to an app is by fetching them in the main thread and thus blocking for network activity, a bad design choice.

I don't see this one in the nightlies.
[Nook Color Android Development] Starphish:
Dumb question... How do you block net access per app. Thanks!
[Nook Color Android Development] WoodmanMN:
So those of us with an es 1.1 device, should we even bother with the cm 10 nightlies since the kernel doesn't seem to like the older processor revision?
[Nook Color Android Development] MechaGen:
Can't than you Dev's enough. Please keep up the great work.

Flashed 20121223 dirty this morning, and all is well. Not a single SOD, on the charger, on battery, WiFi on or off. Most responsive that CM10 has ever been.

QIOCM9DMV3X, 12/23/2010

ES1.1, cyttsp,

20121223 on eMMC

Phone UI, LCD Density=240

Nova Prime, Dolphin w/Jet Pack

SD Card= ADATA 16gb C6

---------- Post added at 09:31 PM ---------- Previous post was at 09:27 PM ----------

Don't give up yet. I feel like this ROM is getting really close to be stable.
[Nook Color Android Development] WoodmanMN:
I backed up my cm7.2 and flashed 1223. Running on par with 7.2 for now. Will see how she does over a day or so.
[Nook Color Android Development] Dave08:
She's using the Lucky Patcher app. It's not on the Play store, but you can find it by Googling it.
[Nook Color Android Development] doncaruana:
Been running CM10 on an es1.1 for over a month now through multiple nightly revisions and have yet to have an SOD. Try running it a little more vanilla and see if the SOD goes away. I've even been OC'd at 1100 since it became available.

MainboardSN: QI0BMXXXXXX

DateManufactured: 11/30/2010

CPU: OMAP3630 ES1.1

Touchscreen:Cypress TrueTouch
[Nook Color Android Development] Lakland:
I am having battery drain during sleep. I left nook on 81% battery and in the morning 63%. It never went to deep sleep. Any suggestions? I am running 12-23 nightly
[Nook Color Android Development] hwong96:
Turn wifi off during sleep.
[Nook Color Android Development] MechaGen:
I have to agree. With WiFi off my NC didn't sleep well last night. CPU Spy says 43% % 300, and 42% @ deep sleep.
[Nook Color Android Development] Lakland:
I set wifi to turn off during sleep
[Nook Color Android Development] WoodmanMN:
Not sure how much more vanilla i can get. I never use alternate kernels, haven't oc'ed past 1000 since i discovered that broke play store on my device. I don't use patch programs, anything to modify the system. Pretty much just dolphin browser, some games, email, and the xda app. Not pushing it hard, and don't flash unless i see a fix. I notice sod doesn't show up till a day or two in, generally after a reboot.
[Nook Color Android Development] RBMacGregor:
The system only rebuilds changes from your previous build. It might not take long at all. I also noticed that my build date didn't change last build for my nexus 7. I did a "make clean" command and started over it took a while but build date was correct. I thought the issue was from what ever crazy stuff I changed.
[Nook Color Android Development] lollyjay:
Are you running from SD or emmc?

QI0CM787SV, 12/11/2010

ES1.2, cyttsp

PA Encore 2.99 16DEC2012 nightly
[Nook Color Android Development] Dave08:
I'm having exactly the same experience on 1223.

Same here, except I'm running Firefox browser. CPU governor is interactive, I/O is BFQ. ES1.1, rom installed on emmc.
[Nook Color Android Development] WoodmanMN:
Emmc, I don't like running from sd
[Nook Color Android Development] lollyjay:
These SODs and other problems don't seem to have a common thread. I really respect all the time and effort of both developers and testers on this.

QI0CM787SV, 12/11/2010

ES1.2, cyttsp

PA Encore 2.99 16DEC2012 nightly
[Nook Color Android Development] Lakland:
I am having random reboot. Without any reason, running any app, the device reboots itself. Thi happends since 12-21 nightly
[Nook Color Android Development] steven676:
To be clear, these random reboots happen with 12/21 and later nightlies, but not with 12/20 or before? Also, are you overclocking?
[Nook Color Android Development] Lakland:
It happends from 12-19 but is very rare. I am not overcloking max cpu= 1000 not 1100
[Nook Color Android Development] majorpay:
Some interesting information that may, or may not, be pertinent to the development of CM10 for the Nook:

I too have noticed the flickering screen when charging, but my issues don't stop with the flickering screen. During prolonged activity while plugged in, the nook exhibits signs of erratic behavior. The touchscreen appears to be completely out of whack with frequent phantom touches, and touch placement becomes severely offset. This could be due to the charger, but I have my suspicions with the odd screen behavior when plugged in that it may also have to do with the current screen drivers? Early on in the revisions, I did not experience any of these issues. Just a thought. Perhaps some work has been done on the host mode over the past month?

Upon unplugging the Nook, everything resumes as normal. Phantom touches and erratic behavior disappear.

Anyone else having similar issues, or is this most likely connected to a faulty charger?
[Nook Color Android Development] Homer_S_xda:
This erratic behavior when plugged is has been around from day 1, even with stock firmware. IIRC some people stated a new charging cable cured it and others did not.

Homer
[Nook Color Android Development] majorpay:
Known electronic defect... good to know. Never seen it until now, and I've been with this thing a few years now, so this may be a sign of age for mine.
[Nook Color Android Development] SacTappingUni:
I've experienced this too. I don't remember it being a problem with stock firmware. I noticed it somewhere up the road when I had already been using cm7 for some time. I have no idea why it does that. I also have never really noticed a flashy charging screen, even though it had flashed when I was turning it off/on when it was in alpha. It might still do that. I just can't really tell because I have a leather screen cover as part of the case. The case looks like a book; my nook is the pages.

Also, Merry Christmas.
[Nook Color Android Development] derekr:
Just to confirm that Bluetooth is working (within limits) on CM10 - at least at a distance of about 6 inches :)

My daughter gave me a GOgroove Blue Sync OR3 Bluetooth speaker for Xmas. It paired up right away and has been working on Internet radio all morning. It gets flaky at about 1 foot away but otherwise works just fine! Not bad for a device without an antenna.

Incidentally, it's an excellent little speaker for the price. 5 stars...
[Nook Color Android Development] jyeley5:
Running great for me! One thing though that greatly improves fluidity is disabling the very-bytecode. Mod here:http://xdaforums.com/showthread.php?t=1263119
[Nook Color Android Development] pdahiker:
I have been looking at that speaker and may give it a go.

I can also confirm that my Zippy Mini bluetooth keyboard is working better with this ROM than it ever did with Gingerbread. Distance was at least a few feet and it set itself up with no difficulty.

I am still running the 20121220 build on an ES 1.2 version Nook. Has been rock solid for 5 days now.
[Nook Color Android Development] Lakland:
Using 12-23 nightly. Is running very smooth and is almost side by side with my p3113 running ics 4.0.4. Will check 1225 nightly :)

---------- Post added at 04:35 AM ---------- Previous post was at 03:54 AM ----------

1225 is even better. I just using my nook more than the samsung p3113 :p:D
[Nook Color Android Development] khaytsus:
The RIM with the kernel fixed around 12/18 (in night lies since 12/22) is fine on my daughters es 1.1 from 12/2010
[Nook Color Android Development] aeturnus77:
Been running the nightlies for the past month, no SODs in maybe 5 days? Had been having them daily or more prior. Just installed 12/25 a few min ago, hopefully it'll have more of the same! Overclocked at 1100, deadline, disabled zram.

Just saying :) happy holidays
[Nook Color Android Development] meteorrock:
I reverted those file changes on the github for that USB host. Hopefully that will take care of that flashing problems you guys were having, if it was related to that at all.

Going to wait and test that USB host .ko before I publish anything on the git, guys. Anyway, I am having "hypervisior" problems, might have to do a dual boot on my machine with this "linux mint" I am using for the git. Lost sound yesterday, looks to be related to using a hypervisor after checking up in the linux mint forums, and I want to build allot of programs I want on this machine from scratch. No .debs for them.

Also getting some email down in the cyanogenmod forums from nervous old hens about me being on the git. Without knowing how to write code, I don't think I will get that .ko to build anyway. Just tried yesterday. That USB host kernel is still in skeleton code, looks to be a premade kernel from the linux 3.2 branch you guys ported over. After downloading a hundred packages to build, I am still getting errors to download more.

Right now I am building apps on linux mint for video recording and such, and looking to download tons of packages. Playing around with that so do not worry. Might try again here in a week or two, but it looks to be a long shot. We need someone that knows how to write code up for that USB host mode driver.

TL;DR

Merry xmas and happy holidays. :)
[Nook Color Android Development] FloydF:
I have had this erratic behavior with the touch screen as well, but clearing the cache (both)has always resolved it, fortunately. The flashing while charging I have not noticed, but have not looked yet either. Worst problem is when using team win recovery. Sometimes touchscreen just stops responding and I have to reboot, which can be bad I think, for the partitions if I read correctly.
[Nook Color Android Development] Dave08:
Running 1223 nightly, no SODs since I had two during the first two sleep cycles after flashing the rom. Also, getting normal deep sleep after that first night. No touchscreen problems. No lag problems. Thanks devs.

ES1.1, interactive, BFQ, no overclock.

Update: had to reboot today (12/28) and, sure enough, had a SOD during the first sleep cycle. It always seems to follow that same pattern.
[Nook Color Android Development] timmyjoe42:
I experienced this same thing on my LG G2x when I was using certain after market chargers. When I switched back to using the official LG charger or my old Motorola ones, everything worked fine. Are you using the stock nook color charger and cable?
[Nook Color Android Development] J-ROCK:
I'm happy to report that I haven't had any SODs in about a week since running the test kernel a few post back. I also had to set my WiFi to

Shut off when asleep after 15 minutes.
[Nook Color Android Development] pmgnet:
no SOD

I'm also not getting SOD now. I'm running nightly from just a few nights back.
[Nook Color Android Development] Whoareyou:
is there a way to connect to an ad hoc network??
[Nook Color Android Development] moocow1452:
Can I connect a bluetooth keyboard to the tablet with this rom. Got one for Christmas, and been having trouble, wanted to know if it was the keyboard or the tablet.
[Nook Color Android Development] pdahiker:
I had no problem pairing my Zippy mini bluetooth keyboard, in fact it was easier with this ROM than ever before.

Not sure about the procedure with your keyboard, but typically, you turn the Nook's bluetooth on, and then turn the keyboard on. In the Nook's bluetooth settings you should see the keyboard broadcasting - then select it on the Nook. Sometimes, it is necessary to enter a code on the keyboard, and do not forget to press enter after entering the code. Depending on the keyboard, the code could be "0000" or "1234", or in some cases, the Nook may give you a code to enter. Forgetting to press enter after entering the code is something I have done in the past.
[Nook Color Android Development] moocow1452:
The keyboard is junky then. Thanks for the help, but even after it gets paired, it can't get a signal. Ah well.
[Nook Color Android Development] hwong96:
Exchange for another one. I went through four BT keyboard/case for my 10 inch tablet before I got a good working one. Quality control is nonexistent on these items.
[Nook Color Android Development] Lakland:
I am having this random reboots. JUst happend a few minutes ago. I just see the cyanogen booting logo, without any apparent reason. Also still having the nook not going to go to deep sleep. IT stay awake, althought i configure the wifi to turn off...

ANyone having the same issue?
[Nook Color Android Development] Starphish:
Not exactly, but after an overnight charge (WiFi off), my NC won't simply turn on. Usually I have to hold the power switch down for 5 seconds (maybe 2 or three times) and then the Cyanogen ferris wheel pops up (not cyanoboot), and things get back to normal shortly after the animation runs. I have no clue what that is all about. I'm going to drop back to 12/10 and see if that clears things back up.
[Nook Color Android Development] Lakland:
I am that strange behavior since version 12-6
[Nook Color Android Development] Lakland:
I install 1227 nightly. All good but in the notification drawer, the icon that clears notification messages are besides settings icon.
[Nook Color Android Development] derekr:
@lakland - the Changelog for 1227 states that they fixed the layout of the status bar for mdpi.