yashsingh1/xdaforums huggingface dataset:
[Fire TV Themes and Apps] githottub:
Well, I guess my Android 12 TV isn't using scoped storage because I was able to use the adbLink file manager to copy everything from /sdcard/Android/data/org.xbmc.kodi to /sdcard/kodi_data/

(BTW: That does make me wonder why it wouldn't just do the backup from the Android folder in the first place. Instead, it seems to immediately look for the kodi_data folder and throw an error if it's not there, instead of at least first trying to backup from the default location if it's not sandboxed... which apparently it isn't since the adbLink file manager was able to copy the files from there.)

Anyway, after copying over everything to kodi_data I then created and pushed the xbmc_env.properties file to the root of /sdcard/. I wanted to confirm Kodi was indeed using the new location so I put a splash.png file in the media folder of the new location and launched the app. It did display the new splash screen. So, other than launching from the alternate location taking ~10 seconds longer than before, which is a bit frustrating, everything is working properly. Therefore, I used the backup function of adbLink and it successfully saved everything to my PC.

So, good news. Backup of a new Kodi install on a new Android 12 TV accomplished and hopefully this information will help anyone else in a similar situation. Thanks again Jocala for your help!
[Fire TV Themes and Apps] sus67:
@jocala

have you idea. One of devices makes restore with userdata folder of Kodi only.

adbLink Log
[Fire TV Themes and Apps] jocala:
I installed kodinerds and backup/restore worked fine. I don't see anything in your log offhand. Can you browse into .kodi/addons via the command-line or via the file manager?

adblink 6.2
/Users/jeff/qtbuild/adblink.app/Contents/MacOS
07/16/24 00:19:40
/Users/jeff
IP:192.168.1.16
macOS
------------
starting server
package: "/Users/jeff/qtbuild/adblink.app/Contents/MacOS/adbfiles/adb" -s R9PT603R69N -s R9PT603R69N shell pm list packages
net.kodinerds.maven.kodi21 is installed
backup function started
"/Users/jeff/qtbuild/adblink.app/Contents/MacOS/adbfiles/adb" -s R9PT603R69N pull /sdcard/Android/data/net.kodinerds.maven.kodi21/files/.kodi/. "/Users/jeff/backups/kodinerds/"
backup: "/Users/jeff/qtbuild/adblink.app/Contents/MacOS/adbfiles/adb" -s R9PT603R69N pull /sdcard/Android/data/net.kodinerds.maven.kodi21/files/.kodi/. "/Users/jeff/backups/kodinerds/"
process time duration: 57 seconds
Backup complete
[Fire TV Themes and Apps] sus67:
This problem appeared overnight, I had previously successfully saved many backups. With adblink or FTP program I can see all Kodi folders, can open them with content and Kodi working well. I suspect it is the Fire TV Cube 3rd gen. itself, I will swap (Amazon Prime days). I will let you know....
[Fire TV Themes and Apps] w8andc:
Need some clarification because it is confusing.

Situation

:

Device concerning is FireTV Stick 4k Max (2nd gen)

Previously have Installed 2 versions of Kodi: Kodinerds 20.5 Nexus + Kodi 21 Omega

Have succesfully changed "scoped storage" through the "adblink" app on my Windows 11 x64 system.

Kodi 20.5 settings were changed and a kodi advancedsettings.xml could be placed at the new location kodi_data

Problem

:

I can start Kodi 20.5 and everything is loaded fine and is working.

Now when I start Kodi 21 the app starts but stated that a migration is taking place. Upon completion of the process I can start Kodi 21.

But if I close kodi 21 and start kodi 20 again, also the migration proces will be started.

Some settings changed earlier must be applied again. Afterwards Kodi 20 runs again normally.

This happens back and forth each time starting another version of kodi.

Question

:

Does exists a

workaround

concerning "scoped storage" and

using 2 Kodi versions

on

same device

to avoid the above described behavior?

Remark

:

Not sure but after using the "get package name" utility in "adblink" the path location for kodinerds is probably: /sdcard/Android/data/net.kodinerds.maven.kodi20.firetv/files/.kodi/.
[Fire TV Themes and Apps] sus67:
Used 1 Kodi version on device.

Today, tried new fresh installation of Kodi 20.5 and Backup was with same behavior (userdata folder only).

Later exchanged to a brand new Fire TV Cube 3 gen. with same configuration and everything working fine in Backups and Restore with awesome adbLInk.

In my opinion looks like hardware problem.
[Fire TV Themes and Apps] jocala:
Currently, I have two devices affected (infected?) by scoped storage: A Max4K stick, and an onn (walmart) streaming box, running Android 11 and 12, respectively.

To run two different Kodis on an Android 11/12 device, using two different /sdcard/xbmc_env.properties files would work (each pointing to a different data directory) , but you'd have to manually switch them, depending on which build you wished to run.
[Fire TV Themes and Apps] ace2048:
There seems to be an issue. On the 2023 Fire Stick 4k Max (2nd gen), when I restore KODI the addons seem to be stuck. Whereas on 2021 max stick, everything works fine. I'm assuming it's an issue with the sandboxed KODI.

It's strange because just several days ago it was working fine.
[Fire TV Themes and Apps] ace2048:
It may be that fire OS 8.1.1.1 is restricting KODI further for some reason.
[Fire TV Themes and Apps] jocala:
I found that after the 8.1.1.1 update my permissions had been reset. Try the set apps permission function under adblink's utility menu, or check permission using the fire stick's settings. Without "write all" permissions, Kodi can't function outside of the sandbox.

If that's not the issue, post more detail. Can your issue be reproduced?
[Fire TV Themes and Apps] ace2048:
permissions has been set to 'write all' permissions, and in the fire TV settings, KODI shows access to 'All Files' . I have attached a KODI log here:

kodi fire OS 8.1.1.1 - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

pastebin.com
[Fire TV Themes and Apps] TX16095:
As a purely anecdotal data point, after upgrading to v6.2, all three of my DIRECTV STREAM Osprey Android 11 boxes refused to accept a previously saved Kodi restore file, which was not a problem with v6.1. As before, the solution was to merely create a new backup file and then install the desired restore file.
[Fire TV Themes and Apps] jocala:
Without adblink logs or a means to reproduce errors, I'm reduced to guesses, sorry.
[Fire TV Themes and Apps] ace2048:
removed.
[Fire TV Themes and Apps] jocala:
Thank you for the feedback, but I can't reproduce your issue. Here is a video showing record addition for both IP and USB connections.

https://youtu.be/Y662kgLx_H8

Diid you check your log for errors?

edit: updated the record addition video
[Fire TV Themes and Apps] Chazaroo1980:
I had the same issue of not being able to give usb devices a name so not being able to select them. Uninstalling the app and deleting c:/adblink folder before reinstalling, fixed it for me. i can only think that updating and then deleting the old saved records before trying to create new was causing an issue.
[Fire TV Themes and Apps] jocala:
I think you're correct. From http://www.jocala.com

Upgrading from earlier versions:

Do not mix content from earlier releases with this release. This includes all files,scripts,

databases, etc. If you do, you will break things. You can run multiple versions of

adbLink, just keep them separate.

So, if your adbLink is installed at the default c:\adbLink location don't install a new version on top of the old. Uninstall the old version or install the new version to c:\[newlocation]. I'll look into making the setup.exe handle this better.
[Fire TV Themes and Apps] krakout:
Just ran 2.06 for the first time, to set up SPMC anew on my AFTV box. I just tried, just for trying's sake, to set the cache settings, but it asks for the directory to be specified. Since these are hardcoded, wouldn't it make sense to automatically push the file to the appropriate directory?
[Fire TV Themes and Apps] jocala:
The cache function pushes the advancedsettings.xml file to the userdata folder of the selected media center. It doesn't ask for a directory.
[Fire TV Themes and Apps] krakout:
Oh, weird... I restarted everything and it worked as advertised indeed, so apologies :)
[Fire TV Themes and Apps] LivinOne:
jocala

Your app never connects to my FTV1 but it connects to my FTV2 properly. Both have the same SSH server app running, with the same settings, and ADB Debug is on. All other apps (WinSCP, Amazon Fire TV Utility, etc) connect just fine.

Looks like you have a bug, it is adding 5555 on the end twice to that connection in the DB. I have completely deleted the DB file and recreated it... same problem

log of problem ...

log of working connection in same, NEW db file...
[Fire TV Themes and Apps] jocala:
Thank you for the feedback. The duplicate port :5555 seen in logs is a cosmetic error in the log routine and has nothing to do with connections. It's on the list for fixes, but not done yet.

I'd like to see a complete log of the failed connection attempt to 192.168.1.15, but in the meantime attempt opening the adbLink console and connect manually by typing:

adb connect 192.168.1.15

See what happens...
[Fire TV Themes and Apps] LivinOne:
I can, and have been, using ADB just fine... I just transferred 1gb of Kodi data to that unit using the Windows based Fire TV Utility app.

full log from adbLink...
[Fire TV Themes and Apps] jocala:
I'd like to see what happens when you attempt a connection manually, using adbLink's supplied adb. Press the adbLink console button, then type or copy/paste:

adb connect 192.168.1.15

This is step one in figuring out a problem.
[Fire TV Themes and Apps] LivinOne:
Your app gives an error when click on the adb console button... Says not connected. I can open an adb console with out issue in Windows... Did it 5 times today.
[Fire TV Themes and Apps] jocala:
You are pressing the ADB shell button. It requires an active connection.

Press the adbLink Console button. It opens a DOS prompt that will utilize the adb.exe supplied by adbLink.
[Fire TV Themes and Apps] LivinOne:
Always fails. AND, even if I replace your adb.exe, in the adbLink folder, with an older/smaller adb.exe from Fire TV Utility --fails on both .15 & .16

cmd snapshot...

Reminder:

1. adbLink 'Connect' button and then ADB opens fine using 'ADB Shell' ONLY for .16 -- not working for .15

2. I just deleted and installed adbLink from scratch, today. Files are not corrupt.

3. I can, and have many times today, opened ADB console from other apps and it works just fine.

2.
[Fire TV Themes and Apps] jocala:
Two problems, one is adbLink-related, the other comes from adb.exe

Problem one:

You pressed the adbLink Console button, the entered "adb connect 192.168.1.16" and got the response:

"* daemon not running. starting it now on port 5037 *"

* daemon started successfully *

This is an issue because the server should be already running. If you start adbLink and don't see the "ADB running" on the status line your installation of adbLink has a problem. Since you are running multiple versions of adbLink and using different adb.exe front-ends as well, make sure they are not in conflict. (previous adb processes running in memory, different versions of adb.exe in conflict,etc)

Problem two:

adb.exe error: unable to connect to 192.168.1.16:5555

In general, when adb.exe refuses to connect to an IP address it's simple (eg: wrong/bad IP, adb debugging off). I'm not saying this is your issue, I'm saying in general.
[Fire TV Themes and Apps] LivinOne:
The issue is something with adblink, other apps work fine. And adblink only fails with one of my ftvs. The other works fine. This tells me there is a bug stopping adblink from connecting to just that one ftv, when all other apps have no problem

And yes, I make sure adb process is not running each time I do a new connection. I've had rooted and romd ftv for 2 years... No issues until I tried your app. Sorry, I can't spend more time on it. I'll just stick with the other apps
[Fire TV Themes and Apps] jocala:
Good luck to you.
[Fire TV Themes and Apps] iOps:
In 2.06 backup of AFTV is broken.
[Fire TV Themes and Apps] jocala:
It works as expected in testing. The backup code hasn't changed since 2.0, and no other reports regarding backup errors from ~70,000 users. But perhaps you've discovered a bug, so please specify your problem and post logs.
[Fire TV Themes and Apps] iOps:
Mh, after installing 2.06 over 2.05 again now it works. There was just a message about not finding "/files/.kodi" or "/files/.spmc".

Anyway no it works again. :)
[Fire TV Themes and Apps] onsoku:
I can't load a splash screen. It tells me "Media folder not found". But it's there...\adbLink\splash. How can I fix it?
[Fire TV Themes and Apps] pennywisetrading:
Hi,

I am trying to connect to multiple devices, can you tell me how I can do this please?

So far I have only managed to connect to one device at a time

If anyone knows how to do this, please advise me on what the process is

Thank you
[Fire TV Themes and Apps] jocala:
adbLink is not finding your Kodi media folder. Have you run Kodi for the first time?
[Fire TV Themes and Apps] jocala:
Select your device via the current device drop-down menu, then press connect. In testing, I've had as many as 10 devices connected.
[Fire TV Themes and Apps] pennywisetrading:
jocala, thank you for your quick reply.

I was using version 2.06 and it did not work, each time I entered a new profile and clicked save, it was not in the dropdown list of devices, however I also installed version 2.05 to try and this worked straight away (so maybe a bug in version 2.06 ?)

While connected to multiple devices, is it possible to Install APK and/or Restore simultaneously on more than one device?
[Fire TV Themes and Apps] jocala:
Deleting the adblink.db file, then restarting 2.06 fixes this issue. It's since been fixed, re-downloading 2.06 should also work.

Yes. However, you won't see any overall speed increase; your bandwidth is just divided differently.
[Fire TV Themes and Apps] pennywisetrading:
Okay so I can connect to multiple devices and it shows them in the list of devices connected however, if I want to install/restore simultaneously, how do I do this? because when I click Install APK/Restore this is done for the Current Device selected only, right?
[Fire TV Themes and Apps] jocala:
There are two ways to run parallel adb processes (both are unsupported, adbLink wasn't designed with this in mind).

1. Install multiple copies of adbLink, each in a different directory. Each will run independently.

2. With a single copy of adbLink installed, start an adb process, then switch to a different connected device to start another process. However, the activity indicator is unaware of parallel ops and will only reflect activity for the last operation started.

Unfortunately, if you choose option #2 , a bug in 2.06 (fixed in upcoming 2.07) prevents parallel adb processes. You can drop back to 2.05 or wait for 2.07 if you want to try this.
[Fire TV Themes and Apps] christoophat:
I'm currently running an AFTV2 +SPMC (installed on SD card) Noticed there is a new version out of SPMC and would like to do a new clean install, this time putting all SPMC (Kodi) files on external thumbdrive. Can anyone post a link or offer the howto on how to accomplish this? Regards.
[Fire TV Themes and Apps] irokutwo:
Mi Box

Curious, does adbLink work with the Xiaomi Mi Box Android TV? I do currently use adbLink on a Shield TV and it works extremely well.
[Fire TV Themes and Apps] jocala:
I haven't tested this box, but there's no reason it shouldn't work.
[Fire TV Themes and Apps] irokutwo:
The reason I asked is because I do not see Network Debugging as a choice in Developer Options on the Mi Box.
[Fire TV Themes and Apps] jocala:
It's pretty straightforward. Press the "Move Kodi Data" button and a dialog will pop up showing your available external partitions. Make your choice and press OK. adbLink will then move your data and write the xbmc_env.properties file needed for Kodi/SPMC to locate the data storage area.
[Fire TV Themes and Apps] jocala:
Well, that's an issue :)

USB should still work. I also seem to remember that with the early release of the Shield, you had to set up via USB, then network debugging was authorized as well.
[Fire TV Themes and Apps] irokutwo:
I am waiting on a male to male USB adapter at the moment. On the Shield TV I disable the Leanback Launcher in favor of the SPMC Launcher. Will I be able to do the same through USB Debugging if for any reason Network Debugging does not reveal itself on the Mi Box?
[Fire TV Themes and Apps] jocala:
No idea, sorry.
[Fire TV Themes and Apps] jocala:
adbLink 2.07 Released

adbLink 2.07 Released

Changelog:

Windows: If installing on top of an existing installation, preexisting

database and log files will be erased.

Select multiple apk files for installation to Android device

Select multiple files for push to Android device

Start/Stop Android apps on connected device

Logs menu item added: view adbLink/Kodi logs

Download SPMC file menu function added

Double-print of port in logfile corrected

Parallel adb processes functionality restored

ADB Port is not reset when switching OS in preferences: fixed

Root menu removed

http://www.jocala.com
[Fire TV Themes and Apps] christoophat:
d/l link still showing 2.06?
[Fire TV Themes and Apps] jocala:
Make sure you update your browser cache.
[Fire TV Themes and Apps] christoophat:
bingo! :good:
[Fire TV Themes and Apps] jocala:
Install/Push multiple files using adbLink 2.07

https://youtu.be/3huMNu5vDe8

This video will demonstrate installing multiple apks and pushing multiple files using adbLink 2.07
[Fire TV Themes and Apps] pennywisetrading:
Excellent work Jocala! Can't wait to go home and test it out! :D

A question regarding 2.05 when connecting to multiple devices, when I click Connect sometimes it doesn't connect/appear in the connected devices straight away and I have to close adblink and reopen it and try again, and it then it usually works. This doesn't always happen but it does sometimes so was wondering if you had any ideas why? do I need to give it a few seconds before I click Connect once I select a different device?

Edit: the first device always connects first time, its the devices after the first that sometimes don't appear straight away
[Fire TV Themes and Apps] jocala:
That's odd, check your log for clues if it happens again. BTW, next time you see lag, try pressing the Refresh ADB button.
[Fire TV Themes and Apps] christoophat:
Installed 2.07 yesterday & used it to:

update SPMC to 16.5, and also to move my data files over to the SD card. Very cool! We watched movies using it last night , everything was fine.

This morning however, now when I try to use SPMC, it won't boot. Have tried restarting AFTV2 several times, but am seeing the same results. I'm kind of lost here on what else it could be, since I didn't change anything , and it worked yesterday. The only difference was using AdbLink. If I wanted to wipe everything & start over, will adblink uninstall SPMC AND also remove the data folder for me? thanks
[Fire TV Themes and Apps] jocala:
You can un-install SPMC with adbLink or the AFTV launcher, however, you'll need to

wipe your external sdcard clean manually and delete the /sdcard/xbmc_env.properties file, or

use adbLink to move your data back prior to SPMC deletion.

adbLink uses the Android "pm uninstall" command to uninstall apps and while it

will delete the default SPMC data area, it doesn't know about the redirect that

the xbmc_env.properties file creates, telling SPMC that its data is located

elsewhere.
[Fire TV Themes and Apps] christoophat:
Figuring I needed to just wipe & start over, I first tried uninstalling it via adblink, but it couldn't seem to find it in the list of installed .apks for me to attempt it, so ended up doing it thru AFTV. During the process, it noted that all data related to the app would also be removed, and I notice the SD now is showing about 2GB more available that when SPMC was installed, so...did it also take out the data folders too (which were about 2.1 GB when I moved them?

Just confused as to why it was working fine last night, but not today...oh well.

Update: I pulled the SD card & looked at it in my PC, and indeed it appears that AFTV does also remove the linked data files from SPMC. All I saw on the card were the normal Android folders
[Fire TV Themes and Apps] jocala:
Unfortunately, the search filter for uninstalls is broken (working on a fix for 2.08). However, scrolling through the list and selecting com.semperpax.spmc will delete SPMC. It's easy to miss a package name when browsing through the list, though.

In my tests, deleting Kodi/SPMC when data has been moved to external locations, does not delete the moved data. It must be done manually. Also, as I mentioned, the /sdcard/xbmc_env.properties file is also left behind. This file will cause problems for a new install if it's not deleted.

adbLiink is mainly just a front-end for Android SDK's adb. No software is bug-free, but I haven't encountered any issues with moving Kodi/SPMC data via adbLink vs doing the same thing manually using the Android SDK.
[Fire TV Themes and Apps] christoophat:
Yes, I'm sure I missed it (kept looking for "spmc" versus semperpax). Anyways, I reformatted the SD card & have reinstalled SPMC using adblink & am rebuilding Movies database, then will move data folder to SD, then continue to rescan TV Shows & Music files. Was time for a refresh anyways, as I've moved my files to a dedicated NAS box & wanted to rescan from the new locaiton.
[Fire TV Themes and Apps] irokutwo:
I can confirm that the Mi Box does not allow for Network Debugging. Utilizing Minimal ADB and Fast Boot with USB Debugging turned on in the Mi Box while connected to a PC via male to male USB cable did the trick. It's a bit of a PIA but I really enjoy having SPMC Launcher over the stock Leanback Launcher.
[Fire TV Themes and Apps] jocala:
Thank you for the report. Using adbLink with the male->male USB cable will work as well.
[Fire TV Themes and Apps] christoophat:
Man, I don't know what is going on here, again SPMC refuses to open after a fresh install using ablink, scanning Movies, set up skin. Then tried to exit, screen froze, had to pull power. Rebooted, and now have same issue, only shows grey screen. Even updated to the latest apk (16.5.1) whack! I posted issue on Github.

One thing I noticed is that after I'd scanned my movies to build up a data file & went into adblink to try & move it to SD card, abdlink said it already existed?
[Fire TV Themes and Apps] jocala:
Video: adbLink Backup and Restore

New video:

Backup and Restore Kodi using adbLink.

https://www.youtube.com/watch?v=tQ0ELD_iQpY
[Fire TV Themes and Apps] jocala:
Sorry to hear that. It will be interesting to hear what Koying has to say.
[Fire TV Themes and Apps] christoophat:
May try reinstalling 16.4 again , just to see what happens.

I was wondering why I couldn't move the data file, or rather why adblink said that /sdcard/xbmc_env.properties already existed? If SPMC/Kodi is installed or moved to the SD card right afterwards (before and media scanning is done), will the data file automatically reside on the SD card? I know when I used it yesterday to move data, it worked, moving over 2GB to SD.:confused:
[Fire TV Themes and Apps] jocala:
adbLink checks for /sdcard/xbmc_env.properties before it does a move. If it exists, it thinks the move has already been done.

In my tests, moving Kodi to SD via AFTV settings does not move data. Settings warns that some apps display this behavior.
[Fire TV Themes and Apps] christoophat:
So would you say the best process would be to install SPMC/Kodi, then scan media, then move SPMC/Kodi to SD card via AFTV, and finally move datafiles to SD card via abdlink?

Currently have 16.4.2 installed on AFTV via ESExplorer and am scanning media now. I closed it & reopened it & it worked, so ...fingers crossed.
[Fire TV Themes and Apps] jocala:
Personally, I don't see the point of moving the Kodi app to sd. You only save a whopping 120Mb or so.
[Fire TV Themes and Apps] christoophat:
hmm...excellent point.