[android-developers] Re: How to replace telecom's native ConnectionService?

2017-02-16 Thread spartygw
Thanks for the Samsung tip. I am now able to display the "Calling accounts" screen but there are no options to select. I've registered a "foo" PhoneAccountHandle with PhoneAccount.CAPABILITY_CALL_PROVIDER and PhoneAccount.CAPABILITY_CONNECTION_MANAGER but I still don't see it as an option.

[android-developers] Re: How to replace telecom's native ConnectionService?

2017-01-18 Thread Jose Riballo
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

[android-developers] Re: How to replace telecom's native ConnectionService?

2017-01-17 Thread Jose Riballo
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

[android-developers] Re: How to replace telecom's native ConnectionService?

2016-11-17 Thread Garett Beukeboom
Pretty sure I copied that over from the CTS test my project is based, but here is a link that explains the permission a bit: https://android.googlesource.com/platform/frameworks/base/+/2ef87ee%5E!/ -- You received this message because you are subscribed to the Google Groups "Android

[android-developers] Re: How to replace telecom's native ConnectionService?

2016-11-10 Thread Rasmus Höglund
I didn't have the permission 'android.permission.REGISTER_CALL_PROVIDER'*. *But after adding this i still have the same error. I can't find the REGISTER_CALL_PROVIDER in Manifest.permission ( https://developer.android.com/reference/android/Manifest.permission.html). Where can I find more info

[android-developers] Re: How to replace telecom's native ConnectionService?

2016-11-09 Thread Garett Beukeboom
Not sure what's going on exactly, but if your service has the BIND_TELECOM_CONNECTION_SERVICE permission specified it should be fine, you're not using the permission just preventing an entity without that permission from binding to yours. What permissions do you have in your manifest? Mine has

[android-developers] Re: How to replace telecom's native ConnectionService?

2016-11-09 Thread Rasmus Höglund
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

[android-developers] Re: How to replace telecom's native ConnectionService?

2016-09-15 Thread Garett Beukeboom
Hey Jocke, I hit this issue myself, the phone account will be registered to the device but disabled unless manually enabled by the user (haven't found a way to enable myself yet). To enable go into the phone settings (using the Google Phone app go into Settings -> Calls -> Calling Accounts ->