Since Android 17 SDK has been released and is now listed in Android Studio

Android 17 is probably coming out soon

Probably, not sure, just a hunch

HiOS vs XOS in a nutshell

Never assume you're smarter than the custom ROM maintainers and devs.

If they tell you to never use Ofox or any custom recovery, then don't use those, ONLY USE AOSP RECOVERY.

Especially on modern vendor_boot devices

And obligatory:

https://cyberknight777.dev/posts/2025/12/why-no-twrp-on-modern-devices/

During my initial backport of reflex

Apparently, I forgot the trace_android_vh_map_util_freq vendor hook from android's schedutil and we're using desktop linux's resolve_freq logic, which caused SODs on some devices

https://github.com/MillenniumOSS/android_kernel_common_android12-5.10/commit/2ba2d0f786723ebdaafaae0c0787fbb76212b3c3

I bet the pickers didn't notice that

This fix will land in Chihiro v2.1 and Yuuka v4.1 respectively

Terms of the Peace Accord for Builders/Porters

Updated: 2026/06/13

Lead Dev: Shirayuki39

ROMs built with MillenniumOSS Device Trees rules

1. You MUST ship Yuuka/Chihiro Kernel, nothing else
2. You MUST remove Chrome, PlayAutoInstallConfig, YouTube, YTMusic(If exists) before building any ROM that includes GAPPS by Default
3. You MUST NOT release QPRs or major android releases until I say it's ready and release the first batch
4. You MUST NOT build any roms that I already maintain

- YAAP
- AxionOS - especially this as this is Officially maintained

5. You MUST NOT make any changes in the device trees apart from adaptations to whatever ROM you are building for.
6. You MUST NOT try to compare between the work you do and the work I do
7. You MUST NOT make any snide comments about MillenniumTeam Members, at all times.
8. You MUST NOT include TranssionCamera support if it's a direct fork of my trees
9. You MUST build the ROMs as erofs
10. You MUST NOT support OrangeFox/TWRP and any obsolete recoveries
11. You MUST NOT use any AI-generated code in device trees or kernel
12. You MUST only ship and support AOSP/LineageOS recovery
13. You MUST NOT ship overclock or anything that can cause permanent hardware damage(i.e Disable Thermal)

Appended for any porters using Custom ROM vendor for custom ROM ports(i.e porting a custom rom like Infinity X from another device)
- Porters are allowed to use the Custom ROM kernel and vendor.
- Porters are not allowed to change the kernel
- Porters MUST USE KagamiChihiro Kernel(or HayaseYuuka if LG8n)

* These rules only apply to any devices that the lead specifically maintains like LG8n, LG7n, LH7n, X678B, CK7n

* These rules also apply to dropped devices (i.e CK7n, X678B)

* It's up to the other Core Members(SEMINAR) that maintain some devices(i.e S666LN, tanzanite) if they were to enforce these rules

Finally, Chihiro v2.1 and Yuuka v4.1 can be built

And of course, as usual, a YAAP update follows a kernel update

And as usual, more bugfixes for reflex backport

Also, no BORE since BORE didn't make that much of a difference with Reflex anyways

Also, BORE kinda nukes battery life

So Yuuka/Chihiro will not add bore

#ROM #LunarisAOSP #Baklava #S666LN #X6881 #X6880 #GRTeam #CKTeam #YMuwaniTeam
LunarisAOSP | UNOFFICIAL | For Itel RS4/Infinix HOT 50 Pro/Pro + | Android 16 QPR2
Released: 10/5/2026

▪️S666LN

Vanilla | GApps

▪️X6881

Vanilla | GApps

▪️X6880

Vanilla | GApps

▪️Screenshots

Changelogs:
• Updated to 3.10
• X6880: follow changes based on X6881 tree
• fix SoFOD on X6880/1


Known issues:
• U tell me (gib logs or gtfo)

Notes:
• Signed build.
• 64-bit only ROM
• SELinux is enforcing.
• Please make sure that you made IMEI backup, you are on right recovery and right firmware version.

Credits:
• Thx to fjrXTR for tree base
• Thx to LineageOS devs, shirayuki39 for reference Commits.
• Thx to shirayuki39 for kernel
• Thx to All donated and support me!

☕️ Donate (liked our work? buy us a coffee!)
• Here

By @KimelaZPrjkt
Follow @ItelRS4Updates | @GR_Logs | @YMuwaniTeam | @Circle_Kendel @MillenniumUpdates
Join @itel_rs4 | @HOT50Series