companion | Bitfocus Companion enables the reasonably priced Elgato Streamdeck and other controllers to be a pro

Just ran into the same issue - you need to instantiate a ManagedVirtualDevice object and configure it, before adding it to your devices list:

I've worked with Compose since the early alpha stages and became quickly disappointed with Google's lame attempt at providing a more modern approach to navigating a single-activity app. When you consider that Android's view-based system was entirely replaced with the declaration approach that Compose uses, you have to seriously wonder why they would stick with a navigation controller that doesn't allow you pass objects from one screen to another. There was also the issue that adding animation when transitioning from one screen to another was an afterthought. There is an add-on that supports animation transitions.

But perhaps the worst thing about Compose was its lack of handling device configuration changes. Under the older view-based system, you defined your layouts in xml files and placed these in resource folders that had qualifiers in the folder name that would aid Android in picking the correct layout based on things like screen density, orientation, screen size, etc. That went out the window with Compose. Eventually Google did add APIs to handle composables that need to be selected based on screen sizes and densities. But ultimately, you end up writing this decision logic within your composable and your code starts to look like spaghetti. Google's Android team completely forgot about the most basic "Separation of Concerns" when they chose to mix UI layouts with the logic that determines which layout gets selected. Designing your composables is one thing and how they get selected is another. Don't mix the two. Your composables become increasingly less reusable when you integrate those APIs. The original developers of Android (who weren't from Google) knew well enough to have the operating system manage the layout selection based upon changes to device configurations.

I chose to create my own framework that handles navigation and manages composables in almost an identical way that the view-based system works. It also remedies the issue of not being able to pass objects from screen to screen. If you are interested, you can check it out at:

https://github.com/JohannBlake/Jetmagic

So to answer you question about whether Compose Navigation is good for navigating, I would have to say no. I have worked with it and have found it severely lacking. If you want to be just-another-run-of-the-mill-Android-developer, then use Compose Navigation. But if you want to chart your own path and liberate yourself from Google's poor design practices, then use Jetmagic or even better, create your own navigation framework. It isn't that hard.

Apps that target Android 12 (API level 31) or higher can't start foreground services while running in the background, except for a few special cases. If an app tries to start a foreground service while the app is running in the background, and the foreground service doesn't satisfy one of the exceptional cases, the system throws a ForegroundServiceStartNotAllowedException.

Exemptions from background start restrictions

In the following situations, your app can start foreground services even while your app is running in the background:

• Your app transitions from a user-visible state, such as an activity.
• Your app can start an activity from the background, except for the case where the app has an activity in the back stack of an existing task.
• Your app receives a high-priority message using Firebase Cloud Messaging.
• The user performs an action on a UI element related to your app. For example, they might interact with a bubble, notification, widget, or activity.
• Your app invokes an exact alarm to complete an action that the user requests.
• Your app is the device's current input method.
• Your app receives an event that's related to geofencing or activity recognition transition.
• After the device reboots and receives the ACTION_BOOT_COMPLETED, ACTION_LOCKED_BOOT_COMPLETED, or ACTION_MY_PACKAGE_REPLACED intent action in a broadcast receiver.

For more info please check link1 link2

Equality is essentially defined as (Any, Any) => Boolean. Mostly because of Java legacy. That means that in fancyDouble == double the expected type of expression double is Any and no implicit conversion will ever trigger.

However Scala 3 introduced the CanEqual typeclass to make equality a bit safer. If you want to compare values of type A and B, an implicit instance of CanEqual[A, B] needs to be in the implicit scope.

Apparently, it's an Android Studio filtering issue. I'm having the Tracking there to filter the log. And it shows multiple log of the same type.

When I remove a character from the log, then the filter get corrected. After putting back the character, the filter is still okay.

See the GIF below.

Create a background.xml finl and set this to the spinner background

Recently on my project I have seen a similar error.

You need to add @HiltViewModel in your vm,if you using hilt vm factory to inject vm in your activity/fragment.

Also, you can just bind your MoviesRepositoryImpl with MoviesRepository Instead of writing a provider for it, you are already using constructor injection for MoviesRepositoryImpl

How about -

Filter extends (HttpHandler) -> HttpHandler and the function type (HttpHandler) -> HttpHandler has a single abstract method (operator) - invoke - implicitly declared, like this: