yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] mateorod:
Edited the egl.cfg file as directed. About to flash. I will report back after some testing, and as I ldid experience the freezing before and should be able to see any differences.

Update: I have been running around in the ROM for maybe 40 mins, no troubles except for a general laginess. I have been messing with the performance settings some, I think I will go back to interactive and leave it there for awhile. But yeah, no freezing, but there is strong sense of general malaise.

Still upfront and center with the overall ability to kick serious ass, mind you. Every time I flash this thing some new setting or configuration will jump out of nowhere and karate chop me.

Update 2: one crash in about 4 hours of testing,, during a market update. That is less than when I was testing the opengl before the modification to ego.cfg file although since ii did have the one crash I can't say wth certainty that the mods are the cause. The laginess hasnimprovedslightly, but is still somewhat of an issue, particularly while using keyboard. It takes a while for the key press to register.

I don't know if that helps you any, keyodi. I did see an almost 200 point increase in m Quadrant scores, but I don't see a lot of stock put into that program, so who knows. Thanks for all your time and talent!
[Nook Color Android Development] racks11479:
For anyone wondering what keyodi's suggestion is used for

Revisiting egl.cfg

-Racks
[Nook Color Android Development] SeaFractor:
Far fewer crashes since I've made this change. Still have crashes, but greatly reduced.

fps in nenamark 1 and other tests also increased. However, still lower openGL scores than from CM7. I suspect that the driver still needs some tweaking, but it's nice to have!

Excellent find!
[Nook Color Android Development] leapinlar:
Fattire/Keyodi,

I have another request for a feature in Nook Color's ICS. As you probably know, ics is set up with two gui's, one for tablets, and one for phones. If your lcd density is set for 160 or lower it displays the tablet gui (the one that most see here). If it is set any higher it displays the phone gui (which is the more traditional one with the status bar at the top). ICS is also designed to operate on devices both with and without hardware buttons. In tablet mode it always displays the soft buttons regardless of whether it has buttons or not. However in phone mode it suppresses the soft buttons on phones with hardware buttons to give the phone screen more real estate. On phones without hardware buttons the soft buttons are displayed.

How does ics know? The manufacturer determines it with a setting in framework-res.apk. Under res/values in the apk there is a setting file named bools.xml. In that xml is a line that says "config_showNavigationBar" that in the nook's case is set to false. It needs to be set to true. The Galaxy Nexus, which is one of the few phones without hardware buttons, has it set true and the soft buttons show in phone mode.

I have been trying to decompile the apk and change the setting and re-compile. But tools available to me do not work well with ics apks. I've had very little success. One really needs to do it in a development environment.

My request is that one of the devs see if they make this change. That way if users want to change the density and use the phone gui to make the text larger in apps, they won't lose the soft keys. It would be good if this could be done in the nook color branch since a majority of devices using CM9 have hardware buttons.
[Nook Color Android Development] SGH-i200:
egl.cfg fix to stop random freezes

@keyodi - My NC didn't freeze since I applied your fix! Will do further testing...
[Nook Color Android Development] swaaye:
So has anyone determined a way to hide that ICS status bar? I want my fullscreen! :D

I read a bit about this back when Honeycomb showed up with the permanent status bar. Somebody figured out how to hide that one eventually. ICS seems to make this harder to pull off.
[Nook Color Android Development] Kem-El:
Devs, any body know why the screen size would calculated as 4.xxxxx inches width?

After flashing the Feb 2nd nightly, the Evernote apk reverts to a phone interface because of this.

Sent from my NookColor rockin' tasty ICS
[Nook Color Android Development] mateorod:
Swaaye—

I am pretty sure if you look under the combined bar settings in the settings menu there is an option to hide. I just reflashed 7.2, so I can't test it, but I am pretty sure you can find it in the home settings. In the same menu as the drawer and so on.
[Nook Color Android Development] dmbyte:
As an FYI, I am testing each build on emmc and so far, none of them are working completely right with Angry Birds or Jelly Defense. The touch interface seems to stop responding at some point after launch when heading into gameplay. Is there anything I need to do to capture anything helpful?
[Nook Color Android Development] swaaye:
I think that I tried the option you're referring to but it didn't seem to have an effect. It looks like a lot of the tweaks are unfinished placeholders right now.
[Nook Color Android Development] Android311:
Wow absolutely amazing, great work devs and everyone that is working hard on ics/cm9, thank you I love this :D

NookColor ICS 9 Nightly "Overclocked"
[Nook Color Android Development] racks11479:
Regarding you're request. I went ahead and compiled last night with "config_showNavigationBar=true" for the framework-res.apk. Unfortunately it was all wonky. :(

My findings were as follows:

I've set my lcd-density to 240, 180, and back to 160

-For 240 the only button that appears at the bottom is one large black bar which turns out to be the recent apps button in landscape and portrait.

-For 180, same as above, but in landscape there is no black bar. It only appears in portrait mode.

-Going back to 160 tablet UI. The buttons basically are non-existent for either landscape or portrait.

So, I guess it takes more than just changing the 'config_showNavigationBar' to 'true'. If you'd like I could PM you the framework-res.apk for you to test out for yourself. This was built with OpenGL renderer on as well with fattires kernel. Not sure if that would have mattered anyways. But just an FYI.

Thanks,

Racks
[Nook Color Android Development] leapinlar:
Racks, thanks for this. I sent you a PM with my email address to send to me. I will keep experimenting. I know with the right help we can make this work.
[Nook Color Android Development] pdanders:
I believe that the "NavigationBar" config only applies to certain phones now and NOT tablets.

Here's what I think is relevant API doc

Controls for system UI visibility

Since the early days of Android, the system has managed a UI component known as the status bar, which resides at the top of handset devices to deliver information such as the carrier signal, time, notifications, and so on. Android 3.0 added the system bar for tablet devices, which resides at the bottom of the screen to provide system navigation controls (Home, Back, and so forth) and also an interface for elements traditionally provided by the status bar. In Android 4.0, the system provides a new type of system UI called the navigation bar. You might consider the navigation bar a re-tuned version of the system bar designed for handsets—it provides navigation controls for devices that don’t have hardware counterparts for navigating the system, but it leaves out the system bar's notification UI and setting controls. As such, a device that provides the navigation bar also has the status bar at the top.

To this day, you can hide the status bar on handsets using the FLAG_FULLSCREEN flag. In Android 4.0, the APIs that control the system bar’s visibility have been updated to better reflect the behavior of both the system bar and navigation bar:

The SYSTEM_UI_FLAG_LOW_PROFILE flag replaces the STATUS_BAR_HIDDEN flag. When set, this flag enables “low profile" mode for the system bar or navigation bar. Navigation buttons dim and other elements in the system bar also hide. Enabling this is useful for creating more immersive games without distraction for the system navigation buttons.

The SYSTEM_UI_FLAG_VISIBLE flag replaces the STATUS_BAR_VISIBLE flag to request the system bar or navigation bar be visible.

The SYSTEM_UI_FLAG_HIDE_NAVIGATION is a new flag that requests the navigation bar hide completely. Be aware that this works only for the navigation bar used by some handsets (it does not hide the system bar on tablets). The navigation bar returns to view as soon as the system receives user input. As such, this mode is useful primarily for video playback or other cases in which the whole screen is needed but user input is not required.

You can set each of these flags for the system bar and navigation bar by calling setSystemUiVisibility() on any view in your activity. The window manager combines (OR-together) all flags from all views in your window and apply them to the system UI as long as your window has input focus. When your window loses input focus (the user navigates away from your app, or a dialog appears), your flags cease to have effect. Similarly, if you remove those views from the view hierarchy their flags no longer apply.

To synchronize other events in your activity with visibility changes to the system UI (for example, hide the action bar or other UI controls when the system UI hides), you should register a View.OnSystemUiVisibilityChangeListener to be notified when the visibility of the system bar or navigation bar changes.

See the OverscanActivity class for a demonstration of different system UI options.
[Nook Color Android Development] webdroidmt:
Hi Keyodi,

Just wanted to give some feedback. I tried eyeballer's 0206 open-gl build last night removing the above line in the egl.cfg and I had just one freeze while in the standard browser requiring a reboot on the initial rom boot. I'm happy to report after that initial boot, I've had no freezeups since.

I visited the top flash websites of 2012 and had no issues with anything I tried to view. Overall, browsing is fairly good but does bog down on the more graphic intensive websites, like ESPN and CNN. Hopefully, some further tweaking will improve overall smoothness.

One other thing with the open-gl, I'm able to use Chrome Beta, the only issue so far is that settings FCs. With the non open-gl build I couldn't even get a website to come up, so I see some great progress here. Thanks for all your contributions on the NC.

Mike T
[Nook Color Android Development] SeaFractor:
Eyeballer,

update-cm-9.0.0-encore-KANG-20120208-030001-signed.zip has been the most stable for me to date.

One question, I've tested this build with the egl change (remove 0 0 android) and received an opengl performance boost, even though I'm sure this is not an opengl version.

I use nenamark 1 to test. With the opengl version of the previous nights KANG, I receive 14.9 fps with 1200Mhz and PERFORMANCE as the govenor. With this new build, the egl change, speed and govenor I receive 13.0 fps.

It seems strange to me that the opengl version only nets 1.9 fps difference (average of 5 tests on each platform) but is much less stable.

I'm not sure what the difference between the 7th opengl and the 8th might be besides the drivers, but it makes a huge difference.

Notifications are working, even from sleep and I've not yet received a DOS where I'd have several through the day with the 7th version.

Hope this helps track down what might be triggering the instability if the 2D portion of the drivers are the same and it's just the opengl changes. Still wild the egl edit works without opengl.
[Nook Color Android Development] Lsjreadingpa:
I'm going to upgrade from 7.2 to cm9 KANG opengl 109-signed and wanted to know do i still need to install sneakpeek1 first?
[Nook Color Android Development] leapinlar:
You only need to post this question on one thread. Please don't double post.
[Nook Color Android Development] SGH-i200:
Which is the correct thread?

@Lsjreadingpa - Do a full wipe and flash the CM9 opengl.

@leapinlar - You are right. But which is the correct thread?

[DEV] CM9/ICS Work-In-Progress = cm9 KANG opengl 109 (eyeballers)?

[USER] ICS/CM9 Discussion = cm9 KANG opengl 109 (eyeballers)?

[UNOFFICIAL][ICS][NIGHTLIES] CM9/ICS Nightly Builds = SAM Builds?

I would prefer a clear line. If I read in SAMs thread I want to read about his nightlys not eyeballers...
[Nook Color Android Development] eyeballer:
I agree, I would keep talk of my nightlies out of Sam's thread. The place for discussion of these is the USER ICS/CM9 thread. People shouldn't be posting in the DEV thread unless they have something development related.
[Nook Color Android Development] Android311:
I've been running this for a day now with no problems :) download a lot of apps and works great thanks dev!

NookColor ICS 9 Nightly "Overclocked"
[Nook Color Android Development] fattire:
Quick heads up...

So the consensus was that the 1.8 egl stuff works fine, and that the "109" kernel build is a little more stable..

So I've merged the kernel changes into the regular source and eliminated the ics-fattire-test branch. At the same time, Keyodi has merged the ics-test branch in the device repo into the regular ics branch. Both the "test" branches have been deleted.

So now we're back to normal. Note that due to a lack of consensus on OPENGL_RENDER being on, it's not for the moment.

If you have edited your repo/.local_manifest.xml file to use "ics-test" you probably want to change that back to "ics". And if you're building, the egl binaries in vendor/cm/proprietary need to be the new ones, not the ones from cm7 (unless mirage has switched over... I don't know if it has).

Thanks, Keyodi, for doing that merge.
[Nook Color Android Development] SeaFractor:
Fattire and Keyodi, thanks!
[Nook Color Android Development] jwzg:
Use the "thanks" buttons folks.
[Nook Color Android Development] sark666:
I didn't have net access for a bit but when I see:

I was curious and asked before about ui hardware acceleration but didn't hear much. Did this relate to an attempt? at implementing hardware acceleration for the UI?
[Nook Color Android Development] lekofraggle:
Take a look at the other ics thread. It has been there for a little while, but it was only on the test branch. It is in this build, but you have to edit a system file.

Good luck.
[Nook Color Android Development] SGH-i200:
Sam doesn't provide builds with OPENGL_RENDER on - but eyeballer does!

[USER] ICS/CM9 Discussion
[Nook Color Android Development] 911jason:
Does anyone know why the Kindle app acts like it's on a phone on ICS compared with GB? Is it the LCD density setting? On CM7 the Kindle app works perfectly for me, but on CM9 it only displays about 1/5th the amount of text with huge margins and line spacing.
[Nook Color Android Development] leapinlar:
You need to upgrade to the latest version of kindle. I had those problems until I upgraded.
[Nook Color Android Development] 911jason:
Just flashed the latest OpenGL nightly tonight and then updated every app that had one available, including Kindle. It still was displaying like a phone screen.
[Nook Color Android Development] bdcrim:
Some apps seem to respond to running spare parts from the market and either ticking or unticking the option to run older apps in compatibility mode. I think a reboot is required. May give that a shot.
[Nook Color Android Development] 911jason:
Thanks for the suggestion bdcrim, I'll give that a try.
[Nook Color Android Development] leapinlar:
Not sure what you mean by "like a phone screen". The margins, line spacing, etc are adjustable in the latest version of kindle. Go to view options.
[Nook Color Android Development] 911jason:
Those options don't make any difference at all in this problem. I'll try to take screenshots tonight and post them for you.
[Nook Color Android Development] leapinlar:
Do you mean the kindle app is running in a small window with black around the edges? If so that is a screen compatibility problem. Go to Dev tools app, choose development settings and uncheck "disable compatibilty mode" and reboot.

It might also be the opengl doing it. Try the other version.

Edit: The problem is lcd density and the Kindle app. And it is just the opposite of what you were thinking. When first installed, CM9 runs at 160 density and is in tablet gui mode. That means that the status bar is at the bottom and it has soft keys. If you change density upwards, the nook switches to phone gui mode with the status bar at the top and no soft keys.

Now, the kindle app senses the difference and changes its interface accordingly. What you are seeing is the tablet version of kindle. If you put it in landscape on the opening screen, you will see two panes, a menu on the left and book covers on the right. And when you open a book it has wide margins, with no way in options to change that.

If you change the density to 240, like I use, the phone gui takes over and kindle switches to the phone layout. It has only single panes and has a "view options" setting to allow changing margins and line spacing.

The only problem with using the nook at 240 is no soft keys. I get around that by using Button Savior. Eventually the devs will be able to add the soft keys in phone mode like the Galaxy Nexus has. Someday.
[Nook Color Android Development] Android311:
Is anyone having music foreclose? I'm running nighlty 2/8/10

NookColor ICS 9 Nightly "Overclocked"
[Nook Color Android Development] Android311:
I downloaded Google music in the market and works perfectly, is it possible to actually add this app in the rom since Google music is really the same as ics music app?

NookColor ICS 9 Nightly "Overclocked"
[Nook Color Android Development] SeaFractor:
I do use it, but it's impersonal. I've never been able to determine how to see who thanked for what just an increasing number. I've a paltry number in comparison, but I don't know who clicked the "thanks" button, just that someone must have.

However, I'll stick to just that from now on. This and the prior post will be "thanks for all the work, past, future and present". I must be one of the increasing numbers from this point forward.
[Nook Color Android Development] leapinlar:
In Tapatalk or XDA app the thankers are always shown. In the web version of XDA, if you click "show/hide" next to the number of thankers, it shows who they are and what date they thanked.
[Nook Color Android Development] Android311:
Ya on the xda app there an icon of a flower and username , that represents thanks

NookColor ICS 9 Nightly "Overclocked"
[Nook Color Android Development] Android311:
what race car game is that?
[Nook Color Android Development] sdlopez83:
Yeah but im trying to get a modification. Maybe a shortsale
[Nook Color Android Development] Android311:
What do you mean? Im not understanding
[Nook Color Android Development] libertus77:
Your question said "foreclose" instead of "force close". Sdlopez83 was messing with you.
[Nook Color Android Development] Android311:
Bahahahaha :p lol
[Nook Color Android Development] botossi:
onScreen Open Source !!

Hey Guys, specially Dalingrin... i remember reading one of your posts that you said that you would like to see Onscreen action in our nook, didnt you :cool:

Well, now is Open Source !!!!

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

Just sharing the news!!!

Thanks for the great work that you guys a doing to keep our Nooks alive and updated!
[Nook Color Android Development] Android311:
Sweet! That's cool! :D
[Nook Color Android Development] Dj-Gutz:
Sweet! Thanks :)

comment from their FB page :
[Nook Color Android Development] leapinlar:
I have some really good news for those folks that don't like the tiny fonts on the default 160 dpi resolution. You can now go to 240 dpi and have SOFT KEYS! With the help of a very smart person (gogodu5sU) on another forum here at XDA, I have been able to develop patches that put soft keys with the phone gui that ics displays with anything higher than 160 dpi.

The only issue is if you want to go back to 160 after being at 240 with soft keys, you probably should reverse the patch because the patch messes up the landscape home screen at 160. No problem though, just reflash your existing or a new nightly and it will remove the patches.

I am attaching one update zip file to the board. It is to apply the patch for soft keys and set the density to 240. The zip can be installed with CWM recovery if on emmc and can be used with SD installs by placing it in the boot partition and booting to recovery.

The patch must be re-installed after flashing a new nightly.

If you use the SD install method, the patches install properly but density must be changed manually by editing build.prop in /system. The first time you flash the soft key-240 it will boot up in 160. Just add the line: ro.sf.lcd_density=240 or whatever density you want, reboot and all will be well. Actually, the best way to set the lcd density for SD installs is to put that line in a file called local.prop in /data. If that file does not exist, just create it with a text editor and put the line in it (don't forget to set permissions). By putting it in local.prop the setting does not get wiped out with each flash of a new nightly on your SD (but you still have to install the patch file).

Enjoy!

Edit: There is a hidden button on the navigation bar far to the right that turns off the screen with a tap or brings up the power menu with a long press.

Edit 2: And there is a hidden search button to the far left.

Edit 3: The order of the keys was driving me crazy (Back/Home/Menu), so I revised them to suit me (Menu/Home/Back, the same as my Galaxy Tab).

Edit 4: Here are screen shots to see what they look like (revised layout).

Edit 5: I have prepared revised patch files based on the nightlies as of 2-12-12. They have a Rev 1 after them.

Edit 6: I have now found how to modify the build so that these patches are not necessary. I am pulling the attachments. If someone still wants them, PM me. See my post of 2/15/12.

Edit 7: I decided to re-attach the file. I don't think these patches will get included into the build. I will try to keep it fairly current. This is necessary because as CM9 evolves, the patches may need to be updated. Check back here periodically to see if a new version is attached.

Edit 8: I created a new thread on this subject and all future updates will be posted there.

http://xdaforums.com/showthread.php?p=23727445
[Nook Color Android Development] HacDan:
I'd recommend people stay away from the above files from leapinlar as they are replacement systemui and framework apks. Which is fine, just as long as you're flashing his update over what ever version that was modified originally. If you're not, however, you're going to run into issues or lose out on new features being added to CM9.

---------- Post added at 10:00 AM ---------- Previous post was at 09:58 AM ----------

No one know's who's 'nightly' you're running. And besides, this is a development thread. If you're looking for help, you could try #nookcolor on freenode, but please try to keep this thread somewhat development related.