Yes. Yes, I did read and follow that doc.
% /usr/bin/adb version (09-05 12:27:00)
Android Debug Bridge version 1.0.39
Installed as /usr/lib/android-sdk/platform-tools/adb
% python3 -V (09-05 12:26:47)
% pip install -r requirements.txt (09-05 12:20:34)
Downloading bottle-0.12.17-py3-none-any.whl (89 kB)
|████████████████████████████████| 89 kB 171 kB/s
Installing collected packages: bottle
Attempting uninstall: bottle
Found existing installation: bottle 0.12.13
Successfully uninstalled bottle-0.12.13
Successfully installed bottle-0.12.17
% adb devices (09-05 12:24:33)
List of devices attached
- daemon not running; starting now at tcp:5037
- daemon started successfully
So adb finds my phone. Running KodularStarter.py seems to work:
% python3 KodularStarter.py (09-05 12:24:40)
Kodular Starter version: 1
ADB path: /usr/bin/adb
Bottle v0.12.17 server starting up (using WSGIRefServer())…
Listening on http://127.0.0.1:8004/
Hit Ctrl-C to quit.
So I start Companion on the phone.
In Creator, I drop down the Test menu and hit “Connect via USB”. I get the Connecting dialog on the Creator. Then, almost immediately, I get the Internal Error dialog. I wait two minutes, nothing happens. If I hit Cancel (Internal) Error 15 times or so, nothing happens. If I hit “Report Error”, an Open Bug page pops up. I close that page, go back and both dialogs are still displayed. So now, I hit Cancel Error about 14 times and the dialog disappears, the Connecting dialog disappears and my project will finally display on the phone.
However, that is using USB, and it seems like an awful lot of machinations to even get the USB to work. Do not understand why there is any error displayed.
The Companion still does not work. I have used the QR symbol and code many times, never does it connect.