No Matches Found!
Try with a different search term
Hi,
we have some Zebra Helios devices Non-GMS.
I have recently tried to upgrade some from A10 to latest Android 14 (14-32-12.00-UN-U00-STD-HEL-04), and figure out that Velocity (2.1.45) crashes just after start.
I'm struggling to get support from Zebra and Ivanti, wondering if anyone here has ever experienced the same.
The same device works fine with Android 13 (13-29-10.00-TN-U00-STD-HEL-04)
Non GMS Zebra Helios devices? Are you based in China? That is technically the only authorized location for Non-GMS Helios devices as a far as I'm aware.
A Non-GMS Helios device would be relatively rare in terms of overall distribution. You very well could be in uncharted territory here. My assumption is most software development teams are not testing against Non-GMS OS variants, and if they were at somepoint likely stopped around A8. An A14 + Non GMS OS variant has a very low likelihood of being tested by any software development teams because that would represent such a small number of overall devices. You may very well be the only person with this problem.
I would recommend converting one device temporarily to a GMS version of A14 to see if Velocity 2.1.45 works on that OS. That will at least narrow things down as being something specific to the Non-GMS build. My guess is there is some sort of dependency that the Velocity app has, possibly on a higher version of System WebView that the Non-GMS version just doesnt have, nor would it have access to update through Google Play.
Hi Matt,
thanks for your reply.
You're almost right, I'm based in Italy but Non-GMS devices are in China (I'm managing Zebra devices for my company globally).
GMS A14 + Velocity 2.1.45 works fine, also Non-GMS A13 + Velocity 2.1.45.
I didn't tested all of the different A14 LifeGuard Updates, just the last one, but there's definitely some sort of dependency that's generating the bug.