Besides debugging, there are a number of other things that are very useful
to users that you can do with log access. One of these, is apps that
provide special per-app settings and hence need to know which app is
currently running. Here are some examples:
1. The SmartApp Protector app (and
I experimented same issue using Crittercism, that I rather liked to use
that permission for debugging crashes. After seeing that it was not
working, I simply desist and rely on other debugging information.
I was not sure if the fail was on Android side or Crittercism one, but
reading your message
Hi, sorry this didn't get documented.
The change is that third party applications can no longer get the read logs
permission, however every app can read the logs containing only the lines
*they* have written, without needing any permission.
Keep in mind that access to the logs has never been
On Thu, Jul 12, 2012 at 12:59 PM, Dianne Hackborn hack...@android.com wrote:
however every app can read the logs containing only the lines
*they* have written, without needing any permission.
OK, I'll bite: how do you do this? Most of the read-the-logs code that
I have seen uses logcat via
Let me just respectfully say that I don't understand the decision.
The API is potentially very dangerous, yes, but that is why it requires
a permission.
--
BoD
On 07/12/2012 07:24 PM, Mark Murphy wrote:
On Thu, Jul 12, 2012 at 12:59 PM, Dianne Hackborn hack...@android.com wrote:
however
Let me just respectfully say that I don't understand the decision.
The API is potentially very dangerous, yes, but that is why it requires
a permission.
Do users even look or comprehend what permissions are being used in any
given app? The user wants the app, they agree, agree, agree
On Thu, Jul 12, 2012 at 4:01 PM, John Coryat cor...@gmail.com wrote:
Let me just respectfully say that I don't understand the decision.
The API is potentially very dangerous, yes, but that is why it requires
a permission.
Do users even look or comprehend what permissions are being used in
I think that locking out developers from using APIs (and yes, I know that
it wasn't part of the SDK) for security purposes is an entirely wrong
approach. Sure, malicious things can be done with reading the logs, but in
the same vein, a kitchen knife can be used to kill someone. Every API can
On Thu, Jul 12, 2012 at 10:24 AM, Mark Murphy mmur...@commonsware.comwrote:
On Thu, Jul 12, 2012 at 12:59 PM, Dianne Hackborn hack...@android.com
wrote:
however every app can read the logs containing only the lines
*they* have written, without needing any permission.
OK, I'll bite: how do
On Thu, Jul 12, 2012 at 1:07 PM, Kristopher Micinski krismicin...@gmail.com
wrote:
Do users even look or comprehend what permissions are being used in any
given app? The user wants the app, they agree, agree, agree and then get
malware.
This is a problem with permissions, not
On Thu, Jul 12, 2012 at 2:11 PM, niko001 ebs...@gmail.com wrote:
I think that locking out developers from using APIs (and yes, I know that
it wasn't part of the SDK) for security purposes is an entirely wrong
approach.
I will respectfully disagree with such a blanket statement. :) If you
11 matches
Mail list logo
