Re: [android-developers] Re: Android Lint Tool - Suggestions for 2 fatal problems (missed)

On Sat, Dec 15, 2012 at 9:12 AM, I.E. <inibehe@gmail.com> wrote:
> 1) We can't assume they are non-standard devices. We just see crash
> reports.

If you are distributing through the Play Store, you only have to worry
about devices that pass the CTS. Any other non-CTS-compliant device
with the Play Store is using a pirated copy of the store, and we have
no way of predicting the behavior of such devices. We cannot have all
non-compliant device flaws be Lint errors. Lint is for CTS-compliant
devices.

> 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.

It may if you are using ActionBarSherlock, I think, which is why I
mentioned it. I agree that the native action bar is probably oblivious
to setContentView().

> Many different devices. Examples: Acer Iconia tablet A500, Dell Streak
> 7, ARCHOS 70it2. Various Samsung devices: GT-P6800, GT-P6210, ...

Then these are problems in the CTS, and should be treated as such, as
the Acer, and probably the Samsungs, should be CTS-compliant. Feel
free to file issues on http://b.android.com with reproducible test
cases, to get new CTS tests added to cover these scenarios.

--
Mark Murphy (a Commons Guy)
http://commonsware.com | http://github.com/commonsguy
http://commonsware.com/blog | http://twitter.com/commonsguy

_The Busy Coder's Guide to Android Development_ Version 4.4 Available!

--
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en