Our company has the same problem. On the MC3200 device does not start with a barcode reader. This problem occurs only in Delphi applications. To test you can give a simple application. After a correct setting datawedge and then run the application can not run a barcode reader. The reader does not react to hardware buttons. The same program and settings on the TC70 is fully functional! Thank you for your response.

I made my own Delphi XE7 application and I can confirm the HW trigger doesn’t work in all JB devices we have. However I can see that implementing SW trigger you can enable scanner and capture data which means that there is some issue with input service. According the logs I captured the Trigger keycode is not passed to scanning service (outside of Delphi XE7 app) at all hence there is no response from device on key press. I would advise to reach Delphi XE7 owner for more information how are the key presses processed by such application in compare with native android application. I am not familiar with this framework but there might be an option how to dispatch key presses to OS for lower level applications.

As a workaround it should be possible to capture the trigger within the application and then toggle on/off scanner following keydown/keyup events.

Thank you for the quick response! I am glad, that you also found this bug. On the web portal.motorolasolutions.com I found a new version OS for this device. Part of the new update, is application Datawedge version 2.2.7. Currently is in the device factory OS version with Datawedge 1.7.x. Once I have available for download a new version, updating OS and run test the scanner using the hardware buttons. Maybe is this a bug, that is already in the new version removed. On TC70 device working all correctly. Tomorrow will perform tests using a barcode reader Intent and if this method to work, it would be great temporary solution. Thank you solve this problem.

as you correctly mention TC70 and our TC55 KK work. The issue seems to be related to JB implementation. It might be also something in ScanningService which picks up the key events. However the true is also that all android apps using SDK written in Java doesn't have this issue so it might be the Delphi XE7 framework as mentioned earlier. We still investigate whether there is something what can be done on OS side.I'll update this post once we have more information.