We’re thrilled to announce that the Shift8 — the latest modular and privacy-focused smartphone from Shift — is now in stock in the iodé Shop. The Shift8 ships immediately — no more waiting — so you can experience the future of sustainable, privacy-respecting smartphones today.
Read more in our announcement. Users already owning a Shift8 otter can install using our graphical installer or download the builds for manual install here.
These are great news! I was able to imstall iodé in my 8.1 and to relock the Bootloader 
I’m now looking forward for a lifetime family subscription. Or maybe a monthly one, didn’t decide yet.
What I’d like to know as the first apps unfortunately require a biometric factor: What is the issue with the fingerprint sensor? Do you think that it will be supported in the future? Is there any rough ETA? Will it be supported by an update or is reinstallation through factory reset necessary? If I were better at coding, I’d pleased to support you but as I’m the worst developer in the world, my contribution is only financial and testing/asking for features 
The fingerprint sensor effectively does not work yet. We may have good hope that it will be supported in the future, but cannot tell more.
Thanks for your answer. I purchased a premium family subscription today to support your project and hope for a fast implementation of the fingerprint sensor. 
Any chance to get the “custom key” implemented as well? I installed the SHIFT-Actions App from their F-Droid Repo an can configure the key but it none of the actions get triggered by a key press.
Once again: Thanks for your work, keep on coding against mass surveillance and big tech! 
Is there an issue or ticket I may follow to be imformed and probably to help testing?
Do you mean for the fingerprint sensor and “shift actions app”?
Yes. Maybe on your Gitlab instance vor so.
Here is the issue I just created you check on:
I created this issue for the “custom key” issue:
Just another hint from my side: Currently the OEM unlock switch under Developer Tools is clickable, so one could accidentally disable OEM unlock and brick one’s device. I’d suggest thinking about to gray out that option in iodé to prevent that.
That would not brick a current install, instead it would just prevent fastboot flashing unlock from succeeding if you want to later unlock it again. So I think all is OK here.
Thanks for the clarification. So there is no risk in disabling OEM unlock accidentally? I’m not an expert but until today I thought if I disable OEM unlock, the bootloader will verify the boot signature of i the OS installed and deny boot if it doesn’t match the vendor defined value.
Do you know if there is any benefit in disabling OEM unlock after installation of iodé?
No, as far as I know it simply enables / disables the ability to use the fastboot flashing unlock command. On my Pixel 7 Pro my bootloader is unlocked and I have OEM unlocking disabled in Developer Options (meaning it doesn’t allow the bootloader to be unlocked). No problems whatsoever.