On 06/19/2014 09:16 AM, William Roberts wrote: > That works fine in a development scenario, for deployed devices just > filter on logcat with an app and save to disk or offload. The drawback > there is that you have to filter a stream at one point that was isolated > from the stuff you didn't care about, thus wasting battery for nothing. > As we have all seen, logcat is quite chatty. > > The other option is to hack logd to send to logcat and a separate > stream, perhaps to disk or wherever you would like.
I guess the question is whether one of the existing options (/proc/kmsg, logcat -b events, logcat -b main) is sufficient already or if you truly need a dedicated audit-only stream. Not sure offhand how hard it is to add new buffers/streams to logd and the underlying infrastructure. _______________________________________________ Seandroid-list mailing list [email protected] To unsubscribe, send email to [email protected]. To get help, send an email containing "help" to [email protected].
