Schedule retry after connectivity timeout instead of giving up

When WiFi connectivity times out after 30s, the device would show an
error and stop — no alarm was scheduled for the next cycle. This meant
the device sat idle indefinitely until the user manually tapped "Next".

Now calls scheduleNextCycle() after the timeout so the device will
wake and retry on its normal refresh interval, matching the behavior
of other fetch error paths.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: mf-lit

src/com/bpmct/trmnl_nook_simple_touch/DisplayActivity.java

@@ -453,14 +453,15 @@ public void run() {
                 logD("Ensure you are connected to WiFi. Press the home button and go into settings to configure.");
                 cancelConnectivityWait();
                 if (showErrorInMenu) {
-                    a.showMenuStatus("Couldn't connect. Tap Next to retry.", true);
+                    a.showMenuStatus("Couldn't connect. Will retry next cycle.", true);
                 } else {
-                    if (a.contentView != null) a.contentView.setText("Couldn't connect. Tap Next to retry.");
+                    if (a.contentView != null) a.contentView.setText("Couldn't connect. Will retry next cycle.");
                     if (a.contentScroll != null) a.contentScroll.setVisibility(View.VISIBLE);
                     if (a.imageView != null) a.imageView.setVisibility(View.GONE);
                     if (a.logView != null) a.logView.setVisibility(View.VISIBLE);
                     a.forceFullRefresh();
                 }
+                a.scheduleNextCycle();
             }
         };
         refreshHandler.postDelayed(pendingConnectivityTimeoutRunnable, CONNECTIVITY_MAX_WAIT_MS);