[Captivate Android Development] ranova:
According to the Vibrant forums, Jr33 has fixed and ported the MobileAP (native Infrastructure Wifi Tethering AP) from the Galaxy S i9000 to the Vibrant:

http://xdaforums.com/showthread.php?t=756804

Why this is important and better than the Wifi tethering apps (Barnacle and android-wifi-tether):

This is REAL infrastructure mode. Not the hacked up ad-hoc mode (which android-wifi-tether and barnacle uses) which A LOT of devices (other android phones, ps3, wii, corporate laptops included) cannot connect to.

Because it being infrastructure mode, it supports WPA, a much more secure protection than WEP.

This is natively built into the Galaxy S i9000 phones. But taken out by AT&T and T-mobile. It just works, and works well - because it was MADE for our phones!

android-wifi-tethering hard crashes a lot on start, forcing you to do a battery pull, and may lose connectivity every so often.

Barnacle requires you to change the MTU of your client device, not possible in a lot of cases (consoles, phones, etc), and may cause conflicts when moving to a different wifi AP.

-------------------------------------------------------------------------------------------------------------------------------

Update 8/22:

Designgears has figured out a way to automatically launch the wlp2pservice on boot, therefore, no more manual entry is needed (but requires kernel flashing). Please see:

http://xdaforums.com/showthread.php?p=7785171

The reason why it requires flashing the kernel (while Vibrant did not) can be explained by Jr33:

-------------------------------------------------------------------------------------------------------------------------------

Update 8/20:

With the help of Jr33 (person that did the port to Vibrant), we *kind* of got it working with a few hoops. Jr33 should be given credit as he created and repackaged the captivate MobileAP update.zip; I was merely a test dummy. This thread will be locked when a solution is made and Jr33 will create a new thread with the final version. Go buy him a red bull!

REQUIREMENTS

Update.zip downloaded below

Rom Manager

ClockworkMod Recovery flashed on your phone (using Rom Manager)

Busybox

An Android Terminal App (ex: http://www.appbrain.com/app/jackpal.androidterm)

DOWNLOAD The Captivate mobileAP update.zip:

http://www.mediafire.com/?ownoqzgo6cbtmoj

File is also attached at the end of this post.

INSTRUCTIONS

Rename to update.zip, put it on your INTERNAL SD card root

Boot into ClockworkMod Recovery (using Rom Manager) and reinstall/update packages.

Reboot - note: first time boot after updating this will take a little while.

Now go into an Android terminal app and type the following:

su
busybox nohup /system/bin/wlp2pservice &

This starts the wlp2pservice. (Props to designgears for finding out this new command)

Old command (just typing in /system/bin/wlp2pservice in terminal (does not require busybox)) works BUT you will need to keep Terminal open during the duration, if force closed, you will have to retype that command in again.

5. Now you can go into Settings -> Wireless and Networks -> Mobile AP Settings to start your Access point.

Note: if you change any of the settings (AP name or WPA password) it may crash wlp2pservice. Use a task manager to force close "MobileAP Settings." Do step 4 again and your settings should be there.

This works until you reboot your phone. If you reboot, you need to go back into terminal and manually start wlp2pservice again (do step 4 again).

If you do not manually launch wlp2pservice, when you open up MobileAP settings, it just sits there on a black screen and if you check logcat, you see the looping message pasted below. We are currently trying to fix the necessity of manually launching wlp2pservice. This is not how it was intended to be.

-----------------

Developers with a Captivate, we need your help:

Upon opening MobileAP settings WITHOUT manually launching wlp2pservice in terminal, yields the following (from logcat):

I/ServiceManager( 3459): Waiting for service WLP2PService....

It loops until you force close "MobileAP Settings" in your task manager. Something is not calling wlp2pservice to execute.

Also, rebooting the phone or closing/ending terminal (on the pc or phone) requires you to go back into terminal and execute wlp2pservice manually, otherwise opening MobileAP settings yields the same loop above.

I am guessing that wlp2pservice is not launching on boot, or not executing at all when you open up MobileAP settings. I'm not sure which is supposed to happen.

This *seems* like an easy fix, and because Jr33 does not have a Captivate it is hard for him to help troubleshoot this. This is why we need other people to help figure out a way.