Develop Bugs

HTC Phone Lock (Transparent)

Hi All,
Does anyone know how to get this working on our beloved HD's? I hate the way the screen goes completely black during a call, we can't use the light sensor to tell the phone that the call has finished and it is away from your ear (so screen comes back on a la iphone), and i keep doing things during a call with my ear!!
So this seems like the ideal solution - but i can't get it to work!!
I've copied over the file to the windows folder, then soft reset. Changed the registry entry for phoneLockEnable to 1 in HKLM/Software/HTC/Phone but still no joy!
All help would be greatly appreciated.
Regards
DF

hi, where you found out this software? it look's great, can you share the link to me? recall i saw some post like this, but just for diamond, i'm looking one for my hd, is there anyone have?

chanmama said:
hi, where you found out this software? it look's great, can you share the link to me? recall i saw some post like this, but just for diamond, i'm looking one for my hd, is there anyone have?
Click to expand...
Click to collapse
Sorry, i don't have the cab file, i just saw the screenshot and thought 'that's what i need'!!!
Hopefully some bright spark here can help us both (and others probably).
Regards
DF

Beside this transparent canvas, where can I get the orginal canvas?
I am using a offical ROM but I don't see this function!

I hate the way the screen goes completely black during a call, we can't use the light sensor to tell the phone that the call has finished and it is away from your ear (so screen comes back on a la iphone), and i keep doing things during a call with my ear!!
Click to expand...
Click to collapse
that's interesting, because my screen doesn't go blank during calls and it happens quite often that i accidently disconnect a call (i suppose because i hit a button with my ear).
so in search for i solution i found in Advanced config a tab Light sensor > Light sensor polling which i set enabled. the explanation says "uses light sensor to automatically turn screen off when the phone come near from your ear to answer a call". so this should set it like the i-phone does, right?
hence when i tested it, the screen still was on, even when i put my thumb onto the light-sensor.
is this because i don't have a stock rom (i use Duttys HD V1.9b XTREME) or is there something i can do about it.
it would be really nice to have the screen locked when i answer a call and to outomatically unlock it if i remove it from my head to use some function on the screen..

take55 said:
that's interesting, because my screen doesn't go blank during calls and it happens quite often that i accidently disconnect a call (i suppose because i hit a button with my ear).
so in search for i solution i found in Advanced config a tab Light sensor > Light sensor polling which i set enabled. the explanation says "uses light sensor to automatically turn screen off when the phone come near from your ear to answer a call". so this should set it like the i-phone does, right?
hence when i tested it, the screen still was on, even when i put my thumb onto the light-sensor.
is this because i don't have a stock rom (i use Duttys HD V1.9b XTREME) or is there something i can do about it.
it would be really nice to have the screen locked when i answer a call and to outomatically unlock it if i remove it from my head to use some function on the screen..
Click to expand...
Click to collapse
Hi take55,
Yes, i'm aware of the advanced config tweak (also in HD Tweak), and as you correctly state, the screen should/will go blank on call connection (i'm running kwbr's A Touch Of HD 3.3.4 and mine doesn't, even with tweak applied!!).
Unfortunately, when the call ends and you move the phone away from your ear, the screen still stays blank????? I've read somewhere on these forums that it never will work like the iphone (not sure why, as the light sensor should recognise that we've moved the phone away from our ears).
So that is why i'm trying to get this other method to work. What i have noticed is that with the bmp copied over to the windows folder or with a cab i found by A-Math installed, my dialler locks up after every call (as if the transparent phone lock is in place) but i can't actually see it. None of the screen works and i have to soft reset. Maybe something is stopping the bmp to show on the phone....who knows.
It also might be the fact that this was designed for the Diamond (found the cab on the Diamond forums).
Just hoping some genius here might now how to sort this.
I've attached the cab file i've found, give it a try and see if you have the same issue as me.
Regards
DF

chanmama said:
hi, where you found out this software? it look's great, can you share the link to me? recall i saw some post like this, but just for diamond, i'm looking one for my hd, is there anyone have?
Click to expand...
Click to collapse
Hi chanmama,
Found the cab file for you, see previous post.
Regards
DF

Datafanatic said:
What i have noticed is that with the bmp copied over to the windows folder or with a cab i found by A-Math installed, my dialler locks up after every call (as if the transparent phone lock is in place) but i can't actually see it. None of the screen works and i have to soft reset. Maybe something is stopping the bmp to show on the phone....who knows.
Click to expand...
Click to collapse
It has nothing to do with the BMPs but with the registry setting that the CAB also makes. It sets HKLM\Software\HTC\Phone\PhoneLockEnable to 1, in wich case you'll have to press the power button to unock (no need to soft reset). For the BMP to work the phone/dialer software will have to support it, otherwise it just locks the phone in the usual way: black screen, power button to unlock.

Datafanatic said:
Hi chanmama,
Found the cab file for you, see previous post.
Regards
DF
Click to expand...
Click to collapse
tks but your cab only for the canvas skin only, do not contain the original software (slidable canvas), anyway, tks for your help

I've also found this problem to be quite annoying during a phone call but have found some sort of way to deal with it.
Firstly my ROM isn't tweaked, its just the basic one already installed.
After a call is connected, the screen switches off. But if you need to access the screen again during a call, I just press the "Back Arrow" key, one of the four hard buttons on the bottom which brings the screen back up again.
If you press the phone button instead whilst the screen is off, the screen lights up again but it puts the call on hold.
This probably isn't the best way to deal with this, but it seems to work for me for the time being, hope this helps anyone else here.

rubbermonkey123 said:
I've also found this problem to be quite annoying during a phone call but have found some sort of way to deal with it.
Firstly my ROM isn't tweaked, its just the basic one already installed.
After a call is connected, the screen switches off. But if you need to access the screen again during a call, I just press the "Back Arrow" key, one of the four hard buttons on the bottom which brings the screen back up again.
If you press the phone button instead whilst the screen is off, the screen lights up again but it puts the call on hold.
This probably isn't the best way to deal with this, but it seems to work for me for the time being, hope this helps anyone else here.
Click to expand...
Click to collapse
Useful info - I found this particularly annoying yesterday during a ouple of calls.
Also discovered Gyrator tries to turn the phone screen and was laggy - which was even more annoying!

Everyone!!!
CHECK THIS OUT - http://forum.xda-developers.com/showthread.php?t=489034
Answer to all our prayers - a screen lock which uses the g-sensor and not the light sensor.
Now, when a call is connected, holding the phone to the ear blacks the screen, but when you bring the phone down (to use the keypad or something), THE SCREEN COMES BACK ON!!!!!!!
Tried and tested on kwbr's A Touch Of HD v3.3.4 (probably the best manila2 ROM out there!)
Regards
DF

[Q] Gyro sensor not working

I've just discovered that my gyro sensor doesn't work. I am running rooted stock 4.1.1. The phone can not detect tilt movements. And under Settings->Motion->Sensitivity settings->Gyroscope calibration, the blue dot does not move from the center, no matter which orientation the phone is held. All of the options under Motion don't seem to work. I just want to see if anybody else has the same problem before calling TMobile.

Firstly, this should have been posted in the q&a section.
And the blue circle isn't supposed to move. You lay the phone on a flat surface and it calibrates itself.
Sent from my SGH-T999 using Tapatalk 2

Moved to Q&A

Sorry for posting in the wrong section. You are right about the blue dot not moving. I downloaded a few apps that detect sensors and all built-in sensor seem to be working as they are supposed too. I have problem for example of taking screenshot with a palm wipe or zooming picture by tilting the device, muting phone by turning it over, etc. None of these features work on my phone. Will try to explore more to see what the real problem is.

tphone said:
Sorry for posting in the wrong section. You are right about the blue dot not moving. I downloaded a few apps that detect sensors and all built-in sensor seem to be working as they are supposed too. I have problem for example of taking screenshot with a palm wipe or zooming picture by tilting the device, muting phone by turning it over, etc. None of these features work on my phone. Will try to explore more to see what the real problem is.
Click to expand...
Click to collapse
Do you have the switch turned on next to motion in the settings?
Sent from my SGH-T999 using Tapatalk 2

tphone said:
I've just discovered that my gyro sensor doesn't work. I am running rooted stock 4.1.1. The phone can not detect tilt movements. And under Settings->Motion->Sensitivity settings->Gyroscope calibration, the blue dot does not move from the center, no matter which orientation the phone is held. All of the options under Motion don't seem to work. I just want to see if anybody else has the same problem before calling TMobile.
Click to expand...
Click to collapse
Before you go off the deep end, run the test on the sensor.
in the stock dialer:
Quick Test Menu
*#7353#
select the accelerometer tester and ilt the phone whatever way you want. If the arrows don't change, then the sensor isn't working. If the Arrows do change, then all good, no panic necessary...
Good Luck
Aloha

Thank you for your help. I ran the sensor test and the sensors work. I also turned on the Motion switch but the Motion features still don't work for me. Maybe this is a software issue. I will continue to explore and will report back if I've found something.

tphone said:
Thank you for your help. I ran the sensor test and the sensors work. I also turned on the Motion switch but the Motion features still don't work for me. Maybe this is a software issue. I will continue to explore and will report back if I've found something.
Click to expand...
Click to collapse
Hi,
Please do the following:
Pull the top notification bar down by using a downward swipe.
Tap on the Toothed Wheel in upper right corner
scroll down till you see the System divider (below the Add account line)
is Motion ON on the right side of it? if not, turn it on.
Tap on the word Motion
Are any of the options you want to use set with a check in the box?
if not, put the check in whatever you want to use by tapping on the box on the right of the function.
Example:
If you want to use Palm swipe for screen captures, tap on the box on the right of the option.
the boxes toggle these options so if you want the option off, then tap on the checkmark and it'll go off.
When you're done, click on the back button on the right side of the menu bar below the screen till you get back to the homescreen.
You are done, and the selected options should now function.
simple huh?

Thank you, bobolinko. I've been doing exactly what you described and no motion feature works for me. I begin to think that my software has a problem, because it does crash occasionally and software upgrade check hangs forever in the "checking for software updates..." screen and never comes back, no matter if I am on wifi or on 4G. Let me reinstall stock firmware and report back.

Try it like this:
http://www.youtube.com/watch?v=T4dPoY1Z6hc
Also, has it EVER worked?
Thanks!

bobolinko said:
Also, has it EVER worked?
Click to expand...
Click to collapse
Thanks for the video. I did exactly as shown and nothing happens. I never tried Motion before until I needed to capture my screen and discovered that it doesn't work for me. In the mean time, using PWR and HOME button at the same time does allow me to capture the screen, so I don't really need Motion feature working for me. I am just thinking that my software has a problem and I will need to reinstall stock. Thanks a lot for your help in any case.

bobolinko said:
Before you go off the deep end, run the test on the sensor.
in the stock dialer:
Quick Test Menu
*#7353#
select the accelerometer tester and ilt the phone whatever way you want. If the arrows don't change, then the sensor isn't working. If the Arrows do change, then all good, no panic necessary...
Good Luck
Aloha
Click to expand...
Click to collapse
im having the same issue. tried the accelerometer test and tilt the phone every which way but the arror didnt move at all. does that mean the accelerometer is done with. any fix for it?
also tried tsp dot mode, tsp grid mode, proximity and light sensors and nothing seems to happen during the test

Prevent Bluetooth App "Always On Top" while connected?

I've noticed that when I receive a call, the Bluetooth incoming call app forces itself over whatever I've got on the screen. That's fine while I'm answering, and convenient for hanging up... but it ALSO covers up things like navigation which I sometimes WANT to be active while I'm on a call.
Is there any way to force the bluetooth app to go away once I've answered?

same question here..............

Same. Looking for solution to this issue. Is there any other ROM that allows to minimize/hide the ongoing call bar?

Bump

I do not have a 'fix' but a work around for outgoing calls. Bring up dial/Bluetooth screen dial your number and once connected just hit the home button. (this only works on full-screen Bluetooth). This does little for incoming calls. Yeah, I know not much of a fix, but at least you can make outgoing calls and still use your maps, etc.
Zeek

There is a transparency mod that would at least show whats behind, i.e. if you were using GPS you wouldn't lose the map viewing.

jakejm79 said:
There is a transparency mod that would at least show whats behind, i.e. if you were using GPS you wouldn't lose the map viewing.
Click to expand...
Click to collapse
How do I get this transparency mod?

w4audi said:
How do I get this transparency mod?
Click to expand...
Click to collapse
I don't remember, I just remember reading about it somewhere, I think it might have been in the software section or an xposed module.

I really hope this can somehow be fixed. I cannot believe they'd design this system to be useless while on a phone call.
Dave

I think this is what I remember seeing:
http://forum.xda-developers.com/showpost.php?p=61199557&postcount=13697

This worked for me
jakejm79 said:
I think this is what I remember seeing:
http://forum.xda-developers.com/showpost.php?p=61199557&postcount=13697
Click to expand...
Click to collapse
The vendor that I purchased my Eonon unit from sent me an updated firmware hoping to fix an issue with the volume control - while it didn't help that, i noticed that the in-call pop-up had a button that allowed you to minimize the pop-up - the screen is still locked, but it moves the pop-up out of the way of the Waze info at the bottom of the screen - I took the attached APK, copied it into the system/apps/mtcblutooth folder - i renamed the existing apk by adding .old to the end, then renamed the copied APK to exactly what the original apk was names - after reboot, I had the new pop up - it also changes the full-screen bluetooth screen slightly, I like it better - hope this helps - FYI,you'll need Root Explorer or something similar to access the root files -

I'm going to try this. It's above my pay grade but i'm going to decompile this and the other to see the differences.
I did install it and it works as designed. Problem is if you are taking a call or making a call you'll not have you navigation in the foreground to see it. So if you do already have it running, at least in waze, you can drag down from the top and press on waze to see it again. Other apps you cannot and it still locks you from opening any other apps unless they're in the navigation bar to begin with.
Dave

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