riul88 / call-recorder-for-android

call-recorder-for-android fork
158 stars 98 forks source link

does not record in android 6.0 (cm13) #36

Open monolithonadmin opened 8 years ago

monolithonadmin commented 8 years ago

It doesn't work under android 6.0 I tested on lg and htc mobiles the latest version of this app. It worked well on cm 12.1 (android 5.1). Please upgrade the code.

frode commented 8 years ago

Same problem with Xperia Z5 and Android 6.0 that was upgraded on my device yesterday.

bestouff commented 8 years ago

/me too Here's an excerpt from the log, there seem to be a problem with perms. If it's not that, I have the full logcat available on request.

03-11 08:40:33.688   979   979 I Telecom : Event: Call 19: SET_RINGING, ringing set explicitly
03-11 08:40:33.690   979   979 I Telecom : PhoneStateBroadcaster: Broadcasted state change: 1
03-11 08:40:33.690   979   993 W BroadcastQueue: Permission Denial: receiving Intent { act=android.intent.action.PHONE_STATE flg=0x10 (has extras) } to Proce
ssRecord{c1adb3b 2268:com.android.systemui/u0a18} (pid=2268, uid=10018) requires android.permission.READ_PHONE_STATE due to sender android (uid 1000)
03-11 08:40:33.691   979   993 W BroadcastQueue: Permission Denial: receiving Intent { act=android.intent.action.PHONE_STATE flg=0x10 (has extras) } to Proce
ssRecord{c1adb3b 2268:com.android.systemui/u0a18} (pid=2268, uid=10018) requires android.permission.READ_PHONE_STATE due to sender android (uid 1000)
03-11 08:40:33.691   979   993 W BroadcastQueue: Permission Denial: receiving Intent { act=android.intent.action.PHONE_STATE flg=0x10 (has extras) } to com.callrecorder.android/.MyPhoneReceiver requires android.permission.READ_PRIVILEGED_PHONE_STATE due to sender android (uid 1000)
03-11 08:40:33.691   979   993 W BroadcastQueue: Permission Denial: receiving Intent { act=android.intent.action.PHONE_STATE flg=0x10 (has extras) } to com.google.android.talk/com.google.android.apps.hangouts.telephony.TelePhoneStateReceiver requires android.permission.READ_PRIVILEGED_PHONE_STATE due to sender android (uid 1000)
03-11 08:40:33.692   979   979 I Telecom : InCallController: Found default-dialer's In-Call UI: ComponentInfo{com.android.dialer/com.android.incallui.InCallServiceImpl}
03-11 08:40:33.693   979   979 I Telecom : InCallController: Attempting to bind to [def-dialer] InCall ComponentInfo{com.android.dialer/com.android.incallui.InCallServiceImpl}, with Intent { act=android.telecom.InCallService cmp=com.android.dialer/com.android.incallui.InCallServiceImpl }
zamber commented 8 years ago

I started fooling around a bit with this today. Hopefully I'll be able to fix this through the weekend. Yesterday I upgraded to MM and was massively disappointed that call recording broke.

zamber commented 8 years ago

BTW @riul88, are you still alive and maintaining this repo?

licaon-kter commented 8 years ago

@zamber How do you build this? Android Studio 2.1 imports it somewhat, but then fails to compile.

zamber commented 8 years ago

@licaon-kter, I haven't taken it up after that but I tried to build it now after importing and you'll have to install the target platform (android-8 in this case).

After that the APK builds nicely :).

2016-05-09-005444_1366x768_scrot

licaon-kter commented 8 years ago

I did that, yet still fails with 28 errors: https://gist.github.com/licaon-kter/937dad0a943b73781dde3422ae2f485b

That's from straight import, no messing with Java version, minSdk, targetSdk or anything else.

zamber commented 8 years ago

Tried this on my work machine. Had similar issues. Gradle resync fixed it https://stackoverflow.com/questions/19932793/syncing-android-studio-project-with-gradle-files :).

licaon-kter commented 8 years ago

IIRC I saw AS complain and I kinda do that anyway, but alas, I'll retry, In the mean time, can you share an .apk build?

zamber commented 8 years ago

Replicated it. I was building the project, not the APK so it worked. When I tried to build the APK it generated the same errors.

licaon-kter commented 8 years ago

Ok. BTW, one does not get notified on gist replies so I saw your answer later.

steelowheel commented 8 years ago

Stopped working on my Oneplus One after updating to MM (cm13). Strangely the last modified date of the folder recordedCalls changes every time I make or receive a call.

licaon-kter commented 8 years ago

@riul88 Any chance of an update?

jaimet commented 8 years ago

I'm just adding this comment in here to let you know that call recording on CM13 is possible. I've just spent a couple of hours trying both this app and pyler's EnableCMCallRecording Xposed module, and while I could NOT get this app to work, I did eventually succeed in getting pyler's module to work perfectly on my CM13 i9300 (13.0-20160601-NIGHTLY-i9300). I'm letting you know in case the source from pyler's module/the CM codebase helps to get this app fixed (I'd prefer to have auto recording of all calls, which pyler's module does NOT offer). HTH.