There are obvious issues with Wifi on the Evo mounts, however I also believe that there are issues in SkyPortal and SkySafari applications on IOS and Android .
I have tested SkyPortal and SkySafari 5 Plus and 6 Pro on my Android and iPad Air 2 tablets respectively (also on a Samsung Galaxy 8+) using:
1.) The Evo internal wifi in Direct Connect mode
2.) The Evo internal wifi in Infrastructure (AP) mode with a nano router next to the mount.
3.) The Evo mount with a SkyPortal Wifi Module in both Direct Connect and Infrastructure modes
4.) Celestron SLT mount with a SkyPortal Wifi Module in both Direct Connect and Infrastructure modes
In all instances, with or without the Hand Controller plugged in to the mount, the tablet (and android cellphone) apps eventually experience issues that span from overrun slewing to major lags to loss of connection. I am always within 3 feet to the mount(s). If I lose connection when in Infrastructure mode, the Wifi lights on the Evo and Wifi module show a connection to the nano router always (blinks slowly, steady on when connected to App) but the tablets lose connection to the mount but not the nano router!.
I wanted to take SkyPortal/Safari out of the equation. I installed SkyQ-Link PC software on a Windows 10 laptop with NexRemote and Stellarium and used in Direct Connect or Infrastructure modes. NexRemote controls the alignment but Stellarium does the navigating for me.
I have not experienced any lags or drops using this setup for at least 4 observing sessions.
I also image with a ZWO camera, so I can use the laptop for everything, however it is not as user-friendly as using SkySafari (I need a wireless keyboard to use NexRemote remotely; lots of Window switching between NexRemote, Stellarium and camera app). A Windows tablet might be the answer.
The only issue I experienced was that my two USB 3.0 ports quit in the middle of a session but the USB 2.0 ports were ok. Could be an issue with NexRemote's use of virtual COM ports.
I have obviously used the SkyPortal/Safari apps a lot more, but I'll continue to test the PC solution to see if I experience the same issues.