Jump to content

Fiery

Administrators
  • Posts

    11737
  • Joined

  • Last visited

  • Days Won

    503

Everything posted by Fiery

  1. Since the v7.50.7200 stable release we've revamped the way AIDA64 manages PNG images. So please upgrade to the latest beta version of AIDA64 Extreme available 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 if it helps.
  2. Thank you for your feedback!
  3. Awesome! Thank you for your feedback
  4. Please check the following new beta update of AIDA64: https://www.aida64.com/downloads/latesta64xebeta This version will turn the screen off when you close AIDA64 or when the computer goes to sleep. Let me know how it works.
  5. Are you sure it's the Turing device that wakes the system up? We've checked it with a 8.8-inch Turing screen and it never wakes the system up. What AIDA64 does is when it senses that the computer is about to go to sleep, it blanks the screen and stops communicating with LCD devices. And it only resumes handling the screens once the computer resumed back from sleep.
  6. About the first issue, please post a screenshot or photo of the System page of AIDA64. As for the second issue, fFor some reason not all devices can provide that information via the standard Android Battery API.
  7. We've implemented support for Turing (Turzx) LCD devices. Let's continue discussing Turing displays in their own topic:
  8. @Korvenwin @amuro1 @hardgamer @Loyd @mitrichonov @pgomespxo We've implemented support for Turing (Turzx) LCD devices. Let's continue discussing Turing displays in their own topic:
  9. @cyablo @FantaZimt @RoadBandito @TrueEddie @sherror @shinra1111 @ForumWT @ThomasK @JPC @Agrias @Dudleydogg We've implemented support for Turing (Turzx) LCD devices. Let's continue discussing Turing displays in their own topic:
  10. We've implemented support for Turing (Turzx) LCD devices. Let's continue discussing Turing displays in their own topic:
  11. @MJP @Damster @thehinac @fyrewyre @petrovv111 @Pepo @cyablo @Naudnaud @sherror @remekra @FiX @rydernword @Mrkillerhomer_xD @RaM @Slayver @ForumWT @Citywolf @ThomasK @KiKoMaSo @AndersDuda @Ultim8um @tibcsi0407 We've implemented support for Turing (Turzx) LCD devices. Let's continue discussing Turing displays in their own topic:
  12. We've implemented support for Turing (Turzx) LCD devices. Let's continue discussing Turing displays in their own topic:
  13. We've added support for Turing (Turzx) displays. It works with the following models: - Turing 2.1-inch (480x480 pixels) - Turing 3.5-inch (480x320 pixels) - Turing 5-inch (800x480 pixels) - Turing 7-inch (1024x600 pixels) - Turing 8.8-inch (1920x480 pixels) You can enable the LCD device from AIDA64 / Preferences / Hardware Monitoring / LCD / Turing. You can check it out in the latest AIDA64 beta build at: https://www.aida64.com/downloads/latesta64xebeta Please let us know if you find any difficulties enabling or using this new feature. Also let us know if you've got another kind of LCD device that is currently unsupported by AIDA64. Regards, Fiery
  14. Thank you! Please check the latest AIDA64 beta build too: https://www.aida64.com/downloads/latesta64xebeta I hope it works properly now
  15. Easter Sale is only for customers who have their licenses already expired, so may be up for a renew deal
  16. We will fix that it in the next AIDA64 beta update.
  17. Please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta Let me know if it helps.
  18. Thank you! We've cleaned up the SPD timing levels and correct the clock frequencies for DDR5 modules in the latest AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works.
  19. Does the UEFI Setup (BIOS) and CPU-Z show the clock frequency of your EXPO profile as 3000 or 3003 MHz? I assume AIDA64 is more precise in calculating the clock frequency based on the best (most ideal) latency value encoded in EXPO, that's why it shows slightly higher clock frequency. But, when you calculate latency timings using 3003 MHz, worse values may come out in the end compared to if you based your calculations on 3000 MHz.
  20. That happens because for some reason it's very slow to communicate with the BeadaPanel display. I'd try using a different cable. If that doesn't help, a different USB port on your computer. If that doesn't help, try to update the firmware of the BeadaPanel.
  21. We've replaced his latest version with your fixed version, so it's all fixed now
  22. We appreciate your attention to potential issues in the language module. In case your fixes are based on the latest beta, then we can join the 2 projects together. I just wanted to avoid you guys separately going on translating left and right, and then it would be impossible for us to come up with a single language module that we distribute as part of AIDA64.
  23. Please contact our Sales Department and ask for a refund: https://www.aida64.com/support/contactform
×
×
  • Create New...