matf-kabouik

Could you please both add a warning at the top of your post, along those lines? 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. We are seeing more and more users losing their attestation keys because they didn't backup their vanilla partitions before flashing alternate OSes, and some data have been shown to be unique to devices and not auto-regenerated when flashing stock. I'm not saying they come from this thread specifically, but

It's a known issue that has been reported during testing in the last few weeks. Engineers/devs at the factory did have HDMI working, but turned out the protocol they used only work with the HDMI adapter they were using. They have showed which adapter they were using and there was nothing special about it, not a proprietary one nor something with a chip in it. Since then they have tried to change the protocol so the same HDMI adapter may not work anymore. This suggests just a software issue though, and Liangchen said it's just an issue with the protocol they used and asked them to change it. Ho

Awesome, @Aka.

Could you please both add a warning at the top of your guides, along those lines? 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. We are seeing more and more users losing their attestation keys because they didn't backup their vanilla partitions before flashing alternate OSes, and some data have been shown to be unique to devices and not auto-regenerated when flashing stock. I'm not saying they come from these guides specifically,

Still not really Linux as in mainline Linux, but speaking of LXC, I have tried to update harbour-containers today to fix some long lasting issues that were keeping many users away: https://talk.maemo.org/showpost.php?p=1574540&postcount=240 It's being tested in the fork, everything may not work, I'm not a dev. If all goes well, I'll make a PR for upstream and push it to the Chum repository (a FOSS GUI store for SFOS).

I received a blue Pro1x today and was planning on flashing it on it tonight, but got a bit sidetracked with LXC containers in SFOS. I have Droidian on a Pro1 and it's really nice and flexible, the main issue being battery life which is not optimized yet. I'll be playing with it on the Pro1x over the night or the week-end, for sure. I was only waiting for the delivery to test it. [Edit]

This has been done here by others indeed (namely @claude0001and you for Android/Lineage, and others and I did it for Sailfish and Droidian too, but I believe I'm the one who used it the most on those two OSes: https://youtu.be/-dgD5jci8Dk, https://youtu.be/8PnDZtKzsSc, https://youtu.be/rgxrJj37xOs). To some extent, running a custom WM onto Droidian (the host, not a LXC container) is feasible too. I have a Pro1 running Droidian with both Phosh and Sway (plus my i3wm container too), but there's a significant issue on the Sway side because the resolution is twice smaller unless I set scaling

That's interesting. I'm experiencing issues with my home network on other devices as well since a few days. I don't remember any of it in the first days i've used Sailfish, though, but maybe I just didn't pay attention. My laptops are losing connection to the WiFi network regularly, but surprisingly the wired devices don't seem to be affected. I don't know if it is related, but it definitely could: ssh over WiFi to the Pro1x running SailfishOS is *very* unstable, and gets more unstable with time, until it eventually just disconnects. Pretty sure this could be the same root cause.

Thanks for your neutral review! The camera issue when keyboard is open is fixed in a later update if I remember correctly, that you could get as OTA soon (hopefully) or in the beta program (see other thread here).

Nice comparison, and good looking Pro1 (I bet it's a spare)! Thanks @VaZso.

Sadly there's nothing fully working yet, and it's hard to know the status of things that were promising. - Kholk/Angelo showed very encouraging progress with mainline on the Pro1 (msm8998) more than 1.5 years ago, but then I didn't see more news about it or instructions (but we may have to check his commit history somewhere?): - Then, as @claude0001mentioned, @Danct12managed to boot Arch ARM on Pro1, but I think it's stalled and he is not working on it anymore (due to touch noise that mainline doesn't dampen): - And then, the same @Danct12 ported postmarketOS to

Check here: https://github.com/UbuntuTouch-vayu/waydroid_11/releases Sorry I missed your previous message asking for that when I was away. Would be interesting to see if that works for you with the UT boot.img.

Pretty sure I read that somewhere from someone who would know. Fortunately we have a Pro1x preorderer who seems to be able to work on mainline too, and even if Angelo is independent again, he might still want to work towards mainlining both devices (after all his work on msm8998 was long before F(x)tec said he was part of the team), so all hope is not lost.

The closer you can get to Linux in the way you mean it, currently, is Droidian, which is like Mobian but based on the Android kernel.. They already have a port working, which I aim to test later this week. But no news on mainline yet. Techwizz on the Discord is motivated to work on it, but it's a huge task so I don't know how far they can get alone. I believe Angelo no longer works officially for F(x)tec, but don't know what is the reason for that. I heard he is in an community dev group though, but no idea if he is active at the moment.

I also got similar results between Pro1, Pro1x and Titan Pocket for WiFi (posted in the first page), which doesn't mean it's great, but certainly is usable. I always felt that my Pro1 was not the best at network reception, but I still wouldn't have used anything else since I got it in late 2019. Mobile network reception is more critical to me than WiFi, and that I didn't compare between Pro1, Pro1x and Titan Pocket because I was too lazy to swap my SIM card, but again the Pro1 was not stellar there, but not what I would call horrible either.

Adam helped me to get Waydroid to work! And shadow.tech works in Waydroid (no sound nor keyboard, though, so it's somewhat limited): See how to get Waydroid to run on SFOS and what doesn't work: https://github.com/sailfish-on-fxtecpro1/droid-config-halium-qx1050/issues/1#issuecomment-1215734546 The current list of issues after just one hour of use: Camera doesn't work (who cares? But it shows that some hardware is not visible to Waydroid) Vibration does not work Landscape rotation is borked (it just stretches ev

Dynamic orientation works in LXC even with a tiling WM, thanks to qxcompositor (we were using qxdisplay with harbour-containers since 2020 because at the time qxcompositor didn't support portrait, but qxdisplay doesn't support dynamic changes so the update qxcompositor is now superior): Useful mostly for other devices, but even on Pro1 it can be cool when just consuming content without the keyboard.

There is a Matrix bridge indeed but I don't remember the address, maybe some others here can comment (@mosenuses it for instance). [Edit]: https://matrix.to/#/#fxtec:revreso.de

This is a known issue that was fixed in a later update, that you should get by OTA soon, or through the testing program when they open it to all bravehearted users.

I can't promise I can help you but it would best if you could join the Discord server (see another thread here on the forum) so that the community can troubleshoot with you and try to diagnose your issue first, it'd be easier to interact quickly than on the forum.

Regarding LXC, as discussed above, configuring keybindings is a key to make them productive on Pro1/Pro1x. However, at the moment, the Yellow modifiers do not send a keycode (nothing in "evdev_trace -t" on SFOS, and nothing in "xev" in Debian). Therefore, although they work and produce the yellow-printed characters when combined, they annot be used to configure custom system-wide keybindings. Yet, they are the most adapted for that use given that they are replicated on both sides of the keyboard and can therefore be combiened with pretty much every key, including other modifiers. I warned

Thanks for checking that. I don´t have access to my openvpn files where I am, but I'll be able to test that later. It's a bit early to tell, especially as I haven´t use my Pro1 in a long time because it had the ghost touches issue and I was too lazy to swap the screen at that time. Overall, it doesn´t feel snappier (no surprise), and might even be a tad slower but I need more time to confirm, and a proper comparison with the Pro1 really. In any case, the extra RAM can be useful for that usage, as I was often reaching 100% RAM use on the Pro1. I think the "boot_a"

Great finding, thanks for posting about it. I edited the first post accordingly. Meanwhile, my old container works, it was just a permissions mixup due to my backup/restore procedure: [Edit] Damn, I wrote "Home seet home". What a fail. :<

I just confirmed that SD card works, and there is hope for Waydroid. I can start a container and a session, but didn't get the UI to start (the loading splash screen spins indefinitely). Adam Pigg managed yesterday to start the UI once: However it's still not really working: closing Waydroid or stopping the container crashes the whole system and a hard reboot is necessary, and Adam could only start the Android UI once, it didn't work at the next boot. It is encouraging though because it appears to be technically feasible, it should work eventually.

I believe the last two lines of your flashing instructions are unnecessary @esialb: … fastboot set_active a fastboot continue I believe it's OK to stop after flashing userdata.img, and then when it completes (there should be a progress indicator), just reboot the phone. I'm not 100% sure, but I think those two commands might even hang and confuse people (though they don't cause any harm, they could just be interrupted with Ctrl+C, which is what I did when I tried them while flashing SailfishOS).