Android 11 Wireless Debugging pairing and persistent connection - debugging

My question actually consists of two:
adb pair command was added recently in 30 version of Android platform-tools, but official Linux repos (in particular, Ubuntu 18.04 and Debian 10) have only 27 version as latest. Is there any way to be up-to-date without manually downloading the latest archive from the website and placing it in the system?
I'm using wireless debugging for some device monitoring and home automation purposes, so I need to have the connection persistent (at least while the device is connected to my home network). Is there any way to keep the connection without root and doing setprop persist.adb.tcp.port 5555? Or at least do not disable "Wireless Debugging" options after the reboot and keep the port number.

Related

How do you get the Expo CLI server to choose the correct network?

I have VirtualBox and VMWare installed on my Windows 10 machine. Each installs virtual network adapters for use by their VMs.
When I use Expo CLI and fire up expo start it seems to randomly pick one of the virtual adapters instead of my wifi adapter. As a result Expo Client can’t connect since it’s running on a different LAN.
How do you tell the Expo CLI to use the same network adapter as the computer it's running on?
OK, instead of setting Expo to grab the correct network I went the other direction and found out how to tell Windows which network to hand off.
Open Powershell
Enter Get-NetIPInterfaceWindows hands the lowest InterfaceMetric network to Expo.
Change the priority with Set-NetIPInterface
I've already set mine in the screenshot. The command was this.
Set-NetIPInterface -InterfaceIndex 18 -InterfaceMetric 10
Now when you run expo start the Wi-Fi network will be used.

How do I connect remote MAC as build host for Xamarin on Visual Studio?

I have mac-mini configured and running at my home.
And I want to pair my Visual Studio to that mac.
Is it possible to configure it as a build host in case when it's located in a different network ?
i.e. Mac is at home and my Windows/Visual Studio setup is at work.
Your OS-X machine has to reachable by a secure shell connection (SSH) over port 22.
If you can ssh from your Windows' PC to your Mac, say using Putty, then yes, you can make Visual Studio/Xamarin connections to that Mac and use it as a build host.
1) You can bridge two private networks via a VPN
2) Expose your Mac (port 22) to the public Internet (buyer beware)
The key issue, other then security on your Mac, is the speed/bandwidth of your connection between the two machines. Well the amount traffic is not really heavy if you are just using it as a build-host and not using the iOS removing simulator, network latency can be a real performance killer.
If using the (new) iOS Remote Simulator, bandwidth requirements climb and the high network latency can make it a non-solution in some situations.
(It only a Mac-Mini, almost fits in a pocket, take it to work with you ;-)
Your Mac needs to be accessible via SSH (port 22) from the PC running Visual Studio. You will need to setup a VPN or configure your home network to properly forward port 22 to the Mac.

QEMU for Win7 hosting Debian : no more able to connect to the network

I'm fighting strongly against a problem that is making me crazy.
I’m extensively using QEMU over a Win7 64bits machine for running different Linux VMs (Debian, Raspbian).
In the past I configured the network following the QEMU instructions using the OpenVPN TAP device and network bridge in Win7 : it ran perfectly and the Linux machine was able to connect the “real world” networks, internet and so on.
In the last few days, on the contrary, this nice behavior stops working. The Windows situation is unmodified (the OpenVPN TAP driver settings are the same, the bridge is still there, when the bridge is active Windows still see the network, the TAP driver becomes “busy” when the QEMU VM starts as usual, the QEMU startup scripts are still the same…), but the emulated Linux system (whatever image I use) is unable to connect the network.
The “eth0” interface is active but unable to get the IP address from the DHCP and also using fixed IP address doesn’t solve the problem, since the IP address is not seen by the “real” network.
I have tried to uninstall and reinstall again the OpenVPN TAP driver, to downgrade Win QEMU to the previous version, but no way !
The only change that I made in the HOST configuration has been to install GNS3 (with its own TAP driver), but without including the QEMU VM in any GNS3 network.
Does anybody have suggestions regarding what kind of checks I have to do on QEMU in order to solve the problem ?
Any help will be appreciated
Regards
Ugo Poddine
I was finally able to get out.
I was forced to restore a previous system image : all attempts to uninstall and reinstall the OpenVPN TAP driver were useless.
The problem is probably due to the update of the OpenVPN TAP driver : with the v.9.0.0.9 no problem, but updating to the 9.21.1 seems to have generated the problem.
I'm now able to use again QEMU and GNS3 in network.
But what a strange case !

Windows Phone SDK Paradox: "Xde couldn't find an IPv4 address.." and "The emulator couldn't determine the host's IP address..."

A few useful pieces of information: I'm running Windows 8 Professional on a custom-built rig, and I am using a 'WiFi dongle' to connect my computer to the local router. I am using a home network, not a public/work/school network.
I installed the Windows Phone SDK. Piece of strawberry cheesecake so far. Coded my first simple browser app (as detailed on the Windows Phone Dev site) and hit the Run button, expecting my app to come to life and breathe in links and breathe out websites!
But instead, I got this:
Something happened while creating a switch:
Xde couldn't find an IPv4 address for the host machine.
In this case, the emulator wouldn't run at all. And so, I did my research and found out that the solution was this:
Remove all the switches from Hyper-V Manager's "Virtual Switch Manager", and make a new Internal one called Windows Phone Emulator Internal Switch.
I did, and the error did NOT show up again but it did screw up my WiFi and Bluetooth adapters (which I had to do a system restore to solve) and now both WiFi and Bluetooth peripherals are working again.
However, I got this error instead when running the emulator again:
The Windows Phone Emulator wasn't able to connect to the Windows
Phone operating system:
The emulator couldn't determine the host IP address, which is used to
communicate with the guest virtual machine.
Some functionality may be disabled.
In this case, the emulator did run, but I couldn't find my app anywhere. I did some research again and found that the solution to this was:
Delete the Windows Phone Emulator Internal Switch from Hyper-V Manager's Virtual Switch Manager.
Now, I created the switch to solve the problem in the first place. But I did delete it, for the heck of trying everything out. And no surprise there but, it went back to the first error.
I am now stuck in this paradox and have no idea how to escape it.
Thank you in advance!
follow the following steps to solve this problem
1.go to network and sharing center
2.go to change adapter setting
3.go to v Ethernet (internal Ethernet port windows phone emulator internal switch)
4.right click it and enable it(if already enabled then disable and enable it again).
Remove any Cisco VPN's or similar connections. I have found this VPN client works as a replacement to Cisco https://www.shrew.net/
For me shrew soft version 2.1.7 was the only version that worked.

On-device debugging with Sony Ericsson Cedar (J108i)

Unfortunately, I have to deal with J2ME (which I consider ancient technology these days) on Sony Ericsson J108i (aka Cedar).
Unfortunately I've failed to configure on-device debugging. I've done the following:
enabled Java developer mode in service settings
configured USB -> Advanced -> Internet access -> Via computer
installed J2ME SDK 2.5.0.6
disabled the Windows firewall
tried the whole procedure on both Windows XP and Windows 7
Unfortunately, Connection Proxy fails to connect to the device. The network interface is there, named 'Sony Ericsson Device 1039 USB Ethernet Emulation (NDIS 5)', but when I try to connect, the following is logged:
[18.03.12 13:23:45] Getting device ip. Failed to get deviceip for interface(Sony Ericsson Device 1039 USB Ethernet Emulation (NDIS 5) - Sterownik miniport Harmonogramu pakietów). Trying to get it from Connection Proxy settings(sdkme.properties). java.lang.RuntimeException: Unable to connect to the SEMC SDK Service1.
[18.03.12 13:23:45] Getting device ip. No device for interface=Sony Ericsson Device 1039 USB Ethernet Emulation (NDIS 5) - Sterownik miniport Harmonogramu pakietów
It actually looks like the interface is never assigned the correct IP. I've tried assigning IP manually, but it failed too (perhaps I did it incorrectly - the documentation is not really verbose here).
Any idea what I do wrong? Any success stories with on-device debugging using this particular phone?
I managed to get my Cedar device working on Vista 32-bit SP2:
1. First of all, make sure you're not using jdk7uX (otherwise you have to install MSVC 10 redistributable pack to make SEMC_SDK_Service start properly).
2. Edit SDK_Root/OnDeviceDebug/lib/sdkme.properties, set ipprovider.rebindOnConnect: true
(it's false by default), then uncomment and set proxy.device.ip: 192.168.8.2 and proxy.local.ip: 192.168.8.1 (both are commented out and empty by default)
3. Run SDK_Root/OnDeviceDebug/bin/restart_service.cmd
4. (Re)connect your Cedar device
5. Wait about a minute
6. Run SDK_Root/OnDeviceDebug/bin/restart_service.cmd
7. Run arp -a in console and ensure your interface is using 192.168.8.*, this could also take about a minute
8. Restart connection proxy and connect to your phone, everything should be OK
9. You should repeat steps 4-8 after each Windows start

Resources