-
-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash on pause and opening new file #48
Comments
Ah shoot didn't see this one issue. Where should i get the crash report at ? |
@Cwpute Um... Please try whether you can extract the crash reports from LogFox https://www.f-droid.org/packages/com.f0x1d.logfox/ . Please LMK if you can't, I'll send a debug APK built with the latest code. |
Oh logcats... last time i tried there were several hurddles i tried to get over but... i got lost in the instructions... you need to enable a bunch of things and i think i couldn't make Android Studio to work on my 32bit machine or something. |
Ok it seems to work! no more needing to tap several times on files to open them :) |
great, happy to hear! thanks for testing :) (if you wish, you can leave the nice words in the wall of love (#28) too) |
Describe the bug
When dmp is already open and paused in the background, if you try to open a new file with it from any app, it takes two attempts to play a sound file.
The first attempt does nothing (or maybe it silently crashes the player), and the second attempt actually starts playing the file. If you try to bring dmp in focus after the first attempt, it will attempt to play the previous file as if you didn't tell it to before, and will not take into account the file you just asked it to open.
After several attempts trying to reproduce this bug, dmp even triggered a crash warning saying "DMP keeps crashing/systematically crashes." (see screenshot)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
DMP should open the file on the first attempt.
Smartphone (please complete the following information):
Additional context
Similar problems seem to have been reported and solved for 2.1.0 —namely #44 and #43 — but i downloaded and tested the apk for 2.1.1 and the problem persisted.
The text was updated successfully, but these errors were encountered: