Description
After updating both Nothing Phone (2) and Nothing Phone (3a) to Android 16 with Nothing OS, Mobile ID (SIM-based electronic signature) has completely stopped working on both devices.
This functionality was working correctly before the update. The issue appeared immediately after upgrading to Android 16.
Mobile ID is a critical authentication and signing method used for:
banking
government services
legally binding electronic signatures
At the moment, it is impossible to use Mobile ID on these devices, which makes them unsuitable for everyday use in regions where Mobile ID is widely used.
Affected devices
Nothing Phone (2)
Nothing Phone (3a)
Affected OS version
Android 16 (Nothing OS, latest available update)
Mobile operators tested
Telia
Bitė
Tele2
(All show the same issue)
Expected behavior
Mobile ID should be detected by the system and work normally when requested by apps or web services (SIM Secure Element access).
Actual behavior
Mobile ID requests fail. The SIM-based signing process does not start or is rejected by the system. The feature is effectively unusable.
Additional notes
The SIM cards work correctly in other phones (older Android versions).
The same SIM cards worked on these Nothing devices before the Android 16 update.
This strongly suggests a regression related to:
SIM access permissions
Secure Element handling
modem / radio firmware changes
or Android 16 API changes not yet properly supported
At the moment, the only workaround is downgrading to an older OS version, which is not an acceptable long-term solution.
Request
Please investigate this issue and provide:
a fix in the next update or
official guidance on when Mobile ID support will be restored on Android 16 for Nothing devices.
This is a blocking issue for users in countries where Mobile ID is a standard authentication method.
Description
After updating both Nothing Phone (2) and Nothing Phone (3a) to Android 16 with Nothing OS, Mobile ID (SIM-based electronic signature) has completely stopped working on both devices.
This functionality was working correctly before the update. The issue appeared immediately after upgrading to Android 16.
Mobile ID is a critical authentication and signing method used for:
banking
government services
legally binding electronic signatures
At the moment, it is impossible to use Mobile ID on these devices, which makes them unsuitable for everyday use in regions where Mobile ID is widely used.
Affected devices
Nothing Phone (2)
Nothing Phone (3a)
Affected OS version
Android 16 (Nothing OS, latest available update)
Mobile operators tested
Telia
Bitė
Tele2
(All show the same issue)
Expected behavior
Mobile ID should be detected by the system and work normally when requested by apps or web services (SIM Secure Element access).
Actual behavior
Mobile ID requests fail. The SIM-based signing process does not start or is rejected by the system. The feature is effectively unusable.
Additional notes
The SIM cards work correctly in other phones (older Android versions).
The same SIM cards worked on these Nothing devices before the Android 16 update.
This strongly suggests a regression related to:
SIM access permissions
Secure Element handling
modem / radio firmware changes
or Android 16 API changes not yet properly supported
At the moment, the only workaround is downgrading to an older OS version, which is not an acceptable long-term solution.
Request
Please investigate this issue and provide:
a fix in the next update or
official guidance on when Mobile ID support will be restored on Android 16 for Nothing devices.
This is a blocking issue for users in countries where Mobile ID is a standard authentication method.