yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] chopsticksny:
so how am i suppose to play flash with this rom?
[Nook Color Android Development] krylon360:
Flash is avail for <=ICS fingerprints.

However, for right now I'm not sure if PA 1.6 has the changes I built into CM9 yet or not which fix HW Decoding and Flash support.
[Nook Color Android Development] leapinlar:
Just because Adobe stopped offering Flash Player on the Play Store does not mean you can't run an earlier version on your Nook. There is a site that archives older versions of free software. You can get older versions of Flash Player here:

http://www.freewarelovers.com/android/app/adobe-flash-player

Edit: Opps. It looks like all the prior versions got removed, Maybe by request from Adobe. Sorry

Edit2: I just uploaded to a fileserver my version which is 11.1 and it runs great in Opera. (Link removed).

Edit3: Just found another site that has archived free apps. iapktop.com. Here is a direct link to flash player for android 4.0+.

http://dl.apktops.com/app/201208/Adobe_Flash_Player_11.1.115.17.apk
[Nook Color Android Development] -somebody-:
im about to head out for a few hours but if im not too tired when i get back home ill upload the adobe flash apk, i know i have the most recent one in one of my backups on my phone, its just a matter of restoring each backup until i find it lol
[Nook Color Android Development] chopsticksny:
got it thx.:beer:
[Nook Color Android Development] mateorod:
As a general announcement, we will be updating for ICS as least once more, with hopefully at least a fixed reboot menu on PA's end.

BUT! Krylon360 has generously agreed, previous to this discussion, to let us sync from his ICS repo, which has the mentioned fixes, plus. So Flash shouldn't be tethered to Opera for the next build. I am going out of town next Tuesday for a week or so, so I will put the build out a couple days before that so I can be there for at least initial support.
[Nook Color Android Development] travisn000:
Does USB host work with this.. just bought an adapter that works on my gnex, but cannot get it to work here.

Thanks.
[Nook Color Android Development] grayfoxmg1:
Question: Does the Paranoid Android OTA actually work on our device?

Supplement #1: If so, than I am having a small (read microscopic) issue (read annoyance) with it FC'ing on start.

Supplement #2: If not, than how does one go about removing it? and perhaps you should look into excluding it from your build.
[Nook Color Android Development] mateorod:
No, it is no longer supported. remove it with titanium backup or something,

I pulled it out of the zip, but I guess I had my wires crossed when I picked the folder to upload. It and Paranoid Backup are pretty much dead. They will be gone next zip, like I said several posts ago.
[Nook Color Android Development] grayfoxmg1:
oh okay, guess i didn't see that post. Sorry 'bout that. That little foible aside, I am still loving this rom.
[Nook Color Android Development] Jainyankee1993:
this rom doesn't boot for me?!?! just reboots into recovery like nothing was flashed.
[Nook Color Android Development] leapinlar:
Booting into recovery means you are in a recovery bootloop. Look at my tips thread linked in my signature to find out what that is and how to get out of it. Look at item A8.
[Nook Color Android Development] Ahiko:
I flashed the ROM first and the gapps-fix right after, but after it finished updating, the screen freezes and the transition animations from switching between home screens stays stuck. I cleared my cache before flashing it too.

Reverting back to the triple boot CM7/CM9 ROM until I can figure out what's wrong.

Should I burn a different .img to the SDcard to make this ROM work? I'm really hoping to try this out since the non-rotating home screen and app drawer was driving me crazy!

Keep up the great work! :)
[Nook Color Android Development] routey:
post deleted
[Nook Color Android Development] DizzyDen:
mateorod... I have pulled them from the pa_encore-1.6a-14SEP2012-171646 zip file if you'd like me to upload... also if you would like help with the project I'd do what I can.
[Nook Color Android Development] Jainyankee1993:
question guys. so i want to flash this rom on top of my stock nc rooted, when i wipe everything, system cache, and dalvik, it doesn't boot up, and it just boots into recovery. if i wipe just cache it boots me into some type of hybrid between the rooted stock, and this rom, and barely anything is working. How do i exactly flash this rom?
[Nook Color Android Development] leapinlar:
You need to do a cleaner wipe (you did not say you wiped /data which is probably the source of your problems). Also I have found that CWM sometimes does not wipe well enough, especially on the newer nooks. I developed a tool to format /system, /data and /cache. Go to my tips thread linked in my signature and you will find a zip there that says format partitions 5, 6, and 7. Flash that zip with CWM and you will have a clean nook. Then flash the PA zip with CWM and hopefully that will be better.
[Nook Color Android Development] mateorod:
I don't think that we need a brand new upload, although if you want to post it you certainly can...I will be updating before the end of the weekend, and they will be gone then, in either case.

As for any offers of help, they are always welcome. I am all about community projects. I tell you what, I will upload the source to Github soon and we can take it from there. My contributions are mostly just make files at this point, along with the pad.prop stuff.

The issue we have faced is how much time do we really want to devote to a dead branch? I have built for CM10 (the last PA for CM10 I built was 1.99, and I think P.A is now at 2.2x.) The amount of work that just our team has in front of them with CM10 coupled with their number has made it a long project.

I will upload the current ICS tree this weekend as well. But I may as well put together a repo for CM10 as well. We won't release any zips until CM10 itself has come out, but at least this way we won't be starting from scratch. You never know, maybe we can do some things to contribute back to main Encore team.

The hardware stuff they were working out the last I saw was stuff I won't be much help on, so who knows. Let's see what Eyeballer thinks, and in the meantime, I will put up PA 1.6.

As far as the issues we know about, the reboot menu specifically, the needed overlay is present in the framework-res config.xml. Krylon said it looked as if the base was overriding our overlay and that additional overlays were needed. That sounds to me more like a bug in PA that should be fixed as opposed to making additional overlays. We can look at both of those options and see what we can see. I'll post here when I get the repos sorted.

Let me add that it should go without saying that this is an open solicitation for contributors. If you are at all interested, come check it out.

Hybrid of cm9 and rooted stock? You should bottle that and post it, people have a right to see!

We switched download pages to try and end some confusion, as well as eliminate the need for a two-person upload process. But maybe that was a mistake...are you getting the ROM from here?

It probably doesn't help that since they closed the PA ICS repos, all the releases are stuck on 1.6, no matter the changes from us here downstream.

Edit: I just saw Leapinlar's post, and he is correct, you do need a complete wipe. PA 1.6 needs what they call "God mode" due to build.prop info and other things.
[Nook Color Android Development] Jainyankee1993:
thank you very much kind sir! IT WORKED! :)
[Nook Color Android Development] mateorod:
Sources for PA 1.6a for encore are up.

Here is the vendor directory, which is where the differences from other trees were needed.

I set up a default.xml for this as well, which should mean that building and syncing will be REALLY easy. I also added a README to the above vendor repo with instructions. The instructions are based on the supposition that the default.xml is correct, which it might not be. Untested at this moment, since I literally edited it in place on Github, while making some underinfomed guesses about how default.xmls work.

But it looks ok to me.

Here is the shorthand for anyone who has a build environment set up. For those that don't, follow this wiki and stop immediately after this line

And instead do this:

cd <working directory>
repo init -u git://github.com/mateor/android.git -b ics
repo sync

Connect device w/adb

cd vendor/cm
./get-prebuilts
cd ../..
. build/envsetup.sh
lunch

[pick whichever number pa_encore_userdebug is. It should be the last on the list (it was 42 for me)]

make bacon

And pick your ROM up in out/target/product/encore when you're done.

This is pretty easy stuff, no local_manifest.xml or proprietary file pulling or prebuilt app installing. You should try it if you have a build environment or even if you don't. Any mistakes should be easy enough to fix, so there won't be any wasted time, even if I did make a mistake.

I was going to sync to krylon's repo, but I didn't see any differences, so I left it as is until krylon makes a recommendation. I also have you downloading and attempting to build the kernel, but it will go ahead and use the prebuilt if that fails, so no harm no foul either way.

Anyone who can or would like to contribute, this is an open project. I spent the time setting it up in the hopes some of you would give it a go.

We'll go ahead and start Jellybean next week. Sound ok?

Edit: I reread this post and decided I need to be clear that we will start work on Jellybean, but the decision about when to release a zip is still going to be up to fat-tire. He absolutely has everyone's best interests in mind. But the source will be public, and the directions easy, so everyone will be encouraged to build their own.

I will say this, PA has matured incredibly since 1.6 and you will have something unique to try should you attempt the builds. But more on that later.

Once cm10 zips are okayed, we'll talk to eyeballer about PA zips.
[Nook Color Android Development] routey:
i dont know bout the others, but it sounds like christmas came early!! :angel:

thank you SO much mateorod :good:
[Nook Color Android Development] les02jen17:
Just wanted to point out that downloading on techerrata dot com seems to be incompatible with using a download manager. I tried both Internet Download Manager/Jdownloader and I get the same result: stuck at 99.99%. Refreshing the link does not make the download continue. The link does not go dead--for some reason it just won't complete. Tried downloading other builds on a different site (example, goo im) and it worked with the download managers just fine. Of course I can't just request to have it mirrored somewhere else. :P But yup, just a heads up for the people who would be downloading the builds cause I was really annoyed when I got stuck at 99.99%... I mean, who wouldn't? :silly:

Also, I've noticed that the previous builds has been removed. Does this mean that the only thing that we flash, say for example we're doing a clean install, would be the 1.6 build + gapps? No flashing the previous builds anymore? If that's the case then thank you so much for making it really easy to install this time! :laugh:
[Nook Color Android Development] jschill31:
Hello,

Thank you for setting up a repo so that we can build this project on our own. While syncing I have been receiving several errors so you may want to check a few things:

error: Cannot fetch nemith/android_vendor_bn_encore| 1.21 MiB/s

error: Cannot fetch CyanogenMod/android_prebuiltiB | 1.11 MiB/s

Fetching projects: 96% (244/254) error: The requested URL returned error: 401 while accessing https://github.com/nemith/android_vendor_bn_encore/info/refs

Fetching projects: 97% (247/254) error: The requested URL returned error: 401 while accessing https://github.com/CyanogenMod/android_prebuilt/info/refs

I believe that 401 messages populate when the file is not found as well as when there are traffic issues. I have never been good with Git so these may be nothing, I just thought I would let you know. The messages above have repeated several times during the sync.

Cheers
[Nook Color Android Development] davidr415:
Mateorod,

Will there be a new zip posted before you leave town?

Hope so.. great ROM..
[Nook Color Android Development] mateorod:
Let me look at this with eyeballer- I have a bunch of stuff at techerrata with great results, but this is a big file...and the other builds are just at a different download page, but this is exactly why I moved the page. That page had builds with confusing naming practices (my fault) and of course the wack install routine.

The new builds will all be at the page linked in the OP, and you should be able to install them no problems.

If you finish the sync, you will still need to install the proprietary files like on a normal build. I am actually tidying up the default.xml right now, it had some errors on it. I wanted to get the sources up, and providing the default was a last minute idea. But I am almost done, and it will be the easiest build you guys will find for the Nook. The prebuilts are the last thing that need to be sorted. I don;t know when this happened, but I guess Cyanogen pulled the prebuilts from their github, and so the we need to point to aosp source. I am experimenting with it right now, and I will update or post when the xml is finalized. I am glad you are getting onboard!

edit: and you must have much better internet than I do, those are the two problem areas (I have the vendor props fixed, the prebuilts are testing right now). My internet will add another traffic related issue every 100 projects or so...
[Nook Color Android Development] jschill31:
Hello,

I have smoking internet service, typically 50+mbs. It sure makes it nice when pulling sources. :laugh: I even see spikes nearing 100mbs after 10pm which is when I get time to work on these. Back on topic: I have yet to get the repo to complete. I have tried it numerous times today and it continues to bounce those two.

Cheers
[Nook Color Android Development] mateorod:
I am 93% sure that the default.xml is finished. The bad news is that you may have to start over. Try deleting the .repo/projects/prebuilt folder, and reinitialize the repo (repo init -u https://github.com/mateor/android -b ics) and then repo sync. Once the projects are all checked out, I can pretty much get you back from anything, but repo itself I have only used here. There is probaby a repo forall command, but whatever.

There has actually been a bunch of movement on the source .xmls, and so a bunch of these are actually incorrect all around github.

Let me know how it goes, my goal is to have a new build and JB sources up and running before I go. The repos will be completely tested by this time tomorrow, so if you just want to wait until I am 100%, that is fine too.
[Nook Color Android Development] jschill31:
Hello,

Looks like you have it cleaned up and syncing now. Just finished checking out and will try a build.

Fetching projects: 100% (253/253), done.

Checking out files: 100% (4743/4743), done.ut files: 41% (1946/4743)

Checking out files: 100% (9386/9386), done.out files: 32% (3013/9386)

Checking out files: 100% (5365/5365), done.

Checking out files: 100% (426/426), done.g out files: 3% (16/426)

Checking out files: 100% (8312/8312), done.out files: 17% (1429/8312)

Checking out files: 100% (1421/1421), done. out files: 34% (485/1421)

Checking out files: 100% (24618/24618), done.ut files: 40% (9892/24618)

Checking out files: 100% (19770/19770), done.ut files: 0% (13/19770)

Checking out files: 100% (557/557), done.

Checking out files: 100% (31645/31645), done.ut files: 19% (6043/31645)

Checking out files: 100% (499/499), done.ng out files: 0% (2/499)

Checking out files: 100% (33094/33094), done.ut files: 0% (20/33094)

Checking out files: 100% (2997/2997), done. out files: 1% (39/2997)

Syncing work tree: 100% (253/253), done.

jim@jim-desktop:~/paranoid$

Cheers

Update:

Looks like there is still an issue with one of the dependencies: nemith/android_vendor_bn_encore

Which would you like? [full-eng] 44

% Total % Received % Xferd Average Speed Time Time Time Current

Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0

curl: (22) The requested URL returned error: 404

Server does not provide clone.bundle; ignoring.

error: The requested URL returned error: 401 while accessing https://github.com/nemith/android_vendor_bn_encore/info/refs

fatal: HTTP request failed

Looks as if it will let the build start but I have a feeling I will be met with an error message when I wake up in the morning...

I will let you know either way

Update 2:

Well that did not take long to error out, here is what it stops at:

make: *** Waiting for unfinished jobs....

Notice file: hardware/libhardware_legacy/NOTICE -- out/target/product/encore/obj/NOTICE_FILES/src//system/lib/libpower.so.txt

jim@jim-desktop:~/paranoid$

Just so I am clear, do I need to add something to your set-up before building? You did make a reference to needing proprietary files but my device folder is full?

So I did delete the folder and redo the repo pull and I still get the exact same error:

https://github.com/nemith/android_vendor_bn_encore/info/refs

Is there only 252 files or should there be the full 254 that it tries to pull?

Cheers
[Nook Color Android Development] mateorod:
There should be 254 projects..you might be able to solve that make error by pulling the proprietary files from the Nook as usual; once this is fixed that will longer be necessary.

Edit: Found the error, I keep editing in place because the damn thing only needs a line changed here or there, and it keeps showing me what a bad idea it is. But then I just want to clean up a small stupid mistake, so I do it again and...arghghghghyg. The whole repo is getting replaced early tomorrow morning, I want that history gone, lol)

That address for the proprietary files is wrong and has been changed in the github version. The problem is that I fixed it early this afternoon, so the reference must still be somewhere else besides in the project file. I am still syncing a fresh repo, so I am not certan that it is fixed, but it looks right.

You might just be best off starting completely fresh, although I do believe that you could build if you pulled those files off your Nook. libpower.so is a prop file, for example.

Hopefully, one of use will wake up to success tomorrow...you could also clone any missing projects by hand, but with your internet, the path of resistance will probably be starting fresh.
[Nook Color Android Development] jschill31:
Hello,

Will do one of the options, thank you for your hard work. Reading through lines of code is never fun.;)

Update:

I was just thinking about this more and I do not think starting completely over will have any affect if the reference to https://github.com/nemith/android_vendor_bn_encore/info/refs is anywhere upstream in your code. I think the only way the repo will repair is to remove all references to this or to satisfy whatever it is looking to download. I did do a git reset hard but the reference still pops up.

Cheers
[Nook Color Android Development] mateorod:
It is gone. The only place it was left was in the vendorprops, which would give you some error messages after lunch, but ultimately allow you to build. Now, I started my initial build as of this morning, so we'll see. But as long as PA doesn't choke out looking for OTA or Backup apps, we'll be fine.

I had moved from syncing from some random person who had forked that repo to nemith, but nemith had his tree somewhat different and I hadn't noticed. Cyanogen removing the prebuilts from githb last week didn't help. The rest was a comedy of errors...but the syncing goes through no problem, finally. If you get an error message after lunch, that just means you missed the last commit to vendor/pa/vendorprops/encore.proprietaries. But all that file does is check for the presence of the prop files, and move on once they're found.

Thanks for the tests, you'll likely know how the builds go before I do as I am running it on my build server, which is an older machine. But the sources haven't changed much, just some tidying up to get us ready as a repo.
[Nook Color Android Development] jschill31:
Hello,

Not sure if I will need to delete everything including all folders and my bin file but I still have the error from nemith when trying to sync:

Fetching projects: 99% (253/255) error: The requested URL returned error: 401 while accessing https://github.com/nemith/android_vendor_bn_encore/info/refs

fatal: HTTP request failed

remote: Counting objects: 11, done.

remote: Compressing objects: 100% (5/5), done.

remote: Total 8 (delta 6), reused 5 (delta 3)

Unpacking objects: 100% (8/8), done.

From https://github.com/mateor/android_vendor_pa

f2efa50..b412fbf ics -> github/ics

error: The requested URL returned error: 401 while accessing https://github.com/nemith/android_vendor_bn_encore/info/refs

fatal: HTTP request failed

error: Cannot fetch nemith/android_vendor_bn_encore

error: Exited sync due to fetch errors

I hate to dump everything but there must be some reference to the above in your git. I just tried to sync in the past few minutes so I there there must still be ghosts.

Cheers
[Nook Color Android Development] tambourineman86:
Just wondering if Netflix works on the latest build. It's a must-have for to my wife and kid. Sorry for the noob question
[Nook Color Android Development] mateorod:
There is a reference to it in your local version, somewhere above the projects directory (not your bin, though. Somewhere in the .repo folder. But I haven't been able to find it). If we were just dealing with git, I could back you out of it, but I just don't know repo that well.

My build synced and finished. The only change is that you WILL have to pull the cm proprietary files (Rom Manager, Terminal Emulator). I had meant to set it so you don't have to do that, it just isn't done. I am thinking about it.

After sync, but before build

connect a CM-running device into computer through adb

go to vendor/cm and run

./get-prebuilt

I can't test this myself (no wifi), but they should be working on the released build. It looks like fat-tire's repo has the HW acceleration commits.
[Nook Color Android Development] tonyp:
Just one note to you guys. As mateorod knows I'm offering ParanoidAndroid ICS builds as well for my phone.

I wouldn't remove the ParanoidAndroid Backup app. Sure it doesn't get new updates anymore but it's working flawlessly.

Without the app you have to manually re-configure your ParanoidAndroid Settings after each ROM flash (or at least manually restore the pad.prop file).

If you keep the app it will automatically launch and offer you to restore your settings after flashing a new build. And it's a handy app to save different dpi/layout profiles :)

If you guys have any dev questions about PA ICS don't hesitate to send me a PM. Unfortunately I don't know where exactly your dpi problems are coming from, for my hdpi device everything worked out of the box.
[Nook Color Android Development] mateorod:
Oh yeah? I thought that was DOA. Learn something new. I put it back tonight. The DPI stuff is fixed, all we have really bugging me is something over rising the power button reboot menu.

It is in our overlay. One of our guys said he thinks the PA stuff is overriding the framdwork-res overlay, but I haven't found put where. Haven't looked super hard yet either, though. I made an invisible power button for the SystemUI, but it didn't work as well as I had hoped, so I yanked it. Thanks for the tip on the backup app.
[Nook Color Android Development] zagzag99:
Looks interesting ROM to use.

But I can't get the wifi to connect.

It says "connecting" but then drops out and remain at "Saved..."

Router logs show no indication of an attempted connection. (WPA2)

Edit: problem is with the /system/etc/wifi/tiwlan.ini

You have there WiFiAdhoc = 1 and when set to 0 I could get to my AP.