search

dgets / CPURecord

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.
0 stars 0 forks source link

Add other system information logging #7

Open dgets opened 6 years ago

dgets commented 6 years ago

In conjunction with issue #6, it would greatly improve the usefulness of this application to save other relevant activity logs. Of course these should be time- & date- stamped, in order to correlate with the processor stats, at any given point in the history. For instance, being able to know when the device went into a locked/blank/off screen mode, would be very useful for cases such as the one that gave me the idea to develop this app. Other system changes, such as application opened, charging status, and LAN/4g networking status changes, are all stats that could, and should, be logged as well. In the original context for this app, such changes could be exceedingly useful to crossref with processor usage at, due to the fact that malware could be using those changes as triggers to activate.

Hell, we could go all the way and log PIDs, I suppose. Maybe options for different levels/stats to log would be a good idea, as well. Actually, I'm sure it would, I just don't want to heap too terribly much work into this one enhancement issue.

dgets commented 6 years ago

This should not be confused with the information from #11, which is currently being implemented. These will be non-kernel/processor specific details.