Samsung Galaxy Core Prime VE LTE (samsung-coreprimevelte)
This is one specific Galaxy Core Prime hardware revision. For an overview, see Samsung Galaxy Core Prime |
Manufacturer | Samsung |
---|---|
Name | Galaxy Core Prime VE LTE |
Codename | samsung-coreprimevelte, SM-G361F |
Hardware | |
Chipset | Marvell PXA1908 |
CPU | Quad-core 1.2GHz Cortex-A53 |
GPU | Vivante GC7000UL |
Display | 480x800px |
Memory | 902MB |
Architecture | armv7 |
Software | |
Original software | Android 5.1.1 with Linux kernel 3.14 |
postmarketOS | |
Category | testing |
Pre-built images | no |
Users owning this device
- AAT596 (Notes: (1+) Original Android, trying to build a custom ROM for them because there's none as of now)
- CoderCharmander
- LegoLivesMatter (Notes: Currently mainlining)
- RobusTetus (Notes: Stuck in a odin mode, cannot boot)
- StandaSK
- Stupidenbyace
Mainline
According to Documentation/arm/marvel.rst
the PXA1908 chipset should be supported, but it is unknown whether it's actually supported.
Downstream
It's possible to compile the Samsung-provided downstream kernel with some config changes (arch/arm64/configs/pxa1908_coreprimevelte_eur_defconfig
should be used as a defconfig):
CONFIG_CRYPTO_XTS
should be set, and CONFIG_ANDROID_PARANOID_NETWORK
should be unset. These are required by postmarketOS. Additionally, CONFIG_EXTCON_SAMSUNG
should be set, to compile a required object file.
However, the compilation fails at the dtb generation phase.
Booting
The G361F's bootimage is a bit weird - it uses 2048 as the page size, but the page size field contains 0x03000000 (50331648), presumably as some kind of magic value. The device refuses to boot with a red KERNEL IS NOT SEANDROID ENFORCING
message in the top left corner if the image is not set up this way.