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...)?
https://labs.perplexity.ai also works.
To anyone with a TV running Android I recommend SmartTubeNext: https://github.com/yuliskov/smarttube
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.
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.
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 sorry. I went to a little rant, but I meant it rather funny even though I realize it feels aggressive 🤣. I am just enthusiastic about this topic even though I don't know that much.
Isn't this a problem with every package/library system? Is there really a solution to this that doesn't limit packages with how they handle their dependencies?
This may also be about trust. npm probably could limit a number of dependencies that a single package can have with an arbitrary limit, but they don't do that, because they trust the developers they won't misuse their options. Well...
Node packaging is fucked. Node packaging remains fucked.
I am sorry, but as a noobie user of npm I don't understand. It works pretty well for me if you use it normally for what it is supposed for.
I know this is probably a primitive topic for most, but I just got into coding in c++ because a simple project I am working on that uses esp8266 which can be programmed using c++. Before this I only had experiemce with python, javascript and typescript.
Now to my problem: I am trying to split my code that is getting longer into multiple files.
I already think that I understand right that each library has a header (.h) file and source (.cpp or .c in case of c) file. The first thing I already have problem with is that as you are defining your functions and classes in the header file and then implementing them in the source file you are repeating yourself with the declarations which is not something I would like. I presume that most IDEs will probably automatically help you with generating or editing the header file automatically as you change code in the source file and I guess I will need to learn to live with it.
Then there's the thing with importing. It may happen that if you create a library it also has some dependencies that it needs to include. But as far as I understand one library shouldn't be included multiple times. So from what I can see most libraries check whether a global variable with an ARBITRARY name that the library chooses itself is not defined and then if that's true it defines that variable to indicate it has been included (the name of the variable is not compketely arbitrary and usually follows LIBRARY_NAME_H but the convention cannot be really relyed on). When the library includes other library it also needs to check whether the variable of that library that is defined on its import is defined. The main file should also probably check this for every library it includes because it can't know what lins were already imported by libs it imported? Am I getting something wrong or is it sometimes ok for some libraries to be included multiple times. There's the #pragma once to handle these situations?