USB Tethering doesn't work after I updated my android phone to Android 16

Ask Fedora
, , , ,
1

I’ve been using USB Tethering on Fedora 42 KDE without issues ever, it was always smooth and an alternative to using my slow WIFI card which only supports 2.4Ghz networks. However, today I updated my phone, and with that update it also received Android 16, and now USB Tethering stopped working entirely. I tested with another phone (not mine) that has Android 15 and it works, what can I do?

EDIT:
Yes, I tried disabling tethering hardware acceleration in developer options, same with USB Debugging. I also tried setting IPv4 to manual, none of that worked.

2

There where firmware updates also on Fedora side, did you upgrade your system lately?

What is the Hardware of your F42?

3

Hi there, I updated a few days ago, my current kernel version is 6.18.16. With hardware you mean my computer’s hardware in general or something more specific?

4

Check again mobile settings – hotspot and tethering – USB tethering is enabled (make sure you connect before usb cable to fedora system) .After that set file sharing or whatever you want to use

5

Already tried that, doesn’t work. Again; it worked before the android update, with the settings I had and everything, now with android 16, it just stays connecting but it never connects.

6

in an 2cd terminal run

sudo dmesg -w

something usefull ?

===

install android-tools and try to connect via

adb shell

7

dmesg only shows me the message of the phone getting connected to my computer with rndis_host. Not sure about what to do with adb

8

USB connection check

with

adb devices (lists an usb connected phone)

and/or

adb shell (sort of ssh to the phone)

see (as an starting point)

1 Like
9

I’ve been trying, changed from rndis to ncm, tried to establish the connection manually through it, and it just doesn’t work for some reason.

10

When you try with adb as proposed above, you might get error messages in the terminal which could help to solve your issue.

11

USB Tethering is working fine here with Android 16.

leigh@fedora:~$ nmcli
enp5s0f3u2: connected to Wired connection 2
        "Google Pixel 8a"
        ethernet (cdc_ncm), 26:A2:3E:7D:BE:80, hw, mtu 1500
        ip4 default
        inet4 10.114.35.193/24
        route4 10.114.35.0/24 metric 100
        route4 default via 10.114.35.53 metric 100
        inet6 fe80::fd6e:b682:1f0a:742/64
        route6 fe80::/64 metric 1024

lo: connected (externally) to lo
        "lo"
        loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
        inet4 127.0.0.1/8
        inet6 ::1/128

enp2s0: disconnected
        "Realtek RTL8125 2.5GbE"
        1 connection available
        ethernet (r8169), 74:56:3C:05:F6:9F, autoconnect, hw, mtu 1500

wlo1: unavailable
        "Intel 6 AX200"
        wifi (iwlwifi), 32:C0:01:97:9A:83, sw disabled, hw, mtu 1500

DNS configuration:
        servers: 10.114.35.53
        interface: enp5s0f3u2

Use "nmcli device show" to get complete information about known devices and
"nmcli connection show" to get an overview on active connection profiles.

Consult nmcli(1) and nmcli-examples(7) manual pages for complete usage details.

leigh@fedora:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 004: ID 152a:8750 Thesycon Systemsoftware & Consulting GmbH D10s
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 0bda:0411 Realtek Semiconductor Corp. Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth
Bus 003 Device 005: ID 18d1:4eeb Google Inc. Pixel 8a
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub


leigh@fedora:~$ inxi -S
System:
  Host: mpd-pc Kernel: 6.19.8-300.fc44.x86_64 arch: x86_64 bits: 64
  Desktop: Cinnamon v: 6.6.7 Distro: Fedora Linux 44 (Cinnamon Prerelease)
2 Likes
12

Without doing anything with adb? No particular settings taken into account?

13

Take in consideration that the OP uses KDE and that they still use F42!

14

It’s plug and play

  1. Connect phone using USB-C lead.
  2. Enable tethering in phone settings.
  3. NetworkManager automatically uses the new connection.
15

For me, it keeps trying to get the IP configuration, which is never received, giving me an IP not found error in return…

16

reboot your mobile to set ip