How to Access the Properties for Zebra Power Precision+ Batteries

Zebra’s range of Android Mobile devices come equipped with Power Precision or Power Precision+ batteries.  You can learn more about Power Precision / Power Precision+ from the product page but one advantage of these batteries for the app developer is access to a wealth of additional battery information not available on consumer Android handsets:

[TC-20][DataWedge 6.7][Android] How to scan variable number of bar codes in multi barcode mode?

I'm working on simple data collecting and matching program.
There will be 5 barcodes to scan in 2 groups (group of 3 and group of 2).
Scanning them one by one would be to slow, so I need to scan them in multi-barcode mode.
Problem is that I have to declare how many barcodes I want do scan in profile, but I have 2 barcodes in one location and 3 barcodes in another location, so I would need kind of flexible profile that would just accept min 2 and max 3 codes.

Not able to parse bug report in Battery Historian


I'm able to generate a bug report from TC75 and analyze it using Battery Historian.
But when I try to do the same with TC57 and TC77 it throws me an error saying : "Exception found in battery dump."

It says that it is unable to find the zone info file in the generated bug report.
I'm following the same process with all 3 devices.

I've attached an image with the error for reference.

Thanks in advance,

ZSDK_DemosAndroid Program: ZebraPrinterLanguageUnknownException

Hello. I'm testing the connection to a ZTC ZT230-203dpi ZPL printer. I tried using the demo program ZSDK_DemosAndroid provided in the link-os sdk package. However, a ZebraPrinterLanguageUnknownException is thrown when this line of code is being run:
printer = ZebraPrinterFactory.getInstance(printerConnection);

Here's the URL of the printer:

Any ideas? Thanks in advance!

Restrictions on non-SDK interfaces with Android Pie

Starting with Android Pie (API level 28), Android will start restricting which APIs your application can call if they are not part of the public API.  These restrictions apply whenever an app references a non-SDK interface or attempts to obtain its handle using reflection or JNI but do not affect calls to the EMDK or other third-party APIs.