Hi All
I want to block the functionality switch between Applications in
my Activity. Is it possible ?
Thanks
David
--
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
I want to block the functionality switch between Applications in
my Activity. Is it possible ?
Fortunately, no. The user can always press HOME.
--
Mark Murphy (a Commons Guy)
http://commonsware.com
Android App Developer Books: http://commonsware.com/books.html
--
You received this
exist some other alternative?
exist some method or function that capture when the press home key ???
2009/12/9 Mark Murphy mmur...@commonsware.com
I want to block the functionality switch between Applications in
my Activity. Is it possible ?
Fortunately, no. The user can always press
Occasionally people find hacks to kind-of do this, and when they do we fix
the platform to prevent it. Don't do this. The home key is the -only-
mechanism a user has to return to a known, trusted state. It is critical
for security that it do this, and apps can not prevent it.
On Wed, Dec 9,
But I do see some screensavers disable it. how can they do that?
2009/12/9 Dianne Hackborn hack...@android.com
Occasionally people find hacks to kind-of do this, and when they do we fix
the platform to prevent it. Don't do this. The home key is the -only-
mechanism a user has to return to a
if i ever mistakenly installed an app that disabled the home key, i'd
promptly reboot my phone, uninstall, and report it as malware.
On 12/9/09 11:31 AM, David Toledo wrote:
But I do see some screensavers disable it. how can they do that?
2009/12/9 Dianne Hackborn hack...@android.com
The idea is an application that is started at boot to prevent others from
entering if they do not know the protect key.
2009/12/9 Jeffrey Blattman jeffrey.blatt...@gmail.com
if i ever mistakenly installed an app that disabled the home key, i'd
promptly reboot my phone, uninstall, and report
IMHO Such a strict gatekeeper has to be very carefully implemented and
should probably be lower in the stack and not at the application layer.
On Wed, Dec 9, 2009 at 1:36 PM, David Toledo dtole...@gmail.com wrote:
The idea is an application that is started at boot to prevent others from
On Wed, Dec 9, 2009 at 11:31 AM, David Toledo dtole...@gmail.com wrote:
But I do see some screensavers disable it. how can they do that?
Please tell me the app so I can break it. :}
--
Dianne Hackborn
Android framework engineer
hack...@android.com
Note: please don't send private questions
i thought this was what the lock screen was for?
btw, whoever --- attaching a graphical sig is badish netiquette. not
just do readers end up with N copies of it, but it ends up being
Nsquared due to being attached to replies etc. please can it? thanks.
IMHO Such a strict gatekeeper has to
On Wed, Dec 9, 2009 at 2:40 PM, Jason Proctor
jason.android.li...@gmail.com wrote:
i thought this was what the lock screen was for?
The lock screen only supports gesture-based security locking. I know
someone for example who really wants to type in a code of some sort to
do the unlocking, not
Sorry, the platform currently does not support replacing the lock screen
from a third party app. There are some hacks people have done to make their
own lock screen, but if you actually want something that is secure then
you really are not going to be able to do this from an app.
On Wed, Dec 9,
On Wed, Dec 9, 2009 at 2:51 PM, Dianne Hackborn hack...@android.com wrote:
Sorry, the platform currently does not support replacing the lock screen
from a third party app.
Open platforms rule, or something.
--
Greg Donald
http://destiney.com/
--
You received this message because you are
On Wed, Dec 9, 2009 at 2:51 PM, Dianne Hackborn hack...@android.com wrote:
Sorry, the platform currently does not support replacing the lock screen
from a third party app.
Open platforms rule, or something.
so change the platform and release your version. all the tools and
code are there.
On Wed, Dec 9, 2009 at 4:17 PM, Jason Proctor
jason.android.li...@gmail.com wrote:
so change the platform and release your version. all the tools and
code are there. can't wait to see it.
As you might have guessed I alone don't have the resources for such a bug fix.
Just seems wrong to call
As you might have guessed I alone don't have the resources for such a bug fix.
Just seems wrong to call the platform open when it's really only as
open as Google sees fit to allow. Would it not be frowned upon if the
Linux Kernel developers started making kernel components vendors
couldn't
On Wed, Dec 9, 2009 at 5:04 PM, Jason Proctor
jason.android.li...@gmail.com wrote:
the issue isn't so much whether you can make changes, as whether
anyone will take them.
Or purposely writing code to break them as with the promises Diane
made on this topic.
apart from a few proprietary closed
Knowing Android engineers will purposely write code to
break any discovered workarounds for the restrictions isn't enhancing
security either.
Knowing Android engineers will purposely fix bugs that shouldn't have been
there in the first place enhances security.
Fixed that for you. :)
- Dan
Or purposely writing code to break them as with the promises Diane
made on this topic.
oh sorry i didn't know there were promises made re home button or
lock app replacements. what were they?
Making it impossible to replace the screen lock app doesn't enhance
security. Knowing Android
19 matches
Mail list logo
