https://bugs.kde.org/show_bug.cgi?id=474318
--- Comment #2 from k...@efreakbnc.net --- (In reply to Urs Fleisch from comment #1) > - An apk hosted on Kid3's SourceForge repo, it is built with Qt 6.5.1, I > would try this: > https://prdownloads.sourceforge.net/kid3/kid3-3.9.4-android.apk?download 1. This version works, but has a few minor visual glitches with the new styles A. the textbox seems to be cut off when adding fields B. the field name looks like an internal id3 identifier instead of a human readable tag name (aART vs Album Artist) C. The app opens with the directory browser open for some reason. This would be ok if not for the fact that it's empty due to 3 below 2. There's also a functional glitch: I told the automatic import to import my new metadata into tag3, but tag3 is nowhere to be seen after import. 3. Design issue: I'd suggest that at least on Android the default directory on first run should be the main sdcard, the music directory, or some other directory, as it currently defaults to an empty directory in the app's private data that no other apps can access (/data/data/...) 4. Visual/settings issue: reccomend defaulting appearance to material/system; currently it's blank, and for those on dark mode it takes a restart of the app to get dark mode on 5. Suggest adding a 3rd style to mobile if possible/trivial, maybe a default qt style or a win3-inspired style. The material styles don't work well with qt apps (or aother apps, honestly) on mobile (nor do gradients seem particularly material to me) 6. I'm getting beyond the original purpose of this issue (I already am far beyond, so why not?), but I'd also suggest having two columns where possible; on my 10" android device there's enough width for a double column view that shows both the original value and new value for each tag. 7. The browse up button closes the browse sidebar. The sidebar should ideally open underneath the toolbar, and interacting with the toolbar shouldn't close the sidebar. 8. The select all/none button has no feedback other than the filenames. If I happen to be in a directory without media files, it just feels like it's not working, as there's no feedback. 9. Would be nice if I could select a directory full of files by checking the directory; currently the checkbox on directories seems to do nothing. > - I have Kid3 in the official FDroid, it is built with Qt 5.15 (FDroid > dictates that Qt must be built from source, so I have not upgraded this to > Qt 6 yet): https://f-droid.org/en/packages/net.sourceforge.kid3/ This version actually also has the same error for me. I installed it first as it was easier than setting up Obtainium with a new URL (just had to pick the version from the fdroid version list) This version links to https://invent.kde.org/multimedia/kid3/-/issues for bug reports, which doesn't tell me until after I register and sign in[^1] that I shouldn't report bugs there. If you're using fastlane for metadata, I believe you can update this yourself, otherwise it's an fdroid issue. > Note however, that this import corresponds to "File/Automatic Import" and not > "File/Import from MusicBrainz Fingerprint" in the desktop version of Kid3, > i.e. it does not use AcoustID but matches the albums by artist and album tag > frames, which have already to be set, and the tracks are matched using length > and file name heuristics. Suggestion: import from MBID or acoustid in tags as well. Some of my music has MBID tagged, but I never finished with Picard. I can somewhat trivially automate adding acoustid using termux, then import to kid3 for the rest. ---------- [^1]: using 3 separate apps: password manager, email client and browser. Why does kde need to validate my email address? Sometimes I really am just *reporting a bug* and not looking for actual support. Yes, I know you're not in charge, I'm just annoyed... Please forward this feedback if you know where it should go, as I don't know. It was suggested that I contact developers on IRC to find out where to file a bug... Not really good UX to involve a fourth application on a mobile device. Unfortunately, I'm currently without a PC, so I'm stuck doing things like this with an inferior Android interface. You can close the bug if you'd like, I would have done so, but it's not fixed (out of your control) and I'm not sure what the status should be to get kde to fix their version. -- You are receiving this mail because: You are watching all bug changes.
