WIFI keeps reconnecting frequently

AmirHZKarimi · 3 January 2024 18:42

I use my Android phone`s WIFI hotspot, But it frequently disconnects for ~5-10 seconds and usually automatically reconnects.

I found the logs when WIFI disconnected but I don’t know what the problem is.
I’ll appreciate it if someone checks it and tells me what’s wrong.

$ journalctl -xef
Jan 03 21:52:10 spaceship kernel: perf: interrupt took too long (2512 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
Jan 03 21:53:05 spaceship rtkit-daemon[1390]: Supervising 9 threads of 6 processes of 1 users.
Jan 03 21:53:05 spaceship rtkit-daemon[1390]: Supervising 9 threads of 6 processes of 1 users.
Jan 03 21:53:21 spaceship rtkit-daemon[1390]: Supervising 9 threads of 6 processes of 1 users.
Jan 03 21:53:21 spaceship rtkit-daemon[1390]: Supervising 9 threads of 6 processes of 1 users.
Jan 03 21:53:26 spaceship kernel: wlo1: Connection to AP ea:36:aa:20:0d:b4 lost
Jan 03 21:53:26 spaceship wpa_supplicant[675]: wlo1: CTRL-EVENT-DISCONNECTED bssid=ea:36:aa:20:0d:b4 reason=4 locally_generated=1
Jan 03 21:53:26 spaceship NetworkManager[18785]: <info>  [1704306206.9437] device (wlo1): supplicant interface state: completed -> disconnected
Jan 03 21:53:26 spaceship NetworkManager[18785]: <info>  [1704306206.9438] device (p2p-dev-wlo1): supplicant management interface state: completed -> disconnected
Jan 03 21:53:27 spaceship NetworkManager[18785]: <info>  [1704306207.0103] device (wlo1): supplicant interface state: disconnected -> scanning
Jan 03 21:53:27 spaceship NetworkManager[18785]: <info>  [1704306207.0104] device (p2p-dev-wlo1): supplicant management interface state: disconnected -> scanning
Jan 03 21:53:27 spaceship wpa_supplicant[675]: wlo1: SME: Trying to authenticate with ea:36:aa:20:0d:b4 (SSID='rocket ' freq=2412 MHz)
Jan 03 21:53:27 spaceship kernel: wlo1: authenticate with ea:36:aa:20:0d:b4
Jan 03 21:53:27 spaceship kernel: wlo1: 80 MHz not supported, disabling VHT
Jan 03 21:53:27 spaceship NetworkManager[18785]: <info>  [1704306207.8610] device (wlo1): supplicant interface state: scanning -> authenticating
Jan 03 21:53:27 spaceship NetworkManager[18785]: <info>  [1704306207.8611] device (p2p-dev-wlo1): supplicant management interface state: scanning -> authenticating
Jan 03 21:53:27 spaceship kernel: wlo1: send auth to ea:36:aa:20:0d:b4 (try 1/3)
Jan 03 21:53:27 spaceship wpa_supplicant[675]: wlo1: Trying to associate with ea:36:aa:20:0d:b4 (SSID='rocket ' freq=2412 MHz)
Jan 03 21:53:27 spaceship kernel: wlo1: authenticated
Jan 03 21:53:27 spaceship kernel: wlo1: associate with ea:36:aa:20:0d:b4 (try 1/3)
Jan 03 21:53:27 spaceship NetworkManager[18785]: <info>  [1704306207.8652] device (wlo1): supplicant interface state: authenticating -> associating
Jan 03 21:53:27 spaceship NetworkManager[18785]: <info>  [1704306207.8653] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating
Jan 03 21:53:27 spaceship kernel: wlo1: RX AssocResp from ea:36:aa:20:0d:b4 (capab=0x1431 status=0 aid=4)
Jan 03 21:53:27 spaceship wpa_supplicant[675]: wlo1: Associated with ea:36:aa:20:0d:b4
Jan 03 21:53:27 spaceship wpa_supplicant[675]: wlo1: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jan 03 21:53:27 spaceship kernel: wlo1: associated
Jan 03 21:53:27 spaceship NetworkManager[18785]: <info>  [1704306207.8806] device (wlo1): supplicant interface state: associating -> associated
Jan 03 21:53:27 spaceship NetworkManager[18785]: <info>  [1704306207.8806] device (p2p-dev-wlo1): supplicant management interface state: associating -> associated
Jan 03 21:53:27 spaceship NetworkManager[18785]: <info>  [1704306207.8947] device (wlo1): supplicant interface state: associated -> 4way_handshake
Jan 03 21:53:27 spaceship NetworkManager[18785]: <info>  [1704306207.8948] device (p2p-dev-wlo1): supplicant management interface state: associated -> 4way_handshake
Jan 03 21:53:27 spaceship wpa_supplicant[675]: wlo1: WPA: Key negotiation completed with ea:36:aa:20:0d:b4 [PTK=CCMP GTK=CCMP]
Jan 03 21:53:27 spaceship wpa_supplicant[675]: wlo1: CTRL-EVENT-CONNECTED - Connection to ea:36:aa:20:0d:b4 completed [id=0 id_str=]
Jan 03 21:53:27 spaceship wpa_supplicant[675]: wlo1: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-45 noise=9999 txrate=26000
Jan 03 21:53:27 spaceship NetworkManager[18785]: <info>  [1704306207.9838] device (wlo1): supplicant interface state: 4way_handshake -> completed
Jan 03 21:53:27 spaceship NetworkManager[18785]: <info>  [1704306207.9840] device (wlo1): ip:dhcp4: restarting
Jan 03 21:53:27 spaceship NetworkManager[18785]: <info>  [1704306207.9841] dhcp4 (wlo1): canceled DHCP transaction
Jan 03 21:53:27 spaceship NetworkManager[18785]: <info>  [1704306207.9841] dhcp4 (wlo1): activation: beginning transaction (timeout in 45 seconds)
Jan 03 21:53:27 spaceship NetworkManager[18785]: <info>  [1704306207.9841] dhcp4 (wlo1): state changed no lease
Jan 03 21:53:27 spaceship NetworkManager[18785]: <info>  [1704306207.9841] dhcp4 (wlo1): activation: beginning transaction (timeout in 45 seconds)
Jan 03 21:53:27 spaceship NetworkManager[18785]: <info>  [1704306207.9841] device (p2p-dev-wlo1): supplicant management interface state: 4way_handshake -> completed
Jan 03 21:53:28 spaceship NetworkManager[18785]: <info>  [1704306208.0091] dhcp4 (wlo1): state changed new lease, address=192.168.104.93
Jan 03 21:53:28 spaceship dbus-daemon[607]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.355' (uid=0 pid=18785 comm="/usr/bin/NetworkManager --no-daemon")
Jan 03 21:53:28 spaceship systemd[1]: Starting Network Manager Script Dispatcher Service...
░░ Subject: A start job for unit NetworkManager-dispatcher.service has begun execution
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit NetworkManager-dispatcher.service has begun execution.
░░ 
░░ The job identifier is 8306.
Jan 03 21:53:28 spaceship dbus-daemon[607]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jan 03 21:53:28 spaceship systemd[1]: Started Network Manager Script Dispatcher Service.
░░ Subject: A start job for unit NetworkManager-dispatcher.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit NetworkManager-dispatcher.service has finished successfully.
░░ 
░░ The job identifier is 8306.
Jan 03 21:53:30 spaceship rtkit-daemon[1390]: Supervising 8 threads of 5 processes of 1 users.
Jan 03 21:53:30 spaceship rtkit-daemon[1390]: Supervising 8 threads of 5 processes of 1 users.
Jan 03 21:53:38 spaceship systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.

System info:

$ inxi --verbosity=7 --filter --no-host --width                                                                                                                                                                                                                      
System:
  Kernel: 6.6.8-2-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc Desktop: GNOME v: 45.2 tk: GTK v: 3.24.38 wm: gnome-shell
    dm: GDM v: 45.0.1 Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Laptop System: ASUSTeK product: VivoBook_ASUSLaptop X512JP_R564JP
    v: 1.0 serial: <superuser required>
  Mobo: ASUSTeK model: X512JP v: 1.0 serial: <superuser required>
    UEFI: American Megatrends v: X512JP.308 date: 05/26/2021
Battery:
  ID-1: BAT0 charge: 22.9 Wh (100.0%) condition: 22.9/37.1 Wh (61.5%)
    volts: 7.8 min: 7.8 model: ASUSTeK ASUS Battery type: Li-ion serial: N/A
    status: not charging cycles: 614
  Device-1: hidpp_battery_0 model: Logitech G603 Wireless Gaming Mouse
    serial: <filter> charge: 100% (should be ignored) rechargeable: yes
    status: discharging
  Device-2: hidpp_battery_1 model: Logitech K780 Multi-Device Wireless
    Keyboard serial: <filter> charge: 100% (should be ignored)
    rechargeable: yes status: discharging
Memory:
  System RAM: total: 16 GiB note: est. available: 15.43 GiB
    used: 9.04 GiB (58.6%)
  RAM Report: permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: quad core model: Intel Core i7-1065G7 bits: 64 type: MT MCP
    smt: enabled arch: Ice Lake rev: 5 cache: L1: 320 KiB L2: 2 MiB L3: 8 MiB
  Speed (MHz): avg: 3476 high: 3692 min/max: 400/3900 cores: 1: 3419 2: 3692
    3: 3211 4: 3685 5: 3120 6: 3502 7: 3593 8: 3587 bogomips: 23968
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_perfmon art avx avx2 avx512_bitalg avx512_vbmi2
    avx512_vnni avx512_vpopcntdq avx512bw avx512cd avx512dq avx512f avx512ifma
    avx512vbmi avx512vl bmi1 bmi2 bts clflush clflushopt cmov constant_tsc
    cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64 dtherm dts epb ept ept_ad erms
    est f16c flexpriority flush_l1d fma fpu fsgsbase fsrm fxsr gfni ht hwp
    hwp_act_window hwp_epp hwp_notify hwp_pkg_req ibpb ibrs ibrs_enhanced ida
    intel_pt invpcid lahf_lm lm mca mce md_clear mmx monitor movbe msr mtrr
    nonstop_tsc nopl nx ospke pae pat pbe pcid pclmulqdq pdcm pdpe1gb pebs pge
    pku pln pni popcnt pse pse36 pts rdpid rdrand rdseed rdtscp rep_good sdbg
    sep sha_ni smap smep split_lock_detect ss ssbd sse sse2 sse4_1 sse4_2
    ssse3 stibp syscall tm tm2 tpr_shadow tsc tsc_adjust tsc_deadline_timer
    tsc_known_freq umip vaes vme vmx vnmi vpclmulqdq vpid x2apic xgetbv1 xsave
    xsavec xsaveopt xsaves xtopology xtpr
Graphics:
  Device-1: Intel Iris Plus Graphics G7 vendor: ASUSTeK driver: i915 v: kernel
    arch: Gen-11 ports: active: HDMI-A-1 off: eDP-1 empty: none bus-ID: 00:02.0
    chip-ID: 8086:8a52 class-ID: 0300
  Device-2: NVIDIA GP108M [GeForce MX330] vendor: ASUSTeK driver: nvidia
    v: 545.29.06 arch: Pascal pcie: speed: 5 GT/s lanes: 4 bus-ID: 02:00.0
    chip-ID: 10de:1d16 class-ID: 0302
  Device-3: IMC Networks USB2.0 HD UVC WebCam driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 1-6:4 chip-ID: 13d3:56dd
    class-ID: 0e02 serial: <filter>
  Display: x11 server: X.org v: 1.21.1.10 with: Xwayland v: 23.2.3
    compositor: gnome-shell driver: X: loaded: modesetting,nvidia
    alternate: fbdev,nouveau,nv,vesa dri: iris gpu: i915 display-ID: :1
    screens: 1
  Screen-1: 0 s-res: 2560x1440 s-size: <missing: xdpyinfo>
  Monitor-1: HDMI-A-1 mapped: HDMI-1 pos: primary model: Samsung LC32G5xT
    serial: <filter> res: 2560x1440 hz: 60 dpi: 93 size: 698x393mm (27.48x15.47")
    diag: 806mm (31.7") modes: max: 3840x2160 min: 720x400
  Monitor-2: eDP-1 note: disabled model: Najing CEC Panda 0x0046
    res: 2560x1440 dpi: 142 size: 344x194mm (13.54x7.64") diag: 395mm (15.5")
    modes: 1920x1080
  API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0
    drv: nvidia device: 1 drv: iris device: 3 drv: swrast gbm: drv: kms_swrast
    surfaceless: drv: nvidia x11: drv: iris inactive: wayland,device-2
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 23.1.9-manjaro1.1
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel Iris Plus Graphics (ICL
    GT2) device-ID: 8086:8a52
Audio:
  Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:34c8
    class-ID: 0403
  API: ALSA v: k6.6.8-2-MANJARO status: kernel-api with: aoss
    type: oss-emulator
  Server-1: sndiod v: N/A status: off
  Server-2: JACK v: 1.9.22 status: off
  Server-3: PipeWire v: 1.0.0 status: off
  Server-4: PulseAudio v: 16.1 status: active with: pulseaudio-alsa
    type: plugin
Network:
  Device-1: Intel Ice Lake-LP PCH CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 00:14.3 chip-ID: 8086:34f0 class-ID: 0280
  IF: wlo1 state: up mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: link
  IF-ID-1: br-b117841c15c2 state: down mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IF-ID-2: br-f6fd13f2a801 state: down mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IF-ID-3: docker0 state: down mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IF-ID-4: nekoray-tun state: unknown speed: 10000 Mbps duplex: full mac: N/A
  IP v4: <filter> scope: global broadcast: <filter>
  IP v6: <filter> virtual: stable-privacy proto kernel_ll scope: link
  WAN IP: <filter>
Bluetooth:
  Device-1: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) driver: btusb v: 0.8
    type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 1-10:5 chip-ID: 8087:0aaa
    class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 2 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 1.2 TiB used: 173.69 GiB (14.1%)
  ID-1: /dev/nvme0n1 vendor: Western Digital model: PC SN520
    SDAPNUW-256G-1202 size: 238.47 GiB speed: 15.8 Gb/s lanes: 2 tech: SSD
    serial: <filter> fw-rev: 20200000 temp: 44.9 C scheme: GPT
  ID-2: /dev/sda vendor: Western Digital model: WD10SPZX-80Z10T2
    size: 931.51 GiB speed: 6.0 Gb/s tech: HDD rpm: 5400 serial: <filter>
    fw-rev: 1A04 scheme: GPT
  ID-3: /dev/sdb model: N/A size: 58.98 GiB type: USB rev: 3.2 spd: 5 Gb/s
    lanes: 1 tech: N/A serial: <filter> scheme: MBR
  Message: No optical or floppy data found.
Partition:
  ID-1: / size: 48.91 GiB used: 27.18 GiB (55.6%) fs: ext4 dev: /dev/nvme0n1p5
    label: N/A uuid: de9e18aa-5696-4157-ae0b-ffa1c00ccc57
  ID-2: /boot/efi size: 187.1 MiB used: 6.2 MiB (3.3%) fs: vfat
    dev: /dev/nvme0n1p1 label: N/A uuid: 9A68-D697
  ID-3: /home size: 56.47 GiB used: 39.3 GiB (69.6%) fs: ext4
    dev: /dev/nvme0n1p2 label: Manjaro Home
    uuid: e34ad995-627f-4b4c-9cb0-f6c330f6c42c
  ID-4: /mnt/Storage size: 495.29 GiB used: 107.2 GiB (21.6%) fs: ext4
    dev: /dev/sda5 label: Storage uuid: 217ca017-5f87-4196-8620-07a6ee35b35d
Swap:
  ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/sda2 label: Swap uuid: b973274e-364b-4b2b-b26b-75bf1f4ad671
Unmounted:
  ID-1: /dev/nvme0n1p3 size: 16 MiB fs: <superuser required> label: N/A
    uuid: N/A
  ID-2: /dev/nvme0n1p4 size: 69.98 GiB fs: ntfs label: Windows
    uuid: 8CD2B4DFD2B4CF28
  ID-3: /dev/nvme0n1p6 size: 40 GiB fs: ext4 label: N/A
    uuid: b5d28cca-8509-458d-ac5a-8fa0abd66ba8
  ID-4: /dev/sda1 size: 416 GiB fs: ntfs label: N/A uuid: 575374D971717453
  ID-5: /dev/sdb1 size: 3.45 GiB fs: iso9660
  ID-6: /dev/sdb2 size: 4 MiB fs: vfat label: MISO_EFI uuid: D0A3-C7FC
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 12 rev: 2.0
    speed: 480 Mb/s lanes: 1 chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 1-3:2 info: Logitech Unifying Receiver type: keyboard,mouse,HID
    driver: logitech-djreceiver,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s
    lanes: 1 power: 98mA chip-ID: 046d:c52b class-ID: 0300
  Device-2: 1-4:3 info: Logitech Lightspeed Receiver type: keyboard,mouse,HID
    driver: logitech-djreceiver,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s
    lanes: 1 power: 98mA chip-ID: 046d:c539 class-ID: 0300
  Device-3: 1-6:4 info: IMC Networks USB2.0 HD UVC WebCam type: video
    driver: uvcvideo interfaces: 2 rev: 2.0 speed: 480 Mb/s lanes: 1 power: 500mA
    chip-ID: 13d3:56dd class-ID: 0e02 serial: <filter>
  Device-4: 1-10:5 info: Intel Bluetooth 9460/9560 Jefferson Peak (JfP)
    type: bluetooth driver: btusb interfaces: 2 rev: 2.0 speed: 12 Mb/s lanes: 1
    power: 100mA chip-ID: 8087:0aaa class-ID: e001
  Hub-2: 2-0:1 info: super-speed hub ports: 6 rev: 3.1 speed: 10 Gb/s
    lanes: 1 chip-ID: 1d6b:0003 class-ID: 0900
  Device-1: 2-1:2 info: N/A type: mass storage driver: usb-storage
    interfaces: 1 rev: 3.2 speed: 5 Gb/s lanes: 1 power: 304mA chip-ID: 24a9:205a
    class-ID: 0806 serial: <filter>
Sensors:
  System Temperatures: cpu: 68.0 C mobo: N/A
  Fan Speeds (rpm): cpu: 3500
Info:
  Processes: 341 Uptime: 3h 14m wakeups: 0 Init: systemd v: 254
  default: graphical Compilers: gcc: 13.2.1 clang: 16.0.6 Packages: pm: pacman
  pkgs: 1335 Shell: Zsh v: 5.9 running-in: gnome-terminal inxi: 3.3.31

Nachlese · 3 January 2024 19:03

use it like a regular wireless network
the above output looks strange to me because of:
(p2p-dev-wlo1)
instead of the normal name of the wireless network interface
which is/should be just

wlo1

The regular disconnects could also stem from power saving applied to your network adapter.
But I would not know how to diagnose this since I do not run Manjaro at the moment.

AmirHZKarimi · 3 January 2024 19:09

Thanks for your quick reply.
I disabled wifi power saving.

cat /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf
[connection]
wifi.powersave = 0

Nachlese · 3 January 2024 19:14

… then there is the other issue (I think it may be one - I’m not sure …):
why is the interface called:
p2p-dev-wlo1
instead of just:
wlo1

Check your connection settings - possibly delete the network and re-create it again?

scan for networks, select it, give credentials, connect …
don’t know where that p2p portion of the name comes from or what it indicates

DeLinuxCo · 3 January 2024 19:35

A quick suggestion, unless you are actually coonecting directly to a modem, I would disable modem-manager;

sudo systemctl stop ModemManager

sudo systemctl disable ModemManager

Restart and test…

AmirHZKarimi · 5 January 2024 15:54

I disabled ModemManager but the problem exists.

Nachlese · 5 January 2024 16:09

I still think that you should delete the connection
and create a new one.

Did you try?
This only takes a few seconds.

You need a standard normal connection to your phone’s hotspot, just like for any normal home router - not anything p2p

AmirHZKarimi · 5 January 2024 19:35

They aren’t two different interfaces?

Anyway, Looks like I do not have this interface.

ifconfig
br-b117841c15c2: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.20.0.1  netmask 255.255.0.0  broadcast 172.20.255.255
        ether 02:42:e0:16:ff:d8  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

br-f6fd13f2a801: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.26.0.1  netmask 255.255.0.0  broadcast 172.26.255.255
        ether 02:42:56:a2:ac:a6  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        ether 02:42:ca:a7:47:a3  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 613187  bytes 45709553 (43.5 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 613187  bytes 45709553 (43.5 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

nekoray-tun: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST>  mtu 9000
        inet 172.19.0.1  netmask 255.255.255.240  destination 172.19.0.1
        inet6 fe80::d82f:13c2:56e8:50d7  prefixlen 64  scopeid 0x20<link>
        unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 500  (UNSPEC)
        RX packets 473839  bytes 125189391 (119.3 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 497031  bytes 63870136 (60.9 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlo1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.104.93  netmask 255.255.255.0  broadcast 192.168.104.255
        inet6 fe80::d798:986c:1f95:5186  prefixlen 64  scopeid 0x20<link>
        ether 08:d2:3e:61:e4:00  txqueuelen 1000  (Ethernet)
        RX packets 366010  bytes 384058571 (366.2 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 209561  bytes 81400407 (77.6 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Nachlese · 5 January 2024 20:04

I don’t know - but this is in the log you posted:

I’m not smart enough, do not know enough, to tell where this p2p-dev-wlo1 comes from.
I just noticed it as “odd”.

Again:
it is easy to delete the stored connection
and then re-create it anew

it’s like 15 seconds to see whether this changes anything …

I have no other ideas based upon what I know (not much) and what I see (the logs).

checking for what the “reason=4” disconnect might mean I found:

The reason is that the network at some point (very soon, very often) stop transmitting data. So the main reason for disconnections is just reason=4 Disassociated due to inactivity - Client session timeout exceeded.

inactivity - Client timeout exceeded …

To me that seems like your phone disconnects you after some time of inactivity.
… maybe the phone is going to sleep - saving power when not connected to the charger? …
don’t know

that is all I can contribute

Whenever I use my phone to provide internet, I rather use USB tethering than the WiFi Hotspot.

AmirHZKarimi · 5 January 2024 20:51

Thank you for your help. I appreciate it.

I deleted the connection several times by changing the hotspot name, password, channel, frequency, etc.
But the problem exists.

About power saving, I don’t think so. Because it re-connects automatically usually immediately.

But is there any option to increase the value of inactivity timeout to prevent it from disconnecting?

Nachlese · 5 January 2024 20:59

I don’t know - it may depend on the type of phone and (if Android) on the Android version it is running.
It was just a guess anyway.

I wonder what the actual problem is, then …

DeLinuxCo · 6 January 2024 00:04

I found this at the endeavourOS forum to disable power saving in wifi run the following command:
echo 'options iwlwifi power_save=0 d0i3_disable=0 uapsd_disable=0' | sudo tee /etc/modprobe.d/iwlwifi.conf

then reboot…

cscs · 6 January 2024 00:44

Funny … because since a long time intel wireless has a secondary module iwlmvm where the real powersaving control is.

https://wiki.archlinux.org/title/Network_configuration/Wireless#Cause_#6

For module iwlwifi (And those options);

power_save is 0 by default
uapsd_disable=0 is enabling a powersave feature while expected to increase latency
d0i3_disable simply does not exist as on option for modern iwlwifi module (since kernel 5.4!) and if functional, setting it to 0 would have been another enabled powersave feature, expected to diminish maximum throughput.

( aw, its @tbg copy-pasting without any analysis again, just different forum )

[ For some dissection of the linked ‘solution’…
Its possible the reloading of the modules was itself a fix … but its also worth noting that the string would have unloaded 4 modules, including iwlmvm, but only restarted iwlwifi… which is another possibility for the ‘solve’ … it may be worth noting also that the configuration options highlighted being placed in a perpetual configuration is not marked for the solution. Which makes sense, because again, the above options would not be very effective. ]