adbLink v5.1

Search This thread

Carboniferocity

New member
Oct 14, 2022
1
0
After struggling with adbLink 5.1 on Wkindows 10 for a while, I finally realilzed that, unlike 5.0 which I had been using for some time, the new version cannot be run successfully from C:\Program Files. When I copied it to another location it words fine again, but now I have another weird issue...

In addition to being a Kodi enthusiast, I also develop mobile Android apps. I thought adbLink would be a great tool to navigate the files on an Android emulator, but the File Manager just can't see anything on the emulator. What is really odd about it is that I can see everything on the emulator with the ADB Shell, but the adbLink File Manager starts up with no files listed, and any attempt to change directories results in "Directory not found."

I realize my intended use is not what adbLink was built for, but any idea why the ADB Shell can navigate the directories on the emulator, but File Manager can't?
 

jocala

Senior Member
Jul 4, 2010
3,203
1
2,469
Ocala
After struggling with adbLink 5.1 on Wkindows 10 for a while, I finally realilzed that, unlike 5.0 which I had been using for some time, the new version cannot be run successfully from C:\Program Files. When I copied it to another location it words fine again, but now I have another weird issue...

In addition to being a Kodi enthusiast, I also develop mobile Android apps. I thought adbLink would be a great tool to navigate the files on an Android emulator, but the File Manager just can't see anything on the emulator. What is really odd about it is that I can see everything on the emulator with the ADB Shell, but the adbLink File Manager starts up with no files listed, and any attempt to change directories results in "Directory not found."

I realize my intended use is not what adbLink was built for, but any idea why the ADB Shell can navigate the directories on the emulator, but File Manager can't?

I just installed 5.1 to both "\Program Files" and "\Program Files (x86)" -- no issues, installed and ran fine. Can you give more detail regarding this issue?

For the FM issue, edit the device record and check "Disable root". See. if that works ...
 

Top Liked Posts

  • There are no posts matching your filters.
  • 32
    adbLink 5.1 is a companion program for Kodi.

    It works with Kodi for Windows, Mac,Linux and Android

    Global Features

    Manage multiple Kodi devices from one PC
    Edit XML and other files on your devices
    Clone Kodi setups to new devices
    Backup/Restore Kodi setups
    Custom Cache Support for Kodi
    Log file viewer for adbLink/Kodi logs
    Hyperlinked HTML Help

    Android Features

    Install Programs without Android SDK
    ADB/Fastboot enabled command-line
    Busybox for root and non-root
    Built-in WIFI/USB remote
    Move Kodi data to external drives
    Manage devices via USB or IP address
    Root-aware File Manager
    Install/Uninstall Apps

    adbLink 5.1 is available for Windows, macOS and Linux/ChromeOS

    http://www.jocala.com
    7
    adbLink 3.6 released

    adbLink v 3.6 released

    /sdcard, /data/local/tmp, & /storage
    added to presets for file manager

    Activity indicator for local restores
    now properly resets when job is done.

    File manager checks that preset
    or ad hoc path exists prior to
    directory change via go button.

    Android Debug Bridge updated
    Version 1.0.39 - 0.0.1-4500957

    File manager updated to work with
    adb v1.0.39

    Fastboot updated
    Version 0.0.1-4500957

    http://www.jocala.com
    6
    08/08/22

    adbLink 5.1 release

    Internal script directory made
    uniform for all architectures.

    Terminal selection expanded.
    Preferences now allows you to
    choose Windows Terminal or
    Command Prompt for Windows,
    Terminal or iTerm for macOS,
    and Gnome Terminal, KDE Console
    or XFCE4 Terminal for Linux.

    Initial support for Intel ChromeOS.
    Tested with ChromeOS Flex.

    5
    adbLink 3.1 released

    adbLink 3.1 changelog 05/01/17

    The file manager is now root-aware. Perform common file management
    functions (copy,move,rename,mkdir,etc) on the /system and /data
    partitions if your device is rooted.

    When upgrading adbLink versions, data is preserved. Tested
    with adbLink 2.04 and up.

    The database and log files are now stored in a standard
    directory located in the user's $HOME. Mac users can
    now run adbLink without admin privileges.

    The progress bar activity indicator is back.

    Devices can be accessed on an ad hoc basis: double-clicking
    a USB serial number or entering an IP address on-the-fly
    allows interaction with the device w/o first creating
    a device record. In this case, Kodi defaults are assumed.

    Notification messages: toast-style messages or normal style is
    now a preference, with normal set as default.

    A global folder location for files copied from your device
    is set to your system $HOME. Changed to a global location of your
    preference, or overridden by a per-device preference in a
    device record.

    Keypad now uses device address as dialog title

    Log filename defaults to kodi.log or spmc.log depending on
    configuration

    System help updated

    http://www.jocala.com

    New video for adbLink v3.1 will be available later this week.