Echo Show 5 Gen 2 (LineageOS)
The reported 2021 device is a 5.5-inch smart display whose reflash identifies the hardware with device codename cronos and model Amzn Echo Show 5 (2nd Generation). The community profile requires both observed values in the same match group; it can be broadened only after another diagnostic proves a real firmware variant.
| Profile fingerprint | device cronos plus model Amzn Echo Show 5 (2nd Generation) |
| SoC | MediaTek MT8163, four cores |
| Android | LineageOS 18.1 / Android 11 (API 30), userdebug |
| ABI | armeabi-v7a (32-bit userspace) |
| Display | 960×480 at 195 dpi, 5.5 inches |
| RAM / storage | 1 GB / 8 GB |
| Root | app-accessible Android-style su on the one reported LineageOS build |
| Sensors | ambient light reported; no Android proximity sensor reported |
| LED / relays / Zigbee | none reported |
| System WebView | LineageOS WebView 146 reported |
Profile scope
Section titled “Profile scope”The community-cronos-lineageos18.yaml profile selects only existing compiled Android mechanisms: ordinary brightness-based screen-off, Android ambient-light sensing and the reported Android-style su form. It declares no RGB LED, relay, radio, hardware-button, CPU-governor or density behaviour.
The root declaration records evidence from one image; it does not grant authority. After activation and restart, the running driver must probe the live route. A missing or blocked route remains unavailable and must not be treated as proof that another reflash is compatible.
Limitations
Section titled “Limitations”- Unlocking, reflashing, recovery and maintaining the community LineageOS image are outside the ha-paneld project. No installation instructions or recovery images are supplied here.
- The profile does not describe the first-generation Echo Show 5 or any Echo Show 8 generation.
- The reported
/sys/class/leds/lcd-backlightnode is not evidence of a supported hardware backlight writer. Screen control remains on the ordinary Android brightness route. - The reported minimum brightness of 10 matches ha-paneld’s general never-blank floor and does not establish a hardware limit.
Use the community catalogue procedure to import and validate the YAML. Review a fresh on-panel diagnostic report and confirm every expected capability after restart before relying on it unattended.
Comments
Comments are kept in this page's discussion on GitHub, so loading them connects your browser to GitHub. This browser remembers the choice and loads comments on other pages when you scroll down to them.
Comment without a GitHub account