ui: update text on unlock jade screen
What the developer wrote
Authored by Daniel Newton
ui: update text on unlock jade screen
What changed, and why it matters
This commit only changes user-facing text labels and removes an unused function parameter. The home screen button text changes from 'Unlock Jade' to 'Ready', and the connection screen now says 'Ready to Pair' with updated instructions. There is no security-relevant code change.
No security action needed. Treat as a routine UI/UX wording update.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The patch is a pure UI string refactor in two C files. It changes the label of the locked-state home menu item and the body/header text of the connect activity. It also updates make_connect_activity() to take no arguments and removes the now-unused device_name parameter and its JADE_ASSERT. No logic, cryptography, authentication, memory handling, or network behavior is modified.
Changed components
main/process/dashboard.cmain/ui/dashboard.cInspect captured patch +6 / −8
diff --git a/main/process/dashboard.c b/main/process/dashboard.c
index a503657..4003085 100644
--- a/main/process/dashboard.c
+++ b/main/process/dashboard.c
@@ -91,7 +91,7 @@ static const home_menu_item_t home_menu_items[HOME_SCREEN_TYPE_NUM_STATES][NUM_H
{ .symbol = "3", .text = "Options", .btn_id = BTN_SETTINGS } },
// Initialised/Locked
- { { .symbol = "5", .text = "Unlock Jade", .btn_id = BTN_CONNECT },
+ { { .symbol = "5", .text = "Ready", .btn_id = BTN_CONNECT },
#ifdef CONFIG_HAS_CAMERA
{ .symbol = "2", .text = "QR Mode", .btn_id = BTN_QR_MODE },
#endif
@@ -166,7 +166,7 @@ gui_activity_t* make_home_screen_activity(const char* device_name, const char* f
gui_view_node_t** status_text, gui_view_node_t** label);
// Temporary screens while connecting
-gui_activity_t* make_connect_activity(const char* device_name);
+gui_activity_t* make_connect_activity(void);
gui_activity_t* make_connect_to_activity(const char* device_name, jade_msg_source_t initialisation_source);
// GUI screens
@@ -2782,7 +2782,7 @@ void dashboard_process(void* process_ptr)
act_dashboard, GUI_BUTTON_EVENT, ESP_EVENT_ANY_ID, sync_wait_event_handler, event_data);
} else {
JADE_LOGI("User navigated to 'connect' screen");
- act_dashboard = make_connect_activity(device_name);
+ act_dashboard = make_connect_activity();
gui_activity_register_event(
act_dashboard, GUI_BUTTON_EVENT, ESP_EVENT_ANY_ID, sync_wait_event_handler, event_data);
}
diff --git a/main/ui/dashboard.c b/main/ui/dashboard.c
index 182ca2e..b637cfb 100644
--- a/main/ui/dashboard.c
+++ b/main/ui/dashboard.c
@@ -113,17 +113,15 @@ gui_activity_t* make_home_screen_activity(const char* device_name, const char* f
return act;
}
-gui_activity_t* make_connect_activity(const char* device_name)
+gui_activity_t* make_connect_activity(void)
{
- JADE_ASSERT(device_name);
-
btn_data_t hdrbtns[] = { { .txt = "=", .font = JADE_SYMBOLS_16x16_FONT, .ev_id = BTN_CONNECT_BACK },
{ .txt = "?", .font = GUI_TITLE_FONT, .ev_id = BTN_CONNECT_HELP } };
const char* message[]
- = { "Connect via USB/BLE", "to a companion app", "and select your Jade to", "unlock with your PIN" };
+ = { "Open your wallet app.", "If needed, the app", "will prompt you to", "connect via USB/BLE." };
- return make_show_message_activity(message, 4, device_name, hdrbtns, 2, NULL, 0);
+ return make_show_message_activity(message, 4, "Ready to Pair", hdrbtns, 2, NULL, 0);
}
gui_activity_t* make_connect_to_activity(const char* device_name, const jade_msg_source_t initialisation_source)
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.