yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] SeaFractor:
Going to try this out today. I'd actually setup an SD-EXT partition on my sdcard, but I'm guessing that it wasn't doing anything prior to this update.
[Nook Color Android Development] Henk Poley:
I do see wpa_supplicant using a lot of CPU coming out of sleep. Don't know if that was common before. Didn't notice it.

Annoying question: Will there be a version that works with CM7 ?
[Nook Color Android Development] jewnersey:
i wiped everything and loaded the opengl 404 rom from eyeballer and im getting random lock ups pretty often.. im gonna throw the non-opengl up and see if that is any better

403 excuse me
[Nook Color Android Development] SeaFractor:
Interesting, my results are quite the opposite at this time. I wonder if it's due to a swap file working now.

Very smooth GUI. Strangely, while the benchmarks don't show much of a measurable performance increase in FPS for EGL/OpenGL tests, the responsiveness of the GUI has noticiably improved for me.

Just waiting for someone to say it's placebo though :)
[Nook Color Android Development] friedsonjm:
Your wait is over... I'm 'seeing' the same thing; feels 'snappier,' but no change on the AnnTuTu benchmark...

---------- Post added at 02:07 PM ---------- Previous post was at 01:55 PM ----------

OK, the instructions are for someone running from SD Card.. what about those of us running from internal memory?
[Nook Color Android Development] keyodi:
We noticed the same thing last night while testing the new kernel. We'll look into what's causing this bug and remove it :D
[Nook Color Android Development] friedsonjm:
Let me guess... you have a side job working for Microsoft?! :p
[Nook Color Android Development] SeaFractor:
I'm not quite sure how to do this with the emmc partition as it looks like the instructions are for the individual creating the ROM.

However, what is working for me is to do the following steps using the wonderful "ROM Manager".

IMPORTANT DISCLAIMER: The steps will completely wipe your SDCARD! When you backup, please realize your clockwork mod backups are on the SDCARD, if you haven't copied them off somewhere else, you will NOT RECOVER. I assume no liability for those that try this procedure....

1. Open ROM Manager.

2. Perform a backup if you wish, be sure to copy this to your PC before proceeding!

3. Click on "Partition SD Card".

4. Accept default of "256MB" Ext Size.

5. Accept default of "32MB" swap size (matches the git documentation).

6. Watch it reboot and reformation/partition your SDCARD from clockworkmod.

7. Restart your Nook and realize all the applications that were installed on your SDCARD are gone, but not uninstalled so you have to uninstall them yourself. Call me all kinds of sweat language because you failed to note my disclaimer above.

8. After calming down and reinstalling your apps, realize that there is an improvement.

9. Experience a cathartic release and then click my thanks button below :D
[Nook Color Android Development] racks11479:
Or you could just do as stated in the documentation and create a swapfile using the 'dd' command. And copy the 'swapfile' you just created to the root of your sdcard. Then create the fstab file in /system/etc/ with:

## Adding Swap Space
/mnt/sdcard/swapfile none swap sw 0 0

Then reboot and perform "swapon -a" and it should work.

-Racks

P.S.- If you're on a Mac and don't have a linux distro handy (since you need to perform mkswap), you could just copy the /swapfile over to the root of your sdcard and open up a Terminal Emulator from your nook and cd to /sdcard and "mkswap swapfile" and that should work as well.
[Nook Color Android Development] jewnersey:
ok ill give it another shot

lots of Q's

is ext4 better than fat32 for my sdcard?

i have backed up and wiped to get everything started fresh

am i making 32mb of swap space? i was under the impression that is too low...

and can you please be a little more specific with the creating the fstab part.

i have the swapfile and its on the root of my unpartitioned sdcard, but not sure whats next

also:

are the community tweaks still relevant?

and supercharging yes/no ?

i always have had issues with the opengl and random lockups btw
[Nook Color Android Development] Henk Poley:
My nook color with the new kernel keeps saying it is connected to a computer over USB. Haven't tried rebooting though. It was connected but not anymore.
[Nook Color Android Development] envied:
mine isnt doing that using the newest nightly (4/3 opengl) and new kernel patch

ive plugged it into computer and also just to regular wall charger

and it goes back to normal like it should when unplugging.
[Nook Color Android Development] jewnersey:
yeah my nook just cant handle this. i started entirely clean, flashed 403 opengl, 317 gapps, then the kernel, installed oi file manager from the market > then root explorer... then i went home and to the app drawer, and the launcher crashed, then not frozen but couldnt do anything, then screen off and dead
[Nook Color Android Development] HacDan:
Depends on your system, but for compatibility's sake, stick with fat32.

You could use as much space as you wanted. I doubt you'll see a performance gain over 128MB though.

Sure, open up your favorite text editor on your Nook and create /system/etc/fstab and add what racks mentioned.

They never were.

No.

That's normal, and mentioned in the thread where you got the build. =)
[Nook Color Android Development] jewnersey:
wow, thanks a million.

using the 32mb swapfile for now. seems to be doing its job.

and not sure if the swap is what changed it, but im not locking up anymore (fingerscrossed)

::::45 seconds later it locked. wooooops
[Nook Color Android Development] keyodi:
Are you booting from the sdcard or emmc? is the nc locking up only when you're using the swapfile?
[Nook Color Android Development] jewnersey:
emmc

locked up randomly before I got the swap running, then I wiped and flashed again, installed swap and it lasted about 30 minutes before dying again. now on non-opengl with no problems
[Nook Color Android Development] cybertimber2007:
Nothing to see here :D
[Nook Color Android Development] stolenmoment:
I'm running with a swapfile on /emmc. It might be faster and I might want to take out the SD. Mkswap and swapon apparently succeeded.

Does swapon happen automatically? I haven't dug into the startup scripts...

We'll see how it goes. I expect that apps should get kept in memory longer, right? In addition to the other things that the new kernel brings.
[Nook Color Android Development] Henk Poley:
If you have it in your fstab it should automatically turn the swap on when you (re)start the Nook Color. `swapon`/`swapoff` are just commands to do it by hand when you changed stab.
[Nook Color Android Development] stolenmoment:
Thanks! That's the way it works with other Linux distros, I wasn't sure about Android.

BTW, "cat /proc/swaps" shows 27268 used of 131016, so something's happening...

Oops! I rebooted, but the swapon apparently didn't happen. The symptom is that "cat /proc/swaps" showed no swap files. After "swapon -a" the space showed up, with none used yet. I filled out /system/etc/fstab as

/mnt/emmc/swapfile none swap sw 0 0

which I lifted almost verbatim from the referenced info, and swapon found it with no trouble. Is Android smart enough to wait until the filesystems are mounted before running swapon -a?

Clues, anyone?
[Nook Color Android Development] cpkroboth:
Ok.. I have tried the Swap file creation.. I boot from EMMC and have the swap file on the SD card. Created the fstab file with the following.

## Adding Swap Space

/mnt/sdcard/swapfile none swap sw 0 0

Reboot and in terminal do swapon -a and get

swapon /mnt/sdcard/swapfile Invalid argument?

EDIT: Went back and started from scratch. After the DD command, when I do the mkswap /swapfile it tells me "image is too small". Suspect this is where the issue is, I did not see this before.

Thoughts and help?
[Nook Color Android Development] nukeruss:
There seems to be a lot of stuff that runs a lot faster and smoother on ics like this app and typing. Bumped it up to 1100 with rom toolbox and its running smooth as ice.
[Nook Color Android Development] 511pf:
Just chipped in $50. They're doing a $4 match for every dollar donated over the next three hours. Who else is in?

https://supporters.eff.org/donate/powerup
[Nook Color Android Development] rickpref:
agreed...I was not expecting this to work this fast. Scrolling in the browser is smoother than ever. I can't wait to see what updates come next.
[Nook Color Android Development] nukeruss:
You tube and google+ videos are working for me now. They weren't earlier. I've installed many variations of gapps today to get the best combo and now the video is working fine. Still no sound though.
[Nook Color Android Development] cybertimber2007:
Results in "nfc service has stopped". From another thread, it seems it's caused by the Google Wallet apk that's in there. Going to try making one w/o that, and flashing it.

Edit: Made a clean SD card based ICS install, Removed googlewallet and googlenfc apks from the gapps-ics-2011125-2.zip. Flashing now...

Edit2: Result? No market? Looking into what went wrong.
[Nook Color Android Development] rickpref:
Which Gapps did you end up with?
[Nook Color Android Development] Nburnes:
Not getting that error and mine has wallet installed D:
[Nook Color Android Development] MrColdbird:
Just wanted to drop that I tested the Preview Build you posted Fattire, miraculous, no other word could describe it.

I can definently see a future in running Android ICS on the Nook Color, don't give up guys, it's brilliant work so far!
[Nook Color Android Development] nukeruss:
20110613 was the only one that I could get the market working with. It also has the older YouTube app that's working. I also manually installed a few updated apps from the 2011125 gapps posted a couple pages back. YouTube was not working this morning but not it works fine. It does have the older interface and not the slick updated one that installed on my first gapps try (20111129 from the Droid x ics thread on rootzwiki). I flashed all these different versions trying to get my email working correctly.
[Nook Color Android Development] cybertimber2007:
Well that means the install script isn't working right.

# don't use nfc or tag if the device doesn't support it.
# check for support to see if the base rom has those apks.
if [ ! -f "/system/app/NfcGoogle.apk" -a ! -f "/system/app/Nfc.apk" ]
then
rm -f /tmp/gapps/system/app/NfcGoogle.apk

# no nfc means no google wallet
rm -f /system/app/Wallet.apk
rm -f /system/framework/com.android.nfc_extras.jar
rm -f /system/vendor/firmware/libpn544_fw.so
fi
if [ ! -f "/system/app/TagGoogle.apk" -a ! -f "/system/app/Tag.apk" ]
then
rm -f /tmp/gapps/system/app/TagGoogle.apk
fi

Edit: Yea it seems that install script changed in the 2011128 version. But you said it worked for you? I'm going to try flashing it again in a bit.
[Nook Color Android Development] EverythingNook:
Can someone get a video of this please?
[Nook Color Android Development] dgozalie:
damn!!

I install it, put the gapps.. and tweak the speed to 1200.. can't believe it run this smooths.. really cannot wait for the next revision... this really exceed my expectation !! now i just using ics as my main rom..

well, xmas does comes early....

Donny
[Nook Color Android Development] groovechild:
wow, for being an early testing release, this is really stable and usable. It's almost ready for daily use.
[Nook Color Android Development] msaraiva:
Guys, use this Google Apps, work like a charm:

http://www.multiupload.com/J3V7QVKVDH

It's going to be my daily rom, since i don't care too much for audio. Thank you Dalingrin and Fattire!
[Nook Color Android Development] BaileyJ205:
Same error for me.
[Nook Color Android Development] nukeruss:
Bluetooth file transfer tested sat. Sent PDF from laptop to nook and back to laptop .
[Nook Color Android Development] capnblackleg:
Thanks so much Dalingrin and fattire, Im in love with my nook again.
[Nook Color Android Development] newellj79:
Here is a link to the gapps i used for the ics build. I've only tested market, gtalk, and gmail, but all work flawlessly. Tablet versions. Its in my dropbox.

http://dl.dropbox.com/u/27515414/gapps-ics-20111125-2.zip
[Nook Color Android Development] sednafx:
Is anyone having wifi issues with wpa2? I was able to connect when I turned encryption off. I wiped everything except sdcard. Thanks.
[Nook Color Android Development] biohazrd51:
Nope. Working fine at home on WPA2 and tether WPA to my phone. I thought there was a problem before I realized I was typing in the wrong wireless pw 5 times :rolleyes:

The thread exploded quite a bit, I have a feeling fattire will regret releasing that zip. :p
[Nook Color Android Development] stolenmoment:
I'm assuming that you did su and mkswap before this. Your /system/etc/fstab looks just like mine except for the filename. I think that I got this error when I tried swapon while running the the old kernel (I just had to try it).

Picky note: mkswap /swapfile is NOT right; your swapfile should NOT be in your root filesystem, which is in main memory anyway. However, giving it a non-existing filename prints "No such file or directory". I do get that error with "touch swp; mkswap swp", so the file exists, but mkswap thinks it's too small.

How big did you make your file? What arguments did you give to dd? What does "ls -s /sdcard/swapfile" print?
[Nook Color Android Development] cpkroboth:
First thank you for responding.

I use: dd if=dev/zero of=swapfile bs=1M count=32

Understanding what you said/asked. I just tried:

dd if=dev/zero of=/mnt/emmc/swapfile bs=1M count=32 (No Errors, and verified file was there)

mkswap /mnt/emmc/swapfile (image is too small)

I verified I am on the new Kernel of 2.5.32.59.

Color me puzzled...
[Nook Color Android Development] Henk Poley:
dd if=/dev/zero ....

You are missing a /
[Nook Color Android Development] cpkroboth:
tried again with the dd if=/dev/zero

Same results.
[Nook Color Android Development] racks11479:
Try setting block size to 1024K because I believe that is how Android reads block size by default.. could be wrong. But it should work.

dd if=/dev/zero of=/mnt/emmc/swapfile3 bs=1024K count=32

-Racks
[Nook Color Android Development] bytte:
You can easily check whether it worked with ls -l

You should see your file sized at 32 * 1024 * 1024 or whatever.
[Nook Color Android Development] SeaFractor:
With the latest opengl build and the new kernel in combination with a 32mb swap file I am receiving the highest nenamark1 frame rate under ICS to date. 14.7fps where as the same opengl build without the new kernel and swap file only did 11.8 fps.

A boost in performance. So far I have had good stability. I would suggest a strong consideration to do a commit in combination with a 32mb swap file in emmc.

Currently I have to do a swap on command after every reboot. Suggestions on how to make this sticky? Is fstab also supported in /data/local to survive updates?

---------- Post added at 08:37 PM ---------- Previous post was at 08:15 PM ----------

Repeating tests with a 128MB swap. I know that some had questions if this would be of benefit. If I detect any added benefit, I'll post an update.

Due to the Git documentation mentioning a 32MB swap, I suspect that this may be an OMAP3 limitation and larger files of little improvment.

I'll know soon.
[Nook Color Android Development] SeaFractor:
It was pretty quick to see the difference.

From fairly stable to fairly unstable. I've had multiple FC's and complete device hangs several times since trying a 128MB swap.

Guess I'll try to split the difference next and see what a 64MB swap provides. However, I'm suspecting that 32MB might be the sweet spot.
[Nook Color Android Development] stolenmoment:
I installed swapper2, which appears to work. Recreating the swapfile at every boot is dreadfully slow, so I'm going to disable that feature. The few competitors I found appear to use a fixed filename on /sdcard, so I discarded them.

EDIT: I spoke too soon, swapper2 appears to be unstable. I'll write a little shell script we can run at boot time.

Hmmm... these sorts of limitations generally come from OS architecture limits rather than hardware. Unless I'm more out of date than usual, there's no hardware assist for swapping (picking the unlucky page, writing it to storage, fetching its replacement page), just the memory mapping itself.
[Nook Color Android Development] stolenmoment:
Here you go...

NOTE: this has been updated after testing.

#! /system/bin/sh

# Create, initialize, enable a swapfile

SWAPFILE=/mnt/emmc/swapfile
SWAPSIZE=512 # megabytes
FSTAB=/system/etc/fstab

# Does swapfile exist?
if [ ! -f $SWAPFILE ]
then
echo Creating swapfile
dd if=/dev/zero of=$SWAPFILE count=$SWAPSIZE bs=1048576
echo Initializing swapfile
mkswap $SWAPFILE
fi

# Does fstab exist?
if [ ! -f $FSTAB ]
then
touch $FSTAB
fi

# Does it contain The Right Stuff?
if fgrep -q $SWAPFILE $FSTAB
then
echo fstab OK
else
echo Creating fstab
echo > $FSTAB \# Automatically created
echo >> $FSTAB $SWAPFILE none swap sw 0 0
fi

if swapon -a
then
echo First swapon successful!
else
if grep -q $SWAPFILE /proc/swaps
then
echo Swap already enabled.
else
echo First swapon failed! Trying mkswap.
mkswap $SWAPFILE # just in case...
if swapon -a
then
echo Second swapon successful!
else
echo Second swapon also failed! Sorry...
fi
fi
fi

cat /proc/swaps

Install this somewhere flashing won't scribble on (/sdcard, /emmc). Must be run as root, probably explicitly with "sh" (/sdcard and /emmc are mounted noexec), with /system mounted R/W.

Customize as you wish!
[Nook Color Android Development] SeaFractor:
This certainly makes sense. Just some feedback from further testing. I tried the new 4-5 opengl build along with the kernel.

128MB cache yields the least stability but also nenamark1 fluctuated between 12 to 13.1fps.

64MB cache the nenamark1 fps leaped to 14.0
[Nook Color Android Development] cpkroboth:
This was the trick... Teach me to follow the original directions... ;):p
[Nook Color Android Development] stolenmoment:
Do any of these tests actually cause swapping? Is "free" or "cat /proc/swaps" any different after running them?
[Nook Color Android Development] SeaFractor:
One would think that the tests themselves wouldn't cause swapping, but the values are different after the test.

cat /proc/swaps always showed that the file use matched it's size after the test.

Currently with 64MB swap I see:

swap: total: 56 used: 56 free: 0

I'm wondering if it's other processes not related to nenamark1 application, but the OS itself, that has this impact?

I reboot, perform the swapon -a and then perform the testing each time, so it shouldn't be swapping other applications yet.
[Nook Color Android Development] stolenmoment:
Ouch! Your swapfile is too small, it's full. Mine is:

Swap: total: 521104 used: 43280 free: 477824

Which also means that mine's too big at 512M. Are you sure yours is 64M and not 64K?

More experiments...
[Nook Color Android Development] SeaFractor:
:eek:

I'm going to delete that file and allow your script to create a new one. I thought I'd created it correctly, but the results are way different than yours.

ZOMG! Time to toss out my avatar and replace w00t with n00b!!

I did have a 32K and 64K swap. When testing why, I found that I had entered in the block size as 1024k and not as 1024K. Android is very much case sensitive and my file was created using a block size of 1024.

Well the silver lining is that if you are going to starve the OS with a teensie tiny swapfile, the smaller the better :)
[Nook Color Android Development] stolenmoment:
Actually, that's not Android, that's Linux's inheritance from Unix; the dd command has been around since at least the 1970s, and its argument handling is a direct poke at IBM's OS/360 job control language syntax. I was a JCL wizard in college, on punch cards, before running an entire department off a PDP-11 running Unix off of two 80M disk drives. (pedantry mode off)

I think you gave it just enough room to act like a sliding-tile puzzle.

I'm going to watch my swap usage, currently just under 50M, and most likely shrink my swapfile. Can't find a high-water mark anywhere, so it's hard to be sure how much would be used.

I'm very interested in your new performance results!
[Nook Color Android Development] mateorod:
I noticed the same thing, and have settled on 64 mb, in emmc.

And seafractor, I did the same thing the first time I made the swap file.:p

Now, when I recreated it, I just made the bs=1M, which worked fine for me. Who knows what the problem with that syntax was for others.
[Nook Color Android Development] Kem-El:
ICS fragments(?) phone instead of tablet

devs, I have a question (which I've asked before, but have yet to get any feedback) ...

First, some background:

Starting with the 2012-02-02 samiam build (february, but could have actually been 1 or 2 builds before) after flashing the update, I noticed that my Evernote app lost its tablet layout, reverting back to the phone UI.

I looked through the log files and noticed the Evernote was logging the NC screen size as 4.xxx inches, comind from the Android API, android.uitil.DisplayMetrics. (The Evernote forum site mentioned that anything less than 7 inches would revert to the phone interface, understandable).

So, I modified the Evernote app, forcing it to ignore the phone UI ... everything was back to normal.

Or so I thought. I've noticed that several apps (Evernote, IMDB, and at least 1 other, although I forgot which one) display phone interfaces instead of the tablet.

(I'm currently running eyeballer's opengl ... and have the same issue.

I run the default DPI of 160, so this should not be the issue.)

I reinstalled fattire's sneakpeak2-fullofbugs.zip, after performing a factory reset ... then installed the IMDB app.

Lo' and behold, IMDB with the tablet interface!

So the question:

Any ideas what could've changed in /system that would cause the android API to report the wrong screen size / or whatever else affects tablet UI?

Obviously, something between sneakpeak2 and 2012-02-02 nightly+ is causing the problem with some apps displaying as phone UI.
[Nook Color Android Development] afzalarsalan:
Its already known that the brand new opengl drivers cause the incorrect screen size to be displayed. To prove this, just flash the kernel which keyodi says to have the old opengl drivers about 5-6 pages back.
[Nook Color Android Development] keyodi:
Actually, i removed the kernel i posted a few pages back since i didn't want a bunch of different kernel versions floating around

@Kem-El - PM me if want to test that kernel out

---------- Post added at 02:02 PM ---------- Previous post was at 02:00 PM ----------

@fattire

@Hacdan

Test setup

opengl, 2.6.32.59 kernel, modded wifi module, wi-fi left on: 43% @ 12:00am 4/6 - 40% @ 8:30am 4/6

So, after 8.5 hrs only 3% battery loss. I must have a blessed nook
[Nook Color Android Development] SeaFractor:
Just reporting back.

With a properly sized 64MB swapfile, stability has gone way up compared to the micro swap :)

Strangely, opengl performance is lower. Nenamark1 get's 12fps, but the overall GUI performance is greatly improved.

I like the overall improvement. I'm certain the opengl stuff will eventually get dialed in with the correct updates over time, but the kernel/swap so far are providing me the best user experience so far.
[Nook Color Android Development] CCivale:
Forgive me for being completely clueless about this....but how and where do I put this script so it runs at boot?
[Nook Color Android Development] stolenmoment:
So far, nowhere. I don't write apps, is there some scripting app that can wrap this up? Is there a directory in /data that contains scripts that get run at boot time?
[Nook Color Android Development] racks11479:
dont know of anywhere in data but ......"/system/etc/init.d" ?????
[Nook Color Android Development] Kem-El:
Thanks keyodi,

Haven't had much time to play around with it yet, but the kernel appears to solve the display issue, the apps are in tablet layout now.

Haven't used it enough yet to know if there are other issues.

I appreciate the help :)