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

Improve ARM Processor CPU Speed Detection #50

Open
I-Rinka opened this issue Jun 27, 2021 · 16 comments
Open

Improve ARM Processor CPU Speed Detection #50

I-Rinka opened this issue Jun 27, 2021 · 16 comments
Assignees
Labels
checks Check improvement or new check. enhancement New feature or request external cause A program other than WhyNotWin11 causes the issue help wanted Extra attention is needed

Comments

@I-Rinka
Copy link

I-Rinka commented Jun 27, 2021

This software is good but it only works on x86 processors. Even though it can run on WOA because of the compatibility layer, it can't provide comprehensive information. The WOA ecosystem is growing, so native ARM64 version may be needed.

image

The supported Qualcomm processors are shown below.

https://docs.microsoft.com/en-us/windows-hardware/design/minimum/supported/windows-11-supported-qualcomm-processors

@rcmaehl rcmaehl self-assigned this Jun 27, 2021
@rcmaehl rcmaehl added this to the 3.0 milestone Jun 27, 2021
@micwoj92
Copy link
Collaborator

I don't think that native is possible, because autoit does not support support arm.

@rcmaehl
Copy link
Owner

rcmaehl commented Jun 27, 2021

I won't be able to make a native ARM64 version, but I can implement improvements for proper detection on Supported Qualcomm Processors. I'm assuming this is in regards to the Architecture check. Odd that it wasn't able to mark the CPU as Compatible as it's in the Qualcomm list. Finally, can you send me a copy of Save All Information from dxdiag?

rcmaehl added a commit that referenced this issue Jun 27, 2021
Add Social Icons
Fix SQ1 / SQ2 Detection
Update Lists to mark EOF
@I-Rinka
Copy link
Author

I-Rinka commented Jun 27, 2021

Sure : ) But my Windows is in Chinese. Hoping it would not trouble you.

DxDiag.txt

I won't be able to make a native ARM64 version, but I can implement improvements for proper detection on Supported Qualcomm Processors. I'm assuming this is in regards to the Architecture check. Odd that it wasn't able to mark the CPU as Compatible as it's in the Qualcomm list. Finally, can you send me a copy of Save All Information from dxdiag?

@rcmaehl
Copy link
Owner

rcmaehl commented Jun 27, 2021

Driver Model: 2.6 WDDM

DXDIAG WHYYYYY. Will fix this in an upcoming build to pass WDDM check

rcmaehl added a commit that referenced this issue Jun 27, 2021
Fix WDDM detection on SQ1/SQ2
rcmaehl added a commit that referenced this issue Jun 27, 2021
Add WDDM 3 fix for Non-English languages
@micwoj92 micwoj92 mentioned this issue Jun 27, 2021
9 tasks
@micwoj92 micwoj92 added the enhancement New feature or request label Jun 28, 2021
@micwoj92
Copy link
Collaborator

micwoj92 commented Jul 1, 2021

@I-Rinka Could you test latest stable release, are there any improvements?

@I-Rinka
Copy link
Author

I-Rinka commented Jul 1, 2021

image
The left one is x64 version and the right is x86 version. Only CPU frequency has problem.

@micwoj92
Copy link
Collaborator

micwoj92 commented Jul 1, 2021

So a regression then :/

@rcmaehl rcmaehl added the checks Check improvement or new check. label Jul 6, 2021
@rcmaehl
Copy link
Owner

rcmaehl commented Jul 25, 2021

image
The left one is x64 version and the right is x86 version. Only CPU frequency has problem.

This is probably the same issue that intel chips have where it reports current speed as max speed instead of max possible speed.

@rcmaehl rcmaehl added external cause A program other than WhyNotWin11 causes the issue in-progress Accepted, at least some code is implemented or pending push labels Aug 12, 2021
@micwoj92
Copy link
Collaborator

@rcmaehl is the cpu speed exact same issue as with intel x86_64 cpus? if yes then this issue should be closed, because the applications works/detects same on arm and on x86_64

@rcmaehl
Copy link
Owner

rcmaehl commented Sep 27, 2021

@I-Rinka
Copy link
Author

I-Rinka commented Sep 29, 2021

image

It works.

@I-Rinka
Copy link
Author

I-Rinka commented Sep 29, 2021

Oh, the CPU Frequency is still not a correct value when I look close to it. It just turns green.

rcmaehl added a commit that referenced this issue Sep 29, 2021
@rcmaehl
Copy link
Owner

rcmaehl commented Sep 29, 2021

Should be fixed in the latest build.

https://nightly.link/rcmaehl/WhyNotWin11/workflows/wnw11/main/WNW11.zip

@I-Rinka
Copy link
Author

I-Rinka commented Sep 29, 2021

image

Basically it's right. But.. I don't know, probably the emulated processor has a slightly lower frequency.

@rcmaehl
Copy link
Owner

rcmaehl commented Sep 29, 2021

Not sure how to improve this unfortunately, just glad it's properly passing now.

@rcmaehl rcmaehl added help wanted Extra attention is needed and removed in-progress Accepted, at least some code is implemented or pending push labels Sep 29, 2021
@rcmaehl rcmaehl changed the title ARM64 support Improve ARM Processor CPU Speed Detection Nov 13, 2021
@rcmaehl rcmaehl removed this from the 3.0 milestone Nov 13, 2021
@WilloIzCitron
Copy link
Contributor

WilloIzCitron commented Mar 18, 2022

the CPU Speed detects on registry only and it may inaccurate

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
checks Check improvement or new check. enhancement New feature or request external cause A program other than WhyNotWin11 causes the issue help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

4 participants