Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added the second AMD APU code value to Steam Deck detection #3434

Merged
merged 1 commit into from
Jan 17, 2024

Conversation

m3e-g
Copy link
Contributor

@m3e-g m3e-g commented Jan 12, 2024

This should fix the #3433

I've added the new APU name to the first check. If neither is true, isDeck is set to false.

@flavioislima
Copy link
Member

flavioislima commented Jan 12, 2024

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

@m3e-g
Copy link
Contributor Author

m3e-g commented Jan 12, 2024

I have read the CLA Document and I hereby sign the CLA

cpus[0]?.model !== 'AMD Custom APU 0405' &&
cpus[0]?.model !== 'AMD Custom APU 0932'
)
return { isDeck: false }
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm checking on my steamdeck and it looks like we have a HOSTNAME env variable with the value steamdeck, maybe we can just use that info for this instead? I imagine it's more future proof

what do you think @CommandMC ?

We have other variables like:

HOME=/home/deck
LOGNAME=deck

and many env variables including /home/deck or steamdeck

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

HOSTNAME is changable from the steam ui itself and I haven't checked how multi users are handled on the deck (may have different HOME?).

Problem I see with the environment variables is that anyone running steamos image on their machine would have the same set, and hardware ID is harder to spoof. (If someone did it, then he had his purpose)

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I haven't checked how multi users are handled on the deck

As far as I can tell, they aren't, you're always the deck user account

Regardless, I agree, we should only look at things definitively proving we're on the Steam Deck hardware, not just SteamOS or something that's very similar to what the Deck might look like

@arielj arielj merged commit a76e4f1 into Heroic-Games-Launcher:main Jan 17, 2024
9 checks passed
@Heroic-Games-Launcher Heroic-Games-Launcher locked and limited conversation to collaborators Jan 17, 2024
@m3e-g m3e-g deleted the fix-deck-apu-check branch January 18, 2024 08:08
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants