Google I/O 2012 - Ten Things Game Developers Should Know
Why Stack Overflow recommends it
Stack Overflow users cite it as an official source that Android Jelly Bean (4.1) restricted the READ_LOGS permission, so apps can only read their own logcat output.
Recommended by 1 people across 1 different months, 2012 to 2016.
What it is
A Google I/O 2012 session by Dan Galpin and Ian Lewis on what game developers should do to earn good Google Play reviews, deliver a strong Android experience and be considered for featuring. It is a conference talk aimed at Android game developers.
What people said
Recommends Lv99Zubat · 2016-06 · Stack Overflow · on “Save Logcat from Android app to txt file”
Oh according to this video [this video] by google. JellyBean and up allows without a permission to read system log for your own app. I wish this statement was thrown around a lot more.
Cites android developer · 2012-07 · Stack Overflow · on “READ_LOGS permission on Jelly Bean (api 16)”
Since Android Jelly Bean doesn't support the logs reading permission [LINK] (according to this google io 2012 video [this video] and this one too [LINK] ) , i would like to know if it's possible for rooted devices (or non-rooted devices) to be able to bypass this restriction and be able to read the logs. How do i do that? Do i really need to make the app a system app, or is rooting enough?
Cites Cat · 2012-11 · Stack Overflow · on “Read the system log on Android 4.1”
System logs changed in 4.1 and are now accessible only by system apps. (Source: Google I/O Video [this video] .) This is an exception on rooted devices, of course, if the installed app is set to be a system app. Aside from this, there is no way to access the system logs on Android 4.1+. Note: End users can access the system log by using the (very finicky) shortcut of Power + Vol Up + Vol Down .
Cites Rick77 · 2013-05 · Stack Overflow · on “Not all data shown when Android logcat is read programatically”
I have bad news for you: as of JB, READ_LOGS don't just work as it did anymore: [LINK] (scroll to the post of Dianne Hackborn, an Android Develper) and this video: Google I/O 2012 - Ten Things Game Developers Should Know [this video] (22:47) for official sources. However his has not been yet documented (the READ_LOGS [LINK] permission doesn't report this) and is yet a source of confusion. You can only access your own logs now, and the good news is, you don't need to request permissions for it anymore (if your are targetting Jelly Beans, that's it...). I guess it's a compromise the Android Dev team took to prevent malicious app from spying on the user, perhaps getting sensitive information (I woul