-
-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
drop support for api10 #122
Comments
I have a Samsung i9000 s1 that is still not on 4+ |
I'm using a Samsung Galaxy S4 Mini (serranoltexx) with Android 4.4 (or still cyanogenmod 11 without Google apps, to be more precisely) and I don't know anybody who uses a version < 4.0. |
Old devices can be used as GPS trackers, but they don't support SBAS, GLONASS, BeiDou, so accuracy of such tracks is worse. I use Suntimes widgets for two places to plan my car trips/repairs during bright part of the day. My main device is Redmi 3 with Android 7.1 (Lineage OS). Previously I used an python script with same functionality at Nokia E71. Other use cases: navigation with Osmand, track recording for openstreetmap, Car PC with hobdrive. There is Heavens Above app for nightly events, which shows same information about dusk/dawn. My older devices:
P.S. Statistics is wrong. Google Play just don't work on old devices, so I use f-droid or install apps manually. |
Reverts changes to gradle-wrapper. Unfortunately upgrading the gradle version isn't possible without dropping support for api10 (see forrestguice#122). Bumping the gradle version also means bumping the buildToolsVersion and the compileSdkVersion (and support libraries). These are basically stuck at version 25 until the decision is made to drop api10 (currently postponed for as long as possible).
Some people say using any Android older than 5.0 is a security risk. Unfortunately Android has quite a lot of security exploits and vendors stop providing security fixes rather soon (less than two years after sale). I'm at android 8.0 (upgraded from original 7.0), and the older device I had was at 4.01, but when GPS stopped working (GPS roll-over?), I sold it... |
From https://developer.android.com/topic/libraries/support-library/index.html
I'd like to continue supporting older devices but dropping support is an eventuality. The targetSdkVersion is currently set to 25 and is going to remain that way into the forseable future. I'll continue to support api10 until forced to bump the version.
I'm not sure when that will happen, but using new api features will of course mean upgrading. The last time I felt compelled to upgrade the build was the introduction of Lollipop (api21) to support changes to permissions.
Personally, my last Gingerbread based device died a few months ago, and https://developer.android.com/about/dashboards/index.html only reports 0.5% - to say most people have upgraded is an understatement. However, I'm not really sure that statistic includes devices that are no longer used as phones (and are without network access to report to gplay). My impression is that older, cheaper, obsolete devices are frequently used as GPS trackers (which was my motivation for supporting them).
Informal poll... What do you think? What version is your device running? Do you still own an Android device running api10? (or even know of anybody). How about api14, or api15?
The text was updated successfully, but these errors were encountered: