6220 classic and PKG dependencies

[jnitard]

Hello,

Does someone know why the usual

[0x2000DA52], 0, 0, 0, {"6220 ProductID"}

does not work on my 6220 classic ? The device displays the usual "This application is not compatible with your phone popup". If I use a S60 3rd platform ID it's ok... The other devices declared in the file are OK ... Of course I have triple checked the value of the product ID (I even installed a software that was giving the value returned by the C++ API). It is a commercial device (bought from a shop).

Thanks,

Julien

[symbianyucca]

Ok, I just made an known issue yesterday for 6210 on this issue, it's been reviewed, so will take while before it is out. I would assume that it could actually be same problem, which is that the stub sis file for the UID is missing from the ROM, so the requisite line fails.

Only workaround, I could think of is to use If-Else clase with machineUID (same value).

[jnitard]

Thanks for that very quick answer !
My guess is that workaround is not going to be express signable and will require a waiver. Can you confirm this ?

Thanks,

Julien

[ltomuta]

I really have to do an express signing session myself to see how that web tool works in details but why would you think your submission will be rejected if using that alternative approach?

[jnitard]

Because I will have to declare a sis file compatible with a platform while it only supports one device. I have tried something like this :

IF machineUID=0x2000DA52 ;
...
ELSE
"incompatible.txt"-"", FT, TA
ENDIF

but if i run that on a N73 it deletes the former application and displays "Installation successfull". That is because TA displays BOTH "ok" and "abort".

I will try with TE option to see if the behavior is better.

EDIT:
- Same with TE, actually it doesn't uninstall the app, it removes all the files ... which means that the user should really press ABORT 

Thanks for your support.

[ltomuta]

Valid concern, indeed.

However, the platform compatibility statement in the PKG will be for S60 3rd Edition FP2 ( [0x102752AE] ) so you should rather test and see what happens on other FP2 devices and not on N73

[jnitard]

Yes that's a good point. But I think I have another "safer" solution:

IF machineUID<>0x2000DA52 ;
"incompatible.txt"-"", FT, TA
ENDIF
(my files to install here)

This way if the user presses yes, the files gets installed anyway. He was warned that the application will not work for its device (well it will probably...).

If I use FP2 Platform ID, on the N73 I get two popups warning me about the incompatibility, but I guess that is acceptable.

[ltomuta]

Yes, I think so too.

Hopefully by the time you're ready to release a new version of your application this problem would have been fixed through a firmware update so you will not have to worry about it.