'24/'25 Nautilus Widget Updates?

[Mooz80]

For the Google directions volume, I tried the Chat tool on the website, they redirected me to the phone line. I called, waited 45 minutes and hung up… nice service! I’ll try the dealer as well…

 

[angore]

@markfm I noticed on your phone snapshot, you likely have the Lincoln Way "nearby devices" setting enabled since the "key" shows up on notification bar. I always keep "nearby devices" permission for Lincoln Way app disabled so they phone does not interact with vehicle from a distance. When permission disabled I never see symbol. The only purpose I see is approach lights and auto unlock. The rest of actions can be done via wifi/modem.

My battery voltage was routinely down to 12.2V and never saw any side effects. When it did go into deep sleep (following a day when I had washed the car), it was around 11.5V.

The best way to get the APIM update is to report issues with google maps, etc. and refer them to latest TSB. A dealer should be happy to update since it is covered by warranty costs.

 

[angore]

For the Google directions volume, I tried the Chat tool on the website, they redirected me to the phone line. I called, waited 45 minutes and hung up… nice service! I’ll try the dealer as well…

The website chat tool is worthless. You should just call concierge.

 

[Mooz80]

For the record, the dealer told me he opened a ticket for the navigation volume. But he said if multiple clients open tickets, it would help. So if you have an appointment soon, have your dealer open a ticker for this.
Thanks

______________________________

Help support this site so it can continue supporting you!

 

[markfm]

I have the latest APIM update and it does not fix the volume issue you mentioned

Last night our '25 R2 got the TCU-24.2.5.9 update (that some owners have gotten as of months ago). This update fixed navigation volume on our '25 R2 hybrid.

After doing a 10-second soft restart this morning, in addition to fixing the Auto Hold LED not working, and phone charging icon not showing, it fixed the navigation directions volume. Make a change while it's giving directions and a "Prompt volume" slider now shows while you're adjusting it with the volume knob; the new volume level is used going forward.

(I'm in no rush getting updated for a couple of new widgets, but the loud directions volume was really annoying.)

 

[angore]

My 24 has always showed a prompt volume that showed up when you turn the knpb while she is talking. Was there something new?

 

[Mooz80]

The prompt volume is there and can be adjusted while speaking, but whatever the volume level you leave it on, it will reset to a high volume on the next prompt.
Dealer confirmed the issue on multiple vehicles while looking for a solution for mine after all software where updated. They told me many clients must escalate the issue through their dealer to hope for a fix.

 

[markfm]

My 24 has always showed a prompt volume that showed up when you turn the knpb while she is talking. Was there something new?

I don't recall seeing that "Prompt volume" prior to the TCU update, back when the change in volume wouldn't "stick" (persist). I may have had it, but don't think so - the audio knob would lower the volume, but the manual change from the knob wasn't being hooked to the "Prompt volume" variable (hence why it wasn't persisted across navigation direction prompts).

Based on navigation prompt volume changes from the audio knob now working after that TCU update (the only other Lincoln-specific OTA I've seen was the ECU update back on 9/8, but the volume issue was still there after the ECU), my conclusion is that something in the TCU relates to that volume change functionality; there must have been a glitch in my existing TCU firmware, with the TCU OTA flash fixing it.

______________________________

Help support this site so it can continue supporting you!

 

[markfm]

The prompt volume is there and can be adjusted while speaking, but whatever the volume level you leave it on, it will reset to a high volume on the next prompt.
Dealer confirmed the issue on multiple vehicles while looking for a solution for mine after all software where updated. They told me many clients must escalate the issue through their dealer to hope for a fix.

For us, when I flagged the issue to our selling dealer, asserting that we hadn't run into that on multiple other Nautilus', they checked and agreed (volume change was working well on others). That's why they stepped up and quickly opened a TAC case.

Since the TCU OTA last night was literally the only change on the vehicle in the past week, and it appears to be corrected (I'll reconfirm next time I take the R2 out, but did drive it enough, have Maps do several navigation rounds), I do expect that TCU is the problem point.

(It's a known thing that sometimes firmware flashes get "bit hits", not properly writing the firmware, not everything expected being modified. 9 out of 10 people may have truly successful updates, but the 10th gets a whoops - whether a bad FDRS firmware download, cruddy USB drive, bad cable, insufficient battery,... beats me, but it does happen.)

 

[swindler]

We find the navigation prompts annoying regardless of the volume. We set it to 'Alerts only' and so I guess we've never encountered this issue.

 

[markfm]

I've got better hearing than DW, and am the driver for the R2, so I purposely like to have prompts at a bit lower volume level - enough that I can pick them up, but not disturbing.
(I like Maps' nav prompts, but that's absolutely a personal preference)

 

[angore]

I believe just reflashing code could solve some issues.

(It's a known thing that sometimes firmware flashes get "bit hits", not properly writing the firmware, not everything expected being modified. 9 out of 10 people may have truly successful updates, but the 10th gets a whoops - whether a bad FDRS firmware download, cruddy USB drive, bad cable, insufficient battery,... beats me, but it does happen.)

______________________________

Help support this site so it can continue supporting you!

 

[markfm]

I believe just reflashing code could solve some issues.

Absolutely.