[Packages][7-16] ICS V6 Supercharger- now w/ PDroid

Search This thread
By:
Advanced…
B

bdcrim

Senior Member
Oct 27, 2010
500
79
mateorod said:
Hmm. I am using it in eyeballer's build for 3/30, and it is okay. However, some merges may be missing, the tablet info does say 4.03 still.

I was concerned that the update would break it though, so it isn't a real shock. I will have to wait until the builds come out tonight to make sure a new services.jar will be compatible going forward.

My repo got broken adding in a patch attempting to port PDroid, or I would build now and put it right up.

Where did you get your ROM? Is it out there already or did you build it yourself? If I can get my hands on a 4.04 services.jar we can have a working package in relatively short order.

Thanks for the heads up, though. I test these nightly, but maybe my nightly is a night behind:rolleyes:
Click to expand...
Click to collapse

It was a build I put together myself around noon today, Central US time. Here is the services.jar from the build. Is that what you are needing?
 

Attachments

  • services.jar
    842 KB · Views: 4
  • Screenshot_2012-03-30-22-30-28.jpg
    Screenshot_2012-03-30-22-30-28.jpg
    31.9 KB · Views: 291
  • Like
Reactions: mateorod
M

mateorod

Inactive Recognized Developer
Nov 16, 2011
1,981
3,503
New Orleans
www.gigmasters.com
bdcrim said:
It was a build I put together myself around noon today, Central US time. Here is the services.jar from the build. Is that what you are needing?
Click to expand...
Click to collapse

Yep, that'll be it! It seems that the public builds are a little behind yours. But I will use this to be ahead of the curve for when the 4.04 goes public.

I will modify this now but am going to hold off updating the repo until the public builds go to 4.04, as it will be incompatible for the large majority of our users who use the posted zips. But I will put it up for you and anyone else who is using a 4.04 build of their own making.

You will need a copy of the latest script as well, as the v6 package will automatically swap out the newer services.jar for the old. You can go get that while I make this new file.

I know that this is a bit of a hassle, it is the danger of having incompatible builds around at the same time. Inportb and I are working on a solution to this problem which should be ready before the next update to the framework (god willing and the creek don't rise).

Here is the link to zep's script for those using 4.04. Use U9RC7 and check back here in maybe 45 mins for the required services.jar.

Thanks for posting the file and for trying BotBrew. Once the common builds get to 4.04, we'all put the newest file in the Botbrew repo, so every time you use it, you will be installing a version of your own file! Thanks for being part of the process.
 
M

mateorod

Inactive Recognized Developer
Nov 16, 2011
1,981
3,503
New Orleans
www.gigmasters.com
Okay, here is the services.jar for the 4.04 builds only! Check your tablet info in the settings menu to make sure you are running 4.04 before using this file!

I am leaving the services.jar in the repo current with eyeballer's builds on techerrata. Since they still show 4.03, I am going to leave the older services.jar there. Therefore:

If you are building your own, and have 4.04, unzip this download and swap the services.jar in system/framework in your zip before flashing. Flash the ROM as usual, and then run the v6 script in a terminal. Just navigate to where you have the script from the link in the last post stored and type sh V6*. Then configure as usual.

If you are using eyeballer's builds, as soon as I see the techerrata zips are upgraded to 4.04 I will have Inportb add the new services.jar to the repo. So basically, you can use Botbrew as normal without worry unless you are trying to supercharge immediately after they go up. I have to use some time to test, and so you could beat me to it in that case. If that happens and your build breaks, don't panic! Just go to CWM and reflash the original zip and you will not lose any info or settings!

But check this thread before using Botbrew to supercharge any 4.04 build, just to be safe. I will update the OP when the repo itself is officially updated.

http://db.tt/B6iWY7DI -4.04 services.jar
You will need a copy of the V6 script to use this properly. Don't use the Botbrew package if you swap the services.jar manually! The link to the script is in the last post.

Many thanks to bdcrim for providing the unmodded 4.04 services.jar!

We realize having two services,jar files is a bit of a hassle, but there is no way around it as there are two different build versions around. We will keep Botbrew inline with the version we feel the majority of people are using, which for now is 4.03.

We have made some major strides in eliminating this problem permanently, but that will have to be a post for another day (hopefully soon)!
 
Last edited:
B

bdcrim

Senior Member
Oct 27, 2010
500
79
mateorod said:
Okay, here is the services.jar for the 4.04 builds only! Check your tablet info in the settings menu to make sure you are running 4.04 before using this file!

I am leaving the services.jar in the repo current with eyeballer's builds on techerrata. Since they still show 4.03, I am going to leave the older services.jar there. Therefore:

If you are building your own, and have 4.04, unzip this download and swap the services.jar in system/framework in your zip before flashing. Flash the ROM as usual, and then run the v6 script in a terminal. Just navigate to where you have the script from the link in the last post stored and type sh V6*. Then configure as usual.

If you are using eyeballer's builds, as soon as I see the techerrata zips are upgraded to 4.04 I will have Inportb add the new services.jar to the repo. So basically, you can use Botbrew as normal without worry unless you are trying to supercharge immediately after they go up. I have to use some time to test, and so you could beat me to it in that case. If that happens and your build breaks, don't panic! Just go to CWM and reflash the original zip and you will not lose any info or settings!

But check this thread before using Botbrew to supercharge any 4.04 build, just to be safe. I will update the OP when the repo itself is officially updated.

http://db.tt/B6iWY7DI -4.04 services.jar
You will need a copy of the V6 script to use this properly. Don't use the Botbrew package if you swap the services.jar manually! The link to the script is in the last post.

Many thanks to bdcrim for providing the unmodded 4.04 services.jar!

We realize having two services,jar files is a bit of a hassle, but there is no way around it as there are two different build versions around. We will keep Botbrew inline with the version we feel the majority of people are using, which for now is 4.03.

We have made some major strides in eliminating this problem permanently, but that will have to be a post for another day (hopefully soon)!
Click to expand...
Click to collapse


Thanks for putting this together. Supercharged once again.

Sent from my NookColor using xda premium
 
  • Like
Reactions: mateorod
M

mateorod

Inactive Recognized Developer
Nov 16, 2011
1,981
3,503
New Orleans
www.gigmasters.com
Now that the update to Android 4.04 is complete and available in the unofficial nightlies, the supercharger packages in Botbrew have been upgraded to reflect the change.

Please, only use Botbrew to supercharge builds 3/31 and later, or in other words, only Android 4.04. Check the tablet info in settings if you aren't sure.

Thanks again to bdcrim, who gave us a heads-up on the breakage before it went public. I test the packages nightly, so it would have been caught, but his post allowed the upgrade to be simultaneous with the nightly. Pretty cool!
 
M

mateorod

Inactive Recognized Developer
Nov 16, 2011
1,981
3,503
New Orleans
www.gigmasters.com
Hey, thanks for bringing that up. I hadn't seen that was out. I'll play with it some today and report back. I have been told it basically adds a fix permissions function, so I don't see why it wouldn't work. Better safe than sorry, though.
 
  • Like
Reactions: grayfoxmg1
RASTAVIPER

RASTAVIPER

Senior Member
May 2, 2011
3,798
834
Could someone advise me which version of V6 is suitable for Racks dualboot rom with ICS 4.0.3?

Unleashed from my Nook Color at 1.2G
 
M

mateorod

Inactive Recognized Developer
Nov 16, 2011
1,981
3,503
New Orleans
www.gigmasters.com
RASTAVIPER said:
Could someone advise me which version of V6 is suitable for Racks dualboot rom with ICS 4.0.3?

Unleashed from my Nook Color at 1.2G
Click to expand...
Click to collapse

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.
 
Last edited:
M

mateorod

Inactive Recognized Developer
Nov 16, 2011
1,981
3,503
New Orleans
www.gigmasters.com
grayfoxmg1 said:
We have any news on if the RC8 script works for us?
Click to expand...
Click to collapse

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.
 
  • Like
Reactions: inportb
M

mateorod

Inactive Recognized Developer
Nov 16, 2011
1,981
3,503
New Orleans
www.gigmasters.com
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:)
 
  • Like
Reactions: dfense27 and inportb
M

mateorod

Inactive Recognized Developer
Nov 16, 2011
1,981
3,503
New Orleans
www.gigmasters.com
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.
 
Last edited:
grayfoxmg1

grayfoxmg1

Senior Member
Aug 9, 2009
1,101
605
Paw Paw, Mi
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.
 
  • Like
Reactions: mateorod and inportb
M

mateorod

Inactive Recognized Developer
Nov 16, 2011
1,981
3,503
New Orleans
www.gigmasters.com
grayfoxmg1 said:
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.
Click to expand...
Click to collapse

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!
 
Last edited:
  • Like
Reactions: grayfoxmg1 and inportb
M

mateorod

Inactive Recognized Developer
Nov 16, 2011
1,981
3,503
New Orleans
www.gigmasters.com
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!
 
Last edited:
G

gumnaam.sur

Senior Member
Jan 2, 2012
72
33
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 ?
 
  • Like
Reactions: mateorod
M

mateorod

Inactive Recognized Developer
Nov 16, 2011
1,981
3,503
New Orleans
www.gigmasters.com
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!
 
Last edited:
  • Like
Reactions: gumnaam.sur
G

gumnaam.sur

Senior Member
Jan 2, 2012
72
33
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 :)
 
Last edited:
  • Like
Reactions: mateorod
You must log in or register to reply here.

Similar threads

D
[DEV] CM11 Work-In-Progress
Replies
4K
Views
2M
owim
owim
phiredrop
[ROM][May 29 2011] >>> phiremod nook V6.3 <<< | TEST Build Available
Replies
2K
Views
730K
G
gryphon101
S
[DISCONTINUED] CM9/ICS Nightly Builds
Replies
2K
Views
663K
cammykool
cammykool
D
Android 3.0 Honeycomb Preview Image v04 - 2/7/2011
Replies
2K
Views
1M
fattire
fattire
I
[2015/03/07] BotBrew: *nix tools for Android
Replies
234
Views
126K
Y
Yunfengdong

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 29
    M
    mateorod
    7-16: Some news. Well, I have some borked hardware and have begun to feel like, to new users, this thread might be more frustrating than helpful.

    Therefore, if you are new to the thread/process, I would like to recommend that you try the Auto-Patcher instead. It ports all the functions of this thread (it is what I use to make the packages in the repo) with the assurance that the output won't be incompatible with your ROM.

    Please see the release/support thread for the Auto-Patcher for downloads/help.

    I am more than proud to have introduced so many of you to Botbrew and native Android package management. Inportb has put together a rock-solid platform that only improves with time. It was a distinct pleasure to watch it evolve, and I hope you all keep an eye on its progress.

    I consider it to be the most powerful app available. There are literally limitless possibilities, software porting being among the least of them. I can't wait to compile my first ROM on a tablet- it will be Botbrew that makes it possible. The possibility of our mobile devices replacing laptops are only possible through things like this, and right now, Botbrew is the only game in town. I expect it to remain the standard.

    Thanks, all. If you would like an existing package updated, you can always request it in the thread. I can no longer maintain in advance, but I will be happy to offer support on demand.

    If you are new, please try the Auto-Patcher instead! Link above!

    Offered Packages (only for Nook Color!)
    • mateorod-v6
      Package that enable the v6 supercharger
    • mateorod-pdroid
      Package that installs the framework for PDroid
    • mateorod-pdroid-v6
      (wait for it...)Package that enables BOTH the v6 supercharger and PDroid

    If you don't know what the v6, PDroid, or even Botbrew does exactly, please see the information section farther down this post.

    Install Directions

    • Download and install Botbrew, free from Google Play. Botbrew will bootstrap in opkg or dpkg-apt along with several other packages necessary to its operation.
    • Install package repository-mateorod and press the refresh packages button at top right.
    • Install the mateorod-whatever package of your choice.
      This will be the only system app package you will need to install. Any dependencies will automatically be resolved by its installation. That includes the v6 script.
    • Reboot.

    If your mateorod package includes the v6 supercharger
    • After reboot open a terminal and enter the following:
      Code: 
      su -c v6
      The v6 script will run immediately and you can configure it from there. If you have any lingering questions about the configuration, please see the artifact that is post #3.
    • If this is your first time upgrading the V6 since update 8, (the one mrg666 used to recommend) don't re-supercharge from your sdcard or you will encounter mount issues! Just configure from scratch.

    If your mateorod package includes Pdroid
    • Install PDroid from Google Play and configure

    That's it!

    **Should you ever wish to reverse these system changes, Botbrew completely takes care of that for you, restoring backups of every file modified by the process! Simply select the mateorod-whatever package and press Autoremove.

    **Upon flashing a new nightly, just launch Botbrew. A repairable packages screen will automatically launch. Select those packages and reinstall them, then reboot. The Botbrew repo will keep up with the CM repo, so as long as you are upgrading to the latest nightly, you will be fine simply reinstalling!

    Information

    Botbrew
    Botbrew is a package manager developed by the totally patient and kind inportb. I make the pitch for its capabilities, as well as my rationale for using it to distribute this software at the top of the 2nd post's ALL-NEW Q&A.
    To learn more about Botbrew, visit its homepage OR the thread here on XDA.

    v6 Supercharger
    The v6 supercharger is a popular script that changes the way your android device's memory management is handled. It was developed by zeppelinrox and lent to Botbrew for the Nook Color by special dispensation. Read more and thank zeppelinrox here.

    PDroid
    PDroid is a security app available for free on Google Play. It has just about a million applications, the foremost of which is allowing you to block permissions to apps (system and user) from having permissions you are uncomfortable giving. Apps that are given permission to access your contacts, for instance, can now be blocked from that privilege at your discretion.
    Pdroid also allows you to set static or random values for sensitive info should an app require them. So apps like Swype and others that require IMEI numbers or phone numbers can now be used like on regular devices. See svyat's original thread and thank him here.




    This is the only method to use these programs outside of smali editing your own apps! Usually this is an either/or, but not with these packages!
     Try the Auto-Patcher instead!

    ohsnap...plug time!

    Humility...
    XDA News Portal article on v6 package (frontpaged!)
    XDA News Portal article on Botbrew (x2)
    XDA News Portal article on the PDroid packages(...x3!)

    Gratitude...
    inportb, for holding my hand through every step of this process, and for Botbrew itself.
    Zeppelinrox for lending us the v6 supercharger script
    svyat for developing PDroid
    PoorCollegeGuy for his continuing support to the project.
    racks11479- y'all know racks. But he's got his hands in Botbrew, as well.
    pastime1971, my collaborator on the PDroid auto-patcher and the port of PDroid to ICS.


    bet you didn't know it took so many people to supercharge a nook, now did ya?
    View
    7
    M
    mateorod
    Brand New Q&A!

    Q: So why Botbrew and package management and not flashable zips?
    A: Ahhh...the million dollar question, I suppose. After all, almost all system changes have been done with flashable zips everywhere else, right?​
    Well, part of the experiment here is to get people comfortable with the idea of package management for their Android device. It is a method that people use with Linux (think Synaptic) and iPhones (Cydia) but is not yet in vogue with Android. But the advantage is not just theoretical, there is tangible and useful value that you will get to experience immediately.​
    For instance, installing system apps for ICS makes the most sense when done through a package manager. With the CM repo being compiled on a nightly basis, the system apps themselves are a moving target. What I mean by that is that the services.jar I mod today may break an install tomorrow. If I distribute the file in a flashable zip that people apply over their install every time they upgrade, well, once the Cyanogen repo updates and the services.jar no longer plays nice with the rest of the install, everyone who flashes that zip on a regular basis is in for a nasty surprise that morning.​
    With a package manager, the first person who realizes the services.jar is out of date (almost always me) just reports back to the thread. I quickly make a new file and update the Botbrew repo. Users don't have to monitor a thread, or personally make a new file, that only has to be done by one person.​
    Now, as is available in this thread, think if there are two different mods to that same services.jar. One user just wants the original mod, while the next would like them both. Neither user has the time or energy to personally decompile and mod the source code for every nightly, but flashing will only install one or the other services.jar. The package management method allows the software distributors to foresee this, and allow for it. That is why you see packages like mateorod-pdroid-v6, something that is just not available for any other nightly install.​
    One last benefit, and this one is a bit theoretical. As of right now, Botbrew only has a few people using it to supply software. But as awareness and the user base grows, more developers will see it as a means of reaching a wider audience. Right now, things like scripts and themes rely solely on word-of-mouth. Think of Botbrew as a potential store-front for all manner of software, everything that isn't a user app (because, of course, Google Play and others already do a fine job of that) could be found here, waiting for your perusal and discovery. That day isn't here yet, but by being willing to try a package manager, you are part of the growing user base that will attract devs. Getting users is the hard part, the devs will follow.​
    Q: So what is Botbrew, exactly, if it just distributes software?
    A: At its base, as inportb will tell you, Botbrew is simply a sophisticated installer, with the capacity to add software repos at will. When you install the repository-meteorod package, you are simply downloading my list of available software. You could add as many repos as you want from the Opkg configuration tab in the menu. However, Botbrew also uses unique maintainer scripts that allow software to be installed with a delicacy and precision not available elsewhere. Modding a live install is no everyday thing, and as Android devices get beefier and more powerful, some of the system-mods can be done live on the device, no pre-made software necessary. That will put the power of every script, theme and mod right in your hands, to apply, try and uninstall at will, without having to flash. There are enormous benefits to this.​

    Okay, the package management proselytizing is done...on to practical matters.
    Such as...

    Package date issues and build selection

    Q: ZOMG! I just installed a package and now I have BOOTLOOPS! What do I do?
    A: As they say, don't panic. Just reboot, and press the 'n' button as Cyanoboot loads. Use the menu to boot into recovery and reflash your ROM. The system app just went out-of-date and you were the lucky first user to discover it. Please come to the thread and report any such occurrence. I check each package on a nightly basis (because I love yooouououo) but I have missed a big repo change before and likely will again. I keep a close eye on the thread, and will update the Botbrew repo as soon as possible.​
    Q: What do you mean, a package goes out-of-date?
    A: As I said above, ICS is, as of right now, in an experimental and alpha state. What we flash every night isn't even an official release. I think in Cyanogen's perfect world, the amount of users on CM9 as a daily driver would be much less, but with it's popularity and rapidly educated user-base, that genie is out of the bottle. But when the source code used to create these system apps is changed enough, the apps made from the older code are no longer compatible with the newer builds. When that happens...ZOMG! and all that jazz.​
    Q: Even though you just explained how it's basically risk free I am cautious by nature. How do I lessen the chances of bootloops?
    A: Just flash in the morning. I check these packages almost every night on builds I set to be tested an hour or two before eyeballer and Samiam go live. By the time you wake up in the morning, there is a 95% chance the packages have already been vetted and replaced if necessary.​
    Q: How often do the packages go out-of-date?
    A: Maybe once every three weeks, although I recently had one go out of date after two days (ouch, right?). If you install the packages only over the latest nightly, you'll likely never notice.​
    Q: So how do I know if the build I am using is covered by the Botbrew repo?
    A: The absolute best way is to flash a nightly on the day it is released, go into Botbrew and install your packages then. That way you'll always be covered. Those packages will last as long as your nightly is installed. When you feel you are ready to update, just grab the latest nightly and do the same thing again.​
    Q: I am real partial to the build from (for example) March 3rd. What if I want to use Botbrew packages on a certain older nightly?
    A: At the bottom of this Q&A there is a list of downloadable packages and the build dates they go with. The links download the package which is installable from any browser or file manager, as long as Botbrew is installed.​

    Q: What do I need to do after updating to a new nightly?
    A: It's real easy. Just launch Botbrew. A screen should automatically appear that supplies you with the list of packages that have been damaged (read: overwritten) by the flash. Select those packages and press reinstall. Then reboot and you're done.​
    Q: Does it work on both eyeballer and Samiam303's builds?
    A: The answer is yes, with a catch. Eyeballer clobbers his builds every night, which means he is using no prebuilts from earlier builds and everything in his build is fresh made from that night's source. Samiam currently does not. That means that if you are using Samiam's builds, I recommend you read your build.prop in /system and find the ro.build.date. The date that is there is the last time Sam clobbered, and you will need to use a package that corresponds with that date. You can download the package and save it to your sdcard, and whenever you update, simply check the build date. If he clobbers, pick the corresponding package and go from there. The list of older packages are at the bottom of this post.​
    Q: OpenGL? Do I need different packages if I do/do not have that enabled?
    A: Nope. The packages work with or without OpenGL functionality.​
    Q: What about the (totally kick-butt) incremental updates that Team Win is distributing through GooManager?
    A: The diff-cm.zips actually break the mechanism Botbrew uses to determine if a flash has been performed (symlinks). For now, we just hope user education will carry us until we come up with a more permanent solution. You WILL have to repair the packages after a flash. Just go into Botbrew and select the germane packages and reboot.​

    Installation problems and errors

    Q: I just ran "su -c v6" and the terminal returned only a "$"! What gives?
    A: That is an unfortunate side-effect of the package installation (one I hope I recently fixed!). Launch Botbrew, go to the v6 package and press reinstall. The script will work in the terminal as before, no reboot necessary.​
    Q: I pressed Auto-remove, but it failed! What went wrong?
    A: It is an unfortunate bug in Opkg, the engine that powers Botbrew, where the autoremoval process sometimes fails. Just try it again until it works. I find that when it fails for me, the third try finishes the removal process completely.​
    Q: I just tried to install a mateorod package, but the install failed because of "check_data_file_clashes" and "file is already provided by * android-framework*"?
    A: Yep, that is a designed file conflict, added to the packages to protect the integrity of the backups and prevent users from accidentally losing functionality they really wanted. The error means you already have a mateorod-whatever package installed. Look for it in the installed packages screen, uninstall that package first, and then try to install your other mateorod package.​
    Q: Can I get (your favorite mod, script, or theme) supported by a package from Botbrew?
    A: We can certainly try. Botbrew is only limited to offering packages we can figure out how to make. Request it in the thread, and maybe we can find a way to package it up together.​

    Older Packages

    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


    5/07-5/10     (Ouch again, amirite?)

    PDroid only
    android-framework-pdroid_1.3.2-6
    PDroid+v6
    android-framework-pdroid-v6_1.3.2-6
    v6 only
    android-framework-services-v6_0.0.4-8


    5/11-5/14     (It is starting to feel personal)

    PDroid only
    android-framework-pdroid_1.3.2-7
    PDroid+v6
    android-framework-pdroid-v6_1.3.2-7
    v6 only
    android-framework-services-v6_0.0.4-9


    5/15-5/18     (It is

    PDroid only
    android-framework-pdroid_1.3.2-8
    PDroid+v6
    android-framework-pdroid-v6_1.3.2-8
    v6 only
    android-framework-services-v6_0.0.4-10

    5/19-5/26

    PDroid only
    android-framework-pdroid_1.3.2-9
    PDroid+v6
    android-framework-pdroid-v6_1.3.2-9
    v6 only
    android-framework-services-v6_0.0.4-12

    5/26-5/27

    PDroid only
    android-framework-pdroid_1.3.2-10
    PDroid+v6
    android-framework-pdroid-v6_1.3.2-10
    v6 only
    android-framework-services-v6_0.0.4-13

    5/27-5/30

    PDroid only
    android-framework-pdroid_1.3.2-11
    PDroid+v6
    android-framework-pdroid-v6_1.3.2-11
    v6 only
    android-framework-services-v6_0.0.4-14


    5/31-6/03

    PDroid only
    android-framework-pdroid_1.3.2-12
    PDroid+v6
    android-framework-pdroid-v6_1.3.2-12
    v6 only
    android-framework-services-v6_0.0.4-15


    6/03-6/07

    PDroid only
    android-framework-pdroid_1.3.2-13
    PDroid+v6
    android-framework-pdroid-v6_1.3.2-13
    v6 only
    android-framework-services-v6_0.0.4-16


    6/08-6/10

    PDroid only
    android-framework-pdroid_1.3.2-14
    PDroid+v6
    android-framework-pdroid-v6_1.3.2-14
    v6 only
    android-framework-services-v6_0.0.4-17


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

    *Note: There is no version 11 for the android-framework-services-v6 package.

    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!
    View
    4
    M
    mateorod
    My Nook has unfortunately met with some disaster. For right now, and possibly forever, I will not be able to, like I have these last three months, test these packages nightly to ensure they're up to date.

    I am, however, willing to continue maintaining the packages.

    What this means for you, if you're using any o the packages, is that the day will come when you update and install the package and it will result in bootloops. These packages were going out of date twice a week. Luckily CM9 started a code freeze right before my Nook died. So it had been steady for a week or two- hopefully this will continue.

    But if you install a package and get boot loops, don't worry. You don't need to wipe or restore a backup. Simply reflash your ROM, with no wiping, and come post in this thread.

    I will update the packages as soon as I see the request.

    If you have access to a Linux environment, you can always count on support for the Nook with the Auto-Patcher in my signature. It will automatically create a flashable zip that will enable PDroid, the V6, or both. It isn't the solution that package-management is, but it works.


    Soooo...
    I do want to thank those of you who have been supporting the project. It has been quite a learning experience for me. The XDA nook community is a great one; I consider myself very lucky to have owned this device, at this time. I especially would like to thank greyfoxmg1 for his continued interest and reportage towards and for this package thread.

    And of course, inportb, who allowed me enough of an inside view of Botbrew that I was able to end up hosting a repo. It was my enthusiasm for Botbrew rather than any other software that fuelled this project. I just wandered into his thread, noob as it gets. Inportb was patient and kind as I fumbled my way through this thing. He didn't have to spend his time teaching me the many things he did, and I am profoundly grateful to him for letting me tag along.

    This wasn't always the most popular thread. For quite some time, it would lose a star every other week due to a 1 star vote. But you guys, whomever you are, would invariably vote it back to respectability. That always made me feel like my time was appreciated- it did make a difference, to me at least.

    Well, it's getting a little dusty in here:p, so I am gonna wrap it up. I will probably replace the tablet-sized hole in my life shortly, so I will be around. And, I haven't ruled out getting another Nook yet, either. This is a pretty fine machine...

    as a bonus...some cowboy hats...followed by some victory:cowboy::cowboy::cowboy::victory::victory::victory::victory:

    regards
    View
    3
    M
    mateorod
    Quick V6 Configuration Guide

    This is an artifact, almost. But if you have questions about the configuration process for the v6, this is what I used.

    The V6 Supercharger menu asks users to confirm operations at several points, usually prompting you to press the Enter button, y for yes or n for no. Those are just confirmations of intent and those steps are skipped in the guide. They are common sense though, and should pose no problem.

    The script and the method of modding the services file is the product of the hard work of zepplinrox. I just followed the directions to save people the effort. Any risks are yours and yours alone, as always.


    1) Download and Launch Botbrew. Botbrew will bootstrap in some necessary packages

    2) Install package repository-mateorod[/] and press the refresh packages button at top right.

    3) Install package mateorod-v6

    4) Reboot. You will see an "Android is upgrading" pop up over your boot animation.

    5) Open a terminal and run the following:
    Code: 
    su -c v6
    6) The script will run. The program should automatically run the Driver Options. (If not, enter option 26 in the main script menu to continue following this guide).

    Choose 1-3 for scrolling speed. (do yourself a favor and select 1, for the fastest)

    7) Y for yes to integrate into init.rc

    8) Enter y if you do not want the V6 script animation.

    9) The script will enter its main menu which has 30 options. Select option 7.

    OpenGL Users: Some slightly less aggressive settings have been reported as resulting in increased stability with OpenGL.

    10) You will be prompted to Super clean and Reboot.
    This is no longer necessary. The supercharger settings take place immediately. But you can do it if it makes you feel better.

    11) Disable and reenable zRAM at 18% in settings/performance/memory management/zRAM in the device settings if you experience lag later. Since this requires reboots, I have changed this to as-needed. Update HacDan informs us our kernel does not have zRam compression. Verdict: Unneeded!

    12) Rerun V6 script and read the info beneath the menu list. It should indicate that
    -Launcher is Die-Hard, i.e. Supercharged
    -ADJ fixes NOT NEEDED
    -OOM Groupings Fixed
    -Current AND prior minfrees = 8, 14, 75, 90, 95, 125 mbs
    -Supercharger Service is installed, and
    -Supercharger Level = 100% Supercharged.

    If so, then you are correctly installed and running, and your values are sticking after reboot. That's it
    View
    3
    M
    mateorod
    farandel said:
    The script is amazing!! I just have a quick question.... when I do a full wipe to install a new rom, do I need to redo the entire process?? Thanks sooooo much in advance!!!

    Sent from my Incredible 2 using XDA
    Click to expand...
    Click to collapse

    Well, anything positive you have to say about the V6 Supercharger is due to the hard work of zeppelinrox, the dev who wrote the script. What we offer in this thread is to create the necessary files and easily install/replace them.

    You can/should thank zeppelinrox here.

    As for repairing the packages after flashing an update, I am glad you asked. I just updated the package in the Botbrew repo due to a change in the Cyanogen repo which caused the previous packages to break newer updates.

    Because this is happening nearly twice a week, I would like to suggest a tweak to the install method.

    After a new flash
    • Please select Clean Archives in the Botbrew menu (top right)
    • Refresh Packages
    • Swipe to the Repairable screen
    • Unless you flash on a daily basis, you should see an Upgrade button on the android-framework-whatever package. Please repair the other packages and then update the android-framework package and reboot.
    • Please, install packages only on the latest install. This will ensure that you only install packages to the proper ROM. If you really, really don't want to upgrade, their is a list of downloadable packages in the second post. But installing to the latest nightly is the safest practice. Then, whenever you choose to upgrade your ROM, you can just update your packages with the above procedure!

    This is to ensure that you don't accidentally reinstall an older package that will break your flash.

    If you do happen to install an older package that causes bootloops, there is no cause for concern. Just press the 'n' button and select boot to recovery. Then reflash your ROM and please report your experience here.

    Thanks!

    A Tip: Reinstall your packages so that the android-framework-whatever package gets repaired last. Installing that package is causing an automatic reboot, which you need anyway, but this way you won't have to relaunch Botbrew afterwards.
    View

New posts