yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] cybertimber2007:
Well two fold... one, it's a developer topic... so trying to contribute there. Two, you really only have the need to flash a ROM and gapps together very rarely, so not worth expanding the boot partition.

It's a very early nook color build that fattire was nice enough to release. :) In time i'm sure this will disappear, but it is the answer to the constant drain question.
[Nook Color Android Development] Homer_S_xda:
More off topic: is there a distro for

former

Ubuntu users that frakkin' hate Unity? I was going to go back to 10.10 but it took too long to download. Who thought it was a good idea to make the simple process of installing Google Chrome as a browser IMPOSSIBLE TO DO?

Homer
[Nook Color Android Development] Nburnes:
Linux Mint?
[Nook Color Android Development] sark666:
I installed Mantano but I received an error opening a pdf and then an error google ttl engine has stopped.

I'm wondering about when I had to take out various apks from gapps to get it to install. I get the impression emmc installations dodge this issue, as some say they install gapps no problem with no mention of modifying the gapps file.

I tried another pdf reader, apv, and it crashes opening pdf's as well.
[Nook Color Android Development] fattire:
From IRC:

<jeffp__> could someone please post on the ics dev thread that sark666 needs to switch to pico tts in settings/language & input/text to speech output, to prevent that error he's getting. i can't do it bc i don't have ten posts on xda yet, and i probably never will bc i only made this account to post on the ics dev thread!
[Nook Color Android Development] Sjflowerhorn:
I didnt read all 30 some pages but in op it says bt is confirmed pairing only. Send and recieve do work confirmed. Just a heads up and sorry if it was covered.
[Nook Color Android Development] Sjflowerhorn:
Install kde on the side and if you hatr unity that much remove it. I left it incase i felt like using it in future but i always use kde over gnome anyway.
[Nook Color Android Development] thetakerfan:
Anyone gotten google reader to work? As soon as I try to add the account it crashes when logging in. Tried reflashing gapps but no change.
[Nook Color Android Development] gambit07:
Works fine for me, angry birds does as well now

Edit: Using these gapps I believe http://download.clockworkmod.com/test/gapps-ics-20111125-2.zip
[Nook Color Android Development] Bawb3:
@fattire

You guys might want to look through jt1134's github and see if theres anything useful in there. Those guys have an almost 100%working build for my phone (fascinate) with a lot of fixes. I don't know what's hardware specific and what not, but it can't hurt.
[Nook Color Android Development] kschumake83:
+1 that's what I use at the moment much better than ubuntu
[Nook Color Android Development] fattire:
Get ye to the wiki with all speed!
[Nook Color Android Development] pmgnet:
If you want some very raw steps, here's what I worked out a while back to do this with gparted, etc.

http://pastebin.com/e073Sf8b
[Nook Color Android Development] ryanl2299:
It looks like there already is a cm11 build for the NC here. No clue how stable it is. Just happened upon it via a web search. It's the same guy who has a CM11 blog for the Nook HD+.
[Nook Color Android Development] steven676:
Sigh. As a reminder:

We cannot, of course, enforce this ban -- given the licensing of the code involved, there's no legal impediment to posting a build. But the Nook Color community has traditionally been good about following this request.

By the way, I note that build is 160 MB compressed, which is quite small -- our CM10.2 nightlies are typically 165 MB in size, and even with the latest slimming work on CM included, my CM11 builds weigh in at 169 MB. If that build isn't broken, it'd be nice to share how he/she got the build size down ...
[Nook Color Android Development] volpo222:
I tried this on an SD card. It installed and worked but was too slow for daily use. I got so frustrated with this particular build that I flushed it and am happily back with the latest 4.3.

It made me understand and happily await the arrival of the nightlies for Kit Kat.
[Nook Color Android Development] andtron:
Does the CWM 6.0.4.5 backward compatible to run CM 10.1 or 10.2?

TIA
[Nook Color Android Development] ryanl2299:
I believe this is supposed to be an internal ROM, not external. I'm surprised it even worked.
[Nook Color Android Development] leapinlar:
I think so.
[Nook Color Android Development] volpo222:
I was surprised at how easy it was. I just used the 'usual' method and didn't see any error messages etc. I have a stock NC on EMMC and it was still there after I removed my sd card. I don't think it was usable but it did work. I must say I have a new respect for the Devs and the magic they do.
[Nook Color Android Development] douginoz:
Regarding not making available builds:

What rubbish.

The majority of people in a dev sub-forum already know about risks of bricking or faulty code or poor performing alpha releases. They just want to play.

The vast majority of people do not want to learn about development or be forced to download, compile, research, analyse, and debug just to be able to play with a build.

They don't care if the build works well or at all. They know about backing up their existing system first.

The primary reason a few people in here try to restrict the release is in the hopes that it will force people to get involved. They may have even succeeded by a few people that got involved and did their own compiling etc. but I suspect those n00bs have not contributed significantly to the real work needing to be done to make ROM work. And their questions and requests for assistance with basic building/compiling/etc operations detracts the core devs from their work.

The only good I see from devs not wanting builds to be made available is to stop the plethora of questions and requests for assistance from the non-dev types in here that just want to try things out and play. But I believe that's not a problem unique to the NC ROM forums, and it seems to be managed sufficiently well elsewhere. For some reason beyond my grasp, this seems to be an insurmountable problem in here.

Either that or there's egos at play.

At any rate, I'm delighted to find out about this "illicit" build release available and will immediately start playing with it. And if I have any questions, I'll be sure to NOT post them in this development-discussion-only thread.
[Nook Color Android Development] tonestertm:
"Daddy, I want to play with my new bicycle NOW!"

"Honey, I haven't put the front wheel on yet-"

"I don't care, it'll be fun anyway!"

"Well, OK...."

(Child climbs on half-assembled bike, promptly demands Daddy hold her upright for 10 minutes of 'fun', then demands to be let loose.... Gravity ensues, blood issues forth, bike is damaged, and child runs, crying, to Mommy about what a Meanie Daddy is.}

Tapatalked from my Nook Color running CM 10.2
[Nook Color Android Development] bowguy:
Still a noob but having fun

I have had a ball the last few years build for my NC. This thread is why I bought my nook in the first place - hey if you can build a custom OS for a tablet and test it on a $10 card I wanted to try. Have I contributed code? No but I have tested some builds for the developers which really helped when they didn't work. Test, feedback, make it better. I have tracked down errors and gave a little advice when people did what I already screwed up on.

All this is still fun. I even have ART running on CM11 on a 4 year old tablet. :laugh:
[Nook Color Android Development] Whompy:
I have thoroughly enjoyed learning the process of creating my own builds through this forum. I have mostly run my own builds for all my subsequent devices as a result and learned much more about the Linux systems I love in the process. There is something so satisfying about seeing my computer name in the "About" section of the settings. Really feels like you own the device.

Oh, and I developed a taste for Fat Tire beer ever since stumbling upon this thread. Had to try it after having that avatar stare me down for so long...
[Nook Color Android Development] fattire:
"Fat Tire"

Heh. Marketing works! I'm clearly very creative when it comes to aliases...

(wiggly flashback effect)

"So IRC is saying I need to register a username. Hmmm. This is a unique opportunity to define myself. So let's see. Okay how about..." (glances around the room, then down to my hand...) "Ahhhh...."
[Nook Color Android Development] bowguy:
Enable ART on CM11 for the Nook Color

I found out how to enable ART on the Nook Color. When you select ART as the runtime in Developer options, the tablet reboots but gets stuck in a bootloop. The problem is during bootup, a lot of files are being converted but the Nook runs out of memory. Then it crashes, reboots and tries again and never gets past it. However the boot animation takes a lot of memory during this process.

Solution: Disable boot animation. What you need to do is open the File Manager app. Go to settings (lower right icon) and General Settings. Under Advanced, Access Mode, select either User Prompt or Root Access mode. You need to alter a root file. Any prompts you get make sure to allow superuser access.

Now navigate to /system touch on build.prop and open with "Editor". Add the following line to the end of the file:

debug.sf.nobootanimation=1

Save the file and exit File Manager.

DO NOT ENABLE ART NOW!!

First make sure you did this correctly by rebooting your nook. Make sure you DO NOT see the Cyanogen logo when it boots up - it will take a while with a blank screen and then go to your standard lock screen. If you see the animation logo, you did something wrong, try again.

Now you can enable ART in the Developer Options. When it reboots, wait a while (2 min?) then you should see the optimizing apps display. A basic install with gapps has about 85 apps to convert. This will take a while.

Report back with results!

The latest nightlies and recent builds no longer need to do anything special to enable ART. Steven676 has greatly reduced the memory footprint of the bootanimation resulting in faster boots and eliminates the need to disable it for ART. However, you could still run out of space especially on EMMC installations. See the posts on partioning for discussions on a solution.
[Nook Color Android Development] Arbelzapf:
mikeioannina, the developer of the LegacyXperia CM11 rom ended up repartitioning the internal storage to make the rom future-proof. Partly because these devices are really short on internal storage, and one side effect of this was that ART started working.

While I would perfectly understand if you guys decided that it's too early to take such drastic measures as to force everyone to completely wipe and repartition their internal storage, this probably will become a neccessity in the future.

It might be worth going down that road now instead of wasting time stripping boot animations and ringtones just to get those extra few megs of space.

We have a ridiculous amount of internal space so why not make room?
[Nook Color Android Development] olenchenko:
Build error

Hi devs!

I have successfully built CM-11 on January 2 (following wiki instructions), but now for two days I have this error:

host C++: libclangARCMigrate <= external/clang/lib/ARCMigrate/TransRetainReleaseDealloc.cpp
CC [M] /root/android/system/hardware/ti/wlan/mac80211/compat_wl12xx/net/wireless/wext-compat.o
CC [M] /root/android/system/hardware/ti/wlan/mac80211/compat_wl12xx/net/wireless/wext-sme.o
LD [M] /root/android/system/hardware/ti/wlan/mac80211/compat_wl12xx/net/wireless/cfg80211.o
LD /root/android/system/hardware/ti/wlan/mac80211/compat_wl12xx/built-in.o
Building modules, stage 2.
MODPOST 4 modules
CC /root/android/system/hardware/ti/wlan/mac80211/compat_wl12xx/compat/compat.mod.o
LD [M] /root/android/system/hardware/ti/wlan/mac80211/compat_wl12xx/compat/compat.ko
CC /root/android/system/hardware/ti/wlan/mac80211/compat_wl12xx/drivers/net/wireless/wl12xx/wl12xx.mod.o
LD [M] /root/android/system/hardware/ti/wlan/mac80211/compat_wl12xx/drivers/net/wireless/wl12xx/wl12xx.ko
CC /root/android/system/hardware/ti/wlan/mac80211/compat_wl12xx/net/mac80211/mac80211.mod.o
LD [M] /root/android/system/hardware/ti/wlan/mac80211/compat_wl12xx/net/mac80211/mac80211.ko
CC /root/android/system/hardware/ti/wlan/mac80211/compat_wl12xx/net/wireless/cfg80211.mod.o
LD [M] /root/android/system/hardware/ti/wlan/mac80211/compat_wl12xx/net/wireless/cfg80211.ko
make[2]: Leaving directory `/root/android/system/out/target/product/encore/obj/KERNEL_OBJ'
make[1]: Leaving directory `/root/android/system/hardware/ti/wlan/mac80211/compat_wl12xx'
mv hardware/ti/wlan/mac80211/compat_wl12xx/net/mac80211/mac80211.ko /root/android/system/out/target/product/encore/system/lib/modules
mv hardware/ti/wlan/mac80211/compat_wl12xx/net/wireless/cfg80211.ko /root/android/system/out/target/product/encore/system/lib/modules
mv hardware/ti/wlan/mac80211/compat_wl12xx/drivers/net/wireless/wl12xx/wl12xx.ko /root/android/system/out/target/product/encore/system/lib/modules
mv hardware/ti/wlan/mac80211/compat_wl12xx/drivers/net/wireless/wl12xx/wl12xx_sdio.ko /root/android/system/out/target/product/encore/system/lib/modules
mv: cannot stat `hardware/ti/wlan/mac80211/compat_wl12xx/drivers/net/wireless/wl12xx/wl12xx_sdio.ko': No such file or directory
make: *** [wifi_modules] Error 1
make: *** Waiting for unfinished jobs....

I have tried cleaning and starting from scratch (from repo init...) with no success. Is there anything I am missing? Any suggestions?

Thanks in advance.
[Nook Color Android Development] anapospastos:
I enabled it using the way you write but when it finishes boot (long time) I'm continuously getting "com.process.gapps has stopped". I cleared the cache and reflashed gapps but nothing changes. I guess that the problem has to do with the gapps and their support of art. I'm using the 31-10-2013 package from paranoid for 4.4.
[Nook Color Android Development] Arbelzapf:
Same problem here.

I built successfully from NookieDevs repo a minute ago, but got this right after switching to steven676's repos to try the hwcomposer
[Nook Color Android Development] bowguy:
I am using the gapps-kk-20131119.zip from dhacker. I am sure there needs to be a lot of testing/crashing until an 'official' package is out. I am downloading gapps-kk-20131111-artcompatible.zip now to do more testing.

Note I am running on a SD card. My /system partition has 494 MB in it which is more than what is available in an EMMC install. Not sure if this makes a difference.

BTW I got a 1885 on the Quadrant Standard test using ART.
[Nook Color Android Development] skyliner33v:
I have recently compiled a build for my NC based on a very good friend of mines' rom called beanstalk rom. For those interested, here are links to:

The Beanstalk Developer's Thread and

The Infuse Beanstalk Thread This is where Beanstalk was born from.

Now I have zero prior in compiling whatsoever. And I mean I've never touched Linux on a computer up until about 2 months ago. That's when I decided that I wanted to try building this rom for my phone and my NC. So I went ahead and got my laptop set up for building. And I spent a lot of time in threads like this reading. There is something very special about compiling your own builds and troubleshooting the errors that you will no doubt run into from time to time. I feel proud that I am now able to build a great rom and I don't have to rely on others to release a build.

And speaking of errors, I ran into one while building for the NC. So my first step in troubleshooting is to google around for answers. I came across a similar error for a different device, and a possible solution. And guess who was the author of said solution? Why our very own fattire! So I pm'd him about my error and he graciously provided me with guidance and tools I could use on how to troubleshoot it. But he did not flat out give me the answer and specifics. He stated in a way that made me responsible for digging around my source code and try and find it myself. And it was the best thing that he could have every done. I spent a few hours across two days digging around, I learned more about how android works than ever before.

So now I have a highly functional 4.4.2 rom with tons of tweaks running on my nook. It is running faster, smoother and with less lag than I have ever seen it before. And I owe it all to the amazing real devs that have done the behind the scenes work to bring up the nook to be able to run these newer versions of android. I've poked around github long enough to know who these people are. You see the same names that submit the majority of the patches and bugfixes. Without you guys, my story wouldn't have been possible. Thank you all.

So I for one agree to keeping the tradition of not releasing builds right now. I encourage anyone to try and build for yourself. Learn it. It really isn't that difficult to compile a build. And I would be willing to help anyone out with building help. Granted I'm just learning too, but I wanted to throw out the offer to help.
[Nook Color Android Development] xflier:
I have the same issue recently too.
[Nook Color Android Development] Arbelzapf:
Are you all using Steven676's sources?
[Nook Color Android Development] xflier:
Yes
[Nook Color Android Development] Arbelzapf:
I think I found the problem:

Steven removed the kernel module from the config 2 days ago:

-CONFIG_WL12XX_SDIO_TEST=m
+# CONFIG_WL12XX_SDIO_TEST is not set

https://github.com/steven676/ti-omap-encore-kernel3/commit/c678acc55c13f9c569012b829543ebf82c1e5ae1

How do you build with this commit reverted?

EDIT: For now, I hand-edited the files and built successfully. Ugly, but it works
[Nook Color Android Development] drmarble:
wl12xx_sdio.ko error -- FIX

I also encountered this error. There is a problem in hardware/ti/wlan. After discussion on IRC with sluo (steven676) he found the solution. Those egomaniacal developers are terribly selfish with their help. Apply this patch to form the hardware/ti/wlan directory:

diff --git a/mac80211/compat_wl12xx/config.mk b/mac80211/compat_wl12xx/config.mk
index a3ea3c3..5142733 100644
--- a/mac80211/compat_wl12xx/config.mk
+++ b/mac80211/compat_wl12xx/config.mk
@@ -582,7 +582,6 @@ ifdef CONFIG_MMC
CONFIG_SSB_SDIOHOST=y
CONFIG_B43_SDIO=y

-ifdef CONFIG_CRC7
ifdef CONFIG_WL12XX_PLATFORM_DATA
CONFIG_COMPAT_WL1251_SDIO=m
endif #CONFIG_WL12XX_PLATFORM_DATA
@@ -593,8 +592,6 @@ CONFIG_COMPAT_WL12XX_SDIO=m
endif #CONFIG_WL12XX_PLATFORM_DATA
endif #CONFIG_COMPAT_KERNEL_2_6_32

-endif #CONFIG_CRC7
-
CONFIG_MWIFIEX_SDIO=m

ifndef CONFIG_COMPAT_KERNEL_2_6_32
@@ -655,11 +652,8 @@ CONFIG_ATH_COMMON=m
CONFIG_BRCMUTIL=m
# CONFIG_BRCMDBG=y

-ifdef CONFIG_CRC7
CONFIG_WL1251=m
CONFIG_WL12XX=m
-endif #CONFIG_CRC7
-
CONFIG_MWIFIEX=m

ifndef CONFIG_CORDIC

Just copy the above to a text file, save it, (eg. crc7.patch), cd hardware/ti/wlan, git apply crc7.patch . All done.

As Steven Luo said:

CRC7 functions are only used in the SPI code for these drivers, so it's

unnecessary for the SDIO drivers to depend on CONFIG_CRC7. See, for

example, commit a011130265e9 ("wl12xx: remove unused crc7 references")

in Linus's tree.

His patch was for a slightly different tree and didn't apply directly for us. The above works for the cm-11.0 tree.

Good luck and keep building.
[Nook Color Android Development] Arbelzapf:
I guess there's no harm if I keep using my hacked build for a while, right?

Oh and is it a good idea to keep using sluo's repo or is this a one-shot experiment and it's better to go back to NookieDev?

I don't really know where most development happens/which way the repos are usually updated
[Nook Color Android Development] pmgnet:
Any ideas why I'm getting these errors?

get-prebuilts gives me this error http://pastebin.com/iAJR8KT6

% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 221k 100 221k 0 0 252k 0 --:--:-- --:--:-- --:--:-- 281k
Archive: ./proprietary/Term.apk
End-of-central-directory signature not found. Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive. In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
unzip: cannot find zipfile directory in one of ./proprietary/Term.apk or
./proprietary/Term.apk.zip, and cannot find ./proprietary/Term.apk.ZIP, period.

I tried that after repo sync gave me this error:

hing projects: 99% (439/443) Fetching project platform/external/pixman
Fetching project platform/external/sil-fonts
Fetching projects: 100% (443/443), done.
Traceback (most recent call last):
File "/media/AndroidBuild/android/system/.repo/repo/main.py", line 418, in <module>
_Main(sys.argv[1:])
File "/media/AndroidBuild/android/system/.repo/repo/main.py", line 394, in _Main
result = repo._Run(argv) or 0
File "/media/AndroidBuild/android/system/.repo/repo/main.py", line 142, in _Run
result = cmd.Execute(copts, cargs)
File "/media/AndroidBuild/android/system/.repo/repo/subcmds/sync.py", line 648, in Execute
if self.UpdateProjectList():
File "/media/AndroidBuild/android/system/.repo/repo/subcmds/sync.py", line 431, in UpdateProjectList
if project.IsDirty():
File "/media/AndroidBuild/android/system/.repo/repo/project.py", line 603, in IsDirty
'--refresh')
File "/media/AndroidBuild/android/system/.repo/repo/project.py", line 2274, in runner
p.stderr))
error.GitError: prebuilts/gcc/darwin-x86/mips/mipsel-linux-android-4.4.3 update-index: fatal: Not a git repository (or any parent up to mount parent /media)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
[Nook Color Android Development] polymath257:
I appreciate and thoroughly encourage the 'no-builds' policy. I wish it was more common in these forums for other devices. I have learned a tremendous amount about my device and android in general. While I have not (yet) contributed code, I am hoping to learn enugh to be able to do so one day.

---------- Post added at 07:50 AM ---------- Previous post was at 07:47 AM ----------

I also had this error. I was able to pull the offending file from a ROM zip file. It looks like the command to make that ko file is not being executed. You can also directly execute it and then re-run brunch.

---------- Post added at 07:55 AM ---------- Previous post was at 07:50 AM ----------

I got errors like the one for Term.apk when I forgot to pull the blobs. Go to device/bn/encore and run install-files.sh. Alternatively, you can pull from a zipped ROM using unzip-files.sh. Also, don't forget the get-prebuilts!
[Nook Color Android Development] polymath257:
If I do this patch, will it survive a repo sync? or do I have to re-apply it?
[Nook Color Android Development] Arbelzapf:
Am I the only one experiencing the Nook regulary completely locking up? Like taking a minute to display the Play store front, or pausing for 15 seconds while scrolling? Things like that?

I've had this on my old build regulary and it's still there on my new build from yesterday evening.

I played around with the performance settings, but it doesn't seem to have that much effect.

Is this normal in the current state of development, or is everyone enjoying snappy and fast NCs?

Any tweaks I can do or anything I can do to hunt down the cause of slowness?
[Nook Color Android Development] unibroker:
20140110 build

I built last night following Dr. Marble's post with the patch. My NC is performing nicely although still with tolerable/noticeable button lag. I was going to wait to report but thought I would give you my initial take.
[Nook Color Android Development] buzz86us:
let me know is there noticeable performance improvement over 4.1, 4.2, or 4.3 builds? I just want to see if there is any credence to google's claim that 4.4 would run very well on lower-specced hardware with 512mb of ram the Nook Color being a prime example. I have switched back to a 2.3 build so please those of you early adopters let me know your take.