Will /e/ include Corona exposure notification API and if so: when?

Great now my email is being spammed again with people spreading FUD against this well documented API insisting it ruins their privacy despite all the research and papers and the ability to read the microG implementation to see it does not upload any data anywhere.

And that all despite the OP explicitly asking to not have this whole discussion again.

I’m muting this topic just… THE API DOES NOTHING UNLESS YOU INSTALL AN APP THAT USES IT AND YOU CAN DISABLE IT IN MICROG. The “concerns” of you FUD-spreaders have already been taken care of, now just let us who want to have this very well designed anonymous way of knowing if you were near someone with COVID have it. Several people I know died to this horrible disease, I don’t care if you’re not afraid or whatever, let those who want it protect ourselves against it.

5 Likes

I’ve been waiting for this one.

No, what you have done is sharing a link that describes a well known weakness of the API for which 1. it has to be turned on and 2. that doesn’t even work on all phones and 3. You have to trace breadcrumbs by being in Bluetooth range of your victim.

The fact they found this weakness and no other, is actually reassuring. The code HAS been scrutinized and THIS is what they found.

So no, nice try, but the burden of proof is on you. I fact shifting the burden of proof is a logical fallacy that is often used by religious people. “Well, show us there is NO god”. No. If you claim something outlandish and against all prior information, if you say, an inactive bunch of lines of code (it can be turned off) are dangerous to privacy, then you need to show, your claim is true. And you haven’t done that. Not for the Google/Apple API and much less for the microG implementation. I did learn more about Google from your sources. I did not learn more about the API.

I am with @Hawthorn here. There were possibilities, it wasn’t a priority and this does not shine a good light. At least for most people, who just want to use these apps to protect themselves and others.

4 Likes

I’d already claimed a ‘procès d’intention’. I’m not the only one wich doubt with gglle/pple spontaneous claim about ‘Privacy’ nor ‘Security’. For example:

I’m not engineer, I read here and there, and definitively I don’t trust in gg’s leniency.

2 Likes

Don’t worry, I fixed it. Installed Lineage from here. Works fine on FP3, and the “with-MicroG” option lets you update to the most recent version with no troubles. UK Covid app works fine. Farewell my libertarian /e/ friends, but I’ll leave you with this. Even with a “dumb phone”, no apps, no google installed. If it has a sim card and a battery in it you can be identified and geo-located with simple cell tower triangulation, and also that “My freedom” always without fail means restricting someone else’s freedom.

2 Likes

Tested it with MicroG most recent version in /e/, Lineage OS, Fairphone Open, and it doesn’t work. MicroG cannot find the App and the App cannot find MicroG. Left Android for Linux mobile today, essential applications don’t work in free Android versions without G00gl Goolag, so why Android? Makes no sense to use Android if you want privacy.
Screenshot at 2020-10-02 22-06-33

I was able to upgrade to the current version microG Services Core version 0.2.12.203315 by manually. So now StopCovid France also works on a /e/ OS 9-Pie ROM.

SwissCovid Corona-Warning-App works with /e/ OS e-0.12-o and microG Services Core 0.2.12.203315

Stopp Corona Austria works with microG Services Core version 0.2.12.203315

(UK) NHS Covid-19 app works with microG Services Core version 0.2.12.203315.

Coronalert - Belgium App version 1.6.0.78 from 24.09.2020 works fine on my device configuration.

German RKI Corona Warn App works with microG Services Core version 0.2.12.203315.

2 Likes

Which phone/OS?
What’s your experience so far?

This sound great - please let me know, how did you upgrade microG manually.

Hi @frank.bxl,
I gather from your “About me” that you describe themselves as technically adept. So it will not be difficult for you to upgrade manually.

I could not test my workaround on a Fairphone 3. Which devices should the microG Upgarde be for?

It’s for the FP3 - and it’s not rooted (for banking apps sake)

If anybody finds a way to upgrade it manually on the FP3, I’d happily switch back to /e/ from stock ROM, which I am (unhappily) using at the moment.

@frank.bxl,
@juri.gagarin,
to verify my workaround I will release the first version of e-0.9-p-20200530-UNOFFICIAL-hero2lte and write down another workaround for me step by step. If it works as before, I invite you to try it as well. Save your most important data already once. Safety first …

2 Likes

Thanks. Is it relevant that FP3 is an A/B device or is your approach independent of this?

I don’t store much personal information on stock ROM anyway, but thanks for the advice :wink:

No! Temporary rooting with MagisK is however necessary because the microG components are system apps.

1 Like

Well, I have unexpected difficulties with the build. The /e/Browser fails and the installation of microG Services Core as well.

hero2lte_harveybuild

hero2lte_harveybuild_microg

I will now try it again on another device with a different 9-pie build.

Hi …
@frank.bxl,
@juri.gagarin,
my microG-upgrade-method from yesterday I cannot verify today. I have tried three /e/ OS 9-pie ROM.

Only the NanoDroid method works on the Galaxy S5 ‘klte’ with the current build e-0.12-p-2020093076095-dev-klte just like here with the build e-0.11-p.
.
e012p2020093076095devklte_m1
e012p2020093076095devklte_m2
e012p2020093076095devklte_m3
e012p2020093076095devklte_m4

Belgian Coronalert App works on different Android phones, but as other /e/ users have noticed, ‘NanoDroid method’ doesn’t work with the /e/ OS FP3.

2 Likes

I did it flashing the Nanodroid microg .zip file from TWRP, and deleting cache/dalvik. It seem to work ok for me until now. Do you know the Nanodroid microg .zip package?

Thanks a lot for your effort.
I guess I will have to stick with stock ROM for the time being :frowning:

Another successful test …

  • without rooting the device
  • without NanoDroid patch
  • only tool: TWRP Recovery

and a WLAN / Wifi online connection to the WWW is required. And of course some time to complete the individual steps.

Starting point is /e/ OS 9-Pie TestROM for Galaxy S4 ‘jfltexx’: e-0.11-p-2020082569744-test-jfltexx by eOS

e-0.11-p-2020082569744-test-jfltexx_by_eOS
.

Dutch Coronamelder

"The apps is active"

Dutch_Coronamelder
.

Dutch Coronamelder | UK NHS Covid-19 | Belgian Coronalert

The apps are active.

NHS_Coronamelder_Coronalert

Actually the update is easy to do if you know how. There are many single steps necessary, but no special Android or technical knowledge is required. The phone is not rooted (Magisk), no external tool (NanaDroid) is used - only TWRP Recovery is in use.

See also:

1 Like