yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] mateorod:
That was certainly the first thing I thought about when I initially saw ParanoidAndroid. At that point, the rom was closed-source and port only, and it seemed like something to check out.

My feeling is that it would be possible, but really pretty difficult to manage. There would need to be patches for, off the top of my head, core, android-policy, services, frameworks, framework-res, SystemUI.apk, Trebuchet and probably more.

That could be a lot to manage.

The best way would be someone who had both repos initialized in the same directory, and then repo synced each repo, and then made two builds after checking out each project. With those builds, you could begin to run them through my patch-making suite.

Ostensibly, those scripts would do all the work making the patches for you. They do work, although I need to beef up the documentation considerably. Now that would probably work as a base to check/debug the process.

The problem is with that many different patches, they would probably need pretty intense maintenance. On average, big patches like this tend to have a shelf life of maybe a month. But with so many different patches, that time frame shortens considerably. Couple that with the fact that PA went open-source and it just no longer seemed worth the time. Any device with a compatible device tree can get a PA rom much more easily that way.

But I like what you were thinking, that was exactly my first thought. I am trying to get the Auto-Patcher to be thought of as a more general distribution-type tools, capable of porting software to the many people who do not build their own roms. But it is an up-hill battle, lol.
[Nook Color Android Development] eyeballer:
Yeah this sounds like a lot unnecessary effort.. I think a better plan would be to have someone auto-build nightlies for PA at some point... ;)
[Nook Color Android Development] huhu22:
argh - excuse ,me im a newcomer with bad english -

I did try a custom DPI now I only get somethung like !excuse Trebuchet was closed..... same if I try o go to the Settings - excuse settings are closed..

Is there any way except of Factory Reset to fix this for me?

Thanxs!
[Nook Color Android Development] mateorod:
If I understand you correctly, you modified the build.prop and now Trebuchet is FCing.

In that situation, you should boot into recovery and reflash your rom. You do not need to wipe anything. Reflashing should suffice.
[Nook Color Android Development] grayfoxmg1:
Man those guys in the CM10 thread are on fire. Beta 4 has been delivered.

Beamed from my Paranoid Android running Nook Color.
[Nook Color Android Development] 911jason:
Nevermind...
[Nook Color Android Development] mateorod:
You thought you'd never see the day: ParanoidAndroid for Nook now has nightly builds!

The builds are available at our download page on techerrata and can also be found via Goo Manager in browse compatible roms -> eyeballer -> paranoidandroid.

There is still some finalizing to be done for our device preferences, but other than that the functionality should mirror that of the Official CM10 builds.

Most everything you need to know is on the first three posts, including a walk-through of the Paranoid settings and links to all the sources should you wish to have a hand in how ParanoidAndroid will be defined for our device.

It was hard holding this rom in my back pocket this last month and a half. I did it not only out of respect for the wishes of our CM team, but also because since this rom uses that team's kernel and device trees, the more feedback they got, the better this rom would eventually be.

That is a long way of saying that those same people who brought you CM10 are bringing you PA as well. Everything that works is to their credit, anything that doesn't is on me...

Enjoy.
[Nook Color Android Development] eyeballer:
PA party time :)
[Nook Color Android Development] leapinlar:
Yay! Just downloaded with GooManager and flashed. Looks great. For you SD users, don't forget to rename to update- at the beginning.

Edit: I love it! My favorite 240 home screen and You-Tube at 160 in HD tablet mode.
[Nook Color Android Development] webdroidmt:
Thanks for doing this, I have a PA JB build on my Kindle Fire and really enjoy using it. Recently, in the GN7 forum, I read that going forward PA was going to use AOSP source instead of CM. Do you plan on going that route, or staying with CM? Thanks again.

Mike T
[Nook Color Android Development] mateorod:
Ahhh... that might explain some of the recent code reorganizations. I hadn't heard that, but it is a common next step. Often forks will try to rebase to aosp in order to distance themselves from their CM kang origins. It also leaves them less dependent, so there are pratical reasons as well.

I will follow the main PA conventions. My goal has been to limit the amount of forks I have to personally maintain, which limits human error, needless effort and speeds integration of new features. Many of my forks have recently been retired, as my reasons for needing those forks have slowly made their way into the main PA repos.

Having said that, no other custom room is likely to replace Cyangen's hardware support, or likely even try. They gave built up a very impressive infrastructure and splitting the resources to compete in that area seems like a waste, not to mention a huge undertaking.

No other custom Rom will ever have device support for encore, that I guarantee you. And I think we have all seen as much as we need to of the stock firmware.

Since most of the project forks have been made in order to increase device support, i imagine just about all custom groups will continue to get those from CM.
[Nook Color Android Development] RoboticBuddy:
Thank you to all the NookDevs out there! You have brought life back into the Nook Color! :D

(I wish i could donate, but I'm currently broke :p)

One quick question, can we dirty flash this over CM10 Nightly, since PA is built off of it? Thank you! :D
[Nook Color Android Development] webdroidmt:
Thanks for your very eloquent reply. :) I tend to agree with you regarding CM & custom groups, especially encore. Thanks again.

Mike T

---------- Post added at 01:29 AM ---------- Previous post was at 01:27 AM ----------

I just flashed this over nightly CM10 1114, wiping cache/dalvik and fixing permissions just for good measure. Seems to be working fine.

Mike T
[Nook Color Android Development] kcls:
From what I have read on the original ParanoidAndroid thread, molesarecoming is rebasing PA on aosp, but the CM side will also be maintained by someone else, so there's no need to worry about losing support :)

I'm looking forward to trying out this and CM10 this weekend. My nook has been gathering dust since I put CM9 on it since it was so buggy :P

Excellent work everyone!

Tapatalk² from my Optimus V
[Nook Color Android Development] les02jen17:
Just wanted to report! I've just flashed the latest PA nightly... and I can definitely say that it's working smoothly! A lot faster, snappier and more responsive the the CM10 Nightly which was my previous ROM before this. I installed it after doing a full wipe (/data, /system and /cache). Thanks for this amazing ROM! I always said that I can never have CM9/CM10 my daily driver, but with this ROM just changed it. Thanks, thanks, thanks! please wait 2 seconds for an uncompressed image, or press Ctrl+F5 for original quality page
[Nook Color Android Development] mateorod:
One of the great things about nightly builds is that I won't need to post to alert y'all to updates.

Having said that...we put up a new nightly this morning (bump to 2.5.5), and I want to briefly talk about it.

If you go to Paranoid Settings, the various presets now are accurate for the Nook.

Use the Launch pane to adjust workspace presets.

Selecting one will apply to the workspace, using Phablet, Phone or Tablet layout.

To define one of the main categories, use the Interface pane.

That can change the UI for general types, i.e. Workspace, System Apps, User Apps, Status bar...

To override something for specific apps, you can then use the Apps pane.

The priority level goes upward- from Apps to Interface to Workspace. Changing something in Interface won't overrule your defined Apps preferences.

And of course, the Colors preset splashes colors over the navbar and soft keys and the soft key glow.

Choosing any Universal preset first is recommended- That will also turn on the circle battery and add a brightness slider to the status bar. Let us know of any cool combination you really like as you explore- we can add some of those configurations to the rom itself.

I have some customizing still to come. I want to increase the size of the soft buttons and I need to increase the battery/clock icons as well as play with some of the other Android/Hybrid settings. But the presets finally are correct and make sense as a base for our device. You can see what we have set up here, although you may notice the lockscreen clock alignment is not working as expected quite yet. I'll get it...
[Nook Color Android Development] leapinlar:
Version 2.55 does not work for me. Version 2.54 worked perfectly. I was able to set the interface to phone and 240 dpi and that's what it did. Then I could set each app to the dpi that I wanted, like setting You-Tube to 160 so it played in HD. Now on 2.55, I try to set the main interface or dpi and nothing changes. So I tried setting dpi in local.prop and that worked, but sometimes SystemUI would crash on trying to do a dpi change with PA. So for now, back to 2.54 for me.
[Nook Color Android Development] peramikic:
Same as leapinlap above,PA 2.55, nothing changes and System UI crashes if Tablet mode is selected (SD install). I'll try 2.54
[Nook Color Android Development] grayfoxmg1:
Running into similar issues as them with the newest PA nightly

Injected by my ViperXL using Tapatalk 2
[Nook Color Android Development] mateorod:
Thanks..I will look at it tonight and it will hopefully be fixed for tomorrow...we aren't releasing these at a set time quite yet as the configuration gets nailed down, so I will let you know when a new one is up.

Edit: You can fix tablet UI (and perhaps several other things) by changing the '%rom_default_dpi' in system/etc/paranoid/properties.conf from 169 to 160.

Probably the other problems too. I will have to dig further to find out why that dpi is causing it to crash. Thanks for bearing with the growing pains.
[Nook Color Android Development] how_weird:
I haven't used my nook since I flashed a year ago, just let the kids have it. After crawling back to this area I am happy to see so much new work being done. I was sad when it looked like my nook was being left behind. Thank you for bring life back to it.. I may have to ground my kids so I can play with this :p

How_Weird is to weird?
[Nook Color Android Development] tambourineman86:
Thank you mateorod and eyeballer. I've always enjoyed your work and this version of PA (2.54), after extensive tweaking, is very stable. Not fast, but stable. I know that a lot of work has been put into this and more work will be put into this, but the fact we now have a fully functioning CM10 base (and offshoots such as PA) means that most of the dirty work has been done. I apologize for my inability to help with the NookieDev project. It was (is) something I really want to do, but is hard to find time for with a 60+ hour/week job, a wife and a kid. So I tip my hat to you gentlemen, and express my admiration that you have so undeniably earned.
[Nook Color Android Development] bitstra:
Thank you mateorod!

the %rom_default_dpi=160 made it - all works fine as before ver. 2.55.

regards bitstra
[Nook Color Android Development] thejrcrafter2:
Latest cm10?

this is based off the latest cm10, or at least one of the nightlies right? does it support oc?
[Nook Color Android Development] leapinlar:
Me too! Works perfectly as before.

---------- Post added at 08:10 AM ---------- Previous post was at 08:09 AM ----------

Yes. To 1100Mhz.
[Nook Color Android Development] thejrcrafter2:
Ok. Do I need to clear data from a plain cm10 install or can I just leave it since pa is based off cm10?
[Nook Color Android Development] bitstra:
I've flashed it over the CM10 nightly 17/11 (with wiping Cache/Dalvik Cache). All works perfectly...

bitstra
[Nook Color Android Development] Quantumrabbit:
Damn smokey... this is way more stable and pleasant to use than the CM9 based PA... nice work Mateorod.
[Nook Color Android Development] mateorod:
Oh yeah. The ICS PA sources were closed within a week or so of being released. At the moment, if you try and build ICS from their github, the build won't compile due to an outdated manifest. I have gotten three to four pms from people trying to build ICS for various devices and getting stuck here.

I say that to illustrate the shape those repos were left in when they moved on to Jellybean. The PA project was just getting off the ground at that point.

ParanoidAndroid 2.5.5, with the fix to the default dpi, has been pushed to our download page and Goo Manager.

I would like to get to the bottom of the troubles with 169 dpi, but for now we'll leave it as is. I still have some UI preferences and settings to pound out and will be slowly merging them in over the next week or two.
[Nook Color Android Development] les02jen17:
Does this mean that we can get 1.1GHz overclocking if we flash PA 2.5.5 over CM10 Nightly 17/11??? :fingers-crossed:
[Nook Color Android Development] eyeballer:
The device tree is common for both CM10 and PA, so if something is merged into CM10 it'll be available in PA. So our recent performance improvements are in the latest PA builds.
[Nook Color Android Development] grayfoxmg1:
I can confirm that PA 2.55 has cpu speeds on 300mhz-1100mhz
[Nook Color Android Development] Tiezane:
ok, so I'm starting to think I've lost my mind here. I could have sworn I awe my MIL playing Words with Friends on her xyboard, in landscape mode, and it looked sweet. I have tried dpi, layout, everything, and I can't seem to get it out of portrait mode. Someone help?

Sent from my Sega Master System via Carrier Pigeon.
[Nook Color Android Development] derekr44:
Mateo, Eyeballer and the rest of the crew, I'm impressed with this one. I haven't encountered an issue yet. PA has been very stable and I'm even more impressed with how quickly you guys busted out CM10 & JB. Major kudos!
[Nook Color Android Development] -somebody-:
i am so happy with this. thanks devs for all of the long hours you continuously spend working on this and also the devs whove been working on cm10 as well. been running for a couple days now and its great, thanks.
[Nook Color Android Development] how_weird:
Just need Netflix to not crash and I will be happy. Other than that is all good so far.

From my Nook Color running Paranoid Android 4.1.2 Nightlies
[Nook Color Android Development] grayfoxmg1:
what netflix are you running? the newest from the store or 1.8.1?
[Nook Color Android Development] how_weird:
The newest 2.0.2 from app store.
[Nook Color Android Development] leapinlar:
My 1.8.1 version works fine on this versionof PA. You can't use the one from Play Store.
[Nook Color Android Development] how_weird:
Thank you both. Now I don't have to watch hoarders, wife controls bedroom TV.
[Nook Color Android Development] les02jen17:
Just wanted to report. Latest build is quite smooth as the last build. I do start noticing lag whenever I try bumping it up to 1.1GHz, regardless whether it's on performance governor or not but as soon as I put it back to 1Ghz it runs just fine. I haven't ran v6 supercharger or anything like that. Just playing with the settings under "Performance". Awesome work from the devs, we can't thank you enough! :)

Tapatalkin' it from my Nook Color running ParanoidAndroid
[Nook Color Android Development] dparrothead1:
Very nice!
[Nook Color Android Development] derekr44:
Oh, one thing: The options in Nook Tweaks don't work in JB. I used it for the DAC Audio boost when I plugged my Nook into my car. Is there another way/app that allows the DAC boost? I've tried a couple other equalizer apps, but none of them gave the amount that Nook Tweaks did.
[Nook Color Android Development] leapinlar:
Nook tweaks is for a different kernel so wont work. But krylon360 has said he is working on a version that will. Just be patient.
[Nook Color Android Development] krylon360:
its going to take a while. with 69 hour work weeks, time is limited. what time I do have i spend with my wife and daughter, but its getting done and will be integrated into the build.
[Nook Color Android Development] lynnji:
My Google Play Store keeps crashing and sometimes disappearing from my apps, anyone else with this? Only since the last update. I've tried reinstalling the latest gapps a couple times, no luck. I can open it and use it fine once or twice, then I start getting a message that says "Unfortunately, Google Play Store has stopped" after it tries to open. Never had this before.

Not sure if this is the right place to post this.
[Nook Color Android Development] bowguy:
Navigation bar issues

Love this!

The only issue I have found is with the navigation bar (? bottom icons for back, home and previous apps). I have the Statusbar set to 240 and the size is good but touching the back icon or the previous apps icon is off. That is I touch directly on the icon nothing happens. If I touch inside of the icons (right of back and left of previous) they fire. All other touches seem to align correctly. This happens in portrait and landscape mode but portrait is more noticeable. I turn on show touches and they are correctly shown on the navigation bar where my finger touches but again they don't fire unless I touch inside of them. Looks like a scaling conversion error.

Just checked with the Statusbar set to 120 and they seem to work fine. This may be due to the default is pretty close to my setting of 120.

I have the ft5x06 touchscreen if that matters.
[Nook Color Android Development] grayfoxmg1:
use this (https://play.google.com/store/apps/details?id=com.assid.android.nookrecalibrate&hl=en)
[Nook Color Android Development] leapinlar:
I also run at 240, but I have the ctty screen. I also used the navagation bar editor to move the icons around. I put recent where the three dot menu was and menu where recent was. Maybe that fixed it. But mine works fine.
[Nook Color Android Development] bowguy:
Navigation bar issues

I tried this but as expected it had no effect. Remember ONLY the navigation bar is off, not the rest of the screen.

Link to navigation bar editor?

Thanks
[Nook Color Android Development] leapinlar:
After rereading you post, you said you only set the status bar to 240. I have the whole device set to 240, phone mode. That may be why yours is wonky. The edit navigation bar only comes up in phone mode.

And the setting is under system.
[Nook Color Android Development] mateorod:
I can take a look at this, but my feeling is that this is an upstream issue. This to is still being worked on extensively, and bugs are present. For instance, the FCs we found when we set our device default DPI to 169. There is no reason that should crash functionality, so there are some scaling problems somewhere.
[Nook Color Android Development] bowguy:
No worries. Now that I know about it and can workaround, lets just keep an eye on it and wait for upstream changes.
[Nook Color Android Development] bsw11:
I just dusted off my NC and wanted to put this ROM on. My concern is that since it is a 4.2 will the old CMW recovery flash it OK. I tried using GOO to load twrp but it does not seem to work - it just reboots into CMW.

Please advise. Do I just use CMW and flash the ROM and then the GAPPs and reboot? (Reset and wipe understood).
[Nook Color Android Development] leapinlar:
Yes. The problem is goo manager expects an open source recovery, which CWM is not. Just go to where goomanager downloaded the rom, probably /sdcard/goomanager. And flash it with CWM. And reset is usually enough.
[Nook Color Android Development] how_weird:
I hadn't flashed in a longtime, still had cwm on SD and had that issue. I had to use ROM manager to download and install cwm on nook. Then after reboot I used goomanager install twrp.

From my Nook Color running Paranoid Android 4.1.2 Nightlies
[Nook Color Android Development] eyeballer:
I just put up a fresh build.. I will be out of town the next few days for Thanksgiving, will try to put out a build or two if I remember..

Hope everyone has a good Thanksgiving!
[Nook Color Android Development] -somebody-:
happy thanksgiving you and everyone else as well.
[Nook Color Android Development] dparrothead1:
Just d/l and flashed 2.99. Everything looked great until I changed the settings to tablet and rebooted. Went in to constant boot loop.

Went back to 2.55 and everything is fine.
[Nook Color Android Development] kcls:
2.99 is nowhere near prime time yet, even in the Nexus 7 and Galaxy Nexus, which are devices supported by moles himself.
[Nook Color Android Development] lollyjay:
What looked like bootloop actually took 5+ minutes! I made coffee and waited it out, and eventually mine booted.

QI0CM9787SV, 12/11/2010

ES1.2, cyttsp,

Go Launcher HD
[Nook Color Android Development] dparrothead1:
Eyeballer put it up for d/l.....didn't say anything about it not being ready for use....
[Nook Color Android Development] mateorod:
Well, let it be said out loud, then. Nightlies, by their very definition, are experimental. We are pulling the absolute latest merges, many of which you guys will be testing for the first time. So there can, and will, be speed bumps.

There is going to be some choppy water for awhile, specifically. PA is changing from a straight CM base to an AOSP one, with select CM projects. The merge to 4.2 is going through in a somewhat haphazard manner as this change is instituted.

As for our device, we haven't changed anything from what you found in 2.5.5. So all the changes are upstream, be they PA or CM. I could run around and roll back any projects that have changes in an attempt to find the offending commit, but then what would be the point of nightly builds? We would just be pumping out identical builds between stable releases.

I am betting our problem is here, nothing else looks invasive enough to be the culprit.

We will just have to ride it out. It looks like they are targeting PA 3.0.0 for the 4.2 update, so maybe that is a target for those of you that want to wait for a more stable build.

I could be conceivably talked into releasing stables in-between the nightlies, if you guys would prefer. Consider our latest 2.5.5 to be the stable for now.

If you flash a nightly and it gives you problems, you do not have to wipe. Just reflash the last build that worked for you and it should be fine.

Thanks guys!
[Nook Color Android Development] dparrothead1:
Lollyjay was correct...I didn't wait long enough. Except I went and made a rum and cherry limeade instead of coffee!!

Everything looks good in tablet mode. I like this much better than the CM10. One thing I did find, it wouldn't recognize my external SD card until I went into settings and hit "mount" and now all is good!!! MX Player, Xifinty Player, HBOGo and YouTube all look good.

Many thanks for this smooth rom:thumbup::)
[Nook Color Android Development] stolenmoment:
DSPManager can boost some apps, SpeakerBoost boosts others. I don't know why it's selective like that.
[Nook Color Android Development] lollyjay:
This nightly is FANTASTIC! No problems whatsoever. I'm a Paranoid believer. BTW I am using Equalizer app from the Play store and it boosts the sound very well. Just had to uninstall DSPMANAGER.

QI0CM787SV, 12/11/2010

ES1.2, cyttsp

PA2.99, 20121121
[Nook Color Android Development] webyrd:
Wiped and did clean flash of 2.99 yesterday, coming from CM10 nightlies. No problems, no SOD's (had SOD's like mad on last CM), running very nice after tweaking per tips in CM10 threads and running V6 SuperCharger. Great job, thanks Devs. Happy Thanksgiving all.