Hi Levgenii Nazaruk,
Thanks for the info that you provided with. But, I do have some douts.
We are currently working on an ERP based Device Administration App in
android, which need to monitor other application and decide which one to
run and which one not to, based on server side policy. The whole
architecture was based on system logs which collapsed due to new Log policy
in Jelly Bean. Please let me know how can I get this permission from code
itself.
To be precise, can I run *pm grant <pkg> android.permission.READ_LOGS *from
within the code like *Runtime.getRuntime().exec("pm grant <pckg name>
android.permission.READ_LOGS");* or something else. If not, what exactly
can be done to get this permission. Do we need to run this from *adb
shell*every time ?
Any help will be much appreciated.
Thanks,
*Karthik*
On Friday, July 13, 2012 2:24:45 PM UTC+5:30, Ievgenii Nazaruk wrote:
>
> I've tested the "adb shell pm grant <pkg> android.permission.READ_LOGS"
> and can confirm that it enables READ_LOGS permission for my application.
>
> Here how persistent this granted permission is:
> 1) Granted permission survives reboot.
> 2) Granted permission survives application update (i.e. "adb install -r").
> 3) Granted permission does not survive if application was uninstalled and
> then installed again.
>
> This is basically what I'd expect from this functionality. So basically
> the developer/tester flow I was worried about is actually covered by Jelly
> Bean. Which is good news.
>
> On Sunday, July 8, 2012 10:26:47 PM UTC+3, Ievgenii Nazaruk wrote:
>>
>> Hi all,
>>
>> I've been working on an application for developers that uses
>> DropBoxManager. The DropBoxManager requires READ_LOGS permission to be
>> granted in order to query information from it.
>>
>> Today I've tested my application on newest (api 16) emulator before
>> releasing it to Google Play. It turned out that Android now refuses to
>> grant this permission to 3rd party applications. This is weird because I've
>> looked through all Jelly Bean's documented changes and couldn't find
>> anything that mentions READ_LOGS permission.
>>
>> So basically my questions:
>>
>> - Did anyone see this change documented?
>> - Can someone confirm this behavior on Galaxy Nexus with Jelly Bean
>> on it (the one released to attendees of Google I/O)?
>>
>> And questions to someone from Android team:
>>
>> - Why this breaking change wasn't described in documentations like
>>
>> READ_EXTERNAL_STORAGE<http://developer.android.com/reference/android/Manifest.permission.html#READ_EXTERNAL_STORAGE>was?
>>
>>
>> - What should developers and testers do in order to use those handy
>> utility applications that require READ_LOGS to be useful? Is there any
>> way
>> to allow READ_LOGS to 3rd party applications without making custom build
>> (i.e. something in "Developer Options" that I could've missed)?
>>
>>
--
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
