yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] mateorod:
There will be an error message if the script cannot find a file, as it pulls the files. make sure your device is running cm9 NOT cm7 when you run the script. That changed in late February, but the only place I saw it mentioned was a comment on fattire's Google doc by eyeballer. I downloaded the directions the first time, and comments aren't included in the download. I almost missed that change.
[Nook Color Android Development] shumash:
I was running CM9 and watched it download the files so I got that part. It's just not easy to figure out what make file is producing the error so that I can find the file. It's like feeding a baby that keeps crying for stuff but can't tell you what it wants!
[Nook Color Android Development] mateorod:
It can look successful and not be so if you are in the wrong directory. The instructions can e easily misread as this section says to install the proprietary files as per original instructions, but then goes on to describe another step in the same sentence.

Were you in android/system/device/bn/encore when you ran

./setup-makefiles.sh

If you are not sure, you can go ahead and do I again with no harm. I would recommend a make clean or clobber too, since you haven't gotten very far.
[Nook Color Android Development] keyodi:
New Kernel

Well, we decided to push the 2.6.32.59 kernel and wifi module into the repo. So, eyeballer's and Samiam303's builds should have the latest kernel by tomorrow.

What's Fixed

keyboard layout issues and key sizes

Wifi module preventing sleep and pinning cpu at max

wifi SOD - we'll see

What's New

PVR drivers backported from the omap3-3 kernel. *non-opengl versions may notice increased 3d scores in benchmarking. No noticeable improvement in opengl builds
[Nook Color Android Development] fattire:
Heh at this point if you get SODs, it's your fault.

(unless I start getting them again, in which case fine.)

But I think sleeping works pretty well now.

Incidentally, this new kernel makes the hacker's keyboard look awesome again.

Everyone go up a post and thank keyodi.
[Nook Color Android Development] SeaFractor:
May notice? I noticed! 19.4fps on Nenamark1. Very close match to the scores from CM7. 2 kang.
[Nook Color Android Development] boyoboyo:
Which build?
[Nook Color Android Development] eyeballer:
For those building along at home there's a new "optional" component you can add to your builds.

Up until a few days ago the CM rom repos and kernel repos were always built separately. Development on the kernel source took place but then it relied on someone (usually the device maintainer) to then build the kernel with the latest source and upload it to gerrit and merge it as the "prebuilt" kernel for it to be available to everyone as a binary and included in the roms you build. In our case, keyodi has been providing flashable builds of the new kernel to test widely before updating the prebuilt kernel - although his changes were pushed to the source 4-5 days ago.

A few days ago this was merged into CM, which allows the kernel source to be downloaded along with the main cm/device source and builds the kernel as part of the rom building process. This is designed to remove the burden of always keeping the prebuilt up-to-date as well as letting everyone else get the latest kernel goodness as it happens... This update needed some minimal changes to the device configs which we merged in last night.

In the case of encore, things are a little different since we're still alpha and hosted on fattire's git not the main cm repo but the way it's set up now it'll mostly work the same. In order to build the kernel with the rom all you need to do is add the line below to your local_manifest.xml in /.repo (in addition to the line you already have to get the device repo from fattire's git) then repo sync.

<project name="keyodi/nook_kernel" path="kernel/bn/encore" remote="gh" revision="ics-kernel" />

This downloads the source and places it in the correct place for it to be picked up by the CM build system. After that, it's all auto-magical :) -> your build will take 1-2 mins longer to complete due to the kernel compile.

As I mentioned, this is optional, if you don't do it then the system will fallback to using the prebuilt kernel as if nothing happened (as of last night the prebuilt is up-to-date - see previous two posts).

For those using my nightlies, I'm switching to building the kernel too, so any latest changes that keyodi pushes up will be automatically included. :)
[Nook Color Android Development] Dj-Gutz:
Are we any closer to UI acceleration?
[Nook Color Android Development] shumash:
Yah, did that, same story. I'm beginning to think it has something to do with trying this in Ubuntu 11.10, although I'm also sure that many have been successful.
[Nook Color Android Development] friedsonjm:
7.33 on Nenamark2, with openGL build 4/17 and force GPU checked on; about 6.5 with it not checked.

19.3 on Nenamark1

Max mHtz at 1200.
[Nook Color Android Development] khaytsus:
The arrows are there, just like they've always been. At some point you could enable them full time, which IMO was silly and annoying, but they've never been "eliminated".
[Nook Color Android Development] Dj-Gutz:
TI has released some interesting stuff , take a look

TI Android ICS 4.0.3 DevKit 3.0.0

This release package provides Android IceCream Sandwich (ICS) 4.0.3 distribution for TI's Sitara(TM) AM3715 ARM Cortex(TM) A8 Processor.
The DevKit provides Android sources with pre-integrated SGX (3D graphics accelerator) drivers, TI hardware abstraction for Audio, WLAN & Bluetooth for TI WL1271 chipset, USB mass storage, etc.
Debug and development tools like ARM GCC tool chain, TI's Code Composer V5 with ADT plugins, are provided to enable Android embedded and application developer to easily build custom Android solutions for non-phone market segments.
The pre-built images in this DevKit package has Android default apps, multimedia files, RowboPerf performance and benchmarking utilities to help user evaluate and quickly prototype AM3715 based Android products.
Kindly refer to documentation section to start development and experience Android on AM3715 EVM, Flashboard and BeagleBoard platforms.

TI Android ICS(Ice Cream Sandwich) 4.0.3 DevKit 3.0.0 Release Notes

I hope this can be useful for the nook as well , and maybe get us forward to 2.6.37 :)
[Nook Color Android Development] DigitalMD:
Looks like a good find. Thanks
[Nook Color Android Development] shumash:
Advice for those who want to use Ubuntu 11.10:

Don't, too many issues with Canonical and Sun Java versions and dependencies.

Running 10.04 in a VMWare box and got a successful build.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Awww, fudge:

make: *** [out/target/common/obj/JAVA_LIBRARIES/framework_intermediates/noproguard.classes-with-local.dex] Killed
[Nook Color Android Development] Nburnes:
I've been building on 12.04 fine. http://www.liberiangeek.net/2012/04/install-oracle-java-jdk-7-in-ubuntu-12-04-precise-pangolin/
[Nook Color Android Development] Dj-Gutz:
One more thing I noticed is that Defy has OMX running somehow on .32 kernel

comparing our BoardConfig.mk

#HARDWARE_OMX := true

to defy's

# OMX Stuff
HARDWARE_OMX := true
TARGET_USE_OMX_RECOVERY := true
TARGET_USE_OMAP_COMPAT := true
BUILD_WITH_TI_AUDIO := 1
BUILD_PV_VIDEO_ENCODERS := 1

android_device_motorola_jordan

Searching through one of their dev threads got me to this post

Seems HQ youtube works for them , can their solution work for us too?

Might be a temp solution till we get updated H/W codecs...

Edit :

https://github.com/fat-tire/android_device_bn_encore/blob/ics/device.mk

https://github.com/tpruvot/android_device_motorola_jordan/blob/ics_mb525/jordan.mk

Also yields some interesting diffs...
[Nook Color Android Development] mateorod:
HQ youtube works for me.

Not so much HD, of course.

Edit: while we're at it, built with 11.10 on multiple computers, in and out of vm's. No real problems, although it was smoother when I didn't install the restricted extras package. Congrats on the build shumash. You sure stuck with it.
[Nook Color Android Development] Dj-Gutz:
Really? my mistake then

I admit I haven't tried it lately since I'm only with my nook on weekends

I remember it was crashing on any HQ video ( can't remember about HD )

Well , I'm just glad it's not an issue anymore :) Thanks
[Nook Color Android Development] mateorod:
And since you were asking about the HW codecs, have you been following the 3.x kernel thread over in the NookTab forum? That thread is unbelievable. Check out Hashcode's thread breaking down some of the progress. Talk about a lot of reading material.
[Nook Color Android Development] Dj-Gutz:
Yeah but this development is due to other similar devices with ICS

We will have to wait for TI / Optimus Black to update everything for full H/W acceleration ( hwcomposer , omx )

Dhiru1602 already got UI acceleration working on 2.6.35 , but our .35 kernel haven't progressed enough yet

Now that TI officially released 4.0.3 for AM3715 that means there is more to come on future updates ( Multimedia abilities like H/W video codec )

If we can use rowboat's .37 kernel to port it to the nook , or back-port stuff to our .35 kernel to make it usable enough to utilize UI acceleration for now - I think we can call it stable

Hopefully next update will be with 3.x kernel , but if we get to the .37 mark I think we will be good enough for now

I'm wondering what kind of support TI already completed in this release

look at the bug list

Known Issues

Power Management
SDOCM00091041
Crashes observed during suspend-resume test when SmartReflex enabled and scaling_governor set to ondemand

Multimedia SDOCM00091042
Streaming media is not working

Application SDOCM00091044
Gadget storage mode is not working

Dalvik SDOCM00091045
Dalvik unit tests 071-dexfile and 089-jumbo-upcodes are failing

Multimedia SDOCM00091046
2048x3172 resolution pictures are not displayed correctly

Browser SDOCM00091047
Kraken benchmark is causing the browser to terminate and exit prematurely
This issue is observed only with 256MB memory configuration.If one increase memory using boot arguments then test passes as expected

What does streaming media actually mean?
[Nook Color Android Development] thereddog:
I am having wifi issues with 4/17. I can connect fine, but it just stops sending data after a minute.

Anyone notice anything similar?
[Nook Color Android Development] shumash:
This particular problem was caused by allocating too little memory to the VM box. Upped it to 2GB, and it completed the build.

Question: Should I be posting these kind of posts in the Q & A somewhere rather than here?
[Nook Color Android Development] skylar.sutton:
YES! I thought I was alone. Very frustrating.
[Nook Color Android Development] shumash:
How do you back this out if you want to do a build without it?
[Nook Color Android Development] racks11479:
patch -Rp1 < onskreen_cornerstone_v0.85.patch

I believe the R stands for Reverse... could be wrong, but that be the command :)
[Nook Color Android Development] shumash:
Yah, research first, ask second. I tried to edit my post but you beat me to it.:o
[Nook Color Android Development] tonyp:
Over at the LG 2x section we have "snappy" compression in our kernel now instead of lzo for zram.. It seems to make the UI more fluid.

I'm no dev but though I'd share the idea.

http://code.google.com/p/snappy/

If you need some github sources of kernels with snappy commits I can post them.
[Nook Color Android Development] zequav:
How can the kernel compression affect snappiness??? :confused:

(edit) Wait, you don't mean the uImage compression, but the zram compression. Ok, that makes sense.
[Nook Color Android Development] HacDan:
I'll give it a shot. Git commits would be cool, but I'm fine with working through them as well. If you get around to it, cool, if not, I'll be starting from scratch.
[Nook Color Android Development] tonyp:
Thank you - and sure I'll provide you some links if they might help you :)

I found three different kernels which include snappy compression for zram - the commits are always entitled with "snappy":

kernel version 3.0.28

- https://github.com/bhanvadia/tegra-linux-3.0.y/commits/p99x-ics-3.0.y

kernel version 3.0.29:

- https://github.com/vadonka/lge-kernel-kang/commits/gb_3.0.y?page=3

kernel version 2.6.32 (commit backported from the first link):

- https://github.com/wildfatduck/lge-kernel-star/commits/android-tegra-2.6.32
[Nook Color Android Development] HacDan:
So, after some digging, and choice words not appropriate for this forum, I found out that the kernel we've been using doesn't include zRAM to begin with. So, after adding in that, patching for zRam and patching in Snappy, I finally have a kernel that

should

work, but, it quite literally just finished compiling as I'm typing this.

I'll report back if it makes a difference.

EDIT:

Well, I'm currently seeing ~100 more on memory score with 18% zRam enabled. I don't notice any huge improvements, but I guess for the benchmark hungry it's there. Gonna test a bit more. If you'd like to test, hop on IRC #nookcolor and bug me. I'm not posting here for a few reasons, but mainly because I haven't finalized the commit yet and the CM zRam settings aren't currently working so things have to be done w/ a script/manually at the moment. (Looking in to this later)

Anyway, I'm HacDan on #nookcolor or just about anywhere else on the Interwebz. Bug me and I'll point you at a script and a kernel to test.
[Nook Color Android Development] SeaFractor:
Interesting. Add's support to why previously adjusting zRAM and perceiving a result was reported as "placebo" :D

Too bad I was one of those that thought adjusting the zRAM settings did actually do something.

Well, I look forward to when they actually do! I'll watch the git and see when this is up.
[Nook Color Android Development] leapinlar:
I finally got my Ubuntu system set up so I can build my own ROM. I have done it a couple of times and the ROMs work nicely. One problem I don't understand though. When I use eyeballer's build the new UMS feature works great with both emmc and sdcard showing. When I use my build, only one drive shows up. Anyone else with that problem with their own builds?

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] eyeballer:
I don't think the prebuilt kernel is up-to-date, so you'll need to build it. See my post a few pages back: http://xdaforums.com/showthread.php?p=24963509#post24963509
[Nook Color Android Development] leapinlar:
That was it. I tested my build with your kernel and it fixed it. Guess I better build my own kernel too.

Thanks eyeballer. Always nice to have someone who knows what they are doing.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] keyodi:
I guess i forgot to upload the prebuilt kernel, but it's up now :)

In addition to the UMS changes, I also reverted the display rotation to default to portrait instead of landscape. If you recall, we made the change awhile ago forcing the display in landscape in order to correct the double rotation issue, however this is no longer needed.

CM change fixing the rotation issue - http://review.cyanogenmod.com/#/c/12135/

So, why change it back to portrait you ask? Cuz, I like it better that way! (Unless fattire vetoes my change)

btw, the changes are not included in eyeballer's or samiam's 4/27 builds
[Nook Color Android Development] pmgnet:
Portrait FTW!

I just want to say "please please let this make it in". NC was made for portrait. I don't mind allowing for landscape rotation, but it needs to default to portrait. All the games that go landscape work just fine and they do what they need to do.

Right now, I set my rotations enabled but only allow 90 degrees, and it is quirky. It keeps defaulting back to landscape, normally when the screen turns on.

EDIT--

Maybe we users need an option to pick default? Default to Landscape or Portrait?
[Nook Color Android Development] glgehman:
+1. I much prefer landscape as default.

glg
[Nook Color Android Development] keyodi:
You can(i think) by modifying the build.prop: ro.sf.hwrotation=270 - valid values 0, 90, 180, 270(default portrait)
[Nook Color Android Development] leapinlar:
Thank you Keyodi for doing this. By reverting the kernel and removing the rotation I no longer need to patch the SystemUI.apk to make the 240dpi/softkey patch. I still need to patch the framework-res.apk to enable the bottom Navigation Bar, but SystemUI now works fine as is. For you users of the patch, the softkey layout will revert to the standard ICS layout of: back - home - recent - and three dots for menu if needed. And starting with tonight's builds you will need to use my latest patch which I posted today on my thread.
[Nook Color Android Development] fattire:
Looking good! Glad it worked.

I too think portrait makes more sense. Someone at some point should get the recovery going in portrait.. hmm.
[Nook Color Android Development] leapinlar:
Eyeballer, you mentioned several posts back that you had to change your build configuration to select the right resolution for the bootanimation. I notice that your new build has a really good bootanimation, sized and rotated properly for the new kernel. My home built ROM is showing a smaller, partial screen bootanimation. Can you tell me what you changed in the configuration?
[Nook Color Android Development] eyeballer:
I didn't change anything, keyodi made the change along with the rotation fix:

https://github.com/fat-tire/android_device_bn_encore/commit/8e555e47f880efa72bbc5ecd1b2b096cc94c26b5

See the change in cm.mk for selecting the new res.

You may need to make clean or delete the bootanimation.zip from $OUT so that it's forced to get the correct one.
[Nook Color Android Development] leapinlar:
Yes, I saw that Keyodi had put the right resolution in the commit. But I wasn't getting it. Deleting the old fixed it. Thanks. I have found that if I want the build.prop to be current I need to delete that too. Is there something else I should be doing to be sure I am getting the latest of everything?
[Nook Color Android Development] eyeballer:
The build system should replace most changed things, the only way to be sure is to make clean though, which is what happens for all my nightlies.
[Nook Color Android Development] leapinlar:
Thanks. How do I make clean? Delete everything in 'encore' before building?
[Nook Color Android Development] eyeballer:
Type 'make clean' before you build
[Nook Color Android Development] shumash:
CM9 In Emulator

How do you set up the Android Emulator in Linux to run the nightly builds?
[Nook Color Android Development] fattire:
Are you asking how you set up Linux as a virtual machine on another computer?

Or are you asking how to set up a virtual android machine in linux (ie, the dalvik one that comes with the Android SDK?)?

---

BTW, as a general note to all-- reverendkjr has created an awesome video showing how to use goo manager w/the TWRP 2 recovery. It's essentially a replacement for Rom Manager/clockworkmod, in case your'e not familiar with it.
[Nook Color Android Development] shumash:
I've got Ubuntu 10.04 compiling the rom running in a VMWare box on Windows 7. I want to run the android sdk emulator using the nightly build, so I think that's the second one :) I imagine that I could use the sdk emulator in either Windows or Ubuntu since I've got it installed in both places.
[Nook Color Android Development] leapinlar:
There is a guide on how to build and run in the emulator on the CyanogenMod wiki. See here.
[Nook Color Android Development] shumash:
Thanks, I had used another source that paraphrased those instructions, but isn't that for gingerbread? It seems that we are compiling for a 4.04 target, but I only have an 4.03 target available in the SDK Manager and no later download available. The wiki uses pretty old instructions.
[Nook Color Android Development] leapinlar:
I was just trying that also and ran into the same problems.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] shumash:
Ah, well. There's always the flash it, fix it, flash it, ad nauseum route.:D
[Nook Color Android Development] fattire:
I'm still not sure if I'm entirely following what you're trying to do with the SDK emulator-- if you're running regular ol' android apps on it, they should run in the sdk emulator no problem, but if you want to run cm9-for-nookcolor in the dalvik machine emulator on windows or ubuntu, you're gonna have issues as the hardware emulated by the emulator isn't the same as the nook. You can set the resolution to be right, but hardware video drivers, and optimizations and modules in the kernel won't likely work.
[Nook Color Android Development] shumash:
That's exactly what I wanted to do. Thanks for disavowing me of that notion.
[Nook Color Android Development] fattire:
5-finger touch on Nook Color?

Well this is cool. User mik_os got 5-finger touch working on the newer touchscreens on nook tablet. Most of the touchscreens on Nook Color use the cyttsp device/driver, but the newer ones share the same ft5x06 panel as NT.

Might be fun for someone to try on NC as well and see if you can get it going. I can't test on mine (older touchscreen).
[Nook Color Android Development] 360Razir:
Good looking out, fattire! Going on a limb here and saying that if my NC is from Jan 2011, then I am in the "cyttsp" category? Is there a way I can know for sure, or is my time stamp a dead-giveaway?
[Nook Color Android Development] fattire:
Best way is to look at dmesg (adb shell dmesg shortly after bootup) for something like this:

<6>cyttsp_init:Cypress TrueTouch(R) Standard Product

<6>cyttsp_init:I2C Touchscreen Driver (Built Apr 28 2012 @ 07:32:25)

<4>cyttsp:Reseting TMA340

<4>cyttsp:Start Probe 1.2

<4>cyttsp::found BL, Overriding maxx & maxy

<6>cyttsp_initialize:cyttsp-i2c: Register input device

<4>max8903_charger_enable: dtct_status 0x04

<6>input: cyttsp-i2c as /devices/platform/i2c_omap.2/i2c-2/2-0022/input/input2

<6>cyttsp_initialize:Setting up interrupt 259

<6>cyttsp_initialize:cyttsp_initialize: Create sysfs_group successfully!

<4>cyttsp:Start Probe PASS

<6>ft5x06_init() - FT I2C Touchscreen Driver (Built Apr 28 2012 @ 07:32:25)

<3>can't get ft5x06 xreset GPIO

<6>cyttsp_power_on:BL101: f=00 s=11 err=D0 bl=010B bld=010B R=16

<6>cyttsp_power_on:BL102: tver=1100 a_id=AA1D aver=0006

<6>cyttsp_power_on:BL103: c_id=C0C1C2

If you have the newer ones, you'll see that cyttsp is not detected but ft5x06 is. If someone has an example of this, please post it...

Also, when I come up from sleep I see this:

<6>cyttsp_power_on:SI102: tver=1100 a_id=AA1D aver=0006

<6>cyttsp_power_on:SI103: c_id=C0C1C2
[Nook Color Android Development] leapinlar:
For those not having adb working or don't feel comfortable using it, you can run the same command in terminal emulator. (after running su, that is).

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] bigbob23:
If your nook has been running for a while, you can use this in terminal emulator:

dmesg | grep cyttsp

This will only display the lines containing "cyttsp".
[Nook Color Android Development] fattire:
But you should probably do it after a fresh boot, because the dmesg log is limited in size- once it reaches its limit, new entries will start deleting older ones...
[Nook Color Android Development] bytte:
looks like I have the old chip:

# pwd

/sys/devices/platform/i2c_omap.2/i2c-2/2-0022

#ls -l

lrwxrwxrwx 1 root root 0 May 1 22:23 driver -> ../../../../../bus/i2c/drivers/cyttsp-i2c

(This is CM7)