DraStic

Hi,

As the title says, whenever I load up any rom, Drastic will force close after a very short while.

I am using a Galaxy Note 3 N9005 with the X-Notes custom rom and kernel. I have the latest version of Drastic available on the Goople Play store (just downloaded it), and yes, I paid for it.

Any ideas on what could be wrong? I have Xposed Framework with some stuff like GravityBox, Greenify (I did not greenify Drastic or any system app) etc. I am using the Google Now launcher. I did a license check before trying.

Thanks!

Can you upload a logcat or the crash log file on the Drastic folder in /sdcard?

Fenrir007 wrote:Hi,

As the title says, whenever I load up any rom, Drastic will force close after a very short while.

I am using a Galaxy Note 3 N9005 with the X-Notes custom rom and kernel. I have the latest version of Drastic available on the Goople Play store (just downloaded it), and yes, I paid for it.

Any ideas on what could be wrong? I have Xposed Framework with some stuff like GravityBox, Greenify (I did not greenify Drastic or any system app) etc. I am using the Google Now launcher. I did a license check before trying.

Thanks!

Mmmm, happened to me before, and that was because I download a update for my LG L9, not only Drastic began to fail, but also other emulators, like PPSSPP, N64, etc. So, what I did was to wait for other update from LG, and then everything went back to normal, maybe that could be your issue.

The issue is he is using q custom rom/kernel that may have compatibility issues esp. With xposed framework.

Hello,

This is the log file that was on the root of my sdcard (name of the file was __57d5__.log):

http://pastebin.com/dMBS660G

I never tried using logcat, but if it is needed I can try figuring it out in a bit. I can also try making a video of the issue if it would help (may be tricky).

Edit: seems like the file above is a log from something else completely different (date does not coincide with when I tried playing Drastic)

I tried making a logcat for you. I did this:

1- Started up alogcat and made it start logging.
2- Opened up Drastic and reproduced the bug
3- Went back to alogcat and saved whatever it is it outputed.

Logcat pasted below:

http://pastebin.com/kivcE1U6

I couldn't find the Drastic error log file. I did use the option to send it for review yesterday.

Edit 2: I tried the beta version by joining the beta program to see if the issue was solved in it, but no luck.

Fenrir007 wrote:Hello,

This is the log file that was on the root of my sdcard (name of the file was __57d5__.log):

http://pastebin.com/dMBS660G

I never tried using logcat, but if it is needed I can try figuring it out in a bit. I can also try making a video of the issue if it would help (may be tricky).

Edit: seems like the file above is a log from something else completely different (date does not coincide with when I tried playing Drastic)

I tried making a logcat for you. I did this:

1- Started up alogcat and made it start logging.
2- Opened up Drastic and reproduced the bug
3- Went back to alogcat and saved whatever it is it outputed.

Logcat pasted below:

http://pastebin.com/kivcE1U6

I couldn't find the Drastic error log file. I did use the option to send it for review yesterday.

Edit 2: I tried the beta version by joining the beta program to see if the issue was solved in it, but no luck.

If ya don't mind, can you try it on stock? As I mentioned, there must be something with the custom rom that's making it crash.

The logcat doesn't really help, but i found your crash report that you submitted.
It seems to crash in the code for MOGA integration. Are you using a MOGA controller at all?

Lordus wrote:The logcat doesn't really help, but i found your crash report that you submitted.
It seems to crash in the code for MOGA integration. Are you using a MOGA controller at all?

I do not have a MOGA controller, but I do have an iPega, and it was recommended that we download the MOGA app to help the ipega correctly emulate the MOGA on some games.

If that is causing the issue, then I will try to freeze or uninstall the MOGA apps and try again. I will report back.

Edit: Removing the offending apps made it work properly. Can you take a look at this at some point, though? I'd like to reinstall the apps in the future (I may buy a Moga, so there is that - the ipega I gave up on it since its terrible).

Thanks for the troubleshooting, guys!

Hello Drastic Team,
I'm having the same problem with force close/crashing
I have not Downloaded anything else like the fellow above

ModSTAR wrote:Hello Drastic Team,
I'm having the same problem with force close/crashing
I have not Downloaded anything else like the fellow above

Does anything here help you? viewtopic.php?f=7&t=2957