I've also switched to flattened APEX for alioth on next test build, and thus require proper clean flash unless you can navigate yourself to /data/apex, delete it and hope for magic to happen

New #alioth test build:
*> [platform] Based on v5.1.3, same platform changes as grus with addition of:
*> [platform] Added special runtime permission group patches from GrapheneOS
*> Killed updatable APEX support


This is an untested build, since I'll have to clean flash :/

Please test WFD on the upcoming #grus build

#grus: Presenting the near-release build

Oh, btw

I won't immediately move to Android 12 once it's out, since I need to have devices running stable platforms for a while

Acdb shit fixed for actual release

I have merged LA.UM.8.6.2.c1-00800-89xx.0 into msm-4.9 kernel fork, however you need to revert this pre-production commit otherwise battery temperature will always be reported as 25°C which is not cool.

FOR FUCKS SAKE CAF STOP PUSHING YOUR TESTING COMMITS TO RELEASE TAG WITHOUT REVERTING THEM

I forgot I posted this on wrong channel, but anyways, I won't delete this message

#grus: Last 5.1.3-based test build before moving to 5.2 codebase

#grus: Let this trigger the fire

Introducing a (not really) TWRP build based on Android 10 sources, but well, I forgot to exclude logging facilities from this build


Actual TWRP build = as soon as declared stable
k4.14 based (compatible with k4.19 ROMs), don't flash in combination with k4.4 ROMs

Just a random SHRP build that you can probably ignore if my unofficial TWRP build works for you all and don't want anything extra.

I did a great job breaking decryption on my own ROM, so anyone please test if decryption works on ROM you're using. #grus