Homebrew Homebrew app sys-patch - sysmod that patches on boot

It's the v4 version working properly now with the games?
for me i got a fatal error when launching game the program id was 01000000000100c i could not find this in my contents so i have no idea what it is so i used the v3 version for now and yes it seems to work just make sure not to use saltynx that cause everything to not work once i removed it everything functioned my only issue now is with breath of the wild i can get it to launch by disabling my sysmodules but on main menu it freezes after a minute or two
 
for me i got a fatal error when launching game the program id was 01000000000100c i could not find this in my contents so i have no idea what it is so i used the v3 version for now and yes it seems to work just make sure not to use saltynx that cause everything to not work once i removed it everything functioned my only issue now is with breath of the wild i can get it to launch by disabling my sysmodules but on main menu it freezes after a minute or two
SaltyNX works on 21.0.0

https://github.com/masagrator/SaltyNX/releases/tag/1.6.0
 
what is saltynx for and could you tell me why breath of the wild might freezing on menu after a minute or when i try to load save i am currently reinstalling with the new dbi to see if it fixes it but this is weird as it is the only game not working now
Post automatically merged:

what is saltynx for and could you tell me why breath of the wild might freezing on menu after a minute or when i try to load save i am currently reinstalling with the new dbi to see if it fixes it but this is weird as it is the only game not working now
so i just installed this saltynx and now on bootup i get fatalat error program id 010000000000013 with error code 2001-0132 (0x10801) so either i have something installed that it is conflicting with or this is still not working any help would be appreciated
 
Last edited by froggy55,
i dont mind using airplane mode my console banned anyways once im in game i can always reenable the internet so for example i can trade pokemon with my other switch localy or when using overide enable after then use what ever apps you need
Having "Airplane mode" enabled is a big deal for those who are heavily reliant on an external gamepad. I personally do not have a joy-con connected to my Switch when I use it because I have an external controller that I prefer to use.
 
Having "Airplane mode" enabled is a big deal for those who are heavily reliant on an external gamepad. I personally do not have a joy-con connected to my Switch when I use it because I have an external controller that I prefer to use.
When you enable Airplane mode, it still lets you enable Bluetooth manually afterwards to continue using wireless devices. Does that not work for you? Just curious.
 
I fix in my setup the problem with Linkalho Linked accounts on FW 21.
Go to atmosphere\config\system_settings.ini open with notepad and add this.

[olsc]
enable_olsc_communication_block = u8!0x1
default_auto_download_global_setting = u8!0x0
default_auto_upload_global_setting = u8!0x0

Save your file and enjoy!

Tks for the help and clarification @bth and @impeeza.
 
I fix in my setup the problem with Linkalho Linked accounts on FW 21.
Go to atmosphere\config\system_settings.ini open with notepad and add this.



Save your file and enjoy!

Tks for the help and clarification @bth and @impeeza.
Wow, this actually works. Thank you! No longer any "Please wait" looping :D y'all are amazing
 
I fix in my setup the problem with Linkalho Linked accounts on FW 21.
Go to atmosphere\config\system_settings.ini open with notepad and add this.



Save your file and enjoy!

Tks for the help and clarification @bth and @impeeza[
[/QUOTE]

Wow, this actually works. Thank you! No longer any "Please wait" looping :D y'all are amazing
i second this thank you so much now if i could only get breath of the wild working
 
  • Love
Reactions: rodrigues14
I fix in my setup the problem with Linkalho Linked accounts on FW 21.
Go to atmosphere\config\system_settings.ini open with notepad and add this.



Save your file and enjoy!

Tks for the help and clarification @bth and @impeeza.
https://switchbrew.org/wiki/System_Settings

yes that was also always an option

but my understanding is that
"enable_olsc_communication_block" is not a real key? placebo probably



these two is what matters anyway, as that is what determines if saves should be uploaded or download (only upload defaults to true), but forcing them off should do the job
default_auto_download_global_setting = u8!0x0
default_auto_upload_global_setting = u8!0x0

it seems to me the system_settings page is documentation for atmosphere's set-mitm, and that the actual setting itself is in OLSC.

olsc-.jpg
 
Last edited by bth,
https://switchbrew.org/wiki/System_Settings

yes that was also always an option

but my understanding is that
"enable_olsc_communication_block" is not a real key? placebo probably



these two is what matters anyway, as that is what determines if saves should be uploaded or download (only upload defaults to true), but forcing them off should do the job
default_auto_download_global_setting = u8!0x0
default_auto_upload_global_setting = u8!0x0

it seems to me the system_settings page is documentation for atmosphere's set-mitm, and that the actual setting itself is in OLSC.

View attachment 540254
No need for creating a patch, the source code for linkalho is already moddified and fixes it:
https://github.com/impeeza/linkalho/issues/4
 
No need for creating a patch, the source code for linkalho is already moddified and fixes it:
https://github.com/impeeza/linkalho/issues/4
> it automatically adds/modifies or creates the fixes to the atmosphere ini file when it creates a linked account.

that's bad UX, having to run linkalho to fix an issue that can be patched.

all he did was make linkalho force-edit system_settings.ini or create one and add the line.

it also does not address every single existing application of linkalho, it requires them to download this modified version (without source code), and run it, it's not automatically applied for end user, only new users

and i already made one such patch; it just needs testing/verification (as .ips patch first)
 
Last edited by bth,
  • Like
Reactions: ber71
Just a question: if syspatch needs to be modified for each new hos version, why not to use fixed offsets for patching known module versions? Possibly with text config, so users can add/modify patches without recompiling.
 
Just a question: if syspatch needs to be modified for each new hos version, why not to use fixed offsets for patching known module versions? Possibly with text config, so users can add/modify patches without recompiling.
it doesn't need to be modified for each new hos version, that's a misinterpretation.

the offsets change every version, almost always.

the regex patterns can at time, need adjustments, to accomodate changes in the pattern results, or like nintendo did in 21.0.0 for NIFM, add 8 byte padding randomly


tl:dr if sys-patch had implementation for pointers, it would simplify process by a lot, as those can usually be found at/in function 0x900
 
  • Love
Reactions: impeeza
No need for creating a patch, the source is already moddified and fixes it:
https://github.com/impeeza/linkalho/issues/4

it also does not address every single existing application of linkalho, it requires them to download this modified version (without source code), and run it, it's not automatically applied for end user, only new users
The source code is what is posted, not a modified version. You can compile it yourself or check the code.
 
Tested and working... Linking a unliking accounts.
of course that works, what he changed was only adding the flag for olsc by editing/creating /atmosphere/config/system_settings.ini, he didn't actually fix or address the issues with linkalho

he's masquerading that as "fixing it", which it does not.
 
of course that works, what he changed was only adding the flag for olsc by editing/creating /atmosphere/config/system_settings.ini, he didn't actually fix or address the issues with linkalho

he's masquerading that as "fixing it", which it does not.


Well, it works...

Now I'm having internal questions... Is really needed a patch for something that can be avoid with the config ini?

It's a masquerade, but it's enough...


Edit: I can test your patches in a few hours... Thanks for all your work
 
  • Like
Reactions: Blythe93 and alcab
Well, it works...

Now I'm having internal questions... Is really needed a patch for something that can be avoid with the config ini?

It's a masquerade, but it's enough...


Edit: I can test your patches in a few hours... Thanks for all your work
your question fails to understand why there should be a patch.

the same reason the nim patch exists, to be able to spread a workaround to crashes/unwanted behaviour, without the user actively needing to run a homebrew remedy their issue, which will only last until the next time they have to delete their atmosphere folder.

its for usage, for the masses, who do not read gbatemp, or speak english, who needs their own communities to translate instructions, make new videos.

just having it be bundled with regular patches and/or sys-patch makes things easier for the larger population of users, to be reached with a fix that doesn't require them to do something new.

it helps unclog support channels.

anyway:

from 0x84F44, a9 c3 5f 38 - ldurb w9, [x29, #-4]
to: 0x84F44, e9 03 1f 2a - mov w9, wzr
olsc.jpg
 

Attachments

Site & Scene News

Popular threads in this forum