For me this is a massive kick in the teeth. While i completely understand the Android Team's concerns and that of the user i am concerned that functionality is removed before alternatives are given.
My biggest issue is the inability to read the Radio logs of a device. Which i had set my app up to do because i am working in conjunction with Mobile Network Service Providers to peg certain events. One such event would be a Dropped Call. Android has no API support for when this occurs, nor does it provide any information about a call besides if it is in call, ringing or idle...which is not sufficient for what i need. I honestly couldn't care less about the rest of logs, or any personal information. I just need certain pieces but i have zero access to them now...which means i will probably lose business. I get that it was a hack around, but it was the only way to access the information i needed. Again like I said, it seems silly to break something before providing a better way to do it, then again, i do understand there is a cause for concern. I realise privacy is a huge issue nowadays and allowing anything to read logs could prove troublesome. On Sunday, 8 July 2012 21:26:47 UTC+2, 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
