yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] krylon360:
actually turned out to be a couple of edits to init and boarconfig.

on my 10th reboot now and wifi still works :)

Our media_profiles.xml seems to be causing a major bug, and needs to be recoded which I will work tonight. It Causes some issues during boot which makes it loop a couple of times before the system says YOU SHALL PASS!. So I am going to look into that next.

Here's where it dumps: http://pastebin.com/X2fGwg2H

If you get to this point where it's just a never ending loop, with the above errors, hold power, then boot into recovery and wipe cache/davlik. That will get you back into the system.

If you do a adb reboot while in this error state, you'll just sit at a black screen. o.0

There is a memory leak I am trying to track down which causes this. You can tell you are going to have the issue if you reboot through the power menu and you just sit at a black screen like the device is off....

so just hold the power button down and boot to recovery through cyanoboot.

pushed a lot of changes, including prebuilt pvr modules :) can't seem to get the kernel to build them on the fly though.

Also pushed the audio_hw.c source I've been using and the Android.mk file to go with it.

Those building at home, you'll notice that BT is an issue. I took the source out from building for now since your logcat is probably full of errors from uim-sysfs. Will have to look into what is causing the BT issue and its source.

One thing I am going to look into is something I found on omapzooms git repo. http://git.omapzoom.org/?p=platform/external/bltsville.git;a=summary

It's for 2D acceleration, and it's not merged into the mainline. Gonna see how it works out.
[Nook Color Android Development] krylon360:
looks nice, but would have to be recoded:

"It's at 80 fps and a total of 240 frames, and it should work on any device whith resolution of 1280x720."
[Nook Color Android Development] ManelScout4Life:
I used the andbot method and got it to boot up, I'm sitting at the lockscreen now....

but the touch screen doesn't seem to be working...
[Nook Color Android Development] eyeballer:
Can you pull a logcat and kmsg?

In two different terminals/cmds:

'adb logcat > logcat.log'

and

'adb shell cat proc/kmsg > kmsg.log'

Then touch the screen, swipe it. Then ctrl-c to cancel in both windows and the two logs should be in the dir you are currently in. Pastebin them and post here.. You can scan the logcat for anything personal but since I assume it's a clean install probably no need.
[Nook Color Android Development] ManelScout4Life:
adb isn't seeing the nook plugged in. I was on the aokp rom when I pulled the proprietary files. Should I be on a cm9 rom when doing that or does it not matter? thanks for the help btw.
[Nook Color Android Development] cybertimber2007:
In comparision to CM9, Wifi seems to die if it goes to sleep for awhile and Wifi is set to "Keep Wi-Fi on during sleep: Only when plugged in" and "never". If it's set to always, no issue with wifi after sleep.

What's the wifi default in JB? I'm not sure if that will help, but it might be a workaround. I need to grab a logcat and look over it to see if there are any hints there.
[Nook Color Android Development] frankusb:
Have you picked up the kernel change here? MiRaGe KANG has been using gcc 4.6+ to build the kernel for a while now.

Frank
[Nook Color Android Development] krylon360:
That's not the issue. The 3.0.8 kernel source we are using doesn't like the 4.6 toolchain. The .32 kernel source compiles and boots just fine with it. If you compile the 3.x kernel with it, it will boot to a black backlit screen.
[Nook Color Android Development] eyeballer:
Does it work for us? Go ahead and test :D
[Nook Color Android Development] krylon360:
Same props. So doesn't matter.
[Nook Color Android Development] fattire:
So these pvr modules-- do they require a newer kernel tha tdoesn't have pvr built-in? Is there source for that?

Also, re: audio_hw.c -- right now the source is in there but we're not building it at all. We're including a prebuilt audiolib-- do you have a new working one to use?

re: uim-sysfs -- I know it's noisy, but wasn't BT working before?
[Nook Color Android Development] jschill31:
Hello,

Bluetooth did turn on for me but I did not try to connect to anything.

Cheers

BTW, I am also going to set up a different build machine that I have at my workplace. I know it sounds funny but I have been building CM9 on it for over a month and it is 12.04 and only 32bit...kinda goes against the rules doesn't it. There were several patches needed, so many I do not know if I could do it again at this point. It was a pain in the rear to get set up but does allow me to do builds while at work.
[Nook Color Android Development] fattire:
Yeah I just did a build after re-enabling uim-sysfs and it did work fo rme. I see my laptop under "available devices".

Also, krylon what's the ril file you added?
[Nook Color Android Development] krylon360:
Pvr isn't built into our kernel. we do have a drivers/gpu/pvr but its missing some stuff and its pretty different than what omapzoom has in their 3-3 kernel source which is what ours is based on.

The audio stuff I added, it builds the primary's.

Uim, yes it was working....I think, we (eyeballer and I took it out only temp. Going to edit the source so it isn't so noisy tonight.

That ril file isn't even needed by our device bit its called by the audio_hw.c source. There's still some stuff I need to do to it.
[Nook Color Android Development] ManelScout4Life:
I rebuilt it a few times still no touch support. ADB is off by default which is why I can't connect to it
[Nook Color Android Development] jschill31:
Hello all,

Can anyone explain why I continue to have a black screen when trying to wake? I thought it had something to do with the lock screen at first but even with it off I only get a black screen. It seems the only time the unit will come back from screen off is within a few seconds of turning it off. Is anyone else experiencing this?

Thanks in advance

Update:

After a wipe of both dalvik cache and cache I can boot to a display again but still have a black screen after any sleep time longer than a few minutes. BTW, it seems both audio and wifi are surviving after re-boot now...thanks Krylon! I wish I had any kernel experience but I am at a loss.
[Nook Color Android Development] swaaye:
Yea this alpha release is surprisingly usable. It doesn't draw as fast as CM7 yet but it's nowhere near bad. It does feel smoother and faster in some ways even.

But I see that the non hideable Honeycomb bottom bar is there. I really hope somebody can get that thing to hide so we have true fullscreen again. I want my usual fullscreen + Button Savior setup again...

emmc storage looks non functional.
[Nook Color Android Development] fattire:
I totally cheated, but got some pics...

How about screenshots?

(note: I totally cheated to get these shots. Quadrant's score, while meaningless, is the result of a max setting of 1200000 w/interactivex, via SetCpu. No use of Tablet Tweaks...)

(note #2-- I used ddms. If you installed adb the "right way" from android's sdk, it's in the /tools directory. Should be obvious how it works.)

(note #3-- please don't spam up the discussion with screenshots. These were meant as examples. Spam up another thread, preferably in the "general" section.)

Cheers.
[Nook Color Android Development] j21blackjack:
Has anyone tried installing the chainfire3d drivers to play Tegra 2 games yet? What's the default screen density for ics?
[Nook Color Android Development] rigy73:
Ohh.. man i planned to free up 20Gbs of space today, then install linux partition, download everything for a day, setup sdk and everything, and then do a full compile from source, but as soon as i saw these screens, i clicked on that zip file as fast as possible :D
[Nook Color Android Development] guy2545:
Downloading the sdk and setting up my build environment. I am current regulated to building on my Ubuntu 11.10 atom2 based media server over ssh. I wonder how long it will take...or if it will even work.
[Nook Color Android Development] MrColdbird:
Long... long long long... I had to do that when I first compiled CM7...

Get a nice DVD and watch it, something along the usual 2 hour blockbusters... :)
[Nook Color Android Development] Ronin3178:
Did a factory reset then wiped cache/davlik after flashing zip. installed 8/28 Gapps, after I found the post about the four corners to get around the "Touch Android to begin". Got Market working, installed Adobe Flash 10.1.106.16 from a file I had saved, don't have (can't find on market) the Youtube app, but browser youtube plays vids in HQ, obviously no sound, but they play.

Tried restoring Youtube App from TB of CM7, said it restored, but didn't appear in list of apps. Drocap2 works, first shot was screwy, but second was fine.

Just listing my experience.
[Nook Color Android Development] biohazrd51:
Shortly after my post about skipping setup, someone posted the ICS gapps. Use those.
[Nook Color Android Development] zorvalth:
I'm not sure your adobe flash backup will work because adobe said they will release next and last ever flash player for android for ICS in january...

http://androidcommunity.com/adobe-says-flash-for-ics-will-be-last-supported-os-20111121/
[Nook Color Android Development] thirteen113:
How do you secure your wireless? I seem to remember some android devices having problems with either TKIP or AES when using WPA2.
[Nook Color Android Development] sednafx:
I am using the same router. If I am not mistaken AES is for WPA2 and TKIP is for WPA. I tested mine on auto. Which can choose either combination. When I get off work I will test them individually. And will also test WEP. If I remember correctly I had a similar issue when the devs first ported CM7 to the NC. Lastly I am going to try to copy my configuration file from my CM7.

In any event I want to thank the devs for their work and for this sneak peek. In no way am I complianing. Very happy to be experimenting with ICS on my NC.
[Nook Color Android Development] sushkov:
Hi,

I'm trying to flash the zipfile using clockwork 3.2.x.x but I get stuck at cyanogen loading screen.

What version did you use to flash the zip?

Gapps are mandatory?
[Nook Color Android Development] Homer_S_xda:
Anyone able to successfully run gapps under ICS running on SDcard via Verygreen's 1.3? I can fake it to flash (change name from gapps-ics-blah to gapps-gb-blah) but then get stuck with the "Nfc Service has stopped" loop. I've tried a couple of 111125 versions and the 111128 version with the same issue.

The ICS preview definitely flashes on Verygreen's 1.3 fine. I flashed, got it boot and connect to wireless (N with WPA2/AES) with no issues other than big fingers (mistyped my password the first time).

Homer
[Nook Color Android Development] biohazrd51:
There was some posts about it earlier and being related to google wallet. Are you able to remove/disable it and see (I didn't read too much into those posts).
[Nook Color Android Development] capnblackleg:
In the Market, I went to download Flash and it says "device not compatible". I realize video is not working but it seems like Flash should still be able to install.

Edit - Other than the occasional FC, everything that is working is really great. I mostly use the NC for web, email, and reading so I don't plan to switch from this for the foreseeable future. Battery life even seems better to me.
[Nook Color Android Development] JonMayer:
There is no Flash app for ICS yet. Adobe's final version of flash for android will be an ICS version soon.
[Nook Color Android Development] foltz61:
This is good enough to be my daily rom. Thanks. Gonna try to fgure out how to move the nav buttons to the right side though.
[Nook Color Android Development] noisufnoc:
Looks great here too, only gripe is that my work's Wifi doesn't connect. Both our network that uses 802.1X and WPA2 PSK. Home wifi worked like a champ.

I'll do some poking around and let you guys know.
[Nook Color Android Development] swaaye:
if you discover a way to enable fullscreen or move that bar please post about it! :)
[Nook Color Android Development] msaraiva:
802.1x with MSCHAPv2 worked just fine here.
[Nook Color Android Development] krylon360:
the black screen is a known issue. we are working on it and I'm hoping this build Im getting ready to flash fixes that. the device wakes up, as seen in logcat, but something isnt kicking. its def a sensor or lights issue.

The 3 things really holding us up are the sleep issue which I just described, the media_profiles issue which will cause a never ending bootloop until davlik and cache are wiped, and video decoding with the TI decoders.
[Nook Color Android Development] krylon360:
media_profiles bug seems to be squashed now. resync :)

https://github.com/fat-tire/android_device_bn_encore/commit/e126bf3b165d9b21401156db0289aec03e7af350

Oh, and whoever said you can't play HQ YouTube vids without HWA..... put down the pipe.

[YOUTUBE]2glU-M8cttg[/YOUTUBE]
[Nook Color Android Development] krylon360:
fattire and I made the decision tonight to change our source for omap3. I am working on getting everything set up so it will compile.

Biggest change in this source, it contains ion souce, full dspbridge source, contains a new liblights source which might be useful for our deep sleep issue...(the screen turns back on, but thats it; its just a backlit screen with logcat working.) and....wait for it....hwc source. :)

Hope to have it ready before I leave work at 7a..that's 3 hours from now. The original source is on my github, with one change so far which fixed a bug which was introduced when TI merged it.
[Nook Color Android Development] krylon360:
well that sure was a pain in the ass.

https://github.com/Krylon360/android_hardware_ti_omap3

dont add that to your local manifest yet though. still needs to be tested. I think Im done for the night. lol
[Nook Color Android Development] krylon360:
2 Kernel changes which I will try to get to tonight if I can. (my weekend starts today)

These fix memory leaks associated with DSP Bridge and the Camera Drivers (in particular omap_resizer)

Unless Keyodi gets to these 1st, not sure if he's back yet or not.

OMAP3:DSP BRIDGE: Fix for the bridge_open memory leak.

The two members of pr_ctxt allocated during bridge_open that
are never freed resulting in memory leaks, these are stream_id and
node_id, they are now freed on bridge_release.

Error path for bridge_open is also fixed.

Change-Id: I0526e9be97c7943e8aafc147e439718e0c68ad37

http://review.omapzoom.org/#/c/25440/

OMAP3:CAMERA: Fix for the memory leak in camera.

The member of ofh allocated during the vout buff prepare that was never freed
resulting in memory leak. ofh->vbq released in vout buff release.

The two member of file handle structure are not released, resulting in memory leak.

The above two cases has been taken care in this patch.

Change-Id: I4f95a17dfdf7e0d2a90e5bc7394157289f6ebbef

http://review.omapzoom.org/#/c/25443/

Sorry for the post spam. Just felt it was easier to keep track of changes done tonight with separate posts.
[Nook Color Android Development] fattire:
Hey Krylon-- having problems with irc, but anyway-- I haven't really been able to take a long look (and will be out most of the day) but I think we want to preserve history rather than start with a flat list of files. This will allow us to quickly know what has and hasn't been committed, such as omap3-specific stuff from the omap3 branch.. (we'l lbe able to just look up the commit, for example).. and it will allow us to stay in sync with upstream. (by just pulling newest changes and applying automatically) Easiest thing to do is to just use the original branch with all its commits, then apply what you did as well as another commits on top. If you can consolidate all the changes of a certain type (say LOG->ALOG) into a single commit, that will be way easier to follow.

Take a look at this for a reference. I suck at git, but I'm trying to get better :) I think you can literally do a git diff COMMIT1..COMMIT2 > thechanges.diff then git reset --hard back to the top of p-ics-mr1 (or really, start with a branch w/history), then git apply the diff, and then do a single commit "my changes to mr1 for jellybean" and it'll do all in a single commit, and that way we have history, one commit, and we're good :) Should take like a minute to do if you start with the version with history. Just branch p-ics-mr1 into "jellybean" and then apply your thing on top and that's it!

As for the kernel, I'll take alook at those commits.. do you not have access to keyodi's repo?

Back tonight.. nice work!
[Nook Color Android Development] ManelScout4Life:
I'm fowarding this PM on to here.

I hope this helps with the touch screen issue!
[Nook Color Android Development] haze_nme:
I am building right now with your omap3 and the two commits for the kernel. I will report how it goes in a bit.

-edit1: Had to remove libion dir from system/core/ to get the build started.

-edit2: Made these changes to use the header files from frameworks/native

https://github.com/fat-tire/android...mmit/efbb6b2de5fa16ef72bbf02526e3c0a7a6d63a4f
[Nook Color Android Development] eyeballer:
Yep, looks like we need to get those drivers from the .32 kernel. Guess the rest of us have the older nooks :)
[Nook Color Android Development] ManelScout4Life:
Just as I had given up I received that PM. I'm very glad the issue can noe be solved! thanks a lot!
[Nook Color Android Development] tomsawyer14:
I'm trying a jellybean compile right now for the sheer hell of it. It's on an older C2D laptop with 2GB RAM so it's taking awhile but I'm having fun watching it every once in awhile. Even so it seems to be faster than my last CM9 attempts in a VM.

Sadly, nothing constructive to add aside from a large THANKS to all you guys that have made this possible.
[Nook Color Android Development] newellj79:
I'm trying to get reset up for building. My first repo sync gave a a ton of fatal errors and crapped out. I probably won't get back to it until early morning but I'm looking forward getting back in the mix.
[Nook Color Android Development] fattire:
Yeah so the NC has two versions with two different touchscreen hardware/drivers and I don' tthink the newer one has made it to 3.0 yet.

Anyone wanna volunteer to add it? Might just be a matter of adding to the baordfile and turning it on in defconfig..

I don't think any of us were able to test (not having new nooks) hence it's not in yet.
[Nook Color Android Development] ManelScout4Life:
the touch screen works fine in every other rom I've tried. I can test a fix no problem
[Nook Color Android Development] fattire:
On your mark... get set....

Okay, so the steps are basically to make sure that in arch/arm/mach-omap2/board-encore-peripherals.c that the ft5x06 driver is initialized and powered and everything. Some changes may need to be made as well.

Look at the .32 kernel as a base to see how it was done, then compare with the 3.0 version. Make them "match up" so that the same things being done in .32 is being done in the 3.0 way.

Then, you'll need to make sure that the Makefile and Kconfig (both in arch/arm/mach-omap2) have options for turning on the ft5x06 driver. Then make ARCH=arm menuconfig and locate the touchscreen driver in the menu and turn it on.

Then build a kernel and try it. If it works, copy your .config to arch/arm/configs/encore_defconfig. Then submit a pull request to keyodi so he/we can all try it and marvel at your genius.

First one to get the touchscreen driver working wins... um, our deepfelt thanks?
[Nook Color Android Development] fattire:
Update on the omap3 repo- - I moved krylon's stuff w p-ics-mr1 history to this branch for now and consolidated into a single patch.

realized I have a typo "m41" instead of "mr1" in the description... but anyway, this is just an experimental branch to see if hwcomposer will work (eventually). I'm guessing at some point TI will move that stuff into jb-dev at which point we can grab it from there. But for those of you building who want to try it, go for it...

https://github.com/fat-tire/android_hardware_ti_omap3/commits/p-ics-mr1
[Nook Color Android Development] haze_nme:
If anyone with a newer touchscreen would like to test the changes, here is a kernel repo with the memory leaks (possibly) fixed and the ft5x06 drivers.

https://github.com/hazenme/ti-omap-encore-kernel3

Just change this:

<project name="keyodi/ti-omap-encore-kernel3" path="kernel/bn/encore" revision="encore-omap3-3" />

to this:

<project name="hazenme/ti-omap-encore-kernel3" path="kernel/bn/encore" revision="encore-omap3-3" />

-edit: I needed to fix the commits so they can be cleanly merged into keyodi's repo, so I am starting from scratch. Should be working in about an hour.
[Nook Color Android Development] ManelScout4Life:
I'll test this later tonight. I'm sure someone else will be able to beat me to the punch though
[Nook Color Android Development] fattire:
Hey krylon360-- trying to find you. There were still a lot of things missing from omap3/p-ics-mr1, so I've updated the repo so that it builds. Take a look.

I can now build, boot, and I think dspexec (formerly cexec- I changed it to maintain compatibiltiy with our device) connects and all that.

Now I can view Youtube HQ videos no problem (sw rendering) but when I try hwa:

E/WVMExtractor( 979): Failed to open libwvm.so

E/OMXCodec( 979): failed to allocate node OMX.TI.Video.Decoder

I/OMXCodec( 979): [OMX.google.h264.decoder] AVC profile = 100 (High), level = 31

I/OMXCodec( 979): [OMX.google.h264.decoder] video dimensions are 320 x 240

I/OMXCodec( 979): [OMX.google.h264.decoder] Crop rect is 320 x 240 @ (0, 0)

E/SoftAVC ( 979): Decoder failed: -2

E/OMXCodec( 979): [OMX.google.h264.decoder] ERROR(0x80001001, -1007)

I/SoftAAC2( 979): Reconfiguring decoder: 44100 Hz, 2 channels

E/MediaPlayer( 2212): error (1, -2147483648)

... test video (local):

E/WVMExtractor( 107): Failed to open libwvm.so

E/OMXCodec( 107): failed to allocate node OMX.TI.Video.Decoder

I/OMXCodec( 107): [OMX.google.mpeg4.decoder] video dimensions are 352 x 288

I/OMXCodec( 107): [OMX.google.mpeg4.decoder] Crop rect is 352 x 288 @ (0, 0)

D/MediaPlayer( 1836): getMetadata

I/OMXCodec( 107): [OMX.google.mpeg4.decoder] video dimensions are 192 x 240

I/OMXCodec( 107): [OMX.google.mpeg4.decoder] Crop rect is 190 x 240 @ (0, 0)

I/OMXCodec( 107): [OMX.google.mpeg4.decoder] video dimensions are 192 x 240

I/OMXCodec( 107): [OMX.google.mpeg4.decoder] Crop rect is 190 x 240 @ (0, 0)

I/SoftAAC2( 107): Reconfiguring decoder: 32000 Hz, 2 channels

(still plays tho)

I think it could be close, and I'm wondering if those media_profile things you set up are right. I could get some things to play (albeit in software) that wouldn't play before just by using the same media_profile.xml as NT uses.

Again, I renamed cexec to dspexec.. just so you kno Also, I'm using the libion in hardware/ti/omap3 not the one in system/core so delete that as well.. :) Dunno if they're the same. if so we should get rid of the ti libion...

Should be able to build with the p-ics-mr tree now and dspexec (formerly cexec) should be working.
[Nook Color Android Development] krylon360:
Sorry had to run. The codec issue is from media_codecs.XML that's new with JB.

Still need to work on that one. The media_profile file I did last night fixed a bug where it would kill the media process on boot.

Lvm.so has been an issue from the start. There is a open change on cm that hides the error.