System uses the same mechanism under the hood. If the app has their own Mobile Operator, it can be more smooth to work with eSIM - without QR scanning at all
I guess Google introduced it for security reasons. You still can install eSIM within your own android or in operator’s app by just giving permissions. Unfortunately service cannot decided by its own so you are as a user staying in safety while using random app.
Hmm I don't really want apps to be able to be messing around with my esims. Just give me a QR to scan. Simple enough.
System uses the same mechanism under the hood. If the app has their own Mobile Operator, it can be more smooth to work with eSIM - without QR scanning at all
The operator decides which apps can interact with a given esim.
Wasn't this supposed to be a general purpose computer? Why can a service decide which apps I can use to access which features of my own device?
I guess Google introduced it for security reasons. You still can install eSIM within your own android or in operator’s app by just giving permissions. Unfortunately service cannot decided by its own so you are as a user staying in safety while using random app.
Does this mean that malware can redirect all my calls by installing an esim with no user interaction?
>The downloadSubscription method requires android.Manifest.permission.WRITE_EMBEDDED_SUBSCRIPTIONS
It's not mentioned but that permission is only available to system apps.
[flagged]