Bug 515168 - just upgraded to android 16 and now can't connect
Summary: just upgraded to android 16 and now can't connect
Status: RESOLVED DUPLICATE of bug 515167
Alias: None
Product: kde
Classification: I don't know
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Android Unspecified
: NOR major
Target Milestone: ---
Assignee: Unassigned bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-01-27 20:03 UTC by bsmiler
Modified: 2026-01-29 11:46 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bsmiler 2026-01-27 20:03:13 UTC
SUMMARY
Today when notified by Motorola of availability I upgraded to android 16 on my Motorola edge 60 fusion. On android 15 KDE 1.34 (Albert Vaca Cintora) worked fine. My old Moto G 5g plus with android 11 works fine too. But now on android 16 it cannot see any of my linux mint 21 boxes or other android phones - says no devices. Connecting manually by ip says ping failed, not found. Enablling MDNS or bluetooth does not help. Do you not support android 16? 

STEPS TO REPRODUCE
1. Install KDE 1.34 on Motorola edge 60 fusion with android 16
2. try to connect to another device
3. cry

OBSERVED RESULT

KDE Connect on android 16 cannot see any other devices on my network and can't be seen by them

EXPECTED RESULT

Connection :)

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: Mint 21
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

android 16
Comment 1 TraceyC 2026-01-29 11:46:07 UTC

*** This bug has been marked as a duplicate of bug 515167 ***