> Android developers are not responsible for adjusting all their apps > to work on non-standard devices.
In theory yes. In practice no: 1) We can't assume they are non-standard devices. We just see crash reports. 2) If you have a high average app rating, and suddenly start recieving 1-star ratings after an update, you have to respond. 3) If you have a free app that uses advertising, and suddenly your daily app revenue goes down after an update, or users are uninstalling, then you have to respond. > The second problem, in particular, has nothing whatsoever to do with > Lint. So long as you have called setContentView() before messing with > the action bar, nothing more needs to be "requested". I think it is a Lint problem. I usually call getWindow().requestFeature(...) first and then call setContentView() to display the layout below the ActionBar / TitleBar. setContentView() doesn't know anything about the ActionBar, as far as I'm aware. > So, please provide some details as to which devices you are seeing > these problems on, so we can determine the proper course of action -- > thanks! Many different devices. Examples: Acer Iconia tablet A500, Dell Streak 7, ARCHOS 70it2. Various Samsung devices: GT-P6800, GT-P6210, ... -- 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
