yashsingh1/xdaforums huggingface dataset:
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] mie_ayam:
yes. indeed the vendor partition must be mounted by the kernel.

for this it may have to be edite the kernel itself.

but I've read. no way without using vendor partition.

Is it true?
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] x86cpu:
Yes, it is true. I have a way to create one though that may eventually be added.
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] mie_ayam:
waw. will be a new breakthrough for g5.

we are waiting for this.

:svetius::good:
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] AutinDroid:
Instead of re-partitioning the device (which even with a somewhat successful repartiiton nearly bricked my device), why wouldn't we try phhusson's no-vendor solution, which doesn't actually create a new vendor partition, I think it's something like a sub-partition. I'm not sure how treble will work with our 7.0 blobs though.
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] mie_ayam:
we can use an oreo costomrom vendor like lineageos.in fact we also do not have to create a vendor partition. dev samsung note 4 puts the vendor into the cache partition it also works.but the kernel must mount the chace as the vendor folder.I do not know too

---------- Post added at 05:36 PM ---------- Previous post was at 05:29 PM ----------

if not using the vendor's own partition maybe when updating rom. will bootloop. because GSI treble rom does not include vendor folder.
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] VortexHD:
Hello, I just installed this ROM along with gapps-full and magisk. I have reinstalled all my apps from a backup and have just inserted my sim card and sd card. However, the phone still says no SIM Card. I'm using an LG H850 and have installed the correct ROM.
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] suenky91:
I'm trying to install this rom but I got Error 7, how can I fix?

FIXED: I had to update the TWRP
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] mie_ayam:
Corrupt file
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] NullaVisus:
Wanted to report that I have not gotten the autorotation bug since the latest update so it either got fixed in the latest sources (or the implementation of the Qualcomm IRQ balancer) or I have just been lucky somehow
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] tiis:
I had this autorotation bug for the first time with 2018-07-20 H850 build. After a reboot it was gone again. :fingers-crossed:
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] NullaVisus:
Interesting. I've since rebooted my device at least one more time since making this post and autorotation still has never broke for me so at least for the H830 its fixed. Not sure about the other G5s though
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] x86cpu:
If auto rotate breaks for anyone, it'd be get to get a logcat before rebooting. It seems some sensors are crashing and may not restart properly. If those can be identified I can try to look into adjusting things, it's just that I have not experienced it yet.
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] NullaVisus:
I honestly can't get autorotation to break on my H830 again after grabbing the latest unofficial build. I might downgrade to get a logcat because I know on all the older unofficial builds it would break consistently upon boot forcing you to reboot until eventually it worked.

I noticed a pattern though, when the autorotation was broken on boot the clock widget would load up faster than if autorotation was actually working but correlation is not causation so not sure how helpful that is
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] pedro1977:
Try clearing cache after flashing the rom, I'm sure this cleared this and other problems up for me.
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] wolf45801:
Does the stock camera app with los 15.1 support dual back cameras if i dont replace it with google camera?
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] x86cpu:
Yes it does. The Google camera does not. There is a cstark camera mod which works well on these devices.
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] wolf45801:
Ok thank you ill be reflashing to this rom again tonight
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] wolf45801:
To flash this rom coming from fulmics on h830 i have to flash the rom then the x86 zip then the gapps? What does the x86 zip file do change the processor so it requires normal gapps and not 64bit?
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] x86cpu:
I believe fulmics is stock based. So you need to wipe your data. No need to disable the to-x86cpu.zip .. you still need 64-bit gapps.

It's listed as to-x86cpu as that's my username and I'm providing the UNOFFICIAL rom.
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] wolf45801:
Even if i have already installed a custom Rom before and disabled verfication or whatever it is
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] x86cpu:
If it is stock based you need to wipe. If lineage based, the to-x86cpu is sufficient. But I'm not sure if many other lineage 15.1 roms.
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] wolf45801:
Ok i flashed this rom before the to-x86cpu zip was made it was like a month ago or so
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] lesterp0310:
Hello, thank you so much for this ROM.

I just flashed it but I'm not able to gain root access.

I can see the option under the developer menu, but it's grayed out (disabled).

So far, I've flashed the SuperSU add-on and magisk but with no lucky. Hope you can help me.
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] mie_ayam:
U need flash magisk no superSU.
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] x86cpu:
Ok . then if you are running this LineageOS UNOFFICIAL one, you need to make sure you flash the to-x86cpu.zip once. That zip file changes the signing keys, otherwise you'll boot back to twrp. Then you can flash the latest here.
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] pedro1977:
SuperSU add-on??? Have you flashed this??

https://download.lineageos.org/extras

Either way flash it again.
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] NullaVisus:
Okay, so I reinstalled the LATEST build from scratch, as in completely clean reinstall, wiped and fully formatted, and the autorotation is breaking for me constantly. I restart maybe 5 times no hyperbole before I get it to work again and then on next restart it is again broken. I then did a clean install AGAIN and again, autorotation is still consistently broken again. I don't know how I got so lucky the first time, but regardless, here is the precious logcat that will hopefully put an end to this awful bug. The beginning was truncated for filesize reasons but hopefully this is enough info you'll need. I'm not sure how many boots was logged but the most recent had the autorotation broken while the one before that it was working

edit: moved into a .7z file because I was having issues uploading it as a .txt
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] pedro1977:
Are you sure you don't have a hardware fault??? Have you tried flashing stock20a back???
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] lesterp0310:
Thanks I resolved this after a few tries.

Yes, that one.

I finally figured out that the magisk manager app was disabled from the apps in settings. It worked fine after I went back to recovery and flashed the rom, gapps and magisk.

The rom is great, I don't have any problems with auto rotating.
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] pedro1977:
For future reference if you flash magisk and it doesn't work you simply download the manager as an APK and install it within android.

---------- Post added at 05:48 PM ---------- Previous post was at 05:46 PM ----------

For future reference, if you flash magisk and it doesn't work you simply download the manager as an APK and install it within android.
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] NullaVisus:
Its a software bug several other people have also been having with this ROM
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] pedro1977:
Although I've had sensor issues in the past they resolved themselves, (use androsensor to see which have failed, usually more than one) either after clearing all caches with twrp or flashing back to 20a and then coming back to los. If it persisting, you should try all of these in this order.
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] djskribbles:
I had it like a few builds ago but I haven't had it since. Coincidentally, it fixed itself after flashing Magisk.
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] x86cpu:
Nothing stands outs. If possible, a "logcat -b all" would help. That catches a dmesg kernel output too. Are you encrypted in this? Just curious if others have this issue and are encrypted too? (ie.. once decryption is done, certain services need to be restarted, so one or a few might be out of order on that).
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] NullaVisus:
I am not encrypted. Trying to encrypt results in a bootloop for me, even if I remove my external SD card before encrypting (to rule out maybe the SD card failing to decrypt). I am unfortunately on stock at the moment (long story short I broke my recovery partition :laugh: ) but I will do this the next time I have a chance and I'll also try installing from Magisk as others have suggested
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] x86cpu:
lineage-15.1-20180726-UNOFFICIAL

lineage-15.1-20180726-UNOFFICIAL

Updated sources.

There is a test script run, which should just output "Checking for vendor partition...". Currently, it is just testing things out. If you use adb shell while flashing it and tail -f /tmp/recovery.log, there is more output. There might be a real possibility of shrinking /system by 512Mg and creating a 512Mg /vendor partition.

AOD is disabled now.

The stock Thermal engine is still in place. This will limit QC to 1a, which screen it on. Non-QC appears to go higher if screen on. This is to minimize heat while using it.

Testing a kernel change to get rid of a lge_charging_wake_lock, which seemed to just creep up at times and cause Deep Sleep issues after hours/days... (Was days for me.)

Pending changes to merge: http://bit.ly/2OjU6s0

Again, this is signed with my keys, so if you have not flashed the to-x86cpu.zip, you need to flash that at least once coming from a build earlier than 0720. (There is no harm if you flash it again, but it is not needed). If you wipe data, the to-x86cpu.zip is not needed to be flashed.

You might notice a file in the g5 folder "recovery-twrp-rs988-2018-07-18-3.2.2-1.img". It is a rs988 TWRP recovery that works with LineageOS encryption. I may make ones for H830/H850, but have not yet.
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] djskribbles:
[MENTION=2881807]x86cpu[/MENTION], After dirty flashing your roms, I notice there's a magisk line in TWRP. Is it necessary to flash Magisk after a dirty flash?

This is what I have been doing:

-Clear cache/dalvik

-Flash file

-Flash Magisk

Do I even need to flash Magisk after a dirty flash?
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] jaggyjags:
I've seen a general thread for all treble supported devices with rom development. Do all those work on all devices with treble support and you mean is there a chance our phone might work too in the future?

Apart from that, are you aware of the weird audio glitches coming out of the headphone jack when no audio is playing on the phone? It is really loud for example when you reboot the phone, all audio artifacts come through the left audio channel. You might have missed it.

Thanks for your work!
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] pedro1977:
No you don't and clear cache last.
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] djskribbles:
Really? Devs that made roms for my old phone (Nexus 4) said to clear cache/dalvik first, then flash, but that was a while ago. Some devs recommended an optional cache clear after the flash too (which I usually do).

They also suggested to re-flash SuperSU after a dirty flash, but I guess Magisk is different?
[Samsung Galaxy S9 & S9+ Cross Device Development] zubi182:
Good work!!!! I will test it later, this is a very good idea, thanks ?
[Samsung Galaxy S9 & S9+ Cross Device Development] Noxxxious:
Pretty Good Privacy.. Why would you want all these governors with EAS scheduler
[Samsung Galaxy S9 & S9+ Cross Device Development] ASHLEY117:
Going to test on treble as it's close to stock
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
This kernel doesn't have EAS, because EAS is a major overhaul of the scheduling subsystem, making it invasive and therefore relatively high-risk.

Some other custom kernels do have it, though, so users have plenty of choice.
[Samsung Galaxy S9 & S9+ Cross Device Development] Noxxxious:
It does. Other kernels merely have it updated and/or changes to the energy model. The exynos9810 is the very first exynos to make use of EAS.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Sorry, I stand corrected. It doesn't appear to have the latest changes from r1.4 and r1.5, though. At least, I don't see the commits that the AOSP common 4.9 kernel has.
[Samsung Galaxy S9 & S9+ Cross Device Development] madhub:
[MENTION=7187684]ianmacd[/MENTION]

Thank you for your Kernel.

I got 2 questions.

How to enabled Double tap 2 wake and do you have a own thread for your magisk builds?
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
The easiest way to manage the wake gestures is with the EX Kernel Manager. It's a great front-end, and you can set up your gestures to be activated at boot.

Otherwise, as root, do the following:

# echo 1 > /sys/android_touch/doubletap2wake

Echoing a 0 would disable the gesture.

sweep2wake and sweep2sleep are configured using the same mechanism, except that the value to echo is a bit-wise AND of the values corresponding to the swipe directions you want to allow for the gesture. You'd have to pluck them from the source if you really want to know them. They can be found in drivers/input/touchscreen/wake_gestures.c. All things considered, this is why I say that EX Kernel Manager should be high on your purchase list.

As for Magisk, no, my builds don't have their own thread, but my source repo is on GitHub, along with a separate repo for the binaries built from it. I haven't yet seen the need for a second thread with unofficial builds. I didn't want to risk diverting useful postings from the existing unofficial build thread to a second one, so I just announced the launch of my builds in that thread and occasionally respond to people there.
[Samsung Galaxy S9 & S9+ Cross Device Development] Muntasir Mahmud Saif:
any plan on vibration intensity?
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Can you give some details of what you're envisaging?
[Samsung Galaxy S9 & S9+ Cross Device Development] Muntasir Mahmud Saif:
i mean on some kernels(maybe not on Samsung i guess) but on op6 and other phones there is vibration control..i mean u can increase or decrease on ex kernel manager
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
You can use EX Kernel Manager in the same way with this kernel, or you can echo a value into /sys/android_touch/vib_strength (off the top of my head).
[Samsung Galaxy S9 & S9+ Cross Device Development] saxena1:
When available for s9 960?:D
[Samsung Galaxy S9 & S9+ Cross Device Development] :
Your magisk builds are stable and they dont remove itself on restart! you should post this on the main thread!
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
I've had about 5 requests for this now, so I'll do the work and release a test build either this evening or tomorrow.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
There's nothing magical about my Magisk builds, I'm afraid. I just pull the latest code, remove anything that obviously breaks things, add one or two useful patches, build, package and release. The builds work well for me, though, and it's gratifying to read that they work well for others, too.
[Samsung Galaxy S9 & S9+ Cross Device Development] kgr:
I cant seem to see the 960 release... did I miss it?
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
No. As always, these things turn out to be slightly more complicated than at first sight, so it's taken a little longer to test and prepare things.

The release will be coming today.
[Samsung Galaxy S9 & S9+ Cross Device Development] aedificavit:
May I use latest BRI1 version on a BRI3 ROM?

Thx
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Yes, I'm using it myself with BRI3 DevBase.

There have been no stock kernel changes since BRGA, I believe, so any firmware since that version and the current one should work.
[Samsung Galaxy S9 & S9+ Cross Device Development] iampatricktan:
Hi Dev. I like this Kernel with Soldier's ROM but some times i'm experiencing freezing and need to lock and unlock my device to make it normal. Any idea? I have no issue like this with the kernels included with Soldier's Rom.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
The problem hasn't previously been reported.

Unfortunately, I don't know what type of device you are using, which version of APGK you were on, which version of the ROM you were using, or anything about what you were doing when the problem occurred.
[Samsung Galaxy S9 & S9+ Cross Device Development] iampatricktan:
Thanks for the reply. I'm using latest build of soldiers rom 8.2, also the version of apkg that the problem occured was the last two version before the latest one. I've experienced it randomly
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
I still don't even know which device you have.

I can't help without logs, preferably a kernel log and a system logcat taken at the time of a freeze.
[Samsung Galaxy S9 & S9+ Cross Device Development] iampatricktan:
Sorry I'm using S9 +. Didn't get any log from it, so sad
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 0.99.21 released.

Another maintenance release and another bug fixed in the installer's Magisk chaining code. Previously, if no versioned files were found, the installer was erroneously using the oldest generically named Magisk archive instead of the newest. Although this bug probably didn't affect a single user in the week it existed, it has now been squashed.

In addition, the installer will now prefer a generically named debug build of Magisk to a release build. This is in order to allow official canary builds to take precedence over Magisk files extracted from ROMs and other unofficial sources. If multiple debug builds are found, the one with the most recent timestamp is used. Note that Magisk files with versioned file names still take precedence over any generically named files.

Change log

Updated to upstream Linux 4.9.129.

Updated WireGuard to v0.0.20180925.

A bug fix and further improvements made to the Magisk chaining feature.
[Samsung Galaxy S9 & S9+ Cross Device Development] pixelmatt:
AFH says 'no mirrors found' :crying:
[Samsung Galaxy S9 & S9+ Cross Device Development] j1gga84:
I can second that..

Regards

Sent from my SM-G960F with Tapatalk
[Samsung Galaxy S9 & S9+ Cross Device Development] emphazer:
i confirm
[Samsung Galaxy S9 & S9+ Cross Device Development] afcaajax:
Working fine on 9.0
[Samsung Galaxy S9 & S9+ Cross Device Development] iampatricktan:
Same here, no mirrors found.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
My apologies for this. Android File Host seems to have some kind of internal problem with the file.

I have reuploaded it and verified that it is downloadable. The links have been updated.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 0.99.22 released.

This release features one further refinement to the installer's Magisk chaining code. The installer will now also look for an unversioned release build called magisk-release.zip. This is to accommodate the new release builds offered via the official Canary channel.

The precise order of precedence is now this:

Files with an explicit version in their name, e.g kantjer and ianmacd builds.

Unversioned files that indicate a release build with their name, e.g. official Canary channel release builds.

Unversioned files that indicate a debug build with their name, e.g. official Canary channel debug builds.

Unversioned files matching the pattern [Mm]agisk.zip, e.g. files extracted from ROMs, etc.

Lexical sort order is used for category 1. The timestamp of the file is used for all others. If no files are found, chaining of Magisk is abandoned.

Change log

v0.99.22 (2018-09-30)

Updated to upstream Linux 4.9.130.

Further improvements made to the installer's Magisk chaining feature.
[Samsung Galaxy S9 & S9+ Cross Device Development] aedificavit:
Download link broken?
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
5 mirrors appear for me. What do you see?
[Samsung Galaxy S9 & S9+ Cross Device Development] aedificavit:
Clicking on "posting #2" in download paragraph sends to no place...

Thx
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Cheers. It seems XDA doesn't support relative paths. Fixed now.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 0.99.23 released.

Another maintenance release, with a minor feature addition thrown in.

Change log

Updated to upstream Linux 4.9.131.

Built without process authentication code (CONFIG_FIVE_PA_FEATURE), since this doesn't work with custom kernels anyway.

LED fader timings now adjustable (via /sys/devices/virtual/sec/led/, EX Kernel Manager [>= 3.71] or MTweaks).
[Samsung Galaxy S9 & S9+ Cross Device Development] aedificavit:
Sorry newbie question: how to adjust LED fader timings with EX kernel Manager? Can't find the option.

Thx for your great work!
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
I forgot to mention that you need at least v3.71 for the parameters to appear. They are under Miscellaneous.

However, I've just inspected the code of the LED patch (a bit late now, I know) and seen that it's buggy. It does alter the LED behaviour, but won't behave as expected, which is why I didn't immediately notice the problem.

I'll have a fix for this out tomorrow.
[Samsung Galaxy S9 & S9+ Cross Device Development] aedificavit:
No problem, mate, no hurry...

Thx again!
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 0.99.24 released.

This release fixes several bugs in yesterday's too hastily added implementation of user-definable LED fader timings. No piece of code is too trivial to contain bugs, and I evidently needed reminding of that. The feature should work as expected now.

There's a reason this kernel hasn't shed its beta tag yet. We're getting there, though.

As a bonus, the WireGuard implementation has been updated to 20181006.

Change log

Bug fixes to custom LED fader timings implementation.

Updated WireGuard to v0.0.20181006.
[Samsung Galaxy S9 & S9+ Cross Device Development] iampatricktan:
Hi Dev. Just a quick question, do you have a recommended setup of EX Kernel Manager when using APGK Kernel? Thank you!