yashsingh1/xdaforums huggingface dataset:
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] taketwicedailey:
Just to add to the DAC discussion, my experience on LOS 20 with the Extreme-Gaming Kernel was that the DAC tile would turn on, but would not stay on for longer than a couple minutes. I didn't report this as the new DAC panel was imminent. I also experienced some app crashes, but I was ok with that because I was no longer experiencing crash and reboot like I did on the stable kernel and earlier LOS 20 (also getting a new battery helped that too).

I have now used the DAC panel on the official LOS 21 with Extreme-Gaming kernel, and it now works great for me. Stays on for as long as I listened to it and really sounds great. Of the three options in the panel for HiFi mode, there is Normal, High Impedance, and AUX High Impedance. I don't know what the difference is, but subjectively the best sounding one with my headphones is AUX High Impedance. I am just using Spotify with 320kB/s downloads. Can we get some explanation from the devs as to what some of these options mean? The details given in the ES9218P documentation doesn't really mean much to me tbh. The Quad DAC tile doesn't seem to work though, and I have to go to settings to turn on the Quad DAC.

I can also say that the problem of downloading my Spotify library not working that I reported before is no longer an issue on LOS 21, so other reports of in-app downloads not working may be fixed with LOS 21.

The only other thing I can say is HOLY STABILITY BATMAN. No app crashes (so far at least), better app persistence, just a great experience. THANKS!
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
That's basically a setting for the DAC to adjust to increasingly higher levels of headphone impedance the further down you go. Normal is for headphones of 32Ohm or below, High Impedance is for anything between 32 Ohm and 600 Ohm, and AUX High Impedance is for headphones beyond 600 Ohm, which is often very high end/studio-grade stuff.

But of course, you can set whichever you like, it won't explode lower-end gadgets or anything like that, this just changes how the DAC's HiFi amplifier is set up.

Known bug for quite a while, i just don't really have the time to rework the tile itself as is (also holding your finger on the tile takes you straight to the panel)... and there's quite a few other bugs beside this one tbh.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] taketwicedailey:
Thanks, that makes more sense.

As for the tile, it is essentially unneeded now that the HiFi DAC seems to enable on plug now, I only just realized. A welcome return.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] dextructor:
@AShiningRay

I'm a little confuse with the situation here, so be a little patient please.

The latest Lineage 21 test that I installed on my H990N didn't recognize any wired headphone buttons (and multiple headphones tested just to be sure) and I reported on the official thread with it's own logcat.

I tested also with Swan2000 and the result was the same, so I'm assuming that the problem isn't on the kernel side (either stock or custom), right?

Since on Lineage 21 you and other devs (I believe @ROMSG and forgive me if I forget someone else) remake the audio route and other things to have a better solution for the DAC in general.

So the error message is: [LGE MBHC] Unsupported jack type(0x8000) is reported

The definition for MBHC(Multi Button Headset Control), and that's it.

Anyway that I can help diagnosing it better for you guys?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] ROMSG:
I didn't actually work on the DAC panel at all but from what I gather this looks like a potiential kernel issue. I'm really not sure though so take that with a grain of salt
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] dextructor:
Yeah, that's right, I was somewhat confused. It was @xxseva44 that worked on the DAC
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
After some personal debugging, it seems to be a kernel issue... which is a bit weird since nothing on our wcd drivers indicate that something is failing (besides LG's debug messages which are useless at best, and misleading at worst thanks to the stupid way they programmed those messages to be printed).

Basically, that "LGE MBHC" entry you noted only pertains to the code block that checks if any dac-specific command was sent through the aux port, and since no headphones out there save for a few specific ones will have built-in commands for this, the kernel reports the buttons as "unsupported" for that function.

As for why exactly those buttons don't work at all... no idea, might be yet another case that requires nuking lge code from the kernel.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
It was, indeed, yet another case that required nuking LGE code from the kernel. Since there's quite a few other changes queued up, i think a BETA11 isn't that far.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] dextructor:
Thanks for the debugging and testing, since you guys made the kernel from scratch and fixed many things, I believe that some bugs are more hidden than others.

If I can help please let me know.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
It wasn't really a case of it being hidden, more so, it's LGE code that shouldn't be breaking things, breaking them. V30 just got a fix for a USB kernel panic by removing LGE crap from ConfigFS/FunctionFS.

Makes me wonder if USB-PD is being hampered by LGE code... eh, that's something for later.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
02/25/2024 build is up!​

Let the backports begin!​

This build focuses on backporting some ZRAM and eBPF commits from linux 4.19 and 4.9 respectively, while also fixing wired headphone buttons.

Key Changes from BETA10:

V20 and G6 Quad-DAC drivers were updated to work with the new DAC panel debuting with Lineage 21 for LGE msm8996. (g6 won't have much use for it though, as that variant can't have its BL unlocked) - On V20, BETA10+ already covered this one

Backported ZRAM from linux 4.19, introducing general fixes and support for deduplication, allowing a bit more data to be held in memory.

Backported some ebpf commits from linux 4.9, in preparation for the big 4.19 backport which will be required for android 15.

Fixed wired headphone buttons by removing LGE code from wcd drivers.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Hadi99:
I can't find the extreme+gaming msm8996.dtsi and msm8996-regulator.dtsi values

Can you please attach them or direct me towards the directory, preferably gaming and extreme+gaming . I want to test the patches on stock

Also, is there any possibility of FUSE PASSTHROUGH backport?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
Damn... it's been a while since i last showed up here. Welp, next build coming "soon", with a MASSIVE set of changes. So much so, that at least for now, the boot times will increase noticeably.

Long story short, 4000+ commits due to a big CIP merge, with some USB and power improvements here and there. Just because LOS can't officially support the device anymore (or hopefully, for now at least), it doesn't mean it's really dead. Still plan on supporting it for a while, besides, there's still stuff to fix even if i'm short on time.

Again, a bit late for this but:

Just look at the commit history for these two files and you should be good to go:

msm8996_lge_kernel/arch/arm/boot/dts/qcom/msm8996-regulator.dtsi at Swan2000-lineage-21 · LGE-G5-G6-V20/msm8996_lge_kernel

Contribute to LGE-G5-G6-V20/msm8996_lge_kernel development by creating an account on GitHub.

github.com

msm8996_lge_kernel/arch/arm/boot/dts/qcom/msm8996.dtsi at Swan2000-lineage-21 · LGE-G5-G6-V20/msm8996_lge_kernel

Contribute to LGE-G5-G6-V20/msm8996_lge_kernel development by creating an account on GitHub.

github.com

As for FUSE passthrough, i do have a (supposedly) working backport for it, but couldn't test extensively since my SDCard died shortly after... been showing signals of failure for quite a while though, so i just discarded the results entirely.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Hadi99:
Thanks for the response.

Fuse passthrough should also affect internal storage, it is mounted through FUSE due to scoped storage enforcement. You can try batch synchronizing files to test that out.

See here
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] DevanWolf:
You forgot that USB tethering is broken. Logcat has this message:

A BETA11+ with this fix is appreciated.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] xxseva44:
Please refer to my message on the Los thread.

[OFFICIAL] LineageOS 21 for the LG V20

LG V20 - Your warranty is now void. - You have been warned. - Use at your own risk. Sadly, this device utilizes android.hardware.radio@1.3 (or below). This means that the March security bulletin - known as QPR2 - fully killed this device...

xdaforums.com
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
That's not a kernel issue. Looking at the output of dmesg, we get this once rndis is enabled:

init: processing action (sys.usb.config=rndis,adb && sys.usb.configfs=1 && sys.usb.ffs.ready=1) from (/system/etc/init/hw/init.usb.configfs.rc:134)

init: Command 'mkdir /config/usb_gadget/g1/functions/rndis.gs4' action=sys.usb.config=rndis,adb && sys.usb.configfs=1 && sys.usb.ffs.ready=1 (/system/etc/init/hw/init.usb.configfs.rc:135) took 0ms and failed: mkdir() failed on /config/usb_gadget/g1/functions/rndis.gs4: Function not implemented

And surely enough, it's not implemented in our device's init.qcom.usb.rc

,

which is supposed to handle those functions... at least, not implemented in the way android now expects it to be. Here's an example implementation from a custom xiaomi msm8996 device tree which could work for us... but this still means that the problem is entirely ROM-side and the kernel has nothing to do with it, hence i can't "fix" it with Swan2000.
[Asus Zenfone Go Questions & Answers] SomeAndroidUserBruh:
yeh I don't know if the battery is dead (probably yes)
[OnePlus 5 Questions & Answers] Pseudorando:
Hello!

I have a OnePlus 5 running OxygenOS 5.1.5 (Android 8.1.0).

It's also running Magisk 26.1, and until today, TWRP 3.2.1-x.

I enabled Zygisk, which caused a boot loop, so now I can't boot normally (though I can fix this if I can get a root shell).

But now the problem is that I also (foolishly) flashed a very recent (and apparently incompatible) TWRP 3.7.0_12-1, which hangs on boot with a white status LED, so I can no longer access a terminal to fix the Magisk issue.

I can boot into Safe Mode, but it seems very limited. No apps, no ADB (neither TCP nor USB).

Is there a way I can re-flash the recovery image to a working TWRP?

Or factory reset to the factory bootloader / recovery image while retaining user data?

I can't seem to get adb / fastboot / shell access in any of the available states:

Bootlooping standard boot

Failed TWRP boot

Safe Mode

Is there any conceivable way forward?

Thanks!
[OnePlus 5 Questions & Answers] Maxdemon5346:
Update your device
[OnePlus 5 Questions & Answers] immortalwon:
Go into bootloader mode and then BOOT the right twrp version instead of flashing.
[OnePlus 5 Questions & Answers] Pseudorando:
Are you referring to Fast Boot mode? And using the fastboot tool over USB from a computer with ADB tools installed?

If so, then that has failed by the phone not showing up as a device (via "fastboot devices").

At this point, I suspect that it may be an issue with the phone's USB port (which has always been flakey).
[OnePlus 5 Questions & Answers] Pseudorando:
A replacement USB/headphone port assembly arrived today, and I installed it successfully.

The USB connection is now solid, but the phone still does not show up when listing "fastboot devices" while on the bootloader screen.
[OnePlus 5 Questions & Answers] immortalwon:
that's because you prob have the wrong drivers installed. IN 90% of cases, its faulty driver installation. Disable windows driver signature enforcement and re-install one plus drivers. Then download platform tools and try again.
[OnePlus 5 Questions & Answers] Pseudorando:
I dug out an old Windows laptop with USB 2.0 ports, which definitely didn't have any residual OnePlus drivers on it.

I put these in Powershell:

bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON

Installed the drivers from here:

https://oneplususbdrivers.com/oneplus-5-usb-driver-download/

Powered up the OnePlus 5 into Fast Boot...

And still no devices listed with "fastboot devices".

(Except when I plug in another phone in bootloader mode... other Android devices show up fine).
[OnePlus 5 Questions & Answers] immortalwon:
I can't help if the device isn't being detected in bootloader / fastboot mode. It should have worked if its OEM unlocked and usb debugging was enabled.
[Red Magic 8 pro] PontiacGTX:
nvm
[Touch HD General] rjcb23:
You can get it for free here (with an Orange contract)

http://www.htc-touch-hd.com

Looks like my (not-so) little ole Kaiser is gonan be going for a short walk off a long pier!!!
[Touch HD General] Mr_Erratic:
Doesn't look like you can get anything from there.
[Touch HD General] rjcb23:
Oh yes you can! Click the offer sin the grey box in the middle...
[Touch HD General] sonypc100:
its just a referral site, hoping to get a few quid cashback from people clicking through to mobiles.co.uk
[Touch HD General] Spike™:
guys, go through phones4u, thats where i got mine from,

next day delivery,

cool!!!!

http://www.phones4u.co.uk/shop/shop_contract_details.asp?ItemKey=233801
[Magisk] silentthunder:
How do I mount the android system as RW? I wish to change my boot animation however the request is blocked as system isnt mounted. I tried to mount using Termux but Magisk denied the permission.

edit: device is Motorola G Stylus 5G XT2131-1.
[Magisk] surajpai524:
Magisk version? Android version?
[Magisk] silentthunder:
magisk v26.1 android 12
[Magisk] surajpai524:
Android version above 9 or 10 cannot mount system as rw. You need to create a Magisk module to replace or change anything in system partition. On mount it will Magic Mount the module systemlessly.
[Sony Xperia 5 III] calamari:
Recently I've been experiencing a low GPS accuracy in Google Maps (with the app reporting a low accuracy and offering to try to use the camera to improve it). When I'm trying to navigate in my car, often the reported location will be off by 25 feet or more. This results in navigation giving the "you missed your turn" drum sound when I'm actually going the right direction or nuisance reports saying to make a u-turn, etc. It makes me think it might be relying on cellular A-GPS rather than actual GPS. Up until recently the GPS had been excellent on this phone.

Google Location Accuracy: Improve Location Accuracy is enabled.

Location > "Use location" is enabled.

The Maps app has "Use precise location" enabled.

I feel like this might have started after I upgraded to Android 13, but I wasn't paying close attention, so perhaps not.

Anyone else having GPS problems? Is there any other setting that could cause this? Is there an app that can tell me if I'm using A-GPS rather than real GPS?

EDIT: The "GPS Status" app seems to show that the phone is seeing GPS, GLONASS, and Galileo satellites. Checking inside my car, it claims 9 foot accuracy. Strange.
[Touch Pro, Fuze General] orcwrath:
when i use tomtom with the traffic service when I go though an area with no signal, not that uncommon with a touch pro;), an alert bubble appears to say that the internet connection has been lost etc. This takes focus from tomtom and is a right bugger to 'dismiss'. I there a way to turn these alerts off?
[Touch Pro, Fuze General] Jim Coleman:
I asked this exact same question a couple of weeks back, and never got a reply. Good luck this time round!
[Touch Pro, Fuze General] StevePritchard:
I've written a program to get around this problem. I use it to launch TomTom (so it knows TomTom is running) and it checks every couple of seconds for the annoying popup, and automatically closes it. Once it notices TomTom has shut down, it ends as well.

This app needs the .Net framework. Simply run this program instead of starting TomTom (it will start TomTom for you) and you shouldn't have a problem with the popups again.

Cheers,

Steve.

[Edit : This version now has a cab installer, and it also sets the device volume to full when it starts TomTom (and puts it back to what it was afterwards).]
[Touch Pro, Fuze General] prusling:
This works brilliantly - saves a lot of frustration trying to hit the small close button to resume navigation while driving and often ending up in the middle of the tomtom menus!

Many thanks
[LG G6 ROMs, Kernels, Recoveries, & Other Developme] AShiningRay:
Don't mind me! Just reserving a post to keep tabs on this thread, and also because we might need to post something up here.
[LG G6 ROMs, Kernels, Recoveries, & Other Developme] AShiningRay:
08/28/2023 build is up!​

Ayy, time for another one (i also skipped a release on G6, smh)... that took a while, but it's here to (kinda) celebrate the LOS 20 release! And what better way to celebrate than with a ton of changes under the hood?

Quick Summary:

We're now using Link-Time Optimization alongside the latest GCC releases, resulting in an even smaller and more optimized kernel.​

This new release now fully supports LOS 20, and that includes Bluetooth.​

It now runs on the latest MSM8998 tag from lineage's repos, with a bunch of fixes on top.​
[LG G6 ROMs, Kernels, Recoveries, & Other Developme] toto6976:
Bonjour,

avant de faire n'importe quoi, juste une question : je peux flasher directement le noyau sur ma ROM actuelle sans rien perdre ?

Rom Android 11 (red velvet cake)
[LG G6 ROMs, Kernels, Recoveries, & Other Developme] AShiningRay:
No, most A11 roms you can find on G6 are running a much older kernel that can't be swapped to 4.4 without suffering major issues.
[LG G6 ROMs, Kernels, Recoveries, & Other Developme] AShiningRay:
10/16/2023 build is up!​

Yet another release, though this one is rather small and barely counts as a new release.

Quick Summary:

More updates to the revamped Quad-DAC (V20 only, unless you got your hands on, and managed to unlock a G6 with this feature).​

DT2W is now fixed (fix found by @xc112)​

Both of these will be making their way onto lineage's official kernel soon, so stay tuned!​
[LG G6 ROMs, Kernels, Recoveries, & Other Developme] AShiningRay:
11/27/2023 build is up!​

Okay, THIS one feels like a proper BETA9:

CAF Upstream updates pulled straight from lineage's qcom_msm8998 repo while keeping wifi intact

Multiple compiler Warnings Fixed (still a few to go in some of the supported models)

Removed some useless logging

General optimizations to string routines, dcache, PM QoS and UFS

Kanged sony's vmalloc backport for improved performance at high memory usage

Some eBPF JIT commits backported to prepare for the big backport from 4.14 (Android 15 will need it apparently)

Other small fixes and adjustments on G5 and V20 (more to come especially on battery)

Note: I'll be gearing towards source and driver fixes on the upcoming builds instead of performance improvements. There's still a few things to fix on usb and power as a whole and i've been neglecting them for far too long... those are also the kind of commit that gets into Lineage's official kernel without issue.
[LG G6 ROMs, Kernels, Recoveries, & Other Developme] DJPRMF:
Just passing to say.... Thank you for keeping this device alive :)
[LG G6 ROMs, Kernels, Recoveries, & Other Developme] xc112:
is it possible to incorporate kernelsu here bro?
[LG G6 ROMs, Kernels, Recoveries, & Other Developme] AShiningRay:
Not really, at least not in the short term. KernelSU wasn't developed with those older kernels in mind, especially ones that deviate quite a bit from their original sources like ours.
[LG G6 ROMs, Kernels, Recoveries, & Other Developme] xc112:
thanks
[LG G6 ROMs, Kernels, Recoveries, & Other Developme] AShiningRay:
01/21/2024 build is up!​

And here's the build that matches Lineage-21's latest kernel state!

...it's actually housing a few improvements and fixes that didn't make their way there yet, but oh well...

Brought a few backports with fixes and improvements from linux 4.14 and newer

More CAF Upstream patches with general kernel fixes

_Even more_ warning and driver fixes (binder should be the only one spouting real warnings now, which is expected due to the partial reverts to keep IR functional)

More eBPF improvements and cherry-picks

Lineage's charge limit feature should now be working as expected, or at least close to it.

A few general improvements to memory management and logging

Due to the focus on fixing things, this one shouldn't be any faster compared to the last release, except for some very specific scenarios where one of the backports should make it almost twice as fast, but it's not something users will notice unless they specifically benchmark that backported change.
[LG G6 ROMs, Kernels, Recoveries, & Other Developme] xc112:
GitHub - LGE-G5-G6-V20/msm8996_lge_kernel

Contribute to LGE-G5-G6-V20/msm8996_lge_kernel development by creating an account on GitHub.

github.com

kernel will work for both android 13 and 14? will use on crdroid
[LG G6 ROMs, Kernels, Recoveries, & Other Developme] AShiningRay:
Should work on both... to be fair even BETA9 already worked on both.
[LG G6 ROMs, Kernels, Recoveries, & Other Developme] xc112:
ok thanks. will use your kernel as default kernel
[LG G6 ROMs, Kernels, Recoveries, & Other Developme] xc112:
i tried to use your kernel as default kernel on rom it wont compile
[LG G6 ROMs, Kernels, Recoveries, & Other Developme] AShiningRay:
02/25/2024 build is up!​

Let the backports begin!​

This build focuses on backporting some ZRAM and eBPF commits from linux 4.19 and 4.9 respectively, while also fixing wired headphone buttons.

Key Changes from BETA10:

V20 and G6 Quad-DAC drivers were updated to work with the new DAC panel debuting with Lineage 21 for LGE msm8996. (g6 won't have much use for it though, as that variant can't have its BL unlocked)

Backported ZRAM from linux 4.19, introducing general fixes and support for deduplication, allowing a bit more data to be held in memory.

Backported some ebpf commits from linux 4.9, in preparation for the big 4.19 backport which will be required for android 15.

Fixed wired headphone buttons by removing LGE code from wcd drivers.
[LG G6 ROMs, Kernels, Recoveries, & Other Developme] Hadi99:
I can't find the extreme+gaming msm8996.dtsi and msm8996-regulator.dtsi values

Can you please attach them or direct me towards the directory. I want to test the patches on stock

Edit: wrong thread
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] AShiningRay:
Don't mind me! Just reserving a post to keep tabs on this thread (just like G6's), and also because we might need to post something up here.
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] AShiningRay:
08/28/2023 build is up!​

Ayy, time for another one (although it seems i skipped one on G5 lol)... that took a while, but it's here to (kinda) celebrate the LOS 20 release! And what better way to celebrate than with a ton of changes under the hood?

Quick Summary:

We're now using Link-Time Optimization alongside the latest GCC releases, resulting in an even smaller and more optimized kernel.​

This new release now fully supports LOS 20, and that includes Bluetooth.​

It now runs on the latest MSM8998 tag from lineage's repos, with a bunch of fixes on top.​
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] cyxae:
Let’s try this ;) Thank you for your work !
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] federicous:
I am having problems with the kernel installation, instead of starting the system, it gets stuck in fastboot

I have an H850. I tested it on a LineageOS 20 and 19