User's Manual

Document:
TBD
Page:
20 of 42
ENGINEERING
Documentation
Revision:
1.6
Date:
24-May-17
Title:
TND540 Requirement
Proprietary and Confidential
This document contains confidential and property information which belongs to Rand McNally, Inc. This
document may not be copied, reproduced, or transmitted to others in any manner, nor may any use of the
information on this document be made, except for the specific purposes for which it is transmitted to the
recipient without prior written consent of Rand McNally, Inc.
o TKIP
o AES
● EAP
o LEAP
o PEAP
BT Profiles
Bluetooth profiles supported
Bluetooth Core Specification Version 4.0
Bluetooth Power Class 2
Bluetooth Profiles:
● RFCOMM 1.1
● AVDTP 1.2
● AVCTP 1.4
● GAVDP 1.2
● HFP 1.6
● A2DP 1.2
● AVRCP 1.5
● OPP 1.1
● SPP 1.2
OS Customization
1. The OS must not include Google Mobile Services
2. The OS shall use a common Release certificate and keystore,
which will be shared between RM and ODM
3. The OS shall include multiple apps, provided by RM, to be
preinstalled in the system partition. The list of apps may
change during development; following is an initial set:
3.1 RMS (RM Services)
3.2 RM Launcher (should be used as the default
launcher/Home in the OS)
3.3 RM Setup (onboarding & user-settings)
3.4 GPS app
4. The OS shall have the Android statusbar disabled and hidden
at all times.
4.1 Android notifications should not be visible or accessible
to the user
5. The OS shall have the Recent Apps button in the Android
navbar hidden at all times.
6. To support RM’s initial user-setup software (“onboarding”),
the OS shall broadcast the intent
“android.intent.action.BOOT_COMPLETED” in the
following scenarios:
6.1 First boot out of the box
9.
PDF 檔案使用 "pdfFactory Pro" 試用版本建立 www.pdffactory.com