Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Mobile and Embedded
  4. Qt/Android on Debian?
Forum Updated to NodeBB v4.3 + New Features

Qt/Android on Debian?

Scheduled Pinned Locked Moved Unsolved Mobile and Embedded
19 Posts 4 Posters 2.3k Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • SGaistS Offline
    SGaistS Offline
    SGaist
    Lifetime Qt Champion
    wrote on last edited by
    #10

    One thing you can try is to follow the phone part of the procedure described in this article. The rest is for a Windows computer but it's at least a start.

    Interested in AI ? www.idiap.ch
    Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

    MucipM 1 Reply Last reply
    0
    • SGaistS SGaist

      One thing you can try is to follow the phone part of the procedure described in this article. The rest is for a Windows computer but it's at least a start.

      MucipM Offline
      MucipM Offline
      Mucip
      wrote on last edited by
      #11

      @SGaist ,
      The error message:

      adb: failed to install /home/milbuga/Qt/Examples/Qt-5.12.3/gui/build-analogclock-Android_for_armeabi_v7a_Clang_Qt_5_12_3_for_Android_ARMv7-Debug/android-build//build/outputs/apk/debug/android-build-debug.apk: Installing to device failed!
      00:47:21: The process "/home/milbuga/Qt/5.12.3/android_armv7/bin/androiddeployqt" exited with code 16.
      00:47:21: Pulling files necessary for debugging.
      00:47:21: Package deploy: Running command "/home/milbuga/Android/Sdk/platform-tools/adb -s 52000026e217250d pull /system/bin/app_process /home/milbuga/Qt/Examples/Qt-5.12.3/gui/build-analogclock-Android_for_armeabi_v7a_Clang_Qt_5_12_3_for_Android_ARMv7-Debug/app_process".
      00:47:21: The command "/home/milbuga/Android/Sdk/platform-tools/adb" terminated with exit code 1.
      00:47:21: Package deploy: Failed to pull "/system/bin/app_process" to "/home/milbuga/Qt/Examples/Qt-5.12.3/gui/build-analogclock-Android_for_armeabi_v7a_Clang_Qt_5_12_3_for_Android_ARMv7-Debug/app_process".
      00:47:21: Package deploy: Running command "/home/milbuga/Android/Sdk/platform-tools/adb -s 52000026e217250d pull /system/bin/app_process32 /home/milbuga/Qt/Examples/Qt-5.12.3/gui/build-analogclock-Android_for_armeabi_v7a_Clang_Qt_5_12_3_for_Android_ARMv7-Debug/app_process".
      00:47:21: The command "/home/milbuga/Android/Sdk/platform-tools/adb" terminated with exit code 1.
      00:47:21: Package deploy: Failed to pull "/system/bin/app_process32" to "/home/milbuga/Qt/Examples/Qt-5.12.3/gui/build-analogclock-Android_for_armeabi_v7a_Clang_Qt_5_12_3_for_Android_ARMv7-Debug/app_process".
      00:47:21: Package deploy: Running command "/home/milbuga/Android/Sdk/platform-tools/adb -s 52000026e217250d pull /system/bin/linker /home/milbuga/Qt/Examples/Qt-5.12.3/gui/build-analogclock-Android_for_armeabi_v7a_Clang_Qt_5_12_3_for_Android_ARMv7-Debug/linker".
      00:47:21: The command "/home/milbuga/Android/Sdk/platform-tools/adb" terminated with exit code 1.
      00:47:21: Package deploy: Failed to pull "/system/bin/linker" to "/home/milbuga/Qt/Examples/Qt-5.12.3/gui/build-analogclock-Android_for_armeabi_v7a_Clang_Qt_5_12_3_for_Android_ARMv7-Debug/linker".
      00:47:21: Package deploy: Running command "/home/milbuga/Android/Sdk/platform-tools/adb -s 52000026e217250d pull /system/lib/libc.so /home/milbuga/Qt/Examples/Qt-5.12.3/gui/build-analogclock-Android_for_armeabi_v7a_Clang_Qt_5_12_3_for_Android_ARMv7-Debug/libc.so".
      00:47:21: The command "/home/milbuga/Android/Sdk/platform-tools/adb" terminated with exit code 1.
      00:47:21: Package deploy: Failed to pull "/system/lib/libc.so" to "/home/milbuga/Qt/Examples/Qt-5.12.3/gui/build-analogclock-Android_for_armeabi_v7a_Clang_Qt_5_12_3_for_Android_ARMv7-Debug/libc.so".
      Error while building/deploying project analogclock (kit: Android for armeabi-v7a (Clang Qt 5.12.3 for Android ARMv7))
      When executing step "Deploy to Android device"
      00:47:21: Elapsed time: 01:17.
      
      1 Reply Last reply
      0
      • SGaistS Offline
        SGaistS Offline
        SGaist
        Lifetime Qt Champion
        wrote on last edited by
        #12

        What happens if you used adb directly ? Can you communicate with your phone ?

        Interested in AI ? www.idiap.ch
        Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

        1 Reply Last reply
        0
        • MucipM Offline
          MucipM Offline
          Mucip
          wrote on last edited by
          #13

          @SGaist said in Qt/Android on Debian?:

          What happens if you used adb directly ?

          How will I do this?...

          Regards,
          Mucip:)

          1 Reply Last reply
          0
          • SGaistS Offline
            SGaistS Offline
            SGaist
            Lifetime Qt Champion
            wrote on last edited by
            #14

            Well... Use the adb command to e.g. list the devices, etc.

            Interested in AI ? www.idiap.ch
            Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

            MucipM 1 Reply Last reply
            0
            • SGaistS SGaist

              Well... Use the adb command to e.g. list the devices, etc.

              MucipM Offline
              MucipM Offline
              Mucip
              wrote on last edited by
              #15

              @SGaist ,
              I guess I've got problem with the Debian which is installed in VirtualBox as a guest and the Samsung phone?!... :(

              I can see the Samsung Android device in VirtulaBox usb device list but can not reach the Telephone content!...

              Regards,
              Mucip:)

              jsulmJ 1 Reply Last reply
              0
              • MucipM Mucip

                @SGaist ,
                I guess I've got problem with the Debian which is installed in VirtualBox as a guest and the Samsung phone?!... :(

                I can see the Samsung Android device in VirtulaBox usb device list but can not reach the Telephone content!...

                Regards,
                Mucip:)

                jsulmJ Offline
                jsulmJ Offline
                jsulm
                Lifetime Qt Champion
                wrote on last edited by
                #16

                @Mucip I don't use VirtualBox, but in VMWare you have to pass the USB device to the virtual machine, so it can access it. Maybe you need to do the same in VirtualBox?

                https://forum.qt.io/topic/113070/qt-code-of-conduct

                MucipM 1 Reply Last reply
                0
                • jsulmJ jsulm

                  @Mucip I don't use VirtualBox, but in VMWare you have to pass the USB device to the virtual machine, so it can access it. Maybe you need to do the same in VirtualBox?

                  MucipM Offline
                  MucipM Offline
                  Mucip
                  wrote on last edited by
                  #17

                  @jsulm
                  I already did it... :(

                  Infact I can see my phone in "Compatible device". But when I run the code Qt can not reach the telephone memory or disk?!...

                  Regards,
                  Mucip:)

                  1 Reply Last reply
                  0
                  • SGaistS Offline
                    SGaistS Offline
                    SGaist
                    Lifetime Qt Champion
                    wrote on last edited by
                    #18

                    I know I insists but adb is the command line tool used to interact with android devices, hence my suggestion to use it and try to manually pull and push stuff on your phone.

                    Interested in AI ? www.idiap.ch
                    Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                    1 Reply Last reply
                    0
                    • Camilo del RealC Offline
                      Camilo del RealC Offline
                      Camilo del Real
                      wrote on last edited by
                      #19

                      Hi @Mucip
                      in linux I have never worrie about the drivers, but yes for the tools, especially for his architecture and permission, but all of it depend on the distribution
                      I always use this to setup my environment in linux
                      Tipos Debian, Ubuntu, LinuxMint
                      $ sudo dpkg --add-architecture i386
                      $ sudo apt-get update
                      $ sudo apt-get install libstdc++6:i386 libgcc1:i386 zlib1g:i386 libncurses5:i386 libc6:i386 lib32z1 libbz2-1.0:i386

                      Tipos Fedora, OpenSuse
                      yum install glibc.i686 glibc-devel.i686 libstdc++.i686 zlib-devel.i686 ncurses-devel.i686 libX11-devel.i686 libXrender.i686 libXrandr.i686

                      After that, download Android SDK, check permission for adb and the other tools in SDK, if need it

                      And finally configure QtCreator with SDK, NDK, Java

                      Regards

                      1 Reply Last reply
                      0

                      • Login

                      • Login or register to search.
                      • First post
                        Last post
                      0
                      • Categories
                      • Recent
                      • Tags
                      • Popular
                      • Users
                      • Groups
                      • Search
                      • Get Qt Extensions
                      • Unsolved