Hasn’t this always been the case in FOSS, I mean look at Stallman.
I just like to let the purists do their thing and if they produce something I like, I’ll use it. Otherwise I’m not getting involved in their infighting. There are only so many hours in a day, I have better (happier) things to do than argue over whose project is really true (to use metal terminology ).
$ host supl.vodafone.com
supl.vodafone.com is an alias for supl.google.com.
supl.google.com has address 64.233.177.192
supl.google.com has IPv6 address 2607:f8b0:4002:c02::c0
iodeOS only included the no IMEI to SUPL patch after I prodded them in 2020/11:
re: dialer
That is a Lineage feature afair and it is default disabled since 2018.
https://review.lineageos.org/q/gdpr
re: ntp
The proper endpoint should be 2.android.pool.ntp.org, as it supports IPv6 and has the correct vendor prefix.
Per their site:
Do not use the standard pool.ntp.org names as a default configuration in your system.
re: captive portal
So instead of blending in with every single other Android device for captive portal checks, you both disclose your IP to a third party (granted a reputable one) and also disclose to any adversary on your local network that you are not running “normal” software.
DivestOS instead leaves the default, but adds an option in Settings app to disable.
I, for my self, have decided not to test it for the time being. i am more than satisfied with my iodé
I’ll wait and see
There are still too many bugs in the A12 and the optics of A12 is also not mine
However, I’ll download it and analyze their installation process.
In the test builds, the installation must be done manually. The installer is not available yet.
The bootloader has to be locked manually with fastboot.
I’m curious to see how many will use it to brick their FP4…
But will also show new findings whether the Re-Lock problem on the FP4 also shows with calyxOS further. As with the other custom ROMs
Interesting that it works without locking the bootloader.
Have you had a look into the flashing script? After about 50 posts scattered over 12 threads regarding FP4 not booting anymore, I lost track. But it seems to me that you have understood it. Is the script doing the correct things to not do any harm to the phone?
None of the available custom ROMs (or the factory images for that matter) have code in their install scripts to lock the bootloader. They could, but you’d always have to press a button on the device to confirm it, as @Volker said.
You wouldn’t want that functionality in your script anyway, way to many possibilities for things to go sideways… (as we all have witnessed )
Locking the bootloader isn’t a requirement to run Calyx, it’s an additional feature.
I’m going to install Magisk next, so I have no intention of locking my bootloader.
My reasoning for running Calyx is easy access to microG preinstalled, a nice built in firewall (haven’t played with it much), almost no preinstalled apps (compared to /e/) and access to the newest Android release (I like my distributions rolling ).
Interesting, I thought for CalyxOS it was a requirement. If I were going to install it and if I wanted to relock, what would be the steps to not brick the device?
The installation instructions say
Re-lock the bootloader using fastboot flashing lock
Is that correct for the FP4? Would I have to lock critical, unlock critical before or do some other magic?
The install instructions don’t mention fastboot flashing unlock_critical, but I had them unlocked already, so I can’t say.
That is correct. Those commands are the same for every ROM.
I can’t tell you. Maybe fastboot flash avb_custom_key avb_custom_key.img as iode and Calyx have started using makes this less likely.
I for one am waiting for Fairphone to investigate all the bricked devices with vanilla FPOS first, not gonna touch locking the bootloader before there is some clarification.
Edit: From what I can tell, compared to the factory install script, Calyx are flashing some of the partitions through sideloading in fastbootd maybe that makes unlocking critical partitions not necessary.
But someone else will have to try, I already installed Calyx several times (to look for errors) and I’m not going to touch fastboot flashing lock_critical either, any command involving fastboot and “lock” doesn’t feel right
I have an “old” Pix5 here. My old business phone.
I use this with original OS for my Banking 2FA apps.
I installed calyxOS on that for testing. And oops, some of the apps don’t work. I knew that…
But anyhow, I wanted to test calyxOS and so I did it.
Now, back to Stock because of my 2FA apps.
Result and lessons learned.
Nothing different as on original A12, and again I don’t like it
Enough that I have to life with it on my stock Pix5. But i switch this one on only once a month or so…
The End
I will stay on iodé on my FP4. I LOVE it. I leave it. I don’t touch it
Pix5 keeps on stock with as many goolag apps deactivated and deinstalled as possible.
Just for 2FA
But fuck, this little road-trip this afternoon has meant that i have to set the whole thing up again
That takes longer than the little trip itself
I follow your lead, Sir. Thanks for all the info on IodeOS here and thanks for making sure I am not sacrificing all the work I had to customize it to my demands just to check out CalyxOS. Highly appreciated!