The ‘Dutch Coronamelder’ is probably extremely close to the system, i.e. it has been programmed to G’'gle Services & Co. The Dutch authorities are responsible for this in the first instance.
MicroG’s ‘Exposure Notification API’ replica in ‘microG Services Core version 0.2.12.203315’ is, according to my tests on various Android devices, not able to provide the desired compatibility.
.
The custom ROM from PixelExperience, known for its almost perfect replica of the G’’ Pixel Stock Android ROM with all G’'-components, is the only custom ROM I know of that the Dutch Coronamelder works with. (see screenshot above)
Right, but then I’m pretty sure it’s not the only ROM working with the Coronamelder. I’m guessing any rom on which the latest version of the Play Services is installed would have a working Coronamelder.
Well, yeah it’s ironic - and irony tends to be pretty funny (;
However, it doesn’t work with Coronamelder, but from what I’ve read on the forum Microg is compatible with the apps of the UK and Belgium. So some people may still benefit from implementation.
.
On my Galaxy S7 with /e/ OS e-0.12-o-2020093076269-dev-herolte and subsequently integrated microG Services Core version 0.2.12.203315 several Corona Warn Apps work. For example from Unitied Kingdom: NHS Covid-19
Yes, the German Corona Warn App should work as well. How strange, Dutch authorities had it developed this way. Goes to show, how important it was that the German CCC did effective advocacy so the German version of the app was developed completely FOSS (apart from the framework, of course).
Yeah interesting. I’ve sent an email about this to Bits of Freedom - a privacy NGO. As far as I know they’ve had an advising role in regards to development.
Out of curiosity: do these apps interact with one another? Would a German app contact a Dutch app? In that case one could just install one of the apps that does work.
We can’t. @SuzieQ has found a workaround that doesn’t work on a Fairphone 3 though.
That is where this dicussion originates. To use the current version of microG we are dependent on the /e/ team, however they found it advisable, to not just update microG but to find a so far secret solution that will only work starting the “end of october”.
I will be honest. It is a little dissapointing, after having waited for a month, with constant refreshing, thinking the update in question will come at any moment, just to be told that an API that I need for my work and where there is very little reason to belive it doing anything more that it is supposed to is delayed another month.
I undestand that the team wants to make everyone happy, however I for one am almost forced to find an alternative for now. Fortunately there is a working Lineage rom for FP3. Guess I will use it as a temporary solution, even though I am really not looking forward to setting up my entiere phone from scratch.
I am pretty sure that some folks here face a similar situation, and I do feel that /e/ has chosen the wrong path here, putting an in my opinion almost supersicious fear (which in latter comments I found increasingly paired with a complete denyal of COVID and it’s dangers) over the essential need of many. But it is not my choice to make.
For me, this delay is a goodbye. Hopefully a temporary one.
@SuzieQ What @DarthDavester said, I have a FP3 which apparantly does not allow the solution you mentioned under your provided link
Maybe I could have stated my device earlier though
A little update about Coronamelder: it does in fact work with microg, but one needs to turn on the location services. However, this is not indicated in the app so I had no clue. Nonetheless: good to know it works. Just not a big fan of always having my location services on.
To avoid any confusion: I am no longer running /e/ but Lineage 17.1 with microg installed. So I have got the latest version of microg but not via an /e/ update.
