Unresolved Issues with the Redmi Note 10 Pro running /e/OS

Device: Xiaomi Redmi Note 10 Pro (M2101K6G) "Sweet"

Current /e/OS version: 3.1.4 community build, Android 14 (upgraded from 3.1.1)

Below is a summary of the problems I have reported in various threads on community.e.foundation forum, but in most cases I either received no answer, or the replies did not resolve the issue.

1. Find‑My‑Device does not work correctly

What happens:

• In version 3.1.1 the Find My Device app returns the code sent from the other device instead of the location coordinates, but nothing else happens.
• After the OTA update to 3.1.4 the situation got worse: the app no longer sends the code back to the sender’s device at all. Instead, the code arrives as a plain SMS, the phone plays a notification sound when the SMS is received, and the text “Find my Device by SMS Tracking location in background” appears on the screen.

Location services:

Location itself works fine – apps such as Maps and BlissWeather can retrieve the device’s position without any problem.

2. Only one of the four rear cameras is functional

Hardware overview:

Rear camera specs:
Primary (wide) 108 MP, f/1.9, 26 mm, 1/1.52″ sensor, 0.7 µm pixel size, PDAF
Ultra‑wide 8 MP, f/2.2, 118°, 1/4.0″ sensor, 1.12 µm
Macro 5 MP, f/2.4, autofocus
Depth 2 MP, f/2.4
Selfie camera: 16 MP, f/2.5, 1/3.06″ sensor, 1.0 µm

Observed behavior:

The camera app only detects two cameras: the selfie camera and one rear camera (most likely the primary wide‑angle lens). Moreover, the primary rear camera produces only 12-MP images instead of the expected 108-MP resolution, and the ultrawide mode is missing, which would be extremely important.

If i run „adb shell dumpsys media.camera” i see next:

== Service global info: ==
Number of camera devices: 9
Number of normal camera devices: 5
Number of public camera devices visible to API1: 5
Device 0 maps to “0”
Device 1 maps to “1”
Device 2 maps to “3”
Device 3 maps to “7”
Device 4 maps to “8”
Active Camera Clients:

Allowed user IDs: 0

However in the OpenCamera settings, I can only see two cameras even though the Camera2 API is enabled:

• Version: 1.53.1
• Code: 90
• Package: foundation.e.camera
• Android API level: 34
• Manufacturer: Xiaomi
• Model: M2101K6G
• Display: 1080 × 2160
• Current camera ID: 0
• Number of cameras reported: 2
• Multi‑camera support: false
• Camera API: Camera2 (Android L)
• Orientation: 90°
• Photo mode: Normal
• Zoom range: 1.0 – 10.0

3. Call‑waiting cannot be disabled

Situation:

Call‑waiting is automatically enabled on the device. When I try to turn it off via Settings → Call settings, the toggle is greyed out (inactive). Visually the feature appears to be off, but the switch does not respond; I cannot enable or disable it.

USSD attempts:

Using the USSD code #43 (moved)# shows a notification that call‑waiting has been turned off, but the setting is instantly re‑enabled. When I place the same SIM card in another phone, I can freely toggle call‑waiting in the settings or with the USSD codes *43# (enable) and #43 (moved)# (disable). On the Redmi Note 10 Pro running /e/OS, call‑waiting remains permanently on, and I have not found any method to turn it off.

Request for Assistance

I would greatly appreciate any feedback on these issues:

• Is there a known workaround for the Find My Device behavior in the current builds?
• Can the missing rear cameras be made visible to the system, or is there a firmware limitation that needs to be addressed?
• How can call‑waiting be properly disabled on /e/OS for this device?

If any of these problems are not solvable with the current software, please let me know so we can set realistic expectations for the next OTA update. Thank you!

UPDATE:
It appears that call waiting stays continuously active only when VoLTE is enabled. When I turn off VoLTE, I can choose whether to enable or disable call waiting. Since I need VoLTE but don’t want call waiting, I’ll contact my mobile carrier to find a solution.

However, the issues with the FMD and the camera persist, and, according to comments on the community.e.foundation forum, other users are experiencing the same problems.