Lawnchair 2 is no longer under development. The development team always starts to develop a new launcher based on the latest stock launcher every time a new Android version is released (so basically every year). This way the app usually never gets past the alpha or beta builds till they already move on to start from scratch. I don’t understand their strategy.

I use Google Lens and I also have to keep Google app installed. I agree it’s annoying that they just can’t make the apps work standalone. There already is a package that nearly all Google apps dependend on. The package is Google Play Services. Why can’t they implement this into Google Play Services as they do with all the other stuff (quick share, find my phone, location services etc…)?

I am not aware of any.

Well the messages app that comes with samsung does support Google’s RCS as far as I know.

Google implementation of RCS (Jibe I think it’s called) is proprietary. A third party client has to be explicitly allowed and supported by Google.

Did you flash a custom ROM? Maybe it will work with a custom ROM.

EDIT: Your phone uses Mediatek processor, so it’s not going to be well supported. I recommend you to stick to locked bootloader and just live with the phone as it is.

https://topjohnwu.github.io/Magisk/install.html

Did you unlock your bootloader? Some apps just scan for Google Play SafetyNet or in some other way to check whether you unlocked your bootloader or rooted and if they think you do they will vaguely state you are rooted.

Other’s concern about your phone being infected are justified and I recommend you to try whether a dedicated root checking app thinks your phone is rooted. These usually don’t lie.

Regarding your rooting situation I always rooted the lazy way. Renamed magisk.apk to magisk.zip, flashed it and it always worked for me. But I rooted only 2 phones in my life really and this is not the recommended method by magisk developer.

deleted by creator

It is not only ironic but pathetic. They promote it as the new open standard and people who just don’t look further into the details believe it.

AOSP source code

He is asking about Android studio not Android Open Source Project?

KOReader. The app is multiplatform (also for some e-readers and Linux) so the UI is not among the most beautiful (but I actually prefer it over Librera), but it’s feature packed, and does really well what it’s made for.

I am not sure if it’s only me, but I have noticed much faster Wi-Fi connecting after enabling Wi-Fi on Android 14, so that’s one thing. But it may be also caused by kernel update and has nothing to do with Android 14.

because they are the only devices on the market that allow locking the bootloader after installation

AFAIK on Xiaomi Mi A2 lite if I flash back the stock fastboot ROM (I had it do it once because I crippled the partition images (this phone is A/B partition device)) it locks your bootloader and you have to unlock it again. I don’t know if this applyes to MIUI/Hyper OS phones too, because Mi A2 Lite uses near to stock Android.

I don’t understand. So if I only lock my phone (turn the screen off) without rebooting it, it is not fully encrypted (considering that the device storage encryption is enabled)?

I don’t have that option and I am on near stock Android 14. This is probably manufacturer-related.

deleted by creator

You can disable Chrome, but not uninstall it, because Chrome is what backs the modern WebViews used in all kinds of apps.

You can safely uninstall Chrome over adb shell. There’s a specific webview package that takes care of webview (com.google.android.webview), not Chrome.

I think you are over exaggerating here. This isn’t just a case for Chrome to first introduce the new features to iOS, but many other cross-platform apps choose to do so. And it doesn’t need to be because nobody cares about Android. Android still has a larger user base especially when it comes to Chrome. But when you develop for iOS you optimize for tens of devices (maybe not even that) and maybe the latest 3 iOS versions, but when you develop for Android you optimize for thousands of devices from different manufacturers, that put different skins on top of Android, where one runs Android 13, the other one Android 11, and the another one Android 9. Hence when releasing a new feature you first put the work to the iOS version, see the user feedback, change and tweak some things and then put the work to make a functional Android version. I am not a professional dev myself by any means, so I can’t really say everything in confidence, but developing for Android probably takes more debugging and time, because of the variability of the environment the app will run in.

No one is able to write the name right 😅. It’s Kvaesitso. I mean no bad. It’s pretty uncommon name. It just makes me smile to see it written wrong more often than right.