Differences

This shows you the differences between two versions of the page.

--- xw_home_screen [2015/01/21 00:49]
FGraham [Auto-Launching HomeScreen application]
+++ xw_home_screen [2022/07/26 23:15]
waltminer Obsolete - delete page
@@ Line 1: / Line 1: @@
 ====== Home Screen ======
 ===== Summary  =====
@@ Line 12: / Line 13: @@
-Watch Home Screen video soon.
+Watch the [[https://download.automotivelinux.org/POC/Xwalk_PoC_Videos/Homescreen%20XWALK%20POC.mp4|video]].
-Access the Design Requirements Document (DRD) soon.
+Access the [[https://download.automotivelinux.org/POC/Xwalk_PoC_DRDs/DRD_XWalk_Homescreen.xlsx|Design Requirements Document (DRD)]].
-Access the Source code soon.
-Download the Widget file soon.
+Access the [[https://github.com/PDXostc/homescreen|Sources code on GitHub]].
+Download the [[https://download.automotivelinux.org/POC/Xwalk_PoC_RPM_WGT/HomeScreen-0.0.1-1.i686.rpm|RPM Package Manager (RPM) file]].
 ===== What the app does  =====
@@ Line 33: / Line 32: @@
 In all application instances, a simple touch is all that is required to launch a given application.
-===== Technical Details  =====
-The sections below are taken from directions for what is known as the September Release of Tizen 3.0 IVI.  The current Tizen release is dated 2014.01.14, and may require some adjustment.
-==== Installation Prerequisites  ====
-The following installation directions take the base Tizen image and install needed supporting software.
-==== Installation Prerequisites  ====
-The following installation directions take the base Tizen image and install needed supporting software.
-==== Modify Weston  ====
-For correct resolution setup and orientation modify /etc/xdg/weston/weston.ini as you have your display connected to HDMI port, modify [output] section, like the following:
-     [output]
-     name=HDMI1
-     mode=1280x720@60.0
-     transform=90
-     [output]
-     name=HDMI2
-     mode=off
-     [output]
-     name=HDMI3
-     mode=1280x720@60.0
-     transform=90
-     [output]
-     name=DP1
-     mode=1920x1080
-     transform=90
-     [output]
-     name=VGA1
-     mode=off
-Note: This config is created as common for both NDIS166 and NUC. (HDMI1 - NUC HDMI1 output, HDMI2 - NUC HDMI2 and NDIS166 DVI output, HDMI3 - NDIS166 HDMI output, VGA - NDIS166 VGA output)
-In [core] section, disable ICO Homescreen (ico_plugin_loader.so) and load desktop-shell.so:
-  [core]
-     #modules=ico_plugin_loader.so
-     modules=desktop-shell.so
-Reboot NDiS166.
-==== Auto-Launching HomeScreen application  ====
-For automatic startup of HomeScreen application create launcher shell script /usr/lib/systemd/system/poc_launcher.sh, that will keep checking until HomeScreen app is up and running (has pid), then break the loop and finish/close the script:
-  #!/bin/bash
-    # extra wait time before first start-up
-    # this is a workaroud for some strange behaviour of webkit/WebProcess(?)
-     <nowiki># note from testing: range 6 to 12 is unsafe and will break webkit/webProcess(?) behaviour (reason unknown)
-    sleep 2
-    # start intelPoc10.HomeScreen app
-    /usr/bin/wrt-launcher -s intelPoc10.HomeScreen
-    # check if app is up and running after 10s, if not try to start it again
-     sleep 10
-     while true; do
-         proc=`ps aux | grep i[n]telPoc10.HomeScreen` # [] used to exclude grep itself
-         set -- $proc
-         if [ -z "$2" ]; then
-             # the application is not running - start it again
-             /usr/bin/xwalk-launcher -s JLRPOCX001.HomeScreen
-         else
-             break
-         fi
-         sleep 5 # check every 5 second
-     done
-and make it executable: chmod +x /usr/lib/systemd/system/poc_launcher.sh
-Create systemd's init script /usr/lib/systemd/system/poc.service with the following content:
-  [Unit]
-     Description=Intel POC HomeScreen application
-     After=ac.target
-     [Service]
-     ExecStart=/usr/lib/systemd/system/poc_launcher.sh
-     [Install]
-     WantedBy=graphical.target
-Auto-enable it by running (as root):
-     systemctl enable poc
-Note: As you haven't installed wgt applications yet, this service will fail to start HomeScreen application after reboot for now.
-==== Instructions for debugging WRT Apps (installation, removal, and deployment)  ====
-Tizen IVI WRT applications are built into widget ('.wgt') files for deployment (a format based on the W3C widget specification, see http://www.w3.org/TR/widgets/ for more information). Once you have built or received the widget files for one or more applications that you wish to deploy and run, the next step is to copy them onto the target device. Common options for this would be tools like scp/sftp (in a Linux/Unix environment), FileZilla (Windows and Mac) or Cyberduck (Mac).
-Once the .wgt files have been transferred to the target machine, they may be installed, launched and uninstalled.
-To get a list of currently installed applications, use the following command from a terminal (or remote shell/ssh session) on the target hardware (log in as root with the password tizen):
-     root:~> xwalkctl -l
-This will produce output similar to the following:
-|**Application ID**     | **Application Name**|
-|JLRPOCX000.HelloTizen  |Hello Tizen|
-|JLRPOCX001.HomeScreen  |Home Screen|
-|JLRPOCX007.News        |News       |
-|JLRPOCX008.HVAC        |HVAC       |
-|JLRPOCX011.Fingerprint |Fingerprint|
-|JLRPOCX015.Navigation  |Navigation |
-|JLRPOCX016.MOSTAudio   |MOST AUDIO |
-|JLRPOCX030.Browser     |DNA Browser|
-|JLRPOCX033.Dashboard   |Dashboard  |
-|JLRPOCX034.NFC         |NFC        |
-|JLRPOCX035.Weather     |Weather    |
-If the application you wish to install is not already installed, simply enter (using intelPoc16.HVAC.wgt as an example):
-  root:~> xwalkctl -i filename.wgt
-If successful, you should see output such as the following:
-[0120/160824:INFO:signature_validator.cc(218)] Verifying widget signature file.
-[0120/160824:INFO:signature_validator.cc(223)] No signed signature in the package.
-[0120/160824:ERROR:package_query.cc(69)] Invalid count (0) of the AIL DB records for the app id JLRPOCX001.HomeScreen
-[0120/160824:ERROR:package_query.cc(69)] Invalid count (0) of the AIL DB records for the app id JLRPOCX001.HomeScreen
-[0120/160824:INFO:xwalk_package_installer.cc(155)] Converting manifest.json into JLRPOCX001.HomeScreen.xml for installation. [DONE]
-[0120/160824:INFO:xwalk_platform_installer.cc(203)] UID of installation : 5000
-__ps_process_metadata_parser
-[0120/160824:INFO:xwalk_package_installer.cc(510)] Installed application with id: JLRPOCX001.HomeScreen to /home/app/.config/xwalk-service/applications/JLRPOCX001.HomeScreen successfully.
-If unsuccessful, you may see errors such as 'invalid widget package', 'privilege level violation' or, if the application is already installed (and its widget file was built with a different signature than the one you wish to install), 'invalid signature'. The first two errors are out of scope for this document.
-If you see 'invalid signature', and the widget file has to your knowledge been created with a valid signature, the likely cause is a conflict between the signature of the currently installed version and that of the new version. Though both signatures may be valid, the system treats the upgrade of an existing package with a different signature as a security violation. To work around this issue, simply uninstall the application and subsequently install the new version:
-  root:~> xwalkctl -u JLRPOCX000.HelloTizen      <-- note: use the App ID when
-  un-installing and the full widget filename when installing
-If the uninstall is successful, you should see output like the following:
-__ps_process_metadata_parser
-Refer to installation instructions above for the subsequent installation steps.
-In order to launch and run an installed application, issue the following command with the application's App ID as an argument:
-  root:~> xwalk-launcher  JLRPOCX000.HelloTizen
-You should see the application start and run on the target device.
-To launch the application in debug mode, add the '-d' flag:
-  root:~> xwalk-launcher -d  JLRPOCX000.HelloTizen
-The port number referenced is a random high port which allows one to connect to the target device with a web browser using a URL of the form:
-  http://&lt;ip address or name of target device>:9888
-**For example:**
-  http://192.168.1.223:9888
-Once connected, you should see a single link in the upper right of the resulting web page, e.g.:  Then click the link with your app listed.
-Clicking that link will launch Webkit Web Inspector, a set of web development tools that should look familiar to users of Firefox Firebug or Chrome Dev Tools. Click the 'Console' icon in the toolbar to go to the Javascript console. Press ctrl-R, or type:
-  window.location.reload();
-...to reload the application in order to display the startup/initialization functions associated with the app (since the app has already started by the time the debug interface is available).
-To kill all running web application, issue the following command:
-  root:~> pkill xwalk

Automotive Linux Wiki

User Tools

Site Tools

Differences

Page Tools