-
-
Notifications
You must be signed in to change notification settings - Fork 766
Disable ha_launcher by default and hide it in automotive #5458
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
app/src/main/kotlin/io/homeassistant/companion/android/settings/SettingsFragment.kt
Outdated
Show resolved
Hide resolved
Using this PR to fix some weirdness from the launcher setting: I propose reverting the change from this suggestion, so always passing |
Other changes get a ✅ from me |
I have another launcher app besides Samsung's OneUI and when the app closed I got the prompt to chose a default launcher, but if you don't have another launcher app, I see how it can be perceived as a crash. Also the Automotive variant didn't even cross my mind. I'll remember that for some future contribution |
The behavior I'm describing happens even without changing the default launcher. Just toggling it on and off is enough. |
Reverted |
Summary
The new feature about being able to use HA as a launcher was not properly setup in the SettingsFragment. It was enabled by default where it should have been disabled by default.
We also don't want to expose this feature in the automotive variant of the app.
Checklist
CC @fpetrovski