14
1.4.2
AOSP device mode
The
Qeedji System
service allows to configure the
AOSP device mode
as soon as the device has started. It is handled thanks to the
persist.sys.device_mode
system property,
used by the
SystemUI
and
Launcher3
AOSP services.
Two values are possible for the
persist.sys.device_mode
system property:
native
(default value): thanks to AOSP menu, the user can, whenever he wants, stops the APK, returns to the AOSP home screen, launches another APK, access to AOSP
func ons like, for example, the
Back
bu on or the
Se ngs
applica on.
kiosk
: all the AOSP user interfaces are unavailable. However the AOSP virtual keyboard remains available.
☛
Note for developers: if the
persist.sys.device_mode
system property value is invalid or if it does not exist, the default AOSP device mode is
native
. If the
persist.sys.device_mode
system property value is
kiosk
, the
SystemUI
service inhibits the
system bars
and the
Launcher3
service hides the
AllApps
view and the
Op onsPopupView
dialog box.
The
persist.sys.device_mode
system property can be changed by using the configura on script:
native
:
setDeviceModeNative(); /* default mode */
//setDeviceModeKiosk();
kiosk
:
//setDeviceModeNative(); /* default mode */
setDeviceModeKiosk();
For further informa on, refer to the
.
¹
To be launched automa cally in kiosk mode, the applica on requires a subscrip on to the event ACTION_BOOT_COMPLETED. In this case, it is recommended to have only one APK
with this subscrip on. For further informa on, refer to
h ps://developer.android.com/reference/android/content/Intent#ACTION_BOOT_COMPLETED
. In case no APK is subscribed
to the event ACTION_BOOT_COMPLETED, the Qeedji wallpaper ² is displayed.
²
A next release will allow to load a custom wallpaper.