You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MacBook Air M1 16GB
macOS Sonoma 14.6.1
The temperature in the graph view shows temperatures that are clearly beyond reason. However, they are not visible when selecting which sensors to use, so the information from them is either discarded or hidden (on purpose or not -- doesn't matter)
Therefore, it would be nice to remove them from the graph view too
[Note: I'm talking about sensors TR3d and TR1d]
Moreover, when sorting temperature from sensors in descending order, I can see that some sensors are giving off some sort of "default" values, that are usually precise to 0.00 (e.g. 30.00) and are changing very rarely. hence, I can deduce that these also don't show any realistsic values, yet I'd assume they are used in the calculations and are shown. For clarity, the temperature in the room is about 26°, but it's the precision and lack of change that gives off 'broken' vibes.
Some of them are even showig negative values, but are changing, weirdly enough
Moreover, the average temperature also seems to be, to say the least, 'off'. It has been showing ≥100°C since I installed it, and yet the laptop is barely hot in the warmest places. I understand, that my laptop doesn't have active cooling system, nor are the sensors placed on the surface, but it would be weird if in such a thin casing the difference between externals and internals were so drammatic (40° is a heck lot for ≤10mm of thickness without the lid/screen)
To be clear, I'm not "complaining", I understand the difficulty of development a project that has to be compatible with so many devices, I'm just pointing out to the issues which could have been overseen. If I knew any Swift, I'd probably try my best to contribute more, but this is about as much as I could do. If you need any further logs, don't hesitate to contact me. Good luck!
The text was updated successfully, but these errors were encountered:
KirillSchmidt
changed the title
Impossiblly high and low temperatures
Impossiblly high and low temperatures M1 Air
Sep 17, 2024
MacBook Air M1 16GB
macOS Sonoma 14.6.1
The temperature in the graph view shows temperatures that are clearly beyond reason. However, they are not visible when selecting which sensors to use, so the information from them is either discarded or hidden (on purpose or not -- doesn't matter)
Therefore, it would be nice to remove them from the graph view too
[Note: I'm talking about sensors TR3d and TR1d]
Moreover, when sorting temperature from sensors in descending order, I can see that some sensors are giving off some sort of "default" values, that are usually precise to 0.00 (e.g. 30.00) and are changing very rarely. hence, I can deduce that these also don't show any realistsic values, yet I'd assume they are used in the calculations and are shown. For clarity, the temperature in the room is about 26°, but it's the precision and lack of change that gives off 'broken' vibes.
Some of them are even showig negative values, but are changing, weirdly enough
Moreover, the average temperature also seems to be, to say the least, 'off'. It has been showing ≥100°C since I installed it, and yet the laptop is barely hot in the warmest places. I understand, that my laptop doesn't have active cooling system, nor are the sensors placed on the surface, but it would be weird if in such a thin casing the difference between externals and internals were so drammatic (40° is a heck lot for ≤10mm of thickness without the lid/screen)
To be clear, I'm not "complaining", I understand the difficulty of development a project that has to be compatible with so many devices, I'm just pointing out to the issues which could have been overseen. If I knew any Swift, I'd probably try my best to contribute more, but this is about as much as I could do. If you need any further logs, don't hesitate to contact me. Good luck!
The text was updated successfully, but these errors were encountered: