Fiery

There are tons of those out there, and we've never purchased any of them, so I have no idea which one is nice and which one isn't. In the specifications they should mention Windows compatibility, DisplayLink or such. If you want to go for sure, then pick one with a DVI, HDMI or DisplayLink connector. Then it wouldn't need a driver at all, and you could connect it to any video source too (like a DVD-player or such).

We've just found a workaround for the Ubuntu Touch OS version detection issue. Also, we've renamed the "Android Version" line to "Android Subsystem Version" to avoid further confusion. The AIDA64 for Ubuntu Touch app has already been updated in the Ubuntu Store as v1.0.1.

SensorPanel is definitely less complicated than an external LCD that does not appear as a monitor under Windows. You can use the SensorPanel with a HDMI connected display, since those devices appear as a monitor under Windows.

Yes, it's because Ubuntu Touch devices feature several portions of Android actually The reported Android version is not the OS version, but the Android subsystem version. Here's how the Ubuntu Touch architecture looks like: Ubuntu Touch OS version cannot be detected due to platform issues about too strict sandboxing (confinement) solution called Ubuntu AppArmor. AppArmor prevents not only regular apps to detect certain system details like Ubuntu Touch OS version, battery readouts and temperature measurement, but also cripples built-in Qt5 APIs that would otherwise be able to provide some of those details. For example: * Ubuntu Desktop / 16.04 LTS (latest updates) QSysInfo::productType(): "ubuntu" QSysInfo::productVersion(): "16.04" QSysInfo::prettyProductName(): "Ubuntu 16.04 LTS" That one was an unconfined environment where everything worked out fine. But, if you call the same Qt5 APIs on a phone where AppArmor confinement is enforced, you get the following values: * bq Aquaris E5 HD Ubuntu Edition / 15.04 (OTA-11) / Device Image Part 20160524-63b1875 QSysInfo::productType(): "unknown" QSysInfo::productVersion(): "unknown" QSysInfo::prettyProductName(): "Linux 3.4.67" This is an oversight on Canonical's part, but we've already notified them about this issue. Once they fix it up, our app will be able to report Ubuntu Touch OS version on the OS page. I wouldn't expect that to happen before OTA-14 though, so this fall the earliest. Regards, Fiery

AFAIK none of them are produced anymore, so you cannot get them brand new anymore. The last series consisted of the 800P, 1000P, 800W and 1000W models. I'm not sure if the "W" version was a successor to the "P" version though.

A constant zero percent CPU throttling means your CPU is not overheating. So it's the best scenario of them all That's why the throttling graph is green at 0%, and turns red at any other value. Regards, Fiery

Yes, it can still happen, since even if you disable all items, the sensor module will still poll many of the sensors. The AIDA64 sensor module has some degree of granularity, so you can disable polling certain sensors by picking from the list of shared memory items, but you cannot disable the main part that polls motherboard and GPU sensors, as well as a few other external sensors devices. Thank you for the list and the extra info! Now we'll try to reproduce the issue on a local test system of ours. Please give us a few days to do that

We believe the issue is related to one of the sensor items you export via shared memory. Can you please send us the full list of IDs you export via shared memory? The easiest way to do that is to locate AIDA64.INI file in the installation folder of AIDA64, and find the line that starts with: HWMonExtAppItems= Please copy-paste that line into your post if possible. Thank you in advance!

Only Samsung SPF and AX206 hacked digital picture frames can display data that you pass through the USB port. No other picture frame can do that I'm afraid. Even Samsung SPF frames have such variants that aren't capable of that feature. And AX206 frames are usually very small, so definitely not something you would want to use.

Please note that we've just rolled out a new update to our AIDA64 Windows 10 UWP app, version 2.0.8.0. The new update implements a dark theme, and a new command bar button to let you switch between themes anytime. I hope you'll find the new design appealing

The closest might be a Samsung SPF digital picture frame. But, some versionso of that device suffers from overheating issues, and also you cannot get one brand new anymore. Mint 2nd hand ones going on the 'bay also tend to be a bit expensive. Some AIDA64 users opt to get an old and/or cheap Android tablet and use Odospace: https://forums.aida64.com/topic/2776-display-pc-sensor-values-on-android-device-connected-via-usb-odospace-remote-panel/ But, you will see that there's no perfect solution out there. A big screen that doesn't act like a monitor, and has direct USB connection is very rare. Most users expect such big displays to work as a secondary monitor under Windows/OSX/Linux. It's even more difficult to find a big screen with fast USB connection that provides fluid full-frame refresh rates. For example, Matrix Orbital makes some great looking large displays with USB connection (e.g. GTT70A), but they all use a very slow serial protocol that is not suitable to be used with the AIDA64 LCD module. Not to mention they're bleeding expensive too

Such USB connected displays appear as regular monitors under Windows. You can extend your Windows Desktop onto the secondary monitor and move any windows of any software to the secondary display. So you don't have to use the AIDA64 LCD module at all, but you can simply use the SensorPanel and move the panel to the secondary monitor. Regards, Fiery

We've implemented the requested new sensor icons in the latest beta version of AIDA64 Extreme available at: http://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

5000 mAh

We don't aim at such deep level of customizations with our LCD module. Our LCD module is relatively easy to use while still offering deep customization possibilities. It's not infinitely customizable, but it also doesn't require a 100-page manual to operate. BTW, it's not the best way to open a meaningful discussion with "the AIDA64 lcds support is poor and ugly" and close the opening post with "aida64 lcd support is ugly poor does not offer any kind of control.... is terrible". It's one thing when you'd say "In my opinion it's terrible", and when you declare something being terrible, like you would declare the universal truth. And we do not want to buy or acquire any other software. We prefer to work with our code, developed by us from scratch. We believe that's the only way to have full control over the software, and most importantly: to provide the highest quality software. Regards, Fiery

Do you mean the actual Windows screensaver (like Mysify, Bubbles, etc) or the power-down mode of the monitor?

Thank you for your help. The issue will be fixed in the next AIDA64 beta update.

Thank you. I've just sent you a private message about this issue.

Thank you, but please note that it's not possible to diagnose such issues remotely. I could give you a few ideas, but I cannot pinpoint any particular hardware component this way I wish I could, but PC hardware is unfortunately too sophisticated, and there are too many variables about hardware components, their compatibility to each other, hardware settings, software settings, drivers, etc, etc

AIDA64 already supports fully automated internet updates since 2011. But, you need to have a valid license for it to work fully automated. If you have an illegal (pirate) license entered into AIDA64, it will only offer a download link and you have to complete the update manually. Regards, Fiery

That's normal, and it's because GPU clock reading is not really suitable to be displayed in a 16x16 pixel icon We could display "1.2" for 1200 MHz and "1.0" for 980 MHz (consider rounding), just like we do with CPU clock and memory clock, but that's not the most accurate system. Let me know if you still want us to do so

Our idea is to alter Corsair Link Software in a way that it would export the measured values using shared memory or Windows Registry. It would work quite similarly to our existing module in AIDA64 called External Applications. That way only Corsair Link Software would need to talk to Corsair water coolers and other CL compliant Corsair hardware, and 3rd party applications could only talk to Corsair Link Software and wouldn't have to access hardware at all. Very convenient, since that completely eliminates the issues about hardware access collisions. The only problem is: implementing such a feature in Corsair Link Software may be a bit tricky and would require certain development and QA resources on Corsair's part that they may or may not be able to allocate in the short run. We'll of course pester them hard enough to push them over the fence

Thank you for the dumps. I've just sent you an email about this issue.

With the latest beta, have you tried running the Cache & Memory Benchmark multiple times? Does it fail in all cases?

Very nice Thank you for the feedback!