Even claude er bij ingeschakeld. Oorzaak zit hem (lijkt het) in de net policy:L0g0ff schreef op woensdag 16 september 2026 @ 09:44:
[...]
Nee liever geen root. Ik zou het liefst al mijn devices van iedereen hier thuis omzetten naar /e/os.
Maar ik heb nu een logcat | grep -i download draaien via adb shell en wat denk je. Het werkt ineens wel. Heel bijzonder dit.09-16 09:42:28.429 5011 32004 D DownloadManager: [3348] Starting 09-16 09:42:28.443 5011 32005 D DownloadManager: [3349] Starting 09-16 09:42:28.463 5011 32013 D DownloadManager: [3350] Starting 09-16 09:42:28.475 5011 32015 D DownloadManager: [3351] Starting 09-16 09:42:28.673 3458 3458 I NotificationListener: received notification posted event - com.android.providers.downloads#UserHandle{0},category=-1 09-16 09:42:28.678 3458 3458 I NotificationListener: received notification posted event - com.android.providers.downloads#UserHandle{0},category=-1 09-16 09:42:28.689 3458 3458 I NotificationListener: received notification posted event - com.android.providers.downloads#UserHandle{0},category=-1 09-16 09:42:28.692 3458 3458 I NotificationListener: received notification posted event - com.android.providers.downloads#UserHandle{0},category=-1 09-16 09:42:28.710 3458 3458 I NotificationListener: received <knip> notification posted event - com.android.providers.downloads#UserHandle{0},category=-1 09-16 09:42:44.755 5011 32004 D DownloadManager: [3348] Finished with status SUCCESS 09-16 09:42:44.779 3458 3458 I NotificationListener: received notification removed event - com.android.providers.downloads#UserHandle{0},category=-1 09-16 09:42:44.780 3458 3458 I NotificationListener: received notification removed event - com.android.providers.downloads#UserHandle{0},category=-1 09-16 09:42:46.370 5011 5062 V DownloadManager: Deleting /data/data/com.android.providers.downloads/cache/downloadfile.bin via provider delete 09-16 09:42:46.379 4676 29933 W ModernMediaScanner: Failed to visit /data/data/com.android.providers.downloads/cache/downloadfile.bin: java.nio.file.NoSuchFileException: /data/data/com.android.providers.downloads/cache/downloadfile.binedit:ok root cause gevonden: Het zit hem ergens in de DNS: play.googleapis.com
even de terminal output wat topic vriendelijker gemaakt.code:Wat vreemd is want dit gaat prima
1 2 3 4 5 6 7 8 9 10 11 12 13 09-16 10:35:16.551 5011 9669 D DownloadManager: [3406] Starting 09-16 10:35:16.558 5011 9670 D DownloadManager: [3405] Starting 09-16 10:35:16.565 5011 9671 D DownloadManager: [3407] Starting 09-16 10:35:16.571 5011 9672 D DownloadManager: [3408] Starting 09-16 10:35:16.574 5011 9670 W DownloadManager: [3405] Stop requested with status HTTP_DATA_ERROR: Unable to resolve host "play.googleapis.com": No address associated with hostname 09-16 10:35:16.574 5011 9669 W DownloadManager: [3406] Stop requested with status HTTP_DATA_ERROR: Unable to resolve host "play.googleapis.com": No address associated with hostname 09-16 10:35:16.575 5011 9670 D DownloadManager: [3405] Finished with status WAITING_TO_RETRY 09-16 10:35:16.575 5011 9669 D DownloadManager: [3406] Finished with status WAITING_TO_RETRY 09-16 10:35:16.576 5011 9671 W DownloadManager: [3407] Stop requested with status HTTP_DATA_ERROR: Unable to resolve host "play.googleapis.com": No address associated with hostname 09-16 10:35:16.577 5011 9671 D DownloadManager: [3407] Finished with status WAITING_TO_RETRY 09-16 10:35:16.579 5011 9670 D DownloadManager: [3405] rescheduling the job id:3405 09-16 10:35:16.579 5011 9672 W DownloadManager: [3408] Stop requested with status HTTP_DATA_ERROR: Unable to resolve host "play.googleapis.com": No address associated with hostname 09-16 10:35:16.580 5011 9672 D DownloadManager: [3408] Finished with status WAITING_TO_RETRYcode:
1 2 3 4 5 6 7 8 9 thomas@kompass:~$ adb shell FP6:/ $ ping play.googleapis.com PING play.googleapis.com (172.217.118.4) 56(84) bytes of data. 64 bytes from 172.217.118.4: icmp_seq=1 ttl=119 time=12.1 ms 64 bytes from 172.217.118.4: icmp_seq=2 ttl=119 time=33.5 ms ^C --- play.googleapis.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 12.114/22.824/33.535/10.711 ms
Ik ga nu even de batterij optimalisatie uitschakelen van app lounge en kijken of het dan wel blijft werken.Bingo — regel matcht exact het tijdstip van de DNS-fout:code:Om 10:32:10.988 wordt UID 10067 (downloadprovider) door netd geblokkeerd tijdens een standby-bucket transitie (BTOP = "background-top" overgang). 66ms later, om 10:32:11.054, faalt de DNS-resolutie. Dat is geen DNS-probleem — dat is de firewall die het proces heel even blokkeert terwijl de app-standby-bucket wisselt (systeem plaatst 10067 steeds in "LAST"-bucket, de strengste standby-klasse voor zelden gebruikte apps), en de resolver interpreteert de geblokkeerde socket als "no address".
1 2026-09-16T10:32:10:988 - 10067:BTOP:----F--T:111692
Policy staat correct op ALLOW_METERED_BACKGROUND, maar dat voorkomt niet de korte block tijdens de bucket-switch zelf — dat is een race in netd, klassiek App Standby-gedrag.
Fix: zet App Lounge (foundation.e.apps, niet de downloadprovider zelf) volledig vrij van App Standby:code:of blijvend via UI: Instellingen → Apps → App Lounge → Batterij → Niet beperkt / onbeperkt (niet alleen "toegestaan", maar de hoogste vrijstelling — dit haalt 'm uit de standby-bucket-rotatie).
1 dumpsys usagestats set-standby-bucket foundation.e.apps active
Fijn al die verbose info
:strip_exif()/f/image/aaEXebQ3pKHdzwOLWWY2s5K0.png?f=user_large)