[EOL] Android 4.0-4.2

pazos · 06-25-2023, 07:36 PM

End of Life for Android 4.0-4.2 devices

NYFAQ (not yet frequently asked questions)

Q: when?
A: Most likely v2023.06 will be the last with 4.0-4.2 support.

Q: why?
A: Modern toolchain

Q: app x runs on Android y. Why this don't?
A: KOReader != app x

Q: Will be possible to backport new features to unsupported devices?
A: Nope. But if you backport something that's not trivial please keep us informed

Q: Will be possible to target non supported APIs building from source?
A: Nope, at least not easily. You'll need to revert each commit that relies on the new toolchain for each one of the libraries that KO uses, and there're a bunch of them. Things will become a mess after a while.

NiLuJe · 06-26-2023, 08:56 AM

Quote:

Originally Posted by pazos

Q: Will be possible to target non supported APIs building from source?
A: Nope, at least not easily. You'll need to revert each commit that relies on the new toolchain for each one of the libraries that KO uses, and there're a bunch of them.

And one of these will be harfbuzz, so, good luck reading stuff without fonts ;o).

Jellby · 06-27-2023, 12:02 PM

Quote:

Originally Posted by NiLuJe

And one of these will be harfbuzz, so, good luck reading stuff without fonts ;o).

Comics and scanned pdfs?

pazos · 06-27-2023, 04:33 PM

Quote:

Originally Posted by Jellby

Comics and scanned pdfs?

MuPDF and k2pdfopt will be bumped in the future and will likely require something newer than gcc 4.9

Frenzie · 06-28-2023, 12:44 PM

Ftr, the older Android NDK/SDK we use right now does have a slightly more recent version of Clang than it does of GCC which hadn't been updated for a couple of years at the time. It might give a really motivated party some leeway.

06-25-2023, 07:36 PM	#1
pazos cosiñeiro Posts: 1,374 Karma: 2200075 Join Date: Apr 2014 Device: BQ Cervantes 4	[EOL] Android 4.0-4.2 End of Life for Android 4.0-4.2 devices NYFAQ (not yet frequently asked questions) Q: when? A: Most likely v2023.06 will be the last with 4.0-4.2 support. Q: why? A: Modern toolchain Q: app x runs on Android y. Why this don't? A: KOReader != app x Q: Will be possible to backport new features to unsupported devices? A: Nope. But if you backport something that's not trivial please keep us informed Q: Will be possible to target non supported APIs building from source? A: Nope, at least not easily. You'll need to revert each commit that relies on the new toolchain for each one of the libraries that KO uses, and there're a bunch of them. Things will become a mess after a while.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Design and Development of Android Applications:Android Apps Solving Real Problem	amazon author	Self-Promotions by Authors and Publishers	0	04-03-2015 04:01 AM
Released 14 HoneyComb ROM MOD for Android OS 1.6 /Android OS 2.1 HCV13.0 B20	tipstir	Android Devices	0	05-20-2011 02:59 AM
Android Android news stumbles upon not-yet-released Amazon Android App store	sarah11918	enTourage Archive	7	03-22-2011 01:07 PM

06-28-2023, 12:44 PM	#5
Frenzie Wizard Posts: 1,727 Karma: 730679 Join Date: Oct 2014 Location: Antwerp Device: Kobo Aura H2O	Ftr, the older Android NDK/SDK we use right now does have a slightly more recent version of Clang than it does of GCC which hadn't been updated for a couple of years at the time. It might give a really motivated party some leeway.

Advert

Advert