hosts: Entries break Waze app on Android

@timkgh thanks for pointing out that it does not happen right away. It took me awhile to reproduce, but changing the destination several times triggered it. Whitelisting only advil.waze.com seems to have resolved the issue for me. I’ve already made the change to my list in https://github.com/lightswitch05/hosts/commit/4de8da8b2478bfd74dac273410c8583bc53c3d94 - please let me know if you continue having troubles after using the updated list

This is unfortunate. I’ll move them to a different list later today.

For the record, there are still 2 entries left on the lightswitch05 list with waze.com domains:

0.0.0.0 ads-resources.waze.com
0.0.0.0 ads-resources-legacy.waze.com

I’ll re-open the issue if they turn out to cause problems.

@timkgh thanks for pointing out that it does not happen right away. It took me awhile to reproduce, but changing the destination several times triggered it. Whitelisting only advil.waze.com seems to have resolved the issue for me. I’ve already made the change to my list in lightswitch05/hosts@4de8da8 - please let me know if you continue having troubles after using the updated list

I am going to do some testing of my own and will report back what i find.

Moved to my aggressive list - which is not in this project - via commit https://github.com/lightswitch05/hosts/commit/74e6160c5f5f55a9af54760b0abfbe7c0cf98446 . It should be removed in the next release. Thanks for keeping track of this and trying different options

Thanks @timkgh. This is done, and is live and online in release 1.4.46.

Closing! Thanks everybody!

I contacted hosts@someonewhocares.org and it’s now removed from the list, if we could please refresh the list here too.

@timkgh the readme has hosts@someonewhocares.org as the best way to submit issues to that list maintainer

@lightswitch05 Thanks, didn’t realize row-advil didn’t come from your list. Reproducing it is the tricky part as it doesn’t happen right away, it takes a while to get into this state (I’m not even sure whether it’s time or some other trigger like POI that causes it), but once it does, the only way to recover is to restart Waze. I will try and whitelist row-advil.waze.com next but not sure when my next long drive is going to be. This has been happening for the past couple of months but driving just around town I blamed it on spotty cell reception and on a buggy Waze app not being able to recover from it, but now I’m pretty sure it’s the ad blocking it’s not happy with. When Waze shows “Searching network” other apps have no problems getting data.

@StevenBlack can we please keep this issue open until we figure out which entries are the problem? Maybe others will be able to test too and chime in. Thanks.

@timkgh row-advil.waze.com isn’t in my list. The only two waze domains in my list are ads-resources.waze.com and ads-resources-legacy.waze.com. Looks like row-advil.waze.com is included by someonewhocares.org. Since I’m not able to reproduce this, could you try whitelisting domains one-by-one on your side until you find the culprit? Like you said, it seems row-advil.waze.com might be the culprit. But thats outside of my control. If it ends up being either ads-resources.waze.com or row-advil.waze.com, then I am happy to remove them from my list. But I would rather have them methodically tested first then to just remove them because they might be the problem