1. I been using LOS for 5 months now (Feb to June 2022), shifted from MIUI 10 eu ROM. Its quite stable and good for daily drive. My battery is already at 75% capacity or so, using the extended kernel and getting an average of 3.5 hours SoT (3 hours lowest and 6.5 hours highest got so far)
I installed the Parrot version, it works but I can't see the picture, I have to use a third party application. Do you have a solution?For the global version of Redmi Note 5, the front camera is, as always, an issue here again. There was a patch here for LOS 17.1, turns out it's the only one working for LOS 18.1 as well. I converted the patch into a Magisk module, it's down below as an attachment (and mirror link here).
As for Gcams, surprisingly only a few worked quite well. Overall the best one is trCamera, which has overall good support for Xiaomi devices. Back camera works, front camera works during bright light. And almost always works when using Magisk module. I attached a config file as well, which mainly provides custom settings for the noise suppression. I adjusted it to have a more clean image (similar to MIUI camera), while still retaining a good level of clarity.
The other great camera is from MGC Parrot, however you need to go in his Telegram channel to get the latest version. The current one is called "v1.2 Hentai" (yes really, lmao)
I try V22.214.171.124.PEICNXM, the China version of the firmware. GPS seems ok ;-)
Downgrading the firmware seems to be the solution to the GPS fix problem.
I hoped that it also corrects the bug of the muffled sound during catches videos with the rear camera with GCAM, but no ... Too bad!
Try opencamera and report it back.I've been using this ROM ever since the device reached EOL and I'm loving it. Thanks a lot for allowing me to not be wasteful and keep using this phone as my daily driver.
However I have taken liking to photography recently and the pictures I take are all very grainy/noisy. Is this something I just have to live with?
I looked at earlier posts in the thread and appreciate the many different apps and firmwares/drivers people recommend but is there a way to get one of these solutions into the ROM release so to not have to risk running into issues with possible incompatibilities?
So for starters it certainly isn't useful to anybody outside China. As for users in China (not Chinese users, there's a difference), official LOS isn't really suitable for them anyway without further patching (at least fallback DNS, SUPL, captive portal and connectivity test URLs should be changed, Chinese-specific fonts and IME also aren't included). In practice not many people there are going to install a custom ROM on a device like this and if they do, it's most likely going to be something locally-brewed like Moqu. Thus, "helping users in China" (not "Chinese," since Chinese people all over the world by and large don't and in fact usually can't use Weixin either unless they happen to be in China) is not a realistic consideration. And as you can see it's also not as if not having this preinstalled would be an extra burden to any user in China.
I read it, again (I first did when I was looking up this APK before even writing anything in this thread) and all the more I don't see any reason why it should be included. On the contrary, it's specific to China and only compatible with some of the devices launched in that market. Why would it be so indispensable that it just has to be part of the official LOS build for this device? (If you were referring to some specific statement in what's written there, feel free to quote it, and I will look at it again.)
The whole point of having a custom ROM is to be able to critically pick and choose what should be in it from the usability perspective. Obviously this involves informed experimentation and something can occasionally break, so what? Reading something like this here makes me want to scroll back to the top of the page to check if this is still "XDA Developers."
What is that even supposed to mean? By definition it's a user-space application, so it's a "system component" as much as Candy Crush is in Windows.
I wanted to save everybody the boring details. In practice I doubt it makes any difference. It's supposed to work by querying the location from nearby Wi-Fi access points but only those with supported SoCs in them (so QCA-only I believe), and then again only those that were configured to provide it.
Actually, here you can't disable it either: given how it's set up, there is no setting for it anywhere in the UI, it just runs all the time in the background. I think it'll also interfere if you wanted to use mock location.