Repository navigation
CrossPoint 1.6.5-A1.3.0
v1.3.0: ON POINT collections, BULACAN routes and 2027 holidays
Changes since v1.2.0. This release also carries the v1.2.1 maintenance changes, which were never published on their
own.
ON POINT
Route collections. ON POINT groups routes into BULACAN, NORTH LUZON and AIRPORT TRANSFERS.
- Choose one with the SELECT COLLECTION row.
- Each collection remembers its own main route.
- ON POINT opens straight to the active collection's main route.
- The choices are stored on the card in
/.crosspoint/onpoint.json.
BULACAN now has six P2P routes (two list pages):
| Route | Operator | Leaving Bulacan | Leaving Metro Manila |
|---|---|---|---|
| Balagtas ↔ TriNoma | Bulacan P2P | PROVISIONAL | PROVISIONAL |
| Caypombo ↔ SM North EDSA | Precious Grace | PUBLISHED | PROVISIONAL |
| Pandi ↔ TriNoma (new) | Bulacan P2P | PROVISIONAL | PROVISIONAL |
| Plaridel ↔ TriNoma (new) | Bulacan P2P | PROVISIONAL | PROVISIONAL |
| Malolos ↔ TriNoma (new) | Precious Grace | PUBLISHED | PROVISIONAL |
| Guiguinto ↔ TriNoma (new) | Bulacan P2P | PROVISIONAL | PROVISIONAL |
Other ON POINT changes:
- Caypombo → SM North EDSA gains the 20:30 last trip, from Precious Grace's 2026 daily schedule.
- Balagtas ↔ TriNoma is now marked PROVISIONAL. Its departure times are unchanged.
- Departure lookups are faster.
2027 holidays (Proclamation No. 1427) are added to the Calendar and to ON POINT:
- Bulacan P2P routes run their Saturday/Sunday/holiday timetable on non-working holidays.
- Special working days, such as the EDSA anniversary on 25 February 2027, keep the weekday timetable.
- Precious Grace routes run their daily timetable every day.
How to read the timetables
PROVISIONAL: estimated departures; actual times may vary.
PUBLISHED: the departure pattern follows the operator's published schedule.
Sources and limitations
Sources:
- Bulacan P2P: first and last trips come from the operator's 30 August 2026 schedule graphics, by day type.
- Departures in between follow a 30-minute pattern from published route listings. The operator's TriNoma terminal
notice gives a 30–45-minute interval, so some listed departures may not run. - Weekend in-between departures are an estimate.
- Departures in between follow a 30-minute pattern from published route listings. The operator's TriNoma terminal
- Precious Grace: first and last trips and the 30-minute interval come from the operator's 2026 daily schedule.
- Its North EDSA departure board does not assign departures to particular destinations.
- TriNoma is also a boarding point for the Caypombo route.
Guiguinto ↔ TriNoma is an editorial reconstruction.
- Bulacan P2P publishes only its first and last trips: 04:30–19:30 on weekdays and 05:00–19:30 on weekends and
holidays from Guiguinto; 06:00 (06:30 on weekends and holidays) to 21:30 from TriNoma. - Weekday Guiguinto departures follow the WalterMart Guiguinto terminal notice photographed in September 2025.
- Weekend Guiguinto departures and all TriNoma departures are reconstructed from those published first and last
trips and the route's observed patterns. - None of the in-between Guiguinto times is confirmed by the operator.
Known discrepancy: TriNoma first trips.
- An undated Bulacan P2P notice at TriNoma lists earlier first trips: Balagtas 05:30, Plaridel 05:00, and a
partly obscured route, probably Pandi, 05:30. - The operator's dated 30 August 2026 graphics give 06:00, and the board uses those.
- Earlier buses may run from TriNoma before the first time shown, and service frequency may differ.
Dispatch can vary: departures can depend on passenger loads and vehicle availability.
The holiday calendar runs to 31 December 2027. Eid'l Fitr and Eid'l Adha will be added when their dates are
proclaimed. 2028 holidays will follow in a later update.
Also in this release (v1.2.1 maintenance)
- The Library index no longer shelves DOGEAR's
/dogearcache folder. - Release tooling: the post-launch maintenance acceptance policy.
Firmware 1.6.5-A1.3.0 (CrossPoint base + APPS 1.3.0), in app packages.
Every package opens its apps from Home > Apps.
| Package | XTEINK X4 (microSD) | XTEINK X4 Pro (USB, flash at 0x0) |
|---|---|---|
| GOTO | firmware-x4-g.bin |
firmware-x4pro-g.factory.bin |
| GOTO + DOGEAR | firmware-x4-gd.bin |
firmware-x4pro-gd.factory.bin |
| ON POINT | not available (needs a real-time clock) | firmware-x4pro-p.factory.bin |
| ON POINT + DOGEAR | not available | firmware-x4pro-pd.factory.bin |
| GOTO + ON POINT | not available | firmware-x4pro-gp.factory.bin |
| GOTO + ON POINT + DOGEAR | not available | firmware-x4pro-gpd.factory.bin |
- Over Wi-Fi: Settings > System > Check for updates keeps a device on its current package.
- DOGEAR (a weekly reading digest) comes only in the packages that name it. To move a device
to one, install that package once by hand (as above); later updates keep it. - X4 (microSD): copy the file to the card and use Settings > System > SD Card Firmware Update.
firmware.binandfirmware-x4pro.binare for devices updating from 1.0.1.
e3-host-evidence.json records that this build's commit passed every required E3 host test
(DOGEAR's CAN'T LOAD AN ISSUE screen), none skipped.
Checksums are in SHA256SUMS.txt. These are the files built by release-candidate run
40715904821 from ff8df71, accepted on device before publication: x4-gd and x4pro-gpd only. Verified in CI only, not installed on a device: x4-g x4pro-g x4pro-gd x4pro-p x4pro-pd x4pro-gp. post-launch-host-evidence.json records that this build's commit passed the host tests that stand in for DOGEAR's two nothing-published checks, none skipped.
DOGEAR acceptance on v1.3.0. DOGEAR's R, Q1, Q2 and offline no-writes fixture checks were not performed on v1.3.0 hardware. The owner accepted the residual risk for this release, based on v1.2.0's completed acceptance and reviewed source comparisons. DOGEAR's live-download and offline-cache checks were performed on both v1.3.0 devices.
On each of the two packages accepted on device (x4-gd and x4pro-gpd), these eight DOGEAR fixture checks were not performed, and the owner-approved acceptance record (acceptance-sha256 30ca3715ee9a4c63ebddd2d550db7af0d5a8a8404c4378598358c1671f13e8a7, named in the v1.3.0 tag) records them as not performed, not as passed: dogear-v2-cache-offline, dogear-v3-q1-cover, dogear-v3-q1-pages, dogear-v3-q1-navigation, dogear-v3-q2-cover, dogear-v3-q2-pages, dogear-v3-q2-navigation and dogear-no-writes-offline.