New to Android Studio 3.1 is a C++ performance profiler to help troubleshoot performance bottlenecks in your app code. For those of you with a Room or SQLite database in their your app, we added better code editor support to aid in your SQL table and query creation statements. We also added better lint support for your Kotlin code, and accelerated your testing with an updated Android Emulator with Quick Boot.
The C++ profiler requires devices to be running Oreo.
Would have been too good. At least wee can see that < 8.0 are already EOL.
Well, we already knew that. Then again, Gingerbread has ben EOL for years and, to this day, there are devices being sold with it. If Google ever really wants to deal with this problem, they’ll have to play hardball.
I’m guessing they could do this kinda thing to stop new devices with gingerbread.
http://www.osnews.com/story/30240/Google_blocks_GApps_from_running_…
Assuming they have gapps as well.
Edited 2018-03-27 18:21 UTC
Gingerbread is down to a 0.3% share on the Google Play dashboard as of February. Google set the minimum API level for its support libraries to 14 (Ice Cream Sandwich) almost a year ago, so no new or updated apps will run on Gingerbread any more. If there are truly new devices with Gingerbread, they are a rounding error.
The new laggard version is KitKat (API 19), which is hanging on at 12%.
Edited 2018-03-27 18:59 UTC
rafial,
Not to take an opinion on whether or not to support gingerbread, but those app store figures are inherently biases towards new phones, which may or may not be what you want to measure.
I personally don’t use google’s store every month, much less every week. Assuming most users are like me and use the app store predominantly in the first few months of ownership, they could be significantly underrepresented by the app store metric despite being active users.
I don’t know how it’s measured but I think it’s counted if an app is updated, even I you don’t visit the Playstore
And there are plenty of users who even never visited the store (like my father, who is happy with a phone on some ancient version of Android, its “smart” parts basically not used…)
To my understanding, any device with the Play Store and internet access is periodically calling home (to see if there are updates) so will be counted.
Any device that doesn’t meet those conditions is likely not of interest to app developers.
FYI,
If you are using 3.01 and updating to 3.1, beware that ‘Instant Run’ seems to be broken. The workaround is just to turn off ‘Instant Run’…not an ideal solution.
The 3.2c8 Preview version on the ‘Canary’ channel doesn’t seem to have this issue, but has other issues with the built APK…I have not had time to fully investigate this, however.