Free qos packet scheduler software for pda

Utility to schedule your text messages to anyone. Let your birthday greetings and other SMS messages be sent even while you sleep
System requirements:
- Smartphone 2002

Auto-launch of different tasks on your smartphone is very useful feature. It allows automating your repetitive and routine tasks in the most natural way. Unfortunately, standard Windows Mobile OS does not have such functionality.
CT Scheduler adds a new functionality of automatic launching programs, documents, media and other files in accordance to your time plan. Tasks can be scheduled to launch based on definite time, dates and days of the week. It is very convenient, because the workday schedule and weekend and holiday schedule can differ. The program has an ability to activate and deactivate scheduled items. There is no need to delete and create them again.
Below are some examples of CT Scheduler usage:
Sound Alert. Select desired audio-file to run in Program / File field and then set the necessary time parameters. You can also select any specific media-player in Program / File field and desired audio-file in Parameters field.
Switching Profiles. Select /Windows/autoprof.exe in the Program / File field. Then enter -s ProfileName in the Parameters field. ProfileName must be English name of the desired profile, for example Meeting.
Downloading web-page. Select /Windows/iexplore.exe in the Program / File field. Then enter the desired URL in the Parameters field.
Enhancements:
- New time engine and small interface changes were implemented.
System requirements:
- Windows Mobile 5 for Smartphones

Utility to schedule your text messages to anyone. Let your birthday greetings and other SMS messages be sent even while you sleep.
Main features:
- Unlimited number of scheduled SMS
- Unlimited recipients (individual contacts and groups)
- Send to Group facility (scheduled or outright)
- Program doesn\t run in the background
- Schedule resumes even when screen is OFF or after doing a soft reset
- Notification for each sent scheduled text message
- Supports landscape screen orientation
- Best of all it\s FREE!!!

Lastest Caltrain scheduler, small, easy to use. It allows you to update the schedule if it changes in the future.
System requirements:
- MIDP 2.0

Call Manager for Windows Mobile 5 and later.
Main features:
- XML configuration
- Call blocking or call answering, can be set to master mode (kill cprog.exe!)
- Profiles
- Scheduler
- Multiple lines
- Cell id profile
System requirements:
- Windows Mobile 5 or later

Truly, collect data with GrandaSoft XSForms is as easy as 1-2-3.
Forms are created with GrandaSoft XSDesigner. Then these forms are transmitted to XSForms on your Pocket PC. Once the form is on your Pocket PC you can enter data with your fingers, a stylus, or even a barcode scanner. The captured data then can be manipulated any way you like: sort it, filter it, send it via PocketOutlook as email, or upload it to any HTTP or FTP-server in the world in XML, HTML or CSV format via WLAN (IEEE 802.11 standards), Cradle, GPRS (General Packet Radio Service), or Bluetooth, depending on the capabilities of the Pocket PC.
It really is amazing how a Pocket PC can actually be put to work, with XSForms. Try it out!
System requirements:
- Requires PocketPC 2002, WM2003/SE or WM5.0 and 2 MB of Available RAM

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