Hi,
This mailing list is focused on Android WebView development, but it sounds like your question is actually regarding the google chrome browser. I'm actually somewhat familiar with the Chrome dino game codebase though, so I'll try to help.
I think the Chrome dino game is configured based on touch input when on mobile devices and keyboard input when on desktop devices. From what you've written, it sounds like we actually might have this part configured correctly for your device: you mentioned that hitting the navigation key starts the game. As for the unwanted mouse pointer, I'm not sure if that's something under our control. I don't think chrome ever generates its own mouse cursor—that's probably something which your phone's operating system is drawing by itself. I'm not super familiar with how Android works for feature phones though, so I could be mistaken about this.
Unfortunately, I don't think this is something we would be able to fix in the game itself. But if you're technically inclined, you are welcome to look at the open source code for the dino game. The code is publicly available at
https://source.chromium.org/chromium/chromium/src/+/main:components/neterror/resources/dino_game/. I believe "offline.ts" in that folder is the specific code file which has the game logic, including the code which handles keyboard and input events. On the off-chance that you do see specific code which is drawing a mouse cursor, let me know and I'll pass this feedback along to the engineering team who maintains the dino game.