u/Attila-The-Pun

Part of the fun of living in the mountains/foothills is understanding that radio waves have a heck of a time with our geography. Getting "great" signal with anything is an exercise in futility.

That said - I am struggling with AT&T and find myself basically unable to really use the service I am paying too much for. 99% of the time I'm dependent on Wi-Fi calling, and even if I do get a bar or two, the service is unusable. (Even in Denver, sometimes!)

Looking at Coverage maps for the various providers, we should all be getting five bars of 5G, even if we live out NW of Bailey....so they're pretty useless as a guide.

What are residents' actual lived experiences with different providers? Or is it all the same, and any differences between AT&T/T-Mobile/Verizon/Google Fi pretty much just placebo?

I am running Ubuntu Linux 26.04 (with KDE) and Elite Dangerous installed via Steam. (So, Proton Experimental)

I have two VKB sticks for a HOSAS setup - a VKB omnithrottle and a VKB NXT Evo + SEM module. It's the latter that is giving me fits.

The X-Axis on the VKB NXT Evo + SEM seems to be permanently stuck 3/4 of the way to the right.

- I have successfully gotten both sticks to properly be detected within Linux as joysticks. (Using protontricks to disable the gamepad detection)

- I do not have the mouse mapped to the "flight rotation" axis I am trying to configure the stick to. (And I have tried multiple bindings to other controls)

- They are both updated using the latest firmware from VKB's website (as of about a week ago?)

- Both sticks were re-calibrated on a Windows machine (since there is no Linux VKBDevCfg on Windows - that calibration was saved to both sticks, and has been verified to be good even a couple days after the fact.

- Running jstest-gtk right after plugging the device in shows a good calibration - until you move the X axis. Then, it is slammed to the right and can only be corrected by a large motion to the left.

- You *can* recalibrate using jstest-gtk or jscal, however this does not change the behavior.

- Running jscal-store /dev/input/js0 after a calibration does not seem to make any changes.

- I can take the same joystick that is showing this behavior, connect it to a Windows machine, run VKBDevCfg, and the calibration is fine. I cannot get the issue to re-occur.

I am running out of ideas here, and I *really* do not want to dual boot my desktop just yet. (Not opposed to the idea, but I would rather figure this out) I have to assume that proton is not updating its calibration, which appears to be bugged in the first place. I'm 99% certain this is not something specific to the sticks, but rather how Linux is reading them.

Any help in pinpointing something I might have overlooked?