

1·
6 days agoIdk, seems like it’s sticking out of the back and isn’t symmetrical like the camera bar, so it might wobble or lay uneven on a table. That’s way more obnoxious to me.
Idk, seems like it’s sticking out of the back and isn’t symmetrical like the camera bar, so it might wobble or lay uneven on a table. That’s way more obnoxious to me.
Nah, the kernel isn’t that important for apps - you can replace the kernel and update the massive Android framework to work with the new one relatively easily (you will need some Linux compatibility for native code that does syscalls on its own, but that’s pretty much it - even WSL1 could do that).
It’s all the APIs and system apps provided by Google that have no reasonable alternative in AOSP that are the problem for compatibility. Look how incomplete projects like MicroG (an open-source implementation of Google Play Services) are, and their only goal is to provide Android compatibility for unofficial ROMs without installing the proper Google services.