2022-11-05, 23:36
No just the one instance.
2022-11-05, 23:39
Now this is interesting:
C:\adbLink>adb devices -l
List of devices attached
adb server version (41) doesn't match this client (39); killing...
* daemon started successfully
C:\adbLink>
C:\adbLink>adb devices -l
List of devices attached
adb server version (41) doesn't match this client (39); killing...
* daemon started successfully
C:\adbLink>
2022-11-05, 23:55
>> I installed adb yesterday and I can connect to the Firestick, no problem
>> adb server version (41) doesn't match this client (39); killing...
I've seen this occur when two different versions of adb.exe are in use on the same machine. A version is running in memory causing conflicts ...
>> adb server version (41) doesn't match this client (39); killing...
I've seen this occur when two different versions of adb.exe are in use on the same machine. A version is running in memory causing conflicts ...
2022-11-06, 02:03
Sorry but I’m still not understanding what you are asking. If you are able to connect with adblink what is the question?
2022-11-06, 03:06
(2022-11-06, 02:03)wags1 Wrote: Sorry but I’m still not understanding what you are asking. If you are able to connect with adblink what is the question?The OP never stated that he was able to connect with adbLink, he said he could connect with ADB. Very basically, ADB (Android Debug Bridge) is a command-line tool that facilitates communication between Android devices and other operating systems, whereas adbLink, is an amazingly versatile and capable PC/Linux/macOS app that utilizes (requires) the ADB tool in order to function. In other words, one can run and use the ADB tool without adbLink, but not vice versa.
2022-11-06, 03:48
(2022-11-06, 03:06)Txxb161 Wrote:(2022-11-06, 02:03)wags1 Wrote: Sorry but I’m still not understanding what you are asking. If you are able to connect with adblink what is the question?The OP never stated that he was able to connect with adbLink, he said he could connect with ADB. Very basically, ADB (Android Debug Bridge) is a command-line tool that facilitates communication between Android devices and other operating systems, whereas adbLink, is an amazingly versatile and capable PC/Linux/macOS app that utilizes (requires) the ADB tool in order to function. In other words, one can run and use the ADB tool without adbLink, but not vice versa.
Thanks, my bad, I was reading to quickly…😲…I really need to stop trying to do too many things at once…🤣
2022-11-06, 13:59
Oh well, only one instance running now and still can't connect.
2022-11-06, 20:52
1. Attempt connection, then check your log for errors.
2. Close adbLink, then use task manager to kill any adb processes running.
3. Start adbLink
4. Press adbLink's console button:
From the adblink-launched command-line:
c:\> \path\to\adblink\adbfiles\adb connect <device-ip>
What errors?
2. Close adbLink, then use task manager to kill any adb processes running.
3. Start adbLink
4. Press adbLink's console button:
From the adblink-launched command-line:
c:\> \path\to\adblink\adbfiles\adb connect <device-ip>
What errors?
2022-11-06, 21:36
Hi,
1. Attempt connection, then check your log for errors.
SELECT daddr FROM device WHERE description="FireStick"
Unable to connect to: 192.168.1.10:
process time duration: 318 seconds
SELECT Id FROM device WHERE description="FireStick"
SELECT daddr FROM device WHERE description="FireStick"
2. Close adbLink, then use task manager to kill any adb processes running.
yes
3. Start adbLink
yes
4. Press adbLink's console button:
console button doesn't work so I opened a terminal as admin
From the adblink-launched command-line:
c:\> \path\to\adblink\adbfiles\adb connect <device-ip>
What errors?
1. Attempt connection, then check your log for errors.
SELECT daddr FROM device WHERE description="FireStick"
Unable to connect to: 192.168.1.10:
process time duration: 318 seconds
SELECT Id FROM device WHERE description="FireStick"
SELECT daddr FROM device WHERE description="FireStick"
2. Close adbLink, then use task manager to kill any adb processes running.
yes
3. Start adbLink
yes
4. Press adbLink's console button:
console button doesn't work so I opened a terminal as admin
From the adblink-launched command-line:
c:\> \path\to\adblink\adbfiles\adb connect <device-ip>
What errors?
2022-11-06, 23:13
Your image (of an error?) didn't paste. The link goes to some auto site.
>> console button doesn't work so I opened a terminal as admin
Not the same. First, admin's not required and second, adbLink's internal console routines provides paths and scripts for adbLink's adb.exe, scrcpy.exe, busybox and more. If the console button isn't working your adbLink installation is broken. I'd reinstall, also uninstalling whatever adb.exe you first installed prior to installing adbLink.
>> console button doesn't work so I opened a terminal as admin
Not the same. First, admin's not required and second, adbLink's internal console routines provides paths and scripts for adbLink's adb.exe, scrcpy.exe, busybox and more. If the console button isn't working your adbLink installation is broken. I'd reinstall, also uninstalling whatever adb.exe you first installed prior to installing adbLink.
2022-11-07, 00:57
I'll do that and thanks for your help!
this image link should work https://servimg.com/view/19883104/79
this image link should work https://servimg.com/view/19883104/79
2022-11-07, 01:02
>> adb server version (41) doesn't match this client (39);
As before, the error shows the mismatch between two different adb.exe binaries.
As before, the error shows the mismatch between two different adb.exe binaries.
2022-11-08, 14:52
Success!
My backup is running now. I uninstalled and reinstalled three times. I finally found an old directory of a 2020 copy of adblink on my D: drive. I also changed my Path to point to C:\adblink
The console button does not open a terminal however nor the ADB Shell.
Where are the "devices" saved, registry or??
Thank you!
My backup is running now. I uninstalled and reinstalled three times. I finally found an old directory of a 2020 copy of adblink on my D: drive. I also changed my Path to point to C:\adblink
The console button does not open a terminal however nor the ADB Shell.
Where are the "devices" saved, registry or??
Thank you!
2022-11-09, 16:09
I'm glad you have a backup working. There's still something off about the console button not working on your system. Anything in your log appear after pressing the button? Devices are stored in an sqlite database:
C:\Users\<yourid>\AppData\Roaming\.jocala\adblink.db
C:\Users\<yourid>\AppData\Roaming\.jocala\adblink.db
