yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] mateorod:
Sure. You can use any copy of the script from U9RC6.1 on. Really, you could use earlier versions, but they aren't configured or written with ICS in mind.

You can go to the link in any of the first three posts that reference zeppelinrox's original thread and find copies of the script there. He somewhat buries the script in all the information he provides, so they can be a little tricky to find, though.

Alternatively, you could give the package manager BotBrew a try. It's a real neat program and we have the necessary packages all ready for you. The current package has U9RC7 as the script. Zeppelinrox just released a new update U9RC8.1, which we are testing but will probably be available withinn Botbrew by the end of the day. If you install the script through Botbrew before we update the package, Botbrew will show that the package can be updated as soon as we upload it, and if you want, you can set Botbrew to automatically update your packages, so you will always have the latest script installed.

Just follow the directions on the first post if you choose to try Botbrew.

If you want to run the script manually, make sure that you get a copy of the latest modded services.jar, which is needed to supercharge ICS. Without the new services.jar in system/framework, home will still be locked-in-memory and the script will complain you are only 50% supercharged.
[Nook Color Android Development] mateorod:
In the flurry of activity swirling around Botbrew, I realized I never addressed this in the thread. The v6 package now has the latest test release of the V6, U9RC8.1. It was upgraded from RC 8 soon after release to address a couple of somewhat serious bugs.

It doesn't appear that those bugs ever affected the Nook Color and this release seems nice and stable to me after some fairly intense testing over the last week. But, of course, that is no guarantee for future releases. For that reason, we will not always have the latest test release in the repo. Botbrew's V6 package was put together with ease in mind, not necessarily for those who want to test pre-pre-alpha versions of release candidates.

However, whenever a new RC candidate is put out, we will add it to Botbrew's repo as soon as it looks stable, as we did with RC8. And, if anyone sees an update that looks particularly promising, let us know. You can see which version of the v6 is in the repo by looking at the package version in Botbrew's repo. Just add 1 to the first digit and then the first three numbers are the script version.

There will be a change in the post-update protocol that will be available in the very near future that will make using the v6 even easier. I will post the details soon.

Thanks again to zeppelinrox for lending us his script for the Nook Color packages, and to Inportb for hosting them on Botbrew. Inportb is still looking for testers as Botbrew is soon to be available at Google Play, so if you are using the supercharger and haven't tried Botbrew, give it a try and let him know what you think.
[Nook Color Android Development] mateorod:
By request, Botbrew has been reconfigured to work smoothly with any dual or triple boot install to supercharge Nook Colors.

Botbrew can now automatically determine which version of ICS you have installed, 4.0.3 or 4.0.4 and will install the appropriate services.jar. This covers any ICS build from 3/10 onward. If you haven't updated to the latest builds, but still want to use Botbrew to supercharge, now you can without fear of breaking your ROM.

And Botbrew can be used to supercharge your other boot options as well. The process is the same, except Botbrew declines to swap out the services.jar on any CM7 (MiRaGe or otherwise), MIUI or Phiremod install.

Simply install the apk, run 'su -c v6' in a terminal, configure and reboot.

If you need any additional info, the first three posts have all the walkthroughs you could ever need (and more :rolleyes:)
[Nook Color Android Development] mateorod:
I've made some packages available that port PDroid to

Nook Color CM9 Roms

. The process is basically the same as for the v6 packages, except you have to add my repo first.

Update: Due to changes to the CM repo, please flash a nightly from 4/16 or later before you install any of these packages! Thanks!

Directions

Launch BotBrew (available for free on Google Play) and:

1. Add my repository

Install package repository-mateorod

2.Press the refresh button at top right. There will be two new packages.

android-framework-pdroid

This consists of modded system apps needed to use PDroid

android-framework-pdroid-v6

This is the PDroid system apps, further modded to enable the v6 supercharger.

You only need one of the above.

If you only want PDroid enabled:

Install the android-framework-pdroid package

Go directly to step 3.

If you would like the Pdroid-v6 combo

There is no way to fully supercharge a PDroid-patched build without the combo package. For now, there is a bit of a workaround to install the v6 script. You can simply install the android-framework-pdroid-v6 package if you have a copy of the script on your sdcard or:

Install the v6 package. No need to reboot

Install the android-framework-pdroid-v6 package

reinstall the v6 package.

configure v6 in terminal with su -c v6 (if you have any questions about the v6, the first three posts have all the info you could want and more.)

This will allow you to get around the dependency issue that would either leave you without the script or swap your pdroid-v6 services.jar out for just a v6 one. I know it is a bit of a pain, it will be fixed SOON.

3. Reboot and download PDroid from Google Play.

4. Upon flashing a new nightly, hit the menu button and select repair packages. This will reinstall anything wiped by the lash. Packages in Botbrew can always be removed by selecting them and pressing Autoremove.

Pdroid is a security and permission management app developed by svyat. I just created some system apps to bring it to ICS. I think it's pretty great, so I hope you try the new packages!

Thanks to svyat for Pdroid, pastime1971 for developing the PDroid port framework,zeppelinrox for the V6 Supercharger and especially to inportb, for widespread generosity and patience, and of course, Botbrew itself.
[Nook Color Android Development] grayfoxmg1:
I figured I would post my experiences with V6 through Botbrew. I've used it on about 4 updates. It saves me time integrating the replacement service.jar with each build, and it keeps it up to date.

So there's that, which is a big thing. It makes supercharging easier. However, there is something I have noticed. Whenever I run the new script, "terminal: su -c v6" It only lets me supercharge or re-supercharge. I can't fix emissions, flush, or enable nitro lag nullifier(spelling?).

In order to do any of that, I need a copy of the script on my SDcard and have to run it with script manager. Which isn't a big thing, just a small annoyance.

Over-all the system of supercharging works great, if thats all your doing. If you use any of Zepplinrox's other features, it doesn't really effect the process to much.
[Nook Color Android Development] mateorod:
Thanks for the feedback!

Hmm..if the su -c v6 starts the script, then everything that the terminal does from there is the direct result of zep's code. All the package does is install the script and run it. It's not actually a new script, all it does is invoke su, and pass the command to run the original v6 script.

What I think you're seeing is Zeppelin's post-flash script process. It (somewhat annoyingly, at times) "automagically" loads the options it believes you would want. In the case of a new flash, the preselected option is to resupercharge from the saved file on the sdcard.

What the script is doing is looking for certain files in /system. If they have been overwritten, then the script presumes an update flash.

Try this. After you are resupercharged, the script will ask you to "superclean&restart". If you rebooted after repairing and reinstalling the packages, then this is unnecessary. Enter any key for no, then Enter when prompted. That should send you to the Drivers Console, and the 31 option menu with the features you spoke of.

If you haven't rebooted yet, then do the superclean and restart. When the Nook reboots, enter the su -c v6 command again. The script should run, and send you to the Drivers console.

If the script does not run and only returns a

$ then the script may have destroyed itself. :eek:

There are two fixes. Either will solve the problem.

Select the v6 package in Botbrew and Reinstall.

Reboot immediatly after installing the v6 package, before configuring in terminal. No reboot necessary after configuring.

I am glad you find Botbrew saves you time as opposed to swapping in your files every time you flash a nightly. That was definitely one of our goals.

Of course, the real benifit is when the CM9 repo has a major update, and installing older services.jars would break your install. Instead of everyone breaking their ROMs individually, or having to check a thread to ensure the file is safe, only one person (almost always me) has to see the file became outdated. Then I can quickly update the Botbrew repo, and regular flashers have a seamless experience. So far, we have had the repo updated before eyeballer and Sam even have their builds posted!

Saving time and preventing broken installs are the driving force behind using a package manager instead of update zips that go quickly out-of-date, without warning, and catch users unaware.

Thanks again for trying the software!
[Nook Color Android Development] grayfoxmg1:
eh, its just easier to have a copy of the script on my SDcard. But thanks for the quick response. :D
[Nook Color Android Development] jakelov:
Gotta say mateorod, your threads are some of the most thorough, complete and all around easy to understand actually put into use, that I've stumbled upon in XDA. KUDOS and thanks!
[Nook Color Android Development] mateorod:
For anyone looking to supercharge or use Pdroid on the new builds with the pushed kernel, the update to the CM repo broke the system apps in Botbrew's repo. I am building new ones as we speak, so unless you are a REAL early riser, there should be no issues on your end.

Should be up sometime in the next hour or two. Thanks!

Update: Okay, the Pdroid packages are up and can be used as usual. Please flash the newest nightly before upgrading the package!

For those of you JUST looking to install the v6, whenever you flash a nightly from today or later, make sure you install my repo repository-mateorod and then upgrade to the newest android-framework-services-v6 package.

The services.jar is what went out-of-date, and since it is 4.0.4 as well, we are going to have to find a way for Botbrew to know which services.jar to install. For now, I would ask that you upgrade to the most recent nightly (whenever you read this) to be safe and ensure your install doesn't break.

If your reboot fails, which it won't if you do the above, but still, IF it breaks, just ref lash a ROM over the broken install only wiping davlik and all you r apps and data will be fine. Just get are cent nightly and do the process again and you will be supercharged in 15 mins or less.

Thanks!
[Nook Color Android Development] gumnaam.sur:
I flashed today's opengl nightly (0417), then

Using Bot Brew did the following

1) Installed v6 Supercharger

2) Installed your repo

3) Installed android-framework-pdroid-v6

4) Re-installed v6 supercharger

5) Upgraded android-framework-services-v6

6) Ran v6 supercharger from terminal (su -c v6)

7) Selected option 6, and rebooted.

8) Verified v6 was setup correctly by running 'su -c v6'

9) Installed PDroid from market

Upon launching PDriod, I get ICS not supported dialog box, and the app exits after that.

So what am I missing ?
[Nook Color Android Development] mateorod:
Sorry, the workaround to inatall the script can make things a little confusing. I made some packages to fix this and am testing them today. Hopefully, the process will be a lot more intuitive tonight. Servicing the wide-range of builds makes things a little complicated from our end.

You do NOT need to upgrade the android-framework-services-v6 package if you have android-framework-pdroid-v6.

In your case:

Launch botbrew, install android-pdroid-v6 (please refresh packages first to ensure you get last night's upgraded package)

Reinstall the v6-supercharger package.

Reboot and that should be that.

All of the android-framework packages contain a modded services.jar, sometimes among other things. Since you can only have one at a time, you actually swapped a PDroid/v6 services.jar for just a v6 one.

Thanks for trying it! Let me know how it goes!
[Nook Color Android Development] gumnaam.sur:
Yep that was it,

Re-Installed android-framework-pdroid-v6 followed by v6-supercharger

and now pdroid works.

Btw I had a hard freeze after this, and upon rebooting Nook entered boot loop.

Had to wipe cache / dalvic-cache and then all is well again.

Had to run the 'su -c v6' again, and re-supercharge from sd-card.

Great job :)
[Nook Color Android Development] gumnaam.sur:
Update

way too many freezes right now. don't know if its the 0417 build or the v6+ pdroid combo.

will do some more tests.
[Nook Color Android Development] mateorod:
Have you tried non-open gl? I don't get freezes at all.
[Nook Color Android Development] gumnaam.sur:
Yep, that's my line of thinking too. btw, what exactly do I lose by using the non-opengl build ?
[Nook Color Android Development] mateorod:
I don't really miss anything. Flash player doesn't work, but if you set something like MX Player to software decoding, internet videos play fine. Chrome doesn't work without opengl either.

There may be more, but those are what i notice. I have only flashed the openGL builds for testing purposes. It is just a little too buggy for me without hardware acceleration. But the non-opengl builds are great. There are still some little things missing, but those are future features that aren't on CM7 anyway.

Now that we have the newest kernel from keyodi, I stay pretty much amazed at what the CM team has put together.
[Nook Color Android Development] gumnaam.sur:
Yep the problem was opengl build, I've tried various opengl builds from 0407 onwards, and get consistent freezes ever 5 minutes or so.

Now on 4/19 non opengl build, and every thing is OK so far. pdroid is working great too. Thanks for your work mateorod
[Nook Color Android Development] mateorod:
Thanks for reporting back!

Gunnaam.sur reminded me I meant to do this:

If anyone is running an earlier build and wants to try the PDroid or PDroid/V6 packages (and this is the only way you're going to get both, short of building a patched rom AND decompiling your own system apps) you can download the attachments below. You need to choose just one.

These packages are available for those of you running an older nightly who do not wish to flash an update. If your build is past any of the dates below, you can install directly from Botbrew!

If Botbrew is installed, the packages below can be installed directly from any browser or file manager.

ONLY install one package at a time!

3/10-4/14

PDroid only

android-framework-pdroid_1.3.2-2_encore.opk

Pdroid+v6

android-framework-pdroid-v6_1.3.2-2_encore.opk

v6 only

android-framework-services-v6.opk_0.0.4-5

4/17-5/05

PDroid only

android-framework-pdroid_1.3.2-4

PDroid+v6

android-framework-pdroid-v6_1.3.2-4

v6 only

android-framework-services-v6_0.0.4-6

5/05-5/06

(Ouch, right?)

PDroid only

android-framework-pdroid_1.3.2-5

PDroid+v6

android-framework-pdroid-v6_1.3.2-5

v6 only

android-framework-services-v6_0.0.4-7

Current nightlies and any Android 4.0.3 builds are always supported by the package in repository-mateorod

If you are running samiam's builds, the package you need will depend on how recently he clobbered! Check the build date in the build.prop and choose your package accordingly!

We are working on a database that will be able to correctly sort which system apps your particular build would need, but that won't be ready for a bit yet.
[Nook Color Android Development] gumnaam.sur:
What should be the steps involved after flashing a new nightly on top of an existing one ? I have both v6 + pdroid setup
[Nook Color Android Development] mateorod:
Glad you asked. We've streamlined the process so it should be very easy.

1. Go to recovery, wipe davlik only, flash new nightly.

2. After booting, launch Botbrew.

3. If you have the Botbrew homepage enabled to show up, press back to get to the main program. A screen will automatically come up with a list of repairable packages (packages with some portion of their function overwritten by the upgrade zip.)

4. Reinstall the package and reboot

.

That's a in-depth look at what is, in essence, a one-click process. At this moment, the latest package is for the most current nightly, so flash 4-22 or later, since I just updated the repo. I still am working on the method to automatically place the correct packages for your build date, but I just haven't finished it yet.

Still, pretty easy, right?
[Nook Color Android Development] tonyp:
Hey mateorod,

thanks a lot for your effort here and in pastime's thread!

I just switched from CM7 to CM9 (first time after sneakpeak2, huge difference!).

Installed eyeballer's newest nightly and used the method you posted here - you could include that in the OP i think :)

Everything is working perfectly, I'm very happy with CM9, hadn't thought that I would be.

I'm using the following setup:

- non-opengl

- OC 1200MHz with OnDemand Gouvernor (I read somewhere that interactiveX might lead to SOD)

- zram/compcache default (18%)

- KSM enabled (not sure if needed)

- surface dithering enabled, 16bit transparency disabled (default values)

- v6 supercharged with option 7

Running really great. The only thing I "miss" is Chrome, but Opera is enough for now.

If anyone has further tips or opinions to my settings above please respond :)
[Nook Color Android Development] CCivale:
Hey guys....maybe someone can help point me in the right direction. I'm trying to install the latest non-gl and gapps on the emmc. I'm fine up until I install Botbrew and configure v6. When I reboot it updates the applications and then very, very quickly I get two error messages. The first is that com.android.phone has stopped working and that System UI has stopped working. Then it reboots and repeats the same process.

Any ideas?
[Nook Color Android Development] mateorod:
Hmm. I am pretty sure that things are OK on our end, although that doesn't mean that is so.

Try this. Reflash, and instead of installing the v-6 package, install android-framework-pdroid-v6. To have the script run in a terminal, you can do this:

Flash current nightly

Install v6 and then BEFORE rebooting

Install android-framework-pdroid-v6

Reboot.

If it boots with no issues, then go ahead and configure the v6 in the terminal with such -c v6.

Let me know if that works. I will probably just update the services.jar in the repo to be safe
[Nook Color Android Development] tonyp:
It did work for me. Maybe you didn't install and reinstall the right packages (or in the right order?)

Btw mateorod: congratz to your (and pastimes) headline :-)

www.xda-developers.com/android/botbrew-used-to-port-pdroid-to-more-devices/
[Nook Color Android Development] CCivale:
Just tried this out, but still getting the same two errors and the boot loop.

I'm not sure what order you used but I rebooted into recovery, wiped EVERYTHING, flashed the latest nightly, gapps from 4-22, rebooted, downloaded botbrew, downloaded the v6 package (using botbrew), tried both configuring v6 first and rebooting and rebooting without configuring, but neither way worked.

I'm just scratching my head trying to figure out what I'm missing.

The thing that's confusing me is that if I don't install Botbrew, then my system is stable and I can reboot all I want and no loop.
[Nook Color Android Development] mateorod:
That is strange. I have tested the newest pdroid-v6 package on the 4-22 nightly myself. This is for a Nook Color, right? And no packages are working for your nightly?

I thought maybe there was a corruption just with the v6 package, but if neither work, i don't know.

I will go through the process you described tonight and tomorrow morning. We'll get to the bottom of it. Sorry it isn't working for you right now. I will find out why.
[Nook Color Android Development] slack04:
How long is the first boot supposed to take? In the guide, it suggests that the first boot takes a long time. I've been watching the bootanim (on eyeballers opengl 4/22) for about 20 minutes. I might be in a bootloop, but the screen never goes dark, just occasionally the animation freezes, but then it starts back up a few seconds later. I followed the guide (except used 6 instead of 7).

Yikes. If this is a bootloop, what should I do? Waiting patiently for a response and hoping I'm just being impatient...

**edit: OK, not sure how much longer I can be patient. This thing is starting to warm up. Grrrr....
[Nook Color Android Development] inportb:
Sounds like a boot loop. It's taking way too long and the animation is breaking in the middle. If you're hooked up via USB, logcat would also show a loop. If so, you might try:

pulling the original files from your update.zip/system/framework/ (core.jar, framework.jar, and services.jar)

remounting /system read-write on your device

pushing those jars to /system/framework/ your device via adb

finally rebooting

You could also do this in recovery, with /system mounted. Of course, you could also just straight-up flash that zip.
[Nook Color Android Development] mateorod:
Okay, I think you are talking about the v6 package, right? I just installed it and it is working for my machine, but I may be running a different build, I have flashed a lot today. I can only think that the repo has updated on that package. I will build a new one, it should be up in 30 mins.

Don't worry, you'll be fine with no loss of data if you haven't done anything drastic yet. Manually restart the Nook by holding the power button for 8-10 seconds. When the cyanoboot logo comes up, hold the 'n' button and a menu will come up.

Select whichever recovery you are running, Internal if you have CWM to emmc, SD card if you have an SD card install.

JUST wipe davlik and reflash any CM9 (or CM7, really) ROM. The boot will go through fine and it will be just as you had it.

We're lucky with the Nook Color, my friend. Nearly impossible to hurt/brick.

Check back here within the hour, I will rebuild the v6 package from YOUR ROM, so we can know it works! I'll test it with tonights build when it posts, to make sure it stays current.

Thanks for trying it, we'll set you straight, I promise.

Edit: Oh, and for next time, the boot should only take 2-3 mins and then a message about optimizing should come up with a countdown of your apps. 5-7 mins, tops.
[Nook Color Android Development] slack04:
Hi- Thanks! I was holding the power button down just as your response came. Followed your directions and it appears I'm in the clear. Don't worry about making another build tonight, I don't have any more time anyways. Who knows what happened; it was probably my fault anyways...
[Nook Color Android Development] mateorod:
Okay, to everyone who had a problem tonight, we apologize. Our fault. :eek:

Basically, to have the most recent versions of any package made by me, you need to install the repository-mateorod package first. Because inportb was hosting some earlier versions in Botbrew's main repo, we didn't even notice that the packages might not be up to date for some people.

Sorry for what must have been a somewhat frustrating night of flashing! Thank you both for reporting back. Since inportb and I both keep repository-mateorod installed, who knows when would have found it if you hadn't brought it to our attention!

The instructions to use any package on this thread are the same, but you must install repository-mateorod first.

I will update the various guides. You are safe to supercharge, and again, thanks a bunch for your patience.