03-10-2025 07:28 PM
As the title says, on my Galaxy A14 4G, I can no longer use a USB A to USB C cable for data transfer. It only supports charging. This is on two computers: a desktop running Windows 10 and a laptop running Ubuntu 22. Tried 6 different cables. What does work, however, is a USB C to USB C cable. Unfortunately, I only have a USB C port on my laptop, no on my desktop. The desktop supports USB A 3.0 ports. Upodating my PC with a dedicated USB C card is not an option, as I do not have PCIe slots available.
I've tried several options suggested in the internet, but none works in my case. This is too silly for words. Anyone knows a solution to this issue? Is is a problem caused by OneUI 7.0 or Android 15?
03-10-2025 07:31 PM
03-10-2025 10:03 PM
Yes, I did, but tapping the notification does not show the options (like it used to), instead it takes me to the battery status page in settings. It does, however, like I already said, work with a USB C to C cable.
other things tried, as suggested on several web sites:
1. changed the default USB Configuration from charging only to file transfer
2. deleted data and cache for the USB settings app, and restarted this app
3. installed the Smartwitch app on the Windows 10 PC and the drivers that come along with it
On a side note: when connecting the phone through a USB A to C cable, the phone doesn't appear as a device in the Windows Device Manager. So it seems there is no longer any communication or handshake possible between a computer and the phone since the update with USB A to C cables.
03-10-2025 10:04 PM
ETA: I also rebooted the phone and the PC several times after making changes.
yesterday
My wife had the same issue today. I had to go into developer mode on the phone and set the USB default to transfer files. I just googled" how to set default USB settings on Samsung Galaxy". there were a few good YouTube videos on this.
yesterday
I had the same problem and got the same thing when tapping on the notification. I had to change it from the developer mode on the phone. See my notes in a previous reply. very frustrating to have this happen after an update without any notification.
4 hours ago
Yes, I've seen those videos as well, but unfortunately in my case they didn't resolve anything. Meanwhile I've been in contact with Samsung, and they confirm that it is a problem with some models after updating to Android 15. Will have to wait for a software update (if ever).