When connecting my Pixel 10 to my FW13, the USB connection is extremely unstable. It constantly disconnects and reconnects until Windows finally gives up and says the device is malfunctioning. I have USB-C ports in the rear two slots, a USB-A in the front left, and an HDMI in the front right.
I spent forever trying to debug this, and I found the weirdest solution: remove both USB-C adapters and connect the Pixel directly to the “hidden” USB-C port that the adapter would typically connect to. Interestingly, when I removed power from the other USB-C port but left the adapter in, the stability improved but was still poor.
This is probably one of these “computers have weird gremlins and USB-C is complicated” problems, but does anyone have any idea what’s really going on here? I don’t actually connect my phone very often—really just to very occasionally put big files on it for whatever reason—and I’ve never had any USB-C problems before with the laptop. More just curious.
Also, I tried different cables all with exactly the same results (high-quality ones, too—one from Apple and a couple Anker ones).
One thing you might try would be to use a USB C to USB A cable to connect your Pixel 10 to your Framework using your USB A port on your Framework. If that works better that might be a workaround. I don’t know what would cause your USB C to USB C problem but going from USB C to USB A might work better. Another thing to try would be to move one of your USB C expansion cards to one of the expansion card slots toward the front of the computer instead of the ones in the back of the computer (and try the USB C expansion card on both sides of the Framework). I prefer fixes to workarounds but if a workaround does work, it at least offers a way to get around a problem.
Thanks for the ideas! I did try a USB-A cable (I already have one of my ports configured for that), and it had the same symptoms. And yes, I do have AMD (7040).
You might want to try booting up your PC by using one of the “Live” Linux distributions to see if the problem you’re having with your Pixel might not be a hardware problem but might be a Windows glitch.
I use openSUSE Slowroll Linux and have no trouble connecting Pixel phones and transferring data between the Pixel phones and my Linux PC. I’ve connected to a Pixel 3 and Pixel 6 and never had any problems when connecting to several Linux PCs.
Many Linux versions allow you to boot up your Framework and try running Linux on it without installing Linux on your Frameworks drive or making any changes to Windows. This allows Linux to load from a bootable USB flash drive and run in RAM making no changes to your computer but allowing you to try using Linux and seeing what it is like to use it.
Linux makes very efficient use of RAM and cpu power so you may find that your Framework works faster with Linux than it does with Windows. Even if you are using Windows 11, I would still give Linux a try.
You can go to the Distrowatch website to read reviews of different versions of Linux as well as to find links to the websites for the various versions of Linux. When you go to one of the Linux distro websites, you will find detailed instructions for how to download Linux onto a USB flash drive and boot up your PC to try using Linux.
You could try using Fedora with KDE which is one of the Linux distros that Framework officially supports, but LMDE (Linux Mint Debian Edition) and MX-Linux work fine on Framework computers, too.
I always use AMD cpus and all of the various Linux PCs that I’ve used without any problems with several different Pixel phones have all had various AMD cpus.
I think it’s specifically an AMD Framework thing. Not AMD in general. Nor a Linux thing. If OP is experiencing similar problems as the thread I have linked to, I doubt there is any solution available.
Looks like it’s basically the same problem as that iPhone issue linked.
I haven’t tried using a different OS like one commentator suggested, but that wouldn’t really matter for my use-case, since I can already connect it just fine to other PCs. Even if it did work under Linux on my FW, it wouldn’t really be practical; it’s easier just to connect it to the other computers I own that do work instead of booting into a different OS each time (and besides, I’m running bitlocker, so the primary volume where all the files are wouldn’t be accessible without even more work, etc.). My goofy remove-all-the-dongles-and-connect-directly does seem to work, and while kind of stupid, is easier than dual-booting an alternate OS.
Since it does work on a Dell running W11 (not to mention various other Linux boxes), I suspect it’s a FW-specific issue (or at least an AMD-specific issue). Maybe they’ll be able to fix it in a bios update some day.