Java Verified
Symbian Signed
Java Verified
- What should I do if installation fails when trying to install a Java™ Verified application to an S60 device?
- If installation fails:
- Make sure that the "Geotrust CA for UTI" root certificate can be found (Tools -> Settings -> Security -> Certif. Management).
- Check that the date and time are correct.
- Make sure that the Subscriber Identity Module (SIM) card is in the device.
- If an application has been previously tested with a Series 40 device and it is Java Verified, can I install the same application
to other Series 40 devices?
- There shouldn't be any problem with the installation itself. However, if the application has only been tested with one device,
there's no guarantee that it will work in other devices. Therefore, retesting at least with target lead devices is recommended.
Java Verified supported devices can be found at www.javaverified.com -> Table of supported devices.
Symbian Signed
- I'm not able to install Symbian SIS file to Symbian OS v.9.x device? What should I do?
- Please check Symbian's FAQ item 1434 "How to diagnose SIS installation failures" at Symbian' s Web page www3.symbian.com/faq.nsf/SearchAll?OpenForm. If your application is Symbian Signed and the installation fails, check that
- Symbian B root certificate can be found (S60 device: Tools -> Settings -> Security -> Certif. Management).
- Date and time are correct
- SIM card is in place
- The application has been previously tested with an S60 2nd Edition device and it is Symbian Signed. Can I install the same
application to other S60 devices?
- There shouldn't be any problem with the installation itself. However, if the application has only been tested with one device,
there's no guarantee that it will work in other devices. Therefore, retesting with other target devices is recommended. Also,
be aware that applications developed for S60 1st and 2nd Editions cannot be installed to an S60 3rd Edition device as such.
At minimum, it will be necessary to recompile the application with the corresponding SDK.
- Is signing mandatory in S60 3rd Edition?
- Yes, signing is mandatory. Be aware that signing is not the same as certification, which is NOT mandatory in S60 3rd Edition.
An application can be signed with a self-created certificate, which you can make with free tools found in the SDK. Or, if
you want to get your application tested and certified by a common testing program, you can submit your application to Symbian
Signed.
- What is the difference between a self-created certificate, a Symbian developer certificate, and Symbian Signed?
- Because signing is mandatory in S60 3rd Edition, all applications must be signed with a certificate to be able to install
the application to a device. If the application doesn’t need any capabilities, other than the user grantable ones, it can
be signed with a self-created certificate, which can be created with the S60 3rd Edition SDK. If higher level capabilities
are needed, a Symbian developer certificate is required in the testing and development phase to be able to test the application
on a real device. For final applications, some capabilities are granted only through Symbian Signed, so the application must
be Symbian Signed to gain access to certain capabilities. Also, Symbian Signed may be a requirement for getting the application
to a manufacturer or operator sales channels.
- Is it possible to execute an application from SIS package during installation and uninstallation?
- Yes it is. This functionality is only allowed for certified applications.
- How do I know which platform security capabilities my S60 3rd Edition application requires?
- The Help documentation in the S60 3rd Edition SDKs provides general guidance on which platform security capabilities are required
for various APIs. The capabilities that an application requires can be confirmed in the S60 emulator. When the option "Enable
EPOCWIND,OUT Logging" is selected in the emulator and the PlatSecDiagnostics is set ON in epoc.ini, a log file is created
in the Windows "temp" folder called epocwind.out that includes information about the capabilities required. The information
is a warning message indicating that a capability is needed.
The Carbide.c++ version 1.3 includes a tool called "Capability Scanner" which scans through the source code for APIs which
require capabilities. Using the Capability Scanner with the S60 emulator with the PlatSecDiagnostics set on will give a very
likelyhood of all capabilities requirement being found.
- The application I'm creating requires to have access to an API or functionality the use of which requires the Nokia Vendor
ID. How can I have the Nokia VID for my application?
-
The Nokia VID is used to protect sensitive areas of the System. These areas may affect the type approval of the device. That
is the reason why Nokia VID use cannot be granted to anyone. Also, there is usually a work-around available through API partnering.
- Where do I find more information about Symbian Signed and UIDs?
-
Please go to Symbian Signed web site and read the "The Complete Guide To Symbian Signed".
RDF Facets:
qdcZidentifierQSxhttpE3aE2fE2fwwwE2eforumE2enokiaE2ecomE2fTechnologyE5fTopicsE2fApplicationE5fE51ualityE2fTestingE2fApplicationE5fTestingE5fFAE51E2eE78htmlX
qfnZupdatedQDx2009E2d05E2d11X
qdcZtypeQUqfnZE45E78cludedFromGeneralE4CistingsQ
qdcZtypeQUqwebZE52esourceQ
qdcZtypeQUqwebZInformationE52esourceQ
qdcZtypeQUqwebZPageQ
qdcZtypeQUqfnTypeZE52esourceQ
qdcZtypeQUqfnTypeZWebpageQ
qdcZtypeQUqmarsZManagedE52esourceQ
qdcZtypeQUqrdfsZE52esourceQ
qfnZdistributionQUxhttpE3AE2FE2FforumE2EnokiaE2EcomE2FX
qfnZtypeQUqfnTypeZE52esourceQ
qfnZtypeQUqfnTypeZWebpageQ
qmarsZlanguageQUxhttpE3AE2FE2FswE2EnokiaE2EcomE2FlanguageE2D1E2FenX
qrdfZtypeQUqwebZInformationE52esourceQ
qrdfZtypeQUqwebZE52esourceQ
qrdfZtypeQUqwebZPageQ
qrdfZtypeQUqfnTypeZE52esourceQ
qrdfZtypeQUqmarsZManagedE52esourceQ
qrdfZtypeQUqfnTypeZWebpageQ
qrdfZtypeQUqrdfsZE52esourceQ
qrdfZtypeQUqfnZE45E78cludedFromGeneralE4CistingsQ