[Xperia Z5 Compact Android Development] torukk:
Hi,I don't uderstand what you mean? It can be cleanly uninstalled by just restoring previous twrp backup of boot partition. What this zip only do, is that if flash new boot.img partition (yeah, apart of copying few aptx bt libraries and wireless firmware), so dirty flashing the rom would uninstall it as well, but it is not necessary if you have backup of boot partition. I don't understand how you get bootloop.

---------- Post added at 12:09 PM ---------- Previous post was at 11:57 AM ----------

@TheVan28 I've read about your issues, you must have screwed up something. If you need microg version, I can provide you my personal LOS build from december, I'm also microg user: https://mega.nz/#!kp1UiIKI!bWOl7op0xGZnNFy4B89mumpBvIwC5tlBEl2ZKosjkNs

---------- Post added at 12:16 PM ---------- Previous post was at 12:09 PM ----------

I've also wanted to update everyone:

Unfortunatelly, I've run into some issues with the kernel developent. As you should probably realized already, the kernel reboots every 4 days in average (at least in my case, can be sometimes 2 days, then 5 days, and so on). I've been hunting this bug for last month, but without success. I've now described in in more detail here in this https://xdaforums.com/showpost.php?p=78815700&postcount=803 if you are more interested, but to be honest, I don't think this can be fixed, so I've abandoned this kernel, and reverted all changes to the point before I've started importing from green kernel.

After my last update here, I've imported sdcardfs (not filesystem but kernel driver replacement for fuse emulated access layer over sdcard and internal emulated sdcard, I think this is default in oreo), I'm also using f2fs on /data at least for a month without any issues. Additionally, not a kernel, but I can also confirm aptx bluetooth codec is working with my new aptx enabled headphones, I've also found and added 64bit aptx libraries (but this should be kept outside of zip with kernel, I'm doing it just now for convenience and lack of time).

After reverting changes, I've synchronized first with kernel sources from repo google-common for 3.10 (sdcardfs), then angler (nexus 6p, also msm8994 and kernel compatible with oreo), then I'm cherry-picking from green kernel only relatively closed parts/areas of code like drivers and not touching kernel core subsystems (to be more specific: crypto modules and algorithms updates, minor update of wireless driver and firmware, rcu, mmc updates, lots of small fixes and improvements). For more potentially breaking stuff, I'll need to cherry-pick some closely related updates (of max 50-100 commits), then wait at least 7 days to be sure kernel is stable and not reboots, but with this speed, it can take many months.

More bad news, with this kernel, I got currently stuck on 2 problems:

- from angler, there were rather significant changes in audio driver, which causes speaker volume to drop 50% (it does not apply for wired or bluetooth speaker/headphones), it means that when I put all sliders in sound settings on max, its like 50% of original volume level (btw which I find to be over the limit by 20% because its too loud on maximum setting and distorted, not sure if this is safe for so small phone speaker bin in my opinion). I hope this is related to settings in mixer_paths.xml and can be solved here, which I'm planning to try, because otherwise, audio changes are really huge and I don't want to revert them all.

- I have some application captune from sennheiser (for my headphones), which crash the kernel. id doesnt with previousr kernel, nor in aiplaine mode, because it happend during the app initialization when it tries to detect DLNA sources on network using multicast, this causes kernel stuck and watchdog reboot. not a big problem because I can use and prefer another player, but still this should be fixed

So, I don't want to import more changes before above problems will be solved, I'll see what can be done with above problems.

---------- Post added at 01:09 PM ---------- Previous post was at 12:16 PM ----------

@TheVan28 another idea: if you didn't uninstalled gapps before flashing microg rom, this might be source of your problem, but dirty flashing Berni's non-microg rom must solve it