I plugged my pi in to my switch for ethernet connectivity, but the UI appears to be only accessible when on the Pi's wifi network. The UI is looking for 9.9.0.1 as the host. Would be nice if the resources loaded by the webpage were relative to the initial page. aka the LAN IP on my network.

The initial webpage loads fine, but the web socket connection fails. The UI reads a message "Virtual touchscreen not available. Wait for Android to boot up."

Originally in https://github.com/tesla-android/issue-tracker/issues/109

Tangential to #8, when I was setting up my accounts from desktop browser, I had to manually key in my generated passwords 🫠

I thought it might be nice to capture the at least paste event and send it over the web socket to trigger an Android paste. Copy would be nice too, but I'm not quite sure that's necessary.

The app and canvaskit is already served directly from the Raspberry Pi over the local network, however something is fetching resources from the internet on the first run. While this is happening the user sees a white page(for up to a minute, T-Mobile LTE in the US) in the car and thinks that something is not working. The issue will appear on every first run of a new version of the frontend

Action points:

1. Modify web/index.html in order to make it look exactly the same as SplashPage.
2. Profile the flutter app in release version and monitor all the external network requests from any flutter plugins. Try to serve the dependencies locally by either forking the libs or injecting required assets in the release process using GitHub Actions.