Reading the excellent guide 'MIDP 2.0: Tutorial On Signed MIDlets' I came away with the notion that buying a code signing certificate from Verisign and signing your application would allow your MIDlet to execute in the 'Trusted Third Party' domain.
This would appear to not be the case when tested with the 6170,7610 and 6230 (the application is untrusted).
Following this up I have two questions:
Do any Nokia handsets trust the application if it's signed by a developer's code signing certificate?
And is there any other way to become a trusted application without going down the Java Verified route (as only a handful of handsets have the certificate)?
What I've managed to figure out when testing Nokia 6600 and 6260 -phones and signed midlets, that you have two certificates (MIDlet-Certificate-n-n -attributes) in your jad-file, because these Series 60 -phones do not have intermediate certificates installed in the phone's memory unlike Series 40-phones.
And with 6600 the phone's SW should be 4.09.1 or higher. A quote from Nokia's known issues document:
"No solutions exist for software version 3.42.1, but this issue has been corrected in software release 4.09.1, where 3rd party domain will be supported."
Thanks for the response.
I spotted that issue for the frimware version of the 6600.
Also, i think this cert business is a bit of a mess.
Looking at Motorola for example, even though the root certs exist on the device and the code is signed using a verisign cert we purchased you still cannot install the app on Motorola.
see following quote from motocoder support on V535 specific
The following article still is true for this device too.