Atmosphere: Actually block auto updates

Created on 1 Jan 2019  路  9Comments  路  Source: Atmosphere-NX/Atmosphere

Feature Request

Respect the user's choice of not auto updating

What feature are you suggesting?

Prevent Horizon from downloading or writing the updates in the background. If the update is already downloaded and the user has the auto update turned off, delete it.

Hopefully blocking before the request reaches N's servers to leave no trace. If not possible, prevent those files from being written to disk

Why would this feature be useful?

Currently Horizon downloads the updates in the background no matter of what the user has set in settings. Then you get nagged to update on each game launch. This is bad behaviour by N

Tested on 5.1.0+Atmosph猫re 0.8.2, auto update turned off, been on wifi for ~1min --> "An update is ready", pressed A twice while opening a game... welcome to 6.2.0.

Thankfully I had autoRCM enabled and no fuses were harmed

Most helpful comment

Why not allow users to specify URLS blocked via a config file? So that we don鈥檛 have to use dnsmasq on a per network basis to partially block Nintendo domains?

All 9 comments

I suppose what I'm asking for is to be able to kill and prevent from running the ns:su service by toggling the setting

Bonus points for deleting the downloaded update data

I actually support this idea. I really wanted a feature like this on the 3DS, (been screwed over WAY too many times to count with ninty's auto updating) and it'd make 90dns useless for us banned squad.

This is a must.

When trying to load a game, without even thinking about it i accidentally clicked update on the nag prompt and it took me from 6.2.0 to 7.0.0.

No more Atmosphere until they get 7.0.0 figured out.

Please we need this

If you need to block updates, use 90dns, and enter Maintenance Mode at least once afterwards.

While it would be nice for Atmosphere to block automatic updates, it's not strictly necessary, as there are solutions available.

i deployed 90dns dnsmasq config to my openwrt. so all ninty communication are blocked

90dns must be deployed on a per network instance so any Pre-loaded Nintendo WiFi's will be excluded so a way to disable system update traffic would be great.

Why not allow users to specify URLS blocked via a config file? So that we don鈥檛 have to use dnsmasq on a per network basis to partially block Nintendo domains?

Closing this issue since no work is being done on this, however given a concrete proposal for how to achieve this, I'm theoretically open to it in the future.

Was this page helpful?
0 / 5 - 0 ratings