Fiery

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. Thanks, Fiery

I guess it's not SensorPanel that you're working on, but a layout for the RemoteSensor LCD module With that you can only use such fonts that are present (installed) on the remote device, simply because the actual rendering is done by the web browser of the remote device, e.g. Google Chrome for Android, and that browser has to have access to all the fonts you're using on your layout.

Does SM 6.6 become available with WDDM 2.8?

I'm afraid, still no good news on this

Thank you! I forgot to ask you for a 3rd dump: Please right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> NVMe Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery

Do you have Valorant Vanguard anti-cheat software installed?

If you have that anti-cheat software installed, then yes, it tends to collide with hardware monitoring software like AIDA64.

1) About the ext.fans, please 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. You may need to enable status bar in AIDA64 / main menu / View first. 2) As for the L/M vs. LPH, the latter is used by AIDA64 as a measurement unit. It's not possible to alter the measurement unit in AIDA64 for sensor values. 3) T_Sensor should be available in AIDA64 as Temperature #1.

It's printed as a list of strings, separated by comma. So a single or multiple reason strings are included in the resulting text.

Thank you for your kindness. I'm terribly slow lately, but it's just because AIDA64 suddenly became twice as popular as before -- fortunately --, and we're swamped under hundreds of user requests

You need to implement some sort of workaround for such situations, because when a certain device lacks proper encoded information that would allow AIDA64 to properly identify it, it's not the fault of AIDA64 then when it cannot identify it by "its name"

To me it seems to be a hardware failure, but please note that it's not possible to diagnose such issues remotely. You may want to take your phone to a local specialist and have it checked out.

Thank you for your feedback. Please note that in Android 7+ (for whatever reason) Google decided to block apps from accessing several system files that were previously readable. That includes the files apps would need to show thermal sensor readings. Battery temperature reading is still available fortunately.

Thank you for posting your solution!

In order to have the missing readings, you need to enable the following 2 options in AIDA64 / main menu / File / Preferences / Stability and restart AIDA64 to apply the changes. Embedded Controller (EC) support Embedded Controller (EC) bank switching

Please note that it's not possible to diagnose such issues remotely. You may want to take your phone to a local specialist and have it checked out.

Do you use an anti-cheat software?

Please note that on most devices dual and triple cameras are managed by the underlying Android platform as single cameras. So it's not possible to detect their individual properties using the standard Android Camera API.

You seem to have an issue about the SensorPanel prevent being minimized options. Is it okay to have it working only when the topmost window option is also enabled?

Yes, you need to use both options in the same time.

Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB 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. Also right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> USB PSU Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery

I'm afraid it's not possible to detect such property for Android devices. We may add that fieldt to the hardware database of AIDA64 for Android later this year though.

What motherboard do you have and which version of AIDA64 do you have installed?

Try to run the AIDA64 System Stability Test twice. First, enable only the FPU subtest so you can put the maximum stress on your system when it comes to power draw and thermals ("heating it up"). Watch the Statistics tab for any abnormalities, and check if the system can stand the pressure for several hours. Meanwhile you can also enable Logging (in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Logging) in case you want to analyze the data later on. When you're done with that, run it again, now with all subtests enabled. If and when you have a crash, check back the logs and see which voltages look abnormally low or high.

Do you have another monitoring software running that may collide with AIDA64 performing the EC sensor access in the same time?