Hi,

I just wrote a PDF reader based on Chromium PDF engine.

It's pretty dummy, written in 30 minutes. But quite useful (at least for me) given the limitations of Document viewer, and that sturmreader is currently broken on noble.

I think it will greatly benefit from Qt6 upgrade, when it comes, because of improvement of the engine in chromium.

It is published in the openstore:

https://github.com/pparent76/chromiumpdf

Regards,
Pierre.

I've succeeded in opening the keyboard when editing text in signal-desktop !!!!

I could do it reusing the work of @ChromiumOS-Guy in uWolf!

I can officially send signal messages from a native Ubuntu Touch app, without Waydroid!

Even though for now it's not convenient , since keyboard hides the text area, and the enter button of the keyboard somehow does not trigger sending the message, and the "send" button in signal is hidden until you expend the editing area. But still very usable.

For now everything is messy, but I will try to make it available soon (I think it should be possible to do a click package, but I'm not sure yet)

Ps: Note that I could do it with Mobian version only for now.

Hi,

Just wanted to share that VLC 4 (not yet released) has an interface very close to VLC for Android.

I will be a very good candidate to port to Ubuntu Touch. The interface would probably be usable as such, but with few minimal patches to the interface it could probably be near perfect on the phone screen.

I don't have time to do that now, but probably later (possibly when release officially)

Hi,

Today I just figured why not try:

sudo snap install signal-desktop

And I realize it just works! This is crazy. With this simple command I can link my device and see my chats. Well it is certainly not a responsive interface (but not terrible either, there's just the left menu coming in the way) and the keyboard does not show for now. But I can consult messages, and this is major.

It means:

1°) We can certainly create quite easily a version of Signal-Desktop that is adapted to mobile display (with few patches to the interface to make it responsive), and that we can get a full-fledge signal client on Ubtunu touch, that way.

2°) That Mir2.0 will certainly help with that.

Ps: I guess the first easy thing to make it usable as a consul-only stuff is adapt the scale, which I guess must be easily doable.

Anyway after all the investigations that I've made I'm extremely confident that we'll be able to have a fully responsive client based on Signal-Desktop landed in the openstore within few month. I see exactly how to make it perfectly adapted to the phone Interface like whatsweb. (Funny enough it is possible to use a modified version of the js script of whatsweb to make the interface responsive, because the interface has an extremely similar structure. )

It's not anymore a question of "if" but a question of "when". But there are few tedious tasks in the way, and I need to go little by little, because I can't dedicate all my time to this.

Of course I'm open to any offer for help and testing!

I've been able to recompile Signal-Desktop from source and apply my responsive script.

It is available in the Openstore alongside these other improvements:
-Fix startup from OpenStore
-Fix open url externaly
-Fix battery problem
-Fix double window problem

There still are some keyboard issues, it's probably the next thing I will work on.

First of, thank you so much for the development on Ubuntu Touch, it is becoming amazing!

I have a question about Wayland/Xmir apps (e.g uWolf, Signal-desktop, Snap apps) in the context of the upcoming Mir2.0

Will you consider implementing any of the following, to polish experience with Wayland apps:

• Standard desktop notifications showing as UT notifications (with sound, vibration, status led, notification panel).
• Easy Import/export files from content-hub by having a custom xdg-desktop-portal for content-hub.
• Open url externally, by making an URLdispatcher app as default desktop browser.
• Review and possibly adapt apparmor profiles to make sure they don't prevent confined Wayland/Xmir apps from accessing the hardware the way they normally do it (GPU ,microphone, camera, ,...), when they should be allowed to access it. (Eg: Signal-Destkop can access microphone when unconfined, but not when it has the confined + microphone profile.)

Would you need/accept some help to do that?

Hi,

Just wanted to mention that I contacted the in-development French identity mobile app, to ask them for interoperability, and remind them their duty to make sure public service is available for everybody, and that their role was not to enforce the choice of mobile OS of their citizens.

https://france-identite.gouv.fr/

Surprisingly I got a pretty open and positive reply, apologizing that their app was not compatible with my OS (Ubuntu Touch), and saying they shared the goal of interoperability, and would study that with the development team what was possible. I did not expect such a positive answer, although I don't know if anything concrete will get out of this.

As a side note I wonder why for this kind of app, with a real need of interoperability, they don't use more Qt, because from what I understand Qt allows to develop apps for Android, iOS, Windows, Mac, Linux desktop, Linux mobile (Ubuntu Touch, Sailfishos, Mobian, postMarketOs, pureOs, ect...), all at once, with only few custom things to go for each platform. Any thoughts on that?

Craziest thing:

The calls are partially working out of the box!!!!
Which means we can certainly get calls working one day!

Ok I've found a way to solve keyboard bugs (in X, in a very hacky way) . I will make a new release soon, Alongside optimizations to make the app less sluggish.

With those, it will reach the stage of good client for text-only notification-less chat!

(Other features will come later)

Unfortunately last update did not improve the situation.

Actually I have had the bug once again, and this time the interface holding the IP "ccmni0" was down, but forcing it up did not restore the connexion, I could ping the gateway but nothing more.

By the way I've just noticed something else strange in the logs:
sometimes I have 2 interfaces called "ccmni1" and "ccmni2". But sometimes I have "ccmni0" and "ccmni2" . I'm not sure if it is related to this bug or not, as both possibilities seem to be able to work if the interface has proper IP.

Improvements on the bug I reported above after 24.04-1.1:

• Sometimes the phone will boot with only one of the 2 sim working or even none of them,
  Seems completely solved

• "The interface is sometimes kind of sluggish, or will freeze for a fraction of a second" : Has improved significantly with 24.04-1.1. Still not always perfectly fluid, but honestly this is very acceptable, the system is quite fast.

• "Gps positioning does not work reliably in webview (in comparison to puremaps)" : There is some improvements with 24.04-1.1, it sometimes works in ideal conditions, but it is still unreliable and will still freeze/crash very easily while it works reliably on Pure-maps.

• 'It often looses celular data connection.': I'm progressing in the investigation, seems to be an IP loss problem, I might be able to write a script to automatically do dhclient when needed as a temporary workaround. https://forums.ubports.com/topic/11700/bug-data-mobile-interface-looses-ip

Which means we're getting closer and closer to a system perfectly suited to my needs, thank you so much.

@domubpkm said in Bug: data mobile interface looses ip:

The simplest solution is to turn off the cellular data and turn it back

Yes I know but this is a workaround not a real solution, it's not convenient at all, especially if you expect to receive notifications Internet needs to run always in background without manual action. Especially in the context of VoLTE I wonder what impact it has on incoming calls.

I've mentioned in Smooth Edges a bug that drives me mad concerning the fact that I regularly loose mobile data on my Vollaphone 22 on 24.04-1.1 ( with "free mobile"), and I have to switch to 2G then go back to LTE to have it working again.

I have investigated and now I know more. It seems to be an IP adress problem. When the bug appears I see "L" (for LTE) in the status bar but I have:

ccmni1: flags=193<UP,RUNNING,NOARP>  mtu 1280
        inet6 fe80::58e:ee25  prefixlen 64  scopeid 0x20<link>
        unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 1000  (UNSPEC)
        RX packets 123325  bytes 160619148 (160.6 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 47763  bytes 4939925 (4.9 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

And ip route is null.

After swtiching to 2G and then 4G I get

ccmni0: flags=193<UP,RUNNING,NOARP>  mtu 1500
        inet 10.15.62.187  netmask 255.0.0.0
        unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 1000  (UNSPEC)
        RX packets 834  bytes 79443 (79.4 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 22  bytes 5869 (5.8 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

phablet@ubuntu-phablet:~$ ip route
default via 10.15.62.187 dev ccmni0 proto static metric 700 
10.0.0.0/8 dev ccmni0 proto kernel scope link src 10.15.62.187 
10.15.62.187 dev ccmni0 proto static scope link metric 700

Next time I see the problem I will see if running a simple dhclient solves it (I think it will). If so I might write a simple script to detect when I loose the IP while the LTE network is connected, and trigger automatically a dhclient as a temporary fix for my own use. Even if including a fix to the system would be ideal.

First thank you for the constant improvements in Ubuntu Touch, it's getting better every month!

I have a question about the upcoming upgrade of Morph browser. When Morph will be upgraded with QtWebengine6, what will be impacted on day one?

-Will all the bookmark apps based on webapp-container be impacted?
-Will qml apps based on qmlscene and containing a WebEngineView be impacted?

During the app migration to the new QtWebengine and to Qt6 altogether, will app developers be able to release two versions based on the capabilities of the system, to make sure we can make use of the improvements of Qt6 as soon as possible, without breaking the app for the users that have not made the system upgrade yet? (including phone staying on focal)

Thank you!

Where should I report the bug?

@jam1388 said in Working VoLTE reports, share your experience:

4g on t-mobile starting next month

If this is not planned obsolescence I don't know what it is.

While in France we still have at least on solid year before 2G disappears, and 3-4 years before 3G disappears!

Did you possibly at some point make your filesystem rewritable to do "apt install wireguard"?

If so the best might be to reinstall the system with the installer to make sure to have a fresh start.

(A durty version might be to make your filesystem writable and remove wireguard, not the most recommended solution )