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
- If you launch the YouTube app, and access the DNS that way, it will automatically re-display the browser after timeout happens
- You can add top sites and bookmarks to Switchbru for faster access
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 how do u open thru youtube app? on switch?
-
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
- If you launch the YouTube app, and access the DNS that way, it will automatically re-display the browser after timeout happens
- You can add top sites and bookmarks to Switchbru for faster access
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 it's been years. its not gonna change, but i might ask a coder friend of mine to look at this to see what is causing this to occur.
-
ah
-
It's best that we don't try to work around what Nintendo has through code, we don't wanna piss them off and they block us entirely.
@Maditalian yeah.... that would upset them big time Wouldn't it? a billion dollar company doesn't wanna give people free access to the Internet when they wouldn't really lose mony from it smfh
-
nintendo be like: -
ok
-
hi
-
This post is deleted!
-
timmy tuff knuckles got mad :-:
-
The timeout is useless
-
Please try and get Nintendo
to get the timer maybe as an option you can turn off or smthn -
Please try and get Nintendo
to get the timer maybe as an option you can turn off or smthn@FoxoAnimates if not please... make the data save
-
Please try and get Nintendo
to get the timer maybe as an option you can turn off or smthn@FoxoAnimates Bro Put TM There
-
b8fg8hr8h8gh37ytyuh7th84ynutm84n7t3ght3rn73th4ht3th8ht3h4th3thty3ty4yth3tht83ht38jty7ht3hthtytth37ht3ut3ht73hr37ht3nr73ht37ht7hrhh7ht7hth7hrhrhrhrhrhrh3hrhrtheirhighhir3yryr3hr3h3fndnfismdribsōűüōśśüśüōüśōśüōśřôůôřůōßôh7727f7fefh7fh7f3h7h7fhh7hf7hfh3h77erh737gehkfuhwifehghbnuhudnudngejűüűűěĺijĺħġěĺħĺķĺěħķĺěħġěĺġìěĺħěğěìĺġìěěčìġčìģğčèġģčèġģčdžðèčdžğèčdžðċdžðāċdžðādžðċdžðċģdzģdzğìħęġħěāģčġħğìğěċħðģāďčèļðâļðèďèħàèādzďħčìďħģry2h8t3y3teirhekthihfwhriwheiqei2tiengskfeuhgenfdnkfnckvnkndkngkdnknsingskrrksmksmfskmfsmfsfwkmwmdnstetrlsfjugigmdinginvkcnkcngidigcnindgidngidngkdngidntkngkengnteimtketienteintiehteinintientienteitnithitimteijeitjijti3tjeitmi
-
b8fg8hr8h8gh37ytyuh7th84ynutm84n7t3ght3rn73th4ht3th8ht3h4th3thty3ty4yth3tht83ht38jty7ht3hthtytth37ht3ut3ht73hr37ht3nr73ht37ht7hrhh7ht7hth7hrhrhrhrhrhrh3hrhrtheirhighhir3yryr3hr3h3fndnfismdribsōűüōśśüśüōüśōśüōśřôůôřůōßôh7727f7fefh7fh7f3h7h7fhh7hf7hfh3h77erh737gehkfuhwifehghbnuhudnudngejűüűűěĺijĺħġěĺħĺķĺěħķĺěħġěĺġìěĺħěğěìĺġìěěčìġčìģğčèġģčèġģčdžðèčdžğèčdžðċdžðāċdžðādžðċdžðċģdzģdzğìħęġħěāģčġħğìğěċħðģāďčèļðâļðèďèħàèādzďħčìďħģry2h8t3y3teirhekthihfwhriwheiqei2tiengskfeuhgenfdnkfnckvnkndkngkdnknsingskrrksmksmfskmfsmfsfwkmwmdnstetrlsfjugigmdinginvkcnkcngidigcnindgidngidngkdngidntkngkengnteimtketienteintiehteinintientienteitnithitimteijeitjijti3tjeitmi
@er ok
-
b8fg8hr8h8gh37ytyuh7th84ynutm84n7t3ght3rn73th4ht3th8ht3h4th3thty3ty4yth3tht83ht38jty7ht3hthtytth37ht3ut3ht73hr37ht3nr73ht37ht7hrhh7ht7hth7hrhrhrhrhrhrh3hrhrtheirhighhir3yryr3hr3h3fndnfismdribsōűüōśśüśüōüśōśüōśřôůôřůōßôh7727f7fefh7fh7f3h7h7fhh7hf7hfh3h77erh737gehkfuhwifehghbnuhudnudngejűüűűěĺijĺħġěĺħĺķĺěħķĺěħġěĺġìěĺħěğěìĺġìěěčìġčìģğčèġģčèġģčdžðèčdžğèčdžðċdžðāċdžðādžðċdžðċģdzģdzğìħęġħěāģčġħğìğěċħðģāďčèļðâļðèďèħàèādzďħčìďħģry2h8t3y3teirhekthihfwhriwheiqei2tiengskfeuhgenfdnkfnckvnkndkngkdnknsingskrrksmksmfskmfsmfsfwkmwmdnstetrlsfjugigmdinginvkcnkcngidigcnindgidngidngkdngidntkngkengnteimtketienteintiehteinintientienteitnithitimteijeitjijti3tjeitmi
@er bro, what? you ok?
-
was so tuff
