@HenkK if you are looking for a response from /e/ developers … ‘we changed line 46 on this code file or the plan is to be ‘perfect’ on day xx of xxx month’… then we do not have such detailed documentation nor a perfect plan with precise dates . It is a small team and most of the time the team members are neck deep in bug fixes and enhancement requests.
In case we are forgetting, the code base we use is from google- AOSP. Which Lineage took up and then we forked from them.
We have de-googled a lot of it. Do not ask exactly which lines because as I mentioned it is simply not possible to track that now as it is not documented…
Getting into an argument or discussing all this again or expect new answers that are beyond what has already been given here is not going to happen because as I mentioned the dev team is already running late on a number of issues for e.g. closing out 600 bugs (numbers as of today), releasing an easy installer, Upgrading the devices still stuck on nougat or oreo to the Pie build, coming out with a system with different levels of profiles and a FOSS only version of the ROM, change the name from /e/ to something more easier, …the list is long and I have not even mention half the issues we are tackling
What will be easier for you is using your experience you can run tools / apps which check the network connectivity or run through the code and let us know if the /e/OS still leaks data.
The entire code base is available on Gitlab.
Find out where we went wrong or what is not done properly and let us know by raising issues on the Gitlab and we will be happy to fix it.