On Tue, Aug 2, 2011 at 1:17 AM, Jim Graham spooky1...@gmail.com wrote:
Ummm, right. No. First, I'm almost 100% certain that that's impossible,
Yes, fortunately, this is impossible.
--
Mark Murphy (a Commons Guy)
http://commonsware.com | http://github.com/commonsguy
On Tuesday, August 2, 2011 1:17:04 AM UTC-4, Spooky wrote:
Install it before the user is given their corporate phone and set it so
it can't be removed. Of course, you can't prevent them from killing it,
but that's another story.
How were you planning to set it so it can't be removed ?
--
On Tue, Aug 02, 2011 at 09:05:42AM -0700, Chris Stratton wrote:
On Tuesday, August 2, 2011 1:17:04 AM UTC-4, Spooky wrote:
Install it before the user is given their corporate phone and set it so
it can't be removed. Of course, you can't prevent them from killing it,
but that's another
@Jim - It would be possible to configure an app to be non-removable by your
average user. Of course you can't stop them but AFAIK if the app is
installed by the superuser, example the bloatware that comes pre-installed
on most devices, then it cannot be uninstalled by anyone except the
superuser.
On Tue, Aug 02, 2011 at 11:13:43PM +0530, Raghav Sood wrote:
On Tue, Aug 2, 2011 at 11:00 PM, Jim Graham spooky1...@gmail.com wrote:
On Tue, Aug 02, 2011 at 09:05:42AM -0700, Chris Stratton wrote:
On Tuesday, August 2, 2011 1:17:04 AM UTC-4, Spooky wrote:
and set it so it can't be
No it is not possible to install a *third party* app as non-removable by the
user.
If you are building your own device, sure, you can put whatever apps you
want in the system image and they can't be uninstalled by the user because
the entire system image is read-only. That is entirely different
On Tuesday, August 2, 2011 3:13:26 PM UTC-4, Dianne Hackborn wrote:
Also just to confirm -- it is indeed not possible for a third party app to
silently install another third party app.
Though it is possible for a 3rd party app to silently augment its current
functionality with additional
That isn't the same thing. It still can't do anything more than the
permissions you allowed it.
NDK or Java is irrelevant -- you could just have a little scripting engine
and download code for it. Or whatever. Trying to prevent apps from doing
dynamic code execution is kind-of a doomed battle.
On Tuesday, August 2, 2011 6:17:53 PM UTC-4, Dianne Hackborn wrote:
That isn't the same thing. It still can't do anything more than the
permissions you allowed it.
That's why I said additional code operating within its current permissions
limits
NDK or Java is irrelevant -- you could
You can't introduce anything new to the manifest: no new activities, no new
services (which means no new IME, live wallpaper, etc), no new receivers
(thus no new app widgets, device admins, etc), no new content providers.
On Tue, Aug 2, 2011 at 8:30 PM, Chris Stratton cs07...@gmail.com wrote:
Hi,
I have one requirement of installing the apk without user intervention.
I know there is very straight forward way to install the apk
programmatically but that requires the user action. I want the way where
user action is not required and that will happen in background.
It is required
On Tue, Aug 02, 2011 at 09:24:39AM +0530, Mahavir Jain wrote:
I have one requirement of installing the apk without user intervention.
Ummm, right. No. First, I'm almost 100% certain that that's impossible,
and if that 1% applies, and it is possible, I'll be royally pissed off.
Second, even
12 matches
Mail list logo
