yashsingh1/xdaforums huggingface dataset:
[Fire TV Themes and Apps] jocala:
Strange. Not reproducible here (new download three macs), nor have there been any other reports. I don't think it's the file.

https://www.google.com/search?q=dmg+no+moujntable+file+systems

It's not an unknown error, unfortunately. This is the first I've personally seen it reported, many,many thousands of dmg downloads.

Email me at jocala@jocala.com, I'll send you a zip.
[Fire TV Themes and Apps] jocala:
adbLink 3.8 Released

3.8 Changelog:

adbLink c++ framework updated

from Qt 5.10.1 to Qt 5.11.2

OpenSSL support added for https format

(jocala.com address moved from http to https)

Windows dependencies removed for:

libgcc_s_dw2-1.dll

libstdc++-6.dll

libwinpthread-1.dll

These dll files are no longer

required by adbLink for Windows.

Linux: Support for KDE Konsole added. Select

KDE Konsole in adbLink preferences, otherwise

the default of Gnome terminal is used for

adbLink's Console.

Window titles added where missing

Job number removed from running jobs display

icons folder added to linux adbfiles directory.

This contains adbLink icons in png,ico and icns

formats.

https://www.jocala.com
[Fire TV Themes and Apps] dcol:
Great program. Use it for my Fire TV devices. But I also have a PC running Android TV with kodi and many of the adblink functions do not work. Especially the file manager. Is there a way to get that to work with my Android TV? It does work with APK installs and the adb shell.
[Fire TV Themes and Apps] jocala:
I don't know. Are you using a virtual android? If your setup is easily replicated (and free) I'd be willing to test it.

edit: regarding file manager from adbLink help:
[Fire TV Themes and Apps] dcol:
Not a virtual Android. An actual OS running on a Dell PC. Works great. Try it out http://185.7.66.140/
[Fire TV Themes and Apps] jocala:
Unfortunately, android x86 doesn't seem to install properly with VMware Fusion so I'm unable to test (no GUI). Sorry.
[Fire TV Themes and Apps] dcol:
Try this one

https://osdn.net/projects/android-x86/downloads/67834/android-x86_64-7.1-r2.iso
[Fire TV Themes and Apps] jocala:
I managed to get Android x86/64 8.1 running using VMware and can confirm your issue with the file manager. I disabled su, but unfortunately, that didn't fix the problem. Same is true of 7.1 as well. No idea at this point, but I'll continue to investigate.

Thank you for bringing this to my attention.
[Fire TV Themes and Apps] krew11uv:
ADB Link 3.8 Fail

The update to ADB Link from 3.7 to 3.8 fails to create a folder for backup due to it's inability to see the sdcard partition. this may be due to changes in the Windows version to eliminate the use of some DLL's. Please use Versions 3.7 or below if you need to use the Backup feature in Windows.

Thank you.
[Fire TV Themes and Apps] jocala:
Duh. Not enough coffee earlier...

adbLink depends on busybox for it's non-adb-related file commands. The busybox binary that's installed by default is for ARM, not x86. Therefore, non-adb file commands (like file manager) fail when adbLink is run on an x86. This is easily fixable with a little console-fu.

Both releases of x86 Android I've played with have a busybox binary located in /system/xbin. You need to replace the ARM binary installed in /data/local/tmp/adblink with this binary. adbLink must have its own busybox, a symlink won't work. So, if your x86 Android has a pre-installed busybox located in xbin use the cp command to copy the binary to /data/local/tmp/adblink/

Connect and press the ADB Shell button. At the $ prompt, issue the commands below.

rm /data/local/tmp/adblink/*
cd /data/local/tmp/adblink/
cp /system/xbin/busybox .
chmod 0755 busybox
./busybox --install -s .

If the x86 android you're working with doesn't have a busybox installed, you can download one from here: x86 busybox

You can also use adbLink's utility menu: Reinstall busybox function and avoid the command-line. Just replace the ARM busybox with the downloaded x86 busybox in your adbLink install folder, then connect and select reinstall busybox. You'll want to make sure you back up the original ARM busybox and not mix the two up.

Edit: The first time file manager is started it may still appear with empty panels. Close, then restart it and it should be ok.
[Fire TV Themes and Apps] jocala:
Sorry, I can't duplicate your problem here. To double-check I just did both a backup and restore using 3.8 and Windows 10. No issues seeing /sdcard/. Can you provide more details please?
[Fire TV Themes and Apps] Black_Beards:
Having trouble getting AdbLink to start on my linux machine. I have the file as executable and the permissions are r/w but the program won't start.

I had been using 3.6 and it was working fine but have since deleted the files associated with it incase they were causing problems... to no avail

Any ideas ?
[Fire TV Themes and Apps] jocala:
adbLink 3.8 is built using Mint/Ubuntu 18x.

Check by attempting to start from the command-line. cd to the installation directory then type:

./adbLink

Keep your eye peeled for error messages.
[Fire TV Themes and Apps] Black_Beards:
Thanks for the help Jocala, I appreciate it. Been using Adblink since AdbFire.

I am also running LM18

Here is the error I received : ./adbLink: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by ./adbLink)

So I checked and I am running the current version: libc6 is already the newest version (2.23-0ubuntu10)
[Fire TV Themes and Apps] jocala:
Sorry, I mistyped. Ubuntu 18.04 / Linux Mint 19

ldd --version

ldd (Ubuntu GLIBC 2.27-3ubuntu1) 2.27eff@u1804:~$

cat /etc/issue: Ubuntu 18.04.1 LTS

cat /etc/issue: Linux Mint 19 Tara
[Fire TV Themes and Apps] Black_Beards:
Thanks, I just reverted back to the older version and it is working great.

If it's not broke don't fix it :eek:
[Fire TV Themes and Apps] jocala:
Glad it worked out for you.
[Fire TV Themes and Apps] Vixius:
Hi, Jocala!

First, Great Job you did.

I'm having problem with "Device Unauthorized" also have tried with a previous version, same error. Even deleted the 2 files.pub

Running Mac os Mojave.

Can u help me?
[Fire TV Themes and Apps] jocala:
https://www.jocala.com/usbauth.html

Something else to try is to delete the adbkey.* files, then turn off adb debugging on the device. Reboot the device, turn adb debugging back on then try a new connection. However, I've seen authorized devices report unauthorized and then I must press the "Refresh ADB" button to clear this error after a connection.
[Fire TV Themes and Apps] Vixius:
Yes, Already tried but without a reboot. I'll try rebooting.

Thanks.
[Fire TV Themes and Apps] Bobbele2011:
Back Problems

Hi, Jocala!

i use win10 and i have a problem to create a backup from my firetvsticks.

I start backup and i became the answer backup complete.

But in the backupfiles (addons) there are no plugins. Only scripts and repository.

Can u help me?

Greetings from Boris
[Fire TV Themes and Apps] jocala:
An adbLink backup is simply a copy of the Kodi filesystem located under /sdcard/Android/data/org.xbmc.kodi/ -- adbLink mirrors the content located there (with the exception of empty subdirectories, which adb will not copy). If your addon stores resources outside of this filesystem they won't be backed up. This has been an issue with some improperly coded plugins in the past.

I can better help if you supply more detail, i.e. what plugin is failing, what's missing, where to download, etc. I'd be happy to see if I can reproduce the problem.
[Fire TV Themes and Apps] j22barb:
Cannot install a backup made with adbLink 3.8 that worked many times before

I refresh my Amazon Fire TV and have installed a number of APKs using adbLink v3.8. I installed koi 17.6 and even ran it after many tries to install the backup made with adbLink 3.8. The Fire TV is working wirelessly when I am doing this back up or the installs of the APKs. I have used this back up many times for fire sticks and even for the fire TVs. But now I am stumped. I am using an IMAC running High Sierra. But as I have said I have be able to use this backup many, many times.

Hoping you can help.

here is the beginning of my Kodi log:

adbLink 3.8

111418163809

IP: xxxxxxxxxxxx

OS X

------------

SELECT Id FROM device WHERE description="My FIRE TV DEN"

SELECT daddr FROM device WHERE description="My FIRE TV DEN"

server started

* daemon not running; starting now at tcp:5037

* daemon started successfully​

Here is the end:

adb: error: failed to copy '/Users/papas_apple/Desktop/1. Kodi Backups/Backup Kodi

17.6_5.20.2018/./addons/script.extendedinfo/changelog.txt' to

'/sdcard/Android/data/org.xbmc.kodi/files/.kodi/./addons/script.extendedinfo/changelog.txt':

couldn't read from device​

The log was 30.5 mb so even zipping it into smaller packages I could not upload it.

Hope you have enough information to help me.

Thanks again.
[Fire TV Themes and Apps] jocala:
Please copy/paste the entire log into an email to jocala@jocala.com. View the log in adbLink, press the copy button, then paste the log into the body of your email. Please don't send zipped logs, screenshots,etc.
[Fire TV Themes and Apps] kasi1956:
Hi, Jocala!

Since version 3.7 the menu items "ADB Shell" and "Console" do not work anymore. The operating system is Win7pro.

The menu "Adb Shell" opens a command line window and only a blinking cursor is visible.

The menu "Console" opens for a short time a command line window, which closes again immediately.

All other menu items function correctly.

The last version without these two errors is version 3.6.

Many thanks for the great tool.
[Fire TV Themes and Apps] jocala:
Odd. This doesn't occur on my test machine, but it does on a fresh copy of Win7Pro. Windows 10 & 8x are unaffected.

Thank you for the report.
[Fire TV Themes and Apps] novawaly:
Hi,

I just installed on my Mac OS 10.14.2. Im noticing that anything I try to type is coming up blank. It's almost like I'm typing in white letters on a white background. When I input things - for example like my IP address - I can see the cursor move as i type but it all appears white. It'll pick up what Im writing and I was able to connect to my device but I cant see anything in a lot of the menus. Like the file explorer - it all appears white unless I select a row.
[Fire TV Themes and Apps] jocala:
This is an issue with macOS dark mode. No fix yet, sorry (working on it).
[Fire TV Themes and Apps] jocala:
I've deployed a patched version of adbLink 3.8 that displays as usual when using macOS dark mode. Note, it does not implement a dark mode version of adbLink, it just keeps the original appearance no matter which mode is selected. Please download and re-install if dark mode is an issue for you.
[Fire TV Themes and Apps] 2WhlWzrd:
Just reinstalled Ubuntu 16.04 on a machine, was previously using adbLink 3.6 (I think).

Downloaded 3.8 this time, and it won't even launch. 3.6-3.7 are fine though.
[Fire TV Themes and Apps] jocala:
Run the ldd --version command.

I'm doing linux builds on Ubuntu 18x/Mint 19 LTS

ldd --version

ldd (Ubuntu GLIBC 2.27-3ubuntu1) 2.27eff@u1804:~$

cat /etc/issue: Ubuntu 18.04.1 LTS

cat /etc/issue: Linux Mint 19 Tara
[Fire TV Themes and Apps] RoyalTS:
Hmm, I am running Mac OS X 10.14.3 now and as 10.14.2 I cannot connect to any FireTV Box (using adblink 3.8 with latest dark mode patch). Within Linux it works.

Any idea?
[Fire TV Themes and Apps] jocala:
No issues here with macOS and adbLink 3.8. In fact, macOS is my primary, development platform. Please try to connect again and check your logs for issues. You can also visit this page for some tips on fixing connection problems. Feel free to post back with more detail.
[Fire TV Themes and Apps] canadave:
Hi jocala,

I've run adblink 3.8 with no problems to connect to my FireTV 2nd gen for a long time (and other FireTV devices and adblink versions before that). However, I've ditched those in favour of two of the new 4K Fire TV Sticks, and I'm running into a strange connection issue while using adblink 3.8 on my 2011 Macbook Pro running High Sierra. I just wanted to see if you have any suggestions.

I'm having some weird connection issues to the two FireTV sticks periodically (not always, but usually) using adbLink 3.8. I'm able to connect to them sometimes, but often I'll get a message "Cannot connect to [IP address]." I've done some troubleshooting and it seems that this is being caused by the simple fact that the 4K Sticks sometimes do not respond to ICMP pings--i.e. adbLink simply isn't seeing them on the network. If I reboot the Sticks, they are pingable, they can be seen on the network, and adbLink connects to them no problem--but only for a while. It seems that the Sticks "drop off the network" within a short period of time--not sure what that period is, but no longer than a couple of hours. I've got them set to static DHCP IP addresses on my LAN; I already tried reducing the lease time to 6 hours to see if reassigning the IP periodically would "kickstart" them so they don't lose ping, but that doesn't seem to have worked.

Have you run into this issue with 4K FireTV Sticks and adblink? I know it sounds like "a network problem", but I'm fairly LAN-savvy and it's not a question of them not being available on the network permanently. They just seem to drop away after a while. So I'm wondering if you have any suggestions to try. Thanks :)
[Fire TV Themes and Apps] jocala:
No issues here with the new stick. I saw your reddit post, but search didn't find this issue elsewhere, unfortunately. The suggestion of trying a different band is worth a shot.
[Fire TV Themes and Apps] canadave:
Hmmm....interesting. I did try using a different band, and making sure all devices are on the same band, but it still didn't work. It's definitely a ping problem with the sticks, because when adblink works, I can ping them, and when it doesn't work, I can't. Now as to why they will ping for a while and then stop pinging, I have no idea :)

Anyway, at least it's good info to know that you aren't seeing any issues on your end with the new sticks, so at least that means it has to be something with my setup. No clue what it is, but I'll continue troubleshooting as best I can. Thanks.
[Fire TV Themes and Apps] jocala:
adbLink 3.9 Released

adbLink 3.9 01/03/19

macOS: Dark mode support.

macOS: Use iTerm as an alternative to Terminal

Windows 7: Console didn't open for some users. Fixed.

Moving Kodi data to external storage fails if external

storage lacks an Android/data/ file structure. Fixed.

Utility menu function: Set timers: Turn Fire TV sleep and

screensaver timers off or set timers to custom value.

Check for pull destination validity added to file manager

Log file location for Windows incorrect: Fixed.

Kodi restore for hosts (Windows/Mac/Linux) removed.

Restore is now only functional for Android devices.

Utility menu function: Show architecture

Displays the architecture for connected device

Help website references changed from http to https

HTML help added for new functions above

https://www.jocala.com
[Fire TV Themes and Apps] Segjin:
Unable to download the windows version:

You don't have permission to access /downloads/adblw39.exe on this server.
[Fire TV Themes and Apps] jocala:
Fixed. Thanks for the heads-up.
[Fire TV Themes and Apps] Segjin:
Nice! Thanks for the quick fix! :good:
[Fire TV Themes and Apps] Segjin:
I haven't used this in a while, so I'm not sure what version I last used, or when this issue appeared, but with the windows version, I cannot edit a file that has spaces in the name.
[Fire TV Themes and Apps] jocala:
Thanks for the feedback. Known issue for rooted systems, not sure why it's happening in non-rooted.
[Fire TV Themes and Apps] Kruk07:
Hi

I try to push some files to Fire Stick 4k but panels in file manager are blanks. Also I can't create any folders. Fire Stick is not rooted and I was able to install OpenVPN. I also tried with Disable root option ticked but still blank panels.

Any ideas?
[Fire TV Themes and Apps] jocala:
I've had a few reports of this issue, but haven't been able to reproduce it on any of my devices, however I'm still investigating. Please post your computer's OS, the Fire OS version and any other details, for instance, does dropping back to a previous version fix the issue, thanks.
[Fire TV Themes and Apps] Kruk07:
Hi

Windows 10 1809 x64

Fire Stick 4k OS 6.2.5.8 (NS6258/1604) / Fire TV Home version: 6.1.2.1-005

Older version tested and still the same: 3.0, 3.6, 3.8 and 3.9.

Also tested on another laptop and still the same.

I never used your app before so maybe I'm doing something wrong. App installed, IP added and connected to device. Computer authorised by Fire Stick. Selecting file manager. Did I missed any steps?

Thanks
[Fire TV Themes and Apps] jocala:
Thanks for the extra detail. I've ordered a 4K stick for testing purposes, be here next week.
[Fire TV Themes and Apps] Kruk07:
What's interesting, when I used ES File Explorer on my Fire Stick I have found the folders I created and files I pushed. So the it's working but for some reason folder/file structure is not displayed in panels.
[Fire TV Themes and Apps] jocala:
Just finished installing the 4K stick. Like the pendant and cube ftvs, adbLink's file manager works fine on this device on my network. So, I'm still clueless why this is issue is occurring for some folks. I've had three blank panel reports thus far.
[Fire TV Themes and Apps] Kruk07:
Thanks for checking. I have switched off my AV (KIS) and still the same. I'm not using abdLink to often so I'm ok with pushing files to main dir. I can later move them with ES File Explorer.
[Fire TV Themes and Apps] kasi1956:
Hi, Jocala!

I also have the problem - the file manager displays empty fields at startup. ADB Shell works fine.

I have AFTV Stick 2 with the latest firmware which has NO root. After the factory reset only kodi 18 was installed.

Client: Win7pro & adblink v3.9

Enabling or disabling the "Disable root" checkbox has no effect.

What can i do to resolve the problem?

do you need more info?

thanks for help!

---------- Post added at 04:43 PM ---------- Previous post was at 04:10 PM ----------

I found this error message

shell@tank:/ $ /data/local/tmp/adblink/busybox --help

/system/bin/sh: /data/local/tmp/adblink/busybox: not executable: 32-bit ELF file

1|shell@tank:/ $

is this important on FireTvStick?
[Fire TV Themes and Apps] jocala:
I've had sporadic reports of this, but thus far I haven't been able to duplicate the issue on any device whatsoever. I'm still considering options and welcome suggestions and feedback. I've attached a screen-shot of adbLink v3.9 on Windows 7 pro with the file manager active. It's connected to a 4K Stick.
[Fire TV Themes and Apps] jocala:
Yep. Thanks for the feedback, I'm working on a solution.
[Fire TV Themes and Apps] jocala:
I believe I've solved this issue and am working on a release. Thanks for the feedback, it was very useful.
[Fire TV Themes and Apps] jocala:
adbLink 4.0 released

adbLink 4.0 02/02/19

File manager empty panel issue fixed

If file manager still has a blank panel you may have

to reinstall busybox on your device:

1. Utility menu

2. Reinstall Busybox

Google+ support links removed. Google+ is EOL 4/2/19.

https://www.jocala.com
[Fire TV Themes and Apps] kasi1956:
Many thanks for the patch / new version!

works fine!!!!!!
[Fire TV Themes and Apps] jocala:
Excellent! Thanks again for your feedback, it was very helpful.
[Fire TV Themes and Apps] jocala:
Just to reiterate, if file manager still displays blank panels with v4.0 adbLink, reinstall busybox via the utility menu. That should fix the issue..
[Fire TV Themes and Apps] kasi1956:
Hi Jocala,

sorry for an new bug report ;)

The following problem exists in the file manager

With the command "push" I want to send a folder to the FireTvStick.

In the file manager panel I select the destination folder

For example: /sdcard/Android/data/org.xbmc.kodi/files/.kodi/userdata/addon_data/

Then I press the "Push" button and select the source folder.

For example: c:\KodiSave\weather.yahoo

In the destination the folder (weather.yahoo) is created and a subfolder with the same name is also created, in which the files are located.

For example: /sdcard/Android/data/org.xbmc.kodi/files/.kodi/userdata/addon_data/weather.yahoo/weather.yahoo/

Do you have any idea how to solve this?

greetings!

copy from logfile:

userpush started

"./adb.exe" -s 10.128.5.175:5555 shell mkdir -p "/sdcard/Android/data/org.xbmc.kodi/files/.kodi/userdata/addon_data/weather.yahoo"

"./adb.exe" -s 10.128.5.175:5555 push "C:/KodiSave/weather.yahoo" "/sdcard/Android/data/org.xbmc.kodi/files/.kodi/userdata/addon_data/weather.yahoo"

[100%] /sdcard/Android/data/org.xbmc.kodi/files/.kodi/userdata/addon_data/weather.yahoo/weather.yahoo/settings.xml: 100%

C:/KodiSave/weather.yahoo\: 1 file pushed. 0.0 MB/s (632 bytes in 0.016s)
[Fire TV Themes and Apps] jocala:
Thanks for the report. I'll look into a fix for v4.1
[Fire TV Themes and Apps] jocala:
Patreon

I've created a Patreon support page for adbLink. If you can help support the project I'd appreciate it!
[Fire TV Themes and Apps] KnifeFed:
After updating to 4.0 I now get the following error while trying to edit a Kodi XML file, on macOS 10.14.3.

Edit failed adb: error: cannot create '/private/var/folders/6v/6rr2qqx94q5csxzhr_p1bp600000gp/T/AppTranslocation/703741DA-8C0D-4EA9-9EC0-1873442B28D5/d/adbLink.app/Contents/MacOS/adbfiles//advancedsettings.xml': Read-only file system

How can I grant it write access?
[Fire TV Themes and Apps] Kruk07:
I was able to test this new relaes just now and all is working fine. Many thanks for so prompt fix.
[Fire TV Themes and Apps] jocala:
Somehow, your installation is flawed. As you see from the error message, adbLink.app is buried deep within the /private/var/folders area of your Mac's filesystem, which is read-only by design. I suggest you reinstall, making sure adbLink.app is located in an area where you have read/write privileges such as /Applications or in your /Users/<home>. Your device database shouldn't be affected by a reinstall.
[Fire TV Themes and Apps] KnifeFed:
When updating, I just replaced the .app-file, so it's weird that it broke the installation. It was indeed solved by removing all traces and reinstalling. Thanks.
[Fire TV Themes and Apps] mrnamster:
When installing multiple apps on two connected devices at the same time, the program switches to install apps to whatever device is highlighted in the list.

Also, when launching or closing another instance of Adblink, it causes the current operation in the open Adblink to fail.
[Fire TV Themes and Apps] jocala:
Thanks for the feedback.

1. This is by design. APK installs default to the selected device, not all connected devices.

2. adbLink doesn't support running multiple instances of the adb server. It's possible to do so (via the command-line: adb -P 9999 start-server / adb -P 9999 kill-server), but coding support for this would be significant.
[Fire TV Themes and Apps] mrnamster:
I understand it doesn't install to all devices in the list, but if I start installing multiple apps to one device, then simultaneously install another batch to a second device, it will not correctly complete the first batch task since the second device will be highlighted. It will switch to complete both batch tasks to the second device since it's highlighted.

The app is still great. Thank you.
[Fire TV Themes and Apps] jocala:
Thanks for the clarification. I'll look into it.
[Fire TV Themes and Apps] jocala:
adbLink 4.1 released

adbLink 4.1 04/09/19

Folder push recursion fixed.

Utility menu/Program start: Window title corrected.

https://www.jocala.com
[Fire TV Themes and Apps] kasi1956:
Many thanks for the patch / new version!
[Fire TV Themes and Apps] auggie2k:
The app is fantastic, I've been using it for over a year now and it's a life saver. I am planning to get a Chromebook shortly, any plans to have an app that is compatible with ChromeOS? Cheers!