Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12004

  • Joined

  • Last visited

  • Days Won

    524

 Content Type 

Everything posted by Fiery

  1. Fiery
    Do you own one?
  2. Fiery
    Such issues could occur on Asus ROG motherboards when a reading comes from the EC (Embedded Controller). Polling for EC registers could collide with background Asus processes/services as well as activities of the BIOS itself. So far we haven't found a 100% reliable way to avoid such collisions
  3. Fiery
    Yes, we've heard about such issues when using SPF devices with Win10, but so far we haven't found a resolution
  4. Fiery
    Indeed, those values do not back the theory of why it takes so much time to update the SensorPanel on your system. Unless of course the SensorPanel rendering itself takes a lot of time in case you have a complex layout.
  5. Fiery
    Do you mean you'd like to add new LCD layout items via a quicker method -- or move existing items to a different place using a quicker method?
  6. Fiery
    Refresh rate is always higher than the configured value, because collecting sensor readings takes time. In your case I suppose it takes 200 to 400 milliseconds to collect all sensor readings. You can verify that by right-clicking on the bottom status bar of AIDA64 main window --> Sensor Debug --> Sensor Profiling Dump. Smooth transition is not supported by the SensorPanel/LCD bars right now.
  7. Fiery
    Try to enable Samsung LCD support in AIDA64 first, and check if the display appears in the Device Manager as an unknown device. When it does, you can install the driver for it.
  8. Fiery
    I'm afraid we cannot do that until we revamp the LCD configuration part of the Preferences panel. Currently there's no room for the LCD options to be quadrupled. Even the four LCD type dropdown lists are a bit of a stretch right now, since it's not explained at all why there are four of them. --- As for the temperature sensor crash, does it crash the whole system or only AIDA64 crashes? What motherboard, CPU and video card(s) do you have in your system, and do you have any external storage devices connected?
  9. Fiery
    Thank you for your feedbacks. 1) About the SPD issue, please post an updated SMBus Dump (Full) dump. 2) As for the crash on the Computer / Sensor page, does it happen in all cases (when you go to the Sensor page), in the same manner?
  10. Fiery
    When that anomaly occurs, it seems for some reason AIDA64 is unable to communicate with the primary sensor chip of your motherboard. Do you have any other monitoring software running in the background that may interfere with AIDA64?
  11. Fiery
    SMBIOS specification doesn't define LPDDR4X, but only LPDDR4. DMI tables are filled in during the bootup process by the BIOS.
  12. Fiery
    LPDDR4X RAM is BGA, and has no SPD chip attached to it. The memory information comes from DMI, and you can check it out on the Computer / DMI page in AIDA64.
  13. Fiery
    Power measurements are displayed on the Computer / Sensor page of AIDA64.
  14. Fiery
    The above mentioned new AIDA64 beta update is available for download at: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works.
  15. Fiery
    The above mentioned new AIDA64 beta update is available for download at: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works.
  16. Fiery
    We've managed to fix the SPD issue while we're struggling to find out what's wrong about the BCLK measurement technique we use. We keep looking into it... Make sure to upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works.
  17. Fiery
    Pressure sensors and water quality sensors are not supported by the SensorPanel.
  18. Fiery
    Does the artifact happen only when you adjust the display brightness? So if you don't touch that setting, the artifact never comes up?
  19. Fiery
    Ah you mean the virtual COM port. Well... Right now we're not planning to unlock interfacing with the EVE2/EVE3 displays using 2 different protocols (USB and virtual COM port). The Preferences page for EVE2/EVE3 configuration will already be complex due to the handling of 4 displays.
  20. Fiery
    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. If it's possible, please try to assure that both fans are spinning while you're making those dumps. Thanks, Fiery
  21. Fiery
    The next AIDA64 beta will support up to four EVE2/EVE3 displays Numbering them is not possible, since the interface is not serial. So you gotta play around and see which one is which by putting something unique on each of the 4 layouts you will build for your EVE2 displays.
  22. Fiery
    We're not planning to enable multi-display support for other Matrix Orbital LCD protocols. Can you please explain what you mean as "COM number at EVE" ?
  23. Fiery
    The EVE2 controller only supports up to 16-bit color depth so RGB888 is not possible. I'm not sure if Matrix Orbital improved on that with the EVE3. AIDA64 renders the image that's sent to external displays the same way, so there's no special trick or dithering used on EVE2.
  24. Fiery
    Please note that on many devices the standard Android Battery API is inadequately implemented, and fails to provide proper charge counter information for the battery.
  25. Fiery
    Awesome
×
×
  • Create New...