yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] mateorod:
Which Nooks do you know of not booting, old or new? If reports come in of some users not being able to boot, I will make arrangements, for sure. We have a bit of an advantage in that area, by virtue of my defaukt.xml. I will have to checkout upstream changes by hand for a number of projects, so in these early stages I will try and leave it in what is for sure a booting state. We can take the non-booting reports as they come.

As of right now, I have three confirmed builds and all boot for their owners. So we'll see.

There are some kooky things happening for my device, and I would love to see if others experience them. My nook has been ridden so hard that I don't know if they are just localized issues.

For instance, when you apply workspace or userspace changes in the ParanoidPreferences.apk, the changes require a reboot. On my machine, the device reboots into Cyanoboot, but then, quite oddly, boots into the stock bootloader for a instant, and then produces the Stock failed install screen.

After a hard reboot Cyanoboot returns and PA boots normally. I have also been having hard freezes on all Cyanongen roms, which are only resolvable by using a bootable CWM card, no flashing necessary, just a boot into recovery and remove. This has been happening regardless of build, and the device has only really been usable with stock. I have just discovered I can get around this if the usb is connected to my computer, which possibly extends to the wall charger.

This points to a bug in the kernel, I believe, although I can't swear to that. There are numerous hardware issues on my device that make it a unique case. Still, the whole picture is quite interesting, I am trying to get my head around the way a UI switch can cause the device to boot into two bootloaders in succession, one of which is supposedly buried deep in the protected read-only-memory.

Funky stuff. I should probably begin taking my own advice and start examining the logs, huh? I just have somewhat discounted my device as an actual development platform, since it has so many non-control disadvantages.

On the plus side, discovering the USB charging stops the black screens has allowed me to fully use this Jellybean build and I actually think it is way more usable as a daily driver than ICS.

EVERYTHING works better.
[Nook Color Android Development] jschill31:
If the black screen has been fixed for 3.0 we should be able to back-port it into the 2.xx kernel. One thing, I finished pulling your repo on the "ParanoidJelly" and for some reason it is giving the below error for me...maybe you are working on it?

Which would you like? [full-eng] 87

build/core/product_config.mk:199: *** vendor/pa/products/pa_encore.mk: malformed COPY_FILE "vendor/pa/proprietary/paranoid/ParanoidPreferences.apk". Stop.

Device encore not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).

Found repository: android_device_bn_encore

CyanogenMod/android_device_bn_encore already exists

Syncing repository to retrieve project.

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

Repository synced!

Looking for dependencies

Dependencies file not found, bailing out.

Done

build/core/product_config.mk:199: *** vendor/pa/products/pa_encore.mk: malformed COPY_FILE "vendor/pa/proprietary/paranoid/ParanoidPreferences.apk". Stop.

** Don't have a product spec for: 'pa_encore'

** Do you have the right repo manifest?

jim@jim-desktop:~/paranoidjelly$

Cheers:)

UPDATE:

Fixed and starting build
[Nook Color Android Development] mateorod:
This error has been fixed, thanks. A quick repo sync will put you right. A dumb typo on my part, did the exact same thing with ICS believe it or not.

You may want to look in your .repo folder for a local_manifest. When the error related to the pa_encore stopped that device spec from loading, it went and looked for on on CM. That project then gets put into a local_manifest. It is essentially forcing the build process to load roomservice.py to look for a matching device since the device we ordered with pa_encore had an error.

Delete the local_manifest, repo sync and you are good to make bacon.

Edit: I just saw that you had bolded some questions into the quoted text. I don't know if the kernel has any fixes in for the black screen reports or even if the issues I am having are the same as everyone elses since I was getting them on CM9 and PA, with or without GL or HWA. But I can run the Nook as long as I want when it is plugged into my computer by USB, that I found out today.

I did talk to eyeballer about potentially using the 2.6.32 kernel for stability purposes here in PA 2.17. But he recommended the 3.x, saying that sleep is fixed. My problems were all related to sleep, so if those problems aren't related to the kernel, they are probably related to my broken wifi chip or something. I used to incorporate software work-arounds to keep the Nook stable with this, but I have gotten lazy since I have had to flash so often and haven't wanted to keep editing my roms.

But sleep supposedly works on 3.x, so I am guessing the black screen SHOULD be fixed.
[Nook Color Android Development] jschill31:
Hello,

Thanks for the explanation. I did complete a build last night and flashed this am...booted just fine for me? I typically have nothing but issues with the 3.0 kernel, so the questions is what is different from current CM10 builds? This is running pretty good so far, no black screens and no kernel panics. I am at a loss, the only CM10 builds that work for me have the 2.xx kernel but yet this boots and runs good so far. I am as excited as it gets! Wifi seems to be a bugger getting it connected so I sugest once you do to leave it on even during sleep. I am going to run this through the paces today but so far it is what my Nook needed compared to CM10. I will test boot to recovery and re-boot to see if it works accordingly. One thing I do notice is the kernel only allows the Nook to OC up to 1gz instead of 1.1 or 1.2.

Cheers

Recent sync brings you up to 4.1.2 JRO03C!
[Nook Color Android Development] derekr44:
I've been using this as my daily driver since the mid-Sept release. I wanted to get some real good use out of it to give an opinion. With previous builds, it became less stable over time.

However, this one has been near flawless. I very infrequently encounter force closes, and I decided not to put v6supercharger on it just to see how it would preform. So far, it's been quick and snappy without it. I do get the reboot into recovery issue though with Quick Boot. It's not a big deal for me, as I can just use the N button to boot into recovery.

YouTube was extremely choppy until I tried your HW acceleration advice from a couple posts above. I enabled it in the Developer Options in Settings. That made all the difference, as now I can even run HD vids from there without a stutter.

Mateorod, I haven't encountered your issue with the app settings. Whenever I make changes, it applied instantly without the need of a reboot.

I've just recently tried to build my own with your Git. Haven't flashed it yet, though. So I guess I'm still in ninja training.

Side Note: Anyone know of an app, besides Nook Tweaks, that allows voltage changes for this ROM? All the one's I've tried don't allow it (SetCPU, ROM Manager, System Tuner, etc). Thanks!
[Nook Color Android Development] jschill31:
Hello,

The boot into recovery works on this build but with TWRP unless the usb is plugged in it jumps around to other functions that what you are selecting. Possibly just a glitch this one time but boot menu works and that is a BIG bonus.

Cheers
[Nook Color Android Development] Tiezane:
Error during lunch with PA 2.17

See here: http://pastebin.com/5pmJ7qNQ . did the repo init and sync this afternoon, did the . build/envsetup.sh and lunch, picked 87, hit enter, and bam. Any ideas?
[Nook Color Android Development] mateorod:
Shoot. I guess i should make this clear, i kinda just assumed the info was out there...unfortunately you are running 32 bit Ubuntu but Jellybean needs 64 bit software. You do have a 64 bit processor, at least.

If you are running a VM, i would just say start over with a 64 bit image. If not, well, depending on your partition layout, upgrading CAN be easy, it just depends if you have your home folder and etc on separate partitions.

I have heard from pretty insistent sources that a workaround to build on 32 bit OS exists, but i haven't looked into it personally.

If you plan to continue android developing, might as well bite the bullet and upgrade now. It isn't gonna get any less painful and it is going to be all 64 bit from here on out.
[Nook Color Android Development] Tiezane:
I have one system capable of 64 bit, and that's my laptop. My other 3 PCs are all 32 bit. I'll have to get the Ubuntu install on the laptop fixed up, something killed my wireless connectivity on it. Back to trying to figure out the boot menu on 1.6a for now.

Sent from my Sega Master System via Carrier Pigeon.
[Nook Color Android Development] Quantumrabbit:
So after upgrading to TWRP 2.3.0.0... I can flash NC-MROM, Mirage, gapps for both, my flashable cyanoboot... all fine.

After flashing both pa_encore-1.6a-24SEP2012-091922.zip and pa_encore-1.6a-OCT082012-noGL-202641.zip... neither boot. I waited 20 min on Oct 8, both with and without GAPPS... and over an hour on Sept 24, neither gave me so much as a logo after the cyanoboot screen. I had previously (I think on CWM 3.2.0.1) flashed the sept just fine.

Not sure where this is a TWRP potential bug, or a potential bug with those zips... figured I'd start here since both NC-MROM and Mirage boot just fine.
[Nook Color Android Development] mateorod:
Well, you know your systems best. But this from your paste leads me to think you have a 64 bit processor:

although maybe that is misleading.

Try this if you are unsure:

more /proc/cpuinfo

If you see a lm flag (for long mode) that's 64 bits.

Here's mine:

flags	: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx [SIZE="4"][B]lm[/B] [/SIZE]constant
_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl es
t tm2 ssse3 cx16 xtpr pdcm lahf_lm dtherm

If you see pm that would mean protected mode, which is 32.

An FYI to anyone who may not know if they can run 64 bit images.

Edit:

I guess we cross-posted this one:

Well, for one, you should never wait more than 15 minutes, and even that is too long. But that is odd. The only TWRP report I have gotten is some phantom touches when running the jellybean builds, but I don't think anything we build is active in recovery. We don't have any recovery resources being built with this rom, unless they are part of a project that slipped by me (possible, always).

If you would like us to look deeper, we would need logs from the loops, though. Thanks for the report, either way. I know that they have had to check in TWRP support at various points. But since I am pulling from the exact CM10 manifests, with only minor variations on my forks, I don't see why I would be missing any of those commits.

Luckily, we have a TeamWin member on staff here at ParanoidNook headquarters. If anyone wants further investigation on this issue, I will page him to the help desk only on receipt of logcat.

Edit2: I just realized that you are referencing PA1.6. Most of the above still applies, but there are some places I can look to see if I missed TWRP-related commits.with this one. Less of a manifest overlap there. Still, logcats would be our best bet at pointing toward a solution.
[Nook Color Android Development] grayfoxmg1:
I have on my Nook, CWM 3.2.01 and have used it to flash the 1.6a-24sep2012.zip along with the gapps from mateorod. So I can tell you that it works(quite spectacularly I might add). Which Nook do you have? Old/New/ or that weird in-between model? the easiest way to tell is to look at your partioning, The Old model(mine) is originally set up with 1GB of app data and 5GB of EMMC storage. The New Model was almost reversed with 4GB of app Data and 2GB of EMMC storage. Now I don't know what the ratio was for the in-between model, and I may be off buy a gig in one direction or another on the New model.

When you flash are you doing a complete /data wipe? or just wiping your caches? Have you been running the ROM .zip through any customizing software or scripts(auto_patcher is an example of a customizing script)? Walk us through your flashing steps starting at when you download it from mateorod's server.
[Nook Color Android Development] halrulez:
TWRP has its problems cwmr is alot more stable. Although I would love to use twrp, just doesn't work well with everything. Kinda sad. Never really wiped correctly, to as I remember.

I'm all thumbs.........
[Nook Color Android Development] boyoboyo:
Same just happened to me. To work this out I made a bootable cwm recovery SD using the usual method. That's the only way my nook would even light on the screen. Maybe something went bad with twrp that messed up the boot. Anyway I also have put the paranoid image and gapps and flashed from the cwm sd above (formatting data, cache, dalvik, system prior).

---------- Post added at 10:33 AM ---------- Previous post was at 10:23 AM ----------

What update are you using? pa_encore-1.6a-24SEP2012-091922.zip?

Thanks :)
[Nook Color Android Development] Tiezane:
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat

pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe up pebs bts cid xtpr

x86 actually indicates 32 bit, not 64 bit. This is an older P4, so it doesn't have the x86-64 extensions. It's a shame, but I did try to install the 64 bit Ubuntu 12.04, and it was a no-go.
[Nook Color Android Development] eyeballer:
Can you pull the recovery.log after trying to flash the zip and pastebin it. You can PM so not to clutter up this thread.

So: try to flash then 'adb pull /tmp/recovery.log' or in advanced you can use the copy log to sdcard button then copy it from there.
[Nook Color Android Development] jschill31:
Hello all,

I have one of the "in-between" Nooks and I can confirm that this build not only flashes fine in TWRP 2.2.2 but actually runs excellent. I have never had issues with TWRP wiping, I believe that rumor was started actually back in the Clockwork 2.xx days. I have had only (1) black screen while unplugging the AC charger in the past 30+ hours. This is by far the best build out there of Jelly (4.1.2) for my Nook. I will continue weekly building this (rather than CM10) going forward if (and when) we are allowed to post builds. My Nexus 7 arrived last night and I plan on concentrating on that for now. Man is it fast...unlocked bootloader, rooted and recovery in less than 2 minutes.

Cheers
[Nook Color Android Development] Quantumrabbit:
Sent. Thank you.
[Nook Color Android Development] WJThomas:
Success! I was able to get my VM setup and build PA1.6. Flashed and running right now.

Thanks to mateorod for the super easy setup, and the link on installing the jdk.

While I play around with it, I'll try to build 2.17.
[Nook Color Android Development] mateorod:
Congratulations and welcome to the club! This is what it is all about, for me. In six months time I could be using your ROM as a daily driver.

You can run the repo init command right on top of the ICS sources, changing the ics to jellybean. Then you can switch back and forth in the same manner.

When I rolled back to ICS I had to incorporate a little shenanigans to keep it working

retitle the kernel folder 'jellybeankernel'

When I return to Jellybean from that, I imagine I will probably have

title my new kernel folder 'icskernel'

rename 'jellybeankernel' just 'kernel'.

But that way I only have to pull down changes and can save significant space on my hard drive.

None of that is needed to pull the jellybean sources, I only mention it in case there are others out there who may want to switch back and forth from ICS to Jellybean often. Tiezane comes to mind, who is working on the ICS power menu for us.
[Nook Color Android Development] davidr415:
Could you share the link for installing the JDK?
[Nook Color Android Development] mateorod:
I have added the link to the build instructions on post 3. Like I say there, I install the JDK to the traditional /usr/local/bin, but this guide 100% works as written.

Since we have plenty of confirmation that the jellybean branch is working for any number of Nooks, I am going to start pulling updated commits from the various projects and catching us up to 4.1.2. GL is still not enabled in the device repo, but if and when it is I may create a branch and manifest for those who have trouble with stability.

They guys have been putting in a bunch of time and effort on CM10, so thanks are owed to them. I am planning on giving their recommendations on kernel and HWA/GL long trial periods before we change anything here. They know what they're doing.
[Nook Color Android Development] Tiezane:
Working on is a lose term for it, I'm going to hack around through stuff I have no idea about until I find something that makes less sense than all the rest, and see if that fixes it :)

Sent from my Sega Master System via Carrier Pigeon.
[Nook Color Android Development] pavlos46:
Hello,

Just a quick question on the JB version for whoever has already built that does flash player work?

Thanks
[Nook Color Android Development] boyoboyo:
New to this whole build thing...

Trying to sync JB from meteor git. However, it seems like the .repo directory is pretty bloated. It's about 17.6 GB at the moment. Is this normal?
[Nook Color Android Development] runningslow:
I'm going to try my hand at building this weekend. I've been debating between dual booting my desktop and using VirtualBox to install Ubuntu. Recommendations?

I don't see this in any of the guides... any tips on a setup for VirtualBox? How much hard drive space should I allocate? Is there a minimum amount of RAM that should be allocated? How much swap space is recommended?
[Nook Color Android Development] runningslow:
Thanks for the great response. I'm not a complete Linux noob, but I do use Windows as my daily. I've dabbled off an on for years, installing just about every distro under the sun: Ubuntu, Fedora, Gentoo, Arch... always went back to Windows for one stupid reason or another.

Wubi might be the way to go, but perhaps I'll just wipe my laptop again and install Xubuntu (I hate Unity).
[Nook Color Android Development] boyoboyo:
Oh wow haven't realized such specs are required. I don't run my linux distro from a VM. However it's in a separate partition with only ~30GB for the /home partition. Also I have only 2GB of memory. Guess I'm out from the game until I build a suitable linux box. Hopefully not for long.:(

---------- Post added at 07:01 PM ---------- Previous post was at 06:48 PM ----------

It shouldn't be a hassle to get a proper linux distro nowadays, even if you need Windows.

Instead of Wubi, have a setup that is independent from grub (such as using EasyBCD). It's not so difficult once you get the hang of it. That way you can remove the linux distro without affecting the bootloader. There are more ways to make your life easier 'with linux.

Sorry for going off-topic here. Just wanted to encourage the building process :)

P.S.

I'd recommend Mint 13. It's ubuntu-based, but without Unity and a lot more benefits.
[Nook Color Android Development] les02jen17:
I flashed the latest PA (10.08.12) and got stuck in a blank screen upon boot. It stayed there for like 15 minutes. I flashed just the .zip via CWM 3.2.0.1 without flashing gapps. I did it after a full wipe (cache, data, system) cause I came from MROM a CM7 Kang. Is it because I neglected flashing the gapps, or something else? Thanks!

Tapatalkin' it from my BlackBerry 9700
[Nook Color Android Development] Robertjm:
missing menu button??

Hi all,

I blew away the old CM9 nightly I had since January(ish) and installed ParanoidAndroid today. Then I went and installed some of my older apps.

One problem I've discovered is there is no soft menu button on the bottom of bar, just the Back, Home and Recent Apps buttons. Is it just turned off somewhere, and I need to turn t back on, or is it not included?

Was trying to reinstall some apps I bought through the Amazon Appstore, but without the soft menu button I have to call up each program manually. Bit of a pain.

Hopefully, it's just something I'm missing.

Thanks for reading.

Robert
[Nook Color Android Development] Cap18k:
The recent apps and soft menu are combined. Just hold the recent apps button to pull up the menu.
[Nook Color Android Development] mateorod:
I don't remember ICS ever having a menu button. Either way, it has been gone from Android UI for a long time now. The official position is that they are trying to encourage appsto lose it as well and use tabs or other solutions. I think it is an attempt to simplify things, although of course many apps still have them.

I don't know what to tell you about Amazon app stores restores, i am not quite sure what you are tallking about. But it will be this way on any rom you use on 4.x.

Edit: the above poster is correct, of course. But this is a PA, not Android, feature.

For those of you reporting install issues, eyeballer has looked at it some, and was hoping you could test this new updater binary. Just replace the one in your zips. You'll find the original at META-INF/com/google/updater-binary.

http://techerrata.com/file/twrp2/utilities/update-binary
[Nook Color Android Development] Robertjm:
Thanks guys. I was running one of the early versions of CM9 so perhaps the menu button got lost somewhere between then and now. Thanks for the pointer on long pressing the previous apps button. That did the trick in the Amazon Appstore just dandy.

Is the Long Press time length adjustable? It'd be nice if it were a bit shorter than it seems to take. In any event, I appreciate your effort. It's running a lot better than the previous ROM was.
[Nook Color Android Development] jimbobcooterrooter:
Just flashed ParanoidAndroid 2.2.0 after a successful compile. It is amazing. Didn't think it'd be this slick. Also didn't expect the build to go flawlessly. Major props guys
[Nook Color Android Development] WJThomas:
When I sync, I get random errors. Usually 'Couldn't resolve host' or a 403. When I do a second sync, those projects fetch OK but others have errors.

I assume that as long as I get a good fetch of each project I am good to proceed with the build. My build seems to flash and run the same as the posted builds, so I think this confirms it, but I ask in case others are experiencing the same issues.
[Nook Color Android Development] boyoboyo:
So... how much does the .repo dir take after sync. Just wondering how much space to allocate.
[Nook Color Android Development] WJThomas:
The ICS .repo is about 5.7 GB, the whole development tree is about 11.5 GB after sync and 23.7 GB after build.

The JB .repo is about 8 GB, the whole development tree is about 18.8 GB after sync and 31.5 GB after build.

Also, my VM had only 2 GB RAM and I was able to build ICS just fine. I have since increased it to 4 GB RAM.
[Nook Color Android Development] WJThomas:
I'm getting this error with the lunch menu for JellyBean.

Which would you like? [full-eng] 90
vendor/pa/products/AndroidProducts.mk:111: *** missing `endif'. Stop.
Device encore not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).

I tried a clean sync, but the error is still present so I just added the missing endif myself.

makin' bacon as I type...