Free implementation software for pda

CleverTexting French 2.0 is designed to be a useful, disruptive new Mobile Texting technology that makes predictions based on the statistical nature of a language instead of a dictionary and performs equally well across dictionary and non dictionary words. It offers single keypress typing in all languages of the world from your existing keypad and phone. It is also comfortable to your thumb while you type.

CleverTexting makes predictions on what characters you are most likely to type next based upon what you have just typed before and armed with the probabilistic statistical tables of what is actually found in the language. This experimental model is providing excellent results for every language. The predictions are shown on the screen and you use the numeric keypad to make the choices, always with a single keystroke. No multitap, no mode change, no disambiguation. That user interface , with no characters fixed to the face of the numeric keypad and dynamic allocation of characters to the keys is also new.

Same software also supports Touch Screen Mobile Phone in which case you choose from the screen directly. It is a pleasure typing with it because the predictions it makes are always on the mark to aid you type and yet you have complete control on what you wish to enter. Prototype Java application can be used to compose and send messages. We also offer on phone SMS compression (as an option before transmission) so you can pack in more text into the same SMS.

Major Features:

1. Ergonomic: The most likely next characters are arranged to positions easiest for the thumb, as in Right hand and left.
2. Ergonomic and Persistent: Alphabets retain their positions between two state transitions. This reduces jitter and improves search ability of characters.
3. Legacy Keypad: Heavy users of legacy keypad habitually look for keys there. In this implementation, alphabets are assigned legacy positions as best as possible.
4. Legacy Colour: An extension of legacy, alphabets that could not be assigned legacy positions are shown highlighted to improve search ability.
5. Nearest Key: The next likely keys crowd around the last used key.
6. SMS Compression: The composed message is compressed before transmission. So you can pack in more text into the same SMS.

Requirements: Nokia Java phone

CleverTexting Swahili 2.0 is a new Texting Technology for Mobile that predicts letters as you type. It offers single keypress typing in all languages of the world from your existing keypad and phone. It is also comfortable to your thumb while you type. CleverTexting makes predictions on what characters you are most likely to type next based upon what you have just typed before and armed with the probabilistic statistical tables of what is actually found in the language. This experimental model is providing excellent results for every language.

The predictions are shown on the screen and you use the numeric keypad to make the choices, always with a single keystroke. No multitap, no mode change, no disambiguation. That user interface, with no characters fixed to the face of the numeric keypad and dynamic allocation of characters to the keys is also new. Same software also supports Touch Screen Mobile Phone in which case you choose from the screen directly. It is a pleasure typing with it because the predictions it makes are always on the mark to aid you type and yet you have complete control on what you wish to enter. Prototype Java application can be used to compose and send messages. We also offer on phone SMS compression (as an option before transmission) so you can pack in more text into the same SMS.

Major Features:

1. Ergonomic: The most likely next characters are arranged to positions easiest for the thumb, as in Right hand and left.
2. Ergonomic and Persistent: Alphabets retain their positions between two state transitions. This reduces jitter and improves searchability of characters.
3. Legacy Keypad: Heavy users of legacy keypad habitually look for keys there. In this implementation, alphabets are assigned legacy positions as best as possible.
4. Legacy Colour: An extension of legacy, alphabets that could not be assigned legacy positions are shown highlighted to improve searchability.
5. Nearest Key: The next likely keys crowd around the last used key.
6. SMS Compression: The composed message is compressed before transmission. So you can pack in more text into the same SMS.

MoMEUnit is an instance of the xUnit architecture for unit testing of J2ME applications. It is derived from well known JUnit framework. It is only CLDC 1.1 complied.

This framework overcomes lack of reflection API in J2ME MIDP API and supports such main features of JUnit framework as:

- Ease of development and run of tests.
- Sharing the same fixture among different tests.
- Running test in its own fresh fixture.
- Modification of fixture for a group of tests.
- Possibility of simultaneous tests runs.
- Independence of tests runners (different tests runners can be used with framework package).

This framework includes an optional Ant Integration package. This package consists of several fully featured, extensible tasks that simplify use of MoMEUnit framework with Ant build system.


MoMEUnit Ant Integration package offers following functionality:

- Calculates list of tests to run based on Test interface implementation and specified patterns. There is no need to specify test cases to run explicitly. Developers can add test cases without configuring test runners.
- Runs test cases of already built J2ME application or builds test application on behalf of developer based on source files, classes, resources and libraries specified.
- Preverifies J2ME application before running tests on demand.
- Formats tests run output by using predefined or custom tests results formatters like in task. All test characteristics including times and stack traces are available.
- Gives developers possibility to choose emulator and/or preverify tool to run by specifying predefined or custom emulator or preverifier.
- Gives developers possibility to configure test J2ME application by specifying attributes of application JAD descriptor and/or manifest.

This framework provides as an extension a MIDletTestRunner - a fully configurable MIDlet. It is intended to run tests in emulator or mobile device. It shows the results of tests run (progress bar, statistics, lists of failures or errors with detailed messages for each test) in one screen. The tests can be run automatically during start-up and re executed more times later. It can print descriptive messages of failures and errors thrown together with stack-trace to the standard error output

MobileMule is a small subproject of eMule, which lets you control your eMule with any java-enabled mobile phone (actually not any, but most). Note that MobileMule is NOT a eMule for your mobile phone, but a remote control for your eMule.
Which mobile phones are supported?
Basically all java enabled mobile phones which have 40 KB free fixed memory and about 150-200KB Heap. A color display is strongly recommended (many older phone types - especially from Nokia - with non color display do not have enough free Heap anyway. Also you need to be able to access the Internet via HTTP. All java-enabled mobile phones should supported this, however it is possible that your contract doesnt allows internet access (prepaid) or that your carrier offers only restricted access. Anyway, the best way to find out is to try it.
Anything else needed?
Yes, your port 80 must be open reachable for incoming connections. So if you have a router or firewall you have to open this port.
Installation
1. Before Installing MobileMule
Before you beginn to install MobileMule make sure you meet all Requirements:
- You have a Java-enabled mobile phone (which is not on the "blacklist")
- You can access the Internet (WAP Gateway or direct Web access)
- Port 80 on your Box is reachable for incomming connection
2. Downloading
Ok, now that you know you could theoretically use MobileMule, it is worth a try to install it ;) Go to the download site and get the most current eMule version. This version is based on the latest official Release, but makes also sure that the MobileMule implementation is the most current one. It is possible that the last eMule release has already the most current MobileMule protocol, in this case you will find a notice about it on the download site. Unpack the Zip-File and replace the your old Exe-File with the new one you just downloaded.
There are two possibilities to download MobileMule: WAP/OTA direct into your mobile phone or saving it on your PC and then transfer it to your handy with a datalink cable. If you have a datalink cable, the second method is recommended, because your Operator will probably charge you for OTA transfer, while the second method doesnt cause any costs. A guide to install MobileMule via WAP can be found on the download site. IF you dont know how to use your datacable, check your phone manual - it is impossible to explain this for all mobile phone types here.
3. Setup
MobileMule needs no further setup. However make sure that your phone settings (WAP, Security) are ok, so that MobileMule can access the internet. In most cases you wont have to change anything.
In eMule you have to activate the MobileMule server. Open the preferences -> Webinterface and click on "MobileMule enabled". Now enter a password, which you will need later to log in. If you use the webserver, make sure it is not assigned to Port 80, or the MobileMule server will not work.
Now you have MobileMule installed, read the rest of the guide to learn more about using MobileMule.
Preferences
You can reach the preferences form the loginscreen. Here is a description of all available options:
Port
With this option you can change the port which MobileMule uses to connect to eMule. You have to choose the same port in the preferences of eMule. Note: Some WAP Gateways do not allow to connections on ports other than 80. If you do not use a WAP gatway there should be no problem with choosing other ports.
Login Method
Here you can select which address format MobileMule should use to find your eMule. If you choose Client ID you have to enter the (high) ID which was assigned to your eMule when it connected to a server, for example "16777343". DynIP or IP lets you choose between your real IP of your PC (for example "212.101.30.14") or the address of a dynamic DNS, which allows you to connect to your eMule even if it changed its IP and you do not know the new IP(only if you installed a dynamic ip programm, please look into the manuals of your favourite dynamic DNS service). An example: "myMule.dyns.net"
Save Password
If you want MobileMule to save your password, enable this option. If you want more security and enter the password everytime you start MobileMule disable it.
Login
ClientID: Enter here the ID which was assigned to your eMule when it connected to a server. LowIDs will not work. Also your ID will change everytime when your IP changes. In future version there will be additional and easier options, which replace the ID (like Dynamic IPs, or an Accountname for an MobileMule account which you can create on this page).
Password: The password you selected in your eMule preferences for MobileMule.
If everthing works, you should now be able to loging, if not you will (probably) get an error message. here are some of the possible errormessages and their meaning:
Unexpected Servererror - MobileMule could not access the internet or it could not find your ID (IP). Make sure you securit settings allow MobileMule to access the internet and that your WAP/Web settings are right.
Wrong opcode received - The responding server was no MobileMule server. If you use a WAP gateway it could also mean that it could not find your ID/IP or that you operator does not allow to access the internet.
Password rejected - Well this should be quite clear :)
Wrong server version - Your eMule version is not compatible to your MobileMule version. Download the latest MobileMule and eMule files and try again
General Servererror - The server (emule) reported an error for some reason. Maybe there is a problem with your WAP Gateway which corrupted the message, but it could have many reasons
Important:
If you have any problems logging in, first try to use the option "Connection test". MobileMule will then try to connect to a server, which is for sure available and will response. If this test succeeds, but you cannot log into your eMule then the problem is located somewhere on your PC. Recheck if you started the MobileMule Server in eMule, if there was no Errormessage in the log and if you have set it to the default port, if you have used the correct ID or IP and if you firewall or router allows/forwards incoming connections on this port.
Status Overview
You can find some basic information about what your eMule does right now here. Everything should be selfexplaining (ok that sounds strange for a HowTo ;) ).
Downloads
On this screen you will see all current downloads and their status. Two red rectangles means this file is paused, a green circle indicates that this file has the waiting state while a filled green circle is a file which is currently receiving data.
You have 4 options here: Cancel, Delete and Pause/Resume should be clear. However be warned: currently there MobileMule will not ask you to confirm your selection if you choose to delete a file. The detail option leads you to the detail screen.
Preview
MobileMule can preview all movie files, which your eMule is currently loading or finished in its current session. Go into the "Finished Files" or "Downloads" screen and select Preview. eMule will try to grab the first frame from the selected movie, resize it to your mobile phones display size and send it.
The preview works with most codecs and video types, but there are some exception were eMule is not able to get a frame. In this case you will see an error message or a complete black image. Also you will only be able to use the preview if your phone has a color display and enough memory to recieve and draw the picture.
Also please keep in mind that the picture has a size of about 5-10KB (depending on the size of your display). This means that it will take a moment until the picture is loaded and it also means that if your operator charges you for transferred volume you should use this option careful.
File Details
This screen contains all information about a file, which you could also find in the eMule download window.
Search
Type the keyword you want to search for into the field (in the prior screen), select a file type and then click start. MobileMule will show you up the 15 results which have the most sources available. The number on the right will you you how many sources this file has. However it has max. 2 digits, meaning if there are more than 99 sources it will show 99.
You have two options here: Detail will show you more details about the selected file like the full name, filesize and how many sources it has and Download will tell eMule to download this file.
Commands
There are currently two commands available here. You can shut down your PC (and turn off power) or shut down eMule. Of course shutting down your PC will result in shutting down eMule too. Another note: Do not expect to be able to connect to your eMule after you used one of those commands ;)
System requirements:
- Java-enabled mobile phone
- Internet connection (WAP Gateway or direct Web access)
- port 80 must be open reachable for incoming connections

A useful educational tool is presented for minimizing low order Boolean expressions.
The algorithm follows the Karnaugh map looping approach and provides optimal results.
For the implementation, C++ was used on the CodeWarrior for Palm Operating System environment.
In order to make the overall implementation efficient, the object oriented approach was used.
The proposed application can be used by students and professors in the fields of electrical and computer engineering and computer science.

Modelled after the implementation of Snake on some Nokia phones. Slither around the board eating the little bits of food. Each bit gives you three points, and makes your tail grow. See how long your tail can get without bumping into anything.
System requirements:
- Palm OS 1.0, 7KB space.

OpenDMTP (Open Device Monitoring and Tracking Protocol) is a highly configurable and extensible protocol for communicating with mobile devices over high-latency/low-bandwidth networks. The protocol is particularly geared towards the transmission of GPS base location information and includes a full-featured reference implementation showcasing its capabilities.
There are many mobile GPS tracking devices on the market today with their own closed proprietary protocols. Searching the web for open protocols revealed only a few available for transferring data (including GPS information) between devices. However these solutions are generally designed for non-mobile applications and/or lack some of the low-bandwidth, configurable, and extensible features that mobile applications require.
Having an open protocol designed specifically for mobile devices has many advantages:
Targeted Event Generation: Many devices on the market are designed simply to transmit copious amount of GPS data to a back-end server hoping that the server can make sense of the data that it is receiving. The problem with this approch is that it tends to result in higher data transmission costs for information which will never be used. A protocol used for mobile applications need to be able to provide the flexibility to generate only the events that are pertinent to the specific application.
Network Efficient: Mobile devices typically have limited network connectivity, and in some cases data communication can be quite expensive (e.g. satellite). Because of this the protocol needs to be efficient in its dialog between the client and server. The communication needs to be optimized such that the necessary information can be conveyed with a minimum number of bytes in the least amount of time.
Transport Media: Differrent mobile applications will have their own unique way of communicating data back to the server. Some may use GPRS, or socket based communication, others may use satellite communication, while still others may use other forms of wireless communication, such as BlueTooth. The design of the protocol should be able to encompass all such transport media types, regardless of the type of transport in use.
Bi-directional: Some devices can support two-way communication (ie. GPRS, or other socket based connections), while others may only support one-way communication (ie. some satellite communication systems). With this in mind, a protocol should be designed to support both duplex (two-way) and simplex (one-way) communication.
Flexible Data Encoding: Most types of transport media allow for the transmission of binary encoded data. However, there may be some forms of media for which an ASCII encoded data packet is much better suited. A protocol designed with this in mind should be able to support both types of data encoding.
Configurable Messages: Due to the broad range of data types used in mobile applications, the protocol should be flexible enough to define standard messages, yet still allow custom messages within the framework.
Extensible: Not every mobile application is the same. Some require special handling and may have various types of inputs and outputs. A protocol designed for mobile applications should insure that the framework can be easily extended to incapsulate the specific needs of the device.
Small Footprint: Mobile devices typically have limited resources on which to run client code (ie. memory, processor speed). An open protocol designed with this in mind should be optimized to allow efficient implementation and should easily support devices such as PDAs, mobile phones, GPS monitoring devices, and other OEM micro-devices.
Industry Compatibility: Having an open protocol insures better compatibility between different client devices and service providers.
Reference Implementation: Having a reference implementation that showcases the major features of the protocol provides an easy starting point on which developers can add their own features and platform specific implementation without having to worry about how data gets from the client to the server.
OpenDMTP was specifically designed to suit all these needs, especially "Targeted Event Generation" and "Network Efficiency". The typical data plan for GPRS communication, for instance, is usually 1Mb per month. OpenDMTP was designed to optimize packet encoding to allow the collection of GPS information packets once every 3 minutes, 24 hours a day, 30 days a month, and still stay under the 1Mb data plan limit.
While XML is very extensible, it fails the "Small Footprint" and "Network Efficiency" requirements. Thus, it was discounted as a viable protocol solution. Many mobile devices do not have the resources necessary to be able to provide full XML parsing functionality. And an XML packet may need to be several hundred bytes in length just to send a few bytes of actual data. This alone would make the solution cost prohibitive for high-cost transport media such as satellite.
OpenDMTP also includes a full-featured commercial quality reference implementation to jump-start development.
System requirements:
- J2ME supported devices