yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] mateorod:
http://review.paranoid-rom.com/#/c/143/Fixed. Merged all of our upstream branches last night- that error occurred then. Thanks for the tip.

I bit the bullet and submitted our makefiles upstream to PA. I still kinda have an issue with the perception that PA is a ROM into and of itself; but we use and enjoy their frameworks so i thought we'd give back.

So this will be the Official PA build for encore, assuming they merge our patch.

Some of the patch may look unfamiliar, because one of our goals is to inspire home building, I am using a comprehensive default.xml, which pulls all projects and dependencies in one document. The patch is set up to PA makefile conventions, which uses a local_manifest when necessary.

But the other than the methods they should be functionally the same.
[Nook Color Android Development] runningslow:
Successful build. It booted! No time to test right now, but going to test later and report back. Thanks!

My phone tastes like jelly beans!
[Nook Color Android Development] lepa71:
I know this is for NC, but ... Can I build on for Nook Tablet?

Thanks
[Nook Color Android Development] WJThomas:
Found this on http://source.android.com/source/known-issues.html

I was using NAT and switched to bridged. For the first time I was able to sync without a failure. I can even drop the -j1 and still sync without error.
[Nook Color Android Development] :
Hey guys,

1. Don't want to be a parasite ;) but could anyone post their CM10 build, or PM me. Do to hardware constraints I can't build my own. My 64 bit pc is broken and I'm writing this from a 32 #!

2. On the last ICS release, my Status Bar suddenly disappeared, I tried looking through all the settings but can't seem to get it back, any help?

Thanks to the dev for all his hard work, this is truly the best NC ICS rom.
[Nook Color Android Development] grayfoxmg1:
Hear ye, Hear ye

As decreed by the great and noble Fattire, non shall distribute nor post a CM10 build until thine gods O' the Cyanogen have doth created and bestowed upon us an official build. If ye wish to experience the upgrade referred to as 'Jelly Bean,' Thine must creatith thine own version.

In other words, though I understand where you are coming from (with my computer in the shop and having to use an old one). The general rule still applies, sorry. My advice is to either wait for a build or your computer to be fixed, or I believe there is a work around for building with a 32bit computer posted somewhere.
[Nook Color Android Development] :
Thanks man, and since I'm extremely grateful for all their work I will comply to their requests.

Do you have a link to the 32 bit work around? I searched google and Xda for building instructions and they all specify 64bit
[Nook Color Android Development] grayfoxmg1:
sadly I do not, which sucks as I'm in the same boat as you (my laptop fried last week and Asus told me they might have it fixed by thursday). Now on to your other problem, you said your status bar disappeared? Which was the first build of CM9 that you noticed this on? Have you tried doing a complete wipe and then flashing a ROM? If you load up a bootable SDcard with CM7 is the status bar there?
[Nook Color Android Development] :
I just noticed it a few days back, I'm running the last posted release from this thread. But don't worry, I'll just do a full wipe, may be a setting I changed and now I can't find it ;) I appreciate all your help.
[Nook Color Android Development] Quantumrabbit:
I've been running the October 8 for 4 days now... unlike the previous I haven't had a single lockup or freeze.

Not sure if it's my hardware, but clearly the HWA or OpenGL is no good for my device.
[Nook Color Android Development] davidr415:
JDK Question:

In looking at all the different sets of instructions for setting up build environments, all are similar, except some tell us to run a bunch of "sudo update-alternatives --install" commands after running the jdk-6u35-linux-x64.bin file and some instructions don't even mention these commands.

So.. are they necessary?

Running Ubuntu 12.04 on 64 bit Virtualbox, BTW.
[Nook Color Android Development] mateorod:
Enter java -version. If it is the Offical JDk then you are done. If it mentions OpenJDK then go through the update-alternatives parts.

That is necessary because some distros are configured to use OpenJDK by default. Essentially you need to tell your environment which JDK you want, since you will have a couple of Java programs on the box.

here's mine:

java -version
java version "1.6.0_33"
Java(TM) SE Runtime Environment (build 1.6.0_33-b04)
Java HotSpot(TM) 64-Bit Server VM (build 20.8-b03, mixed mode)
[Nook Color Android Development] davidr415:
Thanks Mateor..

If I am installing JDK from the Oracle site, wouldn't it be the "official one?
[Nook Color Android Development] WJThomas:
I don't know what I missed, but I don't recall and didn't do any 'update alternatives'

When I build, I do get the following message:

I've been meaining to research/ask about this; but I get a .zip that flashes and runs...

Here is what I had:

So, even though I had the Sun JDK installed and in the path, the system was using the OpenJDK. When looking for the details on 'update alternatives' I ended up at this site: http://www.welarson.com/?page_id=281 and used the installation script for Sun JDK on Ubuntu 12.04.

After running the script, here is what I have:

I want to get a clean build, so I deleted everyting in my system directory (except for .repo) and I'm redoing the sync. Is there an easier way?

Update:

I think make clobber is the command I was looking for. It will clean out the build directory.
[Nook Color Android Development] dparrothead1:
I don't mean to hijack a dev thread, but I had to say thanks for this Rom. I have updated to a Nexus 7 and had pretty much written off my NC for an ereader. Saw this thread and thought I would give it one more shot and low and behold, I have brand new device!!!

D/L, flashed, updated the play store to 3.9.16 and good to go.

One small....I cannot get it forced into Tablet UI. I go in and change the settings, reboot....but the icons on the homescreen stay on the right side of the screen.

Again, thanks for hard work in giving us this awesome Rom !!!!!!!!:)))))))
[Nook Color Android Development] kevin37:
Help please?

forgive me if this is already posted but I am trying the build instruction and I got to this and I was wondering what I did wrong I have tried like 7 times? here is what Im getting.....

-multilib mingw32 openjdk-6-jdk pngcrush schedtool tofrodos python-markdown libxml2-utils xsltproc zlib1g-dev:i386

E: command line 'l' [from -multilib] is not known

was I supposed to add the two lines together? I assumed that seeing it was below, that it was a second command line. Was I wrong for thinking that?
[Nook Color Android Development] mateorod:
It looks like you are having trouble installing the dependencies. Is that the entire command you are running in the terminal? Cut and paste this:

sudo apt-get install git-core gnupg flex bison gperf build-essential zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-dev:i386 g++-multilib mingw32 openjdk-6-jdk pngcrush schedtool tofrodos python-markdown libxml2-utils xsltproc zlib1g-dev:i386

I guess the g++ got cut off of your comman somehow. But assuming your distro has apt-get (Ubuntu for instance) then this should take care of you. I have seen that people struggle the most with the JDK install, there is a link in the 3rd post that you can follow Method 2.

Good luck. Deciding to try is the hardest and biggest step. After that you can come here for any help you need.
[Nook Color Android Development] kevin37:
I just got this error? Is there anything I did wrong? Thanks for the first time you helped.

here is what I did and what I got as a result....

ubuntu@ubuntu:~$git-core gnupg flex bison gperf build-essential zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-dev:i386 g++-multilib mingw32 openjdk-6-jdk pngcrush schedtool tofrodos python-markdown libxml2-utils xsltproc zlib1g-dev:i386

package pngcrush is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source

package python-markdown is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source

E :Unable to locate package mingw32

E: Package 'pngcrush' has no installation candidate

E: Unable to locate package schedtool

E: Package 'python-markdown' has noinstallation candidate

E: Unable to locate package zliblg-dev:i386

ubuntu@ubuntu:~$
[Nook Color Android Development] mateorod:
The apt-get installs from a repo, and the packaging and availability of packages changes regularly. Try this;

sudo apt-get install synaptic
sudo synaptic

That will launch synaptic, which is the package manager that was on Ubuntu by default for years. It will launch and you can search and install those packages there. It is not unheard of for you not to be able to find a package from that list...don't sweat it. Install everything that synaptic has available and you should be okay.
[Nook Color Android Development] kevin37:
Sorry that didnt work ether? pretty much the same message? I broke my pc!!! Lol, just kidding!:D

E: Package 'synaptic' has no installation candidate
[Nook Color Android Development] mateorod:
Okay, I am going to go ahead and assume you are using Ubuntu, since that is the most likely and popular first distro. You either need to upgrade your package listings and/or allow those repos as a source.

Open the software center and click <edit>Software sources. There will be a GUI that opens up that allows you to choose installation sources. Just click all of them. Check the Other Sources tab as well.

Go back to your terminal and run

sudo apt-get update

Edit: Reboot.

That will update your package list. Certainly explains your issues with the original packages, seemed unlikely that so many of them would be missing.
[Nook Color Android Development] davidr415:
An ERROR...?

After what appears to be a successful repo sync , the lunch command yields a message

"Dependencies file not found, bailing out."

Before I go further and possibly lose what I've already done, can someone please help me understand what has happened and how to deal with it?

Trying to build JB.. using a virtual box with xubuntu 12.04
[Nook Color Android Development] mateorod:
Go forth with wild abandon! This is, despite what people might fear, a pretty hardy process, any errors the compiler finds it gives you chances to correct without losing almost any progress.

But what you report is normal. Build away.
[Nook Color Android Development] boyoboyo:
Now that CM10 alpha .zip is up ...

... will we be seeing PA alphas here as well? :)
[Nook Color Android Development] mateorod:
Eventually. But probably not for a couple weeks, though. That may not be the most popular decision, I know.

But this CM10 alpha zip was released so the general public can test and finish hunting down bugs. They're hoping to get the things they need fixed to the point that they get CM10 Official builds for encore; that would be quite a feat.

Even if they don't quite get to Official Build status (for instance, I don't know if GL is required and so forth. I have been wondering whether they intend to turn it back on at some point. I have never been able to stand the performance with it on, personally) a stable CM10 for the Nook is quite a feat.

Think about it, the official manufacturer of this hardware is still actively selling the machine, but with Froyo on it.

The Nook Color was a huge succes for B&N, but I think of it as the best case example for a place like XDA, a device where the experience of owning it is in every way enhanced by turning the software over to the owners of the machine. Over the last 2 years, think of how far the Nook has come and what you are able to do with it through this forum. And then think of the poor people out there still running around with it stock, like my sister-in-law.

Point is, I would like to see people try out the Alpha build for awhile and see what those guys put together. They have been helping the Nook keep pace with the latest released devices, I would like them to get a chance to show people what they have made. And PA is entirely based off of their efforts, without that stable build we wouldn't have a ParanoidAndroid rom at all.

Point is, please go ahead and try out the alpha, people. Find some posts by the team and thank them.

I don't expect this thread to have too much activity for the next couple weeks. In maybe two weeks or so, I will look at it again and we can get together and release a zip.

Also, since running PA could be responsible for any bugs, no one running this ROM counts as a data point for bug and log reports. Since we use their CM10 base, diluting their user base has a direct negative effect on the stability of this ROM. The PA rom will benefit from not releasing a zip quite yet and letting this CM10 alpha get the full testing treatment.

There may be some good news for you flash-a-holics soon though, but let me put a little more energy into that first before I let the cat out of the bag.
[Nook Color Android Development] boyoboyo:
Hey I'm testing it for like 12 hours. It's just hard because there's nothing to report :)
[Nook Color Android Development] kevin37:
thank you that worked great and I got alot further than i did yesterday! but I hit another rock! as soon as I come back to do the repo init -u ect. part on this part i now get this message. Can you tell me what I did wrong?

ubuntu@ubuntu:~/android/system$ repo init -u git://github.com/mateor/android.git -b jellybean

No command 'repo' found, did you mean:

Command 'rep' from package 'rep' (universe)

Command 'repl' from package 'nmh' (universe)

Command 'repl' from package 'mailutils-mh' (universe)

repo: command not found

ubuntu@ubuntu:~/android/system$

Never mind I figured it out!

if anyone has this issue here is how to solve it. add the code below in green inbetween these two like shown belo, this solved my issue. I guess doing it the way its done in the wiki did not direct the fils to the right path!

mkdir -p ~/bin

PATH=~/bin:$PATH

mkdir -p ~/android/system

Sync the Repository

Enter the following to download make executable the repo binary:

curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo chmod a+x ~/bin/repo

Then go back to the first page in this thread and continue. Thanks for the help that I did get and I hope this helps someone in the future
[Nook Color Android Development] grayfoxmg1:
Does the gapps file in the alpha thread work with our PA rom?
[Nook Color Android Development] mateorod:
For ICS you need the fixed GAPPs from techerrata. For JB, the most current gapps for any JB rom will do, including the one from the alpha thread.
[Nook Color Android Development] grayfoxmg1:
thank you, didn't want to flash the wrong set.

---------- Post added at 08:18 PM ---------- Previous post was at 08:16 PM ----------

preforming a back-up right now, in-case of bootloop or app loss.
[Nook Color Android Development] grayfoxmg1:
First, for those of you who don't know me (or care), I'm grayfoxmg1, and I have been using mateorod's fixes for V6 Supercharger, since back when we all had to physically replace the files ourselves(so like January). Since I can't build right now, what I shall do to contribute is the 'Every Man's Test.' This is a test that was created back with building on the G1. It is used to test issues on a ROM.

Rules are, I have one full charge to work this on, and must list everything I have done to the ROM as a set-up. I then run this battery charge to the ground cataloging FC's, SOD's, Wi-Fi signal issues, and lag.

First I shall list my specs, and will leave my device(Nook) on charge for an extra half-hour. You as my fellow devs and testers have that time to inform me what to look for on our ROM.

Specs:

-'Old' Nook with a 2/4 partition set-up

-Running our Paranoid Android 2.X port

-Launcher is Nova

-I am V6 Supercharged using the mfk calculator option on zepplinrox's S11T6 script

-I am using Tablet UI as the option for all of my dpi settings

-CPU Range is 800-1000 with a conservative governor

-Voltage is stock

-I installed this over my past installation of Paranoid Android (1.6)

It is 10:54 my time, so at 11:24 my test starts.
[Nook Color Android Development] pavlos46:
Check touch sound please, it comes and goes for me, keyboard sound is ok games and videos sound also ok.

Thanks

Pavlos
[Nook Color Android Development] grayfoxmg1:
I played fruit ninja on it earlier, and after some initial slowness when starting(which i attribute to the changed cpu speeds) it worked fine. Haven't tried video yet, I'll watch a youtube video later and maybe a mpeg file from local drive.
[Nook Color Android Development] kevin37:
I had a question, I got everything to work but, Im useing virtualbox and after the repo sync it runs for like an hour and then I get a bunch of fatel errors not enough space? It also pops up with a screen that said I had only 70.5MB and it could not complete. Is there any way I can resolve this? Im running windows 7 and have 445GB of free space on the hard drive, if anyone wanted to know. Thanks
[Nook Color Android Development] davidr415:
How much HD space did you set up for the Linux on your virtual box? I set up 50GB after getting the same errors on 12 GB.. and it solved the problem.
[Nook Color Android Development] grayfoxmg1:
So my Nook just died, so my 'everyman's test' is over. It's time for my report. In the little over 25hrs my nook was running my build(as stated in my other post) I experienced:

-1 FC of the Google Play Store*

-2 Drops of Wi-Fi signal at my house (802.11b/g/n wpa2 protected)

-1 SOD after leaving it off for an entire class today [approx 1.5hrs]

-1 crash of the YouTube app when I tried to watch a video with 'HQ' turned on*

*indicates success at a later attempt.

Everything else worked for me, and I will include a list of ALL apps that I launched/had run while doing this test.

APPS:

-Beautiful Widgets

-iHeartRadio

-Google Drive

-Dropbox

-Tapatalk 2

-Aurora (Firefox Mobile Beta)

-Play Store

-Amazon Appstore

-SDspeed Increase

-Script Manager

-Terminal emulator

-Kindle

-FBReader

-Youtube

-Pocket

-Gmail

-Facebook

-Google +

-Fruit Ninja

-Need For Speed: Hot Pursuit(note laggy and extremely slow)

-Gameboid

-Amazing Alex

I realize that this list is not indicative of normal use for within a day, however it could've been. Whenever I had down time and felt like reading I switched up my program. I also played a different game every time I felt like playing a game. But I am happy to report that, I feel, this ROM is daily driver material. I never had any issues with touch, sound never cut-off for me, and none of my apps ever 'forced' themselves out of tablet mode due to an error(which I've had happen before, notably on Kindle). Though the battery didn't last aslong as I thought it would, I can attribute that to heavy use, and there might be some settings I still haven't tweaked properly yet.

Over-all, this is was a triumph. I'm making a note here 'Huge Success.' It's hard to overstate my satisfaction(cookies if you get reference). Hopefully my test will encourage more people who are running Paranoid Android 1.6 to try and build there own 2.X JB ROM. If you see an app listed and you have questions for how well it ran, feel free to ask.

In conclusion, I'd like to thank everyone here who cooperated on this build and all the guys that worked on the CM10 'ALPHA' and are still working(my next stop is that thread to hit the thanks button on all their posts), and everyone who worked/works on auto_patcher as I used that on this ROM.
[Nook Color Android Development] kevin37:
If tried to set it up with a fixed HD side of 88GB and still I get an error when I repo sync about an hour and a half through that I only have 70 MB left not enough space? Can someone give me a walk through on how I should set up virtual box to complete this build? It seems this is the final thing standing in my way and I can't figure it out. Iv searched the threads and Google YouTube and still can't solve this issue? Thanks again for the help in this learning process.
[Nook Color Android Development] davidr415:
One thought.. During setup, when it asks you if you want to erase the entire hard drive, are you doing it? You need to. It is only referring to the virtual drive that will be used for installing Linux.
[Nook Color Android Development] kevin37:
Oh so that's what I'm doing wrong! I'm useing the try Ubuntu option, not the install option! Lol OK I'll try it that way and erase the virtual hard drive like you said and see what happens. Live and learn! Lol such a little mistake makes such a huge hassle!:D
[Nook Color Android Development] anapospastos:
I built 2.23 today but it doesn't boot. Has anyone figured why?

this is my boot log
[Nook Color Android Development] vinal:
I built it last week and got it to run, but it had all the same issues as the jb alpha build so I went back to PA 1.6 that works great.

I assume you wiped all data and caches.
[Nook Color Android Development] mateorod:
I missed your post, sorry. There has been some upstream commits that have broken all CM10 builds. I am waiting to see how they resolve it before checking in any temporary fixes. But if you have it all built, go read the last couple of posts on the dev thread, I think there is a method there that works...I have not built since those changes myself...

Update 10/24: Looks like things have stablilized some...I have pulled all the changes to our forks as well as change the jellybean device repo to the NookieDevs one. I guess they aren't keeping fat-tire's up to speed, or it is just for stable changes, and we don't need our own fork for jellybean like we do for ics.

The point is that the builds should work and are now PA 2.5.1. Also, as per Krylon, Netflix may be en route.

Stay tuned.
[Nook Color Android Development] kcls:
Psyched for 2.5.1, that per app navbar color looks freaking amazing.

Tapatalk² from my Optimus V
[Nook Color Android Development] davidr415:
When I do a "lunch", there are no choices for pa_encore.

Everything seemed to go well during the repo sync..

What now? (building jellybean, BTW) using Ubuntu 12.04 virtualbox.
[Nook Color Android Development] mateorod:
cd vendor/pa/products
cat AndroidProducts.mk

Do you see encore on that list? If not, will you post the output of the cat command. And then check presence of vendor/pa/products/pa_encore.mk

I am going to be doing some updating to the source this weekend, to bring our devices up to speed for the update to 2.5, btw.
[Nook Color Android Development] davidr415:
I think I just found the problem. When I did the repo init, I used:

repo init -u git://github.com/CyanogenMod/android.git -b jellybean

instead of:

repo init -u git://github.com/mateor/android.git -b jellybean

Sorry to bother you.. I guess I need to just stat over??

I'd be happy with CM.. I figure I don;t have all the things I need for that to be correct.
[Nook Color Android Development] mateorod:
No!

Don't delete it!

Just repo init again with the proper command right over the old one. It won't take long.
[Nook Color Android Development] davidr415:
Thanks mateorod.. it is working now..

So.. when I do this correct command after doing the incorrect one, does it just do some sort of incremental sync?