Answered in the dedicated thread for this.Anyone with an active FDRS willing to run my VIN and check for updates?
3FMTK1SS8MMA33726
Thanks!
It's not a J2534 compliant device is it?I've always used my Mongoose for FDRS updates but I forgot it at home and have my OBDLink MX+ at the office. Would that work for FDRS updates or it isn't supported?
It won't work. If it did, people wouldn't be spending $500+ on the Mongoose.I've always used my Mongoose for FDRS updates but I forgot it at home and have my OBDLink MX+ at the office. Would that work for FDRS updates or it isn't supported?
Good point, guess I'll have to wait until tomorrow. Though no one even notices anything in the APIM update? Does BlueCruise "don't show me notices it is on" actually work now?!?!? I thought this was fixed in 2.8.3, hopefully it is fixed in this one... No Alexa, so it can't be the start of the 3.X.X series of updates.It won't work. If it did, people wouldn't be spending $500+ on the Mongoose.
I haven't noticed anything different after updating. For the BlueCruise notifications, do you mean that it's still popping up every time BlueCruise is available even with the notifications turned off? Mine doesn't do that.Good point, guess I'll have to wait until tomorrow. Though no one even notices anything in the APIM update? Does BlueCruise "don't show me notices it is on" actually work now?!?!? I thought this was fixed in 2.8.3, hopefully it is fixed in this one... No Alexa, so it can't be the start of the 3.X.X series of updates.
What the heck! Yeah, I've toggled the notifications setting fifty times as people said 2.8.3 fixes the bug where it doesn't follow your settings. I've restarted sync a handful of times, too. Is there anything else I can try? Or maybe I should just do the APIM update and see if that resolves it.I haven't noticed anything different after updating. For the BlueCruise notifications, do you mean that it's still popping up every time BlueCruise is available even with the notifications turned off? Mine doesn't do that.
The setting just disables the notice that BlueCruise is available. You will still have the BlueCruise enabled message.What the heck! Yeah, I've toggled the notifications setting fifty times as people said 2.8.3 fixes the bug where it doesn't follow your settings. I've restarted sync a handful of times, too. Is there anything else I can try? Or maybe I should just do the APIM update and see if that resolves it.
So you're saying that every time you get on a highway that supports BlueCruise (without enabling BlueCruise), you get a popup saying BlueCruise is available? That's what the notification setting turns off.What the heck! Yeah, I've toggled the notifications setting fifty times as people said 2.8.3 fixes the bug where it doesn't follow your settings. I've restarted sync a handful of times, too. Is there anything else I can try? Or maybe I should just do the APIM update and see if that resolves it.
Ahh, what! I don't need that every single time. Jesus beans, oh well, such a small QoL improvement but I guess I'll live with it lol.The setting just disables the notice that BlueCruise is available. You will still have the BlueCruise enabled message.
I guess I misunderstood it, I thought it disabled the notification that BC was on when you activate it! Such a dunce, but still wish there was a way to turn that off.So you're saying that every time you get on a highway that supports BlueCruise (without enabling ClueCruise), you get a popup saying BlueCruise is available? That's what the notification message turns off.
Yeah, there is no setting to change that.I guess I misunderstood it, I thought it disabled the notification that BC was on when you activate it! Such a dunce, but still wish there was a way to turn that off.