Bronxteck

those values are time delays between battery polling checks. you can try voodoobatterySMC.kext that comes with slice version of HWSensors3 i am not sure if it works with Kozlec fakesmc

did you synchronize your working EFI volumes (as in both the same working version) i ask for obvious reason if efi was broken and not booting then it will still be broken

sometimes resizing and partitioning wipes EFI on the HDD but it looks like you booted to clover from the screenshot. for windows to install in UEFI mode you have to have UEFI enabled in the bios and on next boot you press F12 and select Windows UEFI installer USB. then during install you have windows delete your free volume and install to it. whatever you do do not have OSX partition it as fat because it will turn your OSX drive into a hybrid MBR which in this day and age you do not want. (involves legacy boot and an MBR patch) that might be your current booting issue.

you can try enableing HPET clover acpi patch and reboot then retest. but it sounds like you either have an injection/cache issue or HPET is gobbling up all the IRQ's

try choosing the USB from the F12 boot selection screen.

you might have to revert to a prefpane from an older OS then yours that it still worked in.

maybe something like this might work? https://itunes.apple.com/us/app/brightness-slider/id456624497?mt=12

try with this one just make sure to configure your clover drivers properly when installing as sometimes your defaults might not be what you want Clover_v2.4k_r4636.zip

have you tried editing these in clover config?

make sure you do not install the RC scripts during clover install and if you did you have to find where clover put it and remove them. the RC scripts generate NVRAM.plist. we do not need it when using aptiomemoryfix.

has it been tried with the new WEG drivers Jake? maybe it corrects that behavior

post your EFI folder you are using

did you check in energy saver pref pane and uncheck dim on battery power?

you can try adding ADP1 clover ACPI fix in clover config

did you try other DVMT settings when that happenes. like maybe retry from the lowest value till you get to setup_var 0x05

use aptiomemoryfix and remove any of the older osxfix clover efi drivers

no maybe he added a patch in the kexts he told you to test

well not only IGPU gets populated there you can add any device to that hmm looks like DVMT issue again in your IM screen shot

check again fixed the spoiler are both IGPU cause (0x14,0x0) is a different device path then (0x02,0x0) you should be able to find both devices in your ioreg

have you tried adding PNLF clover ACPI patch.

hmm sounds like your bios might not have ps2 EFI module when running in UEFI mode have you checked dell for bios update maybe they mention a correction for PS2 or you can try add the clover installer driver modules for PS2 its worth a try.

your clover might have a bug that does not boot correctly if in legacy mode. you might have to run an older version.or try this oneClover_v2.4k_r4622.zip

it says thats the ig-platform-id clover used when you ran gen-config. correct it if it is wrong you could probably add the dev-id info you are trying to emulate above on my haswell system the device properties structure looks like this maybe you can modify it and add your data too it. if there is data you are unsure of leave out that entry it also looks like you need to run the beta boot flags for those two lilu kexts for Mojave looks like they are not loading DBG) got load request from AirportBrcmFixup (113) 2018-07-26 15:49:20.220200-0400 localhost kernel[0]: (kernel) Lilu: api @ automatically disabling AirportBrcmFixup (113) on an unsupported operating system 2018-07-26 15:49:20.261569-0400 localhost kernel[0]: (kernel) Lilu: api @ (DBG) got load request from HibernationFixup (122) 2018-07-26 15:49:20.276245-0400 localhost kernel[0]: (kernel) Lilu: api @ automatically disabling HibernationFixup (122) on an unsupported operating system

what patch is that?can you post it?

<key>PciRoot(0x0)/Pci(0x2,0x0)</key> <dict> <key>AAPL,ig-platform-id</key> <data> AAAWWQ== </data> <key>framebuffer-con0-enable</key> <data> AQAAAA== </data> <key>framebuffer-con0-flags</key> <data> kAAAAA== </data> <key>framebuffer-patch-enable</key> <data> AQAAAA== </data> </dict> </dict> AAAWWQ== EQUALS 00001659 is that correct?