wizarPOS - User contributions [en]

How to Understand Master Key and Session Key in WizarPOS Systems

2024-01-16T01:31:36Z

Hans:

== Master Key ==
* In a hierarchy of Key Encrypting Keys (KEKs) and Transaction Keys, the Master Key represents the highest level of KEK.
* Distribution Method: Master Keys are typically distributed using physical methods, such as key loading devices, PSAM card or smart card.
* Replacement: They are replaced using the same methods whenever compromise is suspected or confirmed.
== Transaction Key (Session Key) ==
* A Transaction Key, often referred to as a Session Key, Data Key, communications key, or working key, is used to cryptographically process transactions.
* In scenarios where different cryptographic functions are used, each function might employ a variant of the Transaction Key.
== Key Hierarchy ==
* '''Two-Layer Hierarchy:'''
** There are two type of keys: Master Key and Session Key.
** In the devices, the highest-level KEK is known as the Master Key.
** The Master Key encrypts Transaction Keys (Session Keys) directly.
** Session Keys: These include PIN keys (for encrypting PIN blocks), MAC keys (for MAC calculations), and data keys (for encrypting other data).
** Each Master Key support three slots for Session Keys internally.
* '''Three-Layer Hierarchy:'''
** There are three type of keys: Transport Key, Master Key and Session Key.
** Highest Level: Referred to as a Transfer/Transport Key.
** Middle Level: Known as a Master Key, which is encrypted and updated by Transport Key.
** Lowest Level: Called a Session Key, which is encrypted and updated by the Master Key.
== Groups of Keys ==
* The devices support 50 slots of Master/Session Keys.
== Key Injection ==
* '''Master Key (Two-Layer) & Transfer/Transport Key (Three-Layer):''' For injecting these keys, refer to [[How to Remotely Inject Test Keys (Master Key or DUKPT Key) into a Terminal]] or [[How to Use TMK Delivery System for KeyLoader POS and Master POS]].
* '''Session Key & Master Key (Three-Layer):''' These can be injected using our SDK. Refer to the PINPad section of our SDK for detailed instructions.
== Usage ==
* For information on how to utilize these keys, please refer to the PINPad description in our SDK.

File:2023-12-25 14-47.png

2023-12-26T01:52:38Z

Hans:

Enviroment

2023-12-21T03:20:03Z

Hans:

== [[Hardware/Repair]] ==
=== [[How to Recover a Terminal from Tamper Status]] ===

=== [[How to Understand Trigger Events in Terminals]] ===
=== [http://ftp.wizarpos.com/advanceSDK/TerminalRemoteActivationManual.pdf How remote activate from tamper status] ===
=== [[Recommended TF Card]] ===

== [[Printer]] ==
=== [[How to check the printer on the terminal]] ===
=== [[How to print out character sets not supported by the POS printer]] ===
=== [[How to call Bluetooth printer service of the terminal]] ===
=== [[How to use POS printer to print image]] ===
=== [[How to use POS printer to print QR code]] ===
=== [[About the performance of printing HTML function]] ===
=== [[About the print performance of the terminal]] ===
=== [[How to print by external Epson usb printer(TM-T88IV)]] ===
=== [[How to replace font file(*.ttf) of printing html function]] ===
=== [[Java API usage for Printer]] ===
=== [[Why is there a blank line between two image printing continuously?]] ===
=== [[An android demo for using print in JavaScript]] ===
=== [[How to check status out of paper]] ===

== [[USB/Serial Port]] ==
=== [[USB Driver Download]] ===
=== [[UU cable Driver Download]] ===
=== [[How to install serial port driver for production Q1/Q2]] ===
=== [[How to install serial port driver for production terminal in Linux]] ===
=== [[About the development of serial port of the terminal]] ===
=== [[How to add udev rules for USB debugging in Linux]]===
=== [[Impact of terminal sleep on serial port]]===
=== [[When the serial port cable is disconnected, close/open the serial port again]]===
=== [[How to use accessory mode]]===
=== [[How to detect UU cable connnected programmatically]]===
=== [[Demo for Control FAN by using serial port]]===
=== [[How to list the connected USB device]]===
=== [[How to use accessory agent service between D22 and Q3]]===

== [[Firmware]] ==
=== [[How to update firmware]] ===
=== [[What's the meaning of firmware package]] ===
=== [[What is the difference between engineer mode terminal and user mode terminal]] ===
=== [[How to use poshomesettings.xml]] ===
=== [[How to use possystemsettings.xml]] ===
=== [[How to prevent visitors from uninstalling applications by mistake]] ===
=== [[Error message - agent stopped]] ===
=== [[Security lock has been set, but forget the password]] ===
=== [[How to use the buttons of Q1 in the application]] ===
=== [[Notes on application adaptation to Q1 (4G)]] ===
=== [[How to customize boot logo and boot animation]] ===
=== [[How to set wallpaper]] ===
=== [[How to enter special mode when starting]] ===
=== [[Latest browser for Q-series]] ===
=== [[How many external servers and services that the firmware usually access]] ===
=== [[How to get different firmware mode of terminal]] ===
=== [[How to write customer SN]] ===
=== [[How to enable wake up by touch screen]] ===
=== [[How to set user system property]] ===
=== [[How to enable/disable MTP]] ===
=== [[How to update WebView on POS]] ===
=== [[How to disable TF card and pendriver file explorer]] ===
=== [[Demo for screen on/off]] ===

== [[Settings Menu]] ==
=== [[How to reset factory data]] ===
=== [[Introduction to common menus of Settings]] ===
=== [[How to view the certificate list on the terminal]] ===
=== [[Introduction to Merchant Self Test of Settings]] ===
=== [[How to use terminal merchant self test to test specified networks]] ===
=== [[How to change system language]] ===
=== [[How to login the terminal as admin]] ===
=== [[How to change the login password of terminal administrator]] ===
=== [[How to update the terminal time]] ===
=== [[How to change the terminal time zone]] ===
=== [[How to enable user role to control accessing settings menu]] ===
=== [[How to update user role password by API]] ===
=== [[How to disable bluetooth/wifi in terminal]] ===
=== [[How to enable/disable autotimezone in terminal]] ===
=== [[How to enable/disable autotime in terminal]] ===
=== [[How to set sleep of display in terminal]] ===
=== [[How to grant Accessibility permission automatically]] ===
=== [[How to remove the security lock when starting the terminal?]] ===
=== [[How to launch the sub menu of settings from your application?]] ===
=== [[How to set language by API]] ===

== [[Battery/Power]] ==
=== [[Why do the four LEDs of the charging indicator light flash at the same time]] ===
=== [[For not be powered during a long period (more than 6 month)]] ===
=== [[On what battery% does the Q2 turn off]] ===
=== [[Time for charge/discharge]] ===
=== [[Counter Mode of Q3]] ===
=== [[How to turn off by API]] ===

== [[SIM/Ethenet/WIFI]] ==
=== [[How to turn off the portable hotspot of the terminal]] ===
=== [[How to turn on the portable hotspot of the terminal]] ===
=== [[How to obtain IMEI of the terminal]] ===
=== [[How to obtain MEID of the terminal]] ===
=== [[What modem bands does the wizarPOS terminal support]] ===
=== [[SIM card signal problem]] ===
=== [[SIM card network problem]] ===
=== [[Error while searching for networks]] ===
=== [[How to check e-SIM status?]] ===
=== [[Ethernet support]] ===
=== [[How to set the communication mode of the terminal]] ===
=== [[Why the USSD menu not displaying]] ===
=== [[How to set APN]] ===
=== [[How to set preferred network type of the cellular network by API]] ===
=== [[How to set static Ethernet parameters by API]] ===
=== [[How to enable/disable mobile data]] ===
=== [[How to query and set network operators by API]] ===
=== [[Softsim&Data Plan Activation]] ===
=== [[How to enable/disable ethernet]] ===

== [[Certificate]] ==
=== [[How to apply app certificate]] ===
=== [http://ftp.wizarpos.com/AppCertificateBlackWhitePermissionRuls.pdf How to restrict some APP installing(BlackWhitePermission)] ===
=== [[How to install CA certificate]] ===
=== [[How to clear terminal certificate]] ===
=== [[Why I can not find the imported certificate? ]] ===

== [[Card]] ==
=== [[How far is the reading distance of contactless card]] ===
=== [[What's the buffer size of NFC reader]] ===
=== [[Java API usage for contactless CPU card]] ===
=== [[Java API usage for Felica card]] ===
=== [[Java API usage for contactless Mifare card]] ===
=== [[PSAM card, Code:-6 com.cloudpos.DeviceException: Operation error! Error code = -1, Error message = Operation not permitted.]] ===
=== [[Guide to the best card tap position for front contactless terminal]] ===

== [[FingerPrint]] ==
=== [[How to use fingerprint module interface in wizarPOS terminal]] ===
=== [[Image resolution(DPI) of fingerprint module]] ===
=== [[Data type/template format of fingerprint module]] ===

== [[Other development]] ==
=== [[How to set ANDROID_HOME]] ===
=== [[How to sign app]] ===
=== [[How to install app to POS]] ===
=== [https://developer.android.com/training/basics/firstapp/ Create your first app in android studio] ===
=== [[How to get log from terminal]] ===
=== [[Install APK error: An existing package by the same name with a conflicting signature is already installed]] ===
=== [[How to get a full log without a filter]] ===
=== [[How to get the current location of the terminal]] ===
=== [[How to make the application use the terminal's photographing function]] ===
=== [[APKs for testing]] ===
=== [[Simple ADB command list]] ===
=== [[Advance Samples]] ===
=== [[How to import SDK in C# program]] ===
=== [[How to use PhoneStateListener to get SignalStrength]] ===
=== [[D3 Demos]] ===
=== [[How to customize the graphical user interface of POS when inputting PINPAD]] ===
=== [[Demo for Kiosk Mode]] ===
=== [[How to block status bar]] ===
=== [[Using system API to make full screen]] ===
=== [[Use the API provided by Android to make full screen]] ===
=== [[Disable home key]] ===
=== [[How to block and get power button]] ===
=== [[How to obtain terminal information (brand, manufacturer, product model, etc.)]] ===
=== [[How to save files on device storage]] ===
=== [[How to set the application as the default launcher]] ===
=== [[How to get the firmware(OS) version]] ===
=== [[How to get firmware and EMV kernel version]] ===
=== [[How to use TLSv1.3]] ===
=== [[How to run automatically after installing]] ===
=== [[Secure Connections]] ===
=== [[How to use AnyDesk]] ===
=== [[How to export the APP's db file to SD card]] ===
=== [[How to immigrate payment application to Q2Premium]] ===
=== [[How to run automatically after terminal boot]] ===
=== [[How to integrate SDK aar file to flutter APP]] ===
=== [[How to call AIDL interface]] ===

== [[TMS/Wizarview]] ==
=== [http://ftp.wizarpos.com/advanceSDK/WizarView_V4.pdf TMS Overview] ===
=== [http://ftp.wizarpos.com/advanceSDK/wizarView_UserManual_generalv2.8.pdf TMS User Guide] ===
=== [[How to register terminal to WizarView]] ===
=== [[How to accept parameter files downloaded from TMS]] ===
=== [[How to operate when "User Locked"]] ===
=== [[How to apply for a WizarView account]] ===
=== [[How to batch import terminals]] ===
=== [[How to remove the terminals associated with an application from the configuration]] ===
=== [[How to remove an application from a device using TMS]] ===
=== [[Error codes of TMS and the agent]] ===
=== [[How many ports and IP used by TMS]] ===
=== [[When does the terminal update the applications from TMS]] ===
=== [[What's the meaning of silent, prompt and market when configure app]] ===
=== [[How to apply for an RMA account]] ===
=== [[How to update firmware remotely]] ===
=== [[How to push an APK to a specific device type]] ===
=== [[How to set Agent Working Mode]] ===
=== [[How to control the prompt installing apk configured in TMS to install]] ===
=== [[How to enable/disable wizarviewagent network using]] ===
=== [[How to push apps to a batch of terminals in different groups by tag]] ===

== [[Key Injection]] ==
=== [[How to inject test key(master key or DUKPT key) remotely]] ===
=== [[What is DUKPT]] ===
=== [[What is the master key and session key]] ===

=== [[TMK Deliver System Usage（For KeyLoader POS/Master POS）]] ===
=== [[Remote Key Injection]] ===

=== [[Key Loader POS1 shows serial rcv timeout]] ===
=== [[Update key failed, import TMK: -74496]] ===

== [[EMV]] ==
=== [[What's Tag91]] ===
=== [[What's CAPK]] ===
=== [[How to set issuer script]] ===
=== [[Sometimes when try for chip, contactless is detecting first, how to solve this problem?]] ===

== [[Cryptography]] ==
=== [[Padding]] ===

How to Recover a Terminal from Tamper Status

2023-12-21T02:46:15Z

Hans:

== Overview ==

This guide explains the process for recovering a Smart POS terminal that has entered a tamper status. This status can only be resolved by the terminal vendor (WizarPOS). Unauthorized attempts to recover the terminal are not permitted.

== Steps for Recovery ==

1. '''Token Generation During Booting:''' When the terminal boots, it generates a token. This token is stored in the TF card.

2. '''Sending the Token File:''' You need to retrieve this token file and email it to WizarPOS for recovery. Use the following details for your email:

* '''Subject:''' "Request for Device Recovery from Tamper Status"
* '''Recipient:''' techsupport@wizarpos.com (and include your WizarPOS sales contact in CC)
* '''Email Body:''' Include your Company or Group name as registered in our Terminal Management System (TMS). Note: Without this information, we cannot process your request.
* '''Attachment''': Attach the token file from the TF card.
3. '''Choose the Tamper Reason:''' Indicate the reason for tampering in your email. Options include:

* Received the device tampered from WizarPOS
*
* Tampered during repair
*
* Tampered due to falling or dropping

4. '''Receiving the Signature File:''' After we receive and approve your request, we will respond with a signature file attached (.sig file).

5. '''Final Recovery Step:'''

* Place the .sig file in the same folder as the token file on the TF card.
* Reboot the terminal. Ensure that both the token and signature files are in the same folder for successful recovery.

== Note ==

This process is exclusive to authorized personnel. Unauthorized attempts to recover a tampered terminal are strictly prohibited and may result in further complications.</big>

Enviroment

2023-12-19T04:26:39Z

Hans: /* How the terminal can be recovered from tamper status */

== [[Hardware/Repair]] ==
=== [[How to Recover a Terminal from Tamper Status]] ===

=== [[What is terminal being triggered]] ===
=== [http://ftp.wizarpos.com/advanceSDK/TerminalRemoteActivationManual.pdf How remote activate from tamper status] ===
=== [[Recommended TF Card]] ===

== [[Printer]] ==
=== [[How to check the printer on the terminal]] ===
=== [[How to print out character sets not supported by the POS printer]] ===
=== [[How to call Bluetooth printer service of the terminal]] ===
=== [[How to use POS printer to print image]] ===
=== [[How to use POS printer to print QR code]] ===
=== [[About the performance of printing HTML function]] ===
=== [[About the print performance of the terminal]] ===
=== [[How to print by external Epson usb printer(TM-T88IV)]] ===
=== [[How to replace font file(*.ttf) of printing html function]] ===
=== [[Java API usage for Printer]] ===
=== [[Why is there a blank line between two image printing continuously?]] ===
=== [[An android demo for using print in JavaScript]] ===
=== [[How to check status out of paper]] ===

== [[USB/Serial Port]] ==
=== [[USB Driver Download]] ===
=== [[UU cable Driver Download]] ===
=== [[How to install serial port driver for production Q1/Q2]] ===
=== [[How to install serial port driver for production terminal in Linux]] ===
=== [[About the development of serial port of the terminal]] ===
=== [[How to add udev rules for USB debugging in Linux]]===
=== [[Impact of terminal sleep on serial port]]===
=== [[When the serial port cable is disconnected, close/open the serial port again]]===
=== [[How to use accessory mode]]===
=== [[How to detect UU cable connnected programmatically]]===
=== [[Demo for Control FAN by using serial port]]===
=== [[How to list the connected USB device]]===
=== [[How to use accessory agent service between D22 and Q3]]===

== [[Firmware]] ==
=== [[How to update firmware]] ===
=== [[What's the meaning of firmware package]] ===
=== [[What is the difference between engineer mode terminal and user mode terminal]] ===
=== [[How to use poshomesettings.xml]] ===
=== [[How to use possystemsettings.xml]] ===
=== [[How to prevent visitors from uninstalling applications by mistake]] ===
=== [[Error message - agent stopped]] ===
=== [[Security lock has been set, but forget the password]] ===
=== [[How to use the buttons of Q1 in the application]] ===
=== [[Notes on application adaptation to Q1 (4G)]] ===
=== [[How to customize boot logo and boot animation]] ===
=== [[How to set wallpaper]] ===
=== [[How to enter special mode when starting]] ===
=== [[Latest browser for Q-series]] ===
=== [[How many external servers and services that the firmware usually access]] ===
=== [[How to get different firmware mode of terminal]] ===
=== [[How to write customer SN]] ===
=== [[How to enable wake up by touch screen]] ===
=== [[How to set user system property]] ===
=== [[How to enable/disable MTP]] ===
=== [[How to update WebView on POS]] ===
=== [[How to disable TF card and pendriver file explorer]] ===
=== [[Demo for screen on/off]] ===

== [[Settings Menu]] ==
=== [[How to reset factory data]] ===
=== [[Introduction to common menus of Settings]] ===
=== [[How to view the certificate list on the terminal]] ===
=== [[Introduction to Merchant Self Test of Settings]] ===
=== [[How to use terminal merchant self test to test specified networks]] ===
=== [[How to change system language]] ===
=== [[How to login the terminal as admin]] ===
=== [[How to change the login password of terminal administrator]] ===
=== [[How to update the terminal time]] ===
=== [[How to change the terminal time zone]] ===
=== [[How to enable user role to control accessing settings menu]] ===
=== [[How to update user role password by API]] ===
=== [[How to disable bluetooth/wifi in terminal]] ===
=== [[How to enable/disable autotimezone in terminal]] ===
=== [[How to enable/disable autotime in terminal]] ===
=== [[How to set sleep of display in terminal]] ===
=== [[How to grant Accessibility permission automatically]] ===
=== [[How to remove the security lock when starting the terminal?]] ===
=== [[How to launch the sub menu of settings from your application?]] ===
=== [[How to set language by API]] ===

== [[Battery/Power]] ==
=== [[Why do the four LEDs of the charging indicator light flash at the same time]] ===
=== [[For not be powered during a long period (more than 6 month)]] ===
=== [[On what battery% does the Q2 turn off]] ===
=== [[Time for charge/discharge]] ===
=== [[Counter Mode of Q3]] ===
=== [[How to turn off by API]] ===

== [[SIM/Ethenet/WIFI]] ==
=== [[How to turn off the portable hotspot of the terminal]] ===
=== [[How to turn on the portable hotspot of the terminal]] ===
=== [[How to obtain IMEI of the terminal]] ===
=== [[How to obtain MEID of the terminal]] ===
=== [[What modem bands does the wizarPOS terminal support]] ===
=== [[SIM card signal problem]] ===
=== [[SIM card network problem]] ===
=== [[Error while searching for networks]] ===
=== [[How to check e-SIM status?]] ===
=== [[Ethernet support]] ===
=== [[How to set the communication mode of the terminal]] ===
=== [[Why the USSD menu not displaying]] ===
=== [[How to set APN]] ===
=== [[How to set preferred network type of the cellular network by API]] ===
=== [[How to set static Ethernet parameters by API]] ===
=== [[How to enable/disable mobile data]] ===
=== [[How to query and set network operators by API]] ===
=== [[Softsim&Data Plan Activation]] ===
=== [[How to enable/disable ethernet]] ===

== [[Certificate]] ==
=== [[How to apply app certificate]] ===
=== [http://ftp.wizarpos.com/AppCertificateBlackWhitePermissionRuls.pdf How to restrict some APP installing(BlackWhitePermission)] ===
=== [[How to install CA certificate]] ===
=== [[How to clear terminal certificate]] ===
=== [[Why I can not find the imported certificate? ]] ===

== [[Card]] ==
=== [[How far is the reading distance of contactless card]] ===
=== [[What's the buffer size of NFC reader]] ===
=== [[Java API usage for contactless CPU card]] ===
=== [[Java API usage for Felica card]] ===
=== [[Java API usage for contactless Mifare card]] ===
=== [[PSAM card, Code:-6 com.cloudpos.DeviceException: Operation error! Error code = -1, Error message = Operation not permitted.]] ===
=== [[Guide to the best card tap position for front contactless terminal]] ===

== [[FingerPrint]] ==
=== [[How to use fingerprint module interface in wizarPOS terminal]] ===
=== [[Image resolution(DPI) of fingerprint module]] ===
=== [[Data type/template format of fingerprint module]] ===

== [[Other development]] ==
=== [[How to set ANDROID_HOME]] ===
=== [[How to sign app]] ===
=== [[How to install app to POS]] ===
=== [https://developer.android.com/training/basics/firstapp/ Create your first app in android studio] ===
=== [[How to get log from terminal]] ===
=== [[Install APK error: An existing package by the same name with a conflicting signature is already installed]] ===
=== [[How to get a full log without a filter]] ===
=== [[How to get the current location of the terminal]] ===
=== [[How to make the application use the terminal's photographing function]] ===
=== [[APKs for testing]] ===
=== [[Simple ADB command list]] ===
=== [[Advance Samples]] ===
=== [[How to import SDK in C# program]] ===
=== [[How to use PhoneStateListener to get SignalStrength]] ===
=== [[D3 Demos]] ===
=== [[How to customize the graphical user interface of POS when inputting PINPAD]] ===
=== [[Demo for Kiosk Mode]] ===
=== [[How to block status bar]] ===
=== [[Using system API to make full screen]] ===
=== [[Use the API provided by Android to make full screen]] ===
=== [[Disable home key]] ===
=== [[How to block and get power button]] ===
=== [[How to obtain terminal information (brand, manufacturer, product model, etc.)]] ===
=== [[How to save files on device storage]] ===
=== [[How to set the application as the default launcher]] ===
=== [[How to get the firmware(OS) version]] ===
=== [[How to get firmware and EMV kernel version]] ===
=== [[How to use TLSv1.3]] ===
=== [[How to run automatically after installing]] ===
=== [[Secure Connections]] ===
=== [[How to use AnyDesk]] ===
=== [[How to export the APP's db file to SD card]] ===
=== [[How to immigrate payment application to Q2Premium]] ===
=== [[How to run automatically after terminal boot]] ===
=== [[How to integrate SDK aar file to flutter APP]] ===
=== [[How to call AIDL interface]] ===

== [[TMS/Wizarview]] ==
=== [http://ftp.wizarpos.com/advanceSDK/WizarView_V4.pdf TMS Overview] ===
=== [http://ftp.wizarpos.com/advanceSDK/wizarView_UserManual_generalv2.8.pdf TMS User Guide] ===
=== [[How to register terminal to WizarView]] ===
=== [[How to accept parameter files downloaded from TMS]] ===
=== [[How to operate when "User Locked"]] ===
=== [[How to apply for a WizarView account]] ===
=== [[How to batch import terminals]] ===
=== [[How to remove the terminals associated with an application from the configuration]] ===
=== [[How to remove an application from a device using TMS]] ===
=== [[Error codes of TMS and the agent]] ===
=== [[How many ports and IP used by TMS]] ===
=== [[When does the terminal update the applications from TMS]] ===
=== [[What's the meaning of silent, prompt and market when configure app]] ===
=== [[How to apply for an RMA account]] ===
=== [[How to update firmware remotely]] ===
=== [[How to push an APK to a specific device type]] ===
=== [[How to set Agent Working Mode]] ===
=== [[How to control the prompt installing apk configured in TMS to install]] ===
=== [[How to enable/disable wizarviewagent network using]] ===
=== [[How to push apps to a batch of terminals in different groups by tag]] ===

== [[Key Injection]] ==
=== [[How to inject test key(master key or DUKPT key) remotely]] ===
=== [[What is DUKPT]] ===
=== [[What is the master key and session key]] ===

=== [[TMK Deliver System Usage（For KeyLoader POS/Master POS）]] ===
=== [[Remote Key Injection]] ===

=== [[Key Loader POS1 shows serial rcv timeout]] ===
=== [[Update key failed, import TMK: -74496]] ===

== [[EMV]] ==
=== [[What's Tag91]] ===
=== [[What's CAPK]] ===
=== [[How to set issuer script]] ===
=== [[Sometimes when try for chip, contactless is detecting first, how to solve this problem?]] ===

== [[Cryptography]] ==
=== [[Padding]] ===

How to Recover a Terminal from Tamper Status

2023-12-19T04:26:07Z

Hans: Hans moved page How the terminal can be recovered from tamper status to How to Recover a Terminal from Tamper Status

<big>Terminal can only be recovered from tamper status by terminal vendor. Others can not recover terminal by themselves.
# Tampered device generates a token in the TF card during booting process.
# Please get and send the token file to WizarPOS by mail.

'''Mail information:'''

'''Title''': Device recovery from temper status.

'''Mailto''': techsupport@wizarpos.com; and copy the WizarPOS sales staff.

'''Content''': '''*Company name or Group name in our TMS''', without this infomation, will not sign the token file.

'''Please choose tamper reason''': 1. Tampered when received the device from WizarPOS; 2. Tampered when repair; 3 Tampered after fall down/drop

'''Attachment''': token file.
# After we received the application mail and approved, we will reply and attach the signature file of that token.
# Please put the .sig file to the same folder of the TF card and reboot terminal again. Please notice, that token file should exist in the same folder.</big>

How to Retrieve Terminal Information: Brand, Manufacturer, Product Model, etc.

2023-12-14T08:40:37Z

Hans:

There are some system information in POS, such as brand, manufacturer and product model. Please refer to the following table:
{| class="wikitable"
|-
! Product Name/Property Name !! ro.product.brand !! ro.product.manufacturer !! ro.product.model !! Settings Display/Build.MODEL !! ro.wp.product.model !! ro.wp.product.submodel
|-
| W1 || wizarPOS|| wizarPOS|| WIZARPOS_1|| WIZARPOS 1|| W1||
|-
| W1V2|| wizarPOS|| wizarPOS|| WIZARPOS_1|| WIZARPOS 1|| W1v2 ||
|-
| PAD1 || wizarPOS|| wizarPOS|| WIZARPAD_1 || WIZARPAD 1 || PAD1||
|-
| Q1 || wizarPOS|| wizarPOS|| WIZARHAND_Q1|| WIZARHAND Q1|| Q1||
|-
| Q14G || wizarPOS|| wizarPOS|| WIZARHAND_Q1|| WIZARHAND Q1|| Q1v2||
|-
| Q2 || wizarPOS|| wizarPOS|| WIZARPOS_Q2|| WIZARPOS Q2|| Q2 || Q2
|-
| Q2 Android 7 || wizarPOS|| wizarPOS|| WIZARPOS_Q2|| WIZARPOS Q2|| Q2A7 || Q2
|-
| Q2 Premium || wizarPOS|| SHWP|| WIZARPOS_Q2|| WIZARPOS Q2|| Q2P || Q2
|-
| K2 || wizarPOS|| wizarPOS|| WIZARPOS_Q2|| WIZARPOS Q2(K2)|| Q2 || K2
|-
| M2 || wizarPOS|| wizarPOS|| WIZARPOS_Q2|| WIZARPOS Q2(M2)|| Q2 || M2
|-
| QD4 || wizarPOS|| wizarPOS|| WIZARPOS_Q2|| WIZARPOS Q2(QD4)|| Q2 || QD4
|-
| QD5 || wizarPOS|| wizarPOS|| WIZARPOS_Q2|| WIZARPOS Q2(QD5)|| Q2 || QD5
|-
| QD6 || wizarPOS|| wizarPOS|| WIZARPOS_Q2|| WIZARPOS Q2(QD6)|| Q2 || QD6
|-
| Q3 || wizarPOS|| wizarPOS|| WIZARPOS_Q3|| WIZARPOS Q3|| Q3A7 || Q3A7
|-
| Q3B|| wizarPOS|| wizarPOS|| WIZARPOS_Q3|| WIZARPOS Q3|| Q3A7 || Q3B
|-
| Q3K|| wizarPOS|| wizarPOS|| WIZARPOS_Q3|| WIZARPOS Q3|| Q3A7 || Q3K
|-
| Q3PIN|| wizarPOS|| wizarPOS|| WIZARPOS_Q3|| WIZARPOS Q3|| Q3A7 || Q3PIN
|-
| Q3R|| wizarPOS|| wizarPOS|| WIZARPOS_Q3|| WIZARPOS Q3|| Q3A7 || Q3R
|-
| Q3V|| wizarPOS|| wizarPOS|| WIZARPOS_Q3|| WIZARPOS Q3|| Q3A7 || Q3V
|-
| Q3W || wizarPOS|| wizarPOS|| WIZARPOS_Q3|| WIZARPOS Q3|| Q3A7 || Q3W
|}

Android provides a simple way to get system information. The code snippet is as follows:
<syntaxhighlight lang="java">
String model = getSystemPropertie("ro.wp.product.model").trim()
public static String getSystemPropertie(String key) {
Object strVersion = null;
try {
Class<?> systemProperties = Class.forName("android.os.SystemProperties");
Log.i("systemProperties", systemProperties.toString());
strVersion = systemProperties.getMethod("get", new Class[] { String.class, String.class }).invoke(systemProperties, new Object[] { key, "unknown" });
Log.i("strVersion", strVersion.getClass().toString());
} catch (Exception e) {
e.printStackTrace();
}
return strVersion.toString();
}
</syntaxhighlight >

EMV Develop Spec

2023-12-12T06:08:05Z

Hans: /* Java API Demo */

== EMV API ==
{| class="wikitable"
|-
! Version!! Download!!Release Time
|-
| 4.31 || [http://ftp.wizarpos.com/emv/EMVKernel_Android_interface_4.31(20230517).pdf EMV kernel API]|| 2023-05-17
|}

== EMV Process Flow ==
{| class="wikitable"
|-
! Version!! Download!!Release Time
|-
| EmvProcessFlow_230314 || [http://ftp.wizarpos.com/emv/EmvProcessFlow_230314.pdf EMV Process Flow]|| 2023-04-17
|}
== [http://www.emvlab.org/emvtags/ EMV tag reference] ==
== EMV Demo ==
=== Java API Demo ===
'''Note that after downloading the latest EMV sample, please check the latest [[CloudPOS SDK AAR]], then replace it in the EMV Sample.'''
{| class="wikitable"
|-
! Version!! Download!!Release Time!!Description
|-
| EMVSample_20231113 || [http://ftp.wizarpos.com/emv/EMVSample_20231113.zip latest EMV Sample with AAR&Java]|| 2023-11-13| use cloudpos SDK aar 1.5.4.82||
|}

=== C api Demo ===
{| class="wikitable"
|-
! Version!! Download!!Release Time!!Description
|-
| 20230627 || [http://ftp.wizarpos.com/emv/EMVSampleJNI_20230627.zip EMV Sample with JNI source]|| 2023-06-27|| support Android 12.
|}

EMV Develop Spec

2023-12-12T06:07:51Z

Hans: /* Java API Demo */

EMV Develop Spec

2023-12-12T06:04:12Z

Hans: /* Java API Demo */

== EMV API ==
{| class="wikitable"
|-
! Version!! Download!!Release Time
|-
| 4.31 || [http://ftp.wizarpos.com/emv/EMVKernel_Android_interface_4.31(20230517).pdf EMV kernel API]|| 2023-05-17
|}

== EMV Process Flow ==
{| class="wikitable"
|-
! Version!! Download!!Release Time
|-
| EmvProcessFlow_230314 || [http://ftp.wizarpos.com/emv/EmvProcessFlow_230314.pdf EMV Process Flow]|| 2023-04-17
|}
== [http://www.emvlab.org/emvtags/ EMV tag reference] ==
== EMV Demo ==
=== Java API Demo ===
<big>Note that after downloading the latest EMV sample, please check the latest [[CloudPOS SDK AAR]], then replace it in the EMV Sample.</big>
{| class="wikitable"
|-
! Version!! Download!!Release Time!!Description
|-
| EMVSample_20231113 || [http://ftp.wizarpos.com/emv/EMVSample_20231113.zip latest EMV Sample with AAR&Java]|| 2023-11-13| use cloudpos SDK aar 1.5.4.82||
|}

=== C api Demo ===
{| class="wikitable"
|-
! Version!! Download!!Release Time!!Description
|-
| 20230627 || [http://ftp.wizarpos.com/emv/EMVSampleJNI_20230627.zip EMV Sample with JNI source]|| 2023-06-27|| support Android 12.
|}

How to Retrieve Terminal Information: Brand, Manufacturer, Product Model, etc.

2023-12-05T01:59:32Z

Hans:

There are some system information in POS, such as brand, manufacturer and product model. Please refer to the following table:
{| class="wikitable"
|-
! Product Name/Property Name !! ro.product.brand !! ro.product.manufacturer !! ro.product.model !! Settings Display/Build.MODEL !! ro.wp.product.model !! ro.wp.product.submodel
|-
| W1 || wizarPOS|| wizarPOS|| WIZARPOS_1|| WIZARPOS 1|| W1||
|-
| W1V2|| wizarPOS|| wizarPOS|| WIZARPOS_1|| WIZARPOS 1|| W1v2 ||
|-
| PAD1 || wizarPOS|| wizarPOS|| WIZARPAD_1 || WIZARPAD 1 || PAD1||
|-
| Q1 || wizarPOS|| wizarPOS|| WIZARHAND_Q1|| WIZARHAND Q1|| Q1||
|-
| Q14G || wizarPOS|| wizarPOS|| WIZARHAND_Q1|| WIZARHAND Q1|| Q1v2||
|-
| Q2 || wizarPOS|| wizarPOS|| WIZARPOS_Q2|| WIZARPOS Q2|| Q2 || Q2
|-
| Q2a7 || wizarPOS|| wizarPOS|| WIZARPOS_Q2|| WIZARPOS Q2|| Q2A7 || Q2
|-
| Q2P || wizarPOS|| SHWP|| WIZARPOS_Q2|| WIZARPOS Q2|| Q2P || Q2
|-
| K2 || wizarPOS|| wizarPOS|| WIZARPOS_Q2|| WIZARPOS Q2(K2)|| Q2 || K2
|-
| M2 || wizarPOS|| wizarPOS|| WIZARPOS_Q2|| WIZARPOS Q2(M2)|| Q2 || M2
|-
| QD4 || wizarPOS|| wizarPOS|| WIZARPOS_Q2|| WIZARPOS Q2(QD4)|| Q2 || QD4
|-
| QD5 || wizarPOS|| wizarPOS|| WIZARPOS_Q2|| WIZARPOS Q2(QD5)|| Q2 || QD5
|-
| QD6 || wizarPOS|| wizarPOS|| WIZARPOS_Q2|| WIZARPOS Q2(QD6)|| Q2 || QD6
|-
| Q3 || wizarPOS|| wizarPOS|| WIZARPOS_Q3|| WIZARPOS Q3|| Q3A7 || Q3A7
|-
| Q3B|| wizarPOS|| wizarPOS|| WIZARPOS_Q3|| WIZARPOS Q3|| Q3A7 || Q3B
|-
| Q3K|| wizarPOS|| wizarPOS|| WIZARPOS_Q3|| WIZARPOS Q3|| Q3A7 || Q3K
|-
| Q3PIN|| wizarPOS|| wizarPOS|| WIZARPOS_Q3|| WIZARPOS Q3|| Q3A7 || Q3PIN
|-
| Q3R|| wizarPOS|| wizarPOS|| WIZARPOS_Q3|| WIZARPOS Q3|| Q3A7 || Q3R
|-
| Q3V|| wizarPOS|| wizarPOS|| WIZARPOS_Q3|| WIZARPOS Q3|| Q3A7 || Q3V
|-
| Q3W || wizarPOS|| wizarPOS|| WIZARPOS_Q3|| WIZARPOS Q3|| Q3A7 || Q3W
|}

Android provides a simple way to get system information. The code snippet is as follows:
<syntaxhighlight lang="java">
String model = getSystemPropertie("ro.wp.product.model").trim()
public static String getSystemPropertie(String key) {
Object strVersion = null;
try {
Class<?> systemProperties = Class.forName("android.os.SystemProperties");
Log.i("systemProperties", systemProperties.toString());
strVersion = systemProperties.getMethod("get", new Class[] { String.class, String.class }).invoke(systemProperties, new Object[] { key, "unknown" });
Log.i("strVersion", strVersion.getClass().toString());
} catch (Exception e) {
e.printStackTrace();
}
return strVersion.toString();
}
</syntaxhighlight >

How to Update WebView on POS Systems

2023-10-31T01:49:14Z

Hans: /* WebView with system signature */

== Introduction to Android WebView ==
Android WebView is an important system component on the Android platform that allows Android apps to embed HTML page content and browse websites directly within the app. It uses the Blink rendering engine from Chrome to display webpage content and allows developers to package and distribute webpages as native apps.

The main functions of Android WebView include:

* Loading and displaying webpage content written in HTML, CSS, and JavaScript within an Android app.
* Supporting common webpage elements and features such as images, videos, audio, tables, forms, etc.
* Providing rich APIs for interactions between JavaScript and Java.
* Caching webpage content and user data to improve access speed and user experience.
Android WebView has become an essential part of many Android apps, particularly in e-commerce, social networking, news, and other fields.

WebView is often used in Android development to display web content or web applications within an application, mainly for the following reasons:

* Unified interface experience: The web content displayed through WebView can match the UI interface of the native application, improving the user experience.
* Convenient update and maintenance: Unlike native applications that require publishing a new version to update features, web content in WebView can be updated via the server.
* Reuse existing Web technology stack: For companies or individual developers who have invested heavily in frontend resources, they can reuse their existing frontend technology stack to reduce development costs.

In short, WebView can serve as a powerful supplement to native applications under certain scenarios, allowing applications to fully leverage the advantages of Web technologies.

WebView is commonly used in various scenarios in Android development, including:

* In-app browsing: Displaying external website content within an application, providing users with a seamless browsing experience without leaving the application.
* Hybrid apps: Combining native app functionality with web content to create hybrid apps, which can provide better performance than traditional web-based apps while still leveraging the benefits of web technologies.
* Single-page applications (SPA): Building single-page applications within a WebView, allowing for faster loading times and smoother user interactions compared to loading multiple pages.
* Webviews in widgets: Using WebViews to display dynamic content in home screen widgets, such as weather updates or news headlines.
Overall, WebView is a versatile tool that can be utilized in a wide range of use cases in Android development, depending on the specific needs and requirements of each project.

Here is an example code snippet demonstrating how to use a WebView:
<syntaxhighlight lang="java">
// Create a new WebView object
WebView webView = new WebView(this);

// Set the layout parameters for the WebView
webView.setLayoutParams(new ViewGroup.LayoutParams(ViewGroup.LayoutParams.MATCH_PARENT,
ViewGroup.LayoutParams.MATCH_PARENT));

// Load the specified URL into the WebView
webView.loadUrl("https://www.example.com");

// Add the WebView to the layout
((ViewGroup) findViewById(R.id.activity_main)).addView(webView);
</syntaxhighlight>
The above code creates a new WebView object and sets its layout parameters so that it fills the entire screen. We then call the loadUrl() method to load the specified URL into the WebView and add the WebView object to the layout.

Additionally, if you need to handle JavaScript events inside the web page, you can set a WebViewClient and/or a WebChromeClient for the WebView:

<syntaxhighlight lang="java">
webView.setWebViewClient(new WebViewClient() {
@Override
public boolean shouldOverrideUrlLoading(WebView view, String url) {
// Handle URL navigation events here
return super.shouldOverrideUrlLoading(view, url);
}
});

webView.setWebChromeClient(new WebChromeClient());
</syntaxhighlight>
In this code, we set a new WebViewClient instance and override the shouldOverrideUrlLoading() method to handle URL navigation events. We also set a new WebChromeClient instance to handle other interactive events inside the web page, such as JavaScript dialog boxes.

Note that these examples demonstrate basic usage of the WebView. Depending on the requirements of your project, you may need to implement additional functionality, such as handling network errors or caching web content.

== Update System WebView ==
Android WebView is a native component provided by the operating system, and upgrading to a higher version requires installation of a WebView signed by the system signature to succeed. Customers may provide their preferred versions（ download the latest version of WebView from the Google Developer website (https://developers.google.com/android/guides/webview) ） for review and signing by us, or select from several signed versions offered by us to attempt installation.

Please note that updating the system WebView involves modifying the device's operating system, which can be risky and void warranties.

Note that the version of the system WebView is dependent on the Android OS version running on POS. Some older devices may not support the latest version of the WebView.

Another alternative is to use a third-party WebView library, such as Crosswalk, which includes its own version of the WebView component that you can integrate into your application. This way, you can bypass the limitations imposed by the system WebView and have more control over the WebView version used in your app. However, keep in mind that using a third-party library may increase your app size and could potentially introduce stability issues.

== WebView versions in different model==
* Q2: version is 74.0.3729.286
* Q2 Android 12: version is 95.0.4638.74
== Avaliable WebView Versions ==
[http://ftp.wizarpos.com/webview/com.android.webview_102.0.5005.96-q2_releasekey.apk webview version 102 download]

How to Use Printers with JavaScript

2023-10-30T09:14:41Z

Hans:

This demo shows how to use printer by javascript. This usually happens when developing the HTML and HTML5 application and webview based application.

[http://ftp.wizarpos.com/advanceSDK/JsCallPrint.zip Please download here]

How to Use Printers with JavaScript

2023-10-30T07:05:49Z

Hans:

This demo shows how to use printer by javascript. This usually happens when developing the HTML5 application and webview based application.

[http://ftp.wizarpos.com/advanceSDK/JsCallPrint.zip Please download here]

How to Use Printers with JavaScript

2023-10-30T06:58:30Z

Hans:

This demo shows how to use printer by javascript. This usually happens when developing the HTML5 application and webview based applicaiton.

[http://ftp.wizarpos.com/advanceSDK/JsCallPrint.zip Please download here]

How to Use Printers with JavaScript

2023-10-30T06:58:09Z

Hans:

This demo shows how to use printer by javascript. This usually happens when developing the HTML5 application and webview based applicaiton.
[http://ftp.wizarpos.com/advanceSDK/JsCallPrint.zip Please download here]

How to Use Accessory Agent Service with D22 and Q3 Devices

2023-07-28T02:18:06Z

Hans: /* Init USB Connection Mode in Development */

== Introduction ==
D22 can connect with Q3 via USB cable. The D22 works in master mode and the Q3 works in slave mode. By the helping of the AccessoryConnectionAgent apk, the application in two terminals can send Intent to any other application in another terminal.

== User Manual ==
[http://ftp.wizarpos.com/advanceSDK/AccessoryConnectAgentusermanual.pdf Accessory Connection Agent service user manual]

== AccessoryConnectionAgent Service APK ==
By default, the AccessoryConnectAgent is included in the D22 and Q3 FW. But it maybe not exists in the old FW, so the developer should install the agent by themselves.
Here is the agent apk:

[http://ftp.wizarpos.com/advanceSDK/AccessoryConnectionAgent.apk Accessory Connection Agent APK]

== Demo ==
Demo for APK developing.

[http://ftp.wizarpos.com/advanceSDK/AccessoryAgentDemo.zip Demo]

== Init USB Connection Mode in Development==
By default, the AccessoryConnectionAgent is disabled, the developer can use this apk to enable it. 
For the production FW, the agent will be initialized before releasing from factory.
Please download and install to D22 and Q3.

[http://ftp.wizarpos.com/advanceSDK/SetUsbAttrs.apk APK for enable or disable the Accessory Connection Agent service]

How to Use Accessory Agent Service with D22 and Q3 Devices

2023-07-28T02:17:26Z

Hans: /* User Manual */

How to Use Accessory Agent Service with D22 and Q3 Devices

2023-07-28T02:01:55Z

Hans: /* AccessoryConnectionAgent Service APK */

== Introduction ==
D22 can connect with Q3 via USB cable. The D22 works in master mode and the Q3 works in slave mode. By the helping of the AccessoryConnectionAgent apk, the application in two terminals can send Intent to any other application in another terminal.

== User Manual ==
[http://ftp.wizarpos.com/advanceSDK/AccessoryConnectAgentusermanual.pdf Accessory connect agent service user manual]

== AccessoryConnectionAgent Service APK ==
By default, the AccessoryConnectAgent is included in the D22 and Q3 FW. But it maybe not exists in the old FW, so the developer should install the agent by themselves.
Here is the agent apk:

[http://ftp.wizarpos.com/advanceSDK/AccessoryConnectionAgent.apk Accessory Connection Agent APK]

== Demo ==
Demo for APK developing.

[http://ftp.wizarpos.com/advanceSDK/AccessoryAgentDemo.zip Demo]

== Init USB Connection Mode in Development==
By default, the AccessoryConnectionAgent is disabled, the developer can use this apk to enable it. 
For the production FW, the agent will be initialized before releasing from factory.
Please download and install to D22 and Q3.

[http://ftp.wizarpos.com/advanceSDK/SetUsbAttrs.apk APK for enable or disable the AccessoryConnection Agent service]

How to Use Accessory Agent Service with D22 and Q3 Devices

2023-07-28T02:01:20Z

Hans:

== Introduction ==
D22 can connect with Q3 via USB cable. The D22 works in master mode and the Q3 works in slave mode. By the helping of the AccessoryConnectionAgent apk, the application in two terminals can send Intent to any other application in another terminal.

== User Manual ==
[http://ftp.wizarpos.com/advanceSDK/AccessoryConnectAgentusermanual.pdf Accessory connect agent service user manual]

== AccessoryConnectionAgent Service APK ==
By default, the AccessoryConnectAgent is included in the D22 and Q3 FW. But it maybe not exists in the old FW, so the developer should install the agent by themselves.
Here is the agent apk:

[http://ftp.wizarpos.com/advanceSDK/AccessoryConnectionAgent.apk Accessory connect service APK]

== Demo ==
Demo for APK developing.

[http://ftp.wizarpos.com/advanceSDK/AccessoryAgentDemo.zip Demo]

== Init USB Connection Mode in Development==
By default, the AccessoryConnectionAgent is disabled, the developer can use this apk to enable it. 
For the production FW, the agent will be initialized before releasing from factory.
Please download and install to D22 and Q3.

[http://ftp.wizarpos.com/advanceSDK/SetUsbAttrs.apk APK for enable or disable the AccessoryConnection Agent service]

How to Use Accessory Agent Service with D22 and Q3 Devices

2023-07-27T10:31:41Z

Hans:

== Introduction ==
D22 can connect with Q3 via USB cable. The D22 works in master mode and the Q3 works in slave mode. By the helping of the AccessoryConnectionAgent apk, the application in two terminals can send Intent to any other application in another terminal.

== User Manual ==
[http://ftp.wizarpos.com/advanceSDK/AccessoryconnectSoftwareserviceusermanual.pdf Accessory connect Software service usermanual]

== AccessoryConnectAgent Service APK ==
By default, the AccessoryConnectAgent is included in the D22 and Q3 FW. But it maybe not exists in the old FW, so the developer should install the agent by themselves.
Here is the agent apk:

[http://ftp.wizarpos.com/advanceSDK/AccessoryConnectionAgent.apk Accessory connect service APK]

== Demo ==
Demo for APK developing.

[http://ftp.wizarpos.com/advanceSDK/AccessoryAgentDemo.zip Demo]

== Set Attribute in Development==
By default, the AccessoryConnectionAgent is disabled, the developer can use this apk to enable it. 
For the production FW, the agent will be initialized before releasing from factory.
Please download and install to D22 and Q3.

[http://ftp.wizarpos.com/advanceSDK/SetUsbAttrs.apk APK for enable or disable the AccessoryConnection Agent service]

How to Use Accessory Agent Service with D22 and Q3 Devices

2023-07-27T10:30:52Z

Hans:

== Introduction ==
D22 can connect with Q3 via USB cable. The D22 works in master mode and the Q3 works in slave mode. By the helping of the AccessoryConnectionAgent apk, the application in two terminals can send Intent to any other application in another terminal.

== User Manual ==
[http://ftp.wizarpos.com/advanceSDK/AccessoryconnectSoftwareserviceusermanual.pdf Accessory connect Software service usermanual]

== AccessoryConnectAgent Service APK ==
By default, the AccessoryConnectAgent is included in the D22 and Q3 FW. But it maybe not exists in the old FW, so the developer should install the agent by themselves.
Here is the agent apk:
[http://ftp.wizarpos.com/advanceSDK/AccessoryConnectionAgent.apk Accessory connect service APK]

== Demo ==
Demo for APK developing.
[http://ftp.wizarpos.com/advanceSDK/AccessoryAgentDemo.zip Demo]

== Set Attribute ==
By default, the AccessoryConnectionAgent is disabled, the developer can use this apk to enable it.
For the production FW, the agent will be initialized before releasing from factory.
Please download and install to D22 and Q3.
[http://ftp.wizarpos.com/advanceSDK/SetUsbAttrs.apk APK for enable or disable the AccessoryConnection Agent service]

How to Use Accessory Agent Service with D22 and Q3 Devices

2023-07-27T10:30:27Z

Hans:

== Introduction ==
D22 can connect with Q3 via USB cable. The D22 works in master mode and the Q3 works in slave mode. By the helping of the AccessoryConnectionAgent apk, the application in two terminals can send Intent to any other application in another terminal.

== User Manual ==
[http://ftp.wizarpos.com/advanceSDK/AccessoryconnectSoftwareserviceusermanual.pdf Accessory connect Software service usermanual]

== AccessoryConnectAgent Service APK ==
By default, the AccessoryConnectAgent is included in the D22 and Q3 FW. But it maybe not exists in the old FW, so the developer should install the agent by themselves.
Here is the agent apk:
[http://ftp.wizarpos.com/advanceSDK/AccessoryConnectionAgent.apk Accessory connect service APK]

== Demo ==
Demo for APK developing.
[http://ftp.wizarpos.com/advanceSDK/AccessoryAgentDemo.zip Demo]

== Set Attribute ==
By default, the AccessoryConnectionAgent is disabled, the developer can use this apk to enable it.
For the production FW, the agent will be initialized before releasing from factory.

Please download and install to D22 and Q3.
[http://ftp.wizarpos.com/advanceSDK/SetUsbAttrs.apk APK for enable or disable the AccessoryConnection Agent service]

How to Use Accessory Agent Service with D22 and Q3 Devices

2023-07-27T10:29:16Z

Hans:

== Introduction ==
D22 can connect with Q3 via USB cable. The D22 works in master mode and the Q3 works in slave mode. By the helping of the AccessoryConnectionAgent apk, the application in two terminals can send Intent to any other application in another terminal.

== User Manual ==
[http://ftp.wizarpos.com/advanceSDK/AccessoryconnectSoftwareserviceusermanual.pdf Accessory connect Software service usermanual]

== Agent Service APK ==
By default, the D22 and Q3 is included in the FW. But it maybe not exists in old FW, so the developer should install the agent by themselves.

[http://ftp.wizarpos.com/advanceSDK/AccessoryConnectionAgent.apk Accessory connect service APK]

== Demo ==
Demo for APK developing.
[http://ftp.wizarpos.com/advanceSDK/AccessoryAgentDemo.zip Demo]

== Set Attribute ==
By default, the AccessoryConnectionAgent is disabled, the developer can use this apk to enable it.
For the production FW, the agent will be initialized before releasing from factory.

Please download and install to D22 and Q3.
[http://ftp.wizarpos.com/advanceSDK/SetUsbAttrs.apk APK for enable or disable the AccessoryConnection Agent service]

How to Use Accessory Agent Service with D22 and Q3 Devices

2023-07-27T10:28:27Z

Hans:

== Introduction ==
D22 can connect with Q3 via USB cable. The D22 works in master mode and the Q3 works in slave mode. By the helping of the AccessoryConnectionAgent apk, the application in two terminals can send Intent to the any other application in another terminal.

== User Manual ==
[http://ftp.wizarpos.com/advanceSDK/AccessoryconnectSoftwareserviceusermanual.pdf Accessory connect Software service usermanual]

== Agent Service APK ==
By default, the D22 and Q3 is included in the FW. But it maybe not exists in old FW, so the developer should install the agent by themselves.

[http://ftp.wizarpos.com/advanceSDK/AccessoryConnectionAgent.apk Accessory connect service APK]

== Demo ==
Demo for APK developing.
[http://ftp.wizarpos.com/advanceSDK/AccessoryAgentDemo.zip Demo]

== Set Attribute ==
By default, the AccessoryConnectionAgent is disabled, the developer can use this apk to enable it.
For the production FW, the agent will be initialized before releasing from factory.

Please download and install to D22 and Q3.
[http://ftp.wizarpos.com/advanceSDK/SetUsbAttrs.apk APK for enable or disable the AccessoryConnection Agent service]

How to Automatically Run an App After Installation

2023-04-28T07:53:25Z

Hans:

== Solutions ==
There are two way to run app automatically after installation:
* Solution 1: Write specific information in Manifest file. If you write the apk by yourselves, please use this solution. So the apk can be installed from anywhere.
* Solution 2: Configure in TMS. If you can not update the existing apk, you have to use this solution to install the app from TMS.

== Solution 1: Configure in AndroidManifest of the APP ==
If choose this way, the system apk, WizarViewAgentAssistant version should be 2.8.40 or larger.
=== metadata ===
Add any of the following meta-data extension element data in the <application> field of AndroidManifest to complete the declaration.

* <meta-data android:name="cloudpos_activity_auto_start" android:value="XX.XX.XX.XXXX" />
* <meta-data android:name="cloudpos_service_auto_start" android:value="XX.XX.XX.XXXX" />
* <meta-data android:name="cloudpos_receiver_auto_start" android:value="XX.XX.XX.XXXX" />

meta-data data description：

Two parts of data contained in meta-data, the first part is to specify the type of component to be started, currently only three types are supported(cloudpos_activity_auto_start, cloudpos_service_auto_start, cloudpos_receiver_auto_start);

The second part is the class name of the absolute path of the component to be started, and the class name of the relative path is supported.
=== action ===
Add an action to the component that needs to be auto-started.

<action android:name="android.intent.action.AUTO_START" />
=== Example of AndroidManifest ===

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.wizarpos.pinpadui.test">

<application
android:allowBackup="true"
android:icon="@mipmap/ic_launcher"
android:label="@string/app_name"
android:theme="@style/AppTheme">

<meta-data android:name="cloudpos_activity_auto_start" android:value="com.wizarpos.pinpadui.test.MainActivity" />
<activity android:name=".MainActivity">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<action android:name="android.intent.action.AUTO_START" />

<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
<receiver android:name=".XXXXReceiver">
<intent-filter>
<action android:name="android.intent.action.AUTO_START" />
</intent-filter>
</receiver>
<service android:name=".XXXXService" android:enabled="true">
<intent-filter>
<action android:name="android.intent.action.AUTO_START" />
</intent-filter>
</service>
</application>
</manifest>

== Solution 2: Configure in TMS ==
Click Applications>Application, when add an application, click Advance, there is an auto run configure, now the label name is App Restart Entry.

The input format is type:component name

type: activity, service, broadcast

for example: activity:com.smartpos.autoremoveapk.MainActivity

How to Automatically Run an App After Installation

2023-04-28T07:44:07Z

Hans:

== Solutions ==
There are two way to run app automatically after installation:
* Solution 1: Write specific information in Manifest file
* Solution 2: Configure in TMS.
If you write the apk by yourselves, please use the solution 1. So the apk can be installed from any where.
If you can not update the existing apk, you have to use solution 2 to install the app to terminal.

== Solution 1: Configure in AndroidManifest of the APP ==
If choose this way, the system apk, WizarViewAgentAssistant version should be 2.8.40 or larger.
=== metadata ===
Add any of the following meta-data extension element data in the <application> field of AndroidManifest to complete the declaration.

* <meta-data android:name="cloudpos_activity_auto_start" android:value="XX.XX.XX.XXXX" />
* <meta-data android:name="cloudpos_service_auto_start" android:value="XX.XX.XX.XXXX" />
* <meta-data android:name="cloudpos_receiver_auto_start" android:value="XX.XX.XX.XXXX" />

meta-data data description：

Two parts of data contained in meta-data, the first part is to specify the type of component to be started, currently only three types are supported(cloudpos_activity_auto_start, cloudpos_service_auto_start, cloudpos_receiver_auto_start);

The second part is the class name of the absolute path of the component to be started, and the class name of the relative path is supported.
=== action ===
Add an action to the component that needs to be auto-started.

<action android:name="android.intent.action.AUTO_START" />
=== Example of AndroidManifest ===

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.wizarpos.pinpadui.test">

<application
android:allowBackup="true"
android:icon="@mipmap/ic_launcher"
android:label="@string/app_name"
android:theme="@style/AppTheme">

<meta-data android:name="cloudpos_activity_auto_start" android:value="com.wizarpos.pinpadui.test.MainActivity" />
<activity android:name=".MainActivity">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<action android:name="android.intent.action.AUTO_START" />

<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
<receiver android:name=".XXXXReceiver">
<intent-filter>
<action android:name="android.intent.action.AUTO_START" />
</intent-filter>
</receiver>
<service android:name=".XXXXService" android:enabled="true">
<intent-filter>
<action android:name="android.intent.action.AUTO_START" />
</intent-filter>
</service>
</application>
</manifest>

== Solution 2: Configure in TMS ==
Click Applications>Application, when add an application, click Advance, there is an auto run configure, now the label name is App Restart Entry.

The input format is type:component name

type: activity, service, broadcast

for example: activity:com.smartpos.autoremoveapk.MainActivity

How to Automatically Run an App After Installation

2023-04-28T07:42:23Z

Hans:

== Solutions ==
There are two way to run app automatically after installation: Write specific information in Manifest file or configure in TMS.
If you write the apk by yourselves, please use the solution of update the Manifest. So the apk can be installed from any where.
If you can not update the existing apk, you have to use TMS solution to install the app to terminal.

== Configure in AndroidManifest of the APP ==
If choose this way, the system apk, WizarViewAgentAssistant version should be 2.8.40 or larger.
=== metadata ===
Add any of the following meta-data extension element data in the <application> field of AndroidManifest to complete the declaration.

* <meta-data android:name="cloudpos_activity_auto_start" android:value="XX.XX.XX.XXXX" />
* <meta-data android:name="cloudpos_service_auto_start" android:value="XX.XX.XX.XXXX" />
* <meta-data android:name="cloudpos_receiver_auto_start" android:value="XX.XX.XX.XXXX" />

meta-data data description：

Two parts of data contained in meta-data, the first part is to specify the type of component to be started, currently only three types are supported(cloudpos_activity_auto_start, cloudpos_service_auto_start, cloudpos_receiver_auto_start);

The second part is the class name of the absolute path of the component to be started, and the class name of the relative path is supported.
=== action ===
Add an action to the component that needs to be auto-started.

<action android:name="android.intent.action.AUTO_START" />
=== Example of AndroidManifest ===

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.wizarpos.pinpadui.test">

<application
android:allowBackup="true"
android:icon="@mipmap/ic_launcher"
android:label="@string/app_name"
android:theme="@style/AppTheme">

<meta-data android:name="cloudpos_activity_auto_start" android:value="com.wizarpos.pinpadui.test.MainActivity" />
<activity android:name=".MainActivity">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<action android:name="android.intent.action.AUTO_START" />

<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
<receiver android:name=".XXXXReceiver">
<intent-filter>
<action android:name="android.intent.action.AUTO_START" />
</intent-filter>
</receiver>
<service android:name=".XXXXService" android:enabled="true">
<intent-filter>
<action android:name="android.intent.action.AUTO_START" />
</intent-filter>
</service>
</application>
</manifest>

== Configure in TMS ==
Click Applications>Application, when add an application, click Advance, there is an auto run configure, now the label name is App Restart Entry.

The input format is type:component name

type: activity, service, broadcast

for example: activity:com.smartpos.autoremoveapk.MainActivity

How to Understand External Servers and Services Accessed by Firmware

2023-04-25T07:10:44Z

Hans:

Some of the system services in the terminal will access some external services (IP port):

{| class="wikitable"
|-
! Service !! Domain Name or IPs || Description
|-
| TMS (wizarview) || www.wizarview.com || The major TMS servers: http://sdkwiki.wizarpos.com/index.php/How_many_ports_and_IP_used_by_TMS
|-
| 204 Pages || connectivitycheck.gstatic.com www.google.com www.qualcom.com || Android system will touch an empty 204 HTTP(S) page from those location to check the internet connectivity. Usually it use port 80 and 443. For example: [http://connectivitycheck.gstatic.com/generate_204 http://connectivitycheck.gstatic.com/generate_204]
|-
| A-GPS Location Services || location.services.mozilla.com locprod2-elb-us-west-2.prod.mozaws.net xtrapath2.xboxprod.izatcloud.net || The first 2 is belong to micro-g project. The 3rd one is belong to Qualcomm. TMS agent will use these service to get the GPS information. But this can be disabled by TMS agent configuration.
|-
| NTP Services || asia.pool.ntp.org (old default) cn.pool.ntp.org (old backup) hk.pool.ntp.org (old backup) 2.android.pool.ntp.org (new default from aosp) || Android system will use these server to automaticly adjustment time, when the system is set as "AutoTime". Usually they use UDP port 123
|}

How to Understand External Servers and Services Accessed by Firmware

2023-04-25T07:09:30Z

Hans:

Some of the system services in the terminal will access some external services (IP port):

{| class="wikitable"
|-
! Service !! Domain Name or IPs || Description
|-
| TMS (wizarview) || www.wizarview.com || The major TMS servers: http://sdkwiki.wizarpos.com/index.php/How_many_ports_and_IP_used_by_TMS
|-
| 204 Pages || connectivitycheck.gstatic.com www.google.com www.qualcom.com || Android system will touch an empty 204 HTTP(S) page from those location to check the internet connectivity. Usually it use port 80 and 443. For example: [http://connectivitycheck.gstatic.com/generate_204 http://connectivitycheck.gstatic.com/generate_204]
|-
| A-GPS Location Services || location.services.mozilla.com locprod2-elb-us-west-2.prod.mozaws.net xtrapath2.xboxprod.izatcloud.net || The first 2 is belong to micro-g project. The 3rd one is belong to Qualcomm. TMS agent will use these service to get the GPS information. But this can be disabled by TMS agent configuration.
|-
| NTP Services || asia.pool.ntp.org (old default) 
cn.pool.ntp.org (redundancy backup) 
hk.pool.ntp.org (redundancy backup) 
2.android.pool.ntp.org (new default from aosp) || Android system will use these server to automaticly adjustment time, when the system is set as "AutoTime". Usually they use UDP port 123
|}

How to Understand External Servers and Services Accessed by Firmware

2023-04-25T06:14:58Z

Hans:

Some of the system services in the terminal will access some external services (IP port):

{| class="wikitable"
|-
! Service !! Domain Name or IPs || Description
|-
| TMS (wizarview) || www.wizarview.com || The major TMS servers: http://sdkwiki.wizarpos.com/index.php/How_many_ports_and_IP_used_by_TMS
|-
| 204 Pages || connectivitycheck.gstatic.com www.google.com www.qualcom.com || Android system will touch an empty 204 HTTP(S) page from those location to check the internet connectivity. Usually it use port 80 and 443. For example: [http://connectivitycheck.gstatic.com/generate_204 http://connectivitycheck.gstatic.com/generate_204]
|-
| A-GPS Location Services || location.services.mozilla.com locprod2-elb-us-west-2.prod.mozaws.net xtrapath2.xboxprod.izatcloud.net || The first 2 is belong to micro-g project. The 3rd one is belong to Qualcomm. TMS agent will use these service to get the GPS information. But this can be disabled by TMS agent configuration.
|-
| NTP Services || asia.pool.ntp.org (old default) 2.android.pool.ntp.org (new default from aosp) cn.pool.ntp.org (redundancy backup) hk.pool.ntp.org (redundancy backup) || Android system will use these server to automaticly adjustment time, when the system is set as "AutoTime". Usually they use UDP port 123
|}

How to Understand External Servers and Services Accessed by Firmware

2023-04-25T06:13:01Z

Hans:

Some of the system services in the terminal will access some external services (IP port):

{| class="wikitable"
|-
! Service !! Domain Name or IPs || Description
|-
| TMS (wizarview) || www.wizarview.com || The major TMS servers: http://sdkwiki.wizarpos.com/index.php/How_many_ports_and_IP_used_by_TMS
|-
| 204 Pages || connectivitycheck.gstatic.com www.google.com www.qualcom.com || Android system will touch an empty 204 HTTP(S) page from those location to check the internet connectivity. Usually it use port 80 and 443. For example: [http://connectivitycheck.gstatic.com/generate_204 http://connectivitycheck.gstatic.com/generate_204]
|-
| A-GPS Location Services || location.services.mozilla.com locprod2-elb-us-west-2.prod.mozaws.net xtrapath2.xboxprod.izatcloud.net || The first 2 is belong to micro-g project. The 3rd one is belong to Qualcomm. TMS agent will use these service to get the GPS information. But this can be disabled by TMS agent configuration.
|-
| NTP Services || asia.pool.ntp.org 2.android.pool.ntp.org cn.pool.ntp.org hk.pool.ntp.org || Android system will use these server to automaticly adjustment time, when the system is set as "AutoTime". Usually they use UDP port 123
|}

How to Understand External Servers and Services Accessed by Firmware

2023-04-24T08:11:06Z

Hans:

Some of the system services in the terminal will access some external services (IP port):

{| class="wikitable"
|-
! Service !! Domain Name or IPs || Description
|-
| TMS (wizarview) || www.wizarview.com || The major TMS servers: http://sdkwiki.wizarpos.com/index.php/How_many_ports_and_IP_used_by_TMS
|-
| 204 Pages || connectivitycheck.gstatic.com www.google.com www.qualcom.com || Android system will touch an empty 204 HTTP(S) page from those location to check the internet connectivity. Usually it use port 80 and 443. For example: [http://connectivitycheck.gstatic.com/generate_204 http://connectivitycheck.gstatic.com/generate_204]
|-
| A-GPS Location Services || location.services.mozilla.com locprod2-elb-us-west-2.prod.mozaws.net xtrapath2.xboxprod.izatcloud.net || The first 2 is belong to micro-g project. The 3rd one is belong to Qualcomm. TMS agent will use these service to get the GPS information. But this can be disabled by TMS agent configuration.
|-
| NTP Services || asia.pool.ntp.org port 80 || Android system will use these server to automaticly adjustment time, when the system is set as "AutoTime".
|}

How to Understand External Servers and Services Accessed by Firmware

2023-04-24T07:59:53Z

Hans:

Some of the system services in the terminal will access some external services (IP port):

{| class="wikitable"
|-
! Service !! Domain Name or IPs || Description
|-
| TMS (wizarview) || www.wizarview.com || The major TMS servers: http://sdkwiki.wizarpos.com/index.php/How_many_ports_and_IP_used_by_TMS
|-
| 204 Pages || connectivitycheck.gstatic.com www.google.com www.qualcom.com port 80 and 443 || Android system will touch an empty 204 HTTP(S) page from those location to check the internet connectivity. For example: [http://connectivitycheck.gstatic.com/generate_204 http://connectivitycheck.gstatic.com/generate_204]
|-
| A-GPS Location Services || location.services.mozilla.com locprod2-elb-us-west-2.prod.mozaws.net xtrapath2.xboxprod.izatcloud.net || The first 2 is belong to micro-g project. The 3rd one is belong to Qualcomm. TMS agent will use these service to get the GPS information. But this can be disabled by TMS agent configuration.
|-
| NTP Services || asia.pool.ntp.org port 80 || Android system will use these server to automaticly adjustment time, when the system is set as "AutoTime".
|}

How to Understand External Servers and Services Accessed by Firmware

2023-04-24T07:59:11Z

Hans:

Some of the system service in the firmware usually will access some external services （IP port）:

{| class="wikitable"
|-
! Service !! Domain Name or IPs || Description
|-
| TMS (wizarview) || www.wizarview.com || The major TMS servers: http://sdkwiki.wizarpos.com/index.php/How_many_ports_and_IP_used_by_TMS
|-
| 204 Pages || connectivitycheck.gstatic.com www.google.com www.qualcom.com port 80 and 443 || Android system will touch an empty 204 HTTP(S) page from those location to check the internet connectivity. For example: [http://connectivitycheck.gstatic.com/generate_204 http://connectivitycheck.gstatic.com/generate_204]
|-
| A-GPS Location Services || location.services.mozilla.com locprod2-elb-us-west-2.prod.mozaws.net xtrapath2.xboxprod.izatcloud.net || The first 2 is belong to micro-g project. The 3rd one is belong to Qualcomm. TMS agent will use these service to get the GPS information. But this can be disabled by TMS agent configuration.
|-
| NTP Services || asia.pool.ntp.org port 80 || Android system will use these server to automaticly adjustment time, when the system is set as "AutoTime".
|}

How to Retrieve Terminal Information: Brand, Manufacturer, Product Model, etc.

2023-02-07T03:01:33Z

Hans:

There are some system information in POS, such as brand, manufacturer and product model. Please refer to the following table:
{| class="wikitable"
|-
! Product Name/Property Name !! ro.product.brand !! ro.product.manufacturer !! ro.product.model !! Settings Display/Build.MODEL !! ro.wp.product.model !! ro.wp.product.submodel
|-
| W1 || wizarPOS|| wizarPOS|| WIZARPOS_1|| WIZARPOS 1|| W1||
|-
| W1V2|| wizarPOS|| wizarPOS|| WIZARPOS_1|| WIZARPOS 1|| W1v2 ||
|-
| PAD1 || wizarPOS|| wizarPOS|| WIZARPAD_1 || WIZARPAD 1 || PAD1||
|-
| Q1 || wizarPOS|| wizarPOS|| WIZARHAND_Q1|| WIZARHAND Q1|| Q1||
|-
| Q14G || wizarPOS|| wizarPOS|| WIZARHAND_Q1|| WIZARHAND Q1|| Q1v2||
|-
| Q2 || wizarPOS|| wizarPOS|| WIZARPOS_Q2|| WIZARPOS Q2|| Q2 || Q2
|-
| Q2a7 || wizarPOS|| wizarPOS|| WIZARPOS_Q2|| WIZARPOS Q2|| Q2A7 || Q2
|-
| Q2P || wizarPOS|| SHWP|| WIZARPOS_Q2|| WIZARPOS Q2|| Q2P || Q2P
|-
| K2 || wizarPOS|| wizarPOS|| WIZARPOS_Q2|| WIZARPOS Q2(K2)|| Q2 || K2
|-
| M2 || wizarPOS|| wizarPOS|| WIZARPOS_Q2|| WIZARPOS Q2(M2)|| Q2 || M2
|-
| QD4 || wizarPOS|| wizarPOS|| WIZARPOS_Q2|| WIZARPOS Q2(QD4)|| Q2 || QD4
|-
| QD5 || wizarPOS|| wizarPOS|| WIZARPOS_Q2|| WIZARPOS Q2(QD5)|| Q2 || QD5
|-
| Q3 || wizarPOS|| wizarPOS|| WIZARPOS_Q3|| WIZARPOS Q3|| Q3A7 || Q3A7
|-
| Q3 || wizarPOS|| wizarPOS|| WIZARPOS_Q3|| WIZARPOS Q3|| Q3A7 || Q3B
|-
| Q3 || wizarPOS|| wizarPOS|| WIZARPOS_Q3|| WIZARPOS Q3|| Q3A7 || Q3K
|-
| Q3 || wizarPOS|| wizarPOS|| WIZARPOS_Q3|| WIZARPOS Q3|| Q3A7 || Q3PIN
|-
| Q3 || wizarPOS|| wizarPOS|| WIZARPOS_Q3|| WIZARPOS Q3|| Q3A7 || Q3R
|-
| Q3 || wizarPOS|| wizarPOS|| WIZARPOS_Q3|| WIZARPOS Q3|| Q3A7 || Q3V
|-
| Q3 || wizarPOS|| wizarPOS|| WIZARPOS_Q3|| WIZARPOS Q3|| Q3A7 || Q3W
|}

Android provides a simple way to get system information. The code snippet is as follows:
<syntaxhighlight lang="java">
String model = getSystemPropertie("ro.wp.product.model").trim()
public static String getSystemPropertie(String key) {
Object strVersion = null;
try {
Class<?> systemProperties = Class.forName("android.os.SystemProperties");
Log.i("systemProperties", systemProperties.toString());
strVersion = systemProperties.getMethod("get", new Class[] { String.class, String.class }).invoke(systemProperties, new Object[] { key, "unknown" });
Log.i("strVersion", strVersion.getClass().toString());
} catch (Exception e) {
e.printStackTrace();
}
return strVersion.toString();
}
</syntaxhighlight >

How to Retrieve Terminal Information: Brand, Manufacturer, Product Model, etc.

2023-01-10T02:34:04Z

Hans:

There are some system information in POS, such as brand, manufacturer and product model. Please refer to the following table:
{| class="wikitable"
|-
! Product Name/Property Name !! ro.product.brand !! ro.product.manufacturer !! ro.product.model !! Settings Display/Build.MODEL !! ro.wp.product.model !! ro.wp.product.submodel
|-
| W1 || wizarPOS|| wizarPOS|| WIZARPOS_1|| WIZARPOS 1|| W1||
|-
| W1V2|| wizarPOS|| wizarPOS|| WIZARPOS_1|| WIZARPOS 1|| W1v2 ||
|-
| PAD1 || wizarPOS|| wizarPOS|| WIZARPAD_1 || WIZARPAD 1 || PAD1||
|-
| Q1 || wizarPOS|| wizarPOS|| WIZARHAND_Q1|| WIZARHAND Q1|| Q1||
|-
| Q14G || wizarPOS|| wizarPOS|| WIZARHAND_Q1|| WIZARHAND Q1|| Q1v2||
|-
| Q2 || wizarPOS|| wizarPOS|| WIZARPOS_Q2|| WIZARPOS Q2|| Q2 || Q2
|-
| Q2a7 || wizarPOS|| wizarPOS|| WIZARPOS_Q2|| WIZARPOS Q2|| Q2A7 || Q2A7
|-
| Q2P || wizarPOS|| SHWP|| WIZARPOS_Q2|| WIZARPOS Q2|| Q2P || Q2P
|-
| K2 || wizarPOS|| wizarPOS|| WIZARPOS_Q2|| WIZARPOS Q2(K2)|| Q2 || K2
|-
| M2 || wizarPOS|| wizarPOS|| WIZARPOS_Q2|| WIZARPOS Q2(M2)|| Q2 || M2
|-
| QD4 || wizarPOS|| wizarPOS|| WIZARPOS_Q2|| WIZARPOS Q2(QD4)|| Q2 || QD4
|-
| QD5 || wizarPOS|| wizarPOS|| WIZARPOS_Q2|| WIZARPOS Q2(QD5)|| Q2 || QD5
|-
| Q3 || wizarPOS|| wizarPOS|| WIZARPOS_Q3|| WIZARPOS Q3|| Q3A7 || Q3A7
|-
| Q3 || wizarPOS|| wizarPOS|| WIZARPOS_Q3|| WIZARPOS Q3|| Q3A7 || Q3B
|-
| Q3 || wizarPOS|| wizarPOS|| WIZARPOS_Q3|| WIZARPOS Q3|| Q3A7 || Q3K
|-
| Q3 || wizarPOS|| wizarPOS|| WIZARPOS_Q3|| WIZARPOS Q3|| Q3A7 || Q3PIN
|-
| Q3 || wizarPOS|| wizarPOS|| WIZARPOS_Q3|| WIZARPOS Q3|| Q3A7 || Q3R
|-
| Q3 || wizarPOS|| wizarPOS|| WIZARPOS_Q3|| WIZARPOS Q3|| Q3A7 || Q3V
|-
| Q3 || wizarPOS|| wizarPOS|| WIZARPOS_Q3|| WIZARPOS Q3|| Q3A7 || Q3W
|}

Android provides a simple way to get system information. The code snippet is as follows:
<syntaxhighlight lang="java">
String model = getSystemPropertie("ro.wp.product.model").trim()
public static String getSystemPropertie(String key) {
Object strVersion = null;
try {
Class<?> systemProperties = Class.forName("android.os.SystemProperties");
Log.i("systemProperties", systemProperties.toString());
strVersion = systemProperties.getMethod("get", new Class[] { String.class, String.class }).invoke(systemProperties, new Object[] { key, "unknown" });
Log.i("strVersion", strVersion.getClass().toString());
} catch (Exception e) {
e.printStackTrace();
}
return strVersion.toString();
}
</syntaxhighlight >

How to Push Apps to Multiple Terminals Across Different Groups Using Tags

2022-12-12T10:30:38Z

Hans:

In wizarview, all the termials are managed in groups. It's simple to configure same apps to all the terminals in one group. But if you want to configure apps to the terminals in some different groups, you should use Tag. Tag is another dimession to manage terminals app with different purpose. It can cross groups.

=== Create Tag ===
Click Terminal>Terminal Tag, it will display the Tag list, click Add icon, then create new tag for different requirements, for example we can create 3 tags, gym, catering, loyalty:
[[File:Gymtag-create.png|none|300px|left|caption]]
[[File:Cateringtag_create.png|none|300px|left|caption]]
[[File:Loyaltytag_create.png|none|300px|left|caption]]
=== Configure Tag ===
Click Config icon, it will display Tag Configure window.
[[File:TagConfig.png|none|500px|left|caption]]
In the bottom Terminal List, choose terminals, perhaps the terminals are in different groups, for example terminals in East City group, North City group, click Configure button in the bottom, then they can configure the same tag.

Click Config Application tab, then configure Apps for the tag:
[[File:Tagconfigapp.png|none|500px|left|caption]]
In the bottom Application List, choose application, then click Configure button, you can configure many apps for the tag.
After above two steps, the tag has configured successfully, but if you want batch configure terminals, you can click Batch Config Terminal tab, input SNs as requirement.

=== Push Tag ===
Choose the tag in tag list, click Push Apps, it will push immediately.

=== Monitor the Tag download status ===
Choose Monitor>Download log, input the tag name in Application input area, click Search button, if will display the terminals which downloaded the tag.

How to Push Apps to Multiple Terminals Across Different Groups Using Tags

2022-12-12T10:30:18Z

Hans:

In wizarview, all the termials are managed in groups. It's simple to configure same apps to all the terminals in one group. But if you want to configure apps to the terminals in some different groups, you should use Tag. Tag is another dimession to manage terminals app with different purpose. It cross groups.

=== Create Tag ===
Click Terminal>Terminal Tag, it will display the Tag list, click Add icon, then create new tag for different requirements, for example we can create 3 tags, gym, catering, loyalty:
[[File:Gymtag-create.png|none|300px|left|caption]]
[[File:Cateringtag_create.png|none|300px|left|caption]]
[[File:Loyaltytag_create.png|none|300px|left|caption]]
=== Configure Tag ===
Click Config icon, it will display Tag Configure window.
[[File:TagConfig.png|none|500px|left|caption]]
In the bottom Terminal List, choose terminals, perhaps the terminals are in different groups, for example terminals in East City group, North City group, click Configure button in the bottom, then they can configure the same tag.

Click Config Application tab, then configure Apps for the tag:
[[File:Tagconfigapp.png|none|500px|left|caption]]
In the bottom Application List, choose application, then click Configure button, you can configure many apps for the tag.
After above two steps, the tag has configured successfully, but if you want batch configure terminals, you can click Batch Config Terminal tab, input SNs as requirement.

=== Push Tag ===
Choose the tag in tag list, click Push Apps, it will push immediately.

=== Monitor the Tag download status ===
Choose Monitor>Download log, input the tag name in Application input area, click Search button, if will display the terminals which downloaded the tag.

How to Push Apps to Multiple Terminals Across Different Groups Using Tags

2022-12-12T10:26:11Z

Hans:

In wizarview, all the termials are managed in groups. It's simple to configure same apps to all the terminals in one group. But if you want to configure apps to the terminals in some different groups, you should use Tag.

=== Create Tag ===
Click Terminal>Terminal Tag, it will display the Tag list, click Add icon, then create new tag for different requirements, for example we can create 3 tags, gym, catering, loyalty:
[[File:Gymtag-create.png|none|300px|left|caption]]
[[File:Cateringtag_create.png|none|300px|left|caption]]
[[File:Loyaltytag_create.png|none|300px|left|caption]]
=== Configure Tag ===
Click Config icon, it will display Tag Configure window.
[[File:TagConfig.png|none|500px|left|caption]]
In the bottom Terminal List, choose terminals, perhaps the terminals are in different groups, for example terminals in East City group, North City group, click Configure button in the bottom, then they can configure the same tag.

Click Config Application tab, then configure Apps for the tag:
[[File:Tagconfigapp.png|none|500px|left|caption]]
In the bottom Application List, choose application, then click Configure button, you can configure many apps for the tag.
After above two steps, the tag has configured successfully, but if you want batch configure terminals, you can click Batch Config Terminal tab, input SNs as requirement.

=== Push Tag ===
Choose the tag in tag list, click Push Apps, it will push immediately.

=== Monitor the Tag download status ===
Choose Monitor>Download log, input the tag name in Application input area, click Search button, if will display the terminals which downloaded the tag.

How to Push Apps to Multiple Terminals Across Different Groups Using Tags

2022-12-12T10:25:41Z

Hans:

In wizarview, all the termials are managed in groups. It's simple to configure same apps to all the terminals in one group. But if you want to configure apps to the terminals in some different groups, you should use Tag.

=== Create tag ===
Click Terminal>Terminal Tag, it will display the Tag list, click Add icon, then create new tag for different requirements, for example we can create 3 tags, gym, catering, loyalty:
[[File:Gymtag-create.png|none|300px|left|caption]]
[[File:Cateringtag_create.png|none|300px|left|caption]]
[[File:Loyaltytag_create.png|none|300px|left|caption]]
=== Configure tag ===
Click Config icon, it will display Tag Configure window.
[[File:TagConfig.png|none|500px|left|caption]]
In the bottom Terminal List, choose terminals, perhaps the terminals are in different groups, for example terminals in East City group, North City group, click Configure button in the bottom, then they can configure the same tag.

Click Config Application tab, then configure Apps for the tag:
[[File:Tagconfigapp.png|none|500px|left|caption]]
In the bottom Application List, choose application, then click Configure button, you can configure many apps for the tag.
After above two steps, the tag has configured successfully, but if you want batch configure terminals, you can click Batch Config Terminal tab, input SNs as requirement.

=== Push tag ===
Choose the tag in tag list, click Push Apps, it will push immediately.

=== Monitor the tag download status ===
Choose Monitor>Download log, input the tag name in Application input area, click Search button, if will display the terminals which downloaded the tag.

How to Push Apps to Multiple Terminals Across Different Groups Using Tags

2022-12-12T10:24:56Z

Hans:

In wizarview, all the termials are managed in groups. It's simple to configure same apps to all the terminals in one group. But if you want to configure apps to terminals in different groups, you should use Tag.

=== Create tag ===
Click Terminal>Terminal Tag, it will display the Tag list, click Add icon, then create new tag for different requirements, for example we can create 3 tags, gym, catering, loyalty:
[[File:Gymtag-create.png|none|300px|left|caption]]
[[File:Cateringtag_create.png|none|300px|left|caption]]
[[File:Loyaltytag_create.png|none|300px|left|caption]]
=== Configure tag ===
Click Config icon, it will display Tag Configure window.
[[File:TagConfig.png|none|500px|left|caption]]
In the bottom Terminal List, choose terminals, perhaps the terminals are in different groups, for example terminals in East City group, North City group, click Configure button in the bottom, then they can configure the same tag.

Click Config Application tab, then configure Apps for the tag:
[[File:Tagconfigapp.png|none|500px|left|caption]]
In the bottom Application List, choose application, then click Configure button, you can configure many apps for the tag.
After above two steps, the tag has configured successfully, but if you want batch configure terminals, you can click Batch Config Terminal tab, input SNs as requirement.

=== Push tag ===
Choose the tag in tag list, click Push Apps, it will push immediately.

=== Monitor the tag download status ===
Choose Monitor>Download log, input the tag name in Application input area, click Search button, if will display the terminals which downloaded the tag.

How to Push Apps to Multiple Terminals Across Different Groups Using Tags

2022-12-12T10:13:08Z

Hans: /* By Group */

== By Group ==
To terminals in one group, it is simple, configure apps to the group, then all terminals in the group, will download and install those apps.

== By Tag ==
To terminals in different groups, that is a little complicated, it need create a tag.
=== Create tag ===
Click Terminal>Terminal Tag, it will display the Tag list, click Add icon, then create new tag for different requirements, for example we can create 3 tags, gym, catering, loyalty:
[[File:Gymtag-create.png|none|300px|left|caption]]
[[File:Cateringtag_create.png|none|300px|left|caption]]
[[File:Loyaltytag_create.png|none|300px|left|caption]]
=== Configure tag ===
Click Config icon, it will display Tag Configure window.
[[File:TagConfig.png|none|500px|left|caption]]
In the bottom Terminal List, choose terminals, perhaps the terminals are in different groups, for example terminals in East City group, North City group, click Configure button in the bottom, then they can configure the same tag.

Click Config Application tab, then configure Apps for the tag:
[[File:Tagconfigapp.png|none|500px|left|caption]]
In the bottom Application List, choose application, then click Configure button, you can configure many apps for the tag.
After above two steps, the tag has configured successfully, but if you want batch configure terminals, you can click Batch Config Terminal tab, input SNs as requirement.

=== Push tag ===
Choose the tag in tag list, click Push Apps, it will push immediately.

=== Monitor the tag download status ===
Choose Monitor>Download log, input the tag name in Application input area, click Search button, if will display the terminals which downloaded the tag.

How to Push Apps to Multiple Terminals Across Different Groups Using Tags

2022-12-12T10:12:42Z

Hans: /* By Tag */

== By Group ==
For terminals in one group, it is simple, configure app to the group, then all terminals in the group, will download and install that app.
== By Tag ==
To terminals in different groups, that is a little complicated, it need create a tag.
=== Create tag ===
Click Terminal>Terminal Tag, it will display the Tag list, click Add icon, then create new tag for different requirements, for example we can create 3 tags, gym, catering, loyalty:
[[File:Gymtag-create.png|none|300px|left|caption]]
[[File:Cateringtag_create.png|none|300px|left|caption]]
[[File:Loyaltytag_create.png|none|300px|left|caption]]
=== Configure tag ===
Click Config icon, it will display Tag Configure window.
[[File:TagConfig.png|none|500px|left|caption]]
In the bottom Terminal List, choose terminals, perhaps the terminals are in different groups, for example terminals in East City group, North City group, click Configure button in the bottom, then they can configure the same tag.

Click Config Application tab, then configure Apps for the tag:
[[File:Tagconfigapp.png|none|500px|left|caption]]
In the bottom Application List, choose application, then click Configure button, you can configure many apps for the tag.
After above two steps, the tag has configured successfully, but if you want batch configure terminals, you can click Batch Config Terminal tab, input SNs as requirement.

=== Push tag ===
Choose the tag in tag list, click Push Apps, it will push immediately.

=== Monitor the tag download status ===
Choose Monitor>Download log, input the tag name in Application input area, click Search button, if will display the terminals which downloaded the tag.

How to Evaluate Terminal Print Performance

2022-11-01T08:34:04Z

Hans:

The printing performance of the terminal is as follows:

Column 3 shows how long it took the program to call the print method until the paper started moving.

Column 4 shows how long it took the program to call the print method until the print is complete.

Q2:
{| class="wikitable"
|-
! print method !! receipt length !! paper begin to move (s) !! print finish/method return (s)!!feeling speed (mm/s)
|-
| printText || 60 lines/~30 cm|| 0.1 || 5.5 || ~54
|-
| printText || 120 lines/~60 cm|| 0.2 || 11.3 || ~53
|-
| printBitmap || 25 cm|| 0.3 || 3.6 || ~69
|-
| printBitmap || 50 cm|| 0.4 || 7.6 || ~66
|-
| printBitmap || 75 cm|| 0.6 || 11.6 || ~65
|-
| printHTML || 25 cm|| 1.3 || 4.7 || ~53
|-
| printHTML || 50 cm|| 1.5 || 8.8 || ~57
|-
| printHTML || 75 cm|| 1.6 || 12.7 || ~59
|}

Q1v2:
{| class="wikitable"
|-
! print method !! receipt length !! paper begin to move (s) !! print finish/method return (s)!!feeling speed (mm/s)
|-
| printText || 60 lines/~30 cm|| 0.1 || 6.3 || ~47
|-
| printText || 120 lines/~60 cm|| 0.2 || 12.6 || ~47
|-
| printBitmap || 25 cm|| 0.3 || 4.5 || ~55
|-
| printBitmap || 50 cm|| 0.4 || 8.9 || ~56
|-
| printBitmap || 75 cm|| 0.5 || 13.6 || ~55
|-
| printHTML || 25 cm|| 1.2 || 5.7 || ~44
|-
| printHTML || 50 cm|| 1.3 || 10 || ~50
|-
| printHTML || 75 cm|| 1.4 || 14 || ~54
|}

How to Understand TMS Server IP Addresses and Port Configuration

2022-09-30T01:41:27Z

Hans:

==TMS server IP==
The main server of TMS is located in www.wizarview.com . There are also several assistant servers located in different countries.

'''Main Server:''' 
(port 80, 443) 
www.wizarview.com [default 129.153.119.200 ], [bak 47.243.18.36 ]

'''Communication Server:''' 
(port 11884) 
mqtt.wizarview.com [ 129.153.221.231 ]

'''Download Servers:''' 
www.wizarview.com [129.153.119.200 ] port 8743 8680 
hk.wizarview.com [ 47.91.186.174 ] port 443 8780 
dluae.wizarview.com [193.123.67.48] port 443 8680 
dev.wizarpos.com [180.168.95.118] port 8743 8088 
sg.wizarview.com [129.150.38.203] port 443 8680 

'''Monitor server:''' 
(port 12010, 12011, 12012) 
remote.wizarview.com [47.243.18.36] 
remoteme.wizarview.com [193.123.67.48]

==Ports==
{| class="wikitable"
|-
! Port !!Server !! Description
|-
| TCP 80, 443 || Main Sever|| User login and terminal HTTP request.
|-
| TCP 11884 || Communication Server|| Used by terminal agent to keep connection.
|-
| TCP 8680, 8780, 8681|| Download Server|| Used by terminal to download application.
|-
| TCP 12010, 12011, 12012|| Monitor Server|| Used by terminal remote monitoring.
|-
| TCP 8080|| Main Sever || Used by terminal HTTP request. (Agent version < 4.4).
|-
| TCP 5222, 27777|| Main Server|| Used by terminal access. (Agent version < 4.1).
|}

How to Understand TMS Server IP Addresses and Port Configuration

2022-09-14T06:47:39Z

Hans:

==TMS server IP==
The main server of TMS is located in www.wizarview.com . There are also several assistant servers located in different countries.

'''Main Server:''' 
(port 80, 443) 
www.wizarview.com [default 129.153.119.200 ], [bak 47.243.18.36 ]

'''Communication Server:''' 
(port 11884) 
mqtt.wizarview.com [ 129.153.221.231 ]

'''Download Servers:''' 
www.wizarview.com [129.153.119.200 ] port 8743 8680 
hk.wizarview.com [ 47.91.186.174 ] port 443 8780 
dluae.wizarview.com [193.123.67.48] port 443 8680 
dev.wizarpos.com [180.168.95.118] port 8743 8088

'''Monitor server:''' 
(port 12010, 12011, 12012) 
remote.wizarview.com [47.243.18.36] 
remoteme.wizarview.com [193.123.67.48]

==Ports==
{| class="wikitable"
|-
! Port !!Server !! Description
|-
| TCP 80, 443 || Main Sever|| User login and terminal HTTP request.
|-
| TCP 11884 || Communication Server|| Used by terminal agent to keep connection.
|-
| TCP 8680, 8780, 8681|| Download Server|| Used by terminal to download application.
|-
| TCP 12010, 12011, 12012|| Monitor Server|| Used by terminal remote monitoring.
|-
| TCP 8080|| Main Sever || Used by terminal HTTP request. (Agent version < 4.4).
|-
| TCP 5222, 27777|| Main Server|| Used by terminal access. (Agent version < 4.1).
|}

How to Understand TMS Server IP Addresses and Port Configuration

2022-09-14T06:47:15Z

Hans:

==TMS server IP==
The main server of TMS is located in www.wizarview.com . There are also several assistant servers located in different countries.

'''Main Server:''' 
(port 80, 443) 
www.wizarview.com [default 129.153.119.200 ], [bak 47.243.18.36 ]

'''Communication Server:''' 
(port 11884) 
mqtt.wizarview.com [ 129.153.221.231 ]

'''Download Servers:''' 
www.wizarview.com [129.153.119.200 ] port 8743 8680 
hk.wizarview.com [ 47.91.186.174 ] port 443 8780 
dluae.wizarview.com [193.123.67.48] port 443 8680 
dev.wizarpos.com [180.168.95.118] port 8743 8088

'''Monitor server:''' 
(port 12010, 12011, 12012) 
remote.wizarview.com [47.243.18.36]
remoteme.wizarview.com [193.123.67.48]

==Ports==
{| class="wikitable"
|-
! Port !!Server !! Description
|-
| TCP 80, 443 || Main Sever|| User login and terminal HTTP request.
|-
| TCP 11884 || Communication Server|| Used by terminal agent to keep connection.
|-
| TCP 8680, 8780, 8681|| Download Server|| Used by terminal to download application.
|-
| TCP 12010, 12011, 12012|| Monitor Server|| Used by terminal remote monitoring.
|-
| TCP 8080|| Main Sever || Used by terminal HTTP request. (Agent version < 4.4).
|-
| TCP 5222, 27777|| Main Server|| Used by terminal access. (Agent version < 4.1).
|}

How to Understand TMS Server IP Addresses and Port Configuration

2022-09-01T10:17:37Z

Hans:

==TMS server IP==
The main server of TMS is located in www.wizarview.com . There are also several assistant servers located in different countries.

'''Main Server:''' 
(port 80, 443) 
www.wizarview.com [default 129.153.119.200 ], [bak 47.243.18.36 ]

'''Communication Server:''' 
(port 11884) 
mqtt.wizarview.com [ 129.153.221.231 ]

'''Download Servers:''' 
www.wizarview.com [129.153.119.200 ] port 8743 8680 
hk.wizarview.com [ 47.91.186.174 ] port 443 8780 
dluae.wizarview.com [193.123.67.48] port 443 8680 
dev.wizarpos.com [180.168.95.118] port 8743 8088

'''Monitor server:''' 
(port 12010, 12011, 12012) 
remote.wizarview.com [47.243.18.36]

==Ports==
{| class="wikitable"
|-
! Port !!Server !! Description
|-
| TCP 80, 443 || Main Sever|| User login and terminal HTTP request.
|-
| TCP 11884 || Communication Server|| Used by terminal agent to keep connection.
|-
| TCP 8680, 8780, 8681|| Download Server|| Used by terminal to download application.
|-
| TCP 12010, 12011, 12012|| Monitor Server|| Used by terminal remote monitoring.
|-
| TCP 8080|| Main Sever || Used by terminal HTTP request. (Agent version < 4.4).
|-
| TCP 5222, 27777|| Main Server|| Used by terminal access. (Agent version < 4.1).
|}

How to Understand TMS Server IP Addresses and Port Configuration

2022-09-01T01:29:45Z

Hans:

==TMS server IP==
The main server of TMS is located in www.wizarview.com . There are also several assistant servers located in different countries.

'''Main Server:''' 
(port 80, 443) 
www.wizarview.com [default 129.153.119.200 ], [bak 47.243.18.36 ]

'''Communication Server:''' 
(port 11884) 
mqtt.wizarview.com [ 129.153.221.231 ]

'''Download Servers:''' 
www.wizarview.com [129.153.119.200 ] port 8743 8680 
hk.wizarview.com [ 47.91.186.174 ] port 443 8780 
dluae.wizarview.com [193.123.66.24] port 443 8680 
dev.wizarpos.com [180.168.95.118] port 8743 8088

'''Monitor server:''' 
(port 12010, 12011, 12012) 
remote.wizarview.com [47.243.18.36]

==Ports==
{| class="wikitable"
|-
! Port !!Server !! Description
|-
| TCP 80, 443 || Main Sever|| User login and terminal HTTP request.
|-
| TCP 11884 || Communication Server|| Used by terminal agent to keep connection.
|-
| TCP 8680, 8780, 8681|| Download Server|| Used by terminal to download application.
|-
| TCP 12010, 12011, 12012|| Monitor Server|| Used by terminal remote monitoring.
|-
| TCP 8080|| Main Sever || Used by terminal HTTP request. (Agent version < 4.4).
|-
| TCP 5222, 27777|| Main Server|| Used by terminal access. (Agent version < 4.1).
|}