mirror of
https://github.com/hirschmann/nbfc.git
synced 2026-04-26 00:56:01 +03:00
[GH-ISSUE #10] NBFC prevents charging on Lenova Yoga 2 13 #11
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#11
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 @hugobuddel on GitHub (Jun 22, 2015).
Original GitHub issue: https://github.com/hirschmann/nbfc/issues/10
The fan sound of the Lenovo Yoga 2 13 (non pro) laptops are prone to be loud, as was the case with my Windows 8.1 laptop. Installing Notebook Fan Control unfortunately did not help in reducing the noise but instead prevented my battery from charging. Hovering over the battery icon in the tray would show "22% available (plugged in, not charging)". Charging resumed after uninstalling NBFC.
The root cause of the issue is unclear to me, maybe it's on Lenovo's side. (Well, the noisy fan certainly is.) However, it could potentially help other Yoga owners if it would be possible for NBFC to detect and warn about the problem.
An even more unlucky fellow on the Lenovo forums made me aware of the issue:
https://forums.lenovo.com/t5/Lenovo-Edge-Yoga-Lavie-Z-Flex/Yoga-13-and-battery-is-plugged-in-not-charging/m-p/1768703#M21346
@hirschmann commented on GitHub (Jun 30, 2015):
I’ve tried to gather some information about this issue and it looks like it is not solely related to NBFC.
It seems like tools which access or monitor the hardware provoke this issue, but sometimes it seems to appear pretty randomly.
I’m afraid the only one who can solve this problem is Lenovo.
@hugobuddel commented on GitHub (Jun 30, 2015):
Thank you for looking into it @hirschmann . The problem indeed seems kinda mysterious. Hasn't happened with my laptop since, hopefully it stays that way!