Due to space limitations in my office, I'd like to deploy my apps via network instead of via usb. Both the phone and the PC are in the same network.
I'm hoping for something similar to Ouya: a checkbox in the settings and then "adb connect "
Connect with USB cable and run:
adb tcpip 5555
Disconnect USB cable and run:
adb connect 192.168.0.100:5555
Change the IP to the actual IP of the device.
Related
I want to connect to an android phone using adb over WIFI. When I do (either by using WIFI Adb or the buildin ADB over Network in android) I get:
$ adb connect 192.168.122.203
failed to authenticate to 192.168.122.203:5555
and adb devices shows the same result:
List of devices attached
192.168.122.203:5555 unauthorized
The solution I find everywhere is: Connect the device via USB and authorize the PC, then connect via WIFI.
Unfortunately I cannot do that, because:
I have installed android-x86 (newest version is android 7.1.2) inside libvrt-manager (KVM).
I have no Idea how I would connect this virtual machine with android via USB to my PC.
So is there a way to authorize a PC for adb usage without every connecting the android Device via USB?
True wireless adb is available only on Android version 11 and above. All version below you have to connect the USB cable and forward the tcp/ip port 5555 and then connect this is called adb over WiFi.
More details are here
I would recommend using a Android 11 emulator if possible if you can't have a USB connection
I have deployed automation script in remote ubuntu-server and i want to execute those script on my local mobile device or emulator.
I have googled for the answer but all the solutions work only if both the device are connected to same wifi network below is the syntax
adb connect ip address:port
when i run the adb connect in my remote server i should be able to access my local emulator or device connected in some other network
My goal is to get some IPMI based data from a HP Server through a local pc. I am using ipmiutil. I have installed the ipmiutil on local pc. I tried the following command to discover the server from local pc.
ipmiutil discover -b XXX.XXX.XXX.XXX.
But it says 1 ping sent 0 responses.
I have also tried the following command:
ipmiutil.exe fru -N XXX.XXX.XXX.XXX -U username -P mypassword
But I got the following error:
ipmiutil fru version 3.12
Connecting to node XXX.XXX.XXX.XXX
ipmilan_open_session error, rv = -3
ipmilan receive from BMC failed
ipmi_open error = -3 receive from BMC failed
ipmiutil fru, receive from BMC failed
I think it may be connection problem. I have checked the lan connection, the server is connected to the lan. Even through putty i can access that particular server. So What may be the reason to not able to connect the server through ipmiutil???
There must be something wrong with the IPMI LAN configuration on the HP server.
My guess is that the IPMI LAN configuration was only partially complete.
So perhaps the IPMI LAN gateway IP/MAC is not set, or the LAN Access Mode is incorrect.
Another possibility is that the IPMI LAN IP address is not set to something unique.
Its IP must be different from the OS IP address, and from other systems on that LAN.
You can see all of the relevant parameters by running 'ipmiutil lan' from the HP server, and comparing the IP and Gateway with that of the HP OS (If Linux: 'ip addr', 'ip route').
Quick question. It is possible to get adb via ethernet cable connected to my laptop instead of connecting to router?
This is possible, though it's a bit more work. Here are a couple of options:
Run a DHCP service on your laptop to assign the board an IP address.
Connect to the board over serial and assign a static IP address.
If the ethernet port in your laptop doesn't autocross, you may need to connect the devices using a crossover cable instead of a patch cable.
DHCP Service
Ubuntu: Use a local service like avahi-daemon.
Mac OS: Enable internet sharing on the Ethernet port.
Windows: I have never tried, but others have used DHCP Server for Windows for this purpose.
Static IP
Use the serial debug console instructions to connect a serial cable and access the shell.
Connect the Ethernet cable between the board and your computer.
Run the following command as root (replace x.x.x.x with a real IP address):
ip addr add x.x.x.x dev eth0
Verify that the IP address was set properly with ifconfig
Run adb connect x.x.x.x or adb connect Android.local
The static IP address will only stick as long as the Ethernet link is active. If the device reboots or ethernet is unplugged, you'll have to run this procedure again.
What I can do:
can connect to desktop Win10pro from phone (wifi/data)
can connect to desktop Win10pro from laptop Win10pro (wifi only)
can connect to desktop Win10pro from work Win7 (desktop)
can connect to desktop Win10pro from TeamViewer
Problem:
When I try to connect to my desktop from my laptop using the usb ethernet dongle, everything listed above seizes to function; only a black screen after logging in. Keep in mind, this setup did work 5 months ago, only thing that changed was that I reset/refresh my laptop because it became bogged down and switched from college to home.
What I've tried:
System Restore on the host desktop
sfc /scannow both host and laptop
resetting network adapter and settings on laptop
checking regedit to make sure 3389 was listening on laptop
disabled/enabled NLA
disabled/enabled RDP on host desktop
enabled RDP on latop
uninstalled network adapter and reinstalled on laptop
turning off wifi on laptop and then trying to connect
If anyone has any other suggestions, that would be awesome.
UPDATE: As someone suggest to get a new USB Dongle, went out and bought one. Still does not work. Extremely laggy and black boxes everywhere.
What solved my issue was using the internal ipv4 address when I am on the local network; else, using the external ipv4 when I am away from home.
Thing to note is that even when I was internally using ipv6, I had a huge issue with this and could not connect to it internally using external ipv4 with :3389 at the end of it.
Hope this helps someone.