Languages

Menu
Sites
Language
Launch multiple services within single TPK

All,

We are working on a device based on Tizen 2.1.

We are writing a bunch of native Tizen services that are being packaged into a single TPK. During installation of the TPK, the choice of which is the MainApp seems to be arbitrarily based on the order in which they appear in the manifest file. Additionally, we are finding that the services don't start up like they should.

I can reduce the list to a single service and have found that it consistently starts up not only during TPK installation but on every subsequent boot. Is it possible to have multiple services within a single TPK and have them all launch not only at TPK installation time but also during boot up?

Regards

Edited by: Brock Boland on 17 Mar, 2014 Reason: Paragraph tags added automatically from tizen_format_fix module.
List

Responses

3 Replies
john Smith
Hi, Normally service app running in background. And UI App running in foreground. These you can keep in a single package. For that follow https://developer.tizen.org/help/index.jsp?topic=%2Forg.tizen.native.appprogramming%2Fhtml%2Fapp_dev_process%2Fmultiple_project_dev_package.htm, After selecting reference, you create tpk file and try to run. You can able to get the sequence of running application.
Bihari
Hello, Does that mean that you can't have multiple services within a single TPK that are possibly not referenced by any particular UI application? Our TPK doesn't really have a UI app that is going to be run by the user, we want the service apps to start up automatically like we've seen other Tizen service apps do. I can confirm that with just a single service app in our TPK, things work as they should, it's dealing with the multiple's service apps thats causing us problems. The page you linked to talks about a single UI project and single service project. Regards
Bihari
Just for anyone else that's interested.. After looking further into how I wanted the services to start up, it tuned out that I wanted one service to start by default and do some work and then start the other services only when it was time. So we ended up using the AppControl manifest tag and the associated APIs to basically send a message to the system to start up the other services when we want them and this works great. Regards