Related
Hello,
I recently recieved a Dash from T-Mobile with WM6 Standard. 1 annoying thing I've noticed is that although the phone's keypad is locked, while reaching for the phone in the pouch, I've accidentally answered calls that I didn't want to . I wish there was a way that required a combination of at least 2 keys be pressed in a certain order before the call would be answered. This would be similar to unlocking the keypad. I could also prevent unknowingly answering a call if the ringer was on silent.
Wow, many views, no solution??
Im not sure about your phone, but you might want to disable any key answer
For my phone ( tornado ), its under settings, phone, call options
Hello karhoe,
Thanks for the suggestion, however that option is already disabled. The problem is that when the phone is in the case or in my pocket, the Answer Key can easily be activiated by the slightest touch which is not good. I'm suprised that more people haven't responded with the same issue.
Yes it happened to me a couple of days ago, quite annoying. The phone was just in my pocket and it rang. Reached in to pull the phone out, and apparently I had inadvertantly touched the softkey that answers the phone, before I could check the caller ID
Well there is no app that I know of that makes you have to press 2 or more keys to answer the phone. And that is what you would need, a 3rd party app.
It would be kind of dangerous or even more annoying under certain circumstances like driving. But if you had 2 different lock options, one normal the other for the 2 button answer, that would be cool. Very cool indeed.
But it does'nt always happen, I think it's happened only twice. Usually the phone is not in my pocket or on me in a holster, because I want to keep the radiation away from my body, so it's usually on my desk or sitting in the car if I am driving. In-between those times it is on me.
I'm afraid this applies to any phone of the Candy Bar type. Happened to me quite often to answer a call while reaching for the phone (S620 and S710 ans some other Nokias). Flip phones are much better for that. You got to open the phone to answer a call and you can still check the caller on the outside display before opening it.
You're right, a third party app setting a two level answer mode would be great, although don't know if this can be done, where the core of the phone handles the answering alone preventing any developer to set up an "answering sequence". Good idea anyway, curious to check on this one.
Ka.
Thanks for the replies. I'm still optimiistic that SOMEone out there may have a solution!
Sorry can't resist - If its someone you don't want to talk to, pretend you're on ATT and drop the call
I haven't had a problem. I use this case
http://www.krusell.se/product.php?productID=576&category=5
@jamssx: lol
@timothyjok: thx for the suggestion, I've looked at that case before, but was trying to remain positive that someon may have software solution. sigh...
From http://www.shipiboconibo.com/dash/#callreject :
Disable Accidental Call Rejection
Have you ever recieved a call and as you pull your Dash out of your pocket it says 'Call rejected'? I have, and it annoys the hell out of me! I derived this hack from a hack telling how to enable this feature, but mine was enabled by default so I am going to assume the original hack was intended for the Excalibur and T-Mobile decided to enable the feature on their phones. By default (can anyone else verify this is default on the Dash?) simply touching the JOGGR strip on the Dash during an incomming call will reject the call. I hate this and here is how you can disable it!
\HKEY_CURRENT_USER\ControlPanel\JogBar\Settings\EnableRejectCallFunc = 0
As you probably guessed, this is a binary value, setting it to 0 disables it, 1 enables it.
I was reading the user reviews of the Fuze on another website when I noticed one saying that the Fuze requires you to press the power button to reactivate the screen each time you need to press a phone number button on the screen while you are on the phone. Is this a requirement on the TP2? As someone who has to deal with phone trees and other automated phone systems alot for business calls I was thinking that I should ask about this as it would be extremely inconvenient.
The proximity sensor will automatically turn on the screen if you move your face away from the device during a call. There's a big button to bring up the keypad to use. If the keypad is deployed and you put the device back to your face, the screen will turn off. But if you turn the screen back on, the keypad will still be deployed, so that's pretty useful.
Thank you very much for this information, it in nice to hear that this problem was resolved on the TP2. I was also wondering if it is possible to run the speakerphone with the TP2 in face up so one could type on the dialpad on the screen while hearing the responses from the phone call? I'm guessing this is possible as my old 8525 does it fine but I just thought I should confirm it. Thanks in advance.
During a call, you can also take out your stylus, it will start notes.. makes it available to write on the screen during a phonecall.
coscom said:
I was also wondering if it is possible to run the speakerphone with the TP2 in face up so one could type on the dialpad on the screen while hearing the responses from the phone call? I'm guessing this is possible as my old 8525 does it fine but I just thought I should confirm it. Thanks in advance.
Click to expand...
Click to collapse
Yes, there's a large button during a call for you to tap to switch to speakerphone as an alternative to putting the device face down on a table. Dialpad works the same in speakerphone mode as in normal mode.
Has anyone else noticed that when you receive a call sometimes you have the option to press answer or ignore and other times you get slide up or slide down to answer or reject? Is there anyway to just have one of them? And also why isn't there an option to clear the incoming call screen? It just stays there until I pick answer or ignore.. on my g1 I would press back and it would clear and let me get back to my business. Also is there a way that I can just have the slide up or slide down to answer? The on screen keys always press when pullin the phone out of my pocket.. super annoying
the option you get is determined whether or not you phone display is on (locked or unlocked) at the time.
Oh ok.. thanks. I couldn't pinpoint it.. I guess once root is available then I can completely shut down the answer on the screen feature. Thanks again
you think there is any chance we could get phone calls non intrusively like webos
I'm having issues with the screen not turning back on after a call or even listening to audio messages. I have to relock and then unlock to get it to work, very annoying.
I'm on 8.1, on magisk with xposed.
Could someone recommend me an app or a module?
https://issuetracker.google.com/issues/71510515
You along with a bunch of us... ota messed it up
Good to know, I'm not the only one. Doesn't seem related to screen protector.
Really wish I can disable the proximity sensor for now.
I guess I came to the wrong thread. I don't have any issues like that or at least I don't notice it because I is the power button to turn the screen in/off all the time and I set my lock screen to not relock the phone for 5 minutes or something like that. That way I don't gotta enter my unlock code. There also is a setting which is supposed to keep your phone unlocked as long as you don't set it down. There also is a setting that keeps your phone from locking if you are within range of a Bluetooth (headseat maybe) device. I dunno try some of those options maybe you won't need to type your code in as much.
Personally I came here because I am looking for a way to completely disable my proximity sensor. I absolutely hate them on all phones. How stupid is it that they put the proximity sensor I right up next to where you have to put your hand if you want to pull down the menu bar??? It's like I go to pull down the menu bar - screen off. ****! Power button, slide open the lock screen (no code needed). Pull menu bar - screen off ****! Power.... Slide....menu bar - screen off. Of course it only does that during calls however that's a pretty annoying time because you're usually focused on other things and not wanting to **** with the screen going on and off.
Who the needs a proximity sensor to detect one's face anyway? I just click the power button every time I put the phone to my ear. Any time I don't do that, I run the risk of my cheek pressing the mute button for the 9000th time in my life. I do love Android though.
KirkH420 said:
I guess I came to the wrong thread. I don't have any issues like that or at least I don't notice it because I is the power button to turn the screen in/off all the time and I set my lock screen to not relock the phone for 5 minutes or something like that. That way I don't gotta enter my unlock code. There also is a setting which is supposed to keep your phone unlocked as long as you don't set it down. There also is a setting that keeps your phone from locking if you are within range of a Bluetooth (headseat maybe) device. I dunno try some of those options maybe you won't need to type your code in as much.
Personally I came here because I am looking for a way to completely disable my proximity sensor. I absolutely hate them on all phones. How stupid is it that they put the proximity sensor I right up next to where you have to put your hand if you want to pull down the menu bar??? It's like I go to pull down the menu bar - screen off. ****! Power button, slide open the lock screen (no code needed). Pull menu bar - screen off ****! Power.... Slide....menu bar - screen off. Of course it only does that during calls however that's a pretty annoying time because you're usually focused on other things and not wanting to **** with the screen going on and off.
Who the needs a proximity sensor to detect one's face anyway? I just click the power button every time I put the phone to my ear. Any time I don't do that, I run the risk of my cheek pressing the mute button for the 9000th time in my life. I do love Android though.
Click to expand...
Click to collapse
So it works too well for you with your finger but not enough for your face to prevent muting? LOL. Sorry never had that problem. I just avoid the middle if I had to get to the notifications during a call.
It happens often when I'm trying to toggle BT because my BT icon is directly under it.... For example. Anyway, I don't find it useful to even have an proximity sensor. That's why I stumbled in here, my search query was the exact title. I'm not really experiencing the problem the others were talking about though....
EeZeEpEe said:
So it works too well for you with your finger but not enough for your face to prevent muting? LOL. Sorry never had that problem. I just avoid the middle if I had to get to the notifications during a call.
Click to expand...
Click to collapse
xringo said:
I'm having issues with the screen not turning back on after a call or even listening to audio messages. I have to relock and then unlock to get it to work, very annoying.
I'm on 8.1, on magisk with xposed.
Could someone recommend me an app or a module?
Click to expand...
Click to collapse
It's an option to disable proximity in gravitybox.
Sent from my Pixel 2 XL using XDA Labs
KirkH420 said:
I guess I came to the wrong thread. I don't have any issues like that or at least I don't notice it because I is the power button to turn the screen in/off all the time and I set my lock screen to not relock the phone for 5 minutes or something like that. That way I don't gotta enter my unlock code. There also is a setting which is supposed to keep your phone unlocked as long as you don't set it down. There also is a setting that keeps your phone from locking if you are within range of a Bluetooth (headseat maybe) device. I dunno try some of those options maybe you won't need to type your code in as much.
Personally I came here because I am looking for a way to completely disable my proximity sensor. I absolutely hate them on all phones. How stupid is it that they put the proximity sensor I right up next to where you have to put your hand if you want to pull down the menu bar??? It's like I go to pull down the menu bar - screen off. ****! Power button, slide open the lock screen (no code needed). Pull menu bar - screen off ****! Power.... Slide....menu bar - screen off. Of course it only does that during calls however that's a pretty annoying time because you're usually focused on other things and not wanting to **** with the screen going on and off.
Who the needs a proximity sensor to detect one's face anyway? I just click the power button every time I put the phone to my ear. Any time I don't do that, I run the risk of my cheek pressing the mute button for the 9000th time in my life. I do love Android though.
Click to expand...
Click to collapse
Who needs a proximity sensor? Really? You basically answered your own question. To turn off the screen when you put it to your face so that your face doesn't press anything on the screen. Having to press the power button every time you put the phone to your face and then press it again every time you take it away from your face would suck.
jimv1983 said:
Who needs a proximity sensor? Really? You basically answered your own question. To turn off the screen when you put it to your face so that your face doesn't press anything on the screen. Having to press the power button every time you put the phone to your face and then press it again every time you take it away from your face would suck.
Click to expand...
Click to collapse
I always use speaker or bluetooth and proximity sometimes turns the phone off spuriously so I disable it.
Sent from my Pixel 2 XL using XDA Labs
Yeah.....no basically pressing the power button is where it's at. It the again I'm not one who likes everything done for me. Absolutely NO PHONE I've ever owned has had a proximity sensor that was worth a ****. They all, at one time or another, allow the screen to wake up subsequently letting the microphone mute button to enable. The mute button is another piece of Android trash that needs redesigning. It is not often that mute is needed so why not out that in a drop-down menu or something since it inevitably gets pressed during calls due to a ****y proximity sensor and Screen wake setup.
I also drive a manual transmission car. Actually the last 5 cars I've owned have been manual shifted. When YOU are in 100% control of your devices, there are certain niceities which are otherwise unavailable. But that's only if you're the type who doesn't gotta have everything done for them.
As far as you go buddy, if you like the proximity sensor that's fine. Personally I don't ****ing care what you like. thanks for a wasted Fred post which contacted my email to have me come back here to tell you what a waste of time that was thanks.
jimv1983 said:
Who needs a proximity sensor? Really? You basically answered your own question. To turn off the screen when you put it to your face so that your face doesn't press anything on the screen. Having to press the power button every time you put the phone to your face and then press it again every time you take it away from your face would suck.
Click to expand...
Click to collapse
KirkH420 said:
Yeah.....no basically pressing the power button is where it's at. It the again I'm not one who likes everything done for me. Absolutely NO PHONE I've ever owned has had a proximity sensor that was worth a ****. They all, at one time or another, allow the screen to wake up subsequently letting the microphone mute button to enable. The mute button is another piece of Android trash that needs redesigning. It is not often that mute is needed so why not out that in a drop-down menu or something since it inevitably gets pressed during calls due to a ****y proximity sensor and Screen wake setup.
I also drive a manual transmission car. Actually the last 5 cars I've owned have been manual shifted. When YOU are in 100% control of your devices, there are certain niceities which are otherwise unavailable. But that's only if you're the type who doesn't gotta have everything done for them.
As far as you go buddy, if you like the proximity sensor that's fine. Personally I don't ****ing care what you like. thanks for a wasted Fred post which contacted my email to have me come back here to tell you what a waste of time that was thanks.
Click to expand...
Click to collapse
Relax. It's not that serious.
Sent from my Pixel 2 XL using Tapatalk
No man, the point is that you quoted me so that I would be alerted to your message but didn't even attempt to input anything useful to the conversation. My post is actually a request, with explaination, asking if there is a way to do something. You on the other hand made a comment. This is XDA Developer's Forum. This isn't Facebook or YouTube where everyone has some smartass **** they can't resist saying. We is this for information. So again, thanks for your Nothing input.
EeZeEpEe said:
Relax. It's not that serious.
Click to expand...
Click to collapse
KirkH420 said:
No man, the point is that you quoted me so that I would be alerted to your message but didn't even attempt to input anything useful to the conversation. My post is actually a request, with explaination, asking if there is a way to do something. You on the other hand made a comment. This is XDA Developer's Forum. This isn't Facebook or YouTube where everyone has some smartass **** they can't resist saying. We is this for information. So again, thanks for your Nothing input.
Click to expand...
Click to collapse
I quoted you because you're so upset people don't agree with you that you can't express your frustration withOUT asterisk words. You got your answer:
"It's an option to disable proximity in gravitybox."
Move along.
Sent from my Pixel 2 XL using Tapatalk
Sure that's fine, be one of those snide Facebook commenters always gotta add their smartass quip or opinion like it's an itch you can't help but scratch. I just think it's pathetic that you get some kind of satisfaction out of that. But..... you know, everybody needs to feel like they make an impact in the world. Have a fufulling life. ?
EeZeEpEe said:
I quoted you because you're so upset people don't agree with you that you can't express your frustration with asterisk words. You got your answer:
"It's an option to disable proximity in gravitybox."
Move along.
Click to expand...
Click to collapse
.
So I assume you have earbuds, or if not, you can get some really cheap earbuds from the gas station, and when needed, you can plug it in, and it will register that it has earbuds in and will light up again, disabling the proximity sensor. You can leave it in as well, until you need it to talk, unless it will work while calling. This should work, I haven't personally tried it.
Solution
xringo said:
I'm having issues with the screen not turning back on after a call or even listening to audio messages. I have to relock and then unlock to get it to work, very annoying.
I'm on 8.1, on magisk with xposed.
Could someone recommend me an app or a module?
Click to expand...
Click to collapse
Hi,
Hope you managed to solve the issue.
If you haven't then
1. Install sensor disable from xposed repo. It's an old app so there are a few bugs when you try to remove the sensor as such.
2. Buy the Pro version or use lucky patcher to disable in app purchases for Sensor Disabler.
3. Go to the settings of Sensor Disabler and blacklist the apps that you don't want the proximity to work on.(I had problems with my WhatsApp. But it works perfectly now.)
Since proximity sensor on F3 is fairly useless/non stable on calls I compiled the [A11/A12] AOSP dialer with proximity checkbox. Install via Magisk.
Set dialer as default phone app (reboot) and check proximity ON (so proximity doesn't work anymore...)
In call :
you can either use your powerbutton or double tap on statusbar to dim screen.
or you can use a small macro add-on I made - Call_AutoScreen_On-Off_(F3) - which auto dims screen when call is started and auto lights up the screen when call is ended. How to :
install MacroDroid
import the unzipped macro
give permissions where needed (reboot/don't forget to nuke proximity in dialer ofc).
thx @anuppoudel for testing as well
Added A12 AOSP Dialer
Thank you @raystef66 for providing such a useful solution, most needed
Since I got the F3, I've gotten used to just manually locking the screen before I put the phone to my ear. So, what advantage do I get from using your modified app?
Don't get me wrong, I appreciate your work! I'm just curious...
esszett said:
Since I got the F3, I've gotten used to just manually locking the screen before I put the phone to my ear. So, what advantage do I get from using your modified app?
Don't get me wrong, I appreciate your work! I'm just curious...
Click to expand...
Click to collapse
Automation instead of manually lock
raystef66 said:
Since proximity sensor on F3 is fairly useless/non stable on calls I compiled the AOSP dialer with proximity checkbox. Install via Magisk.
Set dialer as default phone app (reboot) and check proximity ON (so proximity doesn't work anymore...)
In call :
you can either use your powerbutton or double tap on statusbar to dim screen.
or you can use a small macro add-on I made - Call_AutoScreen_On-Off_(F3) - which auto dims screen when call is started and auto lights up the screen when call is ended. How to :
install MacroDroid
import the unzipped macro
give permissions where needed (reboot/don't forget to nuke proximity in dialer ofc).
thx @anuppoudel for testing as well
Click to expand...
Click to collapse
Thanks brother. U rock!
keyoke87 said:
Automation instead of manually lock
Click to expand...
Click to collapse
Ok, thanks...
1. The screen is locked with the app, but I have to manually dim the screen by pressing the power button? Hmm...
2. When the call starts I have to switch loudspeaker on and off again before I actually can hear the one who's calling (or the one I am calling resp.) over the earpiece (is there any solution for this bug out there? or has it even been solved and I'm still doing it out of habit? ).
Unfortunately, it seems that this mod would make the whole dumb workaround procedure even more frustrating (for me)
esszett said:
Ok, thanks...
1. The screen is locked with the app, but I have to manually dim the screen by pressing the power button? Hmm...
2. When the call starts I have to switch loudspeaker on and off again before I actually can hear the one who's calling (or the one I am calling resp.) over the earpiece (is there any solution for this bug out there? or has it even been solved and I'm still doing it out of habit? ).
Unfortunately, it seems that this mod would make the whole dumb workaround procedure even more frustrating (for me)
Click to expand...
Click to collapse
U can choose not to use. Dev is sharing his solution out of goodwill anyways
esszett said:
Ok, thanks...
1. The screen is locked with the app, but I have to manually dim the screen by pressing the power button? Hmm...
2. When the call starts I have to switch loudspeaker on and off again before I actually can hear the one who's calling (or the one I am calling resp.) over the earpiece (is there any solution for this bug out there? or has it even been solved and I'm still doing it out of habit? ).
Unfortunately, it seems that this mod would make the whole dumb workaround procedure even more frustrating (for me)
Click to expand...
Click to collapse
Point of this all is to nuke proximity sensor (more stability during calls) and let the macro do the job of auto dimming the screen when call gets active and waking it up when call's done. No more no less. So no more pressing the powerbutton or whatever.
Even with the macro running during call you can easily dt2w or press power button to wake screen. Dim it again by pressing the powerbutton again (or double tap statusbar). But how many times does that happen? Not much for me.
For you it does apparently because you have to press loudspeaker. Well you can as you did before on the other dialer you had. Only thing now is that proximity is disabled as well. So more stability.
In the past even with just pressing the power button I had wake-ups during calls. Proximity is unstable so therefore diabling it is the logic solution (for me).
As mentioned above, it's up to others to use it or not.
PS : in macro you can easily add some time to it before screen auto-dims so you have time enough to tap your loudspeaker. Or even add a speakerphone task. Up to you.
keyoke87 said:
U can choose not to use. Dev is sharing his solution out of goodwill anyways
Click to expand...
Click to collapse
Unfortunately, the problem with the proximity sensor is extremely unsatisfactory - a feature that always worked reliably since my first smartphone was mightily screwed up by Xiaomi. I guess everyone who makes several calls per day is annoyed by the behavior and is looking for solutions. Therefore, it is of course highly gratifying if among the annoyed users there are also a few developers who can program solutions.
My frustration with the proximity sensor was not meant to blame the dev for not bringing a solution that works for me - the criticism is solely for Xiaomi. As I said, I appreciate the developer's work! Therefore, sorry if my post came across with a bad mood... I'm glad that the workaround app offered by the dev helps many users
@raystef66
Thank you for your answer! Earlier I was still unsure, now I know: the loudspeaker on/off "game" isn't over on my device - I just tested it. For an outgoing call, I have to deactivate the loudspeaker only after the ring tone, otherwise the earpiece remains silent. Unfortunately, this ring tone sometimes starts after 1 second, sometimes after 5 seconds - and sometimes without waiting time the call starts immediately. So, I don't think it's possible to create a universal solution with a macro.
The thing that works for me, on the other hand, is that the phone stays locked until I unlock it (lucky me! ). Initially, this accidently wake-up also happened to me, because I came to the fingerprint sensor with the index finger or thumb - but here I have now also re-educated myself
Anyway, thanks for not resigning yourself to the status quo and continuing to look for solutions!
esszett said:
Unfortunately, the problem with the proximity sensor is extremely unsatisfactory - a feature that always worked reliably since my first smartphone was mightily screwed up by Xiaomi. I guess everyone who makes several calls per day is annoyed by the behavior and is looking for solutions. Therefore, it is of course highly gratifying if among the annoyed users there are also a few developers who can program solutions.
My frustration with the proximity sensor was not meant to blame the dev for not bringing a solution that works for me - the criticism is solely for Xiaomi. As I said, I appreciate the developer's work! Therefore, sorry if my post came across with a bad mood... I'm glad that the workaround app offered by the dev helps many users
@raystef66
Thank you for your answer! Earlier I was still unsure, now I know: the loudspeaker on/off "game" isn't over on my device - I just tested it. For an outgoing call, I have to deactivate the loudspeaker only after the ring tone, otherwise the earpiece remains silent. Unfortunately, this ring tone sometimes starts after 1 second, sometimes after 5 seconds - and sometimes without waiting time the call starts immediately. So, I don't think it's possible to create a universal solution with a macro.
The thing that works for me, on the other hand, is that the phone stays locked until I unlock it (lucky me! ). Initially, this accidently wake-up also happened to me, because I came to the fingerprint sensor with the index finger or thumb - but here I have now also re-educated myself
Anyway, thanks for not resigning yourself to the status quo and continuing to look for solutions!
Click to expand...
Click to collapse
no worries. i know that the proximity sensor on this phone is just trash. cheers!
On previous version call recording didn't work fully. Therefore made a second version which provides call recording as well
Alioth_AOSP_Dialer_Proximity_raystef66_v2
Apologies if this is off topic but this thread will likely attract the right eyes.. Dialing hasnt been my big problem yet..
How do you deal with pocket wake up ?? Face unlock (maybe tap to wake ??) the position of the fingerprint reader mean this thing is constantly awake and pin lock failing in my pockets.. Driving me crazy.
EDIT :::
Testing it (pixel experience plus) my phone never senses, in any orientation.. Others report some form of sensing.
Upright.. hand to phone.. hand over phone.. I am not getting anything.
It wakes on movement.. It wakes to attempt face unlock (I guess).. It wakes on screen touch,, it never overrides that despite there being an option to prevent accidental wake up (which has no noticeable effect). I dont see what combo of settings may be correct here.
Its currently flat out unusable.. Its a mobile phone which you cannot put in your pocket and which wakes as you carry it. People cant be just accepting this...
Both ZIP files added over Magisk? Or one with TWRP and one with Magisk?
Hi,
Thanks a lot for your useful app.
In android 12 I have a problem, app background color is a very awful green! Please check attachment, what is the problem?
Thanks!
beicuxhaven said:
Both ZIP files added over Magisk? Or one with TWRP and one with Magisk?
Click to expand...
Click to collapse
AOSP dialer is a module - Other is a macro - It's all in description.
Creative9170 said:
Hi,
Thanks a lot for your useful app.
In android 12 I have a problem, app background color is a very awful green! Please check attachment, what is the problem?
Thanks!
Click to expand...
Click to collapse
Because its 11.0. Not compiled for 12.
raystef66 said:
AOSP dialer is a module - Other is a macro - It's all in description.
Because its 11.0. Not compiled for 12.
Click to expand...
Click to collapse
Can you please compile it for A12 too? Because most of the A12 roms doesn't have call recorder now. But your aosp app works good on A12 but has some minor theme problems.
Thanks in advance
Creative9170 said:
Can you please compile it for A12 too? Because most of the A12 roms doesn't have call recorder now. But your aosp app works good on A12 but has some minor theme problems.
Thanks in advance
Click to expand...
Click to collapse
I second this. I like having call recording when I call automated robot calls than I don't need to pay a attention and if I miss something I can relisten to it without a problem or with headphones if it was to quiet. It also works to set people up but in my state it's illegal to record someone who doesn't know their being recorder. So you would just be getting yourself in trouble to.
Deleted
qestion where is the call recording saved location at ?
jefffrom said:
qestion where is the call recording saved location at ?
Click to expand...
Click to collapse
internal_music_call recordings