Identical to my first experience.
You release an untested ROM (now marked as “broken”) divested-16.0-20200510-dos-klte.
When a device doesn’t boot at all
On the S3 it works fine and smooth so far, but the S5 starts new again and again after a few seconds of booting.
When a device doesn’t boot at all you have to make an engineering build and get a full logcat.
It is likely the deblobber.
Same command from above is helpful:
abd logcat -b all -d | grep -i -e dlopen -e .so
It can also be selinux, so I recommend making the eng build with selinux disabled.
In the device makefile you can append androidboot.selinux=permissive.
If you can’t make a build, I will try to make one soonish.
It is not uncommon for bugs to be in a build. But nine weeks after the initial release asking the user to do an “engineering build” when the device does not boot is a new negative experience for me and leaves a bitter taste in my mouth. Is DivestOS (DOS) intended for advanced users or developers - and not for the normal user who wants to use a custom rom like LineageOS?
If a working Lineage 16.0 serves as a basis for DOS, but this is changed, then the developer should also call the device his own to be able to control his work personally in advance.
It is unfortunately a frequently encountered bad habit to deliver untested software to the interested user to let the product mature at the customer - keyword banana-software / bananaware.
Your DivestOS premiere fell into the water for me. But DOS get a second chance if it is repaired as soon as possible.