Fiery

Are you using the latest AIDA64 beta build of v6.25.5434?

There's no generic rule or standard on that. You need to experiment a bit and watch how the values change when the SSD is under stress (e.g. doing a longer reading or writing session) and draw your own conclusion for your own drive.

We do not have such plans right now.

The first battery capacity value (labelled as "Capacity (Reported by Android)") comes from the Android profile of your device. It was encoded to the profile by the manufacturer of your device, and may or may not reflect an accurate value. The second value (labelled as "Capacity (From Database)") comes from the built-in AIDA64 hardware database, and should reflect the correct value.

In Photoshop try to do a quick export to PNG. That way the filesize will be less than 13 KiloBytes and will be easy to put on the SensorPanel. Let me know if it works out.

We've heard about such issues, related to PNG images exported from Gimp. If it's possible, please send me one or two of such PNG images that you cannot add to your SensorPanel in email to me. I'll send you my email address in private message. Thank you for your help!

GIF image format and any form of animations are not supported by the SensorPanel.

AIDA64 only supports a single Commander Pro unit.

Are you sure it's possible to 3rd party applications to put information on the LCD of the connector?

Please try to enable DIMM thermal sensor support in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64 to apply the changes. Let me know if it makes DIMM temperatures appear properly.

What's the value reported by AIDA64, what do you reckon the accurate value should be, and what version+build of AIDA64 are you using?

What motherboard and CPU do you have, and which version of AIDA64 are you using?

You're right, it doesn't cause any issues, but of course we will fix this in the PCI database of AIDA64 in the next AIDA64 beta update.

The mentioned new AIDA64 beta update is now available for download at: https://www.aida64.com/downloads/latesta64xebeta

It's implemented in the latest AIDA64 beta update available for download at: https://www.aida64.com/downloads/latesta64xebeta

We're not quite sure why it happens and at what point of Windows 10 development this was introduced, but when you right-click on the Windows Desktop or on a Desktop icon, Windows takes away the always on top setting from the SensorPanel window, and it wouldn't give it back after the right-click context menu gets hidden. The SensorPanel however detects that it no longer has the always on top setting (even though you have it configured in the AIDA64 Preferences for it), and it reconfigures its own window to have it back. It then causes the right-click context menu shown by Windows on the Desktop to vanish. Very weird, but so far we haven't found a perfect solution to get around this. Because if the SensorPanel window doesn't detect its own always on top state change, the always on top behavior will stop working after you press a right-click on the Windows Desktop or on a Desktop icon

Rendering the LCD layout could well cause power consumption spikes, since it consumes system resources to render the LCD layout.

Do you find a pattern across those different systems you've mentioned, like a common hardware component? Maybe they both have the same Radeon video card?

If you deem it's an incorrect reading, then just ignore it and focus on the other thermal readings.

It's not written in stone yet. We're planning to do a release before September, but we'll see how it turns out.

Thank you. Do you think the EK Loop Connect device appears as YiMing 1840 as a connected USB device?

Yes, either Odospace is the solution or the RemoteSensor feature:

I'm afraid I have no idea what could be going wrong in those instances My best guess would be a collision with another software, but it's just a guess.

As for CPU temperature, your motherboard cannot measure that. But you can re-assign the missing reading to another CPU thermal reading like CPU Package by right-clicking on the CPU temperature bar --> Modify. As for GPU temperature, I suppose you use the integrated Intel GPU and not have a video card. In which case you can re-assign the missing reading to another GPU thermal reading like CPU GT Cores or iGPU by right-clicking on the GPU temperature bar --> Modify.

Please try to close CAM and right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery