Re: [android-developers] Permission issues in Android M

[TreKing]

On Thu, Sep 24, 2015 at 4:54 PM, Ankit  wrote:

> Currently I am detecting this and requesting User for the permissions, but
> OEM doesnt want this pop-up.
>

Inform the OEM they don't have a choice in the matter.


> I understand that if the application is signed with platform key, the
> 'dangerous' permissions will be granted by default, but is there any other
> way to grant these "dangerous" permissions to the system application
> without a pop-up for user?
>

Don't think so and I would certainly hope not. That defeats the entire
purpose of the granular permissions.

-
TreKing  - Chicago
transit tracking app for Android-powered devices

-- 
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
--- 
You received this message because you are subscribed to the Google Groups 
"Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-developers] Permission issues in Android M

[Ankit]

Hi,
   I am developing an application (service) for an OEM that will be 
installed as a system application. Due to the new permission model in 
Android M, this system application doesnt get granted 'dangerous' 
permission by default.
Currently I am detecting this and requesting User for the permissions, but 
OEM doesnt want this pop-up. 

I understand that if the application is signed with platform key, the 
'dangerous' permissions will be granted by default, but is there any other 
way to grant these "dangerous" permissions to the system application 
without a pop-up for user?

Thanks
Ankit 

-- 
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
--- 
You received this message because you are subscribed to the Google Groups 
"Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-developers] Permission issues

[Vinicius Carvalho]

Hi there! I'm developing an app for Honeycomb using my xoom device.

Now I got stuck, I'm using SQLite, and I need to access my db during
development, just to check if things are right.

But since this is not a rooted device, I can not access my data/data/
com.acme/databases to open my db file.

Is there any way around this?

The DDMS file explorer won't show me the files, I'm guessing that's
because I'm not rooted.

Regards

-- 
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

Re: [android-developers] Permission issues

[Mark Murphy]

On Tue, May 31, 2011 at 12:08 PM, Vinicius Carvalho
viniciusccarva...@gmail.com wrote:
 Hi there! I'm developing an app for Honeycomb using my xoom device.

 Now I got stuck, I'm using SQLite, and I need to access my db during
 development, just to check if things are right.

 But since this is not a rooted device, I can not access my data/data/
 com.acme/databases to open my db file.

 Is there any way around this?

Write a backup feature in your app that copies the (closed) database
to external storage, then download from there.

Or, develop on an emulator.

Or, write unit test cases using JUnit and the instrumentation framework.

-- 
Mark Murphy (a Commons Guy)
http://commonsware.com | http://github.com/commonsguy
http://commonsware.com/blog | http://twitter.com/commonsguy

Android Training in NYC: http://marakana.com/training/android/

-- 
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

Re: [android-developers] Permission issues

[Dianne Hackborn]

Or make your app debuggable with android:debuggable=true in the manifest
and use run-as in adb shell to switch to your uid.

On Tue, May 31, 2011 at 9:10 AM, Mark Murphy mmur...@commonsware.comwrote:

 On Tue, May 31, 2011 at 12:08 PM, Vinicius Carvalho
 viniciusccarva...@gmail.com wrote:
  Hi there! I'm developing an app for Honeycomb using my xoom device.
 
  Now I got stuck, I'm using SQLite, and I need to access my db during
  development, just to check if things are right.
 
  But since this is not a rooted device, I can not access my data/data/
  com.acme/databases to open my db file.
 
  Is there any way around this?

 Write a backup feature in your app that copies the (closed) database
 to external storage, then download from there.

 Or, develop on an emulator.

 Or, write unit test cases using JUnit and the instrumentation framework.

 --
 Mark Murphy (a Commons Guy)
 http://commonsware.com | http://github.com/commonsguy
 http://commonsware.com/blog | http://twitter.com/commonsguy

 Android Training in NYC: http://marakana.com/training/android/

 --
 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




-- 
Dianne Hackborn
Android framework engineer
hack...@android.com

Note: please don't send private questions to me, as I don't have time to
provide private support, and so won't reply to such e-mails.  All such
questions should be posted on public forums, where I and others can see and
answer them.

-- 
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

Re: [android-developers] Permission issues

[String]

On Tuesday, May 31, 2011 5:10:53 PM UTC+1, Mark Murphy (a Commons Guy) 
wrote:

Or, develop on an emulator.

Develop on an emulator for Honeycomb... ROFL. That's a good one, Mark!

String



-- 
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

Re: [android-developers] Permission issues

[Mark Murphy]

On Tue, May 31, 2011 at 12:23 PM, String sterling.ud...@googlemail.com wrote:
 On Tuesday, May 31, 2011 5:10:53 PM UTC+1, Mark Murphy (a Commons Guy)
 wrote:

 Or, develop on an emulator.

 Develop on an emulator for Honeycomb... ROFL. That's a good one, Mark!

I was figuring it'd take long enough to start up that he'd forget
about the problem... :-)

-- 
Mark Murphy (a Commons Guy)
http://commonsware.com | http://github.com/commonsguy
http://commonsware.com/blog | http://twitter.com/commonsguy

Android Training in NYC: http://marakana.com/training/android/

-- 
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

Re: [android-developers] Permission issues

[Chris Stratton]

On Tuesday, May 31, 2011 12:10:53 PM UTC-4, Mark Murphy (a Commons Guy) 
wrote:

  But since this is not a rooted device, I can not access my data/data/
  com.acme/databases to open my db file.
 
  Is there any way around this?

 Write a backup feature in your app that copies the (closed) database
 to external storage, then download from there.

 Or, develop on an emulator.

 Or, write unit test cases using JUnit and the instrumentation framework

Or set the mode of the database file to world readable... just don't ship 
that way like a certain internet phone app did.

Note that all of the methods aside from rooting or dumping a copy to 
external storage are going to require that you access the database file by 
its full path rather than a file browser, as the directories under /data are 
not browsable by unprivileged users, even though some of their contents are 
accessible.

-- 
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

Re: [android-developers] Permission issues

[Jonas Petersson]

On 2011-05-31 18:30, Chris Stratton wrote:
 [...]

  But since this is not a rooted device, I can not access my data/data/
  com.acme/databases to open my db file.

Write a backup feature in your app that copies the (closed) database
to external storage, then download from there.

Or, develop on an emulator.

Or, write unit test cases using JUnit and the instrumentation framework

Or set the mode of the database file to world readable... just don't
ship that way like a certain internet phone app did.


Or open the database straight from the SD card where you can do whatever 
you like while you develop. (This is actually how my Inventory app does 
the merge feature from the SD database to the closed database.)


Best / Jonas

--
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