Garmin shipped the first stable software update for the Fenix 9 on September 15. Version 6.48 fixed seven documented problems. None of them were the one owners keep complaining about.
Eight days later, the most detailed report on the Garmin forums reads like a man deciding whether to send back a watch he paid flagship money for. He runs a Fenix 9 Pro 51mm inReach, switched from a tactix 8, and updated to 6.48 the day it landed. Then he went for a 15km run.
His AirPods Pro 3 disconnected six times. Each time he had to open the music settings mid-run, disconnect the headphones and reconnect them. And on several of those reconnections, the music came back at maximum volume, with the earbuds already in his ears.
His conclusion is blunt: "I feel that the Fenix 9 was released too early and that its software still needs a lot of refinement."
What 6.48 Actually Fixed
It is worth being fair to Garmin here, because 6.48 was not a nothing update. Here is the full changelog from Garmin's own forum post:
- Fixed Garmin Locate displaying confusing locations and times
- Fixed Messenger Calls not coming through correctly when watch and phone are still BLE-connected
- Fixed microphone not working if Voice Assistant is interrupted by an incoming call
- Fixed potential battery drain issue for Pro devices with activated inReach plans
- Fixed some watchface translation and layout issues
- Fixed voice alerts coming through when in Silent Mode
- Fixed volume increment and decrement
That is a reasonable list, and one of them is specifically relevant. The changelog fixes volume increment and decrement while users are reporting music blasting back at full volume after a reconnect. Garmin patched the volume controls and did not patch the behavior that makes those controls matter.
Two of the fixes are also Bluetooth-adjacent: Messenger calls over a BLE connection, and the microphone during Voice Assistant. Garmin was in the Bluetooth stack in this release. It just did not fix the part that touches your headphones.
The Pattern Is Older Than the Fenix 9
This is where the story stops being about one bad update, because Garmin has been here repeatedly.
A forum member with the Fenix 9 Pro AMOLED and inReach put it plainly: "My F9 Pro AMOLED with Inreach is decisively worse with my Shokz Bluetooth headphones during run activities. I get at least 10 garbled moments during a 45 minute run."
He then added the context that matters most: "I've owned (and still own) many Fenix and ForeRunners using basically same headphones doing same activities listening to same music. F9 Pro is indeed worse for dropouts. I never run with phone. That's actually why I bought Inreach."
The same user drew the comparison to an earlier launch, and it is the most useful thing in the entire thread:
This feels a LOT like the Epix Gen 2 (and Fenix 7) where the initial release had TERRIBLE bluetooth performance. These forums are filled with posts and long threads about the problem. Myself and everyone thought it must be an unfixable hardware issue. Many people returned their watches due to this. But, quite shockingly, Garmin worked through this and a firmware update was able to resolve the issue. I am hoping for same resolution here with the F9. But I wonder if the full titanium case makes this a hardware issue that cannot be overcome with firmware.
That last sentence is the most interesting hypothesis anyone has offered. The Fenix 9 Pro moved to a full titanium case, which was one of the headline hardware changes of this generation. Titanium is a different material for radio frequency passthrough than the part-titanium construction of previous models. If the case is the problem, no update fixes it.
The history gives some reason for optimism: Garmin did eventually solve the Epix Gen 2 and Fenix 7 Bluetooth problems in software, after a lot of returns. It also stretches back further. Bluetooth headphone complaints run through the Fenix 6, Fenix 7, Fenix 8 and Venu lines, in threads going back years, with users swapping earbuds, rolling firmware back and factory resetting watches without a fix. This is Garmin's longest-running unresolved complaint, and the Fenix 9 has the worst version of it.
The Recap: Everything Else the Fenix 9 Has Been Through
The Bluetooth dropouts are the loudest problem because they happen mid-run, but they are not the only one. And they are not Garmin's only live software problem right now: the CIRQA's End button still deletes workouts. Here is the full list from the Fenix 9 forums, separated into what 6.48 fixed and what it did not.
Fixed in 6.48: confusing Garmin Locate times and locations, Messenger Calls over BLE, microphone failure after a call interrupted Voice Assistant, battery drain on Pro devices with active inReach plans, watchface translation and layout errors, voice alerts in Silent Mode, volume increment and decrement.
Still live after 6.48:
- Optical heart rate dying during activity. This one is genuinely alarming. A reproducible bug report describes the optical HR sensor stopping completely during an activity with Bluetooth music playing, with the green LEDs on the back of the watch turning off entirely while music keeps playing. No music, no problem. Music without activity, no problem. Activity plus music, sensor dies. The same reporter later triggered it by panning and zooming the map heavily, which suggests a resource management problem rather than a Bluetooth one, and a third user confirmed it on a three-day-old Fenix 9 Pro 51mm. Substituting an external chest strap made the issue disappear, pointing at the internal optical sensor or its driver.
- Brightness controls broken on MIP models. Increasing brightness from 5 percent to 10 or 15 percent does nothing. Reducing it to 10 makes the display brighter. Returning it to 5 changes nothing.
- Battery dropping to 94 percent immediately after unplugging. Reported on a brand new Fenix 9 Pro AMOLED on 6.48, dropping within minutes of coming off the charger at 100 percent.
- Watchface rendering errors. The current day of the week showing as two letters instead of three on the Fenix 9 Pro inReach Solar 51mm.
- Navigation audio not working. Guidance alerts and navigation audio failing with connected devices on 6.48.
- The Messenger crash. A five-step reproducible crash when replying to a message with a voice note while music plays over Bluetooth. The app hangs, the headphones disconnect, and doing it during an activity crashes the watch outright. The reporter said it was the primary reason he bought the inReach model, and that he would likely return the watch.
There is one genuinely positive post in the pile: an owner reporting that battery consumption on 6.48 dropped from about 25 percent per day to 20 percent per day on a Fenix 9 Pro 43mm. That is a real improvement, and it deserves to be said alongside the rest.
What Garmin Is Telling People
Garmin has responded in the threads, and the response is software support rather than an engineering answer.
A Garmin staff account pointed one owner to the public headphone Bluetooth FAQ and suggested that "some have experienced an improvement to reception by temporarily disabling the watch's Bluetooth connection with their phone." The owner had already tested with the phone left at home entirely, and said so.
That is the gap. Garmin's advice assumes a phone nearby is the interference source. The owners reporting the worst dropouts are running without a phone at all, which is what they bought the inReach model to do.
Why This Round Is Angrier
The complaints are sharper this time for a few reasons.
The price has gone up. Garmin's published Fenix 9 range runs from $999 for the 43mm and 47mm base models to $1,299 for the 51mm Fenix 9 Pro inReach. Several of the angriest posts are from owners of the most expensive configuration.
The compromises are more visible at that price. One owner who switched from a tactix 8 noted he had no headphone or heart rate strap problems on the older watch. Another came from Suunto and said he had never had music connection issues there. A third, whose 14-day return window closed on a Friday, returned the watch and ordered an Apple Watch Ultra 4 instead.
And the tone has shifted from troubleshooting to principle. One forum member framed the max-volume behavior as a safety issue rather than an annoyance, and the underlying complaint as a value judgment: "a flagship watch at this price should not make its users feel like beta testers."
The original poster, who has been fielding replies in Spanish and English, put the scale of it simply: "somos muchisimos con el mismo problema." There are a lot of us with the same problem.
Bottom Line
Garmin's first stable Fenix 9 update fixed seven documented bugs and did not touch the Bluetooth headphone dropouts that owners have been reporting since launch. On the forums, that means six disconnects in a 15km run, music returning at full volume, and at least one customer who has decided to send the watch back.
The dropouts sit on top of a longer list: an optical heart rate sensor that shuts off during activity, broken brightness controls on MIP models, battery readings that drop six points off the charger, watchface errors and navigation audio failures. Garmin fixed enough in 6.48 to prove it is working the list. It has not fixed the one that ruins a run.
The uncomfortable question, raised by a user who has been through this before, is whether the full titanium case makes this a hardware problem that software cannot solve. Garmin solved a version of this on the Epix Gen 2 and Fenix 7, which is the reason to expect a fix rather than a refund. But that took a long time, and a lot of people gave up before it arrived.
Sources: Garmin's official Fenix 9 Family System Software 6.48 release post and changelog; Garmin forum threads including "Fenix 9 Pro 51 mm inReach - 6 AirPods disconnects during a 15 km run after update 6.48," "Anyone else having music dropouts during activity?", "BUG (F9 Pro inreach FW6.38) - Optical heart rate sensor stops working during activity when using Bluetooth music," "Messenger app crashes when replying with a voice message when you have music playing using bluetooth headphones," and the post-6.48 bug reports on brightness, battery and watchface rendering, with replies from Garmin staff and affected owners; and Garmin's published Fenix 9 series pricing across base, Pro and Pro inReach configurations.