From d61622bcde2c9abfe73beeb0f433116ef4b82338 Mon Sep 17 00:00:00 2001
From: bunnie <bunnie@kosagi.com>
Date: Wed, 30 Mar 2022 02:34:22 +0800
Subject: [PATCH] add a 1-second delay on resume before telling connection
 manager to reconnect

now that the suspender is in its own thread, we can do this safely.
It's nice to have a bit of a delay because we want other system recovery
things to take precedence and settle out before we try pinging the COM
to see how the wifi changed while we were asleep.
---
 services/net/src/connection_manager.rs | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/services/net/src/connection_manager.rs b/services/net/src/connection_manager.rs
index 09d854f2f..482aeb6cb 100644
--- a/services/net/src/connection_manager.rs
+++ b/services/net/src/connection_manager.rs
@@ -142,12 +142,14 @@ pub(crate) fn connection_manager(sid: xous::SID, activity_interval: Arc<AtomicU3
             let mut susres = susres::Susres::new(
                 Some(susres::SuspendOrder::Late), &xns,
                 0, sus_cid).expect("couldn't create suspend/resume object");
+            let tt = ticktimer_server::Ticktimer::new().unwrap();
             loop {
                 let msg = xous::receive_message(sus_server).unwrap();
                 xous::msg_scalar_unpack!(msg, token, _, _, _, {
                     // for now, nothing to do to prepare for suspend...
                     susres.suspend_until_resume(token).expect("couldn't execute suspend/resume");
                     // but on resume, kick a message to the main loop to tell it to recheck its connections!
+                    tt.sleep_ms(1000).unwrap(); // wait a full second before kicking out this message, so other services can normalize before attempting a re-connect
                     xous::send_message(main_cid,
                         Message::new_scalar(ConnectionManagerOpcode::SuspendResume.to_usize().unwrap(), 0, 0, 0, 0)
                     ).expect("couldn't send the resume message to the main thread");