Having this is actually useful, because users do need to check if
they actually have a home-button:
1. Always setting this may lead to false-positive home button presses
on some models (IIRC, this has been around for a long time)
2. The home button typical is a windows logo printed on the front of
cheap windows tablets below the screen. Recently I was adding info
for yet another such cheap tablet and I asked the user to test
the home-button since the windows logo was clearly there visually.
But on this specific model touching the windows logo does not do
anything.
I vaguely remember that some users also reported Android-targeted
tablets where the surface covering the soft-touch buttons was simply an
extension of the whole touch surface, and not send any explicit key
press events.
But I may be mistaken, or it was a bug in an older driver version that
didn't support touch buttons well.
