yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] fattire:
new CyanoBoot for testing...

So I decided to address this... see below for a new u-boot.bin. I'll give it a day to let it "breathe" but I doubt there are any issues as the changes are simple UI -related.

There are a few theories on the best way to handle this:

1. Try to boot from SD/altboot/recovery no matter what (current behavior). It gives you all the options. If you try to boot to something that doesn't exist, it fails silently.

2. Give some kind of error or warning or grey out any "illegal" options. This requires some semi-heavy lifting (gotta add detection of boot files and then make the menu smart enough to grey out and skip non-functioning options)

3. Don't have the SD options appear at all if SD isn't inserted or altboot doesn't exist, etc. (this also requires some work)

So right now 1 is how it works... 2 and 3 do require some time-- not as much as writing the menu in the first place... but it will need to detect the presence of various files and then present the menu accordingly.

Anyway, one thing at a time. Try the new CyanoBoot someone and let me know if the message is clearer now :)

cyanoboot-2012-03-16-alpha0-fullofbugs-encore.tar.gz

MD5: 2aaab6428c807faefad77aa786b28158
[Nook Color Android Development] leapinlar:
This could be caused by your wifi, even though on and in deep sleep, losing its connection to your router. Then when the screen comes back on, the wifi indicator on the status bar is not showing because wifi has no connection, not because wifi is not on. Then after a few seconds it reconnects to your router and the status symbol reshows.

This is what happens to me when I have wifi set to turn off with the screen. When turning the screen back on, there is no symbol, but when I go to settings wifi is on, just not connected. All hot spots say not in range. It takes a lot of messing around to get it to connect. Hitting rescan does no good. If I say add new network, they all repopulate and show. Wifi connects. Or I can just cycle wifi off then back on. Left to its own it never reconnects. So I just leave wifi on all the time and charge the battery every night. And of course I have the modded wifi module so I won't get SODs.
[Nook Color Android Development] keyodi:
@leapinlar -- i'm probably going to push the modded wifi module you sent me tonight. So, i hope it doesn't break anyone's wifi :)

I've been using it for a day or so without any issues, so it

should

be good.
[Nook Color Android Development] leapinlar:
Can you hold off for a day or two so I can test the battery drain with your new kernel and the stock wifi module and the modded one?
[Nook Color Android Development] fattire:
Ah screw it. I pushed the new CyanoBoot. :)
[Nook Color Android Development] HacDan:
Deep sleep has varied definitions. I'll be sure to check your dictionary before responding next time.
[Nook Color Android Development] leapinlar:
Thank you for fixing that. New users will appreciate it. I know I do.
[Nook Color Android Development] Lsjreadingpa:
Whats Cyanoboot?
[Nook Color Android Development] leapinlar:
It is the boot screen that comes up when you first boot the nook. It lets you select which thing you want to boot to, like normal or recovery. Fattire just upgraded it. You do not need to worry about it. It will come with the next nightly automatically.
[Nook Color Android Development] keyodi:
ft5x06 touchscreen devices ONLY

I need someone with a ft5x06 touchscreen to test out this kernel. This has updated touchscreen drivers from the nook tablet and I added some ICS specific fixes, but i have no way to test and see if it works.

How do you know if your nc is using the ft5x06 touchscreen drivers?

mostly likely, if you have a new/refurb nc

check the dmesg logs. It should say ft5x06 somewhere in there
[Nook Color Android Development] KingJL:
Looking for input on anything specific? I have installed the new kernel, exercised some apps, and and encountered no anomalies.

Current envirionment:

evergreen SD, CM9 (eyeballer 20130318, no-opengl), gapps-20120304, keyodi modded kernel (3/17)
[Nook Color Android Development] keyodi:
Basically, does the touch screen still work w/ the new driver
[Nook Color Android Development] KingJL:
Yes! Cannot say for sure if is any/much better, but it definitely is no worse.

Thanks for your efforts!
[Nook Color Android Development] keyodi:
It was worth a shot :) Thanks for testing
[Nook Color Android Development] mateorod:
So i made the jump to flashing my own nightly builds, but I have a question. I had seen the commits for the new boot animation but my builds still have the old animation, including the sync/build I did this afternoon. I flashed eyeballers build from last night and the animation was there.

What, if anything, am I doing wrong? I have keyodi's kernel, and the other commits are showing up (for instance, ZOMG magic optimization, worth every penny).

I do have some trouble connecting to github (I never tried the switch to http as I thought is was obsolete(?)) so maybe this is related to a sync error that just happens to let me build?

Its not a big deal just for the animations sake, but now I am wondering if I am missing anything else (more magic, greater optimization).

Is there an updated local manifest I don't know about? Do I need to make clean and/or clobber?
[Nook Color Android Development] eyeballer:
Earlier today fattire merged in the needed stuff for the build to select the right boot animation resolution.. but you actually need them. The boot animation is not merged yet, I cherry-picked it to include it in the build.

http://review.cyanogenmod.com/#change,13579 is the change you need to apply after your repo sync.
[Nook Color Android Development] numus:
nebkat -1 I would prefer that you didn't submit this

Umm... that is a retarded response...
[Nook Color Android Development] cybertimber2007:
I think they have a dropdown menu of responses... otherwise it seems odd that they all said the exact same thing with the same puncuation, spelling and case.
[Nook Color Android Development] eyeballer:
If you go through.. it appears as though the initial zips were with jpegs and caused banding, cyanogen later used pngs. And yes the review panel has 3 standard responses with the option for comments.
[Nook Color Android Development] therkr:
http://arstechnica.com/#!/gadgets/n...f-cyanogenmod-wont-enable-root-by-default.ars

Does that mean that unofficial nightlies would have root disabled also?

And I'd also like to ask: Will there be official nightlies for CM9 or just stable releases? I'm not asking "when" but what I mean to ask is whether development is still underway even for the nightlies?

Thanks. :)
[Nook Color Android Development] gbohm:
nevermind wrong forum :-(
[Nook Color Android Development] leapinlar:
Yes, it just means you have to go to settings and pick a check box before it is root. It just means that the box will not be checked by default. Look in developer settings.

Development is still heavily underway on CM9. Our nook is not officially part of the CM9 development. Fattire has a separate github to add the nook color stuff to the official stuff. He intends to merge it to the official in the future, but has not done it yet. So if CM were to start official nightlies now, our nook would not yet be part of it. I'm sure Sam and Eyeballer would keep making the builds until it is officially part of CM.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] Nburnes:
CM has official nightlies going for a handful of devices already.
[Nook Color Android Development] afzalarsalan:
Would this have any help in building a 3.0 kernel for our device? If not what are we missing?
[Nook Color Android Development] mateorod:
This is from the Nook Tablet forum, but will end up being our kernel as well. Really interesting to watch.

Kernel 3.0 development thread
[Nook Color Android Development] fattire:
I hadn't seen this branch yet... I'll have to have a look at it w/keyodi when he's 'round.
[Nook Color Android Development] SeaFractor:
If the last posts are correct, the NC has a featureset that NT doesn't, namely Bluetooth.

Interesting as this is a feature I use for remote keyboards, where the distance being short range due to a lack of antenna is irrelevant. They both sit in the same case.
[Nook Color Android Development] afzalarsalan:
This is including the fact that the NT has an OMAP4 processor while NC has an OMAP3. This can make a lot of difference, especially in kernel porting.
[Nook Color Android Development] Dj-Gutz:
I thought he is aware of this , I mentioned it here

TI guys says it's still a WIP and not all features work , we should keep that in mind

On the same note , the I9003 devs are working pretty hard and apparently making some good progress , I'm keeping a close eye on them and I would suggest you do the same and even discuss them ( maybe share ideas.. )

The community there is surprisingly good ( I've never heard of this model before :) ) , they actually donated a couple of devices for the devs and they have made some really great progress

Watch their development thread

[ROM][ICS][IML74K] EXPERIMENTAL CM9 4.0.3 Alpha 2 - DEV ONLY!

On recent comments dhiru1602 stated he is working on a 2.6.35 kernel and already fixed 2D acceleration ( no HWComposer yet tough )

They are concentrating now on camera which doesn't mean much to us , but they are working on stuff that we do have in common

dhiru1602 git

codeworkx has started a 3.0 kernel , but I don't know if it's at a state that will help much

android_kernel_samsung_latona

I'm checking updates daily on almost all OMAP3 devices , most of them are at the same point as us and some way beyond ( due to lack of devs / non-released kernel source / whatever )

The advanced ones are Galaxy SL I9003 & Motorola Defy

Are you working with keyodi on 2.6.35? How is it going?

he hasn't pushed much lately to github
[Nook Color Android Development] keyodi:
Thanks for the info. I have already been in contact w/ dhiru1602 in order to try and fix similar egl issues, but they are using the .35 kernel and some of their fixes may or may not apply to us.

As for the .35 kernel...I've taken a small break from working on it, but at this point it maybe best to start looking at the 3.0 kernel instead, which is a lot of work.
[Nook Color Android Development] keyodi:
Large Keyboard

It looks like the gpu/pvr/omaplfb files that were updated with the new 1.8 pvr drivers is what's causing the large keyboard to be displayed. I reverted those files back to the ones prior to the update, but i'm not sure how stable it will be since they are an older version.

I attached the kernel if anyone wants to give it a try
[Nook Color Android Development] Nburnes:
Now it is tiny while in portrait. Which I personally find better.
[Nook Color Android Development] mateorod:
Jeez,I was just coming in to tell you I couldn't get it to boot. Just sticks at Cyanoboot. I have flashed maybe six times without success, including restoring a backup and redownloading the posted uimage.

MD5=ca7aea...whatever both times.

It must be something I am doing. I even downloaded eyeballers latest build, to see if my build was the problem. Still stuck at cyanoboot.

Oh well. If it is just me, it's just me.
[Nook Color Android Development] SeaFractor:
Granted, but the TI set is for the SGX drivers and those are relevant to both, SGX 530 for OMAP3, SGX 540 for OMAP4.

Here's the Git for that update (3/23/2012) http://review.omapzoom.org/#/c/20739/

For the complete Kernel 3.0 git thread, you can see the posting http://git.omapzoom.org/?p=kernel/omap.git;a=shortlog;h=refs/heads/p-android-omap3-3.0

For those that wonder about the two gits, one is general and has the latest ICS SGX listed where as the second is the Kernel 3.0 development thread.

It's the 3.0 items specifically for OMAP3 that are so enticing.
[Nook Color Android Development] Dj-Gutz:
Thanks for that comment

I was pretty sure you are on par with developments on other platforms , good to know you are :)

I wish you guys luck with 3.x , I'm sure it won't be easy as almost no devices has a fully working 3.x kernel yet - especially omap3

2.6.32 > 3.x is a pretty big leap :D

Again , good luck and thanks for what you've done so far... your work is much appreciated

Damn , I wish I had the time to learn and help you , but I have to focus on my degree for now :)

I think that I'm speaking for all of us here that if there is anything we can do to help - we defiantly would
[Nook Color Android Development] taylor.fowler:
FYI, eyeballers more recent builds flashed over formatted (or corrupted I guess) /system will crap out (you need to flash a complete build first, something from before around 3/15/12). I ran into a similar issue a week or so ago.
[Nook Color Android Development] mateorod:
Yeah, thanks for thinking about it, but that wasn't it either. Just renamed it kernel, swapped it out and reflashed after wiping cache only. I did this same thing the last time keyodi posted a kernel.

Non-openGL, but I don't think that matters. Unless it does. I am probably just forgetting something very very basic. I reflashed an unmodded copy of an earlier build after the last bootloop, without even wiping cache, and it installed fine. So the flashing works and the system takes a flash no problem. I've tried flashing six or seven times, including a second flash over the first after a boot loop.

No dice. Not the end of the world, though. If the kernel gets merged, any problems will come to light, and since I am able to build and install every night, I can live with it. Weird, though.
[Nook Color Android Development] leapinlar:
I had trouble the first time also. Just like you. Stuck on loading. I deleted it off my system, redownloaded, unzipped fresh, and it worked that time.
[Nook Color Android Development] mateorod:
Well, if it's not just me I feel better. I already downloaded twice, but once more can't hurt. I'll update this post in a minute.

Edit: Well, this time it worked. No change to the process. MD5 sum is the same each time. Huh.

I might keep a copy of the old kernel on hand if this gets merged. This keyboard is really tiny. I'll give it some time to see, but i have really big thumbs. Thanks for putting this out there keyodi.
[Nook Color Android Development] afzalarsalan:
Is opengl still working with this kernel? :)
[Nook Color Android Development] SeaFractor:
Talk about busy!

http://review.cyanogenmod.com/#q,status:merged+branch:ics,n,z

The link shows the merged and wow a lot of video related items. Interesting to see the result in the nightlies tomorrow.

I'd been watching some of these for some time just to see when they would be merged.
[Nook Color Android Development] fattire:
BTW I talked to arcee last night re the 3.0 kernel... he said that he thought the omap3 branch was for OEMs mostly it's still not ready for prime time tho... dunno if we should work on it at this point or not...
[Nook Color Android Development] Nburnes:
Random question: Does anyone have a new copy of CWM they would be willing to share with me? Got stuck in a bootloop, so fixed with older v3.0.2.8 and I greatly miss the blue.
[Nook Color Android Development] DigitalMD:
ClockwordMod in .zip format:

3.0.2.8 is here: http://xdaforums.com/attachment.php?attachmentid=580726&d=1303999348
[Nook Color Android Development] Nburnes:
Thank you, but I was looking for 5.x.x.x
[Nook Color Android Development] leapinlar:
Racks posted one a few days back.

http://xdaforums.com/showthread.php?p=23537853
[Nook Color Android Development] mateorod:
My build keeps breaking during the building of StageFrightRecorder and libstagefright media player. I saw there is a new commit merged with changes to this. Also, at this point, there is no new build for either Sam or Eyeballer, when by now usually they would both be up. I started a clobbered build, but that takes me (*gasp*) 13 hours to build, so I won't know if that fixes the problem for quite some time. Just wondering if anyone else craps out at that point as well.

Edit: Okay, it books like the the build has progressed past the StageFrightRecorder, so the clobber fixed whatever problem I was having. Nevermind.

Edit2: Spoke too soon: Broke again at same spot. The new commit makes me suspicious. Still no builds from Sam or eyeballer, either. I guess I'll try and see if other devices had the problem. Maybe Ricardo's commit broke the whole build process. It looks like he okayed it himself.

Ah...

Uploaded and then merged 5 hours later by the uploader (though not author) himself, it looks like. That can lead to problems, I bet. Most likely works for his specific device he maintains or uses, one with hardware acceleration. There are probably a lot of broken builds this morning.

Last Update: Looks like it was fixed with a merge around 3:30 am. Five minutes after I clobbered and resynced. Sigh.

Change-Id: I4855bb4b212db3cf34433ab47eb568db8df14f6a
[Nook Color Android Development] fattire:
Heads up-- cyanogen is gonna merge 4.0.4 today, so who knows what breakage if any this will introduce.. hopefully will add some new fixes and stuff too (?)
[Nook Color Android Development] Homer_S_xda:
Any chance at getting proxy working? It works in 7.1-2x but not in 9.x. I use AutoProxy (free version in Play Store).

Homer
[Nook Color Android Development] fattire:
Built quickly.. haven't tested anything..

A quick build... 4.0.4

Note that there were two merge issues that Cyanogen fixed but forgot to push before going to sleep--

The first can be fixed with this quick and easy patch and the second with this one-- thanks to pershoot for making it easy.

No doubt these will be fixed tomorrow but if you wanna try it, that's all you have to do.

Update: They're fixed.
[Nook Color Android Development] j4mm3r:
Enable NAT in the kernel

Hi fattire,

I wrote this kernel config to enable NAT support so that tools like proxy droid can work. Can you add this to the nook_kernel repo and maybe build the kernel against it in the future?

(i've been compiling my kernels with this instead of the one in the repo since past few months now, there are no changes except for the NAT stuff)

/j4mm3r
[Nook Color Android Development] shumash:
Error at repo init

So I'm jumping into trying to roll my own, and I get the following error when trying to "repo init":

./../bin/repo: line 1: syntax error near unexpected token `newline'

./../bin/repo: line 1: `<!DOCTYPE html>'

Any ideas?
[Nook Color Android Development] mateorod:
I am going to guess you minimized the browser window when you copy/pasted the repo unit command. The command line reads things like spaces, tabs and carriage returns as part of your argument. Make sure the command is all on one line before you copy it or type the command manually and see how that goes.
[Nook Color Android Development] shumash:
Thanks, but I figured it out. The repo script was a "404 not found" message, so it wasn't a script. BTW, it turns out, at least with Ubuntu 11.10, that absolute addresses to set the adb/java path don't work (refer to your answer to a question I had in the wrong thread). I had to change it to ~/ relative address, and the path was finally set.

EDIT: And I was finally able to run the repo script, but I had to preface the command line with "bash" to make it run.

I really appreciate the help you've been giving me. Thanks.
[Nook Color Android Development] mateorod:
Glad it's working. As far as absolute paths go, I have my paths set as absolutes and they are working. I just set up a fresh Environ,went on anew machine this morning. However, I have made the mistake of doubling up on the /user part. As in, ~/home/mateorod/... and that does not work, for sure. The ~ is short for /user, so that was just a bad path, not absolute.

But I am glad its working. I've never tried using bash there.
[Nook Color Android Development] fattire:
An update... newer 2.6.32 kernel!

We have another surprise for y'all...

SO! (a little background)

While the 3.x omap3kernel is still in development by TI and not really ready, keyodi and I, following a suggestion from epsylon3 (of the defy), decided to look at our existing 2.6.32 "long term" kernel source to see what we could do for it.

For those of you who may remember, we're currently using 2.6.32.9 as a base and have been since this was provided by BN back in the day.

However... 2.6.32.9 is kinda old as 2.6.32 goes. In fact, you can this version got tagged about halfway down this link. Click through 26 more pages of fixes since then and you'll get to the end, where keyodi just finished bringing our kernel...

So the latest encore version is now 2.6.32.59!

What's better in .59? Well, it's +.0.0.50 better, isn't it?! It's got a year worth of fixes-- from Feb, 2010 to Feb 2011 added. You can go through the 27 pages of commits and see if you can figure out what's changed. It's mostly bug-fixes, but if you find something works now that didn't before or something interesting on that list, let us know.

So here, for your testing pleasure, following a

ton

of work from keyodi (he merged in ~2700 commits for you people!)...

2.6.32.59 for encore CM9

A fresh, newly matching wifi module to go with it

NAT support as mentioned above.

the latest cyanoboot, as modified recently by tonsofquestions.

If this gets a thumbs up from everyone, it's going in the repo. You have 24 hours to register your complaints. GO GO!

And post any bug-fixes or enhancements of interest you find and whether they seem to work better for ya. (I got the ball rolling with an observation in the next post...)

update-encore-kernel-2.6.32.59.zip

md5: 1326dea4f6f3b3269951de66cf85bbad

(source for kernel-- see the cyanoboot thread for cyanoboot source)

Whether it works or crashes or whatever-- you all owe keyodi some serious "thanks". And tonsofquestions too for a great job with cyanoboot.

WARNING AS USUAL, YOU USE THIS ENTIRELY AT YOUR OWN RISK. SEE ALL APPLICABLE DISCLAIMERS IN THE GPL AND ELSEWHERE IN THIS THREAD.
[Nook Color Android Development] fattire:
One discovery...

So it's actually fun looking at what may have been added. Check this out:

OMAP3:Enable Linux Page Swapping by default

Apparently, we can use an emmc-based swap... (and it's on by default) :eek:

Who wants to try it? (note it will require repartitioning and adding a swap partition... but then... more memory?!)

Who will step forward?
[Nook Color Android Development] rampart51:
I run CM9 on an SD card.

Flashed the new kernel and all is well so far.

Thanks Fattire, keyodi, and tonsofquestions!
[Nook Color Android Development] Henk Poley:
Does 2.6.32.59 contain any potential fixes for the sleep of death?

I'm not too intimate with the hardware of the Nook Color, but these seem relevant:

USB: MUSB: Do not enable TX and RX DMA at the same time <-- is in 2.6.32 branch

drivers: misc: ST KIM fix panic when gpio un-available <-- is in 2.6.32 branch - related to CM Issue 5011?

OAMP3:UART : Correct the UART 1 and 2 Pad Configs for wake-up <-- is in 2.6.32 branch

PM: Deny MPU idle while saving secure RAM <-- is in 2.6.32 branch

Edit: I found the above through the on-site search function, it appears not all of the above will be in the p-android-omap-2.6.32 branch..

Edit2: Checked all 4 of them, they are al in 2.6.32
[Nook Color Android Development] friedsonjm:
Would love to try this - could you tell us how we incorporate it, or is this only for folk 'rolling their own?' thanks.
[Nook Color Android Development] ziggy34:
Just flash like you do a rom
[Nook Color Android Development] friedsonjm:
OK, up and running now on the openGL version of 4/3/2012. AnnTuTu test shows no speed change, will continue to test for stability, etc.
[Nook Color Android Development] Nburnes:
SOD with the new kernel D: Installed about 4 this morning, came back here at 9 and had to force reboot.

Edit: should hsve pulled kmesg
[Nook Color Android Development] Homer_S_xda:
DING - DING - DING

Promoted to daily driver on this one. Consider a beer of your choice waiting in your special place!

Homer
[Nook Color Android Development] jewnersey:
I'm going for it. Just following the instructions from omapzoom

Scratch that...not knowledgeable enough.

Should I format emmc then repartition then flash zip then copy swap file into the fs?

....Way to new to Linux...