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
    We're planning to roll out the next AIDA64 stable update sometime during the upcoming 4 weeks.
  2. Fiery
    Try to scan eBay using "7-inch TFT LCD" and "8-inch TFT LCD" as search queries. Some of those may fit your needs as well as fit into your case
  3. Fiery
    Linux kernel will allocate cache buffers during the bootup process. So it's normal that most of the RAM is already taken (allocated) when the Sailfish OS boots up. The two battery temperature readouts are because AIDA64 reads temperature measurements using 2 interfaces. The first one is the thermal zones method, which provides a bunch of readings. The list of readouts via that interface may or may not include the battery temperature. So in order to assure that AIDA64 can measure the battery temperature specifically, it will use a second interface to read the battery temperature. When the battery temperature is provided by both interfaces, "Battery" is listed twice on the Thermal page.
  4. Fiery
    The documentation (https://open.uappexplorer.com/submit) on the OpenStore website clearly states that: Since our app would require a manual review (due to the special permissions it has to request), the last point applies to it. And since it's not open source, it cannot be submitted to manual review. So effectively, it cannot be published in the OpenStore.
  5. Fiery
    It's not easy to pick a screen that you've described. When it comes to large colorful LCD displays, we generally recommend to simply pick up a second-hand 15-inch or 17-inch classic TFT LCD monitor that you can connect via DSub, DVI or HDMI to your computer, and simply use the SensorPanel module of AIDA64 (instead of the External LCD module). Such a solution is cheap as chips these days, and gives you a lot of flexibility, since the monitor simply extends your Windows Desktop. And that means you can put any window or any software's user interface on the secondary screen. So you're not tied to AIDA64 and you can use the display for multiple purposes at the same time as well, ie. to share the display area between the AIDA64 SensorPanel and another window. Of course a classic TFT LCD monitor would require an external power source, so it may not be ideal for your purposes. There are USB-connected displays these days that don't require a separate power input, but they may be too expensive. 2 examples of such a display: https://www.asus.com/Commercial-Monitors/MB168BPlus/ https://www.asus.com/Monitors/MB169C-plus/
  6. Fiery
    Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). 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. BTW, has the total system memory amount increased after you've installed the new memory module? Thanks, Fiery
  7. Fiery
    In theory, any PCIe M.2 SSD should work, as long as it physically fits there. But notebooks can be challenging systems when it comes to hardware upgrades. So there's absolutely no guarantee that 960 Evo would work there.
  8. Fiery
    We'll do our best This is a really new and strange issue to us. We basically needed to come up with a virtual SMBus layout to emulate the 4 memory channels that your motherboard offers. That's because the Skylake-X memory controller manages the SPD channels as if the CPU had only 2 memory controllers. Very odd...
  9. Fiery
    Perhaps Asus removed VRM temperature reading from the BIOS Setup on all versions of your motherboard. AIDA64 fortunately doesn't care about the BIOS version nor the motherboard version. It simply tries to read the corresponding register from the sensor chip, and when it holds a meaningful value, it shows it.
  10. Fiery
    Your notebook features an Intel Sandy Bridge class iGPU that doesn't support OpenCL. AIDA64 GPU stress test and GPGPU benchmarks require a GPU that supports OpenCL.
  11. Fiery
    The Ubuntu Touch OS has been discontinued, and no new devices are rolling out to feature the last release. We will only resume further developing our Ubuntu Touch app in case the OS itself gets further developed and enhanced.
  12. Fiery
    AFAIK OpenStore doesn't accept app submittals that require special permissions and that are not open-source. Due to its nature of being a sysinfo/diagnostic tool, our app requires special permissions, and we're not planning to publish its source code. Hence I don't think our app can ever get to the OpenStore.
  13. Fiery
    Thank you for your feedback.
  14. Fiery
    Try to enable the 2 options about EC in AIDA64 / main menu / File / Preferences / Stability: Embedded Controller (EC) support Embedded Controller (EC) bank switching After altering those options, make sure to restart AIDA64 to apply the changes.
  15. Fiery
    1) The Platform ID is read from the underlying Android subsystem, and it may or may not refer to the actual SoC of the device. For Qualcomm SoCs the platform ID usually refers to a family of SoCs. In your particular case Platform shows that your MSM8956 SoC belongs to the Qualcomm MSM8952 family of SoC's. 2) The system memory is managed by the underlying Linux kernel. And the Linux kernel tends to "eat up" (in other words: fully utilize) the available system RAM for caching. When a certain process is launched or a running process tries to allocate a portion of RAM, the kernel frees up some buffers to provide spare memory for the new allocation. What you experience on your device is absolutely normal for a Linux kernel based system. 3) We cannot reproduce the bug on our own Sailfish OS based test devices (Jolla Phone, Jolla C, Jolla Tablet). We'll reinforce the exception handling of the System Files page in a hope that it will fix the issue on your Xperia X device. Thank you for submitting your report to us!
  16. Fiery
    Please check the latest AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta
  17. Fiery
    Thank you. 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.
  18. Fiery
    We've rolled back the Areca RAID controller related improvements of the latest 2 beta updates. So when it comes to Areca controllers, the following new AIDA64 beta build will act just as Beta Build 4522: https://www.aida64.com/downloads/latesta64xebeta
  19. Fiery

    Aquacomputer MPS

    Fiery replied to Dav''s topic in Bug reports

    Thank you for the dump. The MPS device looks a bit suspicious though. It may feature a more recent firmware than what we've seen so far. We'll do some further test runs using our MPS device to find out more about this anomaly.
  20. Fiery
    The detected memory CRC error can mean either a RAM issue (ie. the RAM modules provide the wrong data to the CPU), or a glitch in the path between the RAM modules and the CPU (ie. the data cannot travel safely between the RAM and the CPU pipelines), or a CPU computation issue (ie. the CPU fails to use the data properly and makes computation errors on the data). Note that the data has to go through the connection between the IMC (integrated memory controller -- can be found in the CPU package for modern processors) and the memory modules, then travel to the LLC (last level cache -- in most cases it's the L3 cache), then travel one level up on the cache level (ie. into the L2 cache), then again one level up (ie. into the L1 data cache), and only then can be used by the CPU. Through all those steps a glitch can occur anywhere, but it's not possible to know at which point the data gets corrupted due to excessive overclocking or too agressive timings.
  21. Fiery
    Please check this (3rd party made) solution:
  22. Fiery
    Intel RST and the different modes that an Intel SATA controller could operate in are the key factors to those anomalies. It's less to do about the firmware version used. The firmware update may have triggered RST to reenumerate the connected drives, and/or triggered Windows to install a different driver for the SSD device. The whole storage subsystem of Windows is a big mystery with a lot of variables that change across not just major Windows releases (like going from Win7 to Win10), but also between major Win10 updates and RST versions as well. You may try to find the root cause of the whole anomaly, but IMHO it's not worth the hassle. Just leave the two RAID options enabled on all your systems, and only disable them if you experience any issues. Such an issue could be when on the splash screen AIDA64 displays Scanning RAID Devices and stucks there, never being able to step further on the initialization process. But that fortunately is not a common occurence
  23. Fiery
    The "SCSI\" prefix in the hardware ID indicates that your drives are not connected via a standard IDE or AHCI mode SATA controller, but to a RAID controller or special SATA controller. In which case you need to enable both the following options in AIDA64 / main menu / Preferences / Stability. RAID member enumeration RAID SMART support Please note that you need to enable those even if you don't have a RAID array in your system. If enabling those options and restarting AIDA64 still wouldn't fix the issue, then please 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. 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 --> Disk Controllers Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Those debug outputs would be a great help for us to understand the nature of the issue. Please note that you don't need to perform those dumps for the system (Win10) where everything works properly, but only for the system (Win7) where you have one or more drives missing from the SMART readout. Thanks, Fiery
  24. Fiery
    Thank you. 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. Then 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. Thanks, Fiery
  25. Fiery

    Aquacomputer MPS

    Fiery replied to Dav''s topic in Bug reports

    Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Aquaero 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. Thanks, Fiery
×
×
  • Create New...