Jump to content

Fiery

Administrators
  • Posts

    11540
  • Joined

  • Last visited

  • Days Won

    488

Everything posted by Fiery

  1. We've replaced his latest version with your fixed version, so it's all fixed now
  2. 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.
  3. Please contact our Sales Department and ask for a refund: https://www.aida64.com/support/contactform
  4. 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 device (in your case Samsung) didn't encode the info there, then sysinfo apps cannot read or detect it.
  5. Awesome, thank you!
  6. Thank you, but the language module was already updated in the latest beta. It's maintained by another AIDA64 fan.
  7. That's fair. Thank you for giving our software a chance though.
  8. Can you please explain the steps you perform to import the .sensorpanel file of your choosing?
  9. Please let us know how to implement touch support for your new generation displays. For Matrix Orbital EVE displays we use touch facility to scroll between LCD pages. When the user touches the left 25% of the screen, AIDA64 switches to the previous LCD page; and when he/she touches the right 25% of the screen, AIDA64 switches to the next LCD page. It would be great to implement similar functionality for BeadaPanels too.
  10. I'm afraid the issue you're experiencing is too generic, so it would take a lot of efforts on your part to dig down deeper, e.g. disable various modules of AIDA64 to try to pinpoint the reason of the error message. If you're up for it, we can go down that path, but I still cannot guarantee that we could find the bug that way So in case you have a sour taste in your mouth about the $$ investment, then perhaps the best way for you is to get a refund and find another solution.
  11. Thank you for your kind words.
  12. I'd do at least a few hours. Even better if you could let it run through the night.
  13. We're working on it. Please note that what seems like a single display is actually a large family of displays with at least 5 different communication protocols. So in order to support all Turing/Turzx displays, we need to do a lot of research and development.
  14. Yes, it is. You may want to try it with factory default settings. It should work properly then, without hardware issues.
  15. With some unstable configurations AIDA64 can detect a glitch in the form of a calculation error. While in the vast majority of cases when the CPU makes a calculation error, it goes completely haywire and either Windows throws a BSoD, or the computer locks up, or the computer suddenly restarts.
  16. In that process have you updated to the latest Adrenalin driver version of 24.12.1 WHQL?
  17. What do you mean by "stuck" ? Please explain it with more details.
  18. Please try the following: 1) Upgrade to the latest AIDA64 beta update: https://www.aida64.com/downloads/latesta64xebeta 2) When the issue of the SensorPanel appearing on the wrong monitor occurs, in AIDA64 please press Ctrl+D --> System Debug --> Devices Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery
  19. @TheRealGD2X Both of you, please try the following: 1) Upgrade to the latest AIDA64 beta update: https://www.aida64.com/downloads/latesta64xebeta 2) When the issue of the SensorPanel appearing on the wrong monitor occurs, in AIDA64 please press Ctrl+D --> System Debug --> Devices Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery
  20. The issue is fixed in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta
  21. In AIDA64 please press Ctrl+D --> 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
  22. I've sent you your product key in email.
×
×
  • Create New...