Hi @darewealth, thanks for making this contribution. It appears that this issue is unique to OS 6 . Glad to know it has been acknowledged by the PO. Thanks again for the contribution. I look forward to

Hi @ckole, thanks for making this contribution. The log is pretty precise and can still be supported with a detailed explanation. I see the PO has acknowledged the issue. The behavior experienced was

Hi @darewealth, thanks for making this contribution. The log is pretty precise and can be supported with a detailed explanation. I see the PO has rectified the issue in the latest release version Good

Hi @harry-heightz, thanks for making this contribution. I see the PO has acknowledged the error. Although, he thinks the new UI features for android pie are too hard for him to grasp and thus he'll let

Hi @darewealth, thanks for making this contribution. I see the PO has acknowledged the error with a promise to have it fixed in the next release. Are you aware you can include in your report an analysis

Hi @ckole, thanks for making this report. Your comment on the main issue was indeed helpful. But this cannot be considered for a review since the issue was known and already confirmed by a different

Hi @darewealth, thanks for making this report. At the time that this was reported the PO argued that the feature itself was yet to be implicitly implemented In fact, EQ can be considered a separate

Hi @harry-heightz, thanks for making this report. I am unable to reproduce the error on OS 6 and 7. Must be unique to OS 9 -- from the stack trace the application is being denied some sort of access

Hi @xee-shan. Thanks for making this report. Cases like this should not crash the application. A simple fix will be to add a catch block for cases of input type that may not pass the set conditions. I

Hi @iamowomizz, thanks for contributing to utopian The behavior described is strange since a user expects numbers to be saved when that particular feature is used. The error would be understandable if

Hi @xee-shan, thanks for making this report. The project owner claims he has fixed the issue in the latest release version of the application. The same issue was also reported days back in this ticket

Hi @darewealth, thanks for making this contribution. The log is pretty precise and can be supported with a detailed explanation. I see the PO has rectified the issue in this commit - Apparently, the fix

Hi @darewealth, thanks for making this contribution Good to know the issue was fixed. It can be seen that you opened the issue a while ago. It's a wonder you are just submitting it. Guess you might have

Hi @ammarraisafti, thanks for making this report. The behavior, from what the project maintainer explained, may be an intended feature. Most probably built that way for security reasons. Did you try logging

Hi @ammaraisafti, thanks for making this contribution. I noticed the issue has been fixed by the PO in this commit - and is available for testing in the latest release version. Are you you can include

Hi @xee-shan, thanks for making this contribution I see the PO has fixed this issue in the latest pre-release version of the application. Unfortunately, pre-alpha versions are not considered review-able.

Hi @masudrana, thanks for making this contribution I see the PO has acknowledged the report with a promise to have it fixed in the next update. The behavior is particularly strange. Strange that it can

Hi @sagorahmed, thanks for making this report I can see the PO has fixed it in this commit . The logcat you provided was helpful, a little breakdown of the cause would have been nice. Still a good find.

Hi @iamowomizz, thanks for making this contribution Unfortunately, this cannot be scored. This is not the correct use case. It is specified in the documentation that you need to have the Elder driver Xposed

Hi @iamowomizz, thanks for making this contribution This issue as explained by the PO is from the online link. By online link I think he means the API link provided by the MV service. This is not completely