mine (Batch 8 wave 2??) was 3.02 i immediately updated to 3.03 as i plan on installing the 2280 ssd today or tomorrow.
(running OS on the 2230)
Now batch 12 i would assume 3.03 would be final & no longer beta by then but it only took like 10 mins if that to update.
Folks, it is immensely helpful for Linux users to include their distro and fwupdmgr --version
Editing existing posts with these details works.
Thanks
Appreciate the details. Did you do the following:
fwupdmgr enable-remote lvfs-testing
fwupdmgr refresh --force
fwupdmgr get-updates
fwupdmgr update
Hi @jared_kidd,
I’d like you to get this into a ticket as I feel like there may be additional factors. A bit warning, we do not actively test against Arch, however, I’d like to get logs from you and see if we can spot the issue, repro again with you testing a few different things.
When creating the ticket, please link to this thread and mention this is for Matt Hartley and to be sent directly to me please.
Hi @Kelton_Page, I’d like you to get this into a ticket as I feel like there may be additional factors.
While I am exclusively Linux support, I would like to get this ticket in front of our engineering team and will be the one connecting everyone in the ticket.
When creating the ticket, please link to this thread and mention this is for Matt Hartley and to be sent directly to me please.
Has anyone encountered issues connecting with the USB-C enabled iPhone 15 Pro Max (or similar) after updating to 3.03? I am encountering an issue where the USB connection goes through an infinite connection/disconnection cycle after plugging it in via a standard USB-C to USB-C cable. This behavior occurs regardless of laptop power state (the behavior continues when the laptop is powered off). I have tried different cables and different ports but nothing resolves the issue. I sent a request in to support to have them look into the issue but it’s been a slow process of gathering data so far.
As mentioned I managed to get it working by (as root):
/var/lib/fwupd/.dnf update --refreshdnf reinstall fwupdfwupdmgr disable-remote lvfs-testingfwupdmgr disable-remote lvfsfwupdmgr disable-remote vendor-directoryfwupdmgr enable-remote lvfsfwupdmgr enable-remote lvfs-testingfwupdmgr refresh --forcefwupdmgr updateI suspect fwupd might have gotten confused as I just upgraded from F39 to F40, and I have no idea what vendor-directory is about, but I suspect disabling that resolved things for me…
There seem to have been one or more bugs in fwupd or rather, the libxmlb depedency for it. See: No testing BIOS update available for Framework 13 · Issue #7060 · fwupd/fwupd · GitHub. The updated libxmlb (3.18) is already in Fedora to fix this. There might be more issues in fwupd though, there’s still discussion going on in a similar ticket.
Who can the userbase engage with at Microsoft to change this?
Yes, same problem on Windows with an iPhone 15 Pro.
Complains there’s not enough power and disconnects. Then repeats the cycle.
There is a seperate thread about iPhones not connecting, from way back.
It is still an active problem problem with the Framework 13 laptops. I could not find a corresponding Framework 16 thread before posting here. It seems like there’s something going on with the Framework USB C negotiation process.
Thank you for the response. I had submitted a support ticket a couple days ago, but unfortunately I can’t find any ticket number or way of referencing it for you. I have just responded to the support agent’s email request for further information.
And to note on OS, I am doing any troubleshooting with Framework on Fedora 39 instead of Arch.
Quick question relating to AMD drivers. If we install the Framework driver bundle (either the current one or the next upcoming one), how do we keep them updated - especially the AMD-related drivers because they get updated pretty often by AMD.
I was made aware the bundled version is Framework-specific so we’re relying on FW to update and release. I’m used to not relying on an OEM for this, and going directly to the source (AMD, nVidia, MediaTek/Intel, etc).
Possible it’s related to the iPhone trying to charge the FW…
I’ll run my battery down, and try it again,
Found it, I have the ticket now. We’ll continue there. 
When I tested and reproduced the bug, the Framework was always fully charged (and sometimes on AC power) and the iPhone was between 80% and 6%. I have not been able to get the iPhone 15 to connect to the Framework 16 over USB-C.
Update: The phone connects but does not charge when connected to USB 3 and 6 (the non-240W ports). I received a bunch of strange kernel level error messages when attempting it in the Fedora 39 live test environment. The logs are being collected and sent over to support for further analysis.
I’ve seen something similar, though on the previous BIOS (maybe latest as well, I have just not tested with 3.03). I plugged in both an external SSD and an HDD (2.5" and 3.5"), with or without an external power supply. My external connector always made a “clicking” sound (from both the SSD and HDD…) when connected to USB 3 with a USB A expansion, and did not connect to Windows properly. I tried it with two different variations of USB A to SSD/HDD connector. As soon as I put the USB A expansion in USB 2, and used the external drive from there, it worked just fine, and no odd noise. Something is definitely up with the front ports and external devices.
I noticed that there are cable issues all over the place.
I have, last year, tested all my USB cables and threw away half of them because of weird results. Some where “charge” only, some where “data only” and max 500mA power delivery etc. leading to all kind of weird results.
bought some decent cables for all of us (family), and since then no more “cry for help” events.