You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched open and closed issues for duplicates
I am submitting a bug report for existing functionality that does not work as intended
This isn't a feature request or a discussion topic
Bug description
I have restarted my Oppo phone in hopes that it'll be resolved, but only to be greeted with pop outs of "Signal keeps stopping". I've cleared cache and changed the battery setting to "allow background activity" in case it may due to battery optimization yet still nothing has resolved. Do I just need to wait for the next update?
Also for additional context, I have both app stores: Play store & Neostore. Would it affect if at first I installed the app from Play store but updated the Signal app in Neostore? Just wanted clarification.
Unfortunately it'll be hard to diagnose without a debug log - could you try turning on airplane mode to see if that prevents crashing long enough for you to get a debug log (instead of doing submit, you would do save which is available in the top right menu)?
Unfortunately it'll be hard to diagnose without a debug log - could you try turning on airplane mode to see if that prevents crashing long enough for you to get a debug log (instead of doing submit, you would do save which is available in the top right menu)?
I've uploaded in the main post the debug log via .zip file and link. I'm looking forward for an update, thank you again!
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions!
@Artemistaken It looks like your log has a lot of database errors, some corruption, some low disk space. Oftentimes low disk space can make sqlite temporarily think it's corrupted. Do you have free disk space?
@wertzuz@paulshryock Please open a separate ticket with a log. It's rare that random crashes have the same root cause.
Activity
mtang-signal commentedon Jul 28, 2026
Unfortunately it'll be hard to diagnose without a debug log - could you try turning on airplane mode to see if that prevents crashing long enough for you to get a debug log (instead of doing submit, you would do save which is available in the top right menu)?
Artemistaken commentedon Jul 29, 2026
I've uploaded in the main post the debug log via .zip file and link. I'm looking forward for an update, thank you again!
paulshryock commentedon Sep 4, 2026
I have this issue too.
github-actions commentedon Nov 4, 2026
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions!
wertzuz commentedon Nov 10, 2026
Me too when clicking chats the first time
greyson-signal commentedon Nov 10, 2026
@Artemistaken It looks like your log has a lot of database errors, some corruption, some low disk space. Oftentimes low disk space can make sqlite temporarily think it's corrupted. Do you have free disk space?
@wertzuz @paulshryock Please open a separate ticket with a log. It's rare that random crashes have the same root cause.
paulshryock commentedon Nov 16, 2026
My issue is resolved, several updates later. Signal for Android has been stable for me, for a while now.