Sei sulla pagina 1di 16

ENTERPRISE BROWSER V1.8

CONTENTS

1. Description

2. Release Notes

3. Device Compatibility

4. Components

5. Installation

6. Usage Notes

7. Issues fixed in this release

8. Known Issues

9. Supported Ciphers

10. Part Numbers

DESCRIPTION

Thank you for selecting Enterprise Browser as your mobility solution tool. User friendly mobile applications are key to leveraging the power, value and return on investment of mobile solutions and Enterprise Browser can significantly reduce the time and cost associated with mobile application development.

Enterprise Browser allows creation of flexible, OS-independent, hardware-agnostic applications that look, feel and act the same on every supported device and that can include a wide range of advanced data capture capabilities. Whether you want to streamline your warehouse, delivery or service operations or enable more robust asset tracking and visibility, Enterprise Browser will help you get your enterprise mobility solution up and running.

RELEASE NOTES

Version 1.8

New Zebra Device Support1.8 See also Enterprise Browser 1.8 online documentation . CC5000-10 Android Lollipop MC33X Android Nougat MC55X

CC5000-10 Android LollipopBrowser 1.8 online documentation . New Zebra Device Support MC33X Android Nougat MC55X Windows Embedded Handheld

MC33X Android Nougat. New Zebra Device Support CC5000-10 Android Lollipop MC55X Windows Embedded Handheld 6.5 MC55X Health Care

MC55X Windows Embedded Handheld 6.5Support CC5000-10 Android Lollipop MC33X Android Nougat MC55X Health Care Windows Embedded Handheld 6.5 TC51 Android

MC55X Health Care Windows Embedded Handheld 6.5MC33X Android Nougat MC55X Windows Embedded Handheld 6.5 TC51 Android Nougat TC51 Health Care Android Nougat

TC51 Android NougatHandheld 6.5 MC55X Health Care Windows Embedded Handheld 6.5 TC51 Health Care Android Nougat TC56 Android

TC51 Health Care Android NougatCare Windows Embedded Handheld 6.5 TC51 Android Nougat TC56 Android Nougat TC70X Android Nougat TC75X Android

TC56 Android Nougat6.5 TC51 Android Nougat TC51 Health Care Android Nougat TC70X Android Nougat TC75X Android Nougat VC80X

TC70X Android NougatNougat TC51 Health Care Android Nougat TC56 Android Nougat TC75X Android Nougat VC80X Android Nougat Ultra-Rugged

TC75X Android NougatCare Android Nougat TC56 Android Nougat TC70X Android Nougat VC80X Android Nougat Ultra-Rugged Scanner Support DS3678

VC80X Android NougatAndroid Nougat TC70X Android Nougat TC75X Android Nougat Ultra-Rugged Scanner Support DS3678 - Now also supported

Ultra-Rugged Scanner SupportAndroid Nougat TC75X Android Nougat VC80X Android Nougat DS3678 - Now also supported on Android Nougat

DS3678 - Now also supported on Android Nougat devices. - Now also supported on Android Nougat devices.

Enhancement To Existing Custom On-screen Buttons/Keyboard Feature For Android PlatformDS3678 - Now also supported on Android Nougat devices. Custom On-screen Buttons/Keyboard Usage Guide ButtonBar XML

Platform Custom On-screen Buttons/Keyboard Usage Guide ButtonBar XML Guide - New ButtonBar and Button-Specific

ButtonBar XML Guide - New ButtonBar and Button-Specific parameters has been introduced.

XML Guide - New ButtonBar and Button-Specific parameters has been introduced. ButtonBar Parameters barTextColor
XML Guide - New ButtonBar and Button-Specific parameters has been introduced. ButtonBar Parameters barTextColor

ButtonBar API - 40 New ButtonBar APIs has been added. ButtonBar API - 40 New ButtonBar APIs has been added.

New Configuration Parameters (in Config.xml) For Android PlatformButtonBar API - 40 New ButtonBar APIs has been added. User Experience Related Features Disable Hardware

User Experience Related FeaturesParameters (in Config.xml) For Android Platform Disable Hardware Acceleration At Webview Level Inside

Disable Hardware Acceleration At Webview Level Inside Enterprise Browser Application - Note: By default, Hardware Acceleration will always be enabled within Enterprise Browser application at - Note: By default, Hardware Acceleration will always be enabled within Enterprise Browser application at Application Level.

Disable All IMEs(Input Method Editors) Inside Enterprise Browser Applicationat Application Level. <DisableHardwareAcceleration> <DisableAllIME> Controls Hiding Of System Bar Inside

Controls Hiding Of System Bar Inside Enterprise Browser ApplicationEnterprise Browser Application <DisableAllIME> <HideSystemBar> Web Related Features Web Security

Web Related FeaturesEnterprise Browser Application <HideSystemBar> Web Security <ClientCertificate> - Used for

Web SecurityApplication <HideSystemBar> Web Related Features <ClientCertificate> - Used for validating the

<ClientCertificate> - Used for validating the Client Certificate silently. <ClientCertificate> - Used for validating the Client Certificate silently.

New Methods/Properties/Callback For Android Platform- Used for validating the Client Certificate silently. System API Property - deviceHostName SignalIndicators API

Property - deviceHostName deviceHostName

New Callback Parameter of wlanStatus Method - New parameters has been added to the existing callback of wlanStatus method. wlanStatus Method - New parameters has been added to the existing callback of wlanStatus method.

Callback Parameter - deviceHostName deviceHostName

New signalEvent Parameter - New parameters has been added to the existing signalEvent . signalEvent Parameter - New parameters has been added to the existing signalEvent.

Parameter - deviceHostName deviceHostName

Barcode API - Applicable on Android platform with EMDK version 6.6 and above. Barcode API - Applicable on Android platform with EMDK version 6.6 and above.

Multi-Barcode and UDI Supporton Android platform with EMDK version 6.6 and above. New Callback Parameter of enable Method -

New Callback Parameter of enable Method - New parameters has been added to the existing callback of enable method enable Method - New parameters has been added to the existing callback of enable method for supporting Multi-Barcode and UDI.

Callback Parameter - isUDIData isUDIData

Callback Parameter - label label

Callback Parameter - UDITokenizedData UDITokenizedData

Property - scanMode scanMode

Property - enableGS1 enableGS1

Property - enableHIBCC enableHIBCC

Property - enableICCBBA enableICCBBA

Property - adaptiveScanning adaptiveScanning

Property - aimingPattern aimingPattern

Property - connectionIdleTime connectionIdleTime

Property - codeIdType codeIdType

Property - disconnectOnExit disconnectOnExit

Property - hanXin hanXin

Property - hanXinInverse hanXinInverse

Property - mailMark mailMark

Property - upcEanCouponReport upcEanCouponReport

- pairAfterScannerReboot Property - upcEanCouponReport EzNFC API New Callback Parameter of enableRead Method -

New Callback Parameter of enableRead Method - New parameters has been added to the existing callback of enableRead method. enableRead Method - New parameters has been added to the existing callback of enableRead method.

Callback Parameter - TagManufacturerName TagManufacturerName

Callback Parameter - TagTechnologies TagTechnologies

Callback Parameter - ATQA ATQA

Callback Parameter - SAK SAK

Callback Parameter - ATS ATS

Existing proximitySensorType Property - The default value of proximitySensorType has been changed from 22 to 65538 proximitySensorType Property - The default value of proximitySensorType has been changed from 22 to 65538 for Android Lollipop & above.

Existing <DomStorageEnabled> Configuration Tag - DOM Storage will always be enabled by default within Enterprise Browser <DomStorageEnabled> Configuration Tag - DOM Storage will always be enabled by default within Enterprise Browser Application.

Enterprise Browser Application And Configuration Version Comparision - From Enterprise Browser 1.8 and above, Enterprise Browser Application and Configuration version comparison is - From Enterprise Browser 1.8 and above, Enterprise Browser Application and Configuration version comparison is now gets captured at Enterprise Browser log file.

Back to Top

DEVICE COMPATIBILITY

Zebra Devices

This software release has been approved for use with the following Enterprise Mobility devices.

Note:

Enterprise Browser 1.6 and higher versions do not support devices running Android Jelly Bean. For Android Jelly Bean support, please use Enterprise Browser 1.5 or lower versions.

Jelly Bean. For Android Jelly Bean support, please use Enterprise Browser 1.5 or lower versions. Mobile

Mobile Computers

 

DEVICE FAMILY

DEVICE

OPERATING

SUPPORTED

SYSTEM(S)

WEB VIEWS

ES400 ES400 Windows Internet

ES400

ES400

Windows

Internet

Embedded

Explorer,

Handheld 6.5

Webkit

MC18 MC18 Windows CE Internet

MC18

MC18

Windows CE

Internet

7.0

Explorer,

Android 4.4

Webkit,

(KitKat)

Android

Android 5.0

Stock

 

(Lollipop)

Webkit

MC3090 MC3000, MC3090 Windows CE Internet

MC3090

MC3000, MC3090

Windows CE

Internet

5.0

Explorer

Windows

Mobile 6.1

MC3100 MC3100R, MC3100S, MC3190G, MC3190R, MC3190S, MC3190Z Windows CE Internet

MC3100

MC3100R, MC3100S, MC3190G, MC3190R, MC3190S, MC3190Z

Windows CE

Internet

6.0

Explorer,

 

Professional

Webkit

Windows

Embedded

 

Handheld 6.5

MC32N0 MC32N0 Android 4.1 Internet

MC32N0

MC32N0

Android 4.1

Internet

(JellyBean)*

Explorer,

Android 5.0

Webkit,

(Lollipop)

Android

Windows CE

Stock

 

7.0

Webkit

MC33X MC33X Android 7.0 Android

MC33X

MC33X

Android 7.0

Android

(Nougat)

Stock

Webkit

MC40 MC40 Android 4.1 Android

MC40

MC40

Android 4.1

Android

(JellyBean)*

Stock

Android 4.4

Webkit

(KitKat)

Android 5.0

 

(Lollipop)

MC45 MC45 Windows Internet

MC45

MC45

Windows

Internet

Embedded

Explorer,

Handheld 6.5

Webkit

MC55 MC5574, MC5590 Windows Internet

MC55

MC5574, MC5590

Windows

Internet

Embedded

Explorer,

Handheld 6.5

Webkit

MC55X MC55X, MC55X Health Care Windows Internet

MC55X

MC55X, MC55X Health Care

Windows

Internet

Embedded

Explorer,

Handheld 6.5

Webkit

MC55A0 MC55A0 Windows Internet

MC55A0

MC55A0

Windows

Internet

Embedded

Explorer,

Handheld 6.5

Webkit

MC55N0 MC55N0 Windows Internet

MC55N0

MC55N0

Windows

Internet

Embedded

Explorer,

Handheld 6.5

Webkit

MC65 MC659B Windows Internet

MC65

MC659B

Windows

Internet

Embedded

Explorer,

Handheld 6.5

Webkit

MC67 MC67 Windows Internet

MC67

MC67

Windows

Internet

Embedded

Explorer,

Handheld 6.5

Webkit,

Android 4.1

Android

(JellyBean)*

Stock

 

Android 4.4

Webkit

(KitKat)

MC70 MC7004, MC7090, MC7094, MC7095 Windows Internet

MC70

MC7004, MC7090, MC7094, MC7095

Windows

Internet

Mobile 6.1

Explorer

MC75 MC7506, MC7508, MC7596, MC7598 Windows Internet

MC75

MC7506, MC7508, MC7596, MC7598

Windows

Internet

Embedded

Explorer

Handheld 6.5

MC75a MC75A0, MC75A6, MC75A8 Windows Internet

MC75a

MC75A0, MC75A6, MC75A8

Windows

Internet

Embedded

Explorer,

Handheld 6.5

Webkit

MC9000 MC9090, MC9097, MC9094 Windows CE Internet

MC9000

MC9090, MC9097, MC9094

Windows CE

Internet

5.0

Explorer

Windows

Mobile 6.1

MC9100 MC9190-G, MC9190Z Windows CE Internet

MC9100

MC9190-G, MC9190Z

Windows CE

Internet

6.0

Explorer,

Professional

Webkit

Windows

Embedded

 

Handheld 6.5

MC9200 MC92N0 Windows CE Internet

MC9200

MC92N0

Windows CE

Internet

7.0

Explorer,

Windows

Webkit,

Embedded

Android

Handheld 6.5

Stock

 

Android 4.4

Webkit

(KitKat)

MC9500 MC9590, MC9596, MC9598, MC959B (WM6.1) Windows Internet

MC9500

MC9590, MC9596, MC9598, MC959B (WM6.1)

Windows

Internet

Mobile 6.1

Explorer,

Windows

Webkit

Embedded

Handheld 6.5

Omnii XT15 XT15 Windows CE Internet

Omnii XT15

XT15

Windows CE

Internet

6.0

Explorer,

(Omnii CE-

Webkit

12.2.44149

BSP and

 

above)

     

Windows

 

Embedded

Handheld 6.5

(Omnii WEH-

8.2.44159

BSP and

above)

TC55 TC55 Android 4.1 Android

TC55

TC55

Android 4.1

Android

(JellyBean)*

Stock

Android 4.4

Webkit

(KitKat)

TC51 TC51, TC51 Health Care Android 6.0 Android

TC51

TC51, TC51 Health Care

Android 6.0

Android

(Marshmallow)

Stock

Android 7.0

Webkit

(Nougat)

TC56 TC56 Android 6.0 Android

TC56

TC56

Android 6.0

Android

(Marshmallow)

Stock

Webkit

Android 7.0

(Nougat)

TC70 TC70 GA1, TC70 GA2 Android 4.4 Android

TC70

TC70 GA1, TC70 GA2

Android 4.4

Android

(KitKat)

Stock

Android 5.0

Webkit

(Lollipop)

TC70X TC70X Android 6.0 Android

TC70X

TC70X

Android 6.0

Android

(Marshmallow)

Stock

Android 7.0

Webkit

(Nougat)

TC75 TC75 Android 4.4 Android

TC75

TC75

Android 4.4

Android

(KitKat)

Stock

Android 5.0

Webkit

(Lollipop)

TC75X TC75X Android 6.0 Android

TC75X

TC75X

Android 6.0

Android

(Marshmallow)

Stock

Android 7.0

Webkit

(Nougat)

TC8000 TC8000 Android 4.4 Android

TC8000

TC8000

Android 4.4

Android

(KitKat)

Stock

Android 5.0

Webkit

(Lollipop)

WorkAbout 7528 Windows CE Internet

WorkAbout

7528

Windows CE

Internet

Pro 4

6.0

Explorer,

(WAP4 CE-2.4

Webkit

BSP and

above)

 

Windows Embedded Handheld 6.5 (WAP4 WEH- 3.0.1 BSP and above)

Vehicle Computers

Webkit BSP and above)   Windows Embedded Handheld 6.5 (WAP4 WEH- 3.0.1 BSP and above) Vehicle
Webkit BSP and above)   Windows Embedded Handheld 6.5 (WAP4 WEH- 3.0.1 BSP and above) Vehicle
Webkit BSP and above)   Windows Embedded Handheld 6.5 (WAP4 WEH- 3.0.1 BSP and above) Vehicle
Webkit BSP and above)   Windows Embedded Handheld 6.5 (WAP4 WEH- 3.0.1 BSP and above) Vehicle
Webkit BSP and above)   Windows Embedded Handheld 6.5 (WAP4 WEH- 3.0.1 BSP and above) Vehicle
Webkit BSP and above)   Windows Embedded Handheld 6.5 (WAP4 WEH- 3.0.1 BSP and above) Vehicle
Webkit BSP and above)   Windows Embedded Handheld 6.5 (WAP4 WEH- 3.0.1 BSP and above) Vehicle
Webkit BSP and above)   Windows Embedded Handheld 6.5 (WAP4 WEH- 3.0.1 BSP and above) Vehicle
Webkit BSP and above)   Windows Embedded Handheld 6.5 (WAP4 WEH- 3.0.1 BSP and above) Vehicle
Webkit BSP and above)   Windows Embedded Handheld 6.5 (WAP4 WEH- 3.0.1 BSP and above) Vehicle
 

DEVICE FAMILY

DEVICE

OPERATING SYSTEM(S)

SUPPORTED

WEB VIEWS

VH10 VH10 Windows CE 6.0 (Omnii CE- 12.2.44149 BSP and above) Internet

VH10

VH10

Windows CE 6.0 (Omnii CE- 12.2.44149 BSP and above)

Internet

Explorer,

Webkit

VC5090 VC5090 Windows CE 5.0 Internet

VC5090

VC5090

Windows CE 5.0

Internet

Explorer

VC6000 VC6000, Windows Internet

VC6000

VC6000,

Windows

Internet

VC6096

Embedded

Explorer

Handheld 6.5

VC70 VC70 Windows CE 7.0 Internet

VC70

VC70

Windows CE 7.0

Internet

Explorer,

Webkit

VC80X VC80X Android 7.0 Android

VC80X

VC80X

Android 7.0

Android

(Nougat)

Stock

Webkit

Tablets

 

DEVICE FAMILY

DEVICE

OPERATING

SUPPORTED

SYSTEM(S)

WEB VIEWS

ET1 ET1 Android 4.1 Android

ET1

ET1

Android 4.1

Android

(Enterprise

(JellyBean)*

Stock

Tablet),

Webkit

ET1 WAN

ET5X ET50, Android 5.0 Android

ET5X

ET50,

Android 5.0

Android

ET55

(Lollipop)

Stock

Android 6.0

Webkit

(Marshmallow)

Kiosks

 

DEVICE FAMILY

DEVICE

OPERATING

SUPPORTED WEB

SYSTEM(S)

VIEWS

CC5000-10 CC5000-10 Android 5.0 Android Stock

CC5000-10

CC5000-10

Android 5.0

Android Stock

(Lollipop)

Webkit

MK3000 MK3000, Windows CE Internet Explorer

MK3000

MK3000,

Windows CE

Internet Explorer

MK3090

5.0

MK3100 MK3100, Windows CE Internet

MK3100

MK3100,

Windows CE

Internet

MK3190

7.0

Explorer, Webkit

MK4000 MK4000, Windows CE Internet Explorer

MK4000

MK4000,

Windows CE

Internet Explorer

MK4090

5.0

Wearable Computers

 

DEVICE FAMILY

DEVICE

OPERATING

SUPPORTED WEB

SYSTEM(S)

VIEWS

WT4090 WT4070, Windows Internet

WT4090

WT4070,

Windows

Internet

WT4090

CE 5.0

Explorer

WT41N0 WT41N0 Windows Internet

WT41N0

WT41N0

Windows

Internet

CE 7.0

Explorer,

Webkit

WT6000 WT6000 Android 5.0 Android Stock

WT6000

WT6000

Android 5.0

Android Stock

(Lollipop)

Webkit

Scanners

 

SCANNER TYPE

MODEL

DEVICE

Ultra- DS3678 TC51, TC51-HC, TC56, TC70X - Android 6.0 (Marshmallow) MC33X, TC51, TC51-HC, TC56,

Ultra-

DS3678

TC51, TC51-HC, TC56, TC70X - Android 6.0 (Marshmallow) MC33X, TC51, TC51-HC, TC56,

Rugged

Scanner

TC70X, TC75X, VC80X - Android

7.0

(Nougat)

Corded RS4000 WT6000 - Android 5.0 (Lollipop)

Corded

RS4000

WT6000 - Android 5.0 (Lollipop)

Ring

Scanner

Cordless RS507 TC70 - Android 4.4 (KitKat) TC75, TC8000 - Android 5.0 (Lollipop) TC51, TC51-HC,

Cordless

RS507

TC70 - Android 4.4 (KitKat) TC75, TC8000 - Android 5.0 (Lollipop) TC51, TC51-HC, TC56, TC70X - Android 6.0 (Marshmallow) MC33X, TC51, TC51-HC, TC56,

TC70X, TC75X, VC80X - Android

Ring

Scanner

 

7.0

(Nougat)

Corded RS5000 WT6000 - Android 5.0 (Lollipop)

Corded

RS5000

WT6000 - Android 5.0 (Lollipop)

Ring

Scanner

Bluetooth RS6000 TC75, TC8000 - Android 5.0 (Lollipop)

Bluetooth

RS6000

TC75, TC8000 - Android 5.0 (Lollipop)

Ring

Scanner

TC51, TC56, TC70X - Android 6.0 (Marshmallow) MC33X, TC51, TC51-HC, TC56, TC70X, TC75X, VC80X - Android

 

7.0

(Nougat)

Vibrators

Android 6.0 (Marshmallow) MC33X, TC51, TC51-HC, TC56, TC70X, TC75X, VC80X - Android   7.0 (Nougat) Vibrators
Android 6.0 (Marshmallow) MC33X, TC51, TC51-HC, TC56, TC70X, TC75X, VC80X - Android   7.0 (Nougat) Vibrators
Android 6.0 (Marshmallow) MC33X, TC51, TC51-HC, TC56, TC70X, TC75X, VC80X - Android   7.0 (Nougat) Vibrators
Android 6.0 (Marshmallow) MC33X, TC51, TC51-HC, TC56, TC70X, TC75X, VC80X - Android   7.0 (Nougat) Vibrators
Android 6.0 (Marshmallow) MC33X, TC51, TC51-HC, TC56, TC70X, TC75X, VC80X - Android   7.0 (Nougat) Vibrators
Android 6.0 (Marshmallow) MC33X, TC51, TC51-HC, TC56, TC70X, TC75X, VC80X - Android   7.0 (Nougat) Vibrators
Android 6.0 (Marshmallow) MC33X, TC51, TC51-HC, TC56, TC70X, TC75X, VC80X - Android   7.0 (Nougat) Vibrators
Android 6.0 (Marshmallow) MC33X, TC51, TC51-HC, TC56, TC70X, TC75X, VC80X - Android   7.0 (Nougat) Vibrators
 

VIBRATOR TYPE

MODEL

DEVICE

External CBL-NGWT- WT6000 - Android 5.0 (Lollipop)

External

CBL-NGWT-

WT6000 - Android 5.0 (Lollipop)

Vibrator

HDVBAP-01

Cable

 

Memory Considerations

Enterprise Browser offers support for legacy device families such as the MC9000 and MK4000. Supported devices span a range of performance capabilities; therefore care should be taken when developing applications, especially for older devices. The following points might help with this:-

JavaScript libraries such as Sencha touch or JQuery Mobile can use a significant amount of memory at runtime. The more JavaScript libraries loaded into the DOM the greater the RAM footprint of the web page will be.older devices. The following points might help with this:- There are APIs available in the product

There are APIs available in the product to monitor the memory including memory logs and a Memory API. Use these tools to get a handle on the requirements of an application.DOM the greater the RAM footprint of the web page will be. Resources are available from

Resources are available from the Developer Community to help create great looking, streamlined apps. Developer Community to help create great looking, streamlined apps.

Online performance tests for JavaScript and CSS, particularly those involving DOM manipulation will often be written to target desktop computers and may not run on all supported devices.Community to help create great looking, streamlined apps. Windows Mobile 5.0 is not supported in this

Windows Mobile 5.0 is not supported in this release, devices should be updated to Windows Mobile 6.x where possible.desktop computers and may not run on all supported devices. Localizations The Enterprise Browser has been

Localizations

The Enterprise Browser has been approved to run on the following localized device operating systems:

Frenchto run on the following localized device operating systems: Italian German Spanish Portuguese Traditional Chinese

Italianon the following localized device operating systems: French German Spanish Portuguese Traditional Chinese Simplified

Germanfollowing localized device operating systems: French Italian Spanish Portuguese Traditional Chinese Simplified Chinese

Spanishlocalized device operating systems: French Italian German Portuguese Traditional Chinese Simplified Chinese Korean

Portuguesedevice operating systems: French Italian German Spanish Traditional Chinese Simplified Chinese Korean (Windows

Traditional Chineseoperating systems: French Italian German Spanish Portuguese Simplified Chinese Korean (Windows Embedded Handheld Only)

Simplified ChineseFrench Italian German Spanish Portuguese Traditional Chinese Korean (Windows Embedded Handheld Only) Japanese Approved

Korean (Windows Embedded Handheld Only)Spanish Portuguese Traditional Chinese Simplified Chinese Japanese Approved localized operating systems can be

JapaneseSimplified Chinese Korean (Windows Embedded Handheld Only) Approved localized operating systems can be obtained from

Approved localized operating systems can be obtained from Support Central.

Localization is not supported on below Zebra devices.

WorkAbout Pro 4 Windows Embedded Handheld 6.5. Localization is not supported on below Zebra devices. WorkAbout Pro 4 CE 6.0 VH10 CE

WorkAbout Pro 4 CE 6.0Zebra devices. WorkAbout Pro 4 Windows Embedded Handheld 6.5 VH10 CE 6.0 Omnii XT15 CE 6.0

VH10 CE 6.0Pro 4 Windows Embedded Handheld 6.5 WorkAbout Pro 4 CE 6.0 Omnii XT15 CE 6.0 Omnii

Omnii XT15 CE 6.0Embedded Handheld 6.5 WorkAbout Pro 4 CE 6.0 VH10 CE 6.0 Omnii XT15 Windows Embedded Handheld

Omnii XT15 Windows Embedded Handheld 6.56.5 WorkAbout Pro 4 CE 6.0 VH10 CE 6.0 Omnii XT15 CE 6.0 COMPONENTS OF ENTERPRISE

COMPONENTS OF ENTERPRISE BROWSER

Windows Desktop PC Components

Enterprise Browser components are installed in the following folders on the Windows Desktop machine:

COMPONENT

LOCATION

Runtimes

C:\EnterpriseBrowser\Runtimes\[platform

(Enterprise

type]\EnterpriseBrowser_[version#].apk

Browser Runtime

For Android)

Runtimes

C:\EnterpriseBrowser\Runtimes\[platform

(Enterprise

type]\EnterpriseBrowser_[version#]_[webview].cab

Browser Runtime

For WM/CE)

JavaScript Files

C:\EnterpriseBrowser\JavaScriptFiles\EnterpriseBrowser\

(New

[platform type]\*.js

EnterpriseBrowser

API)

JavaScript Files

C:\EnterpriseBrowser\JavaScriptFiles\BackwardCompatibility\ [platform type]\*.js

(Backwards

Compatibility)

 

Installer

C:\EnterpriseBrowser\Installer\EnterpriseBrowser.exe

Feature Demo

C:\EnterpriseBrowser\Feature-Demo\

Printing CAB file

C:\EnterpriseBrowser\Printing-Service\PrintingService.cab

Configuration

C:\EnterpriseBrowser\Configuration Editor\

Editor

Shortcuts Utility

C:\EnterpriseBrowser\Shortcut Utility\

Mac OS X PC Components

Enterprise Browser components are extracted to the application folder on the host Mac OS X machine:

COMPONENT

Runtimes (Enterprise Browser Runtime For Android)

Runtimes (Enterprise Browser Runtime For WM/CE)

JavaScript Files (New EnterpriseBrowser API)

JavaScript Files

(Backwards

Compatibility)

Feature Demo

Printing CAB file

EB Online

Help.webloc

Feature Demo

ReadMe.webloc

Back to Top

INSTALLATION

Windows Desktop

Enterprise Browser is installed by running the MSI project available from Support Central. The MSI project can be used to deploy variants of the Enterprise Browser executable to the target device.

Mac OS X

The Enterprise Browser is installed by running the DMG project available from Support Central. The DMG provides access to the Enterprise Browser device executables along with other resources.

Back to Top

USAGE NOTES

Module-specific notes

It is not recommended to use alert boxes to display scanned information or notify of gesture recognition or similar kind of stuff (example: under any callback) in a production environment.USAGE NOTES Module-specific notes The ScannerType property of the Barcode API should not be relied upon

The ScannerType property of the Barcode API should not be relied upon to accurately report the type of Scanner in use.(example: under any callback) in a production environment. Enterprise Browser applications using the Audio capture APIs

Enterprise Browser applications using the Audio capture APIs should specify a name prior to capturing rather than relying on the default name. The application also should be designed to take account of the time taken for the hardware to initialize.relied upon to accurately report the type of Scanner in use. Only one alert should be

Only one alert should be shown at any given time on WM/CE devices.account of the time taken for the hardware to initialize. Printing Issues: Printer discovery is unreliable

Printing Issues:alert should be shown at any given time on WM/CE devices. Printer discovery is unreliable on

Printer discovery is unreliable on Windows and Android devices. The most reliable way to connect to a printer is by calling 'searchPrinters' and providing the Bluetooth or IP address of the desired printer.shown at any given time on WM/CE devices. Printing Issues: Attempting to connect to a printer

Attempting to connect to a printer after disconnecting will return an error on Android/WM.the Bluetooth or IP address of the desired printer. The retrieveFileNames and retrieveFileNamesWithExtensions

The retrieveFileNames and retrieveFileNamesWithExtensions methods require passing an anonymous callback function. Named callback functions will not work.after disconnecting will return an error on Android/WM. Printing on devices loaded with the Stonestreet stack

Printing on devices loaded with the Stonestreet stack are not supported by Printer APIs. Please use Legacy APD APIs to print with the Stonestreet Stack.callback function. Named callback functions will not work. Debug buttons are not designed to be used

Debug buttons are not designed to be used in production code and may cause undesirable side effects.use Legacy APD APIs to print with the Stonestreet Stack. Capturing a signature in full screen

Capturing a signature in full screen mode is not compatible with the device auto rotation function.in production code and may cause undesirable side effects. Usage notes for Android Upgrade 'EMDK For

Usage notes for Android

Upgrade 'EMDK For Android' version to 6.0 or else slight delay will occur on every enable if the custom decode sound is set either via config tag <ScanDecodeWav> or via 'decodeSound' property of Barcode API.the device auto rotation function. Usage notes for Android WriteConfigSetting and ReadConfigSetting of Generic module

WriteConfigSetting and ReadConfigSetting of Generic module is not supported on Android.or via 'decodeSound' property of Barcode API. The Home Key cannot be intercepted or blocked on

The Home Key cannot be intercepted or blocked on Android; please refer to the device documentation for details of how to enable OS lockout.of Generic module is not supported on Android. UsPlanetReportCheckDigit and UsPostNetReportCheckDigit have

UsPlanetReportCheckDigit and UsPostNetReportCheckDigit have no effect on Android.documentation for details of how to enable OS lockout. Once disabled, EAN13 barcodes should not be

Once disabled, EAN13 barcodes should not be scanned with Android.and UsPostNetReportCheckDigit have no effect on Android. The Bluetooth radio does not turn off when

The Bluetooth radio does not turn off when BluetoothManager.off_bluetooth is called and will not turn on automatically on Android when Bluetooth APIs are exercised.disabled, EAN13 barcodes should not be scanned with Android. The Code128IsBtTable Barcode symbology is not supported

The Code128IsBtTable Barcode symbology is not supported on Android.automatically on Android when Bluetooth APIs are exercised. When using the Native TabBar on Android, ensure

When using the Native TabBar on Android, ensure the enablePageLoadingIndication property is set to 'true' to avoid potential issues on load.Barcode symbology is not supported on Android. The device volume buttons will become non-functional in all

The device volume buttons will become non-functional in all Android devices unless you specify <EnableFunctionKey_F1/> and <EnableFunctionKey_F2/> in your config.xml file.is set to 'true' to avoid potential issues on load. The rhoconfig parameter 'local_server_port' is not

The rhoconfig parameter 'local_server_port' is not supported.and <EnableFunctionKey_F2/> in your config.xml file. All RhoElements 1-2.2 APIs that use files treat the

All RhoElements 1-2.2 APIs that use files treat the /mnt/sdcard/ directory as root. Therefore, an SD card must be present.parameter 'local_server_port' is not supported. In MC18 KitKat device, AudioCapture, Imager and KeyCapture

In MC18 KitKat device, AudioCapture, Imager and KeyCapture API are not supported because of device limitations.directory as root. Therefore, an SD card must be present. In TC70 KitKat device, APD Printing

In TC70 KitKat device, APD Printing requires ProgressBar to be enabled.API are not supported because of device limitations. All APIs related to RSM are not supported

All APIs related to RSM are not supported on Android.device, APD Printing requires ProgressBar to be enabled. All APIs related to KeyLight module are not

All APIs related to KeyLight module are not supported on Android.All APIs related to RSM are not supported on Android. To turn off the beeper notification

To turn off the beeper notification when using 2.2 Notification API on Android, set the 'setBeeperDuration' parameter before calling the 'stateOff' parameter.related to KeyLight module are not supported on Android. Within Enterprise Browser, key pressing will work

Within Enterprise Browser, key pressing will work properly if and only if the keycode mapping file is not empty and the content is properly written/captured as per the keycode mapping guidelines.parameter before calling the 'stateOff' parameter. The callback parameter 'TagIDHexa' of enableRead

The callback parameter 'TagIDHexa' of enableRead method of EzNFC API will now return the hexacode of NFC Tag ID in left to right order.written/captured as per the keycode mapping guidelines. Enterprise Browser CardReader API is not available on MC32

Enterprise Browser CardReader API is not available on MC32 Android, MC33X Android Nougat, TC70X Android Nougat and TC75X Android Nougat devices.'TagIDHexa' of enableRead method of EzNFC API will now return the hexacode of NFC Tag ID

Enterprise Browser Scanner API is not available on CC5000-10 Android Lollipop device. Scanner API is not available on CC5000-10 Android Lollipop device.

Config tags such as <DecodeVolume>, <DecodeFrequency> and <DecodeDuration> are not supported on CC5000-10 Android Lollipop device.API is not available on CC5000-10 Android Lollipop device. Barcode properties like 'decodeVolume',

Barcode properties like 'decodeVolume', 'decodeFrequency' and 'decodeDuration' which is being accessed through EB namespace are not supported on CC5000-10 Android Lollipop device.are not supported on CC5000-10 Android Lollipop device. Configuration tag <ScanDecodeWav> and Barcode

Configuration tag <ScanDecodeWav> and Barcode property 'decodeSound' which is being accessed through EB namespace are not supported when wav sound format is used on CC5000-10 Android Lollipop device.are not supported on CC5000-10 Android Lollipop device. Turn off device level rotation to avoid unexpected

Turn off device level rotation to avoid unexpected behavior on CC5000-10 Android Lollipop device.sound format is used on CC5000-10 Android Lollipop device. Usage notes for Windows Mobile / Windows

Usage notes for Windows Mobile / Windows Embedded Handheld and Windows CE

Scanner and Imager viewfinder parameters are not infinitely adjustable. The requested resolution must be supported by the hardware, or the output might be scaled or snapped to the closest supported size. The viewfinder should be configured prior to being displayed. Additionally, the Imager module width and height parameters on devices running Windows Embedded Handheld should not be set to 500 or greater when using the color camera.Windows Mobile / Windows Embedded Handheld and Windows CE Configuring the data buffer size or data

Configuring the data buffer size or data format on Windows CE or Windows Embedded handheld should be done prior to enabling the scanner.not be set to 500 or greater when using the color camera. Kiosk devices sometimes errorneously

Kiosk devices sometimes errorneously report that they have a camera installed when queried through the System API.handheld should be done prior to enabling the scanner. When capturing a video on the MC45

When capturing a video on the MC45 device the preview window fills the whole screen. To stop the capture prematurely use the KeyCapture API to stop() the capture.have a camera installed when queried through the System API. Filenames used in the Video Capture

Filenames used in the Video Capture API should be restricted to alphabetical characters.prematurely use the KeyCapture API to stop() the capture. When using the Signature API on Windows,

When using the Signature API on Windows, the filename of the capture will be returned without the associated extension.Capture API should be restricted to alphabetical characters. When capturing audio or video, please be aware

When capturing audio or video, please be aware of file locks when overwriting existing files, as this can cause the capture to fail.capture will be returned without the associated extension. Audio Capture should not be invoked on devices

Audio Capture should not be invoked on devices without a microphone, such as the VC5090.existing files, as this can cause the capture to fail. Do not set the Windows start

Do not set the Windows start menu to 'auto hide' on CE as this has compatibility issues with Enterprise Browser full screen mode.invoked on devices without a microphone, such as the VC5090. Streaming audio or video is not

Streaming audio or video is not available in the Media Player API for WM or CE.issues with Enterprise Browser full screen mode. Notes around using the RemoteScanner Module: It is

Notes around using the RemoteScanner Module:video is not available in the Media Player API for WM or CE. It is recommended

It is recommended to store the PIN and not require users to manually enter it when associating with the scanner.for WM or CE. Notes around using the RemoteScanner Module: The rsmDecodeFeedback property cannot be used

The rsmDecodeFeedback property cannot be used to disable the sound and illumination.to manually enter it when associating with the scanner. Functionality of the Network API should not

Functionality of the Network API should not be exercised through ActiveSync or Windows Device Center, depending on your desktop OS.cannot be used to disable the sound and illumination. The Bluetooth server connection has stability issues

The Bluetooth server connection has stability issues under some deployment scenarios.or Windows Device Center, depending on your desktop OS. The takeFullScreen method of the Signature API

The takeFullScreen method of the Signature API should not be used on the MK3100 device, non full screen signature capture is still available.has stability issues under some deployment scenarios. The takePicture method of Camera API should not be

The takePicture method of Camera API should not be used on MC9190 device running WM. Instead, use showPreview method of Camera API.non full screen signature capture is still available. JavaScript onkeydown,onkeypress,onkeyup events are not

JavaScript onkeydown,onkeypress,onkeyup events are not supported on devices running on Windows Mobile devices with IE rendering engine. Instead, use EnterpriseBrowser Keycapture APIs to capture the key presses.running WM. Instead, use showPreview method of Camera API. When launching basic autheticated URLs on an

When launching basic autheticated URLs on an Enterprise Browser startpage, perform the followingKeycapture APIs to capture the key presses. steps:- License the Device. Note: If the requirement is

steps:-

License the Device. Note: If the requirement is to have a basic authenticated URL as a startpage, it's the If the requirement is to have a basic authenticated URL as a startpage, it's the device must first be licensed and the ShowLicenseConfirmation parameter must contain a value to 0.

Set <ShowLicenseConfirmation value="0"> Note:Setting ShowLicenseConfirmation value="0" will bypass the License screen if the device is already licensed Setting ShowLicenseConfirmation value="0" will bypass the License screen if the device is already licensed

Refer to 'ShowLicenseConfirmation' section in Config Reference Guide for more information.bypass the License screen if the device is already licensed Avoid using F10 key in Enterprise

Avoid using F10 key in Enterprise Browser application when webkit engine is used.section in Config Reference Guide for more information. Usage notes for the Webkit Rendering Engine

Usage notes for the Webkit Rendering Engine

SMS, Email and wtai URIs e.g. <a href="tel:18006535350"> are not supported on Windows Mobile / CE.It is strongly recommended to avoid using framesets and make use of <div> and <span>

It is strongly recommended to avoid using framesets and make use of <div> and <span> tags instead. A single page is faster to process and it is not possible to guarantee which frames' tags will be parsed first; also any JavaScript callbacks will always be sent to the parent frameset page.are not supported on Windows Mobile / CE. Form input types http://www.w3.org/TR/html5/forms.html

Form input types http://www.w3.org/TR/html5/forms.html are not yet supported. http://www.w3.org/TR/html5/forms.html are not yet supported.

HTML5 Video / Audio is not supported.are not yet supported. CSS Gradients, Complicated CSS shadows or displaying shadows

CSS Gradients, Complicated CSS shadows or displaying shadows on rotated objects have been known to cause visual and performance issues on the CE/WEHH WebKit browser.are not yet supported. HTML5 Video / Audio is not supported. The HTML5 web worker functionality

The HTML5 web worker functionality should not be used on Windows devices.visual and performance issues on the CE/WEHH WebKit browser. Multiple items cannot be selected simultaneously from

Multiple items cannot be selected simultaneously from a combo box on Android devices.worker functionality should not be used on Windows devices. Input attribute 'autofocus' should not be relied

Input attribute 'autofocus' should not be relied upon to set field focus; use JavaScript alternatives.selected simultaneously from a combo box on Android devices. On WM/CE Ekioh Webkit, the "Basic" and

On WM/CE Ekioh Webkit, the "Basic" and "Digest" forms of the WWW-Authenticate header are supported as described here: https://www.ietf.org/rfc/rfc2617.txt . https://www.ietf.org/rfc/rfc2617.txt.

Configuration Options

On reinstalling Enterprise Browser on Android, the previous config.xml file will not be overwritten.. Configuration Options The <LogUser /> log severity has no effect if

The <LogUser /> log severity has no effect if <LogInfo /> is disabled, disabling <LogInfo /> will have no effect on info logs.the previous config.xml file will not be overwritten. To navigate to secure web pages, it is

To navigate to secure web pages, it is necessary to specify both the HTTP and HTTPS proxies.<LogInfo /> will have no effect on info logs. Upgrading Enterprise Browser Settings are not preserved

Upgrading Enterprise Browser

Settings are not preserved automatically when updating Enterprise Browser. To preserve previous settings, please perform the following steps:

For Windows Mobile/CE Deviceprevious settings, please perform the following steps: Save a copy of the Enterprise Browser Config.xml file(s)

Save a copy of the Enterprise Browser Config.xml file(s) with existing settings from the following locations:perform the following steps: For Windows Mobile/CE Device \Program Files\EnterpriseBrowser\Config\Config.xml Uninstall

\Program Files\EnterpriseBrowser\Config\Config.xmlfile(s) with existing settings from the following locations: Uninstall Enterprise Browser from the device. Install the

Uninstall Enterprise Browser from the device.\Program Files\EnterpriseBrowser\Config\Config.xml Install the new version of Enterprise Browser. Overwrite the

Install the new version of Enterprise Browser.Uninstall Enterprise Browser from the device. Overwrite the default config.xml file created at

Overwrite the default config.xml file created at installation with the modified Config.xml.the device. Install the new version of Enterprise Browser. \Program Files\EnterpriseBrowser\Config\Config.xml For

file created at installation with the modified Config.xml. \Program Files\EnterpriseBrowser\Config\Config.xml For

\Program Files\EnterpriseBrowser\Config\Config.xml

For Android Device\Program Files\EnterpriseBrowser\Config\Config.xml Save a copy of the Enterprise Browser Config.xml file(s)

Save a copy of the Enterprise Browser Config.xml file(s) with existing settings from "/<mass storage location>/Android/data/com.symbol.enterprisebrowser/Config.xml" location to the below locations:Files\EnterpriseBrowser\Config\Config.xml For Android Device /<mass storage

/<mass storage location>/EnterpriseBrowser/Config.xml or /<internal_mem_root_dir>/EnterpriseBrowser/location to the below locations: Uninstall Enterprise Browser from the device. Install the

Uninstall Enterprise Browser from the device.or /<internal_mem_root_dir>/EnterpriseBrowser/ Install the new version of Enterprise Browser. Data

Install the new version of Enterprise Browser.Uninstall Enterprise Browser from the device. Data Persistence Users have a number of options when

Data Persistence

Users have a number of options when choosing to persist their data locally including Web Storage and Web SQL databases.

On Android, Enterprise Browser depends on the OS implementation of the storage solution and will persist across a re-install of Enterprise Browser. More detail on storage solutions can be found here:data locally including Web Storage and Web SQL databases. http://www.html5rocks.com/en/features/storage On Windows

On Windows Mobile the location of the databases is defined in your Config.xml and will also persist across a re-install of Enterprise Browser. If wiping your device, it is recommended to take a copy of your .db files on Windows Mobile / CE; on Android, whenever the database persists an OS update will depend on the underlying OS implementation when upgrading.Browser. More detail on storage solutions can be found here: http://www.html5rocks.com/en/features/storage Back to Top

Back to Top

ISSUES FIXED IN THIS RELEASE

[SPR-32893]Config Editor Tool now supports ADB version v1.0.36.ISSUES FIXED IN THIS RELEASE [SPR-33133]Within Enterprise Browser, key pressing will work properly even if the

[SPR-33133]Within Enterprise Browser, key pressing will work properly even if the keycode mapping xml file is empty.Editor Tool now supports ADB version v1.0.36. [SPR-33137]Added backward compatibility support for Android

[SPR-33137]Added backward compatibility support for Android webview.work properly even if the keycode mapping xml file is empty. [SPR-33345]Camera sharpness now gets retained

[SPR-33345]Camera sharpness now gets retained even if power button is pressed.backward compatibility support for Android webview. Back to Top KNOWN ISSUES Known Issues using Android Calling

Back to Top

KNOWN ISSUES

Known Issues using Android

Calling getProperty with 'hasCalendar' always returns FALSE on the MC32N0 Android.pressed. Back to Top KNOWN ISSUES Known Issues using Android Displaying notification messages of type dialog,

Displaying notification messages of type dialog, notification etc are not taking effect on the MC32N0 Android.always returns FALSE on the MC32N0 Android. The default duration will not apply to the TC70

The default duration will not apply to the TC70 when calling 'videoCapture.start()'. To avoid this issue please set the videoCapture.duration.etc are not taking effect on the MC32N0 Android. After installation of Enterprise Browser and subsequently

After installation of Enterprise Browser and subsequently adding an SD card, the original configuration will be ignored and a new default config.xml will be generated and applied from the SD card.To avoid this issue please set the videoCapture.duration. If the user taps the screen outside of

If the user taps the screen outside of the authentication box,it will cancel the login page and display a server page error. This has been observed on MC40 and ET1 devices.config.xml will be generated and applied from the SD card. If the use enters the incorrect

If the use enters the incorrect credentials, the application will clear the fields rather than navigate to the "login failed" page. This is known to affect the ET1 and the MC40 devices.page error. This has been observed on MC40 and ET1 devices. Streaming audio or video files

Streaming audio or video files via https will not function when using MediaPlayer on the MC18 KK device.page. This is known to affect the ET1 and the MC40 devices. Rendering behavior differs based

Rendering behavior differs based on the default browser engine available in the device.not function when using MediaPlayer on the MC18 KK device. Volume UP, Volume Down and Hardware

Volume UP, Volume Down and Hardware Keys will not work when FunctionKeysCapturable tag is set to "0" in Config.xml on an Android device. To make keys functional, set this tag to "1" in Config.xml.based on the default browser engine available in the device. Enterprise Browser Barcode properties must be

Enterprise Browser Barcode properties must be set either before or along with the enable method on CC5000-10 Android Lollipop device.keys functional, set this tag to "1" in Config.xml. Known issues using Webkit on Windows Zebra

Known issues using Webkit on Windows

Zebra Printer APIs is not supported on Windows CE devices.Lollipop device. Known issues using Webkit on Windows Calling takePicture method of Camera API does not

Calling takePicture method of Camera API does not take effect on MC9190 device running WM.Zebra Printer APIs is not supported on Windows CE devices. Calling takeFullScreen method with SignatureCapture set

Calling takeFullScreen method with SignatureCapture set to full screen fails to capture on an MK3100 device running CE7.Camera API does not take effect on MC9190 device running WM. The scanTimeout parameter does not

The scanTimeout parameter does not take effect on MC18 device running CE7.screen fails to capture on an MK3100 device running CE7. Installed Persistent Enterprise Browser is not

Installed Persistent Enterprise Browser is not shown in Remove Programs on CE device after cold boot.parameter does not take effect on MC18 device running CE7. Config tag <JavascriptEnabled> cannot be disabled

Config tag <JavascriptEnabled> cannot be disabled when using Webkit on Windows.not shown in Remove Programs on CE device after cold boot. Passkey is required to be

Passkey is required to be set in order to use the Push API. Affects MC9190 device running CE6.cannot be disabled when using Webkit on Windows. ResizeOnSIP has no effect on MC92N0 devices running

ResizeOnSIP has no effect on MC92N0 devices running CE/WEHHto use the Push API. Affects MC9190 device running CE6. RSM DecodeFeedback cannot be disabled. This

RSM DecodeFeedback cannot be disabled. This occurs on the MC9190 device running CE6.ResizeOnSIP has no effect on MC92N0 devices running CE/WEHH Setting autoRotate to Enabled or Disabled does

Setting autoRotate to Enabled or Disabled does not have any effect on MC67NA WM devices.be disabled. This occurs on the MC9190 device running CE6. SIP disappears when changing screen orientation

SIP disappears when changing screen orientation on Windows Mobile from portrait to landscape. This occurrs on the MC9190 device running CE6.or Disabled does not have any effect on MC67NA WM devices. Streaming video via HTTP will

Streaming video via HTTP will not function when using MediaPlayer on the MC32N0 device running CE7.to landscape. This occurrs on the MC9190 device running CE6. The barcode scanner fails to fire

The barcode scanner fails to fire on MK3100 CE7 device when the <LowBatteryScan> tag, in Config.xml, is set to 0.when using MediaPlayer on the MC32N0 device running CE7. The notification event returns LED and pager

The notification event returns LED and pager objects that do not exist on MK3100 devices.<LowBatteryScan> tag, in Config.xml, is set to 0. Signature barcode is not supported on MC92N0 device

Signature barcode is not supported on MC92N0 device running CE7.LED and pager objects that do not exist on MK3100 devices. Due to platform limitation, tilt

Due to platform limitation, tilt and shake gestures may not work as intended in certain WM/CE devices.barcode is not supported on MC92N0 device running CE7. Rotating the screen from landscape to portrait

Rotating the screen from landscape to portrait while simultaneously displaying the SIP, results in a reposition of the SIP.device running CE7. Due to platform limitation, tilt and shake gestures may not work as intended

After Enterprise Browser is minimized on MC92N0 device running CE7, the device is rotated to landscape position during a restore operation the application may fail to maximize. This can be avoided by setting <AutoRotate> tag value to 0 in Config.xml.Setting the screen orientation using the API 'EB.ScreenOrientation' does not take effect on MC65 device

Setting the screen orientation using the API 'EB.ScreenOrientation' does not take effect on MC65 device running WM.setting <AutoRotate> tag value to 0 in Config.xml. Hold Gestures are not detected on an MC18

Hold Gestures are not detected on an MC18 device running CE7.does not take effect on MC65 device running WM. Known Issues using Internet Explorer on Windows

Known Issues using Internet Explorer on Windows

Gesture Diagnostics overlay disappears when a gesture is performed. This issue occurs when using the IE webview on Windows Mobile only. Tapping the screen after a gesture action will resume the display.running CE7. Known Issues using Internet Explorer on Windows Including external JS/CSS files hosted on Apache

Including external JS/CSS files hosted on Apache server do not take effect on WM device.the screen after a gesture action will resume the display. The product registration screen fails to

The product registration screen fails to show the licensee on MC67 device running WM6.5.hosted on Apache server do not take effect on WM device. The SignatureCapture area may lose

The SignatureCapture area may lose focus, and will not be visible, after scrolling on MC32N0 devices.fails to show the licensee on MC67 device running WM6.5. The Alarm method will not fire

The Alarm method will not fire on MK4000 device running CE5 when using the IE webview. As a workaround, use setInterval or setTimeout.and will not be visible, after scrolling on MC32N0 devices. The card reader does not function

The card reader does not function on the MC959B device running WM6.1 when using the IE webview.IE webview. As a workaround, use setInterval or setTimeout. When navigating to an Authentication screen with

When navigating to an Authentication screen with IE as the webview, on either WM or CE, the application will navigate to the badlink page after the timeout set <NavTimeout> in Config.xml. Note it is not possible to set the time out higher than 45 seconds on IE.the MC959B device running WM6.1 when using the IE webview. CE5 and CE6 truncate the request

CE5 and CE6 truncate the request variables when a navigation to badlink occurs, so the page will be navigated to, but the reason for the failure will not be displayed.possible to set the time out higher than 45 seconds on IE. Known Issues common to

Known Issues common to Internet Explorer and Webkit

Push does not function when setting the port to 8080 on MC32N0 device running CE7.Known Issues common to Internet Explorer and Webkit Back to Top SUPPORTED CIPHERS The following SSL

Back to Top

SUPPORTED CIPHERS

The following SSL Ciphers are supported in Windows WebKit

TLS_ECDHE_RSA_WITH_RC4_128_SHA (0xc011)

TLS_ECDHE_ECDSA_WITH_RC4_128_SHA (0xc007)

TLS_ECDH_RSA_WITH_RC4_128_SHA (0xc00c)

TLS_ECDH_ECDSA_WITH_RC4_128_SHA (0xc002)

TLS_RSA_WITH_RC4_128_SHA (0x0005)

TLS_RSA_WITH_RC4_128_MD5 (0x0004)

TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030)

TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (0xc02c)

TLS_ECDHE_RSA _WITH_AES_256_CBC_SHA384 (0xc028)(0xc030) TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (0xc02c) TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 (0xc024)

TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 (0xc024)

TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014)

TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA (0xc00a)

TLS_DHE_DSS_WITH_AES_256_GCM_SHA384 (0x00a3)

TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (0x009f)

TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 (0x006b)

TLS_DHE_DSS_WITH_AES_256_CBC_SHA256 (0x006a)

TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x0039)

TLS_DHE_DSS_WITH_AES_256_CBC_SHA (0x0038)

TLS_ECDH_RSA_WITH_AES_256_GCM_SHA384 (0xc032)

TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384 (0xc02e)

TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384 (0xc02a)

TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384 (0xc026)

TLS_ECDH_RSA_WITH_AES_256_CBC_SHA (0xc00f) TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA (0xc005) TLS_RSA_WITH_AES_256_GCM_SHA384

TLS_ECDH_RSA_WITH_AES_256_CBC_SHA (0xc00f)

TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA (0xc005)

TLS_RSA_WITH_AES_256_GCM_SHA384 (0x009d)

TLS_RSA_WITH_AES_256_CBC_SHA256 (0x003d)

TLS_RSA_WITH_AES_256_CBC_SHA (0x0035)

TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA (0xc013)

TLS_ECDHE_E CDSA_WITH_3DES_EDE_CBC_SHA (0xc008)

TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA (0x0016)

TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA (0x0013)

TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA (0xc00d)

TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA (0xc003)

TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x000a)

TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f)

TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (0xc02b)

TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (0xc027)

TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 (0xc023)

TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013)

TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA (0xc009)

TLS_DHE_DSS_WITH_AES_128_GCM_SHA256 (0x00a2)

TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (0x009e)

TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 (0x0067)

TLS_DHE_DSS_WITH_AES_128_CBC_SHA256 (0x0040)

TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x0033)

TLS_DHE_DSS_WITH_AES_128_CBC_SHA (0x0032)

TLS_ECDH_RSA_WITH_AES_128_GCM_SHA256 (0xc031)

TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256 (0xc02d)

TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256 (0xc029)

TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256 (0xc025)

TLS_ECDH_RSA_WITH_AES_128_CBC_SHA (0xc00e)

TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA (0xc004)

TLS_RSA_WITH_AES_128_GCM_SHA256 (0x009c)

TLS_RSA_WITH_AES_128_CBC_SHA256 (0x003c)

TLS_RSA_WITH_AES_128_CBC_SHA (0x002f)

TLS_EMPTY_RENEGOTIATION_INFO_SCSV (0x00ff)

Back to Top

PART NUMBERS

The following table lists the part numbers for Enterprise Browser

   

FIRST

 

PART

NUMBER

DESCRIPTION

RELEASE

DATE

COMMENTS

EB_1_8

Enterprise Browser for Android & Windows operating systems

5 th January

Version

2018

1.8.0.0

Back to Top

Last revised: 5 th January 2018