nickvandyke / sia-android Goto Github PK

For example, "No Wallet" text and a create wallet button. Maybe with a cool wallet image. Should be able to use AlertDialog with WalletCreateFragment as it's view for this, or place the fragment somewhere nice in the layout.

Don't know the cause of this. Copying the binary and making it executable succeeds. For both copying and execution, the same process is followed as for the arm64 version of siad.

For this reason, choosing to run a local node on an x86_64 device will say it's not supported, and will not update the setting. If you wish to test this or try to fix it, you'll have to change this (very small change).

My physical android device is arm64 - I'm using an emulator to test x86_64. Maybe this is the cause.

Not sure how much history would be best to keep track of. 1, 2, 3 pages? After exhausting this history, pressing the back button should exit the app, preferably with a confirmation dialog.

This is a big task, and I'm working on polishing the existing app and the Wallet functionality before moving on to it.

When in cold wallet mode, query explore.sia.tech for transactions involving addresses of the cold wallet. Should be able to determine the cold wallet's overall balance using this and some math. Not sure if this is possible with the explorer's API, I haven't looked into it.

The current intro method - the Welcome screen and Help screen - contains a lot of boring text. A menu similar to the About menu that concisely and simply explains each functionality (cold storage, remote node, local node) and at the end offers buttons for setup of each would be hugely preferred. These setup buttons could set the Mode setting to the correct setting, and then bring to user to a Create Wallet dialog - should be able to use an AlertDialog that has WalletCreateFragment as it's view for this. After this dialog, they'll be brought to the Wallet page.

For those of us who prefer not to run google services on our devices, would it be possible to include this app on f-droid ?

I might also add that as far as I can see, the sort of user who goes through the trouble of learning how to install a custom rom without google services/apps on their device, is at this point probably also interested in cryptocurrency - publishing the app on f-droid to hordes of foss fans seems like a good way to get some exposition with the right crowd!

When the app is left open in the background for a while, sometimes the Error retrieving sync progress notification will be shown. This means the WalletMonitorService made an http request for the sync progress and didn't receive a response. Which means the backend service (ColdStorageService or Siad) wasn't running when it made the request. Or that the request failed for some other reason. But there's no way in the code (that I can find) that could cause Siad/ColdStorageService to be shut down but not the WalletMonitorService. So maybe the android OS needs memory and happens to be killing the backend service but not the WalletMonitorService.

Haven't tested if this also happens when Run in background is set and the app is closed.

Less elegant solution would potentially be to stop WalletMonitorService in onDestroy() of the backend services (if the app's preferences are still set to use that backend service. If the backend service is destroyed because the backend modes are switched, then it shouldn't stop WalletMonitorService).

Such as Send, since you cannot send from a cold wallet, and Sync progress text and bar