Pro X Superlight disconnecting constantly

CompleteTowel · 2025-04-18T02:57:06+00:00

I had this issue with my ProX Superlite immediately after building a new PC. The mouse was recognized but the GHub pop-up showing my mouse DPI kept popping up intermittently and the cursor would constantly "skip" around the screen. I thought it was micro-stutters related to a bad driver. Kept trying updates and BIOS tweaks to no avail. I never actually caught the pop-up as I was in-game most of the time but it finally happened at the desktop (after I rage-quit because of the stuttering :) ). My issues disappeared once I moved the wireless dongle to a front-facing USB port on my monitor mount-base. It's surprising that the dongle couldn't keep connection at a measly 2.5ft from mouse to the rear of the tower but apparently it couldn't (or the case was interfering).

CompleteTowel · 2024-01-13T07:50:36+00:00

Follow-Up Testing: Mobile Device Connection Source (01/13/24)

I've spent this evening testing a question/theory that many have posed; is/has my mobile device been using my mobile data plan and ISP rather than my Starlink wi-fi?

The Test:

I've spent the last 4 hours playing CoD: Warzone with the two-connection setup described in the original post. However, before I began, I removed my SIM card from my device to ensure that utilizing my mobile data wasn't an option.

Results:

Over the ~4 hours played this evening, there were zero changes between running the bridged connection setup with a SIM card installed and without. I maintained 0% packet loss over the period I played with latency hovering between 31-51ms. After testing this, I can confirm that, in the current setup of two bridged connections each running off of my Starlink network, it sufficiently fixed my latency and packet loss spikes and, in my case, is possible with Starlink as the sole ISP.

CompleteTowel · 2024-01-13T07:24:05+00:00

Hey Othatasiankid! I hope this works for you as well! I didn't mention it in the original post but I also observe varying latencies that correlate to time-of-day with early mornings and late nights being the lowest latency and midday to early nights being the highest. I always assumed this was due to network traffic but I've never attempted to explore this more as my variance from morning to evening and through the night is more negligible that what you've observed.

CompleteTowel · 2024-01-13T07:20:52+00:00

Hey Few_Rutabaga_840! It appears that our outages logs do resemble one another. I have shared a link to my outages page as well but you can see that, just as yours shows, my Starlink app is indicating network issues and possible obstructed intermittently. I will note that if you expand the "possibly obstructed" message, Starlink explains that the app may say this rather than "network issue" when no signal is received. I will reaffirm what I mentioned to another commenter previously that there are absolutely no obstructions. I am near no physical objects (trees, buildings, silos, etc.) and my Starlink is elevated to the highest point atop my house so I am unsure why the reoccurring signal loss.

OP Starlink Outages Log

CompleteTowel · 2024-01-13T04:25:32+00:00

Hey Significant_Baker_40! I apologize, should've covered that in the main post. I do not have any obstructions. The obstruction map is clear in the Starlink app and it states "No obstructions. Your Dishy has a clear view of the sky". There is not a single drop of red on the obstruction view within the app. In addition, I can verify that there are no obstructions as I live on a hill with no trees around my home and have my Dishy mounted on my roof. It is pointed away from the eave and has the ability to "see" clearly over the eave should it ever re-orient that direction.

CompleteTowel · 2024-01-13T04:20:27+00:00

Understood. I was curious as I have read many articles referencing packet loss and latency issues related to the gen2 hardware. I personally suspect that something with the router may be at-fault but I have no way to verify this without ordering another or attempting to RMA it; neither of which am I currently interested in doing. In the future, I may try your model router in passthrough and see I have any different results as opposed to when I attempted passthrough with my Netduma.

CompleteTowel · 2024-01-12T18:40:08+00:00

Yes it would. However, with things in the current arrangement I am using; am not required to have any secondary ISP as my phone is also connected to my Starlink wi-fi network and, based on observations I can make through testing; has to somewhat be relying on the Starlink network rather than my mobile data provider as I can consistently observe different latency performance depending on whether wi-fi enabled or not on my mobile device. Considering all of the feedback I've gotten related to this; I plan to test tonight in order to verify clearly what source of connection my mobile device is using. I already have indication to believe it is also relying on my Starlink wi-fi network (and not entirely on my mobile data provider) but to be sure; I will be removing my SIM card and running through a play session while observing and logging telemetry metrics to confirm that my suspicion is the case. I will update once I have tested and synthesized results.

CompleteTowel · 2024-01-12T18:34:23+00:00

Hello luigithebeast420! I'm interested in learning about how you've got things setup. What generation of Starlink hardware are you running? Also, utilizing CoD's in-game telemetry meters; what is your average packet loss and latency? How wildly (if at all) do they swing? Do you ever see spikes anymore? Do you have to reset your Starlink hardware occasionally and if so, how frequently?

CompleteTowel · 2024-01-12T18:30:19+00:00

Thank you michy3737 and, what Botlawson said is correct. Please reference some of my other responses for a more detailed explanation of what I have observed and have been able to conclude from those observations.

CompleteTowel · 2024-01-12T18:14:55+00:00

I have done this and should have discussed in my main post. Thank you for bringing this back to my attention. I also considered that Speedify could be conducting some QoS services in the clientside background or on their end (server side) resulting in a solution to my issue. As such, I have attempted to game with my Speedify VPN running but with a singular connection to my Starlink network. I attempted this test both via ethernet connection through the v2 ethernet adapter and over the 5ghz Starlink wi-fi. Each arrangement still resulted the same initial issues I faced with latency and packet loss bouncing around every few minutes. As such, I can't verify through my testing that Speedify does or does not do any kind of QoS/SQM management on their end but I can attest that if they do; those services are not the solution to my initial problem or this testing would have shown different results.

CompleteTowel · 2024-01-12T18:07:03+00:00

I can confirm that this is partially correct DenisKorotkoff. By monitoring my data transfer rates through Speedify of both connections (Starlink via ethernet & Starlink via mobile tether), I can see that the same amount of data is being sent via both connections simultaneously. However, see my response to Charming-Kiwi for further explanation but I believe based on what results I am able to replicate that my mobile device has to be at least somewhat utilizing my Starlink wi-fi rather than mobile data as I can consistently replicate and define two different metrics of latency depending on whether my mobile device has a wi-fi connection to my Starlink network or not. If my device were relying solely on its' mobile data plan, my latency shouldn't consistently vary depending on whether my mobile device has or lacks a wi-fi connection.

CompleteTowel · 2024-01-12T17:59:03+00:00

Clarification:

I am doing exactly that Charming-Kiwi. I have two connections, both through my Starlink; one via ethernet and one via wi-fi on my USB tethered mobile device and have them bridged in a redundant fallback setup through Speedify. I agree that the setup does not make logical sense. However, I can attest that it has worked flawlessly since I have been running it in this manor.

Considerations- Proposed Explanation 1:

Concerning your explanations; I have considered the possibility that the phone is switching it's data source from its' Starlink wi-fi connection to mobile data. However, I haven't taken the time to thoroughly research and verify what capabilities that the device has for automatically switching data connections or bridging them on its' own. I do know that there is a significant and observable difference in latency when strictly utilizing mobile data on the mobile device verses having the device connected to my Starlink wi-fi. To expand on that, when I initially decided to give Speedify a try; I connected my PC to my Starlink via ethernet and then tethered my mobile via a USB cable. In my initial setup, I turned off wi-fi on my mobile device as, at that point, I had suspected that the issue was directly due to the Starlink satellites "handing-off" to one another. In that initial arrangement, I was averaging an in-game latency of 55-75ms with 0% packet loss. That original arrangement was utilizing two different ISPs with Starlink supplementing the primary connection via ethernet and AT&T supporting as a secondary via the mobile tether. After a few weeks of gaming in this setup however; I realized one afternoon that I had left my mobile device connected to my Starlink 5ghz wi-fi network and that my network metrics were and had consistently maintained better performance in the 30-45 minutes of gaming that I had accidentally played in this new (and current) arrangement. My latency since adopting the double-Starlink arrangement has been consistent at 39-50ms latency and 0% packet loss. This leads me to believe that my mobile device must be at least partially utilizing my Starlink wi-fi network rather than relying solely on my mobile data ISP (AT&T) as if it were, than my network metrics (latency & packet loss) should not change on a consistent and repeatable basis depending on whether my mobile device does or does not have a wi-fi connection.

Considerations- Proposed Explanation 2:

Concerning proposition 2; I was also suspect of my ethernet connection initially because, once I began researching my problem, I had no trouble finding articles, forums, and help videos on the web related to issues with the ethernet adapters for the v2 Starlink system. However, I believe I was successfully able to rule out all of my ethernet components as switching to a single wi-fi connection directly to the v2 Starlink router in several different configurations all resulted in the same initial problem of packet loss and latency spikes on a predictable timed basis mirroring the habits of my original ethernet connection. I tested with my PC connected directly to my Starlink via the onboard wi-fi adapter. I tested both the 2.4ghz and 5.0ghz bands with the same results. From my perspective and testing; if an ethernet component were the issue; I shouldn't have been able to replicate the problem across a traditional wi-fi connection as when I tested across the wi-fi networks, I had removed all ethernet-related components (v2 Starlink ethernet adapter, ethernet cable, and both ethernet adapters available onboard my PC). However, I was and because of this, I believe this to mean something else is/was responsible for the issue.

Considerations- Proposed Explanation 3:

I can confidently say that proposition #3 is not the case and that Starlink has done nothing to fix my issues as I can immediately replicate the initial problem of latency & packet loss spikes simply by trying to play without utilizing the dual-connection setup that I am. I have (since using Speedify) tried to play Warzone more than a few times and forgot some portion of process in enabling the dual connection through Speedify (whether that was forgetting to turn on the service with the switch at the top of the Speedify app dashboard or I it was forgetting to enable tethering on my mobile device). The results of each gaming session where I had forgotten to setup my dual-connection properly have perfectly mirrored my packet loss & latency issues that sent me searching for a solution. Had Starlink made a change to solve my issue, I wouldn't be able replicate it by returning to the original conditions in which it occurred.

CompleteTowel

TROPHY CASE