yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] meteorrock:
Well, when I was lurking up here last year waiting for the CM 7.2 going from a fresh nightly to Release candidate, it took around 3 to 4 months for the nightlies getting rebuilt on cyanogenmods mainframe computers to reach that point. And another month to get stable. This is an approximation. Seemed to take forever. It works by straighting the algorithms relationships from the kernel to the framework Java layer, keep in mind this is a crude allegory on my part, I have not done lots of research yet into this.

How long for this build? I can not say, could be a tad longer because of the complexity of the JB code? Might add a month onto that

For how many mainframe computers they have? And the size of it? I am not certain. I know if they had yet another mainframe computer the wait time would approximately be cut in half. So I would assume they only have one?
[Nook Color Android Development] grayfoxmg1:
how'd you make your color's purple?
[Nook Color Android Development] meteorrock:
Did an up-flash to CM-10-20121124

I was experiencing some random lags once and awhile while using the Opera browser between 2 and 3 seconds with the CPU red-lined and the RAM hitting 50 MB. Using the settings on the app "cool tool" to check CPU and the RAM caches.

It was getting kinda annoying. My experience is that the build CM 10 11-18 was too flaky for my daily driver. Did a "dirty" flash, just wiped dalvik caches upon upgrading through ROM manager into CWM.

For those running mods like the V6 supercharger you will have to reapply your OOM memory settings, I lost mine upon flashing. My modded services.jar was still intact, so I did not have to reapply my services.jar. Found that my launcher was still supercharged upon upgrading. All of my other settings stayed intact. My I/O scheduler was still set at <noop>. Still OC at 1100mhz.

~~~~~~~~~~~~~~~

I can already feel the build tightening up through touch responses. Seems just a weeks time the build is strengthening up. Apps opening up are becoming slightly quicker, if only by a few milliseconds, just enough for me to tell its getting better. Been looking over this build for just an hour though. I will report back in a day or two on more results.

NOOK COLOR:

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

CM-10-20121124
[Nook Color Android Development] himasura:
Holo purple theme.
[Nook Color Android Development] 1800collect:
Possible bug, or possible user error on my part.

Settings > System > Status Bar

I selected "Brightness control" which allowed me to swipe my finger across the status bar to control the brightness.

I then went to:

Settings > System > Notification Drawer > Widget Buttons

I selected "Toggle Brightness"

I then swiped down the status bar and used the toggle brightness button. I cycled through the settings and it eventually selected "Automatic Brightness" the one with an "A" in the icon.

Now I can't turn off Automatic Brightness. If I go into Display > Brightness the Automatic Brightness checkbox is not selected. But I can't select it either. If I keep pressing the Widget Button in the Notification Drawer it just cycles brightness but the "A" is constant.

I can't swipe across the status bar to control brightness any longer.

When I go back to

Under Settings > System > Status Bar

"Brightness Control" is grayed out but checked. It says "Automatic Brightness is enabled" but I can't find any option to disable Automatic Brightness.

So this could just be user error and I can't find the setting to disable it. Or I stumbled across a CM10 bug.
[Nook Color Android Development] leapinlar:
Not being able to turn off automatic mode has been a problem with several ROMs including CM7 and CM9, even on my Galaxy Tab. The only way I found to clear the problem is to edit the settings database with SQLite Editor. I don't remember the exact setting, but when you look it is obvious.
[Nook Color Android Development] thejrcrafter2:
Home button bug

Hi,

I found a bug:

If you shutdown the nc with the lockscreen disabled, then when you turn it on the home button will not work until you re-enable the lockscreen. (After you re-enable it, you can disable it again.) If you boot with the lockscreen enabled, though, you are fine.

What I mean by "not work":

Pressing the home button (hard or soft) will just flash the screen then go back to the app you were at, not the home screen. Sliding up on it to get to GNow does not work either.

Sorry that I can't help fix the bug, I don't have a 64-bit computer.
[Nook Color Android Development] ZeikHunter:
Just installed the 11-25 nightly on 2 NCs a friend bought for his kids. followed the guide: http://xdaforums.com/showthread.php?t=1030227

now both report service failures (systemUI, etc) on boot. what did i do wrong?
[Nook Color Android Development] jsmith8858:
I have the lock screen disabled all of the time and never had any problems with the hard or soft home keys not working after rebooting. Running latest nightly.

Could this be a problem with your launcher?
[Nook Color Android Development] micl9:
Its been so long ago that I rooted mine I am afraid I cannot help.

I can tell you that the nook is virtually brick proof. So you can tell your friend you WILL fix it... eventually.

Keep searching and reading, then ask more questions.

Good Luck
[Nook Color Android Development] leapinlar:
Ask on that thread. You might get a better response. He just updated it to CM10. This thread is for bug reports to the ROM itself.
[Nook Color Android Development] ZeikHunter:
thanks. I'm updating my personal NC from cm9, gonna see if i can reproduce it. it's not a showstopper, but still...

mine updated like a champ. time to read up in that other thread.

EDIT: apparently I didnt wipe the system partition. ID10T error on my part.
[Nook Color Android Development] lowsnamebrand:
Might want to just put cm7 on them for stability reasons and upgrade to 10 when stability improves it what I had to do with my so my girl could use it
[Nook Color Android Development] leapinlar:
I agree, for kids you want CM7.
[Nook Color Android Development] tamasrepus:
local.prop changes not sticking

Is anyone using local.prop settings to do things like change DPI? I put

qemu.sf.lcd_density=213
ro.sf.lcd_density=213

into local.prop, rebooted, and my DPI unfortunately had not changed.

This worked in CM9; it doesn't appear to do anything in CM10. Modifying/adding the same settings in /system/build.prop does work, however—but changes there are wiped out on ROM update.
[Nook Color Android Development] leapinlar:
Yes it works, but you only want that first line, not the second. And you did not say, but you want to put that file in /data.
[Nook Color Android Development] les02jen17:
I'm about to update to Nightly 11-25. I just need to ask a quick clarification: would I do the "wipe /cache and dalvik cache" BEFORE or AFTER flashing an update? (Or BOTH?)

(and should I also add fix permissions?)
[Nook Color Android Development] leapinlar:
Does not matter, just do it before you boot. And only do it once. And if you wipe dalvik cache there is no need to wipe cache. The only reason to wipe cache is to clear the dalvik cache that is a part of cache. And it does not hurt to fix permissions, also before boot.
[Nook Color Android Development] meteorrock:
My build is doing good for CM-10-20121124-NIGHTLY

No SOD to report, still have my wifi set to always off in sleep mode though.

CPU is not red-lining to 1100mhz with the memory not dumping in RAM while using multiple apps , on this build I was able to get some memory over to the RAM , hit almost 170 mb at one time with three apps open at once, had a music app open along with a torrent app and a browser open all at once, very minimal lag now for me, with the CPU scaling down like it should to the baseline 300mhz after a few seconds. Using the app "cool tool" to check on these resources.

Touch screen response is now a hit or miss sometimes, sometimes I have to grind on an app for it to open. Just a slight nuisance. Other times it works fine. Haven't noticed any other outstanding bugs so far, very nice work by the developers on these JB builds. I captured a logcat of me grinding on the Opera icon in my home screen so the devs can go over it for the touchscreen response times. Logcat set in debug mode.

~~~~~~~~~~~~~~~

NOTE to LURKERS: To those learning how to read logs: Note in my log where I tested the wifi to a router not set up in my JB build for the password for the nook color in the logs. Can you find the lines? It works good btw. Can you also find what launcher I am using?

The Opera browser in run mode is working superb.

Still OC up to 1100mhz, I believe I have now found my daily driver for awhile. Since this build is working so good for me at the moment I will wait a few weeks before up-flashing.

There is an easter egg for the developers as an wmv file in there too. Close your eyes :)) ROFLMAO ugggh those logcats capture EVERYTHING.

NOOK COLOR:

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

CM-10-20121124 V6 supercharged.
[Nook Color Android Development] les02jen17:
what the heck were you watching? maybe that's why you were getting lags. :cool:
[Nook Color Android Development] bobstro:
Given the subject matter, did you even notice all those skipped frames?
[Nook Color Android Development] RoboticBuddy:
The battery life is still poor, it goes down to ~70% on idle/sleep.
[Nook Color Android Development] bobstro:
Over what period? Battery consumption does seem higher than CM 7.2 (~12%/hr versus ~10%/hr. in use with wifi on), but on sleep, mine appears to be about the same (using the Nov 21 nightly). Do you have wifi set to turn off with the screen?
[Nook Color Android Development] 1800collect:
What do you mean "run mode" is there a different mode to run Opera Browser? I've noticed Opera Mini is super quick compared to Opera Browser, but for some reason the app will go all black and be unusable when I leave it and try to come back later. So I stick with Opera Browser, but if I could make it load pages faster that'd be sweet.

Also, how do you take logs?

I noticed at times my clicks don't register. I put on "Show touches" in "Developer Options" under "Settings". So I know when I actually click, but nothing occurs in the OS. . At times I'll click the Home button and if it isn't direct center it won't work. But it shows me the press was made, but it won't highlight the home button icon and won't do the command.
[Nook Color Android Development] RoboticBuddy:
Oh sorry, it goes around 70% after 4-5 hours, with WiFi on.
[Nook Color Android Development] Divine_Madcat:
BTW, (no one in particular), this is still a dev thread. We need to make sure that the devs get useful feedback, and that general chatter be taken elsewhere. It is simply more work on the devs if they have to fish through conversations to find info that can help you.. ;)
[Nook Color Android Development] ibilln:
-All- devices drain battery if wifi on during sleep. Goto wifi, options, advanced, and set to "never". But you probably know that... So, I don't see the issue.
[Nook Color Android Development] thejrcrafter2:
according to the latest xda-tv post, someone started working on cm10.1 (android 4.2). Any body going to start working on that, or are we going to wait until we get this stable first?
[Nook Color Android Development] leapinlar:
You can build it right now if you know how to build. A couple of users have done it. The rotation was screwy though.
[Nook Color Android Development] thejrcrafter2:
Okay, I guess I'll start a thread for it. Would we be able to build it off of this rom or do we need top build from scratch?
[Nook Color Android Development] lekofraggle:
I think you have to build from scratch. The build environment should be the same.

Sent from my NookColor using Xparent Cyan Tapatalk 2
[Nook Color Android Development] meteorrock:
Run mode: An operational mode of the CPU of a PLC that allows the system to run, but no changes can be made to the program.

Sorry for the confusion, I misspoke. For android its called <activity android:launchMode = ["standard" | "singleTop" | "singleTask" | "singleInstance"] ../>

There is an app on the playstore to go over this, here is the link for it. It is what I use. Its called <Activities LaunchMode demo> https://play.google.com/store/apps/details?id=com.novoda.demos.activitylaunchmode&hl=en

~~~~~~~~~~~~

I am just taking logs through an app called alogcat from the playstore.

I don't think the mods want too much chatter in here so I will sit back for a bit. I sure hope you guys know what you are doing. I thought we were supposed to be debugging and helping the developers??
[Nook Color Android Development] ajrty33:
Thank you. You've spewed a lot of buzzwords that make no sense. FYI the cyanogenmod algorithms are interfacing nicely with the mainframe java layers.
[Nook Color Android Development] meteorrock:
Deleted. Found out nookie devs in other thread are working on it.
[Nook Color Android Development] abreeden:
*You're
[Nook Color Android Development] Divine_Madcat:
Everyone knock it off. I mean, right after my post about keeping this dev oriented, you all have to go and fight. I shake my head at all of you, and remind you that this IS a dev thread, and to keep it that way..
[Nook Color Android Development] gardndj:
I've been experiencing a freezing issue since beta 4 (including 5 and now the nightlies). Full data/cache wipe on install to emmc. Consistently freezes on the CM bootscreen, makes no difference if plugged in to AC or not. Sometimes takes 4 or 5 tries to boot to a functioning system. After that the Nook will eventually freeze as I'm using it, probably within the first 10 minutes and doesn't seem to matter what I'm doing or which app I'm using. Have tested using a clean install (no additional apps added). Did not experience this issue with cm7 or cm9 and don't recall seeing it on the earlier alphas/betas. Haven't seen anyone else with the issue so it may simply be my hardware. Hope someone can help, enjoying jellybean otherwise.

ES1.1

cyttsp

Logcat - http://db.tt/dpMQ9rpc
[Nook Color Android Development] leapinlar:
Try going back to an early beta, then after boot flash the new nightly over it without a wipe. In other words a dirty install. That helped with mine. Then unless you are having big problems, only wipe dalvik on future flashes. Sometimes on my system a clean install does that.
[Nook Color Android Development] gardndj:
Attempted with beta 2 and the latest nightly. Got through initial boot and app update without flaw but now it's back to the same freeze/reboot cycle. Good idea though.
[Nook Color Android Development] leapinlar:
Another thing to try is go to recovery and fix permissions.
[Nook Color Android Development] gardndj:
Also a negative.
[Nook Color Android Development] leapinlar:
Try an experiment. Use your root file manager (there is one built into CM10, all you have to do to make it root is change a setting in the app's settings/general) to create and delete a temporary file somewhere on /data. See if it will.
[Nook Color Android Development] bytte:
I don't claim to understand this all but noticed:

W/MediaScanner( 2368): Error opening directory '/storage/sdcard1/.android_secure/', skipping: Permission denied.

Is your sdcard healthy, is it full etc?

If nothing obvious I suggest you try a new one.

(I boot from SD, so not certain sdcard1 is external in your case - someone here will correct me if necessary)

QI0CM9NNWEC

12/26/2010

ES1.2
[Nook Color Android Development] leapinlar:
You have a good point. What I was trying to lead to is CM10 seems to be very touchy about both /data and sdcard. If it thinks anything is wrong at all with them, it remounts them read only. Which would be indicated by that error you just quoted. If he had apps installed to SD, then sdcard being read only would lead to the symptoms he was having. Same with /data. Some users have these problems, others don't.
[Nook Color Android Development] J-ROCK:
Don't know if this is helpful but when I do a clean install of a nightly I wouldnt get any SOD's . When I start introducing my backed up apps with TB on my freshly installed rom I start getting the SOD's. So to make a long story short I narrowed down what app was causing my SOD and it happened to be my Google + app so I removed it. Now it wakes up without any issues on the same nightly. Don't know if it'll help just sharing my experience.
[Nook Color Android Development] Peoplephobic:
Has anyone noticed slow network performance when using the 11/26 nightly? Not on the Nook but on the rest of the network when the Nook is on.
[Nook Color Android Development] thejrcrafter2:
I'm assuming no 11/27 nightly? Are we getting an 11/28 or are we stopping for some reason? I have noticed some screw ups with get.cm though so that might be why.
[Nook Color Android Development] fulanito01:
Was having very sluggish performance with a dirty install over beta 4 (nightly 11/18 via cm update i believe). Since then, went in to revovery and wipe data,cache,dalvik,battery stats, and flashed nightly 11/25 and performance has been phenomenal. With WiFi sleep on, I no longer have SODs, system is almost "cm7 snappy", and with light use I'm on day 3 with over 80% battery remaining. I've avoided restoring apps with titanium on this build.

I'm still uncertain of the slow network performance. Definitely had that issue with beta 2 and it was resolved with the updated WiFi drivers zip provided in this thread. Will report back if I see anything.
[Nook Color Android Development] gardndj:
I am able to write/delete from /data using the built in file manager. The sd card being at fault was actually one of my first thoughts, so I've already tried swapping in a different one and running without one completely. Same results.
[Nook Color Android Development] RamblingBarba:
SOD after Cyandelta update to 25th

I went from the nightly 24th to 25th using Cyandelta and immediately had SOD. I power cycled it and tried again, same results. When it went to sleep it SOD'ed. I have kept WiFi on Always since Beta3 through the 24th never had a SOD. My region is set to Europe (default I guess) but I live in South America. I reverted back to the nightly from the 24th and am back to full time WiFi and no SOD on wake. I am on emmc and OC'd to 1100 with interactive governor.

Any ideas? I figured I would hold out for a week or two and give it another try.
[Nook Color Android Development] tamasrepus:
Hrm, still not working (i.e. putting settings into /data/local.prop) for me on the 20121126 nightly… at least not the DPI setting.

What local.prop settings are you or others using that do work?
[Nook Color Android Development] leapinlar:
Try a different value. Maybe it does not like 213. Try 240 just to see if it works. 213 is non-standard.
[Nook Color Android Development] nfreebairn:
BBQ tools prompted me to update gapps to 1121 and it didn't do well for me. Playstore would not connect and multiple apps closed. The version you speak of has zero issues.

---------- Post added at 11:20 PM ---------- Previous post was at 10:29 PM ----------

Thanks everyone for all the hard work. Running latest nightly superfast and with no issues. After some tweaks is just as responsive as 7 ever was. Ran v6 supercharger ... die hard settings so I can still longpress kill. Noop on the I/o. Disabled dithering. Enabled 16 bit trans. Changed the launcher to apex. Replaced search with quicksearch. Processor set to interactive and animations at .5x. Force gpu 2d rendering. Running smooth as hell. No complaints.

Slows down if dithering on and 16 bit trans off but still runs. Getting prompted to update gapps from BBQ tools but that broke everything but luckily I had a backup I could restore.
[Nook Color Android Development] meteorrock:
Did an upflash just to see how the nightly builds are coming along. Flashed the cm-10-20121129-NIGHTLY

Did not apply any speed script mods to this build, feels smooth enough now to forgo them. Been having the problem of my builds slowly degrading over a few days, that was what happened to my last build. Started out super smooth and fast, then the UI will start to experience some lag. Still not bad, its usable but I just like to experiment now. Still beats 7.2 in speed, if not for stability, for me at least.

Still at 1100MHZ overclocking, with the governor at "interactive." Did a fresh install on this by wiping data and all caches. Last two builds were a dirty update.

~~~~~~~~~~~~~~~~~~~~~~~~~~~

Wanted to try the "memory management" settings in the performance options on this build without applying mods, I will report back in a day or two to see how it runs with them. I allowed the purging of assets and kernel sampage merging, seems to help speed things up just a bit. Went with 18 percent zRam.

Still not using 16 bit transparency nor the surface improvement, my build seems fast enough without opting in on those options.

I included a logcats of these settings for the other developers to go over, seems the I/choregrapher is skipping less frames now on use. Some I/Activitymanager lines in this log.

NOOK COLOR:

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

zRAM 18 percent

Kernel sampage merging

cm-10-20121129-NIGHTLY
[Nook Color Android Development] bobstro:
You sure are sharing a lot of data with flurry.com, 'Rock: D/FlurryAgent( 8754): Sending report to: http://data.flurry.com/aap.do. Is that an app you loaded doing that?

For the developers, I am not sure if there is any useful information I can provide, but I'm happy to try to replicate results on a mostly-working and stable device if that's of any help. Things are working pretty well on my NC:

I did a complete reset and wipe to load CM10 using the Nov. 18 nightly. I noticed general slowness at that time. I've updated using nightlies since, wiping Dalvik cache each time and performance has been improving. Google Chrome was unusable, but other browsers were acceptable. I loaded Cyandelta a few days ago, and have updated twice using it with default settings with no apparent problems. As of today (Nov. 29), overall performance is good and Google Chrome is even usable, though slow. I have only noted one SoD over the last week, as well as the occasional flicker while powered off. [EDIT: The modified Netflix works well enough to be usable. HBO Go stutters too much to watch.]

Battery life is close to what I experienced with CM 7.2: About 10% per hour using the device with wifi on, about 1-2% per hour with screen off and wifi policy set to Keep Wifi on during sleep - Only when plugged in, Wi-Fi idle timeout - 5 minutes. I have set my region to to United States (correct for my locale).

Twice, I have experienced loss of wifi connectivity, fixed by rebooting the device.

Overall, my experience has been "GOOD".

I am running:

CM 10-20121129-NIGHTLY-encore

300 MHz min/1100 MHz max

Interactive governor

bfq I/O scheduler

zRam disabled

Allow purging of assets enabled

Kernel samepage mergin enabled

16bit transparency enabled

Surface improvement default (fix banding)

I'm not sure if experiences using nightlies were desired in the survey, but here's my data:

# cat /rom/devconf/MainboardSN

QI13M9J5R09

# cat /rom/devconf/DateManufactured

04/01/2011

# dmesg | grep OMAP

OMAP3630 ES1.2 (l2cache iva sgx neon isp 192mhz_clk )

# dmesg | grep ft5x06

ft5x06_init() - FT I2C Touchscreen Driver (Built Nov 29 2012 @ 03:25:46)

can't get ft5x06 xreset GPIO

# dmesg | grep cyttsp

input: cyttsp-i2c as /devices/platform/omap/omap_i2c.2/i2c-2/2-0022/input/input2
[Nook Color Android Development] thorin:
Flurry is an analytics engine that is used by tons of app developers. I am not surprised how much data is being sent.
[Nook Color Android Development] rkleinhenz:
I think you meant 11/14/12