yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] windraver:
Just got my nookcolor yesterday and rooted it using the manualnooter for 1.4.1.

So I wanted to try this out and so I tried downloading botbrew but it won't run. It just stops after the following:

========

fetching libbusybox.so.1.19.4

downloaded bootstrap packages.

...something went wrong :(

Retry?

=========

Did I not root right? Or am I doing something else wrong. The last thing I rooted was a Moto Droid so this is new to me.
[Nook Color Android Development] inportb:
This is a bug report against BotBrew "anise". Thanks for letting us know about the problem.

If you rooted correctly, then it would seem that BotBrew does not work with the rooted "stock" ROM. It does work with CyanogenMod 7+, though, in case you're planning to install it. We could work some bug fixes into the next release of BotBrew, if you're interested in helping us with alpha-testing. Let's move the discussion to the BotBrew thread, to keep this thread on topic.

iirc, these particular packages are meant for CyanogenMod only. Even with a working BotBrew, you should probably not install them on a "nootered" device (though you could install CyanogenMod if you want). Please correct me if I'm wrong.
[Nook Color Android Development] mateorod:
Inportb is correct, of course. The packages for Nook Color are, at this point, only for Cyanogen 9. I do have a PDroid package for MiraGe 7.2 in testing, but we'll leave that for another day.

You can still use the V6 on a nootered stock, I believe. If you have a terminal, then you have all the requirements. Find a copy of the script at the link on my first post, no Botbrew packages necessary.
[Nook Color Android Development] grayfoxmg1:
He's right, V6 will work on a nootered Nook, when I had it on my girlfriends nook she was using a early 7 series script. That I know works, however I can't see why 8.1 or even 8.2 wouldn't work. I've since put her on eyeballer's 5/05 build because it was really stable.
[Nook Color Android Development] mateorod:
Okay, some news.

If you would like to wait until Botbrew Basil is stable, the original Botbrew app, and the mateorod repo will continue to be supported for the foreseeable future! This is an opportunity to try something new, not a requirement!

The new debian repo for this thread, repository-mateorod for Botbrew Basil (a.k.a Botbrew+1) is ready for testing. Note the keyword there,

testing

. In order to test the new debian packages you will need to install a separate app, Botbrew Basil (Experimental) from Google Play. It can be installed alongside the original Botbrew app, if you just want to check it out.

The apk build that inportb has put on the market is marked as experimental, and I am sure he has labeled it as such for a reason.

Having said that, I used it to test some packages last night and today and it is working great! If you're up for some adventure, go check it out!

Botbrew Basil has much more to offer than just these packages enabling Pdroid and the V6, so check out the official thread here at the Nook Forums. I consider myself lucky to have this kind of development happening in my device's forums, it is why I got involved with making packages in the first place.

The Debian library is opening itself up to our Android devices, and it started here. Pretty damn cool.

Directions

The procedure is almost the same as with Botbrew proper, which used opks instead of the new debian packages. I recommend you make use of the

search button

, you will notice a huge uptick in the amount of available packages, and getting through all those libraries through swiping alone can be an undertaking.

Install Botbrew Basil

Install the repository-mateorod (remember the search button!) and refresh packages

Choose the mateorod package you would prefer (the available packages are the same as in the first post)

Reboot and configure!

As of now, there is no option to repair packages after flash. The package will read as if it is installed, but you will need to reinstall all packages after flashing a new ROM.

One last note

I have added a package that enables PDroid for the MiRaGe 7.2 builds, android-framework-pdroid-mirage-cm7.2. These packages were made possible by the contribution of gunaam.sur so thank him when you see him if you try the package! Now, one note of caution. These packages were made for the 5/9 Mirage build. I know mrg666 has been updating often as he tests his new kernel, so there may be a newer build by now. However, with the current stability of the CM7.2 repo, I have every expectation that the packages will be fine for a good long while. Let me know!
[Nook Color Android Development] grayfoxmg1:
Imagine reading that on the android-wiki a few months from now;

"........this program makes use of Debian runscripts, which as you know were first utilized on rooted Barnes & Noble Nook Colors, because of this we can now run packages such as.........."

-Excerpt from a wiki page in the future!
[Nook Color Android Development] inportb:
Ah, thanks for the reminder. I've filed a couple of issues against BotBrew so I don't forget about them:

https://github.com/jyio/botbrew-gui/issues/12

https://github.com/jyio/botbrew-gui/issues/13
[Nook Color Android Development] grayfoxmg1:
So I just did a clean install of Eyeballer's 5/22 rom last night. And I then installed V6 through botbrew basil/+1.

Works perfectly, however I did notice that when you install the V6 package from your repository that it doesn't automatically install the framework. Not a big deal, but the debian repository is huge so that was a lot of scrolling. Maybe work on a script that grabs one when you install the other?

Also am I the only one that hasn't been able to use option 10 on these past few rom updates? It gives me a weird error and closes terminal, I than relaunch the script and install option 5. Not a big deal but was curious if it was just me.
[Nook Color Android Development] inportb:
Now here's a problem in need of a solution. The search function mitigates it somewhat, but we still have an information overload.
[Nook Color Android Development] grayfoxmg1:
perhaps a grouping system? Have a repository of everything Gnome, or everything Python that we can install inorder to have access to those components. So if someone had a Python runscript they were working on, they could have all they need and not things showing up for items they have no use of.
[Nook Color Android Development] inportb:
We have sections and tags for that. If there's an elegant/efficient way to extract them out of all packages, let's do it :)
[Nook Color Android Development] grayfoxmg1:
I don't know how:( Sorry. I'm not a 'poweruser' I know more than most, but on this website, I'm probably one of the dumber people here.

---------- Post added at 11:57 AM ---------- Previous post was at 11:52 AM ----------

I don't know if this is any easier, but maybe you (@inportb) can add a user favorited repository function. Simply if a user favorites/stars/checks one of their installed repositories, than those files appear first in the package list followed by the others as usual.
[Nook Color Android Development] mateorod:
Hey greyfox.

I am glad inportb was able to chime in. I have thought a bunch about possible ways to separate the types of packages as well, although this was more of a long-term curiousity than anything else. It was just clear to me that the packages I offer are for a far different user base than the majority of the Debian tools. I sometimes daydreamed about a modder/developer separation, stuff like that. I like your suggestion a lot. On thing I have learned about inportb, he's usually been thinking about these issues far longer than I have, and may even have an idea of what he's thinking for the future.

Are you installing the mateorod-v6 package? That should pull in all your needed dependencies. If not, look at the revised first post. You've been a long-time user, and I do know it was a dirty trick changing the install procedure on you. It was for a good reason.

And lastly, are you talking about option 10 in the v6 supercharger? I moved up to U9RC8.2 about two weeks ago, and I find it buggier than the 8.1. If you prefer, I can go back to 8.1. I bet the update is to blame for the changes you've encountered.

Thanks man!
[Nook Color Android Development] grayfoxmg1:
Your repository on botbrew basil isn't called mateorod-v6 for me. It's just called V6-supercharger. Just to tell you it is working, but the automatic option does not. Doesn't really matter because multitasking is only off by a few numbers. I was using 8.2 script before you had switched because I kept a copy on my SD.

I also thought the script might have been it, so I downloaded 8.1 from zepplinrox's thread and it still didn't help. The procedure is fine, certainly no harder than replacing the service.jar manually like we used to (or with my old .zip file).

If it is only me reporting an issue than don't worry to much, it means I have a conflicting program(probably Adfree).

However if anyone else is having an issue than you should all post what your issue is and whether or not you have programs like Adfree or NoBloat installed.

On an unrelated note, have you seen zepplin's V8-supercharger? and if so have you used it?
[Nook Color Android Development] mateorod:
Oh yeah, you must have done it before I corrected an error on my part. Try refreshing the package list, sorry!

We have recently changed the way I build the repositories, the way I was doing it had some issues :p.

But that package is now available, I just looked.

I also just tried option 10, with both 8.1 and 8.2. I weirdly had the same issue. I also notice that that the script reads the rom's stock minfree values as 1,1,1,1,1,1, or some such. And that can't be right, obviously. It does display the proper minfree values in the report that scrolls immediately after the option menu.

I will try and take some time later and investigate a little deeper. since the option used to work in 8.1, we know it is something else. I don't have an ad blocker installed right now, so that's not it either. I bet it is changes within the ROM itself.

There have been some...delicacies with the rom lately. I'm sure you've noticed that the device not crashes and automatically reboots after installing a package. That was not by design, although it is practically for the good as far as installiing procedures go. clearing the little bit of davlik cache we do through the install script causes some sort of disruption in the ROM now, when previously it did not. I am testing a version with the davlik cache removal disabled, but I haven't pushed any changes yet.

Any way, I'll look into it, thanks for bringing it to our attention!

oh yeah, and I have seen the v8 floating around, but haven't looked at it. I don't know that it is something that necessitates package management, but I will give it a once over. Thanks again.
[Nook Color Android Development] grayfoxmg1:
Far as I read, he says that the only reason one would want V8 over V6 is that V8 has an overclock function. I just checked my script and noticed that as well, odd. I did notice that it automagically reboots if i restart or force-shutdown.

One thing I discover about this new roms (when I mean new I mean back to when we have some minor appearance of the new cyanogen alien, look at the icon in "settings/theme" if your confused) is that they handle memory differently.

When I restored with titanium after my clean install, it yelled at me for not having enough space. After A quick check I discovered that it was installing programs at a normal rate, but the data that marks certain programs to be stored on the SD was running like 60% slower than the install script. Thus I would use all allocated data, have to quit titanium, and restart for by then it would have relocated my apps in their correct spots.
[Nook Color Android Development] vessamj:
Mateorod,

My previous problem (quoted below) was only a problem because I wasn't yet aware of the new install method. all is well now, thanks for the support
[Nook Color Android Development] inportb:
Build 13 is now in the Play Store, and package breakage detection is working again. After you upgrade, just refresh the package list and install botbrew-reinstdb. And if you install botbrew-wrapper, you get the nifty little botbrew2 shortcut/prefix that you've been waiting for. You could also install botbrew-core, which depends on both of these packages anyway. The app currently does not scroll automatically to the repairables list, but you should be able to swipe over manually and see what needs fixing.

An excellent suggestion, really. I have been grappling with the idea of restricting the view in various ways to make the information more consumable. On the command line, this is not usually a problem because users already know what they want to install (i.e. via Google). This does not translate well to GUI usage. What makes this slightly more complicated is that apt pools together packages from all repositories and uses what it thinks is the most suitable installation candidates. People who have used apt for a while know that they could influence these decisions using pinning, but most newbies are unaware of such a feature. So the idea is to make use of pins in various creative ways...

It's been on the backburner for a while, and it's something that I really want to do to promote BotBrew's utility. Once you enable a repository, you'd be able to restrict your view to that repository only, and prefer packages from that repository while installing stuff (but of course, packages are pulled in from other repos if needed). Maybe even create a home screen icon, use custom graphics, and so on. Developer-specific "app stores", if you would, with apt pinning under the hood.

Of course, once we have that, we'd have to start thinking about paid apps. I'd like to stay away from money for now (because DRM is hard... and inherently broken!), but I'm sure somebody's going to ask for it sooner or later xD

Alternatively... what do you think of the GetDeb.net model? Basically, links on the Web that install packages (from any enabled repo) when clicked.

Thanks for the ideas!
[Nook Color Android Development] tambourineman86:
First, I want to thank everyone involved in this project. I'm glad there is still development going on for this device. I do have a couple questions, though.

I'm trying to use this with eyeballer's ICS running off sdcard. First time I installed the combined package, supercharger + pdroid, the sdcard would no longer boot. I started over and now have v6 alone, installed (or at least thats what BotBrew reports) but the command cannot find the binary. Does it have to do with the fact that I'm running it off the sdcard, or should it work? I used root explorer to check /system/bin (and /xbin) but could not find the v6 script.

I tried reinstalling it and got a segmentation fault. Any ideas?
[Nook Color Android Development] echoedge:
Does this work with SD card cm9's or only emmc cm9's?

I tried it with an SD card boot 5-18 and it just loops at the boot animation screen, never fully starts up.
[Nook Color Android Development] indoline:
I'm following instructions step by step, even went from openGL to non-openGL and tried different build (eyeballer) dates. but regardless, my Current minFrees = 1,1,1,1,1,1 MB

any ideas?

everything else is fine, and tells me I'm 100% supercharged. while its running the script, it even says the new value is: 8, 14, 75, 90, 95, 125

not sure what I should do.....
[Nook Color Android Development] mateorod:
Sorry for the late response...

Yes, the packages work with sdcard installs.

I didn't post about it, but I updated the repo yesterday morning. So make sure you are using a ROM dated 5/27 or later.

The android-framework-pdroid version should be 1.3.2-10. Please clean opkg archives in the settings menu and refresh packages. Then check the version number of this package.

There have been some bugs with the updated v6 script. Please report back if you have roblems with the script itself (seg faults and the like).

If you have an older ROM you would like to use a package for, you can find a list on the second post. If you are using Samiam's builds, please check the build date in the build.prop.

Thanks for trying the packages!
[Nook Color Android Development] indoline:
mateorod, was that in response to me? I'm not sure.

just incase, I'm running the nightly from this morning.
[Nook Color Android Development] mateorod:
No sorry, that was for the sdcard install questions. I have noticed that as well, and haven't had a chance to nail down what is happening. I have stopped recharging from sdcard, and when checking the minfree values elsewhere, they seem to be correct.

I have tried 8.1 as well, but I think it has started appearing with that as well, so that might not be an easy fix I can use. But I will look deeper.

As it stands, I believe that the script is working properly, but not reporting info accurately. I would avoid recharging from sdcard for now.

Basically, this is an issue between the script and the ROM, not a Botbrew or system app issue. I will continue to look into it however, and see what I can find out.

Thanks!
[Nook Color Android Development] indoline:
just as an FYI, I'm not using the SDCARD?
[Nook Color Android Development] mateorod:
I don't know what you mean. There pretty much has to be something functioning as an sdcard for the ROM and apps to function correctly.

Do you mean not a sdcard install? That info was for the posters above you. I should have quoted them.

If you mean, you are not using your v6 settings saved on a sdcard, well, that is the only thing I can suggest for now. Like I said, the packages and Botbrew would not cause these misreported minfree issues (which I have seen myself). But I will look into what is causing it, be it within the ROM or script.

The packages interact with the kernel, for instance and older kernel means you need older packages. We could be having problems due to our new kernel, which is one of the reasons I think our packages need updating so often, due to the active kernel development.

But basically, I am saying that it is an outside issue, but one I am happy to investigate! :)

Edit: And by outside issue, I mean not caused by Botbrew or the packages, not unworthy of discussion. Thanks again.
[Nook Color Android Development] echoedge:
Thanks mate, good to hear.

Why am I having such a difficult problem with it then, what am I doing wrong?

Using the ICS sd card .img, tried both update-encore-20120527 and cm-9-encore-20120528-0730-opengl-unofficial.

Both boot up on the SD card as should just fine.

I then install botbrew, let it configure itself, install the materoid repository, then install pdroid-materoid repository. I then reset (assuming to install pdroid apk) and it just gets stuck at the boot animation forever. Left one on for 60+ minutes, still scrolled at the boot menu.

I've tried this before with the same results in the past prior.

Am I missing a step..?
[Nook Color Android Development] mateorod:
EDIT: You are using Samiam's builds, aren't you? You may have missed this info, which is littered throughout the thread, but easy to miss due to the amount of info here.

Sam doesn't clobber regularly, so you probably have an outdated kernel if you are using his builds, which is incompatible with the latest system apps. The best thing, honestly, is to switch to eyeballer's builds, which you can find at techerrata.com or through Goo Manager. (Sorry, sam...)

If you want to stick with Sam's, you should check your build.prop (in /system) and find the build date. On post 2 of this thread, there is a download link for older packages. Find the package that corresponds to your build date and try that.

But the longer he goes without clobbering, the more his builds are going to be wider mixes of newer pieces combined with older prebuilts and the harder they will be to service with Botbrew. But try it first, they may still work.

Also, you don't have to wait for an hour! Within five minutes of a reboot, at most, an Android is Upgrading countdown should show. If nothing happens after ten minutes, something is wrong!

If you are using eyeballer's builds, try this method.
​

Okay, maybe you have some old packages in your archives, and you are just reinstalling older packages over and over. That can happen, especially if you aren't installing the packages over every install.

I just remade packages and tested them, so I know they work and they have been tested with sdcard installs extensively.

Please clean archives in the Botbrew Settings menu.

Refresh packages.

Before installing, note the android-framework-pdroid-v6 version number. It should be 1.3.2-11, with 11 being the key.

If you haven't done a clean wipe since last trying a package, it should have an option to upgrade. Choose that one.

Reboot (it may do so automatically, with the newest kernel the ROM is a little fragile) and everything should be fine.

To be sure, I just made and tested this from a 5/28 build so you can use them, as long as we get the correct package installed!

Thanks!
[Nook Color Android Development] grayfoxmg1:
does the test 12 script work for us? has anyone tried? WHat's the worse that could happen if I tried it and our roms weren't ready for it?
[Nook Color Android Development] mateorod:
Okay, on your tip, I went and got the latest test script. I usually try and stick with the release candidate's, but as others have noticed, we're having some trouble running the U9RC8.2 so I thought I would check out this latest, which is, as greyfoxmg1 said, the 12th test for the upcoming RC9.

As of my initial tests, the script won't run because of a failure using awk, which the script is using to make calculations. Although the 8.2 script registers our ROM as passing the awk test, this would certainly explain all the various problems we are having with the script lately.

The reported problems include

:

The script crashes upon running the custOOmizer

Misreported minfree values

Now a failed awk test.

As tempting as it would be to blame zep's script, since 8.1 used to work and no longer does, I think we may have discovered a larger problem within the ROM itself. I find it hard to believe that our busybox would escape notice if it wasn't working, but I will check it out today.

Botbrew comes with a pretty robust busybox, so I may modify the script (for my own testing purposes only) and have it use the Botbrew busybox and see if that helps. I will also experiment with replacing our cm busy box as well.

If it is a problem with the ROM, I would have to guess it is a kernel problem, not a CM busy box issue, as our kernel is still under pretty heavy development and is unique to us, while a broken CM busybox would just about have to have been noticed by other devices by now.

I'll update you guys later today.
[Nook Color Android Development] inportb:
For your tests, you might prepend /botbrew/libexec/busybox to your PATH variable -- and let busybox temporarily take precedence. But be careful; either su before setting PATH or use the full path to /system/xbin/su, because /botbrew/libexec/busybox/su doesn't work the same way...
[Nook Color Android Development] mateorod:
Well, it appears it is a busy box issue. Replacing the busy box cures the problem not only within the new RC9test12, but also all of the problems we've been having for awhile with the older versions, problems that didn't use to be there.

I bet zep improved his awk test for this latest script and it is now able to diagnose the problem that got introduced to our busybox maybe a month ago.

I don't know if just awk was affected, but I will go back to the cm busybox and do some more tests. There are some flashable busybox replacements out there, I will go track one down and let those of you who follow this thread get some immediate relief while I look into this further.

Edit: Here is one from zep's pal wraithdu.