matf-kabouik

This really looks like you're flashing the UT userdata as well then, instead of just the UT boot.img and SFOS userdata. Can you double check that the userdata image you flashed had the .simg extension (SFOS) and not just .img (UT)? Sorry if you already did, but that is what a reset UT after flashing would suggest. Yes I could do that but I would still lose a lot of binaries I compiled on the device (I use many terminal tools), which are not easily reinstalled on a new container since, well, since they were not installed as packages. But that is definitely something I can do, it

Thanks @claude0001. If this was my issue, I would assume that newly created containers would equally fail to show in an X window, but they don't. I really need to check the logs when I try to start the Xsession script, see where exactly it fails with that specific container.

I did start from stock Android but I'm not sure if that would be a requirement. After flashing, do you get back to you existing UT install, or was it reset? I bet you did that already, but if it was reset, maybe triple check that you didn't mix the images at the beginning since we need to mix both archives? Can you maybe add a: fastboot set_active a at the end of the procedure? This should not make a difference, but it's worth trying.

I cannot agree more with the neofetch show off part, nicely put @claude0001. And actually I am afraid that many users of LXC on SFOS or other systems have felt overwhelmed by the extra work needed to configure their DE, or just don't see how much of a game changer it can be, and they end up not using it much. I have a VERY configured LXC container from my Pro1 that I can use and attach on my Pro1x, but so far I haven't been able to start X on it. It is a bit oudated and there's probably something that is conflicting, I have yet to identify what the issue is because I can start X in newly

Sure, I posted a link above in the message showing LXC pics, here it is: https://talk.maemo.org/showpost.php?p=1574496&postcount=237 The setup is not exactly user-friendly at the moment because the dev of harbour-containers does not use Sailfish anymore, and some things have changed, but it can still be made to work. Then in my opinion you also need some configuration inside the container to make it really convenient for the small screen size and to use keybindings as much as possible instead of touch (see what I did with my Pro1 for instance: search on Youtube for "Pro1 Saiilfis

Excerpt of the latest changes in the list in the FP:

LXC containers work (with Xsession, but the setup is not as user friendly as it was on Pro1 in 2020😞 Still no luck with Waydroid despite my attempts, but theoretically this should be possible because there are unofficial images for Halium 11 that have already been shown to work on SailfishOS (other devices), Ubuntu Touch, and Droidian. These are the images I tried.

After comparing Pro1x, a Pro1 and a Titan Pocket, they all report similar dBm for my WiFi network, but maybe the Titan is just not great either?

To disambiguate, I'm not the porter! @piggzis. I'll try to progress with Waydroid as I know it's going to be a game changer for many users, but unfortunately right now I have to choose between web-browsing or waydroiding (see issue here: https://forum.sailfishos.org/t/browser-not-working-alongside-dnsmask/10829/29?u=kabouik).

Yup I didn't mean to add the dual-sim item in the Neighs, but wanted it in the Yays! I just meant that I haven't tested the second slot yet. About storage, there's something even stranger since this unit is a 128/6 GB variant, so I shouldn't see this much storage. I forgot to check how the partition sizes were showing in Android. I posted this list on Discord and Telegram too, but I'm trying to keep the one in this thread up to date so far; I updated it a bit already. Not sure I'll dot it in Discord/Telegram. -- Kabouik

Following @esialb's thread on Ubuntu Touch, here's one showing that SailfishOS works too: ——— Instructions: - First and foremost, backup your "persist" partition. Better safe than sorry. Instructions are in other guides, Please, do not skip that step, there is no other way back to the vanilla persist partition. - Download and extract the latest artifacts.zip from the SailfishOS port repository: https://gitlab.com/sailfishos-porters-ci/halium-qx1050-ci/-/jobs - Pick your clacky Pro1x, power it down, hold down [Volume -] and [Power] until it boots

I missed that topic this far! The below video shows 60 wpm/252 cpm, but I'm now about 10% faster. There seems to be a convergence to about 40-65 wpm here, which together with the accuracy (very little mistake rate) should be enough to convince people about how useful can a hardware thumb keyboard be; and that's without bringing screen estate and application/OS keybindings into the equation.

I assume most people will do the same, those ready to use Ubuntu Touch or LineageOS probably were prepared to flashing themselves at some point anyway. I asked to change too, but made sure they knew I wouldn't keep Android. It probably doesn't make any difference, but just in case, I want F(x)tec to know that offering alternate OSes was and still is greatly appreciated and a selling point for me, despite this temporary choice in favour of Android to get the device earlier.

From the latest update: The available engraving area must have been increased in the end. I remember mine (top left, IGG contest reward) used all available space in height and width in the demonstration render they provided, but I see the lunar module in the bottom row is much higher. Not a complaint at all, it is good news for those who wanted bigger logos!

We have a great GPS application with offline support and it supports OSM, but indeed it is difficult to get a GPS fix in SailfishOS since the Mozilla location thingie has been discontinued (very long and how long it'll take is hard to predict). Android apps can be run with compatiblity layers: either the official one (proprietary and not available for community ports normally, but tinkerers found ways to use it if they had a paid licence aside from the port) or Waydroid (free and open source). They have some limitations which usually are related to hardware access (camera, BT) or apps that hav

Ha, I've tried that on SFOS too to cope with the lack of video out, but (1) performance was bad, and (2) I thought it beat the point anyway since a computer is needed (even if it can be a low cost one such as an SBC, in that case I'm probably better off booting Linux from it directly). Interesting to hear that performance was better in your case with a different setup. As for the native ecosystem, there are indeed both pros and cons with SailfishOS. Having many GNU/Linux tools and a terminal with full access to the system out of the box is great for instance, but indeed it's hard to find

You're not the only one, I've been using my Pro1 as a laptop more than a phone since February 2020 (but using a different setup, my host is Sailfish)! And I am not ready to stop anytime soon, the Pro1 really is great at that use case. :] Very happy to see that there are more and more solutions to achieve similar results.

I am not objective, but I recommend the video in this thread: Desktop Linux on Pro1 without sacrificing telephony: LXC containers in SailfishOS (video) (and check also other videos from the same profile on Youtube, there is a shorter one and a couple others showing Debian in action within SFOS). If HDMI-out was working on Sailfish, I'd say it could be used as a pocket laptop (which I already use it as) and a kind of NUC onto which you'd plug a display and full keyboard. The community has been working towards that goal, but no idea when/if this will be done. Linux + HDMI-out can alrea

Please don't hesitate to star the instructions on gist.github.com to make them easier to find by others directly from a search engine.

Hey, I'm Kabouik from TMO but I admit I rarely check the F(x)tec forum nowadays, my interest is still very high but there are just too many forums to check (even on TMO, it goes in cycles with sometimes several months without checking :/). Thanks for posting that here Fxtecish! pmOS on Pro¹ is still immature, but as said in the post, it's a nice milestone and it also facilitates flashing mainline on the Pro¹ (though keep in mind mainline is not ready yet, but at least it's ready enough to boot distros like pmOS). Hopefully this will also attract more developers, including the Maemo Leste

Very happy to see that you got yourself a Pro1 HengYe, and even better, one in mint condition! Also glad to see that this time we don't lose anyone, since DieBruine will use a Pro1x and stay with us! (Now you have a good reason to restore your Discord-Matrix bridge.)

Well then I'm your buyer. :O

I missed the previous mint-condition unit sold by DieBruine and so I'm very interested, but I'm a bit concerned about customs fees (I'm in EU). Does anyone know if the fact that the initial bill came from a EU company (at the time) with prepaid VAT (for EU customers at least, not sure if they made different paperwork for US customers) could help mitigating the cost?

Absolutely. I think now it's only a matter of downloading the image, extracting it, and executing the supplied .sh script. On Windows, one would copy the content of the script and execute things one by one (or use WSL, or convert to .bat, I guess). Note however that users have reported that the late ≥4.0 images do not work and would end up in a boot loop. Adam is on it, but no update has been posted yet. The way to go for now is therefore to flash an older image somewhere between 3.4 and 4.0, and then use OTA update. I haven't tried, but other users on Discord can probably elaborate.

May I be the next on the waiting list? I know there's pretty much no hope to get it, but never know. I bought a spare Pro1 second hand last February but it turned out to be broken and unrepairable, so I'm still with no fully working Pro1 spare, and I don't see myself surviving without one.