Leaderboard

@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

A new thread that may interest some of you here:

I`ve found solution for the waydroid crashes - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.28 specifically the commit https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.28. It is a one line change and it works. I'll provide more soon, but now I am busy with other things. I wanted to share at least the experimental boot image, but I can attach max 2MB files. Any suggestion for a sharing platform?

Just got around to updating to the 20230511 nightly (Official) OTA and everything is fine. It has the May 2023 security patch.

I wish I could get my €800 back to order a Pixel Fold🍷

I have no experience with a Surface Pro (and very little with Win 11), but Windows has always been a bit finicky with fastboot and adb (or, rather, properly connecting with the phone you are using them on. If you have a USB2 hub around, I would try that, USB2 often works better than USB3. Also try different ports, if the Surface has more than one, and different cables. I assume you enabled Developer Options for Android on your Pro1x and then turned on debug? I gave up on using my Windows 10 laptop for this and now use an old Thinkpad X230 running Manjaro Linux and a USB 2.0 Hub atta

The waydroid crash should be fixed by this: diff --git a/drivers/android/binderfs.c b/drivers/android/binderfs.c index 14a4bef358cd..3fd7cf48c39e 100644 --- a/drivers/android/binderfs.c +++ b/drivers/android/binderfs.c @@ -448,6 +448,7 @@ static int binderfs_binder_ctl_create(struct super_block *sb) inode->i_uid = info->root_uid; inode->i_gid = info->root_gid; + refcount_set(&device->ref, 1); device->binderfs_inode = inode; device->miscdev.minor = minor; The edl reboot and pstore console is more complicated and I need to

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

No, at least I don't.

Hi, after many tries I was finally able to bypass the edl panic reboot and enable th psram console. If you are interested in details, let me know, but right now I am not even sure which of my changes are necessary for this. Anyway I have the panic log from the waydroid crash, see the attached file. And now debug what is happenning... waydroid_crash.log

@HookThanks for the clarity, much appreciated, I'll have a play. Edit: That went well, first impressions it looks nice and smooth. Thank you Developers, Community, FxTec.

Hi All, So I have finally made some time to expand the /home storage on my Pro1X. Piggz gave me the instructions on discord some weeks ago (and echoed here a few posts above), but they were suitably vague. I will share what I did, though it may or may not be wise to do the same. I bumbled my way through, not carefully considered my way through. EDIT: I should have noted that this will delete all your /home, so back up anything of importance. On the SFOS install i ran as devel-su "resize2fs /dev/sda13" as per @GoaSkin instructions here. I had to replace the stock recovery

The installation procedure of SFOS creates a filesystem that matches the size of the 128GB version of the Pro1X. With a few quirks after the installation, it is possible to expand the filesystem if you have the 256GB version. For this, open a shell, become root and execute the following command: resize2fs /dev/sda13 Because the partition already ends at the last sector of the disk and just the filesystem does not use the full partition size, it is easy to change this even on a running system. The size of the user home folders still remain at 80GB and I don't recommend to chang