yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] Lakland:
Thanks. Is a waste of space toput that in there. Fat fingering now touh both buttons :D
[Nook Color Android Development] pckoloji:
same. harder to touch there.
[Nook Color Android Development] bytte:
It is difficult to accurately touch within 50 pixels of the edge of the screen. Its been like that since 7.2, but you can now turn on tracking of touches so you can see exactly where your touch is registering. I looked at the code ages ago, and found that it is intentional, presumably because it can't register a touch at the edge.

I'm thinking it would be better with no 'acceleration', and just accepting that you can't touch within a couple of pixels of the edge.

Seems this is likely to be a common touchscreen problem, but I don't have any other touchscreen devices to test. Has anyone played with the code? Do others find it annoying?
[Nook Color Android Development] christiankk:
I am getting frequent SODs with the latest version. I'll fill in the details later.
[Nook Color Android Development] deboyz1014:
Do a full system / data / cache /dalvik wipe if you are running into issue even if you are coming from the previous nightlies. That was an issue I was running into but now its running fine after full wipe. Antutu average is 2300 with interactive and bfq, I also reccommend getting volume+ to boost volume. I got the paid version and it is making a huge difference
[Nook Color Android Development] macrossmerrell:
Have you tried downloading the Nook Touchscreen recalibrator from the app market? That fixes that problem for me every time.

Merrell
[Nook Color Android Development] bigbob23:
I am getting deep sleep with wifi turning off, but the battery drain is still higher than I would expect. 1227 nightly.
[Nook Color Android Development] Lakland:
1225 nightly is the most smooth and fast. I will keep this one for a while. Thanks devs for your hard work
[Nook Color Android Development] deesto-xda:
I hadn't turned the Nook off in a while, so I don't know when this might have started, but while running the 12/28 nightly, I turned off the unit last night, and it wouldn't turn back on this morning until I plugged it in, at which point it turned on on the first try. The battery was at about 40%.
[Nook Color Android Development] bytte:
In the past (CM10 Beta) I have had a BSOD recovered by connecting the charger.
[Nook Color Android Development] deesto-xda:
Right: I've seen that some people have had a SOD. But this is not the same, I don't think: I had turned the unit off with no problem, and it wouldn't turn back on.
[Nook Color Android Development] deboyz1014:
Same thing happen on cm 7.2 so is not just cm10 issue.
[Nook Color Android Development] deesto-xda:
Perhaps, but not for me: it hadn't even been a CM 10 issue for me until this build.
[Nook Color Android Development] ParMaster:
I'm running the latest CM10 nightly and its working beautifully. Although

It seems to run a bit slow at times...

I bumped the max CPU up to 1100 but left the governor in ONDEMAND to see if that might help a little. To be honest its probably because I've been installing all my just tons of apps from the cloud to it. I'll give it a reboot and let it just run effortlessly for a good 15 minutes.
[Nook Color Android Development] Lakland:
Here my current battery drain graph,
[Nook Color Android Development] ParMaster:
One thing I have noticed is that sound volume is incredibly low out of the headphones jack compared with CM7. Tried everything to do with sound including the DSP with no luck. It seems at least 10 times quieter than under CM7
[Nook Color Android Development] jh1521:
Damn... after running my own 10/15 build (the one with OpenGL enabled) without any major issues for about 4 days, I cam across an instance of SOD myself. I left the nook sleeping for over 12h with the battery low (about 30%), then it wouldn't wake up, despite the backlight turning on. It still wouldn't wake up even after connected to the power adapter and left to charge for a while. I powered it off and rebooted. It looks fixed for now, but I'll see if I can reproduce this circumstance.
[Nook Color Android Development] sturmavik:
Sweet ROM once again. Totally smooth and way nicer than the CM7 ROM I had on my NC. Haven't had a single problem yet. Almost a shame to call this an alpha. Saved my NC from a life at the bottom of the junk drawer.
[Nook Color Android Development] dparrothead1:
For everyone still having SOD every time, I found a temp solution until our Devs get it fixed. I d/l Wake Lock from the Play Store and set it on "partial". This keeps the CPU from sleeping and I am able to wake it from the power button, volume rocker and the "n". I disable the app when I'm not going to be using the device for an extended period of time.
[Nook Color Android Development] stwallman:
Got it installed on my Nook and looks good so far...is there a recommended video player that can handle HW acceleration of MKV files ?

Thanks for all the hard work !!
[Nook Color Android Development] RoboticBuddy:
Your solution seems similar to this:

http://xdaforums.com/showthread.php?t=1366757
[Nook Color Android Development] RallyStyle2003:
I got logs from when this happened. Right after I confirmed sound was back I pulled these.

dmesg: http://pastebin.com/CJ7U4Aui

logcat: http://pastebin.com/aGNN7Cjb
[Nook Color Android Development] grayfoxmg1:
I use MX video player
[Nook Color Android Development] aludal:
It's here too, on my earliest NC (Nov. 2010) with "official" Alpha 1, after 72 hours or so. I hoped it won't happen to mine, but alas!

But it's not bricking my Nookie, so developers get my thank-you anyway.

My SOD happened in a particular circumstance though: I pulled the charging cable out before touching the dimmed screen.
[Nook Color Android Development] stolenmoment:
I'm using this treatment as well. Works fine, but as you'd expect, battery life is terrible.
[Nook Color Android Development] edditnyc:
I was getting SOD only on an AC charge earlier but its also happened off the charge. It's infrequent but I filed my info so the devs have the data. Restarting a ROM in its alpha state from time to time isn't the worst thing in the world, much less a great ROM. Great work y'all.
[Nook Color Android Development] kfxdadev:
Netflix: with changes, audio works (but not video)

Hi,

I strongly suspect the reason Netflix doesnt work has to do with the OMX.TI.Video.Decoder codec. I have a post up in the CM9/CM10 WIP thread (#3212) on how I got Netflix videos playing with audio only (video is still a black screen) by using the google H264 decoder. Hope this helps the devs determine the real issue. I tried my change out on a build newer than CM10 alpha 1, but I think the same change will work (to the extent it can be said to work) on CM10 alpha 1.
[Nook Color Android Development] bcvictory:
Just wondering how do I enable the data usage feature on CM10? It doesn't appear on my nook and it's on my N7. If it's not in this ROM is there any 3rd party app that does the same thing?
[Nook Color Android Development] pavlos46:
Quick question what's wrong with techerrata.com ?
[Nook Color Android Development] libertus77:
What is it doing/not doing?
[Nook Color Android Development] bigrat:
I filled out the survey.

So far, very stable. A touch laggy. No SOD. Wireless stable. Games that didn't work before on any rom (PvZ, for example) work fine now. Read books constantly with FB Reader for almost two days.

Went several hours with wireless on, then with it off. Put device to sleep many times, no SOD. Plugged in while sleeping, wakes the device up, charges normally. Charging seems a little slow, but I don't have numbers to back it up.

I will say I had a heck of a time flashing a new recovery. Semibricked it twice. Almost certainly PEBKAC :D
[Nook Color Android Development] unicyclingEMT:
Looks great and have had no problems so far. Left it running overnight and no SoD. Left it plugged in two nights ago and also no problem. The only problem I've had at all is in reporting my HW details. The link just doesn't seem to want to work for me so I'll post the information here:

SN: QI11m9782AP

Manufactured Date 1/15/2011

CPU revision: 1.2

Touchscreen Type: Cypress

Thanks to everyone for their work on this.
[Nook Color Android Development] olm3ca:
It's timing out for me... and the survey link as well.
[Nook Color Android Development] stolenmoment:
I changed it to wifi full, and I get deep sleep but no SoD, even overnight AC-plugged in. Haven't done much time unplugged and idle yet, so the jury's still out.
[Nook Color Android Development] 98tiburonfx:
The dl link is timing out for me as well.
[Nook Color Android Development] olm3ca:
Perhaps someone can help with a mirror? If that is allowed of course...
[Nook Color Android Development] Lakland:
Same here, volume is very low, but i have not try headphones
[Nook Color Android Development] MrPib:
Yes, it's low to the point of being unusable with my MP3 dock. I seem to recall someone mentioning including the Nook Color Tweaks functionality in the CM10 kernel at some point, which would be great. Until then, I mostly run CM7, which goes as loud as hell.

BTW, Showtime Anywhere works on CM10, but not CM7!
[Nook Color Android Development] deboyz1014:
use volume+ app. I use the paid version caused i like it so much
[Nook Color Android Development] bytte:
The clue could be wifi. Default is always on. Disabling that had me loosing 13% battery in 24 hours.
[Nook Color Android Development] RamblingBarba:
I hate to jinx it but my battery life is great. Today, for example, unplugged at 9AM with 100%-minor web surfing, checking a few social media outlets throughout the day and read on Kindle app for maybe 1/2 hour-5:30PM and I'm at 89%. I am on 12/23 Nightly never had SOD problem. I OC to 1100 on interactive governor with NOOP scheduler. Zram is disabled Both purging assets and same page merging are selected as well as 16 bit transparency.

BTW big +1 for Volume+

EDIT: I have WIFI on all the time.
[Nook Color Android Development] SacTappingUni:
Same here with improved battery life. When My Nook is idle the entire day with low-ish usage, it'll be at about 85% at the end of the day. When I'm playing graphically intensive games like Carl on Duty Black Cops Zombies for hours on end, I can play through for an extremely long time without needing a recharge. That's about 3-4 hours with almost constant gameplay.

I'm starting to love this.

Also, has anybody tried the Beats Audio drivers for the Nook? I heard that it's pretty good on the Nexus 7. What difference does it make?
[Nook Color Android Development] bluepen61:
Beats Audio: Didn't work on CM 10. And it would not install on stock B&N rooted with ManualNooter.
[Nook Color Android Development] ParMaster:
Yeah i'm running the 1229 nightly and out of the blue took out my cable and USB self-powered hub that has a bunch of goodies built-in like audio etc. I used Sztupy's USB Host Controller apk to see if it would tell if anything was there. Amazingly, everything showed up. I heard the clicking of my navigations through my speakers connected to the usb audio device. I hit YouTube and blasted some music through it. Sztupy's app displayed everything i plugged into my hub. It literally showed every usb drive i plugged in as mass storage. Also it did show an enumeration for the ethernet - 'ASIX' or something but when i plugged in the ethernet cable for it i didn't even get Link. I also plugged in an RTL driver based DVB-T and it recognized and enumerated that as well! So after all this fun i plugged in a Hauppage Aero-M WinTV adapter and that must have been all the kernel could take ;) cuz i heard a snap of noise out of the USB audio speaker and CM10 froze completely.

That was the only and last time USB Host Mode actually worked :(.

Why does it only just work once and then never again? Do i need to have it specified in a file inside a specific directory?

I tried echoing "force host" into /sys/kernel/debug/musb/testmode but that didn't help at all. The device doesn't show up in /proc ...

When i check it with Sztupy's app it always shows that USB is in Host Mode. That app wasn't made for this device but it is now irrefutable that it at least partially works on it (sometimes?).

There is no OTG, forget about OTG on this device because of the hardware (pin issue). This is USB Host mode.

The hub i used for checking is the same one i sent Oleg (verygreen) when he was developing for USB Host mode. From what i remember he never did get the ethernet port working.

It is a Plugable model UD-160-A.
[Nook Color Android Development] duane1221:
Bug Report - or lack thereof

Ever since the 12/16 nightly through the 12/23 nightly I have been experiencing SOD's. However, I am happy to report that with the 12/30 nightly I am not getting SOD's anymore.

I did a full wipe of Data, Cache, Dalvik Cache, flashed the 12/30 nightly. Fixed permissions. The restored apps from Titanium back up - apps only no data. I have been using the Nook for most of two days including a sleep overnight, charged it twice to a full charge, rebooted several time just to test and I have not has a single SOD.

Performance config (not changed since flash of nightly) 300 min, 1000 max, ONDEMAND. CFQ I/O. Memory management all disabled 16 bit unchecked, surface improvement unchecked.

I am using NOVA launcher and everything seems to be working well, no issues at all to report so far. Battery life seems good too, although I have not specifically tracked it.

I am not sure what changed since 12/23 but I am running great now,

Thanks to all for the work on this ROM
[Nook Color Android Development] ParMaster:
Ummmm what's with the kernel module hubbub? Obviously the kernel already has support built in or it wouldnt have been working for me when it did. Real OTG will never work on this device just Host mode for USB. LOL you are hillarious :) . Don't touch ANYTHING!!! ;)
[Nook Color Android Development] ParMaster:
Changelog for updates in the Nightly's

Hi All,

I've been following the changes in regard to what is being updated in the nightlys. It looks like nothing has been updated since i last installed 1229:

http://changelog.bbqdroid.org/#encore/cm10/next (Look on the left hand side, you can click on any date (nightly) to see what changes if any)

These appear to be just code merges so far so it's possible that other code has been updated which for some reason isn't reflected in the changelog. I know when i look what the changelog says in CyanDelta it is "get prebuilts: update Term.apk download URL"

Have a Happy New Year everyone!
[Nook Color Android Development] webyrd:
Ran cm-10-encore-kernel-v3.0.8-4066-g845dfa4.zip flashed over the 12/20 nightly, only 2 SODs until flashing 12/29 nightly. On 12/29 nightly had one SOD (while charging) but NC would reboot when charger was first connected. Just flashed 12/31 nightly, can connect charger without reboot.

MSBN QI0CM9PJ23L

DATE 12/25/2010

CODE OMAP3630 ES1.1

CYTTSP

OMAP3ISP REVISION 15.0
[Nook Color Android Development] dombeef:
That is odd because I can't reproduce the usb host mode, even with a powered hub. I am on that same nightly too.
[Nook Color Android Development] Lakland:
1231 nightly is working very good
[Nook Color Android Development] pspTP:
I am currently on CM7 and want to try this out. What is a good stable nightly that I can start with?
[Nook Color Android Development] Lakland:
I am running the1231 nightly on the emmc of my nook. So far is very good
[Nook Color Android Development] lollyjay:
12/31 here or 12/16 on PA in my opinion.

Sent from my NookColor

QI0CM787SV, 12/11/2010

ES1.2, cyttsp

PA Encore 2.99 16DEC2012 nightly
[Nook Color Android Development] pspTP:
Thanks for the feedback. Will try the 12/31 build out.

---------- Post added at 01:38 PM ---------- Previous post was at 01:25 PM ----------

Any links to the gapps that I should use with this? Thanks
[Nook Color Android Development] lollyjay:
Use ONLY the one at the beginning of this thread (GAPPS 121011).

Sent from my NookColor

Tapa talk HD

QI0CM787SV,12/11/2010,ES1.2, cyttsp

PA Encore 2.99,16DEC2012 nightly
[Nook Color Android Development] leapinlar:
Go to goo.im and select gapps-jb-20121011.

Sent from my Nook HD+ Running CM10 on SD
[Nook Color Android Development] charliearthur:
Thanks, this info worked for me :highfive:. Current version (2.1.1) would not open in CM10 1231 nightly but 1.8.1 worked fine.
[Nook Color Android Development] pdahiker:
I will second those saying that 1231 nightly is good. I have been running it for a while and it seems to be snappier than my previous (1225) and no SOD's or other issues.
[Nook Color Android Development] webyrd:
12/31 Nightly

12/31 running very well but have had 2 SOD's, one while charging overnight, one after 4 hour sleep.

MSBN QI0CM9PJ23L

DATE 12/25/2010

CODE OMAP3630 ES1.1

CYTTSP

OMAP3ISP REVISION 15.0
[Nook Color Android Development] Lakland:
Same here ome sod while charging
[Nook Color Android Development] MrPib:
Also got an SOD while not charging.
[Nook Color Android Development] fattire:
FWIW, new wiki means the encore build instructions are now moved there.

Check it out:

http://wiki.cyanogenmod.org/index.php?title=Build_for_encore

Cheers!
[Nook Color Android Development] ggbutcher:
Just tried it, got the following at lunch:

Which would you like? [full-eng] 6
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/bn/encore/cm.mk]]: "frameworks/base/build/tablet-dalvik-heap.mk" does not exist. Stop.
Device encore not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_bn_encore
Default revision: cm-10.1
Checking branch info
Default revision cm-10.1 not found in android_device_bn_encore. Bailing.
Branches found:
gingerbread-release
gingerbread
jellybean
gb-release-7.2
Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback branches.
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/bn/encore/cm.mk]]: "frameworks/base/build/tablet-dalvik-heap.mk" does not exist. Stop.

** Don't have a product spec for: 'cm_encore'
** Do you have the right repo manifest?

I synced cm-10.1 per the instructions; should it have been cm-10?
[Nook Color Android Development] fattire:
If cm-10.1 isn't yet available, re-do the repo init command but put -b jellybean instead of -b cm-10.1. I can change the template for now to reflect that only jellybean is supported... doing that now.

Update: Done. The downside is that encore is designated "legacy" since it's not using the latest version. When 10.1 builds I guess we can lose the special legacy branch designation and go back to active :)
[Nook Color Android Development] ggbutcher:
I went back to the init step and redid it with -b jellybean, proceeded step-by-step from there,and got this for lunch:

Which would you like? [full-eng] 5
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/encore/cm.mk]]: "frameworks/base/build/tablet-dalvik-heap.mk" does not exist. Stop.
Device encore not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_bn_encore
CyanogenMod/android_device_bn_encore already exists
Syncing repository to retrieve project.
Fetching projects: 100% (1/1), done.

Repository synced!
Looking for dependencies
Dependencies file not found, bailing out.
Done
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/encore/cm.mk]]: "frameworks/base/build/tablet-dalvik-heap.mk" does not exist. Stop.

** Don't have a product spec for: 'cm_encore'
** Do you have the right repo manifest?

So, recalling how I did this under your google docs doc, I don't remember running lunch between syncing and extracting the device blobs, but this is the step that's blowing up. Was this handled previously by the local_manifest.xml?

Now, I ran the -b jellybean init on top of the previous sync, should I have cleaned it out? It seemed to back out things appropriately, and subsequent repo syncs come back fine.

Git hurts my head...
[Nook Color Android Development] fattire:
Yeah can't hurt to clean out the old directory just in case
[Nook Color Android Development] les02jen17:
Is this the place to start building CM10 from scratch? I've just gotten Ubuntu 12.10 installed on my computer, and would like to learn how to do it. :)
[Nook Color Android Development] drmarble:
If you want to build for the Nook Color look at the new wiki (thanks FatTire!)

http://wiki.cyanogenmod.org/index.php?title=Build_for_encore

Tells you most of what you need to know.

Also, look in the thread [DEV] CM9/CM10 Work-In-Progress

http://xdaforums.com/showthread.php?t=1370873

Lately, there are more building posts in there.

Enjoy.
[Nook Color Android Development] EAK128:
Have you guys seen the seeder entropy generator apk floating around that claims to reduce lag, I installed it and it seems to help a little bit that I noticed, so give it a shot and see. Here is the thread, http://xdaforums.com/showthread.php?t=1987032
[Nook Color Android Development] hwong96:
Installed it this morning. Seems snappier. I'll reboot it a few times to see if it improves app load times and reduce lag.

Verify seeder.apk installed - type the following as root (#) in terminal: ps | grep rngd

Monitor seeder.apk in action - type the following as root (#) in terminal: watch -n 1 cat /proc/sys/kernel/random/entropy_avail

With no seeder.apk installed I get 1865 after reboot. With seeder.apk installed I get 4096 after reboots and fluctuates depending on processes.

Monitoring battery life with Better Battery Stats XDA edition.

Edit: Uninstalled based on xda portal article.
[Nook Color Android Development] pastordl:
Try it, you'll like it

Works great. Thanks for the tip.
[Nook Color Android Development] steven676:
If the posted analysis is correct, solving the problem in the Dalvik VM should be a one-line patch.

Also, if I'm not mistaken, pouring stuff into /dev/random does not actually change the kernel's estimate of entropy available, so if this is working, I'd expect it to be due to some side effect of doing this (pinning the CPU clock frequency to the maximum, for instance). EDIT: The first part of the sentence is correct, but checking the actual code reveals an ioctl which can be used by privileged processes to increase the kernel's entropy estimate, and it's very likely that rngd does do this when it writes entropy into the kernel's pool.
[Nook Color Android Development] Lakland:
Two sod on 1231 nightly, since 3 days
[Nook Color Android Development] timmyjoe42:
I am stuck at the boot loader screen. I'm running CM10 from Dec 3rd, and just copied over the latest nightly zip, installed Clockwork, and tried to boot into recovery to install it.

Do I need to make a new bootable SD card to get out of this, or is there a button configuration that I can press to initiate ROM manager?
[Nook Color Android Development] hwong96:
If you are running cm10 from an SD card you need to make a new boot able SD card. If you are running cm10 internal just use cmupdater in settings-about tablet-cyanogenmod updates.
[Nook Color Android Development] timmyjoe42:
I'm using CM10 from internal, but I can't boot up to get to the settings.
[Nook Color Android Development] leapinlar:
Then you need to make a bootable CWM SD to repair it. I have one in my tips thread linked in my signature.
[Nook Color Android Development] deboyz1014:
Did you happen to format boot when wiping information? Are you able to wipe system/data/cache and reflash?
[Nook Color Android Development] timmyjoe42:
Nope, I was running CM10 fine, but getting a lot of SODs so I decided to try a new nightly, downloaded it, moved it to the sd card and then tried to reboot into recovery but now I'm stuck. I'm going to make a CWM boot sd this weekend to try to fix it back up.
[Nook Color Android Development] thereddog:
Hey everyone, I just gave my Nook to a buddy to use for comic books and I was trying to set it up for him. I flashed the 12/31 nightly and 10/11/2012 Gapps package. But every time the keyboard is needed, it crashes. So everything else is functional, but can't type anything.

Am I using the wrong ROM/Gapps combination?