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 
    < Chronological >      < Thread >
  • From: Paul Dekkers <paul.dekkers AT surf.nl>
  • To: Janos Mohacsi <mohacsi.janos AT kifu.gov.hu>, "geteduroam AT lists.geant.org" <geteduroam AT lists.geant.org>
  • Subject: Re: geteduroam incompatbility on Android 13
  • Date: Tue, 21 Nov 2023 09:54:03 +0100
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=surf.nl; dmarc=pass action=none header.from=surf.nl; dkim=pass header.d=surf.nl; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; 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=uzQQsMMy0NbwBkZMTmu6ujzktDCW8PsSzvx8m3di5tg=; b=lHHaaOwAF7dfNHVfukLw7DcnwyR6Ct1Vz4GVNXwvySpDrtnUbxegoAMYrVYx2qIkM0HrHTv+E9IvBI/dySzhk4jWt9791MlTiC6TwyQePoJtu/WwFld7Lq4JaKstj4kjI2zt/dlVK/Rcqk3dYzvrfzIWPb4vT/+vNjGav3vLgWgA5u69+5r7cxFnM7LXjTuCIklfdYFlzBauR80B5liskjSq1SmljoJ3spy2gc6k6nASfxN4T92Xry52tqOLXX64YCk3y/1yGhJFP5Jr/5ZyT3088bdU/Lz4MZk9UhhHQJKvPxQWjfDbiaTppdQFYpuenCLCz/2VIjzmB9Ts/sfSog==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=SpMEMCOkJHscQgKCydqXtlAqpxxSMEOgbcipZ27JptcNHBNLyXAv8rFqtSFrtt9rF87dBm4iSNegxMdIAjSECCS+h7PGKIDBRdkmsbmA5atRQ1aM0Uea7ZtVXRFHX3FX10eo1bBW8H+lCoPMVWFUHYcctxnwhv+9Jut8Gksof2zsnME6kI29Nj60Gfhq2hGvFvTQIH5409OMXhfXeReYGi4UxqogC3X8uFih24DV89/1C5JTr6v2kcrx0O8D7jERmMABhkTX9NHsn1iB1EZsGo0Ja4lRVBA7qXLO2yyFvG559LjLC8hk4symtXWb195U9J3L+pTHaiAZ1QzF5Ya6IA==
  • Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=surf.nl;

Hi,

We're one step closer to solving this: it appears as some of these phones don't support all EAP-types, or at least not for passpoint.

If you have the ability to test on these Blackwiev and Ulefone, Janos, I have a test version to collect a crash report. Otherwise, it's worth trying a TTLS or TLS account (like the ones from geteduroam's psuedo service).

Regards,
Paul


On 03/11/2023 14:33, Janos Mohacsi wrote:
704fb433-2e67-431c-bbdd-07dc35b09865 AT kifu.gov.hu">

Hi,

    I try get some screenshots.

    Best Regards,

            Janos

On 03/11/2023 11:39, Paul Dekkers wrote:
PAXPR04MB8374E32FE2D58B8D13D50F9487A5A AT PAXPR04MB8374.eurprd04.prod.outlook.com">

Hi,

 

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.

 

Regards,

Paul

 

 

From: geteduroam-request AT lists.geant.org <geteduroam-request AT lists.geant.org> on behalf of Janos Mohacsi <geteduroam AT lists.geant.org>
Date: Friday, 3 November 2023 at 11:34
To: geteduroam AT lists.geant.org <geteduroam AT lists.geant.org>
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 kifu.gov.hu


--

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 kifu.gov.hu



Archive powered by MHonArc 2.6.24.

Top of Page