Skip to content

Latest commit

 

History

History
131 lines (117 loc) · 11.3 KB

README.md

File metadata and controls

131 lines (117 loc) · 11.3 KB

Y2Linux documentation

Y2Linux 1.0 Beta 8.22 (Baseline 121, 2026-10-22) is the current state (eighth public beta: headphone level and profiles, faster updates, error reports, charging fix, Internal Storage setup on battery, crash loop and silent-audio fixes, songs in Strawberry over USB, random shuffle, Japanese text, large libraries, headphones after a pause and SD cards Windows reads, audiobooks and sharper covers, headphone audio that would not start): ready-made images on the GitHub releases, installed once with SP Flash Tool, then updated over Wi-Fi by the player itself (recovery and updates). No image carries MediaTek's radio firmware: each player takes it from its owner's Innioasis package (INSTALL). What works, what does not and the latest hardware results: current platform state; Last.fm scrobbling and why it is safe: Last.fm scrobbling; Internal Storage, the SD card and USB copying: Storage; audiobooks (chapters, progress, speed, sleep timer): Audiobooks; headphone level, profiles and DAC filter: Headphone output; saving a report for an issue: Error reports; the beta's evidence and open gaps: 1.0 Beta 8.22 report, 1.0 Beta 8.21 report, 1.0 Beta 8.20 report, 1.0 Beta 8.19 report, 1.0 Beta 8.17 report, 1.0 Beta 8.16 report, 1.0 Beta 8.15 report, 1.0 Beta 8.14 report, 1.0 Beta 8.13 report, 1.0 Beta 8.12 report, 1.0 Beta 8.11 report, 1.0 Beta 8.10 report, 1.0 Beta 8.9 report (not published), 1.0 Beta 8.8 report, 1.0 Beta 8.7 report, 1.0 Beta 8.6 report, 1.0 Beta 8.5 report, 1.0 Beta 8.4 report, 1.0 Beta 8.3 report, 1.0 Beta 8.2 report, 1.0 Beta 8.1 report, 1.0 Beta 8.0 report, 1.0 Beta 7.11 report, 1.0 Beta 7.10 report, 1.0 Beta 7.9 report, 1.0 Beta 7.8 report, 1.0 Beta 7.7 report, 1.0 Beta 7.6 report, 1.0 Beta 7.5 report, 1.0 Beta 7.4 report, 1.0 Beta 7.3 report, 1.0 Beta 7.2 report, 1.0 Beta 7.1 report, 1.0 Beta 7 report, 1.0 Beta 6.3 report, 1.0 Beta 6.2 report, 1.0 Beta 6.1 report, 1.0 Beta 6 report, 1.0 Beta 5.1 report, 1.0 Beta 5 report, 1.0 Beta 4.1 report, 1.0 Beta 4 report, 1.0 Beta 3 report, 1.0 Beta 2 report, 1.0 Beta 1 report.

Need Start here
Build it yourself BUILDING.md
Flash it, connect, update, go back to stock INSTALL.md
How updates and the Y2 recovery image work RECOVERY-AND-UPDATES.md
What works, what doesn't, latest hardware results Current platform state
What the path to the beta changed (35–50) 1.0 Beta 1, 49 firmware-free images, 48 download screen, 47 DSI clock gating, 46 update space, 43 restart fixed, 35 over-the-air updates
What 34 back to 13 changed 34 shipped themes, battery display, 33 themes, 32 deep idle during playback, 31 artwork and formats, 30 storage and decode speed, 29 top-off corrections, 28 stock battery percentage, 27 panel, VGP2, VSYS sleep, 26 Bluetooth codecs, 25 Cover Flow frame gate, 24 frame pacing, 23 Cover Flow and Genres, 22 dark DSI hand-over, 21 quiet display power, 20 UART1 clock, 19 PMIC_WRAP clock, 18 stock PMIC sleep settings, 17 modem gate and faster wake, 16 stock sleep parity, 15 dependency update, 14 diagnostics, 13 stock power parity
Deep sleep history (01 to 13) Deep-sleep report, suspend architecture
Charging, storage Charging policy, internal storage
Platform API and ownership Platform API, power contract
Partition layout and recovery Partitions, install runbook, recovery runbook
Build inputs and source delivery Locked environment, reconstruction, source delivery
Roadmap and open work Roadmap, scope audits, maintainer handoff
The player Y2Reborn (current state)
Every page Complete catalog, knowledge rules

Most pages under build/, validation/, hardware-evidence/ and release/ are dated records of a specific candidate. Their "current", "next" and permission statements belong to that date. Paths like out/... in them refer to the maintainer's local build outputs and are not part of the repository.

Historical navigation snapshot

The following text retains earlier dated decisions and results. Its “current”, “next” and candidate labels belong to those sessions; the Baseline02 summary above takes precedence. Historical failures and seal-time NOT_RUN receipts remain evidence for their exact images.


Y2Linux documentation

Start with the complete community beta audit and selective RC1 plan. They reconcile current source, sealed images and physical evidence at the2026-10-02 snapshot. The latest broad hardware report is CPU Final Fix02 qualification; newer storage observations are narrower and do not establish whole-system acceptance.

Need Start here
Latest facts, limits and next batch Current state
What happened on the device Fix02 physical result
Current observed capabilities Capability ledger
Exact candidate/fallback identities Candidate index
CPU source/software provenance Fix01 implementation, sources
API and subsystem ownership Platform API, contract catalog
Power/hardware acceptance gates Hardware gates
Next scope and decisions Roadmap, standing audit
Rebuild a recorded source pair Reconstruction
Application state Reborn current state
Every retained document Complete catalog
How this knowledge base stays truthful Knowledge rules

Reading older material

Historical validation, deployment, source research and hardware captures are retained at their original paths. Their "current", "next" and authorization statements apply to the recorded session. They do not override the current state or authorize another flash/test. The catalog labels records by scope; pages outside raw evidence carry corresponding notices. Original captures/checksums are unchanged.

The prior CPU Final physical run is Fix01's before-state. Hardware Final and Platform v1 completion describe earlier software boundaries, not the currently tested pair. The September 23 entry review, old issue specifications, build receipts and hardware evidence preserve provenance and narrow successes/failures. Original boot, stock ROM, partition and source research remains under knowledge/.

Earlier removed rolling handoffs remain available in Git history. This cleanup changes navigation and summaries, not candidate bytes, acceptance flags, reserved memory, firmware, keys or owner data.