No mention has been made on a lot of the installs as to if they installed via the store, or an apk.
The store looks at device type (tablet, phone, etc.), Android version, and perhaps other things to determine if it should allow a download, and I beliece that stuff is set by the software owner/publisher, not determined by the app directly.
As a counter argument, if the kernel were the factor, kernel upgrades as part of Android patching would cause already loaded apps to no longer work, and I have never see that happen (or a bunch of patches immediately after an Android patch).
And I speak to Linux (or *nix in gereral) since it's what Android is rooted, and it's because it's where my professional experience lies (Ultrix, AIX, SunOS, Solaris, Ultrix, Irix, whatever Convergent called thiers, SysV68K SysV88K (Motorola) and a few others . . .
переключити цитоване повідомлення
Показати цитований текст
On December 30, 2024 7:20:57 PM EST, Jerry Stuckle <ai0k@...> wrote:
Well, first of all, Linux is only one OS out there, so it is not really a great reference. There are many other OS's out there, several of which I've worked on, from embedded systems to mainframes.
But I never said an update to libc forced a kernel update. In fact, just the opposite. The kernel is the lowest level and everything must interface to it. And while developers do their best to maintain compatibility, it's not always possible. This is why sometimes an application requires a certain library version.
If what you are saying is true, why is it I (at the latest kernel level) can't install it but other can?
73,
Jerry, AI0K
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
