yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] leapinlar:
It's because of a change made to the kernel and its library files to accommodate opengl. Happened early February. I don't think there is a way to adjust stock.
[Nook Color Android Development] leapinlar:
I was able to isolate my low deep sleep problem to my calendar application. I run CalenGoo which syncs nicely with my google calendar. I was able to improve things by upgrading to the latest version. This did not change my SOD situation though. I still get them even after upgrading to the new version. But since the SOD patch is merged now, I'm not really sure it matters. But my deep sleep is much improved.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] greiland:
@KingJL. Probably that damn Facebook app! :mad:
[Nook Color Android Development] Arbelzapf:
I hope I'm not asking month-old questions, but what's wrong with opera mobile and chrome beta? Opera has an XXL-phone layout and chrome is nothing but a blank page whatever I do. Is the former a dpi issue I'm not aware of that could easily be fixed? I'm sorry if I'm not up to date with the current state of NC CM9, I've been very busy playing with my new Evo3D

I searched, but only found this post
[Nook Color Android Development] leapinlar:
The Opera issue is the same issue as the large keyboard. For some reason after the kernel update in early February, some apps show either too large or in phone mode. Don't know any solution.

I believe Chrome Beta only works on the opengl version of our CM9.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] Arbelzapf:
Thank you for the reply.

I've had nothing but lags and issues with the opengl-builds, so I decided to stay away from them for a while. Sounds like I'm without a decent browser on cm9 then.

All browsers I know aren't smooth enough to be really satisfying to use for me (Even Opera Mobile is terrible, although it's the fastest on CM7).

The only one I have found to be acceptable is "Opera Mini Next". It glides smoothly through everything I throw at it, but it also has the large phone layout and it cannot be disabled due to the lack of a menu button in its current state.

What browsers do you guys use?

PS: I run my NC on 1200mhz
[Nook Color Android Development] leapinlar:
Some say the nook running CM9 actually runs smoother at 1100. And you might try playing with the governor setting.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] Arbelzapf:
I played a lot with that in the past and I still fail to see any noticeable difference.

I also tried different setups with the Nook Tweaks app, but I still can't fight the feeling that it's just as fast as on the stock settings regardless of what I set it to.

You're right, I remember reading that 110mhz is some sweet spot for cm9. I'll switch back and monitor it for a while.

If I may ask one more question: I have read the wifi reconnection problem has been solved. What do I need to do to make that happen on my NC? I still have to turn wifi off and on to get a connection after waking up the device. I played with the wifi standby settings, but it didn't help.
[Nook Color Android Development] leapinlar:
Where did you read that? I've not heard that. And I read all of the CM9 threads. I would like the answer too.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] xdp:
Any reason the battery percentage doesn't show in the new OpenGL builds when you pull up the shade from the bottom? Next to the WiFi SSID. I liked how the older builds did this and wish CM9 for phones offered this as well.
[Nook Color Android Development] numus:
The sleep of death (SOD) issue was corrected.. not the wifi reconnect.
[Nook Color Android Development] lekofraggle:
So odd question. What is the difference between the 1640 730 and 700 versions of eyeballer's zips? Sorry if this is the wrong forum.

~Leko

Sent from my NookColor
[Nook Color Android Development] KingJL:
Could it be the time of the build?!
[Nook Color Android Development] vessamj:
Trouble with BotBrew on latest builds (3/20 exactly)

Just caught up with the latest Opengl build and now BotBrew (although installed) is not working. Whenever I load the app it starts it's "bootstrap" process but then immediately encounters an error. It repeats the same error on every retry as well. In the screenshot it shows that the services.jar service has been installed but that is from before updating to 3/20 and before the app reset from the update due to the error. I've tried wiping the app's data, uninstalling/reinstalling, and re-flashing the update after loading a backup. Has anyone else encountered this? If there is already an answer please direct me towards it.

Thanks for all the hard work guys.
[Nook Color Android Development] kLAcK107:
Build 3/19

Wifi with encryption now works, before it would d/c but still show active

however, Upon waking from sleep, wifi shows "no connection" until it is turned on and off again. Still much better than having to use unecrypted.
[Nook Color Android Development] seth.i.simmons:
Have you installed the latest version of botbrew? Redownload and install it if not.
[Nook Color Android Development] vessamj:
Yea that fixed it. I thought the app was supposed to update itself automatically?
[Nook Color Android Development] fmkaiba:
I have been building off fat-tires repo every week or so, and enjoyed building myself.

I am curious where the openGL is coming from, i assume an alternate kernel?

If anyone knows i would love to build ... just not sure what is enabling the open gl.
[Nook Color Android Development] rabi347:
Edit

10chars
[Nook Color Android Development] rabi347:
Having the same issue here. Tried uninstalling botbrew and reinstalling, but the problem keeps on coming back.
[Nook Color Android Development] keyodi:
In the BoardConfig.mk, which is located in /device/bn/encore/, uncomment USE_OPENGL_RENDERER := true

Then, make clobber and rebuild
[Nook Color Android Development] mateorod:
The packages Botbrew distributes will be current as of the time you install them. If you swipe to the left twice you will see if any packages that updates available in the repo and pressing those packages will give you the option to update. For instance, I maintain the services.jar package, so every night I flash the latest nightly and ensure it works. If it needs updating, I quickly make a new package and shoot it over to Inportb and he updates the repo. So unless you are supercharging the nightly the second it is released, you can be reasonably confident the package is up-to-date.

The app itself is under constant development, with more functions and features all the time. So it requires a manual update whenever a new apk is released. The latest, 3/16, is here.

At this moment the best way to know if there is an update is to keep an eye on the Botbrew thread linked to above. The date of the latest release is in the title, so no need to click until you see an update is available. However, that is kind of a pain, and could be easily missed, so as of, I believe, the next update, an auto-update service can be enabled from within the app itself.

It's memory usage is trivial. I have been running it all day in a testing version and it still doesn't show up in my battery usage graphs. This way the app itself will be able to remain current automatically as well. If you choose not to enable the service, I believe Inportb is working on a notification that alerts you of an update instead, but I can't speak to the progress of that personally.

If you look at the link above, the top of the first post outlines the issues. I would encourage anyone with any Botbrew related questions to go directly to the Botbrew thread. Inportb monitors it regularly, and will either fix or walk you through just about anything. Seriously. If you want some fun, see how patient he is as he taught me how to compile "Hello World" some months back. :p I can't see a situation where a replicable issue would go unsolved.

@Keyodi-- I have an initial launch Nook so I have been excited to try your new drivers! My package literally just completed so I am going to flash now. Thanks a bunch for all the work on the new kernel!
[Nook Color Android Development] stolenmoment:
Try settings/system/combined bar/battery status style.

Yeah, hard to find and non-intuitive to remember.
[Nook Color Android Development] SeaFractor:
Eyeballer,

Is the new kernel in the 21st build? Still says virtual #3.

Thanks!
[Nook Color Android Development] eyeballer:
Looks like the kernel push didn't quite make it (matter of minutes =P), it'll be in the 3/22 build.
[Nook Color Android Development] xdp:
Doesn't that set the percentage in the status bar (so it's persistently visible)? I'm talking about when you tap that to see the clock in large font and the WiFi SSID.
[Nook Color Android Development] jc monkeyballs:
I just installed the 3/22 build and my kernel still says unknown#3 in about phone. Did I do something wrong?
[Nook Color Android Development] eyeballer:
That's really strange, apparently it didn't get pulled in by (3 repo syncs done last night). I just did it manually and am pushing out some new builds. Hold tight.. ETA 15 mins each.
[Nook Color Android Development] jc monkeyballs:
Thanks!

i really appreciate your work on these nightlies.

from my HTC Sensation 4G XE with Beats Audio using Tapatalk
[Nook Color Android Development] vejur79:
I'm not sure exactly what changed, perhaps the new kernel, but the opengl nightly posted this morning, update-cm-9.0.0-encore-20120322-1739-opengl-signed.zip, works wonderfully. It is almost as quick as the earlier non-opengl build. The wallpaper scroll works with minimal lag, and the app drawer is fairly quick. I am running all this with the cpu set at 300 - 800, and the governor set at conservative. I haven't applied any tweaks or supercharged it. (I invariably found supercharging did little for me, in my opinion.)

Hopefully this isn't all in my head. ;)

Ron.
[Nook Color Android Development] boyoboyo:
I agree. Definitely a performance boost on this release.

Just checked if flash is playing, to make sure opengl is indeed active, and it does work.

As a personal benchmark, I always install "Where's My Water" and see if I'm getting a increase in frame rate, and it's definitely felt in this update.
[Nook Color Android Development] fmkaiba:
Thanks, its building smoothly now.

For the life of me i was sure i looked through BoardConfig.mk though it seems my eyes failed me
[Nook Color Android Development] afzalarsalan:
Is anyone else getting horrible battery in the non-opengl version compared to the open-gl version?

---------- Post added at 02:41 PM ---------- Previous post was at 02:26 PM ----------

I noticed that today's non-opengl is open gl enabled. Just flashed it and wallpaper scrolling is working. I had been using yesterday's open gl build but did not wipe /system because I was told not to.
[Nook Color Android Development] leapinlar:
CM fixed the wallpaper scrolling in non-hw accelerated roms. So nothing is wrong with the non-opengl version. You did right to not wipe /system.
[Nook Color Android Development] xdp:
Good to hear, I tried an OpenGL build recently and found the home screen to still be laggy. Any improvement on the too-large elements such as the keyboard?
[Nook Color Android Development] vessamj:
Trebuchet problems

Just updated to 3/24 OpenGL. Not sure if this has been answered already and I just suck at looking things up, but here it is: I am having real crappy performance with the Trebuchet Launcher. Almost every time I go to the home-screen (or unlock the device), Trebuchet force closes. Am I missing something? Is there a better launcher that has the same style as Trebuchet? Any help is appreciated, Thanks in advance!
[Nook Color Android Development] xdp:
Damn, I don't know the details, but I remember reading a SOD patch getting merged. Just flashed 3/22 OpenGL build and got a SOD pretty quickly. Can I still not leave WiFi on when it sleeps?
[Nook Color Android Development] leapinlar:
Yes, both the SOD'd kernel and SOD patched wifi module have been merged. You should be able to have wifi on all the time. But these two mods do not guarantee no SODs. They still can happen occasionally.
[Nook Color Android Development] Android311:
For some reason I cant get mine to boot, its showing a black screen for about 3 min now.
[Nook Color Android Development] DigitalMD:
I think you are having some other issue. I run 3/24 Open GL and have no such issue with Trebuchet or the lock screen. You might try the non-Open GL, some people have reported less lag with that version.
[Nook Color Android Development] leapinlar:
Did you wipe system first? That causes the installation to fail. In any case, flash a pre-3/10 nightly and immediately flash the new nightly without wiping anything or even booting in between.
[Nook Color Android Development] Android311:
This is the steps I used

wipe cache

format cache

wipe data

wipe system

flash rom then gapps right after
[Nook Color Android Development] rabi347:
I don't whether it is only me but I felt the open-gl 3/24 version felt a little more laggy than the earlier version. Anyone else with such an experience?
[Nook Color Android Development] Android311:
I think some users are experiencing this as well
[Nook Color Android Development] vessamj:
*edit* It's not a SOD issue, or a lag issue. It's just that Trebuchet force-closes almost ALL the time...
[Nook Color Android Development] Android311:
Thanks leapinlar its working now :)
[Nook Color Android Development] DigitalMD:
Try wiping the Dalvik cache. That should not happen. Doesn't do that on my install and I don't recall any one else reporting such an issue. As a last resort you might try backing up your current installation and doing a clean install after a full wipe just to see if it clears the issue.
[Nook Color Android Development] leapinlar:
In the future, don't wipe system. Then you don't have to reflash the gapps either. Wiping system screws up the nightly install. Don't do it. (And why are you wiping data, it just makes you have to install all your apps again?)
[Nook Color Android Development] leapinlar:
Don't do a FULL wipe! Don't wipe system. It screws up the nightly install. Don't do it!
[Nook Color Android Development] vessamj:
I reduced the # of home-screens and # of widgets (5 home-screens down to 3) and at the moment that seems to have helped quite a bit. I use V6's "SuperClean" (widget) to wipe caches if things start to get screwy, but that never seemed to clear up the Launcher FC before... I'll continue to do so in the event of more problems tho. My next step was to try a full wipe and re-install as I always keep a current backup, either way I'll keep you guys updated. However I think reducing the widget-load might be what the problem was.

Thanks for all the support and hard work!
[Nook Color Android Development] leapinlar:
Do not wipe system. The nightly will not install properly if you do.
[Nook Color Android Development] Android311:
I thought I had to wipe everything :p lol thanks for telling me :)
[Nook Color Android Development] bigbob23:
I have been wiping only the Dalvik cache and have not noticed any issues.
[Nook Color Android Development] thereddog:
These builds are really great, but is it possible to update through ROM manager?
[Nook Color Android Development] micl9:
no

but you can use the new goo app

Also gives you a direct link to the latest gapps.

Works great - I am now using it to keep both my Nook and TouchPads fed with a stable diet of CM9 nighlties. Thanks to Eyeballer, among others!:)

You can also donate to goo insideme (now Goo.im) and become a sponsor which allows you to set up an account which works on the website and the app.
[Nook Color Android Development] thereddog:
Thank you kind sir
[Nook Color Android Development] leapinlar:
There are no official CM9 builds yet so ROM Manager will not find anything. After you have downloaded these you can use ROM Manager to install them to emmc if you want.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] xdp:
Hm, just flashed 3/25 non-OpenGL thinking it wouldn't have the large keyboard issue and it also does. So all new builds have the problem? What are people doing, using alternate keyboards?
[Nook Color Android Development] leapinlar:
All have it. I use SlideIT which allows you to resize.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] b.roid:
so whats the process for upgrading a nightly? that would be good to add to the front page.

thanks :D
[Nook Color Android Development] leapinlar:
Just wipe dalvik cache and flash. Simple.

If you are flashing over stock, need to wipe data too.
[Nook Color Android Development] b.roid:
just upgraded to opengl 3/25 (thanks leapinlar) my wife is putting it to the test :D i was using a non gl version. my wife said it was sticking a lot.

i was wondering if everyone overclocks? does that make a big difference?

any tweaks for better performance anyone suggests?
[Nook Color Android Development] SeaFractor:
This is a matter of some debate. I had also posted a series of build.prop edits that I was certain had a positive impact. Many others did as well, but the irony is that many were placebo as the ICS code didn't actually execute those commands and infact ignored them.

Fattire drove that point home with his addition of "ro.magic.optimizer=ZOMG" to the build just to educated us all and also relieve some of his stress over our continuing persuit of Build.prop additions that were pointless.

As for overlock, most have and while it does help, opengl rendering appears to impact the smoothness of the GUI still. It has been suggested, but not fully verified that a lower overlocak of 1100MHz might actually be better than 1200Mhz at this point.

However, I've tried that and stil have "stickiness". As for opengl development, I suspect that it's likely on hold for a time. THe reason is that TI did release new drivers but it's for the 3.0 kernel and not the 2.3.9.xx used in the current NC CM9 nightlies. It's not clear if devs will attempt to back rev the drivers for our earlier kernel, or if development efforts to bring 3.0 kernel will be the final solution.

As in Dalingrin's thread, it's been shown that a development effort for the NT is underway and this might also be followed in parallel in the NC development environment. See Mateorod's post http://xdaforums.com/showpost.php?p=24039327&postcount=2118

Personally, my opinion (which is quite humble), I would suggest going with the Kernel 3.x route. Might make it much easier to port TI updates ongoing as they appear to be kernel modules were as 2.3.x might require that it be compiled into the kernel itself.
[Nook Color Android Development] vessamj:
Can someone direct me to the thread on what to use to change screen density? I saw it before and decided to give it a try but can't find it now... thanks in advance

NookColor ICS using xda premium
[Nook Color Android Development] leapinlar:
Put this line in build.prop (anywhere) in /system - qemu.sf.lcd_density=160 - just change the number to whatever you want and reboot. But be aware, any number higher than 160 will force the device into phone gui from tablet gui. And the phone gui on the nook color has no soft navigation keys.

I have a patch that fixes that if you want soft keys. Look here:

http://xdaforums.com/showthread.php?p=23727445
[Nook Color Android Development] DizzyDen:
You can also create local.prop in /data and place that line in it. It will survive updates that way.
[Nook Color Android Development] stewtang:
For some reason I'm no longer able to download any of the ics roms using direct links or gooinside app. I've tried restoring a previous nandroid ics backup, but still have the same problem. Any ideas? I ran into the problem after installing one of eyeballer's nightly but i have restored to samiam's and a previous eyeballer but no luck.
[Nook Color Android Development] friedsonjm:
Nightly version update?

I noticed no nightly at http://techerrata.com/browse/nightly_kangs/encore ?
[Nook Color Android Development] eyeballer:
Can't get anything past you guys =P

Not sure what happened with the builds.. I already pushed out a non-opengl. kevank is fixing the tweet bot right now so waiting on that before the opengl build. Should be up shortly.
[Nook Color Android Development] hnzL:
fruit ninja

i'm having issues running game fruit ninja, on every CM9 build i ever used it crashes... is the game working for anyone or is there any solution how to run it?
[Nook Color Android Development] bigbob23:
I'm downloading it now, update-cm-9.0.0-encore-20120327-1416-opengl-signed.zip
[Nook Color Android Development] friedsonjm:
Yep, its up and running! thanks. jf
[Nook Color Android Development] friedsonjm:
Too many ROMs...?

Eyeballer, would you consider a directory with only the 'current' daily download, or at least, archiving the 'older' ones and just leaving up the most recent few? Its starting to get a bit difficult to select the 'right' one from my Nook screen, just a matter of the way the screen lists all those files and reacts to the finger touch!

thanks, jf
[Nook Color Android Development] friedsonjm:
Ditto today.. or are we just going to see them posted at a 'new' time?

thanks, jf
[Nook Color Android Development] DigitalMD:
The nightly builds are all broken at the moment, once they fix the issues they will build again

Edit: Build just finished.................
[Nook Color Android Development] eyeballer:
This. The builds appeared to be broken at their usual build time. The final set of merges look good so builds are going up now :)
[Nook Color Android Development] jewnersey:
I'm using the latest 3\28 non-opengl build. 300\1250

Haven't seen anything monumental about performance. Thumb keyboard seems less laggy and YouTube videos seem to work with less hassle (once you toggle of HQ) but I haven't noticed anything else yet
[Nook Color Android Development] SeaFractor:
Appear to be for qcom based hardware like the Hp touchpad.

Several had not mentioned that in the git but are related to the qcom merges.
[Nook Color Android Development] HacDan:
So, you seem to be a bit confused.

There is nothing wrong with wiping system. At all. The only thing you will need to do, if you are using GAPPS, is to flash them again. None of the system settings are saved on /system, and in fact, /system is wiped every time you flash a CM zip.(even if it is a kang) There is a script that runs first, of course, that backs up your GAPPS, and restores after system is formatted, but there is nothing wrong with wiping it before hand.

Yes I emphasized it twice, because you did. =)

In regards to wiping /data, it isn't a bad thing. In fact, before reporting any bugs, you should be wiping everything(system/data/cache). Data is where system settings, along with many other files the system uses that it needs to read/write to during normal operation are stored.

So yes, you'll lose all of your installed apps and app data, but, you are testing ALPHA software. There are prices to pay when using ALPHA software.
[Nook Color Android Development] leapinlar:
The only thing wrong with wiping system first is with this new backup script it can get confused and abort, leaving the system still empty and the user stuck. So there is no advantage to wiping first, and one big disadvantage! I'm not confused at all.
[Nook Color Android Development] HacDan:
That's funny, considering you said here that wiping system is bad. Which is wrong. Considering those doing a fresh install from cm7 will need to wipe system. Also those coming from stock software will need to wipe system.

And to top it all off, the zip wipes system. So wiping system is good. So yes, you are confused.