Addition. My suspicion was spot on. If you replace the preinstalled dialer system app with the above app and reboot the phone, then receive a phone call BEFORE you first log in, you cannot accept the phone call. It keeps ringing, you can click it away with power or volume buttons to dismiss, but you can’t accept it.
If you unlock the phone once, then lock it again, the app will work and you can receive calls normally.
By the looks this seems to be a general restriction of Android 9. After a reboot, before the first unlock, NO apps installed by the user will work, but preinstalled system apps disabled by the user will be DISABLED. This applies to vital system apps such as dialer (needed to receive calls) or the keyboard (potentially needed to unlock the phone if password protected)
This is IMHO a serious issue of Android 9, and something that needs to be addressed, either in a patch/update for Fairphone’s stock OS, or a FOSS version for FP3 for the hardcore users. ( don’t think Google would address this, I bet this is a “feature” for them as it makes it harder to replace their stuff with 3rd party apps)
Disabled the Google one and I tried the app just there, it worked.
I had to change settings to allow it display over apps and I allowed it to modify system settings too. This means the popup appears so I can see when a call is incoming.
Great hint with the LineageOS App it seems to work well
(I am not familiar with LineageOS so far).
I tried to replace the Google Phone app before, too.
Ended up with using Simple Contacts (F-Droid) as default phone app, and Open Contacts (F-Droid) to show call log and in-call notification (overlay with name).
Even with Simple Contacts as default phone app the screen during outgoing and incoming calls looks the same as before.
With deactivated Google Phone app no screen at all apears to manage active calls.
Because of this I wonder whether Google Phone and LineageOS Phone using a different UI of the same system app like Call Management for example (similar logo)?
I am not sure which app @corvuscorax meant with system Dialer app?
It looks like the emergency call uses a different UI that’s part of the lock screen app. Even with a freshly rebooted phone, I can still enter an emergency number. I never tried it past the “the inserted number is not an emergency number” error message though, as there’s a fine here for placing unnecessary emergency calls.
Similarly, incoming calls still ring, you just don’t have a button to accept them (but denying the call via power button works) - so it looks like it really is just the user Interface component that’s missing.
I’ll try to confirm that with an emulated Android device.
my observation: without Google or LineageOS Phone app outbound call is possible but no UI to end the call
special condition: when reboot phone (before enter PIN) only preinstalled apps work (LineageOS Phone doesn’t until enter PIN once after reboot)
educated guess: dialing emergency number works, but you can’t stop it (for me this rare usecase is acceptable)
Trust has to be earned The app that came with FP3 is called “Phone” (com.google.android.dialer) and actively tried to make a network connection to a Google IP address, which was intercepted and prevented by the Firewall App I installed, NetGuard.
The app from LineageOS is also called “Phone”, but designated com.android.dialer instead. This app so far has not tried to connect to anything in the 2 days since I installed it. It made 0 connection attempts (as it should)
Now that does not guarantee that it never will, nor that it won’t include code that tries something crazy if triggered by some rare event, but if it does, it still has to get past the firewall, which will prevent it, log it, and rest assured, I will update this thread accordingly if it does.
It’s called “dialer” since it doesn’t handle the call itself - this is handled by device drivers of the GSM modem and the audio stack, and partially in hardware. The dialer would likely just make an API call to send the “AP” commands to the modem to make a call and/or accept one. In newer Android version it also displays how long the call has been going (in call UI) and allows to initiate a hang up. (Which would again be a driver command to the GSM/UMTS/LTE/… modem)
As soon as one of the few FOSS apps has been updated to include the Android9 and higher in-call UI the Dialer now needs to provide in order to accept calls, it can again be replaced by such open source app. (Unless there’s sources for LineageOS, is there?)
Thanks for this info. Had problems after removing com.google.android.dialer via adb before too. I will try the solution with the LineageOS Dialer later.
This probably would be considered not a bug but a “feature” by every major phone manufacturer, since it is generally recommended to never ever end emergency calls and rather let the assistant hang up on you. So totally fine with me either
Does this occur only after a reboot, or every time you initiate an emergency call from lock screen?
Besides, did you or somebody else manage to work around the problem with the keyboard and password-input on reboot? It’s unfortunately the only reason for me to keep the google gboard on my phone.
The issue is only when the phone has been booted but not unlocked yet. Once you unlock and re-lock everything works. (That’s also why you will only notice the issue after a reboot)
My solution to get rid of google gboard was to change the lock from “password” to “pin” and use a long custom pin for unlocking. Unlike passwords, for which the lock screen invokes the system keyboard, for pins, it uses its own pin entry interface (and it also does for emergency numbers and for SIM pins if the SIM is locked with a pin)
in my case, after a cold reboot, I need to enter 3 pins. The pin for the 1st SIM, the pin for the 2nd SIM, and the PIN that phone is locked with.
On standby the SIM’s don’t need unlocking, so I only enter the phone PIN.
I worked around the reduced security of having only 10 digits by chosing a really long PIN.
Thanks, good to know.
When you are in the lockscreen options and try to set a PIN it shows the keyboard-symbol in the lower right corner of the screen, which you can tap on and select between gboard and others. So I didn’t invest more time in this topic and thought that you need gboard for PIN too.
PIN is fine for me. Didn’t want to use Pattern, because of the arrangement of the dots in the middle of the screen, hence its unergonomic design.
I am not able to use the Lineage OS Phone application from Simple Contacts Pro to make calls: If I press on the calling button in the entry of a contact then I can choose between a Dialer app, with the orange icon of Simple Contacts Pro, and a Phone application that is not the Lineage OS one but a Google one which icon is a blue 3D phone with no background. When using the orange Dialer I get no calling UI so I cannot finish the call nor entering digits, which is specially bad if the automatic answering machine of the other person wants me to record a message.
On the other hand, selecting a contact directly in the contacts tab of the Lineage OS Phone application redirect me to the Simple Contacts entry of the contact, so I cannot make the call. The only solution I found is to enter the name of the contact in the Search contact text field in the part of above of the Lineage OS Phone app. When pressing the contact that way, a call is succesfully done, including the UI.
In addition, introducion manually the number in the pad of Lineage OS Phone or pressing the phone icon at the right of the entries in the history calls tab also work.
Yes. Setting the birthday of the contact. I couldn’t set it in LineageOS Contacts.
OK, I did it. The situation is the same. To call someone, I have to choose between the orange Dialer (not working properly) and the blue 3D Phone. Even if I am concerned about privacy with Phone, this time I selected it and the call was done without problems. At any case, I am guessing that the solutions I provided in my previous post make use of Phone silently.
By the way, are Lineage OS applications fully free software? Why they cannot be found in F-Droid? One thing that disturbed me is that in LineageOS Contacts > Settings > About Contacts > Terms of Service you are redirected to Google Terms of Service webpage.
I’ve installed Contact 1.7.31 and Phoen from LineageOS, and I get a problem with the phone app.
It seems i can’t accept in-call (When i click, nothing happens), and when I start a call with this, the call is launched but the app failed. And I can’t relaunch these (by example, I must use “Fly mode” to turn off the call).