PAW Runtime has been updated to support PHP.
To install PHP for the runtime version of PAW, download the file PawRuntime_PHP_Setup.zip (link below) and unzip it to /sdcard of your Android device.
After starting PAW Runtime a PHP menu entry should be available.
After selecting the entry the page shown below should appear...
PHP Setup
Make your selections and press the Install button. PHP should be available after a restart of PAW Runtime.
If you wold like to get rid of unnecessary files and the menu entry, you can delete the file /sdcard/paw-runtime/webconf/apps/php_setup.conf and everything inside the /sdcard/paw-runtime/html/php_setup directory except the conf directory.
This post gives a quick overview what has to be done to move the PirateBox installation to a different directory.
By default the PirateBox HTML files are located in the directory /sdcard/paw/html/app/plugins/piratebox_plugin/html and uploaded files are stored in the folder uploads inside the HTML directory.
I'll demonstrate what to do to move the PirateBox to a different directory (in my example /sdcard/piratebox_ext). You can of course also use a directory on an external SD card.
Copying the HTML Directory
First thing to do ist to create the new folder /sdcard/pireatebox_ext.
Now copy the directory /sdcard/paw/html/app/plugins/piratebox_plugin/html to the new location /sdcard/pireatebox_ext.
As a next step we will edit the PAW server configuration.
Changing the PAW Configuration
The configuration file used for PirateBox is named handlers.xml and it's located inside the /sdcard/paw/html/app/plugins/piratebox_plugin/conf directory.
Edit this file and replace each occurence of /sdcard/paw/html/app/plugins/piratebox_plugin with /sdcard/piraebox_ext.
Changing the Web Pages
Last step to do is to edit the files list.xhtml and pb.xhtml inside the /sdcard/piratebox_ext/html directory.
In each file there is one line that defines the upload directory.
Again, change each occurence of /sdcard/paw/html/app/plugins/piratebox_plugin to /sdcard/piraebox_ext.
That's it ... on next startup the new PirateBox location should be used.
NDEF messages are the standard way to write information to NFC tags on Android.
The latest version of PAW (0.84) has support for text, URI, smart poster and mime media NDEF messages.
The classes and their methods are described in the PAW Functions documentation within the PAW web application.
NFC support is now also available in PAW Runtime.
To show how the new functionality can be used (and to give you the possibility to play with NFC tags), a NFC reader/writer plugin is available for PAW. This plugin is also available in the newest add-on package for PAW Runtime.
Here are some screenshots...
Plugin
NFC Plugin
Plugin requesting NFC Tag
Runtime
PAW Runtime with NFC Reader/Writer
Runtime version
This will be the last update of PAW this year and possibly the last blog entry.
To all of you ... Merry Christmas and a Happy New Year :)
Since December I'm a happy owner of a Galaxy Nexus :)
NFC seemed like an interesting thing, so I started to integrate NFC support into PAW.
First thing I did was to order some Mifare Classic 1K tags from tagsfordroid.com.
They arrived fairly quickly and delivery was free of charge.
NFC Tags
To try things out I installed a lot of NFC reader and writer apps. To my dismay none of them seemed to work.
They could read the tags but could not write them. Having no idea how NFC worked, I was fairly disappointed :(
Googles sais that there will be a fix provided, but when, no one can tell.
So I tried to get it working myself...
If you would like to test the things below, install the latest PAW version (0.80) from the Android Market.
Disclaimer: This solution is only working for Mifare Classic 1K tags!
If you try as described you do it at your own risk!
It's not my fault if your tags do not work afterwards!
Read the updates at the end of the post first! This solution is no longer necessary and will most likely damage your tag(s), so do not use it!
The Problem
The problem (as reported in the bug report) seems to be that the tech reported by the tag do not contain android.nfc.tech.Ndef which is necessary to write NDEF messages.
You can try this with the following code that you can insert into the BenShell Console of the PAW web application:
If the result is TAG: Tech [android.nfc.tech.MifareClassic, android.nfc.tech.NfcA] writing NDEF messages will not work!
The Possible Fix
As mentioned above I have no expirience with NFC, so I tried to find a solution that worked without having to know NFC or the Mifare tags in detail.
I searched the web and found some Mifare Classic 1K dumps at the nfc-tools site.
After downloading a dump I tried to write it to the tag. Interesting enough it seemd to work :)
After writing the dump, the above script reported:
Update 2:
The latest NFC TagWriter by NXP is able to format unformatted tags and fixes the problem.
Here is the Android Market link: NFC TagWriter by NXP
A while ago psundegroud created the thread [TUT]Roll Your Own PirateBox! PirateBoxMobile. At that time my only rooted device was an old Samsung Galaxy I7500 running Android 1.6. We managed to get this working. The two main issues were that WiFi Tether was needed, which didn't run on all Android devices and that only Ad-Hoc mode was available. The missing Infrastructure mode prevented most Androids from seeing the PirateBox hotspot.
Note: This post is somewhat outdated. The current state of the PirateBox can be found here: PirateBox Reloaded
Meanwhile I have a rooted Notion Ink Adam running AdamComb v0.3. So I tried to get PirateBox running by using the built in tether app. Built in tethering uses Infrastructure mode, which solves above mentioned problem.
On my Adam this is really working fine and I hope that it will also run on other Android units.
I'll divide the post in two parts. The first part describes the technical details, so if someone has problems in getting this to work this might be helpful for further testing.
Along with setting up the scripts I have also written a plugin for PAW which should make setup really easy.
If you are not interested in the technical details you can right jump to the Installing the Plugin section.
Techical Details
Setting up the PirateBox during boot is done by PAW startup scripts.
The main tasks of these scripts are:
Killing dnsmasq and restarting it with changed parameters, so that DNS requests always respond with the IP of the Android device.
Configuring iptables so that requests to port 80 are redirected to the port PAW is listening on, because PAW can not operate on privileged ports.
Change the PAW configuration to use the PirateBox Handler, which ensures that all unknown request are forwarded to the base URL (piratebox.org/).
The startup scripts are located in the subfolders 0 and 1 of the directory /sdcard/paw/etc/init. These folders represent PAW runlevels. Runlevel 0 is before the server starts and after server shutdown and 1 is after server start and before the server shuts down. Scripts beginning with S_ will be called on startup and scripts starting with K_ will be run at shutdown.
So here is a short summary what these scripts are doing.
0/S_PirateBox.bsh:
Checks if tethering is running. If not none of the steps below will be performed.
Kills the "original" dnsmasq process and starts a new one.
Executes iptables commands to get port redirection working.
Replaces the original PAW configuration with the PirateBox configuration.
1/S_SpirateBox.bsh:
Checks if tethering is running. If not none of the steps below will be performed.
Restores the original PAW configuration.
Displays a PirateBox notification.
Sets the max upload limit to 200MB.
1/K_S_SpirateBox.bsh:
Clears the PirateBox notification.
Kills dnsmasq process.
Stops tetherig and restarts WiFi.
0/K_S_SpirateBox.bsh:
Removes iptables rules for port redirection.
If you run into problems have a look at these scripts and try to run the commands inside the scripts individually.
Installing the Plugin
PAW Plug-in Menu
Installing the plugin is easy. I've put it on the PAW plugin page, so you'll find it within the PAW web application or you can direct download it from the PAW Plugin Page.
After download extract the ZIP file to the /sdcard/paw/html/app/plugins directory of your Android device.
Now after re-entering the PAW web application, the PirateBox plugin should be visible in the Plugins menu.
If the plugin setup screen shows a warning in red, the installation is likely to fail, because some prerequisites are missing.
If no warnings are displayed, press the Install button. You can also try to setup a PirateBox Access Point (AP) automatically. I'm not sure, if this is working on all devices. If it's not working, please create an AP manually.
To uninstall the plugin, press the Uninstall button.
PirateBox Plugin
It is important to note, that PirateBox will only be started if tethering is active before PAW starts up.
Otherwise the normal PAW configuration will be applied. So you can choose between these two configurations.
I hope that's not just working on my Adam but on many other devices as well.
Screenshost
Here are some screenshots from my setup...
PirateBox Startup
Connected to PirateBox
PirateBox on Nexus One
PirateBox in Chromium
Video
Here is a video that shows the PirateBox in action...
Update
Since version 0.3 of the plugin, PirateBox is also working on rooted Galaxy Nexus devices running Ice Cream Sandwich.
Here is a video...
PAW is only running on ports above 1023, because restricted ports are not permitted for normal apps.
For root users there is a solution by using iptables via theSuperuser app.
I'm not sure if the below mentioned solution is working on all rooted devices.
Here is my configuration: Notion Ink Adam running AdamComb v0.3
If this works for you can easily be tested by copying the below code into the BeanShell Console of the PAW web application:
After executing the code, PAW should respond to requests on port 80.
If not, this solution seems not to be working on your configuration.
To forward port 8080 to port 80 every time PAW starts up, create a file called S_forward.bsh inside the /sdcard/paw/etc/init/0 directory.
In order to stop the forwarding when the PAW service shuts down, create an additinal file called K_forward.bsh and copy the same code.
You only have to change the line action = "ADD"; to action = "DELETE"; to stop the forwarding.