INstalled and using , gets stuck sometimes . Still exploring the ROM . Gpay and other apps work ifne. I dont see aperture cam app yet.
[ROM][R][OFFICIAL] LineageOS 18.1 for Xiaomi Redmi Note 5 Pro [whyred]
- Thread starter SebaUbuntu
- Start date
Sometimes random freeze, but smoothnessUn official LOS 20 available here - good to see things on the works -
LineageOS 20 for Redmi Note 5 Pro whyred
LineageOS 20 for Redmi Note 5/Pro/Ai (whyred)www.pling.com
Have installed it with Nik Gapps - works, gets stuck here and there but I am sure over time those would go away . Thank you
I installed LOS20 today and it has Aperture camera app and its working smoothly.
Yes, Same way to install, Install it from lineage recovery by sideloading zip file using adb sideload
No, My build is failing during Kernel, Have to figure out the reason (Device tree vendor tree is ready but kernel is not building)
I tried LOS 20 by SakilMondal, Problem is LOS 20 may not get updated regularly as he is the maintainer of PixelExperience ROM for Whyred
Last edited:
Ah, Sakli is little freeze for me and doesnt support f2fs on encrypt device.
If ya, the 636 soc on LineageOS is using 4.19 kernel.
Edit: compare kernel with Nokia 6.1 plus is sound good?
Not 4.19 kernel, its working only on 4.4.302
6.1 plus also using 4.4.302
I tried using nokia 6.1 kernel but whyred is failing at selinux.
Will do detailed comparision today
Nokia 6.1 plus users are lucky that its supported by recognised developer
Nolen Johnson
My point is maybe Whyred will be done by Seba when another xiaomi platform with 636 family is ready. I read on Jasmine Mike will be working here sometime early next month.
Yes, those 6.1+ are pretty lucky. I think if Whyred was done in 4.4, we could too. But in LineageOS the same family requires using the same code, e.g Whyred, Jasmine, Tulip, Lavender and it looks like they will only come with 4.9.
Good luck guys to see deeper details.
Thanks for these information,My point is maybe Whyred will be done by Seba when another xiaomi platform with 636 family is ready. I read on Jasmine Mike will be working here sometime early next month.
Yes, those 6.1+ are pretty lucky. I think if Whyred was done in 4.4, we could too. But in LineageOS the same family requires using the same code, e.g Whyred, Jasmine, Tulip, Lavender and it looks like they will only come with 4.9.
Good luck guys to see deeper details.
I will keep an eye on these activities
LineageOS - Browse /LineageOS18.1 at SourceForge.net
Open that link
I have uploaded official lineage 18.1 zip file dated 24.10.2022
OR
Direct download link
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
77
LineageOS is a free, community-built, aftermarket firmware distribution of Android 11 (R) designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS still includes various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS GitHub repo. And if you would like to contribute to LineageOS, please visit Gerrit Code Review. You can also view the Changelog for a complete list of changes & features.
Installation instructions
Here
Device info
Here
Download
Here
Sources
ROM sources: LineageOS
Kernel sources: Here2118To clarify:
It was not a device-side issue, nor a ROM side issue, it's actually a build server isssue
If someone want an accurate explanation, ask me
If you don't, just wait the next build169Re: SoterService & Qualcomm Location
1. SoterService
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.
This APK was not included in official LOS 15.1. I don't even recall it being a part of MIUI Global ROM for this device. Those lucky few who have the use for it (if anybody at all) will know how to install it, just like everybody else installs all kinds of other stuff on top of LOS. However, Lineage OS defines itself as a "free [as in 'libre'] and open-source operating system," and incorporating proprietary, third-party blobs of dubious benefit to the user is hardly in line with the project's objectives.
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.)
For the record, I never said it was spyware, just a leftover that serves no purpose. But device security can be compromised in a number ways, for example through an exploitable bug in the APK. We all know the whole vendor blob for this device is completely outdated. The less is kept of it in its original form, the better. If something can be safely removed without impact, this should be the default action to take.
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."
Vendor blobs are not sacred. Xiaomi's in particular are usually rather bad. For instance, previous vendor blobs for this device enabled Wi-Fi diagnostics by default, needlessly spamming the logs and draining battery. Should this have been kept too?
2. Qualcomm Location
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.
The benefit is supposedly better location indoors, so it could be life-saving if you get lost in a shopping mall but 99.9% of the time when you need precise location is when you are outside and not near any particular Wi-Fi access points.
The idea behind it is not unsound and it could indeed save battery life if GPS doesn't have to run in such situations (and if it really is indoors then it wouldn't work anyway) but the bigger point is that Google (and others) have already been doing the same for years and are better at it. So if you install Google Apps you are already getting all of this functionality anyway.
You can't blame Qualcomm for trying even though they're late to the game but essentially it's about duplicating what already works just was "not invented here." Your location won't get any more precise than what Google already provides, all it accomplishes is Qualcomm being able to use your battery time and data allowance to seed their own database so as to compete with the incumbent.
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.
So even if Qualcomm location were to stay by default, there should be a toggle for it, or at the very least the framework overlay settings should be restored to their defaults because now it's effectively impossible to use any other location provider: it's either Qualcomm or nothing.
Since LOS does not include a complete location solution (people will install Google Apps, MicroG, or perhaps something else), arguably it shouldn't force a partial one on the user either. To be brutally honest, I thought these settings were left like that by mistake, couldn't imagine anyone defending them but here we are. (Feel free to also check out the discussion I linked to in my previous post, and the commit where it was removed for beryllium - Xiaomi Pocophone F1.)
***
I appreciate your effort in building this ROM and making it official. I understand the way you responded must be due to the impression that I attacked or criticized your work. This was not my intention.
I'm not saying anybody should do anything, I'm just sharing what I did. Hopefully it can help others one way or another. And if I'm wrong about something I'll be the first to admit it, after all I'm here to learn.
In the end it's your work and your decisions, you'll do as you wish. But there is a valid argument for the majority of the users and readers of this thread not to have these included in the official LOS build, which is why I wrote about it.
Agree or disagree, either way it's really not necessary to make any of this personal.
New posts
-
General Android desktop mode can also run the Linux desktop
- Latest: HopelesRomantc91
-
-
