LBRY-Vault/electrum/gui/kivy
SomberNight 7962e17df6
invoices: deal with expiration of "0" mess
Internally, we've been using an expiration of 0 to mean "never expires".
For LN invoices, BOLT-11 does not specify what an expiration of 0 means.
Other clients seem to treat it as "0 seconds" (i.e. already expired).
This means there is no way to create a BOLT-11 invoice that "never" expires.

For LN invoices,
- we now treat an expiration of 0, , as "0 seconds",
- when creating an invoice, if the user selected never, we will put 100 years as expiration
2020-03-04 14:24:07 +01:00
..
data android: runtime permission dialog for camera 2018-11-26 17:54:07 +01:00
nfc_scanner fix import error 2018-09-20 01:20:13 +02:00
theming/light kivy: allow generic passwords for wallets 2020-02-15 16:28:15 +01:00
tools android build: fix accepting licenses 2020-02-21 20:08:32 +01:00
uix invoices: deal with expiration of "0" mess 2020-03-04 14:24:07 +01:00
__init__.py config: remove 'open_last_wallet' side-effecting 2019-09-10 17:10:52 +02:00
i18n.py file reorganization with top-level module 2018-07-13 14:01:37 +02:00
main.kv kivy wallet info screen: handle "show seed" for watch-only/no-seed case 2020-03-02 06:12:24 +01:00
main_window.py kivy: set pin_code timeout to 5 minutes 2020-02-21 11:33:07 +01:00
Makefile kivy: commit png icons (for svg resources) into repo 2019-09-08 17:05:06 +02:00
Readme.md android build: persist gradle datadir 2019-09-02 17:32:48 +02:00
util.py Added coloring to the AddressPopup dialog: 2020-02-01 18:16:26 +01:00

Kivy GUI

The Kivy GUI is used with Electrum on Android devices. To generate an APK file, follow these instructions.

Android binary with Docker

This script does not produce reproducible output (yet!). Please help us remedy this.

This assumes an Ubuntu (x86_64) host, but it should not be too hard to adapt to another similar system. The docker commands should be executed in the project's root folder.

  1. Install Docker

    $ curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
    $ sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"
    $ sudo apt-get update
    $ sudo apt-get install -y docker-ce
    
  2. Build image

    $ sudo docker build -t electrum-android-builder-img electrum/gui/kivy/tools
    
  3. Build locale files

    $ ./contrib/pull_locale
    
  4. Prepare pure python dependencies

    $ ./contrib/make_packages
    
  5. Build binaries

    $ mkdir --parents $PWD/.buildozer/.gradle
    $ sudo docker run -it --rm \
        --name electrum-android-builder-cont \
        -v $PWD:/home/user/wspace/electrum \
        -v $PWD/.buildozer/.gradle:/home/user/.gradle \
        -v ~/.keystore:/home/user/.keystore \
        --workdir /home/user/wspace/electrum \
        electrum-android-builder-img \
        ./contrib/make_apk
    

    This mounts the project dir inside the container, and so the modifications will affect it, e.g. .buildozer folder will be created.

  6. The generated binary is in ./bin.

FAQ

I changed something but I don't see any differences on the phone. What did I do wrong?

You probably need to clear the cache: rm -rf .buildozer/android/platform/build/{build,dists}

How do I deploy on connected phone for quick testing?

Assuming adb is installed:

$ adb -d install -r bin/Electrum-*-arm64-v8a-debug.apk
$ adb shell monkey -p org.electrum.electrum 1

How do I get an interactive shell inside docker?

$ sudo docker run -it --rm \
    -v $PWD:/home/user/wspace/electrum \
    -v $PWD/.buildozer/.gradle:/home/user/.gradle \
    --workdir /home/user/wspace/electrum \
    electrum-android-builder-img

How do I get more verbose logs for the build?

See log_level in buildozer.spec

How can I see logs at runtime?

This should work OK for most scenarios:

adb logcat | grep python

Better grep but fragile because of cut:

adb logcat | grep -F "`adb shell ps | grep org.electrum.electrum | cut -c14-19`"

Kivy can be run directly on Linux Desktop. How?

Install Kivy.

Build atlas: (cd electrum/gui/kivy/; make theming)

Run electrum with the -g switch: electrum -g kivy

debug vs release build

If you just follow the instructions above, you will build the apk in debug mode. The most notable difference is that the apk will be signed using a debug keystore. If you are planning to upload what you build to e.g. the Play Store, you should create your own keystore, back it up safely, and run ./contrib/make_apk release.

See e.g. kivy wiki and android dev docs.