May 2024, Solution to connectivity issue on old builds

[piero]

may 2024, the network and wifi icons display a small cross

.

or

.
Official advice is to update to a newer build, but it is not always possible, so,
thanks to @tcecyk @poiuzzz @4nthony for the solution/workacross :

Résumé

@tcecyk

thanks for following up. I don’t know the amount of devices actively in use that are ‘stuck’ and do not have an upgrade path.

For anyone unable to upgrade, there is captiveportalcontroller , but it needs adb assistance, at which point a user could use adb itself to set the murena urls.

Edit: that said, upgrades of major versions have migration risks. /e/ up until today has no easy user backup & restore to give peace of mind for major upgrades. There’s little to no downside for ops to answer on that url. By the amount of users feedback it seems to be too early to sunset the url.

@poiuzzz

Great, works fine!
Here a short tut. I’d use adblink on my laptop (Ĺinux.Mint).

• install captiveportalcontroller
• allow ADB über Netzwerk in den Entwickleroptionen
• connect device with adblink (ip:5555)
• in ADB shell type: pm grant io.github.muntashirakon.captiveportalcontroller android.permission.WRITE_SECURE_SETTINGS
• choose custom servers in captiveportalcontroller
• restart wifi
• be happy

@4nthony

For me the easiest solution was to tap on each field and then select the default option that the app suggests. This got things working, but i do not know how good - or private - these settings are.
In one of the other threads on this topic @tcecyk suggested 3 murena servers. I got those working by trial and error, but do not really know if what i did was in any way sensible either.
I think we, the users with problems, need to be better at not starting new threads, rather first checking thoroughly to see if anyone else has already asked a similar problem. Then people do not need to repeat the answers again and again and there will be a complete, definitive thread with all the info in one place.
Here are the settings i guessed at with the murena servers:

HTTPS: https://connectivity.murena.io
HTTP: http://connectivity.murena.io
Fallback 1: http://204.murena.io
Fallback 2: https://murena.io/generate_204
User agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.32 Safari/537.36

If anyone can tell me if these are right or wrong i am sure the info might be useful to others too.

.

On your phone :

1. go to android settings, in the developper options section, and enable “USB debbuging”

2. install an open source application “captive portal controller” from AppLounge or F-droid

3. open the “captive portal controller” app
   and enable controler :

.

On your PC (where ADB is installed), plug your phone with an USB-cable :

4. open a terminal and type :

adb shell

then

pm grant io.github.muntashirakon.captiveportalcontroller android.permission.WRITE_SECURE_SETTINGS

On your phone :

5. fill-in the captive portal url
   HTTPS: https://connectivity.murena.io
   HTTP: http://connectivity.murena.io
   Fallback 1: http://204.murena.io
   Fallback 2: https://murena.io/generate_204

6. save

7. disable controler and close the app.