Buildozer: My app not launching (seems it does not find the mobile phone)

[Henrik R.]

I am new to mobile app development, so Buildozer seems like an awesome idea. :-)

By now, when I execute the command "buildozer android debug deploy run" in Terminal (under Ubuntu 18.04.3 LTS) Buildozer seems to go through all the necessary steps, but my app doesn't launch on my Android mobile phone (MOTO G5).

Actually it's not really 'my' app, but the 'touchtracer' demo kivy app.

The following is the end of the rather verbose output from the above mentioned command. I notice that "List of devices attached" seems to be empty, although my MOTO G5 mobile phone is connected via USB, and is mounted by Ubuntu. Can anyone help, please.

I have attached a file with the whole output from the "buildozer android debug deploy run" command in Terminal:

[DEBUG]:   -> running cp /mnt/4AF15A0435E762B4/DataDoc/OneDrive/PycharmProjects/2d-graphics/touchtracer/.buildozer/android/platform/build-armeabi-v7a/dists/myapp/build/outputs/apk/debug/myapp-debug.apk myapp-0.1-debug.apk
WARNING: Received a --sdk argument, but this argument is deprecated and does nothing.
No compiled python is present to zip, skipping.
No setup.py/pyproject.toml used, copying full private data into .apk.
Applying Java source code patches...
Applying patch: src/patches/SDLActivity.java.patch
Warning: failed to apply patch (exit code 1), assuming it is already applied: src/patches/SDLActivity.java.patch
# Android packaging done!
# APK myapp-0.1-armeabi-v7a-debug.apk available in the bin directory
# Run '/home/henrik/.buildozer/android/platform/android-sdk/platform-tools/adb devices'
# Cwd None
List of devices attached

# Application pushed.
# Application started.

Best regards,

Henrik

[Robert Flatt]

Yep, it looks like the device is not found.

To confirm this command returns the same message:

~/.buildozer/android/platform/android-sdk/platform-tools/adb devices

There is probably some simple connection problem.

Is the USB cable to the phone a data cable or just a power cable?

[Robert Flatt]

Or is the Linux a virtual machine?

[Henrik R.]

Thank you for your reply!

In that case maybe it's just a power cable. But I have been able to transfer files from Ubuntu to the phone using that cable and a utility called Android File Transfer, which now seems to have ceased to exist...(?)

I am not running linux virtually. It's a boot partition.

The command "~/.buildozer/android/platform/android-sdk/platform-tools/adb devices" in Terminal confirms that no devices are attached. Although both 'Files' (Nautilus) and the phone says the phone is mounted...?

I just tried another cable, which I use for a very serious purpose. That didn't work either. This is strange.

[Robert Flatt]

Well if the computer can see the device on /mnt that presumably means the cable is ok

FYI the virtual machine question arises because usually virtual machines don't have access to physical devices. But not the issue here. 

Is the phone in debug mode?  ( Settings -> Developer Options -> USB debugging. )

The bash command usb-devices might shed some light.

I reached my limit, Google has a few suggestions for 'adb devices not showing ubuntu'......

[Henrik R.]

My MOTO G5 android phone gets mounted as "/run/user/1000/gvfs/mtp:host=%5Busb%3A001%2C022%5D/" when I choose "Use USB to transfer files" - on the phone.

I can't find "Developer options" in Settings on the phone, but I will try asking someone.

The command 'usb-devices' in Terminal gives an extensive amount of information. My mobile phone seems to be mentioned here, but what do I do with the information?:

T:  Bus=01 Lev=01 Prnt=01 Port=02 Cnt=03 Dev#= 22 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=22b8 ProdID=2e82 Rev=03.18
S:  Manufacturer=motorola
S:  Product=Moto G (5)
S:  SerialNumber=ZY3224R37X
C:  #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=00 Driver=usbfs

Can anyone help?

Henrik

[Henrik R.]

[SOLVED]

Someone showed me the secret 'key' to accessing the "Developer options", and there I found and activated the "USB debugging". That solved it!

Thank you!

Henrik