IMEI2 becomes the default IMEI with an eSIM.

Forum|Forum|1 month ago
January 13, 2026
3 replies
25 views

Hello,

On our Ivanti Neurons MDM, we use this API to retrieve IMEIs:

getImei() in TelephonyManager is equivalent to:
getImei(getDefaultSim());
So when the only sim is inserted in the second slot:
getImei() is the same as getImei(1) causing duplication in the report.

Ref:
https://android.googlesource.com/platform/frameworks/base/+/b6587ea/telephony/java/android/telephony/TelephonyManager.java#843

The API used to retrieve IMEIs seems to target getImei(getDefaultSim()), which causes problems with eSIMs that use IMEI2.
It therefore retrieves IMEI2 as the default IMEI, which can cause problems with registration consoles such as ZTE, where only IMEI1 is entered.

Is there a way to correct this to avoid IMEI swapping?

Regards.

M

Moombas

Level 4.4: KitKat

Maybe this is default behavior by Android (and in my opinion an issue) as we see the same when the device has an IMEI, it's not recognized as an eSIM by the MDM but as a normal SIM with the IMEI2.

For me it looks like an Android internal issue.

M

Moombas

Level 4.4: KitKat

Need to correct my first paragraph:

Maybe this is default behavior by Android (and in my opinion an issue) as we see the same when the device has an eSIM, it's not recognized as an eSIM by the MDM but as a normal SIM with the IMEI2.