matf-kabouik

I believe it no longer is necessary (or even recommended) to use the boot partition from Ubuntu Touch with latest SFOS builds. Have you tried using just the SFOS zip and the script in it? Please confirm so that I can adjust the instructions in the first post accordingly.

In case others encounter the same issues @Hook has had along this rocky road, one thing I think has changed when it worked, is @Hook actually booted stock Android and denied all prompts for setting encryption or a lock code, before flashing Droidian. I believe the first boot fiddles a bit with partitions (maybe @eugenio will correct me on that point), in which case Droidian may have found a non-working partition setup when coming directly form Lineage (perhaps with some encryption somewhere?), or when stock was not booted at least once. I have never encountered the same issues, but I alwa

A new thread that may interest some of you here:

@eugenio, core team member of Droidian, had the idea of dual-booting Droidian and SailfishOS a long time ago and even did some experiments, but this was not tested in depth, nor documented. It now is! See instructions here: https://gist.github.com/Kabouik/94e9e60d84c0eeae9d48e18c11ed419e I am not pasting the how-to here, just the URL, so that there's only one place to edit if changes have to be made in the future. This may work with other secondary OSes with some slight changes, or with the Pro1x (where the extra storage could be handy), but was not tested so far. I chose to do that on th

Thanks for trying it @GoaSkin! I remember that I wanted to try it myself some weeks ago as I did on the Pro1 back in the time with that small PR, but got sidetracked to other time sinks and then simply forgot because I don't play much video outside of my LXC container. Great to hear that it (kinda) works.

I updated the flashing instructions in the FP to use Adam's kernel.

harbour-containers is now in the Chum repository, hence easy to install! Please let us know if there are any issues (but check the known issues first), preferably as issues in the repositories so that we get notifications. It's only tested by me so far, and on a single device, so I hope it will work well enough for other devices.

I experience the issues with rebooting the phone when Waydroid has been started (and also the whole OS freezes when we close Waydroid), but I do not have to redo the chmod step at every boot, there must be something missing in your initial Waydroid installation.

I got sound working in LXC! I will now try to make that work in the default install and then the app shouldn't be far from hitting the Chum repo for easy installation, but it'll be some work to automate that.

We should know by tomorrow if Adam's kernel update works out of the box, with even an install script to simplify the process. I'll post an update here and edit the FP when this is confirmed. No need to back dtbo up, it's not unique to devices. Yeah, the video (playback and recording) problem is a known issue, it's listed in the FP, but I don't know if Adam knows where it comes from (or if it is a priority). I expect it may just be some configuration file to edit to properly set hardware decoding/encoding, but I am not sure. I really want to get audio working in LXC because this would

Ha, I was about to reply, but I recognize this excerpt above. 👀

Yes, this is expected with the UT kernel and current SailfishOS configuration. What happened is I submitted a PR to the Sailfish configuration that aims at complying with Adam's kernel, but the things that changed work in the opposite way with UT's kernel. So, if you are using the UT kernel (current instructions in the FP), then you have to revert the changes in these two files (edit them so that they look like the left panel): https://github.com/sailfish-on-fxtecpro1/droid-config-halium-qx1050/pull/4/files Alternatively, you can try using Adam's kernel, which allows using Waydroid,

I'm not a Windows or Mac user, but I'm pretty happy that we have two tools at hand, including one that's multiplatform, fully open source and based on an open source language. The alternatives to that would either be (i) nothing or (ii) proprietary software, which I would view as a much higher "infection" risk. I mean, at some point we'll have to install something on our machines to perform operations to reflash our Pro1(x), there's no other way, and them being flashable easily was one of their selling points. Python also is a language that can easily be containerized in a virtual enviro

Camera works for still images, calls work, WiFi works (but see potential issue in the FP), texts work, MMS work, F-Droid works in Waydroid but I couldn't add custom repositories because F-Droid would crash, I have not tried Google Play apps. Copy/paste works fine in Sailfish, what's difficult is to transfer the clipboard from native apps to Alien Dalvik or Waydroid ones, or to LXC of course. I remember that copy/pasting from emails was not trivial (we had to go into edit mode to copy text), I don't know if that's still the case because I read my emails in my LXC container now.

For me with SFOS, the first command was necessary, or the second would have no effect at all (device would boot when plugged_. On another device with Droidian, even using the two commands had no effect, so perhaps it's OS-related, in which case I suppose Android only requires the second? I don't think the first one hurts anyway, so it might be a good idea to advise it if some OSes need it. Also, I got that from Tadi who has absolutely all my trust. 😮 After asking why the second command didn't work for me, he immediately replied that another one was missing. I didn't think about it much fu

I've opened Pro1s but don't really remember, and it could be a tad different here anyway. What I know however is sometimes the FPC were not perfectly connected, but not necessarily completely disconnecter either. This happened to me after a soft fall when the USB charger was plugged, which applied some force to the USB board and probably disconnected it a bit. After that, several things stopped working, including I think the microphone or the bottom speaker. Reconnecting the ribbon cable fixed it. I can't tell however if the same could happen with backlight. In general, unless you really

Can you make sure you used the Pro1x image and not a generic one? I used a nightly build and it worked with no issue here, but the release 15 days ago should be even more stable so all should be alright if you used that.

I wanted to do it on mine but that didn't work, an extra command is required when in bootloader mode: fastboot oem enable-charger-screen fastboot oem off-mode-charge 1 (Thanks Tadi.)

I have Droidian on a Pro1 since last year, and on a Pro1x since last night. Droidian hasn't been a daily driver for me (mostly due to battery life and the fact that I'm not friend with the ergonomics of Phosh) so I don't know everything about it, but feel free to ask questions. I have played with it somewhat actively last year to get alternate WMs working (Sway doable with some work, and with issues, i3wm doable too with a X hack), LXC (doable with Sway as WM but the keyboard mapping caused issues for my keybindings), Waydroid (Droidian may have the best support for it), or simply install

As far as I understand, IMEI and whatnot should be in fsc, fsg, or more likely modemst1 and modemst2. Don't quote me on that though.

Mosen definitely backed fsc, fsg, modemst1, modemst2 and persist (which I advise to do as well, they're only taking up 40MB of storage space on your disk), but I don't know if he restored them all.

@mosen said he has successfully restored a backed up persist and passed attestation test, so it would be great to have his view on it and know exactly what he did before concluding on that matter.

I can share with you the kernel 1.6.1 from Adam (later versions that can be downloaded from his repo break the keyboard mapping so I don't advise them), but if you're not too much in a hurry, it might be best to just wait until he comes back from holidays and updates it with working mapping improvements.

https://github.com/Kabouik/harbour-containers My PR to harbour-containers has been merged, it should now work much better than the upstream one that was using qxdisplay and, most of all, could no longer configure X in new containers properly. Instructions have been simplified, with just 3 packages to install from one single place (and hopefully from Chum app store soon, I'll submit them today), better default settings for X scaling and Onboard vkb, and most of all without the need to tweak things manually to debug container creation. - 3 packages to install from a single OBS re

Erm, it would have been wise of them to warn you on the need to do a backup first, as the stock persist.img doesn't contain device specific information that came with the persist partition originally on your phone. At the moment, it's not a huge deal as it's not even sure that any software uses that kind of hard verification, so your phone won't be broken, bricked, or unusable in any way, so don't worry too much about it, but we never know if the attestation keys may not be necessary in some obscure software you'd want to use, or in the future years. There may also be ways to regenerate