ONYX BOOX Go 6 (boox-go6)
Appearance
Onyx BOOX Go 6 Onyx BOOX Go 6 | |
Manufacturer | ONYX BOOX |
---|---|
Name | Go 6 |
Codename | onyx-go6 |
Model | Go6 |
Released | 2023 |
Type | ebook reader |
Hardware | |
Chipset | Qualcomm Snapdragon 662 (SM6115) |
CPU | 4x Kryo 260 Gold @ 2.0 GHz + 4x Kryo 260 Silver @ 1.8 GHz |
GPU | Adreno 610 |
Display | 6" Carta 1300 (1448x1072) |
Storage | 32GB |
Memory | 2GB |
Architecture | aarch64 |
Software | |
Original software | Android |
Original version | 11 |
postmarketOS | |
Category | testing |
Pre-built images | no |
Unixbench Whet/Dhry score | 0.0 |
This device is marked as not booting.
Device owners
Notes
I (User:Knuxify) haven't fully looked into this device yet; here's some information I've gathered from a brief look:
- ONYX BOOX notably does not release kernel sources for their products; as such, using a downstream kernel is likely out of the question.
- Using mainline may not be easy either; while the SoC appears to be supported, I don't know how the display is connected. Some other SoCs (e.g. the chip used in the PineNote) have dedicated EPD control chips for e-paper displays, which are not supported in mainline (there was an attempt to add DRM helpers for EPD chips in general, but it never got followed up on past its initial submission in 2022). TODO - How do the various kobo e-readers handle this? Don't they run mainline?
- There is no proper codename for this device, it seems; Android reports the hardware field as "BOOX", and the DTB compatibles appear to be taken from a dev board, "bengal-idp", with "BOOX" added at the end (TODO verify with a dumped DTB instead of reading contents of
/proc/cmdline
- The bootloader is likely unlocked, like other BOOX devices;
adb reboot edl
should reboot to EDL,adb reboot fastboot
should reboot to Fastboot.