yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] sjwaste:
Hi folks - trying to build for the first time, getting this:

external/zlib/x86/adler32.c: In function ‘adler32_MMX’:
external/zlib/x86/adler32.c:747: error: can't find a register in class ‘GENERAL_REGS’ while reloading ‘asm’
external/zlib/x86/adler32.c:747: error: ‘asm’ operand has impossible constraints
make: *** [out/host/darwin-x86/obj/STATIC_LIBRARIES/libz_intermediates/adler32.o] Error 1

Not sure what the issue is. Building on OSX 10.6, and google only confirms others have had the same issue. Not sure about a resolution.

I tried a make clean, make clobber, repo sync. No dice. I'm thinking it's the build environment, but I don't know enough to troubleshoot from here.

Running XCode 3.2 and JDK Update 10 from Apple.
[Nook Color Android Development] MrColdbird:
Thanks everyone for the great tip!

PocketCloud works great, absolutely happy with it.

It's like a better Remote Desktop for Android 4. :)
[Nook Color Android Development] user17600:
Hi all, posted this a couple of weeks back in the general forum, but got no traction (http://xdaforums.com/showthread.php?p=21842316):

Question for the devs or others in the know - in the ICS (granted very early) builds, I can't get IPtables to work, but an earlier list of changes seems to indicate that this should be working.

Manifests itself with errors starting the firewall in Droidwall. So, am I doing something wrong or is IPtables not available in the current ICS builds (I'm using the 0128 nightly)?

Is this included and dormant, or is it a Droidwall problem (well, Droidwall and Avast both give the same error).

I'm maybe a little paranoid about controlling how apps access the internet, so it would sure be great to get this working.

Thanks, Devs and others who have contributed to these fantastic builds!
[Nook Color Android Development] Homer_S_xda:
I had the same experience with Autoproxy, works in CM7, no luck in CM9. The dev updated it for ICS but it whines that IPtables are not available.

Homer
[Nook Color Android Development] khaytsus:
Anyone else just getting a blank screen after the bootloader with the latest build? I must be doing something wrong.. No adb, just backlight, blank screen. Always format /cache, even formatted /system and installed the zip again, same. Trying a few other things, but so far blank screen each time.

I'm going to try getting off the ics-test branch and back to the standard files and building and see what that does I guess.
[Nook Color Android Development] Nburnes:
Are you building the new kernel with it?
[Nook Color Android Development] fattire:
test-branch's new kernel + old proprietary files == black screen (or possibly lead to rickets). Make SURE you have the new props from TI in your vendor/bn/encore/proprietary as described previously, and then make sure you've done a make clobber (or manually add the files to your device...)

If any of those files mismatch the pvr driver in the new kernel you'll have a black screen.
[Nook Color Android Development] khaytsus:
Turns out that repo sync doesn't really repo sync sometimes. Still don't know why, and still don't know what else is missing, but after I downloaded the encore folder separately and moved the files into the build, THEN when i did git checkout ics-test, it switched files around. Still building, but it's at least different now.

So yes, kernel was wrong before. Why... Only git knows. Or does it. :mad:
[Nook Color Android Development] leapinlar:
Fattire,

I know you watch this thread, so I'm hoping you see this and respond.

If you have been following the three threads about Nook Color ICS, which I know you have by your comments, you know that ICS with the 2.6.32.9 kernel exhibits the SOD issue just like CM7 did. I know you and dal had a hard time reproducing the SOD on your units which made it hard to debug. Last October a user on the cyanogenmod forum (Embedded) was able to reliably reproduce the SOD on his unit running CM7 and produced some logs. You can see his comments and logs here:

http://forum.cyanogenmod.com/topic/32316-sleep-of-death-debugging/page__hl__sleep

He experimented a lot and ended up modifying the wifi kernel module. He says how he did it in the thread. Several of us users who were consistently getting SODs tried his modded module and it worked wonderfully. Dal got involved later and thought that a modded kernel would work better. He showed Brian Faris what to do and Brian built a kernel that several of us also tried. It also worked but in my opinion not as well as the modded module. I still got occasional SODs with the kernel and never got any with the module.

So now we are on CM9 with the same basic kernel and I for one had been getting SODs. I decided to try the modded module since it was for the same basic kernel and I thought it should be compatible. I did not want to substitute Brian's kernel for yours since I figured you had made ICS specific mods to yours. Anyway, the module worked well and seemed to reduce the SODs. I have only had one since installing the module. I posted the install zip for the module so that other users could try it. I have got nothing but positive feedback on it since I posted it. I flash mine with each new nightly and I know many others do too.

Now my reason for this post. Would it be possible for you to make the mods to either the kernel that dal suggested or to the module like Embedded made and include those in your local github for builds?
[Nook Color Android Development] sjwaste:
Any ideas on this one? I read somewhere else that it's an old GCC bug. I loaded gcc 4.0 through 4.6 in Ports, and tried selecting both 4.6 and 4.4 to build - no no avail.

ports select --set gcc mp-gcc44 (and so on for other versions)

I'm thinking it's something else in the build environment, but I have no idea what, since it seems to be obviously failing on a compile step. Either I have a hosed lib (I tried installing/upgrading XCode to 3.2.6) or a bad compiler (tried 3 versions of gcc).

I'm at a loss.

EDIT: For some reason, no matter what version of GCC I select in Ports, I'm seeing that brunch runs gcc 4.2. Is there any way around that?
[Nook Color Android Development] racks11479:
You could manually delete the gcc symlink and recreate the symlink to the gcc version to want to execute.
[Nook Color Android Development] sjwaste:
Yeah, I did that - made sure the symlink /usr/bin/gcc was pointed to the version i wanted in /opt/local/bin. No dice. Same error for GCC 4.2, 4.4 and 4.6.

Really strange. I know I could just create a Ubuntu VM and set the environment up there, but now I really want to solve this problem.

Is anyone else building on OSX 10.6, XCode 3.2.6, JDK Upd 10 (from Apple) and GCC 4.2, 4.4, or 4.6 from Mac Ports? Did it just work - is it possible I just need to blow everything out and recreate the environment?

The only thing I'd consider "odd" about my setup is that I'm working out of an HFS+ case sensitive DMG because my host FS isn't set up that way. I'm mounted at /volumes/android but that really shouldn't matter.
[Nook Color Android Development] racks11479:
You know, now that i recall, i remember that this is a gcc issue with compiling. I'm building on OSX Leapord myself. and i ran into the same problem. I can't recall off the top of my head which gcc i'm running. But i'll check when i get into work tomorrow.
[Nook Color Android Development] alienbiker99:
I haven't seen that problem but I set up with brew made it a lot easier

http://xdaforums.com/showthread.php?t=1326743 with fat-tires guide
[Nook Color Android Development] fattire:
Hey leapinlar..

I haven't looked through the thread yet, but I'll definitely give it a look. Also keyodi discovered that:

<keyodi> fattire: i asked hacdan to use the blobs from gfx_rel_es4.x_android instead of 5.x, and so far no freezes

So maybe this is something people can try also? These are the freezes with OPENGL_RENDER on and apparently they go away with the OTHER (wrong?) set of binaries?

keyodi, hacdan, and racks are testing.
[Nook Color Android Development] keyodi:
@fattire

i think leapinlar wants this patch added to the kernel (post) http://pastebin.com/E5hTt08d
[Nook Color Android Development] fattire:
So i tried dalingrin's suggestion-- and the resulting kernel is here if anyone wants to try it. I haven't tested at all so can't suggest anything. Note that this kernel is from the "ics-fattire-test" branch contains the new pvr driver, so unless you're using the new egl blobs (or I think the newer nightlies maybe from samiam area also using this kernel), this will result in a blank screen.
[Nook Color Android Development] leapinlar:
Thanks fattire, much appreciated. I'll give it a try. Both Eyeballer's latest build and Samiam303's latest build have the new ics-fattire-test kernel in them now so it should be safe to use this with them. I am going to try the modded kernel with the original wifi module (unmodified) that comes with CM9 ics_test to see if it helps with SODs.

In CM7 there was an arrangement where two versions of the kernel (uImage16 and uImage32) were stored in /system/bin/kernel and dal's Nook Tweaks would put whichever one you wanted in /boot. That is how you chose whether you wanted 16 or 32 bit rendering of images. I notice that CM9 has a setting like that in performance settings but it must do it some other way than switching kernels so I guess we only need the one version you just made.
[Nook Color Android Development] Nburnes:
uImage fattire just posted with Sam's newest nightly seems to work great.
[Nook Color Android Development] frankusb:
gfx_rel_es3.x_android instead of gfx_rel_es4.x_android?

http://gitorious.org/rowboat/hardware-ti-sgx/blobs/master/ANDROID_RN_4_03_00_01.txt

The 5.x was for SGX core revision 1.2.5 while 3.x is for 1.2.1. 4.x does not exist?

Frank
[Nook Color Android Development] SGH-i200:
uImage from fattire

I'm testing with latest SamBuild, too:

http://xdaforums.com/showpost.php?p=22147912&postcount=647
[Nook Color Android Development] fattire:
If people think it's good, maybe in a day or two, I'll merge the test into the mainline kernel/device and then we'll just consider ourselves migrated... but the build instructions will need to change because you can't extract-files.sh from cm7 any more.

The 16/32 doesn't work in ics-- 16 looks TERRIBLE. If you want to build your own uImage16 and try it, maybe you can somehow get it to look better, but in the mean time I got rid of those extra kernels to save ~/7MB of space for each update.zip
[Nook Color Android Development] leapinlar:
Unfortunately I just got an SOD with the new kernel. I put it on my system making sure I had the right version of twlan_drv.ko, booted, checked to be sure it had your #109 kernel on it. Turned on wifi set to stay on all the time, and pushed power button to let it go to sleep. Waited a while and tried to turn on. SOD. Bummer...

I will keep testing, but we may need to modify the twlan_drv.ko like Embedded did. However, another user on Sam's thread said he just got an SOD with the latest build using just the modded twlan_drv.ko file so that may not be the answer either. Maybe modding doing both?
[Nook Color Android Development] fattire:
Under Settings->Wi-Fi->Action Overflow (top right)->Advanced->Keep WiFi on during sleep--

I had Always and never had a SOD. I'm switching to Only when plugged in and we'll see if it makes a difference.

Just wondering-- what were you set at? And can you try flipping it to the other to see if it makes any kind of difference?
[Nook Color Android Development] leapinlar:
I have it set to always. I have two software packages that run services that do background syncs. Google Voice and CalenGoo. Those services trying to run via wifi while deep sleep is on may contribute to the problem. Maybe it is software trying to use wifi while sleeping is what triggers the SOD. Maybe you are running nothing like that and that's why you never get them.

I never get SODs with wifi set to the other two wifi sleep settings. Only with always.

Edit: when I set it up this time (after the last SOD), I re-flashed the nightly first followed by installing the new kernel. One thing I noticed after a while was cpu spy said I was deep sleeping. I could rarely get it to deep sleep (for more than a few seconds) with wifi set to always with prior builds. Just an interesting point.
[Nook Color Android Development] SGH-i200:
Deep Sleep test with CPU Spy

I have one NookColor running the 1-25 build and just looked up CPU Spy:

49:51:31 Total State Time

43:26:56 Deep Sleep

Seems my Nook is sleeping well! ;-)
[Nook Color Android Development] user17600:
Ah, no love here for a firewall either. I guess I've spent too much time in a Windows environment to feel comfortable without one...

Anyway, for those with similar issues, I've been using LBE Privacy Guard from the Market for the last few days. It's no IPtables but at least it does give some semblance of control over app access to the internet.

I have noticed some apps lock CM9 up tight when denied access (looking at you gmail), so YMMV. And you can control LBE access by going into the trusted apps folder and "untrusting" it.

Will have to suffice until CM9 has IPT working.
[Nook Color Android Development] SeaFractor:
So far my preliminary tests are really positive. I certainly support the idea of merging it in a couple days so others also have a chance to +1 vote if all is well.

Great job! You and the rest of the devs involved are doing fantastic work, this alpha is way better than some Release Candidates from the big houses.
[Nook Color Android Development] racks11479:
Fattire,

Finally having deep sleep with your test kernel and OpenGL Renderer on. No lockups thus far since testing it this afternoon. I have almost no battery drained since putting to sleep at 6pm. And no SOD. Turned right on after sleeping for a couple hours.

Thanks,

Racks
[Nook Color Android Development] jschill31:
Hello,

All I can say is outstanding...new kernel rocks so far!

A big Thank you
[Nook Color Android Development] newellj79:
I'd really appreciate it if some one could tell me whats going on here. I have'nt built in about a week. Tried today and got this...

Install: out/host/linux-x86/bin/sqlite3

Install: out/host/linux-x86/lib/libsqlite_jni.so

zip -qDj out/target/product/encore/recovery.img out/target/product/encore/ramdisk-recovery.ub out/target/product/encore/kernel

----- Made recovery image (zip) -------- out/target/product/encore/recovery.img

target SharedLib: libEGL (out/target/product/encore/obj/SHARED_LIBRARIES/libEGL_intermediates/LINKED/libEGL.so)

target SharedLib: libpixelflinger (out/target/product/encore/obj/SHARED_LIBRARIES/libpixelflinger_intermediates/LINKED/libpixelflinger.so)

target Symbolic: libskia (out/target/product/encore/symbols/system/lib/libskia.so)

target Strip: libstagefright_foundation (out/target/product/encore/obj/lib/libstagefright_foundation.so)

Copying: out/target/common/obj/JAVA_LIBRARIES/framework_intermediates/classes-jarjar.jar

target Strip: libdrmframework (out/target/product/encore/obj/lib/libdrmframework.so)

target Symbolic: libbluetoothd (out/target/product/encore/symbols/system/lib/libbluetoothd.so)

target Strip: dalvikvm (out/target/product/encore/obj/EXECUTABLES/dalvikvm_intermediates/dalvikvm)

target Strip: dexopt (out/target/product/encore/obj/EXECUTABLES/dexopt_intermediates/dexopt)

target Strip: dumpsys (out/target/product/encore/obj/EXECUTABLES/dumpsys_intermediates/dumpsys)

target Strip: libpowermanager (out/target/product/encore/obj/lib/libpowermanager.so)

target Symbolic: netd (out/target/product/encore/symbols/system/bin/netd)

target Symbolic: libril (out/target/product/encore/symbols/system/lib/libril.so)

target Strip: service (out/target/product/encore/obj/EXECUTABLES/service_intermediates/service)

target Symbolic: vold (out/target/product/encore/symbols/system/bin/vold)

target Symbolic: wlan_loader (out/target/product/encore/symbols/system/bin/wlan_loader)

target Symbolic: libdrm1_jni (out/target/product/encore/symbols/system/lib/libdrm1_jni.so)

target Strip: libmtp (out/target/product/encore/obj/lib/libmtp.so)

target Strip: libbcc (out/target/product/encore/obj/lib/libbcc.so)

target Strip: libsqlite_jni (out/target/product/encore/obj/lib/libsqlite_jni.so)

target Strip: sqlite3 (out/target/product/encore/obj/EXECUTABLES/sqlite3_intermediates/sqlite3)

target Strip: su (out/target/product/encore/obj/EXECUTABLES/su_intermediates/su)

Construct recovery from boot

mkdir -p out/target/product/encore/obj/PACKAGING/recovery_patch_intermediates/

PATH=out/host/linux-x86/bin:$PATH out/host/linux-x86/bin/imgdiff out/target/product/encore/boot.img out/target/product/encore/recovery.img out/target/product/encore/obj/PACKAGING/recovery_patch_intermediates/recovery_from_boot.p

failed to stat "out/target/product/encore/boot.img": No such file or directory

failed to break apart source image

make: *** [out/target/product/encore/obj/PACKAGING/recovery_patch_intermediates/recovery_from_boot.p] Error 1

make: *** Waiting for unfinished jobs....

jeremy@jeremy-VGN-FW560F:~/android/system$

Thanks guys...
[Nook Color Android Development] eyeballer:
FYI: discussion of using the v4 or v5 libs is moot, the files appear to be identical.

http://pastebin.com/NnL6D332

http://pastebin.com/6QYRJPKh
[Nook Color Android Development] eyeballer:
Seems like most/all peoples builds are currently broken (mine included). review.cyanogenmod.com is also down again so we'll have to wait it out to see what's going on.

For those wanting to try last nights build or an opengl enabled build, I have them up here http://techerrata.com/browse/nightly_kangs/encore
[Nook Color Android Development] fattire:
It's this commit. Which I'm guessing will break tenderloin as well.

For now, you can cd ~/android/system/build and type git revert d892e1c903f0e050723bce09000a222853f53bb9 and it should build
[Nook Color Android Development] newellj79:
Thanks Fattire. Trying to build again now.
[Nook Color Android Development] fattymcdirty:
Would it be somehow possible to enable OpenGL-Rendering when using the nightlies posted here? (http://www.sphsolutions.net/android/Encore/Nightlies/CM9/) Or this this an option only available to peeps who build on their own?
[Nook Color Android Development] Homer_S_xda:
Q: Does this have the #109+ kernel?

Homer
[Nook Color Android Development] ianPhillips1:
No, after initial boot still says #108 ,hell after boot with new kernal inserted still says #108 (headscratch), used winrar guess ill try 7zip.

Ian

Go pats!

edit:it was a bad kernel download
[Nook Color Android Development] bigbob23:
No, but I replaced the kernel in Eyeballer's opengl zipfile with the new one (using 'zip -j') and it appears to be working fine.
[Nook Color Android Development] eyeballer:
No, just replace it after flashing.
[Nook Color Android Development] zequav:
I tried eyeballer's opengl enabled version and everything worked better (keyboard popups, wallpaper scrolling, etc). But I was still getting the annoying stuttering when playing games that I was getting with my custom ics-test build and the unofficial ics-test build from the other thread by samiam303 (I didn't get that stuttering with the old ics).

UNTIL... I changed the governor. Ondemand is simply broken for me when using ics-test. With conservative, performace or interactiveX I don't get the stuttering in games: all are as smooth as with ics non-test.
[Nook Color Android Development] eyeballer:
By popular demand.. opengl with 109 kernel: http://techerrata.com/file/nightly_....0-encore-KANG-20120205-opengl-109-signed.zip
[Nook Color Android Development] fattymcdirty:
mh.. the opengl version is so way more laggy for me.... ?! games are kinda unplayable and the launcher is laggy as hell, to... shouldn't it be smoother then without opengl enabled?
[Nook Color Android Development] Sam Adams:
The open gl is also very laggy for me - have also had freezes in different apps. Going back to 1/31 for a few days.

Go Pats!
[Nook Color Android Development] afzalarsalan:
For people experiencing stuttering, try changing your cpu governor. Also, does eyeballer's opengl version contain the SOD fix in the kernel?
[Nook Color Android Development] leapinlar:
The one he referenced three posts ago does. (109 kernel means SOD fix).
[Nook Color Android Development] afzalarsalan:
I have noticed that eyeballer's zip that he posted recently has a problem with the portrait keyboard. Is anyone else experiencing this?
[Nook Color Android Development] webdroidmt:
Tried the open-gl version Sat night, also added kernel 109 and experienced lag on homescreens and app drawer as well as significant slowdown on the browser. More importantly, I was getting random freezes on homescreens, some apps and the browser, which required a reboot.

I changed back to nightly 0204 (no open-gl) with 109 and the freezes stopped but the lag was still pretty noticeable, primarily on the app drawer. I changed my launcher to Nova Launcher and it is running much smoother. The screen transitions are much improved and calling up the app drawer is much less "sticky."

Hopefully, there will be progress made with open-gl down the road, as I would definitely like to be able to use Flash material. All in all, there has been fantastic improvements made to this rom from the first sneak peek version, which in itself was a minor miracle.

My continued thanks go to those folks that keeping doing the things they do that I cannot.

Mike T
[Nook Color Android Development] zequav:
After setting the governor to performance with eyeballer's opengl build I haven't had any problem. Everything works smoother than ever with ics, and I had no lockups or anything like that. IMO ics-test+opengl should be the default build config.
[Nook Color Android Development] zequav:
I spoke too soon, got a lockup while installing two apps from the market. I still think ics-test+opengl is worth it.
[Nook Color Android Development] iDidItAll4theNookie:
Changing the governor on 109 didn't provide much of a difference for me. Games were almost as playable as on CM7. Just a little too slow though.

And yes, the keyboard in portrait mode looks rather odd. Really tall, skinny keys that the letters barely fit in.
[Nook Color Android Development] pavlos46:
Ok managed to limit the slagness in the latest opengl build.

Just go to settings> performance> surface dithering and disable it.

Pavlos
[Nook Color Android Development] bdcrim:
Good thought. However, I never had it enabled and it was still to laggy to use.
[Nook Color Android Development] 3rdman:
I got rid of the app drawer slow down by changing the transitions to "standard"...It is running very smoothly on eyeballer's 109/opengl build.
[Nook Color Android Development] SGH-i200:
Launcher alternatives

Nova Launcher is a little faster but has still errors. Sometimes no apps in drawer...

Another alternative is this new one:

Apex Launcher Beta (Android 4.0+)

http://xdaforums.com/showthread.php?t=1452663

---------- Post added at 12:27 AM ---------- Previous post was at 12:25 AM ----------

Changing transition in Homescreen to 'standard' will help, too! :-)
[Nook Color Android Development] MrColdbird:
From what I can tell the ogl one doesn't like cpu clock changes...

Running on performance that always uses your set maximum frequency I can operate everything fine at 800 Max speed.

This includes normal quality youtube.

Still have to try if I can go any lower.

Running on the new kernel here too and can deep sleep just fine not even losing a single percent sleeping all day.

To whoever has trouble with the battery... Check your apps whether they interrupt sleep.

Gesendet von meinem NookColor mit Tapatalk
[Nook Color Android Development] keyodi:
OpenGL testers needed

Another attempt to fix the random freezes...:(

If anyone is using opengl and would like to test this change:

remove 0 0 android from lib/egl/egl.cfg​

The fps during the graphics test in quadrant score improve, but i'm more interested in whether this change prevents the random freezes everyone gets with opengl on.
[Nook Color Android Development] zequav:
Testing now... I only got one freeze anyway prior to this change.