Re: [android-developers] Re: invoking com.android.internal.*
Hello, Dianne, Thank you for the info. May I ask you several questions as follows: 1. What’s the internal implementation of “select network manually”? You may know the Android menu - Settings - Wireless networks - Mobile networks - Network operators - Search networks (select network manually). We want to know the internal implementation of “Search networks (select network manually)”. Does it call RIL lib directly? Or call Android internal classes (lib)? 2. If we want to design one APK to select network manually, can our own APK call RIL lib directly? If not, what’s the proper way to call RIL lib? 3. How to use Android internal classes on our own APK? We found some Android internal classes, such as com.android.internal.telephony.phone com.android.internal.telephony.cdma com.android.internal.telephony.gsm As we learned from internet, there are some Android internal classes, but SDK developers can’t obtain them. Our question is how can our own APK use (call) Android internal classes? Thank you. Helen -- 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
Re: [android-developers] Re: invoking com.android.internal.*
None of this has anything to do with this list. Please visit http://source.android.com to learn more about the Android firmware, including Google Groups that may be more relevant to you. On Tue, Jan 10, 2012 at 1:15 PM, Helen helen.t...@orchestratec.com wrote: Hello, Dianne, Thank you for the info. May I ask you several questions as follows: 1. What’s the internal implementation of “select network manually”? You may know the Android menu - Settings - Wireless networks - Mobile networks - Network operators - Search networks (select network manually). We want to know the internal implementation of “Search networks (select network manually)”. Does it call RIL lib directly? Or call Android internal classes (lib)? 2. If we want to design one APK to select network manually, can our own APK call RIL lib directly? If not, what’s the proper way to call RIL lib? 3. How to use Android internal classes on our own APK? We found some Android internal classes, such as com.android.internal.telephony.phone com.android.internal.telephony.cdma com.android.internal.telephony.gsm As we learned from internet, there are some Android internal classes, but SDK developers can’t obtain them. Our question is how can our own APK use (call) Android internal classes? Thank you. Helen -- 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 -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Warescription: Three Android Books, Plus Updates, One Low Price! -- 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
[android-developers] Re: invoking com.android.internal.*
I can't recommend doing any of the things you're trying to do, for the simple reason that you're putting yourself at the mercy of implementation changes with no notice, and you shouldn't expect to receive any support if anything goes wrong. I write code that's part of the Android platform, which uses private APIs and also exposes some. I have seen first hand what happens when a private API changes under my feet, or when I change a private API under someone else's feet, and I only have to be worried about source compatibility (and I have a testing team helping me find regressions, and plenty of time to do so before the code goes out). Trying to do the same thing in the wild with binaries would only be more painful. You need to assume that those private APIs *will* change. Most likely, either their implementation will change, or they'll stabilize, become public, and move to another package. That being said, if you really insist in doing what you're trying to do, you should do it with reflection instead of direct references. In case an API signature changes, that would at least allow you to detect it and display a meaningful error message. You're still entirely at the mercy of changes in the behavior of those APIs. You probably should explicitly compare the version of the phone that a user is using to the versions that you have explicitly against, and display a warning in case the user runs against a version that you haven't tested. JBQ On Thu, Dec 4, 2008 at 2:58 PM, dreamerBoy [EMAIL PROTECTED] wrote: Yes, I know about this URL and have downloaded much of the source code. The delicate problem is how to build in access to the internal classes that I need and have them be invoked correctly by Android. Question is, how to do this without in effect rolling your own version of Android i.e., doing a full build ... after all, (this probably includes Linux), there are 8 million lines of code in Android. This would likely turn into a project unto itself. I have an old android.jar from version 0.9 with the internal classes available. When I try to use that, the Eclipse aapt environment immediately figures out what I'm trying to do, fails my attempt, and gives me a snarky message saying that I'm going to have problems trying to do this. Monsieur Queru - any comment? Thanks dreamer On Dec 3, 10:10 am, Ash [EMAIL PROTECTED] wrote: Use GIT to checkout the source code and add the internals paths you need to your application. //android.git.kernel.org/platform/frameworks/base/telephony is what you are looking for, I think. --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: invoking com.android.internal.*
Yes, I know about this URL and have downloaded much of the source code. The delicate problem is how to build in access to the internal classes that I need and have them be invoked correctly by Android. Question is, how to do this without in effect rolling your own version of Android i.e., doing a full build ... after all, (this probably includes Linux), there are 8 million lines of code in Android. This would likely turn into a project unto itself. I have an old android.jar from version 0.9 with the internal classes available. When I try to use that, the Eclipse aapt environment immediately figures out what I'm trying to do, fails my attempt, and gives me a snarky message saying that I'm going to have problems trying to do this. Monsieur Queru - any comment? Thanks dreamer On Dec 3, 10:10 am, Ash [EMAIL PROTECTED] wrote: Use GIT to checkout the source code and add the internals paths you need to your application. //android.git.kernel.org/platform/frameworks/base/telephony is what you are looking for, I think. --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: invoking com.android.internal.*
If you want to use private APIs, you need to get the platform source and build it. You are only allowed to use private APIs if you are writing code that is built-in to the android system, so we really don't -want- to make it easy to do this unless you are doing it for the appropriate reason of working on the platform/system itself. On Thu, Dec 4, 2008 at 2:58 PM, dreamerBoy [EMAIL PROTECTED] wrote: Yes, I know about this URL and have downloaded much of the source code. The delicate problem is how to build in access to the internal classes that I need and have them be invoked correctly by Android. Question is, how to do this without in effect rolling your own version of Android i.e., doing a full build ... after all, (this probably includes Linux), there are 8 million lines of code in Android. This would likely turn into a project unto itself. I have an old android.jar from version 0.9 with the internal classes available. When I try to use that, the Eclipse aapt environment immediately figures out what I'm trying to do, fails my attempt, and gives me a snarky message saying that I'm going to have problems trying to do this. Monsieur Queru - any comment? Thanks dreamer On Dec 3, 10:10 am, Ash [EMAIL PROTECTED] wrote: Use GIT to checkout the source code and add the internals paths you need to your application. //android.git.kernel.org/platform/frameworks/base/telephony is what you are looking for, I think. -- Dianne Hackborn Android framework engineer [EMAIL PROTECTED] Note: please don't send private questions to me, as I don't have time to provide private support. All such questions should be posted on public forums, where I and others can see and answer them. --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: invoking com.android.internal.*
Those are private implementation/internal classes that aren't supported for use by 3rd-party applications. JBQ On Tue, Dec 2, 2008 at 5:32 PM, dreamerBoy [EMAIL PROTECTED] wrote: Does anyone know of a way to use classes in com.android.internal.* - e.g., com.android.internal.telephony.Call ? There is sample code in the Android source code distribution. My normal Eclipse-based Android development environment does not allow e.g., import com.android.internal.telephony.Call; Is there a special jar or something that can be downloaded? Thanks much. Paul --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
