yashsingh1/xdaforums huggingface dataset:
[Fire TV Themes and Apps] RootedLee:
Hello jocala. Thanks for adbLink!

May I share a few observations and recommendations regarding the File Manager module?

Even though my device is rooted (via Magisk), on first launch file manager displayed blank panels. Accdg. to your File Manager Help page that is because my "system's 'su' utility does not accept parameters passed via the shell, something that adbLink requires", and I should "solve this by installing SuperSU by chainfire".

This is rather outdated information because:

Chainfire retired from SuperSU 2017-10-03 (latest release from 2017-10-01)

Magisk has been supporting su with ADB since at least October 2017 by simply toggling "shell" from 'off' to 'on' in Magisk superuser settings, and setting superuser access to "Apps and ADB" in Magisk Manager, which I can confirm

Magisk has been far superior to Chainfire's SuperSU in several side-by-side comparisons and test, like Magisk vs SuperSU - XDA and Which Superuser is better, SuperSu or Magisk Manager?

Files and folders are "sorted" completely helter-skelter. I have not been able to fathom the "sorting" order at all. Can you please sort by name as default, and add options to:

also sort by at least date,

maybe also size together with an option to also sort folders by size,

an option to sort files and folders separately (folders on top), or sort them together (mixed)

a

Files and folders are not differentiated graphically, which is quite awkward. Would you please distinguish between them? Examples:

[IMG="Droid Manager"]https://img.xda-cdn.com/vzF71af0Dvd3bCeoarFjwWRC_yA=/https%3A%2F%2Fimg.xda-cdn.com%2FAQvmofFcGaxKSuFnXdiuxxglCx8%3D%2Fhttps%253A%252F%252Fimg.xda-cdn.com%252FXQd4suUtR53C_EA3-bE1EZR7kWg%253D%252Fhttps%25253A%25252F%25252Fimg.xda-cdn.com%25252FSol6hhTIaZ8qbxitL9rPLv5zSsc%25253D%25252Fhttps%2525253A%2525252F%2525252Fimg.xda-cdn.com%2525252FHkhTz8Q3KsbZlyc6fp2LdMVAyUA%2525253D%2525252Fhttps%252525253A%252525252F%252525252Fimg.xda-cdn.com%252525252FjTFG_N775HKeaYUf804oG8Bhhu8%252525253D%252525252Fhttps%25252525253A%25252525252F%25252525252Fcloud.addictivetips.com%25252525252Fwp-content%25252525252Fuploads%25252525252F2012%25252525252F08%25252525252FDroid-Manager-Android-PC1-File-Manager.jpg[/IMG]

[IMG="ADB File Browser OSX"]https://img.xda-cdn.com/x4EnT0G-Y7SOWMxoE1cQjzpBR_s=/https%3A%2F%2Fimg.xda-cdn.com%2FDbZygR29uQCYN_L7UTZYS8THH_U%3D%2Fhttps%253A%252F%252Fimg.xda-cdn.com%252FMej1w9SXTS5xAjZuOsOB_L4FzIE%253D%252Fhttps%25253A%25252F%25252Fimg.xda-cdn.com%25252FGY9WGkUt6wYBDIMiMvYRVPZMjp8%25253D%25252Fhttps%2525253A%2525252F%2525252Fimg.xda-cdn.com%2525252FcxpBM_wX2mlL9ZXcN3dZzUYtuCE%2525253D%2525252Fhttps%252525253A%252525252F%252525252Fimg.xda-cdn.com%252525252FvwlZwoABquC0jpR6itGOMzjV8Pw%252525253D%252525252Fhttps%25252525253A%25252525252F%25252525252Fdl.xda-developers.com%25252525252F4%25252525252F7%25252525252F6%25252525252F2%25252525252F5%25252525252F4%25252525252F2%25252525252FADB_File_Browser_OSX.jpg%25252525253Fkey%25252525253DudfCfykORh4kJBfYkX-YAg%252525252526ts%25252525253D1558381777[/IMG]

Thanks again for adbLink. I hope you can relate to my suggestions :) ?
[Fire TV Themes and Apps] jocala:
I don't own a Chromebook, but supposedly they have an installable Linux compatibility layer of some type. At a minimum to run the Linux version of adbLink you'll need an x86_64 Ubuntu GLIBC 2.27.
[Fire TV Themes and Apps] jocala:
Thanks for the feedback. I'll look into your suggestions for the next release.
[Fire TV Themes and Apps] ldeveraux:
Latest (last?) beta is working perfectly well for most people, while Magisk is certainly a bit more complicated. Not to mention, doesn't Magisk require an unlocked bootloader?
[Fire TV Themes and Apps] RootedLee:
[MENTION=2718012]jocala[/MENTION] : fine. And for the website edits you wouldn't even need to wait for the next release .. ;)

I'll get back with you shortly on su via adb shell for *working* root access in your File Manager (no full adb root via insecure adbd necessary) even with Magisk. Teaser/ spoiler alert:

adb shell "su -c ls /data/data"

as a working example.

[MENTION=1360535]ldeveraux[/MENTION] : Complicated? I installed Magisk, and from it YouTube Vanced and Xposed, then added Xposed modules.. even my banking app works - no idea of any issues.

Any kind of rooting is surgery. Magisk can root WITHOUT modifying the system. Why has the majority been choosing Magisk over SuperSU, and why has nobody fully picked up on its further development? Because a) (metaphorically speaking) it's less risky to have surgery on the foot than on the head, and b) Magisk's module store is awesome and really well established.

Feel free to read the comparisons .. ;)
[Fire TV Themes and Apps] ldeveraux:
SuperSU just worked; flash a zip and install an apk. While ideally the same for Magisk, more have issues in practice. You didn't address the need for unlocked bootloader for Magisk, but I thought that was the case. Historically, SuperSU was more compatible across a larger range of devices

The "majority" don't choose Magisk over SuperSU, the learning curve is far greater. It's a trade off between ease of use (SuperSU) and functionality (Magisk). Some people want something to just work, while others want more customization. SU isnt developed any more because CF sold out and left development to the chinese company who couldn't care less about development.
[Fire TV Themes and Apps] RootedLee:
allright. Many choices there are. My ROM creator testified Magisk compatibility so I installed it, done. Also I've been having TWRP installed for years anyhow. I really don't care if Magisk uses magisk.img to boot rather than boot.img as long as all I need is working fine. So when CF indeed turned Chinese, one more reason to use Magisk LOL.

Above all let's get back to this thread's topic, OK? I mentioned Magisk in my post merely because the statement on the file manager page IS outdated, beyond argue. No reason at all to NOT add the Magisk relevant info. That's all .. ;)
[Fire TV Themes and Apps] jocala:
I first used this method in adbLink 3.2, released 05/06/17 (c++ source is available at jocala.com).

if (checkRoot())
rootShell = " shell su -c ";
else
rootShell = " shell ";
[Fire TV Themes and Apps] ldeveraux:
Sorry, I tend to get off topic too easily ;) It needs to be clarified whether Magisk can be used without bootloader unlock, because some FireTV devices either don't have that, or have the option not to flash the image. I'm in the same boat as you; if I can install TWRP I will. But some don't accept that option.
[Fire TV Themes and Apps] RootedLee:
thanks for the code sniplet. hm, you did.. but it's not working correctly here. When my phone is connected booted into Android, e.g. displaying /data/data in adbLink 4.1 takes 30 seconds or so, and when trying to pull data it takes forever. Also sadly locked files will interrupt pull transfer completely, rather than simply ignoring errors and displaying them after copy. (suggestion: force switch for push/ pull etc. in prefs or even as default)

However when the phone is booted into TWRP, the same actions are lightning fast.

I think TWRP has insecure adbd activated. Does adbLink then connect via adb root via a function which is called before checkRoot() which (only) forks into adb shell and adb shell "su"?

Do you have any more thoughts and insights on this?
[Fire TV Themes and Apps] jocala:
adbLink doesn't depend on or utilize root for connections. It merely makes use of su if it's detected for access to partitions and files.

https://youtu.be/QgFThUyMe3U

The video above was done using a Lenovo device rooted with Magisk and TWRP. The connection is via IP address. As you see, I can't duplicate your problem here. Network lag could be caused by any number of issues. In your case, I'd try connecting via USB.
[Fire TV Themes and Apps] RootedLee:
Thanks for the video demonstration. Had to install a YouTube zoom add-on into my browser to see what you were doing ..:cyclops:

The lag happens regardless of connecting via USB or via IP.

Disabling Xposed did not make a difference, either. And neither did updating the adb and fastboot binaries inside adbLink to the latest from platform-tools (v.1.0.41 - 28.0.3-5475833)

Let me ask because I am by now somewhat uncertain about it: it is *not required* to have either Kodi or SPMC installed on either the phone or in macOS for the file manager to work with adb shell su for folders like /data/data, is it?

Might be it's the ROM I'm using. Do you know if any of the preferences mentioned by Alex P. are a prerequisite for adb shell su to work correctly? Does any of these files on your Lenovo

/system/build.prop
/system/default.prop
/data/local.prop

contain the line ro.debuggable=1 (or even ro.secure=0)?

i want to get this going - trying your Windows adbLink version next.
[Fire TV Themes and Apps] jocala:
No and no.
[Fire TV Themes and Apps] RootedLee:
all right, I did what I could but again to no avail:

- carefully edited /system/build.prop with ro.debuggable=1 and ro.secure=0 (making sure the file's perms and owners stay the same), reboot, test

- tried adbLink Windows

- tried in Total Commander Windows after adding the adb plugin. Interestingly browsing is lightning fast when connected to booted Android- no lagging at all, but pull operation is as slow as in adbLink.

- running adbLink Windows with adb.exe from Total Commander adb plugin (v.1.0.40 vs. v.1.0.39 from adbLink) - no difference

Anyway, this all points to that the ROM does not handle adb as slick as expected. I've already let the dev know.

I did what I could, got a few steps further and can perform many more operations than simply via MTP or with Odin, so it's good for now.

Thanks jocala for adbLink and for your support here - both very much appreciated. Good luck with ramping up the File Manager UI and sort order.

Take care
[Fire TV Themes and Apps] RootedLee:
got it WORKING !! The difference betw. your Lenovo and my Samsung is very most likely that yours is equipped with an insecure adbd binary by default and my Samsung with a secure one which blocks many adb operations, causing lags. So installing an insecure adbd (+ Magisk SELinux Manager prior) was THE KEY! More later, maybe tomorrow, am out of the door now.
[Fire TV Themes and Apps] RootedLee:
[MENTION=2718012]jocala[/MENTION] : I'm very close to getting to the very bottom of this.. Can you please share one little more detail:

Connected to your Lenovo device rooted with Magisk and TWRP, when you run 'adb root', do you get

"adbd cannot run as root in production builds", or

"adb is already running as root"

?
[Fire TV Themes and Apps] RootedLee:
By now it's coming along rather nicely here ? I learned that even "shell su" requires an (insecure) adbd on the phone so that adb switches to root when starting on the computer OS for seamless access to /system/... and /data/data/...

After installing Chainfire's adbd insecure (unfortunately discontinued and outdated) on my phone, adb via your trolCommander is working pretty nicely and swiftly. The old app is using an old adbd binary from Android 5.0 (sdk 21) - my ROM is 7.1.1 (sdk 25), oh well.. (no success yet in creating a root capable adbd from my current ROM's boot.img YET .. )
[Fire TV Themes and Apps] jocala:
jocala.com

I've reverted jocala.com from https back to http.

To download adbLink visit: http://www.jocala.com

You may have to clear your browser's cache; I had to for Chrome, otherwise it will redirect to https. This is a pita, sorry for the confusion.
[Fire TV Themes and Apps] jocala:
adbLink 4.2 released

adbLink 4.2 07/14/19

Open a "stop application" dialog if Kodi is running when the

restore button is selected. (if Kodi is running a restore

cannot be done).

jocala.com has reverted to http from https.

Windows 7 users may need to clear Windows 7 DNS cache:

From a command prompt type “ipconfig /flushdns” (without the quotes).

Your browser may also need to clear its cache as well.

adbLink 4.2 reverts internal references from https://jocala.com

to http://jocala.com

download at http://www.jocala.com
[Fire TV Themes and Apps] jim16127:
[MENTION=2718012]jocala[/MENTION]

When connect via USB on a Linux machine, whenever I click on any option it says "busybox install failed. See log." Any idea how to rectify this?

---------- Post added at 02:25 AM ---------- Previous post was at 02:08 AM ----------

[/COLOR [MENTION=2718012]jocala[/MENTION]

When connect via USB on a Linux machine, whenever I click on any option it says "busybox install failed. See log." Any idea how to rectify this?
[Fire TV Themes and Apps] jocala:
There should be a message in your log showing the specifics of the failure. If you like, you can email the log to jocala@jocala.com, or send me a link to a pastebin. If emailing, please copy/paste the log in text format, no screenshots.
[Fire TV Themes and Apps] jocala:
Just tested with Mint 19, no issues with busybox.
[Fire TV Themes and Apps] Embee11:
No response to "New" device, ever.

I can live (unhappily) with the fact that it takes 12-15 mins before the GUI shows up after launching under 64-bit Windows 7. But once it finally shows up, when I press "New" to add a new device/IP, I get no response at all. Ever. No matter how many hours I wait. The same is true if I manually enter an IP into the Ad Hoc field and press Connect -- nothing ever happens.

I understand that it's most likely that I have some kind of problem on the Windows box, but in either case I have no idea how to troubleshoot this problem. If you could tell me how to create a "device" file (probably XML), or where to download an example file, I could at least use adblink to do what I want (simple stuff).

Please help me out. Thanks!
[Fire TV Themes and Apps] jocala:
adbLink's device data is stored in an SQL database, not a XML file. There's no file you can download that will help you out.

Your situation is certainly atypical, to say the least. I'd try a re-install.
[Fire TV Themes and Apps] =XD=Magoo:
adbLink

I have a FireTV (2nd Gen) running KODI Leia. Kodi will not start once I move the data from internal memory to the SD card. Everything works again once I move the data back to internal memory. Has anyone had this issue? Is there a fix?
[Fire TV Themes and Apps] jocala:
I no longer own a 2nd gen ftv, but testing with a different device moving data to an sdcard seems to work w/o issue using Leia.

Did you use adbLink's move function? Check the file /sdcard/xbmc_env.properties and make sure it's pointing to your moved data.
[Fire TV Themes and Apps] jtstrickland:
Change default app install path?

Hello, Ol' Noob Green here.

If this has already been asked and answered, I apologize. This is a big town.

I created partitions in a 128 gb usb drive for app installation and for additional storage using a "cook book recipe" on Amazon Firestick 4k, and now the firestick generally stores new programs in the usb "internal" storage. I had backed up my apps before doing a factory reset on the firestick, and when I install them with ADBLINK, it puts them back in the 8gb internal memory. Is there a way to change the default path in ADBLINK to install them in the USB "internal" memory? TIA.

Also, is there a way to backup downloaded apps and settings of the firestick? It seems like there should be a way, but I'm too green to figure it out. That's basically what it does with KODI. If anybody can point me in the right direction here, also, I will appreciate it.

Ol' Noob
[Fire TV Themes and Apps] jocala:
adbLink 4.3 Released

adbLink 4.3 01/24/20

Fix for spurious "device unauthorized" when connecting

Internal support links reverted to http from https

http://www.jocala.com
[Fire TV Themes and Apps] ForForkSake:
Great app - although a version without the kodi stuff would be good.

Built-in WIFI/USB remote has got me out of some situations - especially when installing Lineage and remote doesn't pair..... easy to use, quick to connect, great job!
[Fire TV Themes and Apps] =XD=Magoo:
Sorry for the delay in responding to you. I just downloaded the latest version of adbLink v4.3 and have the same exact issue. I used the program to move the KODI data to the sdcard. Here is the path to the data: xbmc.data=/storage/sdcard1/Android/data/org.xbmc.kodi/files/
[Fire TV Themes and Apps] jocala:
I'm sorry, I can't duplicate your issue. I tried with two different Android devices, and had no problems.
[Fire TV Themes and Apps] Michajin:
Fantastic tool- I use it on my tablets too! Great Job!
[Fire TV Themes and Apps] ElroyJx:
I use this to restore my wear os watch quickly after a reset without the play store.
[Fire TV Themes and Apps] jocala:
That's an interesting usage, thanks for the info!
[Fire TV Themes and Apps] Embee11:
Hi, Jocala, and thanks!

I'm having a problem I can't solve. I go into File -> Preferences, press the "Pull folder" button, then browse to an existing folder that I wish to use for that purpose, and press OK. I then connect to my Fire TV, and enter the File manager. But every time I try to pull a file (say, from "storage/sdcard0", I get an error message reading: "Pull destination does not exist".

I've tried re-installing adbLink 4.3 for Windows, but I keep getting the same error.

What am I doing wrong, please?

Thanks!
[Fire TV Themes and Apps] jocala:
Check your active record and see if the pull directory there is invalid. That overrides the global pull directory in preferences.
[Fire TV Themes and Apps] Embee11:
Thanks for your prompt reply! Forgive me, please, but where can I find the "active record" you speak of under Windows 10? I've searched all the XML files and the registry, but I was unable to find something like that.

Would you kindly tell me where to find that? Thanks!
[Fire TV Themes and Apps] jocala:
It's the device record that's currently in use. Press "edit" to see the device details, which includes a device specific "pull directory", which will override the global "pull directory" in preferences. I've attached a screen-shot,
[Fire TV Themes and Apps] Embee11:
Sorry it took so long to get back to you, but that did the trick! Thanks very much!
[Fire TV Themes and Apps] sniktaw:
Trying to move Kodi data but getting 'no storage found' message.

Firestick 4k USB drive OTG formatted and partitioned. ADB Shell responds to df -h with

/dev/block/dm-2 7.3G 17M 7.2G 1% /mnt/expand/30e950bc-0ed7-4643-aa19-e1eec34d5575

so, I know the USB is being seen but not available as storage some how.

Anyone? Many thanks ;o)
[Fire TV Themes and Apps] sniktaw:
OK, answering myself but for others benefit, maybe ;o)

originally I used:

sm partition disk:8,0 private

to create the USB partition which is formatting your entire USB as internal storage hence, no show in Kodi data move menu.

So, I tried:

sm partition disk:8,0 mixed 50

to create a 50/50 split of internal and external storage and SUCCESS, now Kodi data move menu sees storage
[Fire TV Themes and Apps] jocala:
Good to know, thanks for posting back.
[Fire TV Themes and Apps] jocala:
Gone, but back in 2.05. In the meantime, open adbLink Console and paste the command:

adb shell screencap -p /sdcard/screenshot.png

Then pull the png file from /sdcard. Be aware that the screencap command is failing for some users running OS 5.x. In that case the png file created is zero bytes.
[Fire TV Themes and Apps] anthony2312:
great, thank you
[Fire TV Themes and Apps] Rokkit:
Can you explain how to use the ad hoc directory? Nothing I tried works even though I made the folders internally with Kodi.
[Fire TV Themes and Apps] jocala:
To work with a directory not in the preset, {i.e. /sdcard/xml/} simply type /sdcard/xml/ into the ad hoc field, then use the push/pull/del buttons. The clear button clears out the field. If you created directories with Kodi, they may be under .kodi directory.
[Fire TV Themes and Apps] MordredKLB:
Looks like the llama options are gone. Will those be coming back or is that dead now?

In a less complainy vein, I got Kodi up and running in about 20 minutes with all my settings perfect using your app. Couldn't have been easier. Thanks so much!
[Fire TV Themes and Apps] jocala:
Llama's been gone for many,many moons now. It does not work with OS 5x and the author no longer maintains it. Thanks for the feedback, I'm glad your setup went ok.
[Fire TV Themes and Apps] ftgftg:
I just upgraded from a much older version and the first thing I noticed is that it BEEPs at me

Extremely annoying, how can I turn it off? I never, ever want a program to BEEP at me no matter what. It's doubly annoying when I have media playing.

(That my Fire TV also "clicks" all the time when using the remote is quite annoying as well. I don't see a setting to turn that off.)
[Fire TV Themes and Apps] jocala:
adbLink does not contain any sound output functions. There are no built-in beeps or sounds.
[Fire TV Themes and Apps] ftgftg:
Gotcha, sorry.

Indeed, this is a system error beep. I thought I had taken out all of those. I certainly hadn't gotten any such beeps in a loooong time but apparently the popup window call used here uses one not used by my other programs that I had missed.

Thanks.
[Fire TV Themes and Apps] jocala:
No prob, you're welcome.
[Fire TV Themes and Apps] thefamousmoe:
When I move Kodi data to external HDD? Does that mean the Kodi data (cache, thumbnails, etc) will continue to be saved there? Or it is just moved there as sort of a backup?
[Fire TV Themes and Apps] jocala:
No, this changes the live location of Kodi's data store. It's not a backup.
[Fire TV Themes and Apps] thefamousmoe:
Great! Just what Ive been looking for. Thanks for all the hard work you put into this.
[Fire TV Themes and Apps] jocala:
adbLink 2.05 released

adbLink 2.05 changelog

View/copy Kodi log files

Bug condition in busybox installation fixed.

Screen capture function restored. See help.

"Device Unauthorized" help file added.

For drive mounting & samba please use

play store services.

http://www.jocala.com
[Fire TV Themes and Apps] krakout:
Just tried this, it looks really nice!

Just one question: since in Krypton the advancedsettings.xml cache settings have changed, how does one tell it what files to create/push?
[Fire TV Themes and Apps] jocala:
In Krypton <cachemembuffersize> is renamed to <memorysize> and <readbufferfactor> is renamed to

<readfactor>. Additionally, cache settings now have their own tag <cache>, rather than being in

<network>.

adbLink 2.05 doesn't yet use these settings. 2.06 will allow you to choose between 16 and 17 for

advancedsettings.xml styles.
[Fire TV Themes and Apps] krakout:
Ah, perfect! Thanks for letting us know :)
[Fire TV Themes and Apps] madmackem:
Hi, using this on a laptop Win10 with uhd screen, any way to change the settings so I can see all the info in the boxes?

As you can see its all squashed up!
[Fire TV Themes and Apps] jocala:
This is an unfortunate side effect of high-dpi systems.

It's addressed in adbLink 2.06 (not released yet), but this workaround may help:

Create a system environment variable: QT_AUTO_SCREEN_SCALE_FACTOR=1

On Windows 7,8, and 10 you can do this by pressing the windows icon and typing

"environment". Choose "Edit the system environment variables" (this works in both system or

user environment variables).

On the window that appears, click the "Environment Variables" button and then click

"New". Input QT_AUTO_SCREEN_SCALE_FACTOR for the variable name, and 1 for the variable value.

If you created this variable in the user variables, you will have to log out, and log in

for this change to take effect.

If created in the system variables, you must restart the system.
[Fire TV Themes and Apps] Nickchaves29:
Link for Adb states it's under maintenance. When do you expect to be back up?
[Fire TV Themes and Apps] sniktaw:
Great app! Moved Kodi data to Firestick 4K OTG USB as getting storage warnings. No more warnings and Kodi slowed only very marginally. Couldn't have been easier in the end.
[Fire TV Themes and Apps] Y.G.:
Edit: False alarm. App still works great.
[Fire TV Themes and Apps] drizzt09:
Love this app. very useful for Fire TV and Google TV.

Would love to make a request. Would you be able to integrate scrcpy somehow. this would be a need feature to have integrated

https://github.com/Genymobile/scrcpy