You should not have to do anything special when the device wakes up, Enterprise Browser should re-enable the scanner for you and ensure it is correctly configured. I know Android M devices have an additional scanner sleep mode however since your device is Android 'L' that would not be a problem here.
I recommend you ensure you are only using either the scanner API or the Barcode API, you should not mix the two and doing so could confuse the underlying scanner hardware possibly leading to the delay you describe.
Incidentally, "Then we used the rhoapi-modules.js and elements.js API with Metatags:"... you would not need rhoapi-modules.js to use the scanner APIs, only elements.js.
There is a powerOn event which will be called when the device wakes: PowerOn Module - Zebra Technologies TechDocs but as I say, this is not something your application should have to worry about when controlling the scanner.
Do you see any suspicious logcat messages when you come out of suspend?
In Enterprise Browser 1.7, the EB.Barcode API takes only ~1 sec to enable the Barcode and it also depends on the number of properties calling inside enable() method.
We have fixed a similar issue in Enterprise Browser 1.7 and our recommendation will be to use EB.Barcode API that will give more configurable methods.
Kindly Download the latest EB binary from below link and try the same.
Please share the EB, EMDK and BSP version details if the issue is reproducible again.
Thanks & Regards
Enterprise Browser Software Engineer
I am using Enterprisebrowser 1.6 on Android 4.4.3 (TC8000).
I have Checked my Config.xml. There are no Default-META-Tags active.
I have ensured that I am only using the following Scripts
I have created a mini-App which I debugged with Chrome Inspector:
But if I awake from Suspend there is:
Is there something I have missed?
Thanks in advance!
Can you please try with Enterprise Browser 1.7? Unless you are disabling the scanner yourself during suspend that sounds like a bug and if Prabhakar is saying they fixed a bug with 1.7 then perhaps it is the same issue.
You will not need to change your application and the license key is identical between 1.6 and 1.7 so hopefully it should be a simple swap out of the device APK. The config.xml will also be compatible so make sure you take a back-up of your configuration before upgrading and then just copy it back to the device after the update.
The Update to Enterprise Browser 1.7 worked!
Now it saves the autoEnter (and PICKLIST_HARDWARE_RETICLE) property.
The Scanner wakes up after ~1 Second like Prabhakar explained.
Thanks for your support!