fw/apps/prf/recovery_first_use: do not change pairability on mobile event

gmarull · gmarull · commit 9cae0a89243f · 2025-06-16T17:01:03.000+02:00
A mobile event may not signify a BLE disconnection, so pairability,
discoverability cannot be adjusted if disconnection doesn't happen
first. A true disconnection will happen later if PPoGATT fails to
keep connection alive, and so such settings change will be handled
by then.

Signed-off-by: Gerard Marull-Paretas &lt;gerard@teslabs.com&gt;
diff --git a/src/fw/apps/prf_apps/recovery_first_use_app/recovery_first_use_app.c b/src/fw/apps/prf_apps/recovery_first_use_app/recovery_first_use_app.c
@@ -399,9 +399,6 @@ static void prv_pebble_mobile_app_event_handler(PebbleEvent *event, void *contex
   }
 
   const bool is_connected = event->bluetooth.comm_session_event.is_open;
-  // When the Pebble app is connected, to being discoverable / pairable. We do this to avoid
-  // stressing out the BT controller during the FW update with discoverability advertisements, etc.
-  prv_allow_pairing(s_fu_app_data, !is_connected);
 
   s_fu_app_data->is_pebble_mobile_app_connected = event->bluetooth.comm_session_event.is_open;
   if (is_connected) {

Original file line number	Diff line number	Diff line change
`@@ -399,9 +399,6 @@ static void prv_pebble_mobile_app_event_handler(PebbleEvent event, void contex`
`399`	`399`	`}`
`400`	`400`
`401`	`401`	`const bool is_connected = event->bluetooth.comm_session_event.is_open;`
`402`		`- // When the Pebble app is connected, to being discoverable / pairable. We do this to avoid`
`403`		`- // stressing out the BT controller during the FW update with discoverability advertisements, etc.`
`404`		`- prv_allow_pairing(s_fu_app_data, !is_connected);`
`405`	`402`
`406`	`403`	`s_fu_app_data->is_pebble_mobile_app_connected = event->bluetooth.comm_session_event.is_open;`
`407`	`404`	`if (is_connected) {`