[android-developers] Re: 1.5_r3 backward compatibility
Huh? My device hasn't been updated, and I bet that there are lots of countries where the mobile operators haven't sent out any updates. On 3 Aug, 01:59, Fred Grott(shareme) fred.gr...@gmail.com wrote: Peter all devices were updated to 1.5r3 by mobile operators so what devices are u targeting that have 1.5r2 or 1.5r1? Yes, they should explain this somewhere.. Fred Grotthttp://mobilebytes.wordpress.com On Aug 2, 12:59 pm, Peter Jeffe pje...@gmail.com wrote: Sorry if I missed this in the release notes, but if I build against the 1.5_r3 SDK are there any compatibility issues with running it on devices that are at previous levels of 1.5? I would certainly hope not, but I've learned not to make such assumptions. :-) -- Peter --~--~-~--~~~---~--~~ 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: 1.5_r3 backward compatibility
1.5r3 is compatible with 1.5r2, 1.5r1 and even 1.1 and 1.0 if you are careful about which APIs you use. On Sun, Aug 2, 2009 at 11:50 PM, Kaj Bjurmankaj.bjur...@gmail.com wrote: Huh? My device hasn't been updated, and I bet that there are lots of countries where the mobile operators haven't sent out any updates. On 3 Aug, 01:59, Fred Grott(shareme) fred.gr...@gmail.com wrote: Peter all devices were updated to 1.5r3 by mobile operators so what devices are u targeting that have 1.5r2 or 1.5r1? Yes, they should explain this somewhere.. Fred Grotthttp://mobilebytes.wordpress.com On Aug 2, 12:59 pm, Peter Jeffe pje...@gmail.com wrote: Sorry if I missed this in the release notes, but if I build against the 1.5_r3 SDK are there any compatibility issues with running it on devices that are at previous levels of 1.5? I would certainly hope not, but I've learned not to make such assumptions. :-) -- Peter -- Romain Guy Android framework engineer romain...@android.com 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 android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: 1.5_r3 backward compatibility
I think that is sdk release, all released can run on Android 1.5 On Mon, Aug 3, 2009 at 9:59 AM, Fred Grott(shareme) fred.gr...@gmail.comwrote: Peter all devices were updated to 1.5r3 by mobile operators so what devices are u targeting that have 1.5r2 or 1.5r1? Yes, they should explain this somewhere.. Fred Grott http://mobilebytes.wordpress.com On Aug 2, 12:59 pm, Peter Jeffe pje...@gmail.com wrote: Sorry if I missed this in the release notes, but if I build against the 1.5_r3 SDK are there any compatibility issues with running it on devices that are at previous levels of 1.5? I would certainly hope not, but I've learned not to make such assumptions. :-) -- Peter -- Regards, Michael Leung http://www.itblogs.info http://www.michaelleung.info --~--~-~--~~~---~--~~ 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: 1.5_r3 backward compatibility
On Aug 3, 2:04 am, Romain Guy romain...@google.com wrote: 1.5r3 is compatible with 1.5r2, 1.5r1 and even 1.1 and 1.0 if you are careful about which APIs you use. Thanks Romain, can you confirm that there were no API changes between 1.5r1 and 1.5r3? And Fred, there is definitely no way you can expect a given level of firmware to be universally used. We're still getting users on 1.1 (well, not since we recently required 1.5 :-), and then you've got custom builds, dev builds... So that's why I'm really hoping that Google will allow developers to publish multiple builds for different OS versions in the future. It was very tough to have to hold off releasing 1.5-specific features until a critical mass of users were upgraded to 1.5. At this point there's no turning back on increasing platform divergence, and the Market has to allow for us to publish builds for each release we choose to support. Romain, do you know if this is in the plans? -- Peter --~--~-~--~~~---~--~~ 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: 1.5_r3 backward compatibility
Peter Jeffe wrote: So that's why I'm really hoping that Google will allow developers to publish multiple builds for different OS versions in the future. It was very tough to have to hold off releasing 1.5-specific features until a critical mass of users were upgraded to 1.5. At this point there's no turning back on increasing platform divergence, and the Market has to allow for us to publish builds for each release we choose to support. I suspect the answer, at least in the short term, looks like this: http://android-developers.blogspot.com/2009/04/backward-compatibility-for-android.html That being said, this is also another fine area for competing markets to out-do the Android Market: offer N app flavors for different firmware/hardware, yet roll them all up for the purposes of popularity, ratings, etc. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy Android App Developer Training: http://commonsware.com/training.html --~--~-~--~~~---~--~~ 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: 1.5_r3 backward compatibility
On Mon, Aug 3, 2009 at 12:18 PM, Peter Jeffe pje...@gmail.com wrote: Thanks Romain, can you confirm that there were no API changes between 1.5r1 and 1.5r3? There aren't any -- you can tell because the SDK version in android.os.Build has not changed. So that's why I'm really hoping that Google will allow developers to publish multiple builds for different OS versions in the future. It was very tough to have to hold off releasing 1.5-specific features until a critical mass of users were upgraded to 1.5. At this point there's no turning back on increasing platform divergence, and the Market has to allow for us to publish builds for each release we choose to support. Romain, do you know if this is in the plans? At some point it will, though I don't know when that will be. This is what android:minSdkVersion was introduced in Cupcake for. -- 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. --~--~-~--~~~---~--~~ 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: 1.5_r3 backward compatibility
On Mon, Aug 3, 2009 at 12:18 PM, Peter Jeffepje...@gmail.com wrote: On Aug 3, 2:04 am, Romain Guy romain...@google.com wrote: 1.5r3 is compatible with 1.5r2, 1.5r1 and even 1.1 and 1.0 if you are careful about which APIs you use. Thanks Romain, can you confirm that there were no API changes between 1.5r1 and 1.5r3? If there were API changes then the API level would have changed. All Android 1.5 platforms in the 1.5 r1 to r3 SDKs show as API 3. The update of the SDK to r2 and r3 are only for security fixes in the emulator system image. See the original post on these mailing list for details. Xav -- Xavier Ducrohet Android Developer Tools Engineer Google Inc. --~--~-~--~~~---~--~~ 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: 1.5_r3 backward compatibility
On Mon, Aug 3, 2009 at 1:32 PM, Dianne Hackborn hack...@android.com wrote: So that's why I'm really hoping that Google will allow developers to publish multiple builds for different OS versions in the future. It was very tough to have to hold off releasing 1.5-specific features until a critical mass of users were upgraded to 1.5. At this point there's no turning back on increasing platform divergence, and the Market has to allow for us to publish builds for each release we choose to support. Romain, do you know if this is in the plans? At some point it will, though I don't know when that will be. This is what android:minSdkVersion was introduced in Cupcake for. Actually, Market should have been supporting android:minSdkVersion for a while, since that was done way back for 1.5. Is it not working? -- 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. --~--~-~--~~~---~--~~ 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: 1.5_r3 backward compatibility
Xavier and Diane, thanks for the confirmation on the SDK level, I was hoping that was the case! On Aug 3, 3:35 pm, Dianne Hackborn hack...@android.com wrote: Actually, Market should have been supporting android:minSdkVersion for a while, since that was done way back for 1.5. Is it not working? Yes, that works just fine, but it limits us to only being able to publish an apk for that specific level and above--unless we want to create an entirely different app for each supported OS level, which is unreasonable for most apps. Normally (say for PC or Unix software) you would make different install packages available for different combinations of OS and version, or perhaps have a single install package that can handle a set of different OS versions. But at the moment we can't do that on Android, we can only specify a minimum supported SDK level. So what we really need to be able to do is publish, for the same application, one or more apks, each with a minimum and maximum SDK level. If this was available today then I could still support users still on 1.0 and 1.1, but I was forced to abandon them because I wanted to have 1.5-specific features in my app. That's not good user support, and it's going to get much worse very soon as the Android versions proliferate and we have quite a few different levels of OS out there at any given time. We developers need to be able to choose which versions we support and we need to have the tools available to do that. Hope that makes sense. -- Peter --~--~-~--~~~---~--~~ 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: 1.5_r3 backward compatibility
Peter all devices were updated to 1.5r3 by mobile operators so what devices are u targeting that have 1.5r2 or 1.5r1? Yes, they should explain this somewhere.. Fred Grott http://mobilebytes.wordpress.com On Aug 2, 12:59 pm, Peter Jeffe pje...@gmail.com wrote: Sorry if I missed this in the release notes, but if I build against the 1.5_r3 SDK are there any compatibility issues with running it on devices that are at previous levels of 1.5? I would certainly hope not, but I've learned not to make such assumptions. :-) -- Peter --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
