SUMMARY I have KDE Connect 1.32.9 from F-Droid on a Motorola Edge 40 Pro with Android 14. If I go into the settings and try to change the device name (or even just leave it as it is and press rename) I just get a pop-up saying "invalid device name". Also, the name shown in the app isn't correct, KDE Connect on my PC shows the phone as being named "motorola edge 40 pro", but the device name shown in KDE connect on the phone is "moto g play - 2024".
I would like to report the exact same bug. I'm using a Pixel 8 Pro. Same behavior. Cannot rename the device on the Android. Please fix / address. Thankyou.
*** Bug 495579 has been marked as a duplicate of this bug. ***
I'm using a Samsung A12 (android 13), same behavior.
Same issue, invalid device name error when attempting to rename device. Fairphone4, LineageOS21 (Android 14). There is also some strange behaviour with Autofill when typing the new device name - with every character typed, the word suggestion is filled in. eg: T TTe TTeTes TTeTesTest Unsure if it is related, but maybe it helps.
Also experiencing the same bug, Samsung XCover 6 Pro (Android 14)
Version: 1.32.9 Installed from: F-Droid Device: Samsung Galaxy Tab A9+ 5G (SM-X216B) Same issue as others, trying to edit device name gives error "Invalid device name". Even if I don't change anything and just press "rename". Let me know if you need any more info.
TLDR: Problem not present in 1.32.5 Hi, I ran into this problem setting up a new phone, a Samsung Galaxy Z Fold 5 running OneUI 6.1.1 / Android 14. I was installing the latest version 1.32.9 from F-Droid. Any name I entered, including just accepting the default, would result in "invalid device name." I didn't run into this problem with my older phone, so I uninstalled 1.32.9 and installed two versions back, 1.32.5 from F-Droid. I was able to change the name as usual. This suggests that the problem is in a recent commit. Afterwards, I updated to 1.32.9 with no issues. The new name stuck, but I haven't tried to change it since. I was not able to check if the release in-between (1.32.7) also has the same issue. I hope this information is useful.
future10se from comment #7) > TLDR: Problem not present in 1.32.5 > > Hi, I ran into this problem setting up a new phone, a Samsung Galaxy Z Fold > 5 running OneUI 6.1.1 / Android 14. I was installing the latest version > 1.32.9 from F-Droid. > > Any name I entered, including just accepting the default, would result in > "invalid device name." I didn't run into this problem with my older phone, > so I uninstalled 1.32.9 and installed two versions back, 1.32.5 from > F-Droid. I was able to change the name as usual. This suggests that the > problem is in a recent commit. > > Afterwards, I updated to 1.32.9 with no issues. The new name stuck, but I > haven't tried to change it since. > > I was not able to check if the release in-between (1.32.7) also has the same > issue. I hope this information is useful. Thank you for this workaround, I uninstalled/downgraded to 1.32.5 (from F-Droid repo) and was able to rename, then updated again.
This appears to be due to commit 8cb9a180 [1] "Migrate SettingsFragment to Kotlin" The original java version aborted device name change if the string was empty: > if (StringUtils.isBlank(name)) But in the kotlin version, the condition is reversed, device name change fails if the string is *not* empty: > if (!name.isNullOrBlank()) Indeed, 1.32.7 and 1.32.9 allow you to change device name to the empty string (which predictably breaks app's functionality). [1] https://invent.kde.org/network/kdeconnect-android/-/commit/8cb9a1809de64c94a577678c7c982398f3ed69eb