Related
I've seen lots of people complaining that Mi A1 does not have "tap to wake" feature. I personally don't miss it since i'm using the fingerprint reader to wake and unlock in one go.
However, I've seen and tested that small free and open source app: https://play.google.com/store/apps/details?id=com.jarsilio.android.waveup
With this, you can wake phone by "waving" your hand above the proximity sensor.
I've put it on my A1 for 1,5 day now, and have seen no battery drain Developer explains:
Unfortunately, some smartphones let the CPU on while listening to the proximity sensor. This is called a wake lock and causes considerable battery drain. This isn't my fault and I cannot do anything to change this. Other phones will "go to sleep" when the screen is turned off while still listening to the proximity sensor. In this case, the battery drain is practically zero.
Click to expand...
Click to collapse
But it seems on A1 we are good to go.
I know it's not exact same feature than "tap to wake", but you might still want to give it a try if you're looking for a way to wake phone without using hardware button. As well it can wake the phone when taken out of pocket!
BtB said:
I've seen lots of people complaining that Mi A1 does not have "tap to wake" feature. I personally don't miss it since i'm using the fingerprint reader to wake and unlock in one go.
However, I've seen and tested that small free and open source app: https://play.google.com/store/apps/details?id=com.jarsilio.android.waveup
With this, you can wake phone by "waving" your hand above the proximity sensor.
I've put it on my A1 for 1,5 day now, and have seen no battery drain Developer explains:
But it seems on A1 we are good to go.
I know it's not exact same feature than "tap to wake", but you might still want to give it a try if you're looking for a way to wake phone without using hardware button. As well it can wake the phone when taken out of pocket!
Click to expand...
Click to collapse
I've just installed it, thanks for the tip !! if you have more...
Thank you very nice. Working nice so far and no high battery usage
Thx for sharing nice app
Sent from my Mi A1 using XDA Labs
First of all, thank you for the recommendation. This app is working flawlessly for now but I'm just curious about a feature. I have enabled the feature that allows to cover the proximity sensor to lock the screen. It needed device admin permission for that. Now, when I wave to wake it up, it takes me to the enter pin screen instead of fully unlocking so I have to enter the pin to unlock the device because it says that the device is locked by admin. Is there a workaround to bypass this one extra step?
ShaggyPG said:
First of all, thank you for the recommendation. This app is working flawlessly for now but I'm just curious about a feature. I have enabled the feature that allows to cover the proximity sensor to lock the screen. It needed device admin permission for that. Now, when I wave to wake it up, it takes me to the enter pin screen instead of fully unlocking so I have to enter the pin to unlock the device because it says that the device is locked by admin. Is there a workaround to bypass this one extra step?
Click to expand...
Click to collapse
This looks like the Nova's "double tap to lock" feature. If you're not rooted you need to grant admin permission to lock the screen, which requires PIN everytime you log back in.
Exactly, if you're not root, the "lock" feature is no good if you use fingerprint, I have disabled it, anyway phone goes to sleep on its own.
You should also check out KinScreen (https://play.google.com/store/apps/details?id=com.teqtic.kinscreen), it does wave to wake and also has many options to control when the screen stays on. For example, you can set it to stay on when your phone is at more than a 45° angle (like most times you're on your phone, reading something).
BtB said:
I've seen lots of people complaining that Mi A1 does not have "tap to wake" feature. I personally don't miss it since i'm using the fingerprint reader to wake and unlock in one go.
However, I've seen and tested that small free and open source app: https://play.google.com/store/apps/details?id=com.jarsilio.android.waveup
With this, you can wake phone by "waving" your hand above the proximity sensor.
I've put it on my A1 for 1,5 day now, and have seen no battery drain Developer explains:
But it seems on A1 we are good to go.
I know it's not exact same feature than "tap to wake", but you might still want to give it a try if you're looking for a way to wake phone without using hardware button. As well it can wake the phone when taken out of pocket!
Click to expand...
Click to collapse
Thanks bro
You can basically use double tap to wake with this, just enable it and tap your proximity sensor to wake.
I got the phone today, any information why double tap to wake is not possible. or activated ?
I have no idea, but I would also very much like to know. I miss my double tap...!
Same here, just received the phone: Quality seems quite good but I'm surprised this basic functionality (double tap to wake) is not available.
From what I read, if it's not implemented at kernel level then no apps can bring it to the phone ...
If anyone has more info, that would be great!
As an alternative this app can be tried. It wakes the device up by wave gesture.
It must be checked if Mi A2 Lite still goes to deep sleep mode and doesnt stay awake when app is active (hint by dev that some devices have problems)
Also it must be checked if Fingerprint is working without any issues like re-enter PIN after fingerprint unlock
Same problem, got the phone last saturday... it seems that the oreo version has it but our phone's didn't...
This ROM is extremely light so they removed most of the common features.
Let's just wait for a semi-official Lineage release for A2L.
Or you can wait until someone builds a kernel for this device. Many Kernels enable tap to wake functionally.
iLovPieNCake said:
Or you can wait until someone builds a kernel for this device. Many Kernels enable tap to wake functionally.
Click to expand...
Click to collapse
I thought the finger print sensor would make tap to wake useless lol.
I got the phone 3 days ago. Double-tap to wake works from day one.
I really wish I could turn it OFF.
Ambient Light is Off, TalkBalk is Off but phone still wakes up in my pocket all the time.
Anyone know how to turn this feature Off please?
alfiean said:
I got the phone 3 days ago. Double-tap to wake works from day one.
I really wish I could turn it OFF.
Ambient Light is Off, TalkBalk is Off but phone still wakes up in my pocket all the time.
Anyone know how to turn this feature Off please?
Click to expand...
Click to collapse
As it turns out, this phone comes with two types of display CSOT & EBBG.On csot, the double tap works, but it can not be turned off, and on ebbg it does not work.
alfiean said:
I got the phone 3 days ago. Double-tap to wake works from day one.
I really wish I could turn it OFF.
Ambient Light is Off, TalkBalk is Off but phone still wakes up in my pocket all the time.
Anyone know how to turn this feature Off please?
Click to expand...
Click to collapse
can u show us the d2tw option? with a little vid maybe
mrmcphisto77 said:
can u show us the d2tw option? with a little vid maybe
Click to expand...
Click to collapse
Sure
I am on mi a2 lite. No d2tw here
mrmcphisto77 said:
I am on mi a2 lite. No d2tw here
Click to expand...
Click to collapse
On stock Launcher?
I am not liking this feature at all, wish I could stop it.
alfiean said:
On stock Launcher?
I am not liking this feature at all, wish I could stop it.
Click to expand...
Click to collapse
yes stock launcher and even if i install alternative launcher, since not rooted, every tme i lock screen with double tap to sleep it asks for pin, sequence or other, very annoying...
mrmcphisto77 said:
yes stock launcher and even if i install alternative launcher, since not rooted, every tme i lock screen with double tap to sleep it asks for pin, sequence or other, very annoying...
Click to expand...
Click to collapse
Strangely, on my A2 Lite, double tap only wakes up the screen. Double tapping when screen is awake does nothing at all.
I emailed Xiaomi Support about this, asking how I could disable the waking up. The reply came from Xiaomi Support Malaysia:
Go to the Settings - Select Accessibility - Select advanced settings - Turn on the pocket mode option
I replied, "There is no Advanced Settings under Accessibility. There is also no setting available when I search for pocket or double or tap twice."
Their advice was to backup and perform a Factory Reset, which I think is nonsense.
alfiean said:
Strangely, on my A2 Lite, double tap only wakes up the screen. Double tapping when screen is awake does nothing at all.
I emailed Xiaomi Support about this, asking how I could disable the waking up. The reply came from Xiaomi Support Malaysia:
Go to the Settings - Select Accessibility - Select advanced settings - Turn on the pocket mode option
I replied, "There is no Advanced Settings under Accessibility. There is also no setting available when I search for pocket or double or tap twice."
Their advice was to backup and perform a Factory Reset, which I think is nonsense.
Click to expand...
Click to collapse
well... no options like those for me too... it is really frustrating...
luiszevs said:
As it turns out, this phone comes with two types of display CSOT & EBBG.On csot, the double tap works, but it can not be turned off, and on ebbg it does not work.
Click to expand...
Click to collapse
What application is in the screenshots?
Akbhar said:
What application is in the screenshots?
Click to expand...
Click to collapse
*#*#6484#*#* line #1
so there are 2 version of A2 Lite which has and has no double tap to wake, we have to accept it as they are, but which is better or worse?
From few days. My A50 is getting automatically unlocks in my pocket. Is anyone is facing the same issue ??
Please specify more details. What do you mean by automatically unlocks? You get an alert or something? Does it unlock and launch apps on it's own when you place it in your pocket? Which biometric methods are turned on and is Google smart lock on?
Sometimes a random app opens when i check my phone. Currently i am using fingerprint unlock method for my device.
To prevent that, turn on Accidental Touch option and cure the phone
Sent from my SM-A505FN using Tapatalk
Accidental touch option is already on.
Check some apps installed. Maybe some of them making trouble.
On my phone, all's good. Hmmm.
My A50 is getting automatically unlocks in my pocket. I am also facing the same issue. I am using biometrics and faceunlock . Accidental touch is also turned on. Whats the use of secuirty if it can be unlocked my pocket can unlock this phone without biometrics and face. I face so many times in a day. I read samsung s10 also facing this same issue.
coolparmeetsingh said:
Sometimes a random app opens when i check my phone. Currently i am using fingerprint unlock method for my device.
Click to expand...
Click to collapse
Hey I am not having any issue like that. Turn off your facial recognition and see if it still happens.
therealroyston2 said:
Hey I am not having any issue like that. Turn off your facial recognition and see if it still happens.
Click to expand...
Click to collapse
Yes it happens
harman8791 said:
Yes it happens
Click to expand...
Click to collapse
Smart lock or anything on?
Listen, turn off all biometric methods and only keep pin/pattern and see?
Sent from my Samsung Galaxy A50 using XDA Labs
I am facing the same issue. My phone become hot, and there is a message that biometric unlock fail for 5 times and I have to insert the pin. Meanwhile, the battery drained at least 7-8%
heat is normal while playing game, may b u shud try hard reset. Hope it will solve problem. I am using face unlock coz biometric unlocks takes time to unlock. Biometric i use rarely sometimes may b our screen has sometimes white layer of dust or oily . So that can be the reason for fngerprint problem.
Maybe u are using smart lock
Hi, Please check if you are using trusted location or device. If that option turned on turn off trusted location or device. I can not surely tell you where the option is because I will receive my device tomorrow. but there must be a option.
Just visit a service centre. Its already in warranty period. So dont worry.
a50 unlocks
harman8791 said:
My A50 is getting automatically unlocks in my pocket. I am also facing the same issue. I am using biometrics and faceunlock . Accidental touch is also turned on. Whats the use of secuirty if it can be unlocked my pocket can unlock this phone without biometrics and face. I face so many times in a day. I read samsung s10 also facing this same issue.
Click to expand...
Click to collapse
Hi all ,
My samsung A50 also have the same problem , automatically unlocking while in pocket on driving, tried different settings as per various suggestions, such as accidental touch, home screen app changes, disabling of trusted devices,on body detection..etc..etc....
But no use, the issue existing .
But after a recent setting change, now its ok , some days over, till no problem. Try it , May be its workout .
And reply me the result ,...
Firstly make sure , all the normal settings are ok , accidental touch protection enabled /also disable the on body detection , trusted devices/ driving, ....the same is in the link of Smart Lock .
Then
Advanced Features - Motions & Gestures - disable the lift to wake & double tap to wake.
Other items will enable no problem , such as smart stay,alert,easy mute .
Try it and reply
Go to settings ---》 smart lock --》voice match --》while driving (turn off)
Same issue on my A70.
The "Accidental touch protection" feature doesn't seem to do anything. Maybe because it doesn't have a sensor, just the camera? Either way, the software is bugged.
I ended up turning off "Double tap to wake", as I don't really need that.
I also have the same problem that the phone unlocks in my pocket.
So iam trying now the options above to turn off some options.
I'll let know if it will work or not.
Yes my divice also unlocking automatically while in pocket
Hi all
Several times here I had raised a question about not working mode "In pocket", but still no progress.
Just today I made a sprint and flashed several different ROMs (Havoc, crDroid, AEX, AICP, Viper, Colt, RR, and lot of others brands and versions a little bit earlier). Wiped, flashed rom + magisk, booted to new rom, set pocket mode on, rebooted (just for sure) and made a simple test:
locked phone by power button then closed a proximity sensor (left to the speaker on the top), then pressed the power button and always got the same result: regardless that proximity still closed (like in pocket), the lock screen is appearing and I can press playback buttons or unlock the phone. The only Syberia doesn't have this bug (but have some another, preventing me from using it).
Am I "the only one" who want to be sure that your smart will never awake in your pocket (when, for example, some notification will arrive) and start its own life, pressing all that will be available on lockscreen? So, common as a fundamental feature and ... it's not working for a very long time. What's ...? Maybe I missed some well-known trick on how to make it properly work?
comunity said:
Hi all
Several times here I had raised a question about not working mode "In pocket", but still no progress.
Just today I made a sprint and flashed several different ROMs. Wiped, flashed rom + magisk, booted to new rom, set pocket mode on, rebooted (just for sure) and made a simple test:
locked phone by power button then closed a proximity sensor (left to the speaker on the top), then pressed the power button and always got the same result: regardless that proximity still closed (like in pocket), the lock screen is appearing and I can press playback buttons or unlock the phone. The only Syberia doesn't have this bug (but have some another, preventing me from usin it).
Am I "the only one" who want to be sure that your smart will never awake in your pocket (when, for example, some notification will arrive) and start its own life, pressing all that will be available on lockscreen? So, common as a fundamental feature and ... it's not working for a very long time. What's ...? Maybe I missed some well-known trick on how to make it properly work?
Click to expand...
Click to collapse
Try Syberia 2.8 https://forum.xda-developers.com/lenovo-p2/development/rom-syberia-os-v2-8-t3958209
VladSor said:
Try Syberia 2.8 https://forum.xda-developers.com/lenovo-p2/development/rom-syberia-os-v2-8-t3958209
Click to expand...
Click to collapse
I tried... unfortunately, it works very "unstable" with LuckyPacther's Market and Google Pay, as for me ((
comunity said:
I tried... unfortunately, it works very "unstable" with LuckyPacther's Market and Google Pay, as for me ((
Click to expand...
Click to collapse
You are very similar to one of my countryman :laugh:
VladSor said:
You are very similar to one
Click to expand...
Click to collapse
I need a very small set of properly working stuff: Magisk with its MagiskHide, LuckyPatcher and its market, Google Pay working with the previous couple, Working Swift Installer and ... pocket mode. that's it
nevertheless, so easy for the testing feature is not working. it looks like QA is living somewhere in 4-th or 5-th dimension
In LOS16 Pocket mode is not working (
I assume, that this is a source for not working PM in all another custom ROM - a lot of them are using LOS16 as a base for their work. sadly...
May I ask moderator(s) move this question back to ROMs thread where I initially place it?
This is the only way (as it seems to me) to attract ROM builders at last fix this really annoying bug!
New ROMs' versions regularly appears, but ... who care? ((
Working "In pocket" mode. For any firmware!
Finally solved the problem forever.
You must use Automagic or any other automation tool that supports the following commands sequence:
- The screen turns on (trigger event)
- Immediately lock the device!
- Check the distance of the proximity sensor:
***- if <5cm - do nothing
***- if> 5cm - turn on the screen (smart not in your pocket)
Immediately locking is required because it takes 1-2 seconds to measure the distance and during this time you may press something on already switched on screen.
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