yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] steven676:
Can we also have a dmesg from this tablet from a few minutes after it boots (let the screen turn off at least once)? Also, have you filled out the hardware survey?

A couple of bits that jump out at me:

Repeated instances of

PM: suspend of devices complete after 532.714 msecs
PM: late suspend of devices complete after 1.037 msecs
Powerdomain (core_pwrdm) didn't enter target state 0
Could not enter target state in pm_suspend

That suggests some kind of trouble suspending and resuming some driver; I've seen it happen sometimes after the Nook Color has been connected to USB for a while.

The bit right at the end:

twl4030_usb twl4030_usb: USB_DTCT_CTRL=08
twl4030_usb twl4030_usb: HW_CONDITIONS 0xf0/240; link 3
twl4030_usb twl4030_usb: USB_DTCT_CTRL=08
twl4030_usb twl4030_usb: HW_CONDITIONS 0xf0/240; link 3
twl4030_usb twl4030_usb: USB_DTCT_CTRL=08
twl4030_usb twl4030_usb: HW_CONDITIONS 0xf0/240; link 3
twl4030_usb twl4030_usb: twl4030_phy_resume

I used to think this was unrelated to the problem, but I've seen enough kernel logs from random reboots and freezes that end with this set of messages to think that something's wrong in that code.

With that in mind, do you keep your tablet connected to an AC adapter or a computer's USB port? If you do, how often do you connect and disconnect it?
[Nook Color Android Development] hliew88:
Yes, just filled it out. I'll try to capture a dmesg later today after it charges up and I have a chance to see it reboot.

My charging cycle usually is AC charge during the day (around noontime), then USB trickle charge (using a non-Nook usb cable attached to a separate charger, not computer) in the evenings.

Therefore you probably saw that I had it plugged in from about 6:30pm and on yesterday. No reboots occur when it charges. Sometimes it reboots when I first plug in the Nook cable for AC charging, but I'm sure it's because my cable is broken and when plugged in at certain angles the power pins are shorted with the data pins.

From what time did you pull those bits from the last_kmesg?
[Nook Color Android Development] hliew88:
Finally got a random reboot today.

Attached are the dmesg and the last_kmesg.
[Nook Color Android Development] kwyrt:
Is this still needed? Has the battery drain issue been resolved on the newer nightlies?
[Nook Color Android Development] bowguy:
Battery drain

Simply checking the "opt out of interest based ads" helped my battery life a lot
[Nook Color Android Development] reynoben:
Issues with tilt control games?

First, thanks to all the devs who made it possible. I've had an HP Touchpad for a few years and have been flashing CM ROMs on them. Love it. I picked up a used Nook Color for my kids because they never put my TP down! Everything works great on the latest 10.2 nightly, except for a game called Air Penguin. It is tilt control game, but the controls are crazy off. It works great on my TP, but not on the Nook. I can't even tell if the controls are operating backwards or not. When the game starts, I tilt it forward, but holding it straight (not left or right). Immediately the stupid penguin veers to the right and lands in the water.

I was just curious if anyone else had any other issue with tilt control games and/or Air Penguin. Certainly not a deal breaker for me, but find it annoying :)

Thanks again to all the devs. Great job.
[Nook Color Android Development] hliew88:
I haven't played any tilt games in the past year or so, but I am having trouble nonetheless with the screen rotation. For example, if I had it in portrait orientation, and I lay it flat and don't touch it, within a minute it will rotate 90 degrees (to default landscape orientation) by itself. Sometimes if I lay it flat, it will even flip to 180 or 270 degrees for brief instances. This started happening about 2 months ago, I'd say - could be because I use it as a dashboard replacement in my car (in landscape) so the harsh vibrations have screwed up my orientation sensor?
[Nook Color Android Development] snives:
I've been here since the very start of the NC scene with and have always had spotty luck with the accelerometer. It's been improved quite a bit over time, but it has never been accurate enough that I could enjoy games that use it.
[Nook Color Android Development] deadbot1:
I can't say no for sure, but I've noticed similar behaviour from mine. Seems like the sensor won't register unless I give it a sharp tap in the new orientation...possibly a to low sensitivity setting in software? to clarify...sometimes I can pick it up in landscape, rotate to portrait and nothing...simple tap on one edge and instant switch to portrait mode. Giant Boulder Of Death doesn't work for me here...can only turn by turning completely sideways and tapping...all or nothing baby!!! :D
[Nook Color Android Development] hliew88:
Yep, that's how it has always been. Same with the touchscreen sometimes - that's why I could never do well on Temple Run. I think it's a hardware issue, and I'm pretty sure drops and vibration don't help either.

On another note, my random reboots are much less frequent now - some days it doesn't reboot at all, and sometimes it reboots like 3 times in 15 minutes. I'd like to get another dmesg here but usually I don't realize it has rebooted until hours later.
[Nook Color Android Development] sakisa950:
DSP manager

Has anyone noticed dsp manager stays in speaker mode even with headphones plugged in?
[Nook Color Android Development] steven676:
I'm pretty sure the exact values the accelerometer returns are garbage at the moment -- it's good enough for orientation data, but not good enough for tilt control games. I've never had time to look into it, though; that said, the Android compatibility definition requires accelerometer data to be accurate through a certain range (something like +2g to -1g -- I'm too lazy to look it up at the moment), so it'd be good to get this fixed. (If you want to try, I'd have a look at the sensor HAL in device/bn/encore/libsensors and the kernel driver for the KXTF9 (drivers/input/misc/kxtf9.*; board-specific config stuff in arch/arm/mach-omap2/board-encore-*). An app like GPS Status on the Market will show you the exact g values the accelerometer is reading.)
[Nook Color Android Development] reynoben:
Thanks. Using File Manager in root access mode, I scoured the entire NC file system and could not find the directories/files you mention. Maybe this is in the source code?

I installed GPS status but it kept crashing when it was opened. I then installed Accelerometer Sensor. It runs in portrait mode. When laying flat on my table it is perfectly positioned in the center.

A quick tilt left moves the sensor down.

A quick tilt right moves the sensor up.

Holding the NC flat, a quick tilt up moves the sensor to the right

Holding the NC flat, a quick tilt down moves the sensor to the left

Not sure what this all means but thought I'd let you know.

Thanks!
[Nook Color Android Development] hliew88:
I'm noticing something going on with the change in memory management (using the vm_iomap_memory) in the 12/6 nightly. After it has been on for a while, the memory allowed for apps gets very low, even if I have no background apps.

I'm looking at the memory usage, and the system/kernel is hogging up over 300MB (constant - doesn't seem to adjust continuously), and only 100-150MB is occupied by apps. Normally it's more like 200/250 split. It doesn't decrease after putting it to sleep/waking it up, but it's fine after a reboot.

Also, the nook has never had that sort of headset/speaker detection for DSP manager - it always remains in speaker mode.
[Nook Color Android Development] steven676:
I landed a patch to fix a security bug, reported upstream, which could almost certainly be exploited by a clever attacker to obtain root on your device. While I don't know of anyone actively exploiting this bug in the wild, it's strongly recommended that you upgrade to a nightly with this fix (December 6 and later should be okay) ASAP.

That change only deals with access to the DSP (for hardware-accelerated codecs) -- I'd look elsewhere for the cause of your particular issue.
[Nook Color Android Development] hliew88:
Ah, might that be why I was able to play a 720p video unusually smoothly (no hiccups whatsoever) today?

Where should I look, and what should I provide you with when the problem comes around again?
[Nook Color Android Development] Homer_S_xda:
Steven676,

Do you know if this serious security fix has made it into 10.2?

Homer
[Nook Color Android Development] EAK128:
If you look couple of posts up he gives you the answer. Dec. 6 nightlies and newer have the patch.
[Nook Color Android Development] Homer_S_xda:
D'oh! My search fu was weak: http://xdaforums.com/showpost.php?p=48220252&postcount=208

Homer
[Nook Color Android Development] chengjih:
Battery drain due to Android OS?

I have the nightly from 2013-12-08 or thereabouts, and have extreme battery drain on the Nook. It's on the charger, but "Android OS" is running so hard, the charger can't keep up, and the battery will fully drain in about 2 days even though it's been on charger the whole time.

Any suggestions on figuring out what "Android OS" is doing that would cause that?
[Nook Color Android Development] webyrd:
See pastordl's post 182 in this thread
[Nook Color Android Development] pmgnet:
Latest 10.2 nightly I installed (maybe 12/31) seems really snappy. Really nice. Everything is responsive again where last few weeks have been pretty sluggish.

Looking forward to cm11 builds. Still haven't set up my build machine!
[Nook Color Android Development] trouinky:
Pulled my NC out from a box under the bed and went with the latest 10.2 nightly (1/2). Love that CM and devs have kept this device on their list. Is anyone else with this rom experiencing some weird touch issues? Sometimes I touch a button and the device goes multi-touch crazy. I've never seen this happen on this tablet, so I was wondering if it's rom/kernel related, or maybe my device is dying? I thought maybe a low ram issue, so I uninstalled everything except gapps, and it's still a bit sluggish, but that's OK, the screen touch issue is giving me fits.
[Nook Color Android Development] leapinlar:
Try cleaning the screen. If it's been a while it may have old fingerprints on it.
[Nook Color Android Development] drmarble:
Crazy touches also happen when you are plugged into the stock charger/cable. Doesn't happen to me when attaced to a usb port on my PC with a normal usb cable.

Cleaning will also help.
[Nook Color Android Development] trouinky:
Don't know about those fingerprints but the wacky touch problem seems cured when off the charger. Is it a "better quality" cable problem, i.e. maybe a different cable will let me use it on a stand plugged in?
[Nook Color Android Development] leapinlar:
I think it happens with all cables. But try a different low amperage charger.
[Nook Color Android Development] meteorrock:
Hi guys I am back. Are there going to be any android 4.4 kitkat ports for the nook color? Maybe in the nightlies? I saw an unofficial port of android 4.3 in here. The other tablets have Cyanogenmod 4.4 kitkat.

Still fooling around with the OC kernel a bit from CM 7.2. Learning how to rewrite init.d scrips and the headers at the moment that it will need to work on the 3.x kernel. Learning about strings too in the init.d box. If anyone is interested , here is the OC kernel on the git. Learning how the init.d box is the first process picked up for a kernel to boot. https://github.com/meteorrock/Nook_Color_Kernel_Overclock

There could be some init templates around for it, IDK, I will check and see first.

Someday I would like to publish my first kernel, I would like to publish it here for the nook color. I wish <steven676> could pipe that overclock in for us in the kernel mainline, but he was told not to. I feel 1200 mhz could be achievable for this device. (hint hint) Its taking me awhile to figure it out, it is like rocket science lol.

Learning on how to debug running kernels right now too. If I find any errors or segment faults with the 3.x kernel we have on this device, I will let you know. The kernels look tight so far, but I have not fooled around much with them, been busy. Hope you guys are still debugging and looking for exploits, it will help all devices running CM.

Have not looked up in the java application stack for bugs, hope you guys are still looking into it.

My nook color is doing good and still boots up great with the CM 11 nightlies with android 4.2. Hi <leaplinar> :)

EDIT: PORT IT PORT IT TO THE NC. WE ARE HACKING NOW GUYS. HIT ME WITH THE ANDROID 4.4. WE are going to fight this together. I KNOW YOU ARE TIRED and the journey is difficult. WE are becoming as powerful as the top nix wizards of old. You are as powerful as Linus Torvalds. HE is here fighting for us along side you. I have faith in you guys. I can see the code flying now. You can do it too <steven676>. I came back because I care. He is lurking now. Check the /var/logs/ We are going KANG.

Cyanogen just checked in.

YOU check those ****ing /var/logs/

I am taking you KANG

Love you guys. <33. Don't let others hold your talent back. Don't sell out. You guys hide your talents. We NC users need love too.
[Nook Color Android Development] steven676:
Onwards to CM11!

As of today, official CyanogenMod 10.2 nightlies are no longer being built for the Nook Color -- they're being replaced by CM11 nightlies (the first one should be coming early tomorrow morning UTC-8 time, depending on when the autobuilders get around to it). (The CM autobuilders switched to running CM10.2 edge builds on a weekly basis slightly more than a week ago, so the 20140119 build is the final official CM10.2 nightly for encore.) CM10.2 nightlies will expire from the official site as new CM11 nightlies are built, but they'll continue to be available at http://techerrata.com/browse/cm/encore/nightly (thanks eyeballer!).
[Nook Color Android Development] ibilln:
It's now officially not "early tomorrow". :)
[Nook Color Android Development] Protocold:
So is this 20140119 build considered to be more stable than CM10.1.3.2?
[Nook Color Android Development] steven676:
All of last night's CM11 nightly builds failed due to a patch which broke the build. Builds are actually succeeding tonight, so with luck there should be something to play with tomorrow.

I couldn't say for sure -- I haven't personally tested that nightly. That said, I'd expect it to be as stable as CM10.1.3.x at best (and possibly a little worse if you're unlucky).
[Nook Color Android Development] FordPrefect:
Will there be a new "[ROM] CyanogenMod 11 Nightly Builds for Nook Color" thread eventually? As far as I know, there is only a "[DEV]" thread currently. Get me right, that is completely fine, but I guess the DEV thread shouldn't be spoiled by the curious and adventourous users out there giving their feedback ... like me ;)
[Nook Color Android Development] ibilln:
First CM11 nightly:

Bad zip

set_metadata_recursive: some changes failed

(Status 7)
[Nook Color Android Development] dparrothead1:
Worked fine for me. I dirty flashed over Succlent's 1/16 build and it's running great.
[Nook Color Android Development] leapinlar:
That error is because you are using too old of a CWM. You need 6045 or newer to flash CM11.
[Nook Color Android Development] Mr-Glass:
I am not seeing TWRP mentioned at all - is this a no go?
[Nook Color Android Development] Homer_S_xda:
Leapinlar,

I used the 6.0.4.4 that Fattire had in the other post. It seems to work... is it a problem that will crop up later?

Homer
[Nook Color Android Development] ibilln:
NB - there's now a CM11nightly thread (by steven676) in nook color/android development.
[Nook Color Android Development] leapinlar:
I don't think so, if fattire provided it for CM11, it should be ok for that.
[Nook Color Android Development] lifeisfun:
10.2 now released as stable

http://download.cyanogenmod.org/get/jenkins/57353/cm-10.2.1-encore.zip
[Nook Color Android Development] i_guana:
In case anyone is still playing around with the Nook Color here is the mother-load of CM ROM's:

http://techerrata.com/browse/cm/encore/nightly
[Nook Color Android Development] Mikito1976:
Hey guys first of all thanks to all the contributors for keeping this devices alive and kicking it. It's amazing what you guys do.

First, I come from ParanoidAndroid 3.69 on emmc and it was a great experience, for what I used it for, everything was good; Netflix worked with the workaround, played candy crush with no hiccups, browsed the web with Boat browser very well, read a book here and there, etc. Great job by mateorod and his contributors by the way.

I decided to give this new built a go and I'm not disappointed, taking to consideration that it's still a nightly built. I'm using it for my daily driver. I have not update it yet to the latest nightly since I'm still letting the built to set well on the nook. And so far the experience is good. I'm running it at 1100 MHz with Interactive governor, Nova Prime, etc. I do have two things that I'm trying to figure out and I will appreciate any suggestion. It's about preferences, is about the lock screen been on landscape mode, I myself preferred the portrait mode; is there's a way to change it to portrait mode, am I missing something. The other one is that Netflix it's showing but distorted.

Here is what I'm seeing.

http://i61.photobucket.com/albums/h42/poeta_soy_yo/Screenshot_2013-08-30-14-05-05.png

Other than those two things I'm very impressed with the work you guys have put on this, I think that it's a superb job considering how old this device is.:thumbup::thumbup:

CM10.2 Nightly 8/27-NookColor
[Nook Color Android Development] Mononon:
I was wondering about the landscape lock screen myself. I just assumed it would be dealt with in a nightly at some point.
[Nook Color Android Development] EAK128:
Settings; display; rotation and just tick the rotate lock screen box.

Also make sure 0,180 and 270 degrees are checked also.
[Nook Color Android Development] Mikito1976:
Thanks for the help, I really missed that.

CM10.2 Nightly 8/27-NookColor
[Nook Color Android Development] bitstra:
I can't understand your problems with this ROM ...

My impression is, since using CM10.2 (clean 'normal' emmc - installed into internal memory !):

- very, very smooth (!)

- no problems with any app (!).

May be, you should try it with a factory reset and install to emmc...

Thanx to all devs, who made CM.2 possible on our good old nook toys!!! - esp. to [MENTION=4353291]steven676[/MENTION] at this place!

bitstra
[Nook Color Android Development] pastordl:
Answer to Netflix Problem

Go to my post here: http://xdaforums.com/showthread.php?p=44626173#post44626173

Get either the Xposed installer and the workaround module and follow instructions.

Or Get Liquid64's persist.zip and install in recovery.

The zip will persist past ROM update installs. I have both setups and they work great with CM 10.2. I have used it with each of the 10.2 nightlies since the release.

Please make sure to thank the developers of these so we can continue to benefit from their hard work.

Enjoy

:highfive:
[Nook Color Android Development] steven676:
We get this question often enough that I've added it to the FAQ at the top of this thread. (Question for anyone who's done a complete wipe and reinstall of CM10.1 or 10.2 lately: are these settings sane out of the box, or do I need to look for a way to change the defaults?)

Well, "smooth" is relative. I agree CM10.2 on the Nook Color is shockingly smooth for hardware of this age and really quite smooth in day-to-day usage, but if you put it next to a modern device running Android 4.3, you'll suddenly notice a difference in smoothness :p That said, if it does seem very slow on its own, a wipe and reinstall might be called for (and if you're installing to SD card, see the discussion in this thread -- your choice of SD card brand may be the cause of your problems!).
[Nook Color Android Development] bowguy:
netflix

Followed the directions to use the latest Netflix by pastordl. Works great for me.
[Nook Color Android Development] Mikito1976:
I'm not going to clutter this thread with back and forward replies like this one but if you check me out I do press the thanks button 9 out of 10 times meaning the majority of the time, that been said I might miss one here one there, I've been around many forums and I know how they work with the thanks, like, etc. buttons. Not taking it personal but not coming from the person who replied to my post (which by the way I thanked him by taking the time to typed the thanks instead of pressing a button, don't get confused I know the importance of pressing the thanks button) it throws me off a little. By the way I'm hitting the thank button. ;)

CM10.2 Nightly 8/27-NookColor
[Nook Color Android Development] thekrautdog:
Hey guys it is unbelievable we can run 4.3 on this old thing...totally loving it and so many thanks to everyone responsible :good::good:

I have a question/need advice...my NC is incredibly laggy - not unusable just very frustrating. A lot of it is with things like screen touches taking time to register. And to be clear it is not this rom - it is about the same as it was with the last two 4.2's I tried recently.

The thing is I just started using my NC again after a bit of time, and I'm thinking that maybe I changed some things in Developer Options or something like that a while back (would have been from directions from a more advanced user in an effort to improve performance) that is acting detrimental on the newest Android builds. Can someone advise as to recommended settings for things like gpu rendering, dpi, etc...? If it's easiest to just point me to a site with a guide or something that would also be much appreciated.

If it matters, last flash I wiped system in addition to the usual factory reset, cache, and dalvik cache (I use TWRP)...so maybe that already reset any changes I've made in the past?

I'm on 8/31 after starting on 8/28, 1100mhz OnDemand

Thanks so much :cool:
[Nook Color Android Development] Cor-master:
Anyone else get stuck on the boot screen after dirty flashing from 10.1? I just wiped data, hopefully that fixes the issue

Edit: yep that fixed it
[Nook Color Android Development] pastordl:
First thought

My first thought as I was reading your post was sounds like what I had back with 10.1. Your line giving the settings struck home. Try reducing the CPU speed to either 1000mhz or 800mhz. I tried both felt the 800 setting was a little slow but the 1000 stopped the lagginess which was the same as you have described. It had the additional plus of helping to speed things up. Sounds backwards but if the CPU is being pushed to much it can effect performance.

Try it. Hope it helps you as it did me. Still at 1000mhz for 10.2 and happy. I remember others saying that 800mhz worked best for them.

:D
[Nook Color Android Development] thekrautdog:
Many Thanks pastordl :) I will give that a try and report back after a bit of use. Yeah it's funny but I can see the backward kind of sense it makes.
[Nook Color Android Development] pastordl:
Another Thought

Also try installing Nook Screen Recalibrate from Google Play Store. That helps greatly with screen touches and sensitivity.
[Nook Color Android Development] thekrautdog:
Will do thanks :)
[Nook Color Android Development] thekrautdog:
My Nook Color has blossomed :cool:

I wish I hadn't done these three things at the same time so I/we could know what really helped, but I'm really just glad it's working better. What I did in the course of ten minutes was dirty flash the 9/1 Nightly, install and run Nook Screen Recalibrate, and drop the CPU max to 800. It's like night and day, especially the screen response. It is most evident in Moon+ Pro reader, my most used app, which is very snappy now but was lagging just terribly tho I knew it was a great reader which I have been using for a while.

Now I can focus on enjoying the achievement that this rom is :good: Maybe in a little while I'll take the CPU up to 1000 and see how it goes but for now I'm gonna leave well enough alone and be happy.

Thanks again pastordl for your attention and the great advice