No media shown with fresh install

[IzzySoft]

Describe the bug
I just did a fresh install of Aves from IzzyOnDroid. It starts up fine, but none of the media are shown.

To Reproduce
Steps to reproduce the behavior:

1. Install the app
2. Start the app
3. See "Collection loading", but nothing happens

Expected behavior
Media show up

Screenshots
n/a

System information and logs:

Package: deckers.thibault.aves
Installer: org.fdroid.fdroid.privileged
Aves version: 1.11.1-izzy, build 12001
Flutter: stable 3.19.6
Android version: 11, API 30
Android build: lineage_FP2-userdebug 11 RQ3A.211001.001 eng.root.20230101.184648 dev-keys
Device: Fairphone FP2
Support: dynamic colors=false, geocoder=true, HDR=false
Mobile services: ready
System locales: de_DE, en_US
Storage volumes: /storage/emulated/0/, /storage/B820-09EC/
Storage grants:
Error reporting: false

Additional context
As you already pointed out in our communication:

I see from your logs that it goes through most steps in the initialization process but the final initialization log line is missing. Attached a collection of logs, exported from Aves and one generated via adb logcat |egrep '(aves|flutter)'.

aveslogs.zip

[MichaelDevon]

I also experience this. Android 14, AOSP. Other gallery apps instantly start collecting media.
Aves only shows newly added media. For example if i have 400 photos in /sdcard/Download/ then install Aves, it wont pick up anything, but if i then download another image, so there would be 401 images in /sdcard/Download/ then only that single new image would be shown. Its not a permission issue. It happens even when aves has direct access to the folder.

[deckerst]

@IzzySoft Could you please try this build and export/save the logs?
https://drive.google.com/file/d/1pysSJmpVyBjUMZmU8xBrKJCpUFrJiW7I/view?usp=sharing

It will install as Aves [Profile]. I don't expect this build to solve the issue, but I added some logs to help me pinpoint where the code is hanging.

[IzzySoft]

@deckerst I would – but since I installed the previous version, that old phone got very instable – so not sure how helpful I can be here. But I'll try..

Background of instability, only indirectly related to getting the details for above report

I had to unstall Aves from there, but that didn't solve the issue (I don't think it's related to Aves, just that the install triggered something. Now the device hangs at least once a day, logcat spilling something about `lowmemorykiller: Killing 'Binder:30652_2'` in some eternal loop until the device reboots… (the replacement is scheduled to arrive in July/August).

Eh, guess I just found the culpritwhile summing this up – hope you don't ask me again to copy-paste something from the app info: it was the editor I only installed to be able to get those details off-device 🙈 Was hard to get rid of that as the uninstall process hung as well, claiming Specified package com.farmerbb.notepad under uid 10171 but it is really -1 and then Exception while retrieving the package info followed by some unlinkToDeath (only managed to get rid of it doing a hard-boot removing the battery, getting in via adb before the device was fully booted, and then pm uninstall it with root powers, yikes…)

What logs will you need then from me, and where do I find them? If logcat, I'd need some term(s) to grep for, as adb logcat on the affected device currently has something like 100 lines per second (down to 5-10 again now) 🙈

[deckerst]

Thank you for all the efforts.

If you can, the simplest would be to save the logs via the app > About > Bug Report > Step 1.

If you can't or it yields an empty file, logcat could be a solution:

adb logcat | grep "$(adb shell ps | grep deckers.thibault.aves.profile$ | awk '{print $2}')"

[IzzySoft]

Well, call it a disappointment then, Thibault: as my good old FP2 runs smoothly again, I dared installing the APK. Installed fine, started up faster than the old one I had removed a few days ago – and immediately shows all the photos and screenshots. Even without all the artifacts and bucking I had before (hey, FP2, with its old 32bit CPU, that's amazing, and totally unexpected), thanks a lot! Finally, the great Aves usable on my old Fairphone, I'm excited! 🤩

Would you still want the logs – or will they rather be obsolete as the error no longer occurs?

[IzzySoft]

PS: Leaving the issue open so hopefully @MichaelDevon can check and confirm as well.

[MichaelDevon]

PS: Leaving the issue open so hopefully @MichaelDevon can check and confirm as well.

Works for me too. Thanks!

[deckerst]

Thank you both for the feedback.

However, I'd like to double check this positive result.

What you previously had was this version of Aves:

• release build
• izzy flavour
• v1.11.1

What I linked above is:

• profile build
• play build
• vNext

As I understand, it wasn't working with release-izzy-v1.11.1 but it works with profile-play-vNext.

Could you try then this build to confirm? It's a release build of the izzy flavour with the current code on master.

• ❌ aves-izzy-release_v1.11.1
• ✅ aves-play-profile_20240521_2000
• ❌ aves-armeabi-v7a-izzy-release_20240522_2230
• ✅ aves-armeabi-v7a-izzy-profile_20240523_2230

[IzzySoft]

Yuck, I can only uninstall during boot it seems… OK, done: uninstalled profile, installed the new, tried – and failed: starts up, but no images. Here's the corresponding
aves-logs-20240522_235441.txt

Guess next try is profile-izzy-vNext or release-play-vNext to see in which field the culprit lies?

[MichaelDevon]

For me, aves libre from fdroid didnt work, but the one you sent previously did. I cant test the new one currently, but ill get to it eventually.

[deckerst]

Here are some fresh builds:

• aves-armeabi-v7a-izzy-profile_20240523_2230
• aves-play-release_20240523_2230

I added some logs in these releases, hopefully I'll see where things hang (if they do).

[MichaelDevon]

Here are some fresh builds:

• aves-armeabi-v7a-izzy-profile_20240523_2230
• aves-play-release_20240523_2230

I added some logs in these releases, hopefully I'll see where things hang (if they do).

Play Release works fine. I cant install the other one because its "not compatible with my device".
Assuming its because its not arm64 v8

[deckerst]

@IzzySoft if you find the time, please let me know how this goes in your environment.

[IzzySoft]

@deckerst sorry, was AFK (just returned last night). Just tried aves-armeabi-v7a-izzy-profile_20240523_2230 now: works as expected (starts, shows available pictures).