Hello, Thank you both for the constructive response. Through some testing, I have realized that the phone related classes will only work inside the phone process. I have been using TelephonyManager and LocationManager.
I understand the reasoning behind the current situation. At the same time, I am looking forward to a time when we can use Phone.java Thanks for the offer. I have been able to get RadioInfo.java partially working by-passing the need to use Phone.java. An initial high-level answer to your question is that, to start with, I would like to be able to have a fully functional RadioInfo.java. Alex Donnini On Apr 15, 8:02 am, Mike Lockwood <lockw...@android.com> wrote: > Yes, the LocationManager would be the proper way to get the > information you are asking for. It is the public API for location > services and already handles the IPC and permissions checking > necessary for transferring this information from the phone process to > an application. Unfortunately it currently does not provide the > detailed cell location information you are asking for. > > We could add the extra cell location information to the Bundle object > returned via the LocationListener.onStatusChanged() callback. If you > could make a proposal of the information that should be included we > could try to add it in a future release. > > Mike > > > > On Wed, Apr 15, 2009 at 12:37 AM, Dianne Hackborn <hack...@android.com> wrote: > > A lot of the telephony classes you'll see in the framework will only work in > > the phone process, because they do not have any IPC abstraction behind > > them. There is also significant work taking place on them, such as to > > support CDMA, that we have been fairly conservative about what is exposed to > > avoid having to break APIs. The official APIs you can use are > > TelephonyManager, for for location stuff you generally should be using > > LocationManager. > > > On Tue, Apr 14, 2009 at 7:51 PM, alexdonnini <alessdonn...@gmail.com> wrote: > > >> Hello, > > >> As I understand it, the Phone.java interface is not available to > >> application developers. This being the case (please confirm), how can > >> application developers access detailed phone related data such as > >> neighboring CID (refer to the Phone.java code for additional > >> information)? > > >> Retrieving this kind of information depends on the instantiation of > >> Phone (e.g. via makeDefaultPhone, or getDefaultPhones. > >> makeDefaultPhone cannot be used without special permission. > > >> It looks to me like somehow, for reasons I do not quite understand, it > >> is particularly difficult to access and manage phone location > >> information (e.g. have direct access to the Phone.java interface). > > >> Why is that? It cannot be a matter of security as testing of a > >> function and development of an application does not automatically > >> translate into publishing and approval of that application. > > >> I would appreciate anyone's feedback and help on this. > > >> Thanks. > > >> Alex Donnini > > > -- > > Dianne Hackborn > > Android framework engineer > > hack...@android.com > > > Note: please don't send private questions to me, as I don't have time to > > provide private support, and so won't reply to such e-mails. All such > > questions should be posted on public forums, where I and others can see and > > answer them. > > -- > Mike Lockwood > Google android team --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "android-framework" group. To post to this group, send email to android-framework@googlegroups.com To unsubscribe from this group, send email to android-framework+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-framework?hl=en -~----------~----~----~----~------~----~------~--~---
