Just an idea that I had after a few months of noticing every time I'd turn my phone's display back on, the CPU would be pegged. I'm not sure, but I think that it might be indicative of some malware, and I want to collect some other statistics regarding what is going on when the display is inactive.
Luckily, I had all of the VMs on my computer down, for backup purposes, for awhile here. If it wasn't for that, and not having the USB cable to connect my 'droid to the computer, I might not have noticed how other architectures, and/or /proc layouts, are making the app hang. For instance, I switched from my LG G6 (four coar AArch64 rev. 1 -- physical device), to an emulated Nexus 5X (api 26), and now I can't even get the stats box to populate. Need to track down where things like this might be coming from and add cases to deal.
Luckily, I had all of the VMs on my computer down, for backup purposes, for awhile here. If it wasn't for that, and not having the USB cable to connect my 'droid to the computer, I might not have noticed how other architectures, and/or /proc layouts, are making the app hang. For instance, I switched from my LG G6 (four coar AArch64 rev. 1 -- physical device), to an emulated Nexus 5X (api 26), and now I can't even get the stats box to populate. Need to track down where things like this might be coming from and add cases to deal.