Ok, the problem is an issue of Samsung. It is solved here: https://groups.google.com/forum/#!topic/android-contrib/C7qbnnAGzsk
El martes, 17 de enero de 2017, 14:42:44 (UTC+1), Jose Riballo escribió: > > I don´t know if you still have that problem. This exception happens when > your ComponentName is not correct. > I've manage to do this with: > > ComponentName cName = new ComponentName(mContext.getPackageName(), > MyConnectionService.class.getName()); > > This solves that error, however I can't enable my PhoneAccount. I run > startActivity(new Intent(TelecomManager.ACTION_CHANGE_PHONE_ACCOUNTS)); > but my phoneAccount does not appear anywhere. > > Someone could do this? > Thank you all. > > > El miércoles, 9 de noviembre de 2016, 15:45:16 (UTC+1), Rasmus Höglund > escribió: >> >> I'm also trying this, but whenever I try to do >> telecomManager.registerPhoneAccount() I get the exception: >> >> Package [se.example.myapplication] does not belong to 10145. >> >> I have declared the service in AndroidManifest.xml exactly as above. Is >> there something else I'm missing? >> >> I see that BIND_TELECOM_CONNECTION_SERVICE, has protection level: >> signature|privilege: >> >> >> https://developer.android.com/reference/android/Manifest.permission.html#BIND_TELECOM_CONNECTION_SERVICE >> >> could this have something to do with the SecurityException I'm getting? >> > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/android-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/android-developers/20695e83-ebd8-4e4f-b366-0d943d5a121c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
