Some years ago, mal tried to port anbox for Sailfish, but is not working on it anymore…
Issues came from old 3.4 kernel and from anbox <=> wayland backend compatibility, as far as I remember 
2 Likes
Don’t forget OpenRepos. There is no shortage of messanging apps for SFOS. Also, Threema is AGPL software AFAIK. So porting it should be possible. If the company refuses to allow 3rd party apps to interact with centralized servers under their control, that would be a great reason to stop supporting them and switching to another end-to-end encrypted messenger. Personally, I am using neither but see no disadvantage of e.g. Matrix over Threema and there is a client readily available.
IMHO, just the UX improvements of SFOS over Android (and thus /e/OS) easily outweigh the inconvenience of switching an app or two one got used to (or as you put it: ‘needs’).
Either way, enjoy you alternative OS experience (it is all about choice in the end) and have a great one!
Honestly, I don’t understand a lot of your message - there are too many abbreviations not familar to me, sorry.
I don’t have the time to “bastel” as I would call it in German, either the things I need are available, or then I let it be. Dixi.
Sorry for abbreviating so much:
- SFOS → Sailfish OS
- AGPL → Affero GNU (sorry for eplaining an acronym with another one, but there is no other way since GNU literally is short for ‘GNU’s not UNIX’) public license; a free and open source (FOSS) software license that the Threema source code is released under.
- AFAIK → as far as I know
- IMHO → in my humble opinion
- UX → user experience
- OS → operating system
Regarding the non-‘bastel’ solution, my suggestion was to look into Matrix as an altenative to Threema. While not available in the Jolla store, you can easily install the Storeman app to install Sailtrix from OpenRepos. If you find you really need Threema, I’d be curious what it offers that Matrix fails to provide
But like I said: I just wanted to suggest a way forward, if you prefer Threema under /e/OS, who am I to judge?
3 Likes
Thanks for the explanations.
And no, Matrix is not an alternative to Threema, as half of Switzerland is using it now and so there are a lot of lists and chats etc.
@mal Trying to update to first intermediate 3.4.x.x and have a question: Is there a little flaw in the wiki?
version --dup
NOT AUTHORISED. This tool must be run from a privileged shell.
Ran it successfully with “devel-su”.
2 Likes
I thought it mentioned devel-su, if not then I will fix it.
1 Like
A quick status update for next release. I tested updating Sailfish OS 4.2.0.21 and it worked without issues. Based on quick test of all hardware features and built-in apps I haven’t seen any regressions so far. I will continue testing in daily use a bit more to see if everything works correctly.
4 Likes
Hello @mal,
installation works without problems. Also all jolla apps, Nextcloud, email and Browser.
But camera issue occurs as described on earlier updates.
After restart of detection process (three times 
) the camera setting was successfull.
Many thanks for the update
gabs
Hello, I’m happy with Sailfish on Sony, but I want to try the sustainable path.
My FP2 was a clean 18.04 (I installed no TWRP nor openGApps, and yes, I calibrated the proximity sensor etc).
I flashed it via fastboot as described in the Sailfish wiki (i.e. ./flash-for-unix.sh).
After fastboot reboot, the app optimalization completed, but it hangs saying “Android starting, preparing configuration” (translated from my language). It takes forever …
(I haven’t begun with the sailfish zip part yet.)
While still hanging at the configuration: The fp2 is listed as an unauthorized device by adb.
What is the recommended path from here? I am bewildered by many different suggestions online, a hint would be great!
I’ve downloaded TWRP 3.5.2_9, but is it safe to “flashboot flash recovery twrp.img” with an unconfigured android from fp2-sibon-18.04.1-manual.zip? (I would need to turn off the fp2.)
Is TWRP necessary or only recommended?
I run adb/fastboot on a Debian stretch with version 7.0.0+r33-1.
Best regards
@treadmill Hi, if you have already calibrated the proximity sensor and you have flashed Fairphone Open 18.04 as told in the instructions then you then don’t need to boot to Android before installing Sailfish OS, just go to recovery (twrp should be fine) and install Sailfish OS zip on top of the Fairphone Open 18.04 installation.
Thank you, that helped. The pre-installed TWRP worked just fine. Smooth. Only one problem: just after finishing the obligatory gesture teaching tour, the phone froze and the battery looked empty (red LED). A reboot solved that.
Info for people who are not constantly wifi-online: The “semi-permanent” battery power saving mode seems useful to prolong battery life somewhat.
Best regards
Hello @mal,
using the Sailfish OS 4.2.0.21 about two weeks it seems everything is fine, except a small issue with wlan detection.
Some time it seems that known wlan connection did not work when in operating distance.
I did not see a deterministic behave, but sometimes when i leave home and come back (without come in reach of an other known wlan connection) the wlan symbol is in searching state and did not connect within hours. Stop and start wlan resolve the problem (so it is no big problem - but should be known if someone is waiting for emails or messages 
).
I dot not use mobile connection when i leave home for a short time.
I think there was some known issue with wlan handling, I will check if it was also in 4.2.0 or some other version. I have also been using 4.2.0 for quite a while now and no big issues so maybe it could be released already.
1 Like
I’m still in release1 and I have now time to update to release2 
If I understood well, going from release1 to release2 is equivalent to 3 upgrade process:
IMPORTANT! You need to update from 3.3.0.16 first to 3.4.0.24 (note the hack mentioned above), then update to 4.0.1.48 and finally update to 4.1.0.24. Always reboot after each update.
The mentioned hack is a new file to add, here are the step I do in a terminal:
cd /lib/systemd/system/
devel-su mkdir dsme.service.d (this folder didn’t exist before!)
devel-su touch sandboxing-disable.conf
devel-su vi sandboxing-disable.conf (nano is not present 
)
Then I tried to paste (with P) but without any success… (error E353: Nothing in register ”)
Paste with “Shift + Insert” 
Save file with “Esc” + :w and exit with :q
Thank you @mal! After this modification, the rest of the upgrades was flawless 
| Sailfish OS 3.3.0.16 (Rokua) → | Sailfish OS 3.4.0.24 (Pallas-Yllästunturi) 
devel-su rm /lib/systemd/system/dsme.service.d/sandboxing-disable.conf
Error msg: [D] unknown:0 - "No carrier"
| Sailfish OS 3.4.0.24 (Pallas-Yllästunturi) → | Sailfish OS 4.0.1.48 (Koli)
Error msg: -bash: /etc/profile.d/developer-profile.sh: can't open /proc/12829/environ: Permission denied
| Sailfish OS 4.0.1.48 (Koli) → | Sailfish OS 4.1.0.24 (Kvarken)
No error msg.
I also noticed that we have a new screen background 
This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.