yashsingh1/xdaforums huggingface dataset:
[Vibrant General] cashmundy:
CM7 has vibrantmtd as ....device and SGH-T959 as ....model. CM9 has SGH-T959 as both model and device, as does AOKP. If you (or BotBrew) could use model instead of device, it might work well.

What happened before was I tried CM9 over CM7 without a reset. BotBrew didn't catch the upgrade, and so kept the conf from CM7. When I reset and then installed BotBrew, it found the new props and configured accordingly. A hook in BotBrew to check the current rom on startup and reconfigure itself on flashes would be a good thing.

I'm currently showing all three packages, version -9.

One minor note: somewhere you specify the BotBrew refresh button as being on the top right. On my phone it is always on the bottom left. Maybe more vibrant weirdness.

Final random thought: I'm not very impressed with CM9. It has some real drawbacks (the keyboard for example).

CM7 is still overall a lot better (to me) and if PDroid ever makes it there, I'll test it.
[Vibrant General] mateorod:
Well, I am still considering about cm7. Let me see.

Botbrew does has services you can turn on to configure at boot, as well as several ways it detects flashes, although most of those are centered around packages or the terminal.

But thanks for those tips, there is definitely some weirdness going on with the vibrant that I haven't seen elsewhere, but is good to know about because it could resurface in other devices.

But yeah, for instance, you could use light pad to turn your sdcard into a web server, and host websites off of it, so that's one of the services options.

There is honestly a world of stuff in the repo already, and he's about to add debian INSIDE android.

Crazy. Thanks, cashmundy. I will look into cm7.
[Vibrant General] cashmundy:
Very cool.

I think I'll try AOKP again when a new build is out, and test the patch there.

One thing that would be useful would be a white-hat app which would request all permissions, gather all possible data, and display it. As it stands, we have to take it on faith that pdroid, droidwall etc actually work.

For the long term, I am very much hoping for Debian instead of android. ;)
[Vibrant General] gaikokujinkyofusho:
Ok, at the risk of annoying someone (due to my noobness) I wanted to ask if I could do the above for my kindle (which i just flashed with AOKP milestone 5) or is the above strictly for the sammy vib?
[Vibrant General] cashmundy:
The Vibrant is I think the most recent device, and the BandN Nook is supported,

so I expect the Kindle will be someday.
[Vibrant General] mateorod:
If you run cm9 or aokp, I can take care of you.

Post your services, core, and services.jar plus build.prop at my packages thread so we keep this vibrant only.

Thanks for your interest.
[Vibrant General] mateorod:
Done. I have the packages and a thread for Kindle Fire support here.

Okay, c-pimp had brought this up before, and I had an opportunity to look at it, so...I have some test patches for Pdroid 1.3.2 for CM7.2.

I looked for a download pf cm7.2 for vibrant to test, but all I found were torrents. cashmundy, would you attach the system.jar/build.prop pack for me?

If the patches work, I'll put you together a cm7 package.
[Vibrant General] cashmundy:
That was fast!

CM7 here:

http://cm-7-nightlies.appspot.com/?device=vibrantmtd

I'll see if I can pm you some files. As it happens, I gave up on CM9 when I realized it had lost all my contacts and replaced them with what looked like everything in my sim and everyone I had

ever emailed or received email from with gmail, more than 400 useless contacts with no way to batch-delete them. I take this as yet another example of Google's increasing emphasis on Android as a self-spying system over pleasant, useful software. So I will be able to test PDroid on cm7, possibly until I have a Debian phone.
[Vibrant General] cashmundy:
Now, this is a sad situation: I tried a pm, but had no option to attach. Using Boat browser, when I try to attach here, I get a window with "choose file" buttons which do nothing at all. I tried the stock browser, and it doesn't even display this thread well enough to show the "reply" buttons. So I'll paste in build.props here, and we'll have to find another way for the other files.

This is straight from the rom:

# begin build properties

# autogenerated by buildinfo.sh

ro.build.id=GRJ22

ro.build.display.id=GWK74

ro.build.version.incremental=eng.jenkins.20120421.003105

ro.build.version.sdk=10

ro.build.version.codename=REL

ro.build.version.release=2.3.7

ro.build.date=Sat Apr 21 00:31:14 PDT 2012

ro.build.date.utc=0

ro.build.type=user

ro.build.user=jenkins

ro.build.host=cyanogenmod

ro.build.tags=test-keys

ro.product.model=SGH-T959

ro.product.brand=samsung

ro.product.name=soju

ro.product.device=vibrantmtd

ro.product.board=aries

ro.product.cpu.abi=armeabi-v7a

ro.product.cpu.abi2=armeabi

ro.product.manufacturer=Samsung

ro.product.locale.language=en

ro.product.locale.region=US

ro.wifi.channels=

ro.board.platform=s5pv210

# ro.build.product is obsolete; use ro.product.device

ro.build.product=vibrantmtd

# Do not try to parse ro.build.description or .fingerprint

ro.build.description=soju-user 2.3.4 GRJ22 121341 release-keys

ro.build.fingerprint=google/soju/crespo:2.3.4/GRJ22/121341:user/release-keys

ro.cm.device=vibrantmtd

# end build properties

#

# system.prop for smdkc110

#

rild.libpath=/system/lib/libsec-ril.so

rild.libargs=-d /dev/ttyS0

ro.sf.lcd_density=240

#

# ADDITIONAL_BUILD_PROPERTIES

#

ro.opengles.version=131072

wifi.interface=eth0

wifi.supplicant_scan_interval=20

ro.telephony.ril_class=samsung

mobiledata.interfaces=pdp0,eth0,gprs,ppp0

dalvik.vm.heapsize=32m

ro.com.google.locationfeatures=1

ro.com.google.networklocation=1

dalvik.vm.checkjni=false

persist.sys.vold.switchexternal=1

keyguard.no_require_sim=true

ro.ril.hsxpa=1

ro.ril.gprsclass=10

ro.config.notification_sound=OnTheHunt.ogg

ro.config.alarm_alert=Alarm_Classic.ogg

ro.rommanager.developerid=cyanogenmodnightly

ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html

ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html

ro.com.google.clientidbase=android-google

ro.com.android.wifi-watchlist=GoogleGuest

ro.setupwizard.enterprise_mode=1

ro.com.android.dateformat=MM-dd-yyyy

ro.com.android.dataroaming=false

ro.config.ringtone=Playa.ogg

ro.config.notification_sound=regulus.ogg

ro.config.alarm_alert=Alarm_Beep_03.ogg

persist.sys.themeId=Cyanbread

persist.sys.themePackageName=com.tmobile.theme.Cyanbread

ro.ril.enable.managed.roaming=1

ro.ril.oem.nosim.ecclist=911,112,999,000,08,118,120,122,110,119,995

ro.ril.emc.mode=2

ro.additionalmounts=/mnt/emmc

ro.vold.switchablepair=/mnt/sdcard,/mnt/emmc

ro.modversion=CyanogenMod-7-20120421-NIGHTLY-vibrantmtd

ro.setupwizard.mode=OPTIONAL

dalvik.vm.dexopt-flags=m=y

net.bt.name=Android

dalvik.vm.stack-trace-file=/data/anr/traces.txt
[Vibrant General] cashmundy:
Being unable to do this on the phone, I have resorted to the laptop to send the attachments from the recent CM7 nightly. I think a phone with a gigahertz processor and nearly half a gig of memory should be able to upload a few stinking files, but apparently that is just... too... much... to expect... arrr....
[Vibrant General] mateorod:
Sorry that was such a pain. I was worried that the patches wouldn't work after I saw you went through all that effort! But the patches look good, so you should be fine.

The package is in the repo, it is called android-framework-pdroid-cm7.

The architecture is vibrantmtd, so make sure your arch file matches that if you don't see the package. I have been in some conversations with inportb about the architecture situation, but with the upcoming switch to dpkg, we will just have to be careful for now.

Let me know, but it looks fine from here.

Edit: There is one quirk in the postinst script that is designed to ensure only those with cm7.2 are able to install the package. If that gives you trouble let me know, and I will just take out the fail safe part of the script until later.

Thanks!
[Vibrant General] cashmundy:
The patch seemed to install fine, and the phone is working, but PDroid says the patch is not installed.

What info can I provide? Want me to attach the jar files from the phone?

The problem may stem from my running a cm7 kang. I switched to official cm7, but now the package is stuck: it apparently did not install enough to create backup files, which means I can't uninstall or reinstall it with botbrew. Probably need an opkg force command to deal with it.
[Vibrant General] mateorod:
Hmm...I just checked the jar packs and they looked patched correctly to me. Ok, two things you can do. Reinstall the package android-framework-pdroid-cm7 and then take a screenshot of the Botbrew output.

Then you could reboot, double check pdroid, then upload copies of the services, core and framework.jars in your system/framework folder.

We'll get it working for the rom you want. I am not going to give it up now.:D
[Vibrant General] cashmundy:
I must have edited my post while you were sending the one above. The thing is sort of horked at this point: can't uninstall or reinstall. I could just wipe botbrew and start from scratch... that's what I'll try.
[Vibrant General] cashmundy:
Ok, the error is "not replacing services.jar because this is not cm7.2". There is no actual 7.2 for vibrant, but this is the most recent nightly.
[Vibrant General] mateorod:
Okay, try again. I thought that might be it, so I just removed that fail safe. \

Refresh packages again and make sure it is android-framework-pdroid-cm7_1.3.2-8

8 being the important part.
[Vibrant General] cashmundy:
Still no luck. I've been thru iterations of removing botbrew, flashing the rom, etc. I've got version 8, but it still has no effect other than a stuck package.

The first error message on install was "cannot cd to"... mumble mumble... ahem...

I tried one screenshot program, "ascreenshot", which doesn't work. I've never done a phone screenshot.
[Vibrant General] mateorod:
Ahh..that did it. Just enough info so I caught my dumb mistake. Thanks for being so diligent about all this, cashmundy. I can't test these packages myself, so you have been a life-saver several times over.

It should be fixed now. Well, let's say that that particular problem is now fixed.

But it should be okay now. And don't work so hard, for real. If it doesn't work, just report back and tell me what you can. No need to spend too much time on it. That's my job:)

Anyway, I believe we should be done, with this one.

Thanks!

edit: it will be version 9.

Update 5/15: The CM repo had a pretty big change in the source tonight, requiring me to update many of the packages for various devices. It won't affect anything not being built nightly yet, but if any of the packages cease to work, simply post in the thread and I will update the Botbrew repo.

(don't worry cashmundy, it won't affect you:p)
[Vibrant General] cashmundy:
Still no luck with version 9, but I was able to find a decent app, "Screen Grabber".

.... s... s... s...! Using the phone. I'll try fennec, see if it can upload.

Able to upload with Firefox Aurora, which is a perfect candidate for PDroid: the permissions now rival Google apps in their regal disregard for privacy.
[Vibrant General] cashmundy:
(Just found a new cm7, 7.2-RC2, switching to that).

This one is a shot of attempted removal:
[Vibrant General] mateorod:
You can try the new CM7.2 rom you found, but I wouldn't advise it. Or rather,

that's fine, but I made the files from the ones you posted the other day. So they might not (are probably not) compatible with a different ROM.

If you want to keep the 7.2, just upload the same jars and I will put them into the package instead. If you want to keep the kang I guess you had before then you can try the new package that is in the repo version 10.

It was just a careless mistake, sorry. There is a button in the main Botbrew menu that is Clean Archives. That gets rid of competing version info, it can be done with no loss of function. You could try that first and then upgrade to version 10.

But let me know which rom you prefer, because they don't mix and match, you know?
[Vibrant General] cashmundy:
Until there is an official 7.2, it probably makes sense to bulld the patch against an RC instead of a random nightly, so please find below the files from update-cm-7.2.0-RC2-vibrantmtd-signed.zip:
[Vibrant General] mateorod:
Okay, I added a package that covers those files. There was one file where the patching failed in a couple spots, the SyncStorage file. I looked at it, and I think it failed because you don't have those areas of code to patch. So it should be okay.

But just in case you notice anything funny, I just added a package.

Sp, the package for the files you just gave me is

android-framework-pdroid-cm7rc

And the one we had been using (which seems to be a later build, if I remember properly?)

android-framework-pdroid-cm7

I think the scripting problems have been fixed, but let me know. Thanks.
[Vibrant General] cashmundy:
Success!

You should delete the old package. It was based on the nightly previous to RC2, which is currently the most recent CM7. Since there is an RC1, and given that the package is apparently quite version-specific, you might want to rename it from 7rc to 7rc2, but that's up to you.

Thanks for all the work, glad I could help in small ways.
[Vibrant General] mateorod:
Okay, I will get rid of the old package. I didn't realize this was the RC2. I may update the cm7 patches to reflect this, so you may notice an uptick in version number in a few days or so.

Thanks for testing, I am going to add CM7 rc2 to the list of supported ROMS.
[Vibrant General] cashmundy:
I updated this older permission management poll I put up to spread the news:

http://xdaforums.com/showthread.php?p=24007445#post24007445

The Debian BotBrew will be interesting.
[Vibrant General] closedcircuit:
PDROID BOOT LOOP WARNING Version 9 & Build 36

Pdroid 1.32 version 9 is NOT COMPATIABLE WITH AOKP Build 36. Bootloop will occur with installation via botbrew.
[Vibrant General] c-pimp:
I am syncing source for gummy then aokp and hopefully can get the files to mateorod and pastime tonight so they might be able to get patches this weekend :-)
[Vibrant General] hkfan:
Is this compatible with slim ROM
[Vibrant General] c-pimp:
Not yet sorry, I asked kravind to help support it but don't think he was interested
[Vibrant General] mateorod:
Hey, thanks for letting everyone know!

I have updated the Botbrew repo, so the package android-framework-pdroid-aokp-1.3.2-10 IS NOW compatible with AOKP Milestone build 36.

In the future, for anyone following this thread or using a package, if you ever encounter an incompatible package, I would appreciate it if you would do just what closedcircuit has done, and let us know. Maybe even send me a pm, although I subscribe to all these threads, so I should usually see a simple post.

This is the only way I can find out if the packages are outdated, as I don't have the device!

But thanks, closedcircuit. The Botbrew repo has been updated and AOKP is again supported!

Thanks as always for your efforts, c-pimp. I didn't see that Team Gummy had updated, though I looked. And as you can see, the old patches still work for AOKP. I have hope that the Team Gummy patches we already have (made from the files YOU made for us!) will work once that ROM is updated.

...And One more Thing

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 we get the switch hammered into shape.

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 new stuff, 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!
[Vibrant General] c-pimp:
Having trouble with new gummy sync, starting from scratch... Yay!...

re read and answered my own question that was previously here lol...

MORE UPDATES

old gummy patches dont work, new gummy built from sources and hopefully is the next step at getting closer to slim patch (im always hoping that so dont everyone get their hopes up that wants that lol)

repo sync still in progress ... had to start from scratch with gummy was running into some trouble...

Ohh yeah... I made a patch with linux patcher for RMS rom for vibrant!

files are at the thread here for those of you without linux

http://xdaforums.com/showthread.php?t=1654412
[Vibrant General] mateorod:
So c-pimp, I see you're building a new gummy ROM, the newest was posted May 8.

I guess the files you posted before were from before that? I somehow thought they were more current than that.

I haven't had a chance to test this, but are you sure none of the older patches work? I know I have gummy patches personally, but maybe they're not in the patcher. I'll look when I get a chance.

The idea behind the patches is just to make them once. There was a big repo change that broke all the patches that once, but that should be pretty irregular.

For instance, it only takes the two CM9 patches to pretty much cover every nightly since it started.

I'm hoping to figure out what unlocks the aosp roms, but until people try our current patches, we won't know how far we are,

As for slimrom, in my experience, there is pretty rarely any coding going on with the custom builds. It is just a matter of finding out how the ROM was assembled. It is sometimes done through building from source and often done by simply unzipping roms and swapping folders from other roms in and out.

I don't know what slim has done, but I will look at it a little more carefully. It is basically a matter of finding out who or what coded that services.jar, and then applying the proper patch, which should already exist, even though I haven't identified it yet.

His reluctance to give some direction is disappointing, since it costs him nothing. Well, let's see what we see, huh?
[Vibrant General] mateorod:
Okay, if you are looking for some adventure with your Vibrant, this could be for you...

The newest release of Botbrew, Botbrew Basil is on Google Play for testing purposes. The Debian library is opening itself up to our Android devices, and it started here. Pretty damn cool.

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.

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 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.

If you run into problems, or just have some feedback, please report at the dedicated Botbrew thread. I provide software for the app, but Botbrew itself has been developed by inportb, and he will be far more able than I to troubleshoot Botbrew related issues!

Now if you install a package and reboot into bootloops, then that means that your ROM has had a major update, and in that case please continue to report to this thread so I can update the vibrantmtd packages.

Thanks for your interest and support!
[Vibrant General] closedcircuit:
Pdroid 1.32-10 will cause

BOOTLOOP

with AOKP Build 38. Wait for new version before installing.
[Vibrant General] mateorod:
No longer!

Thanks for the tip. New packages are in the repo. I added some new packages for this ROM as well, ones I do for some other devices.

Since this it would seem that AOKP is the only ROM that vibrant users are currently installing packages to, AOKP is the only one I made new packages for.

Other ROMS will be looked into by request.

The packages are:

android-framework-pdroid-aokp

Enables PDroid

android-framework-v6-aokp

Enables 100% V6 Supercharger

android-framework-pdroid-v6-aokp

Enables Both Pdroid and V6.

The installation instructions are the same for all packages and can be seen here.

Edit You will need to download a copy of the V6 Supercharger script separately. You can do so here.

These packages are available on both Botbrew stable (anise or Root in Play) and experimental (Basil).

Let me know how it goes, and if you think I should start a thread for this to let more people know.
[Vibrant General] cashmundy:
I've just noticed that CM7.2 final is out for the vibrant. I haven't been tracking the nightlies, figured to just wait for the 7.2 final before suggesting new botbrew packages. I can extract files if desired.
[Vibrant General] mateorod:
Sure. Thanks for pulling em, I'll update the package when I see them.
[Vibrant General] cashmundy:
CM7.2 final files

OK, here they are:
[Vibrant General] mateorod:
well, I am going to have to investigate further...but my 7.2 patches fail on those jars. It took me a minute to get to it because pastime1971 and I were going live with this...

http://xdaforums.com/showthread.php?p=27589740#post27589740

But since I need the 7.2 patches to work for that project, I am going to work on it now..

I'll report back when I know more. At worst I will have to grab the source and build 7.2 for myself, but that will take me some time...
[Vibrant General] cashmundy:
This is the URL I pulled from:

http://download.cyanogenmod.com/get/jenkins/2872/cm-7.2.0-vibrantmtd.zip

I checked the sums, and followed the same procedure as before, so the files are probably good.

I have what seems to be a working CM build environment set up on my netbook, if that helps at all.

Nice new project.
[Vibrant General] mateorod:
Well, might as well give an update.

I made new patches which work on CM7.2 final, but for some reason they are failing on your files. I could be an issue on my end, I had to leave my work station for awhile and won't be able to look at it until tonight. But I will get back into it tonight. Pastime has built as well, so I am going to make patches from his and check those as well.

Another option is to have you build for Pdroid as well. It really shouldn't be necessary though, I have never had a problem porting between cm builds and I can't see why that would start now.

We'll get there.