Thank you Roman, I will find some other solution.
On Sep 15, 11:58 pm, "Roman ( T-Mobile USA)" <roman.baumgaert...@t-
mobile.com> wrote:
> Using code in the Android source directly instead of the SDK API's is
> always a risk.
> Your application might work for only a temporary time. In cases of
> framework code changes the chances are high that your app breaks.
>
> Use the APIs which are offered on SDK level ....
>
> --
> Roman Baumgaertner
> Sr. SW Engineer-OSDC
> ·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 Sep 15, 6:28 am, Pentiumao <[email protected]> wrote:
>
>
>
> > Hi everyone:
> > I have one problem when developing a sms application. I saw most
> > example code used the android.provider.Telephony package, but
> > that only exist in Android open source project, not in standard SDK.
> > Most people say : that means you should not use it in your
> > application. As you know, there is one application(com.android.mms)
> > runs in emulator and work well, I read its source and it did use some
> > package just like I mentioned before( only exist in open source
> > project), e.g. android.provider.Telephony.Mms. That really puzzled me.
> > Anyone can help me? Thank you.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
