Yes, that is why. The SDK does not provide access to everything, there
are internal APIs that some Android built-in apps use but third-
parties can (or should) not.



Yusuf Saib
Android
·T· · ·Mobile· stick together
The views, opinions and statements in this email are those of the
author solely in their individual capacity, and do not necessarily
represent those of T-Mobile USA, Inc.




On Aug 18, 12:31 pm, cyclopse <[email protected]> wrote:
> First of all thanks for your reply Justin.
>
> On 18 aug, 11:45, Justin Anderson <[email protected]> wrote:
>
>
>
>
>
> >  > Google is stating that code of other installed applications can be
>
> > > used in your own application.
>
> > Essentially what you can do is launch other activities/processes as long as
> > you know the intent and intent filters for the functionality you want to
> > include.  Typically this would be done with a call to startActivity() or
> > startActivityForResult().
>
> > > I would like to incorporate some functionality of the Phone-app into
> > > my own application, but have no idea where to start
>
> > What functionality of the phone app are you wanting to incorporate?
>
> > > (couldnt find anything useful in the SDK docs)
>
> > The information for using startActivity() and startActivityForResult() is in
> > the SDK docs.  Admittedly, it can be a bit hard to digest it all and apply
> > it to your own application, though.  I have had my fair share of struggles
> > with them.  :-)
>
> What i want to do is basically this: watch changes in call status (got
> this part already working), if there is an incoming call compare it to
> a list of numbers and block the incoming call if the phone number is
> on the list. There seems to be 2 problems with implementing this idea.
> The first problem is keeping your app running at any time (maybe a
> wake lock can fix this), the second problem is using functionality
> that actually is in the phone but not available in the SDK.
>
> I figured out that the Phone App which is in Android by default is
> keeping the RIL daemon busy, so making a new connection to the RIL
> daemon is not an option.
> According to the android architecture diagram the Phone App sits on
> the top layer, so i figured i might me able to use some functionality
> in the Phone app to be able to block/hangup a call.
>
> The phone app sits on top of everything and is able to block calls,
> why can't we? Is it because for some reason the phone app is the only
> app that is allowed to use some sort of internal functionality?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Beginners" 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-beginners?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to