-
-
Notifications
You must be signed in to change notification settings - Fork 99
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
fix: Implement BroadcastReceiver to start activity from TileService #424
fix: Implement BroadcastReceiver to start activity from TileService #424
Conversation
To resolve the UnsupportedOperationException when starting an activity directly from TileService, this commit introduces a BroadcastReceiver as an intermediary. This approach aligns with Android's best practices for inter-component communication and ensures a smoother user experience by avoiding unexpected interruptions from Quick Settings tiles.
Fixes: #415 |
@muryno btw you need to add it to the op post, so the issue linked to the PR :) |
@muryno original post - I meant that it should be in first post, writting it in comment doesnt link the issue and the pr together |
@muryno but its still not linked - I meant in first post in this PR, sorry for being clear :) |
There is a conflict @muryno |
now resolved |
I'm not able to launch OpenCalc from Tiles 🤔 |
|
@Darkempire78 now updated from using broadcast receiver and sticking with google documentation TileService |
Thank you! 🤩 |
Sorry for the waiting |
Fixes #415
Refactor: Use BroadcastReceiver for TileService activity launch
Switched to BroadcastReceiver approach for starting an activity from a TileService due to its compatibility with Android's security guidelines, ensuring a smooth and non-intrusive user experience. An alternative could be using notifications, but they may not prompt immediate action as effectively.
The notification approach, while less intrusive, may not be ideal for all scenarios, especially if immediate action or interaction is required from the user. Notifications can be easily missed or ignored, leading to a less responsive or immediate user experience.
More guide on this Android developer guide