-
Notifications
You must be signed in to change notification settings - Fork 6
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
High CPU when adjusting brightness #2
Comments
Hey, thanks for bringing this to my attention. I used XCode Instruments to check the CPU usage with and without the tweak. I found that it does not really differ a lot with and without. The processes I pushed an update to packix today (version 0.1.2), maybe that solves your issue. I added some code to avoid making system calls which probably put a big load on |
Thanks I'll check it out. I was using cocoatop and battrate tweak to show current drain rate. I didn't notice issues the first couple days I was using your tweak (it seemed smooth) but then for some reason yesterday it was being really bad while I was in an app adjusting brightness, the slider wasn't smooth and the phone was getting hot etc every tune I adjusted it so I realized something was wrong. That's when I tried repeatedly enabling and disabling the tweak and saw that it consistently was much better when disabled. I'll try the new version though. |
I’m not seeing the new version available yet.. it shows in the change log but the updated file isn’t appearing in the repo edit: nevermind it just showed up now |
Still seeing the issue on the new version unfortunately I forgot to say my device details: iOS14.4.1 iPhone X |
Hey, i finally got around to testing it out with the tools you mentioned ( |
When I adjust the brightness while tweak enabled, the CPU usage explodes very high. I especially notice while in another app. The slider movement is a bit jerky and my batt rate display indicates massive battery drain as I move the brightness slider up and down. I tested repeatedly with this tweak enabled and disabled and concluded the issue must be caused by this tweak.
The text was updated successfully, but these errors were encountered: