Jump to content
AIDA64 Discussion Forum

Leaderboard


Popular Content

Showing content with the highest reputation since 02/14/18 in all areas

  1. 3 points
    Although I have made some detailed panels that looked ok to me I have come to realize that because I'm using a 5" LCD as my panel monitor I can't see the sensors because everything is just way too small so I decided to use only what I think would be helpful to my situation this round. Thank you StealthDefender for helping me realize this I would also like to thank Stupe9968 for the killer gauge templates . My new panel (I'm still kinda messin with it) So I just finished my new long awaited rig, specs are as of the following: PC Name - Jedi Assassin Motherboard - Gigabyte GA Z370 Aorus Gaming 7 CPU - Intel i7-8700k @ 5.0 MHz, 1.350 V CPU Cooler - NZXT Kraken X52 RAM - G-Skill Trident Z RGB 16G (2x8) DDR4-3000 MHz 16-18-18-38 CR2 SSD - Samsung M.2 960 EVO 500 MB (Temp) Portable HDD - Seagate Expansion 2 TB GPU - Gigabyte GeForce GTX 1060 Aorus Extreme Gaming 6GB Main Monitor - Viotek GN34C 34" curved 3440 x 1440 100Hz + O.C. Sensor Panel Monitor - 5" LCD attached to case PSU - EVGA SuperNova 850 G2 Gold Case - Phantek Enthoo Pro 2x NZXT 5x USB hub Speakers - Logitech Z623 200watt 2.1 THX Certified LG Blu-Ray DVD/Burner FANS 5x 120mm Thermaltake Riing plus RGB 2x 120mm NZXT 2x 140mm Corsair High Volume Purple LED
  2. 2 points
    Thank you. Here's the fix for your motherboard as well as other motherboards that are affected by the same anomaly. https://www.aida64.com/downloads/latesta64xebeta
  3. 2 points
    New Text Version, uses on Desktop > text_v2.sensorpanel Adapted to 5 Inch Dispaly with 800x480 Pixels > PiDisplay.sensorpanel PiDisplay.sensorpanel text_v2.sensorpanel
  4. 2 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.
  5. 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
  6. 1 point
    Hi, UBports https://ubports.com/ is maintaining and developing the Ubuntu touch os, and there is a strong community starting around it, a lot of developers and porters interested in system info have asked about the availability of your program after Canonicals app store has shut down. The new app store is here: https://open.uappexplorer.com/ If possible could you make the click package available to the open store, or even here on the forum?
  7. 1 point
    HWiNFO and HWMonitor might fit the bill.
  8. 1 point
    Android:I recommend huawei M5. I watched a 45-minute Netflix show (downloaded, offline) the other day and had 98% battery left! Streaming video takes a bigger toll on the tablet but was still a high performer! My past experience: Samsung Tab S2, Nexus 7, Apple Mini 2. I did not like the mini because my favorite browser would not word wrap. 1) Speed. M5 is faster than Tab S2 but both are adequate. Nexus 7 is as smooth but much slower. Still useable. 2) Touch screen sensitivity. All three are good with finger touch but Nexus 7 is unuseable with stylus. Tab S2 is perfect with stylus, M5 close behind. M5 Keyboard touch is equal to Tab S2 but for some reason smaller icons such as home screen, back, and even some (closing) x require slight technique some times. 3) Screen. M5 is best, but all three are hi-res and adequate. Anything with 800 in the screen description is inadequate. 4) Sound. This has four components. Adequate internal and blue tooth volume, internal sound quality, and blue tooth sound quality. The Tab S2 doth truely suck in all three. The most irritating thing is none of the PlayStore volume boosters work with S2. ( Sound boosters are needed for some youtube and other presentations that are badly sound engineered.) The sound booster I use works both on the Nexus 7 and M5. The Nexus 7 has the best blue tooth fidelity and M2 is about the same while the S2 a cut below "the best". The M5, however has by far the best internal sound. Recently I have not even bothered to use my nifty blue tooth speaker for audio books on M5. 5) Automatic screen orientation. The M5 does not have 360 orientation. It only rotates 180 degrees. This is a bigger deal than you might think. Speciffically, I can not use the M5 in portrait mode while charging the battery because my favorite (high quality leather) carrying case charging port is on the bottom! 6) Screen proportions. Both the Nexus 7 and M5 have wide screens versus the S2 that has the apple squarish screen. In all honesty, I expected to always prefer the wide screen but I don't. You may have a preference. Summary. If I could only have one tablet I would choose the M5 entirely for its all around sound management. Probably I will still use the Nexus 7 for audio books on blue tooth because it is so small and handy.
  9. 1 point
    How much will it cut ?I want to buy one ,is it on Amazon ?or ?
  10. 1 point
    Hi, I was wondering if it would be possible to make it so that the date format could be changed ? For now it is: 8.08.2018 It would be great if that could be changed for example to: 08.01.2018 or Monday 8 January 2018 or any combination of these. (user configurable) (And optional leading zero for clock hours too, because time jumps left and right with some fonts if hours change from one number to two.)
  11. 1 point
    Hello Here is my panel of ROG control for my second screen 1920x1080. I realized with photoshop at 80% There are some changes to make. Image 1 is without photoshop Image 2 with photoshop Sorry for my english I am french.
  12. 1 point
    That's not possible right now, and I'd rather not make any promises on such a feature expansion on our mobile app.
  13. 1 point
    The remote features of AIDA64 Business are not limited to LAN at all. You can use any kind of connection as long as it's based on the TCP/IP protocol.
  14. 1 point
    HDDs have different measurement units for the SMART attribute 09, so it's not possible to implement a generic solution that would cover all HDDs out there. Do you think your HDD measures power-on time in hours? In other words, do you think 15986 hours which is 666 days would be correct for your HDD? If you can let us know what the measurement unit for your particular HDD is, we can add that model to the SMART module of AIDA64 in order to show you the remaining drive lifetime information. If you have multiple HDDs, and you can send measurement unit information for all of them, that would be even more cool In such case don't forget to specify the full model ID of your HDD, like for this case Hitachi HDT721010SLA360. Thanks, Fiery
  15. 1 point
    We believe we've found the root cause of the issues concerning Windows 10 April 2018 Update (Version 1803 / Build 17134) based systems. The timer that AIDA64 uses for BCLK measurement is also used by a new Win10 component. Most likely that component is used for GPU profiling. And when AIDA64 and Win10 both use the timer for their own purposes in the same time, the system could become unstable. We've had to disable polling for BCLK, so from now on AIDA64 will only measure BCLK once, and then use the last value until AIDA64 gets restarted. Here's the new AIDA64 beta build that includes the workaround: https://www.aida64.com/downloads/latesta64xebeta
  16. 1 point
    You can adjust sensor readings in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction.
  17. 1 point
    Thank you. Please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works.
  18. 1 point
    Ok thanks got it figured out thanks to your help, I did purchase it then was completely overwhelmed by it so decided to just keep using nzxt cam so I removed it. Then decided since I paid for it to give it another try so downloaded it again but forgot to activate it lol thank you
  19. 1 point
    Bluetooth version cannot be detected directly on Android devices. We're planning to add that info using a backend hardware database in a future version of AIDA64 for Android.
  20. 1 point
    You're not forgotten at all We just need to get a similar configuration to yours, install WinXP on it, and check out what could have gone wrong. It takes a bit of time to get that done, especially the "get a similar hardware" issue.
  21. 1 point
    I also have the aforementioned problem for about 6-7 months now. I am in contact with Gigabyte for the last 6 months, and they apparently do not forward anything to you about the problem. I just did a clean Windows 10 reinstall yesterday, just to be sure, and I can say that the problem persists for sure with all AGE versions from 1.0 (including the beta) to 1.31 (current version). The problem is not only with the LEDs control, but also with the Fan Stop (also fan start) function of the GPU. My GPU is Aorus 1080Ti eXtreme and my motherboard is Aorus X299 Gaming 9 (Gigabyte's current top models). When AIDA64 is working, no matter if it's from boot up or if it's manually started later, the user loses the ability to control the LEDs both on the GPU and on the motherboard. After AIDA64 gets started at least once after boot, the GPU loses control of its fans, if AGE is not started. I'll explain this in detail: 1. Windows starts, AIDA64 is not loaded automatically, AGE is not loaded automatically, result is - user can control LEDs on both GPU and MB with Gigabyte RGB Fusion software and Fan Stop of the GPU is working automatically as it should 2. Windows starts, AIDA64 is not loaded automatically, AGE is loaded, result is the same as 1. 3. Windows starts, AIDA64 is loaded automatically, AGE is also loaded, result is - no LEDs control, Fan Stop on the GPU is working as it should 4. continuing from 3. we stop AIDA64 manually, AGE is still running, result is - still no LEDs control, Fan Stop still working as it should 5. continuing from 3. we stop AGE, AIDA64 is still running, result is - no LEDs control through RGB Fusion, Fan Stop is not working as it should anymore (explanation in 5a and 5b) 5a. while Fan Stop is active I run anything to load the GPU to 100%, result is - GPU goes to 91 degrees Celsius and starts throttling, GPU fans do not start at all at any point of the test 5b. while Fan Stop is not active (fans are working because GPU temperature is over 55 degrees Celsius, because anything is currently using the GPU), I stop the software that's loading the GPU, GPU temperature drops below the Fan Stop limit of 55 degrees Celsius, however the fans do not stop ever, if I then run AGE, Fan Stop activates immediately, but still no LEDs control whatsoever neither on GPU or MB. I hope this info helps you fix your software.
  22. 1 point
    As long as Mad Catz offers a similar SDK for RAT9 that it has for Strike7, we can implement that feature in AIDA64. But I haven't seen any such SDK offered by Mad Catz...
  23. 1 point
    I like the gauges ... panel is easy to see/read too
  24. 1 point
    Ok cool I'll see what I can come up with for ya we can fine tune it later on ...
  25. 1 point
×