Replying to Avatar The Beave

Hey, nostr:npub1kvaln6tm0re4d99q9e4ma788wpvnw0jzkz595cljtfgwhldd75xsj9tkzv!

I think I've figured out why I couldn't zap consistently. The app needs to enable background data services. Since I've done that, every zap has gone through via NWC on amethyst. This should be investigated and if found to be the issue that some people are facing, this could and should be documented in your troubleshooting flow, or part of the initial install setup.

Sounds interesting, however I can't see such setting on my Samsung device. Which one has it?

Definitely worth further investigation.

The issues with failing zaps over nwc are really annoying. Thanks to few folks that helped me by setting debug logging (don't do normally) I was able to track that issues are caused by android interrupting background processing, mostly when it keeps running longer due to a casual zapping that adds zaps over time.

In any case, working on an improvement, still about to test how much it will help but promising.

Any other setting that could help is more then welcome, we need to make this use case work to at least to 95% success rate.

Reply to this note

Please Login to reply.

Discussion

No replies yet.