The apps need to be rebuilt with the new API level for proper multi-window. support. It's not as bad as they make it out to be.
Which should be grounds for banning from Play store.https://twitter.com/CopperheadOS/status/775121015504564224 …
-
-
They sometimes get away with breaking compatibility (hidepid=2, stricter SELinux, dropping non-PIE support, etc.).
-
They're very willing to break native code, but the opposite is true for pure Java apps using only documented APIs.
-
Some examples of the outrage they are happy to endure: https://trac.ffmpeg.org/ticket/4928 , https://code.google.com/p/android/issues/detail?id=205565 ….
-
It's because of Android that FFmpeg got rid of ARM text relocations, since they dropped them in 32-bit API level 23.
-
Hopefully
@musllibc could have gotten them to do it too -- we don't support TEXTRELs anywhere but 32-bit x86. -
FWIW, if Clang + Bionic got static PIE support, they'd likely ban non-PIE static @ all API levels.
-
All you need to do static PIE is
@musllibc's rcrt1.o and binutils 2.26's --no-dynamic-linker. -
It seems that's not present for http://ld.gold , which is what Android uses on 64-bit ARM.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.