Probably the exposure notification is enabled by default in 0.2.13
I remember this post, just in case anyone want to remove microg
Probably the exposure notification is enabled by default in 0.2.13
I remember this post, just in case anyone want to remove microg
And I remember the fact that an enabled Exposure Notification only happens if one actively installs an app which utilises this feature and explicitly enables the feature.
Now ask yourself: can’t this be part of a unbelievable sophisticated conspiracy? Who says the switch wasn’t simply removed to fool us all?
“Probably” is too vague for me. I attach importance to concrete “knowledge”.
.
This “fact” is not my personal experience. In GmsCore v0.2.12.203315 the option ‘Exposure Notifications’ is displayed by default and looks at ‘OFF’ by default. Several tests on different devices have shown this.
For all installations without exception the “Exposure Notifications” were set to “Off” by default. Only when an application explicitly asked for “Turn on Exposure Notifications” and confirmed with Tap on the button “Turn on”, the activation took place. [Source]
An example of several:
.
I don’t ask this question because I don’t have any conspiracy theories.
Things go well as long as everything goes well, but then at a certain point things suddenly change and nobody expected it…
So I wouldn’t be so sure that maybe one day some pieces of software, now harmless or inactive, can be used for other purposes…
Anyway, as we say here in Italy, who will live will see (chi vivrà vedrà)
Ciao
Sometimes I come to the conclusion that people who tell me that my attempts to be ironic are often not understandable are right.
Its off and you cant turn it on unless an app has requested this feature. After install of a Covid app the switch can be toggled.
Hi @andrelam, I’m familiar with the functionality of microG GmsCore with Exposure Notifications API. I’ve demonstrated it several times in the near past here in the forum.
The crux is this: On my device with microG version GmsCore 0.2.13.203915 does not show the option ‘Exposure Notifications’, no matter if ‘OFF’ or ‘ON’. The brand new UK NHS Covid-19 app version 3.10 (100) 100 from 05.11.2020 can be installed but not used.
Please also compare with image #1 in posting obove.
This may not be any help for you, but I can confirm that version of microG does include the ‘Exposure Notifications’ framework / API. I am running it under Lineage 17.1 with the latest NanoDroid (NanoDroid-23.0.1.20201029
) on a Sony Xperia XZ1 Compact (lilac). The version of microG is GmsCore 0.2.13.203915
- same as @SuzieQ’s, but the microG Settings page shows ‘Exposure Notifications’ under ‘Location modules’ as in @andrelam’s image.
I have installed the UK NHS Covid-19 app, version 3.10 (100), Date of release 09/2020, which runs, and the Contact Tracing function (which uses the Exposure Notifications) seems to be working.
So I think it’s not a problem with the microG version, but with maybe with how it is setup on your device. (And I know you know more about this than I do )
@petefoth, thank you for your statement. Your LOS 17.1 with microG is GmsCore 0.2.13.203915 installed via NanoDroid-23.0.1.20201029 is not the same as an unofficial /e/ OS with preinstalled microG GmsCore 0.2.13.203915. Optically almost identical “like an egg”, but internally different “like apple and pear”.
Another test with two different COVID-19 Apps on an Samsung Galaxy Tablet with unofficial /e/ OS ROM e-0.13-Q including microG GmsCore 0.2.13.203915 shows the same negative
result. Among other things I get the following message:
CAUSE: 3 Something went wrong. Your Covid-19 app is correctly installed, but the Covid-19 Exposure Notifications System is not available on your smartphone's operating system.
Up to now, running various Covid-19 apps under microG GmsCore v0.2.12.203315 was absolutely easy and without any obstacles. But now …?!
That must be the new /e/ “feature”
same issue as @SuzieQ overhere.
Fairphone3 with e 0.12-q-2020111084008-dev-FP3 and MicroG 0.2.13.203915-94
Exposure Notifications are just not there in MicroG settings
Thank you @screenager, your experience is extremely helpful to me.
Another test with microG is GmsCore 0.2.13.203915 on a third device shows a different result: the option ‘Exposure Notifications’ is displayed.
First I installed on a Xiaomi Redmi Note 4 “mido” this latest LOS-ROM: lineage-16.0-20201022-UNOFFICIAL-microG-mido including preinstalled microG GmsCore v0.2.12.203315 from the official LineageOS for microG website.
As Covid-19 app reference I use the German RKI Corona Warn App. It’s known for its proper functionality, its privacy friendliness (for this the Chaos Computer Club e. V. (CCC) has among others) and last but not least the German main developer of microG, Marvin Wißfeld, is interested in the app working with his microG system.
As a second test app I use UK NHS Covid-19 App to check the camera option “venue check-in” which does not work in all versions of microG GmsCore so far.
The installation of OS and Covid-19 apps was done as usual without any additional changes to the default settings.
Conclusions:
The option ‘Exposure Notifications’ is available in both microG versions: GmsCore v0.2.12.203315 + GmsCore 0.2.13.203915. Both Covid-19 apps work with both microG is GmsCore versions.
So I have to say that if you install the Covid-19 apps the same way on different /e/ OS and LOS, the results will be different.
On my two unofficial /e/ OS e-0.13-p [pʰeː]) + /e/ OS e-0.13-q [ kveː], the option ‘Exposure Notifications’ is not displayed and an activation was not possible with until now.
The current (16.11.2020) unofficial mido build from the official LineageOs-for-mircoG website works as described by other forum participants.
By the way, my question remains: Are there two different versions of the current microG GmsCore v0.2.13.203915 or how should I explain all this?
Well my screenshot is from /e/ 0.11 pie custom build, so they must have removed it in preperation for the final solution. I did not check this though.
@andrelam, it’s good for me to know that the ‘Exposure Notifications’ option worked on a previous /e/ 0.11 pie custom build - and now, one or two releases down the road, it doesn’t.
This process shows that the /e communication is once again more than sloppy and not timely. I’m not saying that other institutions do it better, but the /e/communication is not image-enhancing according to the philosophy laid down in the /e/manifesto. Talk is silver, sil/e/nce is gold/e/n.
I thought someone mentioned somewhere (sorry for the vagueness) that with the update to 0.13 an app will appear in the app store which enables the switch to toggle on the API in the settings. This switch however will only be visible/switchable once a covid-app is installed. The version 0.13 shall be released within the next week (if not further delayed).
I seemed to remember the same thing … here it is:
Thanks, @harvey186! We got our FF3+'es just because of the changed Exposure Notification Express spec that allows the government to enable tracing by submitting config information (https://www.xda-developers.com/google-apple-exposure-notifications-express-covid-19-contact-tracing/).
I am concerned about this. I just want to be able to decide on my own if the government traces my contacts or not.
Could somebody please tell me how we can avoid getting any Exposure Notification API Express implementation on the phones? Where would I find the source code so I could write something that “implements” the API by logging stuff to /dev/null?
I still have the question:
Is there any update on the Timeline? So far, the APK has not been made available, or have I missed something?
Still waiting to revert back to /e/ but I am starting to worry that the implemntation has been given up altogether.