In one of the prior messages on this thread, Dianne Hackborn mentioned her plans to implement a UI screen in Settings to enable READ_LOGS (for apps that have it in their manifest).
One could hope that this screen, whenever it appears, will have a documented launch action - so that apps like CatLog, aLogCat, etc can prompt the user and bring this screen up. This scheme already works for third party keyboards - out of the ones I use, both Swype and Swift Key 3 (highly recommended) have a setup wizard that 1) explains that the just installed keyboard needs to be enabled 2) brings up the system settings screen where this can be done Very simple and it works. -- K 2012/7/19 vt <vadim.tkache...@gmail.com> > On Thursday, July 19, 2012 7:54:35 AM UTC-7, Kristopher Micinski wrote: > >> On Thu, Jul 19, 2012 at 10:44 AM, vt wrote: >> > > >> > If a leaf falls to the ground in a forest and no one hears it, does it >> make >> > a sound? >> > >> > In other words, if your ADK app controls, say, an expensive aquarium >> with >> > fish and corals in it (which can easily run into five figures), and you >> get >> > back home after a week's vacation to find that a few days ago your app >> ran >> > amok and boiled everything and your fish is dead, how is my cool ADK >> > contraption better than a terminally dim PIC hack? >> > >> > - How do I make the bug report span across an arbitrary length of time? >> > - How do I trigger a bug report generation, say, on a regular basis, or >> from >> > inside an application? >> > >> >> This is basically why things like ACRA were invented..., >> >> There's nothing stopping you from dumping your app's logs to a file >> and then syncing that with your backend periodically.. >> > > App log is not enough. Earlier in this thread I mentioned that often, and > in cases where hardware is involved, almost always, system logs contain > information directly related to what is happening to your app. > > As for ACRA, isn't it also going to be crippled by READ_LOGS no longer > granted? > > It starts looking like a security theater to me. > > All right, one can do all this if one gets the custom ROM to get the logs > over WiFi (by extension: one can build a custom ROM which disregards > READ_LOGS completely). Hence, a malicious party will be able to read logs > no matter what *on device in their physical possession*. > > So, why is it not possible for a user to do the same on the production > build, *on device in their physical possession*? > > kris >> > > --vt > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
