This guide refers to Alex' (skvalex) Call Recorder but it can be applied to, and it should be working with most other available call recorders. I have the Canadian SGH-I337M, stock, odex, rooted but in theory this solution should be working on all SGH-I337(M).
IT DOES NOT WORK WITH AOSP/AOKP BASED ROM's (INCLUDING CM) - IT WILL CAUSE SYSTEM CRASHES!!!
MORE DETAILS ON POST# 3
I have been using this Call Recorder on all my previous Samsung phones and personally, I consider it to be the most reliable, capable and best supported call recorder out there, however as of today, Sep.15.2013, although all the North American versions of the S4 are officially supported, the recorder still yields blank records (0m0s) when used out of the box. The WORKING solution is presented bellow.
There is a trial version but if you like the recorder and need it, I would highly recommend buying it - it's worth every penny.
Method 1
1. Install Call Recorder (or your preferred one).
2. Download the attached flashable zip - it contains the 2 modified files from "system/etc/snd_soc_msm".
3. Flash the zip from recovery. (Optionally, you can backup the original files - before flashing the zip - as indicated in method 2 bellow)
4. Enjoy
Method 2 (manually creating a backup of the original files)
1. Install Call Recorder (or your preferred one).
2. Download the attached flashable zip - it contains the 2 modified files from "system/etc/snd_soc_msm".
3. Extract/save the 2 files in the "system/etc/snd_soc_msm" folder from the zip.
4. Go to the same directory on the phone (system/etc/snd_soc_msm) and make a backup of the 2 original files by adding ".bak" at the end (you'll need root).
5. Copy the 2 files extracted from the zip (in step #3), over here.
6. Set the permissions to 644 (rw-r--r--).
6. Reboot and enjoy.
The recommended settings for the Call Recorder:
- Device: Samsung (your version)
- Recording method: Standard API
- Call recording format: AMR
- Audio source: Voice call uplink + downlink
...others as desired.
Let me know how this solution works for you!
Attached are some generic Call Recorder png icons I have made. Feel free to use/share them - but have the decency to give me the due credit.
Thank you for this. It seems to work very well. I am on an AT&T SGH-I337 S4. One bug I have noticed is under the "Audio Player" in settings. The option to "use proximity Sensor" is very buggy. Basically this setting switches the screen off while listening to recorded calls while listening through the phone's regular speaker (not loud speaker). It turns the screen off fine, but sometimes doesn't turn it back on when the phone is moved away from my face (sometimes it does?). When it doesn't come back on, I have to hit the power button (just like putting the phone to sleep) and then hit it again to turn the phone back onto the lock screen (swipe to unlock it) and it turns back on just fine. The funny thing is, that the recorded message keeps playing throughout the entire process? Even when the screen turns back on like it is supposed to, the touch keys don't light back up with the screen. In order to get them back on I have to put the phone to sleep again and turn it back on. I use the proximity sensor with my phone calls and it works fine so it has to be a bug with the audio player or a bug with the call recorder App. I realize Skvalex is the Dev for the actual Call Recorder APK but I thought I would mention this here just to let you and others know about it and, I was wondering if you could check your phone to see if it has the same issue? Other than that, it all seems to work very nice.
I was also wondering if you know if the "Volume Boost Mods" listed in Jrkruse' thread here http://forum.xda-developers.com/showthread.php?t=2352797 will work with your "modded" call recorder?
And, if Skvalex updates the call recorder app and I choose to update it from the play store, will I need to reflash your "Dependency" zip or will updating the call recorder apk not effect those files?
Thank you for your hard work.
scott14719 said:
Thank you for this. It seems to work very well. I am on an AT&T SGH-I337 S4. One bug I have noticed is under the "Audio Player" in settings. The option to "use proximity Sensor" is very buggy. Basically this setting switches the screen off while listening to recorded calls while listening through the phone's regular speaker (not loud speaker). It turns the screen off fine, but sometimes doesn't turn it back on when the phone is moved away from my face (sometimes it does?). When it doesn't come back on, I have to hit the power button (just like putting the phone to sleep) and then hit it again to turn the phone back onto the lock screen (swipe to unlock it) and it turns back on just fine. The funny thing is, that the message keeps playing throughout the entire process? Even when the screen turns back on like it is supposed to, the touch keys don't like back up with the screen. In order to get them back on I have to put the phone to sleep again and turn it back on. I use the proximity sensor with my phone calls and it works fine so it has to be a bug with the audio player or a bug with the call recorder App. I realize Skalex is the Dev for the actual Call Recorder APK but I thought I would mention this here just to let you and others know about it and, I was wondering if you could check your phone to see if it has the same issue? Other than that, it all seems to work very nice.
I was also wondering if you know if the "Volume Boost Mods" listed in Jrkruse' thread here http://forum.xda-developers.com/showthread.php?t=2352797 will work with your "modded" call recorder?
Thank you for your hard work.
Click to expand...
Click to collapse
You're welcome! Yes, I have also noticed the proximity sensor/screen bug - but for the time being we'll have to live with it. As a temporary work around you can disable this feature and simply toggle manually between loudspeaker and internal speaker from the dedicated button in the upper right corner - no big deal and it does the same thing.
As far as the volume boost, it should be working, I don't see any reason why it wouldn't - however, there are a few things to keep in mind before doing any further changes: originally, the Call Recorder (or any other call recorder for that matter) wouldn't be working (at all) on any N.A. S4's for two reasons: 1) missing audio media mixer, so I have added the missing mixer and 2) the voice call recording audio levels were set so high (very sensitive) that most every recording (anything louder than whispering) would be yielding distorted, literally unusable audio outputs. As such, I have modified (brought down) ONLY the call recording levels (call mic) and I didn't touch any other audio outputs/inputs/mixers (loudspeaker, internal speaker, wired headphones, BT headphones/accessories, voice recorder, VoIP, VoLTE +++ others) because doing so may have a negative impact on other applications and/or hardware not related to voice call recording. Because of the implications, I preferred to stay away from playing around with those - especially since there are tons of variables and not much documentations about all that.
Also keep in mind that while there are many versions of these 2 files out there, in order to insure/increase the compatibility, I have used & modified the ones that came with the original stock ROM. I have also tested the Call Recorder with the latest I337MVLUAMG1 firmware and everything seems to working fine.
Now, the volume booster that you are referring to, alters the exact same files in the sense that it increases (to various degrees - hence, boosting) some audio output levels while leaving the call recording audio levels untouched - it's entirely up to you as a user whether you like it or not and whether you see/perceive any negative impacts (sound distortions). If you decide to try a volume booster, take it for a spin, test it extensively, not just the call recorder, but most other apps that use sound and then you'll be the best judge whether that mod works for you or not. Most likely you won't hurt anything. Careful when you play with the 2 files - setting wrong permissions (or no permissions at all) will result in a boot loop.
Thank you. The phone speaker is plenty loud already, it's just the loud speaker playback of recorded messages that seems a little low...but still OK. Knowing the issues you have resolved and the reasons your resolved them, I think I'll just leave everything the way it is for now (not installing any volume mods). And, so far, further testing I have done hasn't revealed any other problems. I can keep the proximity sensor turned off, I just have to remember not to press the phone all of the way to my face when listening to the recorded messages or switching to loud speaker for playback, and again, that's not a huge issue. Again, thanks.
I installed this, and for the most part it seems to be working.
I installed this, and for the most part it seems to be working.
At first, the incoming voice was really distorted, but I applied the volume mod and that cleared that up.
It only seems to record on incoming calls though. If I call out, there is an entry in the log but it shows 0:00 for the recording time.
So, for soem reason this seems to only work on incoming calls, not outgoing.
I have the settings enabled for record all......
Anyone have any ideas on how to fix this?
It's working fine for me here it records on incoming and outgoing calls
thatsupnow said:
It's working fine for me here it records on incoming and outgoing calls
Click to expand...
Click to collapse
Working good here still (Except for the previously mentioned items). I had one instance of the contacts (favorites) going kind of strange, but a reboot fixed it...and it only happened once. The recording starts automatically for me on incoming calls, but I have to manually start it (press the record button) to record outgoing calls. I'm pretty sure it's something in the settings, but it's not a big deal so I haven't tried to change it.
Thanks for this!
billinaz said:
I installed this, and for the most part it seems to be working.
I installed this, and for the most part it seems to be working.
At first, the incoming voice was really distorted, but I applied the volume mod and that cleared that up.
It only seems to record on incoming calls though. If I call out, there is an entry in the log but it shows 0:00 for the recording time.
So, for soem reason this seems to only work on incoming calls, not outgoing.
I have the settings enabled for record all......
Anyone have any ideas on how to fix this?
Click to expand...
Click to collapse
As always...read, read and read!
1. As I have previously explained, installing any volume mod by jrkruse, REPLACES my files - as such you have NOT used THIS mod
2. If you have call records with 0.00s for the recording time, clearly you are not using neither my mod nor jrkruse's volume boost. Most likely, somehow, you are using the original UNMODIFIED files.
3. At this time the ONLY audio source that works for both incoming/outgoing calls is "Voice call uplink + downlink" - as I have suggested
saywhatt said:
Thanks for this!
Click to expand...
Click to collapse
You're very welcome!
scott14719 said:
Working good here still (Except for the previously mentioned items). I had one instance of the contacts (favorites) going kind of strange, but a reboot fixed it...and it only happened once. The recording starts automatically for me on incoming calls, but I have to manually start it (press the record button) to record outgoing calls. I'm pretty sure it's something in the settings, but it's not a big deal so I haven't tried to change it.
Click to expand...
Click to collapse
Make sure that you have set it to automatically record all calls, otherwise...there may be a bug I have noticed in the Call Recorder software - related to our S4's. At least in my case, whenever the Call Recorder gets accessed/opened (settings or simply reviewing calls), the next incoming call won't start by itself. Any other subsequent calls, whether incoming or outgoing will be recorded without issues (until the Call Recorder gets accessed again)
I have emailed the dev. about this but...
nacos said:
Make sure that you have set it to automatically record all calls, otherwise...there may be a bug I have noticed in the Call Recorder software - related to our S4's. At least in my case, whenever the Call Recorder gets accessed/opened (settings or simply reviewing calls), the next incoming call won't start by itself. Any other subsequent calls, whether incoming or outgoing will be recorded without issues (until the Call Recorder gets accessed again)
I have emailed the dev. about this but...
Click to expand...
Click to collapse
I disabled the delay on outgoing calls and it now automatically records all incoming and outgoing. The strange thing was that I had the delay set to .01 and it should have automatically started recording after that short delay, however, I still had to hit the button to record before it would start at all. I guess it's just another bug. I would rather have it record all calls anyway because I tend to forget to manually start it on the calls I need to. It's easier just to delete the calls that didn't need recording from time to time.
Here is a question in general, when I newer version of the call recorder APK is released can we just install it from the play store (as usual) or do we need to reinstall the other modded files (from the OP) after updating the APK?
scott14719 said:
I disabled the delay on outgoing calls and it now automatically records all incoming and outgoing. The strange thing was that I had the delay set to .01 and it should have automatically started recording after that short delay, however, I still had to hit the button to record before it would start at all. I guess it's just another bug. I would rather have it record all calls anyway because I tend to forget to manually start it on the calls I need to. It's easier just to delete the calls that didn't need recording from time to time.
Here is a question in general, when I newer version of the call recorder APK is released can we just install it from the play store (as usual) or do we need to reinstall the other modded files (from the OP) after updating the APK?
Click to expand...
Click to collapse
The 2 modified files are located in "system/etc/snd_soc_msm" - in other words they are system files and most likely they will NOT be touched (modified by an installation), however future releases/versions may be accessing the system resources differently in order to (officially) resolve the current issues.
Are you using CM or an AOSP based ROM? I've seen this happening in CM, just wondering...
nacos said:
The 2 modified files are located in "system/etc/snd_soc_msm" - in other words they are system files and most likely they will NOT be touched (modified by an installation), however future releases/versions may be accessing the system resources differently in order to (officially) resolve the current issues.
Are you using CM or an AOSP based ROM? I've seen this happening in CM, just wondering...
Click to expand...
Click to collapse
Stock, Deodexed AMDL with P-Rom modifications (slightly modified framework). The P-Rom mods didn't effect any of the system sound files or the dialer.
Excuse me!!! Can i use this for SGH I747M?
Carlos6862 said:
Excuse me!!! Can i use this for SGH I747M?
Click to expand...
Click to collapse
.. you don't need to. The Canadian S3 is officially supported by the Call Recorder, so all you have to do is install it and set the proper settings.
Thanks for your help!!!
Galaxy S4 MF3
Can you pls let me know if it would work on galaxy S4 MF3 (AT&T).
Thanks!!
kkvo said:
Can you pls let me know if it would work on galaxy S4 MF3 (AT&T).
Thanks!!
Click to expand...
Click to collapse
Try and see for yourself...nothing will happen or get lost if you save all the originals. Just follow the instructions and let us know.:fingers-crossed:
nacos said:
Try and see for yourself...nothing will happen or get lost if you save all the originals. Just follow the instructions and let us know.:fingers-crossed:
Click to expand...
Click to collapse
Well Total Recall 2 worked for me.The app has an auto patch for S4 MF3,which makes it run without any problem.Well for anyone interested, i had had posted skvalex on his forum about any solution for MF3 and he send me the below link...
http://forum.xda-developers.com/show....php?t=2352797
Related
OUTDATED: Tunnel voice has been fixed in the latest CM7 and CM9 nightlies.
Hope we can find better fix to this in future.
Using the CM7 version with makelegs Kang.
Pushed with Root Explorer (I'm at work and don't have a cable to use ADB).
Phone kept FCing so I:
1. Rebooted
2. Fixed permissions with Root Explorer
3. Rebooted again to recovery and wiped cache and dalvik
Seems to be working so far. I will report back in a few days.
The CM7 version is not working.
I have received several calls and the caller says I sound like I'm in a tunnel. If I mute and then unmute after answering the call, the problem immediately clears up. This leads me to believe that the hacked phone is not properly muting and unmuting.
I will try to reproduce it and get a logcat.
Logcat coming soon...
neobuddy89 said:
Hope we can find better fix to this in future.
Click to expand...
Click to collapse
Me too bro... me too.
I think a commit from before, merging audio HAL fixes in, was supposed to fix it, but part of that got reverted because it broke some devices on some carriers.
Also, apparently, this problem happens on other devices as-well (I'm guessing just Aries devices)
creeve4 said:
Logcat coming soon...
Click to expand...
Click to collapse
If it doesn't have the mute/unmute fix, others will confirm and I'll clean compile a new one.
So everyone else, please post if this fixes your problem.
FaultException said:
If it doesn't have the mute/unmute fix, others will confirm and I'll clean compile a new one.
So everyone else, please post if this fixes your problem.
Click to expand...
Click to collapse
It doesn't seem to have the fix (or its not working) because if I manually mute then unmute after receiving a call the tunnel voice immediately goes away.
creeve4 said:
It doesn't seem to have the fix (or its not working) because if I manually mute then unmute after receiving a call the tunnel voice immediately goes away.
Click to expand...
Click to collapse
I'll clean compile CM7 with it and pull it and upload it tonight then.
Here are two logs. Both calls had the tunnel voice until I manually muted and unmuted.
http://db.tt/1Y4u2aN9
http://db.tt/hKCAeA20
Sorry they are so long. I started recording just before the call and ended recording after ending the call, but I wasn't sure what may be useful so I didn't filter anything out.
V2 is up (just a clean recompile), try that.
Is this useful for aokp if people face mute unmute issues
Sent from my SGH-T959 using xda premium
FaultException said:
V2 is up (just a clean recompile), try that.
Click to expand...
Click to collapse
I'll try it out and report back. Thanks again!
Here are my findings:
I am running CM7.2.0-RC1-vibrantmtd-KANG-signed.02282012-2202
Using the stock phone:
For every call (25 of 25) I receive from my mother, she said I sound like I'm far away and in a tunnel.
If I manually mute and unmute, the "tunnel" voice immediately goes away.
Using the hacked v2 phone:
5 of 8 calls received from my mother were clear with no tunnel voice
3 of 8 calls received from my mother had the tunnel voice, but after I manually muted and unmuted, the "tunnel" voice immediately went away.
It seems this hacked phone helps, but does not fully solve the problem.
I will continue to run it for several more days to gather some data from other callers. I use my mother as a base because most calls I receive from her have the tunnel voice bug.
creeve4 said:
Here are my findings:
I am running CM7.2.0-RC1-vibrantmtd-KANG-signed.02282012-2202
Using the stock phone:
For every call (25 of 25) I receive from my mother, she said I sound like I'm far away and in a tunnel.
If I manually mute and unmute, the "tunnel" voice immediately goes away.
Using the hacked v2 phone:
5 of 8 calls received from my mother were clear with no tunnel voice
3 of 8 calls received from my mother had the tunnel voice, but after I manually muted and unmuted, the "tunnel" voice immediately went away.
It seems this hacked phone helps, but does not fully solve the problem.
I will continue to run it for several more days to gather some data from other callers. I use my mother as a base because most calls I receive from her have the tunnel voice bug.
Click to expand...
Click to collapse
Hahaha. The fix is only in the CDMA portion of the handleCallKey function... (even in the original fix, so it wasn't just my fault! Even though I manually added the fix )
I'll recompile AGAIN with it also in GSM today and re-upload. Sorry 'bout that.
xriderx66 said:
Is this useful for aokp if people face mute unmute issues
Sent from my SGH-T959 using xda premium
Click to expand...
Click to collapse
The apk may not be, because it's based on CM9, but you can use the source of the fix, but you need to put it in the GSM section aswell as the original fix only has it in CDMA.
FaultException said:
Hahaha. The fix is only in the CDMA portion of the handleCallKey function... (even in the original fix, so it wasn't just my fault! Even though I manually added the fix )
I'll recompile AGAIN with it also in GSM today and re-upload. Sorry 'bout that.
Click to expand...
Click to collapse
That's pretty funny, a little frustrating for you probably, but funny.
Thanks for sticking with it and helping out!
creeve4 said:
That's pretty funny, a little frustrating for you probably, but funny.
Thanks for sticking with it and helping out!
Click to expand...
Click to collapse
New ones up, they're not clean compiled but try them first
FaultException said:
New ones up, they're not clean compiled but try them first
Click to expand...
Click to collapse
Thanks, I'll let you know
Still not working.
I called my phone from my wife's phone many times and this is what I've experienced and learned:
1. The tunnel voice does not start until the caller speaks (e.g. after my CM7 phone receives a voice signal from the caller, the caller starts hearing a tunnel voice). When I called my phone and had my wife start talking everything was clear until I said something (I was on her phone), then the tunnel voice started.
2. If I manually mute and unmute my phone immediately after answering a call and before speaking, the entire call is clear, no tunnel voice.
Maybe the mute and unmute functions that Nelson used are incorrect or in the wrong location?
I love Steve's AOKP PUB Rom but I seem to have one really irritating issue upon using it. I set my ringtone and notification sounds to the ones i always use. Pyxis for Ringtone, and Don't Panic for notifications. Then i noticed that i was not hearing the sounds during incoming phone calls and texts. So i go into the sound setting to see whats up and they both have unrecognized sounds listed. When i try to re-establish the original setting all the choices are gone except for 2 or 3 instead of the usual several dozen. If i use Root Explorer to go into the media folder all the ogg files are still present. Sometimes they come back upon a reboot. Sometimes they dont. Anyone else seen this or know whats happening? Thanks.
jslatas said:
I love Steve's AOKP PUB Rom but I seem to have one really irritating issue upon using it. I set my ringtone and notification sounds to the ones i always use. Pyxis for Ringtone, and Don't Panic for notifications. Then i noticed that i was not hearing the sounds during incoming phone calls and texts. So i go into the sound setting to see whats up and they both have unrecognized sounds listed. When i try to re-establish the original setting all the choices are gone except for 2 or 3 instead of the usual several dozen. If i use Root Explorer to go into the media folder all the ogg files are still present. Sometimes they come back upon a reboot. Sometimes they dont. Anyone else seen this or know whats happening? Thanks.
Click to expand...
Click to collapse
Same here. I'm back of AOKPBRAVO at the moment because of the sound issues. One thing that helped me a bit was to disable vibrate with ring and have ring only but it still would lose the ringtone and on calls the screen would light up and i had missed calls because the ringtone wouldn't be recognized.
I have noticed this same issue and believe I have found a work around for the problem. First take off the Vibrate on incoming calls. Then in the root of your sdcard there is a ringtones folder. Make sure that the ringtone is in that folder. With some of these new roms, they will only play ringtones that are in that folder plus the default that the developer chooses. Go into contacts and set the ringtone for the contact. First I would do it as a test ringtone on a number you can call from. If you have the same ringtone for multiple people then you have to make a new copy of that file. It will only play it for the last contact you assign it too. That is how I cleared my troubles with it. Hope this works out for you.
Hi,
As the title suggests, is there any way to disable the bluetooth last number redial functionlity.
I have a Xperia Mini Pro (SK17i, Bootloader unlocked, Rooted) with a Samsung HM1700 bluetooth headset. The headset has a button for answering / ending calls and this same button also has the last number redial functionality, ie when not in a call, pressing this button redials the last dialed number.
AFAIK, the headset just sends a signal to the mobile which then calls the last dialed number.
What I need, is to disable only the bluetooth redial functionality on my mobile.
[ BUMP]
Any suggestions anyone?
Sent from my SK17i
BUMP
Sent from my SK17i
You can try the app Smart Bluetooth Headset from the Play Store.You can not only disable it but also make it do something useful
Since the app "Smart Bluetooth Headset" does not work reliably for me (e.g. not activated by default after program start) I use this now: Go to Bluetooth settings and find your headset. Uncheck Phone to disable the headset from being used for voice calls.
Use an app on your smartphone to enable bluetooth on call and disable after call. There are many apps for this, for example bluetooth on call: https://www.addictivetips.com/mobil...ndroid-bluetooth-for-bt-headset-during-calls/
In addition to solving this problem your phone battery will last longer.
Regards Rob.
Necroing this thread to say that I tried "Headset Button Controller" and "Smart Bluetooth Headset" apps, both free versions, on my rooted HTC10 running Oreo 8.0 with a paired MPOW Crescent. Both apps worked, in slightly different ways.
Headset Button Controller places a dummy call on the call log. Activating the redial function on the headset (double click the answer/end call button on the MPOW Crescent) makes the phone call to the dummy thing, and a little window shows asking for a valid number. No call is actually made.
Problem is, if a valid call is made (for example, you call your boss or a friend), the dummy call setting must be reenabled again manually in the app - meaning that, if you make a valid call, the next time you activate the redial function on the headset, it will call the valid call.
Smart Bluetooth Headset works basically the same way, except that, instead, the redial attempts to call the * or *1 numbers. These attempts open the call window but close it right away, and immediately activate whatever you set the redial function to do. I set mine to run "Tasker 01", but didn't set what "Tasker 01" is. So, what my phone does when I (accidentally) activate the redial function on my headset is open and close the call window, and then return an onscreen self-fading error notification stating that Tasker 01 could not be found.
Best of all, the settings stick - meaning that, if you make a valid call, the redial function will still attempt to dial the * or *1 numbers, as long as the Smart Bluetooth Headset service is active.
So, in my experience, the Smart Bluetooth Headset app works the best.
Of course, I could just turn the headset on and off, whenever I need. It has a physical on/off switch, and immediately pairs with the phone (if previously paired) when turned on.
Awesome guys, thanks! Well written instructions Kam0laZ So nice when a solution presents itself effortlessly. Just turned on my new Bluetooth piece and INSTANTLY ( double tapping by mistake Just to get the damn thing in my ear hole) redialed my (dreaded) Ex BF..... TWICE! .... Noooooooo! Damn it! *Fists shaking furiously* And the ball was only in MY court but for a fleeting moment... wah wah
Could you share a link for these two apps? I've been trying to find them on the Google play store..
Unfortunately, redialing is no easy feat (like instead the stupid "media player opens" case).
https://github.com/LineageOS/android_system_bt/blob/lineage-17.1/bta/include/bta_ag_api.h#L319
https://github.com/LineageOS/android_system_bt/blob/lineage-17.1/btif/src/btif_hf.cc#L423
https://github.com/LineageOS/androi...e-17.1/jni/com_android_bluetooth_hfp.cpp#L194
https://github.com/LineageOS/androi...luetooth/hfp/HeadsetNativeInterface.java#L118
https://github.com/LineageOS/androi...ndroid/bluetooth/hfp/HeadsetStateMachine.java
https://github.com/LineageOS/androi...droid/bluetooth/hfp/HeadsetService.java#L1331
So, like, simply put.. You have a bluetooth HFP device that sends an AT+BLDN command to your phone.
The bluetooth stack runs DialCallCallback in the bluetooth package, which getLastDialledNumber from your phonebook, and then sends an ACTION_CALL_PRIVILEGED intent to the rest of the phone with the number to call.
Where could we act?
Perhaps if you could force some sort of HSP-only mode, you could avoid all the extra cruft but I'm not aware of any way to do so.
Similarly, there are plenty of ways to "directly hack the code", but I don't think anybody has got such a solution yet.
So my efforts have focused on disturbing the phone dialer from getting the action to call.
The problem is, "install-only" permissions aren't changeable. And without root you can't even hope to revoke android.permission.READ_CALL_LOG. And without xposed you can't even block intents.
(if you have either of these though, something could be done I guess?)
So long story short, well, Smart Bluetooth Headset still sounds like the best option.
It's no longer available in any official place as already stated.. But luckily enough it was open source!
We'll see.
Hi,
Install macrodroid app from play store.
Create a macro as follows:
Trigger:
Call/sms -> call outgoing
(Select number(s) from the 3 bullet menu that appears, it is the 3rd)
Enter * (meaning all calls)
Action:
Phone -> call reject
Save the macro.
That's it !!!
Keep in mind to let the macrodroid app on the white list of any battery saver app you may have installed or is built in the android it self (eg xiaomi phones) easy to make it unrestricted to not be killed by any task manager.
Simple solution, minimal battery drain, no wake up the phone to check. The macro runs only on call intent
Thats's it.
Thanks
kounelii said:
kounelii said:
Hi,
Install macrodroid app from play store.
Create a macro as follows:
Trigger:
Call/sms -> call outgoing
(Select number(s) from the 3 bullet menu that appears, it is the 3rd)
Enter * (meaning all calls)
Action:
Phone -> call reject
Save the macro.
That's it !!!
Keep in mind to let the macrodroid app on the white list of any battery saver app you may have installed or is built in the android it self (eg xiaomi phones) easy to make it unrestricted to not be killed by any task manager.
Simple solution, minimal battery drain, no wake up the phone to check. The macro runs only on call intent
Thats's it.
Thanks
Click to expand...
Click to collapse
Click to expand...
Click to collapse
@kounelii how do you configure the macro so that it only applies to calls made from headphones when last number redial is executed?
kounelii said:
Hi,
Install macrodroid app from play store.
Create a macro as follows:
Trigger:
Call/sms -> call outgoing
(Select number(s) from the 3 bullet menu that appears, it is the 3rd)
Enter * (meaning all calls)
Action:
Phone -> call reject
Save the macro.
That's it !!!
Keep in mind to let the macrodroid app on the white list of any battery saver app you may have installed or is built in the android it self (eg xiaomi phones) easy to make it unrestricted to not be killed by any task manager.
Simple solution, minimal battery drain, no wake up the phone to check. The macro runs only on call intent
Thats's it.
Thanks
Click to expand...
Click to collapse
i get two separate ringers when I have an incoming call the one that is set by the system and another that is just a chirping ring. I don't understand where this chirping ring is coming from or how to disable it. Here are some log files that I have been scouring to try to find what sets off the secondary ringer even if Do Not Disturb or total silence is enabled. The chirping ring will stay active through the entire call until you end it. i am using CM13 for the boost mobile samsung j3, sm-j320p.
this is the link to the rom.
https://mega.nz/#!Rd1T0YSB!W4RAl5c7_fLM7JnZYCfQvuwqR6hKM86YYW_aaavO118
the camera is also broken but i can deal with that for now.
thanks
My S5 was rooted, and the rom I used had an option to record calls from the in call menu. Now I have an s9+ and this is the feature I miss the most. A lot of the apps seem shady. Can anyone recommend an app / method to record calls without it beeping or anything, without root, ideally from within the in call menu (easy to do on the fly)
Call recording
This has been covered quite a few times and is very easy to search. There is an app called ACR that performs the function you need without root.
We really do not need another thread on this
I am not OP, BUT I have not gotten ACR to work on the s9+ with Verizon - do you mind sharing your settings with me?