well that was a very well considered response, thanks.
you are probably right, undertaking a lockscreen right off the bat is
probably not a good idea. you see, the reason why i wanted to develop
one was so that i could make a passworded lockscreen, but the password
would have only been a backup. The primary unlock method would have
been whenever the application detects a specific RFID tag with NFC. i
monkeyed around with the intents in your widgetlocker app
(com.teslacoilsw.widgetlocker.UNLOCK) in an attempt to call that
intent from NFC task launcher, but i couldnt make the intent work, so
i figured i would just try to write my own, lol.
1. thanks, i will make learning how to run services my next task
2.yes, i meant my own activity, moveTaskToBack() will probably work
perfectly.
On Dec 18, 3:30 pm, Kevin TeslaCoil Software ke...@teslacoilsw.com
wrote:
But does this mean that you guys are opposed to well known apps
such as WidgetLocker, or Lockscreen Agenda?
Well I'm the developer of WidgetLocker, so I'm not opposed to it at
all :P. But this list is about developing apps that following the
documentation, guidelines and restrictions of the SDK. WidgetLocker
does not. I know it's hypocritical but I recommend other app devs,
especially ones just starting, follow the SDK. It's safer and easier,
and (mostly) protects you from fragmentation (I test against ~20
devices. I still need more). As you noticed, this list isn't very
helpful if you chose to ignore the SDK rules. I imagine most devs that
do, including myself, don't discuss it much. If you choose to ignore
them, you're on your own.
I wish to make an app that
acts as a lockscreen. it would disable the home button, disable the
back button, and then it would dismiss itself upon a successful entry
of a password.
Implementing security in an app, rather than at the system level, is a
huge task and well beyond the scope of this list. There isn't even
anyone to discuss it with, as it has not been done. Find an app that
implements security (Note: WidgetLocker does not. There is good
reason.) and if you can't bypassing it in less than 5 minutes, you
aren't trying hard enough. Android is designed to disallow apps from
blocking other apps.
Even ignoring the Home and recent apps buttons, what about an incoming
call? Or a phone reboot? Or a SMS popup? Or any notification in the
notification bar for that matter? Or a malicious app? Or a task
killer? Or the system task killer? Or out of memory? Or a bug causing
a force close? It certainly is possible to display a screen that
prompts for a password and when the password is enter the screen
disappears. But implementing it in a manner that is more than just a
false sense of security is very different. I theorize that with root
and/or a device admin and a slightly-to-incredibly awkward user
experience it's possible, but even if that's true it's a lot of work
and a lot of testing and I guarantee you'd run into fragmentation
issues of trying to support Sense vs Blur vs TouchWiz vs Stock. A
custom rom, rather than an app, definitely could do this, but again
this list is not the place to discuss that (There's a firmware
building/modifying list for that kind of thing).
1. how do i make an application launch when the screen is activated?
ACTION_SCREEN_OFF and ACTION_SCREEN_ON broadcasts. You'll need a
service running to receive them (not a manifest receiver). Also note
that no app can start within 5 seconds of the Home button being
pressed, so Home, screen off, screen on, and you're delayed.
2. what method does one call to dismiss an application? (for example,
when a password is entered successfully)
Your own activity you mean? finish() or moveTaskToBack().
--
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
