Offline
Ok in this version of whatsweb I have the notifications working without being unconfined, and it gets to the system panel! (Provided the app is not suspended in background)
https://github.com/pparent76/whatsweb/tree/82cd0c659af09bfad4315ba6c39e398d881451c3
Hi,
Whatsweb has been upgraded to version 0.3.0. @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 in current release:
-Support for notifications (if app suspending is disabled in Ubuntu Tweaks and app kept open)
-Smoother navigation with transitions
-Smoother keyboard appearance/appearance
-Avoid opening the keyboard untimely, when navigating
-Enable GPU acceleration
-Hide left panel for more pleasant interface
-Make Emoji panel usable
-Better graphical integration of navigation buttons ( back in chatview )
-Copy a message to clipboard quickly with a long push on message.
-Screensaver when the app is not foreground: hide the webview to save battery
-Fix "contact info" panel
-Fix left menus.
-Fix Upload files
Improvements coming very soon in another revision:
Todo later:
@Opolork Dual boot is possible on vollaphone, it's a feature provided by the manufacturer.
https://wiki.volla.online/index.php?title=MultiBoot_mode_in_VollaOS_for_VollaPhone_Quintus
My solution to the initial question:
Here is my QML module to handle local notifications:
https://github.com/pparent76/UbuntuTouch-qml-notify-module
It contains a script setup-project.sh to install automatically all the requirements into the app project.
Also this push request to the whatsweb app can be pretty informative:
https://github.com/alefnode/ubports-apps/pull/44
Especially this commit that corresponds to setting up the module with setup-project.sh:
https://github.com/alefnode/ubports-apps/pull/44/commits/81d08baba14ed941ca0c9b246d0df543b0a452a6
And I guess privacy and freedom activists especially in the field of mobilephones, might have interest in being proactive and proposing solutions at the edge of privacy protection, rather than letting others propose solutions that are not so good for privacy.
If others want to do it, I'm willing to participate in developing such an app.
@lduboeuf said in Send notification locally from QT/C++/QML App.:
congrats for your perseverance. Now you are in the perfect situation to update or create a documentation
Thank's I will make better than this! 
I will update my QML notification module, and make a scripts that installs into an existing project all the prerequisites for it to work. Because there are some many tweaks to achieve it that it should not be done by a human, it's a loss of time, and the risk of mistake is too high. And anyway a script is always a more precise documentation on the actions to take than a human readable documentation.
Hi,
I'm wondering how much of non-free software is there in UBports?
I guess that there must be at least non-free firmware blob in the kernel, as only few distributions remove them ( e.g Debian, Trisquel, Pureos ). Are there also non-free drivers in the kernel for some devices? Are there other non-free software unrelated to the kernel installed by default?
I think it would be most interesting to have a most precise view on this question, since the free and open-source software argument is the main advantage of UBports against Android.
Also note that Replicant maintans a list of "Freedom and privacy/security issues" for each of its targeted devices. None of them is completly free of issues.
Thank's in advance for your reply!
PIerre.
Thank you for your work it seems very interesting to me!
Just a quick question: do you think it would be feasible to create a .click package and have it in the Openstore? In a similar fashion that uWolf and uFirefox does? Can we avoid libertine containers? Do you think upcoming Mir2.0 will change anything in this regard as it supports Wayland?
Do you use Mobian build scripts for ARM, for signal-desktop? https://github.com/0mniteck/Signal-Desktop-Mobian/releases
And also note: if we can get an initial version to build and make an UT package I'm willing to work on making patches to make the interface responsive as I have done with whatsapp web. I think this is the easy part.
But we should first make a set of scripts to build automatically a binary, and then a click package that can run on UT.
For anyone interested I made a small qml module, allowing desktop notifications with haptic feedback (vibration). Once again this is not optimal as the notification does not make its way to the ubuntu touch panel itself, and requires the app to be unconfined (EDIT it now trigers notifications on system panel, and does not require to be unconfined), but it is still very usable and usefull.
Just wanted to mention that I discovered recently that it is possible to use signal on Ubports, through the app "molly FOSS" in waydroid, that can be linked as a secondary device to your main acount. It works pretty smoothly (although you don't get notifications for new messages) and it is even possible to do video calls with it which is beyond expectations. Of course end to end encryption is preserved.
@pparent This is not a good idea to do.
No disrespect, but I think this is why I will choose pureOS in the long run, whenever I receive the phone and it is usable.
As users I want to be able to do the same things we can do on our computer, and be in control of our device, without being artificially limited, and not being sandboxed into a container. Otherwise I would use Android!
Ps: And by the way I also plan to make this whatsapp application way more usable than it was. The version currently on my repo, already include some improvements that make the app significantly more fluid, polished and usable. But I will keep improving it progressively, and I plan to fix all the major functionalities offered by whatsapp web, that are currently broken on the app (starting with downloading/uploading photos/videos). And also I guess that future upgrade to Qt6 will also be a leap forward in regards of performance of this app, given that the webengine will be significantly more modern.
@RJDan said in Taking the plunge:
@O.o. Thanks for sharing. Its great to see what others have done. The am/pm trick is a neat way to deal with the corners!
In that regard, you might be interested in this:
Thank's a lot for the answer and for your work!
In pratice I get this warning but nothing happens if you don't open it (at least for me). It has been months that I haven't opened the main device and everything works well.
The thing is that we can never hope to have a main device client that is reliable and with all features, if it is not official. Official support will not happen for UT in any forseeable future. And any unofficial client risks to end up in broken and unusable acvounts as it happened many times with axolotl.
And let's be realistic features like calls could possibly work one day with a customized build signal-desktop , but will likely never work with a custom client form scratch or based on signal-cli.
@XPran said in Desperate guy Here:
The version that i have is the 16.04.7 LTS
Uff yes this very old, make sure to upgrade the system before anything else if you want to have a decent experience. For this reason you don't have a good experience of the system.
You may have to do several upgrades in a row, as you probably won't be able to go directly from 16.04 to 24.04. Or you can, indeed reinstall a fresh system, with the installer could be the easiest option. And if you don't have any data on the phone you can wipe userdata when installing to have a completely factory-like install (but you will loose all data!!), but if you have userdata that you want to keep make sure to leave the "wipe user data" box unticked and it will be preserved.
I would recommend installing 24.04, as it works well on Vollaphone 22 and hardware acceleration works significantly better than on 20.04 form my experience from my experience, and it will avoid further major upgrade later.
I'm very surprised you have this version if you bought the phone only 8 month ago. Was the phone new?
@O.o. said in Taking the plunge:
SMS-based authentication is a terrible idea. There are few things more insecure than SMS.
For what it’s worth, I would say there are few things more insecure than current banking to handle money in the digital era! 
Though in practice in my country there has been a scam boom based on these banking applications, and I would say that ironically using the SMS + long-term code protects more against these scam. Because when a fake bank advisor asks you to do something in an app, if you're not tech friendly, you may do as they told quite easily because you don't understand and you're used to be assisted, and that people do it for you (Maybe it's even your adviser that installed the app for you...). But then if a fake bank advisor calls you to ask for your personal code that you have been told to share with nobody, it can trigger way more warnings and it's way harder to justify. Security is not only about tech, there is also a human side.
But anyway the good solution based on smartphone would be to use standard TOTP, which is implemented in UT, and is simple to for users.
I'm glad I'm not living in you're country by the way, where banks handle authentications for public services... It's aslo the banks that edit passports?
Even without internet the js and webassembly scripts keep running in the webview (if it is not suspended)... If it's hidden it's optimized so that it's mainly background workers that stay working.
Yes, I would love to test versions before they are released to openstore!
Great I'll tell you when I have the next revision finalized on my side, probably next week, and we'll see how we can do.
Though if you know how to compile an app I publish my code as I go : https://github.com/pparent76/whatsweb
(Note that in this repo I work with an app id "whatsapp.pparent", so it will not override your app from the openstore)
@mihael said in Whatsweb app upgrade.:
@pparent I have a N10 on focal and a N100 on noble. Whatsaweb looks perfect on both, no problem with the scaling.
Ok Nice you will be able to test it. With latest revision normally you will have fontsize a bit bigger, that to me seems more pleasant to read, and more on par with Android app.
On another note, and I don't know if this is something that can be easily fixed: when I forward a message, it does the forwarding but then there is no back arrow from the chat. I have to restart the app. This has been with the previous version of the app as well.
I see, it will be solved in latest release, alongside other situations where you could be stuck.
