Closed xnumad closed 6 months ago
I have re-checked into this problem on a Android 13 device using the un-changed AndrOBD release:
The error message above (logcat) does indicate a problem in your used photo picker app. That is the app, which crashes based on the file browse request of AndrOBD.
I will also abort the suggested PR, since:
Not to re-ping an old issue, but I'd prefer to continue here as opposed to opening a new one:
So far, I've tried to load/open measurements on two different devices (Samsung with Android 13, Pixel 6a with 14) and both of them end up crashing the app. The only way I can load or open measurements is by installing the app in android studio's emulator or Android-x86, which is (and I don't want to seem rude) a ridiculous workaround.
Could you suggest a better solution or workaround for users with this issue to be able to load the file? Or are we really worried about adding 700KB to a 1.4MB app and keeping support for decade-old, unpatched versions of Android?
I have to agree, that this change is definitely needed for support Android 14. My Android 13 devices all seem to be happy without it . I really hate the way Android behaviour and handling changes. Android somehow appears to degenerate to a huge collection of restricions, which all require workarounds ... ;-(
However, I'll implement your proposed changes :+1:
Test version V2.6.9: https://t.me/AndrOBD_dev/256
Test version V2.6.9: https://t.me/AndrOBD_dev/256
Came here with the Load measurement problem on my Galaxy S21+ running Android 14, and with this version I was able to load my saved measurement finally!! Thanks!
Describe the bug
App closes when clicking "Load measurement" in menu. If I try this multiple times, I get "Media keeps stopping" Android app crash dialog. (When reproducing, always without the "Send feedback" option displayed.)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A file picker opens, to be able to select a saved measurement.
AndrOBD Debug log files
Even with log level ALL, the log doesn't contain anything about the error.
Important details on your environment:
Additional context
from
adb logcat
: