Xperia™ testing submission document. Describes the information required when submitting your game for Xperia™ testing. For additional information, please see the Stand out from the crowd page.
Xperia™ child device test (Xperia™ PLAY) document. Describes the tests performed for the Xperia™ Testing Program. For additional information, please see the Stand out from the crowd page.
Xperia™ master device test document. Describes the tests performed for the Xperia™ Testing Program. For additional information, please see the Stand out from the crowd page.
Xperia™ child device test document. Describes the tests performed for the Xperia™ Testing Program. For additional information, please see the Stand out from the crowd page.
Xperia™ lead device test document. Describes the tests performed for the Xperia™ Testing Program. For additional information, please see the Stand out from the crowd page.
Sony Tablet SDK Add-on package including the Sony Tablet SDK Add-on, Get started guide, IR device keycodes, and LargeScreenLibrary API references. To be used together with the Android SDK.
This document describes WAP User Agent strings and profiles (UAProf) for Sony Ericsson mobile phones. The UAProf is an Open Mobile Alliance (OMA) specification that allows a WAP browser in the phone to deliver device profile information to a serving web server. The profile information includes hardware characteristics, user agent information, the network capabilities of [...]
This document describes how to develop web pages for Sony Ericsson phones which use the Netfront Browser (most phones 2006 onwards – full list in the document).
The Developers Guideline for MMS is designed to give the reader a deeper insight of how to design applications for Multimedia Messaging Service MMS). The Multimedia Messaging Service standard uses specifications from the 3rd Generation Partnership Project (3GPP) and Open Mobile Alliance (OMA), to specify how rich media content can be transmitted mobile-to-mobile or network-to-mobile.
This document describes how to implement themes for Sony Ericsson mobile phones. The document is intended for content providers who want guidelines to optimally create themes and the elements required to create an appealing theme.
This document describes the implementation of OMA Client Provisioning and Device Management functionalities in Sony Ericsson phones with Device Management Client version 5.0 or higher.
The Developers Guideline for AT commands is designed to give the reader a deeper insight into how to design applications with AT commands supported by mobile phones. This document is for advanced users who require detailed information in order to (1) Develop new communications software; (2) Add the mobile phone to a list of compatible [...]
This document describes the RSS (Really Simple Syndication) implementation in Sony Ericsson phones. The document is intended for developers of RSS content and service providers who want insight into RSS features in Sony Ericsson phones.
These Developers Guidelines describe the Microsoft® Exchange ActiveSync® implementation in Sony Ericsson phones and the communication methods and protocols used when synchronising email, calendar and contact items in the phone with a Microsoft Exchange server. The document is primarily intended for corporate IT personnel working with Microsoft Exchange server maintenance and operation.
This guideline provides essential low-level implementation details for recent Sony Ericsson MIDP 2.0 phones. It also includes information on integrating the SDK with a UEI compliant IDE, how to perform On Device Debugging and Mobile JUnit usage
This document covers the media parts of the Sony Ericsson mobile phones enabling media producers to get a quick overview of the media functionality of Sony Ericsson products, with emphasis on video.
This document is designed to give the reader an understanding of how high-quality, polyphonic sound is supported in Sony Ericsson phones. To support polyphonic sound, a synthesiser is built into the phone. The polyphony of a sound generator refers to its ability to play more than one note at a time. In Sony Ericsson phones, [...]
Poor resource management in Android apps can significantly affect power consumption. Our development team has gathered some basic coding guidelines to help you improve power management.
This document describes the Java™ ME platform support for Sony Ericsson Java platformThis document describes the Java™ ME platform support for Sony Ericsson Java platform JPWM_SEMC-2.0.
The UI Rulebook presents useful User Interface design style information for Sony Ericsson phones supporting Java Platform 8 and onwards. The purpose of the UI Rulebook is to provide you with practical help for designing the UI of attractive mobile applications.
This document is a collection of UI components that can be used for the design of applications for Sony Ericsson phones. The document covers the Flash Lite UI components provided by Sony Ericsson Developer World. The catalog gives information on which components should be used in which situations, and how they can be customized.
This document describes how to create basic themes for the Quadrapop game using Adobe® Flash®. Written by Graham Blake, Lead Designer at BlueskyNorth Limited. Quadrapop Mobile Game – Basic Theme Creation Tutorial
Quadrapop is a falling icon based puzzle game that is pre‐loaded onto much of Sony Ericsson’s handset product range. This Tutorial details the steps needed to take the Flash FLA files included and use them as the basis for the creation of an original theme.
Sony Ericsson’s Flash Lite User Interface components are packed in one MXP file for Adobe® Flash CS3 and CS4. They are light, robust, and customizable.
An Xperia™ X2 EXE Panelizer is a pre-built DLL (SonyEricssonPanel.dll) and CAB packager to create a Panel installation package for a native executable application installed on the phone. No C/C++ programming knowledge is required to create an EXE native Panel. This tutorial shows how it is done.
The Xperia™ X2 .NET Panelizer is a pre-built DLL (SonyEricssonPanel.dll) and CAB packager to create Installation package used to create a Panel from native executable applications installed on the phone. No C/C++ programming knowledge is required to create a .NET framework Panel. This tutorial shows how it is done.
Featuring the Sony Ericsson Bluetooth Remote Control Tool, this document describes how to create and maintain Bluetooth™ Human Interface Device (HID) configuration files for Sony Ericsson mobile phones. The document is intended for content providers who want guidelines for the optimal creation of HID configuration files and the elements required for an appealing remote control [...]
This document describes the solution for dynamic presentation of streamed mobile TV content integrated into the Media application, and the complete setup of the server solution needed to deliver streaming video to the application. Note: The mobile TV solution presented here is a customisation offering and is not generally available in Sony Ericsson phone models [...]
Project Capuchin is a Java API defining a bridge between Java ME and Adobe Flash Lite technologies. This API makes it possible to use Flash Lite as the front end and Java ME as the back end of applications. This document provides an overview of Project Capuchin.
This document describes how to handle signing of native Symbian™ OS v9 applications for Sony Ericsson phones. The document is intended for developers of UIQ™ 3 C++ applications who want insight in the implications of Symbian Platform Security (PlatSec) on the deployment and installation of applications in these phones.
The OMA client provisioning and device management functionalities found in Sony Ericsson phones supporting device management v3. Please refer to the accompanying links for relevant device description frameworks (DDF).
Flash Lite first appeared in 2003, and was at that time aimed at the Japanese NTT DoCoMo i-mode™ services. Flash Lite 1.1 followed in 2004, and contained a number of major improvements. Both Flash Lite 1.0 and 1.1 are based on a Flash 4 structure, helping to minimize the footprint and processor demands of the [...]
This document introduces the broader concepts of digital multimedia and networking, along with specific information on formatting and providing media with network-based delivery to Sony Ericsson phones. The tutorial has been authored by Ian Simpson, a magazine journalist and freelance technology writer based in the U.K.
This guideline provides an introduction to i-mode and DoJa development, the contrast to MIDP 2.0 packages, camera support in conjunction to the K610im and IDE integration.
This document describes how to develop Web pages for the browser in the following Sony Ericsson mobile phones: T68, T300/T310, T610, T630, Z600, Z1010, K700, S700, K500, Z500, V800, K300, J300, K750, W800, Z800, K600, V600, Z520, W700 and Z525 series.
The Developers Guideline for MMS is designed to give the reader a deeper insight of how to design applications for Multimedia Messaging Service MMS). The Multimedia Messaging Service standard uses specifications from the 3rd Generation Partnership Project (3GPP) and Open Mobile Alliance (OMA), to specify how rich media content can be transmitted mobile-to-mobile or network-to-mobile.
This document is intended for developers of WAP services who want a deeper insight into designing applications for Sony Ericsson WAP browsers. It is assumed that the reader is familiar with the WAP concept and WML.
This tutorial covers the KDWP technology behind on-device debugging and presents its usage together with the NetBeans 5.0 IDE, Mobility Pack 5.0 and a Sony Ericsson feature phone. It also includes frequently requested serial over Bluetooth setup information allowing debugging without drivers.
This Special Interest paper introduces you to Mobile JUnit, a unit testing framework for the Java™ ME Platform, including smartphones and messaging devices from Sony Ericsson. It includes examples for integration with Eclipse and NetBeans together with Ant driven usage. No prior experience with unit testing is necessary, but an understanding of Java ME development [...]
Getting Started with Web Services, JSR 172 leads Java ME Platform developers through creating a simple hardcoded service example and a MIDlet that uses JSR 172 to interact with that service.
This document is intended to give the reader a basic understanding of how DRM is designed and how it is used to protect media. This includes the Sony Ericsson DRM Packager application and associated technology. It is written for developers that are going to protect media objects residing on their Web server using the OMA [...]
The Developers Guidelines for EMS is designed to give the reader a deeper insight of how to design applications for Enhanced Messaging Service (EMS). Initiated by Ericsson, EMS is now incorporated by the 3rd Generation Partnership Project (3GPP) into the Short Messaging Service (SMS) standard. The SMS standard is supported by the major network operators [...]
The Sony Ericsson Multimedia Messaging Service white paper is designed to give the reader an understanding of how MMS works in Sony Ericsson mobile phones. The white paper also aims at providing the reader with an end-to-end understanding of how MMS applications are provisioned.
A code sample for Symbian OS (C++) showing how to creat a “floating” control / dialog over the top of the foreground application, to indicate a change or prompt the user for some sort of action.
In J2ME MIDlets, two types of properties are available. One set describes the system, allowing the application to gather information about the current platform. For more information on which system properties can be expected, and their default values, read the Sun MIDP 1.0 specification available on http://java.sun.com.
To guarantee compatibility between the MIDP emulators and phones, it is best to use the getGameAction() and compare the result to Canvas.UP, Canvas.DOWN, Canvas.RIGHT, Canvas.LEFT and Canvas.FIRE instead of using the keycodes directly. Make sure to use a Try/Catch around the getGameAction() and getKeyName() functions. This is because the T610 family of phones (T610/T616/T618, T630/T628) [...]
We have in previous newsletters provided a few of Tips & Tricks related to Record Store in Java MIDlets (see Understanding Record Management System in J2ME, Recordstore Size Information for the T610 and Efficient RMS data management in J2ME applications). This MIDlet example demonstrates how to actually create a record store and add and delete [...]
The iMelody format is a minimal set of tones that can be used to transfer melodies between devices. The definition can be extended by defining new formats for MIDI/WAV, DTMF, polyphonic etc.
The T600 white paper is designed to give the reader a deep technical understanding of how the Z600 is designed, and of how it interacts with other media.
The Z200 white paper is designed to give the reader a deep technical understanding of how the Z200 is designed, and of how it interacts with other media. This paper also applies to the Z208 .
The P900 / P908 white paper is designed to give the reader a deep technical understanding of how the P900 / P908 is designed, and of how it interacts with other media.
The Z600 white paper is designed to give the reader a deep technical understanding of how the Z600 is designed, and of how it interacts with other media.
The T630 white paper is designed to give the reader a deep technical understanding of how the T630 is designed, and of how it interacts with other media. This paper also applies to the T628 device.
Over The Air (OTA) Settings Specifications (6.0, 6.5, 7.0 and 7.1) describing how to provide mobile phones with browser and SyncML settings over the air.
The T600 / T602 white paper is designed to give the reader a deep technical understanding of how the T600 / T602 is designed, and of how it interacts with other media.
The T226 white paper is designed to give the reader a deep technical understanding of how the T226 is designed, and of how it interacts with other media.
The T300 / T302 / T306 white paper is designed to give the reader a deep technical understanding of how the T300 / T302 / T306 is designed, and of how it interacts with other media.
The T105 white paper is designed to give the reader a deep technical understanding of how the T105 is designed, and of how it interacts with other media.
The T220 / T202 white paper is designed to give the reader a deep technical understanding of how the T200 / T202 is designed, and of how it interacts with other media.
The T230 / T238 white paper is designed to give the reader a deep technical understanding of how the T230 / T238 is designed, and of how it interacts with other media.
The T100 / T102 / T106 white paper is designed to give the reader a deep technical understanding of how the T100 / T102 / T106 is designed, and of how it interacts with other media.
The T310 / T312 / T316 white paper is designed to give the reader a deep technical understanding of how the T310 / T312 /T316 is designed, and of how it interacts with other media.
The T68i / T68ie white paper is designed to give the reader a deep technical understanding of how the T68i / T68ie is designed, and of how it interacts with other media.
The Sony Ericsson Java™ white paper is designed to give the reader an understanding of how Java works in Sony Ericsson mobile phones. The white paper also aims to provide the reader with an end-to-end understanding of how Java applications are provisioned.
This paper discusses the T610/T616/T618 and Z600 phones and how to adapt your existing MIDlets to them, with special focus on adapting existing Nokia Series 40 MIDlets.
This paper discusses the T610/T616/T618 and Z600 phones and how to adapt your existing MIDlets to them, with special focus on adapting existing Nokia Series 40 MIDlets.
The MMS Conformance Specifications documents were jointly developed by the leading industry players and outline the minimum set of interoperability requirements for the management of MMS content.
The EMS white paper is designed to give the reader an overview and a deeper understanding of Enhanced Messaging Service (EMS). Initiated by Ericsson, EMS is now incorporated by the 3rd Generation Partnership Project (3GPP) into the Short Messaging Service (SMS) standard. The SMS standard is supported by the major network operators and mobile phone [...]
