View Single Post
Posts: 839 | Thanked: 3,386 times | Joined on Mar 2009
#2
I made testing with own hildon-desktop and I found it ultimately handy to kill system's hildon-desktop and then start non-installed version on hildon-desktop.
i.e.

as root
Code:
killall hildon-desktop ; /etc/osso-af-init/launch-wrapper.sh stop hildon-desktop /usr/bin/hildon-desktop
killall hildon-desktop ; /etc/osso-af-init/launch-wrapper.sh stop hildon-desktop /usr/bin/hildon-desktop
killall hildon-desktop ; /etc/osso-af-init/launch-wrapper.sh stop hildon-desktop /usr/bin/hildon-desktop
killall hildon-desktop ; /etc/osso-af-init/launch-wrapper.sh stop hildon-desktop /usr/bin/hildon-desktop
killall hildon-desktop ; /etc/osso-af-init/launch-wrapper.sh stop hildon-desktop /usr/bin/hildon-desktop
#And then start own version
(as user)
Code:
maemo-invoker ~/hildon-desktop.launch
I realized that if phone has --set-rd-flags=no-lifeguard-reset this will work. But if it is not in RD-mode, phone will reboot when hildon-desktop dies.

My questions
* How system decides that hildon-desktop is a critical application?
*How I can see which applications are critical?
*How I can change list of critical applications?

Consider my questions as I would make own operating system based on Maemo5.
 

The Following 3 Users Say Thank You to AapoRantalainen For This Useful Post: