On Nov 10, 6:12 pm, Mark Murphy <[EMAIL PROTECTED]> wrote:
> dreamerBoywrote:
> > Thanks for the reply, Mark (I recognize the name - I read your book.)
>
> In the ACTION_CALL documentation, it states:
>
> "Note: there will be restrictions on which applications can initiate a
> call; most applications should use the ACTION_DIAL."
Whoever wrote that sounds like a politician - lots of room to maneuver
there -
>
> Now, probably it will work, as there have been recent tutorials
> demonstrating that it works from an activity, but I could see where this
> might get locked down sometime in the future.
Ahhh - I miss the good ole days when there was something called a
SecurityPolicy that one could customize ...
>
> > I am also wondering if there exists within the exposed Android API, a
> > way to hang up a call in an automated fashion. No appropriate intents
> > exist - it seems the only remaining possibility is calling finish() or
> > finishActivity(ACTIVITY_ID) on the Activity used to place or answer
> > the call. However, there is nothing in the docs which actually states
> > that. If I can get past my currently difficulty, I will definitely
> > test it.
>
> You could putter through the source code to see how the in-call
> application handles it. Again, whatever technique it uses is probably
> not for public consumption, your mileage may vary, do not taunt Happy
> Fun Android, etc.
I thought that Android was supposed to be about empowering developers
to create new breeds of applications.
>
> > I'll be reconfiguring the program to see if I can get different
> > results - perhaps I missed something simple in the Manifest. However,
> > a NullPointerException really does merit some explanation.
>
> Well, hackbod took a guess, and her guesses are pretty damn good.
According to my logCat readout - onCreate was already called a while
back - time to drill in deeper I guess.
I'm wondering why my attempt to install my own Instrumentation object
doesn't appear to be working (at least, none of the lifecycle
callbacks are talking to me).
>
> Is whatever Context represented by initiateCall "real"? For example, if
> initiateCall is some Activity you instantiated yourself as part of this
> automated , that may not be fully-formed (i.e., gone through the normal
> lifecycle) and therefore may not be able to start other activities.
Yep, it's possible that I got my life cycle out of order .. working on
that -
>
> I hate to be the bearer of bad tidings, since you read my book and all
> ;-),
Actually your book, Haseman's book ("Android Essentials"), Gramlich's
book ("Programming in Android"), and DiMarzio's book ("Programming in
Android").
> but I'm not terribly hopeful you'll be able to place a call,
> initiated by some remote application, automatically, without user
> intervention.
I could think of some quite useful applications that would utilize
automated calling.
Leave a voice or text message for a bunch o' people. Try to contact
computer support or the IRS every 15 minutes - if someone actually
picks up, then transfer the call to the user ...
Yes, I suppose the latter capability could be used in a malicious way
e.g., to stalk someone - however, there's something called a "Previous
Number Dialed" button which can be used to do the same thing manually.
>
> Or, to put it another way, if it works, it'll scare the crap out of me,
> because there's all sorts of nasty things one can do with that technique.
>
Yes, that situation already came up in the case of Applets ...
download an Applet - it will steal your passwords, start emailing
advertisements for erectile dysfunction cures, harass old ladies
etc...
See:
http://www.securingjava.com/chapter-two/
Not saying you're wrong - Android designers may have indeed been
afraid of this but if there are limitations they should be enumerated
somehow - sigh.
> --
> Mark Murphy (a Commons Guy)http://commonsware.com
> _The Busy Coder's Guide to Android Development_ Version 1.4 Published!
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
