I am having problems with S40 Developer Platform 2.0 devices. I just did an upgrade of two of my games ; both of them work on all Symbian devices, DP 2.0 and Asha 501 devices. Both of them hit strange issues on the DP 2.0 phones. Now I don't have such a phone myself (just ordered one from the developer Program, but they say it's going to take 4-6 weeks to ship it).
One of the games failed QC on the DP 2.0 devices because supposedly of runs out of memory during startup. Hmm - when i run it in the emulator, Diagnostics tells me that just after startup, the app uses about 500KB and it never uses more than 800KB. AFAIK heapsize of most of the DP 2.0 devices is 2MB (Asha 311 - 4MB and that one supposedly runs into OutOfMemoryException as well) I have also checked the app on Asha 311 and 309 phones in Remote Device Access and it starts and runs just fine.
Another app passed QC, but users on the DP 2.0 devices now complain accelerometer doesn't work anymore (the game is controller by accelerometer). I have downloaded a .jar and a .jad back from the Store and run that on an Asha 311 in Remote Device Access, on the Asha 311 emulator and on the real Symbian devices I have and everywhere accelerometer works just fine (even though I cannot use the accelerometer in RDA I can see in my app's UI that it got detected successfully which doesn't match users story - they complain the app says it couldn't find software support for the accelerometer ) Previous version of the app didn't have any problems with accelerometer on any devices and I am 100% sure I didn't change anything in this area. I did add quite a few resources which must have increased memory footprint noticeably - that's the only thing that comes to my mind.
This one is a tough one as well without access to the real device - does anyone have any idea why real DP 2.0 devices would behave differently than the ones in RDA and the emulator?