3
adbLink v5.1
source link: https://forum.xda-developers.com/t/adblink-v5-1.3389826/page-24#post-87483875
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
adbLink v5.1
Sure. The recent email address change invalidated my PayPal account token for donations. I just discovered this today, and additionally I neglected to update the embedded support link
in my source code. Rather than releasing an updated 4.9 I decided to drop v5.0. Mea Culpa, sorry for the bother!
No bother at all, just always tend to furrow my brow a bit at full increments.
Last edited: Apr 22, 2022
M1 Beta: You may get an error message when opening these apps saying they are damaged and should be deleted. Fix this with the terminal command: "xattr -cr /path/to/adbLink.app". No idea why Mac is marking these apps as damaged. Investigating ...
Edit: Fixed. The installation file is now in pkg format.
Edit: Fixed. The installation file is now in pkg format.
Last edited: Apr 23, 2022
Another development request if you don't mind. It would be nice to have the ability to set a default Kodi backup/restore directory, either globally or by device, so that directory would autopopulate whenever the Backup and Restore buttons are selected.
Reactions: jocala
Just so you know, the statically linked version for m1 doesn't say the app is damaged, but instead it crashes upon launching, so perhaps best to stick with the other one
Thanks for the feedback. I just setup a VM to test with and discovered the same thing.
Beta 2 of adbLink for Apple Silicon is available at http://www.jocala.com
Beta3 of Mac adbLink 5.0 is available at http://www.jocala.com.
This release is a universal binary that runs on either Intel or Apple Silicon, so any Mac user can run it. Beta feedback is gratefully appreciated.
This release is a universal binary that runs on either Intel or Apple Silicon, so any Mac user can run it. Beta feedback is gratefully appreciated.
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.
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.
Reactions: blaacksheep, RiCkLaR, forkup and 3 others
P650SE
Senior Member
Aug 14, 2013
Thank you for developing this very helpful program!
There is one thing I would like to suggest, I think that when selecting files/folders to push to the device using the ADB file manager, it would be a lot better if the selection dialogue instead used a full-sized Windows Explorer open interface, rather than the current simplified dialogue as pictured below?
The advantages of this idea would be, a resizable larger selection window with the ability to see file and folder thumbnails (especially helpful when transferring images via ADB) and also, much easier navigation via the navigation pane in Windows Explorer, eg. direct access to set directories via Quick Access shortcuts (instead of repeatedly clicking and scrolling through folders to navigate)
There is one thing I would like to suggest, I think that when selecting files/folders to push to the device using the ADB file manager, it would be a lot better if the selection dialogue instead used a full-sized Windows Explorer open interface, rather than the current simplified dialogue as pictured below?
Reactions: jocala and Hotrod369
Thanks for the feedback. I agree an explorer-style file manager would be very nice. Keeping in mind it would have to be portable across three architectures.
Reactions: P650SE
Peter03_de
New member
Aug 12, 2019
Hello,
I have downloaded the latest version of adblink2 v5.1, but I can't find any button to backup or restore the code.
In the version 4.3 of adblink this is still present.
Is there still the possibility? If yes, where?
Thanks in advance for any feedback.
Greetings
Peter
I have downloaded the latest version of adblink2 v5.1, but I can't find any button to backup or restore the code.
In the version 4.3 of adblink this is still present.
Is there still the possibility? If yes, where?
Thanks in advance for any feedback.
Greetings
Peter
adbLink2 does not have Kodi features. You want adbLink.
Peter03_de
New member
Aug 12, 2019
Hello jocala, thanks for the message.
I thought adblink2 is the successor of adblink.
I will try it once.
Could I also make a backup of the entire firetv and then transfer it 1:1 to a new stick?
I thought adblink2 is the successor of adblink.
I will try it once.
Could I also make a backup of the entire firetv and then transfer it 1:1 to a new stick?
adbLink does backup/restore of Kodi data. It does not do a 1:1 copy of a device, or backup applications. Basically, to clone a Kodi device you backup the data of your first device then after installing Kodi on the new device you restore the backup made from the first.
You can see a video demo of backup/restore at the link below:
You can see a video demo of backup/restore at the link below:
Reactions: RiCkLaR
Peter03_de
New member
Aug 12, 2019
Thanks for this Info.
Reactions: jocala
I can't get adbLink to connect to my firestick. If I launch the console from abdLink I'm able to manually initiate a connection the device and it connects fine. When I try to connect with adbLink it immediately fails, it fails so fast with the message it's hard to belive that adbLink is even attempting to make a connection. This is what the log looks like...
I've turned off firewalls, and I've tried different port numbers instead of 5555. I'm using windows 11. I find it strange that adbLink is seeing multiple IP interfaces, with APIPA. Obviously, my laptop is the .23 IP, IDK where it's getting all the APIPAs from, who knows that might be the issue. IDK. Does anyone have any ideas?adbLink 5.1
092422194140
IP: 169.254.213.115
IP: 169.254.204.179
IP: 169.254.184.52
IP: 192.168.1.23
IP: 169.254.49.181
Windows
------------
SELECT Id FROM device WHERE description="firestick"
SELECT daddr FROM device WHERE description="firestick"
start-server failed!
starting server
SELECT Id FROM device WHERE description="firestick"
SELECT daddr FROM device WHERE description="firestick"
SELECT Id FROM device WHERE description="firestick"
SELECT daddr FROM device WHERE description="firestick"
Unable to connect to: 192.168.1.27:5555
process time duration: 1 seconds
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK