mirror of
https://github.com/hirschmann/nbfc.git
synced 2026-04-26 17:15:58 +03:00
[GH-ISSUE #1131] Does Not Work for HP ENVY x360 15-ee0003ca, AMD Ryzen 7 4700U #972
Labels
No labels
Stale
bug
config
discussion
duplicate
enhancement
experimental
feature
help-wanted
info
invalid
invalid
pull-request
question
up-for-grabs
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nbfc-hirschmann#972
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Maghsad on GitHub (May 3, 2021).
Original GitHub issue: https://github.com/hirschmann/nbfc/issues/1131
Describe the bug
It shows the CPU temperature when the "HP ENVY x360 Convertible 15-cn0xxx" profile is selected. However, it cannot read the fan speed (it says a high negative number: -10603.7%) and cannot control the fan speed.
To Reproduce
Install the NoteBook Fan Control
Select "HP ENVY x360 Convertible 15-cn0xxx" profile
Select Enabled
Expected behavior
Can read the current Fan Speed
Can Control the fan speed
System information
@Maghsad commented on GitHub (May 18, 2021):
No support or even any answers after half of a month?
@geonom commented on GitHub (May 24, 2021):
Hey there, open source means pushing devs is not an acceptable behaviour.
For your issue, I have the same notebook and just using a different profile - in my case "HP ENVY m6 1206dx" worked perfectly well.
Spoke to soon - after having changed the Thermal Profile in the HP command center, now I am stuck with 100% fan speed with the annotation critical ;)
There is something slightly buggy with how HP handles the fan speed - I had to switch to another HP model and back to the above and now it seems to work better for some unknown reason.
@github-actions[bot] commented on GitHub (Nov 22, 2021):
This issue is stale because it has been open more than 180 days with no activity. If nobody comments within 7 days, this issue will be closed