Offline
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,
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?
Hi,
Just wanted to mention that a nice and easy addition to Ubuntu touch would be wifi captive portal via RFC 8910 and RFC 8908.
It is actually very simple:
1- When you get a DHCP lease in the wifi interface look for option 114
2- If there is a URL in option 114 it's an API, just make a simple HTTP GET request on this URL (no parameters or header)
3- The result will be a json, if it contains "captive"="true" and has an "user-portal-url" field then we should just open this "user-portal-url" in the browser and it will allow the user to authenticate to the captive portal and use the wifi!
Really I think that's any easy addition, I may try to contribute this inside the OS when I have time.
Ps: Adding a simple script in /etc/dhcp/dhclient-exit-hooks.d/ to do that should do the trick I guess.
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.
Craziest thing:
The calls are partially working out of the box!!!!
Which means we can certainly get calls working one day!
Hi,
Whatsweb has been upgraded to version 0.3.0 and later 0.3.2 . @alefnode has merged my work including some improvements listed bellow 🥳. The app should work correctly for all the main features. If you see something not working please do not hesitate report, as I'm working on it these days.
Improvements released in 0.3.0:
Improvements released in 0.3.2:
Improvements released in 0.3.4:
Hello,
I would like to ask a question about the following behaviour.
In various Gtk/Xwayland apps ( in Chormium for UT, Signal UT, Min Browser, Rocket.Chat) when a secondary X window is opened (like menu window or overlay window), and I see it gets immediatly resized full screen. Then it bothers and it immediately closes. This is kind of problematic.
My questions is:
1- What deamon automatically resize new XWayland windows fullscreen
2- Is it possible to disable this behaviour, or at least for certain windows
3- I see that in uWolf the problem does not happen how come? @fuseteam any idea?
Here are the X logs for example when I open the menu of the Min browser:
bin/xev -root
CreateNotify event, serial 18, synthetic NO, window 0x3ef,
parent 0x3ef, window 0x800013, (-53,66), width 829, height 1433
border_width 0, override YES
MapNotify event, serial 18, synthetic NO, window 0x3ef,
event 0x3ef, window 0x800013, override YES
ConfigureNotify event, serial 18, synthetic NO, window 0x3ef,
event 0x3ef, window 0x800013, (125,302), width 829, height 1433,
border_width 0, above 0xe00003, override YES
ClientMessage event, serial 18, synthetic YES, window 0x800013,
message_type 0x111 (_NET_ACTIVE_WINDOW), format 32
PropertyNotify event, serial 19, synthetic NO, window 0x3ef,
atom 0x111 (_NET_ACTIVE_WINDOW), time 635893, state PropertyNewValue
FocusOut event, serial 19, synthetic NO, window 0x3ef,
mode NotifyNormal, detail NotifyPointer
FocusOut event, serial 19, synthetic NO, window 0x3ef,
mode NotifyNormal, detail NotifyPointerRoot
FocusIn event, serial 19, synthetic NO, window 0x3ef,
mode NotifyNormal, detail NotifyDetailNone
KeymapNotify event, serial 19, synthetic NO, window 0x0,
keys: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
ConfigureNotify event, serial 19, synthetic NO, window 0x3ef,
event 0x3ef, window 0x800004, (0,0), width 1080, height 2277,
border_width 0, above 0x800013, override NO
PropertyNotify event, serial 19, synthetic NO, window 0x3ef,
atom 0x111 (_NET_ACTIVE_WINDOW), time 635897, state PropertyNewValue
ConfigureNotify event, serial 19, synthetic NO, window 0x3ef,
event 0x3ef, window 0x800013, (125,302), width 829, height 1433,
border_width 0, above 0x800004, override YES
ConfigureNotify event, serial 19, synthetic NO, window 0x3ef,
event 0x3ef, window 0x800013, (125,302), width 1080, height 2277,
border_width 0, above 0x800004, override YES
UnmapNotify event, serial 19, synthetic NO, window 0x3ef,
event 0x3ef, window 0x800013, from_configure NO
UnmapNotify event, serial 19, synthetic YES, window 0x3ef,
event 0x3ef, window 0x800013, from_configure NO
DestroyNotify event, serial 19, synthetic NO, window 0x3ef,
event 0x3ef, window 0x800013
PropertyNotify event, serial 19, synthetic NO, window 0x3ef,
atom 0x111 (_NET_ACTIVE_WINDOW), time 635961, state PropertyNewValue
FocusOut event, serial 19, synthetic NO, window 0x3ef,
mode NotifyNormal, detail NotifyDetailNone
FocusIn event, serial 19, synthetic NO, window 0x3ef,
mode NotifyNormal, detail NotifyNonlinearVirtual
KeymapNotify event, serial 19, synthetic NO, window 0x0,
keys: 157 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Anyway in the long run we will hopefully switch to Wayland when Mir2.x is included in the system, and then the OSK will be handled differently that it currently is. Not sure whether the 24.04.2 branch will include Mir2.x .
@developer said in "Are we mainstream-ready yet?":
Was wondering whether it could make sense to publish a table or roadmap outlining the exact features, services and improvements that are missing to match the Android/iOS user experience. This would help potential users, as well as developers to identify quickly where to help, and possibly also funders, who could more easily understand viability.
I would say that the issue with that is that "the Android/iOS user experience" means very different things for different users, depending on how they use their phone. Some might use Android/iOS, only use some very basic phone features that have been covered for long by Ubuntu Touch, while someone might rely on this very niche Application available on Android/iOS and consider it as and an essential basic tool, while only a small minority use it. (And many different users might use different niche applications)
Some people will tolerate without problem some feature being slightly less efficient than in Andoid/iOS because they don't spend much time on their phone or use some feature very regularly, while this might be a problem for someone who use the phone intensively to loose even 1s when doing some operations.
I think all this is very subjective.
(As I've never used Android/iOS I cannot really compare anyway)
Yes I have heard that but unfortunately this is not specific to Signal UT, it concerns all Gtk/Xwayland apps ( uWolf, uFirefox, Chormium for UT, Min browser, Rocket.chat, ...).
This bug should be reported to the system devs, because it would be a real shame that it make its way to the stable release, as it would be a regression in usability for many users.
I have no way to investigate right now, because I have only one phone, and cannot afford to change to unstable version.
Ps: I'm working on notifications, a new release should be available quite soon.
@bunt7 said in No Network Connectivity – microphone is not working:
The second thing is, that the Network Connectivity jump, without doing anything, from the first to the second sim card (the second sim card is usable only for calls), and than there is no Connectivity.l.
I have the same problem on my vollaphone 22 I plan to write a script that reconnects automatically when the network cellular connexion get lost but LTE connexion is enabled, as a temporary workaround. Then we'll see with the devs if anything can be integrated in the system to make connection more reliable.
Well not sure, I've never done this process. It's possible that if the process uses a popup that requires subsurface, that it does not work properly! But other than that I don't really see why it wouldn't work, bur you never know.
@gpatel-fr said in More Apps Please!!:
also for keyboard thats an easy fix you need to include a cache file look to ufirefox/uwolf for example on how to get gtk apps to use maliitI thought first of compliing a Ubuntu touch driver for each Kde pack but it's not obvious to learn to compile various stuff for UT, especially at things that no one other than a core dev would touch. It would be a cleaner fix though
Honestly I don't know why maliit/inputcontext-gtk is not included by default in the system, so that it does not have to be included in the apps. Although the problem is that this module has some bugs and I had to make some very hacky patches to get it to work properly with SignalUT and Min Browser (spoiler: and soon Rocket.Chat ).
But hopefully this won't be necessary to use this module when we can switch to Wayland with Mir2.x .
I'm not sure what exactly this would look like, or where this would display. If you have a screenshot it could help!
@moem Maybe you could edit the first post to mention that "there is currently no native, working Signal client for UT" is no longer up-to-date. Because your topic often appears on the first results, when people are looking for "Signal Ubuntu Touch", and they might not read until the end.
Yes I know abut uFirefox.
Distributions like Mobian, or postmarketOS, don't seem to bother much about trademark concerns, in this situation.
