83
Device power manager tasks
To create a
power manager
task, click on the
button then click on the
+
button.
The possible
power manager
task profiles are:
Very highly optimized
,
Highly optimized
.
It is possible to create several
power manager
tasks within the same day. The
power manager
tasks are stored into an ICAL format in the
secure.power_manager_calendar
user preference.
Value example (ICAL format):
BEGIN:VCALENDAR
VERSION:1.0
BEGIN:VEVENT
SUMMARY:Standby Task 1
X-POWER-MANAGER-LEVEL:MIN
DTSTART:20230303T200000
DTEND:20230304T080000
RRULE:FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR,SA,SU;UNTIL=20230403T235959
END:VEVENT
END:VCALENDAR
☛
During the device standby, the configuration upgrade through TFTP (DHCP/code 66) is effective but the associated information message
cannot be seen on the screen.
☛
During the device standby, the device configuration update by USB storage device injection, the APK installation by USB storage device
injection and the operation system upgrade by USB storage device injection keep supported. Setting the
persist.sys.power-
manager.level.low.externalstorage.copy.enable
user preference to
false
prevents the USB storage device injection to work during the device
standby.
☛
During the device standby, at any time, making a short press on the
system button
allows to wake up automatically the device and exit the
kiosk mode
.
☛
During the device standby with the VERY HIGHLY OPTIMIZED profile, by default, touching the screen does not allow to wake up automatically
the device. To work around, set the
persist.sys.power-manager.level.min.hid.pointer-event.enable
user preference to
true
. After a tap on the
screen, if there is no user activity during the
persist.sys.power-manager.level.min.screen-off-timeout
(by default, sixty seconds), the device
returns to
Device Sleep
mode. For further information refer to the chapter §
Power manager and Screen Saver modes
.
☛
It is not recommended to keep two different activated Apps running with their own
Power Manager
strategy else the
Power Manager
task of the
end-user App could not behave as expected.
☛
The
persist.sys.power-manager.device-sleep.level.default
allows to set the
Power Manager
profile that requested by the App: if its value is
min
(default value), the
Very highly optimized
value is applied for the
power manager
task requested by the App; if its value is
low
, the
Highly
optimized
value is applied for the
power manager
task requested by the App.
☛
In case, two
power manager
tasks with different profiles (i.e
Very highly optimized
and
Highly optimized
) are concurrents, meaning one
requested by the App and one requested by the OS, the
power manager
task requested by the OS is priority.
☛
In case, two
power manager
tasks generated in this pane, with different profiles (i.e
Very highly optimized
and
Highly optimized
) are
concurrents, meaning one requested by the App and one requested by the OS, the
Very highly optimized
power manager
task is priority.
☛
When the end time of the
power manager
task is lower or equal to its start time, the
power manager
task runs automatically till the day after.
Summary of Contents for TAB10b
Page 1: ...User manual TAB10b 9 10 18 001A TAB10b 8 30...
Page 5: ...5 Part I Description and installation...
Page 10: ...10 1 3 1 Device dimensions...
Page 13: ...13...
Page 26: ...26 Part II System con guration...
Page 42: ...42 This message is then displayed until the device is rebooting automatically once...
Page 50: ...50 Part III Applicative user interface...
Page 52: ...52 Part IV Administration console user interface...
Page 63: ...63...
Page 95: ...95 Part V Technical information...
Page 99: ...99 5 3 Antenna return loss This is the return loss diagram for the WIFI Bluetooth antenna...
Page 101: ...101 Part VI Contacts...
Page 103: ...103 Part VII Appendix...