That's not good to hear....

Thanks for the info.

Edit: DOes anyone have a working link to the AlienDalvik RPM for cm12.1? Just started editing the Wiki page and couldn't find a working link for the AD rpm...

Here it is!

@mautz news on the wiki page?
Unfortunately after a drop my Nexus 5 has problems with mobile networks, I guess the antenna detached from the main board. I'm switching to a Jolla phone for a while, thinking if it's worth to buy an XA2.

I'm still on it, but i am very busy at the moment.

I like the XA2 except for the size, Jolla Phone and Nexus5 were perfect for me.

That's also my concern, I've also considered the X Compact but maybe it's better to go directly to a more recent model and hope it'll last long enough, my Nexus 5 lasted 3 years and a half "only".

I am not sure why the XA2 is considered as a much larger phone than the Nexus 5. I just have compared them together and the XA2 is only a few millimeters taller than the Nexus 5. That is not a big difference.
The pro for the XA2 is the newer aliendalvik that helps to substitute apps with android ones where there is no native sailfish version.
The pro for the Nexus 5 is the multiboot option which is priceless!

However, if you need to use any video calling or banking apps than I suggest the XA2.

On My Nexus 5 (because of the old aliendalvik) more and more android apps stopped/stops working. Use the websites instead of apps you'd say. Well, the native browser doesn't work well with many websites and the android version of Firefox crashes too often. (I have tried many other browser but some of them do not even install because of the old aliendalvik, others just crash often.)
This is how I see and how I experienced it.

@mautz
I hope you are doing well.

Recently I am getting errors when I try to install/update something from Storeman. An example: I have checked your repo (http://repo.merproject.org/obs/home:...atest/armv7hl/) and realized there was no "droid-hal-version-hammerhead-0.0.1+master.20191129005653.28304d5-1.2.4.jolla.armv7hl.rpm" however there is a newer version "droid-hal-version-hammerhead-0.0.1+master.20191129005653.28304d5-1.2.8.jolla.armv7hl.rpm" what was generated on 28-May-2020.
Do you remember why the 1.2.4 was changed to 1.2.8?

(When I disabled the "adaptation-community-hammerhead ... http://repo.merproject.org/obs/home:/mautz:/cm12.1/sailfishos_3.2.1.20_latest/" repo, the error was solved and I managed to install/upgrade packages from Storeman.)

I updated some packages for 3.3, this is why there is a newer droid-hal.

Today 3.3.0.16 built all packages fine, so if someone is willing to test it, here are the repos for cm12.1:

Is it normal for first boot to take over an hour? I installed 3.3.0.16 from page 79, installing the CM12.1 base then SFOS in TWRP. Initially I thought I screwed something up, so I tried again... and again... and again. Eventually I just left it and it finally booted after an hour and a half. I then selected my language and it got to the boot screen then went black. It took about 45 minutes after that point before I got impatient and hard reset it. It hasn't booted since.

EDIT: I have tried 3.3.0.16, 3.2.1.20, 3.2.0.12, and 2.0.4.13. Only 2.0.4.13 has worked (it booted instantly into the language screen, runs great), and OTAing from that version results in the same insanely long boot. I have also tried 4 other CM12.1 zips, one newer than the one in the first post, 3 older. All boot fine without Sailfish installed.

EDIT 2: I have now tried 3 versions of TWRP (3.0.2-0, 3.0.0-0, and 2.8.5.0), and some CWM and Philz Touch recoveries I had saved somewhere. Absolutely no difference.

Do you guys have any idea what could be the issue? Am I just SOL?

No, a fresh install normally should boot into the initial setup within a few minutes.
Please double-check the following:

• Use TWRP 2.8.7. This is well known and works fine.
• Only use the CM12.1 image which is available to download from the first post in this topic.
  Both the TWRP and CM12.1 base are available here. (You can experiment with TWRP versions, but no guarantee that they work while version 2.8.7 will for sure.)

OTA from 2.0.4.13 to any newer version I am not sure that works.
When you upgraded, did you follow the instruction from here?

(I just have upgraded (OTA) my 3.2.1.20 installation to 3.3.016 following this instruction and using the new repos from this post. So far seemingly everything works.)