yashsingh1/xdaforums huggingface dataset:
[Nook Color General] routey:
thanks. will try flashing the non open gl version. will I have problems playing YouTube and videos by using non open gl?
[Nook Color General] grayfoxmg1:
CHange your governor to high performance, if that doesn't help than nook tweaks will let you up your cpu above 1.2
[Nook Color General] leapinlar:
It will play youtube and with opera mobile even play flash.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color General] janko10:
Wondering if this Wifi issue was every resolved within the ICS builds. I also have the DIR-825 and the only way I could get my Nook to connect with one of eyeballers ICS builds is if I lower the encryption to TKIP instead of AES (b, g, n modes didn't matter).

I never had any problems connecting with CM7 with TKIP and AES active. I'd rather not lower encryption if I don't have to, TKIP is easily defeated. Thanks all for the good info.
[Nook Color General] routey:
thanks. will flash non open gl once I knock off work today..cheers!
[Nook Color General] routey:
tried that but it still lags.
[Nook Color General] routey:
tried flashing non-gl version but the lag is still there. probably cause i just did a wipe cache? now even youtube seems to lag for me
[Nook Color General] leapinlar:
You must have something running the background stealing your processor time. I would recommend backing up your apps with Titanium Backup, followed by wiping your data. Reinstall only angry birds and see if you have lag. If you don't, reinstall your other apps one at a time till you find out what it is.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color General] martyg7:
Good For Me: 20120606-opengl

For those of you looking for a good CM9 load to try out,

20120606-opengl looks like a good baseline

Everything in the last 2 weeks prior to that was unstable,

with freezes every couple hours of use

Works well for me

Your mileage may vary, of course
[Nook Color General] speedfreak007:
Thank god! I flashed CM7 yesterday because the latest cm9 build were slow and buggy. Also there was something wrong with the memory management i think. I'll try the version you mentioned!
[Nook Color General] giedrys:
Just installed CM9 on SD for the 1st time using this "guide":

http://blog.benlk.com/2012/03/28/installing-cm9-on-a-microsd-card-updated/

Things seem to work except there is no google play.

Can someone advise how to enable it or point me towards better CM9 SD install etc.

I'm no geek, I've tried search, so even if this topic was discussed before please curb your burning desire to call me noob.

TIA.
[Nook Color General] boomn:
It's somewhat mentioned in step 10 in that guide. Download the latest CM9 GApps zip from this site, rename as noted in step 10, drop the file onto the SD card like you did for the ROM, and let it flash this update like it flashed the ROM
[Nook Color General] koopakid08:
You need to install gapps

Edit:

Looks like I was beat

Sent from my HTC Evo V 4G
[Nook Color General] giedrys:
Done and done. Thank you both.
[Nook Color General] nolook:
how well does this work as a daily driver?
[Nook Color General] meteorrock:
You can find the google play aka playstore by downloading the .gapps file for CM9 on cyanogenmods Wiki.
[Nook Color General] Art2Fly:
Sorry for the noob post, but what is the best way to install CM9? Or in other words, what is the best version to install and what settings will let it run the smoothest? I'm new to the nook.
[Nook Color General] mikelav456:
I used this method to flash Sam's ROM for weeks now. I then tried it with eyeballwe'd ROM and it did not work. Is there a reason for that? are there different instructions for installing his ROM on a Sd?
[Nook Color General] leapinlar:
Yes, his now follow the new CM naming standard which starts with cm- instead of update-. You either need to start renaming them to update- at the beginning or upgrade to my new script file for your boot partition. If you go to my tips thread linked in my signature, you will find information there about it.
[Nook Color General] mikelav456:
Thanks but I tried that and still ran into a problem. Not sure what I'm doing wrong.
[Nook Color General] leapinlar:
Describe your procedure and say what is happening (or not happening). Does it try to install and fails, or installs but does not boot? Tell us more. Is the file still on the boot partition after booting?
[Nook Color General] mikelav456:
At work but what I remember I'd that it boots into the Linux code thing and tries to install ROM but claims it can't find anything and that I should be sure the file name behind with"updatei-" (the "i" was not a typo on my part).
[Nook Color General] leapinlar:
That is wrong in the script. It should be update- at the beginning. I noticed that error too. I will correct it next time the script needs updating.
[Nook Color General] mikelav456:
Sorry but what us the practical implication of that for me? Is the Sd card image bad? Is the nightly bad? is it just saying the wrong thing?
[Nook Color General] leapinlar:
Just saying the wrong thing. It had a typo in the text that said the zip should be named updatei-. That is wrong it should be update-. I have fixed that and one other error and reposted a rev 3 version. Go to my tips thread linked in my signature and there is a section (B2) that explains it. You should update to the rev 3 files and you will no longer have to rename. Your version will still work, but the new version is better.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color General] mikelav456:
Great thanks. Hopefully I'll have some time after work to try it out and I'll report back. Really appreciate the help.
[Nook Color General] mikelav456:
Btw, rev 3 worked out for me. Thanks for all your help!
[Nook Color General] martyg7:
Works for me: 20120618

Switched to the non-opengl loads a few days ago.

Much faster with less lag. Only 1 lockup in the past 3 days of heavy use.

About as fast as I could ever expect from a single core CPU w/o 2D acceleration.

Now on 20120618. Works for me.

---------- Post added at 01:10 PM ---------- Previous post was at 12:49 PM ----------

Would be nice of these loads were build with the dropbear SSH server.

All the CM7 loads I have used had this already baked in.
[Nook Color General] leapinlar:
If it is not already there, I doubt you are going to see it soon. The CM devs have 'frozen' the changes allowed now getting ready for releasing an RC. The only changes they are allowing are device specific additions, bug fixes and translations. That mod does not fit into any of those categories.
[Nook Color General] eyeballer:
Not exactly. The way CM releases work is that they branch from the mainline code, into a release branch (in this case "ics-release"). This forms the codebase for the CM 9.0 RC0 release and eventually CM9.0 final. This branch is feature frozen and only bugfixes are pulled in from the mainline code (branch = "ics") into the release tree.

New features and other code changes go in as usual to the mainline codebase ("ics"). Our nightlies are compiled from the main codebase so the feature freeze for CM9.0 RC doesn't affect us at all.
[Nook Color General] leapinlar:
I stand corrected. Thanks.
[Nook Color General] martyg7:
CIFS Module

It would also be nice if the CIFS module was made part of these kernel builds.

(I don't see it in the eyeballer images)

This is the preferred way to locally mount filesystems on other hosts.

Thanks to the developers/integrators for all their hard work.
[Nook Color General] leapinlar:
I'm not certain, but I think keyodi said in an earlier post that CIFS was already built into the kernel. Search his posts.

EDIT: It was fattire. See here.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color General] martyg7:
CIFS Module

You are right.

I innocently thought it was built as a module, but failed to check if it was compiled in.

# ls /proc/fs
cifs
ext4
jbd2
nfsd
# lsmod
tiwlan_drv 770791 0 - Live 0xbf000000

Still plugging away to get CifsManager to work on this load.

No issues on my CM7 phone. Trying to understand the difference.
[Nook Color General] RASTAVIPER:
If you just want to test drive it first, I would recommend read and try some of the SD installations guides for the CM9.

In this case you could switch anytime to your normal system.
[Nook Color General] martyg7:
DolphinHD

Still using CM9 non-opengl as my daily driver, in use several hours a day.

These load are getting better and better, speed and stability wise.

Probably the best improvement I have made to my user experience during the last couple of days was to dump DolphinHD and go back to the stock browser. I am finding the stock CM9 browser to be much more responsive and reliable.

Tracking the daily updates. Running 20120623 and it's a keeper.
[Nook Color General] pastordl:
Cm9 rc1 is out

http://forum.cyanogenmod.com/forum-224/announcement-24-cyanogenmod-90-rc1-released-2012-jun-26/

Took a while but worth the wait
[Nook Color General] leapinlar:
Good news.
[Nook Color General] ryuz4ki:
Hopefully our Nooks will get a version soon.
[Nook Color General] therkr:
How's could they make an RC when we haven't even got those gpu drivers? (Or am I really outdated on the nook scene?)
[Nook Color General] eyeballer:
Nook Color is NOT in RC stage for CM9. It's not even an official device.
[Nook Color General] leapinlar:
Does that mean one can't be built for it? No way to change my build configuration so that one builds?
[Nook Color General] eyeballer:
Well if you really want to, you can git checkout "ics-release" in each CM repo and then build, but you're basically using mainline CM code from 2 weeks ago with a few fixes that may or may not even work for our device and are already included in the nightlies. There's literally no point in doing that.

Stable releases (RCs/Finals etc) are really targeted for devices that are really almost 100% stable and for people who aren't comfortable with nightlies.

As fattire always states NookColor CM9 as a whole is alpha.. so how can you build an RC?
[Nook Color General] leapinlar:
I agree with all that. But there are those that don't trust nightlies and think there is something magic about RCs that makes them more stable. You saw how some were celebrating over it.

There was a user a few days back that was trying to get someone to somehow make a more stable version because frequent nightlies were more than he could handle. I explained to him that RCs were just basically a one time snapshot of a nightly slightly modified. But that is what he wanted. Something that was not going to change frequently.

That was the reason I was asking. Some want these.

I personally like your nightlies and update every day.
[Nook Color General] eyeballer:
To put it simply to them: Release Candidate signifies a stable build almost ready to be called "Final." Our device as a whole is still "Alpha" so you simply can't have an RC for a device that's still in Alpha stages of development - it doesn't matter if the mainline CM code is stable or RC stage, it all depends on our device tree.

I'm not sure how else to explain it to people that don't understand this. :confused:
[Nook Color General] Morphling27:
I wouldn't worry about explaining it too much.
[Nook Color General] therkr:
Well, I got a lot of my answers...

On a side note, is there still hope that we'll ever get h/w acceleration?

(Seeing that 3.0 kernel is being worked on, I assume so but still confirming)
[Nook Color General] pastordl:
Mea cupla

I didn't check it all out. In the cyanogen, nook color forum, experimental the first item on the list is "CyanogenMod 9.0 RC1 Released! (2012-Jun-26)

Posted by ciwrl" http://forum.cyanogenmod.com/forum/224-nook-color-experimental-mod/ (Was deleted after this posting)

Read the post but didn't follow through.

I had today off and planned on installing CM9 on my Nook Color. When I chased down the Zip file was surprised (and disappointed). Did set up the latest "unofficial nightly" CM9 on SD like it but will wait till the "real" RC1 before put it on EMMC.

:cyclops:

Sorry for the confusion I helped perpetuate.
[Nook Color General] koopakid08:
Updated title for cm10. Seems a bit long now but oh well. Exciting stuff happening.

Sent from my HTC Evo V 4G
[Nook Color General] Morphling27:
It's awesome that we're already on cm10. At least jelly bean rolls off the tongue easier than ice cream sandwich. It's easier to type too.
[Nook Color General] crono141:
Are the nightly links in the OP JB or ICS still?
[Nook Color General] wmuflyer:
Still ICS, I'd expect the file name to be changed to CM10 when they go to JB.
[Nook Color General] fattymcdirty:
and do the nightlies already inclide the wifi, hd, sound fixes from 3.0 development?

Gesendet von meinem GT-I9100 mit Tapatalk 2
[Nook Color General] cybertimber2007:
I believe the CM9 builds are still based on the 2.6.32 kernel. I would think that they have branched both the 2.6.32 and 3.0 kernels for JB, as any fixes made to the kernel for jelly bean may abrubtly break ICS.

eg:

2.6.32-ICS

2.6.32-JB

3.x-ICS

3.x-JB

I'm guessing here though. Eyeballer & Sam may have changed their build systems, but you would have to refer to their thread for that info.
[Nook Color General] eyeballer:
As of right now, nothing has been back-ported to ics (and it probably won't be). CM9 still has fixes going in where needed (both in the mainline code and also in our tree - https://github.com/fat-tire/android_device_bn_encore/tree/ics )

My builds will stay on CM9 for a little while until things smooth out with CM10. Of course just like with CM9, all the code is open for CM10 and building your own is encouraged - especially if you can help fix stuff. :)
[Nook Color General] fattymcdirty:
thats too bad... i'd really like to try out that new branch woth the 3.0 kernel and fixes but apperently i'm not able to get myself a build environment right now :( any1 here willing to build that one and upload a flashable zip for testing purposes for those of us who are willing to?

Gesendet von meinem GT-I9100 mit Tapatalk 2
[Nook Color General] fattymcdirty:
or is there any "howto" for building the cm10 branch with the included fixes? i could install ubuntu on my machine for building.. all i need would be a tutorial on a) how to set up a build environment and b) how to build that cm10 branch PROPERLY ;) any1?
[Nook Color General] eyeballer:
I'm not sure if that would achieve anything. The 3.0 kernel is now built for jellybean.

Well there's currently a cm9 build guide still in the dev thread. If you read it over you can probably figure out how to set up the environment for cm10, and then if you read the last few pages of the dev thread everything you need is posted there.
[Nook Color General] elwappo99:
nvm, got it.

Anyone else getting netflix to work, or is the update not yet implemented?
[Nook Color General] leapinlar:
Netflix still does not work.
[Nook Color General] luigi90210:
any chance the new module that the defy team has discovered for the .32 kernel will be implemented into your nightlies?

i would build cm9 and the kernel myself but i dont have an adequate building environment anymore(i only have my 1ghz acer w500 windows tab with a 32gb ssd and 2gb of ram)
[Nook Color General] Midnitte:
Any particular reason why? I thought the reason was tied to why youtube HQ videos didn't work.
[Nook Color General] leapinlar:
It is tied to why YouTube HD (not HQ, they work) videos don't work. Lack of hardware video acceleration and flash.
[Nook Color General] elwappo99:
There's hope!

http://xdaforums.com/showpost.php?p=28931874&postcount=2484

I don't think it's been implemented yet is all
[Nook Color General] leapinlar:
That is for jellybean with 3.0 kernel. A ways off yet. It is easy to get confused. Almost all of the work you are reading about now in that thread is for a jellybean build for our color, so don't get too excited about it applying to ics. But there is hope that it might translate to ics later.
[Nook Color General] elwappo99:
Dream killer.....

Sorry, in case you couldn't tell I'm a little new and there's a lot going on :/
[Nook Color General] RASTAVIPER:
HQ dont work at UT no matter which ICS rom I have tried.
[Nook Color General] leapinlar:
HQ will work on ics if you switch to the phone GUI. Or if you use ParanoidAndroid and set the YouTube app to phone GUI. Or use an old version of YouTube that does not try to run HD.
[Nook Color General] jewnersey:
Any flashable builds available? Wanna see JB on this piece before I buy the N7
[Nook Color General] leapinlar:
No, not yet, too buggy still.
[Nook Color General] brian717:
Here I am back in general asking dev-related questions because I didn't go and spam development threads to get up to 10 posts...

Anyway, if any devs happen to come into this thread. I started from scratch with a new android/system directory and a fresh repo init and sync to the jellybean branch, using the local_manifest posted in the dev thread. There was one oddity with the init / sync: despite running it in android/system, it placed the .repo folder in the android (parent) directory, along with all the other directories that usually live in android/system (build, vendor, device, for example). Strange, but everything built fine after that, so I didn't think it was an issue.

Now, after installing CM10, I got as far as "android upgrading" dialog after boot, and it hung there. After wiping all data, it actually hung even sooner - at the boot animation.

Just wondering if anyone else has had this issue, and if so, what they did to fix it. Also, have the directories been restructured in the repository, or did I do something wrong?

Thanks!

---------- Post added at 07:34 PM ---------- Previous post was at 07:05 PM ----------

Didn't realize I could pull a logcat during the boot animation. Useful, and attached. Again, if any devs stumble upon this, I'm just wondering if anyone's run into this particular issue. A logcat just reveals the log I attached, repeating over and over again. Looks like possibly an issue with the audio and mediaserver. My proprietary files were pulled from a working build of cm9 that I had on the nook. Guess I'll look into this later tonight / tomorrow if no one has any advice on how to fix it.
[Nook Color General] krylon360:
haven't looked at the logcat yet. But seeing that it syncd to android and not android/system, you probably ran init from android by mistake. Since a system dir was there it most likely didn't sync that dir and errord. Delete system and resync.

There still might be a few things we need to touch up on in the extract and setup files. You can push the 2 pre built audio files in device/bn/encore/prebuilt/alsa to get past the audio error.
[Nook Color General] pdanders:
I have a nook color and a Nexus 7 (and a Transformer prime for that matter).

Get the Nexus 7... it's awesome and a really great value for the price. It's faster than my transformer prime which cost almost 3x as much

I bought a nexus 7 to replace my nook color and the difference is night and day.... and I'm not a nook color hater by any means, but it's pretty slow compared to more recent devices (and esp something like the Nexus 7)
[Nook Color General] luigi90210:
seeing as its a 2 year old 800mhz cpu with 512 mb of ram i expect it to be slow and not fast like newer stuff, and if the newer stuff was slower than the older stuff than we would be getting ripped off by companies who make the newer products

as far as people purchasing something new, some people dont have the money to purchase a nexus 7, and others dont want to purchase one(like myself im sticking to windows 8) and we just want to work with what we got(or mess around for that matter)

and if you want to brag about how much faster your nexus 7 is compared to a nook color than make a new thread about it, please dont derail this one because some people want to use this thread for information and asking questions about the new builds and not want to read how much you are enjoying your new tablet
[Nook Color General] steven676:
Hmm. Can you rebuild with BOARD_USES_AUDIO_LEGACY := false (or comment that line out) in device/bn/encore/BoardConfig.mk? I believe that's the correct setting given the current state of our audio stack (so BoardConfig.mk is wrong).
[Nook Color General] fattire:
I'm doing it now and assuming my nook charges enough to boot I'll letcha know.

Update: I had the same sort of issue even after turning legacy off. However, when I rm'd /system/lib/hw/audio_policy.default.so the boot continued. We'll have to look at this tomorrow and see what's up, unless someone else what's to do some investigating.
[Nook Color General] brian717:
Your fix also worked for me. I'm glad to see that smarter people than me are having this issue, though. Makes it more likely to actually get fixed soon. I'll still look into it myself, but I'm predicting you'll figure it out before I do. Thanks everyone for taking the time to respond.
[Nook Color General] koopakid08:
Added link to build instructions for cm10 in op. Remember don't post your kangs.

Sent from my HTC Evo V 4G
[Nook Color General] eyeballer:
This. Please don't post builds yet. The last thing we need is flooding the forum with "xyz doesn't work" or "jellybean killed my cat" - we already know a lot of it doesn't work :)

Wifi and audio are still very unstable. Please build and help fix stuff though :good:
[Nook Color General] svip:
Is there any way to trigger screen recalibration under the current JB kernel? /sys/bus/i2c/devices/2-0022/forcecal no longer exists

edit: The answer appears to be that the code for that isn't in the new cyttsp driver and needs to be ported.
[Nook Color General] jamesjhare:
Building from source

I just got my build environment setup and built from code synced about an hour ago. I get nothing but a black screen. Looking through the comments in the dev thread I can see several suggestions to work around commits that don't work -- are these still necessary to get a build that boots? How long should I wait for a first boot before booting back to recovery and trying to pull a log?
[Nook Color General] eyeballer:
Nothing extra should be needed at this point for a working build other than a sync and build.. unless something else merged into CM that broke. I have a working build from this morning. Try to get a log and I'll look at the CM code and do a test build.

Edit: Just sync'd and built and boots just fine (~7.15pm EST).
[Nook Color General] sakisa950:
is there another wway we can help test i cant build right now main pc is dwn
[Nook Color General] DizzyDen:
Unfortunately, right now, if you can't build... you won't be able to test... there are very good reasons for fattire not wanting any builds to be released at this point... it is far too fast of a moving target... just as CM9 was in its embrio stages.
[Nook Color General] wpbear:
I have been running CM 7.2 forever but got bored and just tried CM9 both with and without openGL. OpenGL was very laggy!!! Non-OpenGL was ok but the "stock" Launcher was so laggy. I put ADWLauncher on it and it is usable.

An interesting thing is HuluPlus plays great and as previously stated of course Netflix does not.
[Nook Color General] wicozani:
07-24 non-openGL working good in dualboot from SD!

Just a quick note to give thanks to everyone providing these nightlies, and to report that I was able to use Rack's script tool to prepare and install the 07/24 non-openGL build on his dualboot from SD setup! The install went excellent, and the build is working very well for 12 hours now, without any freezes or lockups. The stock Trebuchet launcher is very slow, but I'm trying the new Nemus launcher and it is very minimal and fast, with a unique dock setup. I need to dial-in spacing and sizing, but this new launcher looks like it has some future. YouTube is working, though not in HQ, and Netflix freezes when loading video. Thanks again to everyone involved!

I might note that I tried twice unsuccessfully to boot the Krylon AOKP build 40 ROM using the Racks script tool - on both occasions it simply went black screen at boot.
[Nook Color General] Hephaestus_:
If you want to see it, compile it from source yourself. ;P