Android Development

Hi guys.

I have an android head unit for my car that only manages multimedia, navigation and stuff. it also has multiple physical buttons and knobs. It’s offbrand so can name the particular brand or model.

can I for example upgrade the OS?

cross-posted from: https://programming.dev/post/22983650

I know that Android 14 requires targetSdkVersion >= 23 (or higher on the Play Store), but are there other minimums for this and minSdkVersion?

I followed the recommended processes for adding images to my app, and it is being displayed correctly on the layout preview, but not at all on the app. I have vector assets, webp, png images, but none are being displayed.

The project is too big to put here in its entirety, but please ask for any snippets that could help you solve the issue. I've tried searching the web and asking LLMs and neither could help, so please help me, fellow humans.

Title Thanks

I have no experience with android apps and just started working on one that needs to work with relational data. The relational data has multiple many-to-many relationships and the inbuilt ORM (Room) is leads to class explosion.

While looking at ORM libraries for android, there seem to be many that are out of date:

From 5 of the Best Android ORMs (2014) and AlexeyZatsepin/Android-ORM-benchmark (2017)

• ORMLite: 3 years old and the M2M example makes me feel quite queasy
• SugarORM: description explicitly only mentions 1:1, 1:n
• GreenDAO is unmaintained but replaced by ObjectBox which I haven't yet looked at
• Active Android: abandoned
• Realm redirects to MongoDB 💀
• Freezer: abandoned
• DBFlow: no documentation and 3 seemingly abandoned
• Requery: 4 years old (abandoned?). Actually my favorite in terms of API
• Sprinkles: 10 years old, dead

I'm leaning towards Requery because I like its API the most (hides SQL the most), but haven't looked at ObjectBox yet.

I'm new to using reactive and functional programming in kotlin with libraries. I'm maintaining a project at my company that uses only .orNull() from the arrow.core.Option class.

My question is: why is the project returning the first type instead of the second one?

Single<Option<UserEntity>>

Single<UserEntity?>

Can't the DAO object return a null type if it doesn't find the object on a query such as SELECT * FROM users WHERE id = 1 ?