yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] les02jen17:
May I ask how you we're able to run V6 SuperCharger? I can certainly run it via SManager but I never was able to apply the "launchers" as they call them (die-hard, hard-to-kill+ bulletproof, etc...) hence only achieve 50% supercharged. Based on what I've read it's to do with a modified services.jar. I can never get ApG to work to be able to male one, unfortunately. :( Care to help?
[Nook Color Android Development] lollyjay:
I have an interesting situation. When I plug in to USB on my windows 7 laptop:

1. Do not see a prompt to allow access to SD;

2. Do not see "eject" option on the laptop

The Nook Color shows as a drive, and allows full access.

Can anyone try and either confirm or tell me I'm nuts?

QI0CM787SV, 12/11/2010

ES1.2, cyttsp

PA2.99, 20121121
[Nook Color Android Development] webyrd:
I only got 50% also, running good so I did not try messing with the services.jar - saw instructions on Zeppelinrox's V6 thread but didn't bother since I am flashing so often - sorry I don't know more about it

---------- Post added at 12:39 PM ---------- Previous post was at 12:31 PM ----------

Settings > Storage > menu button > USB computer connection > Mass Storage
[Nook Color Android Development] mateorod:
I know that the Autopatcher can automatically 100% supercharge this rom; GreyFoxmg1 uses it for every update. There is a link to the program in my sig, and if you are on windows, look for the link to ApG, a windows GUI.

The program runs on Mac, Linux and Windows, and it is a 1 step process. Post in the autopatcher thread, I can help you if you need.

Is this different than the CM10 behavior? That is kind of the baseline here. As I love to remind everyone, we use their device/kernel trees. So everything except the UI is the result of their hard work.

Now if you experience something with PA you don't see with CM10, then that is where I come in. ;)
[Nook Color Android Development] webyrd:
Thanks for the Autopatcher info, will try when I get time

I saw the mass storage thing on the CM10 nightlies also
[Nook Color Android Development] grayfoxmg1:
You know it ;) However I will say that whomever is using auto_patcher shouldn't be stupid like me and try and use the tabletUI patch on PA :Facepalm: But ApG does patch this ROM, initial boot takes a bit(but I'm hearing that from people who don't patch their ROMS as well. If you absolutely cannot get it to work on your computer, than send me a PM and I'll see if I can help out.

Tips for people using/or attempting to use ApG:

1. Norton, McAfee, and Viper anti-virus programs WILLNOT allow you to download Apg, they quarentine the file before you get any say in the matter. I could go into a few paragraphs explanation on why I THINK this happens, but it boils down to Microsoft wanting money for something that isn't needed for our shareware program that has been lovingly crafted and maintained by our fellow XDA member(big thanks btw love the program).

You can download the file by disabling your anti-virus/firewall program before clicking the download link(addendum: Everyonce in a while my computer still won't download the file so I have to disable everything Norton related and <gag> use Internet Explorer </gag>).

2.If after running the program you get an error and after closing it see what the error was caused by ApG disappears, your anti-virus tagged the running process and followed it to the program and quarantined/deleted it. Again you must turn of AV and firewall stuff BEFORE running the program.

3. Anytime you preform a virus check, it will tag ApG as malicious software(pfft malicious) and remove it making you re-download it.

NOTES: There are absolutely NO virus, worms, Trojans, Athenians, or Persians in this software(though I think a couple of Spartans might live in it ;) ). Likewise, unless someone has overhauled the entire site(which would be really impressive) There aren't any of the before mentioned items on the file-sharing site we download ApG from. So feel free to disable your AV when downloading or using ApG.

This has been a public service announcement provided by Grayfoxmg1, have a good day.
[Nook Color Android Development] sisterchick:
Running 1121 nightly and all is well. Noticed an improvement with the Kindle app performance vs straight CM10. Just curious what Scheduler some of y'all are running. I am using BFQ.
[Nook Color Android Development] webyrd:
I am also using BFQ, helped with the CM10 lag, stuck with it
[Nook Color Android Development] grayfoxmg1:
using cfq, and have no problems to report
[Nook Color Android Development] les02jen17:
Staying at 1GHz, IO is noop and running V6 Supercharger, 100% supercharged. Almost unnoticeable lag. Whenever I bump it up to 1.1GHz I get problems.
[Nook Color Android Development] RoboticBuddy:
I have my Nook set the same as yours, with I/O as noop, but I clocked it to 1100 MHz and didn't have any problems. I also have 16Bit enabled, as well as zRAM (26%), and everything enabled in Memory Management.
[Nook Color Android Development] grayfoxmg1:
So I made a simple sig to show that I use this ROM and figured I'd share, enjoy :D
[Nook Color Android Development] jayjay7411:
Where can I get this 1.8.1 apk?
[Nook Color Android Development] boyoboyo:
Any link to a gapps 4.2? I can't seem to spot a normal one.

In the meantime I'm using the 4.1.2. Is that OK?
[Nook Color Android Development] whiffer2:
Yes, you should be fine with that.
[Nook Color Android Development] dparrothead1:
http://www.mediafire.com/?ggyws8c8g9kgbht
[Nook Color Android Development] boyoboyo:
Reboot on SD unmount

Any body else experiencing Settings->Storage->Unmount SD cause a reboot?

I get that every time...
[Nook Color Android Development] mateorod:
I have had a bunch of trouble with sdcard mounting, from betas through to today. Haven't spent any time looking at it though...

Lots of crashes and reboots, occasionally into a black screen, which I sometimes have to use a bootable CWM card to get out of.
[Nook Color Android Development] leapinlar:
Lots of people are experiencing that, me included (remember me telling you the first time I tried your beta PA?). It appears that CM10 is more sensitive to SD errors than other versions of CM or Windows. If it thinks something is wrong with the card, it won't mount it or mounts it and sets it read only and you are in a bunch of hurt. There are two solutions. Sometimes formatting with the Windows program SDFormatter fixes it, either permanently or temporarily. If it does not fix it, get a better card and format it with SDFormatter. CM10 is just picky. I suspect it is something in the new kernel, but I am no dev, so don't know.
[Nook Color Android Development] -somebody-:
here ya go

Netflix-1.8.1.apk

i dont use netflix personally but i was bored and hunted this down incase anyone else needed it.
[Nook Color Android Development] mateorod:
I'm going to link to this from the OP. I see folks asking about it everywhere. Thanks -somebody-.
[Nook Color Android Development] -somebody-:
welcome, glad to be of service.
[Nook Color Android Development] lorddunlow:
Switched to this ROM last night after getting tired of flashing the tabletui zip on cm10. I also wanted to have setting toggles with tablet ui. This ROM is awesome. Running very quickly with no issues so far. Looking forward to playing with the settings for individual apps.
[Nook Color Android Development] homerxd:
I am trying to flash 21NOV2012 zip and everytime I try to flash.. I get error saying " Error in /sdcard/download/pa_encore......zip" (Status 7).

I tried to download zip again.. also tried zip from goo.im and link in OP

Any help is appreciated.. I currently run CM10 nightly.
[Nook Color Android Development] -somebody-:
try wiping everything correctly then flashing
[Nook Color Android Development] homerxd:
I did.. multiple times.. every time same error.
[Nook Color Android Development] leapinlar:
Status 7 means either there is something wrong with the zip commands built in or one of the safety tests it automatically runs is failing. Like one of the tests it runs is checking to be sure you are really flashing this to a Nook Color. You are aren't you?

How are you trying to flash this? With TWRP or CWM and from emmc or a bootable SD.

Edit: Rootzwiki says Status 7 usually means a corrupt download, or bad file signature. Re-downloading will usually fix it. But you have done that. I suggest you go to play store and install goomanager. It will download that file for you and check the md5 sum to be sure it downloaded properly.
[Nook Color Android Development] homerxd:
I had to use twrp to flash nov212012 rom.. the zip nov182012 worked fine with cwm.

thanks for your inputs.
[Nook Color Android Development] leapinlar:
The difference might be how your CWM was set. When you go to the install zip from SD menu there is an option to disable verification. That is the feature that checks signature. On older CWMs, I think the default was to always verify. I think on the newer versions and TWRP that is turned off by default. CWM may have had a problem with the PA zip signature.
[Nook Color Android Development] mateorod:
I philosophically oppose touch recovery, so I use CWM 3.2.0.1 still...no problems here. I would be interested to know what the problem was.
[Nook Color Android Development] WJThomas:
I tried switching to touch recovery on the nook colors that just I got my kids. After flashing touch I discovered that the zips to repartition do not work with touch. I ended up going back to cwm. I did upgrade to 5.5.0.4 on theirs (extracted from the boot SD image), but I still have 3.2.0.1 on mine.
[Nook Color Android Development] leapinlar:
Try toggling the verification to verify on and see if you can flash that one. It may have a signature problem.
[Nook Color Android Development] lepa71:
run from sd card

Can I run this from sd card?
[Nook Color Android Development] leapinlar:
Yes. Follow the directions in my updated SD instructions linked in my signature. Just be sure to rename the zip to beginning with update- so the installer script will recognize it.
[Nook Color Android Development] mateorod:
No, it works with signature verification on and off. If anyone else see that problem, let me know, but for now I feel pretty good that everything is working like it should.
[Nook Color Android Development] grayfoxmg1:
I had something similar happen, it just required a FULL wipe, and I couldn't use TiBu to restore system data
[Nook Color Android Development] boyoboyo:
Suddenly it doesn't sleep (reboot helped)

I left my my nook on the table at night, haven't pressed the power button, and at morning I've found out that the screen was still on (battery dropped to ~10%). I plugged in the charger and went back to check after half an hour - still haven't gone to sleep.

A reboot fixed the issue.
[Nook Color Android Development] nfreebairn:
great rom, one question

This rom is great. Thanks. One question: if I am already running cm10 on my nook can I flash this as I would an update (clear cache and dalvik only) or do I have to do a factory reset? Just wondering if this is something I could easily switch between or not.
[Nook Color Android Development] grayfoxmg1:
clean flash is recommended
[Nook Color Android Development] dparrothead1:
You need to do a full wipe......but you will most likely not be switching back and forth once you try this ROM.
[Nook Color Android Development] RoboticBuddy:
I just flashed 2.99 21NOV2012, it seems to be running very smoothly, but battery life still isn't too great, but improved :P.

Anyways, I have a few questions.

How do you stop the Status Bar from hiding in Fullscreen apps?

How do you enable the Rotation Toggle in Tablet Mode?

Thank you in advance. :)
[Nook Color Android Development] thejrcrafter2:
I was able to dirty flash from cyan to paranoid just fine, no data wipe. That was one of the very early builds, sao I don't know about now, you could still probably dirty flash just fine since its essentially the same operating system just with more settings, I'd only clean flash if you have some sort of navigation bar tweaking app or the build.prop tablet mode.
[Nook Color Android Development] RoboticBuddy:
I am also able to dirty flash from CM10 on the newest update. In CM10, I flashed the TabletUI mod, and then dirty flashed to PA 2.99, works perfectly,
[Nook Color Android Development] ahecht:
I'm on 2012-11-21, running off SD, and I have an interesting bug where the backlight will flash on briefly from time to time when the screen is off. The screen stays black, and the blinks are very short and dim. I only really notice them in a dark room, but they can be annoying if I'm trying to sleep.
[Nook Color Android Development] grayfoxmg1:
YES!! It's not just me, I though I was going insane as I have only ever seen the flash out of the corner of my eye, and when I would stare at my Nook it wouldn't flash at all.
[Nook Color Android Development] leapinlar:
CM10 folks are also reporting this bug.
[Nook Color Android Development] derekr44:
ParanormalAndroid? :laugh:
[Nook Color Android Development] nfreebairn:
crashing and boot-looping

well i did a dirty-flash and ran into some crashes and boot-loops so I did a full-wipe and clean install ... got the same results. very odd. it will just pause/jam and every time (crash or not) i restart it needs to wipe dalvik cache to get out of a boot-loop.
[Nook Color Android Development] plasticarmyman:
I just did a clean install...well..wiped system and cache, but not data....so semi clean?...and i have to say I love it. Thank you for porting this over...

also...i noticed a 2nd easter egg on this ROM :)
[Nook Color Android Development] WestChi:
Anyone else having issues with keyboard has stopped error and no onscreen keyboard. I can't even get my Bluetooth keyboard to work.
[Nook Color Android Development] hwong96:
Make sure to use the 4.1.x GApps not the 4.2 GApps.
[Nook Color Android Development] AidenM:
Hi,

whenever I try to press the home button (hw or soft) it doesn't do anything.

What's going on?

Thanks
[Nook Color Android Development] WestChi:
Thanks
[Nook Color Android Development] bretzke:
Had the same problem...maybe the OP should reflect this.

Otherwise nice.

Dave
[Nook Color Android Development] mateorod:
I didn't know anything about this. It is a CM10 (or more accurately AOSP) problem, not a ParanoidAndroid problem. If I listed every known issue for CM10/AOSP, not only would maintaining the OP take all my time, but then the useful stuff would get lost. Users are going to have to rely on Google and each other for things of this nature.

Since I'm here...

We have not forgotten about the nightlies. Right as we made the move to committing to providing them, the upstream ParanoidAndroid repos went dark. They are in the process of switching to AOSP, and as is their practice, have closed the repos until they are satisfied with the migration.

That kind of leaves us in a pickle of sorts. I could rebase all of our existing PA repos on Cyanogen, and maintain the commits individually, but then I would have to revert it right back once they finished moving to AOSP. I have been taking the position that since their last release was 2.99, 3.0.0 could not be far away.

So I am keeping my eye on it, thanks for being patient. If there is anything particular you see in CM10 upstream (not CM10.1), let me know and I can add it for you. I am working on the source on my local machine, but haven't seen anything that warranted starting or maintaining more forks of my own.

Thanks everyone.
[Nook Color Android Development] leapinlar:
It is a PA problem too. What they are saying is, since you base your PA on CM10. 0, which is jellybean 4.1.x, you should warn users to download the 4.1.x version of gapps, not the 4.2 version. They won't know PA is 4.1.x unless you tell them.
[Nook Color Android Development] mateorod:
Fair enough. 4.1.2 will be stressed on OP.
[Nook Color Android Development] aniym:
I'm running the latest nightly and having constant crashes on the stock browser and Dolphin Browser. I did a clean wipe and install from a previous CM10 nightly, which didn't have these crashes (it was laggy though). I'm running CM10 Gapps as well.

I did a thread search and no one else seems to be affected by this. Any ideas on what the problem might be?
[Nook Color Android Development] WestChi:
Thanks for the help, didn't want to start a commotion over it. I'm still new at this, this is only my 3rd device rom/root.
[Nook Color Android Development] davidr415:
mateorod..

Could you explain the significance of PA "switching to AOSP" (a quote from your last psot).. will that make i different, better/worse, faster/slower, more features, etc...

Thanks.. just looking for some education..
[Nook Color Android Development] mateorod:
Sure...

Firstly, all Android roms are based on AOSP. Google releases their source code which makes it available for people, like Cyanogen or Samsung or whoever, to make their own modifications and release their own Android flavors. So when I say they are rebasing on AOSP, that is a bit misleading, since Cyanogen is itself an AOSP rom. But Cyanogen is a full-featured fork of AOSP.

When PA started, the devs intended to commit it to Cyanogen as a new feature. That ended up changing, why I do not know. Maybe they decided to keep it, or quite possibly the CM team indicated that it was not a feature they were willing to add. CM has really worked at keeping the settings to a minimum, after CM7's settings overload they try and keep things very simple.

One way or another, PA ventured out on their own. It started as a replacement frameworks and additional vendor files. But since they are not going to be joining Cyanogen, I guess they want to establish themselves as a full rom and not a Cyanogen kang. The first steps to truly making that happen is to take their repos from Google's AOSP. This will be a long process, and is somewhat misleading. CM has years of work porting full Android to all sorts of devices, difficult work with proprietary files and especially working with device folders and hardware. The PA team will likely never completely split off from Cyanogen. Someday, someone will start that stuff from scratch, but it will be a monumental undertaking.

Right now, they are forking the AOSP (as opposed to the CM versions) of many of the Android projects, and are probably not doing much more than catching up with the commits that allow it to build and run correctly. As time goes on and people commit upstream to PA (assuming they start actually merging submissions, something I have not seen them do) the forks will become more robust and begin to take on more of a personality as opposed to the more workman-like quality they will have at first.

They are waiting until they get their builds stable before releasing the source, which is why nightlies have stalled. I could go ahead and rebase it back to CM, but then I would have to undo that again once they put out 3.0. And since they have not been keeping up the compatibility, it would be a good bit of work. So we wait, for now. If it takes much longer, I will fix up our tree and put out another CM build, just to keep the flashoholics (like me) happy.

TL;DR: If you consider AOSP a food, let's say it is fruit. Cyanogen is a type of fruit, let's say a peach. Previously, ParanoidAndroid was a type of peach, a Georgia Peach, or something. But now they do not want to simply be a kind of peach. They have the ambition to be a brand new type of fruit, an apple maybe. But because of all of the irreplaceable work that the CM team has done with hardware and device trees, the apple is likely to always have a peach pit inside of it.

Make any sense?
[Nook Color Android Development] davidr415:
Makes perfect sense.. thanks a bunch..

Your explanation does raise another question in my mind, however.

It sounds to me (based on how I am reading your explanation), that, whereas we have a 1-to-1 relationship to new CM10 releases now, that may not be true in the future and CM10 may "progress" faster while PA is just trying to get the basics right.. is that a correct conclusion or will the continuing "peach pit" keep that from happening?
[Nook Color Android Development] Tiezane:
But, I don't WANT to own an apple product! ;)

Thanks for the explanation Mateo!

Sent from my Sega Master System via Carrier Pigeon.
[Nook Color Android Development] mateorod:
Well, it could be good and bad. We will continue to get ALL of the Nook related work. So the device trees and kernel the guys have been and continue to work on will always be in these builds.

The larger CM efforts will most likely be continued to be in these builds. Their ambition is to be based off of AOSP, but that won't happen over night. They are just no longer forking CM projects by default. They still will have many, for now and the near future.

And AOSP code is improved daily as well, so we will get the upstream AOSP stuff. My guess is that you will see PA be a little more aggressive about features than you would even see with CM. In my experience, cyanogen is very meticulous about this stuff, they think long and hard before adding any new settings. You won't see a navbar themer in CM, ever. But I think that PA's ultimate goal is to be noticed by upstream AOSP, so I wouldn't expect it to explode into AOKP, either.

We'll just have to wait and see, but if there is anything people want from CM that they don't see in ParanoidAndroid 3.0, let me know and I will see what I can do.

HA! Perhaps that was an ill-considered choice on my part.
[Nook Color Android Development] lekofraggle:
I tend to like AOSP. It seems a bit lighter than cm. I wonder though if the main devs are building for it as well.

Since the beginning of in, we have built for cm. So I wonder if we may accidentally lose dependencies in the shift.

This is all hypothetical mind you. I have been building and designing on cm, and though I would like to build aosp, have not taken that plunge

~Leko

Sent from my ADR6425LVW using Xparent Cyan Tapatalk 2
[Nook Color Android Development] mateorod:
I have an aosp build for encore I am working on. I have two major problems with it for now, the rotation/screen display is reversed, and there is an ever-building backup of skipped frames until lag renders it unusable. We'll see.
[Nook Color Android Development] voodoomurphy:
Guys,

I'm in a bad spot here. I've tried installed the ROM twice now and had no luck with the GApps. I've tried manually flashing the apps and adding them via goo and nothing happens. Goo says it's flashing, the screen goes dark but nothing happens unless I restarts the nook. Any ideas?
[Nook Color Android Development] leapinlar:
If you are having problems, it is best not to use goo to do the flashing. It is ok to let it download the zips, but not flash. When it downloads it automatically checks the md5 sum to assure it was downloaded properly. But flashing requires that you have the right recovery installed. Manually boot to your recovery, CWM or TWRP, and manually flash the zip.
[Nook Color Android Development] WestChi:
I love this thing! It is nice and smooth I installed it on a 64GB sandisk class 10. The only problem I am having is viewing magazines in the native nook app. I get a black screen and the only way I can get a page to appear is to tap on it to display the page navigation on the bottom and then it loads. The annoying part is that I have to do it on every page, I checked the settings but I can't find anything to change.

Thanks
[Nook Color Android Development] disynthetic:
just an aside with regard to battery life. do people still manually delete phone.apk from /system/app/? that still boosts battery life for me on my nc.

too bad we'll never see hw ui accel. random.
[Nook Color Android Development] moocow1452:
If I can ask, what would be the better experience at this point to Flash, between CM10 nightly or PA equivalent? I'm enjoying the CyanDelta experience of keeping up to date, but would jump ship if Paranoid is markedly faster or more stable. Is that even a fair question to ask?