Bug Nokia: TimeZone.getTimeZone() returns invalid value for GMT whenusing daylight saving time (summer time)

A bug related to the use of the class Timezone using the Daylight saving time.

Click here to see

Open a connection with the new Android SDK 0.9

It took sometime to me to understand why my connection class wasn't working anymore after the update to the new Android SDK 0.9.

Trying to open a simple socket I got the error "UknownHostException" even if my code wasn't changed.

The solution has been add to the AndroidManifest.xml this line:

<uses-permission xmlns:android="http://schemas.android.com/apk/res/android" android:name="android.permission.INTERNET"></uses-permission>

Magically the problem disappears.

LG KE970 Shine bug using MediaPlayer and setVolume

If you want to set the volume in the MediaPlayer using the following code:



                InputStream is = getClass().getResourceAsStream( "/sound.amr" );

                Player player = Manager.createPlayer(is, soundType);

                player.addPlayerListener( this );

                player.realize();

                VolumeControl volumeControl =

                (VolumeControl) player .getControl( "VolumeControl" );

                if ( volumeControl != null ) {

                    volumeControl.setLevel( volume );

                }



when you launch the player with:



                player.start();



no sound can be heard on the LG KE970 Shine without getting any error.



This device requires to get the prefetched status if you want to set the volume and play the sound correctly. The working code is then:





                InputStream is = getClass().getResourceAsStream( "/sound.amr" );

                Player player = Manager.createPlayer(is, soundType);

                player.addPlayerListener( this );

                player.realize();

                player.prefetch( );

                VolumeControl volumeControl =

                (VolumeControl) player .getControl( "VolumeControl" );

                if ( volumeControl != null ) {

                    volumeControl.setLevel( volume );

                }



Maybe other phones are affected as well (especially LG). Post comment if you other phones with the same problem.

Nokia Serie60 and 40 bug: softkey codes are not reported on a normal Canvas

This bug is reported by forum.nokia.com in their "Knowledge Base" section.

Some key codes are not reported through the keyPressed(), keyRepeated(), and keyReleased (methods of the Canvas class on a normal, non-full screen Canvas. This applies especially to the left, middle (when present), and right softkeys. Those are only reported back to the above key-capturing methods on full-screen Canvas instances.

The MIDP 2.0 specification says:

For some devices the keys used for commands may overlap with the keys that will deliver key code events to the canvas. If this is the case, the device will provide a means transparent to the application that enables the user to select a mode that determines whether these keys will deliver commands or key code events to the application.

This does not happen on all tested devices.

The tested devices are Nokia 6301, Nokia 6555, Nokia N95, Nokia E61i. The families affected are S40 5th Edition (and FP1) and S60 3rd Edition (and FP1 and FP2) .

Bug Nokia series 60: WMA and Push Registry behaves inconsistently receiving several SMSs

The problem happens sending several SMSs (5-10 or more) to a series60 device (all S60 2nd and 3rd Edition devices). The WMA unsinged midlets using PushRegistry acts wrongly when launching. We can have:

• Slow queuing of received SMSs;


• Symbian OS Error;


• Launching fails;


• Crash of application without message or error.

The solution claimed by the Forum Nokia is the signing of the Midlet with the Third Party Protection Domain and change the permissions for the autostart to "always allowed".

It is not a easy solution (the sign process is always a pain) and also it is a pity that the affected feature is one of the most interesting for J2ME developers.

Link to the Forum Nokia Knowledge Base article.

Java ME Tips

Java Tips is a resource where we can find interesting articles about Java developing (J2EE, J2SE, IDE, Web Services, ...).

There is a specific section with a huge collection of J2ME tips starting from some very useful for beginners up to more sophisticated suggestions.

The J2ME section is visible clicking here

Bug MMAPI Nokia: setDisplaySize method in Series60 3rd edition

The method setDisplaySize() for VideoControl doesn't work properly for S60 3rd edition.
The implementation doesn't user the parameters passed but uses always the max allowed size mantaining the aspect ratio.

Here is the link to the Nokia Technical Library about the bug:

Go to Technical Library

Bug Nokia: S60 2nd edition platformrequest always launch browser

I experienced this problem in the Nokia 6670 launching a platform request to call a number (using the protocol tel:).

After the call, the result is the start of the web browser and then the call starts. The problem happens in the series60 2nd edition and 2nd edition FP1

Here is the link to the Nokia forum post about this problem:

Forum Nokia

Bug Nokia: extra withespace character causes error in installation

Newer the phone, more strange the bug. The following is a bug affecting some Series60 devices (3rd FP1, 3rd FP2 and 5th): Nokia E71, Nokia N79, Nokia N96, Nokia 5800 XpressMusic.

The withespace characters before and after JAD attributes should be ignored according to MIDP specifications but if user tries to install an application with a whitespace character after the last JAD attribute on one of the mentioned decvies he will get a "Compulsory attributes missing".

So, be sure to remove whitespace chars from your JAD!

Additional confirmation to edit PIM data

This issue appears on the Nokia families: Series 80 2nd Edition, S60 2nd Edition FP2, S60 2nd Edition FP3, S60 3rd Edition, S60 3rd Edition FP1.

From Forum Nokia: when a MIDlet tries to edit an existing contact, add a new one, or remove an existing contact using the JSR-75 PIM API on S60 2nd Edition FP2, S60 2nd Edition FP3, and S60 3rd Edition devices, the user is asked for change confirmations every time, even if the API access setting is "always allowed". This includes situations where the MIDlet is placed in the operator/manufacturer domain (excluding S60 3rd Edition FP1 devices), or the user has manually changed the API access settings for the MIDlet in a trusted 3rd party domain.

Unfortunately, there is no workaround for this problem.

J2ME bug on Nokia series60: no newline with 'n' in Alert

Despite the 'n' can be used in any string in J2ME applications, with S60 Editions up till S60 3rd Edition, Feature Pack 1, the new line is not inserted properly in the Alert and the message remains in the same line (at least until it fits in the alert width).

The issue has been fixed starting from S60 3rd Edition, Feature Pack 2.

Read more at the Forum Nokia Wiki