Closed Masamune3210 closed 7 years ago
I'm pretty sure this has been requested before a long time ago.
Yeah, normally a successful connection test is required for using the wireless connection. MicroSD Management is the only app capable of bypassing that.
Unfortunately, this is infeasible to implement. The 3DS uses that connection test to choose which wireless network to connect to. mSD Management only "bypasses" it because it forces you to manually select a network.
So yeah, µSD management doesn't really bypass it, it simply isn't affected.
Tbh I'd have implemented it if it were feasible.
Thanks anyway, figured it was worth a shot
On Jun 15, 2017, 7:26 PM, at 7:26 PM, Yuuki Hikari notifications@github.com wrote:
Closed #618.
-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/AuroraWright/Luma3DS/issues/618#event-1126048865
System model:
[e.g. 2DS, New 3DS, Old 3DS]
SysNAND version (+emu/redNAND version if applicable): 11.4.0-37 [e.g. 11.4.0-37U SysNAND, 11.4.0-37J EmuNAND]
Entrypoint (How/what you're using to boot Luma3DS): Boot9Strap [e.g. Boot9Strap/Sighax, etc.]
Luma3DS version: 8.0 [e.g. 7.1 stable or if using nightly/hourly specify the commit like this https://github.com/AuroraWright/Luma3DS/commit/9570e6cbeca53128433abbf5e3473cb8a07fe69e]
Luma3DS configuration/options:
Default EmuNAND: ( )
Screen brightness: ( )
Splash: ( )
PIN lock: ( )
New 3DS CPU: ( )
--
Autoboot EmuNAND: ( )
Use EmuNAND FIRM if booting with R: ( )
Enable loading external FIRMs and modules: ( )
Use custom path: ( )
Enable game patching: ( )
Show NAND or user string in System Settings: ( )
Show GBA boot screen in patched AGB_FIRM: ( )
Patch ARM9 access: ( )
Set developer UNITINFO: ( )
--
Explanation of the issue:
Since we now have the ability to control the entire system, would it be possible to keep the 3DS from disconnecting from WiFi when it can't talk to nintendo
Steps to reproduce:
1.
2.
Dump file: