J2ME devices are inherently lightweight computing devices not meant to provide the same level of functionality as traditional desktop or server computing devices. Thus, we must examine how to measure performance on a J2ME device. With less emphasis on heavy computation and complexity, J2ME devices instead emphasize simplification of user tasks. Given the typically small screen size and constrained data input mechanisms, the user interface and the computations associated with a good user experience are paramount in any J2ME application. In this article, we approach performance measurement by examining J2ME devices' performance from a user functionality perspective.
Rather than compare what processor and operating system a particular device runs, the tests focus on determining whether a good user experience results when accessing a particular function. In the future, we will update our benchmark if real devices support higher J2ME versions. As of May 15, , more than 70 types of J2ME-enabled mobile devices were available in the market. The number is increasing dramatically. See Resources for a list of devices that support J2ME. We use the following devices in our benchmark; here we classify the devices based on their functions not performance :.
Because different devices have different hardware settings, operating systems, and Java platform implementations, we provide a general benchmark standard and related applications to test the performance of various J2ME devices, and compare the performance fairly. We define the benchmark according to two different levels: kernel level and application level.
- GPRS - Mobile Phones - Tutorialspoint.
- GPRS - Mobile Phones.
- history of dui laws in virginia?
We only benchmark general J2ME platform performance. We do not benchmark an individual application's performance nor do we locate an application's bottleneck to optimize it. But application developers may glean from our benchmark tests which parts of J2ME applications consume more processor time and heap size as compared to others. These benchmarks should show developers which J2ME-enabled devices perform better in certain areas.
Many companies define benchmarking strategies for Java platforms some are free, some are not.
Mocha RSS for Nokia 3310 3G + Java enabled phones
Most benchmarks test desktop and server-side environments. Some provide powerful tools, with, for example, support for thread monitoring.
- georgia department of correction sex offender!
- can u find a song called bombs of bagdad.
- summary of sex offender law 1000 feet school.
- yellowbook vs the real yellow pages.
- Mocha Radio for Nokia 3G and other Java phones?
- The Best Mobile Applications for Twitter.
- how to find stolen car!
For our standard, we follow the common procedures for performing benchmarks and use typical test areas. In the kernel-level test, we pick up some of the common test areas for J2SE Java 2 Platform, Standard Edition benchmarks and add our own.
In each test area, we execute a test-specific code in a loop. We receive the speed loops per second as the result. We built an application named JKernelMark version 1. In the application-level test, we define some test areas first. In each test area, we execute a test-specific code in a method. The speed milliseconds per execution is the result we receive. For each benchmark, a MIDlet suite application performs the benchmark in the real device. The following sections explain what we test in each benchmark application. Since a normal XML parser is too heavy for mobile devices, performance—which includes runtime performance, user perception, and deployment code size—proves important when parsing XML in J2ME.
Snaptu just announced that it has raised funding from Sequoia Capital , a VC that funded Google, Yahoo, YouTube, and a few other companies you might have heard of. UberTwitter is a popular Twitter client for BlackBerry devices. One nice option lets you reduce the size of profile icons, enabling users to fit more text on the screen. The app supports multiple accounts, allowing each account to have unique on-device settings. Gravity is a fully featured and smooth looking Twitter client for Nokia S60 smartphones. Gravity supports multiple Twitter accounts, offers tabbed views of your timeline, messages, friends, etc.
You can also post URLs from tweets to del. TinyTwitter is another popular Twitter app. Like Snaptu, it supports Java enabled devices, meaning it is not just focused on the mobile bourgeoisie that own an iPhone. Connected Device Configuration. Maintenance Latest Stage:. This specification will define a profile that will extend and enhance the "J2ME TM Connected, Limited Device Configuration" JSR , enabling application development for mobile information appliances and voice communication devices.
The Foundation Profile is a set of APIs meant for applications running on small devices that have some type of network connection.autisminrussia.org/scripts
Top 5 Twitter Apps for your Mobile Phone
Distributed Real-Time Specification. Dormant Reason:. Personal Profile Specification. Withdrawn Reason:.
The Best Twitter Apps for your Mobile Phone
Its original purpose to define the architecture for Java ME and additional processes for building blocks are not necessary. The Community Review draft contains useful working definitions of Configurations and Profiles and useful rules for subsetting and merging APIs. It allows Java applications to discover, read, write, and manage USB devices.
Bluetooth is an important emerging standard for wireless integration of small devices. The specification standardizes a set of Java APIs to allow Java-enabled devices to integrate into a Bluetooth environment. Download page. This JSR extends the work of the 1. Mobile Information Device Profile 2. This defines a set of optional APIs which provides standard access to wireless communication resources, designed to run on J2ME configurations and to enhance J2ME profiles with unique functionality. Personal Basis Profile Specification. Java TM Game Profile. Defines a Java 2 Micro Edition Profile for the purposes of game development targeting high-end consumer game devices and desktops.
It was determined that the needs of games developers were best served by moving to a pure open source model for game client technologies. This changes in strategy will allow the broadest participation by the game development community, and will focus the energies of the community on timely solutions that address a rapidly changing technology landscape.
The Spec Lead wishes to thank the Java Community and the Game Developers who supported and showed interest in this effort. This specifies a small-footprint multimedia API for J2ME TM , allowing simple, easy access and control of basic audio and multimedia resources while also addressing scalability and support of more sophisticated features.