Home » Epson Manuals » Electronics Accessories » Epson BT-2000 » Manual Viewer

Epson BT-2000 Developers Guide - Page 32

Hardware, buttons, Key event

View all Epson BT-2000 manuals

Add to My Manuals
Save this manual to your list of manuals

Page 32 highlights

Hardware buttons A button B button X button Y button D-pad up D-pad down D-pad left D-pad right select/OK key Key event KeyEvent.KEYCODE_F1 KeyEvent.KEYCODE_F2 KeyEvent.KEYCODE_F3 KeyEvent.KEYCODE_F4 KeyEvent.KEYCODE_DPAD_UP KeyEvent.KEYCODE_DPAD_DOWN KeyEvent.KEYCODE_DPAD_LEFT KeyEvent.KEYCODE_DPAD_RIGHT KeyEvent.KEYCODE_DPAD_CENTER ■ Using the change function for key assignments By changing the key assignments, the key codes called when you press the A, B, X, or Y buttons are not the standard Back, Home, or Menu buttons in Android, instead, the key codes are changed to F1 to F4. Therefore, you can include optional funtions to the F1 to F4 codes making use of the A, B, X, and Y buttons as with the application's original function. ■ Specifications for status transitions in key assignment mode Status transitions (where the value of the key is changed) for the key assignment mode cannot be set in the app; they should be set in the system. For example, when the key assignment mode for application A is set to User mode, and then a different application B is started, the key assignment mode for application B is also set to User mode. The BT-2000 is equipped with a standard iWnnIME text input system. This system uses the Back, Menu, and D-pad keys for input, and automatically changes the key assignments to Default mode when starting up the BT-2000. When closing an app, the key assignment mode changes to the mode set in iWnnIME for the last app that was started, however operations are not guaranteed when an error occurs or if the app does not close normally. For key assignment mode management, we recommend using the mode used for the last app to be started. When an app is constructed with multiple source calls, and calls that apply not just iWnnIME, we recommend managing the key assignment status according to each app that is started. MOVERIO Pro Developer's Guide (Rev.1.0) 28

Section	Page
1. Introduction	5
1.1. Product Summary and Functions	6
1.2. Main System Specifications	7
1.3. Basic Information for App Development	8
1.4. Other Main Functions	9
2. Developing Apps	10
2.1. Summary of Developing Apps	11
2.2. Introduction to the Android SDK	12
1.	12
2.	12
2.1	12
2.2	12
2.2.1.1. Acquiring Android Studio	12
2.2.1.2. Acquiring and installing JDK	12
2.2.1.3. Installing Android Studio	12
2.2.1.4. Installing Platform-tools, SDK Platform, and USB Driver	13
2.3. ADB driver settings	15
2.3	15
2.3.1.1. Editing the Google USB Driver	15
2.3.1.2. Vendor ID setting	16
2.4. Connecting the BT-2000 to a computer	17
2.4	17
2.4.1.1. BT-2000 settings	17
2.4.1.2. Install the BT-2000 driver	17
2.4.1.3. Checking the connection	18
2.5. Including the SDK provided by EPSON	19
3. Display control	20
3.1. Display control summary	21
3.2. Full screen display function	22
3.3. Switch between 2D/3D display function	24
3.4. Backlight control	25
3.4.1. Adjust backlight brightness	25
3.4.2. Backlight auto dimmer	25
3.5. Mute function	26
3.5.1. Display mute	26
3.5.2. Audio mute	26
3.6. See-through function	27
4. UI control	28
4.1. UI control summary	29
4.1.1. Hardware button types and functions	29
4.1.2. BT-2000 change key assignment function	31
4.2. Application interface list	33
4.3. Application interface details	34
4.3.1. getKeyAssignMode	34
4.3.2. setKeyAssignMode	35
5. Audio commands	36
5.1. Audio commands summary	37
5.2. Application interface function summary	38
5.3. Application interface list	39
5.4. Application interface details	40
5.4.1. setSnr	40
5.4.2. getSnr	40
5.4.3. setAmp	41
5.4.4. getAmp	42
5.4.5. start	42
5.4.6. stop	43
5.4.7. registerCallback	43
5.4.8. unRegisterCallback	44
5.4.9. getVoiceCommandSystemInterface	44
5.4.10. bindToRemoteRunningService	45
5.4.11. unBindFromRemoteRunningService	45
5.5. Others	46
5.5.1. Timing for reflecting the setting for the voice recognition start conditions	46
5.5.2. List of default lms files and vocabulary	46
5.5.3. Callbacks that acquire recognition results	48
5.5.4. Audio command API usage flow example	48
6. Camera control	49
6.1. Function summary	50
6.2. Available parameters	51
6.3. Image organization and format	52
6.4. Depth data characteristics	53
6.5. Application interface function summary	55
6.6. Application interface list	56
6.7. Application interface details	58
6.7.1. getSupportedEpsonCameraMode	58
6.7.2. setEpsonCameraMode	60
6.7.3. getEpsonCameraMode	63
6.7.4. setPreviewFpsRange	64
6.7.5. setPreviewSize	66
6.7.6. getSupportedSharpnessMin/getSupportedSharpnessMax	68
6.7.7. getSharpness	69
6.7.8. setSharpness	70
6.7.9. getSupportedContrastMin/getSupportedContrastMax	71
6.7.10. getContrast	72
6.7.11. setContrast	73
6.7.12. onPreviewFrame	74
6.7.13. setPreviewCallback	76
6.7.14. setOneShotPreviewCallback	78
6.7.15. setPreviewCallbackWithBuffer	79
6.7.16. addCallbackBuffer	81
startDepthStreaming	83
6.7.17. stopDepthStreaming	85
6.7.18. onDepthMap	86
6.7.19. setDepthCallback	88
6.8. Depth Information Acquisition Flow Details	90
6.9. Sample Code	92
6.10. Important points	96
7. Sensor control	97
7.1. Sensor control summary	98
7.1.1. IMU and the geomagnetic sensor	98
7.1.2. ALS	99
7.1.3. Headset tap detection	100
7.2. Using the sensor	101
7.2.1. Sensor type	101
7.3. Using SensorEventListener	102
7.3.1. Registering sensors being used	102
7.3.2. Acquiring a sensor value	102
8. Bluetooth/BLE	103
8.1. Summary	104
8.1.1. Supported specifications	104
8.1.1.1. Bluetooth Legacy specifications	104
8.1.1.2. BLE specifications	105
8.2. Usage method	106
8.2.1. Using Bluetooth Legacy	106
8.2.1.1. Turning Bluetooth Legacy ON/OFF	106
8.2.1.2. Searching using Bluetooth Legacy	106
8.2.1.3. Connecting using Bluetooth Legacy	106
8.2.1.4. Disconnecting using Bluetooth Legacy	106
8.2.2. Using BLE	107
8.2.2.1. Using the BLEBeacon sample application	107
8.2.2.2. Using the FMP_PXP sample application	109
8.3. Important Points & Restrictions for BLE App Development	112
8.4. Import module	113
8.5. Application interface list	114
8.6. Supported GATT procedure table	116
8.7. Application interface details	117
8.7.1. getInstance	117
8.7.2. isEnable	117
8.7.3. enable	118
8.7.4. disable	118
8.7.5. startScan	119
8.7.6. stopScan	120
8.7.7. getDeviceName	120
8.7.8. getBdAddress	121
8.7.9. connect	122
8.7.10. connectCancel	124
8.7.11. disconnect	125
8.7.12. setAuthType	126
8.7.13. notifyInputPasskey	127
8.7.14. setGapCallback	128
8.7.15. discPriSrv	129
8.7.16. discChar	130
8.7.17. discCharDesc	131
8.7.18. readGatt	132
8.7.19. readUuidGatt	133
8.7.20. writeWithoutRspGatt	134
8.7.21. writeGatt	135
8.7.22. confirmation	136
8.7.23. setGattCallback	137
8.7.24. BluetoothLeGapCallback.onScanResult	138
8.7.25. BluetoothLeGapCallback.onConnectResult	139
8.7.26. BluetoothLeGapCallback.onDisconnectResult	141
8.7.27. BluetoothLeGapCallback.onPasskeyInput	142
8.7.28. BluetoothLeGapCallback.onPasskeyDisplay	142
8.7.29. BluetoothLeGattCallback.onDiscPriSrvResult	143
8.7.30. BluetoothLeGattCallback.onDiscCharResult	145
8.7.31. BluetoothLeGattCallback.onDiscCharDescResult	146
8.7.32. BluetoothLeGattCallback.onReadGattResult	147
8.7.33. BluetoothLeGattCallback.onReadUuidGattResult	148
8.7.34. BluetoothLeGattCallback.onWriteGattResult	149
8.7.35. BluetoothLeGattCallback.hvxEvt	150
8.8. BLE Processing Sample Code	151
8.8.1. Enabling BLE	151
8.8.2. Disabling BLE	151
8.8.3. Registering scan start and callback	152
8.8.4. Connecting and Disconnecting BLE	153
8.8.5. Searching for Primary Service	155
8.8.6. Searching for Characteristic	156
8.8.7. Searching for Characteristic Descriptor	157
8.8.8. Acquiring Characteristic Value by Specifying a Handle	158
8.8.9. Acquiring Characteristic Value by Specifying a UUID	159
8.8.10. Writing a Characteristic Value	160
9. Power control	161
9.1. Power control summary	162
9.2. Acquiring Battery Information	163
10. Appendix	164
10.1. Self-diagnostic function	165
10.1.1. Self-diagnostic function summary	165

Match case Limit results 1 per page

MOVERIO Pro Developer's Guide (Rev.1.0)

Hardware

buttons

Key event

A button

KeyEvent.KEYCODE_F1

B button

KeyEvent.KEYCODE_F2

X button

KeyEvent.KEYCODE_F3

Y button

KeyEvent.KEYCODE_F4

D-pad up

KeyEvent.KEYCODE_DPAD_UP

D-pad down

KeyEvent.KEYCODE_DPAD_DOWN

D-pad left

KeyEvent.KEYCODE_DPAD_LEFT

D-pad right

KeyEvent.KEYCODE_DPAD_RIGHT

select/OK key

KeyEvent.KEYCODE_DPAD_CENTER

■ Using the change function for key assignments

By changing the key assignments, the key codes called when you press the A, B, X, or Y buttons

are not the standard Back, Home, or Menu buttons in Android, instead, the key codes are

changed to F1 to F4.

Therefore, you can include optional funtions to the F1 to F4 codes making use of the A, B, X, and

Y buttons as with the application's original function.

■ Specifications for status transitions in key assignment mode

Status transitions (where the value of the key is changed) for the key assignment mode cannot

be set in the app; they should be set in the system. For example, when the key assignment

mode for application A is set to User mode, and then a different application B is started, the key

assignment mode for application B is also set to User mode.

The BT-2000 is equipped with a standard iWnnIME text input system. This system uses the

Back, Menu, and D-pad keys for input, and automatically changes the key assignments to

Default mode when starting up the BT-2000. When closing an app, the key assignment mode

changes to the mode set in iWnnIME for the last app that was started, however operations are

not guaranteed when an error occurs or if the app does not close normally. For key assignment

mode management, we recommend using the mode used for the last app to be started.

When an app is constructed with multiple source calls, and calls that apply not just iWnnIME, we

recommend managing the key assignment status according to each app that is started.