Request for Vendor Blobs / Vendor Tree Information for Custom ROM Development for Redmi A5 Serenity

Hello Xiaomi Open Source / Development Team,

I hope you are doing well.

I am an independent Android enthusiast and beginner custom ROM developer, currently working on improving compatibility and stability for AOSP/GSI-based ROMs on the Redmi A5.

At the moment, while GSI-based systems can boot and run, there are several hardware-related issues (such as input stability, UI performance, and HAL behavior) that clearly originate from vendor-level incompatibilities. These issues significantly limit the possibility of developing a stable and fully functional custom ROM for this device.

I understand and fully respect that many vendor components (HALs, firmware, proprietary drivers) are closed-source and not covered by GPL. I am not demanding or legally asserting access to proprietary source code.

However, I would like to kindly ask whether any of the following could be made available or documented for development purposes:

Vendor blobs (or a reference vendor image suitable for custom ROM development)

Vendor tree or partial vendor configuration references

Hardware abstraction layer compatibility notes

Any documentation regarding vendor–system interface expectations for this device

Even partial information, documentation, or guidance would be extremely valuable to developers who want to improve software support and long-term usability for Redmi A5 users.

The goal here is not to bypass security or proprietary protections, but to enable:

Better hardware compatibility

Improved stability

Reduced bugs in AOSP-based and custom ROM environments

Xiaomi has historically been supportive of the Android developer community, and many devices have benefited greatly from that openness. I genuinely believe that providing limited vendor-level guidance (where possible) would significantly help developers and users alike.

Thank you very much for your time and consideration.
Any response, clarification, or direction would be greatly appreciated.

Kind regards,
A custom ROM developer & Android enthusiast

No files, tests, or entry points are named. Start by reviewing the requested vendor blobs, vendor tree references, HAL compatibility notes, and vendor–system interface documentation; done would require a concrete response or published development material.