yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] inportb:
Just to clarify -- we've decided to host all the relevant packages in mateorod's repository, so that y'all could have packages to install as soon as he's got something new, without waiting for the main repository to update. Consequently, the packages have been dropped from the main repository to avoid confusion. From now on, you must install repository-mateorod and refresh the package list first.

Thanks for understanding!
[Nook Color Android Development] CCivale:
Excellent. Thanks Mateorod and Inportb. That worked perfectly. Awesome job.
[Nook Color Android Development] mateorod:
Thanks for sticking with it!

To anyone interested, I have made some patches for PDroid which should be able to bring it to any CM9 rom, at least, and for any device. The patches have been confirmed to work for the Nook and the LG-P990, but obviously we would like to test it further before putting it out in the wide world.

Does anyone have another device running CM9 they would like PDroid for? Are you willing to flash some pre-alpha test patches?

If you would like to try this, please post a zip of your

Build.prop

Services.jar

Core.jar

Framework.jar

The build.prop is in /system and the other files are in /system/framework/.
[Nook Color Android Development] numus:
Updated botbrew and attempted to install v6 today.. getting a lot of read-only file system errors.. I checked superuser and botbrew is allowed in there...

Update: I fixed this by mounting filesystem writable in ES Filemanager...

After reboot i went back to terminal and typed su -c v6 and nothing.. just gives me a new terminal line but doesnt run v6...
[Nook Color Android Development] inportb:
Please try reinstalling v6-supercharger. Just select the package and hit reinstall.
[Nook Color Android Development] numus:
Had to decline to use the previous saved from the sdcard... Seems to be working now that i actually got to select the options instead of using the previous stuff...
[Nook Color Android Development] CCivale:
Not a problem. It's worth it to make my device more efficient. Thanks again for putting in the time to figure it out.
[Nook Color Android Development] gumnaam.sur:
Same here.

- Wiped Dalvic Cache + cache

- Flashed new nightly (4/24) + new gapps (4/20 I think)

- Reboot

- Updated 3 packages from botbrew (framework, v6, pdroid-v6)

- reinstalled v6 as per first thread

- ran "su -c v6" selected re-supercharge

- reboot

- Confirmed pdroid worked

- ran 'su -c v6', nothing happened

- reinstalled v6 from botbrew

- ran 'su -c v6' , got a lot of readonly filesystem errors

- mounted system r/w from EZ File explorer

- ran 'su -c v6', and this time it worked, and DID NOT "re-supercharge", so basically re-ran the whole stuff again

- reboot, and now both pdroid + v6 working correctly.
[Nook Color Android Development] mateorod:
I bet that is a glitch from upgrading the v6 supercharger script. I am betting you both had update 8 on your sdcards, which is now quite a few versions ago.

I think that our little corner of XDA is unique in that such an old script is the one in most use. I will put a note in the OP with your workarounds. Thanks.
[Nook Color Android Development] grayfoxmg1:
Reporting that botbrew/V6 set samiam303's latest image into a bootloop for me, fixed it by dropping down to an older one.
[Nook Color Android Development] mateorod:
Well, I can confirm that is true. Thanks for letting us know. There are no boot loops for eyeballer's or my builds, though.

I see that samiam posted his build a little later than usual last night. I went to the repo and scanned it for that period of time, and I don't see anything that would break the packages, but it must be there. I am currently building as I post this. I will test the packages on that, and if they break, I will have our packages updated before tonight's builds go up.

Thanks for the heads up.
[Nook Color Android Development] grayfoxmg1:
No problem, thanks for the fast response :D

Sent from Tapatalk 2 on my Nook Color running ICS
[Nook Color Android Development] mateorod:
This is interesting. I just built a straight source ROM and a PDroid-patched one, anticipating updating the Botbrew repo when the new nightlies go up today. But when I checked the regular CM9 build with the android-framework-pdroid-v6 package it still works fine.

I wonder why Samiam's build gave us bootloops with that package?

I am going to check Samiam's build when he posts tonight. I may just update my Botbrew repo for GP, it doesn't hurt any. I'll test eyeballer's too, just for fun.

As of right now, the packages work for eyeballer's 4/17 to current, as well as all of my build from the same period, which are straight source. Greyfox, what was the build date of Sam's rom that worked? Would you mind letting us know?

I'll let you know about tomorrow's Samiam nightly (4/25) when he posts.
[Nook Color Android Development] grayfoxmg1:
it was 4/19/12 that worked for me, but I did update to his newest(not the one that is being posted now) and supercharged it the old way with the service.jar file I had lying around.
[Nook Color Android Development] mateorod:
Okay, now that is weird. Are you talking about the one I posted in March, I think you made a flashable zip out of it?

I would guess you are one of the few people using both Botbrew and Sam's builds. I am going to not only test his tonight, but some of his older ones as well.

If you are using the services.jar I think you are, then something is really old in Sam's builds.

Ah ha! I was about to ask you to check the build.prop, but I realised I have Sam's build on my Nook right now. I just checked the build date. March 31st. The build date doesn't change until he makes a clobber. He hasn't clobbered in almost a month.

That means his build is reusing all old prebuilts from March. He hasn't made any fresh pieces in a while. I think that means he still has the older kernel (two updates ago?)from March as well.

Well, in any case, that most likely means that the current package won't work for those people using Sam's builds until he clobbers, which is going to be hard to predict by us.

This is what I can do though.

For anyone using Samiam's builds, here is a post with links to the opks you'll need for the v6 and Pdroid both. You can install them directly from the browser, or download them and they will install from any file manager. Just select the package , and Botbrew will pop up as the compatible application. If you have the v6 installed, you can reinstall it and get the script whenever you want.

If this is your FIRST time supercharging with Botbrew, you will need to install the v6 package, them immediately install the above android-services-framework-v6 package and THEN reboot.

I know it's a bit of a pain. inportb has written a real cool program that will take care of a LOT of these type of problems, the delay is I have to figure out the scripting to integrate it into these packages, and I have a lot to learn :p. I hope to have a major update to all the packages in this thread in a couple days.

I change the date on the OP when that update goes out so you all can see it, as it will involve a slightly different install procedure. But it will easier and safer, so I think it is worth it.

Thanks for your info greyfox. If you stick with Sam's builds, will you please let me know whenever he clobbers? You'll know because you'll have to use the newest package.
[Nook Color Android Development] grayfoxmg1:
Here is the Zip I made for anyone else using Sam's builds.To supercharge you'll need this, the script that you get from zepplin's page, and script manager to make it easier.

Directions:

-Flash your build

-Flash the Zip

-Run Script Manager

-Locate your supercharge script

-Run said script with superuser permission

-continue to supercharge as normal

Edit: Mater where can I find your builds?
[Nook Color Android Development] mateorod:
Oh, I just build so I can make mods on demand and flash when I need to. I don't put them out or anything. People use pieces of them when they use Botbrew, that's about it. They are identical to eyeballers most nights, assuming he doesn't add any cherry picks, which he usually doesn't. There wouldn't be any point to offering them publicly, they don't offer anything people don't already have access to.
[Nook Color Android Development] spamolamo:
Can't find repository-mateorod in botbrew, even after refreshing. any ideas?
[Nook Color Android Development] mateorod:
Hmm..well, inportb has been very hard at work putting together Botbrew +1, which has all sorts of interesting things happening. He is the one who maintains the master repository, and maybe you just checked when he was reorganizing.

I just checked my package list, and it's there now. I always look for it in the 'm's and THEN I remember it is repository-mateorod

If you continue to have problems, I can have you add the repo manually, or provide download links to the packages. Let me know, and thanks!

Update: See below...
[Nook Color Android Development] inportb:
If you refresh and get "update failed", here's why: our repo server is down (oh, no!). Don't worry; I'm currently working with our host to bring it up again, which should restore service. Sorry about that. Hang in there, folks!

(excellent timing, right? it just had to happen at ~0400UTC on a Sunday)

/edit: ... and fixed! (at 1400UTC)
[Nook Color Android Development] mateorod:
Well, the repo went out-of-date tonight. I have updated the files already, though, so normally I would let it pass without comment as you wouldn't even notice anything had changed. Except I had set the repo up for a big change in protocol set to be rolled out sometime tomorrow.

If you are running a nightly 5/06 or later, the below directions are for you. Older nightlies can find the needed packages here, which will still use the original directions.

So...if you're an late-night flasher, there are some changes to how these Botbrew packages are installed. Sometime early tomorrow I have a fairly big restructuring of the thread to roll out, but until then...here is the short version.

As the system-mod offerings continue to grow, there is an increasing chance of backup mismanagement through installing different packages one on top of the other. To avoid such problems, we have added meta-packages containing a conflict file.

From now on, all system-mod packages from this thread are to be installed like this:

New Directions

Install the package repository-mateorod and press the refresh button at top right.

Install a mateorod-package

The new way to install the v6, pdroid, or pdroid-v6 packages is to look for a new, correspnding mateorod-<x> package. So if you want pdroid and the v6, you would install the mateorod-pdroid-v6 package.

Reboot

That's it. If you choose a package that includes the v6, the script will automatically be included in the mateorod package install. You can install the package and go straight to the terminal and enter su -c v6 to configure.

If you try and attempt to install a mateorod package with one already installed, you will get an error message regarding check_data_file_clashes. Look on your installed package list and auto-remove any mateorod- package and try again.

Note: the auto-remove function can sometimes report a failure upon first try. It should work if you try it again.

Thanks for sticking with us as we try to keep the packages working while better protecting your system.

Also For anyone using eyeballer's incremental update feature through goo.manager, the packages will not show up as needing repair after flashing the diff.update.*.zips. Simply select the packages and press reinstall. Thanks!
[Nook Color Android Development] mateorod:
Another update to the repo. Must have been fairly substantial, it broke the patches I use to build PDroid, the auto-patcher, everything.

All dross, though. The Botbrew repo is now current.

* If you are installing on a current nightly (5/07 and up) use Botbrew as in the above post. Please be mindful of the new install protocol if you haven't updated in a while!

* If you are using an older nightly, install Botbrew and install the package from this post that matches your build date. The package can be installed directly from your browser or file manager.

* If you are using Samiam303's builds, check your build date in the build.prop in /system before choosing a package! The build date will determine which package you need.

* If you use the incremental updates, you will still need to repair the Botbrew packages every time you flash. Just select your installed package and press reinstall.

That should cover it...

If you are using the package manager and have a mod you would like to see added, please go ahead and request it.

Thanks!
[Nook Color Android Development] pkchainsaw:
Materoid packages?

Ok, I'm new at this, so be nice. I've installed the repository-materoid in brewbot, but there are no materoid packages showing up on the list. What am I doing wrong?
[Nook Color Android Development] inportb:
Did you try refreshing after installing the repository-mateorod package?
[Nook Color Android Development] pkchainsaw:
thanks

Thanks. That worked. I didn't know.
[Nook Color Android Development] mateorod:
I saw this and hoped that it would.

It's not your fault that you didn't know, to be honest. This thread has undergone about a dozen changes in purpose since I started it and reflects its Frankenstein origins.

I actually spent forever redoing it the other day, and then my cat (ain't it always the cats?) unplugged the computer and ppffoooooooofff!

I haven't had the heart to redo it since then, but seeing your post is making me feel guilty. I will try and get it up soon.

Thanks for your patience and for trying the packages.
[Nook Color Android Development] mateorod:
Okay, the long-promised and long overdue rewrite of the first three posts is finally up.

The first post is a straight-forward (I hope) write-up on the new install procedure.

The second post starts with a long Q&A (seemed like a good idea when I wrote it the first time. Re-writing it after my cat uplugged the computer right before I submitted it was like pulling teeth) as well as a list of older packages available for download for those of you who callously refuse to update your ROMs.

The configuration guide for the v6 is now relegated to the kitty-box of history that is the third post on this thread.

As for the repo, the CM team is really going at it, the repo went out of date again last night. I can't hardly keep up.

So there is a new link in the second post covering the last two days, and since I was at it, I upgraded the v6 script to U9RC8.2, just because.

Thanks for sticking with us, while we plan to keep offering new packages, this should be the last change in procedure. Which, for the record, is:

Install Botbrew

Install repository-mateorod

Refresh packages

Choose your package

mateorod-v6

mateorod-pdroid

mateorod-pdroid-v6

Install mateorod-whatever

Reboot

Configure the v6 in a terminal with "su -c v6" or PDroid in the app itself.

Thanks so much for trying the packages!
[Nook Color Android Development] phroenix:
Hi,

Thanks for agreeing to port this, I already installed V6 for ICS with modified services.jar and don't have the time to reflash orignial ROM so just extracted from the original zip.

The rom was built 2nd May in case thats what you need from build prop, had to change ext to txt, said invalid file when i tried to upload

ROM CM9 4.0.4 on X10 Mini Pro

Thanks
[Nook Color Android Development] mateorod:
Ha! I had actually tried to get a jump on this for you last night, but struggled since I didn't realize this most recent build was put out on May 2nd. There was the biggest change to the system apps since january or so between May 2 and now, and I had to make new patches for the current builds that have nightly releases. Anyway, not important, your packages are put together and in my repo.

Directions

Launch Botbrew

Install repository-mateorod

Refresh Packages

Install either

android-framework-pdroid-cm9

For just Pdroid

OR

android-framework-pdroid-v6-cm9

For Pdroid and to enable the V6 supercharger

REBOOT!

Install Pdroid and configure

If necessary, download the V6 script from zeppelinrox and configure in terminal as usual.

The packages are uploading to the repo now, if you don't see them, wait an hour before reporting back any problems. My wireless has been straight garbage since I upgraded to 12.04. It's killing me.

Anyway, please let me know how it goes. If it all works like it should (and does for about 10 devices already) let me know, and I can get a thread up in your forums so people can know about it and have a place to go for support.

As I said, there was a big CM repo change recently, so whenever y'all get some newer builds, these packages will probably break. No worries. Just reflash the rom and let me know (attaching the same files you did for this package). I'll update the packages ASAP and you'll be back in business. They are just modded system apps, so there isn't really much risk at all to your system.

Thanks for contacting me and trying this out! Let me know how it goes.

Edit: inportb informs me that there is some trouble bootstrapping, huh? Well, you're gonna get a lucky first look at basil or whatever. With the move to dpkg, I will migrate these over, so give me a little time and we'll take it from there.
[Nook Color Android Development] mateorod:
Okay, well the coders over at Cyanogen HQ have been busy little buggers [geddit? BUGgers? ( and get it? GEDDIT?)...oh yeah, that's how fun I am] and have forced me to upgrade the repo again.

It's a pain for me, but shouldn't impact you too much unless you wish to install a package on an older nightly.

If you would like PDroid or the V6 on a nightly from before tonight's 5-15 build date, then head over to the second post and you can download a package that covers your ROM.
[Nook Color Android Development] mateorod:
Okay for those of you who live on the bleeding edge...

Botbrew +1

I don't know if y'all have seen, but the new Botbrew+1 is out in the wild for debugging purposes, and is going to be available on Play in very short order.

This is going to be a separate release from the Botbrew you currently use, and is going on Play for easy and apparent updating purposes only!

Botbrew+1 is powered by a completely new engine, as the switch from opkg to dpkg is finally here!

I intend to have a separate repo set-up for the debian packages sometime in the next 24 hours. I will post here when it is ready. The current repo will remain available for quite a while, as the switch gets hammered into shape. If you install +1, you won't see my packages until I get the repo up, which should be pretty soon.

This means that if you update Botbrew, be prepared for things to be a little different. From the user-side, it should be very much the same set-up, but this is the new roll-out of all sorts of features and processi (is that a word? who knows.) so the possibility of bugs will remain.

Like I said, I will keep the repo you are currently using up to date, so if you want continue using the Botbrew you already have installed, that is fine and will be supported.

Thanks, I will let you know when the debian repo is ready, for those of you early adopters!
[Nook Color Android Development] inportb:
As mateorod said, we're experimenting with the next release of BotBrew. I decided to put up the source code and regularly upload new binaries to the Play Store so we could all have a chance to play around with it, find bugs, and see what's lacking. Even though the idea is to eventually migrate all the current packages to the new system, you may have both versions installed in parallel, without conflict. Just avoid installing the same package in both versions, because they would not keep you from doing so, and bad things might happen! If we're expecting some major breakage/conflict, I'll put that in the app description.

That said, mateorod has been working hard to maintain packages for both Opkg and Dpkg. My job is a lot easier, because I could just ask you to use stuff from Debian until I'm ready to migrate the native-code software over.

Thanks for listening!
[Nook Color Android Development] grayfoxmg1:
Hey materoid I'm having an issue here.

So I just updated to Eyeballer's 5/19 build from his 5/08 build. When I went to install V6 through botbrew it wouldn't replace the service.jar. It told me that I wasn't running CM9. I've added nothing else to my Nook.

One thing I noticed is that his build now says 'unofficial' in the title, could whatever necessitates that tag be causing my issue?

EDIT: anyway for you to send me that latest service.jar while you work on this?
[Nook Color Android Development] mateorod:
Hmm...okay. That means that there was a change in the build.prop that slipped by us. I only have the CM9 check in the V6 package, so I had missed it as I check the combo package for expediency reasons.

I will check it out and update the package tonight. I am in the middle of trying to finish up the Cyanoboot stuff, but I will fix it and let you know when it's done.

Thanks for the heads up!
[Nook Color Android Development] grayfoxmg1:
Thanks for the fast response, I'll just hang loose and wait. Incedentally, since Sam doesn't clobber all the time, Where else is everyone getting their builds? Just Eyeballer, or is there another source that I am unaware of?
[Nook Color Android Development] mateorod:
Since I saw you were waiting, I pushed through a hotfix. It merely consists of removing the CM9 check, so I will probably update it again in the next day or two once I have time to look over the changes. But it should install no problem, now.

I have not had a chance to check the package though. Usually I would assume it is fine, but the repo has been in a state of near-constant flux lately :o

Let me know how it goes, like I said, it was fine 24 hours ago, so you should be okay.

Edit: Nevermind. I am about to test. My conscience got to me. Give me maybe 15-20 at worst.
[Nook Color Android Development] grayfoxmg1:
Thanks, but you didn't have to. I didn't mean to give you more work so sorry about that. But it still awesome that you are going through this much trouble for just one person. Just shows how great a person you are.
[Nook Color Android Development] mateorod:
Well, I am glad I tested. Loops. Give me like 15 to 20 mins more and wait until version 12.

I wish I knew what they are doing different to make these ROMs so delicate lately. I guess I could pour throught the commits, but that sounds like a lot of work...:p

Thanks for the kind words, I am just glad to hear that people are finding it useful.
[Nook Color Android Development] grayfoxmg1:
When will version 12 be done? or perhaps you can tell me if your debian build works on this rom okay.
[Nook Color Android Development] mateorod:
Version 12 is loaded into the repo. My dropbox folder is still syncing, but it should be available momentarily.

The debian repo should be ready soon, we (ha! inportb, really) are just hammering out some errors retrieving the package information.

Hopefully the go ahead to try it will be any minute!

And thanks for the heads up, I rely on you guys to let me know if I need to address things and you've been very consistent in helping keep the repo up to date!
[Nook Color Android Development] grayfoxmg1:
Always happy to help, I'll give it like a half hour before giving it a go. Hopefully the new eyeballer build being released sometime in the next few hours won't screw it up. If you ever need someone to help test anything feel free to ask.

I'm looking forward to Botbrew +1 to see if the debian packages fit in seemlessly. Than it's only a mater of time until we can all start porting linux programs to our nooks with simple point and click commands.
[Nook Color Android Development] mateorod:
It's ready by now. Just look for the version number 12 and you're set! Botbrew+1 is looking great, I think it is ease of use bugs that are being hammered out now. And the Debian library is indeed at our fingertips. Exciting stuff.
[Nook Color Android Development] grayfoxmg1:
Just put on Eyeballer's 5/20 nightly and Version 12 still works. Just thought I'd let you know.