yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] SeaFractor:
Posting my cross-link to the ICS thread from Dalingrin. http://xdaforums.com/showpost.php?p=23249779&postcount=2033

In this, I explain that I do receive positive results using Keyodi's suggestion every time. I'm more than certain that it's not a placebo and should be considered as an addition for the default configuration in the OpenGL builds.

Seperately, I also wanted to note that the latest build you created has gone a long way to resolve stability issues. At a review of what had changed, you can see in my post that I point that it's likely related to the Javadoc fix by Steve (who continues to astound in CM even with his new job :) ).

The 3-1 and 3-3 builds still didn't have that merged code yet, so it'll be interesting to try from 3-4 onward for those that had enough instability that it was difficult to determine if Keyodi's suggestion had impact.

I also mention my memory configuration settings using the stock OpenGL builds.
[Nook Color Android Development] numus:
Might want to also limit the background processes to 2 or 3... I find that the standard background processes eat the battery and also slow it down a lot...

I think one of the problems with V6 is.. we don't have 512 mb of avalible ram... So the aggressive profile is bordering on limiting all functionality of the device.. Hense why i recommend 6 (or even 5)...

Update running 3-4 with V6 (option 6) and Keyodi's suggestion on removing the 0 0 Android line...

Also switched to 600-1200 with conservative gov. (just for the time being) and already noticing a much faster rotation (landscape to portrait and back) transition.. Was very sluggish on previous builds and it takes about 1/2 the time (still a second or two) for it to attempt to make the transition...
[Nook Color Android Development] SeaFractor:
Thanks! I'd missed that setting as it's not sticky in "Developer Options". However, if I reboot and will remember to check it, I do see the benefit.

Currently I'm looking for the corresponding build.prop entry to add to fix that setting.

While in "Developer Options", have you tried the Windows and Transition animation scales changed to .5x?

Once I find the entry for fixing the setting for background process limits in build.prop (if that option does exist), I'll come back and update this post.
[Nook Color Android Development] numus:
That speeds up the animation which is fine.. what i am referencing is a sensor lag tho... The time between you switching it into another mode and the sensor triggering the action to occur.

Anyone tried these?

# Render UI with GPU

debug.sf.hw=1

# Increase overall touch responsiveness

debug.performance.tuning=1

video.accelerate.hw=1

Don't we have video acceleration with opengl?

Strange... the build.prop has wifi.supplicant_scan_interval = 30

This seems like a very short time and could be leading to battery drain with wifi on.. correct?!?

But then v6 sets wifi.supplicant_scan_interval = 180

Any idea which one is the one that will set? Think i am going to delete the =30

Also in buildprop

Dalvik.vm.heapsize=256m ... That can't be right.. Shouldn't it be 48m since growthlimit is set to 48m?!?
[Nook Color Android Development] timmyjoe42:
Is the only difference between the 700 and 800 kangs the open gl?
[Nook Color Android Development] eyeballer:
Yes, unless something is merged in that hour, then it will make it to the 0800 build.
[Nook Color Android Development] stolenmoment:
I'm running a tnp build (20120220-tnp), and I've been having a problem updating ever since I installed it. I just installed both of this morning's eyeballer builds, and latest gapps (20120304), and I get a complete lockup after Android starts up.

The installs this morning went: wipe both caches, format /system, install system zip, install gapps, go. Both played the (cropped) bootanim, "optimized" my apps, then went into the lock screen. After that, my NC locks up completely with the screen on. The clock doesn't update, no touches appear to register, short press on power does nothing, unplugging the cable doesn't turn off the charging icon. It does connect to the local WiFi. I might get a few notifications (usually ClockSync), I might not. While it's "optimizing", touches appear to register; I have "show touches" enabled, it's very instructive, esp. when the screen gets wet or dirty!

I get the same behavior with tnp's last build, 20120225-tnp-emmc.

Any ideas? I can reflash 20120220-tnp as above and all is well. Does anybody know if that build leaves some settings that kill the later builds? Can I wipe settings without a complete data wipe? Have I missed a setup step somewhere?

I have set CPU to 600-1200 interactivex. I've deleted all of my superuser allows and I'll see what happens next, but I'm at work, and there's stuff to do...

Thanks for any help!
[Nook Color Android Development] numus:
Added:

# Render UI with GPU

debug.sf.hw=1

# Increase overall touch responsiveness

debug.performance.tuning=1

video.accelerate.hw=1

To my build.prop and the UI is much faster and smoother (only 3/4 with opengl and the 0 0 android removed)... Only problem.. I scrolled thru my app drawer way to fast back and forth and caused the nook color to reboot lol.....
[Nook Color Android Development] SeaFractor:
Numus,

You likely have been referencing thread that I also have used for build.prop, etc, referencing.

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

In that one, the supplicant timeout is set much higher than from SuperCharger, so 180 shouldn't be an issue. Guess some are using 7 minutes. The only disadvantage I would see is if you are in an environment would be with multiple networks and are roaming between them. With a large value, it would be possible to loose connection to one Wireless connection and wait before it discovers the new one during the scan 3 minutes later.

As for the rapid scrolling leaving you a locked up Nook, perhaps the following setting is something to try experimenting with.

It's item #6 on the thread I posted.

windowsmgr.max_events_per_sec=150
[Nook Color Android Development] numus:
Naa i was referencing from the google documents but it is the same thing in the end..

Our wifi supplicant was set to 30 seconds (which if you dont have wifi sleep policy turned on can eat the battery a lot)... V6 implemented a 180 but it didn't delete the 30.. So i had 2 entries for wifi supplicant. I deleted the 30 second one and left teh 180 second..

I also enabled hardware acceleration and rendering of the ui by the gpu.. it made it much snappier... Will try changing the max events per second...

V6 also set windowsmgr.max_events_per_sec=200... just dropped it down to 150

Also dropping VMheapsize from 256m to 48m ...

I would recommend you try those in your buildprop and let me know what you think.
[Nook Color Android Development] meklord:
Stolen moment: wipe cache & dalvik

Using today's build and the latest g-apps :

Everything seems much snappier. Only thing I noticed is a FC while playing "Words with Friends" (after making a move then backing out of the advertisement)
[Nook Color Android Development] stolenmoment:
That did it; it appears to have been either LCD Resolution or the JMRI throttle app. I uninstalled the former and disallowed the latter and I'm now running last night's opengl build. I'm much happier now.
[Nook Color Android Development] stolenmoment:
Yep, did that every time. Turns out to be a misbehaving superuser-allowed app.

I've had one spontaneous reboot, but all else is very smooth. A bit slower, perhaps, but smooth.
[Nook Color Android Development] numus:
I have a feeling manually editing build.prop every update is going to be annoying
[Nook Color Android Development] pavlos46:
Loaded latest opengl build and flash player doesn't work!!!

Any ideas? It used to work on previous builds...

Pavlos
[Nook Color Android Development] SeaFractor:
I agree. I have used your recommended settings for a day and found it the most stable so far.

Thanks!
[Nook Color Android Development] friedsonjm:
Apex vs Nova Launcher

Well, I've installed the Apex launcher and will spend the hours setting it up... I'm reluctantly moving on from Nova, as I just can't 'live' with the waste of screen space and limited number of apps on the home screen. Was hoping that I could use a home screen migration app to pull in my Nova setup, but, strangely, it recognized the 'Trebuchet' launcher, but did not 'see' Nova.

Lots of work to do... will report on how well it works. jf
[Nook Color Android Development] slickie88:
I haven't use Nova yet, but I love Apex. Much better performance compared to Trebuchet. Even started using in favor of GoLauncher EX on my Galaxy S2.
[Nook Color Android Development] tourist2:
I found a problem with the ICS (at least with the non OpenGL version). The tilt control only works in landscape mode disregarding the orientation of display. So I have a hard time playing Doodle jump or similar games that I have to hold it in landscape position while the screen is in portrait mode. Is there any fix to that. The same games work fine in CM7. :(

Thanks.
[Nook Color Android Development] leapinlar:
Go to settings and accessability and make sure you have 'auto-rotate screen' checked.
[Nook Color Android Development] friedsonjm:
First comment... adding icons to the home screen is very, very slow. I have a lot of apps, but compared to other launchers, for this process, Apex takes a long time to load the list, and like most, only loads one at a time. This is going to be painful... :(

EDIT: More than slow, just locked up trying to add an icon.. will reboot...

EEDIT: Process is faster after a reboot... not to be confused with 'fast..'

EEEDIT: And just had a reboot while trying to select an app icon to add... may be in a bootloop.. Yep, had to shut it down the hard way. Running now, and continuing to add apps to home page.

EEEEDIT: Added a couple of more icons.. and the system locked up! Rebooting... and adding more...
[Nook Color Android Development] Henk Poley:
That doesn't fix it. A simple game where this happens is "Cube Runner". You have to hold the NC in landscape to play the game that displays in portrait. It's kind neat for playing on the couch, but..
[Nook Color Android Development] leapinlar:
Part of the problem is that the devs rotated the screen in the kernel which was necessary for android to display properly. The downside is that some apps display things 90 degrees off. No fix that I know of.
[Nook Color Android Development] tourist2:
The screen does rotate fine, but the motion sensor does not. :(
[Nook Color Android Development] sherpajosh:
I am having trouble installing this ROM. I am coming from cm7, so I wiped everything, system, data, datadata, cache, and dalvik cache. Flash a nightly, which flashes very quickly, then flash gapps. Reboot and I get a black screen after cyano-boot screen. I have tried flashing 2 and 3 times before rebooting and still nothing. Any ideas?
[Nook Color Android Development] leapinlar:
Your mistake was wiping system. The new nightlies do not like you doing that. Reflash CM7 and immediately reflash the new nightly without wiping anything, or even rebooting in between.
[Nook Color Android Development] slack04:
Been using this ROM since I got my nook about 2 weeks ago. Haven't had time to update until now. I downloaded the goo app and have DL'd the most recent build (I know the next one will be up in an hour but I can't stay up that late).

So, for updating, can I just flash in recovery? I know I don't need to do any wipes, but is there anything else? Can it really be that easy? I'll wait for a response before I press go, so... anyone?
[Nook Color Android Development] racks11479:
Its really that easy! :)

Flash away!!
[Nook Color Android Development] Henk Poley:
Are you saying that these apps display sideways on all Android 4.0 tablets ? [Sort of inferring, but that's something to approach the app developers with.]
[Nook Color Android Development] sherpajosh:
Thank you, got it running finally.
[Nook Color Android Development] eyeballer:
keyodi has an updated .59 kernel you can flash right over any nightly: http://xdaforums.com/showthread.php?p=24664697#post24664697

Feedback please :)
[Nook Color Android Development] friedsonjm:
Uploaded it today, running on top of 4/9/12 openGL, Apex launcher, 1200mHtz max, Conservative governor.. No issues so far... except just checked CPU Spy, and although sitting for most of the last couple of hours, did not go into deep sleep at all. That is a change... not a good one...

EEDIT: Have just reverted back to the previous version of the .59 kernel - will check to see if can get deep sleep with it and 4/9/12 openGL build.
[Nook Color Android Development] leapinlar:
No, I am not saying that. I am saying some apps may use lower level programming that may bypass some of the android software and work at the kernel level. Since our kernel is modified, it displays improperly. But you might approach the app designer and tell them how our kernel is different and maybe they can modify their code.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] jc monkeyballs:
I've also had deep sleep issues with the new kernel.

Resorted to setting WiFi to turn off during sleep, which means I need to turn WiFi off then on when I want to use it. It's a crappy fix, but better than coming home to a dead battery.
[Nook Color Android Development] friedsonjm:
It's actually keeping it on 1200mHtz 98% of the time - even with screen off! Changing governor to 'on demand' to see if that makes a difference...
[Nook Color Android Development] Henk Poley:
With the April 10 non-opengl build and the 2.6.32.59-take2 kernel, the "Hackers keyboard" from the Play Store now turned into a Happy Hacking Keyboard, since the key-labels [QWERTY etc.] don't show :P. No, resetting the keyboard does nothing.

I wonder what change is responsible. Everything worked with the April 2 non-opengl build and the first 2.6.32.59 kernel.

That Opera now thinks it's on a tablet, not a phone, is a positive change though :)
[Nook Color Android Development] ibilln:
Using 4.9 build with Open GL. No new Keyodi Kernel. On-demand. Running off SD.

Subjective impression is that this is the best performing setup for ICS for me so far. Pretty quick app-loading response. Deep-sleeping like a bear. Chrome settings still crashes - oh well.
[Nook Color Android Development] bigbob23:
Keyodi kernel is working fine here. No deep sleep problems (I only turn wifi on when I need to use it, then off again).
[Nook Color Android Development] friedsonjm:
CONFIRMED: The new .59 kernel prevents 'deep sleep,' with the previous version, and 4/9/12 update, goes into deep sleep just fine.
[Nook Color Android Development] RASTAVIPER:
What exactly is your setup for getting this best performing setup?

I am using the Dualboot Rom from Racks and every now and then I have random app crashes, like mail stopped working, gapps stop working, without even using the nook.

I have the Open Gl version too.
[Nook Color Android Development] eyeballer:
For those using my nightlies with the Goo Manager app, see here for an update on TWRP which now supports auto-flashing of the nightlies via TWRP. You can auto-install TWRP by updating Goo Manager in the market then flashing recovery using the option in menu. If you want to keep CWM, you can always have TWRP as recovery and CWM as alternate (that's my set up). Lots more app features to come from goo.

TWRP 2.1 thread: http://xdaforums.com/showthread.php?t=1397513
[Nook Color Android Development] KingJL:
It must have something to do with opengl vs. non-opengl. I have eyeballer 04092012 non-opengl and the new. 59-take2 kernel and I am getting plenty deep sleep (wifi always on, cpu performance "conservative).
[Nook Color Android Development] ziggy34:
Thanks so much, my Nook Color and Acer A500 are both happy, now if only MyTouch 4G
[Nook Color Android Development] friedsonjm:
TWRP Not functioning correctly?

OK.. installed the zip, after the system came back up. rebooted into recovery, TWRP gui came up, but screen is almost totally unresponsize to my touches and swipes. I was able to get the backup menu to come up, for example, but it would not accept any input, including swiping, I could only get to the main menu via the hard n button. Long press of the power button to shut down, then to restart. Thoughts?
[Nook Color Android Development] ziggy34:
On the nook, I am still using version. 2.0, have not updated to 2.1 yet., 2.0 is a little slow, but works OK. Also found that any touch recovery on any of my devices is slower than recoveries that us the hardware buttons.
[Nook Color Android Development] eyeballer:
Can you PM me on IRC, or join #twrp on freenode?

Also, please keep twrp/recovery discussion in the twrp thread just to not muddle things here :)
[Nook Color Android Development] micl9:
can you point me to how I can set up CWM as alternate?
[Nook Color Android Development] eyeballer:
Yep, flash the CWM as alternate zip from here: http://xdaforums.com/showthread.php?t=1469732

Don't use the TWRP zips in that thread yet, I need to update them for 2.1.
[Nook Color Android Development] ibilln:
I don't know about the "Dualboot Rom from Racks".

My setup is a basic SD card image from verygreen. I did my own expansion of the boot partition to ~200MB.

I've been running this card for a while (ie, /system has been set up correctly by previous builds)

I installed some version of samiam303's gapps on his op page.

I installed the Alt boot for recovery for SD cards provided by leapinlar here

When I install a new build, I wipe the cache and dalvic cache using the latter.

Current setup is simply a download of 4.9 opengl version from here. No other add-ons or installs. Of course I have several additional apps, but nothing fancy. Standard performance setup - 300/1200, switching between ondemand and conservative performance. Don't notice much diff.

I suspect the above is not much help, but it's what I got...
[Nook Color Android Development] RASTAVIPER:
Hmm yeah, not many things to do different, but thanks anyway.

I guess its all a matter of the Rom that I use from Racks.
[Nook Color Android Development] frankusb:
This is likely the result of the removal of ro.sf.hwrotation=270 and subsequent kernel/touchscreen/accelerometer changes.

Originally, the ICS rotation animations were distorted, so ro.sf.hwrotation=270 was removed. This then caused the display, touchscreen and accelerometer drivers to be changed to compensate. Since then, at least on CM7, the back ported ICS rotation animations take ro.sf.hwrotation into account.

So theoretically, the rotation changes should can all be reverted and you should have the same compatibility as on CM7.

Frank
[Nook Color Android Development] leapinlar:
It is not exactly like that. In CM7, that line was necessary to compensate for hardware differences in the nook color versus other devices. Fattire decided to not do the necessary rotation in build.prop with ICS and do it in the kernel instead (both graphics and touchscreen). So the line was removed. I think the problem is that some software work at the kernel level instead of using the android api's and the rotation in the kernel is wrong for that.

Theoretically, fattire could remove the kernel rotations and revert to the build.prop line, but somehow I don't think he is going to do that.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] tourist2:
I am also using the dual boot from Racks, but updated to the latest ICS (no OpenGL) and CM7.2 using modified zip files. So far I only experience frozen once in ICS (in a month) through various updates. I guess your problem may be related to your SD card. In addition, the OpenGL is less stable. So I only put it on my test bed microSD for fun. Currently, both CM7.2 and CM9 dual boot work really well for me (except for the accelerometer issue in ICS) after I tweaked the performance settings.
[Nook Color Android Development] eyeballer:
I'm adding the fix for not being able to flash cm9 over a formatted /system into my builds as of the ones dated 4/13.

It's still pending being merged into the cm repo (http://review.cyanogenmod.com/#change,14651)
[Nook Color Android Development] friedsonjm:
.59 Kernel Update?

Any word of a 3rd version of the .59 kernel update? I'm still using the first version, due to the deep sleep issue of the second version....
[Nook Color Android Development] mateorod:
Just an FYI, I've posted some packages that allow you to use PDroid on CM9. The post is on a pretty old thread, so I thought I'd mention it here.
[Nook Color Android Development] attmakesmevomit:
Google Account Sync/Google Apps

First of all, thanks for all the helpful posts in this thread... been running eyeballer's CM9 builds on my NC for several months now, upgrading from CM7.

For the last month or so, though, every nightly update I've done wipes out Google Account Sync from my NC, and I have to re-flash a Gapps ZIP (I'm using samiam's) to get Account Sync back, then enter the information for my Google account and my wife's, then re-sync both...

It this normal? If so, what changed, and is there anyway to avoid it? Will using the Gapps package from goo-inside.me make a difference?

Thanks in advance!
[Nook Color Android Development] Homer_S_xda:
Is it necessary to update to the latest nightlies? I'm checking these two pages and nothing jumps out as particularly important:

https://github.com/fat-tire/android_device_bn_encore/commits/ics

http://review.cyanogenmod.com/#q,status:merged+branch:ics,n,z

Although, having said that, I noticed these little gems, so maybe tomorrow's would be good?

http://review.cyanogenmod.com/14663

http://review.cyanogenmod.com/14664

Is there any other pages we should monitor for new commits?

Homer
[Nook Color Android Development] DigitalMD:
This should not happen unless you do a full wipe when you install.
[Nook Color Android Development] attmakesmevomit:
It happened first when I did an update in mid-March (after doing nightly updates about once a week w/ no issues)... then I accidentally applied a really old Gapps update (one that was for CM7) trying to fix it, and hosed everything up. So, I restored back to an old CM7 update from before I even started messing with CM9, did a full wipe, then updated to one of eyeballer's CM9 builds from late March, and applied Samiam's Gapps package again. Everything was kosher, so I updated to a newer nightly, and lost Gapps again... set up everything and got it all synced, then lost it again when I updated to the newest nightly just last night.

Any ideas on this? I guess I'll experiment by installing the goo-inside.me Gapps package and see what happens when I update next. Thanks.
[Nook Color Android Development] mateorod:
It happened to me after switching from my own builds to Sam's one night. After that it happened every flash until I restored a backup from before the switch. I didn't have that problem with eyeballer's builds.

Only wiped davlik. All the user gaps (Gmail, market, browser) were still there, but Talk and the background apps were gone (Calender storage, stuff like that.)

I tried flashing several times right on top of each other, all sorts of stuff.
[Nook Color Android Development] eyeballer:
IMO everyone should be using the gapps from goo at this point.
[Nook Color Android Development] DigitalMD:
That would be my recommendation too I Believe the version you were using that is not from goo was outdated.
[Nook Color Android Development] freonchill:
4/12 OpenGL release

3/17gapps

boxbrew to install v6 super charger

interactiveX, 600-1100 setting

1. crashed (hard lock) on home screen when trying to go to apps, before i installed boxbrew

2. crashed (hard lock) on home screen after configuring v6, wiping dalvik cache,

rebooting twice.

3. crashed (hard lock) when clicked on link to read article within google reader

tested out watching video in youtube, still choppy, even if not using HD

i think im not going to use the OpenGL release till it gets ironed out.

any comments or suggestions welcome
[Nook Color Android Development] foltz61:
Every time I install gapps from the 3/17 goo version I lose my google account and have no option of adding it back.