I own a Note 8, the Aida64 app was working fine with my phone running Android Nougat. However as I updated to latest Android Oreo (8.0) today whenever I am opening the app it only loads a blank white screen on the start up and crashes after a while automatically. How do I fix it??
Along with the Logitech Arx integration, we've also come up with a new LCD module that basically acts as a web server. You can use your main computer to run AIDA64 on it and maintain its built-in web server, and you can use your other computers or mobile devices to monitor your main computer's status remotely, using nothing but a web browser.
You can activate it in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / RemoteSensor. Once you activated it, you can enter the IP address in virtually any web browsers to connect to the RemoteSensor. You can check the primary IP address of your computer on the Computer / Summary page in AIDA64. If it is e.g. 192.168.1.123, then enter the following in the address bar of your web browser:
Or, in case you use a different TCP/IP port than the default http port of 80, then enter the address like this:
http://192.168.1.123:8080 (if you use a TCP/IP port of 8080)
Or, in case you try to use a web browser on the same computer where AIDA64 is running, you can simply use "localhost" instead of the IP address, like this:
Once you did that, you should see the AIDA64 splash screen in your web browser. It will provide you with information on the resolution that you need to use to get the most out of the LCD layout designer. On iOS devices the default setting should be close to the actual value to use, while on Android and other devices it may not match at all, so you need to change both the width and height.
Please note that the Preview Resolution usually will not match the native screen resolution of your device. It's not a problem at all, and that discrepancy is due to the way web browsers manage the pixels of your screen, so don't be surprised that e.g. an iPhone 5 would report a Preview Resolution of 980 x 1360 pixels
After the Preview Resolution is updated on the AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD page, you can use the same LCD layout designer that you would use for other LCD devices or the SensorPanel.
Known issues and limitations:
1) Graphs and gauges are not implemented yet. We're planning to add them in the next few weeks.
2) RemoteSensor uses HTML5 SSE (Server-Sent Events) to refresh the web page, without having to reload it all the time. SSE is supported by almost all major web browsers, including Android Browser, BlackBerry 10 Browser, Chrome, FireFox, Opera, and Safari. However, it is sadly not yet supported by Internet Explorer. AIDA64 implements a trick to get around that limitation, but it sometimes will result in a mixup of the browser. If you notice that after changing the LCD layout in the AIDA64 Preferences, a strange log replaces the LCD layout in your browser, just refresh the web page. Hopefully Microsoft will finally implement SSE support in Internet Explorer 12
3) In order to prevent your mobile device from going to sleep while having the web browser open, you may need to install special apps on your mobile device. RemoteSensor has absolutely no control over the power management behavior of your mobile device. In case this is a deal breaker for you, and you've got a Logitech Gaming hardware, consider using Logitech Arx instead of the RemoteSensor.
You can try the RemoteSensor in the following new AIDA64 beta update:
Please let us know how it works on your mobile devices
have you seen the new Logitech Arx Control solution?
It's basically a way to use iOS and Android phones and tablets to display and control various stuff of your gaming PC.
The only requirement - besides the phone or tablet - is to have Logitechs Gaming Software installed. It works with all Logitech keyboards and mice that are supported by the Gaming Software.
And, as far as I understand, there's a documented API which allows you to display custom stuff in the app. I haven't looked at it, but I guess it's not too different from the API that they used for their LCD displays.
Do you want to check that out and give us an idea whether you'd like to support that?