Recent content by SpiritCroc

I'd go for option 2.

I have been busy recently, but I plan to provide further updates. Maybe I can do a new build in the next couple of weeks. There hasn't been much work on Android 10 though, since the team focuses on Android 11 currently. While I have already been compiling Android 11 for other devices, I'd like...

Are you sure there was L1? I thought it was only possible to get L3 for custom ROMs, and it looks to me like AICP 15 has the same drm lib included like CarbonROM on Oreo - but I'm no widevine expert.

15 is still being built, 14 is not supported officially anymore. 15 is stable enough for me, but I can't speak for "regular" users - best to try out yourself. I don't know what the requirements for dualrecovery are. Usually, when no recovery works, I just flash the full ROM using fastboot. If...

Right, for stock rom, you need a different recovery. If I remember correctly, I used this one back then: https://forum.xda-developers.com/showthread.php?t=2794175 Any particular reason why you chose AICP 14 over AICP 15?

I see. Probably won't change for AICP 15.0, since most team members focus on Android 11 currently. I think I have heard this is the same on stock ROM since Android 10, so not sure if I can do anything here. Is this possible on stock ROM? If the device does not have hardware support for this...

Great to hear you like it :) 1. As old.splatterhand told you already, it still needs permissive mode for selinux right now. We have a setting for that in Aicp Extras/System behaviour, which might be useful. 2. Go to AICP Extras/Navigation/On-screen navigation for long press and double tap...

I can't remember having face unlock in AICP, was this maybe included in your gapps? Either way, AICP won't add it (unless you find a good open source way maybe...), since a few ROMs already had their code being taken down because they used proprietary libraries without permission, if I recall...

There were reports from sony z1 compact users who experienced the same (both on AICP and LineageOS), but to be honest, I don't even know how to debug this right now

I see I made a mistake in the flashing instruction, sorry! Glad you figured it out :)

I don't think I have seen any FBE backported to old devices like ours yet

Hm, I think I experienced this once or twice in the past too (back on Android 9?), haven't found out why this happens yet, unfortunately

So you flashed the old build (20200425_1435)? That one might need older firmware (around 52.1.A.0.672). For the newest AICP build (20200731_1348), you need the new firmware (52.1.A.3.49) and the new instructions.

These are working for me. Have you flashed the latest stock ROM (52.1.A.3.49) to both slots before flashing latest AICP?

I uploaded a new build. I have not tested a dirty flash this time, so I recommend to do a full backup to external storage in case something goes wrong if you try to upgrade from the previous AICP build (otherwise, you need a clean flash either way). This time, it's a flashable zip (instead of...