@moose in case you have removed /e/ and put in lineage, please could you check for the same scenario and share the logsā¦ sorry for troubling you but it will be a great help to us in debugging the issue. It will be helpful to compare the behavior in the two OS and understand what is wrong and where.
Sorry @Manoj, I didnāt see your answer in time. LineageOS is on the phone by now. When AFWall+ and AdAway are in place and the scenario is to be compared I will share the logs. Iād be glad to see /e/ succeed.
I try to avoid the terminal where possible. Thats why I posted the log that was produced by Logcat Reader in the first place. Shall I do it same way again or the the way that you described? Iām not aware if the output of both is comparable.
Do not mind. I aknowledge that you are but a few people with a heavy workload and me too could have put in an other way.
2 Likes
@moose please share the logs for LineageOS in the way you generated it for /e/ . We wanted to compare the logs from the two OS and debug the issue. Thanks for your time and support.
Checking the IP addresses from your logs (see summary below), application āOnePlusPocketModeā is the one connecting to Google. Since this is a device-specific App we anticipate the problem is indeed with LineageOS and you will see the same running LineageOS itselfā¦
Anyhow good catch and thanks for reporting this issue, we definitely want to hear about such findings, and get those resolved. Topic title updated to indicate issue is applicable to One Plus phones.
OneplusPocketMode
108.177.126.96 Google LLC google.com
172.217.17.68 Google LLC google.com
185.207.104.70 netcup GmbH netcup.eu
172.217.17.38 Google LLC google.com
74.125.143.94 Google LLC google.com
173.212.196.208 Contabo GmbH Contabo.com
172.217.17.36 Google LLC google.com
1 Like
Hi @Patrick, good to see how you look into it!
Your answer by the way made me aware of a problem with this here page. I can see only the 7 lines of the ip addresses that concern PocketMode. In the mail receceived, there are much more (see screenshots). Iāve tried Firefox, Falkon and Epiphany, but its all the same, your text seem to be truncated when viewed here. This might cause misunderstandings ā¦
No mystery there, I updated my post to focus IP analysis to the problem statement you raised, now the email was already sent with original post content including all. No bug on that one 
If anyone here notices that Google tries to boycot the development of an alternative, you could consider to report this to Margarethe Vestager of the EU Antitrust Commission. Or to an EU MP. Twitter: @vestager
MP: @UGambini
It is very important to let the European Commission know what Google is doing.
1 Like
Issue is resolved - it is possible to use both 01. and 0.2 with all hardware working now
1 Like
Thank you very much. This is an encouraging progress. I will keep watching the development, because my main problem is not yet resolved. Furthermore I am waiting for /e/s step to Oreo for the cheesburger too, as I hope that I then will be able to easily switch back (and forth if necessary) from Lineage-microG 15.1 to /e/. That is why installed LineageOS for microG in the first place. I do not need and use microG.
Does /e/ use the same signing keys as LineageOS for microG ??
Hmm. Have you visited the issue with your my main problem recently?
It is closed and resolved (see my latest comment there that references another issue with the solution). Basically the problem is firmware incompatibility. For /e/ 0.1 you need a certain version (linked there) and for /e/ 0.2 you need the latest version of firmware (lined out in the other issue in the latest comment as well).
BTW, there is /e/ 0.2 unoffical available including OTA support: Oneplus 5 (cheeseburger) /e/ 0.2 unofficial now available (Bonus: receives OTA updates)
How could /e/ sign with the keys of a different project? That would render the idea of signing useleses, wouldnāt it?
1 Like
Iāve visited that issue often, but I did not notice that it was closed. Even now that I knew and looked for it I did not find it beeing so. I had to make my browser search for it. I guess I was too much preoccupied by the idea, that the āclosedā badge was a label and to be found in the right sidebar with the other labels.
As to the signing keys: /e/ is based on LineageOs an uses microG. Thats what made me think its the same combination and therefore it might be the same signing keysā¦ 
So, if I understand that thing rightly, it will not be possible to do a so called dirty flash. This makes the change of course trickier for an unexperienced user like me. I feel insecure about backing up my data that canāt be backed up using TWRP. I tried that once with an other phone but did not succeed. So I will rather wait for an official version, hoping that I can stick to it.
In order to install a recent Lineage-microG update I had to flash firmware and modem 5.1.7. I think it would be a good thing if /e/ could attach its development to the actual firmware at a time, avoiding downgrades prior to installation. I fear downgrades are normally not intended or even expected and thus might more often cause issues than upgrades.
I personally donāt like Gitlabās way of issue tracking as well. For all other aspects it is quite a great tooling.
The idea of signing is to prove that the build is actually coming from legit sources / the orginal distributor/team and signing happens with a PRIVATE key that must not be shared.
You are right. Switching back and forth by dirty flashing āon top of incompatible dataā just like that is not possible due to this. You could theoretically build a custom data migration zip however that is a bit advanced and depends on the level of your expertise and adventurousness.
Regarding firmware: /e/ 0.2 requires the latest 5.1.7 firmware as well. It is just the older Nougat-based /e/ 0.1 that requires older firmware. This downgrade is indeed somethign that is not very desirable. BTW, if I were you I would used firmware from original sources only (support.oneplus.net) unless you know the person who upped the ZIP.
I would like to, but I can find there only a new ROM, not a separate firmware and radio zip-file. Do I miss something again?
If I had an account at /e/, could I use it to backup my data out of lineageOS, then install /e/ and finally recover my data from that account?
For App-configuration and -user data, you need to have a look into each App if they provide a backup&restore functionality and follow their steps.
I am not aware of a way to backup&restore system settings between different OSs.
Pictures, Music, Video, ā¦ files can be synced from Lineage OS to your /e/-drive account by using the Netcloud Sync App. After installing /e/ you can sync the data from your /e/-drive account back to your device.
An other choice would be to sync these files from your Lineage OS device to your local computer and syncing it later to your /e/-device.
1 Like
Which app did you use to see this ?
It is AFWall+. View log (switch to old view)
Same with even Moto G6. Disabled all google related services except google play services.
But apps (some of them) seems to take a route of accessing net going through play services or through āsystemā (donāt know why) as a network monitor shows - the inference seems to be at OS level of collecting data without setting any explicit permissionsā¦!!!