Maybe, maybe not. They certainly failed to keep the MediaPlayer API stable when they swapped out OpenCore for StageFright. When they did that, they broke streaming AAC audio files. See http://www.androidcentral.com/fix-coming-froyo-audio-issues and its references for details.
That can legitimately be called "breaking the API" because following the API documentation correctly for 2.1 or earlier yields code that works on 2.1, but with no documenation in 2.2 requiring a change in the way it is used, the code fails on 2.2. That means the API is broken. I recall hearing complaints about other APIs breaking with new releases, but this is the one I know about. For all I know, the other examples may have been "cockpit errors". On Aug 17, 3:42 pm, Brad Gies <[email protected]> wrote: > Well.. I think that's exactly what they are doing by not releasing it as > a public API until it is stable. > > Brad. > > On 17/08/2010 3:31 PM, Indicator Veritatis wrote: > > > But then this is just another example of why Google needs to make the > > committment to keep such APIs stable. > > > On Aug 16, 11:08 pm, nexbug<[email protected]> wrote: > >> Everyday we get requests from our users for this functionality. We > >> have resisted the temptation to do this because the risk of a new > >> android release breaking this is scarier than telling no to a few > >> hundred customers. > >> Id advise against doing it. > > >> On Aug 16, 2:49 pm, RichardC<[email protected]> wrote:> > >> Google Calendar is not a supported API. > > >>> On Aug 16, 4:38 pm, Bender<[email protected]> wrote: > >>>> Hi! > >>>> I'm currently writing a class to access the android calendar, > >>>> retrieving and inserting new events does already work but I'm having > >>>> trouble to update existing events. With the the methods I already have > >>>> I could check the ID of the calendar I want to work with, which is 5. > >>>> I also could find out the ID of an event in that calendar which is 87. > >>>> I'm trying to update that event with this code (well actually it is a > >>>> bit different but I've shorten it a bit so it's not so much code to > >>>> read for you): > >>>> if(Build.VERSION.RELEASE.contains("2.2")) { > >>>> contentProvider = "com.android.calendar"; > >>>> } else { > >>>> contentProvider = "calendar"; > >>>> } > >>>> eventsUri = Uri.parse(String.format("content://%s/ > >>>> events",contentProvider)); > >>>> Uri updateEventUri = Uri.withAppendedPath(eventsUri, > >>>> String.valueOf(87)); > >>>> ContentValues event = new ContentValues(); > >>>> event.put("calendar_id", 5); > >>>> event.put("title", "Modified Title"); > >>>> mContext.getContentResolver().update(updateEventUri, event, null, > >>>> null); // mContext is the context of the activity which is using my > >>>> helper class. > >>>> (Of course the id's aren't hard coded in the original code. ;-) ) > >>>> The problem is, after that update, the event I wanted to change isn't > >>>> changed at all. I'm not recieving any error messages that the Uri is > >>>> wrong or something like that, so I have no idea why it isn't working. > >>>> I tried different calendar IDs and different event IDs but there was > >>>> no effect either. In the logs I've created the resulting Uri is > >>>> "content://com.android.calendar/events/87" which looks fine to me > >>>> since I'm running it on froyo. > >>>> I hope somebody has some advice for me. Sincerely, > >>>> Bender > > -- > Sincerely, > > Brad Gies > ----------------------------------------------------------------------- > Bistro Bot - Bistro > Blurbhttp://bgies.comhttp://bistroblurb.comhttp://ihottonight.comhttp://forcethetruth.com > ----------------------------------------------------------------------- > > Everything in moderation, including abstinence > > Never doubt that a small group of thoughtful, committed people can > change the world. Indeed. It is the only thing that ever has - Margaret Mead -- 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
