[Feature] Add some statistic info

[red7nikotin]

Problem Statement

It is necessary to add a section statistical information about the performance of this software on various devices.

Proposed Solution

Аdd it to the main page of the project as well as in the form of a documentation section

Alternatives Considered

none

Use Case

Saving time and nerves for users, as well as improving software support on various devices

Additional Context

I was only able to test the installation itself on such devices and the launch was simple with all the default settings:

Device name	Device OS version	Start default Podroid VM (qemu) 1.2.6
Sumsung Galaxy A24	One UI 8.0 / Android 16	✅
Honor Play 60 Plus	Magic OS 8.0 / Android 14	✅
Huawei nova Y72S	EMUI 14.2.0	✅
Huawei Pura 70 Pro	EMUI 14.2.0	✅

[ExTV]

Useful idea, and thank you for the four devices you already tested. Reports like that are the only way this list can exist, since I have access to two phones and a project like this runs on everything.

I want to build it around the fact that actually changes a user's experience, rather than a generic "works / does not work" column.

The one thing worth knowing per device

Podroid has two backends, and which one a device can use matters far more than any other difference:

• AVF (pKVM) is hardware accelerated. Boots in seconds, and a desktop is genuinely usable. It requires the device to report android.software.virtualization_framework, which today is mostly Pixel-class hardware.
• QEMU (TCG) is software emulation and is the fallback everywhere else. It works on any arm64 Android 8 or newer device, which is why your four devices all started with default settings, but it is much slower, and heavy GUI work is where you feel it most.

So "it launched successfully" is a good data point, and "it launched successfully on which backend" is a much better one. You can see this in the app on the Status screen, where the Backend row shows either Auto (avf) or Auto (qemu).

If you are willing to add that for your four devices, I would like to include them:

Device	Android / skin	Backend shown
Samsung Galaxy A24	One UI 8.0 / Android 16	?
Honor Play 60 Plus	Magic OS 8.0 / Android 14	?
Huawei nova Y72S	EMUI 14.2.0	?
Huawei Pura 70 Pro	EMUI 14.2.0	?

What I will not put in it

I am not going to publish performance numbers, and I would rather explain why than quietly leave them out. A boot time or a benchmark score on the QEMU backend depends on the device's single-core speed, the RAM and core count assigned to the VM, thermal state, and whether the load balancer is on. Two people with the same phone can differ by a wide margin. A table of numbers would look authoritative and mislead people into buying or avoiding hardware on bad evidence.

What is stable and worth recording per device: whether it runs, which backend it lands on, and any device-specific problem worth warning about. Those last ones are the genuinely valuable entries. There are already a few known: some Tensor G3 and G4 Pixels cannot bring up all vCPUs under AVF and fall back to fewer cores (#29), and one tablet had AVF networking fail entirely for a reason that was fixed in v1.2.6 (#43).

Format

I am inclined to keep this as a pinned issue rather than a documentation page, so anyone can add their device in a comment without opening a pull request, and so it does not go stale in a release that nobody updated. If it grows large enough to be worth curating, moving it into the docs afterwards is easy.

Leaving this open to track that. If more people post device, Android version, and the backend shown on the Status screen, the list becomes worth publishing quite quickly.

[red7nikotin]

Great.
I just suggested an idea, and it's up to you to decide exactly how and how much detail to implement it.

Yes, I read the documentation and realized that there are 2 emulation modes: AVF and qemu.

You may not have noticed, but I clearly indicated in the table that I was running everything exactly with the default settings, i.e. I kind of imagined a case that anyone would do the very first thing when installing your software. That is, they would just press all the buttons next, next, and launch to just understand how it works Whether he sees the console or not on his smartphone is the most important first experience and first impression of the program.

If the program starts and the user sees a terminal with default settings (it doesn't matter which virtualization is automatically selected there), the user will be happy and will start his experiments and will study the project, and if he fails immediately, then with a high degree of probability he will simply abandon this project and this program and will use something else (look for other solutions)

In general, I repeat once again that I used all the default settings and in fact on all my devices I saw that qemu was being used, which I indicated in my table.

If you need to conduct some experiments with running with certain parameters and collecting logs, I will be happy to help (only I will need the most detailed instructions for this)