Re:Sign-in on Android 2.3.7 or lower will not be allowed sta...
by derefr on Monday August 02, 2021 @02:34PM
(#28040797)
That's interesting. If there are use-cases for this old version of Android, is there a reason that the people who want to build such devices, haven't created a "living" descendant OS forking off from Android 4.x, with the old APIs but a modern kernel et al? Sort of like the living GTK2 that stuck around for so long after GTK3.
Re:Sign-in on Android 2.3.7 or lower will not be allowed sta...
by zozbot234 on Monday August 02, 2021 @03:12PM
(#28041280)
You can add back the Gapps-free applications quite easily - clones of them are widely available in F-Droid, or as part of custom ROMs like LineageOS and formerly CyanogenMod.
Re:Sign-in on Android 2.3.7 or lower will not be allowed sta...
by derefr on Monday August 02, 2021 @03:27PM
(#28041479)
Sure, but then why put Android 4.x on these newer devices, rather than putting F-Droid/LineageOS on them?
Re:Sign-in on Android 2.3.7 or lower will not be allowed sta...
by baybal2 on Monday August 02, 2021 @04:10PM
(#28041967)
Post 4.X Android is almost a wholly different OS. It was the biggest API break, and a shift to much more over-engineered APIs.
Companies doing things like POS terminals, eKiosks, signage, set-top boxes, Android TVs, etc are not interested in that, and this is a big part of why 4.X is so prolific.
It's because it's the last Android version Google released without turning it unusable without Gapps.
It is simple to customise. Put any of the crazy CyanogenMod era skins on it, and then customise UI any way you want with your own brand look.
And it is simple to code for, unlike overengineered APIs of later Android versions, with simple raw filesystem access being a particularly highly sought feature.