Languages

Menu
Sites
Language
Cannot load app onto Z3

Hi,

I'm trying to build and load the File Manager sample app. 

I'm working on Windows 7, using Tizen IDE 2.4.0 Rev 3 (20151223-1451), with a Z3 phone.

The app builds fine in the IDE, and the console shows the following:

Launching the Tizen application...
# If you want to see the detailed information,
# please set the logging level to DEBUG in Preferences and check the log file in 'C:\tizen-sdk-data\ide\logs/ide-20160225_185822.log'.

[Deploying the package...]
    RDS: On
[Creating the package...]
    Created the package: C:\Users\Tim\tizenworkspace\FileManager\Debug\org.example.filemanager-1.0.0-arm.tpk
[Transferring the package...]
    Transferred the package: C:\Users\Tim\tizenworkspace\FileManager\Debug\org.example.filemanager-1.0.0-arm.tpk -> /opt/usr/apps/tmp
[Installing the package...]
    Uninstalling the package...
path is /opt/usr/apps/tmp/org.example.filemanager-1.0.0-arm.tpk
start process (install)

end process (fail)
processing result : FATAL_ERROR [61] failed
spend time for pkgcmd is [1089]ms
cmd_ret:61
(12.924 sec)

Checking the log file, I get the following messages:

[2016.02.25 19:00:24][ERROR] TizenLaunchDelegate2.java(220) - failed to open Choose Target Dialog
[2016.02.25 19:00:27][ERROR] ConnectionExplorerLabelProvider.java(106) - Failed to get platform capability

I've been unable to find any details on what these messages mean, or why the install might be failing.

I thought the issue might be passwords, so I generated another P12 cert, and used my Samsung username/password for it, and the other passwords for the certificates. I'm not sure if I needed to request another certificate due to changing the P12 author cert.

I had enabled "Permit installation to device" for the Z3, where Debug mode is enabled, and had selected the DUID of the device when setting up my certs.

Any suggestions? Just hoping to get over this hurdle of being unable to install a simple app, which seems much more confusing than it should be.

 

List

Responses

24 Replies
daniel kim

Hi,

I would suggest you to check whether your application need platform certificate or not.

In such case, you need to generate platform certificate to run your application.

And please check this log as well.

     'C:\tizen-sdk-data\ide\logs/ide-20160225_185822.log'

Regards

Tim Howie

Here is another log, but with the log level set to Debug (sorry, I hadn't noticed this option before):

[2016.02.25 21:24:16][PERFORM_S] NativeExternalBuildRunner.java(75) - [Category: native.build] at 2016-02-25 21:24:16.448
[2016.02.25 21:24:16][PERFORM_E] NativeExternalBuildRunner.java(78) - [Category: native.build] at 2016-02-25 21:24:16.561   [113(ms)]
[2016.02.25 21:24:19][PERFORM_S] NativeExternalBuildRunner.java(75) - [Category: native.build] at 2016-02-25 21:24:19.413
[2016.02.25 21:24:23][PERFORM_E] NativeExternalBuildRunner.java(78) - [Category: native.build] at 2016-02-25 21:24:23.728   [4315(ms)]
[2016.02.25 21:24:31][PERFORM_S] AbstractTizenCLaunchDelegate2.java(174) - [Category: native.launch            Variable: .buildForLaunch] at 2016-02-25 21:24:31.517
[2016.02.25 21:24:32][PERFORM_S] NativeExternalBuildRunner.java(75) - [Category: native.build] at 2016-02-25 21:24:32.017
[2016.02.25 21:24:32][PERFORM_E] NativeExternalBuildRunner.java(78) - [Category: native.build] at 2016-02-25 21:24:32.127   [110(ms)]
[2016.02.25 21:24:32][PERFORM_E] AbstractTizenCLaunchDelegate2.java(196) - [Category: native.launch            Variable: .buildForLaunch] at 2016-02-25 21:24:32.873       [1356(ms)]
[2016.02.25 21:24:32][DEBUG] LaunchesListener.java(77) - Added - project: , device serial: 
[2016.02.25 21:24:32][PERFORM_S] TizenLaunchDelegate2.java(189) - [Category: native.launch] at 2016-02-25 21:24:32.881
[2016.02.25 21:24:32][PERFORM_S] TizenLaunchDelegate2.java(870) - [Category: native.launch          Variable: .deploy] at 2016-02-25 21:24:32.963
[2016.02.25 21:24:36][DEBUG] RdsDeployer.java(186) - [RDS] Cannot find information of the latest launch
[2016.02.25 21:24:36][PERFORM_S] TizenLaunchDelegate2.java(984) - [Category: native.launch          Variable: .packaging] at 2016-02-25 21:24:36.479
[2016.02.25 21:24:36][DEBUG] FilenameUtil.java(357) - Calculated relative path: bin
[2016.02.25 21:24:36][DEBUG] FilenameUtil.java(357) - Calculated relative path: bin/filemanager
[2016.02.25 21:24:36][DEBUG] FilenameUtil.java(357) - Calculated relative path: lib
[2016.02.25 21:24:36][DEBUG] FilenameUtil.java(357) - Calculated relative path: res
[2016.02.25 21:24:36][DEBUG] FilenameUtil.java(357) - Calculated relative path: res/edje
[2016.02.25 21:24:36][DEBUG] FilenameUtil.java(357) - Calculated relative path: res/edje/filemanager.edj
[2016.02.25 21:24:36][DEBUG] FilenameUtil.java(357) - Calculated relative path: res/images
[2016.02.25 21:24:36][DEBUG] FilenameUtil.java(357) - Calculated relative path: res/images/etc.png
[2016.02.25 21:24:36][DEBUG] FilenameUtil.java(357) - Calculated relative path: res/images/folder.png
[2016.02.25 21:24:36][DEBUG] FilenameUtil.java(357) - Calculated relative path: res/images/home.png
[2016.02.25 21:24:36][DEBUG] FilenameUtil.java(357) - Calculated relative path: res/images/home_press.png
[2016.02.25 21:24:36][DEBUG] FilenameUtil.java(357) - Calculated relative path: res/images/img.png
[2016.02.25 21:24:36][DEBUG] FilenameUtil.java(357) - Calculated relative path: res/images/music.png
[2016.02.25 21:24:36][DEBUG] FilenameUtil.java(357) - Calculated relative path: res/images/pdf.png
[2016.02.25 21:24:36][DEBUG] FilenameUtil.java(357) - Calculated relative path: res/images/ppt.png
[2016.02.25 21:24:36][DEBUG] FilenameUtil.java(357) - Calculated relative path: res/images/text.png
[2016.02.25 21:24:36][DEBUG] FilenameUtil.java(357) - Calculated relative path: res/images/up_folder.png
[2016.02.25 21:24:36][DEBUG] FilenameUtil.java(357) - Calculated relative path: res/images/up_folder_press.png
[2016.02.25 21:24:36][DEBUG] FilenameUtil.java(357) - Calculated relative path: res/images/video.png
[2016.02.25 21:24:36][DEBUG] FilenameUtil.java(357) - Calculated relative path: shared
[2016.02.25 21:24:36][DEBUG] FilenameUtil.java(357) - Calculated relative path: shared/data
[2016.02.25 21:24:36][DEBUG] FilenameUtil.java(357) - Calculated relative path: shared/res
[2016.02.25 21:24:36][DEBUG] FilenameUtil.java(357) - Calculated relative path: shared/res/filemanager.png
[2016.02.25 21:24:36][DEBUG] FilenameUtil.java(357) - Calculated relative path: shared/trusted
[2016.02.25 21:24:36][DEBUG] FilenameUtil.java(357) - Calculated relative path: tizen-manifest.xml
[2016.02.25 21:24:36][DEBUG] ReadSigningProfileFileCommand.java(83) - Read profile[StartOver] from C:\Users\Tim\tizenworkspace\.metadata\.plugins\org.tizen.common.sign\profiles.xml
[2016.02.25 21:24:36][DEBUG] ReadSigningProfileFileCommand.java(104) - profile: TizenSP
[2016.02.25 21:24:36][DEBUG] ReadSigningProfileFileCommand.java(104) - profile: StartOver
[2016.02.25 21:24:36][DEBUG] TizenIncrementalSigner.java(1021) - Load key path: C:\tizen-sdk-data\keystore\StartOver\author.p12
[2016.02.25 21:24:36][DEBUG] TizenIncrementalSigner.java(1021) - Load key path: C:\tizen-sdk-data\keystore\StartOver\distributor.p12
[2016.02.25 21:24:36][DEBUG] TizenIncrementalSigner.java(1021) - Load key path: C:\tizen-sdk-data\keystore\StartOver\author.p12
[2016.02.25 21:24:36][DEBUG] TizenIncrementalSigner.java(1021) - Load key path: C:\tizen-sdk-data\keystore\StartOver\distributor.p12
[2016.02.25 21:24:37][PERFORM_E] TizenLaunchDelegate2.java(1031) - [Category: native.launch        Variable: .packaging] at 2016-02-25 21:24:37.003        [524(ms)]
[2016.02.25 21:24:37][PERFORM_S] TizenLaunchDelegate2.java(1048) - [Category: native.launch        Variable: .transfer] at 2016-02-25 21:24:37.021
[2016.02.25 21:24:42][PERFORM_E] TizenLaunchDelegate2.java(1084) - [Category: native.launch        Variable: .transfer] at 2016-02-25 21:24:42.227            [5206(ms)]
[2016.02.25 21:24:42][PERFORM_S] TizenLaunchDelegate2.java(1165) - [Category: native.launch        Variable: .install] at 2016-02-25 21:24:42.234
[2016.02.25 21:24:42][DEBUG] SdbCommand.java(203) - $ /usr/bin/pkginfo --pkg org.example.filemanager | grep -i Removable
[2016.02.25 21:24:42][DEBUG] SdbCommand.java(203) - $ /usr/bin/pkgcmd -l  | grep "\[org.example.filemanager\]"
[2016.02.25 21:24:43][DEBUG] SdbCommand.java(203) - $ /usr/bin/pkgcmd -G -q -i -t tpk -p "/opt/usr/apps/tmp/org.example.filemanager-1.0.0-arm.tpk"
[2016.02.25 21:24:44][DEBUG] SdbCommand.java(203) - $ /usr/bin/pkginfo --app org.example.filemanager | grep Package: 
[2016.02.25 21:24:45][PERFORM_E] TizenLaunchDelegate2.java(1210) - [Category: native.launch        Variable: .install] at 2016-02-25 21:24:45.276   [3042(ms)]
[2016.02.25 21:24:45][PERFORM_E] TizenLaunchDelegate2.java(939) - [Category: native.launch          Variable: .deploy] at 2016-02-25 21:24:45.282             [12319(ms)]
[2016.02.25 21:24:45][DEBUG] LaunchesListener.java(187) - removed - project: , device serial: 
[2016.02.25 21:24:45][PERFORM_E] TizenLaunchDelegate2.java(286) - [Category: native.launch] at 2016-02-25 21:24:45.310   [12429(ms)]

 

daniel kim

Hi,

I've failed to find information from the log. so If you have  the same problem to run sample code, I would suggest you to generate author and device profile certificate and try it once again for testing. 

Regards

Tim Howie

Hmm, I had done that already, but will do that again.

All of the passwords entered into Tizen for the certificates are not related to the username/password that need to be entered when requesting a certificate, correct? 

daniel kim

Hi,

In case of author certificate, you need to use the password what you've used..

I would suggest you to check this link.

      https://developer.tizen.org/community/tip-tech/issuing-tizen-certificate-certificate-extension-ver-1.1.1

Regards

AVSukhov

Hello,

Also, maybe this article helps you:

https://developer.tizen.org/community/tip-tech/trouble-shooting-certification?langredirect=1

Alex Dem

Hi,
I have 2.4 rev 3 installed on Win 7 - 64 bit. It works with Z3 devices from box. You do not need to request any certificates from Samsung for this case.
All you need is just add security profle here  'Window->Peference->Security profile' and generate author certificate.
Alexey.

Tim Howie

Thanks Alex,

I've done that, yet still get the FATAL_ERROR [61] error message. 

Running Tizen 2.4.0.2 (Z300FXXU0AOJA)

For you, did you just:

- set your Z3 to developer mode

- install Tizen IDE

- create a security profile, generate an author certificate

- load a Tizen project, build it, run as 'debug'

- app loads onto Z3

?

I've basically followed this process, except the 'app loads onto Z3' never occurs.

Alex Dem

Hi,
Just important note:
You do not need request certificate for Z3 'Custom' devices, see: Settings->About Device-> Device Status. In this case you need  to add profile and generate author certificate just.
But if  there is Settings->About Device-> Device Status -> Official, you will need to request certificates from Samsung, certifcate extension should be installed in this case.
https://developer.tizen.org/community/tip-tech/issuing-tizen-certificate-certificate-extension-ver-1.2
Alexey.

Tim Howie

Hi Alex,

I checked and the Device Status is Official, so I do need the certificate. 

 

Alex Dem

Hi,
Try to check Settings->Data and Time.There should be actual date and time. In my case it was root cause.
Alexey.

Alex Dem

Also fyi,
I was able to check onto Z3 'official' device 2.4.0.0 (Z300HDDU0AOJ4) just. I have got the same FATAL_ERROR in all cases (even for for Z1 mobile official) for certificates which I have got via Certificate Extension 1.2.
But for Gear S2 such certificate (with all mentioned mobile/wearable DUIDs) works ok.
Alexey.

Tim Howie

Hmm, do you think there's an issue with the Certificate Extension? My version that I have installed is 1.0.31; I installed it through the Update Manager.

Peter Wegner

1.

Error 61 is something with wrong or not existing Cert...

I hate this...

 

2.

If I see Z3 then I think about India SM-Z300H not SM-Z300F...

 

Ehm, no idea how special your Firmware and device is...

""Running Tizen 2.4.0.2 (Z300FXXU0AOJA)""

 

Best Regards

Tim Howie

Thanks Peter.

Hmm, not sure how to do anything else with the cert. I generate it in the IDE, as per the instructions, I believe. I had created a cert online as well, setting the password to something very easy (since it's just for testing). 

I think the phone is a Russian version of the phone - not sure if it's unique at all or anything.

Masum Talukder

Hello Tim Howie,

I have once faced this type of issue and then I updated the phone binary. Cause while working in Latest IDE, the signin process does not work with old version binary.

If possible, try to update or flash updated binary and then try again.

Hope it will work !

thanks and regards

Tim Howie

Thanks Masum,

Where would I find available phone binaries? I'm working on the phone in Canada, so would need to download from a Samsung or Tizen site, I would imagine.

Masum Talukder

Hello,

You can update the binary using FOTA update.

thanks and regards.

Tim Howie

Thanks Masum - although my device does not have an 'Update Software' option under 'About device', and I have not seen an option anywhere else in the menus.

Peter Wegner

@ Tim Howie

 

Meanwhile you managed your problem?

If yes, please share your steps.

 

Thanx in advance.

 

Best Regards

Tim Howie

Hi Peter,

No luck as of yet, unfortunately. I can get the sample app (File Manager) to load onto the emulator, but cannot get it to load and run on the device.

Peter Wegner

Are you able to work with SDB?

 

Maybe to check if you have some Developer or pre commercial or what ever your Z300F is...

SDB ROOT ON

If your Z300F switch to root...

 

Check if you have this folder + file:

/home/developer/device-profile.xml

DUID of your Z300F should inside this cert...

 

Your Z300F has "old" Firmware... from 2015...

Meanwhile SDK 2.4 Rev 4 is available.

 

I have no idea where what is incompatible, missing, not working or wrong...

 

SDK Emulator has installed enough Certs... to run examples without big "magic"... only real devices need f%& Cert proper installed with your DUID from device(s).

Z300F is not comparable with Z300H...

As I have only seen 2 or 3 users with Z300F...

Look here... it is possible to have more older Firmware...

:)

https://developer.tizen.org/forums/general-support/sm-z300f

 

Btw...

You can try to follow rzr post about TM1 problem...

https://samsung.tizenforum.com/?topic=236.msg12672#msg12672

 

Best Regards

Tim Howie

Hi all,

Back with an update - today I successfully managed to load and run my Tizen app onto the Z3 (well, successful except for my Knox license not being properly activated, for unknown reasons, and I see to be unable to print messages to the console to easily trace the program...).

I'm not sure what I did differently, if anything. I did create new certificates and followed the instructions from the documentation in the IDE - which I'm fairly sure I followed everything in the same manner previously.

In particular, I followed the steps in the Certificate Guide from the Tizen IDE, performing the steps from the Creating new certificates, Permitting device to install applications, and Importing certificates steps.

Many thanks to all who took some time out to help me work towards a solution - I appreciate it!

Peter Wegner

Thanx for feedback.

 

Best Regards