[Xposed] Scoop - Catch the stack trace when an app crashes

MrWasdennnoch · Dec 23, 2016

Scoop: Catches a stack trace when an app crashes unexpectedly

This module - as the description says - saves the stack trace of a crashing app and displays all crashes in a list so you don't have to look through a long logcat anymore. Additionally you get a notification on every crash (configurable) which already displays the most important information.

This module is based off the module Cracker which sadly isn't being developed anymore so I made an updated version which catches crashes more reliably (supports custom crash handlers set by apps), features material design and contains more functionality such as:

Search in crashed apps
Search in stack trace
Crash preview in notification
Combination of same crashes / apps to avoid long repetetive lists
Crash blacklist
Quick actions to copy / share a stack trace

Download: http://repo.xposed.info/module/tk.wasdennnoch.scoop
Source: https://github.com/wasdennnoch/Scoop

You can help translate this module on GitHub!

Changelog:

XDA:DevDB Information
Scoop, Xposed for all devices (see above for details)

Contributors
MrWasdennnoch
Source Code: https://github.com/wasdennnoch/Scoop

Xposed Package Name: tk.wasdennnoch.scoop

Version Information
Status: Stable
Current Stable Version: 1.6.4
Stable Release Date: 2017-04-01

Created 2016-12-23
Last Updated 2017-04-01

mauam · Dec 23, 2016

Amazing, thanks for this Christmas gift

KaMyKaSii · Dec 24, 2016

Could you add line break and search in log? Thank you!

MrWasdennnoch · Dec 24, 2016

KaMyKaSii said:
Could you add line break and search in log? Thank you!

Done and available in v1.3.0

(Disabled by default)

KaMyKaSii · Dec 25, 2016

MrWasdennnoch said:
Done and available in v1.3.0
(Disabled by default)

Thank you. I upgraded from version 1.1.0 to 1.3.0 and now it says I do not have Xposed installed. I've restarted, cleaned up data, reinstalled, same thing. Before clearing the data, by clicking on the crash log of another app, Scoop also crash. Attached are the logs logs

MarioUnoDueTre · Dec 25, 2016

Word wrap is very appreciated!

Version 1.2 and 1.3 does't work on n910f (note 4) running marshmallow 6.0.1

Definitely a good upgrade from the good Cracker.

I have an old S3 on 4.1.2 (that i use for debugging) with xposed version 54, could this beatiful tool work on xposed version lower than 81 like Cracker?

MrWasdennnoch · Dec 25, 2016

KaMyKaSii said:
Thank you. I upgraded from version 1.1.0 to 1.3.0 and now it says I do not have Xposed installed. I've restarted, cleaned up data, reinstalled, same thing. Before clearing the data, by clicking on the crash log of another app, Scoop also crash. Attached are the logs logs

I fixed the warning (yet have to push it), but I need a logcat to resolve the crash. Your one unfortunately didn't contain any crash info. Make sure to capture it during the crash (because the module doesn't always catch itself

).

KaMyKaSii · Dec 25, 2016

MrWasdennnoch said:
I fixed the warning (yet have to push it), but I need a logcat to resolve the crash. Your one unfortunately didn't contain any crash info. Make sure to capture it during the crash (because the module doesn't always catch itself ).

I took it with the Logcat Extreme app, I hope to be enough. I configured it as verbose, fresh log, main, brief. Let me know if you have any better. You said that Scoop does not log its own crash logs, but actually once here it happened, before clearing Scoop data

MrWasdennnoch · Dec 25, 2016

KaMyKaSii said:
I took it with the Logcat Extreme app, I hope to be enough. I configured it as verbose, fresh log, main, brief. Let me know if you have any better. You said that Scoop does not log its own crash logs, but actually once here it happened, before clearing Scoop data

I said "not always"

I fixed it in v1.3.1. The fault was a misconfigured Proguard which removed more than it should have. I enabled Proguard for debug builds to avoid such issues in the future.

KaMyKaSii · Dec 25, 2016

MrWasdennnoch said:
I said "not always"
I fixed it in v1.3.1. The fault was a misconfigured Proguard which removed more than it should have. I enabled Proguard for debug builds to avoid such issues in the future.

No more crashes, but the notification that Xposed is not installed persists. I updated the module, cleaned data and rebooted

Edit: Looking at this screenshot I recommend future features like search in the main screen, grouping of same app logs and individual exclusion

MrWasdennnoch · Dec 25, 2016

KaMyKaSii said:
No more crashes, but the notification that Xposed is not installed persists. I updated the module, cleaned data and rebooted
Looking at this screenshot I recommend future features like search in the main screen, grouping of same app logs and individual exclusion

Now it should be fixed. Problem is I can't test it because I updated to N and thus don't have Xposed anymore, so I had to try different ways. And of course it was Proguard again.
I'll add the search soon, I thought of only searching for different apps though and not searchin the short description. Not sure how I should approach the grouping but it's possible too. With exclusion you basically mean blacklisting?

Fabian Rï¿½ling · Dec 26, 2016

Xposed bridge version

Xposed installer tells me that I need Xposed bridge version 81. There are no updates for the XPosed bridge for me and the current version is 54, so I think that's a bug.

MrWasdennnoch · Dec 26, 2016

Fabian R�ling said:
Xposed installer tells me that I need Xposed bridge version 81. There are no updates for the XPosed bridge for me and the current version is 54, so I think that's a bug.

The newest available version is 87, but I just remembered: 81 isn't available below LP, right? I'll fix that in the next release.
EDIT: Compatibility down to 52 added in v1.4.0

MarioUnoDueTre · Dec 26, 2016

Compatibility down to 52 is very good, thanks.
The problem is in the image below

Only version 1.1 works for me (n910f note 4 running marshmallow 6.0.1)

KaMyKaSii · Dec 26, 2016

The bug of not having Xposed installed continues, but the app continues to intercept the crashes normally

MrWasdennnoch · Dec 26, 2016

MarioUnoDueTre said:
The problem is in the image below

KaMyKaSii said:
The bug of not having Xposed installed continues, but the app continues to intercept the crashes normally

That's really weird, it hould be working. I completely disabled the warning and will have a look again when Xposed for N is available.

KaMyKaSii · Dec 26, 2016

MrWasdennnoch said:
That's really weird, it hould be working. I completely disabled the warning and will have a look again when Xposed for N is available.

I reported with version 1.3.2, although you talk about version 1.4.0, it was not available when I opened the Xposed Installer. I will update now

Edit: The new version is not working, no crash is being logged

MrWasdennnoch · Dec 27, 2016

KaMyKaSii said:
I reported with version 1.3.2, although you talk about version 1.4.0, it was not available when I opened the Xposed Installer. I will update now

Edit: The new version is not working, no crash is being logged

1.4.2 should fix it... Really bad that I can't test it myself, it could've avoided many issues. But hey, at least I now know how to configure ProGuard properly. At least I hope so.

KaMyKaSii · Dec 27, 2016

MrWasdennnoch said:
1.4.2 should fix it... Really bad that I can't test it myself, it could've avoided many issues. But hey, at least I now know how to configure ProGuard properly. At least I hope so.

Thanks, now it's working. Can you explain to me how the grouping that you implemented works? When I suggested, I wanted to say that after clicking on the crash group of the app, a list of all the crashs with information like date and time appears, and that they expand in the full log when they are clicked. And about the deletion, I'm talking about a button to clear any individual log after a long click on it. At this time it is only possible to clear all logs at once

MarioUnoDueTre · Dec 27, 2016

Yes!
1.4.2 is working; good job, thanks a lot.

[Xposed] Scoop - Catch the stack trace when an app crashes

Inactive Recognized Developer

Attachments

Senior Member

Senior Member

Inactive Recognized Developer

Senior Member

Attachments

Member

Inactive Recognized Developer

Senior Member

Attachments

Inactive Recognized Developer

Senior Member

Attachments

Inactive Recognized Developer

Senior Member

Inactive Recognized Developer

Member

Senior Member

Attachments

Inactive Recognized Developer

Senior Member

Attachments

Inactive Recognized Developer

Senior Member

Member

Similar threads

Top Liked Posts