You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Lawnchair Notification Dots need the system notification dots specific settings enabled to actually turned on, but sadly, although most of the phone manufacturer gave user the switch, but in some cases (like my spark go 1) it didn't, so automatically, notification dots couldn't be turned on no matter how hard you try to find the settings, this lead to another features locked; "Now Playing" on the "At a Glance" provided by Lawnchair itself.
Steps to reproduce
Steps to reproduce the behavior:
Go to 'Settings - General'
Click on 'Notification Dots'
Scroll down to '... nowhere since OEM didn't provide user the Notification Dots switch'
Notification Dots couldn't be turned on, lead to Now Playing to be unlocked too.
Expected behavior
Could be forced to enabled like Microsoft Launcher and Total Launcher, which didn't need System Notification dots settings to be turned on
Screenshots
Device information
Device: TECNO Spark Go 1
OS: HiOS V14.0.1 on Android 14 Go Edition
App version: 15.Dev.(2066)
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
Lawnchair Notification Dots need the system notification dots specific settings enabled to actually turned on, but sadly, although most of the phone manufacturer gave user the switch, but in some cases (like my spark go 1) it didn't, so automatically, notification dots couldn't be turned on no matter how hard you try to find the settings, this lead to another features locked; "Now Playing" on the "At a Glance" provided by Lawnchair itself.
Steps to reproduce
Steps to reproduce the behavior:
Expected behavior
Could be forced to enabled like Microsoft Launcher and Total Launcher, which didn't need System Notification dots settings to be turned on
Screenshots
Device information
Additional context
No response
The text was updated successfully, but these errors were encountered: