Instructions 1

Download as pdf or txt
Download as pdf or txt
You are on page 1of 10

Barcode Handy Terminal

BHT-M60-QWG-A10N Difference Manual


Copyright © 2022 DENSO WAVE INCORPORATED
All rights reserved.
The copyright of this Reference Manual belongs to DENSO WAVE INCORPORATED.

BHT is trademarks of DENSO WAVE INCORPORATED.


The Bluetooth® is a trademark owned by its proprietor. DENSO WAVE uses Bluetooth wireless
technology under license.

All other products and company names mentioned in this manual are trademarks or registered trademarks of their
respective holders. In this manual, all of trademarks are not marked with ™ or ®.
Preface

This manual describes the software differences between BHT-M series and BHT-M60-QWG-A10N. The
differences in specifications described in this manual conform to the required specifications of Chinese NAL
certification.

Refer to the BHT Software User’s Manual for other information on how to handle software, the BHT Hardware
User’s Manual for basic usage of the BHT, and the API Reference Manual for software application development.
This manual applies to the OS versions described below.

Version Description BHT-M60-QWG-A10N


1st First issue 1.00.00

-i-
Contents
1. WLAN/Bluetooth ....................................................................................................................... 1
1.1. Toast display upon connection completion.................................................................... 1
1.2. Display confirmation dialog when turning ON/OFF with API ......................................... 1
2. Permission ................................................................................................................................ 3
2.1. Permission classification refinement in permission manager ....................................... 4
2.2. Changing the message on the permission dialog ......................................................... 5

- ii -
1. WLAN/Bluetooth
1.1. Toast display upon connection completion
If the WLAN/Bluetooth connection is successful, a toast appears indicating the connection is complete.

Connect WLAN successfully Connect Bluetooth successfully

1.2. Display confirmation dialog when turning ON/OFF with API


When turning WLAN/Bluetooth on/off from an app using the API, a confirmation dialog appears asking if you want to
allow the change. To accept the change, press the ALLOW button in the dialog. The ON/OFF status is not changed until
the ALLOW button is pressed. If you press the DENY button or tap outside the dialog, the dialog will close without
changing the ON/OFF status.

WLAN ON WLAN OFF Bluetooth ON Bluetooth OFF

Notes
If you call the API android.net.wifi.WifiManager.setWifiEnabled or android.bluetooth.BluetoothAdapter.enable/disable
and attempt to change the ON/OFF state of the WLAN/Bluetooth, as shown above, a confirmation dialog appears
asking if you want to allow the change. The API returns true when the dialog is displayed, but note that the ON/OFF
state is not changed until the ALLOW button in the dialog is pressed.
If there is an action that you want to execute after the ON/OFF state change, you need to wait for the user's dialog
operation. Therefore, get the status with android.net.wifi.WifiManager.isWifiEnabled or
android.bluetooth.BluetoothAdapter.isEnable before executing it.

-1-
Sample coding
When processing is executed with WLAN set to ON

WifiManager wm = (WifiManager) getApplicationContext().getSystemService(WIFI_SERVICE);


boolean enabled = false;

if (wm.setWifiEnabled(true)) { // Show dialog


for (int cnt = 0; cnt < 100; cnt++) { // Change count limit as needed
if (wm.isWifiEnabled()) { // Wait for user operation
enabled = true;
break;
}
try {
Thread.sleep(1000); // Change sleep time as needed
} catch (InterruptedException e) {
e.printStackTrace();
}
}
}

if (enabled) {
// Program the process you want to run
}

When processing is executed with Bluetooth set to ON

BluetoothAdapter ba = BluetoothAdapter.getDefaultAdapter();
boolean enabled = false;

if (ba.enable()) { // Show dialog


for (int cnt = 0; cnt < 100; cnt++) { // Change count limit as needed
if (ba.isEnabled()) { // Wait for user operation
enabled = true;
break;
}
try {
Thread.sleep(1000); // Change sleep time as needed
} catch (InterruptedException e) {
e.printStackTrace();
}
}
}

if (enabled) {
// Program the process you want to run
}

-2-
2. Permission
There are following changes about permission specifications for certain functions. See the table below for
applicable functions.

1. Changed permission manager to control individual permissons instead of permission groups. See 2.1
for details
2. Added the following description to the message in the permission dialog. See 2.2 for details
3. Modified the application behavior to exit if permissions are not granted in the permissions dialog at
application startup. *1
4. Changed the timing of permission checks at app startup. *1

━ point ━ Depending on application's specifications, some apps can be lauched even if some permissions are
missing at startup. Recommend that check the operation of each model and prepare a kitting manual.

Permission Permission name Description


group
Calendar READ_CALENDAR read calendar events and details
WRITE_CALENDAR add or modify calendar events and send email to guests without
owners’ knowledge
Call logs READ_CALL_LOG read call log
WRITE_CALL_LOG write call log
PROCESS_OUTGOING_CALLS reroute outgoing calls
Camera CAMERA take pictures and videos
Contacts GET_ACCOUNTS find accounts on the device
WRITE_CONTACTS modify your contacts
READ_CONTACTS read your contacts
Microphone RECORD_AUDIO record audio
Phone CALL_PHONE directly call phone numbers
CONFERENCE_CALL make conference call
READ_PHONE_STATE read phone status and identity
ADD_VOICEMAIL add voicemail
SMS/MMS READ_SMS read your text messages(SMS)
RECEIVE_SMS receive text messages(SMS)
SEND_SMS send and view SMS messages
READ_MMS read your text messages(MMS)
RECEIVE_MMS receive text message(MMS)
RECEIVE_WAP_PUSH receive text messages(WAP)
Storage WRITE_EXTERNAL_STORAGE modify or delete the contents of your shared storage
READ_EXTERNAL_STORAGE read the contents of your shared storage
ACCESS_MEDIA_LOCATION read locations from your media collection

━ point ━ It is recommended that the authority necessary for the work be granted when the terminal is kitted.
Also recommend that check the operation of each model and prepare a kitting manual.

-3-
2.1. Permission classification refinement in permission manager
The categories of permission that can be specified in the permission manager for specific functions are more
detailed.

Ex)

BHT-M60-QW-A10N BHT-M60-QWG-A10N

-4-
2.2. Changing the message on the permission dialog
In a permission dialog message that appears at application startup for a specific function as follows:
Detailed permission information has been added.

Function

Detailed permission

━ point ━ Depending on application's specifications, different permission dialogs will be displayed.


Recommend that check the operation of each model and prepare a kitting manual.

-5-
Barcode Handy Terminal / 2D Code Handy Terminal
BHT-M60-QWG-A10N

Difference Manual

1st Edition, September 2022

● Duplication or reproduction of this manual in part or in full is prohibited without prior consent.
● The contents of this manual may be subject to change without prior notice.
● DENSO WAVE accepts no responsibility for any damage arising out of use of this manual.

-6-

You might also like