By the way I've personally installed the script in a way that stands in time by creating a systemd file:
( Because it improves a log my day-to-day experience)

/etc/systemd/system/backup-4g.service :

[Unit]
Description=LTE backup Service
After=network.target

[Service]
Type=simple
ExecStart=/home/phablet/backup-ip.sh
Restart=on-failure
WorkingDirectory=/home/phablet/

[Install]
WantedBy=multi-user.target

and then

sudo systemctl enable backup-4g

So that it starts automatically at startup.

For this to work you need to have the script that I have posted above in /home/phablet/backup-ip.sh

@lduboeuf said:

Have you filed a bug somewhere ?

https://gitlab.com/ubports/porting/reference-device-ports/android11/volla-phone-22/volla-mimameid/-/work_items/26

I've not understood the quotes about 26.04!

@brenno.almeida

Hello Brenno,

Could you explain where the deamon is installed? Becaused I notice that when I disable the account inside the app and then uninstall the app, I still have some greenline deamon running, and creating some logs:

Jun 07 10:06:30 ubuntu-phablet systemd[2675]: greenline.service: Failed with result 'exit-code'.
Jun 07 10:06:30 ubuntu-phablet systemd[2675]: greenline.service: Main process exited, code=exited, status=203/EXEC
Jun 07 10:06:30 ubuntu-phablet systemd[2675]: Started greenline.service - Greenline Sync Service.
Jun 07 10:06:30 ubuntu-phablet systemd[2675]: greenline.service: Scheduled restart job, restart counter is at 5123.
Jun 07 10:06:20 ubuntu-phablet systemd[2675]: greenline.service: Failed with result 'exit-code'.
Jun 07 10:06:20 ubuntu-phablet systemd[2675]: greenline.service: Main process exited, code=exited, status=203/EXEC
Jun 07 10:06:20 ubuntu-phablet systemd[2675]: Started greenline.service - Greenline Sync Service.
Jun 07 10:06:20 ubuntu-phablet systemd[2675]: greenline.service: Scheduled restart job, restart counter is at 5122.
Jun 07 10:06:10 ubuntu-phablet systemd[2675]: greenline.service: Failed with result 'exit-code'.
Jun 07 10:06:10 ubuntu-phablet systemd[2675]: greenline.service: Main process exited, code=exited, status=203/EXEC
Jun 07 10:06:10 ubuntu-phablet systemd[2675]: Started greenline.service - Greenline Sync Service.
Jun 07 10:06:10 ubuntu-phablet systemd[2675]: greenline.service: Sch
eduled restart job, restart counter is at 5121.
Jun 07 10:05:59 ubuntu-phablet systemd[2675]: greenline.service: Failed with result 'exit-code'.
Jun 07 10:05:59 ubuntu-phablet systemd[2675]: greenline.service: Main process exited, code=exited, status=203/EXEC
Jun 07 10:05:59 ubuntu-phablet systemd[2675]: Started greenline.service - Greenline Sync Service.

Thank you very much!

@projectmoon said:

And it seems like that when keyboard closes, the text entry still stays halfway up the screen. But that bug was preexisting.

Yes because for now I cannot detect when the keyboard is really open or not.

The keyboard closing after every message is new.

Ok I guess it might be a change upstream in Signal-Desktop that provoked it. Thank's for reporting I'll see what I can do about it in next revision.

I've just released revision 8.13.0-1, it includes the following improvements:

• Better integration of ContentHub
• Better integration of left menu
• Bump to Signal-Desktop 8.13

It took a bit of time as changes upstream broke my way to compile the package and I had to investigate it.

Also I've changed the way ContentHub is handled, now it is hardcoded in Signal-Destkop thank's to a patch. I will make things smoother and more reliable for the user, but it will also prepare the ground for switching to Wayland, with Mir2.x

This version should also not crash on Ubuntu Touch 24.04-2.x, although the virtual keyboard will probably not work, like on all XWayland apps with 24.04-2.x (currently).

I plan to release a new version every 1-2 month, as a Signal-Desktop version is only guarantied to work for a period of 3 months.

A feature I want to add is the ability to configure scaling with fine grain.

Tell me if the new version works well for you!

@domubpkm

I need to test again soon,

When I tested a few month ago the OSK (on-screen keyboard) was not working anymore in XWayland apps ( uWolf, Chromium for UT, Signal UT, Whatsnew, Min browser, Rocket.Chat), which is a huge problem for me.

If someone has tested maybe you can say if it is better now.

@domubpkm

To stop the script:

sudo pkill backup-ip.sh

It's true that I've not taken into account the case where LTE is activated, but mobile data is disabled.

@kdb7

You can publish on youtube or other video platform.

For the record I will publish a new version with update Signal-Desktop version, in early june.

@domubpkm

Great!

In any case in a train you cannot expect a perfectly stable connection!

@bunt7

You can find a workaround script, for Network connectivity jump here:

https://forums.ubports.com/post/95548

I've reported the bug here:

https://gitlab.com/ubports/porting/reference-device-ports/android11/volla-phone-22/volla-mimameid/-/work_items/26

@brenno.almeida

Would you consider doing a confined version of the app without a background deamon, and with the go part only running when the app itself is running? I think it would be usefull for those who don't want notifications all the time, and don't want their battery to be drained by the deamon or are not comfortable with having a whatsapp deamon running at all time. And it would be easier to publish on the openstore!

Thank's a lot for your work!

@domubpkm said:

May you please suggest a complete procedure to test

1°) With adb create the script with

nano /home/phablet/backup-ip.sh

and paste the content

2°) Give execution rights:

chmod +x /home/phablet/backup-ip.sh

3°) Start the script with:

sudo su -c "/home/phablet/backup-ip.sh > /home/phablet/log-backupip 2>&1 &"

It will then be running until next reboot.

@domubpkm said:

Did you notice side effects (you said that, i have a Volla 22 too) ?

The only thing that I've noted so far, is that If I enable airplane mode with a wrong timing (bad luck), it might go into a loop of disabling / re-eabling the modem. But then I switch off and on, the airplane mode it goes fine.

@lduboeuf said:

did you reported the issue to the porter ?.

I plan to do so when I have time.

Here is the script that I currently use, it improves greatly the usability of my phone, because it reduces dramatically the need to go in the settings to restart cellular connexion, in order to get access to the Internet.

Though it's not perfect and might have side effects, use at your own risks!

#!/bin/bash

MODEM="/ril_0"
HOST_TO_PING="8.8.8.8 www.google.com ubports.com 1.1.1.1 9.9.9.9 cloudflare.com amazon.com microsoft.com wikipedia.org apple.com"

function get_modem_iface()
{
/usr/share/ofono/scripts/list-contexts |awk -v target="$1" '
/^\[ \/ril_/ { r=$2 }

/Type = internet/ { i=1 }

/Interface=ccmni/ && r==target && i {
    sub(/^.*Interface=/, "")
    sub(/ .*/, "")
    print
    exit
}
'
}

IFACE=$(get_modem_iface $MODEM)

i=0;

while true; do
    if [ "$IFACE" = "" ]; then
        IFACE=$(get_modem_iface $MODEM)
    fi
    ifconfig $IFACE | grep -v inet6 | grep inet > /dev/null 2>&1
    if [ "$?" -ne "0" ]; then
        gdbus call --system --dest org.ofono --object-path "$MODEM" --method org.ofono.NetworkRegistration.GetProperties | grep "'Technology': <'lte'>" > /dev/null 2>&1
        if [ "$?" -eq "0" ]; then
            date
            echo "IFACE: $IFACE";
            echo "IP loss detected"
            /usr/share/ofono/scripts/offline-modem $MODEM
            /usr/share/ofono/scripts/online-modem $MODEM
            sleep 5;
            IFACE=$(get_modem_iface $MODEM)
        fi
    else
        route=$(ip route show default)
        if [ "$route" = "" ]; then 
            gdbus call --system --dest org.ofono --object-path "$MODEM" --method org.ofono.NetworkRegistration.GetProperties | grep "'Technology': <'lte'>" > /dev/null 2>&1
            if [ "$?" -eq "0" ]; then
                date
                echo "IFACE: $IFACE";
                echo "Route loss detected"
                /usr/share/ofono/scripts/offline-modem $MODEM
                /usr/share/ofono/scripts/online-modem $MODEM
                sleep 5;
                IFACE=$(get_modem_iface $MODEM)
            fi
        fi
    fi
    
    i=$((i+1))
    if [ "$i" -gt "15" ]; then
        i=0;
        gdbus call --system --dest org.ofono --object-path "$MODEM" --method org.ofono.NetworkRegistration.GetProperties | grep "'Technology': <'lte'>" > /dev/null 2>&1
        if [ "$?" -eq "0" ]; then
            internetaccess=0;
            for host in $HOST_TO_PING ; do
                ping -W 1 -c 1 $host >/dev/null 2>&1
                if [ "$?" -eq "0" ]; then
                    internetaccess=1;
                    break;
                else
                    echo "Ping to $host failed, trying next one in 4s ...."
                    sleep 4;
                fi
            done
            if [ "$internetaccess" -eq "0" ]; then
                    date
                    echo "IFACE: $IFACE";
                    echo "Internet access loss detected"
                    /usr/share/ofono/scripts/offline-modem $MODEM
                    /usr/share/ofono/scripts/online-modem $MODEM
                    sleep 5;
                    IFACE=$(get_modem_iface $MODEM)
            fi
        fi
    fi
    sleep 20;
done

@domubpkm said:

A good test is to see if the connection is still lost after reboot or complete shutdown and startup.

This is not really the purpose of the script for now. The purpose of the script is that, when you keep the phone up, and you travel, Internet remain accessible at any moment, without needing to manualy go in the settings to restart the connection.

@projectmoon

Can you do

journactl -r | grep 99captive_portal

?

@projectmoon

Ok well I don't know, are you testing with a specific wifi network with captive portal? Does it support RFC 8910 and RFC 8908, or is it legacy? Did you try with other wifi networks?

Ps: You can also retry with mobile data disabled, sometimes it's better.

@projectmoon

What do you mean, do you get the notification when you connect to the wifi network with captive portal?

(You should not open the app from the app grid, it is useless, it will open when you click on the notification, in the notification panel, like in the video)