yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] mateorod:
All of that has been pulled from elsewhere, but I will see what I can see.

For anyone building:

The crazyness with the encore proprietary files has been settled. If you have already tried building, if you look in .repo you will see a local_manifest has probably been generated. PA's repo's try to take care of that for you, but they point in the wrong spot for our particular repos. I have removed the file that is generating the local_manifest.xml, so we should finally be done with that.

The Paranoid Backup has been replaced (thanks tonyp) and I have removed the need to pull the cm vendor files from the device (which is Rom Manager and Terminal). I did this to make building REALLY EASY in the hopes that some new people will try it.

There will be the incentive that you can then contribute when we transition to Jellybean. Right?

Total and Complete Build Instructions.

Get the packages from the wiki

This is the most intensive part of the whole enterprise. If you can install a package, you can build, I promise.

The part I see people struggle with is setting the path for adb and java. There are very clear instructions here, just type carefully

After that, you just have a few commands to enter and wait out. Then you can be ready to build anything!

mkdir -p android/system/pa
cd ~/android/system/pa
repo init -u https://github.com/mateor/android -ics
repo sync

now wait it out.

. build/envsetup.sh
lunch

pick pa_encore_userdebug. Should be number 44 or so.

make bacon

Your new rom will be in home/user/android/system/pa/out/target/product/encore. Enjoy!

Tip

Repo syncing takes a long time. This will depend on your internet. It takes me 5-6 hours. Sounds like it might take jschill 35 minutes. If you get a bunch of fetch errors, try

repo sync -j1 -f

It will take longer, because there is no threading, but the fetch errors go away.

I will put out a new build on techerrata tomorrow. This is really just a clean-up build, synced with the new tree I put together. But the entirety of the project is now available for perusal and correction, I hope to see some interest.
[Nook Color Android Development] bodi524:
I tried Pulling the latest code.

When I do I get this error:

bodi-EC14:~/android/system/pa$ repo init -u https://github.com/mateor/android -b ics

fatal: manifest 'default.xml' not available

fatal: project CyanogenMod/android_frameworks_av not fou

EDIT:

I have it working now. Doing the repo sync and going to build.

Thanks for all the work mateorod!!!
[Nook Color Android Development] mateorod:
I am going to be working on this today. If you get any build errors, just do the repo init again and repo sync. Should take less than 5 mins to catch up with whatever I am merging, should you pull anything that is in the middle of a merge.

Glad it is working, I didn't know what your error meant...

Update: I don't want to bury lepa's contribution to the thread, so I am adding this build info here...

It pains me to write this, hopefully no one has to deal with this and it was just a side effect of some of the repo shifting I have done locally.

If you get any build error's similar to this:

make: *** No rule to make target `vendor/bn/encore/proprietary/lib/egl/egl.cfg', needed by `out/target/product/encore/system/lib/egl/egl.cfg'. Stop.

It just means that you are missing the vendor props. There are two easy ways to fix this.

cd ~/android/system/pa/vendor/bn
git checkout encore/proprietary

or you can connect your nook through ADB and

cd ~/android/system/pa/device/bn/encore
./extract-files.sh

I consider the first option the easiest. But if anything gives you any trouble, the second option is surest.
[Nook Color Android Development] lepa71:
Is there PA rom for nook tablet?
[Nook Color Android Development] -somebody-:
obviously you neglected to read the MAIN POST or the last few pages of this thread. try again.
[Nook Color Android Development] AgentCherryColla:
Hey sorry for this Ultra Noob Question, but I can't seem to find my answer. So if somebody can help me out :D

I'm new to the NC, and wanted to know if any CM9 Roms had working HWA? I see that some CM9 say they have the UI HWA, but some say they don't. I've just been wanting to play N64oid, which I'm having little luck doing. So can somebody please help me?
[Nook Color Android Development] mateorod:
A couple posts back we cover the hardware acceleration question. The best way to not have to ask noob questions is to read the thread. At least the last page or two.

And for another moment in great advice:

https://play.google.com/store/apps/details?id=trev.android.mupen64plusae&hl=en

I played Zelda on my Nook from Gingerbread up with this. HWA should be working, irrespective.
[Nook Color Android Development] lepa71:
Thanks you for your "smart" response.

I just re-read this thread. There is nothing has been spoken about Nook tablet and I know it is a nook color thread and not tablet, but if you do have info it would be nice to share.
[Nook Color Android Development] mateorod:
Let's stop this before it starts, I shouldn't be encouraging the...uhhh..discouragement of this stuff.

We don't have any information about the Nook tablet. Considering we are probably the LEAST likely people to own a Nook tablet (since we sit around talking about its older version) you will probably have better luck at the Nook Tablet forum. Or Google.

No need to respond, I wish you luck in your search.
[Nook Color Android Development] les02jen17:
May I humbly request that you include a file manager on your ROM? So we can install the important apps right away (TitaniumBackup) when without a wifi access.
[Nook Color Android Development] bodi524:
I have completed the sync. Now when I try to build.

No private recovery resources for TARGET_DEVICE encore

host C: mkbootfs <= system/core/cpio/mkbootfs.c

In file included from /usr/include/stdio.h:28:0,

from system/core/cpio/mkbootfs.c:2:

/usr/include/features.h:323:26: fatal error: bits/predefs.h: No such file or directory

compilation terminated.

make: *** [out/host/linux-x86/obj/EXECUTABLES/mkbootfs_intermediates/mkbootfs.o] Error 1

Am I missing some files? I pulled the whole repository. I did an reinit of the repo

and synced again. I still get the same error.
[Nook Color Android Development] -somebody-:
my apologies for being an ass. i use mine as a desk clock basically and they all look the same, i didnt even distinguish that you asked about the tablet just went through my head as the color.
[Nook Color Android Development] mateorod:
Looks like you are missing glibc-dev. Did you install all the packages from the wiki? There are a bunch, but if you have java done, the rest is easy. What bit is your system?

Already happened. I actually included one in the source as well, but it looks like I may need to rethink that strategy, looks like I would need to require ant, maybe? Might just upload the binary to my repo and do it that way for now.

Either way, a release is going it tonight, and it will include a simple file manager. I like it because since I don't have WiFi, no file manager means an actually functionless tablet. I still don't understand how cm doesn't include their own. I am sure there is a good reason though.
[Nook Color Android Development] bodi524:
I have 64bit Linux Mint(the one based off Ubuntu).

I dowloaded Andbot to build CM10. I was able to build.

I figured that had all the packages for CM9-PA as well.

I removed andbot and installed all the packages from the wiki.

I am now syncing the repo from scratch and will try again.

Edit:

I reinstalled the packages. It was a pain to find Java6. Once I got the proper java I am off to make bacon :)

Compiling now. I have a really slow machine...its gonna be all night.
[Nook Color Android Development] mateorod:
Me too. One thing to recognize is that if it stops building due to a compile error, you don't have to start over most of the time. It is really just suspending the operation until you fix whatever the error is. Since I have been pretty active the last couple days, trying to get the repo finalized before I leave town, errors could always be merge related.

A good way to check that (again, if you have a error) is to reintitalize the repo (repo init -u etc.), repo sync again and then make bacon again. The repo sync will only need to pull down the latest changes, so it takes maybe 5 minutes to do the whole process. Make that your first thing you try if you get another error.

I will try and keep an eye on the thread to offer advice over the next week, but the best thing I can do is to get the tree in working shape. It should be there now, I don't have anything pressing on my action list.

This is what is new in the sources, some of it very recent

All-in-one sync. No extra file pulling steps

File Manager (by Open Intents, the latest version of the CM7 File Manager)

Superuser app is back (if you are building and didn't get it in your repo sync, just install it from Play. The binary is there)

Cleaned up PA mk files.

100% open source, from PA upstream and me here with the vendor stuff.

ParanoidOTA is gone. No more FC's.

QuickReboot is still needed (optionally needed, if that makes sense). Anyone with some ideas of how to fix the reboot menu, feel free to send pull requests or pms. The info is available. I spent my time getting the repos in order, so I haven't looked into this any more than where I was the last build.

HWA is commited. You tell me if it works.

Kernel now compiled with source...I used a premade for the last build.

More! Little things, froom administrative to best-ish practices.

Now, with all that said, the only things with this build you are likely to notice as a user is that OTA is gone, and that the File Manager has been added. But some of these things have best practice/benchmark-improvement-theory behind them, so this should be a better release, in invisible, trust your maintainer kind of ways.

I will, as I have said, be out of town starting tomorrow night. So help each other out, ok? Alright, go get get it.

What? Oh, yeah. It's at the Download Page right now.
[Nook Color Android Development] les02jen17:
Downloading it now. That was pretty fast! Thanks a lot! ;) :D
[Nook Color Android Development] bodi524:
I have PA 1.6a compiled and SuperCharged with auto-patcher.

I am going to start poking around with the reboot menu....I am new to Android programming

so it should be interesting.

Thanks mateorod for all the work setting this up. Paranoid Android is a great rom

and if you need help working with the PA for CM10 I will be happy to help if I can or test.
[Nook Color Android Development] mateorod:
Congratulations! All from scratch, if I remember. Not so bad, was it?
[Nook Color Android Development] bodi524:
All from scratch. I setup the build environment, did the repo sync and compiled.

The hardest part was finding the Java6 version for the build environment. The compile looks

for that version and bails if its not correct. Atleast it did for me.

Now I need to see if I can start getting my hands dirty down inside the code:D
[Nook Color Android Development] Tiezane:
Well, Mateo, following your directions, here goes nothing! First time I'm building a rom myself (well, sorta myself)!

Edit 1:

It seems to be hanging for quite a while at "target Dex: framework". Is this normal?

Edit 2:

Ok, it seems to still be running, but it's a P4 machine, so it runs a little slow. Will post when it's done.
[Nook Color Android Development] mateorod:
Be very patient with it. Good luck!
[Nook Color Android Development] halrulez:
You have a build guild mateorod?

I'm all thumbs.........
[Nook Color Android Development] les02jen17:
I'm getting really fired up with building and stuff and I just read the 2nd post... is it still relevant? If that's true, then it is indeed a very simple build process! I'm gonna try it out on virtualbox! :D
[Nook Color Android Development] Tiezane:
Package complete: /home/mike/android/system/pa/out/target/product/encore/pa_encore-1.6a-25SEP2012-201436.zip ! Adb pushed to the nook, backing up and flashing now! :fingers-crossed:
[Nook Color Android Development] Tiezane:
Had a couple of lockups, but wasn't in a position to get logs, will be later tonight or tomorrow (it's my anniversary today).

Sent from my Sega Master System via Carrier Pigeon.
[Nook Color Android Development] Quantumrabbit:
I've had numerous lockups,

I flashed the fixed GAPPS, but I am getting constant "Unfortunately, the process com.google.process.gapps has stopped. Did I flash the wrong GAPPs?
[Nook Color Android Development] Tiezane:
So, my build locks up as soon as I try to do anything with it. I tried to get a logcat, but it doesn't seem to have worked. Going to rebuild/reflash tomorrow and see what happens. I'm also going to try to configure my setup to run distcc, to hopefully speedup the build process. Wish me luck!

Sent from my Sega Master System via Carrier Pigeon.
[Nook Color Android Development] mateorod:
I have been getting some serious lock-ups as well. I installed the last build of CM9 though, and got them there as well. I am thinking about disabling OpenGL. I know that it has been enabled by default as they finish work on the kernels and CM10, but I never got the same performance with it.

That would kill standard flash, although it would still work with Opera.

Thoughts?

It should make the ROM much steadier and solid but I will defer to the users for the public builds and just go to non-OpenGL personally if that is the consensus.
[Nook Color Android Development] leapinlar:
I would vote for a non opengl version. Mine locks up all the time. And I love the PA features. I was considering going back to 1.5.
[Nook Color Android Development] jschill31:
+1 on this, flash is not worth the headache...

cheers
[Nook Color Android Development] davidr415:
+1 for non openGL
[Nook Color Android Development] mateorod:
Okay, polls close with a landslide. I will get something out soon.

Hopefully this will solve our issues. I had gotten the impression that OpenGL was pretty stable, but that wasn't the case for me. The older versions of PA were non-OpenGL, which I guess accounts for the big difference we have seen.

Confirming that the issues remained in the 20120904 CM9 was enough for me too. I got the idea (possibly wildly incorrect) that the GL was enabled in order to get a census on how well it works and find bugs. But since our data points are not useful in that respect (since determining if GL or PA is at fault is time consuming), I fail to see any reason to continue to struggle.

New build will be out in the next couple days, the source code will likely be adjusted sooner. If you are building from source, I will have those changes checked in today.

If you are not building from source, now is a good time to try, as the work on jellybean starts today or tomorrow. I tried to make it as clear and straight forward as possible, and I think i have done that.

Update: Sources have been changed to remove GL and HWX. If the need arises, I will create a new branch that will include those features, but the users have agreed with me that they are not worth the cost as a default option.

If you are building, you should be able to go ahead try it out. Due to my Nook's numerous hardware issues, I am relying on you guys for input, so please let me know about your experiences, good or ill.
[Nook Color Android Development] jschill31:
Hello,

I cooked up a version this morning without opengl, just have not had a chance to flash it yet. I only commented out opengl are you saying you changed the branch to take out it as well as hardware accelleration?

cheers
[Nook Color Android Development] mateorod:
Yep. If you repo sync, you will have basically the same effect. If you look through my commits, you will see that I reverted all of the HWA/D and OMAP_COMPAT as well. Most of the projects have been forked into my repo at this point for little changes like this.

I would recommend running a build off of the repo sync, but that is just because I have never flashed anything with the sort of mix-and-match of HWA settings you describe. But just shutting it off may work fine too. I did it this way as a better safe-than-sorry method, and because if we are trying to mitigate the freezes/bugs I didn't want to draw the process out. Better to go to a state we know is stable and work from there.
[Nook Color Android Development] pavlos46:
Ok if I may share my experience.

I have run PA for a couple of days and found it to not have HWA, and I experienced that when I was playing online videos where MX player would crash and turn to S/W mode. In normal CM9 0409 I found that the above didn't happen and videos would run in H/W mode but the built was generally very unstable, until I turned on force HWA in 2D apps in developer menu and everything turned on smoothly.

Now don't think I don't get my occasional crash but no more than once a day, so I strongly believe that the problem is not with. HWA bur lies somewhere else.

My 2cents.
[Nook Color Android Development] jschill31:
Hello,

Just an FYI my latest build flies...all I did was to change the commit under opengl from true to false and left all hardware acc. as is. I did a sync early this morning and before building went back in and changed the make file for the nook, only one line change. What you did is correct for all who are syncing without wanting to mod. I have no idea if there is any advantage to how I did it over removing both opengl & HWA but I have not had a single lockup since flashing and it flies.

Cheers
[Nook Color Android Development] mateorod:
Thank you both for the reports. I will leave the source as is for now and wait to see if anyone can report. Please keep testing your non-GL only build, jschill and let us know how it goes, but I AFAIK without GL none of the other features will work. I changed the settings completely to avoid mixed signals but have no real data on whether or not that is required.

I have taken your thoughts that OpenGL is not to blame under advisement. I suppose we can just wait and see how these builds with it disabled react. That would be the ONLY change, so we have a pretty pure laboratory. We will find out, one way or another.

I would appreciate the builders out there to give it a shot so we can have the data instead of rolling out a blind update. I may have a suprise coming up for those of you who take the plunge, as an incentive.
[Nook Color Android Development] Tiezane:
synch'd and building now.
[Nook Color Android Development] Tiezane:
Flashed and started testing last night, got sidetracked by a Co-worker's nook tablet and trying to un-bork it. It definitely ran longer than the last build without locking up, but I did notice that after a sleep (even a short one) produced a loss of wifi until I rebooted. Will look into more tomorrow.

Sent from my Sega Master System via Carrier Pigeon.
[Nook Color Android Development] mateorod:
I have put out an update on our download page at techerrata with no OpenGL or HWA.

If you are happy with the last update and use the HWA, then don't update as that is the only difference. I have titled the one from Oct07 as noGL, so it should be clear.
[Nook Color Android Development] leapinlar:
So far so good. Installed smoothly on my SD. No lockups yet and I usually have a lot. I LOVE this ROM.

Sent from my Nook Color running ParanoidAndroid and Tapatalk
[Nook Color Android Development] jschill31:
Hello all,

So has anyone looked into why reboot kills the OS? Also I have no problems using Quick Boot but it also seems to not boot into recovery. It is like the recovery flag is not present in the OS? Quick Boot reboots fine but choosing re-boot recovery it just reboots into OS. Checking for recovery flags is not something I know how to do if someone else can check....

Cheers
[Nook Color Android Development] mateorod:
Leapinlar-- Glad you like it, your opinion means a lot. You'll love the JB ParanoidAndroid, it is superior in every way.

As for the reboot issue, I cannot check that due to hardware limitations I can only use a bootable card recovery. But I can tell you how to check the recovery flags, if you wish. /rom/BCB is your boot control text file. Is anyone else having this problem?

4.1 Sources

Builders out there, if you want to try ParanoidAndroid 2.17, try these steps, which you can do right over your ICS sources.

repo init -u [url]https://github.com/mateor/android[/url] -b jellybean
repo sync
. build/envsetup.sh
lunch
make bacon

If you have any trouble syncing the source, you can consider syncing separately but it posed no problem for me. The only thing I had to tweak was renaming the kernel folder to "jellybeankernel" when I rolled back to ICS to build the latest update.

Notes

Jellybean is a work in progress for this ROM as much as straight CM10. In fact, if you look at the github manifest you can trace the lineage of this project. We are syncing 99.5% of the last local manifest that eyeballer posted, so remember the work of our encore CM10 team, especially eyeballer, keyodi, steven676, krylon360 and fat-tire. They have been pulling this hardware into the new day by force, and it has been neat to be around.

All of the rules (stern requests, let's say) for CM10 apply here. PLEASE don't post any zips, fat-tire's word carries weight around here. They have been working steadily on getting to the release, they will get there when they get there. I won't be posting a zip of JB PA until the CM10 has been out for awhile, so the only way to try it is to get your hands dirty.

ALSO: If you are running PA, you can report bugs and issues here. PLEASE (see all the caps I get to use?) don't clutter the dev thread with reports from the PA rom. They have enough ghost chasing going on over there, they don't need us to add to it, especially when it could very likely be our sources that are the problem.

There is a new ParanoidPreferences app, which you will find in the usual spot. I haven't predefined anything, let's figure this out together.

The last note on this is that we are using keyodi's 3.x kernel and the GL/HWA for JB. The consensus from above is that is the way to go. We can decide to roll back, but I am a little more hesitant about it as the whole point of CM10 is to get our device one more Official release.

Let's try and post logs and investigate the actual problems instead of working around them. Attach logs!

Good luck building, folks.

All sources are available on my github page, as in ICS I was forced to fork many of the projects. Go ahead and suggest code changes, the idea is a community effort.
[Nook Color Android Development] jschill31:
Hello,

Using the 3.0 kernel will limit some of the builders (and users down the road) much like those of us building CM10. Using the 2.xx kernel would limit some of the features but allow all (old & new) Nooks to boot.

Cheers