If you are creating applications to distrubute via the market place then you have to use just use the documented/supported functionality from the Android SDK.
As had been said repeatedly in these groups - if you get your code to work today using functionality NOT supported by the SDK there is NO guarantee that it will continue to work tomorrow. If you need to use the platform code then you will have to build your own device. -- RichardC On Oct 26, 4:46 pm, DulcetTone <[email protected]> wrote: > I have the Android open source tree, and can even build within it my > own voice dialer, cribbed from the stock Google VoiceDialer. However, > my understanding is that doing it this way submerges my app within a > firmware image, and it does not give me the means to throw its > finished form onto (say) Android Market. > > How can I do this within an SDK environment? I need access to classes > that are apparently not a part of what is available to a purely SDK- > crafted app. Examples of what I cannot get to are: > > android.bluetooth.* > android.os.SystemProperties > android.speech.srec.* > > Do I code from the Android source and somehow extract my app from the > firmware morass? > Do I somehow tweak my Eclipse settings (e.g.: add a library or jar) to > gain access to this from within an SDK installation? > > Thanks in advance for some explicit instruction. Build environment > set-up has always been the most challenging aspect of this work for > me! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
