Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12179

  • Joined

  • Last visited

  • Days Won

    536

 Content Type 

Everything posted by Fiery

  1. Fiery
    There's no fix for that I'm afraid. On its Nexus and Pixel devices Google -- for whatever reason -- decided to further limit apps access to certain system directories, like the ones necessary for temperature measurement. So now it's not possible to read any temperatures but the battery temperature. It applies to any apps running on your device, not just AIDA64.
  2. Fiery
    Generally speaking, AIDA64 supports more sensor devices than HWMonitor, and collects more sensor readings from those devices. It may not explain the higher CPU load on your particular system configuration though. For example, on my main work computer, which is a Core i7-6700K + Gigabyte Z170X-UD3 based run of the mill desktop PC, both AIDA64 and HWMonitor consumes cca. 2% CPU cycles, both with 100 milliseconds update rate. There's no noticable difference between their impact on the system. You can lower the 1000 millisec update rate to 100 millisec in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Update Frequency. You can track Current / Minimum / Maximum / Average readings by using the Statistics tab of the AIDA64 System Stability Test feature that you can launch from AIDA64 / main menu / Tools. Regards, Fiery
  3. Fiery
    Such anomaly could indeed happen when you connect/disconnect external drives on-the-fly. It's not possible to lock the drives to a particular ID, but we can check what's happening with your drives in details, and possibly come up with a workaround. Because external drives are supposed to be the last ones in the list of drives, and so the IDs for the internal drives shouldn't be affected by connecting/disconnecting external drives. Maybe in your system the internal and external drive IDs are mixed together for some reason. 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. Finally, 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. Please repeat those dumps after disconnecting your external drive, so we can check how the list of drives and their IDs change. Thanks, Fiery
  4. Fiery
    Yes, those sensor items are already available in the System category. They're called: Desktop Resolution and Vertical Refresh Rate
  5. 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
  6. 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.
  7. Fiery
    Great, thank you for your feedback
  8. 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.
  9. 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
  10. 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.
  11. 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.
  12. 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?
  13. 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.
  14. 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.
  15. 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
  16. 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%.
  17. 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
  18. 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.
  19. 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.
  20. 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.
  21. 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.
  22. 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.
  23. 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?
  24. 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.
  25. Fiery
    We've found something... Do you have a video card that supports iCX?
×
×
  • Create New...