Posts made by Talkless

Talkless

@Talkless OK so I've changed to download updates no only on WiFI, but always.

After that I've got list of chanels, and got the update.

I guess there's a bug with "WiFi" "detection" in Volla Phone X?

Talkless

I've remembered that there must have been some new upgrade, but my phone still shows no updates to OTA-5.

If I go to channel settings, "Fetching channels" (translated) just keeps spinning, and after maybe 5 minutes or so it results in no channels o select.

Any ideas how to troubleshoot this?

Thanks!

Talkless

Previously I've tried using Volla Phone X (and earlier BQ Aquaris E5) with Parrot car Bluetooth setup. Result was that contacts did sync, but my Parrot mic sound was not forwarded to other side. I've heard what other person is talking via car speakers, but they did not hear me.

Now with Golf 2018 multimedia all sound works fine, but car multimedia fails to sync phonebook. It just immediately returns to the same prompt after split second of trying to sync. I can call by entering number manually via car's touchscreen, or initiate call via phone, but I can't select number from multimedia phone book, as it is not synced (empty).

Is there a way to workaround this? What's the best way to debug this?

Thanks!

Talkless

So if apps are run in container (using clickable desktop), how do I pass environment variables, such as QT_LOGGING_RULES=lomiri.deprecations.debug=true per this suggestion:

lomiri.deprecations: At least 1 Ubuntu.* QML type is in use. Ubuntu.* type is deprecated and is provided for compatibility. To print what types are being in use, set "QT_LOGGING_RULES=lomiri.deprecations.debug=true" environment variable.

Talkless

@jonius said in Issues with clickable gdb / gdbserver:

@talkless please clean the build dir when switching between versions.

I do clean. What am I missing?

clickable clean --arch arm64
clickable clean --arch arm64 --libs
clickable script prepare-deps --arch arm64 && clickable build --libs --arch arm64 && clickable build --arch arm64 --skip-review --release

Talkless

@jonius said in Issues with clickable gdb / gdbserver:

@talkless the latest version of Pure Maps is UT 20.04 only. If you run 16.04, you can go back to Pure Maps 3.1.1 which is still made for 16.04.

I see.

But now I can't even build 3.1.1 or 3.1.0:

Cloning into '/home/vincas/code/puremaps/pure-maps.git/libs/picotts'...
remote: Enumerating objects: 93, done.
remote: Counting objects: 100% (93/93), done.
remote: Compressing objects: 100% (80/80), done.
remote: Total 93 (delta 9), reused 91 (delta 9), pack-reused 0
Receiving objects: 100% (93/93), 5.15 MiB | 9.25 MiB/s, done.
Resolving deltas: 100% (9/9), done.
error: patch failed: platform/qt/qt.cmake:226
error: platform/qt/qt.cmake: patch does not apply
Command exited with non-zero exit status 1, see above for details. This is most likely not a problem with Clickable.

Clickable images updated.

Talkless

@jonius Uhg, right... Thanks!

And this probably means that latest clickable expects 20.04?

Launching app.
Pseudo-terminal will not be allocated because stdin is not a terminal.
-bash: line 1: lomiri-app-launch: command not found
Command exited with non-zero exit status 127, see above for details. This is most likely not a problem with Clickable.

vincas@ubuntu-ubports:~/code/puremaps/pure-maps.git$ clickable --version
clickable 7.11.0
You are running the latest version of clickable!

Intalling also fails:

pure-maps.jonnius_3.2.0_arm64.click                                                                                                                                      100%  101MB 189.5KB/s   09:07    
Pseudo-terminal will not be allocated because stdin is not a terminal.
Trying to uninstall the app first.
Pseudo-terminal will not be allocated because stdin is not a terminal.
Klaida: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name com.lomiri.click was not provided by any .service files
Command exited with non-zero exit status 1, see above for details. This is most likely not a problem with Clickable.

...

Talkless

@jonius I'm now trying to build latest 3.2.1, but it stops due to.. lack of Clang 12 in clickable image?

Digest: sha256:6c2c0d80d9b3a3dff72e647c3c4c8a9a6798da277b38239418f49739d4d5866c                                                                                                                            
Status: Downloaded newer image for clickable/amd64-20.04-arm64:latest                                                                                                                                      
CMake Error at CMakeLists.txt:16 (project):                                                                                                                                                                
  The CMAKE_CXX_COMPILER:                                                                                                                                                                                  
                                                                                                                                                                                                           
    /usr/bin/clang++-12                                                                                                                                                                                    
                                                                                                                                                                                                           
  is not a full path to an existing compiler tool. 

  Tell CMake where to find the compiler by setting either the environment
  variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path
  to the compiler, or to the compiler name if it is in the PATH.


CMake Error at CMakeLists.txt:16 (project):
  The CMAKE_C_COMPILER:

    /usr/bin/clang-12

  is not a full path to an existing compiler tool. 

  Tell CMake where to find the compiler by setting either the environment
  variable "CC" or the CMake cache entry CMAKE_C_COMPILER to the full path to
  the compiler, or to the compiler name if it is in the PATH.


-- Configuring incomplete, errors occurred!
See also "/home/vincas/code/puremaps/pure-maps.git/build/aarch64-linux-gnu/maplibre-gl-native/CMakeFiles/CMakeOutput.log".
Command exited with non-zero exit status 1, see above for details. This is most likely not a problem with Clickable.

I've updated clickable, and it's images.

Talkless

@jonius said in Issues with clickable gdb / gdbserver:

@talkless Can you try building it again with verbose output (clickable build --libs picotts --arch arm64 --verbose)?

Here's verbose build output:

https://paste.debian.net/1267273/

Talkless

@jonius It's empty:

$ tree build/aarch64-linux-gnu/picotts/install
build/aarch64-linux-gnu/picotts/install

0 directories, 0 files

Other sibling directories (like mimic) are NOT empty.

Permissions of picotts are right.

picotts directory of x86_64-linux-gnu and arm-linux-gnueabihf are NOT empty too.

Talkless

@jonius said in Issues with clickable gdb / gdbserver:

Are you sure you have picotts built?

Picotts seems to be cloned in prepare-deps step, and in build --libs step I see this:

[92mBuilding picotts[0m
[93mCached container is outdated[0m
Sending build context to Docker daemon  3.072kB


Step 1/3 : FROM clickable/amd64-16.04-arm64:16.04.5
 ---> a783c3e92703
Step 2/3 : RUN echo set debconf/frontend Noninteractive | debconf-communicate && echo set debconf/priority critical | debconf-communicate
 ---> Using cache
 ---> e1b83f8da45f
Step 3/3 : RUN apt-get update && apt-get install -y --force-yes --no-install-recommends libtool:arm64 libpopt-dev:arm64 && apt-get clean
 ---> Running in b280d7a9aa37
Get:1 http://ports.ubuntu.com/ubuntu-ports xenial InRelease [247 kB]
Get:2 http://ppa.launchpad.net/bhdouglass/clickable/ubuntu xenial InRelease [15.4 kB]
Get:3 http://archive.ubuntu.com/ubuntu xenial InRelease [247 kB]
Get:4 https://deb.nodesource.com/node_16.x xenial InRelease [4584 B]
Get:5 http://repo.ubports.com xenial InRelease [21.2 kB]
Get:6 http://ppa.launchpad.net/mardy/qbs-on-lts/ubuntu xenial InRelease [15.4 kB]
Get:7 https://deb.nodesource.com/node_16.x xenial/main amd64 Packages [774 B]
Get:8 http://ports.ubuntu.com/ubuntu-ports xenial-updates InRelease [99.8 kB]
Get:9 https://deb.nodesource.com/node_16.x xenial/main arm64 Packages [772 B]
Get:10 http://ppa.launchpad.net/bhdouglass/clickable/ubuntu xenial/main amd64 Packages [784 B]
Get:11 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [99.8 kB]
Get:12 http://ports.ubuntu.com/ubuntu-ports xenial-security InRelease [99.8 kB]
Get:13 http://archive.ubuntu.com/ubuntu xenial-security InRelease [99.8 kB]
Get:14 http://ppa.launchpad.net/bhdouglass/clickable/ubuntu xenial/main arm64 Packages [784 B]
Get:15 http://ppa.launchpad.net/mardy/qbs-on-lts/ubuntu xenial/main amd64 Packages [1125 B]
Get:16 http://repo.ubports.com xenial/main amd64 Packages [2111 kB]
Get:17 http://ppa.launchpad.net/mardy/qbs-on-lts/ubuntu xenial/main arm64 Packages [1129 B]
Get:18 http://ports.ubuntu.com/ubuntu-ports xenial/main arm64 Packages [1466 kB]
Get:19 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages [1558 kB]
Get:20 http://ports.ubuntu.com/ubuntu-ports xenial/multiverse arm64 Packages [146 kB]
Get:21 http://ports.ubuntu.com/ubuntu-ports xenial/universe arm64 Packages [9493 kB]
Get:22 http://archive.ubuntu.com/ubuntu xenial/restricted amd64 Packages [14.1 kB]
Get:23 http://archive.ubuntu.com/ubuntu xenial/multiverse amd64 Packages [176 kB]
Get:24 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages [9827 kB]
Get:25 http://repo.ubports.com xenial/main arm64 Packages [2106 kB]
Get:26 http://ports.ubuntu.com/ubuntu-ports xenial-updates/main arm64 Packages [1556 kB]
Get:27 http://ports.ubuntu.com/ubuntu-ports xenial-updates/multiverse arm64 Packages [17.2 kB]
Get:28 http://ports.ubuntu.com/ubuntu-ports xenial-updates/universe arm64 Packages [1466 kB]
Get:29 http://ports.ubuntu.com/ubuntu-ports xenial-security/main arm64 Packages [1118 kB]
Get:30 http://ports.ubuntu.com/ubuntu-ports xenial-security/multiverse arm64 Packages [3332 B]
Get:31 http://ports.ubuntu.com/ubuntu-ports xenial-security/universe arm64 Packages [943 kB]
Get:32 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [2560 kB]
Get:33 http://archive.ubuntu.com/ubuntu xenial-updates/restricted amd64 Packages [16.4 kB]
Get:34 http://archive.ubuntu.com/ubuntu xenial-updates/multiverse amd64 Packages [26.2 kB]
Get:35 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages [1544 kB]
Get:36 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 Packages [2051 kB]
Get:37 http://archive.ubuntu.com/ubuntu xenial-security/restricted amd64 Packages [15.9 kB]
Get:38 http://archive.ubuntu.com/ubuntu xenial-security/multiverse amd64 Packages [8820 B]
Get:39 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 Packages [984 kB]
Fetched 40.2 MB in 4s (8160 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Suggested packages:
  libtool-doc gfortran | fortran95-compiler gcj-jdk
Recommended packages:
  libltdl-dev
The following NEW packages will be installed:
  libpopt-dev:arm64 libtool
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 232 kB of archives.
After this operation, 1079 kB of additional disk space will be used.
Get:1 http://ports.ubuntu.com/ubuntu-ports xenial/main arm64 libpopt-dev arm64 1.16-10 [38.5 kB]
Get:2 http://archive.ubuntu.com/ubuntu xenial/main amd64 libtool all 2.4.6-0.1 [193 kB]
[91mdebconf: delaying package configuration, since apt-utils is not installed
[0mFetched 232 kB in 0s (815 kB/s)
Selecting previously unselected package libpopt-dev:arm64.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 54550 files and directories currently installed.)
Preparing to unpack .../libpopt-dev_1.16-10_arm64.deb ...
Unpacking libpopt-dev:arm64 (1.16-10) ...
Selecting previously unselected package libtool.
Preparing to unpack .../libtool_2.4.6-0.1_all.deb ...
Unpacking libtool (2.4.6-0.1) ...
Setting up libpopt-dev:arm64 (1.16-10) ...
Setting up libtool (2.4.6-0.1) ...
[91mW: --force-yes is deprecated, use one of the options starting with --allow instead.
[0mRemoving intermediate container b280d7a9aa37
 ---> 339b027b7540
Successfully built 339b027b7540
Successfully tagged clickable/amd64-16.04-arm64:16.04.5-8a63b05d-ed0b-4ef1-89f6-7d72d35c4d74
make: Nothing to be done for 'all'.
make: 'install' is up to date.
[92mBuilding mimic[0m

Not sure if these final lines are actually OK:

Successfully built 339b027b7540
Successfully tagged clickable/amd64-16.04-arm64:16.04.5-8a63b05d-ed0b-4ef1-89f6-7d72d35c4d74
make: Nothing to be done for 'all'.
make: 'install' is up to date

Talkless

Thanks @stanwood for the fix, it worked!

Talkless

I've reported: https://github.com/waydroid/waydroid/issues/628

Talkless

I've tried to install again.

It did install, I can launch Waydroid, I do hear some sort of notification sounds, but the view does not appear - I only see Waydroid app loading forever.

Talkless

Oh boy, I've updated clickable (it suggested that there's latest version):

pip3 install --user --upgrade clickable-ut

Updated images:

clickable update-images

Rebuilt everything:

clickable script prepare-deps
clickable build --libs --arch arm64
clickable build --arch arm64 --debug

But it fails to install picotts on final app build step:

Installing libraries
  /home/vincas/code/puremaps/pure-maps.git/build/aarch64-linux-gnu/s2geometry/install/lib/libs2.so
Installing binaries
  /home/vincas/code/puremaps/pure-maps.git/build/aarch64-linux-gnu/mimic/install/bin/mimic
find: '/home/vincas/code/puremaps/pure-maps.git/build/aarch64-linux-gnu/picotts/install/usr/bin/': No such file or directory
Command exited with non-zero exit status 1, see above for details. This is most likely not a problem with Clickable.

Not sure why it install pico if it's full build:

$ file clickable.yaml 
clickable.yaml: symbolic link to packaging/click/full-build.yaml

Talkless

Reported: https://github.com/Aarontheissueguy/WaydroidHelper/issues/22

Talkless

So I've removed waydroid, installed OTA-24, installed Waydroid using Waydroid Helper app, but.. theres' no Waydroid icon, and waydroid --help says command not found.

Talkless

Hi.

I see there's OTA-24 upgrade available.

I have Waydroid installed, and also see that kernel is named "lineage_halium_arm64...". So I assume installing Waydroid installs different Linux kernel..?

Now the questions arises, can I upgrade to OTA-24 without doing anything specific, or maybe I have to remove Waydroid, install OTA-24 upgrade and later re-install Waydrod again?

Thanks!

Talkless

It seems I forgot to add --arch arm64 together with --debug, so I was building.. probably desktop version all the time.

Yes, removing CmdLineParser lines allows to keep debugging further.

Does that mean that clickable gdb launches application incorrectly, without some expected arguments that where provided via .desktop file (or whatever) for example?

Talkless

@jonius Have you actually seen these source lines within gdb? Because there's no symbols for me:

Reading symbols from /home/vincas/code/puremaps/pure-maps.git/build/aarch64-linux-gnu/app/install/lib/aarch64-linux-gnu/bin/pure-maps...(no debugging symbols found)...done.

Also, commenting out command line parsing did nothing, and even adding qFatal() did not make app to die in normal run. As if clickable install --arch arm64 just installs some old release build...

Also, clickable install takes 3 minutes to upload app into my Volla Phone X...

Also, clickable launch logs does not show any output, no "logs"...

So far, much pain...