Hi @friendsmobile, thanks for providing this report I can see that the contribution has been acknowledged by the PO. He has self assigned the issue. Hopefully, a fix is in the works. I love that you included

Hi @ammarraisafti, thanks for making this report. Unfortunately, the report cannot be scored. The guidelines does not accept contributions that involve the rotation or altering of the screen orientation.

Hi @brave1, thanks for providing this report I can see that the contribution has been acknowledged by the PO in different instances. He has also gone ahead to proffer solutions to the bug experienced.

Hi @peerzadaabid, thanks for making this report Great to see that this issue has been acknowledged by the esteem team. I am very hopeful of a fix coming out soonest. Do you know you can include in your

Hi @ckole, thanks for making this contribution I love that you provided a logcat but these days we look out for a bit of analysis. A little detailed explanation of what may have went wrong. The PO would

Hi @ammaraisafti, thanks for making this contribution Unfortunately, this cannot be scored. The PO in his comments is unable to reproduce the bug. Also there is no way to tell if he plans to fix the bug.

Hi @friendsmobile, thanks for another report Unfortunately, this report cannot be scored. The PO is yet to acknowledge the report. The logcat initially provided did not contain enough information to point

Hi @friendsmobile, thanks for another wonderful report I see the PO has acknowledged the report and the issue in question has been fixed. The error was simple enough, hence a very simple fix must have

Hi @friendsmobile, thanks for making this contribution. Great to know that this issue was fixed. I love that you included a logcat. The stacktrace provided was of great help and can be supported with detailed

Hi @friendsmobile, thanks for making this contribution. Great to know that this issue was fixed in this commit - The log you provided was of great help and can be supported with detailed analysis. Your

Hi @jubreal, thanks for making this contribution I love that you provided a logcat but these days we look out for a bit of analysis. A little detailed explanation of what may have went wrong. I see the

Hi @sagorahmed, thanks for this contribution This is strange. I see the PO has acknowledged the issue with a promise to come up with a fix. The logcat you provided was indeed helpful but a quick analysis

Hi @sagorahmed, thanks for reporting this crash The crash is not all that strange considering the input given. It is impossible to have a reading that starts and ends with zero. While an application should

Hi @sagorahmed, thanks for this contribution The initial crash is strange. I see the PO has acknowledged the issue with a promise to come up with a fix. The logcat you provided was indeed helpful but a

Hi @peerzadaaabid, thanks for this report Great to see this has been acknowledged and fixed by the PO. Are you aware you can include detailed analysis on what possibly led to the bug in your report. Doing

Hi @masudrana, thanks for making this report I was able to reproduce the behavior described. Looking through the repo I noticed this part of the code was commented out , I believe the implementation of

Ohh.. It will be better if you dumped just the important log in the post, enclosing it within the code blocks tag

Hi @dongentle2, second of his name. It's good to have you contributing to the category.Either it's your first report or you took a break from the category. Anyways, glad to have you This behavior of the

Hi @asad44, thanks for making this contribution. The log provided is not as precise and should be supported with a detailed explanation. You could have thrown more light on the cause of the crash. I can

Hi @ckole, thanks for making this contribution I can see that the PO has acknowledged the report. From the video you provided, the track jumps back to some 8, 9 seconds after the track's supposed starting