Free your mobile software for linux

2mobile is a kommander script that can convert your avi & mpeg files to 320x240 pixels for viewing on a pda or mobile phone.

You NEED kommander for this to work. Youll also need mplayer & mencoder to use this script.

MobileFS is a virtual file system builded on FUSE to provide access to any OBEX-compliant mobile device.
The project supports all Siemens mobile L55 series, including:
- A55
- A56
- A56i
- A60
- C55
- C56
- 2128
- CT56
- C60
- C61
- C62
- CF62
- M46
- M50
- MT50
- 3118
To install, run:
cp src/mobfs /sbin/mount.mobfs

Mobile::Wurfl is a Perl module interface to WURFL (the Wireless Universal Resource File.

SYNOPSIS

my $wurfl = Mobile::Wurfl->new(
wurfl_home => "/path/to/wurfl/home",
db_descriptor => "DBI:mysql:database=wurfl:host=localhost",
db_username => wurfl,
db_password => wurfl,
wurfl_url => q{http://wurfl.sourceforge.net/wurfl.xml}
);

my $dbh = DBI->connect( $db_descriptor, $db_username, $db_password );
my $wurfl = Mobile::Wurfl->new( dbh => $dbh );

my $desc = $wurfl->get( db_descriptor );
$wurfl->set( wurfl_home => "/another/path" );

$wurfl->create_tables( $sql );
$wurfl->update();
$wurfl->get_wurfl();
$wurfl->rebuild_tables();

my @devices = $wurfl->devices();

for my $device ( @devices )
{
print "$device->{user_agent} : $device->{id}n";
}

my @groups = $wurfl->groups();
my @capabilities = $wurfl->capabilities();
for my $group ( @groups )
{
@capabilities = $wurfl->capabilities( $group );
}

my $ua = $wurfl->canonical_ua( "SonyEricssonK750i/R1J Browser/SEMC-Browser/4.2 Profile/MIDP-2.0 Configuration/CLDC-1.1" );
my $deviceid = $wurfl->deviceid( $ua );

my $wml_1_3 = $wurfl->lookup( $ua, "wml_1_3" );
print "$wml_1_3->{name} = $wml_1_3->{value} : in $wml_1_3->{group}n";
my $fell_back_to = wml_1_3->{deviceid};
my $width = $wurfl->lookup_value( $ua, "max_image_height", no_fall_back => 1 );
$wurfl->cleanup();

Mobile::Wurfl is a perl module that provides an interface to mobile device information represented in wurfl (http://wurfl.sourceforge.net/). The Mobile::Wurfl module works by saving this device information in a database (preferably mysql).

It offers an interface to create the relevant database tables from a SQL file containing "CREATE TABLE" statements (a sample is provided with the distribution). It also provides a method for updating the data in the database from the wurfl.xml file hosted at http://www.nusho.it/wurfl/dl.php?t=d&f=wurfl.xml.
It provides methods to query the database for lists of capabilities, and groups of capabilities. It also provides a method for generating a "canonical" user agent string (see "canonical_ua").

Finally, it provides a method for looking up values for particular capability / user agent combinations. By default, this makes use of the hierarchical "fallback" structure of wurfl to lookup capabilities fallback devices if these capabilities are not defined for the requested device.

MobileRemoteSE is a light (non-Java), serial-over-bluetooth-based remote control for Amarok.
Uses the Sony Ericsson AT command set, and supports the following Sony Ericsson phone models: K750, W800, Z520, W550, W600, W900, W810, Z530, W300, K510, K310, W700, Z525, W710, Z550, Z558, K320
Main features:
- Appears under "Entertainment" menu on the phone.
- Supports Play/Pause, Next, Prev, Stop, Volume Up/Down operations from mobile phone.
- Displays the current running track on Amarok in the phone menu title.
- Since J2ME is not used (unlike some other alternatives), the remote control can be used while running some other application on non-multitasking models.
Instructions:
1) Bind /dev/rfcomm0 to the serial-over-bluetooth channel of your mobile. Please refer to your distro docs or howtos on the internet to find out how to do this.
2) Install Device::Modem package for Perl. You can either use your distro packages for this, or install through CPAN as:
cpan -i Device::Modem
3) Install and start script from Amarok.

Funambol is open source mobile application server software that provides push email, address book and calendar (PIM) data synchronization, application provisioning, and device management for wireless devices and PCs, leveraging standard protocols. For users, this means BlackBerry-like capabilities on commodity handsets.
This project is also a software development platform for mobile applications. It provides client and server side Java APIs, and facilitates the development, deployment and management of any mobile project. Funambol is the de facto standard implementation of the Open Mobile Alliance Data Synchronization and Device Management protocols (OMA DS and DM, formerly known as SyncML).
Main features:
- Funambol Data Synchronization Server: a mobile application server providing synchronization services for wireless clients and PCs, including push email.
- Funambol Device Management: an OMA DM server to remotely manage mobile devices.
- Funambol Connectors: gateways to file systems, databases, email systems, and applications for two-way synchronization with existing data assets.
- Funambol Client Plug-ins: protocol extenders and clients for Outlook, Windows Mobile, BlackBerry, Palm and iPod so users can synchronize their email messages and PIM data (address book, calendar, tasks and notes) with the server.
- Funambol Software Development Kit: tools to develop sometimes-connected mobile applications on devices (in Java - J2SE and J2ME - and C++) and to add data sources to the server.
Enhancements:
- Major feature enhancements

Implementing Mobile Calculi provides a Java framework for distributed applications and code mobility.
IMC (Implementing Mobile Calculi) is a Java framework for implementing distributed applications possibly with code mobility.
The name is due to the fact that this framework was originally built to help implement the run-time system of a mobile calculi implementation, i.e., calculi accessing remote resources and nodes, and, possibly, exchanging code, processes, and mobile agents.
If you dont need code mobility features, you can simply ignore them and use IMC for building any distributed and network application.
Enhancements:
- SessionStarter is a base class instead of an interface (*)
- IpSessionId syntax (*)
- Primordial log capabilities
- close in NodeProcess and NodeCoordinator (*)
- autogenerated names for NodeProcess and NodeCoordinator.
- The same SessionStarter should not be used for concurrent accepts. (*)
- Udp, Tcp and LocalSessionStarter are in separate packages
- ProtocolStack.createXXX (passing the ProtocolLayer to be considered
- as the highest layer). (*)
- closeSessions(SessionId). (*)
- mark, reset, skip in UnMarshaler (*)
- ProtocolThread moved in topology (it is now a NodeProcess) (*)