SalahOS v1.6.2

SalahOS v1.6.2 release notes

SalahOS v1.6.2 is a focused Qur’an editorial and governance update following the expanded Muhkam/Mutashabih review of the SalahOS 2026 English-meaning layer. It incorporates the reconciled project-guide treatment now on main while preserving explicit disclosure that independent qualified scholarly review is still pending.

Release status: v1.6.2 is published as a project-owner-authorized prerelease while independent qualified whole-corpus scholarly review remains pending. This release status is not scholarly certification, and no pending review row has been converted into an approval.

Qur’an Muhkam/Mutashabih reconciliation

• Maintains 143 translation-risk verses under the supplied Muhkam/Mutashabih and tanzīh review policy.
• Maintains a 147-row review register: 143 trigger verses plus four governing Muhkam foundations.
• Gives every maintained trigger an explicit SalahOS 2026 English meaning instead of silently falling back to the Pickthall baseline.
• Applies direct non-corporeal contextual taʾwīl to all seven Qur’anic istiwāʾ-over-the-Throne passages, using absolute dominion/subjugation wording and explicitly rejecting sitting, place, direction, movement and bodily modality.
• Retains the project-guide treatments for expressions including wajh, yad, sāq, nūr, maʿiyyah, fawqiyyah and related translation-risk language without turning verse-specific taʾwīl into global lexical replacement.
• Includes the ru’yah pair 6:103 and 75:23, preserving the distinction between non-encompassment and the believers’ seeing Allah in the Hereafter without direction or modality.
• Includes the later need/dependency/transaction idiom pass so expressions such as lending to Allah, helping Allah and commercial imagery do not imply divine need, dependence or gain from deficiency.

Review and provenance status

• All generated review rows remain status: pending-scholar-review with reviewer: null.
• The 2026-09-09 project-owner whole-corpus record remains an editorial/release attestation only, not independent qualified scholarly approval.
• The v1.6.2 release authorization is exact-version and prerelease-only while qualifiedScholarReviewStatus remains pending.
• Stable publication remains gated on independent qualified scholarly approval unless the project policy is explicitly revised with equivalent transparent provenance.

Quality and release engineering

• Synchronises npm/package-lock to 1.6.2, Android to versionCode 13 / versionName 1.6.2, and iOS to build 13 / marketing version 1.6.2.
• Retains formatting, lint, typecheck, unit/coverage, Qur’an integrity/governance, dependency/security, mosque reproducibility, production-build and bundle-budget checks.
• Retains permanent Quality, Visual Regression, Android emulator lifecycle, iPhone/iPad Simulator and Windows executable workflows.
• Keeps publication tied to the exact current main revision, persistent Android signing, archive integrity, exact final file-set verification and SHA-256 verification.

Downloadable v1.6.2 assets

A successful publication contains:

• SalahOS-v1.6.2-android.apk
• SalahOS-v1.6.2-android.aab
• SalahOS-v1.6.2-windows-x64.exe
• SalahOS-v1.6.2-web-pwa.zip
• SalahOS-v1.6.2-raspberry-pi-kiosk.tar.gz
• SHA256SUMS.txt

GitHub also exposes the standard source-code ZIP and tarball for the release tag.

Distribution boundaries

A consumer iOS/iPadOS .ipa is not included because Apple distribution signing/provisioning is not configured. The iOS build remains covered by the repository’s iPhone/iPad Simulator validation workflow. No native macOS .dmg is included because SalahOS has no native macOS target.

Physical Android/iOS device acceptance remains a separately tracked hardware-validation item; emulator, Simulator and browser evidence are not represented as physical-device testing.

Author

privacyOG

SalahOS v1.6.1

SalahOS v1.6.1 release notes

SalahOS v1.6.1 is a focused post-v1.6.0 update for Qur’an navigation, mobile Arabic/RTL presentation and the Hadith library. It contains the two feature updates merged to main after v1.6.0 and keeps the existing exact-main release, signing and checksum safeguards.

Qur’an reader improvements

• Adds faster Surah and Ayah navigation in the Knowledge Qur’an reader.
• Improves mobile layout and deep-verse navigation behavior.
• Makes translation verse references more explicit and easier to follow.
• Strengthens wrapped Arabic RTL rendering so Arabic remains right-aligned across wrapped lines and narrow phone widths.
• Adds dedicated Qur’an navigation and wrapped-Arabic RTL visual acceptance coverage.

Hadith library

• Adds The Forty Nawawi Hadiths as a complete offline collection containing all 42 numbered entries supplied for the project.
• Organises Hadith content by scholar/compiler and collection, including Imam al-Nawawi and the existing curated Imam al-Bukhari and Imam Muslim selections.
• Adds search across hadith title/text, scholar names, collection names and references.
• Preserves the existing Bukhari and Muslim entries as clearly identified curated selections rather than representing them as complete Sahih collections.
• Adds mobile-friendly scholar/collection browsing and dedicated Hadith-library visual acceptance.
• Enforces Arabic dir="rtl", right alignment, bidi isolation and wrapped-line right alignment in the Hadith reader.

Quality and release engineering

• Synchronises npm/package-lock to 1.6.1, Android to versionCode 12 / versionName 1.6.1, and iOS to build 12 / marketing version 1.6.1.
• Retains formatting, lint, typecheck, unit/coverage, Qur’an integrity/governance, dependency/security, mosque reproducibility, production-build and bundle-budget checks.
• Retains permanent Quality, Visual Regression, Android emulator lifecycle, iPhone/iPad Simulator and Windows executable workflows.
• Keeps publication fail-closed on the exact current main revision, persistent Android signing, archive integrity, exact final file-set verification and SHA-256 verification.

Downloadable v1.6.1 assets

A successful publication contains:

• SalahOS-v1.6.1-android.apk
• SalahOS-v1.6.1-android.aab
• SalahOS-v1.6.1-windows-x64.exe
• SalahOS-v1.6.1-web-pwa.zip
• SalahOS-v1.6.1-raspberry-pi-kiosk.tar.gz
• SHA256SUMS.txt

GitHub also exposes the standard source-code ZIP and tarball for the release tag.

Distribution boundaries

A consumer iOS/iPadOS .ipa is not included because Apple distribution signing/provisioning is not configured. The iOS build remains covered by the repository’s iPhone/iPad Simulator validation workflow. No native macOS .dmg is included because SalahOS has no native macOS target.

Physical Android/iOS device acceptance remains a separately tracked hardware-validation item; emulator, Simulator and browser evidence are not represented as physical-device testing.

Author

privacyOG

SalahOS v1.6.0

SalahOS v1.6.0 release notes

SalahOS v1.6.0 is a mobile usability, Qur’an reliability, Islamic Knowledge organisation, theme and release-hardening update. It improves small-screen, large-text, Arabic/RTL and offline behavior while preserving provenance, signing and exact-head release checks.

Highlights

• Removes Iqamah content from Today while retaining prayer start times, locality and calculation provenance.
• Adds persistent Standard, Light Blue, Emerald, Navy, Warm Sand and Soft Lavender palettes independently of Light, Dark or System appearance.
• Improves mobile Calendar, mosque empty/offline/location-denied states, Qiblah sensor fallbacks and Settings discoverability.
• Adds permanent responsive acceptance across 320×568, 360×780, 390×844, 430×932, 844×390 and 768×1024, including Arabic RTL and 200% text scenarios.

Qur’an reader and SalahOS 2026

• Adds SalahOS 2026 (English meaning) as the default English-meaning mode, transparently derived from the pinned M. M. Pickthall (1930) baseline/reference with project-guide verse-specific overrides.
• Keeps M. M. Pickthall (1930) separately selectable and preserves Arabic-only reading.
• Applies the supplied Ashʿarī Muhkam/Mutashabih methodology to the required seed passages, preserving Salaf-style tafwīd/tanzīh and contextual Khalaf taʾwīl notes where provided.
• Pins Qur’anic Arabic as Uthmani · Medina Mushaf · Hafs, with explicit Arabic language metadata, RTL direction, right alignment and bidi isolation.
• Corrects opening Bismillah presentation: Al-Fātiḥah retains Bismillah as ayah 1; At-Tawbah receives no opening Bismillah; ordinary surahs display one standalone opening Bismillah without duplicating a source prefix in ayah 1.
• Keeps canonical packaged Qur’an bytes and integrity hashes unchanged while performing Bismillah normalization only in the reader display layer.
• Preserves search, bookmarks, Resume, copy/share, retry recovery and normalized Arabic search without modifying canonical display text.

Whole-corpus sign-off

The project owner privacyOG explicitly signed off the complete 114-surah / 6,236-ayah SalahOS 2026 corpus for V1.6.0 release on 2026-09-09. The authoritative sign-off is recorded in src/data/quran-scholarly-signoff.json.

The verse-level review register remains supplemental provenance and is not artificially expanded into 6,236 machine-generated reviewer records. CI validates the complete corpus, required Mutashabih seed treatments, translation identity, Uthmani/Hafs/Medina provenance and the explicit whole-corpus sign-off.

Islamic Knowledge

• Separates Qur’an, Hadith and Fiqh & questions scopes.
• Makes content and source information easier to reach on mobile while keeping translation distinct from commentary.
• Renames the abbreviated Hadith “Isnad” field to Companion narrator while retaining sourced grading and school distinctions.
• Aligns curated Qur’an excerpts with the SalahOS 2026 identity while preserving explicit Uthmani Arabic, Pickthall baseline and tafsir provenance.

Quality and release engineering

• Synchronises npm/package-lock to 1.6.0, Android to versionCode 11 / versionName 1.6.0, and iOS to build 11 / marketing version 1.6.0.
• Retains formatting, lint, typecheck, unit/coverage, Qur’an integrity/governance, dependency/security, mosque reproducibility, production-build and bundle-budget checks.
• Retains permanent Quality, Visual Regression, Android emulator lifecycle, iPhone/iPad Simulator and Windows executable workflows.
• Keeps publication fail-closed on the exact current main revision, persistent Android signing, archive integrity, exact final file-set verification and SHA-256 verification.

Downloadable v1.6.0 assets

A successful publication contains:

• SalahOS-v1.6.0-android.apk
• SalahOS-v1.6.0-android.aab
• SalahOS-v1.6.0-windows-x64.exe
• SalahOS-v1.6.0-web-pwa.zip
• SalahOS-v1.6.0-raspberry-pi-kiosk.tar.gz
• SHA256SUMS.txt

GitHub also exposes the standard source-code ZIP and tarball for the release tag.

Distribution boundaries

A consumer iOS/iPadOS .ipa is not included because Apple distribution signing/provisioning is not configured. No native macOS .dmg is included because SalahOS has no native macOS target.

Physical Android/iOS device acceptance remains a separately tracked hardware-validation item. Emulator/Simulator/browser evidence is not represented as physical-device testing. By project-owner release decision, that outstanding hardware validation is documented as a post-release follow-up rather than a blocker to the V1.6.0 downloadable release.

Author

privacyOG

SalahOS v1.5.3

SalahOS v1.5.3 release notes

SalahOS v1.5.3 is a prayer-correctness, Qur’an-reading, notification-onboarding and UX refinement release. It tightens mosque data handling, makes prayer-state semantics more explicit, improves navigation across the full 6,236-ayah Qur’an corpus, and preserves the project’s strict provenance, licensing, accessibility and exact-head release contracts.

Prayer correctness and Today

• Rejects implausible published mosque congregation times instead of clamping or silently shifting them, including guarded Fajr, Dhuhr, Asr, Maghrib and Isha acceptance windows and Isha midnight-wrap handling.
• Hardens the Australian mosque data generators so Jumu’ah collisions and coarse impossible fard-time candidates are dropped before reaching runtime data.
• Prevents a far-away selected mosque from silently relocating the user’s prayer calculation beyond the named 150 km guard while still allowing its published congregation/Jumu’ah information to be viewed.
• Promotes every available Friday Jumu’ah session directly beneath the Today hero and carries directory-published Jumu’ah times through the selected-mosque context without inventing khutbah times.
• Adds a Night section for Islamic midnight, final-third/Tahajjud start and optional configured Ishraq/Duha, with an explicit night-end convention.
• Widens the Hijri correction control from ±2 to ±3 days.
• Replaces the ambiguous “Between prayer times” state with explicit civil-day schedule states. Before Fajr, SalahOS reports that it is before today’s first obligatory prayer rather than silently carrying the previous civil day’s Isha forward. This is a presentation convention, not a fiqh ruling about prayer validity.
• Adds a persistent method/Asr provenance chip and refreshes Today when settings or selected-mosque profile state changes.

First-run setup and prayer notifications

• Adds a focused first-run prayer-setup step for calculation method and Asr convention, including offline country-based method suggestions, an MWL fallback and Standard/Hanafi Asr preview times.
• Adds a third onboarding step for local prayer notifications with accurate platform-limitations copy and existing per-prayer preference semantics.
• Requests native notification permission only after explicit opt-in; skipping or declining does not cause automatic re-prompting and notification controls remain reachable later in Settings.
• Preserves Android exact-alarm handling behind explicit user action, keeps an inexact fallback when exact scheduling is unavailable, and preserves reboot/reschedule restoration behavior.

Qur’an and Islamic Knowledge

• Gives the Qur’an a dedicated deep-linkable reading route while retaining Library / Qur’an / Hadith navigation inside Knowledge.
• Bundles the Amiri Quran font under SIL OFL 1.1, removes conflicting Arabic typography rules and standardises Qur’an font/scale state across reader surfaces.
• Makes the full 6,236-ayah corpus practical to navigate with searchable surah indexing, Juz and mushaf-page navigation, continuous virtualised surah scrolling, per-surah scroll restoration and Resume last read highlighting.
• Improves ayah presentation with Arabic-Indic end markers, surah header bands, basmala exceptions, cleaner reading controls and less repetitive provenance chrome.
• Gives translation/transliteration and mixed-script metadata explicit lang/dir handling and strengthens RTL isolation.
• Moves Qur’an aria-live behavior to a concise result-status region so screen readers do not re-announce whole passages.
• Localises Juz/page/reference/source labels and numbers, and keeps required Tanzil attribution and its reviewed external-link path visible in-app.
• Keeps the current curated hadith scope honest about partial Arabic matn, isnad, grading authority and unavailable metadata.
• No new rights-pending Qur’an translation or transliteration content is bundled in v1.5.3. The approved licensing strategy remains gated on actual written permission or a compatible licence before product integration.

UX, navigation and performance

• Refines Sunrise as a visually secondary non-prayer boundary and distinguishes selected-mosque, approximate and saved/precise location states without changing prayer semantics.
• Consolidates phone bottom-navigation ownership, equal-width six-destination layout and overflow handling, including the shorter Indonesian Ilmu label.
• Reduces lower-hierarchy Today eyebrow density to sentence case/weight 600 while preserving strong uppercase tracking for hero prayer/countdown labels and RTL overrides.
• Splits astronomical schedule computation from live countdown derivation, memoises schedule work across stable date/settings/location inputs, and reduces unnecessary per-second recomputation.

Quality and release engineering

• V1.5.3 implementation items were accepted through the permanent Quality, Visual Regression, Android emulator lifecycle, fresh iPhone/iPad Simulator and Windows executable workflows before release reconciliation.
• Preserves design-token ownership, domain/platform/UI boundaries, native-permission policy, remote-network policy, dependency audit/licensing checks, Qur’an integrity/governance, mosque-directory reproducibility, coverage, production build and bundle-budget enforcement.
• Keeps the reviewed Today typography golden-image delta scenario-scoped rather than weakening the global visual-regression threshold.

Release reconciliation

• Synchronises npm, package-lock, Android and iOS marketing versions at 1.5.3.
• Advances Android versionCode and iOS CURRENT_PROJECT_VERSION together from build 9 to build 10.
• Preserves fail-closed exact-current-main release preflight, Android production-signing verification, archive-integrity checks and exact-final-file-set verification.

Downloadable v1.5.3 assets

A successful v1.5.3 publication includes:

• SalahOS-v1.5.3-android.apk — persistently signed Android release APK for direct installation;
• SalahOS-v1.5.3-android.aab — persistently signed Android App Bundle for Google Play/distribution workflows;
• SalahOS-v1.5.3-windows-x64.exe — self-contained 64-bit Windows 10/11 desktop executable;
• SalahOS-v1.5.3-web-pwa.zip — complete production Web/PWA package;
• SalahOS-v1.5.3-raspberry-pi-kiosk.tar.gz — production Web/PWA files plus Raspberry Pi/Linux Chromium kiosk launch and autostart helpers;
• SHA256SUMS.txt — SHA-256 hashes for the packaged release assets.

The Windows executable includes its .NET runtime and expects the Microsoft Edge WebView2 Runtime, normally present on current Windows 10/11 installations. GitHub also exposes the standard source-code ZIP and tarball for the release tag.

Distribution boundaries

• A consumer iOS/iPadOS .ipa is not published until Apple distribution signing/provisioning is configured and a distribution archive can be validated. iPhone/iPad Simulator acceptance is test evidence, not a consumer installer.
• No native macOS .dmg is published because SalahOS does not contain a native macOS application target.
• Physical Raspberry Pi, TV/panel, iPhone/iPad and broad Android OEM acceptance is not inferred from browser, emulator or Simulator evidence.

Release gates

The v1.5.3 release revision must be the exact current main commit and pass the permanent Quality Gate, Visual Regression, Android, iOS and Windows workflows. The release-asset workflow reruns repository quality checks, verifies persistent Android signing, builds and verifies APK/AAB packages, validates Web/PWA and Raspberry Pi archives, checks the exact final file set and SHA-256 manifest, and only then creates or updates the GitHub release. The Windows workflow independently self-tests the packaged executable and reconciles its checksum into the published manifest.

Author

privacyOG

SalahOS v1.5.2

SalahOS v1.5.2 release notes

SalahOS v1.5.2 expands the Australian mosque experience and corrects the Fajr/Sunrise prayer-state boundary while preserving the exact-head quality, signing and packaging contract established in prior releases.

Australian mosque directory

• Expands the bundled Australian mosque catalogue from the former 106-record OpenStreetMap-only runtime to a 254-record deduplicated combined directory built from reviewed OpenStreetMap and Australian Mosque Finder factual source snapshots.
• Preserves source provenance and attribution through the combined catalogue and deployable country/region packs.
• Uses audited and evidence-scored cross-source identity matching, coordinate quarantine for unsafe geospatial records and explicit protection against known false merges.
• Keeps the directory offline-first and integrates the combined catalogue into the shared directory service and generated Australian state/territory packs.
• Strengthens reproducibility and visual acceptance so source, combined and pack outputs must remain internally consistent with the 254-record contract.

Selected mosque prayer and Iqamah context

• Use mosque now activates the selected directory mosque as the Today prayer-location context without overwriting the user's separately saved personal location.
• Prayer starts continue to use SalahOS calculation settings at the selected mosque's coordinates and timezone unless an explicit authoritative local-mosque timetable is selected.
• Explicit mosque-specific congregation times published by the Australian Mosque Finder listing are surfaced as Iqamah/Jama'ah times.
• Multiple published congregation sessions remain visible rather than being collapsed to one value.
• Missing congregation times are shown as Not published; SalahOS does not fabricate an Iqamah time.
• Generic locality prayer calendars are not mislabelled as mosque-specific Iqamah data.
• A separately configured full local-mosque timetable remains authoritative and is not overridden by directory metadata.

Fajr and Sunrise correctness

• Adds Sunrise permanently to the Today timetable as a distinct non-prayer time labelled as the point where Fajr ends.
• Corrects current-prayer resolution so Fajr can no longer remain marked as current after Sunrise.
• Between Sunrise and Dhuhr, Today reports the state as Between prayer times while Dhuhr remains the next obligatory prayer.
• Sunrise is never treated as an obligatory prayer, current prayer or next obligatory prayer, and its Iqamah value is correctly shown as not applicable.
• Updates mobile, tablet, accessibility, RTL, weather and device-UX visual contracts to preserve exactly five obligatory prayer rows plus the separate Sunrise boundary row.

Quality and release engineering

• Preserves strict Prettier, ESLint and TypeScript checks with no suppressions added for this release.
• Keeps the 254-record Australian source/combined/pack reproducibility checks and shared-directory acceptance in the permanent Quality Gate.
• Keeps the main JavaScript chunk below the unchanged 550,000-byte architecture budget by persisting only a lightweight selected-mosque context rather than eagerly bundling the complete Australian catalogue into Today.
• Preserves full unit/coverage, production-build, bundle-budget, visual-regression, Android emulator lifecycle, fresh iPhone/iPad Simulator and packaged Windows executable acceptance.

Release reconciliation

• Synchronises npm, package-lock, Android and iOS marketing versions at 1.5.2.
• Advances Android versionCode and iOS CURRENT_PROJECT_VERSION together to build 9.
• Preserves fail-closed exact-current-main release preflight, persistent Android production-signing verification, archive integrity checks and exact-final-file-set verification.

Downloadable v1.5.2 assets

A successful v1.5.2 publication includes:

• SalahOS-v1.5.2-android.apk — persistently signed Android release APK for direct installation;
• SalahOS-v1.5.2-android.aab — persistently signed Android App Bundle for Google Play/distribution workflows;
• SalahOS-v1.5.2-windows-x64.exe — self-contained 64-bit Windows 10/11 desktop executable;
• SalahOS-v1.5.2-web-pwa.zip — complete production Web/PWA package;
• SalahOS-v1.5.2-raspberry-pi-kiosk.tar.gz — production Web/PWA files plus Raspberry Pi/Linux Chromium kiosk launch and autostart helpers;
• SHA256SUMS.txt — SHA-256 hashes for all packaged release assets.

The Windows executable includes its .NET runtime and expects the Microsoft Edge WebView2 Runtime, normally present on current Windows 10/11 installations. GitHub also exposes the standard source-code ZIP and tarball for the release tag.

Distribution boundaries

• A consumer iOS/iPadOS .ipa is not published until Apple distribution signing/provisioning is configured and a distribution archive can be validated. iPhone/iPad Simulator acceptance is test evidence, not a consumer installer.
• No native macOS .dmg is published because SalahOS does not contain a native macOS application target.
• Physical Raspberry Pi, TV/panel, iPhone/iPad and broad Android OEM acceptance is not inferred from browser, emulator or Simulator evidence.

Release gates

The v1.5.2 release revision must be the exact current main commit and pass the permanent Quality Gate, Visual Regression, Android, iOS and Windows workflows. The release-asset workflow reruns repository quality checks, verifies persistent Android signing, builds and verifies APK/AAB packages, validates Web/PWA and Raspberry Pi archives, checks the exact final file set and SHA-256 manifest, and only then creates or updates the GitHub release. The Windows workflow independently self-tests the packaged executable and reconciles its checksum into the published manifest.

Author

privacyOG

SalahOS v1.5.1

SalahOS v1.5.1 release notes

SalahOS v1.5.1 is a focused quality, accessibility and usability update that completes the v1.5.1 theme and Prayer Calendar programme while preserving the release-verification contract established in v1.5.0.

Theme, contrast and visual consistency

• Strengthens semantic foreground/background ownership so Light, Dark and System appearance modes remain readable and predictable.
• Adds and validates eight curated palettes: Salah Classic, Midnight Gold, Emerald Mosque, Royal Blue, Desert Sand, Olive Heritage, Monochrome and High Contrast.
• Keeps appearance mode independent from palette selection and persists the selected palette through Display settings.
• Extends the shared theme contract across phone, tablet, Web/PWA and mosque/smart-display surfaces.
• Strengthens display-oriented hierarchy for clock, next prayer, prayer/Iqamah rows, announcements and mosque branding without creating a separate styling system.
• Expands representative theme-matrix contrast checks, RTL/large-text coverage and regression protection for the Today and Qiblah readability failure classes.

Hijri-aligned Prayer Calendar

• Adds a dedicated Prayer Calendar destination with Daily, Weekly, Monthly and Yearly views without changing the Today screen.
• Aligns Gregorian and Hijri presentation through the Umm al-Qura calendar while preserving the existing optional local Hijri correction of ±2 days.
• Standardises English Hijri month names and explicitly displays the AH era.
• Locks reference acceptance for 1 January 2026 = 12 Rajab 1447 AH and key 2026 Hijri month/year boundaries.
• Keeps all calendar views on the same civil-date, location, timezone, calculation-method and prayer-time pipeline so views remain mutually consistent.
• Adds responsive, RTL and accessibility coverage for the Prayer Calendar.

Instructions and operational guidance

• Adds Instructions guide.md for ordinary users and mosque administrators.
• Covers Android, iPhone/iPad, Web/PWA, Raspberry Pi and TV/kiosk operation.
• Documents setup, location, prayer calculation and madhhab options, Iqamah, Qiblah, mosque features, Adhan/notifications, language/themes, offline use, display operation, updates, troubleshooting and reset.

Release reconciliation

• Synchronises npm, package-lock, Android and iOS marketing versions at 1.5.1.
• Advances Android versionCode and iOS CURRENT_PROJECT_VERSION together to build 8.
• Preserves fail-closed exact-main release preflight, Android production-signing verification, archive integrity checks and final package verification.
• Corrects the mobile device-UX acceptance contract so it matches the current seven route-capable destinations, with Community retained as a route but hidden from the six-item mobile primary navigation.

Downloadable v1.5.1 assets

A successful v1.5.1 publication includes:

• SalahOS-v1.5.1-android.apk — persistently signed Android release APK for direct installation;
• SalahOS-v1.5.1-android.aab — persistently signed Android App Bundle for Google Play/distribution workflows;
• SalahOS-v1.5.1-windows-x64.exe — self-contained 64-bit Windows 10/11 desktop executable;
• SalahOS-v1.5.1-web-pwa.zip — complete production Web/PWA package;
• SalahOS-v1.5.1-raspberry-pi-kiosk.tar.gz — production Web/PWA files plus Raspberry Pi/Linux Chromium kiosk launch and autostart helpers;
• SHA256SUMS.txt — SHA-256 hashes for all packaged release assets.

The Windows executable includes its .NET runtime and expects the Microsoft Edge WebView2 Runtime, normally present on current Windows 10/11 installations. GitHub also exposes the standard source-code ZIP and tarball for the release tag.

Distribution boundaries

• A consumer iOS/iPadOS .ipa is not published until Apple distribution signing/provisioning is configured and a distribution archive can be validated. iPhone/iPad Simulator acceptance is test evidence, not a consumer installer.
• No native macOS .dmg is published because SalahOS does not contain a native macOS application target.
• Physical Raspberry Pi, TV/panel, iPhone/iPad and broad Android OEM acceptance is not inferred from browser, emulator or Simulator evidence.

Release gates

The v1.5.1 release revision must be the exact current main commit and pass the permanent Quality Gate, Visual Regression, Android and iOS workflows. Stage 5.1 is accepted only when its calendar acceptance runs successfully on that exact final head. Stage 7 is accepted only after the complete v1.5.1 reconciliation is green.

The core release-asset workflow reruns repository quality checks, verifies persistent Android signing, builds and verifies APK/AAB packages, validates Web/PWA and Raspberry Pi archives, checks the exact final file set and SHA-256 manifest, and only then creates or updates the GitHub release. The Windows release workflow independently self-tests the packaged executable and reconciles the published checksum manifest.

Implementation and exact-head completion state are recorded in TEMP_TODO_V1.5.1.md. See Instructions guide.md, docs/RELEASE_ASSETS.md, TESTING.md, TODO.md and docs/PLATFORM_STATUS.md for detailed operation, validation and distribution boundaries.

Author

privacyOG

SalahOS v1.5.0

SalahOS v1.5.0 release notes

SalahOS v1.5.0 completes the ten-stage v1.5 programme with stronger real-world resilience, richer mosque and Islamic-content experiences, clearer privacy controls, more focused product UX, and an explicit release-verification contract across Web, Android, iOS/iPadOS, Windows, Raspberry Pi Touch Display and TV/kiosk targets.

Location, weather and local context

• Strengthens best-available location handling so precise GPS remains preferred while network-assisted fallback is used only after non-terminal precision failures.
• Preserves terminal permission-denial behaviour and fails closed when both precise and approximate acquisition fail instead of inventing coordinates.
• Integrates automatic local weather with cached current/daily context, stale-cache recovery on provider/network failure and expiry of obsolete weather data.
• Improves Today around current/next prayer, prayer times, weather, location confidence and concise local context.

Mosque directory and timetable quality

• Expands mosque directory coverage and enrichment with distance-aware discovery, selection/favourites, directions, report/edit flows, verification/freshness state, provenance and data-quality scoring.
• Adds explicit quality checks for completeness, provenance coverage, freshness boundaries and unresolved-data conflict penalties.
• Removes unsafe website/social URLs before they can become user actions.
• Preserves local-mosque timetable precedence over calculated times and exposes missing mosque entries as unavailable rather than silently substituting calculated data.
• Keeps timetable date validation fail-closed so mosque data from the wrong civil date cannot override the active schedule.

Qur'an, Hadith, Fiqh and Islamic Knowledge

• Expands the Islamic Knowledge experience while preserving source/reference provenance and governance requirements.
• Strengthens Qur'an offline/content handling and the supporting content-source policy.
• Extends Hadith and Fiqh/Q&A presentation with explicit reference, grading/scholarly attribution and juristic-context safeguards where applicable.
• Keeps Islamic-content source governance in the permanent Quality Gate.

Product UX refinement

• Strengthens Today hierarchy around current/next prayer and reduces explanatory-card clutter through progressive disclosure.
• Simplifies phone navigation to the primary destinations while preserving the broader desktop experience.
• Reorganises Settings into Location, Prayer settings, Adhan, Display, Mosques, Privacy & data and Advanced.
• Preserves SalahOS visual identity while improving location-confidence feedback, Arabic/RTL behaviour and compact-device usability.

Real-world and accessibility verification

• Expands automated GPS/location fallback, weather failure/cache, mosque data-quality/action and timetable-precedence tests.
• Adds a v1.5 representative acceptance matrix for Android-phone, iPhone and iPad viewports with 200% text scaling, reduced-motion preference and assistive-technology-oriented accessible-name/current-prayer semantics.
• Retains dedicated Raspberry Pi Touch Display acceptance across representative 5-inch, 7-inch and 10-inch portrait/landscape profiles.
• Retains TV/kiosk acceptance across all prayer-board templates at 1920×1080 and 3840×2160, including safe-frame, burn-in mitigation and keyboard recovery checks.
• Retains axe-core WCAG A/AA, RTL/container-overflow and cross-browser Chromium/Firefox/WebKit acceptance.
• Clearly distinguishes emulator, Simulator and browser evidence from physical-device testing. Physical Android OEM, iPhone/iPad, Raspberry Pi Touch Display and TV/panel acceptance remains supplementary where hardware is available.

See docs/REAL_WORLD_VERIFICATION_V1.5.md for the Stage 9/10 acceptance matrix and physical-device boundary.

Release reconciliation

• Synchronises npm, package-lock, Android and iOS marketing versions at 1.5.0.
• Advances Android versionCode and iOS CURRENT_PROJECT_VERSION together to build 7.
• Preserves the established release-asset pipeline for persistently signed Android APK/AAB, Web/PWA ZIP, Raspberry Pi kiosk archive and portable SHA-256 manifest.
• Adds a self-contained Windows x64 desktop executable with the production SalahOS application embedded and a packaged self-test before publication.
• Preserves fail-closed release preflight for exact-main revision, Android signing, version/build parity, archive integrity and final package contents.

Downloadable v1.5.0 assets

A successful v1.5.0 publication includes:

• SalahOS-v1.5.0-android.apk — persistently signed Android release APK for direct installation;
• SalahOS-v1.5.0-android.aab — persistently signed Android App Bundle for Google Play/distribution workflows;
• SalahOS-v1.5.0-windows-x64.exe — self-contained 64-bit Windows 10/11 desktop executable;
• SalahOS-v1.5.0-web-pwa.zip — complete production Web/PWA package;
• SalahOS-v1.5.0-raspberry-pi-kiosk.tar.gz — production Web/PWA files plus Raspberry Pi/Linux Chromium kiosk launch and autostart helpers;
• SHA256SUMS.txt — SHA-256 hashes for all packaged release assets.

The Windows executable includes its .NET runtime and expects the Microsoft Edge WebView2 Runtime, normally present on current Windows 10/11 installations. GitHub also exposes the standard source-code ZIP and tarball for the release tag.

Distribution boundaries

• A consumer iOS/iPadOS .ipa is not published until Apple distribution signing/provisioning is configured and a distribution archive can be validated. Fresh iPhone and iPad Simulator acceptance is test evidence, not a consumer installer.
• No native macOS .dmg is published because SalahOS does not contain a native macOS application target.
• Physical Raspberry Pi, TV/panel, iPhone/iPad and broad Android OEM acceptance is not inferred from browser, emulator or Simulator evidence.

Release gates

The v1.5.0 release revision must be the exact current main commit and pass the permanent Quality, Visual Regression, Android and iOS workflows. The exact final pull-request head is revalidated after tracker reconciliation before merge. The iOS runtime gate is accepted only when the fresh iPhone/iPad Simulator install/launch/relaunch step itself reports success, not merely when the enclosing workflow reports success.

The core release-asset workflow then reruns repository quality checks, verifies persistent Android signing, builds and verifies APK/AAB packages, validates Web/PWA and Raspberry Pi archives, checks the exact final file set and SHA-256 manifest, and only then creates or updates the GitHub release. The Windows release workflow runs independently with read-only build permissions, self-tests the packaged executable, waits for the verified core release to complete, verifies exact-main identity and then uploads the Windows executable while reconciling and revalidating SHA256SUMS.txt.

The completed implementation and exact-head evidence for all ten v1.5 stages is recorded in TEMP_TODO_V1.5.md. See docs/REAL_WORLD_VERIFICATION_V1.5.md, docs/RELEASE_ASSETS.md, TESTING.md, TODO.md and docs/PLATFORM_STATUS.md for detailed validation and distribution boundaries.

Author

privacyOG

SalahOS v1.4.0

SalahOS v1.4.0 release notes

SalahOS v1.4.0 completes the ten-stage v1.4 programme and packages the resulting release-ready targets from one exact, validated main revision. The release strengthens mobile accessibility, makes live Qiblah guidance substantially more automatic and resilient, expands mosque and Islamic-content capabilities, improves startup architecture, and raises permanent verification coverage across browsers and native runtimes.

Mobile and accessibility hardening

• Hardens compact phone layouts at 360×780 and 390×844 so the final prayer row and trailing content remain reachable above bottom navigation and safe areas.
• Improves confirmed light/dark/RTL contrast cases while preserving the established SalahOS visual identity.
• Extends automated regression coverage for navigation overlap, RTL, text expansion, viewport containment and accessibility-sensitive states.

Automatic Qiblah and compass guidance

• Automatically acquires the best available OS location when Qiblah opens and starts true-heading updates where supported, while retaining saved and manual fallbacks.
• Moves required permission education into first-run onboarding at the earliest operating-system-valid point.
• Adds a manual Recalibrate Compass action plus poor-heading-accuracy detection, guided recalibration and post-calibration reassessment.
• Makes Google Maps the primary interactive Qiblah provider with Map, Satellite and Hybrid modes, user and Kaaba markers, a high-visibility geodesic Qiblah line, full-route refit, click-to-pin selection and provider-error recovery.
• Keeps a network-free manual-pin fallback when the interactive provider is unavailable.

Mosque directories

• Adds a bundled offline-first Australian mosque catalogue generated reproducibly from a committed OpenStreetMap snapshot with contributor/ODbL provenance.
• Adds nearby ordering, text search, selection/persistence and deduplication for the bundled catalogue.
• Adds shared/community mosque directory models and service flows for text/geographical lookup, submissions, duplicate detection, moderation/edit suggestions, verification/claim state and local offline cache resilience.

Adhan audio library

• Adds two rights-verified packaged Adhan recordings with pinned provenance/attribution and normalized audio metadata.
• Adds default and per-prayer selection, preview, volume and notification-only controls.
• Keeps private user-selected local recordings device-local.
• Extends permanent quality/native bundle checks so packaged Adhan audio integrity is verified on Web, Android and iOS synchronization paths.

Islamic Knowledge

• Adds the Knowledge destination with bundled offline-first Qur'an, Hadith and Q&A starter modules.
• Adds local search and module filtering.
• Preserves explicit Qur'an source/reference labels, Hadith collection/reference/grade/grading authority and Q&A scholar/source attribution with juristic-variation notes where appropriate.
• Provides Knowledge navigation and shell copy across English, Arabic, Turkish and Indonesian, including Arabic RTL acceptance.

Performance architecture

• Removes the ineffective static edge around timetable import/export so the module is emitted as a genuine lazy chunk.
• Keeps Today eager while Admin, smart-display, Mosques, Qiblah, Knowledge, Community and Settings load at route/surface level.
• Reduces the validated startup JavaScript path from the previous approximately 882 kB monolithic chunk to a largest chunk of 469,196 bytes; the timetable-import module is approximately 4 kB and lazy loaded.
• Adds a permanent bundle architecture budget. The validated v1.4 build emits 21 JavaScript chunks, with 898,871 total JavaScript bytes.

Verification upgrades

• Adds deterministic golden screenshot regression for representative Today EN/light and Knowledge AR/dark states.
• Adds axe-core WCAG A/AA checks plus stronger RTL and viewport/container-overflow acceptance.
• Adds Chromium, Firefox and WebKit smoke journeys covering eager and lazy-loaded application surfaces.
• Locks V8 core coverage thresholds into the Quality Gate.
• Preserves exact-head Quality, Visual Regression, Android emulator lifecycle and fresh iPhone/iPad Simulator lifecycle acceptance before release.

Release and integrity improvements

• Synchronises npm, package-lock, Android and iOS marketing versions at 1.4.0.
• Advances Android versionCode and iOS CURRENT_PROJECT_VERSION together to build 6.
• Publishes both a persistently signed Android APK and signed Android App Bundle (AAB).
• Verifies the APK with Android apksigner, verifies the AAB signature, validates Web/PWA and Raspberry Pi archive integrity, and publishes a portable SHA-256 manifest covering every packaged artifact.
• Fails closed if the release candidate is not the exact current main, persistent Android release signing is unavailable, version/build metadata diverges, or the final package contains missing or unexpected files.

Downloadable v1.4.0 assets

A successful v1.4.0 publication includes:

• SalahOS-v1.4.0-android.apk — persistently signed Android release APK for direct installation;
• SalahOS-v1.4.0-android.aab — persistently signed Android App Bundle for Google Play/distribution workflows;
• SalahOS-v1.4.0-web-pwa.zip — complete production Web/PWA package;
• SalahOS-v1.4.0-raspberry-pi-kiosk.tar.gz — production Web/PWA files plus Raspberry Pi/Linux Chromium kiosk launch and autostart helpers;
• SHA256SUMS.txt — SHA-256 hashes for all packaged release assets.

GitHub also exposes the standard source-code ZIP and tarball for the release tag.

Distribution boundaries

• A consumer iOS/iPadOS .ipa is not published until Apple distribution signing/provisioning is configured and a distribution archive can be validated. Fresh iPhone and iPad Simulator acceptance is test evidence, not a consumer installer.
• No native macOS .dmg is published because SalahOS does not contain a native macOS application target.
• Physical Raspberry Pi, TV/panel, iPhone/iPad and broad Android OEM acceptance remains separate from automated browser, emulator, Simulator and packaging evidence.

Release gates

The v1.4.0 release revision must be the exact current main commit and pass the permanent Quality, Android, Visual Regression and iOS workflows. The release-asset workflow then reruns the complete repository quality gate, verifies persistent Android signing, builds and verifies APK/AAB packages, validates Web/PWA and Raspberry Pi archives, checks the exact final file set and SHA-256 manifest, and only then creates or updates the GitHub release.

The completed implementation and exact-head evidence for all ten v1.4 stages is recorded in TEMP_TODO_V1.4.md. See docs/RELEASE_ASSETS.md, TESTING.md, TODO.md and docs/PLATFORM_STATUS.md for detailed implementation, validation and distribution boundaries.

Author

privacyOG

SalahOS v1.3.0

SalahOS v1.3.0 release notes

SalahOS v1.3.0 completes the UI/UX v2 programme through Stage 27 and packages the current release-ready SalahOS targets from one exact, validated main revision. It preserves the local-first prayer engine, explicit privacy boundaries and prayer-source semantics while completing the redesigned congregation, administration, phone/tablet and smart-display experiences.

UI/UX v2 completion

• Completes the six original SalahOS prayer-board designs across managed TV/kiosk displays and validated Phone/Home Today variants.
• Adds optional fail-soft prayer-board weather plus scheduled announcement/display rotation without making remote content authoritative for prayer times.
• Completes the managed-masjid administration redesign with dedicated overview, prayer/Iqamah, Jumu'ah/Ramadan, community, display, integration, member and administration destinations.
• Completes phone, tablet, desktop, Raspberry Pi Touch Display and 1080p/4K TV/kiosk refinement.
• Completes accessibility, Arabic/RTL and visual acceptance coverage, including forced-colours, reduced-motion, text expansion and representative human review.
• Retires the legacy single-page application composition, destination-hiding CSS and root compatibility colour aliases. Dedicated v2 Settings panels and SmartDisplayApplication now own their surfaces directly.
• Keeps administrator-only fleet, credentials and publishing controls isolated from ordinary congregation workflows.

Congregation and display experience

• Prayer-first Today presentation with clear Start/Athan, Iqamah/Jama'ah, current/next prayer, countdown, Jumu'ah and Ramadan context.
• Dedicated Today, Mosques, Qiblah, Community and Settings destinations with responsive phone bottom navigation, tablet rail and desktop navigation.
• Category-based Settings for Prayer, Location, Mosque & Iqamah, Notifications & Adhan, Appearance & Language, Data & Privacy, Display Themes and Advanced controls.
• Direct Phone/Home theme selection and optional weather configuration remain available after legacy UI retirement.
• Six independently usable prayer-board templates: Heritage Classic, Minimal Modern, Bold Countdown Focus, Structured Split Board, Scenic Spiritual and Family & Classroom.
• Smart-display runtime remains isolated from congregation navigation and administration forms and continues to use authoritative local prayer data when optional remote content is unavailable.

Release and integrity improvements

• Synchronises npm, package-lock, Android and iOS marketing versions at 1.3.0.
• Advances Android versionCode and iOS CURRENT_PROJECT_VERSION together to build 5.
• Tightens exact-main release preflight to verify lockfile-version consistency and Android/iOS build-number parity.
• Produces both a persistently signed Android APK and signed Android App Bundle (AAB).
• Verifies the APK with Android apksigner, verifies the AAB JAR signature, verifies Web/PWA and Raspberry Pi archive integrity and publishes a portable SHA-256 manifest for every packaged artifact.
• Fails closed if persistent Android release signing is unavailable or if the final package contains missing or unexpected files.

Downloadable v1.3.0 assets

A successful v1.3.0 publication includes:

• SalahOS-v1.3.0-android.apk — persistently signed Android release APK for direct installation;
• SalahOS-v1.3.0-android.aab — persistently signed Android App Bundle for Google Play/distribution workflows;
• SalahOS-v1.3.0-web-pwa.zip — complete production Web/PWA package;
• SalahOS-v1.3.0-raspberry-pi-kiosk.tar.gz — production Web/PWA files plus Raspberry Pi/Linux Chromium kiosk launch and autostart helpers;
• SHA256SUMS.txt — SHA-256 hashes for all packaged release assets.

GitHub also exposes the standard source-code ZIP and tarball for the release tag.

Distribution boundaries

• A consumer iOS/iPadOS .ipa is not published until Apple distribution signing/provisioning is configured and a distribution archive can be validated. The existing iPhone/iPad Simulator acceptance is test evidence, not a consumer installer.
• No native macOS .dmg is published because SalahOS does not contain a native macOS application target.
• Physical Raspberry Pi, TV/panel, iPhone/iPad and broad Android OEM acceptance remains separate from automated browser/emulator/Simulator and packaging evidence.

Release gates

The v1.3.0 release revision must be the exact current main commit and pass the permanent Quality, Android, Visual Regression and iOS workflows. The release-asset workflow then reruns the complete repository quality gate, verifies persistent Android signing, builds and verifies APK/AAB packages, validates Web/PWA and Raspberry Pi archives, checks the exact final file set and SHA-256 manifest, and only then creates or updates the GitHub release.

See docs/RELEASE_ASSETS.md, TESTING.md, TODO.md, docs/PLATFORM_STATUS.md and docs/UI_UX_V2_PLAN.md for exact implementation, validation and distribution boundaries.

Author

privacyOG

SalahOS v1.2.1

SalahOS v1.2.1 release notes

SalahOS v1.2.1 is the first packaged release to include the completed UI/UX v2 work through Stage 23.10. It keeps the local-first prayer engine and privacy boundaries of v1.2.0 while substantially improving congregation navigation, prayer-board presentation, Qiblah usability and managed-display assignment.

UI/UX v2

• Dedicated congregation destinations for Today, Mosques, Qiblah, Community and Settings.
• Responsive phone bottom navigation, tablet navigation rail and desktop navigation with RTL-aware ordering/alignment.
• Prayer-first Today hierarchy with conditional Ramadan, Jumu'ah and community context.
• Category-based Settings with progressive disclosure for advanced timetable/import/calculation workflows.
• Consolidated SalahOS Design System v2 with semantic tokens, reusable layout/control/state primitives and accessibility contracts.
• Dedicated Mosques and Community reading experiences separated from administration workflows.

Daily Prayer Display Theme Library

• Shared versioned prayer-board data/template contract that preserves calculation, source, Iqamah and next-prayer semantics.
• Six original SalahOS display templates:
  • Heritage Classic
  • Minimal Modern
  • Bold Countdown Focus
  • Structured Split Board
  • Scenic Spiritual
  • Family & Classroom
• Full-screen preview/configuration workflow with supported module visibility, branding, locale, time-format and accent controls.
• Permanent 1080p/4K English and Arabic/RTL visual-regression coverage for the completed display templates.

Managed display assignment

• Mosque-level default prayer-board configuration with per-display override/inheritance.
• Revisioned managed-display prayer-board configuration and applied-template heartbeat reporting.
• Exact 1920×1080 and 3840×2160 landscape preview before publication; unsupported portrait/unvalidated targets are blocked.
• Last-known-good managed prayer-board cache with native persistence.
• Reconnect reconciliation that keeps local prayer calculation authoritative and uninterrupted.
• Fail-soft managed display operation when remote configuration/media synchronization is unavailable.
• Safe managed-service state migration and deterministic handling of device-local branding/background assets.

Qiblah and congregation refinements

• Dedicated Qiblah experience with dominant compass/bearing hierarchy and secondary saved/offline/manual location workflows.
• Local/offline bearing remains authoritative; optional map networking stays explicit and privacy-gated.
• Improved mosque discovery/profile and community announcement/event presentation with provenance/freshness states.

Downloadable v1.2.1 assets

A successful v1.2.1 release publishes:

• SalahOS-v1.2.1-android.apk — persistently signed Android release APK, verified with Android apksigner;
• SalahOS-v1.2.1-web-pwa.zip — production Web/PWA package;
• SalahOS-v1.2.1-raspberry-pi-kiosk.tar.gz — production Web/PWA files plus Raspberry Pi/Linux Chromium kiosk launch and autostart helpers;
• SHA256SUMS.txt — portable SHA-256 hashes for all published packages.

The workflow fails closed if Android release signing is unavailable and verifies archive integrity, checksums and the exact final asset set before publication.

Distribution boundaries

• A consumer iOS/iPadOS .ipa is not published until Apple distribution signing/provisioning is configured and validated.
• No native macOS .dmg is published because SalahOS does not yet contain a native macOS application target.
• Physical Raspberry Pi, TV/panel, iPhone/iPad and broad Android OEM acceptance remains separate from CI packaging evidence.
• Stage 23.11 optional weather, Stage 23.12 announcement/display rotation, Stage 23.13 mobile Today/home prayer-board variants and later Stage 24–27 work remain separate roadmap items and are not claimed complete by this release.

Release gates

The v1.2.1 release revision must be the exact current main commit and pass the permanent Quality, Android, Visual Regression and iOS workflows. The release-asset workflow reruns the full repository quality gate for Web/PWA/kiosk packaging, verifies persistent Android signing and apksigner, verifies portable checksums and the exact four-file package, and only then creates/uploads the GitHub release.

See docs/RELEASE_ASSETS.md, TESTING.md, TODO.md and docs/PLATFORM_STATUS.md for exact distribution and validation boundaries.

Author

privacyOG