Fiery

It would definitely require either: 1) You develop a firmware/program for your microcontroller to suit one of the existing external LCD display protocols that AIDA64 supports. For example, you can choose the Pertelian or Matrix Orbital protocol. They're both widely used in 3rd party displays. One advantage of this path is that for test runs you can use either AIDA64 or LCD Smartie while you develop your protocol, and you don't necesserily need any input from us, neither you need to wait for us to alter AIDA64 to make sure it works with your display. 2) We (you + us) come up with a proprietary protocol, one that is the most suitable for your display. However, in order to do this, we may need to develop a device emulator or have a sample of the final version of the hardware that you're developing. This one is a much more difficult solution, since it requires a lot of efforts on both ends (you + us).

Thank you for your feedback. I've sent you an email.

Yes, but first we need to find out whether the register readout works on your video cards. Both of you, please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA SMBus 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

Please submit a report from the About page of our app, and we'll take a look at it. You can also contact us directly in email in case you have a technical question about our app

Thank you! In order to have a reference set of readings with 100% accuracy, can you please also post a screen shot of Gigabyte's own monitoring utility of the UEFI Setup (BIOS Setup) where the temperature, voltage and fan RPM values are shown?

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 --> SMBus Dump (Full). Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery

The mentioned new AIDA64 beta update is available for download at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works

The mentioned new AIDA64 beta update is available for download at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works

I'm sorry for the delays. Here it is: https://www.aida64.com/downloads/latesta64xebeta

Please note that in order to detect the missing details, the camera ID information had to be previously encoded into the Android profile of the device. When the manufacturer of the devcie (in your case Meizu) didn't encode the info there, then sysinfo apps cannot read or detect it.

It's not only about users' perception. We also would feel a jerky animation unsuitable for the generic quality of our software.

Yes, because it would look bad with no anti-alias support

When I said CRC above, I meant hash (SHA).

Yes, we sadly couldn't finish it up before having to finalize AIDA64 v5.92. We'll work on it as soon as we can get a X299 motherboard, which would be an ideal platform to work on this matter.

AIDA64 detects the current Windows Desktop layout when you start it up, and when it detects that the previous position where you've left the SensorPanel at no longer falls into the visible Desktop area, it will reset the position to (0,0) -- which is the top-left corner of the primary monitor. In your case the problem might be that when AIDA64 starts up, Windows still didn't restore the previous Desktop arrangement, and the Desktop area doesn't yet cover the secondary display. Can you please check if the issue only happens when you restart (or cold start) your computer, or it happens also when you keep your computer running and only restart AIDA64?

Make sure to upgrade to the latest version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xe After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if the problem persists.

Thank you. We will fix the issue in the next AIDA64 beta update. I'll post a message into this topic once the new beta is available for download.

Thank you for the report! Reading that temperature would involve EC (Embedded Controller) bank switching, which is a dangerous thing to pull off, especially when AI Suite is installed. Or when AI Suite may leave behind its services after uninstallation...

I'm sorry for the delays, and thank you for the dumps. I'm afraid neither of the RAID codepaths AIDA64 currently features supports your RAID controller. We'll try to find out how to handle it.

Thank you. Sadly, Aquaero uses a slow USB protocol, and there's nothing we can do to get around that limitation

Sadly, not all Adaptec controllers are handled properly by AIDA64 at this time. So it's best not to pretend it supports all Adaptec RAID controllers

Multi-GPU support can be dangerous with ULPS-enabled CrossFire setups, but it is fine to have enabled with SLI

That indeed looks very weird. We'll need to see the before & after dumps to find out more about the root cause of the issue.

We don't use an offset for the "CPU" value. AIDA64 should show the same value that Gigabyte's own monitoring software displays as "CPU" temperature.

Thank you. We will fix the issue in the next AIDA64 beta update. I'll post a message into this topic once the new beta is available for download.