[davidrenstrom]

Hi,

I've got a strange problem with an application working on the older Nokia 6600 (CLDC 1.0, MIDP 2.0) but not on the newer Nokia 6630 (CLDC 1.1, MIDP 2.0). On the Nokia 6630 you get the startup screen and you can choose the Continue item from the Options menu, but then the application exits (no crash). On the Nokia 6600 it works just fine, i.e. the next screen appears. What could the reason be?

Regards,
/David R.

[wang_shui]

Hi,

It can be due to a variety of reasons..

u may be using something which is not supported in 6630.
Sometimes the recordstore got corrupted..

please check all these

Wang

[balagopalks]

Please check that you have enough memory remaining in your 6630. So that your app can run fine. Also as wang suggested, check for corrupted record stores.

If you are using a canvas based app try initialising a variable and change the values in different check points in your code and draw the value in canvas so that you can identify at which point is the code hanging.

Regards
Gopal

[peterblazejewicz]

hi Kevin,

could you post that part which handles user interaction ("continue" case),

thx,
regards,
peter

[davidrenstrom]

Hi,

I'm not using any RecordStore components. Neither am I using the canvas - just a simple Java MIDlet. I don't think that there is an memory issue because the same software is running on both phones and the 6630 should have more memory, not less than the 6600.

Below is part of the code that I think causes the problem (part of actionCommand()). It may not make sense to you, but it's a Swedish word game which randomly puts together sentences. The random generation stuff may seem weird, but the 6600 doesn't seem to support nextInt(int v) function. I guess it's a CLDC 1.1 feature, but I don't quite remember from the docs.

if(c == cmdContinue)
{
switch(currentForm)
{
case 0:
appForm.setTitle("Adjectives");
for(int i = 0; i < 5; i++)
{
appForm.append(txtWords[i]);
}
break;
case 1:
adjectives = new String[5];
for(int i = 0; i < 5; i++)
{
adjectives[i] = txtWords[i].getString();
}
appForm.setTitle("Names");
break;
case 2:
names = new String[5];
for(int i = 0; i < 5; i++)
{
names[i] = txtWords[i].getString();
}
appForm.setTitle("Verbs");
break;
case 3:
verbs = new String[5];
for(int i = 0; i < 5; i++)
{
verbs[i] = txtWords[i].getString();
}
appForm.setTitle("Prepositions");
break;
case 4:
prepositions = new String[5];
for(int i = 0; i < 5; i++)
{
prepositions[i] = txtWords[i].getString();
}
appForm.setTitle("Substantives");
break;
case 5:
substantives = new String[5];
for(int i = 0; i < 5; i++)
{
substantives[i] = txtWords[i].getString();
}
frmResults.deleteAll();
int num;
for(int i = 0; i < 5; i++)
{
while(((num = rnd.nextInt() % 5) < 0) || (adjectives[num] == null));
String sentence = adjectives[num];
adjectives[num] = null;
while(((num = rnd.nextInt() % 5) < 0) || (names[num] == null));
sentence += " " + names[num];
names[num] = null;
while(((num = rnd.nextInt() % 5) < 0) || (verbs[num] == null));
sentence += " " + verbs[num];
verbs[num] = null;
while(((num = rnd.nextInt() % 5) < 0) || (prepositions[num] == null));
sentence += " " + prepositions[num];
prepositions[num] = null;
while(((num = rnd.nextInt() % 5) < 0) || (substantives[num] == null));
sentence += " " + substantives[num];
substantives[num] = null;
frmResults.append(sentence);
}
appDisplay.setCurrent(frmResults);
break;
}
if(currentForm < 5)
{
currentForm++;
for(int i = 0; i < 5; i++)
{
txtWords[i].setString("");
}
appDisplay.setCurrentItem(txtWords[0]);
}
}

Regards,
/David R.

[peterblazejewicz]

hi David,

6600 is CLDC 1.0/6630 CLDC 1.1,
so you are correct,
there could be different reason, including setCurrentItem(..) exception from last line,
could you enclose your code into single try/catch and handle possible exception to Alert?
best,
Peter

[davidrenstrom]

Hi,

Ok, I could try enclosing the setCurrentItem() statement in a try block. What exceptions do you suggest I try to catch? I'll have to wait though because I don't own a 6630, so I need to borrow one.

Thanks,
/David R.

[peterblazejewicz]

hi,

general one (Exception ex) and simply check error message you get if any,
regards,
Peter