Skip to content
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

Closed
forrestguice opened this issue Dec 4, 2017 · 4 comments · Fixed by #811
Closed

drop support for api10 #122

forrestguice opened this issue Dec 4, 2017 · 4 comments · Fixed by #811
Labels
Milestone

Comments

@forrestguice
Copy link
Owner

forrestguice commented Dec 4, 2017

From https://developer.android.com/topic/libraries/support-library/index.html

Caution: Starting with Support Library release 26.0.0 (July 2017), the minimum supported API level across most support libraries has increased to Android 4.0 (API level 14) for most library packages. For more information, see Version Support and Package Names in this document.

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?

@nutpantz
Copy link

I have a Samsung i9000 s1 that is still not on 4+
I only use it as a GPS logger once in a while and nothing else. And I have a HTC desire that is not updated to 4+ yet , but it's not used as all.
I'm the only person i know who has a phone running such an old Rom.
But then i have almost every phone i ever bought
(Just trashed my old Windows mobile devices and palm phones last month).
If your worried about it just keep the last viable apk for distribution for anyone who needs it.
Host it here github.
I know lots of people who are still on 4.4 kit Kat.
But nothing older that i can think of.

@HerHde
Copy link
Contributor

HerHde commented Feb 5, 2018

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.

@radioxoma
Copy link

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:

  • ONYX BOOX i63ML Newton on Android 2.3.1 (API Level 9, kernel 2.6.32.27) It has e-ink display and hardly useful for reading. No sensors, no GPS. It would be nice to turn it into static screen with currency, yr.no weather, and sun/moon state, but it will take too much time to setup.
  • Huawei QISU8110 (CyanogenMod-7-2013-01-09-UNOFFICIAL-u8120) - home microserver trough LinuxDeploy. Screen is small and broken, battery is weak for usage in field.

P.S. Statistics is wrong. Google Play just don't work on old devices, so I use f-droid or install apps manually.

forrestguice added a commit to Raulvo/SuntimesWidget that referenced this issue Oct 24, 2018
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).
@forrestguice forrestguice added this to the 1.0.0 milestone Dec 2, 2018
@sjvudp
Copy link

sjvudp commented Jan 12, 2020

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants