196

3134 readers

1675 users here now

Community Rules

You must post before you leave

Be nice. Assume others have good intent (within reason).

Block or ignore posts, comments, and users that irritate you in some way rather than engaging. Report if they are actually breaking community rules.

Use content warnings and/or mark as NSFW when appropriate. Most posts with content warnings likely need to be marked NSFW.

Most 196 posts are memes, shitposts, cute images, or even just recent things that happened, etc. There is no real theme, but try to avoid posts that are very inflammatory, offensive, very low quality, or very "off topic".

Bigotry is not allowed, this includes (but is not limited to): Homophobia, Transphobia, Racism, Sexism, Abelism, Classism, or discrimination based on things like Ethnicity, Nationality, Language, or Religion.

Avoid shilling for corporations, posting advertisements, or promoting exploitation of workers.

Proselytization, support, or defense of authoritarianism is not welcome. This includes but is not limited to: imperialism, nationalism, genocide denial, ethnic or racial supremacy, fascism, Nazism, Marxism-Leninism, Maoism, etc.

Avoid AI generated content.

Avoid misinformation.

Avoid incomprehensible posts.

No threats or personal attacks.

No spam.

Moderator Guidelines

Moderator Guidelines

Don’t be mean to users. Be gentle or neutral.
Most moderator actions which have a modlog message should include your username.
When in doubt about whether or not a user is problematic, send them a DM.
Don’t waste time debating/arguing with problematic users.
Assume the best, but don’t tolerate sealioning/just asking questions/concern trolling.
Ask another mod to take over cases you struggle with, if you get tired, or when things get personal.
Ask the other mods for advice when things get complicated.
Share everything you do in the mod matrix, both so several mods aren't unknowingly handling the same issues, but also so you can receive feedback on what you intend to do.
Don't rush mod actions. If a case doesn't need to be handled right away, consider taking a short break before getting to it. This is to say, cool down and make room for feedback.
Don’t perform too much moderation in the comments, except if you want a verdict to be public or to ask people to dial a convo down/stop. Single comment warnings are okay.
Send users concise DMs about verdicts about them, such as bans etc, except in cases where it is clear we don’t want them at all, such as obvious transphobes. No need to notify someone they haven’t been banned of course.
Explain to a user why their behavior is problematic and how it is distressing others rather than engage with whatever they are saying. Ask them to avoid this in the future and send them packing if they do not comply.
First warn users, then temp ban them, then finally perma ban them when they break the rules or act inappropriately. Skip steps if necessary.
Use neutral statements like “this statement can be considered transphobic” rather than “you are being transphobic”.
No large decisions or actions without community input (polls or meta posts f.ex.).
Large internal decisions (such as ousting a mod) might require a vote, needing more than 50% of the votes to pass. Also consider asking the community for feedback.
Remember you are a voluntary moderator. You don’t get paid. Take a break when you need one. Perhaps ask another moderator to step in if necessary.

founded 3 months ago

MODERATORS

[email protected]

229

joycon surgery success (and homebrew!) (lemmy.world)

submitted 1 week ago by [email protected] to c/[email protected]

23 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 13 points 1 week ago (2 children)

That's super cool! I'm very curious about this whole process, and I have many questions.

Do the controllers also need to be jailbroken? Do they retain their full functionality, most importantly the wireless capabilities, pairing and motion sensing? Does the dock still work? How's the performance for x86_64 games? How's the performance (and experience) for Switch games? What are the risks in doing this? How would you compare this to just getting a Steam Deck or making something that's probably easier?

Thanks in advance for answering, but in case it's too much, could you please link me the homebrewing project? I've got a Switch that's probably old enough to use the plastic jig, but I won't screw around with my little sibling's toy if the joycons don't work properly. I'd rather harvest the mainboard of my Framework 13 when I decide to upgrade it and build the aforementioned Beth Deck.

[–] [email protected] 11 points 1 week ago

Not OP, but I've done this to my Switch.

Only works if you have a first-run Switch that is susceptible to Fusee-Gelee. Or if there's a modchip involved, but a) adding a modchip is really fiddly and b) I don't know how much of the following applies if you have a modchip.
There are ways that don't require modifying a Joycon. There are "jigs" that you can buy or even 3d print if you've got access to a printer. Those slide down into the Joycon rail to connect a couple of pins necessary to do the whole homebrew thing. There are also paperclip and tinfoil methods that... aren't 100% safe.
No, the Joycons don't need to be jailbroken or anything. The modification OP is referring to, if you go that direction, is strictly a hardware mod to connect (electrically) a couple of pins inside the Joycon that connect to pins on the Switch (at the bottom of the "rail").
I'm not sure what's running on what OP has in the photo there but it looks like either Linux or Android. Either way, it probably isn't an x86_64 emulator. But one thing you can do with homebrew is to run a (slightly-tweaked) "copy" of the factory-installed Switch OS from the SD card. If you're doing that, then everything retains full functionality. The dock works fine and the Joycons work exactly the same with one minor caveat: when switching between the main/system and "copy"/"EmuEMMC" OS's, you'll need to re-pair.
No idea whether x86_64 emulation is an option and if so what kind of performance you could expect.
Performance and experience for Switch games is perfect!
One risk is bricking (obviously) which is a pretty negligible if you back everything up the way the guides tell you to ahead of time. (In fact, it's very arguable that homebrewing your Switch actually makes your Switch more resistant to bricking because you have more options with regard to fixing it yourself.)
Another risk is getting banned from the e-shop and all online interaction. Basically if Nintendo detects you're running homebrew (for instance, if your Switch is online and communicating with Nintendo and reports to Nintendo that you have something installed that isn't officially-lisenced Nintendo software/games) they'll ban you from all online things. The Switch itself will still work fine for all offline interactions and any games on the device will continue to work as will physical game cartridges. But, as long as you only make modifications to the "copy"/"EmuEMMC" and set up some of the DNS blocking options that prevent your Switch from communicating with Nintendo's servers (or just never connect to the internet from the EmuEMMC OS), you should be golden.
Also, if you have a first-run Switch (that doesn't require a modchip) there's very little chance of voiding your warranty. If you need to send your Switch in for service, as long as you don't send them a modded Joycon, jig, or SD card loaded with homebrew stuff, and as long as you don't make any mods to the main OS, there's no way for them to detect that you've modded it. The only downside is that if you send in a first-run Switch for service, it's almost guaranteed they'll replace the motherboard with one that isn't hackable without a modchip.
Oh, I guess one more risk I should mention. It's possible your EmuEMMC will get corrupted randomly (at least that happened to me) and you won't be able to boot into it again without setting it back up from scratch (from a (new or old) backup of the system OS). That will lose you any saved game data on your EmuEMMC. Though that can be mitigated by backing up your save games to the SD card on a regular basis. (I've learned my lesson.) That isn't so much a risk for any games you play on the system OS (which you can boot into at any time trivially.)
I don't have any experience with the Steam Deck, so couldn't speak to that. I love being able to mod Switch games, back up my saves, install emulators, etc on my Switch.

If you want to get homebrew on your Switch set up, you can start here. But of course, it only works for the earliest-released Switch runs. And you'll need a computer or something to send a "payload" to your Switch to get booted into a homebrew environment.

Good luck!

[–] [email protected] 7 points 1 week ago* (last edited 1 week ago) (1 children)

I haven't modified the behavior of the controllers at all; that much is just decorative. Same for the dock. You can use this as a "normal" switch and everything works :)
- edit: you can also use some third-party laptop docks! but not all of them. I think the switch is using some non-standard protocol. Some docks advertise themselves as "switch compatible". However, when you are using a homebrew os (linux or android), then it will work with any dock.
I have a steam deck as well, and I use both. A modded switch (or any switch, tbh) has very limited system specs. x86 emulation is possible, but only for games that don't use much cpu or ram. Steam and Proton are basically unusable. This is for emulation and low-spec indie games.
The trailhead begins at https://switch.hacks.guide/. I recommend a 512 GB microsd, with 128 GB set aside for ubuntu and 64 GB for android. Happy hacking :)

[–] [email protected] 5 points 1 week ago

Yeah the Switch uses myDP protocol which is obscure and unsupported by most laptop docks out there, only ones which support that protocol and supply charging will work with the Switch. Also I didn't know that Laptop docks worked fine in Linux if they didn't work in the normal Switch OS. I assumed the lack of compatibility was due to hardware or chipset reasons, not OS related reasons.