Application freeze

[mburton]

Hi,

I have a strange problem with a midlet on S40 devices. Our midlet runs fine on lots of devices. And I've been tasked with making sure it works well on S40 devices. If I build the app on my dev box or get it from our build machine and install via usb it runs happily

However, if I download and install the app hangs the 2nd time it's started. If I move the app to the memory card it works again!

I have no clue to what is going on. Any ideas?

I think it's something to do with the jad file, but I'm yet to find out what.

[jitu_goldie]

Hi,

I have a strange problem with a midlet on S40 devices. Our midlet runs fine on lots of devices. And I've been tasked with making sure it works well on S40 devices. If I build the app on my dev box or get it from our build machine and install via usb it runs happily

However, if I download and install the app hangs the 2nd time it's started. If I move the app to the memory card it works again!

I have no clue to what is going on. Any ideas?

I think it's something to do with the jad file, but I'm yet to find out what.

I don't think that the problem is due to application. May be this is device issue. Try the same app on some other s40 device.

check and revert..

[mburton]

I get the same problem on both the 6300 & 6500.

I've now done a little more investigation. When I download over the air and then copy to the memory card I can copy the .jad & .jar files to my pc.

I noticed that that the .jar file is 118 bytes longer and no longer a valid zip file.

It's odd that moving the app to the memory card then allows it to run!

[mburton]

Hmmm, just decided to open the jar in in a text editor. The zip header is now gone and I have

application/java-archiveflcontent@fl.contentid.s40drmv1#

[mburton]

Me again,

I think this has something to do with record stores. Our app is actually starting because I can see some debug output on the USB port. Also, if I delete the record stores when on the memory card and move the app back it starts up.

[grahamhughes]

My first suspicion of any application that works only the first time is always record stores. Can you determine if any exception is being thrown?

Graham.

[mburton]

I was just thinking the same thing.

The problem being I can only reproduce this when downloading. I don't want to mess about with our servers, so I'll have to come up with another solution.

I'll post here with my findings

[grahamhughes]

I'm surprised this only happens when installed OTA. Do your servers do anything unusual? Are you adding the DRM? Do you have access to another server (any web server will do) from where to test the app?

Graham.

[mburton]

I downloaded the jad & jar with firefox (pretending to be a phone by modifying the headers) and the jar file was exactly the same as what pops out of our build machine.

I'm now running apache on my dev box and forwarding through our firewall.

[mburton]

This is a follow up post for readers in the furture!

The problem I had wasn't related to the record stores.

For some reason our logging code was the cause of this problem. If we log things too early then the app hangs (only when running from phone memory). I don't have time to locate the root cause - maybe some static data.

The fix was simply not to log so early.