SOTI Pulse Logo

System information in Native mode

W
Wesley
ReverseIT

This is something I can't wrap my head around.
When using native lockdown system information works just fine on some devices but won't work on others.

We have about 100 devices running with CK65 that work just fine in native.

With these settings:

While a PS20 does not show any system information:

With exactly the same settings, I even tried to use the same template.
But it didn't help.


Why do some devices work fine and others don't?

I generally just use activity supression but sometimes you just need to hide some buttons (like home and recents) and these features area a lot harder to setup otherwise.

lockdown native system-information
4 years ago
Android
ANSWERS
R
Rafael
4 years ago

Do all devices you tried on have the same Android (in general)? MAybe write down here which device has which Android and which is working or not.

How about plugins, are they installed and working fine?

W
Wesley
4 years ago

Okay I might have found something.

I made a new profile from scratch with the correct settings without changing anything and send it to different devices.
This all worked fine, no issues.
So I send it to the PS20 aswell...no issues.
Then I started putting it to activity supression, send it, put it back to native....now no system information and it doesn't hide home button. either (while it is selected and worked in the other profile).

Basicly what i'm thinking right now is you have to make the profile perfect emediatly, don't make any changes as this is what seems to be breaking the settings.

MD
Matt Dermody Diamond Contributor
4 years ago

What OS versions are you running on each device? Native mode is leveraging the Android Enterprise Kiosk feature that is built into the OS. The AE Kiosk has been enhanced over time in subsequent versions of Android and therefore you will find there is more configurability and functionality when the devices are on Android 9, 10 or higher. If you are running the PS20 on Oreo still that is likely the cause of the inconsistency you are seeing with the kiosk mode. This is actually a universal AE paradigm that supersedes anything SOTI related as you would see similar behavior on any EMM that has leveraged the native Kiosk.

W
Wesley
4 years ago

Hello,

The PS20's are Android 10, most devices are, second most is Android 9 and rest is pretty much Android 8.1.

Funny thing is, last Friday I made a profile from scratch and it worked perfect on every device I tested it on.
As a test I put that profile to activity supression, assigned it and put it back to Native Mode and the issues started to happen again.
Now I'm trying to remake a profile from scratch with the exact same settings / text / template as Friday but it doesn't work anymore....

It really seems highly unpredictable.

RC
Raymond Chan Diamond Contributor
4 years ago

Try not to swich between activity supression and Native modes to avoid your problem.  Try out which mode provide the best control for your device model/agent version on a test device, and apply the same mode to all production devices afterwards.

If something goes wrong after making avoidable mode change during your tests, you might try cold-booting the device to see if the problem goes away.

Similar Discussions