yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] leapinlar:
With the latest build I've noticed the touch sensitivity is much improved. I hadn't flashed for a few days so I don't know which version did it. This is almost livable now. I used to have to touch icons several times and aim lower to get them to respond. Now just touch once lightly and they activate. Yay!

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] RileyGrant:
Move to ics-test. :p builds on this pos net book I'm using take like 2 days. ):
[Nook Color Android Development] Dubbee:
Hi all it looks like I got my 10 posts in and now can post here after lurking for a bit.

I've been flashing the nightlies at least 1-2 times a week and having a grand time of it, but I have to ask, in appreciation of all the work that's been done to date, what exactly can I do to help further the cause? Like, are there specific things to be tested, etc? What would be most useful?

Thanks!
[Nook Color Android Development] Samiam303:
Well you'll all likely be happy to know that after debating the stability of the new drivers with the guys in IRC, I moved my build setup to the ics-test branch, so tonight's build will take longer than usual but it'll be a fresh build with the new drivers!

We're really to the point where most of the major features are pretty complete and stable. If you run into any major bugs, it's always helpful to grab a logcat and post it in the development thread... but it seems like a lot of the fixes at this point are going to come from upstream CM, so if you're really interested in contributing to the project in the longer term it may be worth doing a little reading about how they do what they do.
[Nook Color Android Development] seth.i.simmons:
I second the motion to move to ics-test, would love to try out the new driver, but can't build for myself right now... if anyone would be so kind as to upload an ics-test build, that would be awesome!
[Nook Color Android Development] Techienana:
For those of you who, like me, were missing Swype on ICS, I am now using TouchPal for tablets and it is very nice. There is a learning curve but it definitely is close enough to Swype for me. Tried SlideIt but liked Swype better and am satisfied with TouchPal.
[Nook Color Android Development] SGH-i200:
Sam moved his build setup to the ics-test!

Sam answered your request 1min before you sent it! :p

I'm looking forward to test the new drivers, too! :)
[Nook Color Android Development] KidJoe:
I am enjoying the progress and improvements with each nightly that I install...

Last night I installed update-encore-20120131.zip and it cleared up an issue with MoboPlayer (mobo would pop up an error box to "Report" or "Force Close" if you tried to exit while the movie/video was still playing, that is now fixed).

I still have some minor issues...

1. MovieBrowserHD can't identify any movies. Looks ups to IMDB or other providers returns no data. (It looks like its working, as I see data activity).

2. I have EA Monopoly installed. When I launch the first time, its supposed to download the files it needs to run... I starts, and tries, but the progress bar never moves and eventually it fails saying try again later.

3. Monopoly appears to identify the Nook w/ICS as a "phone" rather than "tablet" as wants to download only 20meg of files, rather than the 80-200meg it did when I was running CM7.

4. Screen doesn't always register my taps and presses.

Is there anything I can do to help trouble shoot this, or provide info to those who could fix? Or should I just keep trying the new build each night?
[Nook Color Android Development] zequav:
My ics-test build seems worse than the old ics... yeah, some games work that didn't before, but everything else (especially games that did work) seems... "jerkier" than before.

Let's hope it's just my build.
[Nook Color Android Development] HarleyChick:
So is the ics-test in the same place as the "nightlies"?
[Nook Color Android Development] Samiam303:
It will be, it's going to be the same nightlies. Looks like last night's build didn't work. I'll investigate when I get home from work.
[Nook Color Android Development] SGH-i200:
02-Feb-2012 19:16 - Nightly?

I just looked up your server for the new build and saw:

"02-Feb-2012 19:16 118M"

Has this version the new or the old driver? Since it is 3M bigger it must be the first one with the new drivers, right?

Download is running...

Edit: Didn't start up. After Cyanogen-Bootlogo there is the normal flash but after that no boot animation is shown. :-(
[Nook Color Android Development] Harlley Sathler:
Same here! I noted a message during zip install that say Ramdom offset bla-bla-bla (it was a number but I can't remember).

Think the zip file is corrupted or something else.
[Nook Color Android Development] dark79:
Same here. Tried clean install on a freshly formatted microSD with and without the fixes. Both just show a quick flash of light and then stuck on black screen.
[Nook Color Android Development] boomn:
That's not an error message or an indication of a problem, it's a notification that a security feature was used. This is new starting in 4.0
[Nook Color Android Development] leapinlar:
Me too, exactly as your case. Without the fixes. The zip file was 3MB bigger too. I think something is wrong with the build. Fattire said those symptoms are because of the new kernel with old files.
[Nook Color Android Development] Samiam303:
Yeah, sounds like something's not right... I'll poke around and let you know when I've got a build that's confirmed to work.
[Nook Color Android Development] SGH-i200:
Ramdom offset

That's normal. I don't know for what reason the random offset is used but it is there in every build I used.
[Nook Color Android Development] boomn:
This wikipedia article is a good summary
[Nook Color Android Development] Harlley Sathler:
Ok, never paid attention to this message. I believe this was the first time I've noted that. Sorry.
[Nook Color Android Development] SeaFractor:
I'm starting to test it now myself. No worries as I always backup my ROM first, so if it's not happy I'll be able to recover quickly.
[Nook Color Android Development] Thermogenic:
I tried two different builds and could never get my device to wake from deep sleep - basically causing me to power cycle every time. Went back to CM7 and will wait for the official release - I liked what I saw though!
[Nook Color Android Development] SGH-i200:
I do that, too - and now have the update-encore-20120131 ROM running.

Sam removed the 20120202 nightly which was the first with new drivers because it was not working...

@Sam - I mentioned a new "Auto-hide the system tray in full screen mode" feature. How to get the system tray back? Only by going to home screen?
[Nook Color Android Development] SeaFractor:
I noticed that the 20120202 build was back up, however the size is 115MB rather than the prior 118MB.

I've installed it and it's working, but I'm not sure if this is a build from the ics or the ics_test branch.

If the system was set to auto-build, perhaps it created another of the ics branch. The perfomance doesn't appear that much different than before, which is why I question if it's from the ics_test. However, the GUI does appear more "responsive", but nenamark 1 provides a low score still.

Still really stable though! Impressive for an Alpha.

---------- Post added at 11:44 PM ---------- Previous post was at 11:27 PM ----------

Cleared my cache and dalvik-cache and it is much better. Using pulse and the browser is much faster and easier to use.

Great Job!

Don't forget to clear the caches.
[Nook Color Android Development] pavlos46:
Try flash player, if it works you have the new drivers!
[Nook Color Android Development] pavlos46:
Just tested it and flash doesn't work although I am not sure if that means that the drivers are on or not...
[Nook Color Android Development] seth.i.simmons:
Definitely loving the latest build. Haven't run into any bugs yet, and the launcher seem much snappier, along with Pulse and scrolling throughout.great work guys, still can't believe this is just an alpha, CRAZY stable!
[Nook Color Android Development] siobhter:
This nightly seems to be more stable and WAY faster, but my screen resolution got pushed down and everything is huge... Gonna try a screen density app to see if I can get my real estate back. Will update later.
[Nook Color Android Development] aaplus12:
I did a clean install on this nightly. I never tried flash before but it does not work on this build either. Other than that i noticed that keyboard is quite huge now in portrait mode. Has anyone else noticed this. No doubt that this nightly feels faster than ever.
[Nook Color Android Development] Samiam303:
Everything's been moved over to the new branch, so the nightlies (including last night's) will include the new drivers from here on out. However, I've left the USE_OPENGL_RENDERER := true line commented out, so we're not using full opengl -- which is why some stuff still doesn't work. I may upload a test-build with that enabled, but it's not recommended as stable enough for normal use yet.
[Nook Color Android Development] siobhter:
Yeah, I thought my screen density was messed up but it's just the keyboard that's gigantic. Will try another KB to see if it affects the 3rd party ones as well.
[Nook Color Android Development] mateorod:
Okay, first flash since 1/28. Responsiveness and touch accuracy is great, really first class. Tons of functionality added in such a short time, especially in the settings. The performance tweaks are very welcome.

Can confirm that flash is still not working, although vpn is up by all appearances. Slide status bar to adjust brightness doesn't seem to work, but I could never get that working in gingerbread either. The keyboard is pretty big, alright.

Tell you what, this is probably enough function for me to go daily with the builds. Vpn was probably the last thing holding me back. If firewalls are doable, I will probably be here to stay.

Sam, a hell of a public service you're providing here.

I like ICS. I do, I like it, samiam.
[Nook Color Android Development] aaplus12:
@Sam,

Is it possible to turn on OpenGL rendering by changing something in config file or do you need to have a new build with that option turned on.

I must say, we all really appreciate your putting up a fresh build every night

Thanks a bundle man
[Nook Color Android Development] mateorod:
Oh yeah, and the extended power menu is so very welcome. Reboot into recovery and screenshot now working.
[Nook Color Android Development] xxsxx:
Never understood why we have an option for screenshot. Just press volume down and power both at the same time for 2 seconds. Instant screenshot.
[Nook Color Android Development] aaplus12:
to save you 2 seconds :)
[Nook Color Android Development] SeaFractor:
Noticed this in the DEV thread, http://xdaforums.com/showpost.php?p=22142935&postcount=1858

Looks like a solution is on the horizon. The 2D performance is very much appreciated. I think I can handle waiting for the full opengl.
[Nook Color Android Development] ibilln:
Latest: Same-O

Running with

update-encore-20120202.zip and

gapps-gb-wifi_SOD-bootanimation-telephony_patches.zip

Get SOD after letting it sit for an hour or so, Lots of CPU usage, big keyboard in portrait mode.

Fyi, thnx
[Nook Color Android Development] leapinlar:
Fattire has made us a new kernel using dalingrin's patch that he wrote earlier for an SOD fix. I am testing it now. It only should be used on Eyeballer's or Sam's latest build (like you are running). And to be fair for the test, the modded wifi module should be replaced with the original. If this tests out well, I think fattire will incorporate it into the build.

Edit: If you want to test it, it is very easy for SD card installations. First, reflash the latest version of Sam's build to get rid of the modded wifi module (don't add it back). Then connect to PC and go to boot. Rename uImage to uImage.bak. Then copy the uImage file downloaded from fattire's post to boot. Then reboot and you should be OK. If you get a black screen, it means you tried to install it on an older build. Just go back and change back to the original uImage file. Once you have booted successfully, you can tell you have the new kernel by looking in settings, about tablet. The kernel should say #109.
[Nook Color Android Development] SGH-i200:
Fattire kernel into zip

I'm running on intern memory so I exchanged the file "kernel" in the zip with the "uImage" file from fattire and renamed that to "kernel". It works. Says #109 in about screen.
[Nook Color Android Development] taylor.fowler:
Same here. Worked like a charm. Also Attached the telephony/bootanimation fixes (stripped out the wifi modules) flashable zip.
[Nook Color Android Development] siobhter:
I have "No Frills CPU Control" installed to handle overclocking. I wonder if the built-in clock control is better?
[Nook Color Android Development] fattire:
Kindle Fires don't have volume buttons :)
[Nook Color Android Development] fattire:
probably doing the same thing, which is writing values into sysfs (aka "files in /sys") which is a fake directory/file structure that's provided by the kernel to let you switch kernel values/settings on-the-fly. It doesn't matter if those are set by the CM9 settings, "No Frills", setCPU, or you in the bash (#) shell... it all does the same thing.
[Nook Color Android Development] Homer_S_xda:
One more reason to own a Nook instead of a Kindle! :D

Homer
[Nook Color Android Development] halrulez:
Could someone make this flashable?
[Nook Color Android Development] leapinlar:
I have made one but I hesitate to post it because I don't want people that don't know what they are doing to try to flash it to an earlier build. Then they would have a real mess. It would not boot and have a black screen. Just wait until it gets tested a little more and fattire will make it part of the build.
[Nook Color Android Development] SGH-i200:
Simply follow the instruction I posted if you want to flash the new nightly with this testkernel.

Open the ZIP of the current nightly and exchange the file. It's simply drag-and-drop if you use 7ZIP.

After that you can flash like normal.

Right!
[Nook Color Android Development] bobtidey:
Very happy with the great progress being made here.

On my device the ROM with new drivers significantly slowed the interface and made the touch more sensitive and trickier to use.

I've restored the latest pre-test versions for normal operation but will continue to update and try out the later ones as they appear.
[Nook Color Android Development] Techienana:
Works!

Update: First impressions: I've only been using this nightly for five minutes but my screen is the best it's ever been! Very responsive and the lag that I was experiencing when bringing up the open apps is much, much improved.
[Nook Color Android Development] bmar08:
with the latest build having new drivers would we need to do a fresh install or just a normal update clearing the cache and dalvik cache?
[Nook Color Android Development] leapinlar:
Just normal.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] Kem-El:
So, if I'm running the modified image on SD, it should say 109 ... not 108? Mine says 108
[Nook Color Android Development] leapinlar:
Then it did not install properly. How did you install it? It definitely should say 109.

I bet you put the uImage file in boot before you put the nightly in. By doing that the nightly will overwrite the 109 version with 108 when it boots and installs.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] Kem-El:
I renamed the original to uimage.bak and copied the new uimage to the SD (it downloaded as uimage.txt so I removed the file extension before copying it)

Then copied the 20120202 nightly to the SD also. Rebooted and went into verygreen's recovery ... the new zip installed fine.

Seems like the right process ...

Doh! Just realized I need to replace it AFTER flashing ... woopsie ... trying it the right way now ... update in a moment
[Nook Color Android Development] SeaFractor:
Created my image and it shows fattire@laptop #109. w00t!

Prelim tests are really good!

Great work!
[Nook Color Android Development] leapinlar:
You need to flash first then come back and put the uImage in. BUT you did not download the kernel if it had .txt on the end of it. It was probably an error message. Do it again. The real file should be 3.2MB.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] Kem-El:
Yeah, I just realized I needed to copy it AFTER flashing the new zip ... woopsie ... done now and it is the right one 109! WooHoo!

Those dang flabbit rookie mistakes ...
[Nook Color Android Development] bigbob23:
I have tried a bunch of things but have not been able to install the new kernel into the zip file, either on my Mac or on the NC itself. If I unzip, put in the new file and zip it up, it will not install in CWM Recovery (I have disabled signature checking).

Can anyone point me to a way to use the new kernel?
[Nook Color Android Development] leapinlar:
Do not unzip. Just open the zip with your zip program and first delete (remove) "kernel" then rename "uImage" to "kernel" and copy it (add) to the zip in the same place you deleted the original. Then save the zip.
[Nook Color Android Development] jschill31:
Hello,

First off don't unzip the file, that is your problem...you break the signed file. Leave it ziped but double click on it so you can see the compressed file structure. Just drag your re-named "kernel" file into the still zipped file and it will replace but stay signed.

Cheers
[Nook Color Android Development] bigbob23:
Thanks, I was dragging it into the folder created by double-clicking, not into the zip file itself.

Edit: I did again as you said but it still comes up a kernel #108. :confused:
[Nook Color Android Development] Kem-El:
This ROM is amazing; the increase in UI response (smoothness, navigation, button clicks, etc) is great!

Thank you devs and anyone else who contributed!

Just a quick question:

Anybody use Evernote?

It seems after I flashed this latest nightly with the uImage replacement, Evernote reverted to the phone interface.

Now this could be on Evernote's end as I upgraded the app after flashing. To be sure, I even removed the android.hardware.telephony.gsm.xml permissions file.

(I never applied the telephony-fix with the other nightlies, so not sure if this is even the issue.)

Anybody got any ideas?
[Nook Color Android Development] jschill31:
Hello all,

New kernel and build make for a outstanding experience so far...a huge improvement!

Cheers
[Nook Color Android Development] leapinlar:
As I said in my earlier post, sometimes it's best to delete the file first to make sure the old one is gone before adding the new one. If you just try to copy over the old one, it sometimes errors out and you don't see it.
[Nook Color Android Development] pavlos46:
Tryied the new build 109 with the new kernel and flash player does not work is this expected ....? Or I should wait for the opengl one ....
[Nook Color Android Development] zequav:
So, am I the only one that notices way more jerkiness with the ics-test build? I did with my own build (reported it in the other thread), and do it now with the build posted here. I'm at 1100MHz. Cut the Rope, Fruit Ninja, Speedx 3d, World of Goo, etc. were perfectly playable with ics and are very laggy/jerky with ics-test.
[Nook Color Android Development] frikakwa:
This new kernel makes huge difference: everything's smoother! GG dudes! :)
[Nook Color Android Development] RETIEF:
2-3 nightlies

Was there a problem with the buildbot last night?

Retief:confused:
[Nook Color Android Development] Techienana:
No battery drain and deep sleep reported at 32% :-) by CPU Spy.
[Nook Color Android Development] bdcrim:
I am having the same issues. Scrolling through the app drawer is very painful.
[Nook Color Android Development] Samiam303:
Yeah, my cat unplugged my laptop so it died and nothing built. The build that should have happened is up now though.
[Nook Color Android Development] Sam Adams:
I'm sure the cat looked cute as hell doing it though...
[Nook Color Android Development] bigbob23:
I think the problem I had is that you apparently can't add a file to a zip archive in the OS X archiver (ez7x, a version of 7-zip didn't work for me either).

I then tried it from a command line using "zip -j <path to zipfile> <path to new kernel>" and that did the trick. This method will work on Linux as well.

:)
[Nook Color Android Development] michaelg1030:
I've been away from this for awhile. I just flashed the latest build. Is this new kernel included in the build or where and how do I install it(can I just flash it like a normal kernel). Also, so I flash the patch that fixed boot animation, telephony, wifi sod?
[Nook Color Android Development] SGH-i200:
Newest Kernel #109 in not included. See howto a few posts ago.

Wifi fix is not needed with new Kernel.

---------- Post added at 06:55 PM ---------- Previous post was at 06:50 PM ----------

I can reproduce that opening one web page freezes my nook (hard reset needed):

http://www.godlaya.de/?page_id=2428

Ics Browser+ does the trick without problem.

Edit: Second time I opened that link also B+ froze my Nook...
[Nook Color Android Development] Jainyankee1993:
This is probably a stupid question..but where do I find the updated kernels?? I'm really sorry for the dumb question
[Nook Color Android Development] SGH-i200:
If you don't know how to include it yourself - wait a few days. But instruction on how to you can find in the post following the quoted one.
[Nook Color Android Development] michaelg1030:
Is the updated kernel with latest build significantly better? I am really considering going back to CM7 based rooms. My gf uses the nook and is always having issues with it. I can wait it out a few more days, but if the new kernel and build isn't significant than I'll have to go back.
[Nook Color Android Development] Rick_V:
Yeah blame the defenseless Cat. :D
[Nook Color Android Development] leapinlar:
Yes it's significantly better, but still but not as good as CM7.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] michaelg1030:
Thanks for the info. Back to CM7 for what is hopefully not to much longer.
[Nook Color Android Development] bobtidey:
Like a couple of others have noted the test-ics versions with new drivers seem to have made the ui a bit more jerky at least for some of us. I think the touch is more tricky as well making it more difficult to 'click' on something without it being interpreted as a slide.

As a test I thought I would try out a Quadrant benchmark test to see if that picked anything up even though I know it's not necessarily the best.

Tests done with 1200 max InteractiveX

20120128 pre test build

Corridor fps ~20

Helix fps ~16

Overall score 1762

20120203 test build and new kernel

Corridor fps ~16

Helix fps ~14

Overall score 1806

That sort of surprised me because the overall score was similar and although the graphic fps were a little slower they were not that much worse.

It certainly didn't seem to explain my perceived slow down which I found pretty noticeable. Apart from the general speed of sliding home screens even on a simple game like backgammon the pieces are moving about twice as quick on the pre-test version.

I used to get about 2700 overall Quadrant on CM7 which made for an even smoother experience. I'm not planning to go back though as the experience with pre-test was pretty acceptable and I'm hoping for further improvements from these early stages of CM9 anyway.

Thanks to all the devs involved.
[Nook Color Android Development] zequav:
Glad to see I'm not alone. It's weird that some people are reporting huge improvements and we get this crappy performance.

(edit) BTW, in case anyone suggests it: yeah, I wiped everything before flashing the ics-test builds.
[Nook Color Android Development] bdcrim:
I switched to apex launcher and things are much better. It can be found in the Galaxy Nexus themes and apps forum.