I have deployed automation script in remote ubuntu-server and i want to execute those script on my local system where appium server is running.I have googled for the answer but all the solutions work only if both the device are connected to same wifi network
Please suggest me the solution to run the script in my local system where Appium server exist.
Where is the device - is It connected at ubuntu-Server?
Where is appium server running?
Where are the test scripts?
I have tried in this way and it worked.
Test scripts are available in System-1
Appium Server & Devices are available in another system. Where devices are connected through a physical cable.
With this approach, I am able to run the scripts remotely from my machine.
Observations: We can try out through accessing devices through WIFI (adb wifi google it). But if wifi fluctuates then appium session will be terminated. To avoid all these go with the physical usb connection.
I am working on an embedded linux based device that runs ubuntu. Now the device driver for the wifi is really crappy so I cannot create a hotspot so this device connects to another device which is running a hotspot. Now I am connecting to that device for some input but at the same time connecting to internet to send mqtt message using paho mqtt in python via a gsm modem. The modem connect to internet using pon command and it works nicely. But when both connections are running, paho-mqtt cannot connect to internet anymore. pinging using -I ppp0 works fine. I tried to bind ppp0 ip address to paho-mqtt client using the bind_address argument but it does not work. How to resolve this issue?
I'm using Pimoroni Rainbow-Hat Raspberry pi3 kit. I have loaded android things image on sdcard. I have power cable and ethernet cable connected.
I can see Android things boot screen on display but i don't see the IP.
When i try to connect with adb connect Android.local it's not working(getting unknow host). I tried the ethernet cable from pi3 ethernet port to laptop , i can see the lan ip when i do ipconfig /all but when i try adb connect <-ip-:5555, still connection gets refused. but am able ping to the ip.
I am using Windows 7 OS.
Tried turning off IP v6, Windows Firewall, rebooting host etc, still not able to connect.
My main problem is getting the Aot device recognised on the host and load the app onto it.
I'm aware but haven't tried usb to ttl serial cable option mentioned here
I'm familiar with Android but new to iot/Aot , any help about where i am going wrong would be appreciated.
When i try to connect with adb connect Android.local it's not working(getting unknow host).
I tried the ethernet cable from pi3 ethernet port to laptop
The Raspberry Pi is a computer in its own right.
You need to connect the ethernet cable from the Pi3 to your router aka to the local network (not into your computer directly)
The follow the steps from the docs here and setup wifi to avoid further cable issues.
After upgrading to OSX Yosemite, I can no longer test my app on a mobile device by using my development machine's (MacBook Pro) IP address. For example, I used to be able to view a Rails app on a phone by going to http://192.168.0.4:3000, but now I get the following error:
ERR_CONNECTION_REFUSED
I get the same error when testing an AngularJS app using the grunt server running at http://192.168.0.4:9000
Any help will be greatly appreciated.
It could help to bind the server to your local IP, like
rails s -p9000 -b192.168.0.4
to start your rails app
Consider giving a try to Pow. Its pretty simple to install, and a great solution to share a local development across multiple devices.
Like it explains in their homepage, you can install it with just :
curl get.pow.cx | sh. To prevent any errors, install in Terminal app outside a Tmux session.
And just symlink your app :
cd ~/.pow
ln -s /path/to/myapp
You can access your app at http://myapp.dev/, and at http://myapp.[your ip address].xip.io from another device.
Not a direct response to your issue, but an alternative to setting yourself a configuration in your preferences.
Turn IPv6 off. It Prevented me from connecting to my localhost from other computers on my LAN. And, with the newer versions of OSX there is no way to turn it off in the Network Preferences Panel so you have to do it from terminal.
Open Terminal and enter to turn it off:
networksetup -setv6off Wi-Fi
And this to turn it back on:
networksetup -setv6LinkLocal Wi-Fi
If you are connected via Ethernet or something else just run this command to list the available options:
networksetup -listallnetworkservices
and replace "Wi-Fi" with the appropriate device.
I don't have a mac, but that seems to be the server not accepting connections, if that is the case, it's only accepting localhost connections, try binding de server to accept all connections or bind it to 0.0.0.0 ip
Can you access that IP from Browser? are you sure your IP is in the same range with 192.168.0.4? It is your mobile device connected on the same network? Maybe you used internet sharing before update to Yosemite and now is off?
I think your IP address changed. Telnet from console(terminal) your I.P. port. If 192.168.0.4 is your real Ip then maybe add(as root or via sudo) an entry in /etc/host file an entry as 127.0.0.1 192.168.0.4. Restart network or reboot. Also you can try nmap ( on ip to see open ports). Nmap has been ported to OSX just google for installer.
I am using Android ICS 4.0.4 source code for enabling the Wi-Fi Direct and run on i.MX6 board with Wi-Fi module which supports marvell 8787 chipset.
I was able to make the wfd0 interface up for wifi direct but the other p2p operations such as device discovery was failing.
I was using WEXT as driver interface .After googling I came to know for the p2p operations nl80211 must be used.
I changed the configurations from WEXT to nl80211. But the wpa_supplicant stopped working.Even though I am starting the wpa_supplicant service from init.rc file the wpa_supplicant does not seems to be running.
Does Android ICS 4.0.4 provide a complete support for Wi-Fi Direct?
Could anyone help me with this issue. ?
The support for Wi-Fi Direct on Android has began for the 4.1 version (source).
Moreover, as you said, the WEXT drivers does not support P2P. So you have to use nl80211 drivers. But are you sure that your device have a valid nl80211 driver?
If you want to known why your wpa_supplicant is crashing, you can start it by hand in a shell without the -B option and with the -dd option and check the log.