Fiery

I'm afraid no, since animations are not supported by the SensorPanel.

You need to have AIDA64 running to have the SensorPanel working. You can double-click on the AIDA64 System Tray icon to hide and show its main window.

M.2 temperature is measured by your motherboard and it uses a thermal sensor near one of the M.2 slots. What motherboard do you have? Maybe on your motherboard that reading shows an incorrect (bogus) value and should be removed.

What's wrong about your ASRock motherboards?

If you're running the latest version of AIDA64, you can push the Reset position button in AIDA64 / main menu / File / Preferences / Hardware Monitoring / SensorPanel to fix that up.

We've checked and HAMP fan measurement should work properly. We may find a trick there if you could kindly submit an ISA Sensor Dump and an Embedded Controller Dump. Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor 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. Also right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery

We've fixed issue 1, 2 and 4 in the latest AIDA64 beta update: https://www.aida64.com/downloads/latesta64eebeta We currently have no information on a potential mutex on your motherboard. Also, on several recent AMD Zen processor based systems the CPU firmware is actively blocking access to the SMBus and so far we haven't found a method to get around that limitation.

We've fixed it in the latest AIDA64 beta update: https://www.aida64.com/downloads/latesta64xebeta

Riing Quad seems to use a new protocol that currently is not supported by AIDA64. We'll order a Riing Quad set and check out the controller's new protocol and will implement support for it if possible.

If you could kindly ask one of your contacts to contact us about this matter, that would be very helpful.

I've sent you a private message about this.

It's not possible to measure individual core temperatures on AMD processors.

I think it may just work as is right now. Just select an EVE3 display with the same resolution. Have you tried it yet?

It's not the memory module per se, but more the fact that your motherboard uses a proprietary and quite unique, EC (Embedded Controller) based sensor solution that is not yet supported by AIDA64. We'll work on it as soon as we can gather the necessary technical information on the EC of your motherboard.

It's actually absolutely normal. On many 4K devices (e.g. Sony Xperia Z5 Premium) and 4K displays, Android itself uses 1080p resolution for apps, and will only switch up to the full 4K resolution mode when you're watching a movie or looking at photos.

Power draw of individual components are supported already as long as they provide such a measurement. And no, and it's not possible to show a total power draw for the whole computer because it's not possible to measure power draw of every component in a PC.

We only show official codenames of Android releases.

We can support it as long as it can run our existing Tizen phone app or Android app.

The list of apps shown on the Apps page would be a lot longer if it included system apps. We may add them as a separate list below the current one.

Check Matrix Orbital's EVE3 Series too.

AIDA64 for Android will show you the properties of the default screen, as the device came from the factory.

Please post a System Debug / PCI Dump as well. Thanks, Fiery

Where is your flow sensor connected to? Motherboard? An AquaComputer device? Maybe something else?

What sensor readings do you miss from AIDA64?

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> nVIDIA GPU Registers. 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. BTW, is the memory clock reported incorrectly when your video card is under load? Does GPU-Z report the same as Afterburner or the same as AIDA64? Thanks, Fiery