yashsingh1/xdaforums huggingface dataset:
[Nook Color General] Hephaestus_:
Yeah, that reminds me. Why is the stock trebuchet launcher so laggy? Even with 100mb of free ram and oc'ed to 1.4ghz (not recommended) it will still lag. I haven't had the time, but once I do, I'll compile ics and see if it still lags with the default launcher. ;P
[Nook Color General] skwalas:
Oc'ing to 1400 will definitely kill performance. It's been frequently observed that oc'ing past 1100 tends to cause performance to degrade rapidly , which some people think is counterintuitive and don't want to believe. Try dialing back to 1100 and see if that doesn't help. As I recall, this effect was found even more pronounced in cm9 than in cm7.
[Nook Color General] Hephaestus_:
I usually run high intensity games at 1.325ghz and they perform alot better than at 1.1ghz Also, my default clock speed is at 1.2ghz. It might depend on your processor, but anyways, it will still lag at 1.1 ghz, or at any reasonable clock speed for that matter, ADW Launcher Ex does not.
[Nook Color General] Hephaestus_:
So does thst mean that haze_nme's fixes for the new touchpad have been merged with keyodi's repo?

Thanks.
[Nook Color General] krylon360:
that post was made on Monday night. The patch was made last night. It has not been merged yet.
[Nook Color General] Kurlon:
Got a clean build out of andbot last night, fired it up on a clean sdcard and... wifi enables but doesn't see any networks.

Actually - I think it just crashed, screen powered off for sleep, had to hold power down to get it to boot.
[Nook Color General] krylon360:
Wipe davlik and then get wake lock from the market
[Nook Color General] mrfeh:
stability of nightlies?

Hi folks.

I tried the CM9 nightly about 4 weeks ago. After a couple days, I gave up because it was simply too unstable. Frequent crashes/hangs. I moved to AOKP ICS, which has been fairly functional.

At some point, I'd like to go back to CM9. What is the current status? Are things better than they were a month ago?

Thanks.
[Nook Color General] leapinlar:
The non-opengl has been stable for me.
[Nook Color General] mrfeh:
Has stability increased recently, or did you find non-opengl to be stable in June also?
[Nook Color General] leapinlar:
Non-opengl has always been stable for me.
[Nook Color General] krylon360:
You are responding to an answer that was posted 3 days before the fix was even pushed.....you know that right?

Either way, keyodi pushed the fix today.
[Nook Color General] Morphling27:
I would agree with this. Back in either late April or early May, I switched to non-opengl and it's been pretty stable for me. The only total freezes I've experienced since then were having many tabs open in browser. Otherwise it chugs along.
[Nook Color General] bowguy:
CM10 builds

Did a build today with all the latest updates. The directions by fattire can be followed directly including those of you with the new touchscreens. Installed it including Google Apps. Very nice. The bugs are getting squashed thanks to all the hard work by the Dev guys. If you want it - build it. Lots of directions on the dev thread.

It also works great on the SD card for dual booting. Keep your existing setup and test on a cheap SD (but ScanDisk) card. See Leapinlar's tips.
[Nook Color General] topcaser:
Hi,

I used NC during gingerbread times already. I had no problems with WIFI on GB.

Now, when I install ICS on NC, the WLAN won't turn on any more when the screen was off for some time. I know there is an option to switch on WIFI all the time even during screen off. But this is not what I want to have, since with WIFI on all the time NC eats up battery. I do not use NC on a regular basis and when I forget to sitch it off manually it ends up with an empty battery :(
[Nook Color General] leapinlar:
I had the same problem. I usually leave it on all the time since I need the background notifications. But I have tried that setting occasionally and it won't turn back on. I usually have to manually turn off and back on to get it on. If you are not going to have it on all the time, I find it best to just turn it off manually.
[Nook Color General] topcaser:
Hi leapinlar,

thats not an option to me since I want to give NC to my father. And I cant expect it of him to deactivate it manually. Propably I will turn back to GB. Nevertheless, I am wondering why this issue is not fixed (coming from the very first nightly).
[Nook Color General] meteorrock:
How are you guys pulling your builds off of the github? Just pull the JB branch, or <fattires> ICS 3.0 branch instead of pulling the whole linux nook color branch. The wi-fi driver I exploited from TI is just 3 months old. That means you will have to go in and use git to "cherry pick" just the JB branch instead of pulling up the whole tree. Don't start laying down JB builds up in here with old code for the nook color. Check over the forks with a git GUI. This means you need to stop pulling the code for that old wifi driver that was merged into the JB branch. Use the cherry pick function and clean up the wifi commits.

You can do the same for the ICS builds. Just cherry pick and pull out the kernel modules from the GB and earlier ICS branches and use the kernel modules from ICS 3.0. Then recompile.

I think some of you guys need to go over on how the github works. I started a link down here for those that do not know how. You are reaching in and pulling up old code from the other forks in there. That is why you are getting those wifi problems. Check this thread over in the cyanogenMod forums here. http://forum.cyanogenmod.com/topic/50994-follow-along-with-me-trying-to-learn-how-to-code/
[Nook Color General] eyeballer:
meteorrock, I'm not sure what you mean. See fattire's build guide here to make sure you get all the right repos: http://xdaforums.com/showthread.php?p=29075653#post29075653
[Nook Color General] meteorrock:
Its ok eyeballer. I just have a hard time explaining myself on what I mean. Doesn't the code run like water up and down the branches with its code? Maybe not. I thought the code was pushed upstream and flows like water into the whole nook color linux branch. I might be wrong on that. Or does git have a way to stop the whole linux branch with its code from merging in from earlier builds? Or does forks keep that code down in the other branch?

For example when I pull the nook color linux branch and review it on my git GUI it shows the whole branches , the GB branches from last year that forked into ICS then one last fork for JB or ICS 3.0. Does git know how to correct itself from older code that could have become corrupted in the gingerbread branch from merging in with the JB build branches?
[Nook Color General] topcaser:
Meteorrock, I have no clue what you are talking about. The only thing I might understand is that the nightlies may grab an old Wifi driver which causes the problems and if it would grab the newest driver the problem would be fixed? That would be good news...

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Nook Color General] meteorrock:
Yeah I am trying to get my head around on how the git and github works. I want to try to see if I can somehow submit a build for us. I have been researching quite a bit on how the github works. I think I might be out of everyones league and need to find some unix wizard to help me better understand how it works.

From what I have learned so far, and I might be incorrect on this as I , myself am having a hard time trying to grasp this CVS git thing, is that the code flows like water inside of a branched network. So old code that might have got corrupted in some linux branch from last year or even a few years ago can work its way up and infect the whole linux kernel branches.

Kind of like cancer. I lurk on some developers forums and hear of them talking about how cancer infects some linux kernel branches and they , the developers have to go in and perform a type of cure for it by cutting out bad, or corrupted code to correct this situation. Let me research this a bit more on some other forums and see if I can get a better grasp on this for us.
[Nook Color General] eyeballer:
We'd prefer people don't post cm10 builds just yet.. Just build for yourself to test it out, it's not quite ready for public consumption.
[Nook Color General] meteorrock:
AWESOME! So you do know how git works. I am impressed. Just make sure its fixed for us ok? You will need to purge that old wifi module out of your main line. Thanks for all of your help btw.
[Nook Color General] velizet:
At that stage of things, are there any changes in the ICS nightlies, or is everybody going after JB? If that is the case, maybe we should not bother about installing the nightlies ICS at all.
[Nook Color General] meteorrock:
Any work submitted on the github can be used through all of the branches, if I understand how the github works. So work being done even on Jelly Bean, that code will help improve all of the builds, even for the ICS nightlies being built. I guess its what they call backporting.

I think the other developers are just waiting on the buildbots to help improve and clean up the bugs on the kernel development they just got done doing for Jelly bean, doing it by hand and going through all of that code is very time consuming.

I was kind of hoping someone wanted to give me tips on how the github and the git works so I can also move up in development, but it seems I am stuck at a glass ceiling in development right now. Part of it is needing for myself to do a bit more research.

Anyway I have spammed enough for one day here.

/thread
[Nook Color General] fattymcdirty:
is there any chance that some of you guys, who actually have a recent working JB build by themselves, upload it and post me a link as PN for the download? i won't publish it anywhere... i just want it to test of my GF's nook to see, if we should keep that device, when the chance of having a 7inch tab running JB is good or not... and we want to compare it to cm9's "performance" ... otherwise we would sell that tab and buy a device with a little more performance... would be GREAT if someone could provide a link for a flashable for testing in PM.
[Nook Color General] velizet:
My understanding is that, if you use JB on NC, you will find it unacceptable.

Devs keep saying that CM10 for NC is not even in alpha state. Even CM9 is still unofficial, and did not reach the beta yet.
[Nook Color General] topcaser:
eyeballer,

meteorrock tries to find a way, to include the newest Wifi driver in any ROM independent of ICS or JB.

In his opinion the Wifi driver in the current build is an old one due to structure of that version management.

We hope that you can include the most recent working Wifi driver so that we can get rid of this "WIFI does not connect after screen was disabled" problem.

(PS: Meteorrock, please correct me if Iam wrong)
[Nook Color General] meteorrock:
Topcaster, I am a girl. And I am still trying to learn how the github works. From my understanding only a few people here know how the github works and there is a process to go through with the developers. I am kind of sorry I even brought it up now. I have spent over 100 hours plus getting a handle on it and I barely know how. My suggestion may be well off on the process on it and was only offered as a suggestion, in hopes that someone would want to help us along that might be possibly lurking this thread at the time.

Like what the developers said, we are lacking people up here with the correct knowledge to properly maintain the Central repository code for the nook color and we need others to start wanting to learn how to build their own nook color builds from scratch and want to take a look over the github code and maintain it. As far as I know only one person knows how and that is <fat tire>. If you know of anyone with the skills to help us please bring them here.

You can learn some of what I have figured out from the link I posted earlier down in cyanogenMod. Knowing how to code and build kernels is the easy part of development, knowing how to maintain that code on the github can become downright brutal. They will not answer you because , frankly, if you do not want to help contribute and only ask for solutions that no one here really knows the answer to, then development for our nook color will come to a halt and we don't want to see that.

That is one reason why that problem has not been fixed. Some people in kernel development will spend their whole careers with degrees in computer science and/or engineering and never get a handle on maintaining their code on the git. Linus Torvalds goes over this subject on his speeches on youtube that I have watched on this subject.

```````````````````````

I know <fat tire> has been offering to help people learn how to get a handle on using the git and the github, for those that show promise in development. So please learn how to build. This will be my last reply to this subject myself, and I feel the other developers should not reply either.

~~~~~~~~~~~~~~

BTW my JB build on my nook color is soooo smooth and no problems here with wifi. Just no OpenGl. I wanted to share but eyeballer said not yet. Not until you guys get ICS up and going right. Feels almost like an RC :D
[Nook Color General] Morphling27:
Go read the development forum. Also, if you need an up to date tablet that has good performance, go get the Nexus 7, it's only $200 with a $25 Play Store credit which should cover your tax or shipping.
[Nook Color General] jdpdata:
The quickest way to try to build your own JB is inportb's Anbot method.

You can download and find instructions here:

https://github.com/jyio/andbot

Even a noob like me was able to roll my own JB build in no time.

But be warned, it's very early alpha stage right now. Very buggy.

WiFi is wonky (solved with partial wake lock).

JB does feel alot smoother than ICS for me.
[Nook Color General] paleh0rse:
Quick question: does the Plex app work on any of the current CM9 builds? If so, which one?

I'm trying to set up my trusty old NC as a kid's tablet, but I'll have to stick with CM7.2 if I can't get Plex to work on CM9.

Thanks ahead of time! :)
[Nook Color General] csrabear:
Had this method been available when I started building I might have been tempted to use it. But I have been building CM9 for a while using <fat-tire>'s guide. It has been a great learning experience, especially since I never used linux before. I've learned a lot and actually like using terminal to get things done.
[Nook Color General] bullfrog527:
Hi all, my wife and father in law have enough having some battery issues with their nook colors. I have installed CM9 on emmc on one and running off of the sd card on the other. The battery seems to be jumping around a lot when plugging in/unplugging, going from 5 to 25% and vice versa. Her version is from 7-14, going to update today with eyeballer non Open Government and see if that helps.

Sent from my wife's CM9 nOOK color
[Nook Color General] leapinlar:
Are they using the stock chargers and cables?
[Nook Color General] bullfrog527:
Yea, i did get a replacement one from amazon but this was still happening when using the stock charger

sent from my MoPhoKing CMX MoPho
[Nook Color General] leapinlar:
By stock, I meant B&N equipment regardless where you bought it. I was having those problems when using a standard microUSB cable. It did not clear up for me until I wiped battery stats with CWM and reverted to stock. There are those that say wiping battery stats does nothing useful, but my experience is different than that. In any case, it hurts nothing to try it and it just might make a difference.
[Nook Color General] bullfrog527:
I wiped caches, fixed permissions, and as soon as it charges fully i an going to wipe battery stats and for a clean install of eyeballers latest. See if that helps. I got the replacement charger cable cause her stock one has some frayed wires sticking out, I think I'll have to go get an oem one tomorrow.

sent from my MoPhoKing Paranoid JB MoPho
[Nook Color General] bullfrog527:
I am still having crazy battery drop while the screen is off. I'm using the old charger cable with the frayed wires, gotta go get a new one. No need have any ideas?

Sent from my wife's CM9 nOOK color
[Nook Color General] leapinlar:
From what I can see, the dropping is because something is running. I thought you were talking about straight vertical drops like your battery was suddenly giving you different values. Those are steep, but something is constantly using it. Get the BetterBatteryStats app here on XDA. (It is free here, but costs on the play store). That will track what is called 'wakelocks' that keep the nook awake. It is usually some app using wifi. That will give you some idea what is going on.
[Nook Color General] dstarke:
Discouragement

Hi Guys -

I want to start out by acknowledging that I realize that no one owes me anything. I bought a Nook because I thought it would be fun to see just what could be done with Android on a somewhat different device. No one held a gun to my head and I may have misconstrued what the goals of this community were. I own my own disappointment and am not blaming anyone else.

I was amazed by the Gingerbread ROMs that were initially available, and it seemd to me that in no time we would have updated (read Honeycomb, ICS, and JB) Roms that would continue to amaze

I did not think that Honeycomb should have been abandoned when ICS was still a glimmer in the eyes of its developer parents, and I do not think that ICS should be abandoned either now. I am totally confused by the lack of progress in bringing these later ROM to the state where GB was a year ago. The only thing I can think of is that Android is so much of a moving target that no one can spend the time necessary and that the changes to Android in moving from GB to ICS to JB have actually made it harder to adapt the OS to the hardware bits of the Nook Color. This, if true, is a major disappointment in the development of Android.

In my mind, the philosophy of open source software is to make adaption and adoption easier, not harder; and to celebrate those developers who try to do so, rather than keeping them in the dark and withholding necessary information and code from them.

My initial reaction, when faced with such disappointment was to set up a Linux box (I chose Knoppix poor man's install for personal reasons) and to download andbot and the sources. I have gotten through the initial glitches and believe I have the full set of sources, the open and proprietary ones. Now it seems that the java runtime available in Knoppix is not appropriate (1.6.0 vs SE 1.6.0). I am running down the errors in the building in brunch to see if I can get around the problems. Java SE when downloaded from Debian and reinstalled, says that I already have the proper version.

I am willing to spend some time at this to get it working, but my dream of a more stable ICS or JB seems to be receding into the mists.

Of all the ROMs I have tried (and I've tried most of them) I think that (believe it or not) Honeycomb gave the best balance of tablet loveliness and usability. So I'm afraid I am currently asea.

I guess I will buy a Nexus 7 so that my wife doesn't have to keep asking me why my tablet doesn't work. It just seems like admitting defeat.

Thanks to all who have spent countless hours and who are probably just as frustrated as I am. Sorry for the rant.
[Nook Color General] eyeballer:
I think your first line mostly summed it up, but heck I'll take a couple of minutes to respond.. responses are inline in bold.
[Nook Color General] jh1521:
Issue with installing the 8/15/12 CM9 nightly and gapps-20120429

Been running CM7.2 for a while on my NC (and 7.0 since last year) so I thought I'd give the current CM9 build a go.

Used the size-agnostic image by verygreen from here (used version 3 for ICS) and the cm-9-encore-20120815-0800-opengl-unofficial.zip from the Techerrata server. The install went fine. Then I installed gapps-ics-20120429-signed.zip from the same server - the installation in recovery seemed to work fine without any errors, and powered down as expected.

I powered the nook back again, booted into CM9 and went to setup the play store. After I entered my username and password, the store froze for about 2 minutes (yes, wireless was already connected), then the store opened to the main page for a second or two, then the nook rebooted.

Since then it has been at the animted boot screen. The animation runs for 2-3 seconds at a time then freezes for about a minute, runs again a few seconds and freezes etc.

It's been like this for over 1h now, and the battery will probably run out soon. I plugged it in after about 20min (it was 97% full whan I started) but I doubt it's charging in this state. That wouldn't be a problem otherwise since I have the CM7.2 card untouched to boot back to something useful (used a brand new card for the CM9 install), but from my previous experience the patience needed to restart a NC with the battery completely drained is enough to drive a guy criminally insane :)

Is this behavior normal or not? I can't post in dev threads (old user, but with low post count) so I posted here instead.
[Nook Color General] grayfoxmg1:
Noo that doesn't sound like it is acting like it should. Now I don't run mine off of a Verygreen SD card (Mine's installed to EMMC) so I can't help you there, but when I upgraded from CM7 to CM9 back in February (God have we been working on this that long!?) it went right through with no problems *cough*Wifi SOD *cough*. I would recommend you re download your ROM, because you might have a bad DL and start your CM9 SD from scratch. If you still have issues, come back and tell us exactly what you did from start to finish (file names and links if possible) and one of the Andriod Guru's here will help.
[Nook Color General] jh1521:
Well about 10 min after I posted the battery died as expected, I took the SD out and booted to stock, let it charge for a while then turned it off, put the CM9 SD back in and booted. This time it finished booting fine, and the store works as expected..

Filenames and locations are in my previous post.

Too bad Netflix doesn't work. It loads and almost starts playing, but the video never gets rendered. That's a showstopper for me, one of my main uses for a tablet is watching Netflix. Flash doesn't work either.
[Nook Color General] Homuradama:
Question

Hey guys, I have a question. Since Krylon360 stopped his AOKP for Nook Color project, and eyeballer is still making his nightlies for CM9, I am guessing if the latest builds of CM9 are now better than the Build 40 of the AOKP ROM for the Nook Color. It would be great if someone can tell me their experiences with both ROMS.
[Nook Color General] freonchill:
i have not used eyeballer's cm9 since i found aokp

the last eyeballer cm9 build i did use was cm-9-encore-20120628-0730-opengl-unofficial.zip (june 28, 2012)

i was testing a new build every week (complete wipe and re-install from scratch) as i was having hard lock-ups within the first 5 minutes in the cm9 builds. i tested both opengl and non-opengl builds for about 2 months.

i was so excited when i first installed aokp and was able to read through all of my typical daily news in google reader (60+ sources, 1000+ articles) about 20-30 minutes; rather than having it lock-up after 5 minutes.

using aokp i will still typically get hard lock-ups; but they occur after 5-10 minutes of use when i have not rebooted in a week.

i am eagerly awaiting the fat-tire/sluo/keyodi/krylon's first cm10/jb builds with the 3.x kernel.
[Nook Color General] bowguy:
Updated CM9 nightlies

I just installed the latest CM9 from eyeballer's thread. Lots of updates from Krylon are now included. Better graphics performance and feels smoother to me. Big thanks to all the dev's out there.

Eyeballer's thread:

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