Free ericsson software for linux

Erlang is a programming language designed at the Ericsson Computer Science Laboratory.
Open-source Erlang is being released to help encourage the spread of Erlang outside Ericsson.
Installation
When installed, the entire system, except for a small start-up script, resides in a single directory tree. The location of this directory tree can be chosen arbitrarily by the installer, and it does not need to be in the users $PATH.
The only requirements are that the file system where it is placed has enough free space, and that the users who run Erlang/OTP have read access to it. In the example below, the directory tree is assumed to be located at /usr/local/erlang, which is here called the top-level directory.
It is assumed that you have the compressed tar file, the name of which is < PREFIX >.tar.gz, where < PREFIX > is a string denoting the particular Erlang/OTP release, e.g. otp_LXA_11930_sunos5_R9B.
Wherever the string < PREFIX > is used below, it should be replaced by the actual name prefix of the compressed tar file.
The tape archive file does not have one single directory in which all other files are rooted. Therefore the tape archive file must be extracted into an empty (newly created) directory.
1. If the top-level directory does not already exist, create it:
mkdir /usr/local/erlang
2. Change the current directory to the top level directory:
cd /usr/local/erlang
3. Create the installation directory with an appropriate name. For example:
mkdir otp_r7b
4. Change to the installation directory, e.g.
cd otp_r7b
5. Assuming the compressed tar file resides in the directory ,. extract the compressed tar file into the current directory:
gunzip -c / .tar.gz | tar xfp -
6. Read the README file in the installation directory for last minute updates, before proceeding.
7. Run the Install script in the installation directory, with the absolute path of the installation directory as argument,
./Install /usr/local/erlang/otp_r7b
and supply answers to the prompts.
In most cases, there is a default answer in square brackets ([]). If the default is satisfactory, just press . In general you are only prompted for one thing:
- "Do you want to use a minimal system startup instead of the SASL startup?"
In a minimal system, only the Kernel and STDLIB applications are loaded and started. If the SASL startup is used, the SASL application is included as well. Normally, the minimal system is enough.
8. Make Erlang/OTP available for users, either by putting the path /usr/local/erlang/otp_r7b/bin in users $PATH variable, or link the executable /usr/local/erlang/otp_r7b/bin/erl accordingly, e.g.:
ln -s /usr/local/erlang/otp_r7b/bin/erl /usr/local/bin/erl
Enhancements:
- Among other things, SMP support was added.

Leif is a tool for managing your Sony-Ericsson T68/T68i/T610 mobile phone. It supports phonebook editing, file uploading and SMS management.

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.

Sync4j is a mobile application server, and more. Sync4j includes a suite of tools to develop, deploy and manage any mobile project. It is a certified implementation of the Open Mobile Alliance Data Synchronization and Device Management protocols (OMA DS and DM, formerly known as SyncML).
Sync4j reached more than 19,000 downloads in a single month and it is supported by one of the largest mobile developers community in the world.
Main features:
- Sync4j Server: a mobile application server with connectors to SQL relational databases, Microsoft Exchange, Lotus Domino and SugarCRM.
- Sync4j Clients: applications for Outlook, Windows Mobile PocketPC, BlackBerry, Palm and iPod that you can use to synchronize your PIM data (address book and calendar) with the server
- Sync4j Email Gateway: a POP, IMAP and SMTP gateway, to support your mobile email needs.
- Sync4j 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
- Sync4j Device Management: an OMA DM server to remotely manage mobile devices
A wireless application needs data. The information must be available even when the device is off-line. Synchronization between multiple mobile devices and corporate servers is a fundamental component in every wireless project: data is supposed to be consistent when accessed by multiple users who are not always connected to the network.
Once a wireless application is developed, it needs to be transferred to a remote device, over-the-air. Then, it must be kept up-to-date. Application provisioning is pivotal for the success of any mobile project.
Developers of applications around the world have been looking for a platform that would make it easier to create mobile applications. IT Managers are struggling with PIM synchronization and mobile email deployments, locked by commercial vendors on a spiraling high cost structure and unable to manage a fast growing fleet of mobile devices. Sync4j is the solution they are looking for.
Open source means freedom from vendor lock-in and high quality software (thousand of eyes on the code, an enourmous community effort for testing). Sync4j is well supported by the community and the company behind it, Funambol.
Sync4j is an open source complete and unique mobile application server, addressing all the aspects of the equation:
- data synchronization, including PIM and email
- application provisioning
- device management
Sync4j is multi-device and multi-platform, running both in Windows and Linux. It runs on Tomcat and on top of J2EE application servers. It has been designed for carrier-grade deployments.
Since day one, scalability and reliability have been a clear focus of the Sync4j architecture, Sync4j is built on the Open Mobile Alliance data synchronization and device management standards (OMA DS and DM, formerly known as SyncML), thus leveraging the availability of SyncML clients pre-installed on cellular phones (such as all Symbian, Nokia, Motorola, Sony Ericsson, Siemens and others). For devices where a SyncML client is missing, Sync4j provides its own clients: Outlook, Windows Mobile PocketPC, BlackBerry, Palm and iPod.
Sync4j target market is everyone looking to build, deploy and manage a mobile project:
- Developers who need to extend an existing product to the mobile world or are looking for an easy way to create new mobile applications, grabbing data from existing data sources (such as SQL databases, Exchange, Domino or SugarCRM) or adding new data sources.
- IT Managers that want to deploy a PIM and mobile email solution or just need a way to manage a fleet of mobile devices.
- Device Manufacturers, that are looking for an OMA DM or DS client.
Download includes:
Apache Tomcat 5.0, Sync4j Admin 1.2.4, Sync4j Java GUI Client 1.0.9, PIM Web Demo 1.1.7. Runs out-of-the-box.
Enhancements:
- Major bugfixes

ATSlog is a program that is used for collecting information about calls from different PBX (Private Branch Exchange) systems.
It also parses this information and displays statistics through a flexible Web interface. The project has many features.
Enhancements:
- Support was added for the NEC NEAX7400, Ericsson BP-250, and Panasonic KX-TDA600.
- Keep-alive tuning was added for the Linux TCP/IP stack.
- CID detection in the kx1232.lib was fixed.
- 12h time format processing was added to the tda100.lib library.
- PostgreSQL fixes were made, and automatic reconnection to the SQL server is done in case of problems.
- Many atslogd fixes were done.
- An incorrect PID in the atslogmaster script was fixed.

Cobex is a small implementation of the OBEX communication protocol for slow serial cables. Its primary use is to communicate with cell phones such as the Sony Ericsson T610, T310, and T300.

Currently the project consists of a couple of headerfiles and some sourcefiles, which results in a small executable that can be used to send files to a SonyEricsson T3x0, and probably other SonyEricsson models. Fetching files is NOT implemented. In fact, its not even implemented (or at least not working) in the phone...

Its not a full-scale, foolproof, ironclad implementation of Obex. Check out OpenObex instead. They even have a v1.0!

Install the required libraries . If they are not installed in the usual places, you will have
to modify the Makefile. Come on, a configure script with all its fluff would be several
times larger than this entire project.

When ezV24 and expat are in place, do a simple "make" and the project should build.

Should you need to change the baudrate, you have to edit the files and recompile. It is
set to 115200 in cobex_serial.h baud by default.

Cobex does handle port locking using lockfiles. Unfortunately, f.ex. Fedora Core 3 does not, at least not very well. So, therefore port locking is turned of by default. You can enable it by editing the Makefile, and removing the hashmark infront of the LOCKSERIAL definition.

You can use it with following commands:
cobex_get
cobex_ls
cobex_put
cobex_rm