Olga Weis
Sep 6, 2023
FlexiHub
The ability to perform Android remote testing can be instrumental when developing a new app. You may find that a bug is affecting a device in another country or a distant location and need to access the device remotely. Another instance where you may want to remotely debug Android devices is when you have a team of developers distributed across multiple physical locations.
When you cannot physically access the device, Android remote device testing is the answer. FlexiHub is a great way to implement the connectivity you need to remotely debug Android devices from anywhere with an Internet connection.
If multiple developers and testers will be involved in a project, they may all need to access the devices from different locations. You should strongly consider a FlexiHub Team subscription that lets everyone on the development team perform remote Android debugging. You can enjoy the following benefits with a FlexiHub Team subscription.
✅ A single account for the whole team. You can share connections among all team members. You can also designate a maximum number of connections that a specific developer or tester can simultaneously create.
✅ Streamlined billing with no need to purchase a subscription for each team member. All team members and connections are included for one price.
✅ Easily locate teammates by searching for them by name and invite them to remotely connect to devices connected to your USB or serial ports.
An alternative solution exists for remotely accessing Android devices but it is more limited than FlexiHub. This method, called ADB over network or TCP/IP debugging can only connect over a LAN. It can be used to establish wireless connections to a rooted Android device without a USB cable. A cable will be needed to change the debugging mode on non-rooted devices. This technique simplifies sharing an Android device with a group of developers.
This method requires that the Android device is rooted. If it is not, you will need to root the device before proceeding. The following steps are necessary to debug remote Android with ADB over the network.
If the device is not rooted, you will need:
Now follow these steps:
“C \Users\Public\Documents\Embarcadero\Studio\22.0\CatalogRepository\\platform-tools” “Adb tcpip 5555” replacing 5555 with the port that will be used to listen for incoming connections.If the device is rooted, you need one of these items:
Now, enable TCP/IP debugging mode on the rooted Android device with the following steps.
su
setprop service.adb.tcp.port 5555 changing 5555 the port you will use.
stop adbd
start adbdConnecting to the remote Android device requires you to know the IP address of the device. Use one of these methods to obtain the device’s IP address:
To disconnect from the Android device, run the adb disconnect
You can also opt to reset the debugging mode on the device. Debugging mode is reset when you restart the device. You can reset debugging mode without a restart with the following procedure.
su
setprop service.adb.tcp.port -1
stop adbd
start adbd
