Jump to content
AIDA64 Discussion Forum


Popular Content

Showing content with the highest reputation since 04/12/17 in all areas

  1. 7 points
    My Custom sensor panel, in the style of Asus' AI suite. It's 800 x 460 as this will be displayed on an in-case LCD-screen. The dials on top are dynamic, as well as the animated fan icons. I'm quite pleased with it. In case anyone's interested, I'll post a picture with the final result!
  2. 3 points
    We wanted to wait to tell final judgement on this issue until we have more info and more input. It's a Windows 10 bug indeed that plagues Windows 10 Insider Build 16273 and 16275, but only the 64-bit editions. It prevents certain software to install and use its otherwise perfectly fine kernel driver. The issue affects several software, not just AIDA64. We're already working on a workaround, but we also expect Microsoft to fix this up soon. I'll post a message into this topic once we have an update.
  3. 3 points
    After buying a new comp i was started with modding. More info - http://nl.hardware.i...irus_59-edition SilverStone Fortress FT03 Black + MIMO 720F Touchscreen USB Monitor (7" 800x480) He was supposed to be better than the old one. Lian Li PC-A05NBF Black + Alphacool LC-Display 240x128 I was looking for software to use the built-in monitor as my old Alphacool LC-Display. And I found AIDA64. The first attempt / v1 The second attempt / v2 - v2.sensorpanel The third attempt / v3. I use now v3 BW 128 v2 - v3.sensorpanel - v3 BW.sensorpanel - v3 BW 128.sensorpanel - v3 BW 128 v2.sensorpanel Possible future - v4.sensorpanel I can't upload anymore, the limit is reached Now I'm waiting for the appearance of the possibility to monitor hard drives and wireless signal strength.
  4. 2 points
    You're right, 16278 carries on the issue. We need to release one more AIDA64 hotfix to get around it again. We'll do that tomorrow or worse case Friday. I'll post a message into this topic once the new AIDA64 beta build is available for download.
  5. 2 points
    new set of gauges , If some like it, leave coment and i sent you on you email. I have for LCD and sensor panel in ( Large and medium sizes ) in png
  6. 2 points
    Some new gauges. LOAD and IDILE. If some like it, leave coment and i sent you on you email. I have for LCD and sensor panel in ( Large and medium sizes ) in png
  7. 2 points
    This is a real layout GA-Z77X-UD5H. Panel size 1000x792 GA-Z77X-UD5H.2015-11-20.sensorpanel I have layered .psd file.
  8. 2 points
    Thanks for the quick fix. All working fine now. Here is my custom panel. System Idle Example System Load Example Desktop Example If any one wants to use it you can download it from my blog - http://blog.psine.com/sensorpanel.html
  9. 1 point
    Hi, Aida64 now provides support for the Odospace Remote Panel app: Reuse your old android device to display sensor values of a Windows PC. A WiFi connection is not (!) required, Remote Panel works even when the device is connected to the PC via USB only. However, an SDK for Remote Panel is provided also. Sensor values are provided by the industry-leading system information tool Aida64 which must be purchased separately. Please note that Remote Panel is not affiliated with Aida64 or FinalWire in any way shape or form and no support can be provided by the Aida64 team for this app. Requirements - Aida64 version 5.20.3414 or heigher must be installed on the Windows PC. - Remote Panel (for Windows) version 1.16 must be installed and running, it can be downloaded with the following link http://apps.odospace.com/RemotePanelSetup.exe - Microsoft .Net framework 4.5 must be installed on the Windows PC. This will be done during the installation of Remote Panel (for Windows). - The android device vendor's drivers must be installed on the Windows PC. - USB debugging must be enabled on the android device. This is described in detail here. Enable Aiada64 plugIn - After installation of Remote Panel (for Windows) Aida64 must be restarted. - Within Aida64 open the preferences page, navigate to LCD and enable "Odospace". Add items within the LCD items page. Settings - A long press within the view opens the settings dialog. Troubleshooting - In general the settings dialog of Remote Panel (for Windows) can be opened from the popup menu of its tray icon. - Remote Panel (for Windows) uses port 38000 and 38001 for local communication, if you experience problems because another PC program is using one of this ports, change the port number within the Remote Panel (for Windows) settings dialog and within the Aida64 Odospace LCD plugin. - Remote Panel (for Windows) uses the Android Debug Bridge (adb.exe) for communication. If you experience problems with other Android synchronization programs, try to use another adb.exe file - it can be changed within the settings dialog of Remote Panel (for Windows). - On default, Remote Panel (for Windows) checks every 30 seconds for new devices, decrease this value within the settings for faster device recognition, increase this value for less CPU usage. Alternative usage - If an additional PC should send its sensor values to the android device, set the IP address within the Aida64 Odospace LCD plugin to the address of the PC where the android device is connected. For every PC specify a different panel position parameter. Remote Panel (for Windows) must be installed on every PC, however the Remote Panel (for Windows) executable must only be started on the PC where the Android device is connected. - Remote Panel can be used within a WiFi network also, in such case set the IP address within the Aida64 Odospace PlugIn to the device's address. The port must be set to 38000. The Remote Panel (for Windows) executable can be stopped in this case. Advanced topics - To automatically start Remote Panel you can use AutoStart. - To power off the device on PC shut down you can use AutomateIt Pro - use the USB disconnect trigger. - If the device battery discharge even connected via USB, try to set the CPU speed to a lower level. For example you can use Tickster MOD. - To power on the device on PC startup the device firmware must be modified (follow this AT YOUR OWN RISK, tested with Cyanogenmod 10.2 on LG P760/P880 and may not work with all devices): General 1. Download the device firmware - it can be the original or custom ROM. 2. Use Boot/Recovery Repacker to extract the boot.img file of the downloaded ROM. 3. Within the file init.rc, in the section beginning with "on charger" replace the string "class_start charger" with "trigger boot" or "trigger late-init". Ensure that your editor writes the file in UNIX format. 4. Use the repacker to compress the boot.img file. 5. Apply the new firmware. Nexus 7 (2012) 1. Boot in fastboot mode 2. Issue the following command within a command prompt: "fastboot oem off-mode-charge 0" Version 1.14 - Now sensor data of multiple PCs can be displayed on one android device - The android device can be connected to any PC (not only to the PC where Aida64 is running) - Requires Aida version 5.20.3414 or higher and Remote Panel (for Windows) version 1.14a Version 1.15 - Fullscreen mode (long press for settings) - RemotePanel (for windows) version 1.15: Verbose mode for better problem handling, fixes a rare ADB hang when multiple PCs are connected to one android device. Version 1.16 available - New option added: Keep screen on (long press for settings) Many thanks to the Aida64 team for the great support! Best regards odospace
  10. 1 point
    Hey, Would it possible to have a list like Task Manager does where the processes / applications that are using the CPU or network would come up. EDIT: On the LCD I mean. I ask for this as I find myself noting via AIDA64 on my LCD that the CPU might be at 20% and then I wonder what might be causing it so I open task manager to find out. It would be ideal if I could have a list like that on a different page on the LCD via AIDA64 so I could quickly check what was causing the spike. A similar idea for the network would be great like what's found in the "Processes with Network Activity" tab of the Resource Monitor. Many thanks.
  11. 1 point
    Thank you for your answer. I will not worry anymore about battery wear level
  12. 1 point
  13. 1 point
    I'm glad you could resolve it, because we couldn't find out what's wrong on our end. We've tried to replicate the issue, but the only idea we came up with -- and even that one was a weak one -- is that your internet connection to our server (that provides the external IP info) is very slow for some reason. As for alerts: the existing AIDA64 Alerting module doesn't support changing label colours when an alert is fired. You can have a warning message box popped up, your computer shut down or an audio alert fired (played).
  14. 1 point
    Thank you for your feedback. We'll complete the iCX support in the next AIDA64 beta update due later this week. I'll post a message into this topic once the new beta build becomes available for download.
  15. 1 point
    Thank you for the dump. Yes, we'll add it, but first, we need to find a way to detect the presence of the iCX MCU. So far we haven't found a reliable way of doing that, but we keep looking for a proper solution. Please give us a few more days to investigate this.
  16. 1 point
  17. 1 point
    Hi Of course, an update is scheduled to support new devices very soon. Thanks for the report.
  18. 1 point
    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.
  19. 1 point
    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%.
  20. 1 point
    We do have plans, but not for the near future. We're watching the market, the evolution of the Windows PC ecosystem, and we'll make our move to 64-bit once it will become necessary or mandatory. The 32-bit main binary is there because that's the best compromise. Having a 64-bit main binary wouldn't be a major benefit, but on the other hand it would raise a lot of issues. One such issue would be a considerably bigger distribution package, more than twice the size of the current ZIP and EXE package. That's because when you have a 64-bit main binary, you need to have all DLLs compiled to 64-bit as well -- while retaining the existing 32-bit DLLs for compatibility reasons. Another issue is that many interfaces and APIs that AIDA64 relies on have no 64-bit support. And so when you want to use such an interface/API from AIDA64, it works now, but it would stop working if the user switched to the 64-bit main binary. As for the name itself: it's there to separate the software from its predecessors, namely AIDA32 and AIDA16. While it's true that the main binary is still 32-bit, but the critical parts (modules) that truly benefit from porting 64-bit are already available in both 64-bit and 32-bit flavours. Those modules are the benchmarks and the stress test (AIDA64 System Stability Test).
  21. 1 point
    It seems when vram usage passes 4GB, the aida64 values for the used GPU begin showing very low numbers. This i what i see in Aida64, where GPU-Z and Nvidia Inspector show >4.8GB used. Utilization GPU 98% Memory Controller 46% Video Engine 0% Bus Interface 5% Dedicated Memory 609 MB Dynamic Memory 699 MB DirectX Video info shows Direct3D Device Properties Total / Free Video Memory 8192 MB / 3385 MB
  22. 1 point
    Used Booers panel and modified it. I use Rainmeter so I needed a narrower panel to fit at the bottom of my Rainmeter sidebar. Edited/Updated (04-11-2015): I tweaked it further, made a few more improvements and replaced the files with the updated versions (e.g., switched out RAM temps for VRM, spacing improved, and tweaked some of the max values). Attached Thumbnail Attached File AIDA64 default cpu gpu net v7.sensorpanel
  23. 1 point
    Hello, I have a laptop with a AMD A8 5557m APU and a dedicated HD 8750M GPU. But Aida64 only shows me the data of the 8550G in the APU, it doesn't identify my dedicated GPU. Please help... Drivers are 13.12 WHQL.
  24. 1 point
    Hi guys I'm new here on forum, so... My name's Pav, i'm from Navan (Ireland).Today i've created my first sensor panel MIDNIGHT(based little bit on sunj's work. Thanx man ). Hope you like it. preview: And on my desktop: MiIDNIGHT.sensorpanel
  25. 1 point
    Hey guys, just thought you might like my Star Trek TNG sensor panel. I styled it like the control panels from The Next Generation. It's fully functional. I'm always tweaking though. It's a large size. 1024 x 972. I usually use it with 25% transparency on my 1600 x 900 desktop. I may do another design, just to switch up now and again.