Samsung Galaxy Core Prime VE LTE (samsung-coreprimevelte)
USB Networking |
Works |
---|---|
Flashing |
Broken |
Touchscreen |
Works |
Display |
Works |
WiFi |
Broken |
Xwayland | |
FDE | |
Mainline | |
Battery | |
3D Acceleration | |
Accelerometer | |
Audio | |
Bluetooth | |
Camera | |
GPS | |
Mobile data | |
SMS | |
Calls | |
USB OTG | |
Users owning this device
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.
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.