yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] Nburnes:
2+ hours? That's ridiculous. I wouldn't even bother if it took that long. I'm also jealous of the Thinkpad, king of laptops.
[Nook Color Android Development] clamder:
I noticed I get sod when I let my device deep sleep while connected to wifi, but connect it to a computer via usb with the screen off.

I just notice it happening and have done it a few times now. Maybe someone can confirm?
[Nook Color Android Development] crashdau:
I'll give that a go. Thanks much.
[Nook Color Android Development] bonobomidwest:
i had this the other day on v5. rebooting fixed it.
[Nook Color Android Development] FletchF:
I've seen this once, on nightly7. Cleared it by simply turning the screen off and on.
[Nook Color Android Development] crashdau:
racks....Thank you, I got Let's golf to run. Any ideas on how to get it use the full screen?
[Nook Color Android Development] racks11479:
Unfortunately no. I have that same issue. Spare Parts doesn't help me either. Sorry.
[Nook Color Android Development] bratliff:
Over on the CM forums they are able to get full screen by getting LCD density app and going down 1 setting... not on your specific app but it worked on others. Give it a shot.
[Nook Color Android Development] racks11479:
Thanks for the tip. Gonna give it a go and see if it helps any.
[Nook Color Android Development] crashdau:
I tried changing the density in root explorer from 180 to 190, 200, 210 and it still was too small.
[Nook Color Android Development] KitF:
I think he means in the other direction.

Just tried setting to 160 and Google Reader is back to working correctly.
[Nook Color Android Development] Khegobier:
After a bit of research, this doesn't help at all. The only thing in there is a single boot partition spanning the entire partition. I'm at a loss at this point as to how to set up the partitions on a SD card and what to put where.
[Nook Color Android Development] antony617:
I dunno if this is a known issue...

When I install extra input method, the last one I installed wont work (can't tick the box)

e.g. if I install Keyboard a,b,c, only a and b will work. If I install Keyboard a,b,c,d, only a, b and c will work.

Other then this and Wi-Fi setting FC (workaround is okay), #7 is fine.

Thanks for the efforts!!

P.S. How is the IMEI problem fixed? A generated IMEI is stored?
[Nook Color Android Development] woolmonkey:
I don't think the store a IMEI number because when using network info it doesn't show one. But from looking at the commits at github it looks like a cell radio was "faked".
[Nook Color Android Development] nemith:
No IMEI is being generated. I can't see where the IEMI is required. I think the biggest part was the phoneType being returned null instead of PHONE_NONE or PHONE_GSM.
[Nook Color Android Development] Homer_S_xda:
Sorry if I missed this. I'm running Nightly 7, how do I format an SDcard? I've tried in the NC and it seems to do something but apparently does nothing.

Homer
[Nook Color Android Development] antony617:
#8 flashed, Problems found by now: Google Map FC (works in LCD Density>160)

Other than that is fine.

Thanks devs!
[Nook Color Android Development] tominabox1:
Also flashed #8 everything working ok except xda still crashing when logged in.
[Nook Color Android Development] newellj79:
Just installed nightly 8. So far all I have noticed is that "my apps" don't come up in market. I also noticed the rom is a few megs smaller than 7. Any idea why?
[Nook Color Android Development] crashdau:
Flashed v8 everything still working well. Rockplayer is crawling when watching videos. Didn't have that problem on v7 or lower. Not a deal breaker. This rom just keeps getting better.
[Nook Color Android Development] dalamchops:
anything noticeably changed?
[Nook Color Android Development] antony617:
Bug fixed like Wi-Fi setting FC and weird blue line in UI... anymore?
[Nook Color Android Development] mr_fosi:
Sure you didn't mean Ideapad? :D

I'm betting that my i7 quad HT won't take too long. It's cut down my vid transcoding times from 3+ hrs to 20 min. :cool:
[Nook Color Android Development] mr_fosi:
Well, that sucks.

I can't get repo. The site listed in the guide (http://android.git.kernel.org/) is a dead link. I searched around but this is the only place that people are directed to in order to get the bin, so I guess I'm screwed.
[Nook Color Android Development] fattire:
I just downloaded it last night... if it's down now it'll be up soon. kernel.org is where the official Android source (and the official linux kernel) are served from, so there's no way it's down for long.

Try in an hour or something.

Update: Indeed it's back up.
[Nook Color Android Development] khaytsus:
I wonder what's going on with the changelog?

http://cm-nightlies.appspot.com/?device=encore
[Nook Color Android Development] Awats:
Maybe all or part of the server down. Someone mentioned it was acting goofy and they were working on it. The mirror site is working again.
[Nook Color Android Development] khaytsus:
Guys, anyone experiencing SOD, please see this thread and help the devs out by filling out the form. Hopefully it'll help them track down the issue.

http://xdaforums.com/showthread.php?t=1108964
[Nook Color Android Development] Gin1212:
Shouldn't this wait till after N88, so we can see if the battery fix works and whether or not people are just mistaking PBD as SOD?
[Nook Color Android Development] khaytsus:
Nah, plus I have some info there to isolate PBD from SOD.... Although there's certainly enough misinformation confusing the two ;)
[Nook Color Android Development] JeremyNT:
I continue to see occasional system lock ups even at stock clock speeds. Is anybody else experiencing this sort of instability? I never encountered this with builds that predate the new kernel, even at much higher clock speeds.
[Nook Color Android Development] paleh0rse:
Anyone feel like making a build and posting it up on a private link somewhere? I'm dying to test the new commits, but I'm not home to build it :(
[Nook Color Android Development] painter_:
I wish I had the setup to build it.
[Nook Color Android Development] Anon87:
Check the CM7 User thread. Someone posted a build there...

Sent from Soft-Rooted HTC Desire using Tapatalk
[Nook Color Android Development] paleh0rse:
Yep, got it. Running it now. Charged at 30%... time to see if it cured my PBD. :)
[Nook Color Android Development] joenathane:
Build 91 is officially available

http://cm-nightlies.appspot.com/?device=encore
[Nook Color Android Development] dexx0008:
build 91

full market isn't showing up for the first time in a long time for me

netflix isn't showing up for me.
[Nook Color Android Development] lyam23:
Ditto on netflix.
[Nook Color Android Development] chisleu:
I had it installed (didn't wipe) and it still works fine, but it doesn't show up in the market for me.

Although LWP's (nightfall/silhouette/etc) still work.

Anyone missing anything else from the market?
[Nook Color Android Development] smully1:
I was missing netflix from my market for the last 2 days on nightly 87
[Nook Color Android Development] mkm1126:
ya . . . it's not just our rom, Netflix removed it. Evidently they are working on a new release that fixes some issues folks on 2.3 were complaining about. Works fine on CM running Gingerbread so I don't get it.
[Nook Color Android Development] :
Confirmed . . . I am at N87 and Netflix is not in my market anymore.
[Nook Color Android Development] lyam23:
I will say that my NC is finally reaching a seemingly correctly reported full charge for the first time since moving to the .32 kernel. Everything else on n91 seems to be working well so far.
[Nook Color Android Development] smully1:
I am getting a lot of fc's since loading 91. Also my u-boot changed and menu no longer loads. I am using fat tire's uboot.

Edit : does the install save a new uboot over mine?
[Nook Color Android Development] racks11479:
Yes. Latest nightlies comes with the .32 kernel compatible uboot. So if you don't want it to overwrite yours. Just use an archive manager and remove it from the .zip.
[Nook Color Android Development] newellj79:
Yes, the nightlies now come with uboot so if u r using a custom one (cyan, or untimely for example) u will need to reflash it.
[Nook Color Android Development] smully1:
Any thoughts on the fc's?
[Nook Color Android Development] racks11479:
Beat cha to it! :p
[Nook Color Android Development] joenathane:
Did you wipe the cache partition and dalvik cache? If not try that and report back...
[Nook Color Android Development] The Mad Mule:
For the record, the Dalvik cache wipe option is right after you choose the "Advanced" choice at the start of the CWM.
[Nook Color Android Development] TainT:
So what happened to 92?

On a side note....93 seems to work well.
[Nook Color Android Development] dexx0008:
you can find it in market if accessing market from a computer. I have it backed up so it's not a big deal but thought i should point it out.
[Nook Color Android Development] angomy:
Was getting weird battery percentages with 91 --- this after I flashed, wiped /cache and dalvik, and reset battery stats after charging to 4200mV. It would show a much lower mV than I've so far associated with percentage - e.g., 3910mV @ 98% battery life.

When I flashed 93 it corrected it to 75%. I haven't rebooted since after flashing 91 until now so that may explain battery drift (re: battery check on boot that fattire or another dev added to 91, unless I'm misremembering the changes for 91).
[Nook Color Android Development] ADude:
From batteryuniversity.com :
[Nook Color Android Development] angomy:
I've had the nook barely a month and never leave it idle on the charger past full, so I doubt it's that. Battery percentage/mv are behaving as expected now with 94 + battery stats wipe via CWR.
[Nook Color Android Development] Awats:
If clearing the stats helps fix the battery status issue, why don't they clear them on a reboot?
[Nook Color Android Development] chisleu:
Clearing gets rid of bad data(by deleting all data). If I understand it, now every hour all the data of the battery curve is brought in (good data) and then processed on reboot (to be added to the battery percentage calculator for android.)

You shouldn't have to clear more than once per ROM install. (unless you change the battery.)
[Nook Color Android Development] Divine_Madcat:
So, for me, i upgrade to n91 from beta 3.1, and lost deep sleep initially, even after reboots. However, i did the usual fix permission, and rebooted, and all is good now. I suggest people give it a try, especially if they have new nightlies or done things like installing Chainfire..
[Nook Color Android Development] MedLine:
users without deep sleep are you checking /proc/wakelocks (at time of no deep sleep)? i posted mine back here, wondering if anybody else seeing "omap3-dac3100" holding wakelock through standby.
[Nook Color Android Development] chisleu:
no but when and if mine comes back I will check this.

Also, the crap Mr Dude posted from battery university has nothing to do with why the battery stats were off. They were fixed when you rebooted. You need to clear stats after you do a rom install, then run through a battery cycle (rebooting as often as you feel like) and then charge it up. It records the discharge curve and makes better percentage calculations.

I think this was why we had the PBD. The curve data wasn't being updated and was corrupt, so it would go from 20-40% to 0 nearly instantly and the system couldn't shutdown properly.
[Nook Color Android Development] dalingrin:
If someone can reproduce the deep sleep issue, for the love of God and all that is holy, post dmesg, logcat and the output of /proc/wakelocks.
[Nook Color Android Development] greenmky:
I'm not great with Android logging (I'm a VMS tech) but I think I've figured out to break and bring back deep sleep. I can look at my logs but Pastebin is blocked by my FW at work.

Maybe someone else can verify they lose deep sleep if they follow the same steps?

EDIT: still ironing the steps out precisely...

OK...think I got it.

The key was to me that I lost deep sleep after upgrading to nightly 94... when wi-fi didn't want to start up with the Nook.

If I do this (I'm on nightly 94 & 5/23 OC Kernel) it seems to break deep sleep:

Settings: Toggle Airplane mode (or just turn off wi-fi I think)

Reboot with wi-fi down

Nook comes up with wi-fi OFF. Turn off screen WITHOUT turning on wi-fi.

20-30 minutes later...still no deep sleep. CPU Spy shows most of the time spent at 300mhz.

To bring back deep sleep:

Toggle wi-fi on. Turn off screen. Deep sleep works fine.

Still playing around with it a bit.
[Nook Color Android Development] fattire:
Wait... what? VMS? As in VAX/VMS? Like w/DCL? Does that still exist?!

Sorry... I missed the rest of what you said.
[Nook Color Android Development] greenmky:
I know of an 80mhz-ish VAXstation up since Y2K....now that's uptime. :p

What's interesting is, once I get deep sleep working again (wi fi juggle) it's actually kind of hard to break it again. I pretty much have to futz around with airplane mode and turning wi-fi off...but when I break it, it's definitely a reboot with wi-fi off.

It seems doubtful to me this is the only way to get deep sleep to stop working...but the kernel upgrade did it for me also until chisleu mentioned wi-fi toggling helping him.
[Nook Color Android Development] Divine_Madcat:
ASk and ye shall recieve. Background:

Upgraded to N91 (system did have deep sleep) to N97 (no deep sleeping, even after a reboot with wifi off).

Fix permissions has been run.

WiFI was off when these messages were taken, as well as when the system was allowed an attempt to deep sleep.

Dmesg:

http://dl.dropbox.com/u/19844443/dmesg.txt

Wakelocks:

http://dl.dropbox.com/u/19844443/wakelocks.txt

Logcat:

http://dl.dropbox.com/u/19844443/logcat.txt

Lemme know what else you need! :D
[Nook Color Android Development] chisleu:
I am not certain that was what was doing it, just wanted to add to the noise because eventually a pattern can rise out of the randomness of ill-informed assumption.

This post brought to you by Henry David Thoreau. May he rot in hell.
[Nook Color Android Development] chiballer20:
i'm not sure where i went wrong but i'm having some problems. Just started flashing my nook again since I stopped once I got my Nexus S. My problem is, since #76 and still now with #97, every time I flash the rom and gapps, the nook boots the initial logo and just stays on a backlit black screen. I left it for 20, 30 minutes and it never boots. I do have a nandroid so i'm good there, or at least I thought. Now that I flashed #97, I can't get to recovery. I do the two button combo and the new logo actually say Booting in Recovery but it doesn't go and just ends up at the backlit black screen. I tried everything from wiping data, cache, delvik and fixing permissions. Nothing seems to work. It wasn't a big deal since I could just restore, but now I can't even get back to recovery. damn

HELP!
[Nook Color Android Development] martian21:
Did you try booting recovery from an SD card?
[Nook Color Android Development] Divine_Madcat:
So, not sure what fixed it; but a couple of reboots later, and the system is deep sleeping now. I am not even sure when it fixed itself...
[Nook Color Android Development] chiballer20:
Boot from an SD card?
[Nook Color Android Development] martian21:
microSD card actually but yes. Also please keep this in the general thread as this is not development.
[Nook Color Android Development] rhester72:
I guess a clarification of what 'development' is would help.

It would seem by logic that any support issues against stable would belong in General, and any support issues against nightlies would rightfully belong in Development, since a) it is code in development *laughs* and b) it's where the devs tend to hang out, and are thus more likely to see the bug reports, corroboration, and logs/dumps for analysis.

If that's not the case, perhaps it might be better to have subforums - General for plain old Nook conversation, Development for threads _only about coding_, Support - Stable and Support - Nightlies/Development?

Rodney
[Nook Color Android Development] muness:
http://xdaforums.com/showpost.php?p=11452450&postcount=19

Follow my instructions to re-install and see if that helps. You may need an updated uBoot.

You could also use the bootable recovery to restore from backup if you prefer:

* Move backup from SD to PC

* Burn the recovery image (steps 1-3 in the instructions)

* Move the backup back to the SD

* Boot from recovery

* Restore
[Nook Color Android Development] newellj79:
I posred a similiar question in USER. It got lost in the sauce and never replied to. I'm.trying to use the new boot menu that's comes with cm7 to boot USB host kernel as my alternate. I copied the uiamge and uramdisk out of the oc zip, renamed them appropriately and placed them on the boot partition. It boots fine by selecting the alternative kernek boot option, problem is wifi is broke when I use it. It says wifi error. If I flash the kernel thru cwm it works fine. I must be missing something. Please help.
[Nook Color Android Development] racks11479:
Well wifi would be broke if you're not copying over the "tiwlan_drv.ko" module to your system folder as well. It works when you flash via CWM, cause it installs it for you. However it will replace your Primary CM7 "tiwlan_drv.ko". So I"m not 100% sure if it will conflict with that either. Guess you won't know till you try. :)

-Racks
[Nook Color Android Development] newellj79:
Where do I copy it to? Does one already exist for the oc kernel? Ill try it and report my resulted I just need to know where to put it. Thanks!
[Nook Color Android Development] racks11479:
same location that it's in the .zip file.

/system/lib/modules/

make sure you set correct permissions if you do it via ADB

-Racks
[Nook Color Android Development] newellj79:
Hmmm. Of course that file already exists for the oc kernel andnthere different. I don't see n e point of being able to boot alternate kernel if u can't use the other file to enable wifi?
[Nook Color Android Development] racks11479:
Have you tried replacing the wifi module with the one from the USB Host zip and see it wifi works on your Primary CM7 install?

Edit: From fattire
[Nook Color Android Development] newellj79:
I think changing the although ramdisk may be over my head. Is it as simple as using a text editor? Ill have to take a look when I get off work. Thanx again.
[Nook Color Android Development] screech:
It is not as easy as a text editor, but if you have a linux/unix setup it is not that hard.

Follow the instructions here, (skip to the portion about using cpio and unpacking/repacking the ramdisk)

http://blog.different1.com/2011/03/hacking-the-nook-color-saga-1/

Let me know if that does not work for you.
[Nook Color Android Development] :
Gah! So let's say I don't want to do all that...anyone have an Ramdisk I can use for the usb host kernel with a link to the wifi driver (so I can use wifi without changing the file between the OC and USB kernels)?

I figure someone could get one whipped up for usb host, then change the encore init file to look for the wifi driver in some other folder (or maybe renamed)?
[Nook Color Android Development] newellj79:
No Linux setup but thanks.
[Nook Color Android Development] madguy2006:
Where is the menu bar?

Hello-

Quick questions for your guidance please:

I am currently running 2.6.32 beta 3 from dalingrin. I understand the new kernel has been merged with CM7 nightlies starting with #87

When I download the nightly #99 and install it, I do not see the menu bar at the bottom. Could somebody explain why it disappeared in latest version of the nightlies?

Thanks!
[Nook Color Android Development] newellj79:
It should be there. Did u get a status bar fc? Try wiping dalvik and fixing permissions. PS, n100 is out with a new tablet tweaks commit.
[Nook Color Android Development] Rick_V:
It is there on mine try going into settings/tablet tweaks and seeing if is disabled.
[Nook Color Android Development] nukeruss:
Keeps freezing after Nightly 100

I just installed N100 and now every time I connect my nook to my computer, it freezes and I have to do a hard reboot. I'm going to try and flash it again and see if that fixes the problem.

Update:

Downloaded N100 again and then gave it another try before re-installing and it worked just fine. Weird, it happened three times in a row and now all seems well.
[Nook Color Android Development] madguy2006:
Hi-

I have a quick question: Does the basic CM7 nightly say #100 have the full color depth?

Thanks!
[Nook Color Android Development] fattire:
I believe it does unless it is replaced with Dalingrin's overclocked kernel, which reduces the bit depth for speed improvements...
[Nook Color Android Development] madguy2006:
Thanks for the reply fattire. I installed the #100 nightly and I see grains or bands in pictures. This is the new nook color by the way. I formatted system, data and cache. Installed uboot 1.2, nightly #100, and google apps. Then I wiped dalvik cache and restarted.

The icons have grains in them and the pictures have big bands.

Is there any setting that I have to tweak?
[Nook Color Android Development] khaytsus:
None I'm aware of, and 100 looks fine to me. I didn't notice anything immediately on the stock kernel, and using Dal's 0609 right now and looks fine there too.
[Nook Color Android Development] :
Are you using a live wallpaper by chance? The only time I would start noticing the grain/banding is when I switched to a live wall paper for my desktop background.

Note: I only see the banding in Dalgrin's OC kernel. Stock doesn't exhibit the same.
[Nook Color Android Development] chisleu:
dalingrin's kernel has 16 bit instead of 24 bit color which is why you see that in gradients. I think the stock kernel is 16 bit now too. I can't recall for sure.

It was done for a huge increase in 2d/3d performance.
[Nook Color Android Development] xdajunkman:
If you enable surface dithering in 'settings->CM settings' then the banding in gradients is nearly eliminated.
[Nook Color Android Development] dalingrin:
The stock kernel has a 32 bit framebuffer. Note that many, if not most things are rendered using RGB565. In fact, our video drivers have relatively poor support for 32 bit surfaces.

Much of the banding that people see is not due to framebuffer limitations. It is due to interpolation from using a non standard lcd density in Android. If you change it to 160 you will see the banding disappear. However, you will also see your installed apps eventually disappear from the Market due to a bug in the Android market.

This was discussed some time back and I posted screen captures showing that there is practically no IQ penalty in using a 16 bit framebuffer. The only place it is noticeable is the launcher and even then it requires careful examination.
[Nook Color Android Development] rhester72:
Really? I'm assuming you don't run the News and Weather widget, then. The gray gradient ends up showing so much banding (even with dithering turned on) that you could drive a car across each of the bands. =)

That having been said, again, I think the bigger impact is to video playback. Color banding, especially in low-bitrate encodes already subject to blocking and ringing, wind up with absolutely horrible banding and artifacts in 16-bit...as you can see on your own Windows desktop with ease. No need for a Nook. ;)

Rodney
[Nook Color Android Development] dalingrin:
Like I said, the launcher is where it is most visible. Are you running the OC kernel? Did you try running the LCD density @ 160 to see if it fixed the banding?

I have yet to see banding in videos with the 16 bit framebuffer. Not saying it won't happen but I've not seen it on the Nook.
[Nook Color Android Development] madguy2006:
Color problems with nook

Guys-

Apart from the grainy icons and the banding in the images - like it is a 16 color Windows 95 machine, I found something else that is very odd: The screen when it switches off does not switch off like my old nook - the old nook fades. This one blinks off like its an old CRT monitor.

Maybe its something to do with drivers - maybe i accidentally lost them. Is that possible? Please help?

Thanks for the help and advice!