{
  "name": "newdroid",
  "icon": "https://bb10repo.whytofly.de/img/bb10-newdroid.png",
  "category": "Runtime",
  "type": "cli",
  "author": "whytofly",
  "homepage": "https://bb10repo.whytofly.de/",
  "description": "newdroid — upgrades BlackBerry 10's built-in Android runtime from Jelly Bean 4.3 (API 18) to Marshmallow 6.0 (API 23), so modern Android apps install and run on a 2013 phone. No reflash, nothing written into the Android Player, fully reversible.\n\nREQUIRES OS 10.3.3.3216 and bb10-rootd (installed with it). The runtime was rebuilt from that exact OS build's own Android files, so the package refuses to install on any other version and names the version it found.\n\nHOW IT WORKS. The new runtime is one image file that is mounted OVER the Android Player's system folder after each boot, in memory only. The Player's own files on disk are never modified. Every restart therefore boots the untouched stock runtime first -- which is what keeps root safe -- and a minute or two later (a few minutes the first time) the image is mounted again and Android 6 starts. A notification says \"Android 6 runtime: Ready\" when it is live; an Android app opened before then runs on the stock runtime and is closed when the switch happens, so wait for it. If the patched runtime ever fails its health check, it switches itself back to stock for that boot; after two failed boots in a row it stays stock until you run `newdroid on`.\n\nWHAT CHANGES. BB10 ships a real Dalvik VM but a 2013 API surface. This package raises it in two layers: a rebuilt boot image (29 framework jars and 64 system apps, re-patched as one consistent set) and a class injector that adds the API-19..23 classes at startup. Measured on the installed package: the API-23 conformance suite reports 556 pass, 0 fail (plus 11 declared gaps and 19 checks that do not apply to this hardware).\n\nWHAT YOU GET. WhatsApp, Firefox, VLC, NewPipe, AntennaPod, Organic Maps, Briar, K-9/Thunderbird, KeePassDX, Aegis, F-Droid and more. Working camera2 and CameraX (including the image-analysis path QR scanners need), MediaSession lock-screen controls, JobScheduler and androidx.work background jobs, TLS 1.2 using your device's own trusted certificates, hardware video decode, telephony, SMS, NFC and the microphone.\n\nWHICH APPS. Apps that need Android 7.0 or newer (minSdk 24+) cannot install -- Android's own installer refuses them, and BlackBerry shows \"Unable to install this app\". Many current releases need 7.0+; look for an older version. For example the current F-Droid (2.x) needs Android 7, while F-Droid 1.23.2 supports Android 6 and works. BlackBerry pauses an Android app as soon as you switch away from it unless it is running a background service (this is BlackBerry's own behaviour, not newdroid's), so keep F-Droid open on screen during its first repository update, which takes a few minutes. Apps must include 32-bit ARM code (armeabi-v7a). App stores work: Aurora Store (bb10-aurora, apps from Google Play) and F-Droid (bb10-fdroid) install apps as normal BlackBerry apps, including Google Play's split APKs; a downloaded .apks / .xapk / .apkm file installs with `newdroid install-apks <file>`.\n\nWHAT IT IS HONEST ABOUT. This is a faithful API-23 surface on a 2013 VM, not an Android 6 phone. It answers \"no\" where a real Android 6 device would -- no fingerprint reader, no app widgets. Apps needing OpenGL ES 3.0 cannot render: the GPU tops out at ES 2.0.\n\nINSTALL. `apk add bb10-newdroid` (or install it from Rubus). If bb10-rootd is already running, Android 6 is set up right away and every step is shown; on a first install bb10-rootd starts at the next restart, and the runtime then sets itself up automatically -- restart once, nothing else to do. It needs about 280 MB free.\n\nREMOVE. `apk del bb10-newdroid` switches back to the stock runtime immediately and deletes the image; since the Player's files were never touched there is nothing to restore. Even without root, removing it guarantees the next restart is stock.\n\nTRUSTED CERTIFICATES come from your device's own certificate store. If you add or remove certificates, the runtime picks the change up at the next restart (that boot takes a few minutes longer while it rebuilds).\n\nCommands (from Term49 or Rubus): `newdroid status`, `newdroid off` / `newdroid on`, `newdroid log` (the last boot, plus a history of earlier ones), `newdroid queue` (install the Android apps that are waiting now), `newdroid install-apks <file>`.",
  "history": [
    {
      "version": "2026.11.18-r301",
      "released": "2026-11-18",
      "changes": "- Less garbage-collection work in busy apps. Apps that create a lot of short-lived objects (for example ones built with Jetpack Compose) now get more free memory after each clean-up, so they need far fewer of them.\n- Measured on a Classic while scrolling Aurora Store: 7 clean-ups instead of 16-20 in the same 11 seconds, 130-150 ms of app freezes instead of 310-530 ms, and about 3 seconds less processor time spent cleaning up. Busy apps use about 10 MB more memory; small apps are almost unchanged.\n- Frame rates in that test stayed within their normal variation; the gain is less processor work (heat, battery) and fewer short freezes.\n- Android 6 CTS on a Q5, unchanged from r300: Content 613/630, Database 263/264, Graphics 1025/1051, Jni 62/62, Os 399/409, Text 698/712, Util 203/206. 12 of 12 installed test apps start, draw and pause cleanly."
    },
    {
      "version": "2026.11.18-r300",
      "released": "2026-11-18",
      "changes": "- Code in an app's extra code files (most modern apps ship several) now gets Dalvik's bytecode optimisation like the rest of the app. Before, it was loaded without it.\n- Correction to this note: an early quick measurement suggested much smoother scrolling in Aurora Store; a careful back-to-back comparison on a Classic showed no measurable difference (Aurora's scrolling varies between 12 and 30 frames per second from run to run either way). The change is kept because it is correct and passed all tests, but expect no visible speed-up from it.\n- After this update, apps with several code files take one slower start while they rebuild their optimised code.\n- Android 6 CTS on a Q5, unchanged from r299: Content 613/630, Database 263/264, Graphics 1025/1051, Jni 62/62, Os 399/409, Text 698/712, Util 203/206. 12 of 12 installed test apps start, draw and pause cleanly."
    },
    {
      "version": "2026.11.17-r299",
      "released": "2026-11-17",
      "changes": "- Full-screen games react to touch again. Games that hide the system bars in \"immersive\" mode (Minecraft, and most games made with Unity, GameMaker and similar engines) drew fine but ignored taps: BlackBerry's window manager comes from Android 4.3, which did not know immersive mode, and put an invisible layer over the game to catch the tap meant to bring the navigation bar back. That layer is no longer added for immersive apps.\n- Tested with Minecraft Pocket Edition 0.16: menus, world creation and gameplay all work, about 30 frames per second on a Classic.\n- For developers: frame timing now also covers games that draw from native code.\n- Android 6 CTS on a Q5, unchanged from r296: Content 613/630, Database 263/264, Graphics 1025/1051, Jni 62/62, Os 399/409, Text 698/712, Util 203/206. 12 of 12 installed test apps start, draw and pause cleanly."
    },
    {
      "version": "2026.11.17-r296",
      "released": "2026-11-17",
      "changes": "- Java and Kotlin code that creates typed arrays (very common: list.toArray(), Arrays.copyOf(), Kotlin's toTypedArray(), and many game engines) runs faster. Each such call used to make the runtime look the array type up again in a global table under a lock; it now remembers the answer. Measured on a Classic: Array.newInstance 4.0 -> 2.7 microseconds, toArray 7.3 -> 5.7 microseconds per call; Mindustry's first load about 6% shorter.\n- For developers: the built-in frame profiler can now follow the thread that actually draws (games that render on their own GL thread).\n- Android 6 CTS on a Q5, unchanged from r294: Content 613/630, Database 263/264, Graphics 1025/1051, Jni 62/62, Os 399/409, Text 698/712, Util 203/206. 12 of 12 installed test apps start, draw and pause cleanly."
    },
    {
      "version": "2026.11.17-r294",
      "released": "2026-11-17",
      "changes": "- Apps start faster again. While starting, apps tried again and again to make private copies of system libraries (the graphics drivers, the network library), something that can never succeed for those; each failed attempt cost several slow file checks, a median of 23 per app start. The runtime now remembers the answer for the rest of the process.\n- Measured on a Classic, cold start, old vs new: NewPipe 3.8 s -> 3.5 s, AntennaPod 5.5 s -> 5.3 s.\n- Android 6 CTS on a Q5, unchanged from r293: Content 613/630, Database 263/264, Graphics 1025/1051, Jni 62/62, Os 399/409, Text 698/712, Util 203/206. 12 of 12 installed test apps start, draw and pause cleanly."
    },
    {
      "version": "2026.11.17-r293",
      "released": "2026-11-17",
      "changes": "- Less background work while the phone is idle. The runtime's installer helper checked every installer record with a separate program every 5 seconds, all day; with many old records (55 on a test Classic) that kept the phone's storage busy. It now does one check for all records.\n- Goes together with the bb10-rootd update of the same day, which removes the other big idle cost.\n- The new helper starts with the next restart.\n- Android 6 CTS on a Q5, unchanged from r292: Content 613/630, Database 263/264, Graphics 1025/1051, Jni 62/62, Os 399/409, Text 698/712, Util 203/206. 12 of 12 installed test apps start, draw and pause cleanly."
    },
    {
      "version": "2026.11.17-r292",
      "released": "2026-11-17",
      "changes": "- Apps start faster. Before every app start the runtime looked through the records of all installed apps to find the one being started, a delay that grew with every app you installed. It now remembers the answer and re-checks only that one app.\n- The first time an app reads a file bundled inside its own APK (most apps do this while starting) the runtime no longer parses the APK's whole file list first.\n- Measured on a Classic, cold start, old vs new: NewPipe 4.9 s -> 4.0 s, AntennaPod 6.7 s -> 5.7 s, Aurora Store 3.7 s -> 3.3 s.\n- No changes for Termux in this release.\n- Android 6 CTS on a Q5, unchanged from r291: Content 613/630, Database 263/264, Graphics 1025/1051, Jni 62/62, Os 399/409, Text 698/712, Util 203/206. 12 of 12 installed test apps start, draw and pause cleanly."
    },
    {
      "version": "2026.11.17-r291",
      "released": "2026-11-17",
      "changes": "- Termux: programs that open a terminal of their own (tmux, ssh server sessions) now see the terminal's real name.\n- Termux: a shell or Python script checking on a child process that has not finished yet no longer gets a stale status back.\n- Termux: when a child process is killed or stopped by a signal, shells and Python now report the right signal and the usual exit codes (for example 137 for a kill, 143 for a terminate).\n- No changes for Android apps in this release.\n- Android 6 CTS on the test phone, unchanged from r290: Content 613/630, Database 263/264, Graphics 1025/1051, Jni 62/62, Os 399/409, Text 698/712, Util 203/206; all 12 apps of the app matrix start and draw."
    },
    {
      "version": "2026.11.17-r290",
      "released": "2026-11-17",
      "changes": "- Termux: logging in over ssh (sshd from the openssh package) gives a working terminal session; other programs that take ownership of a terminal work too.\n- Termux: Python's pty.spawn and similar programs no longer hang when the program in the terminal exits.\n- Termux: df and mount work.\n- No changes for Android apps in this release.\n- Android 6 CTS on a Q5, unchanged from r288: Content 613/630, Database 263/264, Graphics 1025/1051, Jni 62/62, Os 399/409, Text 698/712, Util 203/206; 12 of 12 installed test apps start, draw and resume."
    },
    {
      "version": "2026.11.17-r288",
      "released": "2026-11-17",
      "changes": "- Termux: looking up a host name together with a port number works in Python and other programs started from the shell.\n- Termux: ifconfig no longer crashes.\n- Termux: /proc/loadavg exists and vmstat works.\n- No changes for Android apps in this release.\n- Android 6 CTS on a Q5, unchanged from r287: Content 613/630, Database 263/264, Graphics 1025/1051, Jni 62/62, Os 399/409, Text 698/712, Util 203/206; 12 of 12 installed test apps start, draw and resume."
    },
    {
      "version": "2026.11.17-r287",
      "released": "2026-11-17",
      "changes": "- Termux: the clock is right. date, ls -l and Python's time functions now use the phone's time zone instead of GMT.\n- Termux: getprop works, and programs started from the shell can read Android system properties (they saw none before).\n- No changes for Android apps in this release.\n- Android 6 CTS on a Q5, unchanged from r286: Content 613/630, Database 263/264, Graphics 1025/1051, Jni 62/62, Os 399/409, Text 698/712, Util 203/206; 12 of 12 installed test apps start, draw and resume."
    },
    {
      "version": "2026.11.16-r286",
      "released": "2026-11-16",
      "changes": "- Termux (the legacy build for Android 5/6) now installs and runs: the bootstrap completes and you get a bash prompt. Verified in the app on a Q5: pkg install, git clone, python with threads, pip install and HTTPS requests, shell pipelines and redirections, ps, free, uptime, pgrep. Known gaps in this release: date shows GMT and getprop prints nothing (both fixed in the next release); top and vmstat do not work yet.\n- Smoother scrolling: app windows get one more frame buffer, which on the Classic cut frames that miss the 60 fps deadline from about 8% to about 3%.\n- Native code that uses signal handlers no longer has its floating-point/NEON registers corrupted when a signal arrives (BB10 does not save them); this could cause rare, random crashes or wrong results in any app.\n- Native code can use pipe2, dup3, accept4 and the close-on-exec/non-blocking flags on sockets that Android 6 apps expect.\n- Layouts that use GridLayout weights (Android 5+) are sized correctly instead of collapsing to nothing; this is what Termux's extra-keys row needed.\n- Upgrades are more robust: a leftover process holding the old runtime can no longer leave Android restarting in a loop after an upgrade.\n- The newdroid command now works by name in Term49 (newdroid status), not only by its full path.\n- Android compatibility tests (CTS) on a Q5, no regressions against r254: Jni 62 of 62, Os 399 of 409, Content 613 of 630, Database 263 of 264, Graphics 1025 of 1051, Text 698 of 712, Util 203 of 206. All 12 installed sample apps across frameworks (Compose, Flutter, React Native, Godot, libGDX, SDL2, WebView, ExoPlayer, CameraX and others) start and draw."
    },
    {
      "version": "2026.11.14-r254",
      "released": "2026-11-14",
      "changes": "- Web pages that open a pop-up window (window.open) no longer crash the app, and apps that run their own secure (HTTPS) server no longer crash on the first connection.\n- Links an app handles itself (custom schemes, sign-in redirects) now open in the app instead of being sent to BlackBerry's invoke handler, and an app that was shrunk to an Active Frame comes back to the front when it opens a screen.\n- Invalid dates now report -1 from Time.toMillis()/normalize() like Android 6; Parcel can carry a PersistableBundle; pasting no longer adds automatic spaces, and \"Paste as plain text\" works.\n- Secure storage: importing a key without block modes or paddings works, and HMAC SHA-1/224/384/512 keys can be generated.\n- Android compatibility tests (CTS) on the Classic: Widget 1046 of 1067 (the full module now runs), Text 697 of 712, Keystore 696 of 873, Location 104 of 104, Graphics 1025 of 1051. Known issue: after a web page opens a pop-up, later screens in that app may not open (being fixed)."
    },
    {
      "version": "2026.11.14-r244",
      "released": "2026-11-14",
      "changes": "- Accounts: renaming an account works (AccountManager.renameAccount) and keeps its saved data and sign-in tokens; the old name is remembered (getPreviousName). Removing an account whose app asks for confirmation now shows that confirmation screen instead of silently failing (as on Android 6).\n- 73 system constants that Android 6 apps may use (file-system flags, network and capability names) were missing and made such apps crash; they are all present now.\n- Accessibility: the actions a screen element offers (tap, focus, custom actions) are reported consistently, as on Android 6.\n- Android compatibility tests (CTS) on the Classic, no regressions against r239. Several test modules used to stop early at one crashing test; they now run to the end: Text 686 of 712, Widget 835 of 892, View 676 of 680, Net 139 of 158."
    },
    {
      "version": "2026.11.14-r239",
      "released": "2026-11-14",
      "changes": "- Background jobs that ask for a network now wait for one: a job set to \"Wi-Fi / unmetered only\" no longer runs on mobile data, and a job that needs any connection waits until there is one (as on Android 6). A job's deadline still wins.\n- Camera apps: the remaining Android 6 camera settings keys exist, so apps that read them no longer crash on start.\n- Android compatibility tests (CTS) on the Classic, no regressions against r237: JobScheduler 15 of 15 (was 14), Graphics 1025 of 1051, Widget 785 of 794, Location 104 of 104."
    },
    {
      "version": "2026.11.14-r237",
      "released": "2026-11-14",
      "changes": "- Encryption with extra authenticated data (AES-GCM \"AAD\") now actually authenticates that data; before, it was silently ignored. Data an app encrypted with AAD on an earlier newdroid version may no longer decrypt.\n- Dual-SIM / subscription APIs (SubscriptionManager) return the phone's real SIM instead of nothing, so apps that ask \"which SIM?\" before calling or texting work.\n- Camera: apps that open the camera while another app still holds it retry and get a proper \"disconnected\" callback instead of hanging.\n- Cookies, sensor flush (step counters, fitness apps), popup menus without a stray animation, and image/jpeg files getting a .jpg extension now behave as on Android 6.\n- Android compatibility tests (CTS) on the Classic, no regressions against r232: View 638 of 641, Widget 785 of 794, Webkit 75 of 82, Location 104 of 104, Animation 82 of 82."
    },
    {
      "version": "2026.11.13-r232",
      "released": "2026-11-13",
      "changes": "- Text-to-speech works for apps written for Android 5 and later: the modern speak() call (and five related ones) did nothing at all here, so navigation, reading and accessibility apps were silent. Stopping speech now tells the app (Android 6 behaviour) instead of leaving it waiting.\n- Material buttons and list items show the touch ripple; a \"ripple\" background used to be drawn as a plain layer, and apps that expect a real ripple object no longer crash.\n- Secure storage (Android keystore): RSA key pairs can be created the Android 6 way, EC (elliptic-curve) key pairs work, and encryption follows Android 6's rules (fresh IV per message, no IV reuse, GCM parameters). Keys are software keys on this phone (no secure hardware), as before.\n- Background jobs that only set a deadline run at the deadline and report it, as on Android 6.\n- Animations restart correctly when re-run or retargeted; drawables that wrap another drawable no longer leak a colour/alpha change into every other copy; mirrored icons report it for right-to-left layouts.\n- getSystemService(SomeManager.class) works for 18 more services (captions, battery, USB, fingerprint, launcher apps, ...).\n- Contacts: apps using the old social-stream permissions work under Android 6's rules.\n- Android compatibility tests (CTS), full runs on both phones: Graphics 995 to 1025 of 1051, Provider 261 to 277 of 307, Location 104 of 104, Animation 82 of 82, Speech 11 of 11, Keystore 197 to 677 of 873 since r208."
    },
    {
      "version": "2026.11.13-r222",
      "released": "2026-11-13",
      "changes": "- Icons and backgrounds that use theme colours (?attr/... in drawable XML, common in Material apps) are drawn in the app's theme colours; before they came out transparent or failed to load.\n- Vector icons are cached like other drawables instead of being re-read on every use, and fading or tinting one copy no longer leaks into the others until the app asks for a private copy (Android 6 behaviour).\n- Apps that keep their own account type (sync and chat apps written for Android 6) can add, read and remove their own accounts without the permissions Android 6 removed; removing an account from inside the app works.\n- Apps can ask whether GPS/network location is switched on without holding a location permission, and list their own tasks, as on Android 5 and later (both used to crash such apps).\n- Secure storage: keys can be imported into the Android keystore the Android 6 way, and the \"AndroidKeyStoreBCWorkaround\" provider that Android 6 apps and samples name explicitly exists.\n- Images: reusing a bitmap for a new decode works for any size that fits (photo and gallery apps use this heavily); bitmaps report their real memory use; radial gradients with a percentage radius are drawn at the right size.\n- Right-to-left grids are spaced correctly; android-app:// links open the right app.\n- The setup check now counts the runtime's own classes instead of assuming a fixed number, so adding a class can no longer make a restart fall back to the stock runtime.\n- Android compatibility tests (CTS), full run on a Classic: Graphics 995 to 1020 of 1051, Provider 261 to 272 of 307, Content 613, Widget 784; newly measured: Keystore 197 to 488 of 873, AccountManager 0 to 15, Permission 147, Preference 73 of 73, Theme 21 of 21."
    },
    {
      "version": "2026.11.13-r208",
      "released": "2026-11-13",
      "changes": "- Recurring calendar events show up again. Dates before 1970 were read as dates in the year 2106 (this phone's C library treats times as unsigned), which left every repeating event with no occurrences and put old birthdays in the wrong place.\n- Contacts and call-log apps written for Android 6 can ask for the newer columns (pinned, in_default_directory, backup_id, carrier_presence, a call's cached photo) instead of failing with \"Invalid column\"; the call log keeps a contact photo address.\n- Tapping a contact badge in an Android 6 app opens the contact (it did nothing), with the app's preferred kind of contact data first.\n- A voicemail's file location can no longer be changed by an update (Android 6 security rule).\n- Settings lookups written the Android 6 way (name=\"...\") find just that setting; before, such a lookup matched -- and could change or delete -- every setting.\n- Text: the cursor moves to the start/end of the text from the first/last line, and a single line of text no longer gets extra line spacing, as on Android 5 and later.\n- Several drawable fixes: inset/clip/scale wrappers pass state only to drawables that use it, clipped drawables report the right opacity, bitmaps report their filtering setting.\n- Android compatibility tests (CTS), full run on a Classic: Provider 244 to 261 of 307, Location 104 of 104, Graphics 995, Text 211, View 638 of 641, OS 404 of 414."
    },
    {
      "version": "2026.11.12-r202",
      "released": "2026-11-13",
      "changes": "- Material and AppCompat backgrounds are tinted the way Android 6 does it: the tint follows button states and is kept when an app swaps the background (it used to be painted once and lost).\n- Text selection and other contextual toolbars are routed as on Android 6, so apps that customise them (and floating selection menus) get the right one.\n- android:theme on an <include> now applies, as on Android 6.\n- Files and pipes shared between apps report how they were closed (closed, error, crashed, detached) to the app that opened them -- document providers and file-sharing apps notice a failed transfer instead of waiting for ever.\n- Installing an app no longer wakes every modern app that listens for installs: apps targeting Android 8 or newer get those broadcasts only while running, as on Android 8, so installs stay responsive.\n- Location: the location-mode setting matches the enabled providers, test locations are marked as mock locations, and mock-location apps work.\n- `settings` and `appops` from the command line finish instead of hanging.\n- Several Android 6 behaviours apps depend on: multi-dimensional arrays survive a Bundle, malformed data is rejected before any code runs, search-key events, stylus/mouse context clicks, Intent links with selectors.\n- Reports security patch level 2015-10-01 -- the earliest Android defines. This runtime carries no Android security bulletin fixes and says so.\n- Android compatibility tests (CTS), measured on a Q5 and a Classic: OS 175 to 404 passing (the suite now runs to its end: 414 tests), View 241 of 255 to 638 of 641 (likewise), Location 73 to 103 of 104."
    },
    {
      "version": "2026.11.12-r187",
      "released": "2026-11-12",
      "changes": "- Network changes no longer wake every installed app at once. As on Android 7, apps targeting Android 7 or newer get connectivity changes only while running, so the phone stays responsive after switching networks and other system broadcasts aren't held up (Android CTS broadcast-receiver tests now pass)."
    },
    {
      "version": "2026.11.12-r186",
      "released": "2026-11-12",
      "changes": "- Apps whose native code needs the standard C++ library (libc++.so) without bundling it now load it (Android CTS JNI tests: 0 to 62 of 62).\n- Python/Kivy apps format dates and times correctly, and Kivy games such as FreeCell draw.\n- Several system-call fixes (Android CTS OS tests: 153 to 175 passing)."
    },
    {
      "version": "2026.11.11-r182",
      "released": "2026-11-12",
      "changes": "- NewPipe no longer closes while loading video thumbnails; WebP images from modern apps decode with an up-to-date decoder.\n- Apps that run JavaScript in a WebView and wait for the answer (NewPipe playback and many hybrid apps) now get it.\n- QR and barcode scanners built on CameraX (Binary Eye and others) now see the camera.\n- Unity games now load their game engine (Fruit Ninja reaches its game screen; its Google Play Games sign-in still needs a Google account).\n- Apps that load code at run time through their own class loader no longer fail to find it.\n- Apps that load extra native libraries by name, and Python (Kivy) apps, now get further through their start.\n- Fixed a rare crash in apps that start helper processes."
    },
    {
      "version": "2026.11.11-r159",
      "released": "2026-11-11",
      "changes": "- Games and apps that play sound through Oboe or OpenSL ES with the newer Android 5+ audio formats now get sound instead of crashing (ScummVM).\n- Apps that bundle their own MultiDex (8 Ball Pool, WhatsApp and many others) no longer redo the runtime's work on every start, which made some of them stop themselves as \"not responding\".\n- Apps that check whether they run on the main thread the usual Android way now get the right answer.\n- Native libraries built with recent Android NDK versions that share a memory page between two segments now load (they failed with \"Unresolved symbols\").\n- Apps whose first screen immediately opens a second one (RetroArch, Simon Tatham's Puzzles) are no longer sent back to the home screen behind a black card.\n- Apps that use Google Play services (Chrome, Gmail, Deezer, Shazam and others) now prepare its code properly instead of loading it slowly from memory on every start; Chrome no longer closes on its first start after an update.\n- Tip: installing Android apps without tapping the permissions screen needs Development Mode on (Settings > Security and Privacy > Development Mode)."
    },
    {
      "version": "2026.11.11-r151",
      "released": "2026-11-11",
      "changes": "- Apps that load another app's code several times in one process (Chrome loading Google Play services for each of its modules) now load it once and reuse it, instead of preparing it again each time.\n- Facebook Lite now gets to its login screen.\n- The Shumei anti-fraud library some shopping apps include no longer crashes the app when it inspects system code.\n- Updating rebuilds the runtime once (a few minutes). The first start of each app after updating is slower once while it prepares again; Chrome may close on that first start and opens normally the next time."
    },
    {
      "version": "2026.11.10-r148",
      "released": "2026-11-10",
      "changes": "- Gmail now starts and stays open. On its first start Gmail restarts itself to turn on its Exchange services; the BB10 card it left behind showed a blank screen on every tap, and is now closed the way a crash is. Its second start no longer crashes on layouts that pick their content from the theme (<include layout=\"?attr/...\">).\n- WeChat's background performance monitor no longer crashes: the memory statistics Android 6 always provides (Debug.MemoryInfo.getMemoryStats) are now filled in.\n- Updating the runtime is more robust: Android processes left over from the previous runtime are removed before the new one starts, and if the runtime stops while it rebuilds all apps on its first start, it is started again instead of staying off until the phone restarts.\n- Apps with several processes no longer break each other's code preparation: the processes of one app (and Chrome's processes loading Google Play services code) now take turns optimizing the same files instead of racing, a file a failed run left half-built is rebuilt, and where optimizing fails in a process the code is loaded from memory instead. Chrome's first start after an update could otherwise miss Google Play services classes or give up waiting for its GPU process.\n- Updating rebuilds the runtime once (a few minutes). The first start of each app after updating is slower once while it prepares again."
    },
    {
      "version": "2026.11.10-r141",
      "released": "2026-11-10",
      "changes": "- Apps can use Java 8's default methods on java.util.function (Function.andThen and compose, Predicate.and/or/negate, Consumer.andThen and the primitive versions). Dalvik has no default methods; the runtime now supplies them. Google Photos no longer loses a background thread to this at start and reaches its welcome screen.\n- Updating rebuilds the runtime once (a few minutes). The first start of each app after updating is slower once while it prepares again."
    },
    {
      "version": "2026.11.10-r140",
      "released": "2026-11-10",
      "changes": "- WeChat and Temu now start: WeChat reaches its login screen and stays up, and Temu gets past its splash screen.\n- Native code that relies on the Linux kernel's atomic helper page no longer aborts at start (WeChat's media libraries).\n- Apps can read their own thread list and CPU times (/proc/self/stat, /proc/self/task), which QNX does not provide; WeChat's performance monitor no longer crashes about 40 s after start.\n- Character.UnicodeBlock knows every Unicode block (Temu hung on its splash screen without them).\n- More native libraries load: fixes for libraries that had no spare slot for the runtime's library redirection, and for symbol names that share their ending with another symbol.\n- Message.recycleUnchecked() exists, which WeChat's background task pool looks up.\n- Taps no longer carry BB10's extra hover events into Android apps; real Android never sends those for a finger.\n- When an app kills itself, the runtime logs where from (logcat tag NdKill).\n- Updating rebuilds the runtime once (a few minutes). The first start of each app after updating is slower once while it prepares again."
    },
    {
      "version": "2026.11.09-r129",
      "released": "2026-11-09",
      "changes": "- Tested with 20 popular apps from Aurora Store; these now start: Telegram, Pinterest, Signal, VLC, Opera Mini, imo, AliExpress, YouTube Music, Google Translate and Google Drive.\n- VLC and other apps whose native code writes to the console no longer crash at start or when playing a video.\n- Instagram no longer crashes in the background when another Meta app starts it.\n- Apps that check that all their Google Play pieces are installed (Netflix, ...) no longer close themselves; apps with Play feature modules load those modules' code.\n- Gmail and other Google apps no longer stop with a security error when they ask microG for accounts.\n- Background jobs of apps (WorkManager, Firebase) no longer fail with a NullPointerException when they start.\n- Fewer crashes from missing Android 4.4-6 functions (Telegram, AliExpress, WeChat, Signal) and from native code that hands the runtime a raw object pointer or walks the loaded-library list (Kindle).\n- Thread dumps: kill -QUIT <pid> now writes every Java thread's stack to /data/anr/traces.txt.\n- Updating rebuilds the runtime once (a few minutes). The first start of each app after updating is slower once while it prepares again."
    },
    {
      "version": "2026.11.09-r117",
      "released": "2026-11-09",
      "changes": "- Scrolling no longer freezes for memory cleanup at all. The pauses that remained after r109 (about 0.13 s each) came from small allocations; those now also make room straight away and leave cleanup to the background, so in Aurora's lists these freezes went from about 20 per minute of scrolling to none.\n- Updating rebuilds the runtime once (a few minutes). The first start of each app after updating is slower once while it prepares again."
    },
    {
      "version": "2026.11.09-r113",
      "released": "2026-11-09",
      "changes": "- Instagram (and Facebook, Messenger, Threads) installed from Aurora Store no longer stops with \"Unfortunately, Instagram has stopped\" on its first start. Previously only apps installed with bar-install got the fix.\n- \"Open in Play Store\" links inside apps work again. BlackBerry redirected them to the closed BlackBerry World store; they now go to Aurora Store (BlackBerry asks once which store to use).\n- Fixes a rare freeze when Chrome starts: a helper process could inherit a lock from the browser and wait for it for ever.\n- Updating rebuilds the runtime once (a few minutes). The first start of each app after updating is slower once while it prepares again."
    },
    {
      "version": "2026.11.09-r109",
      "released": "2026-11-09",
      "changes": "- Much smoother scrolling through image-heavy lists. When an app needed room for a new picture, the runtime used to pause the whole app (about 0.13 s each time, a visible stutter) to clean up memory first, usually finding nothing to free. It now makes room straight away and cleans up in the background, as Android 5 and later do. Measured in Aurora's app lists: 21% more frames drawn while scrolling and 3 to 4 times fewer of these pauses.\n- Updating rebuilds the runtime once (a few minutes). The first start of each app after updating is slower once while it prepares again."
    },
    {
      "version": "2026.11.09-r107",
      "released": "2026-11-09",
      "changes": "- Menus in WhatsApp and other modern apps work again: tapping an item in a popup menu (for example WhatsApp's menu > Help) now opens it. Previously the menu opened and scrolled but ignored taps.\n- WhatsApp no longer crashes with \"corrupt installation\" on its first start or after an update, before you reach phone-number verification.\n- Chrome now draws with the graphics chip (OpenGL ES 2) instead of the processor, and no longer freezes on start: Chrome's helper processes could hang the browser at startup.\n- More reliable app start-up generally: a rare freeze between starting a helper process and loading a library is fixed.\n- Updating rebuilds the runtime once (a few minutes). The first start of each app after updating is slower once while it prepares again."
    },
    {
      "version": "2026.11.08-r84",
      "released": "2026-11-08",
      "changes": "- Smoother scrolling in busy apps: apps now get more memory headroom before the system has to pause them to clean up. In Aurora's app lists these pauses (about 0.15 s each, a visible stutter) used to happen every few moments while scrolling.\n- Apps with many native libraries start 1.5 to 3 seconds faster (measured on Instagram). The runtime now remembers how it prepared an app's libraries instead of re-checking all of them on every start, and skips looking for system libraries inside the app's own folders.\n- More room for compiled code, so long-running apps no longer throw away and recompile their hot code.\n- Updating rebuilds the runtime once (a few minutes). The first start of each app after updating is slower once while it prepares again."
    },
    {
      "version": "2026.11.08-r80",
      "released": "2026-11-08",
      "changes": "- Big apps start much faster. Instagram now starts in about 24 seconds instead of about 48: loading each of an app's native libraries no longer repeats a dozen slow storage checks.\n- Chrome no longer freezes now and then. Its crash reporter starts in a separate process, and starting it could deadlock and take Chrome's browser process with it. Fixing this should also help other apps that start helper processes.\n- Faster network and event handling in Chrome and in apps built with Rust or tokio (Firefox, Signal, Delta Chat). Their event loop could sit idle for up to 50 ms without noticing new data.\n- Tapping an item in a popup menu now works where it did not before.\n- Less logging noise in the system log.\n- Updating rebuilds the runtime once (a few minutes). The first start of each app after updating is slower once."
    },
    {
      "version": "2026.11.07-r72",
      "released": "2026-11-07",
      "changes": "- Instagram no longer crashes with \"Unable to find unpacked GraphService asset file\". The file was there, but Instagram opens it with an option that Android ignores and the BB10 runtime rejected. The runtime now ignores it too, which can help other apps that use the same option.\n- Background services of large apps (Instagram's notifications, for example) are no longer killed every minute while they start up. They now get the same 200 seconds Android 6 allows.\n- Fewer \"isn't responding\" messages while big apps start or right after the runtime restarts. Background broadcasts get 200 seconds, and an app's screen gets 20 seconds to react to a tap.\n- The first start of each app after this update takes a little longer once.\n- Updating rebuilds the runtime once (a few minutes)."
    },
    {
      "version": "2026.11.07-r69",
      "released": "2026-11-07",
      "changes": "- Chrome loads web pages. Two runtime bugs were in the way, and both affected other apps too:\n  - Apps that link their native code in a certain way read error numbers in BlackBerry's numbering instead of Android's. Chrome saw every network connection as an unknown error and gave up on it.\n  - On BB10, a forked child process of a multithreaded Android app could freeze for good. Chrome starts its crash reporter this way, and that froze the browser's own network and tab handling, so every page after the first one hung. Now that child processes start reliably, apps that run helper programs should benefit too.\n- Instagram no longer crashes after its welcome screen.\n- Updating rebuilds the runtime once (a few minutes)."
    },
    {
      "version": "2026.11.07-r65",
      "released": "2026-11-07",
      "changes": "- Chrome no longer stops behind its welcome screen. Android asked for a thread priority that BB10's runtime could not describe and Chrome treated the error as fatal; every priority now gets an answer.\n- Chrome's page renderers start. They run as separate, locked-down processes that could not prepare their own copy of Chrome's native code, so every tab died and stayed grey; they now reuse the copy Chrome's main process already prepared. (Pages still do not load in Chrome yet: its network connections fail. Being worked on.)\n- Instagram gets past its first startup crash (it asked about a thread that does not exist). Also install the new bb10-bar-install and reinstall Instagram for its second fix.\n- Updating rebuilds the runtime once (a few minutes)."
    },
    {
      "version": "2026.11.03-r59",
      "released": "2026-11-03",
      "changes": "- Aurora Store no longer disappears when you press \"Finish\" at the end of its setup. Aurora restarts itself at that point, and BB10 was closing its window before the restarted app could appear. Other apps that restart themselves the same way are fixed too.\n- Fixed a crash in apps that load many images or pages at once, such as Aurora Store's main screen. When an app cancels a network request just as it connects, Android 4.3 treated that as a fatal error; it is now reported to the app as an ordinary network error, as on newer Android.\n- Updating rebuilds the runtime once (a few minutes)."
    },
    {
      "version": "2026.11.02-r58",
      "released": "2026-11-02",
      "changes": "- Google Maps now draws the map: zooming, panning and street-level detail work, along with search, place details and Street View previews. Three more runtime problems were in the way, and fixing them helps other apps too:\n  - Code that apps load from microG at run time (such as its fast network library) now finds all of its parts, not just the first.\n  - An app can now use native code that belongs to another app (Maps uses microG's network library this way). Before, this failed and Maps showed \"Reinstall Maps\".\n  - The Q5/Q10/Classic graphics chip cannot handle one common way of writing graphics shaders, which made apps report a broken graphics context. The runtime now rewrites those shaders on the fly into an equivalent form the chip accepts.\n- Apps can now see which OpenGL ES version the phone supports.\n- If Maps already shows \"Reinstall Maps\", clear its data once (or reinstall it) after updating.\n- The first start of each app after this update takes longer once, while it is re-prepared.\n- Updating rebuilds the runtime once (a few minutes)."
    },
    {
      "version": "2026.11.02-r57",
      "released": "2026-11-02",
      "changes": "- Google Maps now runs (the last version for Android 6, which Aurora offers automatically): search, place details and directions work. Three runtime bugs were in the way, and each one affects other apps too:\n  - Apps could read their own process name wrongly when it is 24 characters or longer (BlackBerry lists a program's arguments differently from Android). Apps that check whether they run in their main process, as Maps and many libraries do, then skipped their own setup.\n  - Added Java's CountedCompleter and related pieces, needed by apps whose built-in Java library uses them (Maps' map data code).\n  - microG's location service no longer crashes when an app asks for location.\n- Every Android app starts faster: the runtime no longer re-reads the whole app package on each start just to find its code files (up to 0.4 s saved per start for big apps like WhatsApp).\n- The first start of each app after this update takes longer once, while it is re-prepared.\n- Known: the map itself does not draw yet (search and details work).\n- Updating rebuilds the runtime once (a few minutes)."
    },
    {
      "version": "2026.11.01-r56",
      "released": "2026-11-01",
      "changes": "- More room on screen for modern apps. Apps that draw edge to edge (most newer apps, for example AntennaPod) left an empty band of about 80 pixels above BlackBerry's bottom bar, and their real bottom edge was hidden behind it. They now use the whole Android area.\n- Updating rebuilds the runtime once (a few minutes)."
    },
    {
      "version": "2026.11.01-r55",
      "released": "2026-11-01",
      "changes": "- Fixed \"Unfortunately, the process android.process.acore has stopped\" after adding an account (for example Nextcloud). The contacts service asks Android for every app's content providers, and with microG Companion installed that answer grew to about 440 KB, more than BlackBerry's system messaging can carry. Android now leaves out data that answer never needed.\n- Fixed Nextcloud's \"Upload from camera\" crash. Android apps can now find the phone's storage under /storage, as on every other Android phone.\n- In-app web pages (login pages, sign-in sheets) can now connect to modern websites. Android 4.3's web view only spoke TLS 1.0, which most servers refuse today, so these showed \"Webpage not available\". It now uses TLS 1.2. Pages that need modern JavaScript can still appear incomplete, because the web view's engine is from 2013. For Nextcloud, log in with the QR code.\n- Updating rebuilds the runtime once (a few minutes)."
    },
    {
      "version": "2026.10.30-r54",
      "released": "2026-10-30",
      "changes": "- Android apps queued for after a restart no longer get lost when nobody is at the phone. They install one at a time, and each waits for you to tap Accept on its permissions screen, however long that takes. Before, an app whose screen went unanswered for 10 minutes was reported as \"not installed\" even though accepting it later still worked, and the next app was started while the screen was still up, which failed.\n- Declining an app's permissions screen removes it from the queue instead of asking again at every restart.\n- New command `newdroid queue` installs waiting apps now, without a restart.\n- Android 6 is ready about 40 seconds sooner after a restart.\n- No runtime rebuild: updating from r53 takes seconds."
    },
    {
      "version": "2026.10.27-r53",
      "released": "2026-10-27",
      "changes": "- App stores can no longer install Google's own Play services, Play Store or Google services framework. Aurora Store offers Google Play services as an 'update' to microG, because both use the same name. Google's version cannot work on BlackBerry, and apps that find it stop using microG. microG's own updates still install. If you need Google services, install microG from Rubus.\n- No runtime rebuild: updating from r52 takes seconds."
    },
    {
      "version": "2026.10.26-r52",
      "released": "2026-10-27",
      "changes": "- Apps from Google Play now get their images and translations. They come as several pieces, and the r51 way of adding the pieces never actually worked on this phone's Android resource system: WhatsApp, for example, stopped on start. The installer now merges an app's resources into one set and the runtime loads that first. Tested: WhatsApp from Aurora Store starts and shows its welcome screen.\n- F-Droid, browsers and file managers can install apps: their 'install this APK' request now goes through BlackBerry's installer (home-screen icon, permissions screen) instead of Android 4.3's own installer, which put apps on the phone without a BlackBerry icon. Uninstalling from those apps works the same way.\n- Fixed: in apps built with Jetpack Compose, scrolling rows and lists could draw outside their area (for example a row of game tiles showing up on the next page in Aurora Store).\n- Less storage used: an extra full copy that BlackBerry's installer kept of every Android app is now removed; existing ones are cleared at the next restart.\n- Installing uses less free space: the installer moves files instead of copying them.\n- Needs bb10-bar-install 20261026-r2. This version rebuilds the runtime image once (a few minutes)."
    },
    {
      "version": "2026.10.26-r51",
      "released": "2026-10-26",
      "changes": "- Split APKs: most apps on Google Play come as a base plus split APKs for the phone's CPU, screen and language. Stores that install through Android's session installer, such as Aurora Store, can now install them. The app installs like any other (home-screen icon, permissions screen), its 32-bit ARM code goes into the app's library folder, and its screen and language resources are added to it. Tested with Material Files from Google Play through Aurora Store.\n- `newdroid install-apks <file>` installs a split set you downloaded (.apks, .xapk, .apkm, or a folder of APKs).\n- Apps can uninstall other apps through the same installer.\n- An app whose permissions screen nobody answered is no longer reported as failed. You get a 'waiting for you' notification, and accepting the screen later still finishes the install. It is also not installed a second time after a restart.\n- Fixed: Rubus could not update newdroid on a phone where Term49 had installed it first (the setup stopped at 'Permission denied').\n- Fixed: installs run by newdroid left bar-install's staging folders owned by root, which broke later installs from Rubus, including Rubus updating itself.\n- This version rebuilds the runtime image once (a few minutes) on the first restart or when updated."
    },
    {
      "version": "2026.10.26-r50",
      "released": "2026-10-26",
      "changes": "- Android apps can now be installed at the same time as the runtime, or in the first minutes after a restart. If Android 6 isn't running yet, the app waits in a queue and is installed automatically as soon as it is (tap Accept when the phone asks for permissions). 'newdroid status' shows what is waiting.\n- Installing or upgrading a package while the phone is still setting up Android 6 after a restart no longer stops that setup halfway. This is what broke microG on the Classic on 24 October.\n- If Android doesn't come back when the runtime is switched on, it now clears a known leftover that blocks it and asks once more before giving up.\n- Keeps a history of every start attempt across restarts, including Android's own error messages when one fails ('newdroid log'), plus the previous two boot logs.\n- Fixed: two installer runs could start at the same moment and wreck an app install.\n- The Android runtime itself is unchanged, so nothing is rebuilt on upgrade."
    },
    {
      "version": "2026.10.23-r49",
      "released": "2026-10-23",
      "changes": "- Fix: on some restarts Android 6 did not start and no notification appeared -- most often the first restart after installing. The start-up job could be stopped early in the boot, and the second start attempt that every boot makes then skipped because the first one had claimed the slot. A start-up job that is no longer running now gives the slot up. If Android 6 didn't start after a restart, update and restart once.\n- The runtime itself is unchanged from r48, so updating does not rebuild it."
    },
    {
      "version": "2026.10.22-r48",
      "released": "2026-10-22",
      "changes": "- Fix: installing or upgrading from Rubus could stay on \"installing\" for ever after the runtime had actually been set up. The installer left a background disk driver attached to the installer's output, so apk waited for it to finish. If an earlier update seemed stuck, this update completes normally.\n- Apps using a current Chrome network stack (Cronet), such as Netflix, no longer crash at startup: the Android 6 per-process network calls (ConnectivityManager.getBoundNetworkForProcess and friends) are now present.\n- Apps that bundle their own fonts with the AndroidX support library no longer crash when the first such font loads (the hidden FontFamily class those libraries use is now present).\n- Added GridLayout.spec with a weight (the weight itself is ignored).\n- Netflix now starts but shows \"This app is not compatible with your device\": it needs Google's Widevine DRM, which cannot be provided."
    },
    {
      "version": "2026.10.21-r47",
      "released": "2026-10-21",
      "changes": "- Signal and Delta Chat start. Apps built with Rust's tokio crashed at startup: the runtime's syscall() bridge overwrote a value belonging to its caller.\n- Discord no longer closes at random during startup. Looking up native functions re-read library files from flash on every miss, and Android gave up waiting for the thread doing it.\n- Facebook Lite: the Google sign-in sheet now opens inside Facebook Lite instead of in a separate microG card.\n- Reinstalling an app keeps its Android user id, so a reinstalled app no longer fails to open with \"fork() failed\".\n- Plants vs. Zombies 2 and other EA games no longer crash at launch (encryption IV handling). PvZ2 still needs its game-data download.\n- Newly verified: Spotify, Telegram (Play build), Temple Run 2, Candy Crush.\n- Apps re-prepare their native libraries once on the first launch after this update, so that launch is slower."
    },
    {
      "version": "2026.10.19-r41",
      "released": "2026-10-19",
      "changes": "Version 1.0.\n- Google Play services: the new optional package bb10-microg (microG) gives apps push notifications, Google sign-in and location services. The runtime lets microG stand in for Google Play services -- and only microG: the permission is tied to microG's own signing key.\n- Large apps install from Rubus: Android parsed an app while BlackBerry was still copying it, which made every app over roughly 80 MB fail (WhatsApp, Firefox, many games). The runtime now waits for the copy to finish. Needs bb10-bar-install 20261019.\n- Unity games run (Temple Run 2, Angry Birds 2, Fruit Ninja): the app's main thread now gets an 8 MB stack instead of BlackBerry's 512 KB, which Unity overflowed.\n- Snapchat no longer closes a few seconds after its login screen: apps asking for Linux's CLOCK_BOOTTIME clock (and the other Linux-only clocks) now get it.\n- Installing an app with very many components (such as microG) no longer makes \"android.process.acore\" stop.\n- Unchanged: API-23 conformance suite 556 pass, 0 fail."
    },
    {
      "version": "2026.10.19-r37",
      "released": "2026-10-19",
      "changes": "- Faster command execution: apps that run a command (Runtime.exec / ProcessBuilder) no longer copy their whole memory to do it. A command now starts in about 10-50 ms instead of up to several seconds in large apps. This removes the \"isn't responding\" Candy Crush showed at start (its analytics SDK runs a command on the main thread).\n- Candy Crush Saga now reaches its main screen."
    },
    {
      "version": "2026.10.19-r36",
      "released": "2026-10-19",
      "changes": "- HTTPS: added 26 current root certificates that BlackBerry's own store never received (Google Trust Services, Amazon, Microsoft 2017, ISRG Root X2, GlobalSign R46/E46/R6, DigiCert G5, Sectigo R46/E46, SSL.com, Certainly). Apps using Google/Firebase, AWS-hosted or Microsoft services no longer fail with \"Trust anchor for certification path not found\". Your own BlackBerry certificates are all kept; these are only added.\n- Fix: on a phone where an earlier install had been interrupted, rebuilding the runtime could leave out the certificate store entirely, so every app's HTTPS failed. The installer now starts each rebuild from a clean slate."
    },
    {
      "version": "2026.10.19-r34",
      "released": "2026-10-19",
      "changes": "- More everyday apps start: Snapchat, Discord, Telegram (Play and telegram.org builds), Reddit, DuckDuckGo, Firefox Focus, Opera Mini, Viber, Instagram Lite; Twitter/X, Messenger, Spotify, Pinterest, LinkedIn, Duolingo and Shazam confirmed working. All fixes are in the runtime, none app-specific.\n- Games: Candy Crush Saga, Geometry Dash Lite, Mindustry and Antimine now start; Shattered Pixel Dungeon, Luanti, Unciv, SGT Puzzles, HyperRogue and Freedoom confirmed.\n- Faster app start: about 4-6% quicker cold launches. The class loader no longer builds and throws away an exception for every app class the system libraries cannot have (thousands per launch), and the security-provider table is now built once at runtime start instead of in every app.\n- Fix: Unity games (Temple Run 2 and others) crashed at start: about 1,500 newer platform constants that native code looks up by name (e.g. immersive-mode flags, Build.VERSION_CODES.M) were missing; they are now present.\n- Fix: native code that reads the CPU thread register directly (the mimalloc allocator in Snapchat and others) got the wrong value on BB10 and crashed; it now reads the real thread data.\n- Fix: apps registering a native method declared in a parent class (React Native/Reanimated in Discord) stalled on the splash screen.\n- Fix: native libraries built for Android 6+ with packed relocations (the NDK default) were never relocated and crashed; they are now unpacked when the library is prepared.\n- Fix: native libraries with only a GNU hash table and many imports (Rust/Go code, e.g. Signal, Opera, Viber) crashed the loader; a SysV table is now added even when it doesn't fit in place.\n- Fix: an app's own extra code files (Facebook Lite/Instagram Lite) could not be optimized; their cache now goes into the app's own directory.\n- Fix: apps with several code files that also use the Maps library (Telegram) only loaded the first file.\n- Fix: a library's JNI functions living in one of its dependencies were not found; JSON objects built from maps/lists stored nested lists as text (DuckDuckGo); Crashlytics' native reporter crashed apps when flushing stderr (Opera Mini, Viber); library names of exactly 127 characters were dropped (Instagram); R8-optimized apps calling an inherited constructor failed (Antimine); malloc_usable_size was a stub.\n- Added APIs: AccountManager.removeAccount(with Activity), Display.getSupportedRefreshRates, ConcurrentHashMap.newKeySet, WebViewFactory.getWebViewPackageName (Candy Crush thought WebView was disabled), and the API-24 _chk functions some prebuilt native libraries need.\n- Known not working: Instagram and Facebook (full apps; use the Lite versions), Facebook Lite after a crash (its crash reporter needs Android 7), Signal (crashes after the first screen), Roblox, TikTok (too large for this runtime), Netflix (DRM), Uber (needs Google Maps). Large games (Unity titles, Candy Crush) start slowly the first time and may show \"isn't responding\"; tap Wait."
    },
    {
      "version": "2026.10.09-r24",
      "released": "2026-10-18",
      "changes": "- Firefox 143 now runs and renders web pages (HTTPS included). Every fix below is in the runtime, not Firefox-specific.\n- Fix: Java threads ignored the stack size apps request (Android 6 honours it); Firefox's main thread overflowed its 1MB stack.\n- Fix: apps could only create 57 thread-local keys (Android 6: 128+); Rust libraries crashed. Now 1024.\n- Fix: apps that load their own libraries by path or name (NSS, plugins) got the unpatched copy -- Firefox had no TLS.\n- Fix: Rust/tokio thread parking (futex wait/wake with bitsets) was unsupported, so those threads spun at 100% CPU.\n- Fix: passing file descriptors between processes lost data on large messages, and MSG_CMSG_CLOEXEC receives failed -- multi-process apps (browsers) could not hand rendered pages to the window.\n- Fix: two causes of a hot phone: an emulated event descriptor that never went quiet (AudioIPC/tokio wakers), and posix_fallocate looping forever.\n- Fix: a closed eventfd's number reused by another file could corrupt reads of that file.\n- Fix: dladdr could name the wrong library while another was loading, so JNA/libffi mapped its callback code from the wrong file and crashed; libffi trampoline pages are now copied correctly.\n- Fix: the runtime no longer reads, writes or closes a descriptor of its own after the app has closed it and the number was reused.\n- Fix: a large read-only file mapping that fails is retried (Firefox's APK mapping occasionally failed on first launch).\n- JSONObject.wrap and JSONArray(Object) (API 19) added.\n- Known issue: Firefox may still occasionally fail its first launch after the runtime starts; launching it again works. Delta Chat (Rust core) still fails to create its account store."
    },
    {
      "version": "2026.10.09-r23",
      "released": "2026-10-14",
      "changes": "- Native API: the runtime now provides every library and every function Android 6's NDK promises apps (checked against the NDK's own API-23 list: 0 missing, from ~460 missing). Covers libc, libm, liblog, libandroid, libmediandk, libEGL, GLES 3.1 entry points, libz, OpenSL ES, jnigraphics.\n- Fix: timed waits on CLOCK_MONOTONIC condition variables returned immediately, so apps built for Android 5+ could spin at 100% CPU and stall (Chromium did).\n- Fix: libraries that relocate themselves (Firefox's) crashed at load; libraries that bring their own loader (Chromium's) could not resolve newer libc functions or load from inside the APK; dlclose(NULL), RTLD_NEXT/RTLD_DEFAULT lookups and dl_iterate_phdr now behave like Android.\n- Fix: JNA/libffi callbacks crashed (their code pages were never executable); getpagesize() returned a wrong value; timerfd now works; epoll is available to every app by default (WhatsApp stays opted out until re-checked).\n- Fix: libmediandk.so was never shipped, so apps linking the NDK media API (Firefox) failed to load.\n- Multidex works in isolated processes (browser renderers); Chromium 106 now starts and reaches its own Google-Play-services check."
    },
    {
      "version": "2026.10.09-r22",
      "released": "2026-10-13",
      "changes": "- New: a notification tells you when the Android 6 runtime is ready after a restart (or that this boot fell back to the stock runtime). It takes over a minute or two after the root notification; an Android app opened before that runs on the stock runtime and is closed when the switch happens.\n- Fix: the runtime could fail to start after a restart that had to rebuild its image (e.g. right after installing or upgrading). The boot step ran twice at once, and the second run pulled the image out from under the first; two such failures in one boot then disabled the runtime for the next restart too. It now runs once per boot, and waits for the root script to finish with the Android core first."
    },
    {
      "version": "2026.10.09-r21",
      "released": "2026-10-13",
      "changes": "- Telegram X now starts properly instead of showing a blank dark screen. Its network engine waits for events, and the runtime's event emulation reported every connection as ready all the time (a flag-numbering mix-up between BlackBerry and Android), so the engine spun without ever doing anything. Also fixes lost wake-ups for apps that use eventfd the way Telegram does.\n- App updates to the runtime now reach apps you have already opened: the per-app cache of adapted native libraries is rebuilt when the runtime's adaptation changes.\n- Installs no longer get stuck waiting: newdroid now nudges BlackBerry's installer for any pending request, not only Android's ID requests. Neither of our test phones runs the service that normally does this.\n- If Telegram X shows its \"Aw, Snap! TDLib fatal error\" screen once after updating, that is a record of crashes under the previous version: tap Launch App and it starts normally from then on."
    },
    {
      "version": "2026.10.09-r20",
      "released": "2026-10-11",
      "changes": "- Fixes F-Droid crashing when refreshing its repositories (\"interface not implemented\"). Several standard Java classes -- zip/jar files, network sockets, Scanner, Selector, and some resource classes -- did not declare that they can be closed automatically, which Android 6 apps (Kotlin's use {}, Java try-with-resources) rely on.\n- Fixes apps with native code crashing on launch, Telegram X among them. When an app's first native library came from its own folder, the runtime set up the Android library loader in the wrong order and the app died at once. The loader is now set up the way BlackBerry's own code does it.\n- Fixes Telegram X (and other apps built on the same network library) still aborting right after: the setting that gives an app a working epoll was never included in the package. It is now, with Telegram X and Delta Chat enabled.\n- Fixes Android apps sometimes not opening at all (the Android system stuck half-started), and Android-side installs stalling. Android asks BlackBerry's installer for an ID whenever it finds a new app, and waits for the answer; on some phones BlackBerry's installer service is not running and the answer never came. newdroid now answers those requests itself, and also restarts bb10-rootd if it ever stops during a session.\n- Fixes Android 6 sometimes not switching on after a restart. The boot step could be killed as the boot script finished, about 20 seconds in, and the runtime then stayed stock for that boot, with no log.\n- First-install message no longer says \"Setting it up now\" and then \"next restart\".\n- Package files are group-writable, so a copy installed from Rubus can be upgraded from Term49 and the other way round.\n- The runtime image is rebuilt once after this update (a few minutes)."
    },
    {
      "version": "2026.10.09",
      "released": "2026-10-09",
      "changes": "- New design: the runtime is a RAM overlay mounted after boot. Nothing is written into the Android Player, and every restart starts from the stock runtime, so a failed Android runtime can no longer cost root. Replaces the on-disk installer withdrawn on 2026-10-08.\n- No longer needs bb10-rootchain; needs bb10-rootd 20261009 or newer, which now really starts at every boot.\n- Sets itself up automatically after the first restart; self-checks every boot and falls back to stock if unhealthy.\n- HTTPS: the system certificate store is built from the device's own certmgr store.\n- Install/upgrade output is shown in full in Rubus/Term49.\n- Conformance 556 pass / 0 fail on the installed package."
    },
    {
      "version": "2026.09.27",
      "released": "2026-09-27",
      "changes": "- Installs from Rubus/apk directly: `apk add bb10-newdroid` now does the whole install, instead of staging it and asking you to finish it from a terminal.\n- OS version gate: the package refuses to install on anything but 10.3.3.3216 and names the version it found.\n- Depends on the new bb10-rootchain: a boot guard that restores the stock runtime if a patched image is found at boot, bounded boot wait-loops, and an unprivileged boot log -- so a failed runtime cannot cost you root, and if it does you can read why.\n- Always active while installed. The Settings-app toggle is gone; uninstalling removes it from devices that had it.\n- Storage Access Framework: a system document provider and picker, so ACTION_OPEN_DOCUMENT / CREATE_DOCUMENT / OPEN_DOCUMENT_TREE work.\n- SQLite 3.45.3 replaces the 2013 engine (restored on revert).\n- System CA trust store is populated from the device's own certificate manager, fixing TLS on a clean install.\n- Conformance: 556 pass / 0 fail on a package-installed device."
    },
    {
      "version": "2026.09.20",
      "released": "2026-09-20",
      "changes": "- First release. API-23 surface: 572 injected classes, rebuilt 93-file boot image. Conformance suite 574 pass / 0 fail; 31-app corpus with 0 fatal exceptions and 0 real link failures. camera2 + CameraX ImageAnalysis, MediaSession transport controls, JobScheduler, TLS 1.2, telephony/SMS/NFC, MediaRecorder. Reversible: the revert restores the device's own saved stock files and verifies all 93 by checksum."
    }
  ]
}
