OS Update policy behaviour?Solved

Hey @douglas, 

We’ve been running android devices with Hexnode for quite some time, and this topic comes up often. 

From what we’ve seen, there isn’t really a way in the console to view pending OS updates or track how much postponement time is left. Android doesn’t seem to expose that information back to the management layer, so the postponement works more like a holding period than something you can actively monitor. 

On the postponement behaviour itself, our understanding is that hexnode’s role is limited to deferring updates for the configured window. It doesn’t schedule or trigger an install once that window ends. After postponement expires, Hexnode is essentially no longer blocking the update, but what happens next is still handled by Android and the device manufacturer. 

In practice, that means updates don’t automatically install just because postponement ends. Whether the update shows up again, prompts the user, or requires manual interaction varies by OEM and device model. 

Kiosk mode adds another layer. Allowing com.android.settings in Background Apps can help surface update related screens or notifications, but it doesn’t necessarily give users the ability to initiate updates while admin level restrictions are still in place. 

We’ve generally treated postponement as a way to delay updates during a control window, not as a way to manage or automate the update flow end to end. The rest tends to depend on how Android and the OEM handle updates on that device. 

Hope that helps based on what we’ve observed.