Bug 493795 - Device Name Input Field in Settings Is Broken
Summary: Device Name Input Field in Settings Is Broken
Status: RESOLVED DUPLICATE of bug 494110
Alias: None
Product: kdeconnect
Classification: Applications
Component: android-application (other bugs)
Version First Reported In: unspecified
Platform: Android Android 14.x
: NOR normal
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-09-28 21:00 UTC by franske2000
Modified: 2024-10-30 14:01 UTC (History)
3 users (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 franske2000 2024-09-28 21:00:07 UTC
SUMMARY
When entering text in the "Device name" input field in the app settings on Android (`v1.32.2`), text that is already typed is copied on every insertion of a new character. For example when the text "ph" is already there and the user types "o", the result is "phpho" instead of the expected "pho". I've tested this on both a OnePlus 5T running LineageOS (Android 14) and on a OnePlus Nord 2T 5G (Android 14). It is only possible to set the correct name by typing it somewhere else, copying it and pasting it entirely at once in the input field.

STEPS TO REPRODUCE
1. Go to the app settings in the Android app
2. Select "Device name"
3. Type something and observe the incorrect behavior in the input field

OBSERVED RESULT
Previous text is copied on every keystroke.

EXPECTED RESULT
Normal insertion behavior for text.

SOFTWARE/OS VERSIONS
Android: LineageOS 21 (Android 14) on OnePlus 5T
Android: Oxygen OS (Android 14) on OnePlus Nord 2T 5G
KDE Connect Android: 1.32.2

ADDITIONAL INFORMATION
/
Comment 1 Lukas ThyWalls 2024-10-23 22:06:32 UTC
Hello.

Same issue here, in my case using AnySoftKeyboard as Keyboard.

KDE Connect version: 1.32.7 (from F-Droid)

Also this is a duplicated of 494110 https://bugs.kde.org/show_bug.cgi?id=494110

Thanks.
Comment 2 Filip 2024-10-30 14:01:18 UTC

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