On v3.4 the same behaviour 
(all incoming calls are unknown) I did factory reset but it stays on v3.4 - I cannot set it to version of Murena which was originally pre-installed when I received this phone. Any idea what to do with it ?
It’s a common misconception because of the name, but an Android “factory reset” doesn’t touch the installed OS at all, it only deletes user data, Apps installed by the user and their data, some settings … and then restarts with the initial user setup.
Simply offering risk-unaware users to go back to the originally preinstalled version would be a security risk, the higher the further back in time it would go.
(I know Windows Phone could do this, but that was ages ago and nobody knows whether Microsoft would have kept it this way.)
If you want to go back to an older OS version you will have to install the older version from scratch, wiping your data.
Older versions are still available for manual install here … https://images.ecloud.global/official/FP4/ … instructions are here … https://doc.e.foundation/devices/FP4/install.
Be safe with a backup of everything important from the phone to somewhere else.
Did you have a look at the search whether there’s something useful perhaps? … Search results for 'incoming calls unknown order:latest' - /e/OS community
I have the same problem.
Does the problem persist if you update to the current version 3.4?
After a week on 3.4, I am happy to report that battery life is now better than ever before!
Yes it did.
I updated a few weeks ago.
1 Like
Vendor Name: Motorola
Device name: Edge 30
Device CodeName: dubai
Version of /e/OS or Stock which existed previously: 3.2-a14-20251026540137-community-dubai
Is the device Rooted / Not rooted: Not rooted
After OTA update to 3.4 (android 14) device freeze during log screen.
Then I have also tried an update to 3.3 (Android 15) including recovery 3.3 (A15) manually, but then data were corrupt:
Then I would suggest posting in Feedback for v3.4 .
Android rollback protection will prevent you from doing this without a factory reset for security reasons, as 3.3 is on an earlier security patch level than 3.4.
OK, but if I try a rollback from 3.4 (A14) to 3.3 (A15), the result of the rollback protection are corrupt data?
Strange…
Is that even on community and with unlocked bootloader?
YES to both questions
Unknown caller issue started with my FP3+ after upgrading to v3.3. Disabling VoLTE brings them back and N26 now works again. Can’t have it all I guess
model : Teracube 2e "emerald”
Vendor : Murena 2023-06
serial number : 202112T2*****
build SQ3A.220705.004
pb : –> Not OTA for 3.4
