The current patch for bug 1186100 works with the new lockscreen state manager which is not available in earlier version. To keep things simple, the backport can be implemented as hotfix in Find My Device instead: When it requests to lock immediately, it would need to set the pass code timeout setting to 'immediately' before signalling 'lock-immediately'.

Comment on attachment 8657929 [details] [gaia] cr:immediatelockfix-v2.2 > mozilla-b2g:v2.2 Alexandre, could you review this trivial hotfix, please? STR in bug 1186100.

Landing this depends on bug 1195872 being fixed.

Comment on attachment 8657929 [details] [gaia] cr:immediatelockfix-v2.2 > mozilla-b2g:v2.2 [Approval Request Comment] [Bug caused by] (feature/regressing bug #): Design flaw. Hotfix for bug 1186100. [User impact] if declined: FindMyDevice lock command will not passcode-lock immediately when the user had configured a long timeout. Thief can continue to use the device until timeout occurs. [Testing completed]: Local tests passing. [Risk to taking this patch] (and alternatives if risky): Low risk. One-liner change in FMD which forced the pass code timeout to 'immediately'. [String changes made]: None Please also give v2.2r approval.

Hey CR, is the dependent bug not required before we land this?

(In reply to Mahendra Potharaju [:mahe] from comment #5) > Hey CR, is the dependent bug not required before we land this? This patch isn't technically dependent on 1195872 which is about broken test automation on all non-master branches. Meanwhile sheriffs have been landing a few other in the blind on v2.2. I marked my 2.2 patches as dependent just to raise awareness.

Thank you Christiane.

Comment on attachment 8657929 [details] [gaia] cr:immediatelockfix-v2.2 > mozilla-b2g:v2.2 Approved to apply patch on v2.2. Thanks