I did originally debug this and found that I get an end of file attempting to read the first byte!

Given that it only occurs on S40 SDK 2 I think this is a platform bug.

I have logged a bug...

I create a reader from an input stream:

InputStream stream = System.class.getResourceAsStream(path);
Reader reader = new InputStreamReader(stream, encoding);

Here's the fix/workaround for anyone that comes across this problem:

This effected Touch UI versions of devices. The LCD Command was created using type.ITEM. Evidently, no item is selected in the...

This is my third post regarding possible bugs in S40 SDK 2 when compared with previous S40 SDKs & devices - see Unable to read Chinese resource file S40 SDK 2 and Buttons in LCD forms start on a new...

All resource files are in UTF-8.

[Apologies for the slow response - I just found the alert email in my junk folder :(]

My app has navigation buttons on various view forms - e.g. Next, Previous, Detail, etc. The first button uses Item.LAYOUT_NEWLINE_BEFORE and the following buttons use Item.LAYOUT_DEFAULT (I have also...

My app is translated into 9 national languages: English, French, Spanish, Portuguese, Italian, Chinese, Hindi, Russian, & Arabic.

However, I've hit a really odd problem on S40 SDK 2. It cannot...

The reply from Nokia does not mention S60 at all that I can see. :confused: The only references to S60 are in the email I sent, which was a reply to Ovi's email with an attached zip file containing...

Ovi was my first point of contact.

I sent this:

I'm initially developing for Series 40. I would like to run some tests in my devices in the trusted domain.

I have been searching the Nokia...

My development environment is comprised of Eclipse IDE with maven for building. I haven't used Sun WTK IDE (but I do use the WTK emulator from time to time).

I have completed the Publisher Registration and have received the .crt, .key, and .sis files from Ovi. I have learnt that the .sis file is for Series 60 but I can't find anything regarding the .crt...

Thread.yield() didn't work but was absolutely correct.

The solution is to run the slow method as a thread, thus giving the system the time to display the alert:

public void...

I added Thread.sleep(5000); but it makes no difference.

Whilst I have found other examples like this on the net, I thought that it may be the combination of the settings: Alert AlertType.INFO,...

I understand your point, but DataFactory.createAndSaveCustomerDOs(size, new int[] { 1, 1, 1, 1, 0 }); is slow - it varies from a couple of seconds to 60 or more depending on the size parameter....

I have the following piece of test code:

public void createTestData(int size)
{
try {
Alert alert = new Alert(null, "Creating test data...", null, AlertType.INFO);
Gauge gauge = new...