yashsingh1/xdaforums huggingface dataset:
[Barnes & Noble Nook Tablet] tonyp23:
After a lot of toil and trouble, I'm now running CM9 on my 16GB NT from a build off my computer! Thanks for all of the great info and guide.

Couple of things I learned on the way that might be helpful for others. I'm using Gentoo x86_64, so some of this stuff may not apply to you.

Make sure you are using Python 2.6 or 2.7 I started with Python 3.1 and had to revert. on gentoo, eselect python set x and then run python-updater

Install tofrodos, you'll probably have to unmask it, I did

As mentioned previously, install sun-jdk 6. You can leave the icedtea on there, but use java-config to select the sun-jdk for the user

After installing the sun-jdk I had to export ANDROID_JAVA_HOME=/opt/sun-jdk-1.6.0.31/

I also added ~/bin to my path to make using the repo command easier
[Barnes & Noble Nook Tablet] lenardo:
deleted the manifest.xml, ended up going back 2 steps from the repo init,- redid it from just prior to the chmod command redid that, the chmod, the repo init and then the sync and it appears to have worked.
[Barnes & Noble Nook Tablet] fattire:
Oooo Gentoo! Fancy-pants!

Congratulations.. :)

Oh, by the way to follow up with another thread, if you want to try the linero improvements as I did with NC, here's how you do it:

1. repo sync to get the latest everything.

2. Do this:

croot
cd frameworks/base
git fetch http://review.cyanogenmod.com/CyanogenMod/android_frameworks_base refs/changes/80/17380/2 && git checkout FETCH_HEAD
cd ../../bionic
git fetch http://review.cyanogenmod.com/CyanogenMod/android_bionic refs/changes/35/17535/2 && git checkout FETCH_HEAD
croot

then build as normal. In case the commits don't take from the above, you can find the relevant submissions here and here.

I would expect the result should be significant, especially w/benchmarks and framerates and such, since the linero video demo was a pandaboard, which is an omap4430 and the NT is an omap...4430. These aren't all the refinements from linero, but I think the bionic one is supposed to make a big difference.

Also, not sure if

ARCH_ARM_HAVE_ARMV7A := true

is set automatically, but if you don't notice anything in bionic building differently, add the above to your BoardConfig.mk file in devices/bn/acclaim/BoardConfig.mk and see if it helps.

Lemme know if it does anything!
[Barnes & Noble Nook Tablet] succulent:
Hmm. I might give it a try but I am wondering if I can use it for CM7?
[Barnes & Noble Nook Tablet] fattire:
No-- at least on CM I had someone try the bionic binaries w/cm7 and it didn't work. That said, you can try applying the patches to the cm7 version of bionic and who knows-- might need to do some creative jiggering to get it to take....

The framework stuff would be totally different from cm7->ics.

The pandaboard demo from linaro is pretty impressive, so I'm hoping someone tries it.

[youtube]mrQRYmYip6Q[/youtube]
[Barnes & Noble Nook Tablet] succulent:
I just tried it myself and yes, it doesn't work with CM7. It does work with CM9. :o
[Barnes & Noble Nook Tablet] Demetris:
@succulent

Would we have the opportunity to flash your compiled image CM9+Linaro someday?

Thanks
[Barnes & Noble Nook Tablet] succulent:
I have it on my blog,

I definitely see an improvement in CPU score in Quadrant.

To compare to CM7 internal, the average score is simlar to CM9 3.x internal. This is same with external.

I've also changed some stuff in the boardconfig.mk,

ARCH_ARM_HAVE_TLS_REGISTER := true

NEEDS_ARM_ERRATA_754319_754320 := true

TARGET_GLOBAL_CFLAGS += -DNEEDS_ARM_ERRATA_754319_754320

ARCH_ARM_HAVE_ARMV7A := true (It's not needed, but I added it anyway)

TARGET_BOOTLOADER_BOARD_NAME := acclaim

# Kernel/Boot

BOARD_KERNEL_CMDLINE := androidboot.console=ttyO0 console=ttyO0,115200n8 init=/init rootwait vram=32M,82000000 omapfb.vram=0:5M@82000000 def_disp=lcd2 (vram=0:16 causes rebooting problem on CM7)
[Barnes & Noble Nook Tablet] tonyp23:
Giving it a try now, I'll run a few benchmarks with the current build and put on the bionic one and try it out. Hopefully I don't get a random reboot while benchmarking
[Barnes & Noble Nook Tablet] Demetris:
@succulent

Isn't your config at BOARD_KERNEL_CMDLINE for 512mb Ntabs?
[Barnes & Noble Nook Tablet] tonyp23:
Here are my test results with the Linaro additions. Overall, not a lot of change.

Is there any way to check to make sure the additions took in the build? I followed the instructions like this:

repo sync

get new stuff

compile, but the compile broke due to Error 41, so I synced again, which made a change to the frameworks

compile again and it worked, flashed on top of previous CM9

CM9 3.x 1 2 3 4 5 AVG
CF-Bench 5181 5150 5174 5138 5148 5158.2
AnTuTu 4857 4693 4713 4694 4869 4765.2
Quadrant 2364 2404 2426 2572 2462 2445.4

CM9 3.x Bionic/Linaro Delta
CF-Bench 5362 5308 5140 5180 5200 5238 79.8
AnTuTu 4647 4597 4698 4710 4812 4692.8 -72.4
Quadrant 2453 2316 2380 2510 2495 2430.8 -14.6
[Barnes & Noble Nook Tablet] meghd00t:
One question, As I understand it the big gains come with using the Linaro Toolchain ie gcc-4.7.1 snapshot. The patches to android are mostly to make it compatible with the stricter checking in gcc-4.7.1. I am not clear from the comments of succulent and tonyp23 if they have installed the Linaro toolchain and modified the build invocation to use it.
[Barnes & Noble Nook Tablet] fattire:
Yeah, chrmhoffmann is working on building with the 4.7 toolchain for acclaim and I'm doing the same for encore... so we'll see..
[Barnes & Noble Nook Tablet] succulent:
Yup. Wait for the Linaro toolchain to get added to Cyanogenmod. I haven't use the Linaro toolchain but there is a slight increase in the CPU performance.

I've seen the patches here but I haven't add it,

http://review.cyanogenmod.com/#/c/17446/

http://review.cyanogenmod.com/#/c/17444/
[Barnes & Noble Nook Tablet] TheForceUnleashed:
I've built a Linaro CM9 build too. Some speed increase. You can fairly see it.

We must wait on toolchain, even if it is father's day...
[Barnes & Noble Nook Tablet] jdebay:
I tried your build...

I tried your build and it works better than the daily build. Opera flash works. YouTube works fine. I did notice your have more memory available for use than daily. (938,324 vs 662.684 for daily). Thanks for the build and it was fun testing it.
[Barnes & Noble Nook Tablet] fattire:
FWIW-- I built cm9 for Nook Color (omap3) w/linaro's 4.7 toolchain. Have some issues on NC, but they may be platform related. Since pandaboard works nicely, I'm guessing NT will work great.

I posted the build instructions here. These steps assume you're already building fine for NT w/the 3.0 kernel.

You don't need to make changes to hardware/ti/omap3 (not sure if there are omap4-specific changes that will need to be pulled from linaro's github..) I'm guessing if there are any issues it'll be kernel-related (only because I haven't built the 3.0 kernel for NT w/the new toolchain... but it may go smoothly as it did for NC)

ft
[Barnes & Noble Nook Tablet] stklv:
I follow fat's instructions use the new linaro toolchain (4.7) and build CM-9-XXXX.zip successfully, then i flash it use TWIP,but when i reboot it give me a blank screen. i adb it and try using su command it say:

root@android:/ # su
link_image[1965]: 2118 could not load needed library 'libandroid_runtime.so' for 'app_process' (link_image[1965]: 2118 could not load needed library 'libui.so' for 'libandroid_runtime.so' (link_image[1965]: 2118 could not load needed library 'libskia.so' for 'libui.so' (link_image[1965]: 2118 could not load needed library 'libjpeg.so' for 'libskia.so' (link_image[1937]: 2118 missing essential tables))))CANNOT LINK EXECUTABLE
root@android:/ # ls /system/lib/libui*
/system/lib/libui.so
root@android:/ # ls /system/lib/libjpeg*
/system/lib/libjpeg.so
|root@android:/ # ls /system/lib/libskia*
/system/lib/libskia.so
root@android:/ #

is it because libandroid_runtime.so compiled using old 4.4.3 toolchain and libui.so compiled use new linaro toolchain? and Does kernel been compiled use the new toolchain?
[Barnes & Noble Nook Tablet] fattire:
Maybe some answers.

See some of my more recent instructions-- you may also want to modify build as follows:

diff --git a/core/tasks/kernel.mk b/core/tasks/kernel.mk
index e677731..e3f07bf 100644
--- a/core/tasks/kernel.mk
+++ b/core/tasks/kernel.mk
@@ -96,7 +96,8 @@ ifeq ($(TARGET_ARCH),arm)
# Check that the executable is here.
ccache := $(strip $(wildcard $(ccache)))
endif
- ARM_CROSS_COMPILE:=CROSS_COMPILE="$(ccache) $(ARM_EABI_TOOLCHAIN)/arm-eabi-"
+# ARM_CROSS_COMPILE:=CROSS_COMPILE="$(ccache) $(ARM_EABI_TOOLCHAIN)/arm-eabi-"
+ ARM_CROSS_COMPILE:=CROSS_COMPILE=/home/fattire/Development/linaro/android-toolchain-eabi-4.7/bin/arm-linux-androide
ccache =
endif

diff --git a/envsetup.sh b/envsetup.sh
index 5e54026..34355c2 100644
--- a/envsetup.sh
+++ b/envsetup.sh
@@ -134,13 +134,13 @@ function setpaths()

# The gcc toolchain does not exists for windows/cygwin. In this case, do not reference it.
export ANDROID_EABI_TOOLCHAIN=
- toolchaindir=toolchain/arm-linux-androideabi-4.4.x/bin
+ toolchaindir=toolchain/linaro-4.7.1/bin
if [ -d "$prebuiltdir/$toolchaindir" ]; then
export ANDROID_EABI_TOOLCHAIN=$prebuiltdir/$toolchaindir
fi

export ARM_EABI_TOOLCHAIN=
- toolchaindir=toolchain/arm-eabi-4.4.3/bin
+ toolchaindir=toolchain/linaro-4.7.1/bin
if [ -d "$prebuiltdir/$toolchaindir" ]; then
export ARM_EABI_TOOLCHAIN=$prebuiltdir/$toolchaindir
fi

And symlink that directory to wherever you are downloading the linaro stuff as well as using the stuff I mentioned.

FWIW, the changes above have been abandoned by Cyanogen and GCC 4.7 won't be used for CM9 officially.

As far as errors go, you can always try pulling known "good" files. Also, if the problem seems to be related to a particular service, you can modify the related init.rc file to add an strace which you can examine in the log.

For example, I had a problem where I kept seeing "Netd starting..." but it seemed to be related to something previous as I didn't see any errors that made sense in netd itself. so I changed all the services, from looking like this:

service whatever /system/bin/something

to

service whatever service zygote /system/xbin/strace -tt -o/data/whatever.strace /system/bin/something

I did this for each of the services, then went and looked at the strace logs and noticed a crash related to libjpeg.so in one of the services (can't remember which). When i replaced libjpeg.so with the known "good" one, immediately the boot resumed...

If you are using my build instructions, the kernel is building. Be sure you use the right CROSS_COMPILE setting in BoardConfig.mk for the kernel and the modules...

And, uh, I guess that's it. The Nook Color dev/kernel threads have more info, cuz I am able to test with that device, so you can read more of my progress or lack thereof over there.

I expect it will be easier with the NT since it's bona fide omap4430 device, same as the pandaboard in the miracle video.
[Barnes & Noble Nook Tablet] Zippy Dufus:
Works for Fedora 17 x64 too!

Hello,

Thank-you for an excellent how-to! This was fun and I learned a lot.

I now have a working build from a Fedora 17 x64 KVM virtual machine running on a Fedora 17 x64 host.

A head's up - Fedora is a bleeding-edge distro and the modprobe -l option has been deprecated and this may affect other distros soon. Thanks to meghd00t for researching and developing a workaround in this post.

My notes can be found in this post.

One lesson learned is to use the official Oracle Java from the get-go. I originally kludged the build script to keep going with OpenJDK 1.7. The build failed so I downgraded to Fedora 15 1.6 OpenJDK and this build hollered that this was an "unsupported version of Java" but was successful anyway. The resulting package crashed a lot so I installed the official Java 1.6.

However, I still get crashes and reboots. From reviewing the forms I like to think these are unrelated to the Fedora build and just the nature of alpha software. I will be regularly watching for updates and rebuilding.

Again, many thanks!
[Barnes & Noble Nook Tablet] Danrarbc:
Can these be altered for Jelly Bean?

Edit: Oh, no the device stuff would need redone wouldn't it.
[Barnes & Noble Nook Tablet] fattire:
Well, modified somewhat. Shouldn't be a huge deal. It wasn't for nookcolor, which is up and running now. Nt is not much different from kfire, which hashcode said was pretty easy. So some changes to the build and boardconfig maybe. Possibly a few more fixes, but nothing on the scale of gb->ics. Cyanoboot and all that are the same too, though please try the new version of cb from last night (see cb thread) as it has been run through the Awesomizer.

I think chrmhoffmann has expressed interest in jb and though I'm nt-less (n7 soon) and focused on nc as well, I can probably help.
[Barnes & Noble Nook Tablet] Zippy Dufus:
Jellybean tweaks

Many thanks to tonyp23 and his post.

I was able to create a working Jellybean (CM10) build.

Here are the 2 tweaks:

1. tonyp23's change the local manifest as per the diff below:

[COLOR="DarkGreen"]--- local_manifest.xml.ics	2012-08-15 08:54:51.141963669 -0400
+++ local_manifest.xml.jb	2012-08-15 08:55:51.907293417 -0400[/COLOR]
@@ -7,11 +7,11 @@
<project path="device/bn/acclaim"
name="CMNookTablet/android_device_bn_acclaim"
remote="gh"
[COLOR="Red"]- revision="ics"/>[/COLOR]
[COLOR="SeaGreen"]+ revision="jellybean"/>[/COLOR]

<project path="kernel/bn/acclaim"
name="Kuzma30/kernel3NookTablet"
remote="gh"
[COLOR="Red"]- revision="master"/>[/COLOR]
[COLOR="SeaGreen"]+ revision="jellybean"/>[/COLOR]

</manifest>

2. Change this command in step 2 of CM9 for NookTablet Build Instructions to:

repo init -u git://github.com/CyanogenMod/android.git -b jellybean​

Some notes:

My build is cm-10-20120815-UNOFFICIAL-acclaim.zip

I noticed that the boot animation is still CM9 (About Tablet->Android version: 4.1.1)

The UI looks nice!

Bizarrely, the wifi is not working. Sees my neighbor's WPA connection 150' away but not mine 10' away (actually I saw it but briefly and not since.)

Has not SOD'ed yet like CM9 does once it goes to sleep.

I wasn't able to get tonyp23's dual CM9/CM10 repository approach working (my incompetence?, Fedora build environment?) so I just started from scratch with the tweaks above.

Perhaps the OP can confirm this and update the thread accordingly.

Still reviewing ...

Cheers.
[Barnes & Noble Nook Tablet] fattire:
Yeah, if you update "ics" to "jellybean" (or better yet, and if you have the space, re-init in a new location so you can have both). Also see the kernel thread if you want to use one of the other test branches with the 3.0 kernel...

chrmhoffmann had a breakthrough today too with-.. well,... I'll let him test and announce if/when he's ready.. :P
[Barnes & Noble Nook Tablet] TheForceUnleashed:
I smell loophole :D sync'd my sgt7 tonight, no changes.

Sent using my mom's dirty IPad :P
[Barnes & Noble Nook Tablet] cdaters:
I have been out of the game for a bit, but I am going to start playing with this when I get home. I have both Ubuntu and Mountain Lion that I can build on.

How difficult is this to get onto a bootable uSD? Is there any one uSD "how-to" that is better than another out there? I would like to try this on my NT, but I want to keep my EMMC intact.
[Barnes & Noble Nook Tablet] ShinnAsuka:
trying to build cm10 with the cm9 instructions modified as posted by another user. i am getting the following error and have no idea how to get it to work...

here is a pastebin link for easy viewing:

www.pastebin.com/ZzikDyAU

EDIT: got the problem to go away. apparently javac wasn't showing up. using the command which java didn't return anything so i had to export the bin directory of the jdk in the .bashrc and now its building...

hope to produce a working cm10 flashable zip to test out. jellybean ftw!
[Barnes & Noble Nook Tablet] Zippy Dufus:
Beginner's luck?

Hello,

Has anybody created a working Jellybean build since my 08/15 post 85 above?

I've tried on 08/25, 09/02 and 09/03 and these builds fail to flash. Upon reboot after flashing, I see a quick flash of the screen and then just a dark screen with the back light on.

My local_manifest.xml is the same my previous post.

I'm currently running chrmhoffmann's 0.05.1 build and compared my build.prop with his and do see a few interesting differences. I'm wondering if I am building the right branch (jellybean versus jb_test)?

(BWT, Chris's build is working great especially the hardware video acceleration now being able to play high-definition video files which would not run on previous builds. Nice work!)

I'm at a loss for ideas.

12d11
< com.ti.omap_enhancement=true
27,28d25
< omap.enhancement=true
< persist.sys.root_access=3
34,39c31,36
< ro.build.date=Mon Sep 3 22:33:07 CEST 2012
< ro.build.date.utc=1346704387
< ro.build.description=cm_acclaim-userdebug 4.1.1 JRO03L eng.chris.20120903.223210 test-keys
< ro.build.display.id=cm_acclaim-userdebug 4.1.1 JRO03L eng.chris.20120903.223210 test-keys
< ro.build.fingerprint=Android/cm_acclaim/acclaim:4.1.1/JRO03L/eng.chris.20120903.223210:userdebug/test-keys
< ro.build.host=c3po
---
> ro.build.date=Mon Sep 3 08:44:23 EDT 2012
> ro.build.date.utc=1346676263
> ro.build.description=cm_acclaim-userdebug 4.1.1 JRO03L eng.android.20120903.084357 test-keys
> ro.build.display.id=cm_acclaim-userdebug 4.1.1 JRO03L eng.android.20120903.084357 test-keys
> ro.build.fingerprint=Android/cm_acclaim/acclaim:4.1.1/JRO03L/eng.android.20120903.084357:userdebug/test-keys
> ro.build.host=fedora17.localdomain
45c42
< ro.build.user=chris
---
> ro.build.user=android
47c44
< ro.build.version.incremental=eng.chris.20120903.223210
---
> ro.build.version.incremental=eng.android.20120903.084357
62,63d58
< ro.crypto.state=unencrypted
< ro.hwc.legacy_api=true
76c71
< ro.product.model=Barnes & Noble Nook Tablet
---
> ro.product.model=NookTablet
[Barnes & Noble Nook Tablet] meghd00t:
go look at the revised manifest at https://github.com/CMNookTablet/android_acclaim_local_manifest
[Barnes & Noble Nook Tablet] tonyp23:
They made a bunch of changes to the local_manifest. Here's mine

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- Specifiy remote gits -->
<remote fetch="git://github.com/" name="gh" />
<remote fetch="git://git.omapzoom.org/" name="omapzoom" />

<!-- CM removals -->
<remove-project name="CyanogenMod/android_hardware_libhardware" />
<remove-project name="CyanogenMod/android_hardware_libhardware_legacy" />
<remove-project name="CyanogenMod/android_hardware_ti_omap4xxx" />
<remove-project name="CyanogenMod/android_hardware_ti_wlan" />
<remove-project name="CyanogenMod/android_system_core" />

<!-- omapzoom replacements -->
<project path="hardware/ti/domx" name="platform/hardware/ti/domx" remote="omapzoom" revision="jb-release" />
<project path="hardware/ti/omap4xxx" name="platform/hardware/ti/omap4xxx" remote="omapzoom" revision="p-jb-release" />
<project path="device/ti/common-open" name="device/ti/common-open" remote="omapzoom" revision="jb-release" />
<project path="device/ti/proprietary-open" name="device/ti/proprietary-open" remote="omapzoom" revision="jb-release" />
<project path="hardware/ti/wlan" name="platform/hardware/ti/wlan" remote="omapzoom" revision="p-jb-release" />
<project path="external/wpa_supplicant_8_ti" name="platform/external/wpa_supplicant_8_ti" remote="omapzoom" revision="jb-release">
<annotation name="vendor" value="ti" />
</project>

<!-- modified CM projects -->
<project path="system/core" name="KFire-Android/android_system_core" revision="jellybean" remote="gh" />
<project path="hardware/libhardware_legacy" name="KFire-Android/android_hardware_libhardware_legacy" revision="jellybean" remote="gh" />
<project path="hardware/libhardware" name="KFire-Android/android_hardware_libhardware" revision="jellybean" remote="gh" />

<!-- Local Projects/gits -->
<project name="CMNookTablet/android_device_bn_acclaim" path="device/bn/acclaim" remote="gh" revision="jellybean" />
<project name="Kuzma30/kernel3NookTablet" path="kernel/bn/acclaim" remote="gh" revision="jellybean" />
<project path="device/amazon/otter" name="KFire-Android/device-amazon-otter" revision="jb" remote="gh" />
<project path="kernel/amazon/otter" name="KFire-Android/kernel_omap" revision="4AI1.7" remote="gh" />
<project path="vendor/amazon/otter" name="KFire-Android/android_vendor_amazon_otter" revision="jb" remote="gh" />

</manifest>

You can drop the last 3 lines of project path, as I'm building for both my NT and wife's kindle
[Barnes & Noble Nook Tablet] Zippy Dufus:
Beginner's woes?

Hello again,

I'm having difficulty getting the build to work. This is the error that I am getting when the brunch acclaim command is executed:

Checking build tools versions...
device/ti/proprietary-open/Android.mk:199: warning: overriding recipe for target `out/target/product/acclaim/fake_packages/ti-wpan-fw'
build/core/base_rules.mk:530: warning: ignoring old recipe for target `out/target/product/acclaim/fake_packages/ti-wpan-fw'
fatal: No names found, cannot describe anything.
fatal: No names found, cannot describe anything.
fatal: No names found, cannot describe anything.
fatal: No names found, cannot describe anything.
find: `src': No such file or directory
build/core/Makefile:38: warning: overriding recipe for target `out/target/product/acclaim/system/etc/mkshrc'
build/core/base_rules.mk:530: warning: ignoring old recipe for target `out/target/product/acclaim/system/etc/mkshrc'
PRODUCT_COPY_FILES frameworks/native/data/etc/android.software.sip.voip.xml:system/etc/permissions/android.software.sip.voip.xml ignored.
No private recovery resources for TARGET_DEVICE acclaim
build/core/tasks/kernel.mk:174: warning: overriding recipe for target `out/target/product/acclaim/kernel'
build/core/Makefile:38: warning: ignoring old recipe for target `out/target/product/acclaim/kernel'
make: *** No rule to make target `out/host/linux-x86/bin/mkbootimg', needed by `out/target/product/acclaim/boot.img.sdcard'. Stop

My local_manifest.xml is here: http://pastebin.com/4rFs4S8D It is the same as the previous post with all references to Kindle Fire removed.

My build script is here: http://pastebin.com/NU5QeXgg

The full log is here: http://pastebin.com/7ZPLcpgv

To get to this state I first started with https://github.com/CMNookTablet/andr...local_manifest as mentioned in the second previous post and ran into errors too as well as what appears to be a mistake whereby remote name "private" isn't defined.

Next I edited tonyp23's version and ran it and got these illustrated error messages.

Finally, I ran with my original local_manifest.xml and it no longer works too!

I fear that my repo is messed up and I have to download EVERYTHING all over again. Please tell me it ain't so!

Any help or suggestions would be appreciated.
[Barnes & Noble Nook Tablet] tonyp23:
I get those first few messages when I compile as well, not sure what they mean. Before you download everything again, if you look back to a previous post of mine with the repo clone tool there is another one in that same git called reporeset which will put everything back to pristine sources which I have used with success. Wish I could help more.
[Barnes & Noble Nook Tablet] meghd00t:
the mistake is you have removed libhardware and libhardware_leagcy but not replaced it with the patched versions from the KFire repo

FYI here is the current setup that I am building here
[Barnes & Noble Nook Tablet] chrmhoffmann:
The local_manifest needs to be from the jellybean branch (not master).

I don't do anything extra then:

1) . build/envsetup.sh

2) lunch 5 (or whatever cm_acclaimuserdebug is)

3) make otapackage

Rgds,

Chris