yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] leapinlar:
More good news. I set Opera Mobile to tablet GUI, 128 dpi, upgraded to latest flash player 11 and lo and behold, flash works! This with mateorod's non-opengl base.

Sent from my Nook Color running ParanoidAndroid and Tapatalk
[Nook Color Android Development] davidr415:
Can someone comment specifically on general performance.. "smoothness," "Snappiness", "lagginess" (three very hi-tech terms), FC's? Etc..

I have all my uSD's full right now and am wondering if I should replace one of the other systems with this one. Current using AOKP (krylon360).. happy with it but curious about general performance differences or similarities.
[Nook Color Android Development] halrulez:
Man I was so all over this rom last night I didn't even get to sleep till 4am and now I woke up at 9am just to play with it again. This is the BEST work I have seem for a rom all these options is totally what I have been looking for. Only thing missing is the option for the ICS onscreen buttons to be able to be turned on and off and this is complete. GREAT JOB +1

They need to have all these options implemented into cm9 and AOKP builds. Great job again guys really really great job!

---------- Post added at 09:13 AM ---------- Previous post was at 09:13 AM ----------

This needs to make it to front page.
[Nook Color Android Development] mateorod:
Is this something that still doesn't work for our CM9? Because that would be real interesting...(sorry, my nook still has no network so I had to farm out any testing that involved the internet...)

Thanks for all of the positive feedback, everyone. I am going to see what I can do about the little clean up stuff this ROM needs over the next several days.
[Nook Color Android Development] leapinlar:
Flash does not usually work on non-opengl CM9. A couple of months ago I discovered that flash worked with my soft navigation patch and opera mobile. Shortly after that I did not need the patch anymore, just some settings in build.prop. And flash quit working in Opera. Now it works again.
[Nook Color Android Development] eyeballer:
Since it seems there's an overall positive response and the paranoid guys have updated to v1.6 mateorod has already begun work on an updated version. It might be the last ICS version depending on how things go with CMs jellybean merge.. which is already underway ;)

leapinlar, computerist, or anyone else that's had a chance to play with this over the past day, please post up your pad.prop files (/system/pad.prop). This is where the rom stores the configs/dpis you have chosen for the system/apps. I'd like to compare peoples preferences and see if we can put together a stock pad.prop that offers the best of what you've found so far - eg. we'll put leapinlars opera mobile settings in, so if someone downloads the rom, they can go install opera mobile and the rom will be set up for the optimal settings.
[Nook Color Android Development] bachikho:
much slower than AOKP!
[Nook Color Android Development] mateorod:
You took the words out of my mouth...I am working on the update now, and it will involve bringing it forward to Paranoid Android 1.6 as well as some residual cleanup. I intended to take a little more time than this, but I figure getting 1.6 out is the first priority. After the update, then I will go into serious cleanup mode.

So, yes, please post any tips and attach any pad.prop (in /system) that you have worked on.
[Nook Color Android Development] leapinlar:
Here is my pad.prop. There is nothing really special there. I like phone gui, but set a few apps to tablet ui with low dpi. But in particular I have YouTube set for 128 dpi and phone ui. That makes the videos play in HQ instead of attempting to play in HD and failing. I think computerist mentioned that. And with my settings for Opera Mobile (128dpi, tablet ui) it plays flash. Other things are just me experimenting with various apps to make them readable to me. I did have to update to the latest Root Explorer to get it to show it's menus properly.

One other thing, I wiped everything and started fresh so I could not figure out why things were kind of sluggish. I forgot to set overclock. lol.

Edit: Also playing around I see there is an app that lets you back up your pad.prop file to SD. This is good if it does get overwritten in a new flash. Just restore from SD after flashing.

Removed attachment
[Nook Color Android Development] halrulez:
I'll upload mine in a little bit. I will also add my build prop too. and voltage settings. I have this thing as smooth as cm7 right now, except for load times. couldn't tune that part. but traditions and animations are fast. Plus I took swappiness up to 90%...... is nice!
[Nook Color Android Development] halrulez:
ok so here they are in a zip. I couldn't get them to upload any other way.

Voltages are as follows: ps these gave better battery "and" made the rom quicker.

Step1 0.825v

Step2 1.0v

Step3 1.15v

Step4 1.225v

Step5 1.3v

SD read ahead is set for 4096 on a 16gb class10 PNY

The rom is running from the emmc

oom is enabled

I am on conservative Gov 300-1200

And was running BFQ but have seen improvements in speed using noop so switched over.

Hope this helps a little.

Once again I am SUPER excited over this rom and all its options.

BIG THANKS to you guys and great work.
[Nook Color Android Development] mateorod:
An update on the update, as it were.

I had been having problems with porting the 1.6 Paranoid Android framework over to us. It turns out that the framework is relaint on runtime a lib that is chipset specific and that was my problem. They are considering rebuilding it as a porters version, but for now only the PA creator's devices have 1.6, along with anything that may happen to have the same chip as they do.

There are some things about 1.5 to tweak while we wait, and I think that eyeballer's plan to aggregate a pad.prop is a quite worthy addition. So this ROM will get an update over the next week. I am going to return my attention to 1.5 until we get any news from PA.

From what they tell us (without source, we kind of have to wait to be told), there aren't any major updates in 1.6 outside of the speed increases, which are unfortunately the very thing that is stopping us from effectively porting. It somewhat sounds like they were trying to get ICS out of the way so they could move on to JellyBean. So basically, the same thing you're seeing all over XDA lol.

I'm all about JellyBean, but they sure know how to shoot a platform in the foot, don't they? ICS died before it ever truly lived...

Thanks for trying the ROM and keep submitting any interesting pad.props. And anytime you play with the Paranoid Settings, you're writing to pad.prop. So anyone who is playing with their GUI has something to offer!
[Nook Color Android Development] Dj-Gutz:
NM.

Please Delete
[Nook Color Android Development] derekr44:
Edit: Ok, yes I'm a retard...

So far so good!
[Nook Color Android Development] derekr44:
Couple questions:

How did you adjust your SD read ahead?

What do you mean by OOM? Noop?
[Nook Color Android Development] halrulez:
I use 2 specific programs that let you tweak you android experience. My fav one is, and well worth the money is ROM too box pro. The other is free and very awesome to use once you get to know what everything does, system tuner. To learn what all the settings do I suggest searching through xda and learning what they do before tweeking. To set read ahead times there are allot of free SD programs on Google play. But if you get both these programs they are well worth it. The part about noop is the sceduler . It is what controls the type of I/O that the kernel uses. I change this with ROM toolbox. But there are free CPU/kernal tweeking programs free on play aswell. Hope this helps a little. ;)

If you have any more questions I'll always try to help the best I can.
[Nook Color Android Development] skyliner33v:
I am so flashing this as soon as i can get my NC fixed. Im running this rom on my samsung infuse phone and i love it.

Btw, anyone know how i can replace a cracked NC screen? It still works perfectly except anything above the crack doesnt respond to touches.
[Nook Color Android Development] mateorod:
I haven't used the backup app yet, but you guys want to try a cool trick I wish I knew ages ago?

Create a file called custom_backup_list.text in system/etc. Populate it with whatever you wish to survive a CM install. So for pad.prop, the file would just say /system/pad.prop.

Tell me that won't make your life easier...could have used this when I was updating every night.
[Nook Color Android Development] derekr44:
Fantastic! Thanks for the help. My SD is blazing at 4096 (19.6W/30.1R). This ROM is very quick with those system adjustments.

Perhaps I didn't boot the market correctly, but should I be able to get ICS launchers from the market (like Apex)? Play says it is incompatible with my device.
[Nook Color Android Development] halrulez:
Try going into settings then apps select google play market, what ever it is called now lol clean your data and cache on the app then restart the nook. Should work then. If not then go into recovery and wipe you cache and dalv cache that should do the trick.

It might think you are still on cm7 thats why
[Nook Color Android Development] mateorod:
Oh, shoot.

Did I not put it in the OP?

davidtre, I will try and be much clearer.

Your attitude is terrible; I am glad it doesn't work for you; you can go away and never come back.

All further communication re: you and/or your opinions will be ignored. I'd ask everyone else who feels that my work is worth every dime they paid for it (zero) to follow suit.
[Nook Color Android Development] mateorod:
For anyone building at home, we're still merging these new files into our tree. If you had errors related to multiple libions, I have fixed that issue at least.. We are just checking to see if it exists before trying to pull it from core.

I will update you as I find stuff out. I set it to build last night, but found this error waiting for me this morning. It is found almost immediately, so there was no real progress in the build.

Okay. Update : We have also moved back to my fork of android_device_bn_encore. Eyeballer's addition of expanded desktop stops compile, as the items in the base package (Settings) the overlay works with aren't there.

We are using the PA settings, not the CyanogenMod one. I chose to go this route because since the expanded desktop was ported from PA in the first place I think we have it enabled somewhere else in settings than where eyeballer's overlay addition is looking for it.

If it for some reason missing, then I will bring it all over from CM later. Everything else from the NookieDevs device repo is in our fork.
[Nook Color Android Development] anapospastos:
Sorry for this. Give me your address to send you my nook running paranoid so you won' t need to move again your little finger to get yours working.

(this post is a kind of joke:cool:)
[Nook Color Android Development] Tiezane:
Now, this is nothing to joke about. I will GLADLY take his nook so we never have to hear from him again!

Sent from my Sega Master System via Carrier Pigeon.
[Nook Color Android Development] mateorod:
So, weirdness.

I just finished a clobbered build, testing our newly in-line source. Builds fine, but some of the little things were stangely missing (most notably toggles) and I was getting Death Screens.

I saw that fat-tire posted a backed out kernel and since I was tired of getting death screens everytime I had to reboot to set a PA setting, I threw it in there.

BOOM. Toggles back. So there are some kernel problems beyond Death Screens, for us at least.

Anyone building for Jellybean- here is a link to the good kernel (by NookieDevs, posted by NookieDevs. Just linking).

I am experimenting with some of our pa_pref.xmls, trying to get the best balance. This is something that anyone could help with, so if you are building, pop out a fresh build (it IS building again. I had to do some tricky cherry-picks, and even submit some stuff upstream. But we're back) and let me know.

The files we are going to be editing are in vendor/pa/prebuilt/preferences/pa_large-mdpi.

There are three pa_prefsX.xml right now, but we can also add a couple more. It is in xml, which is SUPER intuitive to understand (no programming necessary, really) and involves things like deciding which toggles we want. The properties of hybrid and tabletUI and so forth. So the fun stuff.

Anyone who is interested should check it out and post their favorites. I can provide some templates to look at should it come to that...
[Nook Color Android Development] anapospastos:
So, mateorod, I used the uimage you posted by NookieDevs but I' was getting the same errors during boot. I wasn't sure if I used it correctly(you could give me a hint to this) so I builded myself using branch "lastknowngood" by steven676 and I'm having again the same errors.

Did you try to boot version 2.52 with steven676's kernel?
[Nook Color Android Development] krylon360:
E/libEGL ( 1465): eglGetDisplay:123 error 300c (EGL_BAD_PARAMETER)

E/libEGL ( 1465): eglInitialize:139 error 3008 (EGL_BAD_DISPLAY)

E/libEGL ( 1465): validate_display:209 error 3008 (EGL_BAD_DISPLAY)

E/libEGL ( 1465): validate_display:209 error 3008 (EGL_BAD_DISPLAY)

PVR blobs are your issue
[Nook Color Android Development] mateorod:
Let me translate that for you...xD...Krylon is saying you don't have the proper nook proprietary files.

But that should be included in your repo sync(Look at the bottom of the manifest for 'eyeballer'. Did it perhaps fail to pull the project?

Look in vendor/bn and compare it with here.

Repo sync again and see if it pulls something new from eyeballer.

Now my experience with the 'lastknowngood' kernel is that it has not fixed the issues. I haven't reported it because we're not supported by them. I may fork the kernel and roll back to an earlier state, I haven't decided. Keyodi had sent me a bunch of kernels to test early on after the alpha was released, and I had one that worked perfectly. But that was before the Video additions, and it would take a bunch of work to roll back all of the projects to before that state,

Well, how about this, I could do that, but then maintenance becomes a *****, since I would have to following their changes really closely to know which projects/commits to add and which to wait on.

So we may just wait it out. These guys are great, and we have every reason in the world to trust they will work it out. I tried to keep our particular project in a bootable, working state but it was just too much to keep track of.

tl;dr: Make sure you have vendor/bn populated and repo sync again, watching for that project. A rebuild might take 20 mins, max.
[Nook Color Android Development] grayfoxmg1:
Beta 2 has been released, if you want to check that out link is HERE
[Nook Color Android Development] anapospastos:
It was my fault. I clobbered and then repo synced but it didn't pulled vendor/bn proprietary files. The folder was empty. I synced again, built it and now it's running flawlessly.
[Nook Color Android Development] mateorod:
Some merges/fixups were just brought in from upstream.

Of particular note:

Updated wifi firmware, thanks eyeballer

Updated manifest to include all latest CM projects

The CM projects are all subuser stuff, but they will make some difference. The firmware update to the wlan is a big big deal, that looked like it basically was making the Nook unusable as a network device for some people. Great job by eyeballer getting to the bottom of that.

Places where we diverge from Encore CM and Upstream PA, withinthese merges:

Took off the encore overlay for extended desktop

I included the CMFileManager, because I believe that including a file manager is the right thing to do.

I hated when the File Manager was left off of CM9, even if I understood why they felt they needed to move away from OI (and what was OI thinking with their latest update, omg). But having their own is the right thing to do. When/if PA's code review adds us as a device, we'll consider getting in line with their vendor practices, but since we are still just 'builds', I think we can do what we want...

I have been busier than expected with some outside work, but there will be some more device-specific optimizations for our PA being finished over the next week. Small things, like some edited strings and some toggle-preferences. As of right now, I think the toggles are only visible in TabletUI, and that is obviously not preferable.

But everything should be synced with the current state of the CM10 for our device, and with the fixes for the Nav bar menu key as well as the mentioned commits. If you are building, let us know how it goes, and go thank the guys at the top of the release thread, if you haven't already.
[Nook Color Android Development] davidr415:
mateorod...

Both last night and this morning.. I did a make clobber and then repo sync , build and lunch..

I get a whole lit of errors... for instance..

find: `frameworks/base/icu4j/java/android': No such file or directory

find: `frameworks/base/voip/java/android': No such file or directory

find: `frameworks/base/core/java/android': No such file or directory

find: `frameworks/base/graphics/java/android': No such file or directory

find: `frameworks/base/location/java/android': No such file or directory

find: `frameworks/base/media/java/android': No such file or directory

find: `frameworks/base/media/mca/effect/java/android': No such file or directory

find: `frameworks/base/media/mca/filterfw/java/android': No such file or directory

.... eetc

ending in

build/core/base_rules.mk:171: *** abi/cpp: MODULE.TARGET.SHARED_LIBRARIES.libgabi++ already defined by .local/share/Trash/files/android/system/abi/cpp. Stop.

Is this my problem? If so, can you help me get past it? I need pretty detailed guidance..

Thanks
[Nook Color Android Development] mateorod:
Hmm. I don't know what is going on based on the info right there. You must have trashed some folders with hard links in them, as it is looking in your trash bin for things.

Those missing files from frameworks are the classes that populate the framework2.jar. Are those files in the place they should be, as in, do you have frameworks/base/media/mca/effect/java/android and so on?

Here is something you can try, empty your trash to get rid of whatever is tied to your source code in there. Then repo sync once more. After the repo sync, enter

repo forall -c 'git reset --hard'

That should set all of the various projects back to the state of the last commit, and hopefully return your source to a buildable state.

I just synced and built last night AND this morning, so I know the source will compile in its current state.
[Nook Color Android Development] vinal:
Finally got some time this weekend to create a new 2.5 build again and I was surprised at how much better it is than 1.6 (and the earlier 2.5 build I did a couple of weeks ago). Many thanks to Mateorod and the other devs for their work and help in these CM10 threads.

One issue I've seen is that it drained my battery completely overnight and got stuck in bootloops after charging for a while this morning, though it did reboot once successfully and then rebooted into bootloops sometime after it was plugged back in charger. Will let it charge completely and report back.

Note: my build doesn't contains Mateorod's lastest merges from last night.
[Nook Color Android Development] mateorod:
Those merges should help, I promise. Also, for our jellybean builders, you can now run the custom build script that come packaged with paranoidAndroid.

. build/envsetup.sh
./rom-build.sh encore

DONE

A rebuild should take you maybe 30 mins if you don't clobber, with the latest merges.
[Nook Color Android Development] vinal:
Thanks for quick response. Sync'd, rebuilt, cleared caches, flashed and it booted fine once and then got into boot loop again on next reboot.

I have since cleared all data and reflashed, so I'll see how that works after google play restores apps.

My boot loop is similar to this http://xdaforums.com/showpost.php?p=33585130&postcount=458. Didn't find a response to his issue in that thread.
[Nook Color Android Development] davidr415:
mateorod.. your suggestion worked great.

It is built.. now just to flash and try it.

EDIT: Like Vinal.. I a getting bootloops after the first (successful) boot.. fresh SD install.

Oh well..B2 is running so well I can't complain.. Just like PA bettter.
[Nook Color Android Development] vinal:
Clearing data didn't fix my boot loop. Went back to PA1.6 and had no boot loop. Then cleared all data and re flashed 2.52. Google Play didn't auto re-install apps and so far no more boot loops after manually re-installing apps.

So, I may have had a rogue app I haven't re-installed or 2.52 doesn't like Cobalt theme I was using. I also haven't altered much in settings yet.
[Nook Color Android Development] mateorod:
I will be checking this out personally tonight, thanks to both of you for the reports. My feeling is that this is actually a reflection of the kernel troubles we're having with upstream as opposed to PA issues. Feel free (if you can) to submit logcats or dmesg to this thread. I will not be much help in kernel debugging, but I can generally parse the logcats.

They are hitting the kernel pretty hot and heavy, attempting to get this all worked out.

I did try and keep it on a 'stable' branch, but that turned out to be a fiasco.

So what we are seeing is likely a reflection of their upstream work. We are lucky they have been so willing to devote their time to finishing this project.

Exciting time to be a Nook Color owner, which is insane, since the device came out YEARS ago. The ultimate open-source triumph, in my opinion.

If you had a beta running stable on your device, you could try porting the kernel from there, although be cautioned the alpha kernel is not compatible. Otherwise, just try a rebuild every couple days. Once your source is pulled and your intermediate files are composed, the builds take 20 seconds to start and 30 mins to finish, so no real work required to check in on the progress every couple days.

You CAN dirty flash back and forth over the CM10 releases, I have found, YMMV.
[Nook Color Android Development] grayfoxmg1:
To all my fellow XDA hackers, crackers, and flashers; the CM10 Beta 3 for our device just dropped over in that thread curtsey of Eyeballer and Krylon.
[Nook Color Android Development] mateorod:
crackers...what about mexicans like me?:silly:

Thanks greyfox. If this beta goes well, we will begin looking at a release here pretty soon. Get testing folks.
[Nook Color Android Development] grayfoxmg1:
Just as a quick informative for everyone here, I tried to dirty flash Beta 3 (henceforth known as B3 because I said so) over the latest PA port. And while the flash was successful, I got so many FC's and errors that it made it unusable. So the golden rule of CLEAN wiping before jumping platforms still holds, so DON'T ASK US IF YOU CAN DIRTY FLASH.
[Nook Color Android Development] DizzyDen:
I always recommend a shower and clean underwear when flashing.... just in case
[Nook Color Android Development] leapinlar:
Mateorod,

I have successfully built CM7 and CM9 but for some reason have not been successful building CM10. It probably is because I am running a 32 bit version of Linux.

And I am beginning to love CM10 beta 3. I can hardly wait to get my hands on a PA version.

You have said in the past that PA is just pretty much a port to the frameworks. And I have recently looked at your AutoPatcher thread. Awesome BTW. And now my question. Would it be feasible to create an autopatch to make a PA patch from a regular CM10 ROM?

Sent from my Nook Color running CM10 and Tapatalk.