yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Z Fold3] Acoustichayes:
To answer you, it's something that would require root to fix.

Explanation below.

Assuming two different things, Let's figure they made it easy and didn't cut the code out in the actual kernel dependencies and Samsung didn't cut it from the original build because that would be too detailed and time consuming.

Conditions to change should be in the wifi module(packages/modules/wifi), com.google.android.wifi.apex, specifically in service-wifi.jar if wifi 6 is fully disabled. Or, less likely, in framework-wifi.jar if it's just disabling end user access to wifi 6.
[General Questions and Answers] Abbasmohamed:
Is there any update for emui 10.0.0.178
[General Questions and Answers] Deleted member 1890170:
Updates automatically get rolled out by manufacturer if they deem it necessary.
[Nokia 3.1 Guides, News, & Discussion] belkaliz:
Unlocking bootloader on Nokia 3.1​

#include <std_disclaimer.h>
/*
* Your warranty is... still valid/probably? (Subject to OEM's)
*
* We are not responsible for bricked devices, dead SD cards
* unpleasant experiences. Custom ROM's are Custom for a reason and
* as developers, we try our best to give you the most complete experience
* When you choose our ROM, its a choice which you make but it doesnt make us
* liable to any unfortunate events. But we will be happy to help for the greater good.
*/

Requirements:

PC with Linux/Windows/MacOS.

Nokia 3.1 with any version of Android.

Installed mtkclient with official instruction.

Straight arms.

If you using windows, installed preloader vcom driver.

Unlocking bootloader:

Open terminal (cmd) on folder with mtkclient.

Power off device.

Run command:

python mtk da seccfg unlock

Hold a Vol- button and connect device to PC.

Wait for the script to finish.

Enjoy unlocked bootloader.

Notes:

Data won't be wiped, but it is better to make backup.

Works on all MTK devices, except entering on BROM.
[Nokia 3.1 Guides, News, & Discussion] Nicknackpaddywack101:
Sorry, but this is a bit confusing...

Is this for all mtk devices, or is this guide for only Nokia devices with mtk chips?
[Nokia 3.1 Guides, News, & Discussion] belkaliz:
In theory for all MTK. But on some devices you need to hold down different key combinations to enter BROM, and on some it does not work at all.
[Nokia 3.1 Guides, News, & Discussion] handcore:
thanks you, i tried on nokia 3.1 and it worked
[Nokia 3.1 Guides, News, & Discussion] Ricky Thunderfox:
Works!

Thx a lot.
[Nokia 3.1 Guides, News, & Discussion] htc-8925:
IDFK if I'm stupid or if my $1k+ "laptop" is but I followed the installation and driver instructions IMPECCABLY and I can't get this piece of excrement motorola g power to be recognized by python script
[Realme 6 Pro ROMs, Kernels, Recoveries, & Other De] matrix_05:
My device randomly reboot
[Realme 6 Pro ROMs, Kernels, Recoveries, & Other De] priiii08918xda:
did u flash this rom over rui 2 ?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] askermk2000:
Hey

This will not be a (much) maintained thread. This is the main thread: G5 forum

Kernel is for Lineage based roms. Works with Android 11

US996 = Officially unlocked

US996Dirty = Unlocked "the other way"

It was tested to give about 30% longer battery life, using youtube playback constantly, than stock lineage/lighthouse kernels.

Stock (original lg) rom was tested also, which lasted 7h in the test. The same as my kernel, but I dare say my kernel will be faster

in addition, but it's obviously difficult to compare stock vs lineage in that manner (stock being very old un-optimized userspace).

Keep in mind the number above is from G5 which has a 2800mAh battery. The tester's battery was also a bit worn.

-----------------------------

Downloads:

V0.8 - Androidfilehost

Beta builds - Androidfilehost

-----------------------------

UPDATE - feb 14 2022

Version 0.7 Beta2 uploaded. You'll find it in the link above.

UPDATE - april 26 2022

For H990 - version 0.7 beta4 - To solve crashing (obsolete with 0.7 stable build)

UPDATE - june 28 2022

Version 0.7 uploaded -- Built with gcc12.1, disabled kpti for better performance and enabled zram (with upstreamed lz4, zsmalloc, zram)

Removed the old builds from this post

UPDATE - feb 19 2023

Version 0.8 uploaded

Source

Thanks to @AShiningRay

I've put his undervolt, and tweak to schedutil in v0.7
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Mysteriouslog6:
I will try building the H990DS variant , Will send here.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] askermk2000:
Don't bother, I'm building now. I forgot the 990 is also a very common device.

I will also upload the final/stable build for each device at some point.

Edit: Added to post #1
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] stingbandel:
Hi, is the IR working with this kernel? Thanks
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
Unfortunately this app only checks if the IR blobs have been implemented and can be accessed by the phone's OS, because it reports the same info on Lineage's stock kernel where the IR doesn't work properly after sending the first signal, so that app is not a reliable way to test it. I could be wrong tho, since i would really like to test this kernel's IR by myself, but it throws me right into fastboot when flashing it on top of either LOS 18.1 or Lighthouse.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] askermk2000:
IR is not working. I've looked into that and i understand now why nobody has ir working.

The main driver part is in userspace, so we need to implement a solution from a msm8996

LeEco device which has the same ir chip (maxq616), on the ROM side. This is in official Lineage

here: https://review.lineageos.org/c/LineageOS/android_device_leeco_msm8996-common/+/274548

GitHub - LineageOS/android_device_leeco_msm8996-common

Contribute to LineageOS/android_device_leeco_msm8996-common development by creating an account on GitHub.

github.com

People have been saying Gamma kernel works; that may be, but looking at his sources show

no changes in that regard. So then he either wrote his own driver based on NDA restricted

documents or he found something ready-made. In any case; not making it public would be

the right ting to honor the NDA and not get in trouble.

Just putting it out here for potentially interested devs. I have shown this to one of the Lighthouse

devs, and he is currently trying to port those changes.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] askermk2000:
I see you have a H910 device. Anyone else have the same problem?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
As far as i tested some time ago, gamma kernel had the same behaviour after flashing, but i tested that one on LOS 17.1. It might be because my refurbished V20 is a bit weird in regards to the SoC. No matter where i check it, the phone reports a Snapdragon 821 (MSM8996Pro) with clock tables all the way up to 2.34Ghz and etc even on LG's stock rom, which i find really strange because the V20's are supposed to have a Snapdragon 820, so i'm not really sure if that is the reason behind the fastboot problem, since both LG stock and Lineage's kernel works just fine.

And as for gamma, even the IR on that seems a bit finicky at best due to some reports on V20 Reddit also saying it doesn't work, making it even less likely to ascertain exactly "how" or "why" it works there. I am also compiling a custom kernel for the V20 based on LOS 18.1 sources and from what i saw, gamma's source has basically identical IR files, be it LIRC or IRRC, and some logging about the IR has specifically shown me that the kernel is actually issuing the signal correctly, but something breaks between the kernel and the OS, making the ConsumerIRService return error -1 right after that., which eventually led me to this as well:

https://xdaforums.com/t/ref-how-infrared-is-not-working-on-lepro3-some-infos-for-ir-devs.3506257/

It might be something outside of the kernel, but i don't have the skills to mess around with ROMs yet and logging it is the best i can do on them.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] askermk2000:
Ah ok. I know why then.

You see, me and Omar removed some board definitions from our kernel to make it smaller. Those where definitions for sd821 V20s - which we gathered was for some prototype devices which would likely never be in circulation.

But here you are with one such device :eek: :LOL:

Edit: see here: https://github.com/stendro/msm8996_...a80921570789d20375f0b62516be3c6973ccb3375552a
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
Welp, at least the phone is doing its job of being a device mainly for development, lol. It also means your kernel probably works fine on H910's running a snapdragon 820, and thanks for clearing that up, makes me feel a bit more comfortable knowing that the chance of my phone being some kind of Frankenstein is a bit smaller.(y)

If you need any testing or logs in the future, i'll be happy to help.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
Mine doesn't look very similar to this Pro version, since my variant is actually a H910 and save for the SoC, everything else fits right in line with other standard V20's (the screen for example is clearly 5.7", since it is relatively bigger than my 5.5" Redmi Note 4 despite having smaller bezels, while the V20 Pro reportedly has a 5.2" screen plus a Snap 820, mine also has 64GB of internal storage versus the Pro's 32GB), if i flash a kernel or ROM of any other variant it either gives me a very glitched screen rendering right at boot (US996) or doesn't boot at all.

Edit: After finding some pictures of the Pro model's back, i can now affirm that the design is completely different from mine, even the camera layout that puts the flash and laser in the center and not on the sides, while the one i have is the opposite just like the default mode, so it definitely isn't the Japanese Pro version, but thanks for the heads-up.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] askermk2000:
The Lighthouse dev I mentioned has replied. He says that LG has proprietary blobs specifically for IR, and LeEco don't. He'd rather make it work as intended with the blob, instead of using some hacky solution.

So then it makes sense that it work on first try and possibly working normally on gamma - there is some facility already there. Why it doesn't work I can't quite fathom though.

I have looked at source, dtb, configuration... but I may have missed something. I may have to compare to stock config, at least we know it works there.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
I guess the only reason the IR supposedly works in Gamma is due to proprietary code not released on Github, because i ran through a massive gitlog of its repository going all the way back to january 2016 and there is no relevant commit about LG's IR as well, only the CAF updates seem to change IR files, and those seem to be present on lineage's source as far as the files are concerned. I could also have missed something, but it is highly unlikely at this point. We could at least find someone that managed to make the Infrared work on Gamma and check if they are running the latest ROMs or if the older ones like LOS 16 are also part of the reason why it works there.

And about the Lighthouse dev's response: That's a bummer, LG could have gone with the SDK approach as LeEco did, now i can just hope he manages to port the proprietary IR blobs successfully, since the only alternative left would be to reverse engineer it.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] askermk2000:
Was my conclusion first as well.

I checkout to gamma-pie source and did a quick make, to create .config for H850. Then I compared to lineage h850 config.

There are two options that stand out that are enabled on gamma but not on lineage, those are:

CONFIG_DEVPORT

CONFIG_AUDITSYSCALL with accompanying (CONFIG_AUDIT_WATCH and CONFIG_AUDIT_TREE)

I did see this before but didn't pay much attention, but now that we know blobs are present, perhaps they make use of some of those facilities.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
There's also a possibility that those configs are only needed on older android versions, as that gamma branch is for android 9 and we are currently on 11. But nonetheless i will add those configs into my kernel and see if it compiles, then check if the IR status changes, shouldn't be much of a problem. I'll report back in a few hours.

Edit: Managed to test it sooner than expected (thankfully no repo sync was needed on lineage sources), and there was no change whatsoever, the infrared still fails after the first transmit signal.

The audit configs themselves are mostly used to audit file changes in the kernel so it is more of a system admin feature, while the devport one was more promising, since there was a chance that the IR could be using /dev/port as a way to let the apps interact with it directly, and considering how hacky some proprietary code can be (LG messes up even the KDZ recovery files sometimes, like with my old LG Leon, essentially making it unrecoverable), so you never know.

Turns out the lineage kernel source code has all of those configs defined in the files and they were just disabled.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] askermk2000:
Thanks for testing. I'm compiling gamma kernel now to see if it works, else there's no point in messing with that source.

Another interesting bit is module signature. Gamma has modules enabled and signature disabled. Then I though it might

be possible for blobs to be signed and verified in a similar manner as the *.ko modules in lib/modules.

I asked on irc with some knowledgeable folks, and the answer was: yes its possible. but I'll see at least if gamma works as is, if it does then that could be the cause.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
Understood. As it stands, all modules compiled by the lineage kernel are test modules for TCP, IO Blocks, optional TCP algorithms and other nonessential things, everything else is baked into the kernel itself. The general lack of warnings of any kind pertaining to them also means that everything that should be compiled is being completed without any problems, unless lineage's default GCC and Clang are implicitly omitting those errors. I'm almost releasing my custom kernel here on the V20 subforum as well, so it will be easier to find people to test it too.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] askermk2000:
Ok, so it seems it didn't work.

I haven't used the phone previously as a remote, but I got Asmart remote on there, and have a samsung tv in standby.

I tried to shuffle through all samsung models pressing the power button, but tv didn't react.

Then I tried looking at the ir led through a phone camera while pressing button and I could not see anything.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
That's the worst part actually, i only managed to ascertain that it works on the first transmission because my IR app had a preset that worked on my LGTV right at the start. Mi Remote for example behaves just as your app is behaving, where my TV doesn't respond at all to it, so i guess the phone's IR hangs no matter if it sends the correct signal or not. The only difference there is that my H910 still flashes the IR light even after the first transmit while using Lean Remote, but with a massive delay between each cycle and even freezing the app for a while, but still, only the first command is issued.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] xxseva44:
Issue is most likely kernel related OR consumerIR related. Reason it works on gamma is that it's using an older version of the linux kernel source compared to say los 18.1. After the kernel was upstreamed, Ir broke.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] xxseva44:
Reason it only sends one signal per flash of the kernel is that after it sends that command, the ir drivers crash
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] askermk2000:
Strange thing is, I found download for gamma kernel H850. I tried both v0.0.6 and v0.0.7 still couldn't get any light from the led.

It was discussed in the thread how IR works with those, but that was back with LOS 15.1 and possibly LOS 16.

IDK what's going on in my case (the app itself?). I think I'll just get back to the kernel stuff. This needs some proper debugging which

I'm sure many of you are better suited than me.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
I suppose we should narrow it down to a version where the IR works. Considering that there is only one upstream commit touching LG's IRRC driver implementation(which i assume is the one being used by the phone), and that upstream can be found here, i might be able to revert the codebase to an older version than that one, fix up some things so it boots on my SD821 H910 and then test it.

But is it confirmed to be working by someone in the community? No matter where i check, even outside of XDA the reports are kinda conflicting on that front.

Edit: Yeah... i don´t think this will work because reverting the commit above basically removes LGE's UEI IRRC driver, so that same driver has effectively two states in gamma's repo: 1 - Non Existent, 2 - Identical to LOS 18.1 after the upstream. And the fact that i couldn't find any relevant commits other than that one even going as far back as January 1, 2016 makes the situation even messier, as i have no idea how to go about checking the IR even on gamma now. There are some changes on other IR drivers and codecs such as lirc where the LOS source has newer code, so i will try to revert those back instead and see if it works, but does the phone even use lirc?

I don't think reverting a simple "check for integer overflow" will fix the problem. I am not a ROM developer, so i have no idea about the way the IR communicates there, does it use more than the LG's driver from the kernel? If so, it would help a lot to know the underlying steps taken by the infrared such as libs used and etc, making it easier to pinpoint where the problem could be if it is in the kernel.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] askermk2000:
Ok, we are getting close after all :)

I do hate doing debugging and routine testing, but eventually got around to trying a different IR app, Lean remote as AShiningRay mentioned.

So now I got some response from the TV, on my kernel, but only first try. Then I tried Gamma kernel v0.0.6 again and damn it works properly, and

finally I tried the self-compiled gamma kernel (gamma-pie branch) and that one works too. This was on Lighthouse android 11.

So then we can't really be far from figuring it out. There's no doubt now, gamma kernel as it is on github, works! period.

Two possibilities as I see it:

1 - The commit above (v20: Import LG msm8996 LineageOS base on top of CAF.) contains some subtle edit.

2 - Gamma uses a newer CAF base kernel (don't know exact tag), one or more of those caf patches must have solved something.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
That's great! I'm in the process of updating my kernel to linux 3.18.140 right now (done, i just need to apply some fixes in order for it to boot as there were some conflicts) and adding some CAF patches as well. Once that's done, i'll take a look at the IR again, editing gamma to boot on my phone should clear some things up as i debug it.

And about the possibilities, yes, both are equally valid as the commit i mentioned has some sparse changes not present on Lineage's source, some related to IR and whatnot, but it is a lot of files to check through and will definitely take a while to go through. Hopefully we get to the end of this, since the IR is kinda crucial for some.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] pro_granade:
It's so cool to see people still giving this awesome gem of a phone some love still <3
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] askermk2000:
So IR was functional on stock lineage kernel before being upstreamed?

My stock lg kernel is also upstreamed, and I'm sure I would have gotten many complaints if IR broke. Not to say it's impossible, but at least it didn't break on the stock kernel for some reason.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
That's actually a good point, i'll strip the boot.img from an older LOS 15.1 rom to test if the upstreaming was the problem. For completeness sake, the kernel versions i am currently testing are as follows:

mk2000 & Swan -> v.3.18.140

LOS 18.1/Lighthouse Stock -> v3.18.113

Gamma Oreo Stable(the one i just confirmed to have the IR working, gamma-pie throws many errors here) -> V3.18.71

So yes, the Gamma Kernel is running an older version of 3.18 and the IR works fine there. That leaves us with 2 things: Either the kernel upstream broke the IR, which i will verify shortly, or Gamma has some commits that fix it when compared to Lineage's sources like the CAF upstream i linked some time ago. I will also run a git log on lineage's commit history to check if there is anything suspicious after i test the old lineage kernel. As it stands, only gamma managed to get the IR working on my H910.

Small edit: Will be testing the lineage 15.0 kernel source instead since 15.1 also seems to have been updated do 3.18.113. At least on github, LOS 15.0's branch appears to be running on v3.18.78 which is the closest one yet to gamma.

Edit 2: Yeah... things aren't looking good. I couldn't find a LOS 15.0 kernel or even a 15.1 for that matter(x86cpu's requires drive access and i'm not even sure he will answer) and also didn't manage to compile a working one as well. Not only that, but the lineage's sources definitely had the IR broke as far back as 3.18.102 at least, which is the oldest one i managed to compile with some changes and a supposed IR fix committed in the same code base here. All newer LOS kernels should already have that fix, and that means that this fix itself does not help much. Even compiling the kernel after reverting it to this exact commit results in a non-working IR. To be honest, i don't know what to do now because all commits related to the IR are either newer than 3.18.102, or do not fix the problem. If anyone else has a tip or anything that may help solve that i'm all ears.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] xxseva44:
Then yea it's an incompatibility between the kernel and consumer ir
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] askermk2000:
Does the Lineage H990 work with *DS? Because it's basically the same setup/config

I'm using on my kernel. I remember doing some fancy things on my stock kernel to

differentiate between single and dual-sim, but I don't recall exactly what now.

If needed I can do something similar here probably.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Mysteriouslog6:
Will check and report tomorrow , Currently the V20 isnt being used.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] xxseva44:
It does work with dual sim variants
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Black6spdZ:
I have 15.0 and 15.1 LOS 996 Roms if that's what you're looking for. Also, just flashed the .5 kernel and get the old scrambled video after boot.. I haven't seen that issue in years ;) but glad few of us still running these nice old phones
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
Well i tried those kernels a few days ago (got them from x86cpu) and they are a no-go in newer roms like LOS 18.1 or Lighthouse, but it seems the IR never worked in their kernel at all according to x86cpu's post about Lineage 15.1. Even Gamma's IR seems unintentional tbh. We're still looking at it, but we have no idea how to fix this particular problem yet... it just gets a bit exhausting after consistently turning the kernels upside-down trying to figure out what is causing the IR to fail.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] askermk2000:
New Builds Available

V0.6 - Androidfilehost

V0.7 Beta1 - Androidfilehost

Source
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] askermk2000:
Re-uploaded builds due to build environment causing messed up builds.