Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Skip to content

Problems to connect to several domains after upgrading to /e/OS V1.0

  • /e/ version: /e/OS 1.0-20220526188859
  • Build-Number: e_herolte-userdebug 10 QQ3A.200805.001 eng.root.20220526.110739 dev-keys,stable-release
  • Device model(s): Samsung Galaxy S7 (SM-G930F)
  • Device rooted: no? (I bought the phone two years ago with /e/OS pre-installed. The phone has been updated and upgraded "over the air" only.)
  • Mobile network provider: Congstar (Deutsche Telekom)
  • Server of email provider: secureimap.t-online.de, securesmtp.t-online.de

Summary

When being connected to a mobile network it is impossible to send or receive emails and some (not all) web-sites cannot be reached.

When trying to send an email the following message is thrown: GaiException: android_getaddrinfo failed: EAI_NODATA (No address associated with hostname)

When trying to connect to some web-sites using the Browser the following message occurs: DNS_PROBE_FINISHED_NXDOMAIN

Examples for web-sites that cannot be reached being connected to a mobile Network:

Examples for web-sites that can be reached even when being connected to a mobile Network:

In addition even the /e/OS App Lounge doesn't seem to be able to establish a connection to the app repository and fails to start when being connected to the mobile network. Being connected to WLAN/WiFi it works fine.

Problems occur regardless of "Advanced Privacy" being enabled or disabled.

I have already tried to use different DNS-Server (instead of the one of the mobile network provider). Unfortunately, this did not change the behaviour of the phone.

Before upgrading my phone I used /e/OS 0.19-20211023142428 without any (obvious) problems.

The problem

Steps to reproduce

What is the current behavior?

What is the expected correct behavior?

Technical informations

Relevant logs (adb logcat)

Relevant screenshots

Solutions

Workaround

While being connected to my private WLAN/WiFi everything works fine.

Possible fixes

As described in issue #5668 (closed) the reason for most of the problems described in this issue are due to out-of-date APN settings. My fault, sorry for that! After having changed the APN settings all web-sites can be reached and emails can be sent and received even when being connected to the mobile network.

Nevertheless, App Lounge still crashes most of the time when being connected to the mobile network. However, it does not crash every time. There seems to exist a correlation between the likeliness of crashes and the strength of the signal of the mobile network. Perhaps a kind of timeout error?

Now, that the remaining problem is described in issue #5668 (closed) as well and that i can deal with this problem, i suggest to close this issue. Any objection?

Checklist

  • License
  • Translations
  • Documentation
  • Test plan
Edited by Carsten