[LG G6 ROMs, Kernels, Recoveries, & Other Developme] Eliminater74:
Nah thats ok, you do enough as it is, and you dont need to go through all that.. I know that I only added Oreo media/audio and sensors, most likely the sensors are the issue....

I will revert that back.. Wont make a new build of rom just yet.. because the only dif is the media/audio and sensors blobs, other then that its the same rom.. so stick with prev beta..........

I know this goes against my nature, but I ported over HTC Debugging Tools, with custom changes for my self and my Kernel, because LG has a crap way of using ramoops and debugging.

its lousy really. HTC has a custom way, that when I was on HTC, it almost next to always told me why something didnt boot or whatever...... Heck a friend on the HTC even ported a 4.4 Kernel to the msm8996.

using the logs that the HTC debugging tools told him.. and im tired of LG not showing me enough nfo on issues.. it takes to much time to track down reasons...

So I ported that over. and made some changes.. and now my ramoops looks more professional.. on top of many other things I can log now.......

Once I get past the BS part, I will disable all debugging on FULL Final stable builds of kernel..............

But this is really for my own personal so I can figure out what the deal is with bootloops or not booting or whatever............

Funny because I hate debugging crap and thinks it slows things down. but in this case.. The debugging doesnt even work unless I turn it on in defconfig.....

its very min, and I manually picked out what I wanted and aported it over..

Also increased the size for ramoops so more nfo pulls in for me.. now I can see everything from bootloader and on...........

im still trying to figure out the bootloader log....... LG's old method, doesnt log very well if you never make it to boot animation.....

so if your stuck at the LG logo, chances are ramoops will be empty or not complete with the info needed...........

But with the new custom one I added, it should now store all info.. I cant be sure if bootloader logs will work.. cause there is a magic number, which im pretty sure it has to do with bootloader locations and all

in memory.. as LG might be dif.. and not sure on figuring out LG's.. but I could be wrong and it works............

Here is a small example of my ramoops using a controlled kernel panic:

[ 0.228075] cpu-clock-8996 6400000.qcom,cpu-clock-8996: resources init failed
[ 0.260065] msm_watchdog 9830000.qcom,wdt: wdog absent resource not present
[ 0.260375] msm_watchdog 9830000.qcom,wdt: MSM Watchdog Initialized
[ 0.268944] spmi_pmic_arb 400f000.qcom,spmi: PMIC Arb Version-2 0x20010000
[ 0.270364] spmi_pmic_arb 400f000.qcom,spmi: missing property: qcom,pmic-arb-max-periph-interrupts
[ 0.275954] platform 9300000.qcom,lpass: assigned reserved memory node peripheral_region@8e900000
[ 0.276257] platform ce0000.qcom,venus: assigned reserved memory node peripheral_region@8e900000
[ 0.276581] platform 1c00000.qcom,ssc: assigned reserved memory node peripheral_region@8e900000
[ 0.277015] platform 2080000.qcom,mss: assigned reserved memory node modem_region@88800000
[ 0.279585] msm-thermal 70000.qcom,msm-thermal: probe_vdd_mx:Failed reading node=/soc/qcom,msm-thermal, key=qcom,mx-restriction-temp. KTM continues
[ 0.279661] msm-thermal 70000.qcom,msm-thermal: probe_vdd_rstr:Failed reading node=/soc/qcom,msm-thermal, key=qcom,max-freq-level. err=-517. KTM continues
[ 0.284673] platform soc:qcom,msm-adsprpc-mem: assigned reserved memory node adsp_region
[ 0.284899] platform soc:qcom,msm-mdsprpc-mem: assigned reserved memory node adsp_region
[ 0.289291] msm_cache_erp64 6500000.qcom,cache_erp64: Registering for L1 error interrupts
[ 0.289394] msm_cache_erp64 6500000.qcom,cache_erp64: Registering for L2 error interrupts
[ 0.289557] msm_cache_erp64 6500000.qcom,cache_erp64: Registering for L3 error interrupts
[ 0.289823] msm_m4m_erp 9a40000.qcom,m4m_erp64: Registering for M4M error interrupts

That log shows info before the original init.. you see at the top where it says: [ 0.228075] cpu-clock-8996 6400000.qcom,cpu-clock-8996: resources init failed,

That is on the msm8996pro.dtsi where the silvercores are screwed up so that the max 2.1 never stable...

and fmax only registered 19 freq's when table shows 20, with 19 missing.. so fmax reverts back to 18 which is the 1.5 .......

That was the mistake I kinda found by mistake..

Here is another nice little error:

2.865096] diag: Unable to initialize POOL_MDM_DCI_WRITE mempool, itemsize: 0 poolsize: 0
[ 2.882189] ------------[ cut here ]------------
[ 2.885873] WARNING: CPU: 2 PID: 1 at ../drivers/gpio/gpiolib.c:68 gpio_to_desc+0x40/0x4c()
[ 2.894122] invalid GPIO -517
[ 2.897070] Modules linked in:
[ 2.900446] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 3.18.113-Nebula_2019~-g6f0ba77d395 #1
[ 2.908430] Hardware name: Qualcomm Technologies, Inc. MSM 8996pro v1.1 + PMI8996 MTP (DT)
[ 2.916680] Call trace:
[ 2.919118] [<ffffffc000207810>] dump_backtrace+0x0/0x254
[ 2.924491] [<ffffffc000207808>] show_stack+0x14/0x1c
[ 2.929531] [<ffffffc0004d628c>] __dump_stack+0x20/0x28
[ 2.934733] [<ffffffc0004d6248>] dump_stack+0x60/0x84
[ 2.939772] [<ffffffc000222dd8>] warn_slowpath_common+0xa4/0xe8
[ 2.945671] [<ffffffc000222d10>] warn_slowpath_fmt+0x50/0x74
[ 2.951314] [<ffffffc00050c958>] gpio_to_desc+0x40/0x4c
[ 2.956532] [<ffffffc0006ac4f4>] register_smp2p+0x70/0x94
[ 2.961905] [<ffffffc001834538>] rdbg_init+0x19c/0x33c
[ 2.967027] [<ffffffc000200a10>] do_one_initcall+0xf8/0x1b0
[ 2.972593] [<ffffffc001800bc8>] kernel_init_freeable+0x198/0x228
[ 2.978666] [<ffffffc000f20a08>] kernel_init+0x10/0xf4
[ 2.983798] ---[ end trace d8abc8a73ed4113f ]---

So now you can see why I added that.. to help in future development..