FYI
I am noticing that the call to obtain CradleInfo takes about 3 seconds to finish, even when the MC18 is not docked in the cradle. This seems excessively long when compared to the same operation being run from the Windows version of the MC18.
PersonalShopper device = (PersonalShopper) _manager.getInstance(EMDKManager.FEATURE_TYPE.PERSONALSHOPPER);
Cradle cradle = device.cradle;
try {
cradle.enable();
CradleInfo cradleInfo = cradle.getCradleInfo();
cradle.disable();
result = cradleInfo.getSerialNumber();
}
catch (CradleException e) {
throw new Exception(e.getMessage());
}
finally {
_manager.release(EMDKManager.FEATURE_TYPE.PERSONALSHOPPER);
}
return result;
06-11 20:19:42.580 27728-27728/com.opticalphusion D/com.symbol.emdk.personalshopper.PersonalShopper﹕ Initialized
06-11 20:19:45.049 27728-27728/com.opticalphusion D/com.symbol.emdk.personalshopper.PersonalShopperHelper﹕ release
If this command is called by a user interaction, like a button press, then it will seem as though the application is hanging.
Message was edited by: Jon-Luke West
Identified that this is also the case when the MC18 is not docked in a cradle.
1 Replies
Hi Jon-Luke,
Thank you for providing all these details.
Your observation is correct and it is due to the OS overhead in Android compared to CE.
Our understanding is that this operation is not a normal shopper use-case, but rather an operation performed by a technician or back end store associate; let us know if you have a different perspective or other use cases affected by this delay.
Ana