Sport Master 0.5.154 Colleague test guide

Basic activity recording is free. AI coaching, intelligent training planning and cloud companion features require a verified, active paid membership; invitation rewards and ordinary PRO do not include paid AI. Payment, third-party AI data permission and EverMe authorization are separate choices. Shengwang real-time voice is not enabled. This page does not offer purchases or automatic renewal.

Update 154: the home screen now proactively asks for separate TianDiTu map permission; existing permission does not need repeated confirmation. After location access is allowed, the phone's real position identifies the city for route browsing, while a city selected manually is retained. If location or city lookup is unavailable, choose a city manually; a default city is not presented as a GPS result. Software checks do not establish outdoor GPS or physical-device acceptance.

Prioritize these checks: the map-permission prompt appears on first entering home; declining still allows normal app use; after location permission, the route city matches the current position; a manual city choice is retained. With location disabled, offline conditions or an unsuccessful city lookup, manual city selection must remain available without pretending a fix was obtained.

Priority checks for 151: clearer maps and cadence from real phone sensors

Start with these four checks, then use MAP1–MAP4 for the map basics. Test only in safe conditions with the necessary equipment, and mark each item Pass / Issue / Not tested.

BEAUTY1 Route visibility: on an online Tianditu map, check the orange main route with white casing, green start and orange finish. A blue current-location marker must appear only after a real location is received. Public routes remain red and local routes blue; their meaning must stay distinct.

BEAUTY2 Controls and gestures: check prompts, zoom and close buttons on the route home, drawing and fullscreen maps. With larger phone text, labels and buttons must remain fully visible. The route home must show only one copy of the same consent prompt, and the surrounding page must not take over dragging or pinch-to-zoom.

BEAUTY3 Real basemaps and sharing: open maps from route drawing, an older activity and poster preview. Check road names, route placement, separate track segments and Back. A grid or illustration must not impersonate a loaded basemap; missing connectivity or consent must be reported accurately. Sport Master’s post-activity shared-video export can still be tested separately.

CADENCE1 Cadence without a watch: after allowing activity recognition, walk or run normally in a safe setting and check whether the phone obtains real cadence. Pausing must stop accumulation. With no usable step sensor, no permission or no valid samples yet, show unavailable rather than inventing cadence from GPS speed.

These are device checks to perform, not a pass report. Software rendering, a consent dialog or successful installation does not establish outdoor GPS, sensor or glasses behavior. Official Rokid AI App recording is deferred this round.

Historical regression: checks introduced in 148

  1. Me → Settings & About → About → Registration and public information: Back, official lookup and privacy links should work. Unverified reference numbers must not be invented or displayed as verified.
  2. Read the initial consent notice. AI, maps and analytics are managed separately. Disable and unregister notifications under messages and training reminders.
  3. Website/ADB installations should continue to open website updates. Real Xiaomi/OPPO store installations should open the matching store; an app that is not listed does not count as success. Record the actual prompt rather than repeatedly installing differently signed builds.

This is a checklist of tests to perform. Software checks or local screenshots do not replace phone, glasses or store acceptance.

Tianditu basics regression (MAP1–MAP4); MAP5 deferred

Unified domestic Rokid phone test app. Record actual device results for the map checks below; official Rokid AI App recording is outside this round’s test scope.

  1. MAP1 Separate consent: On first opening a route map, choose Not now; existing records and other features should remain. Then allow maps under Settings & About → Tianditu service consent and view again. Revoking consent should clear the current online basemap and stop further requests. Allowing it again must not start an activity for you.
  2. MAP2 Route and activity maps: Open one of your routes and an older activity record. Check the real map, route bounds, separate track segments and photo points. Dragging and pinch-to-zoom must not be taken over by the surrounding page. Do not join unrecorded gaps into a false track.
  3. MAP3 Journey sharing and offline maps: Open Share this journey from an activity record; Back should return to that record. Geotagged photos should mark only their actual locations. Going offline must not be reported as a successful load. Usable offline maps you have already imported should still work with their existing configuration.
  4. MAP4 Existing account and four languages: After updating in place, check that your account, records and route names remain. Select Chinese, Japanese, English and French to view map descriptions, Back and consent buttons. Signing in to another account you own must not expose the previous account's private routes or delayed callbacks.
  5. MAP5 Official Rokid recording: deferred At the user’s request, official Rokid AI App recording is not being handled or requested for testing this round. Sport Master’s post-activity shared-video export may still be tested separately; it is a different feature.

Shared videos continue to use a track background drawn from this session's GPS, not a street map. An overseas Google Maps edition is not included in this public installer.

Priority this round: four languages and AI coach

This is a colleague test checklist to perform, not a passing test report. Prioritize LANG1–LANG8. Mark “Not tested” if the required voices, equipment or glasses are unavailable.

  1. LANG1 Selection and persistence: On the login page or under Settings & About → App language, choose 中文, 日本語, English and Français in turn. Closing and reopening should retain your selection. Follow system should use a supported system language and fall back to English for unsupported languages, without switching your account or units.
  2. LANG2 Screens and large text: View Home, Me, Devices, Settings, height/weight selectors and activity records. Use large system text to check Back, Next and Confirm. Text must not be clipped or pushed off-screen; sliders and precise input must retain the values you actually selected.
  3. LANG3 New coach conversations: Ask a routine training question in the selected language, then view a training draft or calendar. New answers, states and explanations of reliable data should match that language. Missing heart rate, distance or profile data must still be described as unknown. No formal sessions should be created before you choose Adopt. You need not adopt an unsuitable plan to test it.
  4. LANG4 Speech capabilities: Test one question and answer if the phone already has recognition and read-aloud engines for the language. Missing language resources should produce a clear notice or retain text. Japanese and French depend primarily on actual local capabilities; Chinese/English cloud speech support must not be described as four-language support. Report actual audio and recognition based on phone testing.
  5. LANG5 Glasses text: With compatible, connected Rokid glasses, check that the HUD sport, units, available data and pause state match the phone. Changing language alone must not change distance, time or data source. Without glasses, mark Not tested; phone screenshots do not replace lens display checks.
  6. LANG6 Indoor data: With a trainer or rower, check its entry, instructions for formal exercise or the 90-second experience, stages and data labels. Device totals and averages should reflect actual responses; zero, missing and expired data must remain distinct. Do not set unsuitable resistance just for testing.
  7. LANG7 Confirmations and safety information: Read update, permission, AI consent, save and delete prompts. Buttons and descriptions should be understandable. Switching language must not grant consent, adopt plans, publish results or delete records for you. Actual deletion is not required for testing.
  8. LANG8 Original text and feedback: Route names, nicknames, old chats and historical analyses may retain their original language; do not claim they were regenerated in translation. Check that the account, old records and units remain unchanged. Feedback should include language, phone version, page and steps, with phone numbers, verification codes and private content hidden.

Existing standard heart-rate broadcasting, rowing details, pursuit, music, games and sharing remain. Revisit the older checks below when conditions allow.

Retained entertainment and device features (NEW1–NEW11, optional)

144 highlights: more measured rower data

  1. Connect your rower and open Device totals and averages at the bottom of the preparation page. Stroke count, device timer, resistance, calories and averages should appear only when reported. Unsupported fields show “—”; valid zeros remain zero.
  2. Enter formal rowing and the 90-second experience separately, row continuously, and compare pace, power and newly added session distance on phone and glasses. Existing machine mileage is only the session baseline; machine elapsed time must not be presented as the current session's duration.
  3. Stopping, disconnecting or expired data must not leave old values displayed as current. After recovery, check new readings; unknown distance from an interruption must not be added back.
  4. Existing standard heart-rate broadcasting remains a fallback when the main machine lacks heart rate. Report the exact equipment model, phone version, formal activity or 90-second experience, and phone/glasses behavior. Passing historical replay checks does not establish current physical equipment or optical acceptance.

143 highlights: experience distance and heart-rate broadcasting during exercise

  1. First select your own standard Bluetooth heart-rate device under Me → Devices & platforms → Receive heart-rate broadcast. In formal indoor exercise or the 90-second experience, phone and glasses should show the same valid fallback heart rate when the main equipment has none.
  2. Turn off broadcasting on the selected device, then enable it after the activity starts. Without ending or restarting the activity, it should recover after the current bounded retries and cooldown. Fresh main-equipment heart rate takes priority; fallback is used only when main heart rate is missing. Removing a device, disconnecting or expired samples must not keep old readings displayed.
  3. During real pedaling or rowing in the 90-second experience, forest, river, galaxy and rowing RPG scenes should show meters added during this experience. If equipment distance is unavailable, distance may be estimated from real speed/pace and labeled accordingly. Unknown remains “—”. Pausing, backgrounding or interruptions must not backfill progress, and no formal activity record is saved.
  4. For on-site feedback, include phone version, equipment and heart-rate device models, formal activity or 90-second experience, phone screenshots and what was actually seen in the glasses. Software checks and public downloads do not establish real broadcasting or lens acceptance.

142 highlights: simpler indoor HUD

  1. With fresh stationary data, trainer and rower entertainment / 90-second experiences no longer repeat descriptions such as “Live demo · Not recorded” or “Resting”. Measured power, cadence/stroke rate, time and missing-data values must remain correct.
  2. Explicit pause, disconnection and expired data still need essential notices. Removing text must not make scenes advance, score or generate bullets on their own.
  3. Compare actual phone and glasses images item by item. Software checks cover rower river / galaxy / RPG scenes; real rowing and lens optics still require actual testing, not a public test installer as a substitute.

141 highlights: full-screen scenes, rear-view rowing and foreground HUD

  1. Enter trainer/rower entertainment or the 90-second experience. Forest/river/galaxy should fill the background, with the player seen from behind and three simulated rivals sharing the same scene, without an extra small track overlay. Instruments, tasks and Stop stay in the foreground, clear and usable.
  2. Real motion drives the scene: advance only when new valid cycling or rowing data arrives. Hold position when stopped, paused or interrupted; page refreshes alone must not add points. Fields not reported by the equipment remain unknown.
  3. With Rokid, check scenes and foreground data on the effective 480×352 HUD canvas. Moving from a basic HUD to entertainment/demo may cause one brief reconnect. While voice or photography is busy, retain the embedded image first; repeated exits or reconnects are not acceptable. Outdoor routes keep their original layout. Without equipment, mark Not tested; a software preview is not lens acceptance.
  4. For rowing RPG, also test auto-aim and energy shots. Actual strokes trigger the corresponding shooting, and faster strokes should affect firing rate. Power or speed changes alone must not invent extra strokes or shots. Phone and glasses should use the same game state.
  5. In trainer forest or galaxy themes, check that the road extends to the bottom of the screen and remains visible behind data overlays. Check the rowing scenes similarly. Other sports pages should keep their existing layouts.
  6. Pedal or row gently on real equipment. Phone scenes and glasses should follow fresh motion data. If one channel reads 0, other valid power, cadence/stroke-rate or equipment-speed data may still drive the image. With only power or speed available, rowing RPG must not invent strokes or fire shots.
  7. Stopping, pausing, disconnecting or expired data must not backfill game rewards. Motion should resume promptly when you move again; the first fresh sample re-establishes the baseline, and the next advances it. The glasses no longer display “Not advancing”, using short natural status text instead.
  8. Switch routes to Hangzhou: five sports each have 3 new routes, with simpler names such as Heart Loop, Phoenix Route and Squirrel Route. Actual track segments and sources are preserved.
  9. Connect real equipment and keep the 90-second experience page in the foreground for at least 11 minutes. Even when stationary, it should continue to show the actual connection and fresh zeros instead of becoming disconnected through a preparation timeout. Leaving the experience page must not end another formal activity.
  10. Connect a real trainer or rower before entering its 90-second exhibition experience. Before connection, show a waiting state; unknown power, speed, cadence or stroke rate must remain “—”, without sample numbers appearing by themselves.
  11. Start the 90-second experience, pedal or row, and check phone readings, scenes and virtual pursuit. Stopping, pausing, disconnecting or switching apps must not continue progress. Returning requires explicit Resume and must not backfill progress while away.
  12. After connecting and authorizing Rokid, view the phone's glasses diagnostics, then personally confirm the green scene and matching live readings in the glasses. Report connection, display opening and image-upload acknowledgement separately; report an ACK with no visible image too.
  13. In formal indoor entertainment sessions, check forest, river and galaxy themes. Simulated rivals, auto-aim and game state should match the phone. The phone performs the calculations; glasses do not score independently.
  14. The 90-second experience does not create activity records or automatically send resistance or start/stop commands. It must not take over or end an existing formal activity.
  15. Music and effects switches, coach audio priority, stopped-rowing prompts and themed formal-session results remain as optional checks. Actual glasses visibility, sustained connection and equipment experience require real hardware acceptance.

Retained features and optional regression checks follow

This page covers the 0.5.154 (version code 184) unified Rokid phone test app. First update in place and check your existing account, records and device settings, then mark “Pass / Issue / Not tested” below. Prioritize BEAUTY1–BEAUTY3 and CADENCE1 above, then MAP1–MAP4; MAP5 is deferred; use LANG1–LANG8 for language feedback. Entertainment, device and other checklists below cover retained features and are optional when conditions allow.

Download this round's unified phone test app · 18.50 MiB (19,393,784 bytes).Installation instructions and full SHA-256 checksum

View this APK's SHA-256cfa47d159ede77d78e3040902ed8acf0c09cee1bfdc27f34f3d5d1ec932d415a

Login note:If sending an SMS reports temporary unavailability, retain the exact notice and report it rather than repeatedly tapping Send. Use the existing-account or temporary-experience entries actually available on the page. Do not uninstall or clear data to troubleshoot login. Never post verification codes, authorization links or private chats in a group.

Demo and real exercise are separate:The 90-second exhibition experience uses only fresh, real data connected for this session, with missing values shown as “—”. It does not save exercise results or automatically send resistance or target-power controls to equipment. This is a checklist for colleagues to perform, not a passing report for physical equipment, glasses, watches or sound.

IDHow to testWhat to expect / What to report
NEW1 Icon and login brandingAfter updating in place, check the launcher icon and open login/registration. If possible, increase system text size.The character should be clear and complete, not clipped by the icon edges. Login uses the same brand character, with readable text and buttons. Showing the character does not mean you are logged in or connected to any device.
NEW2 Four onboarding pagesView onboarding through normal first use. If an existing account does not show it again, do not clear data to repeat it; mark Not tested.The brand character and route, glasses, coach and other icons should be clear. Page text and bottom actions must be readable and scrollable. Existing consent order remains; changing pages must not authorize anything for you.
NEW3 Height and weight bottom sheetsDuring body-profile onboarding, open height or weight selection and move the scale and slider. Cancel once, then enter a valid precise value of your own and confirm, preserving decimals if your original profile has them.The bottom sheet previews values live. Cancel or exit must keep the original value; Confirm fills it in, and final saving follows the original flow. Height range: 100–250 cm; weight: 30–200 kg. Slider steps must not silently round a precise decimal you entered. Empty values must not be replaced by defaults; invalid input should show a message rather than crash.
NEW4 Scrolling MeOpen Me, scroll up and down, switch to another page and return. Check your account and existing records.The endless top refresh spinner should be gone. Scrolling should work normally, retaining the existing account, records and normal loading states. Loading and network errors should show appropriate notices, without turning unknown data into 0.
NEW5 Next-week drafts for four sportsSwitch among running, cycling, hiking and trail running. Generate next week's draft using your real availability; review it, then make one adjustment. You may test your usual sport first and mark the rest Not tested.The draft should include this sport's schedule, training evidence and full units, without getting stuck on “Missing server training evidence”. Missing information should be explained. Generation or adjustment is not adoption; only your confirmation puts it in the formal schedule, without crossing into another sport.
NEW6 Trainer 90-second exhibitionWith a usable connection on the trainer device page and no activity recording, enter the separate exhibition demo. Choose forest or galaxy before explicitly starting. Try pause, return after switching apps, replay and exit once each.The 90 seconds continuously combine supply, overtaking and pursuit highlights, with the themed background and real equipment instruments visible together rather than three separate level pages. Only fresh real movement data drives progress. Pausing/switching apps must not advance secretly; returning requires Resume. Replay retains the chosen theme. No activity record is created and equipment resistance is not adjusted.
NEW7 Rower 90-second exhibitionEnter the rower exhibition under the same conditions and view river and galaxy themes. Without usable equipment, mark Not tested.The boat, buoys/starlight, overtaking and splash/energy effects should flow continuously. Pace uses per 500 meters and stroke rate uses spm. Virtual effects remain separate from real measurements. Missing valid personal heart rate shows “—”, and experience results are not saved.
NEW8 Formal indoor instrumentsConnect your compatible trainer or rower and start formal manual, dynamic or entertainment training through the existing flow. View data in the default and galaxy themes; if possible, also check a small screen, large text and landscape orientation.Forest/river/galaxy fills the background, while foreground main instruments, power, cadence or stroke rate, heart rate, duration and session distance remain clear. Pause and End must work. Use only valid sources for this session; real 0 and “—” stay distinct, with no invented unsupported fields. Target power, virtual scene progress and actual results must not be conflated.
NEW9 Natural stopping and recoveryOnly during safe normal use, briefly stop pedaling or rowing, then resume a comfortable rhythm. You need not turn off Bluetooth or deliberately create faults. Record whether the equipment was still coasting or had stopped.Coach and scenes should distinguish moving, coasting, resting, recovering and expired data. They must not keep urging “Keep pushing” after you stop exerting, or treat all coasting as disconnection. Recovery prompts should match the current state, without expired playback or a barrage of messages.
NEW10 Original outdoor interfaceSwitch back to outdoor running or cycling and view preparation, existing records, routes and data. A comfortable activity following your original plan is sufficient.No forest, river or galaxy indoor instruments should remain. Original outdoor records, maps and sport identity stay intact; indoor distance must not become GPS results. Without outdoor location conditions, test pages only and note that limitation.
NEW11 Indoor coach and voiceIf you wish, enable proactive indoor voice prompts. Once safely stationary, ask the voice coach “What stage am I in, and which current readings are actual measurements?” Then turn off optional prompt sounds.Text answers, stage prompts and current equipment should agree, clearly distinguishing virtual events from real data. Missing speech engines, microphone permission, network or service should be explained. Captions do not prove actual audio playback. After optional prompts are disabled, old content must not keep playing; stop and recovery messages must not conflict.

Formal entertainment still uses 3-minute stages in a three-stage, 9-minute loop; gentle dynamic training remains 55 minutes. The 90 seconds are only for the separate exhibition demo and do not change formal courses. Without the equipment, authorization or voice service, write Not tested; no purchases or dangerous scenarios are needed.

Retained features and optional regression checks

Older device, AI, route and account regression checklists remain below. Existing fixes are not all new this round. For this round’s additions, use BEAUTY1–BEAUTY3 and CADENCE1 above; NEW1–NEW11 are historical regression checks only. Mark Not tested when conditions are unavailable.

Retained feature: four new icons and direct hiking entry

Hiking, trail running, city roaming and indoor training use fuller sports silhouettes. Running and cycling artwork is unchanged; the four icons appear on both selection cards and activity entries.

  1. Open sport selection from Me and check the six sports and selected colors. With larger text, icons and labels must not overlap.
  2. Tapping Hiking should select hiking directly, without a Mountaineering or Citywalk submenu. Activity preparation and pre-training planning should no longer show Hiking / Mountaineering / Citywalk buttons.
  3. City roaming retains its separate card and must not become hiking. After changing sports, check that pages, routes and records match that sport.
  4. If Mountaineering was selected in the older version, upgrading while idle should select Hiking. Existing mountaineering records retain their original identity; an older active session must not change sport mid-session. You need not create an old session to test this.
  5. This round's phone installation and interface checks do not replace real exercise, heart-rate, glasses or equipment acceptance. Report under actual conditions; without the corresponding equipment, mark Not tested.

Retained feature: clearer device branding

Devices and sports platforms now include Huawei, Xiaomi, Garmin, Suunto, COROS, Apple, Rokid, Wahoo and KingSmith logos. Images ship with the app instead of depending on temporary URLs. Wahoo is a trainer reference brand; KingSmith is a rower reference brand. A logo does not mean connected, authorized or compatible with every model.

  1. Open Devices & sports platforms. Check that brand images, names and connection states are clear and that images do not cover text on small screens or with large text.
  2. Enter indoor trainer and rower pages. Check that reference brands and actual device names are shown separately. Without a connection, the state must remain Not connected; a logo must not imply success.
  3. Use the original flow to connect or authorize your supported equipment. Check that existing buttons and descriptions still work. Without equipment, mark Not tested; this logo update does not replace physical compatibility acceptance.

Retained features: update prompts and app-switch recovery

This is still the same unified Rokid phone test app and can update an older build with the same package name directly, without uninstalling. Fixes for checking on every opening and restoring unanswered prompts after app switching remain. No prompt is normal when 0.5.154 is already the latest online version. Do not downgrade yourself just for testing; development has checked a controlled higher-version response. Indoor trainer and rower dynamic training, three-stage loops, proactive voice and Q&A remain. Follow this round's specific checks below; actual sound and equipment behavior depend on colleague testing.

  1. After updating in place, first check your original account, activity records, routes and device authorizations. Do not uninstall the old app or clear data to bypass issues.
  2. Complete login, consent and onboarding normally to reach Home. No update prompt should appear for the same version, and failed background requests must not block use. A later higher website version should offer “Update now” and “Maybe next time”. Choosing the latter suppresses repetition in the current foreground session; reopening after backgrounding should check again. With no button selected, the prompt must still await a choice after app switching, rotation or system page restoration. Back or tapping outside must not dismiss it. Do not interrupt activity recording.
  3. Under Settings & About, view consent information and local open-source licenses. Check scrolling, Back and readability on small screens and with large text. Decide personally whether to authorize.
  4. Choose AI coach, route, trainer and rower checks below according to your conditions. Record the actual version, phone model and issue screenshots. Without the equipment, mark “Not tested”.

This round provides a website test download. Software and interface checks do not replace physical equipment, Rokid, Garmin, outdoor location or actual audio acceptance. It is not yet on Google Play.

Retained features: coach voice and disabling prompt sounds

Retains compatibility fixes for some newer Android phones unable to find speech recognition or playback services, and fixes an indoor prompt continuing after prompt sounds are disabled. The phone still needs an available speech engine and Chinese resources. This software fix does not establish physical audio acceptance.

  1. Enter indoor trainer or rower mode, choose dynamic training or challenge mode, enable coach prompts, and record whether stage reminders can be heard.
  2. Disable prompt sounds while one is playing. The current optional indoor prompt should stop immediately instead of reading to the end. This switch must not forcibly interrupt user Q&A or independent safety alerts.
  3. On the activity page, tap the voice coach, choose whether to allow the microphone, ask a current training question and compare recognized text, response and audio. If there is no speech engine, no Chinese resources or a service failure, record the page notice rather than passing silent output.

Focused regression: indoor rower, separate connection and records

The native phone Bluetooth FTMS rower entry remains separate from outdoor running and trainers, without using phone GPS for indoor distance. Without compatible equipment, write “No equipment, not tested”.

  1. From sport selection in Me, enter Indoor training, choose Rower, then search and explicitly select your own machine. A Bluetooth name or Connected label alone does not mean rowing data has arrived.
  2. After starting, check stroke rate (spm), pace per 500 meters, distance, power and available heart rate. Missing readings show “—”; only a real zero shows 0. Do not substitute cycling cadence or pace per kilometer.
  3. Adjust resistance or target power slightly only when the equipment actually declares support, reports a valid range and grants control. Do not show confirmation before a successful machine response. Rowing has no cycling incline control. Interface confirmation does not replace actual mechanical response.
  4. During normal use, check pause, resume, reconnect and save. Pausing must not accumulate results; resuming must not double-count prior distance or strokes. Reopened records remain rowing records, and unknown distance stays unknown. Do not deliberately create faults just for testing.
  5. With Rokid glasses, compare stroke rate, pace, distance, time, heart rate and measured power. Power should share the phone's source this round. Missing data stays unknown; target power must not be shown as measured power. Record background, locked-screen and sustained-display results separately.

Scope this round:Vendor-specific protocols outside standard FTMS, USB and ANT+ machines are outside this round's scope. Specific models, firmware, measurement accuracy and mechanical resistance response have not had physical acceptance. Rowing does not yet offer watch activity synchronization or AI coach scheduling. Watch and trainer controls below apply only to the matching sport. Test rowing proactive voice and Q&A under this round's indoor checks; speech support does not imply rowing AI scheduling is enabled.

Retained feature: phone Bluetooth trainer connection, separate from outdoor cycling

A dedicated indoor trainer entry was added in 0.5.122 and remains in this version, initially targeting Wahoo KICKR ROLLR. The phone searches, selects and connects directly before indoor cycling starts, with a separate control page available during exercise. Existing accounts, activity records, routes and EverMe authorization carry over. Update in place without uninstalling the older version first.

  1. Select Cycling in Me, then open Indoor trainer · Bluetooth connection & control on the preparation page. Power on the trainer, let other training apps release control first, tap Search trainers and select only your own equipment.
  2. Wait for connection and subscription to finish before tapping Start indoor cycling. Until the first valid data packet, show Waiting. Missing speed, cadence or power should show “—”. A Bluetooth connection alone does not establish data reception.
  3. During the activity, open trainer controls and test only target power, resistance or incline actually supported by the equipment. Make small changes first. Only a Confirmed target means the machine accepted it; a button action, successful write or waiting notice does not mean the target has been applied.
  4. Cycle comfortably following your original plan and try pause, resume, end and save. High-power efforts are not needed. Check that indoor records save separately, without outdoor routes or phone GPS drift.

ROLLR capabilities:Official firmware 1.1.31 and later supports estimated onboard power, not the precise measurement of an external power meter. The unit does not provide cadence; without a separately connected compatible cadence sensor, cadence should remain unknown. Available controls depend on the current firmware's reported capabilities and ranges. Unsupported controls should be disabled; the model name alone is no promise that every control works.

Scope this round:Code and software validation are complete. Real KICKR ROLLR resistance response, sustained Bluetooth, physical phone/Garmin/Rokid interaction and locked-screen behavior still await colleague testing. This website download remains the unified Rokid Android test app. The overseas Google Play channel is being prepared separately and has not been released on Google Play. This page supplies the domestic unified Rokid phone app.

Use optional regression checks NEW1–NEW11 for onboarding, profile data, next-week drafts and indoor themed experiences. TR, AI, training planning, proactive messages, rankings, routes and background location below are retained features and optional regression checks. Mark “Pass / Issue / Not tested” per item. Do not exercise or buy equipment solely to complete every item.

This installer is the 0.5.154 (version code 184) unified Rokid test app, package name com.funpizza.sportmaster. The same phone APK is used without glasses. For Garmin integration, use WatchApp 1.0.8 (localized Sport Master / English SportMate). Existing indoor cycling watch layouts and display sources remain. For older watch builds, ask the team for the new build matching your model.This is a feature test app awaiting colleague device confirmation. Physical trainer, phone, Garmin and Rokid locked-screen behavior and sustained heart rate have not passed acceptance.

Retained features: indoor cycling and rowing

This is the 0.5.154 device test app. Mark “Not tested” for checks without the necessary equipment, glasses or speech service. Do not substitute illustrations for actual data.

ItemHow to testWhat to check
Live powerConnect compatible equipment on the indoor trainer or rower page and start exercise. View Rokid too if available.Phone and glasses should show the same actual watts W. Real 0 W remains zero; missing or expired data must not appear valid. Target and actual power are displayed separately.
Gentle dynamic trainingSelect Dynamic training on the equipment control page and start. Try it briefly first; complete the full 55 minutes only when conditions are suitable.Course stages and road/trees or river scenes change with progress. Automatic targets are requested only for equipment supporting control. Distinguish Suggested, Sending and Confirmed states.
Three-stage entertainmentChoose Forest Supply Race for cycling or River Adventure for rowing.Each stage lasts 3 minutes; the three-stage sequence loops after 9 minutes. Items, opponents and pursuit prompts respond to real movement. Watts must not be invented without connected data.
Coach voiceListen for proactive stage prompts. Once safely stationary, tap the activity-page microphone and ask “What is my current power?” or “What should I do next?”Answers should match the current equipment and stage. After Q&A, the current stage prompt may resume only once; expired prompts must not replay. If silent, record the notice and phone speech-engine state. A text answer does not prove audio passed.

Retained features: trainer tests item by item

Without the trainer or corresponding accessory, write “No equipment, not tested”. Keep each item ID; demo pages or software tests do not establish hardware acceptance. Phone, glasses and watch can display the same trainer speed, distance and power relayed through the phone. Heart rate still comes from the separately selected heart-rate device; cadence comes from an actually available sensor.Matching Garmin screen data does not mean native FIT files exported by Garmin Connect use trainer data: native watch FIT files still collect data independently on the watch.

IDStepsWhat to expect / What to report
TR1 Dedicated entry and connectionCycling → Activity preparation → Indoor trainer. Search, select your own ROLLR and connect. Also return once without choosing a device.Do not automatically connect to all nearby devices. No selection must not start exercise. Show connection, subscription and live-data receipt separately; after subscription, wait if no valid sample is available.
TR2 Start and unknown dataAfter connection, start indoor cycling. Observe while stationary first, then pedal comfortably as planned. Watch speed, distance, power, cadence and their sources.Time starts with this session. Distance comes only from valid equipment data, without GPS or a default treadmill speed filling gaps. Real zeros and missing “—” stay distinct. ROLLR without an external cadence source must not invent cadence.
TR3 ERG target powerOnly if target-power control is available, set a small change within the displayed range, wait for the result and record the power source at that time.Send only if the device declares support and a valid range. Do not switch to Confirmed target while waiting; update only after a successful device response. A confirmed target is not instantaneous measured power. Report actual response and estimation error separately.
TR4 ResistanceOnly if resistance control is available, make one small adjustment using the page's actual range and step size.Do not use guessed levels or percentages. Resistance units and steps follow device reports. Confirmation, rejection and timeout states must be clear; no response must not show Applied.
TR5 Incline and capability checksView incline control. If supported, make a small adjustment within the page's allowed 0–10% range. Also inspect disabled controls.Unsupported controls must clearly be disabled. The ROLLR model name must not unlock everything. Incline is a simulated target sent to the trainer, not actual phone ascent and not a promise that the bike physically tilts.
TR6 Controls during exerciseAfter returning to the activity screen, open trainer controls again, view this session's data, adjust one available parameter and return.It remains the same activity, without resetting time/distance or opening extra records. Do not repeat sends while a control is pending. Failure must not present the old target as a new one. Record the exact error and wait duration.
TR7 Pause and resumeWhen safe, pause from the activity page for about 20 seconds and resume. View the phone and any connected watch or glasses.Pause and resume belong to the same session. Paused time and data must not become activity results or double-count distance on resume. App Pause/End is not a physical flywheel brake; ensure your own safety first.
TR8 Brief data interruption and reconnectionIf an interruption occurs naturally during normal use, record the last values, waiting notice and recovery. Explicitly choose Reconnect if needed.After about 5 seconds without a fresh trainer sample, live fields should show “—” or Waiting rather than continuously replaying old values. Totals remain, without time or GPS filling gaps. Recovery must not double-count pre-disconnection data. With no fault, mark Not tested.
TR9 Data sources across three devicesWith matching WatchApp 1.0.8 or Rokid, start the same indoor cycling session and compare sport, speed, distance, power and missing fields at the same moment.Synchronized screens use trainer data. The watch shows Indoor cycling and cycling metrics, without a treadmill speed of 6.0 or incline of 1.0 appearing. Watch GPS totals must not override trainer data. Check heart-rate source separately; native FIT remains watch-collected.
TR10 Saving and indoor/outdoor separationAt End, cancel once, then save or discard as you wish. View cycling records and separately open outdoor cycling preparation.Cancel keeps this session running. Discard needs confirmation; Save creates only one indoor cycling record. No invented outdoor track or location mileage, no mixing into outdoor routes/public results. Outdoor cycling retains its original flow without indoor control targets.
TR11 Remove equipmentAfter ending, tap Remove this trainer. Cancel first, then confirm if you wish; search again afterwards.Cancel preserves the selection. Confirm disconnects and clears the reconnect selection while keeping old activity records. Searching again must not automatically restart exercise or use another account's device selection.
TR12 Firmware and real responseRecord ROLLR firmware, whether power is an onboard estimate or an external power meter, and trainer control Confirmed target separately from what you actually feel.Onboard power requires official firmware 1.1.31 or later. Older firmware or unreported fields remain unknown; the unit does not provide cadence. A successful Bluetooth response only means the machine accepted the command. Actual resistance changes, accuracy and long-term stability require measured feedback.

Optional historical checks: training automation, proactive messages and rankings

No formal Mountaineering/Citywalk schedules or running-club tiers have been added. Report “Pass / Issue / Conditions unavailable”; no special long-distance exercise or equipment purchase is needed.

IDActionExpected
AUTO1 Automatic suggestionsFor an account with AI data consent and credible hiking/trail-running evidence within the last 21 days, view next-week suggestions for that sport.After the automatic task runs, a draft awaits adoption; it must not create a new one on every opening. Without suitable evidence, manual planning remains available and must not invent your circumstances.
AUTO2 Check conflictsReview full stages, change frequency or duration, and check the actual resulting schedule.Warm-up, main activity and cooldown should be complete. Unknown targets stay unknown. Unmet requests should explain actual frequency and duration, without pretending all requests were satisfied.
AUTO3 Personal adoptionCancel adoption once, then confirm. Check the calendar and confirm the booking separately.Cancel does not write formal sessions; after confirmation, they can be reviewed. Adoption, booking and starting that day's activity are separate actions, without mixing courses across sports.
MSG1 Reminder statusOpen Messages & training reminders from Devices. Check phone notifications, Google services, your registration and server state separately.Registration or provider acceptance must not be described as receipt on the phone. Disabled sending or unavailable vendor integration should be clearly explained.
MSG2 Quiet settingsSet and save quiet hours, disable remote notifications or switch between your own test accounts.Valid messages are delayed during quiet hours, expired ones are not replayed, and the old account's messages do not appear. Messages must not automatically adopt a plan or start an activity.
MSG3 No remote channelWithout Google services, use in-app messages or enable a local reminder per session after personally confirming its booking.The entry should work and explain possible system/network delays. Local reminders are not vendor push. Actual remote receipt first requires a designated account, phone and authorization for one send.
RANK1 Four sports kept separateIn Community & rankings, select running, cycling, hiking and trail running. Switch among daily, last 7 days, last 30 days and all-time rankings.Sports are separate. Daily rankings use midnight Beijing time and the actual activity start time, not upload time.
RANK2 View a region onlySelect a province/city from the lists and view its rankings.No manual typing is needed and GPS must not infer membership. Viewing alone must not change your region or automatically publish results.
RANK3 Join a regional ranking personallySet your ranking region separately, cancel once, then confirm and later clear it.Save only after explicit confirmation and change only this setting. The original public-sharing switch remains independent. Clearing the region removes participation in its ranking.
RANK4 Real resultsView your exclusion reasons, synced records and appeals.Demo, indoor, too-short, pending-review or nonpublic records must not go directly into rankings. Details and appeals retain their original sport. No running-club tiers are added.
RANK5 Separate confirmation for public resultsAfter setting a region, separately tap Join public rankings. Cancel first, then confirm if you wish. Check the leave-confirmation flow and refreshing after a network failure.Before enabling, explain that nickname, avatar and eligible results become public. Setting a region does not publish results. If submission status is uncertain, refresh to verify instead of resending blindly. Account changes must not retain the old state.

The web prototype shows local interactions only, without invented cloud rankings. Required information for actual FCM delivery and vendor channels is listed separately in a TXT file. Physical-device operations by the release owner remain paused this round; colleagues with equipment may report their own tests using this checklist.

Existing features, optional checks: four sports from scheduling to completion

First choose running, cycling, hiking or trail running in Me, then open multiweek planning in the AI coach. Try them separately if you wish; completing the whole training program is not required for testing.

IDActionExpected
F1 Generate multiple weeksEnter your goal, sessions per week and available duration. Choose 2/4/8 weeks and view week two, then check that choosing 1 week displays only one week.Each week has its own dates and stages, with the correct sport name. Nothing is adopted or started automatically.
F2 Adjust, then adoptAdjust the schedule in text, cancel adoption once, then review and confirm. Leave and reopen it.Cancel must not create formal sessions. After confirmation, all weeks can be reviewed, without missing weeks, changing sports or reverting to an older version.
F3 Calendar and bookingView the full course, choose a session and schedule a time. Cancel first, then confirm.Course adoption, time booking and starting exercise require separate confirmations. Changing sports must not show another sport's courses. Future sessions are read-only.
F4 Start from a sessionOnly on the scheduled day and if you wish to exercise, enter preparation and start. Pause, resume and end as needed.Stages should match the course accepted for that day. Pausing must not advance stages. After ending, the record and course completion should correspond without duplicate writeback.
F5 Outdoor coursesFor hiking and trail running, enter your expected terrain. You may leave the ascent target blank. View the course.This free-outing goal remains independent of the formal schedule. Stages use time; unknown distance, actual ascent, pace or heart rate must not be filled with zeros or invented.
F6 Outdoor reviewOpen a completed hiking or trail-running record of your own and view its review. If it shows rule-based advice, you may explicitly retry the AI review.Data should come from this record and unknown stays unknown. Model and rule-based sources must be clear. Retry preserves the original summary, without creating duplicate activities or adopting plans.
F7 Garmin sportsWith compatible WatchApp, use phone 0.5.154 and SportMate 1.0.8, choose hiking or trail running and start.The full session uses Garmin native values for the same activity. An old watch program or heart-rate broadcast alone must not be presented as full sport synchronization. Report actual physical results.

Retained feature: precise background location

First open Me → Settings → Precise background location. The activity or glasses device page also offers Background & lock-screen checks → Precise background location. Enabling permission must not automatically start exercise.

  1. Tap Allow precise location first. On Android 12 and later, choose precise location.
  2. Once allowed, tap Enable background location. On Android 10, choose Allow all the time in the separate permission flow. On Android 11 and later, go to this app's system settings → Permissions → Location and choose Allow all the time. If a Use precise location switch is present, enable it too.
  3. Return to the app and check Background location: precise location allowed. If the system no longer shows a permission prompt, open App permissions & battery settings manually.
  4. Enable system location services and allow background running or unrestricted battery use. Start the activity on the phone and confirm the recording notification.
IDCheckExpected
L1 User-initiated settingsOpen the app, enter the permissions page and explicitly tap Allow. Also try Not now, go back.Startup must not request background location automatically. Precise and background permissions are requested in separate steps. Skipping must not start running or prevent going back.
L2 Accuracy and revocationView the state with approximate location only. Allow precise/background access and return, then revoke it in system settings and return again.Approximate access must not show as precise location allowed. Returning refreshes actual authorization rather than retaining an expired success state.
L3 Normal locked-screen recordingWhen conditions allow during your usual activity, compare screen-on and locked-screen records and glasses status. Without equipment or an outdoor outing, mark Not tested.Record actual location and background behavior. Granted permission does not establish GPS accuracy or successful lock-screen testing. Location signal, battery policy and recording service require separate checks.

Background permission may be deferred. A location-recording service legitimately started while the phone app is in the foreground can already continue after locking. The new entry adds permission choices; it does not guarantee indoor GPS accuracy or bypass force-stop and every background-start restriction. Existing Garmin native-source synchronization requires paired updates to phone 0.5.154 and watch 1.0.8. Phone-only testing uses the same Rokid APK.

Existing outdoor regression checks (optional): Garmin native activity data takes priority

Update phone 0.5.154 and Sport Master/SportMate 1.0.8 together. This section applies only to outdoor running, outdoor cycling, hiking and trail running. Use the TR checks above for indoor trainers, where the trainer is the source. Once valid native data arrives for this outdoor session, phone and glasses use the native watch activity's cumulative time, distance, current heart rate and available speed. Bluetooth pairing or heart-rate broadcasting alone is not full activity synchronization. Before that, the phone records from real sources, then corrects when native data arrives; an interruption in this session does not switch back to phone mileage. Without equipment, mark Not tested. Actual watch-screen-off behavior still awaits colleague verification.

IDActionExpected
G1 One source across three devicesStart the same outdoor activity from phone or SportMate and compare time, distance, heart rate and speed at the same moment. Check whether values are labeled live or average.A full outdoor session uses Garmin as the source and no longer writes phone location mileage back to the watch. Unknown distance and real zero are distinct. Without valid GPS distance, the native timer may still continue.
G2 Watch display turns off automaticallyKeep the watch in Sport Master and let its screen turn off naturally. Continue normal activity for 3–5 minutes, observe phone/glasses, then wake the watch.Recording must not pause because the screen turns off; all three devices should still receive data for the same session. Record stalled updates, jumps on recovery and Garmin Connect's background state.
G3 Phone lock screen and heart rateKeep the watch activity running, let the phone lock naturally, and check glasses data and the record after recovery.The connected Garmin heart rate should continue to be received. Without a valid sample, show unknown rather than stale heart rate or another device's value.
G4 Recovery after interrupted dataIf data briefly stops during normal use, note the last time and distance, then compare again after recovery.Retain the last native totals and await recovery; do not switch to phone mileage or add both device totals. Clear expired live speed/heart rate.
G5 Pause and endPause, resume and end from SportMate or the phone, then check the summary and sharing.Same-session states should correspond to the native totals being used. The companion data field only observes the system's native activity; native activity controls must be operated on the watch.
G6 Record isolation on restartReport a watch-app restart only if encountered in normal use. You need not cause one deliberately.Another native recording must not overwrite this session's totals or mix its heart rate into an old session. Record the abnormal state; if needed, end this session before starting a new one.
G7 Actual distanceIf measured markers or a standard track are available, record actual laps, lane and additional segments.Matching values on three devices do not establish better distance accuracy. Calculate errors against actual laps for each source; do not assume the larger reading is true. Without a reference, mark accuracy Not tested.
G8 Remove heart-rate sourceRemove the heart-rate device during exercise, then observe the next Garmin data batch and the final average.Heart rate must not resume automatically or enter the average after removal. Time and distance may still update; previously accepted heart-rate history remains.
G9 Pairing or heart-rate broadcast onlyWithout starting a full SportMate recording, start phone running. Check hiking and other sports separately.Pairing, SDK readiness or HELLO must not freeze the phone timer. Sports without a full protocol retain phone timing, location and actually supported device heart rate. Phone estimates must not be labeled Garmin native values.

The AI coach and existing features below remain optional checks. Software tests and signed builds do not establish acceptance on physical Rokid/Garmin, outdoor GPS or all phones.

Retained checks: three-device duration, lock screen and heart rate

WatchApp 1.0.8 updates indoor cycling display this round. Outdoor duration, background connection and heart-rate checks below remain, without implying all phones, watches or firmware passed. The separately compiled test PRG currently matches only fēnix 8 - 47 mm AMOLED. For other models, tell the team your model and obtain a matching build before installing. Do not substitute the 51 mm file from an old page. Compiling a multi-model IQ package is not device-by-device testing.Back to downloads and release notes。

IDSteps in orderWhat to expect / What to report
T1 Three-device durationConfirm phone 0.5.154 and watch SportMate 1.0.8, connect normally and start from the phone first. Do a comfortable planned activity or stationary interface trial for 3 to 5 minutes and record duration on phone, watch and connected glasses at the same moment. Pause for about 20 seconds and resume. After ending, start a separate session from the watch if conditions allow.Phone and watch should share one session. The watch should keep time from actual elapsed time; it must not lag at only 3 minutes when the phone already shows 4 minutes. Pausing must stop accumulation of activity duration; resuming remains aligned to the same session. Glasses show its state. Transmission and screenshots may differ by a few seconds; record the actual difference, starting device, pause/resume times and any duplicate records.
T2 Phone locked, glasses keep updatingDuring comfortable normal activity, first confirm current data on phone and glasses with the screen on. Then lock the phone and observe for 2 to 3 minutes. Keep the glasses normally worn and connected; unlock and compare time, distance and state for the same session.Glasses time and real activity data should keep updating in the same session as the phone, without freezing on the old image at lock. Distance changes only with valid location/sensor data. Missing location should be explained as unknown, without invented distance. Record how long freezing lasts, whether unlocking immediately recovers, phone model, OS and battery-saving settings. A brief indoor trial is not outdoor distance acceptance.
T3 Continuous Garmin heart rateWear the watch normally, keep its SportMate activity running and select only this watch as the heart-rate source. Observe phone, watch and glasses with screens on for about 1 minute. Then let the phone lock and watch display turn off naturally; keep observing glasses and check the phone after unlocking. If conditions allow, test phone-start and watch-start separately.Phone and glasses should continue using fresh, real samples from the same selected source. An unchanged numerical heart rate must not repeatedly become “Not connected”. If a disconnection or prolonged sample gap occurs naturally, show Unavailable/Expired after about 10 seconds rather than treating old data as live forever; recover after a valid new sample. If the watch has a reading but phone/glasses do not, record each value, duration, screen states and heart-rate source. You need not remove the watch or create faults deliberately.

Retained checks: five AI features introduced from 0.5.112

These are steps for you to perform, not a claim that models, glasses sampling, cloud memory or system notifications have all passed. Server sending remains disabled this round, and real system push is not enabled this round; FCM receipt awaits testing. First check entries, descriptions and disabling actions; you need not wait for a notification.

IDSteps in orderWhat to expect / What to report
N1 Chat action cardsIn the current sport's AI coach, ask “Using the training times I entered, help me prepare next week's schedule.” Add missing information truthfully. When an action card appears, open and cancel once, then review and confirm generation or adjustment.Ask for missing information first. The card should match this account and sport; cancel creates no draft. Confirmation opens a reviewable draft. Adoption, booking and exercise start still require separate confirmations. Saying “Plan it for me” must not overwrite the formal schedule directly. Record the card title, destination after confirmation and any duplicate generation.
N2 Glasses voiceWith Rokid and while safely stationary, tap AI coach on the activity page and select Rokid glasses microphone. First authorize the microphone separately on the official page, then return and select it again. Read the notice, record a short question and try cancellation separately. Skip if you do not want to record.The prompt should specify the glasses microphone and a maximum of 8 seconds per recording. Audio goes to Tencent speech recognition for transcription without saving the original recording. Transcription, answer and playback should correspond; cancellation must prevent delayed replies. Missing authorization or audio should be clearly reported, without silently switching to the phone. Record audio capture, transcription and response separately.
N3 Cycling and outdoor sportsSwitch to cycling, view the weekly schedule and generate or adjust a draft using your real goals. Then open hiking and trail running and ask “What should I prepare before setting out for my current sport?” Actual completion of these sports is not required.Cycling should explain load and adjustments using cycling information, without invented power or results when information is missing. Hiking and trail running have their own formal multiweek plans, separate from running schedules. Mountaineering and Citywalk are deferred and need no testing or new entries this round. Automatic weekly suggestions await their actual generation time; if absent, mark None available, without requiring same-day appearance.
N4 Choose a route for trainingOn Routes, choose the current sport and city, then open Choose a route for training. If today's course has a distance target, you may leave the target blank. Otherwise enter your desired walking/running distance and optional ascent preference, then tap View recommendations. First use View on map, then decide whether to select it.Candidates should come from real public routes viewable for that city and sport, with matching reasons explained. Missing course targets should prompt for input, and missing elevation should be described as unknown. Viewing suggestions must not select, adopt or start automatically. After choosing, still check location and the requirement to be within 500 meters of the route before starting. With no suitable route, explain clearly and allow map selection or local routes.
N5 System push settingsOpen Messages → Coach care · System push. First read the Google device identifier and notification notice. Only if you wish, personally tap Agree and enable system push and choose system notification permission. You may then tap Disable and unregister system push. If you do not wish to enable it, mark Not tested.Sending is not enabled this round. Successful registration or an in-app message must not be treated as system delivery.The entry and state should be clear. Permission denial, missing Google services or restricted network should be explained. In-app messages remain viewable after disabling. Actual care content still requires your separate agreement; it cannot automatically adopt, book or start sessions. Testing actual receipt and taps will be announced separately after sender configuration is complete.

Existing checks: AI training planning from scheduling to exercise

Use your real goals. Personally confirm formal course adoption and activity starts. Future sessions can be viewed; enter preparation on their actual day. Dates without sessions remain blank.

IDStepsWhat to expect
P1 Schedule and adjustOpen AI coach training planning, answer goal questions and adjust one draft.The draft should reflect the goal. Generation and adjustment alone must not adopt it or start exercise for you.
P2 Personal adoptionReview and confirm adoption, then inspect Schedule week N training times and View week N sessions separately.Return to the correct adopted week. Adoption confirms courses only, without booking or starting exercise by default.
P3 Schedule a timeChoose a session and preview its time. Cancel once, then confirm once if needed.Canceling the preview does not save. A confirmed schedule can be read back. Canceling a confirmed booking still keeps the course.
P4 Dates and stagesSwitch to previous/next weeks and each day to view full sessions, then enter from My training calendar.Dates and courses should correspond. Empty dates must not invent sessions; future sessions are read-only. The schedule should remain available after reopening.
P5 Start on the dayEnter preparation only for today's session, review all stages, then start personally.Recheck the latest session before starting. If it changed or loading failed, ask for verification instead of directly using an old course.
P6 Sports stay separateWhen relevant courses exist, switch between running and cycling and review schedules and times.Selected sport, week and course must agree without showing another sport's course. Booked times across different sports should still avoid conflicts.

Device regression: phone, Garmin and glasses start together

The phone APK and Garmin Sport Master WatchApp 1.0.8 (SportMate) need matching updates.The watch IQ app is not yet in the store and is not the phone APK. The team supplies test PRG files matching the hardware model. Without the new watch app, mark joint start Not tested. Other devices offering only standard heart-rate broadcasting may supply heart rate only and cannot thereby control native watch activities. A Datafield in a Garmin native activity cannot remotely create a native FIT activity from the phone. Actual three-device, locked-screen and outdoor behavior still needs testing; not all brands or models are promised to have passed.

IDStepsWhat to expect / What to report
W1 Matching updatesKeep screenshots of old records first, then update the phone in place using the same package name. Ask the release owner to confirm WatchApp 1.0.8 (SportMate) matches your Garmin model. Open Sport Master on the watch, select this watch on the phone and grant necessary permissions.Old records should remain accessible and device selection clear. Updating only the phone or pairing in system Bluetooth settings does not update the watch app. Report uncertain models or firmware first, without uninstalling or clearing data.
W2 Start from phoneLeave the watch on the ready-to-start screen and start a brief activity from the phone. If glasses are connected, observe them too.The watch should enter the activity and phone, watch and glasses should follow the same session, with time and distance updating continuously. Record whether the watch stays ready, only the phone advances and roughly how long you waited. A brief trial is not full GPS acceptance.
W3 Start from watchAfter the previous session ends normally, keep Sport Master open and ready on the phone, then press START on the watch.The phone should enter the same session and connected glasses show activity data. The watch must not be timing alone while the phone has not started, nor should an unexplained extra phone record appear.
W4 Real heart rateWear the watch or heart-rate strap properly and select one heart-rate source only. Start from phone and watch separately and wait for actual samples.Phone and glasses should show the selected real source and keep updating. Before a sample arrives, show Waiting or Unavailable. Note whether worn, which device has a reading and whether old values persist. Bluetooth pairing does not prove heart-rate sampling.
W5 Pause, end and reconnectWhile safely stationary, check pause, resume and end. If conditions allow, briefly disconnect watch and phone, end the session on the phone, then reconnect. There is no need to unpair, uninstall or reset devices.States should follow the same session. After reconnecting, the watch should end the old session already ended by the phone, rather than pretending it is still running or starting another session from an old message. Saving follows your page selection; report extra records.
W6 Lock-screen comparisonAfter normal outdoor high-accuracy positioning is available, comfortably walk or run short sections of the same route with the phone screen on and locked. Observe glasses updates too if available.Compare duration, distance, route and glasses updates; timing should not be the only metric moving. Report phone model/OS, battery-saving settings, location permission and distance/time for both sections. Note indoor or poor-signal conditions; a test without GPS is not a lock-screen conclusion.

1. Installation and account: keep existing data first

IDActionExpected results / What to report
A1Before upgrading, record the current version and screenshot the activity list and record count. Install this APK over the existing app. Do not uninstall, clear data or switch to another package name.The same package name and release signature should support an update retaining data. If there is a signature conflict, installation failure or uninstall requirement, stop and send the complete notice and old version. Do not delete old data to solve it.
A2Open the app, check its version in Settings & About, then inspect old records, adopted plans, photos and existing device settings.It should show 0.5.154 and existing content should still open. If signed out, log back into the original account before checking. An empty list while signed out is not necessarily lost data.
A3Log in with your own regular account, view Third-party AI data consent · Independent choice, and read and choose for yourself.Login state should be clear. AI consent is separate from EverMe authorization. Without permission for AI sharing, content must not secretly be sent to models or cloud memory; non-AI features such as activity records can still be checked. Do not post verification codes, passwords or authorization links in groups.

2. Prioritize the AI coach: start with these six groups

These are optional AI regression checks; test trainers with the TR group first. Copy the questions below and adapt them to your real situation. Chats may offer action cards requiring your confirmation. A generated draft is not an adopted formal schedule; adoption, booking and exercise start still require separate confirmation.

IDEntry and actionQuestion to copy / Expected result
B1 TextSelect Running, open AI coach, ask one question and then one follow-up.“I only want 20 minutes of easy activity today. Explain the basis for your advice; if you do not have my heart rate or recent training data, explicitly say you do not know.” Then ask: “Condense that advice into three points. Which parts are estimates?” The answer should understand this conversation's context and current sport. It must not invent missing data or pretend the model succeeded when unavailable; explain any fallback. Note whether the first answer and follow-up are reasonable or remain stuck for a long time.
B2 VoiceWhile safely stationary, start a brief activity-interface trial and tap the AI coach voice button. If granting microphone permission for the first time, tap again afterwards. You may end without saving; no actual run is required.“In one sentence, tell me what to watch for during easy activity, and explain if evidence is missing.” Check that recognition, response and playback agree. One question must not produce a series of duplicate replies, nor should old answers suddenly play after cancellation. If silent, specify no recognition, no text, no playback or system mute.
B3 Pre-run planOpen next week's schedule from Me → Training plans & weekly reports or the training page. Enter real available times and generate a draft. Do not adopt it yet; check all seven days and make one text adjustment.Suggested adjustment: “I am unavailable next Wednesday. Keep the other arrangements and change next Saturday to 15 minutes of easy activity.” The result should explain actual changes or limits and retain dates, goals and units you did not ask to change. Nothing should enter the formal calendar before Adopt.
B4 Personal adoption / CalendarAfter reviewing the draft, personally tap Adopt all displayed weeks → Confirm adoption. Open the corresponding next-week calendar, leave and return. If there is a separate time candidate, review and personally confirm it too.The formal calendar should read back the same schedule version without replacing the current week by mistake. Saying “Arrange it for me” in chat does not mean adopted. If the version changed or readback is unconfirmed, retain the notice and refresh to verify before repeating Generate or Adopt. You may decline an unsuitable schedule and mark Not tested.
B5 Preparation and nutritionOpen Comprehensive assessment / Departure preparation on the training page and review its evidence. Preview one real meal description or photo in Nutrition.You can ask: “Using the information I have already provided, what is still missing before I set out today?” Evidence should distinguish actual records, your own entries and unknowns. Meals first appear as previews/estimates; without your confirmation, they must not become formal food records. Do not invent injuries, meals or training facts for a test.
B6 Review / Weekly plan / Weekly reportComplete a normal activity from the next section. On the finish summary, enter your real RPE, fatigue and physical condition and save. View its review in activity details, select this record under Training & recovery to verify how you felt, and check Training plans & weekly reports.“Review the journey I just completed, using only existing records. If heart rate is missing, do not assess heart-rate zones.” The review should match this activity, and saved RPE should persist after reopening. Automatic weekly suggestions should start as drafts awaiting adoption, without replacing schedules automatically. New accounts or weeks without a report should clearly show no data/generation time rather than inventing weekly results. Same-day scheduled report generation is not required.

3. Before, during and after activity, with sport isolation

IDActionExpected result
C1 One comfortable activityPrefer running and complete a comfortable activity following your existing plan. Before starting, view the goal and preparation. Check data during it and pause/resume once if convenient. At the end, choose to save or discard. A brief interface trial is also acceptable; label it “Brief trial”.Start / Pause / Resume / End states should agree. Discard needs clear confirmation; saving creates only the corresponding single record. A very short distance or duration may prompt whether to save. A brief interface trial is not full GPS acceptance. No need to keep looking at the phone while exercising.
C2 Guidance before, during and afterAsk about preparation before starting. During exercise, ask one current-guidance question only when safely stopped. Afterwards view this activity's review and recovery.Answers should match the phase: do not claim completion before starting, treat a paused session as moving, or keep reporting live data after ending. Missing heart rate, power or location remains unknown; estimates need labels.
C3 Quick check across four sportsSelect running, cycling, hiking and trail running in turn, view titles and record filters, and ask the coach “What is my current sport, and what should I focus on preparing?” You need not complete all four sports.Do not mix sports, old replies, records or goals. Cycling discusses sport-specific matters such as speed. Hiking/trail running can generate, adopt and start their own formal multiweek courses, separate from running schedules. Mountaineering and Citywalk are deferred and excluded this round. The four sport identities remain separate. When there are no records, show an empty state rather than filling it with another sport's data.

Do not create pain, discomfort, connection failures or dangerous exercise to test. Enter how you actually feel. Stop activity if uncomfortable; you do not need to finish the checklist.

4. EverMe: voluntary connection; distinguish “Connected” from successful cloud memory

  1. Also test once without a connection: With normal AI sharing consent and available service, the coach can still answer from the current question and this account's local information. It should honestly show no long-term cloud-memory connection and must not claim it read EverMe.
  2. Test connection only if you wish: Settings → Agent memory → EverMe · AI memory. Read the dedicated notice, log into your own EverMe, complete official authorization, then return and refresh. Connecting does not enable the separate AI consent for you.
  3. Record what the card states mean: Connected, Readable and Will attempt to save successful Q&A. Keep an existing regular connection; do not repeatedly authorize, disconnect or revoke it for testing.
  4. If you wish to leave a test example, send only once: “Interoperability test code: 〈a short temporary code you choose〉. This is a memory-connection test, not a health, training or preference fact. Do not adjust plans based on it.” Record send time and reply state. If failed or awaiting confirmation, report first instead of repeatedly sending the same item.
  5. Repeating a code in the same chat window is not proof of cloud recall: Local chat history can also supply the answer. “Pending sync 0” does not mean this item reached cloud memory. The owner separately verifies individual delivery, actual cloud retrieval and sources. Colleagues report only states and behavior actually observed this round.

5. Offline behavior, retries and account isolation

IDActionExpected result
D1 Network recoveryWhile stationary with no activity recording, briefly go offline and try to read a draft or submit an ordinary question. Once the network returns, use only the page's Retry / Verify actions.Offline / Awaiting confirmation notices should be clear and existing drafts/records retained. Recovery must not create duplicate chats, records, schedules or meals from the same action. If results are unknown, refresh to verify instead of “solving” them by generating again.
D2 Switch accountsOnly with two test accounts you own: ask an ordinary question or open a draft in A, log out and into B, then return to the related pages.B must not show A's drafts, chats, pending events or delayed replies. Without a second test account, skip it rather than borrowing a colleague's account or sharing codes. Do not revoke a regular EverMe connection for testing.

6. Optional regression: colleagues test personally when conditions allow

Without glasses, watch or a heart-rate device, write “No equipment, not tested”. You can still report AI coach behavior first.

7. Feedback format to copy

[0.5.154 test] Pass / Issue / Not tested
Item ID: prioritize NEW1–NEW11 this round; optional retained items include TR / AUTO / MSG / RANK / AI
Phone model / Android version:
Previous version → Current version:
Sport / Indoor or outdoor:
Trainer model / Firmware (if applicable):
Power source: onboard estimate / external power meter / unknown
Control / Set value / Confirmed target / Actual response:
Page connection state / First data packet received?:
Watch model / Firmware / WatchApp 1.0.8 (SportMate)?:
Started from phone or watch:
Phone / Watch / Glasses time and distance at the same moment:
Reference route length / Actual laps / Extra segments (if applicable):
Phone and watch error against real reference distance (without a reference, mark Not tested):
Behavior after phone lock / Watch screen off:
Heart-rate source / Values on each device / Duration of missing readings:
Lock state / Screen-on distance and time / Locked-screen distance and time:
Glasses model and firmware (if applicable):
Time of issue / Network conditions:
Steps: 1… 2… 3…
Expected:
Actual:
Reproducible?:
Screenshots or recording: hide phone numbers, verification codes, passwords, authorization links and private chats

First check installation group A, then test BEAUTY1–BEAUTY3, CADENCE1 and MAP1–MAP4; NEW1–NEW11 remain optional regression checks. Older TR trainer, AI, AUTO training automation, MSG messages, RANK rankings, background and outdoor checks remain optional. Mark Not tested when conditions are unavailable. Without a designated account and phone authorization for remote delivery, mark Conditions unavailable; receipt of system notifications is not required. Prioritize installation failure, missing old data, cross-account data, unconfirmed plan writes, duplicate saves and lost background records.

Legal documents are currently available in Chinese only.