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
Same issue as #3812 except when the launcher crashes, the phone locks and reloads. I tested on Nightly#1532 and had the same issue, but no crash notification with logs appeared.
Might be Samsung's fault? (Tested on Samsung device.)
Steps to reproduce
Steps to reproduce the behavior:
Set Lawnchair as home app.
Reboot (So Lawnchair is launcher on boot.)
Open any app with predictive back gesture support, e.g. hold down and open home settings.
Try to use back gesture (Instantly starts to crash)
Note: Workaround found
Open the stock (OneUI Home) launcher (Doesn't even have to be set as default, just has to be opened.)
Close it
Predictive back gesture back to home screen works normally on Lawnchair.
(I can automate this workaround using Tasker, Go Home action with OneUI Home as the package, just has to open the launcher and then the launcher can be exited.)
Expected behavior
Show back gesture animation and not crash.
Screenshots
No response
Device information
Device: Samsung Galaxy S22
OS: stock Samsung OneUI 6.1 Android 14 (Unrooted)
App version: 14 Beta 3 and Nightly
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
Same issue as #3812 except when the launcher crashes, the phone locks and reloads. I tested on Nightly#1532 and had the same issue, but no crash notification with logs appeared.
Might be Samsung's fault? (Tested on Samsung device.)
Steps to reproduce
Steps to reproduce the behavior:
Note: Workaround found
(I can automate this workaround using Tasker, Go Home action with OneUI Home as the package, just has to open the launcher and then the launcher can be exited.)
Expected behavior
Show back gesture animation and not crash.
Screenshots
No response
Device information
Additional context
No response
The text was updated successfully, but these errors were encountered: