Related
Hi all,
The effect I'm looking for:
While an open phone call, I'd like to be able to play sounds into the call stream so that (similiarly to the in-call DTMF tones) the sounds would be heard by the other party.
My questions:
1) Is this possible without modifying phone.apk (or what ever system .apk needed to gain access to the call stream)? Does it help if the device is rooted?
2) If not, is it at all possible? What would it take to achieve such an effect?
Any help would be much appreciated.
Need a solution too, looking into reflection.
This is rather old but I was wondering if there's any news? I searched for anything related to call, stream, DTMF etc. in XDA and everywhere else I could think of.
So far I found nothing. Is there really no way to send tones up the call stream?
I'm looking into the source code to see whether I can use some reflection, even just to see if it works. The best bet seems like CallManager..
It has 'SendDtmf' and 'StartDtmf' that automatically goes to the active call, gets the active phone from it and shoots up the tones.
HOWEVER I got stuck. Both methods keep returning false. Digging into it you see that both methods check whether there are any active calls before sending anything. So I tested it myself and here lies the issue - 'HasActiveFGCalls' (and HasActiveBgCalls too) returns false no matter what.
In fact, getting the full call list (getForegroundCalls) always gives me an empty list.
I tested it on my phone (SGS, CM7) and on the emulator on several versions. Same results - always no active calls regardless of whether the phone is in a call or not.
I'm at a loss here. Seems like this is as far as I can go with my knowledge at the moment.
So... anyone has any clue regarding this?
Am I the only Relay user having trouble using voice command thru bluetooth?
I'm running Cyanogenmod 10.2, on tmobile, and using google voice/talktone for calls.
On both bluetooth car kits I've tried (Blueant Commute and Kinivo BT450), things work fine (music, navigation, reading incoming texts, taking calls) until I try to voice command the phone thru the BT unit.
I've tried:
~ google now, voice search, voice dialer
~ turning on talkback (hate that constant reading of each page, AGHH!)
~ blueant app (does F%&&% all)
~ every tip on both gear's support pages
~ tmobile's support page (HA!)
~ even reverted back to stock (in case it was CM), and IT STILL SUCKED MY @**#&#$
I am ready to throw this POS phone against the nearest underpass..... if someone can solve this, I will send you thanks, and a present. Seriously.
(I appreciate all advice, but feedback from those who have this prob, or solved this prob are the most helpful. THX)
Epiclectic said:
Am I the only Relay user having trouble using voice command thru bluetooth?
I'm running Cyanogenmod 10.2, on tmobile, and using google voice/talktone for calls.
On both bluetooth car kits I've tried (Blueant Commute and Kinivo BT450), things work fine (music, navigation, reading incoming texts, taking calls) until I try to voice command the phone thru the BT unit.
I've tried:
~ google now, voice search, voice dialer
~ turning on talkback (hate that constant reading of each page, AGHH!)
~ blueant app (does F%&&% all)
~ every tip on both gear's support pages
~ tmobile's support page (HA!)
~ even reverted back to stock (in case it was CM), and IT STILL SUCKED MY @**#&#$
I am ready to throw this POS phone against the nearest underpass..... if someone can solve this, I will send you thanks, and a present. Seriously.
(I appreciate all advice, but feedback from those who have this prob, or solved this prob are the most helpful. THX)
Click to expand...
Click to collapse
We (TeamApexQ) have thrown ourselves against this wall a few times, to no avail. This is a known issue in our sound configuration. It really comes out of the fact that getting this to work would involve having a bluetooth device work in two separate profiles (A2DP for output, SCO for input) at once which is not a trivial or easy thing to implement. What we need are more logs of this issue, and probably some direct communication in IRC with a couple of testers to bang this one out.
Magamo said:
We (TeamApexQ) have thrown ourselves against this wall a few times, to no avail. This is a known issue in our sound configuration. It really comes out of the fact that getting this to work would involve having a bluetooth device work in two separate profiles (A2DP for output, SCO for input) at once which is not a trivial or easy thing to implement. What we need are more logs of this issue, and probably some direct communication in IRC with a couple of testers to bang this one out.
Click to expand...
Click to collapse
OK, so I'm not a retard. hehe, thanks for that, I was going crazy thinking it must be some setting I overlooked. Strange though, it still didn't work when I reverted to stock.... no? (THAT must be something I am doing wrong...)
After 6 months enjoying CM10 (big thumbs up for TeamApexQ!!), I can't bear the thought of trying to suffer thru stock rom....what's the closest rom to CM that has good bluetooth integration..?
Epiclectic said:
OK, so I'm not a retard. hehe, thanks for that, I was going crazy thinking it must be some setting I overlooked. Strange though, it still didn't work when I reverted to stock.... no? (THAT must be something I am doing wrong...)
After 6 months enjoying CM10 (big thumbs up for TeamApexQ!!), I can't bear the thought of trying to suffer thru stock rom....what's the closest rom to CM that has good bluetooth integration..?
Click to expand...
Click to collapse
Now, someone can correct me if I am wrong on this, but I believe all of the community images are using the same sound configuration that TeamApexQ has been developing since CM 10.1, so... None of them. Again, with some community assistance, logcats, testing, and patience we can fix it.
Magamo said:
Now, someone can correct me if I am wrong on this, but I believe all of the community images are using the same sound configuration that TeamApexQ has been developing since CM 10.1, so... None of them. Again, with some community assistance, logcats, testing, and patience we can fix it.
Click to expand...
Click to collapse
I thought I heard CM9 had working BT... if not, what can I do to help? how do I capture and send you the logs?
Epiclectic said:
I thought I heard CM9 had working BT... if not, what can I do to help? how do I capture and send you the logs?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1726238
Please, please, please issue a 'logcat -c' before doing this proceedure to capture a log of the issue, to clear the log, and to avoid having us to sift through every log your phone has taken since reboot.
Also, send us the contents of the 'dmesg' command after encountering the issue, just to rule out anything on the kernel side.
I'm working on adding support for a WiFi only build of CM-11 for the SM-T325.
I am making no attempt at this time to add cellular support because I don't own the device and it would be very painful to try to do that without the device. However, a WiFi only version seems possible and I want to use this thread to validate that.
As a first step, I'm looking for people to test that this recovery works for them on a SM-T325: cwmr-20140528-mondrianlte.
You'll need to unzip the file and then flash it in Odin. If you don't know how to do that, then a test build is probably not for you!
Yes..it works!!!
crpalmer said:
I'm working on adding support for a WiFi only build of CM-11 for the SM-T325.
I am making no attempt at this time to add cellular support because I don't own the device and it would be very painful to try to do that without the device. However, a WiFi only version seems possible and I want to use this thread to validate that.
As a first step, I'm looking for people to test that this recovery works for them on a SM-T325: cwmr-20140528-mondrianlte.
You'll need to unzip the file and then flash it in Odin. If you don't know how to do that, then a test build is probably not for you!
Click to expand...
Click to collapse
i can confirm that this recovery does indeed function as expected...i installed my rom (ran into a weird "android is upgrading" bootloop but it eventually loaded...that may be my experimental multiwindow mod i'm using or the fact that i have completely deleted the touchwiz launcher) as well as created a backup (didnt restore) & all seems to be in order. I may be overreaching a bit about my abilities but im sure if u get a working wifi version going for us then the least i can do is get the cellular working...on a sort of related note would u happen to know if its possible to output through hdmi while in recovery mode? As far as this build is conncerned...anything else u may need tested just give me a shout
edit: looked for the backup which is usually on the internal sd (read:accessible from pc) and although the folder is there its empty...finally found it in "data-media-clockworkmod" & just wanted to know is this normal?
THEDEVIOUS1 said:
i can confirm that this recovery does indeed function as expected...i installed my rom (ran into a weird "android is upgrading" bootloop but it eventually loaded...that may be my experimental multiwindow mod i'm using or the fact that i have completely deleted the touchwiz launcher) as well as created a backup (didnt restore) & all seems to be in order. I may be overreaching a bit about my abilities but im sure if u get a working wifi version going for us then the least i can do is get the cellular working...on a sort of related note would u happen to know if its possible to output through hdmi while in recovery mode? As far as this build is conncerned...anything else u may need tested just give me a shout
edit: looked for the backup which is usually on the internal sd (read:accessible from pc) and although the folder is there its empty...finally found it in "data-media-clockworkmod" & just wanted to know is this normal?
Click to expand...
Click to collapse
That is normal (it is independent of users and /sdcard is specific to user 0 of the tablet).
If you want to work on the radio, you'll need to be able to build sm-t320. If you get that to build, I'll push up my current repos for the sm-t325.
Would you mind booting into recovery and grabbing a dmesg (/proc/kmsg) for me?
Hopefully I can post a cm 11 build in a couple of hours and we can see how that works.
crpalmer said:
That is normal (it is independent of users and /sdcard is specific to user 0 of the tablet).
If you want to work on the radio, you'll need to be able to build sm-t320. If you get that to build, I'll push up my current repos for the sm-t325.
Would you mind booting into recovery and grabbing a dmesg (/proc/kmsg) for me?
Hopefully I can post a cm 11 build in a couple of hours and we can see how that works.
Click to expand...
Click to collapse
either i dont know what i'm doing or adb isnt working properly in cwm...when i connect i get a weird "usb recognized but there's a problem" sound instead of the usual "affirmative" noise if that makes sense (windows)
Here's a build to try: cm-11-20140528-UNOFFICIAL for the sm-t325.
crpalmer said:
Here's a build to try: cm-11-20140528-UNOFFICIAL for the sm-t325.
Click to expand...
Click to collapse
I will give it a try. No mobile Internet with this rom, right? Which gapps I should use? Or is gapps for every rom the same?
works perfectly...thx
crpalmer said:
Here's a build to try: cm-11-20140528-UNOFFICIAL for the sm-t325.
Click to expand...
Click to collapse
everything seems to be ok on my end although i cant test as thoroughly as i'd like to because my screen is screwed (broken lcd)...gps took a long time to track & still never redrew the map after it did but that was without high accuracy mode enabled & no data of course. Mic, camera, mhl/hdmi, sound, video playback, wifi, bluetooth (wait let me check...yep!), auto brightness, lid sensor are all working properly...so now i need your permission. Besides getting data working...i just want to know am i free to use this in a dual boot configuration with my rom & post it in my thread? Also...this is not important but do u know if screen mirroring works with the wifi version?
THEDEVIOUS1 said:
everything seems to be ok on my end although i cant test as thoroughly as i'd like to because my screen is screwed (broken lcd)...gps took a long time to track & still never redrew the map after it did but that was without high accuracy mode enabled & no data of course. Mic, camera, mhl/hdmi, sound, video playback, wifi, bluetooth (wait let me check...yep!), auto brightness, lid sensor are all working properly...so now i need your permission. Besides getting data working...i just want to know am i free to use this in a dual boot configuration with my rom & post it in my thread? Also...this is not important but do u know if screen mirroring works with the wifi version?
Click to expand...
Click to collapse
I don't know whether or not screen mirroring works. No one has complained but I don't have any way to test it.
You can (obviously) post a link to the thread. I would prefer that you didn't link to a specific version as I hope to post more test builds here (although so far only 3 people have downloaded it which shows either a lack of interest or a lack of early adopters).
crpalmer said:
I don't know whether or not screen mirroring works. No one has complained but I don't have any way to test it.
You can (obviously) post a link to the thread. I would prefer that you didn't link to a specific version as I hope to post more test builds here (although so far only 3 people have downloaded it which shows either a lack of interest or a lack of early adopters).
Click to expand...
Click to collapse
Hello, I will root my device and download the test build as well ! Will post back soon.
Thanks for trying to bring support for this device !
Bautinho88 said:
I will give it a try. No mobile Internet with this rom, right? Which gapps I should use? Or is gapps for every rom the same?
Click to expand...
Click to collapse
Sorry, I missed this post... Use the gapps from the sm-t320 thread.
crpalmer said:
Sorry, I missed this post... Use the gapps from the sm-t320 thread.
Click to expand...
Click to collapse
woohoo...well i got data working but calls are a no go as of right now. i can assure u the lack of activity in this thread is definitely not due to lack of intereset....more than likely its because its barely been a full day not to mention that there are not that many of us lte users but best believe once word gets round they'll come running. As far as my permission request...what i was thinking is that i'll just wait until the monthly releases start coming, make the proper changes for data (unless u actually make ours official also which would be awesome) & include it in a dualboot (hopefully multirom) setup. From what i've read ...alterations will need to be made to both kernels/roms which is why i was asking could i use it. I would definitely put a "use at your risk" disclaimer up as to not have the official thread flooded with issues not actually related to cm itself...let me know if u need anthing else on my end
edit: i do have one weird issue though...i copied the dialer app from another device with cm11 but it doesnt show up in the app drawer but is in fact found within the app manager in settings (i know i can just download another dialer but thought i would ask)
edit 2: calls not working yet & but i did get the phone app to appear & sms are also good to go (no mms at the moment)...got rid of the error message on outgoing calls (incoming wont even ring at all) but now it just force closes before it dials out (even with a different dialer)
THEDEVIOUS1 said:
woohoo...well i got data working but calls are a no go as of right now. i can assure u the lack of activity in this thread is definitely not due to lack of intereset....more than likely its because its barely been a full day not to mention that there are not that many of us lte users but best believe once word gets round they'll come running. As far as my permission request...what i was thinking is that i'll just wait until the monthly releases start coming, make the proper changes for data (unless u actually make ours official also which would be awesome) & include it in a dualboot (hopefully multirom) setup. From what i've read ...alterations will need to be made to both kernels/roms which is why i was asking could i use it. I would definitely put a "use at your risk" disclaimer up as to not have the official thread flooded with issues not actually related to cm itself...let me know if u need anthing else on my end
edit: i do have one weird issue though...i copied the dialer app from another device with cm11 but it doesnt show up in the app drawer but is in fact found within the app manager in settings (i know i can just download another dialer but thought i would ask)
edit 2: calls not working yet & but i did get the phone app to appear & sms are also good to go (no mms at the moment)...got rid of the error message on outgoing calls (incoming wont even ring at all) but now it just force closes before it dials out (even with a different dialer)
Click to expand...
Click to collapse
Here's a new build that has all of the telephony bits enabled. I haven't tried booting it (I'm at work, the tablet is at home) but it should have the dialer and all the other framework that is needed for telephony. Let me know if you get calls working with it:
cm-11-20140529-beta
crpalmer said:
Here's a new build that has all of the telephony bits enabled. I haven't tried booting it (I'm at work, the tablet is at home) but it should have the dialer and all the other framework that is needed for telephony. Let me know if you get calls working with it:
cm-11-20140529-beta
Click to expand...
Click to collapse
Can I use TWRP or must be done under recovery (cwmr-20140528-mondrianlte) from the first post?
megatooth said:
Can I use TWRP or must be done under recovery (cwmr-20140528-mondrianlte) from the first post?
Click to expand...
Click to collapse
twrp is fine. The recovery was just because the first step is to make sure that boots before bothering to get the whole system to boot..
I will install your latest build and return with impressions.
Edit: @crpalmer: Phone.apk/dialer is missing and I have no service.
megatooth said:
I will install your latest build and return with impressions.
Edit: @crpalmer: Phone.apk/dialer is missing and I have no service.
Click to expand...
Click to collapse
Yeah, I made no attempt to get the radio working, hence the title...
@THEDEVIOUS1, did you make any progress on modifying the build I posted to get voice working? If so, let me know what changes you've made and I'll see if I can incorporate them.
crpalmer said:
Yeah, I made no attempt to get the radio working, hence the title...
@THEDEVIOUS1, did you make any progress on modifying the build I posted to get voice working? If so, let me know what changes you've made and I'll see if I can incorporate them.
Click to expand...
Click to collapse
Long story short...still no voice. Now for the rest of it...i've gotten it to the point where i can dial out but neither the mic nor speaker works when the call is answered by the other party (i think this is due to the fact that it reports that the call ends as soon as it begins on my device). As far as receiving calls is concerned...NOTHING. I have even gone as far as flashing a note 3 modem (yeah i know...stupid :silly in an attempt to fix it & still no go...i just recently found the build prop edit to allow outgoing calls so hopefully the rest is as simple as editing the build prop. Speaking of which...getting data/phone working is NOT quite so simple but i've gotten it down to the bare minimum number of changes that need to be made. So far we need to add the "lib-qcril-hook-oem.so" from the n9005 cm11 rom & the "libsec-ril.so" as well "libril.so" from the stock T325 rom (which is enough by itself to get data working) as well as decompile the framework-res.apk & and change both the sms & voice config bools enable to true (which i'm sure there is a flag for in source)...this makes the phone app appear as well as allows u to send texts then we need to add the line "ro.telephony.ril.v3=newDialCode" to the prop which allows us to dial out. Well...thats where i'm at as of right now so its back to google for me to put together the rest of the pieces unless u have some insight from working on devices with radios that can be of some assistance
THEDEVIOUS1 said:
Long story short...still no voice. Now for the rest of it...i've gotten it to the point where i can dial out but neither the mic nor speaker works when the call is answered by the other party (i think this is due to the fact that it reports that the call ends as soon as it begins on my device). As far as receiving calls is concerned...NOTHING. I have even gone as far as flashing a note 3 modem (yeah i know...stupid :silly in an attempt to fix it & still no go...i just recently found the build prop edit to allow outgoing calls so hopefully the rest is as simple as editing the build prop. Speaking of which...getting data/phone working is NOT quite so simple but i've gotten it down to the bare minimum number of changes that need to be made. So far we need to add the "lib-qcril-hook-oem.so" from the n9005 cm11 rom & the "libsec-ril.so" as well "libril.so" from the stock T325 rom (which is enough by itself to get data working) as well as decompile the framework-res.apk & and change both the sms & voice config bools enable to true (which i'm sure there is a flag for in source)...this makes the phone app appear as well as allows u to send texts then we need to add the line "ro.telephony.ril.v3=newDialCode" to the prop which allows us to dial out. Well...thats where i'm at as of right now so its back to google for me to put together the rest of the pieces unless u have some insight from working on devices with radios that can be of some assistance
Click to expand...
Click to collapse
Can you send me a logcat of making a call?
crpalmer said:
Can you send me a logcat of making a call?
Click to expand...
Click to collapse
Keep an eye on this post...i just jumped off the deep in end & tried to install the hlte version as is (with kernel swap of course ) so it may take me a minute to get back (i have a nandroid but like to make the cjanges manually so i know the exact process & origin of files). Well i'll be damned...incoming calls work (complete with mic & speaker) with note 3 version of cm11! Outoing still seem to be an issue but this clears up a few gray areas i had concerning whether the ril files matched the modem & so on...i had the bright idea of swapping a few of the framework files then just thought they were so similar that the whole thing should boot. Anyway....shouldnt be long to figure out what the hold up is now bu tgive me a few & i'll post the log after i test a ouple of things then flash back to the other setup
edit: Aaaaaaannnnddd....done! added the line i spoke about in my previous post to the build.prop & now both incoming & outgoing calls are working with the N9005 version...just out of curiosity i'm about to go through & see whats broken the first of which i notice is rotation (i personally hate portrait) but seems like everything else is as well including wifi, camera, lid, bluetooth, & ironically speaker audio (video playback & apollo play no audio through loudspeaker...both work through wired headset). I will still get that logcat a lil later...at this point i dont think it has anything else to do with the build prop because i had already added most of the stuff i found missing in ours from the hlte & it didnt work. I'm thinking maybe another lib file that needs to be swapped...perhaps maybe something in framework
THEDEVIOUS1 said:
Keep an eye on this post...i just jumped off the deep in end & tried to install the hlte version as is (with kernel swap of course ) so it may take me a minute to get back (i have a nandroid but like to make the cjanges manually so i know the exact process & origin of files). Well i'll be damned...incoming calls work (complete with mic & speaker) with note 3 version of cm11! Outoing still seem to be an issue but this clears up a few gray areas i had concerning whether the ril files matched the modem & so on...i had the bright idea of swapping a few of the framework files then just thought they were so similar that the whole thing should boot. Anyway....shouldnt be long to figure out what the hold up is now bu tgive me a few & i'll post the log after i test a ouple of things then flash back to the other setup
edit: Aaaaaaannnnddd....done! added the line i spoke about in my previous post to the build.prop & now both incoming & outgoing calls are working with the N9005 version...just out of curiosity i'm about to go through & see whats broken the first of which i notice is rotation (i personally hate portrait) but seems like everything else is as well including wifi, camera, lid, bluetooth, & ironically speaker audio (video playback & apollo play no audio through loudspeaker...both work through wired headset). I will still get that logcat a lil later...at this point i dont think it has anything else to do with the build prop because i had already added most of the stuff i found missing in ours from the hlte & it didnt work. I'm thinking maybe another lib file that needs to be swapped...perhaps maybe something in framework
Click to expand...
Click to collapse
The outgoing call issue is likely just that the audio configuration is missing the use cases for voice calls. That's why I wanted the logcat because that should be easy to add.
When you're done with the hlte version (which is actually not a great idea for a daily driver as there are other things that are different that you may not notice (two biggest I can think of is that the hardware is different and several of the HAL libraries need to enable/disable different files in /sys/ and the networking configuration is different which may break some kernel/user-space interactions).
But if you can send me the logcat, the build.prop that you are happiest with and detailed information about anything else that you chnaged (e.g. exactly what you changed in frameworks so I'm not guessing) then I'll take a look at another test build.
Hello!
I have a major issue during videocalls using google duo, skype where if there are any background noise around me, i can't hear the person i am talking to. The audio cuts off. It has to be silent around me in order for me to hear the person i am talking to. Is there any fix to this problem? I have already reset the phone but the problem is still there.
mic (over) sensitivity? perhaps some will stop by and know the file and file entry to edit.
any of this type setting elsewhere (Settings, the app itself, and sound modification yo have installed, eg Viper, etc... that you can check/get to?
I have no sound modification installed. I checked the settings but there seems to be no part adressing this issue. The same problem happens when i use different apps like skype, google duo and signal. Could it be a hardware problem? The microphone works fine when i record a video or recording audio.
Maybe.
Rooted? If so, and you've done a full, clean install, and sure that the install is working ok, maybe try another custom ROM.
Normal calls work, as I get you it's (just) video calls? Another possibility, I'd consider looking up mic sensitivity and ways to decrease it. On the OnePlus One I am aware there was a configuration file folks could mess with to try and resolve that phone's mics over sampling. That was a common issue for many.
Have you tried turning the volume down and see if that has any effect?
Wish I could offer more ideas, I have used video calls maybe 3 times in 8 years.
The phone is not rooted. This problem occurs only when i use internet based videocalls (skype, google duo). The volyme is not usually high when i call. Thank you for your time, hopefully i will find a solution soon.
Frustrating. Good luck.
Hi. Is it possible to record calls on Android os 13?
I heard since some Android 9 there is no possibility by many developers because they require a level of root to grant apps access.
Does it depend on root access and which os might have call recording function or might be working with call recorders?
Yes, call recording is possible on Android 13, but if it's not already enabled on your software, it will likely require root to enable.
Keep in mind that call recording may be illegal or restricted in some areas, and it is your own responsibility to be aware of the laws regarding recoding your calls.
liltechie said:
Does it depend on root access and which os might have call recording function or might be working with call recorders?
Click to expand...
Click to collapse
In addition to what was @V0latyle said above, yes to this part. Even with the same phone it might be available in one country but not another (native). Other require root and some just aren't compatible. If you post more details maybe someone else can give you more detailed info for your situation.
SyCoREAPER said:
In addition to what was @V0latyle said above, yes to this part. Even with the same phone it might be available in one country but not another (native). Other require root and some just aren't compatible.
Click to expand...
Click to collapse
I wanna buy a new phone and look which device might fit call recording best.
How do the manufacturers build phones detecting the permission or forbidance of recording? Is there a list of devices working? How come that some devices are not compatible for call recording at all?
I can only speak from what I've read and experienced. Samsung for example has it in a few markets only. Some call recorders I used in the past in the playstore listed certain phones weren't compatible, maybe technical limitations.
3rd party used to work with Samsung/for me but don't anymore. Unless it's allowed in your country (and comes with the phone) it could stop working at any time. Since I am in the USA, our laws are different in each state so none of our phones have it by default so I wouldn't be able to recommend anything.
There are subscription apps that route your calls through their servers and record on their end but don't recommend that.
SyCoREAPER said:
3rd party used to work with Samsung/for me but don't anymore. Unless it's allowed in your country (and comes with the phone) it could stop working at any time.
There are subscription apps that route your calls through their servers and record on their end but don't recommend that.
Click to expand...
Click to collapse
Which Samsung was the last working with recorders? Seems like devices might scan the gsm?
Why don't you recommend these call routings? Due to data privacy, quality of voice or cost or other interference?
Ever since android 11 or 12 is stopped working for me. Haven't tried anything new since
And yes, privacy reasons. Also a bad experience, they all inevitably (except business grade solutions) tank. They are there one day and gone the next. I loved the one I was using, month after I bought a year subscription they were closing.
At this point I only make and acccept calls that I know won't need recording. If they do, I carry a second phone (impractical) or wait till I get home and use my tablets voice recorder app
SyCoREAPER said:
I loved the one I was using, month after I bought a year subscription they were closing.
At this point I only make and acccept calls that I know won't need recording. If they do, I carry a second phone (impractical) or wait till I get home and use my tablets voice recorder app
Click to expand...
Click to collapse
How much did a subscription for one year cost you?
Do you use a speakerphone or make a hands-free mobile phone call while holding the microphone of your second mobile phone towards it?
It wasn't cheap, $52.99, did other things like let you listen into the call and have their "bot say what you typed" , etc.. but again that's gone. There might be similar services but it's not worth it.
And for the second device method, you can do wired (a lot of splitters/y-cables) or just speaker on the phone making the call.
All this is last resort stuff though. If you're in a country that allows it, just Google whatever model you're interested in "can phone-XYZ record calls in Country-ABC?"
SyCoREAPER said:
And for the second device method, you can do wired (a lot of splitters/y-cables) or just speaker on the phone making the call.
Click to expand...
Click to collapse
Can you recommend a y-cable or splitter or name a technology that works well? And then just pluging in the 3.5mm jack or usb and how to record on the second device?
It's janky and It's really not practical though, just warning you in advance. It's also like $50 of cable spaghetti.
Basically you get a usb-c to 3.5 headset adapter for each phone. You get a headset splitter, headset goes into another splitter. Audio goes into one port, on the other headphone splitter plug you route a cable to the microphone splitter input of the second phone.
Maybe something pre-made exists but don't know what it's called. You should be able to find a diagram on Google of what I'm describing above.