I have some experience on this and could make an article if you are interested.

The key is to have downstream sources and be very very conservative with the AI, slowly build step by step.

You also have to know C and have a spider sense of what's acceptable or not.

Another key is to ask for approval before editing any source with a patch of what it intends to do. This way you can judge what it wants to do and ask for a double check of the patch. Go quality over quantity.

This isn't web frontend with Tailwind, you have to be very strict and somewhat knowledgeable. Nobody can use AI to write kernel code without some good low level and engineering knowledge.

I’d be interested in that.

I completely agree, this is not the place to let AI blindly edit kernel code. The useful approach is to use it conservatively: understand the error, compare against downstream sources, propose a small patch, review it, test it, and then move one step further.

I’d be happy to work together on an article or guidance document, where to start, how to approach debugging, what to never let AI touch blindly, and how to build confidence step by step. That could help others avoid a lot of mistakes and maybe give a second chance to other devices.

Please do write an article! I've wanted to get into reusing old android hardware for quite some time now, but never knew where to look for good instructions to get started. Especially PostmarketOS seems very interesting, but rather underdocumented in some places.

Interested!