Develop Bugs

locking/unlocking programs and battery consumption

i was wondering if i could get sum people to tell me about ehir experiences with their locking/unlocking programs...such as, which ones youve used with success...im interested in knowing which ones use the least about of battery power, least amount of memory/ram...so on and so forth...any input wiould be greatly appreciated
specifically programs being used with the touch pro 2

I'm personally not a big fan of screen lock programs. I just think that for something as simple as locking the screen, the end-user shouldn't have to give up anything in terms of resources/battery life.
That's why I suggest sticking with the default WinMo lock.
I suggest either SmartLock or LockDevice to auto lock your device. Neither uses up any resources.

I've perused the threads concerning both the locking apps you cite above, but both appear to have some issues (i.e. not everything working properly after the install). I'm specifically looking for a way to have the screen locked when the device is turned on, mostly because I carry the thing in my pocket (yes, with a screen protector) and want to be sure that if I should inadvertently bump the power button I don't end up calling friends overseas from the inside of my pocket. It doesn't appear to me as if the default locking app can do this (and not simply turn on the lock after a timeout) -- or am I missing something?

pistou said:
I've perused the threads concerning both the locking apps you cite above, but both appear to have some issues (i.e. not everything working properly after the install). I'm specifically looking for a way to have the screen locked when the device is turned on, mostly because I carry the thing in my pocket (yes, with a screen protector) and want to be sure that if I should inadvertently bump the power button I don't end up calling friends overseas from the inside of my pocket. It doesn't appear to me as if the default locking app can do this (and not simply turn on the lock after a timeout) -- or am I missing something?
Click to expand...
Click to collapse
I've used both of those apps and it works fine for me. I have the exact same concern that you have. I don't want the device to wake because someone called and hung up after a second, thus making the screen susceptible to taps.
In both apps, you can customize how you want the lock mechanism to kick in. You can set it to lock when you screen goes off. My personal preference is to set it to lock on suspend.
I'm not really sure what you mean. If your device is locked (with the WinMo default lock), you won't be able to do anything (including making calls) without unlocking it first either via tap & slide (WinMo 6.5) or left soft key & unlock button (WinMo 6.1).

I would really like to use the app, but there is a dialer conflict when getting incoming calls for boths apps. For example during an incoming call, I initially get HTC dialer. During the middle of the call, I get the original WM dialer. Do you have any suggestions to avoid this problem?

ohyeahar said:
pistou said:
I've perused the threads concerning both the locking apps you cite above, but both appear to have some issues (i.e. not everything working properly after the install). I'm specifically looking for a way to have the screen locked when the device is turned on, mostly because I carry the thing in my pocket (yes, with a screen protector) and want to be sure that if I should inadvertently bump the power button I don't end up calling friends overseas from the inside of my pocket. It doesn't appear to me as if the default locking app can do this (and not simply turn on the lock after a timeout) -- or am I missing something?
Click to expand...
Click to collapse
I've used both of those apps and it works fine for me. I have the exact same concern that you have. I don't want the device to wake because someone called and hung up after a second, thus making the screen susceptible to taps.
In both apps, you can customize how you want the lock mechanism to kick in. You can set it to lock when you screen goes off. My personal preference is to set it to lock on suspend.
Click to expand...
Click to collapse
Thanks: I've loaded lockDevice and so far so good
ohyeahar said:
I'm not really sure what you mean. If your device is locked (with the WinMo default lock), you won't be able to do anything (including making calls) without unlocking it first either via tap & slide (WinMo 6.5) or left soft key & unlock button (WinMo 6.1).
Click to expand...
Click to collapse
What I meant was that my understanding of the default WinMo lock is that it only locks after a specific period of in activity (which I don't want to happen) rather than after a suspend (which is what I do want).

[CM 12] Double tap 2 wake "disappear" fix

Currently dt2w doesn't work properly in CM 12, at least for some devices.
Because dt2w caused "black screen after call" issues, they patched it in this commit:
http://review.cyanogenmod.org/#/c/84385/
But it is not effective.
There are cases when this feature doesn't recognize that the call ended and leaves dt2w disabled.
Few examples would be: when you end call with power button; when callee hangs up the phone while you hold the phone near your face.
Basically it happens when call ends with proximity lock active.
It might even be the reason for another bug, "screen freeze after phone call", but I need more testing to be sure.
It is hard to tell why it happens, maybe it's because LG hardware/drivers, combination of both or something else. It seems G3 doesn't like when additional features "attached" to proximity sensor lock.
I even tried to report this bug, still nothing.
https://jira.cyanogenmod.org/browse/NIGHTLIES-948
So right now I'm trying to fix this, but still most important part yet to be done.
I reverted 84385 commit, but it brought me back to the state where double tap on screen during the call with proximity lock active recognized as dt2w. It just leaves the device with black screen after call. Kinda obvious.If I just turn off dt2w in settings it fixes the issue, but then I don't have this feature on my phone at all.
So far I tried different things to fix this issue:
- Modified /kernel/lge/g3/drivers/input/touchscreen/lge_touch_core.c, after that can't even finish the build.
- Tried to add feature from 84385 commit to /packages/apps/InCallUI/src/com/android/incallui/ProximitySensor.java, now incallui just crashes every time I try to make the call.
- GravityboxLP actually has the feature to disable dt2w while proximity sensor is covered, but for some reason it doesn't work while in phone call (only when screen just turned off).
- Same goes for https://github.com/SlimRoms/device_lge_g3-common/commit/5a8f935bdfc129f6fa3f906afa83f77c2c9084c1
- Various apps from PlayStore - nothing helps
What could actually work - if it was possible to find or implement thing like:
if (IsScreenBlank() && !in_phonecall) {
Log.d(this, "DT2W activated");
***.turnOnTapToWake();
}

Mate try contacting galaid he found a fix in his cm11 thread....

Device wake issues (power button ignoring first press)..

Hi,
I've had my M9 for a couple of weeks now, and slowly getting it to work how I want it to. One thing nagging me is this weird issue I have with waking the device from sleep.
I have tried to disable all the gesture/smart wake features (double tap the screen, etc). The issue I'm having seems to relate to the light and/or proximity sensor. It seems (and I haven't been able to find any info on this, online or on the phone) that there is a feature which will enable the device to wake up when being picked up or taken out of my pocket. This doesn't always work, but sometimes it does. When I pull my phone from my pocket, it will sometimes wake up. When I glide my finger over the front camera & light sensor, it will sometimes wake up. This is a minor annoyance, as I would like to only be able to wake my device by hitting the power button.
It gets really annoying when these 'gesture' wakes start to interfere with the power button wake. For example (and this is happening more often than not), when I pull my phone out of my pocket, the phone is off, then I hit the power button once, and the phone still doesn't wake. Hitting the power button a second time will wake the device. It seems to me that the smart waking is some how interfering with the manual waking.
Is anyone else seeing this behavior?
Any suggestions for a solution?
Thanks a lot for any help.

This is really odd considering the M9 doesn't support air gestures. Sorry, I have no solution, but is it possible you may have installed an app that may be causing this?

I would think two button push would be the normal, otherwise you could accidentally hit it once and turn the screen on. Do you have Ambient display and pocket detection all turned off ?
Gravity Screen in the play store gives you total control of all that stuff

That for the replies guys.
Clsa, there is no way to disable ambient display & pocket detect because those features do not exist on the M9 (at least... Not that I have found). That's what is bugging me.
I don't think the 2 button press is normal. I've never had to do it on previous phones.
Fernand - not sure if it is another app causing it. I think I have no extra apps installed compared to my last phone.
I just tried Gravity Screen, and it seems to just give me the ability to enable all the features I want to disable.
Any other suggestions?

[email protected] said:
That for the replies guys.
Clsa, there is no way to disable ambient display & pocket detect because those features do not exist on the M9 (at least... Not that I have found). That's what is bugging me.
I don't think the 2 button press is normal. I've never had to do it on previous phones.
Fernand - not sure if it is another app causing it. I think I have no extra apps installed compared to my last phone.
I just tried Gravity Screen, and it seems to just give me the ability to enable all the features I want to disable.
Any other suggestions?
Click to expand...
Click to collapse
Settings / Display & Gestures / Ambient display (Wake screen when device is picked up or notifications arrive)
Pocket Detection is part of some Rom Tweaks (insertcoin & viperOne if i remember right)

Hi again, that option is not available on my phone. Do you see it on your M9?
I don't have a custom ROM. Not rooted either.

[email protected] said:
Hi again, that option is not available on my phone. Do you see it on your M9?
I don't have a custom ROM. Not rooted either.
Click to expand...
Click to collapse
Yes I have it, but I'm on LeeDroid right now. He adds so much stuff i forget whats "custom" and whats stock

Got the same issue
The power button will ignore the first push while standing by for a long time. Thought it might be caused by apps like greentify?

Hi Ducati, is that a fact or is that just how you understand it? Seems strange that that would be intentional. But it definitely seems to be the case.
I do not have greenify installed either.
Do you get similar behaviour on your One?

After a bit more testing. I can confirm that there are some sort of air gestures on this device. I can wave my finger in front of the front light sensor/camera, and the device will wake.
This doesn't happen all the time, I am not always able to reproduce this. But right now, it is happening. Can anyone else reproduce this?
http://somevid.com/N1OnU8JS

I have the same issue on my M9. Glad I found this thread. Thought my power button was defective.
I can't activate any gestures by waving my hand.
I think it's happening mostly when waking from deep sleep.

I know it's an old thread, but I just installed CyanogenMod 12.1 and I guess my google-fu is rusty. I find that if I hit the power button in quick succession (double click) it turns off the phone. Anyone know how I can stop this?
By quick succession I mean multiple times within 20 seconds

Any way to disable the proximity sensor?

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.)

Themes / Apps / Mods [APP][11.0][12.1][13.0] AOSP DIALER with Proximity checkbox (call recorder incl) + macro

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