22 <li id="GUID-2948CF00-2335-51CF-A5A1-9746D62FAB53"><p>backup and restore. </p> </li> |
22 <li id="GUID-2948CF00-2335-51CF-A5A1-9746D62FAB53"><p>backup and restore. </p> </li> |
23 </ul> |
23 </ul> |
24 <p>The integrity of the keyspace is maintained over modifications of this |
24 <p>The integrity of the keyspace is maintained over modifications of this |
25 kind by applying the appropriate rules for each operation and combination |
25 kind by applying the appropriate rules for each operation and combination |
26 of operations. </p> |
26 of operations. </p> |
27 <section><title>Installating keyspaces </title> <p><b>Steps to be taken at |
27 <section id="GUID-95F7E0FB-1435-4B68-B246-9DB111C31FC2"><title>Installating keyspaces </title> <p><b>Steps to be taken at |
28 device creation</b> </p><p> There are two ways of equipping an application |
28 device creation</b> </p><p> There are two ways of equipping an application |
29 with a keyspace when the |
29 with a keyspace when the application is installed on the device. One is to |
30 application is installed on the device. One is to save the keyspace to the |
30 save the keyspace to the directory <filepath>z:\private\10202BE9\</filepath>at |
31 directory <filepath>z:\private\10202BE9\</filepath>at ROM build, as explained |
31 ROM build, as explained above. This method has the disadvantage that a keyspace |
32 above. |
32 created in this way cannot subsequently be uninstalled, though it can be modified |
33 This method has the disadvantage that a keyspace created in this way cannot |
33 by the software installer or firmware upgrades. The other way is to install |
34 subsequently be uninstalled, though it can be modified by the software installer |
34 the keyspace along with the application using the software installer. Application |
35 or firmware upgrades. The other way is to install the keyspace along |
35 writers cannot do this on their own because the process requires one of the |
36 with the application using the software installer. Application writers cannot |
36 necessary files, the stub .sis file, to be set up appropriately by device |
37 do this on their own because the process requires one of the necessary files, the |
37 creators, and another, the upgrade .sis file, to be signed by Symbian. </p><p> |
38 stub .sis file, to be set up appropriately by device creators, and another, the |
38 You install a keyspace by placing a stub .sis file (installation file) |
39 upgrade .sis file, to be signed by Symbian. |
39 in the <filepath>\System\Install</filepath><file>\System\Install</file> |
40 </p><p> You install a keyspace by placing a stub .sis file (installation |
40 directory in ROM. This file is written by device creators rather than developers. |
41 file) in the <filepath>\System\Install</filepath><file>\System\Install</file> |
41 It must contain the central repository server executable. It must list all |
42 directory in ROM. This file is written by |
42 the ROM-supplied keyspace files which are ntended to be upgradable. </p><p> |
43 device creators rather than developers. It must contain the central repository |
43 The following template is supplied for use in device creation. Device |
44 server executable. It must list all the ROM-supplied keyspace files which |
44 creators are free to modify the major and minor version numbers but are strongly |
45 are ntended to be upgradable. |
45 recommended to retain the UID 0x20007770 which is allocated for use with the |
46 </p><p> The following template is supplied for use in device creation. |
46 central repository. </p><codeblock xml:space="preserve">; |
47 Device |
|
48 creators are free to modify the major and minor version numbers but are |
|
49 strongly recommended to retain the UID 0x20007770 which is allocated for use |
|
50 with the central repository. |
|
51 </p><codeblock xml:space="preserve">; |
|
52 ; template_stub.pkg |
47 ; template_stub.pkg |
53 |
48 |
54 ; Template Central Repository Stub Package File |
49 ; Template Central Repository Stub Package File |
55 |
50 |
56 ; Copyright (c) 2006 Symbian Software Ltd. All rights reserved. |
51 ; Copyright (c) 2006 Symbian Software Ltd. All rights reserved. |
161 the case where the keyspace was originally installed as an upgrade to a stub |
156 the case where the keyspace was originally installed as an upgrade to a stub |
162 .sis file. </p> <p>If there are notification requests on any of the keys, |
157 .sis file. </p> <p>If there are notification requests on any of the keys, |
163 the requests will complete as a result of installation, upgrading and uninstallation. |
158 the requests will complete as a result of installation, upgrading and uninstallation. |
164 If transactions are pending during an upgrade or uninstallation, those transactions |
159 If transactions are pending during an upgrade or uninstallation, those transactions |
165 will fail. It is advisable to close all sessions on a keyspace before uninstalling. </p> </section> |
160 will fail. It is advisable to close all sessions on a keyspace before uninstalling. </p> </section> |
166 <section><title>Firmware updates</title> <p>Symbian OS provides limited support |
161 <section id="GUID-D3331692-F84F-4421-8314-E46FA17F02A4"><title>Firmware updates</title> <p>Symbian provides limited support |
167 for firmware updates to ROM over a serial connection or by FOTA (firmware |
162 for firmware updates to ROM over a serial connection or by FOTA (firmware |
168 over the air). The generic term for these firmware updates is FOTx. When this |
163 over the air). The generic term for these firmware updates is FOTx. When this |
169 happens, the Central Repository detects the upgrade when the device is next |
164 happens, the Central Repository detects the upgrade when the device is next |
170 restarted and makes corresponding updates to its keyspaces. A firmware update |
165 restarted and makes corresponding updates to its keyspaces. A firmware update |
171 reboots the device: as part of this process the Central Repository gets the |
166 reboots the device: as part of this process the Central Repository gets the |
218 </ul> </li> |
213 </ul> </li> |
219 <li id="GUID-75404D8E-11D5-53EE-963A-53C3E1E9A720"><p>Conflicts between user |
214 <li id="GUID-75404D8E-11D5-53EE-963A-53C3E1E9A720"><p>Conflicts between user |
220 modified keyspaces and SWI modified keyspaces were covered in the previous |
215 modified keyspaces and SWI modified keyspaces were covered in the previous |
221 section. </p> </li> |
216 section. </p> </li> |
222 </ul> </section> |
217 </ul> </section> |
223 <section><title>Restore factory settings</title> <p>The Central Repository |
218 <section id="GUID-01DD59CD-E22D-43C5-8E62-2271F176C705"><title>Restore factory settings</title> <p>The Central Repository |
224 can restore factory settings across all keyspaces. Only device creators can |
219 can restore factory settings across all keyspaces. Only device creators can |
225 restore factory settings by starting the Central Repository in a special mode |
220 restore factory settings by starting the Central Repository in a special mode |
226 during a reboot. The restore does not affect all settings in the keyspace, |
221 during a reboot. The restore does not affect all settings in the keyspace, |
227 only those which have the appropriate metadata bit set. </p> <p>The effect |
222 only those which have the appropriate metadata bit set. </p> <p>The effect |
228 of restoring factory settings is to revert settings to their value at the |
223 of restoring factory settings is to revert settings to their value at the |
243 it last had after any modifications by SWI or FOTx. </p> </li> |
238 it last had after any modifications by SWI or FOTx. </p> </li> |
244 <li id="GUID-09EA88F1-2A32-5207-B6FE-FF9E0B3C9F85"><p>If a setting was created |
239 <li id="GUID-09EA88F1-2A32-5207-B6FE-FF9E0B3C9F85"><p>If a setting was created |
245 in existing ROM and modified or deleted by SWI or firmware upgrade, the changes |
240 in existing ROM and modified or deleted by SWI or firmware upgrade, the changes |
246 are not reversed. </p> </li> |
241 are not reversed. </p> </li> |
247 </ul> </section> |
242 </ul> </section> |
248 <section><title>Backup and restore</title> <p>The Central Repository can back |
243 <section id="GUID-D02F0D21-6081-4C5C-B9E1-63DE65C7DF82"><title>Backup and restore</title> <p>The Central Repository can back |
249 up data in a repository. Backup does not affect all repository entries, only |
244 up data in a repository. Backup does not affect all repository entries, only |
250 those which have the appropriate metadata bit set. </p> <p>The effect of a |
245 those which have the appropriate metadata bit set. </p> <p>The effect of a |
251 restore is to merge the backed up values of backed up settings with the current |
246 restore is to merge the backed up values of backed up settings with the current |
252 values of non-backed up settings. It does not mean restoring the device state |
247 values of non-backed up settings. It does not mean restoring the device state |
253 at the time of backup. </p> <ul> |
248 at the time of backup. </p> <ul> |