[ABS] events: change method of launching app

After discussion with Aleksandr Sapozhnik we agreed that lockscreen
should not verify application launch request result, since its primary
task is to unlock screen, not launching application. Moreover there is
no guideline how lockscreen should handle failed launch requests.

Current logic has been modify in following manner:
1. If event do not support launching application or any error
   occured during launching, lockscreen will unlock immideatly
2. If app_control is launched successfully, lockscreen wait until
   APP_CONTROL_RESULT_APP_STARED or APP_CONTROL_RESULT_CANCELED events
   appear and unlock.

Issues: this way of unlocking do not enforce any synchronization method, so
        lockscreen may unlock before launched application appear.

Reference: submit/tizen/20160504.080735
Commit id: eb4ce69fdfb07df471ce2f41f62b347d6d94e840
Requested by: l.stanislaws@samsung.com
SDK rootstrap version: 20160503_2

diff --git a/org.tizen.lockscreen-0.1.0-arm.tpk b/org.tizen.lockscreen-0.1.0-arm.tpk
new file mode 100644 (file)
index 0000000..bd0ec3e
Binary files /dev/null and b/org.tizen.lockscreen-0.1.0-arm.tpk differ

diff --git a/org.tizen.lockscreen-0.1.0-i386.tpk b/org.tizen.lockscreen-0.1.0-i386.tpk
new file mode 100644 (file)
index 0000000..929317b
Binary files /dev/null and b/org.tizen.lockscreen-0.1.0-i386.tpk differ

diff --git a/packaging/org.tizen.lockscreen.spec b/packaging/org.tizen.lockscreen.spec
new file mode 100644 (file)
index 0000000..d419509
--- /dev/null
+++ b/packaging/org.tizen.lockscreen.spec
@@ -0,0 +1,44 @@
+Name:       org.tizen.lockscreen
+#VCS_FROM:   profile/mobile/apps/native/lockscreen#eb4ce69fdfb07df471ce2f41f62b347d6d94e840
+#RS_Ver:    20160503_2 
+Summary:    Lockscreen app
+Version:    0.1.0
+Release:    1
+Group:      Applications/Core Applications
+License:    Apache-2.0
+Source0:    %{name}-%{version}.tar.gz
+
+BuildRequires:  pkgconfig(libtzplatform-config)
+Requires(post):  /usr/bin/tpk-backend
+
+%define internal_name org.tizen.lockscreen
+%define preload_tpk_path %{TZ_SYS_RO_APP}/.preload-tpk 
+
+%ifarch i386 i486 i586 i686 x86_64
+%define target i386
+%else
+%ifarch arm armv7l aarch64
+%define target arm
+%else
+%define target noarch
+%endif
+%endif
+
+%description
+This is a container package which have preload TPK files
+
+%prep
+%setup -q
+
+%build
+
+%install
+rm -rf %{buildroot}
+mkdir -p %{buildroot}/%{preload_tpk_path}
+install %{internal_name}-%{version}-%{target}.tpk %{buildroot}/%{preload_tpk_path}/
+
+%post
+
+%files
+%defattr(-,root,root,-)
+%{preload_tpk_path}/*