Who can the userbase engage with at Microsoft to change this?
1 Like
Yes, same problem on Windows with an iPhone 15 Pro.
Complains thereās not enough power and disconnects. Then repeats the cycle.
1 Like
There is a seperate thread about iPhones not connecting, from way back.
1 Like
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.
1 Like
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,
1 Like
Found it, I have the ticket now. Weāll continue there. 
1 Like
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.
1 Like
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.
4 Likes
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.
1 Like
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.
1 Like
wouldnāt it be nice if USB-C standards were better enforced, and manufacturers followed them?
6 Likes
At least my personal perspective is that the spec allowing all these types of different cables with the same physical connector and no way to tell how they will behave is the problem.
This really is different than the āmonster hdmi cableā vs ābest buy brand HDMI cableā from 15 years ago.
This is one of those cases that the more expensive type C cable will be higher quality and be able to handle more optional things from the spec.
4 Likes
Unless youāre buying from Amazon, where hundreds of fake reviews can be easily bought and the cables could be $50 but still shit
5 Likes
USB-C is the most frustratingly awful connection āstandardā to troubleshoot because every cable and every port have a (mostly) undocumented compatibility set and (usually) have a boat load of technical and design quirks to deal with. āOne connector to rule them allā is both a great marketing slogan and a terrible way to actually design connections. 
3 Likes
Totally agree with you here. And Iām happy that I fiddle with linux since end 1992, because I know my way around Linux, and logs, and kernel ring buffer and stuff, and can see pretty fast if the cable works as expected.
But my test was pretty simple. I have one external NVMe enclosure that came with 2 cables: USB-C to USB-C, and USB-C to USB-A. These cables work with all my devices and showed absolutely no error in the kernel ring buffer.
I then took all the other cables, and checked the kernel ring buffer when I plugged them into 4 devices I have at home for testing: Raspberry PI 4, DVD Drive, Camera and SSD NVme and SSD S-ATA connector.
If that showed only 1 error in the kernel ring buffer while plugging in, I dumped it.
I used a similar approach testing the iPhone 15 issue. I have a verified and tested Samsung branded cable from a recent monitor purchase that I always use for connecting the iPhone to my desktop. When I was testing the Framework USB issue, I would test the laptop and then use the testing cable on the desktop to download any pictures that support wanted.
Final update on the issue for now: After 5 days of troubleshooting, Framework Support finally admitted that there is a known issue connecting iPhone 15s to Framework 16 laptops and that they are actively working on a solution. They do not have an exact date on a fix yet. Any further issues will be communicated via the Framework Community Forums. They also recommended not plugging in the iPhone 15 to the Framework to avoid any further issues. My opinion: It is not a great customer service experience to get a āthis is a known issue - please stand by and donāt use it for nowā response after 5 days of intensive research and troubleshooting.
5 Likes
I donāt see it anywhere in the posts here, but for those unaware - it seems they promoted the BIOS and driver bundle out of beta. Linked here Framework Laptop 16 BIOS and Driver Releases
5 Likes