I confirm this is working with the 5-12 CM9 nightly. Thanks to mateorod and everyone he thanks in the post above!

Thanks, cashmundy. The problem was that cm9 has a weird naming convention for just your device, at least unique as far as I have seen.

I just changed the package to reflect your arch.conf.

So thanks very much for testing and finding the problem. I am pretty sure everything is OK now, but let me know!

Still on CM9. Did a reset, installed botbrew and your repo, and I now have no pdroid package.

As expected, botbrew fetched the CM9 props on install
, except that it down-cased the model to "sgh-t959".

arch.conf:

arch all 10
arch any 20
arch noarch 30
arch armeabi 100
arch armeabi-v7a 110
arch sgh-t959 120

build.props:
ro.product.model=SGH-T959
ro.product.brand=samsung
ro.product.name=SGH-T959
ro.product.device=SGH-T959
ro.product.board=aries
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi

Okay man. I took out the sgh-t959 package because I thought you said cm9 had vibranttmd as arch.

Are you saying that it changes whether or not you install cm9 as an update? Cause I don't see how that would be.

I am going to make it so Botbrew has cm9 packages for sgh-t959 and vibrantmtd. We'll sort it out for good later tonight when I have some time.


Thanks for your time and effort testing this stuff!

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.

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.

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.

Originally Posted by mateorod

Hey guys-

Most everyone in this thread I already know from the port thread. I was looking for a good place to put out this info. Glad I didn't start another thread already!

Okay, this is directions for PDroid support through Botbrew. Installing these packages over your nightlies will get PDroid working each time you flash, without having to patch every time. This way you can update your rom whenever you want.


Here is the XDA frontpage article about this exact process!

IMPORTANT: Eventually, the source code for these ROMs will change to a large enough degree that the packages won't work anymore! Just reflash the ROM and come report here at the thread. I will update the package as soon as possible (usually pretty damn soon, if I do say so myself...)

Directions

1. Install Botbrew from Google Play
   Botbrew will bootstrap some packages necessary for its operation.
2. Install package repository-mateorod and press the refresh button at top right!
3. There are three packages available at the moment for the Vibrant. Install the package that matches the ROM you are using.
   • android-framework-pdroid-cm9
     For Cyanogen9 ROMs
   • android-framework-pdroid-aokp
     For AOKP Milestone builds
   • android-framework-pdroid-aosp-gummy
     For Team Gummy AOSP builds
   YOU MUST install the package that corresponds with your ROM, or it will result in bootloops!
4. Reboot!
5. Launch PDroid and configure.

That's it!

Note: You won't see any of the packages if you look while running CM7 due to an inconsistency in the cm7 build.prop.
If you have any questions about Botbrew or the process, here is a Q&A I have at the thread for my packages I host for the Nook Color.

If you have any questions about PDroid and the port to ICS, here is pastime1971's thread on the process. Thanks pastime!

Also thanks to c-pimp for the Team Gummy files! Also to svyat for PDroid and inportb for Botbrew!

cashmundy- could you maybe put a note in the OP about this being here? If you think I should start a new thread, I will. Thanks!

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?

Originally Posted by 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?

The Vibrant is I think the most recent device, and the BandN Nook is supported,
so I expect the Kindle will be someday.

Originally Posted by 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?

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.