Docs: expand DEVICE-SUPPORT.md with a community results table

[molotovgit]

docs/DEVICE-SUPPORT.md should grow into a table of confirmed devices: model, SoC/GPU, Android version, and what works (boot / skirmish / campaign / audio / cutscenes / controls).

Good first issue — take results people post in the device compatibility discussion and turn them into a maintained table. No device or C++ needed.

[Ayush-0918]

Hi! I'd like to work on this issue if it's available.

My plan is to collect the confirmed compatibility reports from the discussion and organize them into a clear, easy-to-maintain table in docs/DEVICE-SUPPORT.md, while keeping the format consistent and easy for future contributors to update.

Could you please assign it to me? Thanks!

[molotovgit]

Go ahead, it's yours — assigned.

Here's what I'd aim for. The raw material lives in the device compatibility discussion (#4): that's where people post their results, and it already has a rough reporting template (device, SoC/GPU, Android version, how far it got, rendering/audio/cutscenes, notes). The task is basically to take those free-form reports and normalize them into a table in docs/DEVICE-SUPPORT.md that stays readable as it grows.

For columns I'd go with something like: Device | SoC / GPU | Android | Status (boot / menu / skirmish / campaign) | Rendering | Audio | Notes. The GPU column is the one that really matters — most of the porting differences are per-GPU (Adreno vs Mali vs PowerVR vs Xclipse behave differently at the shader/swapchain level), so keeping SoC+GPU explicit is what makes the table actually useful to the next person trying to figure out whether their phone will work. Keep the formatting dead simple so future contributors can append a row without reflowing the whole thing.

One practical note: DEVICE-SUPPORT.md is pretty thin right now, so don't feel like you need to invent data — just structure what's actually been reported and leave the table ready to extend. If a report is ambiguous (someone says "works" but doesn't mention their GPU or how far they got), it's fine to leave cells blank or add a short note rather than guessing.

Only hard rule on the repo is no game files in a PR (.big/.bik/maps) — won't come up here since it's pure docs, just flagging it so it's never a surprise. There's a short CONTRIBUTING.md for the rest. Open a PR whenever, and ask here if anything about the sources or the format is unclear.

[Ayush-0918]

Hi @molotovgit,

I checked the device compatibility discussion (#4), but it currently doesn't contain any community device reports yet—only the reporting template.

Since the issue is intended to organize confirmed reports into a maintained table, I'll wait until there are actual submissions to avoid adding placeholder or fabricated data.

Please let me know if you'd instead like me to prepare the table structure with an empty "Community Compatibility Results" section for future reports.