I see several things that concern me

From the FAQ

Uses Monero v0.12.2

From what i can tell we are on v0.18.3.1. Either the FAQ needs updating or this thing is using quite an old monero version.

Spend Moneroj (handle with care on mainnet!)

This needs to be pointed out to be careful?

My storage is getting full

Newly generated wallets are stored in .new in the main wallet folder. They are never erased (for now). You can delete this whole folder from time to time.

Also, the backup folder named “backups” (formerly .backups) is never automatically cleaned up. You may want to do housekeeping manually with a file browser.

All wallet files (testnet and mainnet) are stored in the main Monerujo folder. So be careful erasing stuff. One of the future releases will split the wallets and move testnet wallets out of there.

This just sounds like an accident waiting to happen.

CrAzYpass is awesome - but I don’t want it!

Creating a file named .nocrazypass in the wallets folder will disable generation of crazypass for NEW passwords (new wallet or change password). The content of the file is not read and is irrelevant. Wallets with CrAzYpass will continue working normally. The currently set real wallet password can be checked in the “Show Secrets”. The wallets folder is:

In 1.x: monerujo on your external storage (legacy) In 2.x: /data/data/com.m2049r.xmrwallet/files/wallets (requires root access)

NB: This feature is for test purposed only - all your XMR will be stolen if you use it!

No idea what this even is but why include something that you explicitly have to point out will get your monero stolen?

Edit: to me this sounds much less like a user wallet and more like a dev wallet.

    • shortwavesurfer@monero.townOPEnglish
      1·
      1 year ago

      Yes, it does, but the checking thing is just a little bar underneath the address that I did not notice at first, and I was not giving it enough time to give that connected message, because I did not see the checking bar.

        • shortwavesurfer@monero.townOPEnglish
          1·
          1 year ago

          All .onions are like that. The only way i discovered the connected message was by using a clearnet node the first time. After that i saw what it was doing and waited for the .onion to respond

            • shortwavesurfer@monero.townOPEnglish
              1·
              1 year ago

              That may be the issue then because I was using the Tor browser which opens a socks port on 9151 but I think it uses Orbot internally. I also have InviZible so I shall have to try it and see how that goes.