I've flashed stock ICS, installed a few logcat applications with READ_LOGS
and upgraded to JB. Permissions were still granted to all applications
(even though these permissions were not listed in Application's info from
settings). Clearing applications' data or rebooting the phone does not
I've just created one:
http://code.google.com/p/android/issues/detail?id=35298
On Friday, July 20, 2012 4:12:26 PM UTC+3, BoD wrote:
:(
Did anybody open an issue?
--
BoD
On 07/20/2012 11:25 AM, b0b wrote:
Exactly. StrictMode thread policy (and it seems only thread policy) is
Hm, I've had an impression that permissions are granted or denied on each
fresh start of application. But after doing some experiments and looking
through logs, it seems that they are only granted or denied during
installation. Which explains the behavior of inherently granted READ_LOGS
I guess that's because I tried it on emulator. I don't have a device with
JB to verify that same procedure works for real devices.
On Wednesday, July 18, 2012 7:58:10 PM UTC+3, vt wrote:
On Friday, July 13, 2012 1:54:45 AM UTC-7, Ievgenii Nazaruk wrote:
I've tested the adb shell pm grant
is user 2000?
shell@android:/ $ id
uid=2000(shell) gid=2000(shell)
groups=1003(graphics),1004(input),1007(log),1009(mount),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats)
Aha, it's the uid used by adb shell.
-- K
2012/7/18 Ievgenii Nazaruk
Moving StrictMode configuration to activities is not an acceptable
solutions. As you generally don't know which activity might start first,
and adding same code (even only one function call) to each activity is not
always possible. Even more, you'd need to enable custom StrictMode
Just curious, how did this influence your application? Do you access
network layer from UI thread?
Anyway, I think this is a bug, there is nothing changed in documentation.
And StrictMode example in documentation still uses App's onCreate(). So
there are no signs of this being an intentional
not want the checks happening in
Application.onCreate() because it is okay to do disk access and such there
(the process is after all in the process of being launched).
On Mon, Jul 16, 2012 at 1:25 PM, Ievgenii Nazaruk
ievgenii.naza...@gmail.com wrote:
Just curious, how did this influence
On my instance of JB emulator it runs with new behavior.
Make sure you've started correct emulator, as I noticed several times that
ADT/SDK 20.0 could start something else (non-selected item) from the list.
On Sunday, July 15, 2012 9:54:18 AM UTC+3, Ran wrote:
It seems that on the JB
, 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
for developers in later
releases. It would've been great to have both these changes at the same
time. But we have what we have.
By the way, thanks for the power + volume down + volume up trick. Didn't
know it existed. This somewhat mitigates the issue in some cases.
/Ievgenii Nazaruk
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
Here goes the stack trace from eclipse:
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
According to android icon design guidelines ( here
http://developer.android.com/guide/practices/ui_guidelines/icon_design.html,
see table #1), developer needs to provide status bar icons of next
sizes:
Status Bar 24 x 24 px (LDPI) 32 x 32 px (MDPI) 48 x 48 px (HDPI)
While my measurements
14 matches
Mail list logo
