yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] mateorod:
Have you solved this problem? They seem to be there for new users, going by the last post...
[Nook Color Android Development] NapalmDawn:
Hi Mateor. I'm away from the NC for a few days but I will check Monday. Yes, I still have the problem. I even removed the repo and readded it.
[Nook Color Android Development] grayfoxmg1:
Script 9 and a request.

Which botbrew are you on? Because running 'Basil' I had an issue where it was bootstrapped in two locations and locked the program up. I had to delete all the data I had on it and uninstall. I then had to set everything up again, annoying but not that big a deal.

If your problem is in regular botbrew than I am sorry to say that I quit using it sometime ago, and wouldn't know how to fix it.

A good backup plan to have, is to grap one of his newer scripts (I can vouch the script 9 works on nooks with the exception of wheel alighnment) and save it on your SD card. Zepplinrox now has a service to edit a service.jar that is linked with the scripts and happens on the nook. So if you ever run into a problem with botbrew you can still supercharge your nook.

Mateorod, I've included the script that we need to work on our nook in order for the wheel alignment function to work. If you have time than could you possibly take a look, if not than that's fine, its not a big deal. Also included is Script 9, because I'm nice like that.
[Nook Color Android Development] mateorod:
Thanks greyfoxmg1. I will update the V6 package to include the latest script today. I will also add a link to your post alerting users to the attachment needed to run the wheel alignment.

As for the missing packages, when try clearing package archives in the Botbrew settings and refreshing packages. I have checked and the packages are in the repo correctly. Which Botbrew are you using?
[Nook Color Android Development] grayfoxmg1:
Mate, The attachment doesn't run on our nooks, CWM aborts it, I was wondering if you could take a look at the actual script (can you do that?) and then maybe we can get it to work.
[Nook Color Android Development] mateorod:
are you talking about the sqlite and zipalign script you attached above? I haven't tried it as I don't have a wifi on mine anymore and loading stuff is a bit of a hassle.

I can certainly look at it, though. Although if that is what you mean, (I can't think of what else you might mean?) then it looks like something you run in the terminal by removing the .pdf attachment and running like the supercharger script.

But like I said, I haven't looked at it yet :-) Let me know a little more
[Nook Color Android Development] grayfoxmg1:
That is what I mean, and I have tried running it in script manager and it just aborts(and I'm the one that added .pdf to it's name so I could upload it). It comes as part of the supercharger starter kit (included) which has some script along with the wraithdu busybox. The starter kit also, doesn't work on our nook. Since I can add the busybox on my own and nothing bad happens, I think it is safe to assume that the error is in the way the script identifies our device. Something is telling it, that it isn't being run on an appropriate device, but I don't know how to fix that.
[Nook Color Android Development] mateorod:
ahhh...that is weird. But not first time scripts from these guys have needed some tweaking to run properly for us. Which is so random, considering that for most of this thread's life, we've only had CM9, nothing off-brand about it.

But I will give some time to this tonight, I was going to update the v6 package already. So I will dig into the script some and see what I can see.

Thanks for the info.

and what's with xda handcuffing us with the .sh extension? You know? This is one place that should be no problem...
[Nook Color Android Development] grayfoxmg1:
Thanks for looking into it, as for XDA shackling scripts, I remember when we could upload .sh files but sometimes the uploader would yell about an "invalide file type." Eventually we stopped being able to so everyone just started adding .pdf to them. I actually think zepplinrox started it.
[Nook Color Android Development] NapalmDawn:
With regular botbrew and reinstalling it and rebooting, still not getting your repo. Sits at 226 packages. When using basil and installing the repo, it says it's refreshing the cache. It comes back to the packages screen and nothing new is added even after refreshing it again and telling basil to restart
[Nook Color Android Development] mateorod:
Okay, I think your problem is that you are running the sqlite installer script from a separate directory. It looks to install sqlite3 and zipalign binaries in data/local and system/xbin, that's all this script is doing. Now we have sqlite3 standard, but not zipalign, which I am betting is what the wheel alignment is (smart, huh? lol)

The script is grabbing those binaries from the Supercharger Starter kit. It has relative links, not a download like from wget or something. So if you run the script separately, it doesn't know where to find the files and returns an error.

Unzip the starter kit package and you will see a folder called xbin. Inside are the sqlite3 and zipalign binaries. I simply renamed the uncompressed directory starterKit.

soo...

su
cd sdcard/starterKit
sh sq*

and then the script will run fine.

After I this and tested it, I quit looking at the scripts, so if you have anything else that is bugging you about it, let me know and I will dig into it again. I will update the V6 script in a little minute.

I don't have a Nook Color that has access to the Internet anymore, so this is going to be hard for me to test. I know that the repos are up, the kindle fire thread has been quite active over the last month. What ROM are you using for your Nook Color?

Reinstall botbrew root, not basil for the moment. I don't know what changes have happened lately in Basil and I don't want to speculate or assume. So let's debug Anise, which is the original, stable Botbrew.

After installing, please clean archives and refresh packages. If the repository-mateorod packages still don't show up, could you please post the contents of botbrew/etc/opkg/arch.conf file? Maybe the package filtering is set incorrectly. Something is wrong, since you are seeing the rest of the Botbrew repository.
[Nook Color Android Development] grayfoxmg1:
Thanks for looking at that, I was in fact, able to get it to work after that. Perhaps you can work an automated installer into the next botbrew update, than the followers of this thread that either do not know how, don't care to know how, or are to lazy to install it themselves will be able to run the service from the supercharger script.
[Nook Color Android Development] NapalmDawn:
One of them is running a CM9, 06/20/12 from Eyeballer. This one never seems to get the repo when added. I blew both Botbrews away, reinstalled Botbrew (regular), removed the package, re-added, cleaned the archive and refreshed. Still-226. My other NC, the one running a Team Kang ROM did get the repos to show. I installed the v6. I was on the stock browser and the NC hung up forcing me to power it down. Now it's stuck on the pink unicorn loader. I wiped caches and fixed permissions . . .still stuck atm. Going to try a recovery a little late. So basically one NC got it, one didn't (CM9 06/20)
[Nook Color Android Development] grayfoxmg1:
open-gl or non? and have you tried updating the a more recent build of CM9?
[Nook Color Android Development] mateorod:
Okay, I have updated both of the Botbrew repos. They both now have the update 9, RC10_test8 V6 script. I also updated the mods on the services.jar, which is why this took me an extra day. Zeppelinrox has added some additional smali edits for Jelly Bean and ICS which he is confident make a huge difference. So you are not only getting the latest script, but also the most up-to-date services.jar mods.

Let me know what you think!

Well, if you can see them on one Nook then we know they are available. Would you please look at the arch.conf file I directed you to a couple posts back? The designations on that file are what filter your packages. The best bet is that somehow the configuration of that file is somehow wrong, and Botbrew isn't showing you the packages because they are assigned to be visible to only encore devices.

Please paste in the contents of that file as well as attach the build.prop of the rom you are running. Somewhere in there we probably have an inconsistency. Although Greyfox is probably correct; the easiest fix may just be to update the ROM and check again. You don't have to wipe anything or lose any data, just download, wipe davlik, and flash.

Oh, and I sincerely doubt that any of the packages here will work for AOKP. I actually used to have error checking to ensure the packages were only visible to CM9, but I found it was causing more problems than not, especially when CM9 was the only ROM we had for so long...

Anyway, let us know how it goes.
[Nook Color Android Development] NapalmDawn:
Here are the 2 nooks I have. One on the left can never seem to get the 234 apps. The one on the right did add the repo properly when it was AOKPed. It crashed, I restored and it was able to get it again running the version you see. That right one was able to add the repo again.
[Nook Color Android Development] DizzyDen:
The one thing that stands out to me is the one on the left has a build.prop edit saying its a Samsung GalaxyS... don't know if this would impact syncing repo's the way your trying or not.
[Nook Color Android Development] mateorod:
Yep, that is what it is. You said you were using a build by eyeballer, you didn't tell me it was the PA rom I put together...that's why I asked you to print the contents of the arch.conf file in my other responses.

I left the build.prop that way in PA because the system apps in that build were pulled from a galaxy s2. I would rather have it reflect the fact that the device is a nook color...but I think that might cause more harm than good. For sure when using Botbrew. The packages in Botbrew are for sure going to be incompatible with PA.

What package are you trying to install? If you just want the V6 supercharger then you can easily use the Auto-Patcher that is in my sig. It works on OSX, Linux and Windows using Cygwin. It also includes the latest smali edits just released by the V6 dev. Any questions about the patcher are better put in either the PA or Auto-Patcher thread, though. I am maintaining this thread because I know a bunch of people have gotten used to the method and there are some significant advantages to package management in general. But the reality is that for both of these mods, the Auto-Patcher is more than sufficient.

If you were trying to get PDroid, I haven't tried it yet but the Auto-Patcher has patches for that as well. Try the 20120615 or 20120626 patches for that.

But the patches might not work. The reason that eyeballer got together with me for PA was my experience with binary hacks. There isn't any source code released for PA yet, so he can't build a native one yet. The port is kind of a feeler to see how people like it. The reaction has been very positive, so we're planning on keeping it updated...but for now, with no source, the likelyhood is that PDroid will be out of reach for PA for the time-being.

Thanks Diz.
[Nook Color Android Development] explorer-10:
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..
[Nook Color Android Development] NapalmDawn:
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.
[Nook Color Android Development] mateorod:
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.

Okay. Glad you got what you needed.
[Nook Color Android Development] NapalmDawn:
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.
[Nook Color Android Development] mateorod:
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.
[Nook Color Android Development] inportb:
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
[Nook Color Android Development] grayfoxmg1:
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.
[Nook Color Android Development] inportb:
@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 :)
[Nook Color Android Development] mateorod:
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.
[Nook Color Android Development] cmonty14:
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
[Nook Color Android Development] mateorod:
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...
[Nook Color Android Development] NapalmDawn:
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.
[Nook Color Android Development] NapalmDawn:
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?
[Nook Color Android Development] mateorod:
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.
[Nook Color Android Development] generalpelmen:
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.
[Nook Color Android Development] mateorod:
hey sorry. Only CM10 is supported.

You can use the Auto-Patcher in my sig to make an update.zip that will enable V6 or Pdroid for that rom, though.
[Nook Color Android Development] grayfoxmg1:
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.
[Nook Color Android Development] mateorod:
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.
[Nook Color Android Development] tzpm:
收件人： [Packages][7-16] ICS V6 Supercharger- now w/ PDroid

can I use those to diff and patch
[Nook Color Android Development] mateorod:
Numus-

Thanks for the heads up! I have spent so much time crawling that thread, I never realized the latest update isn't on the sig of the first post. I have updated the links on the guide to include the single post where zeppelinrox puts it up. It can also be found in the twitter link on his sig.

Here it is for you- http://xdaforums.com/showpost.php?p=22689090&postcount=8372

As far as the integrate to build.prop, I think that is being done automatically with both linked versions now. That may have been a hold-over in my notes from the first test release. I have been installing it over updates the last couple weeks, so I had thought the script was noting that it wasn't my first run and was skipping the step. I will test off a complete wipe and adjust the guide if I still don't see it.

Update: Dug through the code, and it the script now skips asking to integrate build.prop if it detects the device is running ICS and simply does it automatically. I am not sure if that is a featutrenofnthe newernupdatesnor a holdover from my notes when I first began the guide. I am not sure it matters, really. I have adjusted the guide to acuratly reflect the user experience. Thanks for bringing it to my attention!

I also may have, ahem, deleted my build.prop and had to restore a backup around the same time. Strictly for test purposes, you understand. So I didn't think it was a universal change when that step went away.

Thanks for the feedback.
[Nook Color Android Development] gsutton:
I have a rooted stock (v1.4.1) nook color. Do I flash the zip to install the services.jar? I did that many minutes ago, and it is still showing the initial startup screen with the "n" logo. Thanks.
[Nook Color Android Development] mateorod:
This services.jar file was taken from a build of a custom ROM for the Nook. It is not to be added to other ROMs, including stock. It is only for Cyanogen 9, the port of Google's ICS.

Your stock, even though it is rooted, has a different set of code altogether. It is running Froyo, which is equivalent to CM6.

I don't know very much about the internal structure of the stock ROM, I must say. I would assume the structure would be similar. I mean, is your stock Nook still functioning correctly after flashing the above zip? I can probably help you undo any damage if there was any, so don't get overly nervous, but it probably wasn't the best idea.

But yeah, your ROM isn't what was in mind with this guide. I guess you should be able to run the script though, although I don't see why you would want to. B& N pretty much handles how many things you can do from within the OS, and I just don't see the benefit.

Edit: Ahh, I see. Bootloops. That does seem the likely consequence. I would recommend getting the stock 1.41 zip on a SD card, booting into clockwork recovery, and re-installing. I don't know much about rooted stock, but you do have recovery, I have to assume.