Unfortunately, as I still type, there’s no liberated deblobbed ROM. /e/OS, like every custom AOSP fork, is dependent on leaks &/manufacturer provided ROMs.
After Google silos AOSP ROMs, all forks will not be able to acquire updates downstream.
But if the forks are able to tear out the gapps, shouldn’t this “cert” check go with it? I understand that the check would have to be in the installer app. Even if it’s a part of launching mechanism, it should also be possible to tear it out
Linux Phones, are not alternatives.
I’m sorry, I don’t follow. AFAIK GRUB did not need to get some blessing to get installed on UEFI. So Linux Phones should be free of big tech gatekeeping. This exchange we are having here is on technology community, not privacy (where I would get your point)
WDYM?
The way I understand what /e/OS is, it sounds like it should be able to not include this check
Unfortunately, as I still type, there’s no liberated deblobbed ROM. /e/OS, like every custom AOSP fork, is dependent on leaks &/manufacturer provided ROMs. After Google silos AOSP ROMs, all forks will not be able to acquire updates downstream.
Linux Phones, are not alternatives.
Looks like we need dedicated hardware. /e is phones, graphene phones etc then.
But if the forks are able to tear out the gapps, shouldn’t this “cert” check go with it? I understand that the check would have to be in the installer app. Even if it’s a part of launching mechanism, it should also be possible to tear it out
I’m sorry, I don’t follow. AFAIK GRUB did not need to get some blessing to get installed on UEFI. So Linux Phones should be free of big tech gatekeeping. This exchange we are having here is on technology community, not privacy (where I would get your point)