We are developing with a demo version of Enterprise Browser and as soon as we load the browser the yellow hardware button stops triggering the scanner. Open Chrome, Notes, etc it works fine. Open EB and nothing. In reading some of the docs it seems like the default setting may be for the EB API to take over controlling the scanner from the key-mapping/dataWedge process. Is this correct? We have changed some settings in config.xml that seem like they might control this but it doesn't help. We also found instructions for creating an EB profile in dataWedge but that is of no help either. We have this issue on both of our development devices.

Looking for clear input on whether EB is taking over for the hardware buttons (expecting soft buttons?) and what steps to reverse the behavior.