Jump to content

Samsung Galaxy Core Prime VE LTE (samsung-coreprimevelte)

From postmarketOS Wiki
Revision as of 19:11, 20 May 2022 by LegoLivesMatter (talk | contribs) (Device does not boot at the moment)
Note This is one specific Galaxy Core Prime hardware revision. For an overview, see Samsung Galaxy Core Prime
This device is marked as not booting.
Samsung Galaxy Core Prime VE LTE
Manufacturer Samsung
Name Galaxy Core Prime VE LTE
Codename samsung-coreprimevelte
Released 2014
Hardware
Chipset Marvell PXA1908
CPU Quad-core 1.2 GHz Cortex-A53
GPU Vivante GC7000UL
Display 480x800
Storage 8 GB
Memory 1 GB
Architecture aarch64
Software
Original software Android 5.1.1 on Linux 3.14.27
postmarketOS
Category testing
Pre-built images no
postmarketOS kernel 3.14.27


Users owning this device


Mainline

According to Documentation/arm/marvell.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.

CONFIG_OPTIMIZE_FOR_SIZE should be set, or the boot image will be too big for the partition.

The concatenated dtb blob should be generated with https://github.com/osm0sis/pxa-mkbootimg, because the G361F's chipset is a bit different.

Booting

The SM-G361F uses the Marvell PXA1908 chipset, which is, while really similar to Qualcomm ones, has some differences. It has a bit different way to specify the revision in DTB files, therefore the dtbTool from https://github.com/osm0sis/pxa-mkbootimg should be used. This is the same with mkbootimg. Additionally, SEANDROIDENFORCE should be appended to the bootimage, in order to silence the "KERNEL IS NOT SEANDROID ENFORCING" warning.

The postmarketOS kernel does not boot on the device at the moment. It was assumed that this was because the kernel did not like the latest GCC, but attempting to compile with GCC 4 proved that this was not the case. This issue has yet to be properly investigated.

See also