Home > Uncategorized > QtADB 0.8.1 fix

QtADB 0.8.1 fix


Hey,

recently some users reported that application crashes on start. I replaced binaries in packages so if You have problems with previous version, please download the new files.

If someone needs the most recent QtADB 0.8.1 sources here is the link: http://motyczko.pl/qtadb/qtadb_src.tgz

Meanwhile I’m going back to QtADB 2.0 πŸ˜‰

Ps. If this version also causes segmentation fault, please do as following:
edit /home/yourusername/.config/Bracia/QtADB.conf file and set checkForUpdatesOnStart to β€œfalse” as displayed below:
checkForUpdatesOnStart=false
On windows You should seek for Bracia entry in regedit.

Regards
Jakub

Advertisements
Categories: Uncategorized
  1. Heart1010
    April 15, 2014 at 21:10

    http://motyczko.pl/qtadb/QtADB_0.8.1_linux64.tar.gz !?

    I get
    $ aunpack QtADB_0.8.1_linux64.tar.gz

    gzip: stdin: not in gzip format
    tar: Child returned status 1
    tar: Error is not recoverable: exiting now
    aunpack: tar …: non-zero return-code

  2. 7ymekk
    April 16, 2014 at 05:54

    I’m using: tar -xvf QtADB_0.8.1_linux64.tar.gz

    • Heart1010
      April 16, 2014 at 07:33

      really strange… tar command worked, thanks.

      But something must be “corrupt” because the archive manager gui and aunpack command give errors, that doesn’t happen with all the hundred archives I extracted the last years πŸ˜‰

      • 7ymekk
        April 16, 2014 at 07:39

        I’m using tar for tgz and unzip for zips and never had any problems πŸ˜‰ The GUI managers for archives never worked as I wanted

  3. April 24, 2014 at 08:27

    Downloaded your modified QtADB 0.8.1 sources, compiled with Qt 4.8.4 and tested under Linux / 64-bit.

    Phone: Samsung Galaxy S4 (GT-I9505 / ROM: KOT49H.I9505XXUFNC4)
    OS: Linux Mint 16 / x86_64 (kernel: 3.13.6-031306-generic / x86_64)

    Phone become visible only when development mode with USB debugging was enabled (this actually is normal beaviour). So far so good… But not without problems:

    1) When launched, QtADB displayed application window then crashed. Cause of problem is missing network resource, which raise SIGABRT in classes/updateapp.cpp, line 57 (function UpdateApp::gotWWW). Probably because QtADB version updates currently is not available. Perhaps QtADB 2.0 should check for resouce availability too and shouldn’t crash only because update server is missing. To avoid this problem in 0.8.1, automatic updates must be switched off. Open QtADB.conf (Linux users must look in /home//.config/Bracia) and set checkForUpdatesOnStart to “false” as displayed below:

    checkForUpdatesOnStart=false

    and save file. Now QtADB should be able to run.

    2) Files and directories is not visible in file manager view, but can be listed and traversed in ADB shell view. Perhaps this is phone or Qt version specfic problem. I seen this issue before with some other devices (can’t remember exact models, but those was some LG and Samsung devices).

    • April 25, 2014 at 06:42

      Tested QtADB on more devices and found that phone side tree file manager view is always empty on newer devices with MTP access to device content (Android 4.x) and additional SD card inside. Note to QtADB 2.0 developer – you must foresee situation with more than one storage device. Because there can be situation with 3 and more devices too (device storage + additional SD card + one or more flash drives or HDD drives attached directly or via USB OTG.

      • 7ymekk
        April 25, 2014 at 06:58

        QtADB 0.8.1 supports only 1 device at the time. MTP is not supported, You have to use USB charging or camera mode (e.g. nexus 7). SD cards are mounted in /storage/ path in Your device, so if You want to get access to them, then look in there.

        I’m working now on QtADB2, which will support many devices simultaneously atc.

  4. April 25, 2014 at 08:10

    7ymekk :
    QtADB 0.8.1 supports only 1 device at the time. MTP is not supported

    Probably lack of MTP support is the right answer to empty phone side in file manager.

    Glad to read about new version progress.

    • 7ymekk
      April 25, 2014 at 08:13

      You need phone with root and busybox. Without it, the phone side will be empty.
      New version doesn’t use busybox, in fact it doesn’t use adb so it is more slick solution.

  5. SpAiK
    April 29, 2014 at 10:05

    Hi, I often use QtADB and find it very usefull. I’ve been using it without a problem on Win7, but now I’ve updated to Win8.1 and QtADB crashes every time it’s started. I’ve updated to v0.8.1 but it’s still crashing, also on my Win8.1 tablet. Could it have something to do with the adb version? I’m using latest from android sdk.

    • May 19, 2014 at 10:31

      Disable the automatic updates by setting the checkForUpdatesOnStart=false in QtADB configuration file. Detailed info is in my previous comment above.

      • SpAiK
        May 19, 2014 at 10:50

        Hi, thank you for your answer, but unfortunately I’m unable to find that file. It’s not in the app folder nor in the user account’s AppData (Win8.1).

      • 7ymekk
        May 19, 2014 at 10:54

        thats strange because I removed every usage of checkForUpdatesOnStart in the source code. I have to check it again

    • Zander
      May 26, 2014 at 11:34

      Hey there,

      I have the same issue as you. I managed to work around the problem by using a firewall (in my case it’s Norton Internet Security) to block access to QtADB.exe.

      I say it’s a workaround because after a few seconds the Window that says “There was problem checking for updates” popped up. But of course it’s definitely better than the non-stop crashes.

      Hope that helps! πŸ™‚

  6. Grzesiek
    July 3, 2014 at 12:09

    Hej,

    still application crashes on start 😦 i have windows 7.

  7. Leo
    July 10, 2014 at 16:11

    Confirmed not working on windows 7 x64. I used to use this all the time, now qtadb pops up the error “qtadb.exe has stopped working”. It does this whether I have the phone plugged in or not. Also, windows makes the device disconnect sound at the same time as the error pops up IF the phone is plugged in. I hope that this provides a clue.

    The phone is a moto g xt1045 running kitkat 4.4.3. I have the motorola drivers installed and can see and connect to the phone via adb.

    OK, so I decided to do a little troubleshooting and searched for qtadb in the windows registry. I found the qtadb entries under Bracia in current user. I changed the value of checkForUpdatesOnStart from true to false and now qtadb works as expected.

    Now, granted, editing the registry seems a bit extreme, but I could not find any qtadb config files in the folder or under the current user.

    My phone is not yet rooted so I suspect that this is why the app can not display Files, Apps or storage use under Phone Info.

  8. Nekto
    September 29, 2014 at 16:00

    Amazing tool! Thank you.

    Can you make copy-paste posibility in terminal?

    • 7ymekk
      November 5, 2014 at 12:22

      It’s already there. Shift + Ctrl + V

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: