App sometimes becomes unresponsive when attempting to open logcat
Steps to reproduce
Opening logcat will sometimes crash the app. My assumption is because there is to much logs in there. I think this could be fixed by limiting it to a specific size and trimming the oldest parts of it when it reaches that size, or alternatively have a clear button that doesn't need logcat open to clear it, otherwise you can not open it, nor clear it to make it open again.
On a side note, I think there should be some way to share it to the cloud, upload to a pastebin or something directly from within the app, that way you can easily get it from TV as well if it's possible. Some pastebins have free APIs that I believe this should be possible. That would also make you be able to share large ones without having to open it and crashing the app as well, then you could view it in the pastebin which would likely work better.
Expected behavior
The app should open logcat normally
Actual behavior
The app becomes unresponsive, and eventually gives a force stop dialog
Cloudstream version and commit hash
4.2.0 177b1e4
Android version
Android 13
Logcat
No response
Other details
No response
Acknowledgements
- [X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
- [X] I have written a short but informative title.
- [X] I have updated the app to pre-release version Latest.
- [X] If related to a provider, I have checked the site and it works, but not the app.
- [X] I will fill out all of the requested information in this form.
u can enable auto send logcat to tv , when crashed it will automatically send to a google form to lagradost
u can enable auto send logcat to tv , when crashed it will automatically send to a google form to lagradost
I didn't know what was automatically sent, I did know it was sent to Google forms on crashes, just note the context of that. Thanks for that clarification as well.