Kotlin good first issues

This issue proposes adding automated code formatting and static analysis tools to the CI pipeline for this repository. The goal is to improve code consistency and catch potential issues early, as currently, there are no tools enforcing style or performing static analysis for Kotlin, XML, or Java code. This will involve integrating tools like ktlint, Detekt, xmllint, and Android Lint into the CI workflow.

Users are experiencing significant loading delays for the first image in the 'Place Values 1' lesson, particularly when the app's language is set to Arabic. This issue occurs with locally stored images in the beta version and is not reproducible with demo explorations that download images.

This issue proposes a code health improvement to standardize the naming convention for all XML IDs to use `snake_case`. This change aims to enhance consistency across the codebase, making it more readable and maintainable.

The survey list incorrectly displays a "No surveys" message and a sign-out button during a reload if the initial attempt times out. The proposed solution is to increase the timeout duration, which is expected to resolve this visual glitch.

The user is requesting a feature to easily navigate back to a predefined 'base' or 'home' URL within the Ava Pro browser. Currently, there's no quick way to return to the starting URL after navigating to external links or different sections of Home Assistant, unlike in Fully Kiosk Browser.

This issue proposes a new quest for OpenStreetMap data collection focused on identifying and tagging organic products in food-related businesses. The quest would involve checking for the presence and value of the 'organic' tag in various food establishments and shops, with proposed values of 'yes', 'no', or 'only'. The issue also includes suggestions for the quest's visual representation, such as an orange color scheme and a leaf icon.

This issue proposes adding support for multiple-instrument callbacks in OpenTelemetry. This feature allows a single callback function to observe and process data from several asynchronous instruments simultaneously, which can optimize expensive read operations. The implementation will involve new API types and updates across various modules.

This issue proposes adding a new login method to the mobile application that utilizes a join code. Currently, the web interface supports this, but the app only offers username/password or Home Assistant OAuth. The fix involves implementing the join code exchange mechanism and storing the resulting token.

This issue requests the addition of functionality to add radio stations or tracks via URL within the application's Radio and Tracks lists. Currently, this feature exists in the web version but is missing in the app. The proposed solution involves adding a toolbar action with a text dialog, which should be hidden if the user lacks write permissions to the library.

This issue identifies that while certain metadata like descriptions, biographies, reviews, publishers, and narrators are parsed by the system, they are not currently displayed in the UI. The fix involves adding expandable text blocks to the `ItemDetailsScreen` to show this information based on the item type.

This issue proposes adding a long-press action to library items in the web interface. This action will mirror the existing "Refresh" and "Find on music services" functionality, which is currently accessible via `music/refresh_item` and requires specific library management scopes. The goal is to make these features available through a more intuitive user interaction.

This issue requests the addition of three queue item actions (play next, move to end, and radio from item) to the long-press menu in the mobile application's queue view. Currently, the mobile app only offers 'Add to playlist' and 'Delete' in this menu, while the web version has these additional options.

This issue proposes adding a "Save queue as playlist" feature to the mobile app, mirroring functionality already present in the web player. The fix involves adding an option to the player menu, prompting the user for a playlist name, and later hiding the option until library write permissions are available.

This issue proposes a UI change in the web player to display a 'Stop' button instead of a 'Pause' button when the player does not support pausing. The corresponding backend command for stopping the player is also not being sent, which needs to be addressed by routing through `PlayerRequestFactory`.

This issue proposes adding a detail screen for radio stations, mirroring functionality present on the web. The detail screen should include a tracklist tab, but this tab will only be visible on version 2.11 and for non-endless radio stations.

This issue proposes adding a detailed screen for tracks, mirroring the functionality available on the web. The new screen will include tabs for albums, versions, similar tracks, and lyrics, leveraging existing components where possible.

This bug report suggests that images downloaded by the Bunori app are being stored in the user's gallery folder instead of the app's cache. This can lead to images disappearing if the user manually deletes them from their gallery. The proposed solution is to change the storage location to the app's cache.

This bug report highlights missing tests for features merged in Beta MR1. Contributors are asked to write tests for specific scenarios related to PIN password management, profile deletion, and translation handling, with a focus on UI verification and domain layer functionality.

The user is reporting that the "island" feature in HyperLyrics Enhanced is only displaying the song's artist, title, and cover art, and is not showing the lyrics as expected. This issue occurs for all songs and is persistent across different tracks.

The issue reports an `android.database.sqlite.SQLiteException` with the message "no such table: workspec". This indicates that the database is trying to query a table named 'workspec' which does not exist. The stack trace points to the `WorkSpecDao_Impl.getInputsFromPrerequisites` method, suggesting a problem with the database schema or initialization related to work specifications.

This issue proposes adding support for timezone switching within a multi-tenant mode. It aims to allow users in different geographical locations to have their time displayed and managed according to their local timezone, enhancing the user experience for a global user base.

This issue tracks the progress of getting the 'Vela' application to work with Android Auto across various Android installation methods and ROMs, including stock, GrapheneOS, and rooted devices. Different approaches like KingInstaller, AAEnabler, PlayInstaller, and Gearslip are being tested, with varying degrees of success depending on the phone's setup and the car's head unit.

This feature request proposes optimizing the CI workflow by pre-checking for the existence of a signed Android App Bundle (AAB) in Google Cloud Storage (GCS) before initiating a potentially lengthy Bazel build. This would prevent wasted CI time and resources when the same code revision is accidentally rebuilt.

The user is experiencing an issue where audio from phone calls is not being forwarded to their Amazon Fire tablet when using Wireless Helper and Android Auto. While other Android Auto features like navigation and Spotify work, call audio remains on the phone after answering on the tablet. The user is asking if this behavior is expected.

The user is experiencing intermittent connection issues with a USB dongle to their phone. The dongle connects to the phone before the app is ready to detect it, leading to connection failures. They've found a workaround by delaying the dongle connection but are seeking a more robust solution, and also note that the USB-only mode seems to still attempt wireless connections.

The project is seeking 20 users to participate in a closed beta test of their app on Google Play for at least 14 days. Testers need to join a Google Group, opt-in as a tester, and install the new version alongside the existing app without needing to uninstall it.

The user is asking if the project is available or can be made to run on the Windows operating system. This is a straightforward question about platform compatibility.

This feature request asks for modules to integrate Supabase Authentication into a custom backend, specifically targeting the Spring Boot framework. The goal is to provide a package that can decode JWT auth tokens and offer ready-made integration for common use cases where a frontend (like React/Next.js) communicates with a Spring Boot backend that relies on Supabase for user authentication.

A user is reporting an issue with importing cards into Ankidroid after a recent update. They are seeking confirmation from other users if they are experiencing the same problem and have provided a Discord link for further discussion.

The user is requesting an update to the in-app setting description for "launch other apps." The current text "Allow cards to launch other apps" is misleading because cards can still open apps like the Play Store or YouTube even when this setting is off, due to App Links. The proposed change is to refine the description to accurately reflect this behavior.