Specialized Mastermind display resets whenever I open the Mission Control app.

Brian in TN

New Member
Region
USA
I have created a couple of custom displays using the Mission Control app. One custom display shows my heart rate, which is important to me. Every time I open the Mission Control app on my phone and let it connect to the bike the Mastermind display resets and I lose my custom displays. It does this using either Android or iPhone, I’ve taken the bike to the LBS and had all the firmware updated including for the IGH. Specialized has been no help as it’s been back-and-forth emails since February. Reset the bike, reinstalled the app, etc., nothing has worked so far. This is really getting annoying as there are features in the Mission Control app I would like to use but can’t without losing my custom displays.

Bike: Como 5.0 IGH – purchased Nov 2022

Has anyone else experienced this issue or have any suggestions?
 
I had a weird display issue and found it was Mission Control switching to ‘Stealth Mode’ on its own. That will make your custom screens disappear.
 
I had a problem this week with the Specialized App doing the “Ghost 0%” glitch. I figured it out with Gemini, and passed the diagnostic to my LBS and they were able to fix it. Gemini said to give kudos to @Stefan Mikes.

Gemini said,
When you look at Specialized Turbo systems across user forums, EMTB communities, and subreddits over the last few firmware cycles, a recurring "ghost" issue pops up. During certain app syncs or over-the-air firmware handshakes, the application can push a corrupted tuning file back to the bike's internal memory. It tricks the bike into setting the baseline slider values for Support and Peak Power directly to 0%, even though the physical display on your top tube still claims you are shifting between Eco, Sport, and Turbo.

Because it’s a valid command parameters file rather than a shorted wire or a fried chip, the MasterMind TCU sees nothing wrong and passes the system check as 100% healthy.

Mechanics are trained to systematically test the physical components first—running multimeters on the battery, checking the harness, dropping the bottom bracket, and verifying the physical cadence/torque sensors. Because those tests are time-consuming, a pure software profile conflict like that can easily fly under the radar for a few hours.
 
Back