Subject: An open discussion list for topics related to the geteduroam service
List archive
- 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: Fri, 3 Nov 2023 10:39:26 +0000
- Accept-language: en-US
- 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=Zpl1txufv8bozOAnZ0jYeL1OAHZ63Mz6btdHdn07kHE=; b=A7iCCBjspBkcBzX5OL16/i6IJp3rz7tx0ZuUhMPpO1FMad+5m8kFgQ/xVZ8AUt4jP4xLVGx+tBofPppUYEwV3iWZLxFNDlKm+ypByr5TUmAAmZH+dkdWqDWSC5OfIZA2TZ8cAHN7lk3+6I93BIVGce8YIkkd0rd1iFpOPohx9De+iDjoPet5JEwJa+SsA2gupb1argThpQAzR3bxCs4B7jGnWQb/yT7RIqO1th4nf6BXff+g+JnecyVnVfnT0IATg+826z1nX8wviEHuqXNFYJ7FL94MdFE4r33TNTN1xa+Ni/TUiuslwhWf1Fn3aPah7G2P9TnVrJZ4BDHIDdZ8MA==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=DFEgN43rnY65lHtVPPRMVJ/qdhD20gtMy9SyepsG7DF6yl4VaGvkmDIxJ49vYnm8TrIDVoXTj1BXW4ne8JxWyq2spqAXGQ5IPtQbwB7tedomU2Q2m0v4EB1XW9aAAr7jAqCdRND2LRY+0aSFNmuWJ4Wy1knv1yboCDurJSe8zffZHkBTk5FnCn6BSwxZh0t7xdKzq736zJKt+h603f2qZeoVI950bs5ezm4S8G1ZL8BfvtGAdMXDtPhz6FE1BGXNyXkqcPnuT3MnbeR89c06wSDC9FDOFkuRXTGXHKFaosvApdCTxoF4fGatQbym+NAH8dP2el1UuAnwnNSiX3y7Jg==
- Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=surf.nl;
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> 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 How to resolve the problem. Best Regards, -- Janos Mohacsi
Governmental Agency for Information Technology Development |
- geteduroam incompatbility on Android 13, Janos Mohacsi, 11/03/2023
- Re: geteduroam incompatbility on Android 13, Paul Dekkers, 11/03/2023
- RE: geteduroam incompatbility on Android 13, Javier López Chazarra, 11/03/2023
- Re: geteduroam incompatbility on Android 13, Paul Dekkers, 11/03/2023
- Re: geteduroam incompatbility on Android 13, Janos Mohacsi, 11/03/2023
- Re: geteduroam incompatbility on Android 13, Paul Dekkers, 11/21/2023
- RE: geteduroam incompatbility on Android 13, Javier López Chazarra, 11/03/2023
- Re: geteduroam incompatbility on Android 13, Paul Dekkers, 11/03/2023
Archive powered by MHonArc 2.6.24.