![]() Thought not consistent in our triaging we have seen that sometimes this may be due to the following reasons Alternatively you can get a new Wallpaper without transparent layers and upload it. JPEG's replace transparent layers by either black color or white color. If you have a branding with a Wallpaper, please edit the branding and upload a JPEG version of the wallpaper. However on the above models, as the bug reports and crash reports indicate, the transparent layers are causing an OS level crash causing the device to boot into recovery mode. Transparent layers are part of images which have no color and when applied on the device pick the background color of the device. ![]() ![]() We have observed that this issue happens if there is a branding applied to the device with a Wallpaper that has Transparent (Alpha) layers. Root Cause: Branding with Wallpaper that has Transparent Layers This has been acknowledged as a Known issue and a fix is slated for Android OS 11 release. This has been acknowledged as an OS specific issue and can be reproduced using Google's Test Agent. We have contacted Google Android team and the respective OEMs and have provided the device logs. Models: SM-G398FN, SM-J530F, SM-A405FN, SM-A105FN, SM-G398FNĬurrent Status: Open Scalefusion Plan of Action - Part 1: Report Issue to OEM & Google.First Report Date: 25th May 2020 Issue Observed On ![]() In some cases a message is displayed on reboot which reads System UI has stopped and the issue is typically seen across multiple reboots. This basically causes the devices to show the Recovery Mode screen to the end users, requiring the device to be factory reset and enrolled in Scalefusion again. We have observed that on certain Android EMM devices which are set-up in Kiosk or Agent Mode, boot into recovery mode. Android EMM Devices booting into Recovery Mode ![]()
0 Comments
Leave a Reply. |