Develop Bugs

Incoming call notification bug?

I'm running the Eragon v6.7 rom - fantastic work by Skeleton.
I use the Elephone smart view cover and have 2 SIM's fitted.
I've become aware of what may be a small (but inconvenient) bug and wonder if anyone else has experienced this...
Phone is in standby and the screen is off.
Incoming call is received and phone rings. Display remains off - i.e. nothing visible in the round clock window.
I open the cover - display wakes up but still no call is displayed.
I unlock the screen using the fingerprint scanner.
When screen unlocked the incoming call is shown in the notification area at the top of the screen.
Should not the incoming call wake the phone and enable me to see which SIM and from whom the call is from?
Is there a setting somewhere I'm missing?
Does anyone running a stock ROM know if the issue/problem is there also?
By the way, if the screen is still active, i.e. the clock is visible in the smart view case window then the incoming call displays showing caller and which SIM.
Any comments appreciated.
Thanks
Mike

Answering calls

My Dad recently bought a Moto G5. It's his first smart phone and it's hard for him to get used to. The biggest issue at the moment is that he has problems answering calls. He just can't get used to the swiping.
He lives about 400 kilometers away from me so I can't just hop by and help him. So I wanted to ask if there are any settings on this phone which allow answering calls by a gesture or by pressing the power button or the fingerprint sensor or anything like that? If not, is there any app for this? Or a (trusted) dialer which has more (or other;easier) answering options? The phone doesn't have root ofc.

Frankie73 said:
My Dad recently bought a Moto G5. It's his first smart phone and it's hard for him to get used to. The biggest issue at the moment is that he has problems answering calls. He just can't get used to the swiping.
He lives about 400 kilometers away from me so I can't just hop by and help him. So I wanted to ask if there are any settings on this phone which allow answering calls by a gesture or by pressing the power button or the fingerprint sensor or anything like that? If not, is there any app for this? Or a (trusted) dialer which has more (or other;easier) answering options? The phone doesn't have root ofc.
Click to expand...
Click to collapse
I know this is a setting on lineageos os but I'm not sure about stock as I'm not currently running it
Goto settings
Buttons
Answer call > enable to answer call with volume buttons
You can also enable end call with power button

Unfortunately this setting isn't present on the stock rom. Thanks anyway!

1) Disable Unlock Swipe when taking or rejecting a call. 2) Blue lines at top

The answer may be right in front of my nose, but I've searched and can't find it:
1) Why do I have to swipe to unlock phone before accepting or rejecting an incoming call? Is there a way to disable this? My Moto Z did not have this, or ANY other phone I have ever had. Very annoying extra step.
2) There are two active blue lines at top of screen, one long, one short. I get that they are additional battery status indicators, but what if I don't want them? How to disable?

I think those are apps you have installed which are causing the "problem", because no one else is facing this issue.

victorhbm15 said:
I think those are apps you have installed which are causing the "problem", because no one else is facing this issue.
Click to expand...
Click to collapse
Well, that's a relief . . . now to figure out the culprit - I did a transfer of apps and data from my Moto Z, can't think of what else I might have added or enabled in the 2 days I've had the new phone!
Update:
The unlock swipe is an option in Tiny Call Confirm, now unticked.
The battery info lines are options in 3C Battery Monitor Widget. Shows battery percentage and temperature, but I found it more distracting than useful.

Call answering bug

When somebody calling me and I pick up, I can make conversation but phone is stuck on ringing mode, and after few moments hang up phone call, and I have missed call...
Somebody else have this problem? How can I fix this?

I dont have this problem.

pogano_celjade said:
When somebody calling me and I pick up, I can make conversation but phone is stuck on ringing mode, and after few moments hang up phone call, and I have missed call...
Somebody else have this problem? How can I fix this?
Click to expand...
Click to collapse
That's weird, I did never face this issue but my A2L is relatively new (1 week only).
I'll try to phone to my own A2L using different devices to see if I face this issue.

lbsilva said:
That's weird, I did never face this issue but my A2L is relatively new (1 week only).
I'll try to phone to my own A2L using different devices to see if I face this issue.
Click to expand...
Click to collapse
Yes, it is very weird and annoying. Not happens every time, but sometimes... ?

This happened to me yesterday for the first time, but I thought that was a problem of the person that was calling me.
It was a number I didn't have in my contacts, and after the bug I immediately called back that number, but it was not available.
I thought the person that was calling me had a very low battery charge and while calling me his phone turned off, causing the bug (because immediately after the bug it was unavailable).

To this date I still did not have this problem.

Me too, i cant answer and reject calls when i upgrade to android pie

Solved: Screen not turning on with incoming calls
Step 1: Go to Dialer or Phone app settings. To do so, you can either go to main settings, then open ‘Apps’, and then scroll down to Dialer or Phone App.
You can also access App Info page by long pressing the app icon, and then tapping the App info option or the small ‘i’ icon in the corner.
Step 2: Now select “App notifications” option and turn it "on"
Step 3: Now if App notifications are turned off, your display won’t wake up when someone calls you. Also if only the “Incoming calls” permission is off, your screen will not light up with incoming calls. Make sure required permissions are turned on and your issue will be fixed.

Xiaomi Mi 2 Lite. I cannot get incoming calls to show on my screen, so I can't answer. Tried switching notifications off and on again, tried forcing stop. Two days ago I did a factory reset and was OK for 2 days. I think this is since latest Android update about a 10 days ago.

Call answer bug
I have similar issue on Mi A1, been going for a while. Sometimes, call comes in, the answer key cannot pick and cannot reject the call. This happened after a certain update I just dont know which. I have noticed that this mostly happens at some particular GSM antennas, sometimes, just by moving away from that antenna (that's when in a car) solves the problem. But as long as I remained in that location at that time, i cannot pick or reject calls, I also can't make calls, I get the promt, network problem, even though the service bars r showing. And in some cases the people calling will tell me, that calls to me are not going through.

This is driving me nuts. When I get a phone call I get a bar at the top of the screen with two buttone, one saying Decline and the other sayng Answer. I can tap on it like a demented woodpecker, but nothing happens. If Itry to swipe it, the two buttons just disappear into a void and the phone keeps ringing with no way to answer. Very, very occasionally I get the normal notification that I can swipe to answer, but I have to phone nearly everybody back.

PeterSharpe said:
This is driving me nuts. When I get a phone call I get a bar at the top of the screen with two buttone, one saying Decline and the other sayng Answer. I can tap on it like a demented woodpecker, but nothing happens. If Itry to swipe it, the two buttons just disappear into a void and the phone keeps ringing with no way to answer. Very, very occasionally I get the normal notification that I can swipe to answer, but I have to phone nearly everybody back.
Click to expand...
Click to collapse
Clear data and cache of the "phone" App and if necessary reinstall the application

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