If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite
No, its the decision from the kodi devs to drop the support for all pre android 5 versions. And and the problem by this decision is that android 4.x is more used as 5 and 6 together.
No, its the decision from the kodi devs to drop the support for all pre android 5 versions.
If the features they need aren't in pre 5.0, it would be dishonest to make a Kodi 17 without them for older Androids.
They switched to the unified MediaCodec system of Android, that is fully fledged only starting at 5.0.
That's not eye candy, it abstracts all kinds of shitty hardware acceleration used in the differen SoCs, so that you can just offload to that that will than take care of offload on the right hardware.
And and the problem by this decision is that android 4.x is more used as 5 and 6 together.
Kodi development is mostly for OS that don't have these stupid restrictions, so their team cannot just double and keep porting Kodi to all custom shit Android runs on. (cough Amlogic cough)
The positive news is that MediaCodec is now a standard, and is one less reason they will have to drop support of older Android versions.
Can back that. Better performing Kodi is always cool, especially for these that use a Raspberry PI 2
Eh, I can stream rips of my DVDs to Kodi 16.1 on my Raspberry Pi 2, but it flat out won't play rips of my Blu Rays in mkv (Matroska) h.264 - even from local USB storage.
Comment