1. 14 Jan, 2021 1 commit
  2. 03 Dec, 2020 4 commits
  3. 02 Dec, 2020 1 commit
  4. 19 Nov, 2020 1 commit
  5. 13 Oct, 2020 2 commits
  6. 15 Sep, 2020 5 commits
  7. 19 Jul, 2020 1 commit
  8. 06 Jul, 2020 1 commit
    • Sebastian Krzyszkowiak's avatar
      wwan: Fix signal strength display when extended signal retrieval is disabled · 2bea12b0
      Sebastian Krzyszkowiak authored
      MMModemSignal interface is used to retrieve extended signal information that
      requires periodic polling. Therefore, it needs to be manually enabled in order
      to use. There if a fallback to use mm_modem_get_signal_quality when MMModemSignal
      interface is unavailable, but it didn't check whether it's actually enabled,
      leaving the UI with empty label.
      2bea12b0
  9. 26 Mar, 2020 1 commit
  10. 25 Mar, 2020 1 commit
  11. 16 Mar, 2020 2 commits
  12. 21 Feb, 2020 2 commits
    • Mohammed Sadiq's avatar
      Merge branch 'kyle-lower_wwan_dns_priority' into 'librem5-3-24' · ca4627de
      Mohammed Sadiq authored
      Lower WWAN DNS Priority
      
      Closes OS-issues#130
      
      See merge request Librem5/gnome-control-center!6
      ca4627de
    • Kyle Rankin's avatar
      Lower WWAN DNS Priority · cc932710
      Kyle Rankin authored
      Fixes Librem5/OS-issues#130
      
      The current DNS priority settings for WWAN were set far too low. Most
      connections (including WiFi) do not set DNS priority (set to 0) and per
      https://developer.gnome.org/NetworkManager/stable/nm-settings.html :
      
      "A lower value is better (higher priority). Zero selects a globally
      configured default value. If the latter is missing or zero too, it
      defaults to 50 for VPNs and 100 for other connections."
      
      By setting both the "low" and "high" settings to 15 and 20 respectively,
      the WWAN DNS servers were always appearing above WiFi, even though WiFi
      had routing priority. This caused latency and other problems when the
      wwan connection was slow because the system would query those DNS
      servers before WiFi ones. Beyond that, it would even cause WWAN to
      override VPN DNS settings which isn't what we want.
      
      This change puts the "low priority" setting above the default 100 that
      connections get when they don't otherwise set a priority, and the "high
      priority" slightly below 100. I did this instead of setting the values
      to 0 because I noticed that NM doesn't seem to be aware it should
      prioritize WiFi in that case so WWAN DNS servers were still sometimes
      taking precedence.
      cc932710
  13. 27 Jan, 2020 3 commits
  14. 25 Jan, 2020 2 commits
  15. 13 Jan, 2020 2 commits
  16. 31 Dec, 2019 1 commit
  17. 30 Dec, 2019 1 commit
  18. 16 Dec, 2019 9 commits