-
Notifications
You must be signed in to change notification settings - Fork 2
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
Framework Laptop 13 120Hz screen not correctly handled #6
Comments
Ho that's intresting, i'll push some changes in 5 mins can you try again after? |
the changes are live, the integration is basic atm but tell me if it work and send me your log in the logs folder 👍 |
did a other commit, try it out :) |
did a other update, try it and send me your logs and your file sensors.json too please 🙏 |
2024-12-31_2.log |
Thanks you, I look at the sensor id problem and I will tell you when i push a fix |
Updated, can you try and again send me the files? Thanks for your help ! |
Hi! Here they are: |
Updated, tell me if it works :) |
Hi! Sorry for the long delay. I took some holidays from my laptop :) Additionally, there are a bunch of warnings (that seem to be originating from incorrect PowerShell command parameters) and some other errors on setting power plans, I'll attach the usual files :) Finally, just a small quality of life request: When the hub is started it defaults the refresh rate to "Auto". I usually keep my FW at 120Hz and this defaults it at 60Hz, requiring me to change it back. Do you think it would be a nice change if the hub defaults to the current refresh rate? This avoids a temporary black screen and some apps to stop working in case the refresh rate is different. Thank you, as always! |
Hi,
I have the 120Hz screen on my FW 13 and the application shows 3 possibilities for the refresh rate: "Auto", "60Hz" and "165Hz". I believe that this is what it should show for a FW 16. Also, the "165Hz" button does nothing on my laptop.
Proposed solution
Add a laptop model check when the app builds the UI and dynamically set button text and click event functions to the compatible options.
Thank you for your great work and happy new year! :)
The text was updated successfully, but these errors were encountered: