Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

App not responding after multiple days of continuous use with "persist" option enabled on Android #2452

Closed
Perlover opened this issue Oct 3, 2024 · 0 comments

Comments

@Perlover
Copy link

Perlover commented Oct 3, 2024

Dear developers,

I have been experiencing a recurring issue with Zeus Wallet version 0.9.0 on Android. While I can't provide exact steps to reproduce it, the problem occurs as follows:

When I use the wallet continuously over many days with the "persist" option enabled (i.e., the app is always running), after several days, Android starts displaying a message saying that the Zeus application is not responding. Despite this warning, when I open the wallet, the interface works fine. I can access the logs, and the internal LND server appears to be functioning correctly. However, the "application not responding" message keeps reappearing when the app is on the screen, prompting me to close it.

If I choose to close the app, the interface shuts down. When I reopen Zeus, the message appears again. The only solution I've found is to go into the Android system settings for the Zeus app and tap the "Force Stop" button. Afterwards, I clear the cache just to be safe. Once I relaunch the app, it starts working normally again.

It seems that the issue isn't related to the interface freezing—it continues to operate smoothly—nor is it connected to the internal LND server, which also appears to be running based on the logs. It appears there might be a third service that stops responding to Android system requests, but it's not linked to the interface or the internal LND server.

Do you have any idea what could be causing this problem?

Thank you for your attention to this matter.

Best regards, Perlover

@Perlover Perlover closed this as not planned Won't fix, can't repro, duplicate, stale Feb 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants