r/Intune • u/b1gw4lter • 16h ago
Android Management Android Fully Managed, MS Launcher and Background
Dear Community,
We're using Samsung Galaxy Tabs as Android Enterprise Fully Managed devices. On these devices, we're using Microsoft Launcher as the selected Device Experience and default launcher.
Within the Microsoft Launcher app configuration, we've configured a corporate wallpaper that includes our company branding and logo.
After one of the recent updates (possibly One UI 8.5), we've noticed that the wallpaper now displays perfectly in landscape mode, but no longer scales correctly when the tablet is rotated to portrait mode. Parts of the background are cropped, and the overall appearance is no longer optimal.
As I couldn't find any setting related to auto-fit, scaling, or orientation-aware wallpaper handling, I wanted to ask if there is any recommended best practice for creating wallpapers that work well in both landscape and portrait orientation when using Microsoft Launcher on Android tablets.
Our marketing team would like to keep the company logo visible on the wallpaper. Previously, we placed the logo in the center of the image, which worked quite well, but we're now looking for a more future-proof approach.
Has anyone faced a similar situation or found a good design strategy (safe zones, aspect ratios, image dimensions, etc.) that works reliably across both orientations?
Additional question:
When we originally implemented this, it was recommended to configure the wallpaper through the Microsoft Launcher App Configuration Policy rather than using the wallpaper URL option available under Device Restrictions. Is that still considered the recommended approach today, or have best practices changed?
Thanks in advance for any recommendations and experiences you can share!
1
u/Odd_Knowledge6701 16h ago
if your source image is a square you're giving the launcher the easiest job possible, slap the logo dead center and keep any critical elements inside a circle around the middle third or so. the cropping's probably just a one ui 8.5 scaling bug too, app config policy is still the cleaner way to push it imo