[Xperia Z3 Compact Android Development] Infy_AsiX:
Same my other had no original paste either. Not in any of the three places shown in the previous.

I did the same 0.3mm copper with double sided paste and some paste to match the other two points. That dropped around 3°C. Still not as much as the around 5°C with paste on the covers. However I think some of that's causing dark patches on my screen. Though I think it's probably because this cheap ebay replacement screen I ended up with has no thin paper like cover behind the LCD like normally. May need to open it up and check it out.

After all of that I still had the charging issues I was trying to fix initially. So I tested with the battery running while outside of the frame. With the battery feeling cool to touch outside it's temperature reading still only drops several degrees to around 30°C while in use. Makes it apparent the battery temp sensor is on the board and not on the battery. Anyhow, I found charging still gets heavily throttled while cool like this. Best I can gather by watching the temperatures, CPU and charge current throttling is; when the CPU averages >60 over something like a 30 second sample time regardless of battery temp, charge current drops. Hard to reason exactly why charge current is throttled by average CPU temp but that's what I can see. Setting intellithermal <60 results in a too aggressively heavy CPU throttling.

I tried some further hardware mods. I put two small shims to physically separate the battery and back of the board. This cools both the CPU and battery ~3deg, but I suspect the battery temp reading is higher than actual as it's measuring internal temp close to the battery slot as found earlier when running externally. So the battery isn't glued in place anymore but is slightly raised and held by my phone case. I also cut out part of the plastic inside back frame to allow a quick removable battery. Using the spare broken phone as a spare removable battery charger! That was my compromise solution to not being able to charge up in even moderate usage.

Then this recent XDA article inspired me to look for a software fix. https://www.xda-developers.com/lg-v20-mod-stops-slowdown-charging/ However "/system/etc/thermal-engine.conf" is missing on my stock 6.0.1 with custom kernel. A quick google search shows it exists on other Xperia devices. Could someone on stock rom and kernel confirm?

Anyway I found a workaround fix. You can directly set the charge current with root at "/sys/class/power_supply/usb/current_system_max" for USB and "/sys/class/power_supply/qpnp-dc/current_max" for the dock port. The value for USB resets however on each replug so I make use of Tasker to customise. I don't like doing things half arsed though so I went further with Tasker to entirely customise how the phone charges. I've setup a charging voltage/percentage limit with 'trickle', charge rates by level and heat/overheat. Can also do an alarm clock based charge to full, which is more reliable than the later Sony's Qnovo schedule behaviour learning. This is going into a whole post topic in itself so I'll leave that for later. Without the hardware tweaks to thermal it seems apparent why charge throttling is so aggressive, though poorly configured by CPU temp.

Anyway to relate back to EliteKernel :p, I was getting a lot of reboots straight after bootup. I think it has something do with stock Thermald or rather it's lack of, due to it's removal and also how Mpdecision handles the situation. Kernel setting apps have a varying boot delay for applying settings and that helps to explain some of the heat up I've felt in the past. I've put my kernel settings into init.d so they take effect as soon as possible with intellithermal and thunderplug kicking in, I don't have issues anymore. This also particularly helps if you're not using the default ZRAM value. Changing via a kernel app creates a significant CPU load to decompress all ZRAM loaded since boot til app settings apply.

Also talking about Thunderplug, check out putting Sampling Rate to '500'ms in Kernel Adiutor (which is '400' in it's variable script). I think it's too aggressive sampling at 100 (0 in variable), you can see it rapidly plugging unnecessarily. After a lot of experimenting, watching and even hardware modding I'm sticking with 1574mHz max freq as it's efficient with a balance of voltage/performance. Watching current draw from two cores with 1574 max looks to use the same power while being a little faster and ready for demand compared to one at 2457 (with all cores enabled just plugged inactive). Then consider most of the time is spent at 1574 or less due to throttling anyway, even on my hardware tweaks. IMO anything to prevent heat is worth it in our heat induced design package to attempt to spare the battery life.

I know my battery's pretty dead... It's only now so long after getting it do I have the right tools and knowledge to prolong battery life. But there's no worthy upgrade device in my opinion unless the LG G6 Asian model luckily gets bootloader unlocking... So there's still a need to prolong this phone's life. If anyone's interested I can share some kernel settings, maybe the Tasker charge setup. I’ve only been using it for a week so I’m still testing it, also not sure if it's easy to share a Tasker setup. I do know of this app that allows you to set and customise a limit via Tasker plugin. However it doesn’t set the charge current, though the devs have considered it. https://xdaforums.com/android/apps-games/root-battery-charge-limit-t3557002