Jump to content

Samsung Galaxy Core Prime VE LTE (samsung-coreprimevelte)

From postmarketOS Wiki
Revision as of 13:29, 16 November 2021 by StandaSK (talk | contribs) (The port is aarch64, not armv7)
Note This is one specific Galaxy Core Prime hardware revision. For an overview, see Samsung Galaxy Core Prime
Samsung Galaxy Core Prime VE LTE
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 aarch64
Software
Original software Android 5.1.1 with Linux kernel 3.14
postmarketOS
Category testing
Pre-built images no
postmarketOS kernel 3.14.27
Features
Flashing
Broken
USB Networking
Works
Internal storage
No data
SD card
No data
Battery
No data
Screen
Works
Touchscreen
Works
Multimedia
3D Acceleration
No data
Audio
No data
Camera
No data
Camera Flash
No data
Connectivity
WiFi
Broken
Bluetooth
No data
GPS
No data
NFC
No data
Modem
Calls
No data
SMS
No data
Mobile data
No data
Miscellaneous
FDE
No data
USB OTG
No data
HDMI/DP
No data
Sensors
Accelerometer
No data
Magnetometer
No data
Ambient Light
No data
Proximity
No data
Hall Effect
No data
Haptics
No data
Barometer
No data


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.

See also