Custom Search

Thursday, October 2, 2008

• 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.
  • I'm not able to install Symbian SIS fle 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 developer.symbian.com/main/academy/faqs/. 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.
  • 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.
  • 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 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, it can be signed with a self-created certificate, which can be created with the S60 3rd Edition SDK. If 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, for example.
  • Why do I need TC Trustcenter Publisher ID?

· TC Trustcenter Publisher ID is needed if you want to get your application Symbian Signed (freeware developers excluded). Publisher ID identifies you as the source of the application. Before submitting the application to Symbian Signed, you need to sign it with a Publisher ID. The test house checks the signature and verifies that the application hasn’t been tampered with on the way to Symbian signing and that the application is coming from you.

A Publisher ID is also required if you need a Symbian developer certificate with certain capabilities, or if you want to test your application with more than one device (for S60 3rd Edition applications only).

  • What is a Symbian developer certificate and when do I need it?

· A Symbian developer certificate is needed if your application requires certain capabilities and you want to test the application on a real device (for S60 3rd Edition applications only). A developer certificate can be requested at www.symbiansigned.com -> Request DevCerts; authentication depends on how many devices you have and which capabilities you request.

Number of IMEIs

Authentication

Granted capabilities

1

Symbian Signed Account

LocalServices, ProtServ, UserEnvironment, NetworkServices, Location, ReadUserData, WriteUserData, SW Event, SurroundingsDD, ProtSrv, PowerMgmt, ReadDeviceData, WriteDeviceData, TrustedUI

2-100

Publisher ID and Symbian Signed account

As above

>100

Publisher ID, Symbian Signed account and licensee support

As above + NetworkControl, MultimediaDD, ComDD, DiskAdmin, AllFiles, DRM & TCB

  • How much does Symbian Signed testing and certification cost?
  • Test houses have their own prices for Symbian Signed testing. You can check the prices at www.symbiansigned.com -> Test houses.
  • Have freeware developers been taken into account in S60 3rd Edition?
  • Yes. Symbian has introduced a model for freeware applications. Detailed information is available at www.symbiansigned.com -> Freeware.
  • What is a UID and how do I get one?

· The Unique Identifier (UID) is a unique identification for the binary (EXE or DLL) within the system. Its purpose is to prevent executables from interfering with each other. For S60 3rd Edition applications UIDs have to be reapplied. More detailed information is available at www.symbiansigned.com -> UIDs.

  • Do I need to have an UID from protected or unprotected range?

· The following table explains what UID range to use depending on the status of your application.

Signing status

Symbian Signed (ready to be submitted to Symbian Signed)

DevCert self-signed

Other self-signed (e.g. signed with self-created certificate)

UID range

Protected

Protected or unprotected

Unprotected

  • How can I back up and restore my application in an S60 3rd Edition device?

· Applications are not backed up by default in S60 3rd Edition. You should take the following steps if you want the application to be backed up and restored:

Create an XML backup registration file named "backup_registration.xml"




Include "backup_registration.xml" to your project .pkg-file.

"backup_registration.xml"-
"!:\private\98765432\backup_registration.xml"

NOTE: By placing the registration file in an application's private data area it is protected on the device.

  • Is it possible to execute an application from SIS package during installation and uninstallation?
  • Yes it is. This functionality is allowed only 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.
  • 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 application I'm creating requires to have access to an API or functionality which use 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.

  • For how long are TC Trustcenter Publisher ID and developer certificates valid?

· TC Trustcenter Publisher ID is valid for one year. Developer certificate is valid for six months. When requesting developer certificate, check that your Publisher ID is valid. When signing an application with developer certificate, Publisher ID (.key) and developer certificate (.cer) must both be valid. You can check the certificate expiration date by double-clicking the .cer file in Windows explorer.

  • What are the requirements for becoming a Symbian Self Certifier?

· It depends on which capabilities your application needs. If it doesn't need any sensitive capabilities, you can discuss and agree on the Self Certification directly with Symbian (symbiansigned@symbian.com). But if your application uses some sensitive capabilities, then Nokia needs to support granting the Self Certifier rights. In that case, Self Certifier rights are granted for an application. The requirements are:

0. The developer is or is becoming a Symbian Signed Self Certifier. The developer needs to contact Symbian about this.

1. The case is presented to Nokia internal Capability granting steering group.

    • Capability request form is sent to to nokia.testing@nokia.com. Responsible: developer
    • Internal capability request template is needed and presented to the steering group. Responsible: Nokia business owner
    • Company evaluation is done with the business need to become a Self Certifier with manufacturer capabilities.

2. After capability approval, developer submits the application via Symbian Signed for Nokia. Application is tested against Symbian Signed and Nokia test criteria (excl. NUI-01 - NUI-05 test cases).

3. Symbian Signed for Nokia tests must be passed once.

4. Legal agreement is done. Resposible: Nokia business owner, developer.

5. After Symbian Signed for Nokia testing has been passed once and legal agreement is in place, Forum Nokia lets Symbian know that we accept the use of the requested capabilities in Self Certification.

Current cost is 10 000/year.

No comments: