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

Search This thread
By:
Advanced…
E

explorer-10

Senior Member
Dec 28, 2010
1,245
63
L.A.
sorry to sound like a noob, but what's the point of using this whole thing?
i still have a nook running cm7 and havent kept up with development for the NC for a while, so yeah..
 
NapalmDawn

NapalmDawn

Senior Member
Sep 3, 2010
1,002
169
Raleigh
Yes I was just trying to get the supercharger. Was looking to get a performance increase. The one that couldn't snag the repo was actually the one dizzy helped me recover from a bootloop last month where it would only pop to the menu you get after holding the nook N. Sadly, all the work was for naught. An app I was hoping would run doesn't so I snagged a TP as the gift I was intending the nook to be.
 
M

mateorod

Inactive Recognized Developer
Nov 16, 2011
1,981
3,503
New Orleans
www.gigmasters.com
explorer-10 said:
sorry to sound like a noob, but what's the point of using this whole thing?
i still have a nook running cm7 and havent kept up with development for the NC for a while, so yeah..
Click to expand...
Click to collapse
This thread offers an easy way to use some programs that normally require you to edit code. There are links to the original mod threads in the OP.

Some users feel that the V6 provides performance increases and reduced lag. It can definitely decrease the launcher redraws that can slow down switching between apps.

PDroid is an app that lets you block permissions that applications normally require to function, can spoof IMEI's, phone numbers, and other privacy related things.
NapalmDawn said:
Yes I was just trying to get the supercharger. Was looking to get a performance increase. The one that couldn't snag the repo was actually the one dizzy helped me recover from a bootloop last month where it would only pop to the menu you get after holding the nook N. Sadly, all the work was for naught. An app I was hoping would run doesn't so I snagged a TP as the gift I was intending the nook to be.
Click to expand...
Click to collapse

Okay. Glad you got what you needed.
 
NapalmDawn

NapalmDawn

Senior Member
Sep 3, 2010
1,002
169
Raleigh
Hi again Mateo. Unfortunately, I wasn't able to test it out. In installed the charger, went through all the prompts but when it was done and I rebooted, it got stuck. I just simply restored from a back up I had.
 
M

mateorod

Inactive Recognized Developer
Nov 16, 2011
1,981
3,503
New Orleans
www.gigmasters.com
NapalmDawn said:
Hi again Mateo. Unfortunately, I wasn't able to test it out. In installed the charger, went through all the prompts but when it was done and I rebooted, it got stuck. I just simply restored from a back up I had.
Click to expand...
Click to collapse

Well, like I said a while back, I am not able to test these packages either, due to a malfunctioning device.

But one thing that is important to note is that these packages are ROM specific, and usually pretty strict about build date. This is framework installation we're doing, and it is highly sensitive.

The packages listed in this thread are ONLY for straight CM9 builds- if you aren't using them on Eyeballer or Sam's or your own builds, they won't work.

Now if you used it on a recent nightly and it bootlooped, let me know the date and I will update the packages.

Actually, hold that thought. I haven't truly been able to get a handle on what rom(s?) you are running or what you are trying to do. Last I understood you had 7.2/PA, neither or which are supported in this thread.

Just use the Auto-Patcher...the link is in my sig. It can be used on Linux, OSX and Windows (using Cygwin) so there is really no need for me to keep running in circles trying to help without the information I would need.

I might just close the thread...I am no longer sure how many people are using these packages, and I haven't gotten any reports of outdated packages yet, which I find hard to believe.

This thread might just be frustration-bait, for me and any potential users...let me think on this.
 
I

inportb

Retired Recognized Developer
Dec 29, 2008
438
194
inportb.com
Hm... what about a big message right on top of the first post, directing users to the auto-patcher? It looks like the way to go! Of course, there would be people who skip right past that :D
 
  • Like
Reactions: mateorod
grayfoxmg1

grayfoxmg1

Senior Member
Aug 9, 2009
1,101
605
Paw Paw, Mi
Now, now importb, they'll figure that out on their own.

As for you 'explorer-10', CM7 is the official supported ROM for the Encore/NookColor, created by Cyanogenmod team. However, as Nook users we've always longed for a more Tablet oriented OS. *Dramatic Music* Enter CM9 and ALL the XDA members who have made it possible for us to have $300(about average price for a new tablet) toy for about have the cost (original Nook Colors are now about $150).

As for the point of this thread, it's to help make installing the V6-Supercharger onto Nooks easier for other people, I also think this is the ONLY way to get PDroid to work on our devices. V6-supercharger is a script that when ran, edits memory values so that whatever Android device you are using is both faster, and more responsive. V6 also has lots of little gadgets built in that can; decreas lag, prevent certain processes from closing, fix FC's, and also realign your packages so that your device is slightly more energy efficient. Basically it's a really cool mod made by XDA-member zepplinrox, that both does lots of things, and is pretty easy to do. Mateorod, inportb, and all of us that contribute to this thread, we just make it easier for you.

So while using V6 is as easy as changing the oil in your car, using botbrew and Mate's repositories is like taking it to the shop and getting it done for you.
 
  • Like
Reactions: inportb
I

inportb

Retired Recognized Developer
Dec 29, 2008
438
194
inportb.com
@explorer-10: those of us who are involved in the making of things hope to share something useful with the community. Perhaps this method is not for you; but you'd see that it has been useful to some people who are looking to squeeze a bit more performance out of these Nooks.

I'm still working on BotBrew, of course. basil has come a long way and might become the default version soon. If you use Android 4.1 (probably not, if you're supercharging), you'd find that it does not work; but 4.1 support is in the pipeline. Hopefully, we'll have a 4.1-friendly supercharger too. Just looking ahead a little :)
 
Last edited:
  • Like
Reactions: mateorod
M

mateorod

Inactive Recognized Developer
Nov 16, 2011
1,981
3,503
New Orleans
www.gigmasters.com
inportb said:
@explorer-10: those of us who are involved in the making of things hope to share something useful with the community. Perhaps this method is not for you; but you'd see that it has been useful to some people who are looking to squeeze a bit more performance out of these Nooks.

I'm still working on BotBrew, of course. basil has come a long way and might become the default version soon. If you use Android 4.1 (probably not, if you're supercharging), you'd find that it does not work; but 4.1 support is in the pipeline. Hopefully, we'll have a 4.1-friendly supercharger too. Just looking ahead a little :)
Click to expand...
Click to collapse

Well, my hesitation about ending the thread mostly was due to wanting to hear from you, as you had so much to do with it existing.

I think maybe I will split the difference. I have no problem maintaining support for any of our current users, but I do think that anyone tripping across the thread for the first time is more likely to encounter trouble than not.

I will drop a suggestion to try the Auto-Patcher in the OP but will continue to support anyone who asks for updates.

I, personally, am still won over by package management as a preferable way to install these things. To me, that includes things like the update.zip outputted by the Auto-Patcher. My personal setup here runs the Auto-Patcher but outputs a debian package instead of a flashable zip - this is what I do when an update is needed.

But one thing that is needed for package management to succeed is an able maintainer, something I no longer have the hardware to be.

I am personally pretty excited about Botbrew for JB. I have a grouper coming (maybe? Google, hello? I don't use a cell phone, so this month and a half w/o any type of device to mess with has dragged...) and would be willing to test just about anything you want, should you need it. Let me know.

My first project when you get it up and running is the long-lusted after on-board patching. I believe that Grouper has the power to make that manageable, and is pretty much the reason I chose it.

That's something I feel will only be possible through Botbrew, as I have said before, my enthusiasm for your project is what fueled this thread and led to many others.
 
  • Like
Reactions: inportb
C

cmonty14

Senior Member
Sep 30, 2011
400
24
Packages "mateorod-*" unavailable

Hi!
I have successfully installed BotBrew on my devices SGS GT-I9100 running CM9 nightly.
The installation of repository "repository-mateorod" finished without problems, and the repository is now listed in tab "Installed".

I've clicked on refresh button in bottom left corner.

However, I can't find any of the "mateorod-*" packages to install PDroid or SuperCharger V6.

Can you please help here?

THX
 
M

mateorod

Inactive Recognized Developer
Nov 16, 2011
1,981
3,503
New Orleans
www.gigmasters.com
c.monty said:
Hi!
I have successfully installed BotBrew on my devices SGS GT-I9100 running CM9 nightly.
The installation of repository "repository-mateorod" finished without problems, and the repository is now listed in tab "Installed".

I've clicked on refresh button in bottom left corner.

However, I can't find any of the "mateorod-*" packages to install PDroid or SuperCharger V6.

Can you please help here?

THX
Click to expand...
Click to collapse

Well, I edited the post, and it looks like I edited out the very large warning that says these packages are for the Nook Color only.

I have added it back to the OP.

But it does say, in pretty large letters, if you are new to use the Auto-Patcher instead. Follow the link in my sig, it can make a zip for most roms...
 
NapalmDawn

NapalmDawn

Senior Member
Sep 3, 2010
1,002
169
Raleigh
HI Mateor. The one that boot looped on me *is* a CM nightly, Not sure if it's the most recent one though. I"ll flash whatever is the most recent and try again. The crazy one that's not reporting as a Nook is the one that doesn't find the repo. I"ll get back to you ASAP on the CM nightly issue.
 
NapalmDawn

NapalmDawn

Senior Member
Sep 3, 2010
1,002
169
Raleigh
Cm 7/17 nightly. V6 installed, ran and rebooted. Working fine now. With v6, is it safe to OC? I used to run at 1.1. Is it okay to push back to that?
 
M

mateorod

Inactive Recognized Developer
Nov 16, 2011
1,981
3,503
New Orleans
www.gigmasters.com
Glad that the directions still work when followed. The V6 doesn't interact with your hardware, it simply changes your memory management priorities. So, any clock changes you like to apply should work just as they always have, no less safe than before.
 
  • Like
Reactions: gsutton
G

generalpelmen

Member
Dec 27, 2010
36
1
Hey thanks for the script. I have a little problem, when I install the v6 script and go to restart like said in steps I get stuck in boot screen. Im running Krylon AOKP. I have re-flashed couple of times and same thing. When I restart without v6 works fine.Much appreciated.
 
grayfoxmg1

grayfoxmg1

Senior Member
Aug 9, 2009
1,101
605
Paw Paw, Mi
What do you mean only CM10 is supported? Granted I've taken to using your autopatcher script within Cygwin do configure my rom for the use of a V6 script. It's just easier to update the rom and the update.zip at one time within CWM.
 
M

mateorod

Inactive Recognized Developer
Nov 16, 2011
1,981
3,503
New Orleans
www.gigmasters.com
grayfoxmg1 said:
What do you mean only CM10 is supported? Granted I've taken to using your autopatcher script within Cygwin do configure my rom for the use of a V6 script. It's just easier to update the rom and the update.zip at one time within CWM.
Click to expand...
Click to collapse

Ha. Yep, you're right. I did mean Cyanogen, specifically ICS. Shows I have had my mind totally on JB with the Auto-Patcher.

Plus, have inundated with pm requests for Botbrew support lately, sometimes by the same people over and over.

I actually think Botbrew still makes a ton of sense for operations like this. Instead of a bunch of people making their own update zips, only one maintainer per device is needed. I was the nook maintainer, but when my WiFi pooped out, I could no longer do the job.

But the larger point stands, I guess, that the Auto-Patcher is the way to go right now.
 
tzpm

tzpm

Senior Member
Oct 5, 2012
137
20
收件人： [Packages][7-16] ICS V6 Supercharger- now w/ PDroid

can I use those to diff and patch

Sent from my HTC X515d using xda premium
 
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