SOLVED:Android 11 phone app issue - OnePlus 7T Questions & Answers

On the newer Android 11 releases, I have issues with the phone app.
No response when Pressing the "Answer button" . On the main window of the phone app, as well as status bar drop down button. Neither work.
3rd party phone apps do not work .
Decline button works.
I am able to make out going calls.
Any one else experience this issue?
Earlier Android 11 versions don't seem to be affected , Latest builds on multiple roms seem to affect me.

hightech316 said:
On the newer Android 11 releases, I have issues with the phone app.
No response when Pressing the "Answer button" . On the main window of the phone app, as well as status bar drop down button. Neither work.
3rd party phone apps do not work .
Decline button works.
I am able to make out going calls.
Any one else experience this issue?
Earlier Android 11 versions don't seem to be affected , Latest builds on multiple roms seem to affect me.
Click to expand...
Click to collapse
Make sure default phone apps are set to your dialer app and all permissions r correct

HueyT said:
Make sure default phone apps are set to your dialer app and all permissions r correct
Click to expand...
Click to collapse
Indeed, First item I checked.

SOLVED :
Remove Google FI app

Related

Install button not working

Hi,
Fairly basic Android user here with an irritating problem. Running whatever the most basic version of Lollipop is on my M8, installed today but this problem has been ongoing well before that.
So the problem is that the 'Install' button here on the screen in the image attached is totally unresponsive, no matter the app I'm trying to install. Showbox is here but that's just because it's an old apk I had on my phone, I've the same problem for anything I've tried.
In the fine words of Ned Flanders' father, I've tried nothing and I'm all out of ideas - thought it best to ask for advice from people who know more than me. Any advice much appreciated!
laighean said:
Hi,
Fairly basic Android user here with an irritating problem. Running whatever the most basic version of Lollipop is on my M8, installed today but this problem has been ongoing well before that.
So the problem is that the 'Install' button here on the screen in the image attached is totally unresponsive, no matter the app I'm trying to install. Showbox is here but that's just because it's an old apk I had on my phone, I've the same problem for anything I've tried.
In the fine words of Ned Flanders' father, I've tried nothing and I'm all out of ideas - thought it best to ask for advice from people who know more than me. Any advice much appreciated!
Click to expand...
Click to collapse
You have allowed installation of apps from unknown sources in settings > security > unknown sources, correct?
xunholyx said:
You have allowed installation of apps from unknown sources in settings > security > unknown sources, correct?
Click to expand...
Click to collapse
I have indeed!
Do you have any screen dimming app installed? I've had the same issue on my phone with total screen control, whenever I tried to install an app with TSC running the install button was unresponsive. When I stopped TSC from running I could press install without issue.
Some apps will for some reason stop you from hitting install. For example.... I use copy bubble... Which has a floating circle for accessing the clipboard. If that bubble is on my screen, I can't hit install... No matter where the bubble is on my screen. I just close the bubble and it's fine.
Look at apps that may be causing the same affect. ?
BOO5TED said:
Do you have any screen dimming app installed? I've had the same issue on my phone with total screen control, whenever I tried to install an app with TSC running the install button was unresponsive. When I stopped TSC from running I could press install without issue.
Click to expand...
Click to collapse
Just to confirm that this was the issue, would never had occurred to me! Was using Twilight, turning it off sorted it out. Thanks a million!
Glad you got it figured out. :highfive:

OP3 echo on phone calls observation

Hi, I'm new here however I've read on a few rom threads about an echo on voice calls. Today I started experiencing the echo for the 1st time and I think I have and idea what's the cause.
I am running freedomos ce v1.10 but I've seen the issue as a known bug on other ROMs and it doesn't affect everyone.
I think it affects those of us who flash the pixel dialer, maybe other dialers as well but in my case it's the pixel dialer.
Why do I think so?
Today it started, i received a call and I noticed the call screen was the default phone app screen not the pixel screen. (I've disabled the stock app). but somehow its still activating when there's an incoming call.
Also after accepting the call I notice 2 phone icons in the status bar suggesting maybe that there's 2 phone calls active.
I've checked and the stock phone app is still disabled so there may be an OS level trigger still allowing it to accept incoming calls.
teostar said:
Hi, I'm new here however I've read on a few rom threads about an echo on voice calls. Today I started experiencing the echo for the 1st time and I think I have and idea what's the cause.
I am running freedomos ce v1.10 but I've seen the issue as a known bug on other ROMs and it doesn't affect everyone.
I think it affects those of us who flash the pixel dialer, maybe other dialers as well but in my case it's the pixel dialer.
Why do I think so?
Today it started, i received a call and I noticed the call screen was the default phone app screen not the pixel screen. (I've disabled the stock app). but somehow its still activating when there's an incoming call.
Also after accepting the call I notice 2 phone icons in the status bar suggesting maybe that there's 2 phone calls active.
I've checked and the stock phone app is still disabled so there may be an OS level trigger still allowing it to accept incoming calls.
Click to expand...
Click to collapse
Wrong place to post this.
dpryor88 said:
Wrong place to post this.
Click to expand...
Click to collapse
OK, maybe a mod can move it to the correct area. I didn't post in any specific rom thread since it occurs on various ROMs.
teostar said:
Hi, I'm new here however I've read on a few rom threads about an echo on voice calls. Today I started experiencing the echo for the 1st time and I think I have and idea what's the cause.
I am running freedomos ce v1.10 but I've seen the issue as a known bug on other ROMs and it doesn't affect everyone.
I think it affects those of us who flash the pixel dialer, maybe other dialers as well but in my case it's the pixel dialer.
Why do I think so?
Today it started, i received a call and I noticed the call screen was the default phone app screen not the pixel screen. (I've disabled the stock app). but somehow its still activating when there's an incoming call.
Also after accepting the call I notice 2 phone icons in the status bar suggesting maybe that there's 2 phone calls active.
I've checked and the stock phone app is still disabled so there may be an OS level trigger still allowing it to accept incoming calls.
Click to expand...
Click to collapse
I'm not using pixels dialer and I have echo bug.
ivicakc said:
I'm not using pixels dialer and I have echo bug.
Click to expand...
Click to collapse
When it happens do you notice the double phone icons in the status bar?
teostar said:
When it happens do you notice the double phone icons in the status bar?
Click to expand...
Click to collapse
Nope, one icon..
teostar said:
Hi, I'm new here however I've read on a few rom threads about an echo on voice calls. Today I started experiencing the echo for the 1st time and I think I have and idea what's the cause.
I am running freedomos ce v1.10 but I've seen the issue as a known bug on other ROMs and it doesn't affect everyone.
I think it affects those of us who flash the pixel dialer, maybe other dialers as well but in my case it's the pixel dialer.
Why do I think so?
Today it started, i received a call and I noticed the call screen was the default phone app screen not the pixel screen. (I've disabled the stock app). but somehow its still activating when there's an incoming call.
Also after accepting the call I notice 2 phone icons in the status bar suggesting maybe that there's 2 phone calls active.
I've checked and the stock phone app is still disabled so there may be an OS level trigger still allowing it to accept incoming calls.
Click to expand...
Click to collapse
In which threads you have read about the echo issue? This issue is mainly present on the nougat roms and it's due to the audio hal, however workaround was found and now everything is fine(when you flash the fix ofc). I have never had this issue on MM roms and especially on stock(ye, freedom rom is stock based), so maybe the problem you have is really somewhere with the apps you use. And can you tell how did you find that you have the issue?
siankatabg said:
In which threads you have read about the echo issue? This issue is mainly present on the nougat roms and it's due to the audio hal, however workaround was found and now everything is fine(when you flash the fix ofc). I have never had this issue on MM roms and especially on stock(ye, freedom rom is stock based), so maybe the problem you have is really somewhere with the apps you use. And can you tell how did you find that you have the issue?
Click to expand...
Click to collapse
As I stated I noticed that incoming calls seemed to come in the stock phone app not the pixel dialer. But because the stock app is disabled think that may have been the issue.
ivicakc said:
Nope, one icon..
Click to expand...
Click to collapse
Here's what happens for me.
teostar said:
Here's what happens for me.
Click to expand...
Click to collapse
Do you have root? If yes, just go to the system folder, find the app that you don't want to use and rename it(add .back at the end), so you can revert to it later if you want, then reboot
siankatabg said:
Do you have root? If yes, just go to the system folder, find the app that you don't want to use and rename it(add .back at the end), so you can revert to it later if you want, then reboot
Click to expand...
Click to collapse
I'm not sure which is the stock phone app. Apart from "Google dialer" there's "OPincalui", "phonesky", "telecom" and "telephonyprovider"
I'm not sure which is the actual phone app.
teostar said:
I'm not sure which is the stock phone app. Apart from "Google dialer" there's "OPincalui", "phonesky", "telecom" and "telephonyprovider"
I'm not sure which is the actual phone app.
Click to expand...
Click to collapse
I would eliminate Phonesky (Play Store), and TelephonyProvider from the list because those are not directly tied to the phone app.
teostar said:
Here's what happens for me.
Click to expand...
Click to collapse
I have the same problem. Freedom OS, stock kernel and google dialer and contacts....
teostar said:
I'm not sure which is the stock phone app. Apart from "Google dialer" there's "OPincalui", "phonesky", "telecom" and "telephonyprovider"
I'm not sure which is the actual phone app.
Click to expand...
Click to collapse
Actually you should be able to see the app icon when you go to the folder, so try with some other file manager that support this function. I can bet that OPIncallUI is the dialer, but to be sure, try with other manager
siankatabg said:
Actually you should be able to see the app icon when you go to the folder, so try with some other file manager that support this function. I can bet that OPIncallUI is the dialer, but to be sure, try with other manager
Click to expand...
Click to collapse
OK, with solid explorer I see this. It gets even more confusing...
teostar said:
OK, with solid explorer I see this. It gets even more confusing...
Click to expand...
Click to collapse
Rename the OPIncallUI, don't touch the other apps, that should do the job
siankatabg said:
Rename the OPIncallUI, don't touch the other apps, that should do the job
Click to expand...
Click to collapse
OK, just rename the apk, not the actual folder?
teostar said:
OK, just rename the apk, not the actual folder?
Click to expand...
Click to collapse
Just the .apk, rename it to .apk.back and if you get problems just rename it back to .apk
Sent from my ONEPLUS A3003 using Tapatalk
siankatabg said:
Just the .apk, rename it to .apk.back and if you get problems just rename it back to .apk
Click to expand...
Click to collapse
Thanks. That worked.

Unable to Answer or Reject Calls

Hello,
I have been struggling recently to answer or reject calls when given the swipe up or down option.
When its unlocked and I get the tap to answer or reject as a notification its fine.
I'm just wondering if anyone else had a similar issue or had found a fix.
I'm on the official firmware, running 8.1.0
I've experienced something similar too. Sometimes I find myself swiping over and over again just to get one call answered or rejecte I have no idea why it does that, or when, it seems to be random on mine
I have to swipe upp exactly(?) 3 times to answer a call from the lock screen.
Also running official ROM 8.1, no root or mods so far.
Have only had the phone for a few weeks, so don't know what is normal.
Otherwise it seems to work very well.
I've found you can swipe down from the top of the screen and can answer it from the notification menu instead.
Just takes longer.
cobben said:
I have to swipe upp exactly(?) 3 times to answer a call from the lock screen.
Also running official ROM 8.1, no root or mods so far.
Have only had the phone for a few weeks, so don't know what is normal.
Otherwise it seems to work very well.
Click to expand...
Click to collapse
Just after having written the above, the phone corrected itself.
Now I can answer calls on the first swipe.
Interesting . . .
Sometimes my phone will let me answer normally. most of the time however I have to use the notification bar.
I have been having this issue since the very beginning. I even changed to the google phone app and jt still does that. Its because of the framerate. I think. Its very hard to test because uts vey inconsistent.
Yup, been having the same issue. Stock phone, no root. What's frustrating is there as no further updates.
iliais347 said:
I have been having this issue since the very beginning. I even changed to the google phone app and jt still does that. Its because of the framerate. I think. Its very hard to test because uts vey inconsistent.
Click to expand...
Click to collapse
I had display set to 90Hz for no particular reason, have now tested having it set to 60Hz, and I have been able to answer every call directly with one swipe .
Of course I don't get so many calls to this sim card I have in it now, but previously it hardly worked at all
So the problem might welll be connected to the display refresh rate for some reason.
cobben said:
I had display set to 90Hz for no particular reason, have now tested having it set to 60Hz, and I have been able to answer every call directly with one swipe .
Of course I don't get so many calls to this sim card I have in it now, but previously it hardly worked at all
So the problem might welll be connected to the display refresh rate for some reason.
Click to expand...
Click to collapse
What i did is i added the google dialer app to my phone, then to game booster and set its fps to 40. Now i can answer the calls.

Lots of different small issues

Hi all
I have been using this phone for a month, and I have experienced a lot of different small issues, I hope someone may have solution to them.
Phone:
Mi A2 Lite, rooted (Magisk) Android one pie, January update. Has a screen protector.
Apps:
Here are some apps that I think may cause the issue that I mention below, these apps are Nova and datally. Really can't think of a third one, I don't use any cleaning app or battery performance app.
Issue:
1. Typing experience is horrible. Using stock google input, the keyboard is not very sensitive and accurate. The letter just can't be recognized even though I am sure I have pressed the key and pressed the right key. So my typing is really slow, the key doesn't display immediately (it does seem to have a delay), and for some reason I always type wrong and missing some letters, so gotta use backspace a lot.
2. It always wakes up randomly in my pocket, so I may take the phone out with torch on and airplane mode on without my awareness.
3. When I am on a call, I can accidentally press some random on screen keys.
4. The background apps AWALYS get killed, even though I have turned the battery optimization off globally, and the individual apps that I never want to be killed.
5. Messaging service apps have huge delay when delivering the notification. It may only show when I open the app. Used PNF app but couldn't fix the problem.
Does anyone have the same issue and know the fix?
I hope it is only the software problem (Pie system) and maybe I can fix it by flashing a better rom, but I don't seem to find a stable official custom ROM for Mi A2 Lite (even lineage OS is unofficial)
Many thanks
luckyvictor said:
Hi all
I have been using this phone for a month, and I have experienced a lot of different small issues, I hope someone may have solution to them.
Phone:
Mi A2 Lite, rooted (Magisk) Android one pie, January update. Has a screen protector.
Apps:
Here are some apps that I think may cause the issue that I mention below, these apps are Nova and datally. Really can't think of a third one, I don't use any cleaning app or battery performance app.
Issue:
1. Typing experience is horrible. Using stock google input, the keyboard is not very sensitive and accurate. The letter just can't be recognized even though I am sure I have pressed the key and pressed the right key. So my typing is really slow, the key doesn't display immediately (it does seem to have a delay), and for some reason I always type wrong and missing some letters, so gotta use backspace a lot.
2. It always wakes up randomly in my pocket, so I may take the phone out with torch on and airplane mode on without my awareness.
3. When I am on a call, I can accidentally press some random on screen keys.
4. The background apps AWALYS get killed, even though I have turned the battery optimization off globally, and the individual apps that I never want to be killed.
5. Messaging service apps have huge delay when delivering the notification. It may only show when I open the app. Used PNF app but couldn't fix the problem.
Does anyone have the same issue and know the fix?
I hope it is only the software problem (Pie system) and maybe I can fix it by flashing a better rom, but I don't seem to find a stable official custom ROM for Mi A2 Lite (even lineage OS is unofficial)
Many thanks
Click to expand...
Click to collapse
Try to update I never had any of those issues
I have also these problems. I have February update.
madmanwild said:
I have also these problems. I have February update.
Click to expand...
Click to collapse
Do you have all these problems? or just one or two? After seeing my configuration/apps that I installed, do you think is it app related or system related?
rob420p said:
Try to update I never had any of those issues
Click to expand...
Click to collapse
not even one of these? Your background app never get killed?
Are you using Stock Android One? did you root your phone?
luckyvictor said:
Do you have all these problems? or just one or two? After seeing my configuration/apps that I installed, do you think is it app related or system related?
Click to expand...
Click to collapse
all these problems without wakes up in pocket. killing the background application is the biggest problem for me (I use a lot of smart home app- eWelink,Room Heat,Magic Home) and it's horrible. ewelink starts 5sec after kill, Room Heat - frequent crash like a white screen...
the next problem is huge delay when delivering the notification....
I am on Stock Android One-February update,I'm allowed only cam2api...
madmanwild said:
all these problems without wakes up in pocket. killing the background application is the biggest problem for me (I use a lot of smart home app- eWelink,Room Heat,Magic Home) and it's horrible. ewelink starts 5sec after kill, Room Heat - frequent crash like a white screen...
the next problem is huge delay when delivering the notification....
I am on Stock Android One-February update,I'm allowed only cam2api...
Click to expand...
Click to collapse
You have battery optimization off? any battery improvement app? I think all these is because the 'intelligence' in Android is playing up, it doesn't understand exactly how we use the app. However, even have it turned off, the problem exists....
luckyvictor said:
not even one of these? Your background app never get killed?
Are you using Stock Android One? did you root your phone?
Click to expand...
Click to collapse
I am on stock but I do have root.havent done much modification yet waiting for twrp
rob420p said:
I am on stock but I do have root.havent done much modification yet waiting for twrp
Click to expand...
Click to collapse
Don't understand why there is such different, did you have battery optimisation off and all time since the first day you use the device?
luckyvictor said:
Don't understand why there is such different, did you have battery optimisation off and all time since the first day you use the device?
Click to expand...
Click to collapse
Honestly I don't think so I really haven't messed with the battery besides putting a %
luckyvictor said:
You have battery optimization off? any battery improvement app? I think all these is because the 'intelligence' in Android is playing up, it doesn't understand exactly how we use the app. However, even have it turned off, the problem exists....
Click to expand...
Click to collapse
Yes, all off - battery adaptation and manually set no optimization on my app...

Question Issues afteratest update

S21fe updated to UI5.
Couple of issues.... Fingerprint reader sometimes doesn't work when phone hasn't been used for some time. When it happens I need to double tap the screen to wake it up and then scan my fingerprint again.
Also "back" gesture (where I swipe up from the right bottom of the screen) sometimes instead of going back brings up the list of background apps.
Both issues very annoying.
Anyone else experienced anything similar?
Try clearing the system cache. Double check all settings. If that flaws things get more complicated...
A factory reset may be needed, but hard to say if it will resolve the issues. Someone will need to try the latter if the former doesn't work. A global reset of settings is a less drastic option but it may not be enough and still take a lot of time.
This is one reason why I spurn upgrades on a platform that's fulfilling its mission. Lol, I'm still using UI 1.5, no glaring issues.
Unfortunately with latter versions an upgrade may resolve flaws in earlier post >1.5 variants. Tough choice once you are on Android 11 as there's no roll back on stock Samsung's for that. I wasn't locked into using 11 on my N10+'s and never will load it. 12 is even worse.
Roll back is an option for you if bootloader wasn't upgraded too. Eventually Samsung will fix it if it's a firmware/software glitch but don't hold your breath for that
blackhawk said:
Try clearing the system cache
Click to expand...
Click to collapse
With each major update, I always clean the system cache from the recovery !
jbs68 said:
With each major update, I always clean the system cache from the recovery !
Click to expand...
Click to collapse
That may not be enough if going from 11 to 12, etc.
Rule #1 - if the OS is fast, stable and fulfilling its mission let it be! You have little to gain and a lot to lose. Although there was a big security hole in 12, not sure if it was patched already or if the patch is in what you just install. Oddly that hole isn't in 9-11.
Gookill is a mess...
I have the same problem with fingerprint unlocking. It simply doesn't work (if I press the side button, it works). Some hours ago I wiped the system cache and after that, I didn't notice the described problem. I will see in the next few hours.
Now I changed "Fingerprints -> Show icon when screen is off" to "Tap to show" instead of "On always on display" which was the default after the upgrade to Android 13.
UPDATE: The phone still has the same problem. Sometimes it simply doesn't allow it to unlock with a fingerprint. The screen is locked as hell. Only the side button unlocks it.
If you go to Lock screen>Always On Display>Show always, does that solve your problem? Mine was set to "show for new notifications" only and the fingerprint icon would disapperar after locking it.
Mine was set to "Show for new notifications". As you suggested, I changed it to "Show always" and we will see, how it works. In my opinion, it is better to show display only when something happens. But something changed and problems occurred.
Report: it didn't help. I have found out that the issue appears if the phone is locked for a while and then a notification comes. This is the reason why this problem exists also while using Android Auto. It creates a notification when it connects ... and then the phone can be unlocked with a fingerprint until the side button is pressed. I'm sure this is a bug that didn't exist before the upgrade to Android 13.
no such issues here with the eu version. definitely an upgrade in every way.
After 3 days with Android 13 on snapdragon variant, only two minor issues found here : slow charging (2h20 from 0 to 100, less than 2h before) and an "unauthorized action due to modified device" screen when rebooting, disappearing by touching "OK" button. Don't know what is unauthorized but... well. I was rooted before, now stock unrooted and relocked bootloader. It doesn't seems to lock something, everything I use is working.
I have the same fingerprint issues after updating to UI5 (unlocking from turned off screen). Sometimes it works, sometimes it doesn't. It worked perfectly before I updated, didn't change any settings. Very annoying, hopefully it will be fixed in a future update.
d0j0m0j0 said:
I have the same fingerprint issues after updating to UI5 (unlocking from turned off screen). Sometimes it works, sometimes it doesn't. It worked perfectly before I updated, didn't change any settings. Very annoying, hopefully it will be fixed in a future update.
Click to expand...
Click to collapse
The recent update with the December security patch seens to have resolved this issue for me.
Edit: scratch that, still not fixed...
Edit2: turning off lock scrern mods in Galaxy MaxHz seems to help.
jbs68 said:
With each major update, I always clean the system cache from the recovery !
Click to expand...
Click to collapse
How does one do that?
xda-eh said:
How does one do that?
Click to expand...
Click to collapse
It's on the boot menu on Samsung's.
blackhawk said:
It's on the boot menu on Samsung's.
Click to expand...
Click to collapse
You're referring to accessing the recovery mode as explained here?
xda-eh said:
You're referring to accessing the recovery mode as explained here?
Click to expand...
Click to collapse
This. Some have said Android 12 needs to be plugged into the PC to access the boot menu, don't know as I run Pie and Q.
blackhawk said:
This. Some have said Android 12 needs to be plugged into the PC to access the boot menu, don't know as I run Pie and Q.
Click to expand...
Click to collapse
The link I provided and the one you did refer to the same thing. Only difference is my link also provides a way to do it via ADB. In any event, thanks for your response.

Categories

Resources