Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    11546

  • Joined

  • Last visited

  • Days Won

    489

 Content Type 

Everything posted by Fiery

  1. Fiery
    Please right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> ATA 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. Then right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> SMART Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Then right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> RAID Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Finally, right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> Disk Controllers Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery
  2. Fiery
    We don't really want to implement separate indicators. It would involve adding 48 new sensor items (6 reasons multiplied by 8 GPUs). We're thinking more in the line of simply returning the reason bit mask as it is passed by ForceWare. It would work like: a value of 1 means Power Limit, 2 means Temperature Limit, 4 means Reliability Voltage, 16 means Utilization, etc. A value of 3 would mean Power Limit + Temperature Limit occuring in the same time, and a value of 7 would mean Power Limit + Temperature Limit + Reliability Voltage occuring in the same time. I'm not sure however how you could define a proper LED colour assignment to make it useful for your purposes.
  3. Fiery
    Great, thank you for your feedback
  4. Fiery
    It's definitely not normal. It didn't behave like that the last time we've checked. We haven't altered the Razer LCD module of AIDA64 recently at all. Maybe Razer messed up something in the Razer SwitchBlade UI API or in the Synapse module. We'll check it out on an up-to-date Windows 10 installation, along with the latest Synapse release. I'll let you know about our findings in this topic. Please give us a few days to set the whole thing up.
  5. Fiery
    We've added the Performance Cap Reason information to the Display / GPU page in 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. It can indeed have multiple reasons combined as a bit mask, so it's not trivial how to add that to the existing LCD and SensorPanel modules. We'll think about it
  6. Fiery
    We've added the requested information to the Display / GPU page in 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 how it works. We're planning to add it to the SensorPanel and other modules as well, but first we need to figure out how to implement it in a useful way.
  7. Fiery
    AIDA64 does support remote connections through WiFi via the RemoteSensor module, but I don't think you'd have a http client on your device Let us know more about the protocol we'd need to use to talk to the mentioned ESP8266 MCU.
  8. Fiery
    I'm not sure how that issue affects AIDA64. Can you please tell us more about the readings in AIDA64? Do we need to fix anything?
  9. Fiery
    You can save the Desktop Gadget settings by backing up the AIDA64.INI file that you can find in the installation folder of AIDA64 (e.g. C:\Program Files (x86)\FinalWire\AIDA64 Extreme). As for slow updates, make sure to check if the Desktop Gadget update frequency is properly set in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Update Frequency.
  10. Fiery
    AIDA64 reports the cameras as the standard Android Camera API manages them. AFAIK all dual-cameras are handled as a single camera by Android.
  11. Fiery
    Basically, no, there's no way to do that I'm afraid. But, there's something we can do about such issues: I've sent you a private message about it
  12. Fiery
    System availability indicates the percentage of a day that your system is up (online, in use). So for example, if you use your computer between 8am and 4pm every day, including weekends and holidays, your system availability will be 33% (8 hours out of 24 hours). If you however use your computer only between 8pm and 10pm on Saturdays and Sundays only, then your system availability will be 2%.
  13. Fiery
    We've implemented the requested feature in the latest AIDA64 beta update: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works
  14. Fiery
    First, you need to configure the right resolution for your display (let me know if you need guidelines on how to do that). When you've done that, the LCD preview will show you the same layout that you can see on your phone. However, when the LCD preview layout only has the top-left corner populated, it is normal that it looks tiny on the mobile device. In which case you need to use larger font sizes to assure proper legibility on the smaller screen of the mobile device.
  15. Fiery
    Not yet. M.2 SSD temperature measurement works fine already, but not when those drives are part of a NVMe RAID array. We'll work on it in the upcoming weeks.
  16. Fiery
    It's not the basic idea of power efficiency that we find problemous. The issue is with the AXi firmware that produces incorrect (unrealistic) overall power output values. And if you base your efficiency calculation on an incorrect value, the end result will also be incorrect.
  17. Fiery
    We'll decrease the minimum update rate to 0.1 sec (from the current 1 sec) in the next AIDA64 beta update that is rolling out later today.
  18. Fiery
    I don't think that's necessary, since you can easily estimate the update frequency by looking at the frequency of values. So e.g. if you have 5 updates with the same HH:MM:SS value, then the actual update rate is 200 millisec.
  19. Fiery
    What laptop do you have? Does it reboot while AIDA64 is showing its splash (welcome) screen? If so, then what's the last message you can see displayed on the bottom of the splash screen?
  20. Fiery
    No, we haven't changed anything about it. But we've already seen overheating issues about Samsung SPF devices. So in case the ambient temperature got hotter around your device, that may cause the hangs after a period of time.
  21. Fiery
    We've found something... Do you have a video card that supports iCX?
  22. Fiery
    That's definitely not normal. Do you mean that while you have AIDA64 running, Windows 10 pops up message boxes about finding new USB hubs every few seconds? If yes, then do you have all Windows 10 updates applied, and have you tried to restart Windows? Also, do you have an external USB device connected to your PC that's not a mouse or keyboard? Printer, external card reader, flash drive, external HDD/SSD?
  23. Fiery
    Such issues can happen when Windows gets mixed up after upgrading AIDA64 from an old version to a new one -- or when one of the drivers get updated by Windows Update or manually by the user. In most cases restarting Windows fixes everything. That's why we always recommend AIDA64 users to restart their system after updating AIDA64 to a new release.
  24. Fiery
    36:3 is normal for a configuration with 100 MHz BCLK and DDR4-2400 RAM (running at 1200 MHz). Regards, Fiery
  25. Fiery
    It must be due to a system pecularity that is specific your particular device. We'll try to get a similar device to check it out. On our existing devices, including a Snapdragon 810 based Nexus 6P (running Android O DP2 right now), we can see no such issues. On our Nexus 6P all 8 cores are properly measured. Before the Android O update, it used to work properly with Android 7.x and Android 6.x as well.
×
×
  • Create New...