Skip to Content.

geteduroam - RE: geteduroam incompatbility on Android 13

Subject: An open discussion list for topics related to the geteduroam service

List archive

RE: geteduroam incompatbility on Android 13

Chronological Thread 
  • From: Javier López Chazarra <javier.lopez.chazarra AT>
  • To: Paul Dekkers <paul.dekkers AT>, Janos Mohacsi <mohacsi.janos AT>, "geteduroam AT" <geteduroam AT>
  • Cc: < AT>
  • Subject: RE: geteduroam incompatbility on Android 13
  • Date: Fri, 3 Nov 2023 11:49:53 +0000
  • Accept-language: es-ES, en-US
  • Arc-authentication-results: i=1; 1; spf=pass; dmarc=pass action=none; dkim=pass; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed;; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=TksI/9PwoYPw/yt/7cu6OOY1ZOt48VSl3Q9oYoZ6pQc=; b=Pqsd8+a78sVfvp/KEjxEfg2YabiSU3h6GQP7fTY1kj1aPlBNiL5MnaATfuG/JfZyQj4nzmMQ6UeMAJykdIcbFh3BETfgC8NYcDSn6cakFhpOYb7i0dWQryZpbx/0tSuyAmm348yftcIsOKiuYAQw6IqT4ucWWf0VzY38HLLfvzhW+RkrKuv/HXrWR5qgx0/W60PjM1EOIm1VLlgxCIBu26ZrMmetwhCAKdvaHOQJB+AFZbsK4Zf5ghb8uKjcuG8qcgHK1NDQ7BJQR6eYwTu1gwKhLEfPRdo3vGQtt2aK2GZGtD/I3OUx54KiyWfe7NWJttD+HUArMqkqH5pReEylCg==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901;; cv=none; b=DFnRNmuwKwa2smPaV607qtqOs/a4AKG5cdTrCyG9EOsHULsAxTyqM/TSMUf0u5D3HV2m/JWiWwG2w6NjlU2Jb/rM6xSl1sSA+FGxeh3UtddUD/5HCmVI7fp3FAowwDIkQeWnLF4rlV/RtKJ1vTjVLxajwQ5E1OKDAPxKP96FDHEvu5Rf0rPrGqky9N2Ft0iyoDcofNtwqI7zsF3GJZnZdST/9a1z5KPj5fiKeVL9uoqUjcK0+Tr8wyCZVMvT2TCd8ci96FJP8jG9Rjp7DWhKh/nsxLtwBuzOw8OXCcbAvmsN0nVzbZXTnn4HfcaS4VqS6521kCV/eVZMrKqZ1wbBQg==
  • Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none;

Hi to all,

We have problems with Android 13 on HONOR 70 phones with GetEduroam.


Build Number (C430e224r1p1 patch01)

MagicOS 7.1

Android 13

We saw same problems with HONOR 90 too on





Fco. Javier L. Chazarra

Grupo Comunicaciones Unificadas / IT / S. Informática

Universidad Rey Juan Carlos

Despacho 027/030, Ampliación de Rectorado,

Campus de Mostoles  (Madrid), España

Teléfono: 91 488 85 34 / 699 948 784

javier.lopez.chazarra | | @URJC |




De: geteduroam-request AT <geteduroam-request AT> En nombre de Paul Dekkers
Enviado el: viernes, 03 de noviembre de 2023 11:39
Para: Janos Mohacsi <mohacsi.janos AT>; geteduroam AT
Asunto: Re: geteduroam incompatbility on Android 13




I’ve never heard of a “red screen” behavior before. Wow, I’m not so sure how we should diagnose this. Do you know at what point the red screen appears, like at the last step of the configuration?


I’ll ask the dev’s if they have some ideas. What may be interesting, is to try the new App that’s currently in development, and maybe we can identify a different API call works better on these devices.






From: geteduroam-request AT <geteduroam-request AT> on behalf of Janos Mohacsi <geteduroam AT>
Date: Friday, 3 November 2023 at 11:34
To: geteduroam AT <geteduroam AT>
Subject: geteduroam incompatbility on Android 13

Dear All,

    We have several reports from users about incompatibility of geteduroam with Android 13 on certain phones. The geteduroam app generates some red error screen, then it crashes. They tried to use the latest geteduroam available on Google Play Store. We have reports from following phones:

1.) Blackwiev N600; Android 13; Build:   N6000_EEA_TE305_V1.0_01_20230913V04
2.) Ulefone Armor 22; Android 13; Build: Armor_22_TF1_EEA_V11

How to resolve the problem.

    Best Regards,


Janos Mohacsi
Head of International R&D, Infrastructure Division, T&I service owner
GÉANT activity coordinator in Hungary, EOSC representative

Governmental Agency for Information Technology Development
address: 1134 Budapest, Váci út 35.   P.O.Box: 1255 Bp., Pf.: 182.
mobile: +36 30 555 7599   e-mail: mohacsi.janos AT

Archive powered by MHonArc 2.6.24.

Top of Page