History of VemsDisplayOnBrokenAndroidVersions
Older Newer
2019-02-18 15:48:50 . . . . 84-236-105-82.pool.digikabel.hu [android 9.x broken in many ways; cannot run many apps that other androids run]
2019-02-18 15:39:02 . . . . 84-236-105-82.pool.digikabel.hu [android 9.x broken in many ways; cannot run many apps]


Changes by last author:

Added:
[Android 9 cannot run apps reliably: Lots of apps crashing]

OS software should maintain compatibility, even when adding new features (new APIs, new API functions, or new special cases).

Breaking APIs is very unfortunate in case of OS, because it results in some programs operating reliably only on old OS versions (eg. Android 4..8) while NOT on newer incompatible versions (Android 9.0 ?)

Unfortunately, while OS-es keep acquiring new backdoors, surveillance, and sometimes useful features, breaking APIs and failing to execute SW sometimes happens. (eg. PHP changed multiple times in major incompatible ways, especially in the early days of internet). In lucky cases there is clear indication of the error (eg. out of memory; or missing variable; or some explicite permission required).

Android used to be quite reasonable regarding compatibility, but apparently, now, without competition, Android is getting broken as well. Investigating if there is some hope, or android 9.x is just plain broken at the time being.

Collecting data about how new Android became unable to run software, that previous, working Android versions executed well

Permission, configuration perhaps ?

----

Collecting symptoms / use cases / test cases. Please provide as detailed information as possible (just saying Android 9.0 is NOT enough)

* phone / tablet manufacturer, model, type

* architecture (armhf, aarch64, x86_64, or ... ? )

* android version

** linux kernel version, date

* symptom (eg. starts and crashes after ... sec )

** always after same amount of time, or sometimes ..., sometimes more ... ? (or usually after some certain action)

* vemsdisplay version (under android settings / installed applications); and vemsdisplay installed size (APP + data + caches all could be interesting, not just the sum)

** vemsdisplay.apk date (size, md5sum if possible)

* other relevant information ?

** was it an upgrade from ... vemsdisplay version, or first install ?

----

* android 9 om My (?) phone and vems APK crash all the time

** ... might be useful after some more information

----

Any android 9.x that runs [VemsDisplay] reliably ?

* ... ?

----

Android 9.x URLs, many sicknesses (most not related to vemsdisplay)

* [Android 9 cannot run apps reliably: Lots of apps crashing] (means android 9 OS kills the application).

* [Pie problems]

* [android 9.x issues]

** "faulty 2xl" .. is that relevant ?

** other known android 9.x bug perhaps ?

* [generic app-crash checklist] ... clear cache unlikely to help if android kills the app (we sometimes say "app crashing", but it's android 9.x that is actively killing the app; not the application exiting, usually)

Even if android 9.x might be the shittiest ever software released by google,

* perhaps the issue is more complex, and there is some special circumstance that vemsdisplay should handle differently (although vemsdisplay is using very simple API-s, mostly available since android 2.x).

* Perhaps related to the way vemsdisplay was built (SDK version, or metafile, or similar ?)