Yes, an experience topic would probably be useful, but I do not see how android version (if at all) is usefull, and/or why rom version or hardware used would even have an impact.
For useful data we would need to know the device OS and the client used, and recognize it could be Win10 or Win7 with desktop Outlook 20013 and up as well as Android or iOS or even cloud-based interfaces like Google.
On the server side the used groupware as well as its exact config would be required. Including but not limited to the used authentication back-end, and how the user-account-fields are populated (eg: mail field)
Given that scope it almost requires a dedicated team with different configs who test identical scenario’s in a meticulous way, While I am open to that idea, I am already overpromissing on guides … so do not see how to make it happen myself.
Maybe we could create a test-procedure, and ask people to fill out the relevant fields. otoh, that seems like a lot of work to discover that different clients just implement the same protocol in a different way, and all are equally valid, and thus there is no easy fix for this issue.