When given the chance, I'll try to fix xdroid dreaded framerate bug again

Speaking of xdroid btw, I did 2 builds, each with a different approach to fix
Will try them later, if the dreaded framerate bug is gone, I'll release the one that worked

https://t.me/vbaloboto
Channel is public now

And neither worked
I have officially given up on Xdroid
It's a tree issue and there's not much I can do for now
RIP 😔

[LINK_DEAD]
Original ROM release
Changed:-
ROM is converted to RO Ext4!
Nuked addon.d and install-recovery.sh
Disabled native bridge (build.prop modified)
Replaced default emojis font with twemoji (source)
Removed BCR and Viper4Android
[Experiment] Updated LeciaCam to 5.0 (source)
cherish good cooked rom sar no bugs no issues

Why converted to ext4?

I tried so many different configs to keep it as is EROFS but none worked as either of the scenarios happen:
A. ROM fails to flash in recovery
B. Successful flash but then boots into fastboot + recovery unable to mount any partition (with /data being the exception)
So I had no choice but to convert to Ext4, and atlas, it successfully flashed + boots with no issue regarding partition mounting or decrypting data in recovery
I'll try again later to cook again as EROFS
RO however seems to be side-effect/leftover from converting EROFS, I'll look into why that happened

Why uploaded to Mega and not AFH?

AndroidFileHost seems to have issues at the moment, and I don't want to upload somewhere else like sourceforge, so I opted to upload on Mega instead

There's a bug on LeciaCam 5.0 where zooming is not working and all pictures are captured at 1.0x zoom regardless of how much you zoomed in (ultrawide 0.6x is unaffected)
There are 3 solutions
A.(System is not RW unfortunately) Downgrade back to LeciaCam 4.7 that came with ROM, I'll do a tutorial+share LeciaCam 4.7 that came with ROM
B. Use Gcam for the meantime
C. Ignore if you're most of the time just taking pictures in 1.0x zoom anyways and/or crop the picture in editor
D. Flash original ROM release instead
UPDATE: https://t.me/vbaloboto/59

I will fix it as soon as possible

Expect new update for vb.Cherish, especially regarding LeciaCam and EROFS (if possible)

Should I try CarbonROM with experimental props changes? Like change lineage props
I'd try, but cherish is currently making me lazy

Also pre-include gapps and vendor too

UnmoveD has fixed the zoom bug on LeciaCam,
For EROFS I'll take the "let MIO generate install script" approach
[vb.Cherish]

Bug: Supermoon and Fastshot are currently not working.

Doesn't matter/not important anyways, since I suspect sweet doesn't even have support for those features, but I'll let it be known

I have also taken the make super image route alongside too

If that approach to have EROFS fails, then I'm not going to bother with cherish anymore and just move on to supex
Do not expect an ext4 build

SUCCESSFUL FLASH AND BOOT! No issues over at recovery too!
Can dirty flash over previous build with no issues too

[LINK_DEAD]
Original ROM release
Changed:-
Same as the previous release +
ROM is finally EROFS (you can dirty flash over previous ext4 one)
Updated LeicaCam to 5.0 (zoombug fixed) (source)
cherish good cooked rom sar no bugs no issues

After reading into the Chinese texts on the install script that MIO Kitchen generated, it offers the user through the volume buttons on whether it should proceed with the installation even if the device is incorrect.
In this case, sweetin users should try to select vol down button (I think so, if it aborts then try the other) when it brings up the warning that the ROM is for sweet and the device is sweetin