From Symbian Developer Community

Welcome to Live Release Notes - by putting these release notes into a Wiki page we hope to respond more quickly to your feedback and add the information that you really need. Please feel free to add more information to these release notes - we will be watching and may apply some editorial control if necessary.

The full logs from our Symbian^3 platform builds are now accessible here. PDK 3.0.0 is published from build 680 and summarised here.

The standard information about how to unpack and use the PDK is at the bottom of this page.

Headline Features

Feature Complete!

The Release Council has announced that Symbian^3 is now Feature Complete, and this is the first Symbian^3 PDK to reflect that: The PDK version string now has a number on the end instead of a letter.

UI ROMs

PDK 3.0.0 is the first release to support a full UI ROM executing on ARMv5 platforms. The work described on the wiki here has been incorporated and a full UI Syborg image included in the PDK. For licensing reasons we are not able to distribute the TI Zoom2 ROM however all the necessary changes to the OS to support Zoom2 have been incorporated and the images should shortly be available for downloaded from TI. See the Syborg_Manual_Testing section later in these release notes for more details on using the Syborg ROM.

Symbian UI Theme

Symbian Foundation has commissioned a new theme for the S^3 release of the platform - "Fresh" - included for the first time in this PDK.

Following are screen shots of the S^3 theme.

Homescreen

Menu

Applications

Settings

Calendar

Any bugs or enhancement requests can be submitted to Bugzilla (uiresources package).

Support for Java Midlets

This feature was working, until two separate mistakes late on in the PDK preparation combined to remove it. First, the instruction to include the R&D binaries for the IBM J9 Java virtual machine was lost in a reorganisation, and second, the work to deliver the UI ROM added a new head to the RCL_3 branch, bypassing the change which enabled the full JRT build instead of the stubs. Had either mistake been made on its own, we would have noticed a build failure, but the combination gave a clean build of the stubs - in this case, two wrongs made a right.

set JAVA_6_HOME=c:\Program Files\Java\jdk1.6.0_20
set ANT_HOME=%HELIUM_HOME%\runtime\ant_1.7

set PATH=%PATH%;%ANT_HOME%\bin

perl c:\Symbian\utilities\uh_parser\truclean.pl -p app/jrt

#define __JAVA_STUBS

#undef __JAVA_STUBS

cd \sf\app\jrt\group\sf
sbs -b bld.inf -c winscw -k

It will be in PDK 3.0.1, definitely.

Testing and Analysis

Models

The System Model for PDK 3.0.0 is available as XML, and as SVG files showing various levels of detail: packages, collections, and components.

The Agile Browser database for PDK 3.0.0 is available here. See the AgileBrowser wiki page for instructions on how to use this file..

Smoke Testing

Automated smoke tests were run on PDK 3.0.0. Results are available here.

All tests passed.

Content Management tests have been temporarily disabled due to the outstanding defect listed below:

• bug 1566 - Content Management tests are failing (E32User-CBase 47)

Emulator Manual Testing

There are a few quirks to be aware of when using the emulator from this release.

• Screen lock activates intermittently

The emulator will go into screen lock mode, where the display turns into a grey rectangle. To recover from this right click in the window.

• Emulator may quit without warning

The emulator may quit without warning until all of the "first boot" configuration steps have been completed (setting the location, date and time). If this happens to you, then our current best advice is to try again, and dismiss the error message boxes as they appear - it seems to be more likely to happen if the boxes are left to stack up... It also seems sensitive to performance, if you have intrusive anti-virus or indexing programs you may want to try disabling them. You could also try running the winscw\urel emulator instead of winscw\udeb, as this will execute faster and speed seems to be a factor in this problem.

• Bug 1530: ALF EGL 1 Panic

This is not fatal to the normal operation of the emulator. Some other applications will show a similar error (e.g. all of the Qt demos).

• Bug 2219: !AlwaysOnlineManagerServer CAlwaysOnlineMan 0 Panic
• Bug 2671: Sysap: System error -1
• Bug 2675: Messaging: System error -1

These messages disappear when the emulator networking has been configured.

• Bug 2708: Panic DevSoundAdaptor 7

This panic appeared intermittantly in the previous Symbian^3 PDK. So far we haven't had any reports of it appearing in PDK 3.0.0, but it's included here just in case. We don't know what damage this problem does, if it does appear.

• Bug 3167: Not possible to open web page from address field a second time

When a URL is entered in the WEB browser's address a second time, an error message appears instead of the intended page. Bookmarks work normally though.

• The screen occasionally goes grey and displays 'Standby'. You can unlock the screen by right-clicking the mouse on it.

Syborg Manual Testing

Full UI ROM

• Full UI syborg ROM is provided in this release

To execute this ROM you will need to unzip the QEMU binaries with support for persistent storage. These binaries are supplied in the PDK as qemu.zip, which is not automatically unpacked:

x:\7z x qemu.zip

If you have extracted the PDK to X:\ and have installed the qemu.zip to the same location you will be able to execute the ROM with the following command:

x:\qemu\bin\qemu-system-arm.exe -M X:\epoc32\rom\syborg\syborg.dtb -kernel X:\epoc32\rombuild\temp\helium-imaker2287709254642693927\core\syborg.rom.img -show-cursor

Note: The performance of this ROM is not yet good enough for it to be considered a replacement for the emulator. It currently uses no hardware acceleration and has a non-optimised software implementation for openVG.

• F5 and F8 are mapped to the left and right soft keys.
• It will take up to 5 minutes for first time boot and response to key presses is very slow.
• The first time you boot the ROM it may freeze. If it does not show the full UI after several minutes try again. Subsequent attempts should boot reliably.
• Touch input is supported however the mouse pointer alignment may be slightly offset.

On Windows machines it is necessary to have the .NET Framework 2.0 or higher installed, as the nvmemory component depends on it.

For instructions on how to rebuild the full UI ROM see here.
Note : The ROM provided with PDK 3.0.0 includes an additional patch not in the supplied source. Add the following line to the end of the file \epoc32\rom\config\sf_refhw\bigrom.oby before rebuilding the ROM. If you do not include this patch the ROM will still boot but will have an additional "System Error" warning at startup.

ECOM_PLUGIN(ptikeymappings_itut_01.dll,ptikeymappings_itut_01.rsc)

TextShell ROM

• Syborg textshell ROMs are also supplied pre-built in the PDK and boot to the eshell prompt.

f you have extracted the PDK to X:\ and have installed the qemu.zip to the same location you will be able to execute the ROM with the following command:

x:\qemu\bin\qemu-system-arm.exe -M X:\epoc32\rom\syborg\syborg.dtb -kernel X:\epoc32\rom\syborg_tshell_ARMV5_udeb.img

• The Syborg baseport can be rebuilt using the free version of RVCT 4.0 (specifically, RVCT4.0 [Build 771] for Symbian Foundation)

cd \sf\adaptation\qemu
sbs -s package_definition_2.0.1.xml -c armv5.rvct4_0 -j 4 -k

MiniGUI ROM

• Ensure you have the [extensions] needed to build roms
• Modify epoc32/rom/include/base_syborg.iby by adding .pdd to fix a black screen problem

 /* Generic nonvolatile memory */
 extension[VARID]=	KERNEL_DIR\DEBUG_DIR\_PLATFORM_NAME_mednvmemory.pdd		\sys\bin\mednvmemory.pdd

• Build the ROM

buildrom syborg minigui-stripped

There is a test application called grid which may be built and included in the rom. For more details on building grid and using miniGui see here

Binary Compatibility Report

The list of public APIs which have their compatibility managed is published here: Symbian^3 public headers.

Compatibility reports comparing PDK 3.0.0 with the Symbian^1 SDK are available online under the following links:

• Binary Compatibility Report (Headerfiles)
• Binary Compatibility Report (Libraries)

The header report is filtered to show public API only.

Open Defects

A snapshot of the open defects at the time PDK 3.0.0 was prepared may be found here.

FCLs

This PDK was built using FCL versions of the packages listed below: for each one we list the changes in the FCL which are not in the MCL. (Changes that are not considered "significant" may be manually removed to avoid repeated messages about merging the same fixes into the codeline.)

The previous PDK also involved some FCLs, so we indicate which FCLs are new to this build.

beagleboard (sf/adaptation/beagleboard)

qemu (sf/adaptation/qemu) NEW

stubs (sf/adaptation/stubs)

conntools (sf/app/conntools)

contacts (sf/app/contacts) NEW

homescreen (sf/app/homescreen) NEW

jrt (sf/app/jrt) NEW

printing (sf/app/printing) NEW

appsupport (sf/mw/appsupport)

classicui (sf/mw/classicui)

drm (sf/mw/drm)

homescreensrv (sf/mw/homescreensrv)

inputmethods (sf/mw/inputmethods) NEW

mmappfw (sf/mw/mmappfw)

platformtools (sf/mw/platformtools)

remotemgmt (sf/mw/remotemgmt)

uiresources (sf/mw/uiresources)

buildtools (sf/os/buildtools)

cellularsrv (sf/os/cellularsrv)

deviceplatformrelease (sf/os/deviceplatformrelease)

graphics (sf/os/graphics)

kernelhwsrv (sf/os/kernelhwsrv)

lbs (sf/os/lbs)

networkingsrv (sf/os/networkingsrv)

ossrv (sf/os/ossrv)

textandloc (sf/os/textandloc)

usb (sf/os/usb)

Standard Stuff

This section contains the information that you usually only need the first time you download a PDK.

Unpacking the PDK

The PDK zip files often contain too many files for the ordinary zip utilities, and are compressed using an improved compression algorithm called LZMA, so you will need to use 7-Zip. The extraction command is

7z x zipfilename

which will extract the content into the current directory.

The downloadkit utility is the easiest way to download and unpack a PDK, because it understands the structure of the kit, it can navigate the Symbian Foundation websites, and it can issue the 7z commands for you.

7z x binaries_epoc.zip
7z x binaries_winscw_lib.zip
7z x binaries_winscw_udeb.zip

\epoc32\release\winscw\udeb\epoc.exe

7z x bin_rndonly_monotype.zip
7z x bin_rndonly_aricent.zip
7z x bin_rndonly_realnetworks.zip

7z x binaries_winscw_urel.zip
7z x binaries_epoc_sdk.zip
7z x binaries_prebuilt.zip
7z x tools_epoc.zip
7z x build_BOM.zip

7z x src_oss_app.zip
7z x src_oss_app_*.zip
7z x src_oss_mw.zip
7z x src_oss_mw_*.zip
7z x src_oss_os.zip
7z x src_oss_os_*.zip
7z x src_oss_adaptation.zip
7z x src_oss_adaptation_*.zip
7z x src_oss_tools.zip
7z x src_oss_tools_*.zip

7z x binaries_armv5_lib.zip
7z x binaries_armv5_udeb.zip
7z x binaries_armv5_urel.zip

7z x bin_redist_objective_systems.zip

7z x bin_rndonly_samsung.zip

Trying out the Symbian Platform

To run the WINSCW emulator, type

epoc32\release\winscw\udeb\epoc.exe

The first boot of the emulator takes longer than normal, and models the "first boot" behaviour of a phone: for example, it asks for the location and the current time.

Which PDT? Which Compiler? Which Perl?

This release was built using PDT 1.6 - we used Perl 5.10.1, RVCT 2.2 (686) and WINSCW compiler 3.2.5 b487.

The WINSCW compiler is included in PDT 1.6 but RVCT has to be obtained from ARM. Note that the Qt package requires a command-line option which is not available with the RVCT 2.2 (616) version used for previous PDKs.

The release could also be built using earlier versions of the PDT, but some patches would be required, see Which PDT.

Building a package

You can find the instructions in the How to Build a Package page.

Building the whole platform

Warning Qt requires a pre-processing step not implemented by Raptor, and a newer version of RVCT 2.2 - We don't have a simple way to do this with Raptor, so PDK 3.0.0 platform builds should use Helium - updates to follow

We build the platform using the Foundation Build Framework (FBF), and recommend that you do the same. The cookbook steps are described in How to build the Platform. The FBF is mostly concerned with tasks which happen before or after the main compilation stage (for example getting the source code and creating ROM images). The main build work is done using Raptor.

Once you've got the platform building from the command line, we recommend using Hudson - a simple web GUI based method that encapsulates the manual steps described in the How to build the Platform linked page above. See Using Hudson for Building for details of where to obtain Hudson, how to set it up, and the range of Hudson tasks which we publish for doing Symbian Platform tasks.

The logfiles and analysis results from our build are included in the PDK in build_logs.zip, if you want to compare your results with ours, and our summary is available online.

Warning The size of a platform build is increasing significantly: we now need ~156 Gigabytes of disk space to do the whole build including the packaging into a PDK.

Comments

Faimemon said…

Faimemon said…

Song217 said…

Sign in to comment…