Mobile extensions trouble

[KimmoX]

Hi!

I'm having hard time installing mobile extensions preview applications to real device.

Installed packages: ssl libs, cpp libs, pips. Qt. Mobile extensions.

Prebuilt sysinfoex and locationex applications will not install, "varmennusvirhe" (authentication? error).
Self-built sysinfoex example builds fine (in command line) but also will not install (some other error suggesting not enough rights)...

I installed everything but Carbide after being not able to run any extension-using applications neither in HW nor in emulator (error -2 when starting up), but seems things did not quite improved...

What I would prefer is
a) one package that installs everything at once in a way everything just works OR
b) reliable step-by-step instructions that guarantee everything just works OR
c) turn to android & company (joke, I got 2-year contract with my 6220C

Yes, I know it's just pre-release, but it still sucks. Mobile extensions preview 2 at least worked in emulator with Garden, those are still on my other work PC.

BR, Kimmo

ps. What drives me to Qt development is tiny fonts and indicators in idle screen, when I would like BIG CLOCK and indicators so I don't need magnifying glass

[axeljaeger]

Is there any particular problem you had and that we can help you to solve?

[savaj]

Prebuilt sysinfoex and locationex applications will not install, "varmennusvirhe" (authentication? error).
Self-built sysinfoex example builds fine (in command line) but also will not install (some other error suggesting not enough rights)...

Both example require developer certificate, self signed application will not work as it require some Extended capabilities.

I installed everything but Carbide after being not able to run any extension-using applications neither in HW nor in emulator (error -2 when starting up), but seems things did not quite improved...

Some APIs only work on real device.

What I would prefer is
a) one package that installs everything at once in a way everything just works OR
b) reliable step-by-step instructions that guarantee everything just works OR

Mobile Extension APIs already described to use developer certificates for some APIs.

[KimmoX]

"Starting with S60 3rd Edition Feature Pack 2 release (aka S60 3.2) the Location capability can also be granted to self-signed applications." says developer certificate page.
There's no mention about system information (battery level, signel strength) requiring explicit certificate.

Also why prebuilt location and system information extension examples did not install? They seem to be .sis not .sisx though... Why?


The -2 was present both on emulator and HW, and I told it the first time.


So, to make the problem/question crystal clear:
exactly what packages and in which order must I install to a) SDK/Qt/Carbide and b) to S60 3.2 device in order to be able to create, install and use Qt applications with mobile extensions? If I can't do that without certificates and signing, it has been waste of time & resources.

BR, Kimmo

[axeljaeger]

Do you get examples and own code WITHOUT mobile extensions to work? Do the binary examples by Qt Software work for you? As far as I know, it is only convention that a signed sis has the suffix .sisx but it is not mandatory.

Usually packages created with createpacke are signed with a self signed certificate which works for most examples.

[KimmoX]

Hi!

Yes, self-built plain-Qt example installs and works.
Also location extension example, self-built, installs and works.

So it is so that sysinfo extension requires certificate due to read device data capability. I don't know why the APIs that require certificate are not pointed out on mobile extensions main page? Not everyone reads documentation

New question: is there other way to get battery level and signal strength in self-signed application?
Or do I really have to take developer certificate route?


BR, Kimmo

[axeljaeger]

You can upload an unsigned sis here: https://www.symbiansigned.com/app/pa...ignedOnline.do
You will have to enter the EMEI-Number of your telephone because the resulting sis is restricted to that single phone. It is for testing purposes only.

[KimmoX]

Yes, I already did so.

Seems that getting even developer certificate is pain in certain location.
OK, I could sign my own application(s) online, but with even little debugging/testing/trying out that will be impossibly difficult. How on earth can Nokia expect people to develop non-professional, extension-using applications to their phones? Guess they should break certificate-needing stuff to parts that really access "sensitive information" (like IMEI) and "general information" (like battery level) that works with self-signed... Where's the feedback, I'm in the mood for that

Thank's all,
Kimmo

[axeljaeger]

There have been a couple of discussions here about that topic. See http://discussion.forum.nokia.com/fo...d.php?t=103255

[savaj]

New question: is there other way to get battery level and signal strength in self-signed application? Or do I really have to take developer certificate route?

Yes, you can get it with self-signed certificate, make sure that you are not calling any other function which require capability.

So it is so that sysinfo extension requires certificate due to read device data capability. I don't know why the APIs that require certificate are not pointed out on mobile extensions main page? Not everyone reads documentation.

Agreed. Documentation needs to be updated.

[KimmoX]

Funny thing. Mobile extensions preview 3 documantation lists:

Prerequisites -
Libraries xqsysinfo.dll
Capabilities ReadDeviceData
Symbian Signing Self-signed
.pro file
INCLUDEPATH += [my relative extensions path]\extensions\include
symbian:LIBS += -lxqsysinfo
symbian:TARGET.CAPABILITY = ReadDeviceData
Related information -

The sysinfoex example does not use other extensions nor capabilities. But there may be feature-pack related differencies, for example location is documented as requiring symbian signing - but in my phone it just asked me when self-signed.

There are also other mindless partitioning between capabilities and uses. Alarms API requires also symbian signing, for reasons I can't imagine. Is there danger about wild application creating alarms for every minute? Or creating alarms for those special evenings (as example alamsex implies )

I'll have to try it again, but it really should work out-of-the-box without online or certified signing.

BR, Kimmo