Browser Timeout: "This Screen will be closed."
-
EDIT for Feb 3rd, 2024:
The summary of this thread's findings is:
- This notification will appear after 20 minutes of screen-on time using the browser
- The browser will always immediately close after the pop-up
- Nintendo has ignored so far the petition asking them to enable the browser
Tips:
- If you lock the device, you can stretch the total time you have out longer. Screen off time doesn't count against the 20 minutes
- If you set up the DNS and then launch the YouTube app instead of doing a Connection Test, it will automatically re-display the browser after timeout happens
- You can add top sites and bookmarks to Switchbru for faster access, or submit useful links via the survey on the BrowseDNS landing page
About the browser:
- The timer is built-into the Switch, and enforced by the Switch's OS
- The browser itself is called NetFront, and is made by ACCESS Co
- It's possible that there is a deal between Nintendo and ACCESS that limits the usage of the browser (This is only speculation)
Homebrew workaround:
- If you have a Switch that can run homebrew, then the browser can be accessed with BrowseNX, which bypasses the timeout and allows video content
- Configuring homebrew however is much more involved than just using the DNS, and should only be done by advanced and/or technical users
Original post:
This is a thread to talk about the browser closing on the Nintendo switch when using BrowseDNS or Switchbru DNS... This appears to be a timeout added by Nintendo in FW update 10.0, but the mechanisms of when/why it closes are not known.
In my experience, I have had both web pages live for a long time (even overnight!) by sleeping the switch or pressing home, and when it decides to close always seems a little random.
It seems like no matter how many page loads occur, or clicks/scrolls I make, it's determined to shut down. Does anyone have any other experiences or theories about whne it decides to close?
If the timeout can be better understood, then we may be able to discover a workaround to it. If it's something networking related, for instance, maybe there are changes that can be made to prevent it from closing.
It would also be interesting to know if this same timeout occurs when using "normal" captive portal airplane/hotel hotspots (which is what the browser applet was made for).
I will also again plug the petition to Nintendo to unlimited this browser, including removing the timeout.
Sign the browser petition! Or visit my site at vgmoose.dev.
-
EDIT for Feb 3rd, 2024:
The summary of this thread's findings is:
- This notification will appear after 20 minutes of screen-on time using the browser
- The browser will always immediately close after the pop-up
- Nintendo has ignored so far the petition asking them to enable the browser
Tips:
- If you lock the device, you can stretch the total time you have out longer. Screen off time doesn't count against the 20 minutes
- If you set up the DNS and then launch the YouTube app instead of doing a Connection Test, it will automatically re-display the browser after timeout happens
- You can add top sites and bookmarks to Switchbru for faster access, or submit useful links via the survey on the BrowseDNS landing page
About the browser:
- The timer is built-into the Switch, and enforced by the Switch's OS
- The browser itself is called NetFront, and is made by ACCESS Co
- It's possible that there is a deal between Nintendo and ACCESS that limits the usage of the browser (This is only speculation)
Homebrew workaround:
- If you have a Switch that can run homebrew, then the browser can be accessed with BrowseNX, which bypasses the timeout and allows video content
- Configuring homebrew however is much more involved than just using the DNS, and should only be done by advanced and/or technical users
Original post:
This is a thread to talk about the browser closing on the Nintendo switch when using BrowseDNS or Switchbru DNS... This appears to be a timeout added by Nintendo in FW update 10.0, but the mechanisms of when/why it closes are not known.
In my experience, I have had both web pages live for a long time (even overnight!) by sleeping the switch or pressing home, and when it decides to close always seems a little random.
It seems like no matter how many page loads occur, or clicks/scrolls I make, it's determined to shut down. Does anyone have any other experiences or theories about whne it decides to close?
If the timeout can be better understood, then we may be able to discover a workaround to it. If it's something networking related, for instance, maybe there are changes that can be made to prevent it from closing.
It would also be interesting to know if this same timeout occurs when using "normal" captive portal airplane/hotel hotspots (which is what the browser applet was made for).
I will also again plug the petition to Nintendo to unlimited this browser, including removing the timeout.
It also seems to do it even in sleep mode. For me I came back after half an hour or so & poof! Gone!
-
EDIT for Feb 3rd, 2024:
The summary of this thread's findings is:
- This notification will appear after 20 minutes of screen-on time using the browser
- The browser will always immediately close after the pop-up
- Nintendo has ignored so far the petition asking them to enable the browser
Tips:
- If you lock the device, you can stretch the total time you have out longer. Screen off time doesn't count against the 20 minutes
- If you set up the DNS and then launch the YouTube app instead of doing a Connection Test, it will automatically re-display the browser after timeout happens
- You can add top sites and bookmarks to Switchbru for faster access, or submit useful links via the survey on the BrowseDNS landing page
About the browser:
- The timer is built-into the Switch, and enforced by the Switch's OS
- The browser itself is called NetFront, and is made by ACCESS Co
- It's possible that there is a deal between Nintendo and ACCESS that limits the usage of the browser (This is only speculation)
Homebrew workaround:
- If you have a Switch that can run homebrew, then the browser can be accessed with BrowseNX, which bypasses the timeout and allows video content
- Configuring homebrew however is much more involved than just using the DNS, and should only be done by advanced and/or technical users
Original post:
This is a thread to talk about the browser closing on the Nintendo switch when using BrowseDNS or Switchbru DNS... This appears to be a timeout added by Nintendo in FW update 10.0, but the mechanisms of when/why it closes are not known.
In my experience, I have had both web pages live for a long time (even overnight!) by sleeping the switch or pressing home, and when it decides to close always seems a little random.
It seems like no matter how many page loads occur, or clicks/scrolls I make, it's determined to shut down. Does anyone have any other experiences or theories about whne it decides to close?
If the timeout can be better understood, then we may be able to discover a workaround to it. If it's something networking related, for instance, maybe there are changes that can be made to prevent it from closing.
It would also be interesting to know if this same timeout occurs when using "normal" captive portal airplane/hotel hotspots (which is what the browser applet was made for).
I will also again plug the petition to Nintendo to unlimited this browser, including removing the timeout.
@VGMoose the timeout from what i can tell seems to close the browser after around 20 minutes so that may or maynot be helpful
twitter with my fursona ref sheet if any one cares: @jakemasson6
switch brew friend code: SB-7286-3458-4175 -
@VGMoose the timeout from what i can tell seems to close the browser after around 20 minutes so that may or maynot be helpful
@MaxiTheFox i think around 15 minutes, i watch the time
who dares underestimate highway trucks? i dont, its the path, not the truck, brains over brawns are the way
-
are you talking about when it says this page will now be close in then it takes you back to the settings on the switch
Friend Code SB-2777-1008-7084
Friend Code SW-2627-0871-5212 -
are you talking about when it says this page will now be close in then it takes you back to the settings on the switch
@Giovani yeah
-
why you need to watch videos in the dns when you can get youtube in the e shop
Friend Code SB-2777-1008-7084
Friend Code SW-2627-0871-5212 -
@Giovani different site i assume
-
EDIT for Feb 3rd, 2024:
The summary of this thread's findings is:
- This notification will appear after 20 minutes of screen-on time using the browser
- The browser will always immediately close after the pop-up
- Nintendo has ignored so far the petition asking them to enable the browser
Tips:
- If you lock the device, you can stretch the total time you have out longer. Screen off time doesn't count against the 20 minutes
- If you set up the DNS and then launch the YouTube app instead of doing a Connection Test, it will automatically re-display the browser after timeout happens
- You can add top sites and bookmarks to Switchbru for faster access, or submit useful links via the survey on the BrowseDNS landing page
About the browser:
- The timer is built-into the Switch, and enforced by the Switch's OS
- The browser itself is called NetFront, and is made by ACCESS Co
- It's possible that there is a deal between Nintendo and ACCESS that limits the usage of the browser (This is only speculation)
Homebrew workaround:
- If you have a Switch that can run homebrew, then the browser can be accessed with BrowseNX, which bypasses the timeout and allows video content
- Configuring homebrew however is much more involved than just using the DNS, and should only be done by advanced and/or technical users
Original post:
This is a thread to talk about the browser closing on the Nintendo switch when using BrowseDNS or Switchbru DNS... This appears to be a timeout added by Nintendo in FW update 10.0, but the mechanisms of when/why it closes are not known.
In my experience, I have had both web pages live for a long time (even overnight!) by sleeping the switch or pressing home, and when it decides to close always seems a little random.
It seems like no matter how many page loads occur, or clicks/scrolls I make, it's determined to shut down. Does anyone have any other experiences or theories about whne it decides to close?
If the timeout can be better understood, then we may be able to discover a workaround to it. If it's something networking related, for instance, maybe there are changes that can be made to prevent it from closing.
It would also be interesting to know if this same timeout occurs when using "normal" captive portal airplane/hotel hotspots (which is what the browser applet was made for).
I will also again plug the petition to Nintendo to unlimited this browser, including removing the timeout.
Does anyone have some more concrete information on when this appears?
Sign the browser petition! Or visit my site at vgmoose.dev.
-
Its closes on me in 20mins its quite a annoyance I wish it didnt though :(
-Liz
-
i am not 100% sure on this, but i think pressing x, and pressing cancel seems to delay it
the sandwich
soad deer dance
i need a medic bag
lehrer für kacke -
i am not 100% sure on this, but i think pressing x, and pressing cancel seems to delay it
@dafunkymonke woud be cool if you could do some more testing on that .
-
EDIT for Feb 3rd, 2024:
The summary of this thread's findings is:
- This notification will appear after 20 minutes of screen-on time using the browser
- The browser will always immediately close after the pop-up
- Nintendo has ignored so far the petition asking them to enable the browser
Tips:
- If you lock the device, you can stretch the total time you have out longer. Screen off time doesn't count against the 20 minutes
- If you set up the DNS and then launch the YouTube app instead of doing a Connection Test, it will automatically re-display the browser after timeout happens
- You can add top sites and bookmarks to Switchbru for faster access, or submit useful links via the survey on the BrowseDNS landing page
About the browser:
- The timer is built-into the Switch, and enforced by the Switch's OS
- The browser itself is called NetFront, and is made by ACCESS Co
- It's possible that there is a deal between Nintendo and ACCESS that limits the usage of the browser (This is only speculation)
Homebrew workaround:
- If you have a Switch that can run homebrew, then the browser can be accessed with BrowseNX, which bypasses the timeout and allows video content
- Configuring homebrew however is much more involved than just using the DNS, and should only be done by advanced and/or technical users
Original post:
This is a thread to talk about the browser closing on the Nintendo switch when using BrowseDNS or Switchbru DNS... This appears to be a timeout added by Nintendo in FW update 10.0, but the mechanisms of when/why it closes are not known.
In my experience, I have had both web pages live for a long time (even overnight!) by sleeping the switch or pressing home, and when it decides to close always seems a little random.
It seems like no matter how many page loads occur, or clicks/scrolls I make, it's determined to shut down. Does anyone have any other experiences or theories about whne it decides to close?
If the timeout can be better understood, then we may be able to discover a workaround to it. If it's something networking related, for instance, maybe there are changes that can be made to prevent it from closing.
It would also be interesting to know if this same timeout occurs when using "normal" captive portal airplane/hotel hotspots (which is what the browser applet was made for).
I will also again plug the petition to Nintendo to unlimited this browser, including removing the timeout.
@VGMoose I'm working on identifying the piece of code that tells the console to leave everything running.
\'-'/
free-palestine.carrd.co
veteran member and moderator
Ash Ketchum・1997-2023 -
@VGMoose I'm working on identifying the piece of code that tells the console to leave everything running.
happens to me to if there a way to stop this plz let me know
Im sorry you couldnt make to my show so I'm bringing the show to you
-
Its closes on me in 20mins its quite a annoyance I wish it didnt though :(
@Elizabeth said in Browser Timeout: "This Screen will be closed.":
Its closes on me in 20mins its quite a annoyance I wish it didnt though :(
its super annoying when trying to hold a conversation or roleplay
who dares underestimate highway trucks? i dont, its the path, not the truck, brains over brawns are the way
-
@Elizabeth said in Browser Timeout: "This Screen will be closed.":
Its closes on me in 20mins its quite a annoyance I wish it didnt though :(
its super annoying when trying to hold a conversation or roleplay
@SnowRunnerLegend fr q-q
-
happens to me to if there a way to stop this plz let me know
very annoying
-
I am trying to do some researching by "cronometring" the time for the timeout in various situation like pressing the x button or changing page very 5 minutes ecc. when the results are ready I will make a spreadsheet
-
thanks :D
