SUMMARY Elisa can't find my music, I tried the filesystem and os search STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
Can you find it with `baloosearch [some song filename]`?
(In reply to Nate Graham from comment #1) > Can you find it with `baloosearch [some song filename]`? How can I do that on android?
However you normally get a terminal on Android, I guess. However you said that Elisa can't find your music even when you use the filesystem search feature which doesn't use baloo at all, so I guess this was mis-filed to Baloo. Moving back to Elisa since the fault is more likely to be there.
Can confirm. When I click Hamburger -> Files, the app just displays the rotating loading symbol and doesn't list any files. It also doesn't list anything under Hamburger -> Tracks. Tried with flac, ogg, and mp3.
Forgot to mention I'm using Android 12 with CalyxOS 3.4.0
*** Bug 451344 has been marked as a duplicate of this bug. ***
After running `adb logcat` and pressing "Scan for New Music" I get these lines 06-13 15:24:37.089 21094 21128 D elisa : org.kde.elisa.database: transaction failed QSqlError("", "Driver not loaded", "Driver not loaded") "Driver not loaded" 06-13 15:24:37.092 21094 21114 W elisa : qrc:/android_rcc_bundle/qml/org/kde/kirigami.2/private/globaltoolbar/BreadcrumbControl.qml:17:5: Unable to assign [undefined] to QQuickItem* so probably an issue with the database? I get the same two errors if I press "Reset Databse and Re-Scan Everything". This happens for the fast native indexer and for scanning the filesystem directly.
Unfortunately, I can reproduce but so far lacked time to really work on a fix. Will try my best in the following days. Best regards
I can reproduce this on Android 9 with Elisa version 22.11.70. sudo logcat | grep kde 10-06 15:07:21.716 29777 29829 D elisa : org.kde.elisa.database: transaction failed QSqlError("", "Driver not loaded", "Driver not loaded") "Driver not loaded" 10-06 15:07:21.720 29777 29794 W elisa : qrc:/android_rcc_bundle/qml/org/kde/kirigami.2/private/globaltoolbar/BreadcrumbControl.qml:17:5: Unable to assign [undefined] to QQuickItem*
*** Bug 461290 has been marked as a duplicate of this bug. ***
*** Bug 469377 has been marked as a duplicate of this bug. ***
*** Bug 473004 has been marked as a duplicate of this bug. ***
Based on other places on the web, and the above error message, the problem seems to be that the appropriate .so file for the SQLite driver either isn't being included in the build or isn't found during runtime. The androiddeployqt tool seems to control which qt libraries get included in the build. According to https://doc.qt.io/qt-5/deployment-android.html, it should be able to tell us if the dependency is detected correctly and if it's being included in the build: "If you are wondering why a particular plugin is not included automatically, you can run androiddeployqt with the --verbose option to get the list of missing dependencies for each excluded plugin. You can achieve the same in Qt Creator by ticking the Verbose output check box in the Projects > Build Steps > Build Android APK > Advanced Actions." Looking at the build output for the latest build, (https://binary-factory.kde.org/job/Elisa_Nightly_android-arm/806/console), I see the following output: > -- Skipping /home/user/Craft/BinaryFactory/android-arm-clang/plugins/sqldrivers/libplugins_sqldrivers_qsqlite_armeabi-v7a.so. It has unmet dependencies: lib/libsqlite3.so. As a wild guess, will adding a dependency to libsqlite in the CMAKE file resolve the issue?
It could also be that the correct sqlite dependency is missing from the build environment, which is probably more likely.
Wanna submit a merge request to fix it?
*** Bug 476363 has been marked as a duplicate of this bug. ***