3rd and 5th Edition application development

[deedux]

i wanna ask bout n73,my n73 didnt support the chinesse language,i really really need them...oh,i'm from indonesia...i already upgrade the firmware but still cant support this language...
should i flash with other firmware?plz help me...
thx

[liuxg]

Please flash your N73 firmware with Chinese variant. The software can be found at your Nokia care centers in your country. Normally, the Chinese variant software also supports the English language as well though the language codes are different from the standard one (01). The main purpose for this is the support of Chinese dictionary in different region. Once an English word is supplied in the dictionary, the dictionary can know what type of Chinese characters should be displayed. The language codes for the Chinese variants are:

Language code Meaning

01 English
029 Taiwan Chinese
157 Twaiwan English
030 HongKong Chinese
158 HongKong English
031 Mainland Chinese
159 Mainland English

Please further refer to the sample code "ChineseDisplay" I posted in this thread.

For Chinese developers, there is a very good wiki article talking about this:

http://wiki.forum.nokia.com/index.ph...B5%85%E8%B0%88

[ronaldwh]

Hallo,

This thread is Excellent!!!
Btw, I want to use the RMobileCall, RMobilePhone, and other RMobile classes like I used in 2nd edition. But when I porting my application for the 3rd edition, the dialling process did not working at all.
Is there anything that I should do for this to work?

Thank You!

[liuxg]

You probably need to have "NetworkControl" capability to get it working. Please try the following example code:

\Symbian\9.1\S60_3rd\S60Ex\IsvTelCallApp

The code uses "CTelephony" API to make the outgoing call.

Meanwhile, you may find the following plug-in package "PhoneClientDialAPI.zip" to make an outgoing call:

http://www.forum.nokia.com/info/sw.n...Pack1.zip.html

[liuxg]

Attached please find a sample code for "Sensor API". Currently, sensor can be found in Nokia 5500, Nokia N95, Nokia N95 8GB, N82 phones.

The sample code is recreated based on the sample code provided in the plug-in SDK. I have put the necessary code into an engine file, which can be easily reusable by other developers. Developers may use it as a base to further developer some more interesting applications.

More information can be found at:

http://wiki.forum.nokia.com/index.php/S60_Sensor_API

http://blogs.forum.nokia.com/blog/ju...O5WZ603HL6D-20

Moving ball example code:
http://research.nokia.com/projects/activity_monitor

Another opensource project "shakerracer"
http://www.symbianresources.com/proj...hakerracer.php

[liuxg]

Attached please find a sample code to find the UID of the installed applications. The sample code once was published at Forum Nokia "Code and Exmaples" section. However, unfortunately, it was removed. I have basically cleaned the code a little bit to make it working on our Nokia S60 3rd edition only! I think it is still a good untility to some developers!

[liuxg]

For the fans of Microsoft Vistudio tool, a good news is that two new updates for the Carbide.vs tool have finally been released:

http://www.forum.nokia.com/info/sw.n..._vs_2_0_1.html

http://www.forum.nokia.com/info/sw.n...de_vs_3_0.html

To me, I like the classview of the tool and efficiency of the tool although both do not support on-device debugging!

[liuxg]

Set QWERTY on Series 60 3rd edition emulator.

Many of us have wanted to have the QWERTY layout on the Series 60 3rd edition emulator, so that we can test applications for E61 or E90 devices which have similar key layout.

Surprisingly, for me atleast, such a layout configuration is provided by default in the Series 60 3rd edition SDK itself, but not included in the default emulator configuration for unknown reasons.
The layout is provided in epoc_352x416_qwerty.ini file which can be found in \Symbian\9.1\S60_3rd\Epoc32\Data folder.
So as to enable this configuration just include this line in epoc.ini(Also found in \Symbian\9.1\S60_3rd\Epoc32\Data):

configuration epoc_352x416_qwerty.ini
Make sure that this is the first line,so that it becomes your default configuration.
This is the screenshot of my emulator with the QWERTY layout.

[liuxg]

It has been found that GCCE build have generated huge binaries on S60 3rd MR SDK compared to S60 3rd FP1 SDK .So to trim them a bit just include the following lines in your .mmp file when compiling GCCE under S60 3rd edition MR SDK.

OPTION GCCE -O2 -fno-unit-at-a-time

You would get a considerably smaller size binary.

More explanation of the problem can be found at:

http://discussion.forum.nokia.com/fo...d.php?t=125565

[propertrue]

It is very useful. Thank you so much!

Cheers

[liuxg]

Attached please find an updated sample code for "CameraApp", which was inititally created by me long long time ago. In the updated sample code, I removed all of the codes for 2nd edition support, which makes the code very messy sometimes. In order to make it working, you need to unzip the "autofocus_extension_library_s60_3rd_ed.zip" file first to the SDK installation directories.

If you want to make it compilable for WINSCW, please rename "CameraApp_winscw.mmp" to "CameraApp.mmp".

If you want to make it combilable for GCCE or ARMV5, please rename "CameraApp_release.mmp" to "CameraApp.mmp", or modify the "bld.inf" file to the following format without renaming the file:

PRJ_MMPFILES
CameraApp_release.mmp

[Tanya]

Hi liuxg

Really it's all are very useful for us. specially for 3rd edition developer.

Thank You.

Regards
Tanya

[liuxg]

INTERNATIONAL MOBILE EQUIPMENT IDENTITY（简称IMEI）。中文译做「国际移动设备身份码」，它的最大功能是用来协助辨别手机身份真伪。

发挥身分识别功能

IMEI包含手机型号核准码同出厂序号，同型号手机核准号码一定一样，但出厂序号就永远不会一样.

本文章转自·http://www.cnonline.org/2002/article/2063.html IMEI码速查表__中国手机在线

IMEI一般由15个数目字组成，按「*#06#」就会显示出来，格式是123456-78-901234-5。

　　123456=TYPE APPROVAL CODE，即设备型号核准号码。
　　78=FINAL ASSEMBLY CODE，即最后装配号码。
　　901234=SERIAL NUMBER，即出厂序号。
　　5=SPARE NUMBER，即备用号码。

以下就用诺基亚 8850(该手机详细资料)：

Nokia 8850按下「*#06#」后，屏幕出现448901-30-233588-9，其中448901代表手机核准型号系8850，30代表最后装配地是韩国，233588代表手机出厂序号，9代表备用号码。

最后装配号码，是指手机最后完成装配时是在哪一家工厂，每一家工厂都有它特别的代号，所以这并不是哪个国家制造的代号。

产品在线保修查询：
http://www.nbaer.net/batch.viewlink.php?itemid=991

[liuxg]

Attached please find a sample code called "Sensor". It is an updated version of the previous release. Basically, a sensor engine is developed; a moving ball example code is incoporated into the sample code. Meanwhile, a practical use case is also displayed.

In the "Image" window, a user is able to displaying the image files in the "Media gallery" by slanting the phone. As such, a user is able to display the images one by one forwards or backwards.

In order to build the sample under WINSCW though sensor function is not working in WINSCW, it is recommended to copy the "RDAccelerometer.lib" from "ARMV5" to make it build successfully.

It is recommended to build the sample code in MS-DOS box to generate the needed "sensor.mif" file.

Meanwhile, please download the "Sensor Plug-in for 60 3rd Edition" and "N95 RD Accelerometer Plug-in package" at the following link:

http://research.nokia.com/projects/activity_monitor

in order to successfully build the example code.

Hope you enjoy the sample code.

[dougcn]

Attached please find a sample code called "Sensor". It is an updated version of the previous release. Basically, a sensor engine is developed; a moving ball example code is incoporated into the sample code. Meanwhile, a practical use case is also displayed.

In the "Image" window, a user is able to displaying the image files in the "Media gallery" by slanting the phone. As such, a user is able to display the images one by one forwards or backwards.

In order to build the sample under WINSCW though sensor function is not working in WINSCW, it is recommended to copy the "RDAccelerometer.lib" from "ARMV5" to make it build successfully.

It is recommended to build the sample code in MS-DOS box to generate the needed "sensor.mif" file.

Hope you enjoy the sample code.

Thanks for your example.

What is the supported S60 version? Some header files (RDAccelerometerObserver.h, etc) can not be found under S60 3rd FP1. What is missing? And if a release note exists in the attached package, it will be more helpful.

Also for an example, it is recommended to use an unprotected UID from the range beginning with 0xAxxxxxxx or 0xExxxxxxx.