Driver station crash on startup - possible race condition

[acharraggi]

There are some reports from the field that the Driver Station, or Driver Hub will crash on startup, but on restart be fine.

REV sent us a log:

08-29 10:39:50.036  1310  1341 E AndroidRuntime: android.view.ViewRootImpl$CalledFromWrongThreadException: Only the original thread that created a view hierarchy can touch its views.
08-29 10:39:50.036  1310  1341 E AndroidRuntime: 	at android.view.ViewRootImpl.checkThread(ViewRootImpl.java:8372)
08-29 10:39:50.036  1310  1341 E AndroidRuntime: 	at android.view.ViewRootImpl.focusableViewAvailable(ViewRootImpl.java:4273)
08-29 10:39:50.036  1310  1341 E AndroidRuntime: 	at android.view.ViewGroup.focusableViewAvailable(ViewGroup.java:940)
08-29 10:39:50.036  1310  1341 E AndroidRuntime: 	at android.view.ViewGroup.focusableViewAvailable(ViewGroup.java:940)
08-29 10:39:50.036  1310  1341 E AndroidRuntime: 	at android.view.ViewGroup.focusableViewAvailable(ViewGroup.java:940)
08-29 10:39:50.036  1310  1341 E AndroidRuntime: 	at android.view.ViewGroup.focusableViewAvailable(ViewGroup.java:940)
08-29 10:39:50.036  1310  1341 E AndroidRuntime: 	at android.view.ViewGroup.focusableViewAvailable(ViewGroup.java:940)
08-29 10:39:50.036  1310  1341 E AndroidRuntime: 	at android.view.ViewGroup.focusableViewAvailable(ViewGroup.java:940)
08-29 10:39:50.036  1310  1341 E AndroidRuntime: 	at android.view.ViewGroup.focusableViewAvailable(ViewGroup.java:940)
08-29 10:39:50.036  1310  1341 E AndroidRuntime: 	at android.view.View.setFlags(View.java:15732)
08-29 10:39:50.036  1310  1341 E AndroidRuntime: 	at android.view.View.setVisibility(View.java:11372)
08-29 10:39:50.036  1310  1341 E AndroidRuntime: 	at android.widget.ImageView.setVisibility(ImageView.java:1685)
08-29 10:39:50.036  1310  1341 E AndroidRuntime: 	at com.qualcomm.ftcdriverstation.FtcDriverStationActivity.testDriverStationRobotMismatch(FtcDriverStationActivity.java:1765)
08-29 10:39:50.036  1310  1341 E AndroidRuntime: 	at com.qualcomm.ftcdriverstation.FtcDriverStationActivity.onNetworkConnectionEvent(FtcDriverStationActivity.java:1686)
08-29 10:39:50.036  1310  1341 E AndroidRuntime: 	at org.firstinspires.ftc.robotcore.internal.network.NetworkConnectionHandler$NetworkConnectionCallbackChainer.onNetworkConnectionEvent(NetworkConnectionHandler.java:707)
08-29 10:39:50.036  1310  1341 E AndroidRuntime: 	at com.qualcomm.robotcore.wifi.NetworkConnection.sendEvent(NetworkConnection.java:186)
08-29 10:39:50.036  1310  1341 E AndroidRuntime: 	at com.qualcomm.robotcore.wifi.DriverStationAccessPointAssistant.onWiFiNetworkConnected(DriverStationAccessPointAssistant.java:427)
08-29 10:39:50.036  1310  1341 E AndroidRuntime: 	at com.qualcomm.robotcore.wifi.DriverStationAccessPointAssistant$2.onAvailable(DriverStationAccessPointAssistant.java:147)
08-29 10:39:50.036  1310  1341 E AndroidRuntime: 	at android.net.ConnectivityManager$NetworkCallback.onAvailable(ConnectivityManager.java:3256)
08-29 10:39:50.036  1310  1341 E AndroidRuntime: 	at android.net.ConnectivityManager$CallbackHandler.handleMessage(ConnectivityManager.java:3474)
08-29 10:39:50.036  1310  1341 E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:107)
08-29 10:39:50.036  1310  1341 E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:214)
08-29 10:39:50.036  1310  1341 E AndroidRuntime: 	at android.os.HandlerThread.run(HandlerThread.java:67)
08-29 10:39:50.095  1310  1310 V DriverStation: Lifecycle onPause() : bb28929
08-29 10:39:50.142  1310  1341 I Process : Sending signal. PID: 1310 SIG: 9

This is because the code that checks device names for team number mismatches is not running on the Android UI thread.

A work around is to keep trying until the driver station starts properly. Then change the robot and driver station names to match.
https://ftc-docs.firstinspires.org/en/latest/programming_resources/shared/managing_smartphone_ds/Managing-a-Smartphone-Driver-Station.html?highlight=device+names

This will be fixed in the 11.1 release expected in January.

[texasdiaz]

As an aside, there is a recommended process to help the Driver Station start properly:

1. Turn off your robot and your Driver Station device (e.g., Driver Hub).
2. Turn on the Driver Station device (e.g., Driver Hub).
3. Log in to the Driver Station device, this may/should auto-launch the Driver Station App.
4. If the Driver Station App crashes, disable Wi-Fi on the Driver Station device and restart the Driver Station App. Disabling the Wi-Fi on the Driver Station device might be required if the Wi-Fi is connecting/connected to a venue connection and not the robot.
5. Once the Driver Station App has loaded, turn on your robot.
6. After 30-45 seconds, the robot will be ready to pair with the Driver Station. If you previously disabled the Wi-Fi on the Driver Station device, re-enable the Wi-Fi on the Driver Station device at this time.
7. Connect the Driver Station to the robot.
8. Update the Driver Station name.
9. Update the Robot Controller network name.
10. Reconnect the Driver Station to the Robot.
11. Celebrate Success!