Does anyone want to try A14 versions?
A14 was what we’ve been waiting for in order to get the SMS bug fix sorted out on the NP2, right?!
Does anyone want to try A14 versions?
A14 was what we’ve been waiting for in order to get the SMS bug fix sorted out on the NP2, right?!
I think so, and some other bugs
Update for /e/OS-T 2.2:
e-2.2-t-20240723-UNOFFICIAL-Pong.zip
https://sourceforge.net/projects/eosbuildsronnz98/files/OtherSmartphones/e-2.2-t-20240723-UNOFFICIAL-Pong.zip/download
I’ve finally freed up my NP2 and can flash it with /e/OS again! Is this the hopefully-fixing-the-SMS-bug A14 build? Forgive me; I still get my version schemes confused…
Also…is it an easy thing to integrate this?
Sources were not changed, so I suspect all issues still exists.
But you can use iode or LOS version for A14 I build and upload here:
https://sourceforge.net/projects/eosbuildsronnz98/files/OtherCustomROMS/
When A14 for /e/OS is available I will port Pong too
I tried A14 build now, but got this errror:
[“arm64”] unknown cpu variant “cortex-a510”, support variants: [“cortex-a53” “cortex-a55” “cortex-a72” “cortex-a73” “cortex-a75” “cortex-a76” “kryo” “kryo385” “exynos-m1” “exynos-m2”]
My original post here was probably the least helpful thing I’ve written on these forums =).
Relevant sections from asking ChatGPT:
Ensure that the device’s configuration files (like
device.mk
,BoardConfig.mk
, etc.) are properly set up to specify the CPU variant. If these files explicitly mention supported CPU variants, you’ll need to add or modify them to include Cortex-A510.
Modify Configuration: In your device configuration files, look for lines that define
TARGET_ARCH_VARIANT
or similar, and addcortex-a510
to the list if needed.
This might be the second-dumbest post I’ve ever made here, @ronnz98 , so please forgive me for being both ambitious and unhelpful…BUT…is it possible that it’s something as nominal as specifying ‘cortex-a510’ in the device.mk file manually?
It shows more that ChatGPT is really dumb
I device cortex-a510
is defined, but the android environment seems not to know this cpu variant yet? I could use kryo385 successfully instead