So after being on a few hours I noticed the upper left corner of the screen loose touch sensitivity and is completely unresponsive until you reboot.
Has anyone had this happen?
Haven't suffered that in 1 month of use...
Enviado desde mi Oneplus X
1. some time d2w doesn't worl
2.when the phone unlocks there is recent tast menu opened already and no apps showing in it
3.in call settings after making sim1 as default calling sim it still asks whenever you try to call someone
i really hate oxygen i want some rom like that xperia z5 rom based on cm12.1
i hate you oxygen os devs
mohammedtabish said:
1. some time d2w doesn't worl
2.when the phone unlocks there is recent tast menu opened already and no apps showing in it
3.in call settings after making sim1 as default calling sim it still asks whenever you try to call someone
i really hate oxygen i want some rom like that xperia z5 rom based on cm12.1
i hate you oxygen os devs
Click to expand...
Click to collapse
Big words...
I notice an issue where my set responded very weird when it is plugged into charging mode. The touch will go haywire. Once unplug, it is normal
I thought the screen was losing touch sensitivity when this happened to me, so I turned on the "Show Touches" option under the Developer options, and it picks up everything perfectly fine. Odd and a bit annoying though.
lavenderyew said:
I notice an issue where my set responded very weird when it is plugged into charging mode. The touch will go haywire. Once unplug, it is normal
Click to expand...
Click to collapse
that could be an issue with the ac charger itself. i had that issue with my nexus 4 using the 2A 5v samsung ac charger i got off amazon. note that the adapter made an electrical hissing/whine noise when plugged in... that issue only happened when used with that adapter... i have since thrown them away.
...but if you're plugged directly to pc, then who knows...
have you tried a different ac adapter? hopefully doesnt happen with the one that came with the phone, cause then that would be strange...
Mic issue when toggling from speaker to internal mic
Has anyone had an issue whre you are on a call, you toggle to speaker phone, all is ok, then you try to toggle back to the internal mic and the person can not hear you?
This may have something to do with my call recording, I haven't been able to test though
dipeshb said:
Has anyone had an issue whre you are on a call, you toggle to speaker phone, all is ok, then you try to toggle back to the internal mic and the person can not hear you?
This may have something to do with my call recording, I haven't been able to test though
Click to expand...
Click to collapse
On Stock and without any recording apps, it worked just fine.
s4b3r said:
On Stock and without any recording apps, it worked just fine.
Click to expand...
Click to collapse
Great, thanks for the information! I'm sure my recording app is to blame, will try and tweak it
Related
Hey guys,
My Hero says the headphones are connected but they aren't connected!? This is very annoying when I want to call someone, then I have to use the headphones because otherwise I can't listen what the persons I'm calling to says. So the speakers are disabled (can still play music through headphones).
I also see the headphones icon in the Android bar.
I tried another ROM but it's giving the same problem (Android 2.1 stock, 2.2 Floyo, FV 1.5, etc.)
How can I solve this?
As far as i know this is not a rom specific problem, more of a software thing. It happens if you restart your phone too much (its how i get it). Three ways to solve problem
1. turn off your phone and wait at least 2 minutes before turning back on and it shud be gone
2. download toggleheadset.apk and it will no longer matter how much you restart your phone since u can toggle the icon off/on
3. least practical on long term and takes a while but works, poke a headphone in and move around until icon disappears
I get this problem all the time, and it seems like a lot of other hero users get it as well, i solved it using toggleheadset
Thanks for your message. I tried all these methods but they don't work
When I install Headset Blocker, I can still see the icon in the black HTC Android bar. The other two methods also don't work.
Haha! Yeah, it works!
I installed toggleheadset.apk but I didn't notice it's a widget and not an app.
So now it works and I can use my speakers again.
Thank you very much!
walkinhotdog said:
As far as i know this is not a rom specific problem, more of a software thing. It happens if you restart your phone too much (its how i get it). Three ways to solve problem
1. turn off your phone and wait at least 2 minutes before turning back on and it shud be gone
2. download toggleheadset.apk and it will no longer matter how much you restart your phone since u can toggle the icon off/on
3. least practical on long term and takes a while but works, poke a headphone in and move around until icon disappears
I get this problem all the time, and it seems like a lot of other hero users get it as well, i solved it using toggleheadset
Click to expand...
Click to collapse
Sent from my HERO200 using XDA App
Rrrtro5rttotwxyoyrxrtxrcxszzeeytrtTeyEtytttryyyrtyryyteyrtytrcyy00 using XDA App
it can solve the problem tempoly ,but it's not a long term solution...the toggleheadset it won't work in android 2.2,you can try..
I also have this problem.
Maybe there is another solution?
Am I the only one having problems with the Proximity Sensor on the Atrix? I can't seem to get it to kick in when on a call. I have already dial-toned a couple of people when talking on the phone. I have tried covering up the sensor by placing the palm of my hand over the to 1/2 of the phone and it never kicks in.
Can someone verify for me that it does work and not some software bug.
Thanks,
Ed
Did you ever find the problem? My proximity sensor has stopped working also.
i am having an issue with mine too. at first i thought it was an issue with the screen not coming back on, but now i realize that the proximity sensor is not turning off the screen at all and my screen is just turning off when the screen timeout value is reached.
my phone is rooted, i have used titanium backup to freeze some of the apps associated with blur, and i have installed the hack to use webtop mode. can others that have this issue confirm if they are running stock or modified software?
***EDIT***
http://forum.xda-developers.com/showthread.php?p=12035170#post12035170
Any of you guys ever find a fix for this? I just noticed that mine is not working anymore either. It's rooted using aRoot but it was working for a while and now it doesn't anymore. I have another couple of days to exchange in store if I want to if it's a phone issue.
Crap, I'm having the same issue now too -- was working fine since I had it, but this occured just today, Day-2 of using 1.5.7 .... wonder if it's related ...
Crap, I'm having the same issue now too -- was working fine since I had it, but this occured just today, Day-2 of using 1.5.7 .... wonder if it's related ...
Reboot seems to fix this -- but annoying >_<
Is anyone that is having these issues using bluetooth? I have isolated mine to bluetooth and sent an issue report to Motorola.
same problem here but not using bluetooth
My wife's Atrix does the same thing. "dials or hangs up while in a call". She does not own a bluetooth headset and I have only connected a Motorola 305 one time to it. Reboot fixes the problem. Reboot seems to take forever when compared to my Dell Streak.
Ed Venture said:
Am I the only one having problems with the Proximity Sensor on the Atrix? I can't seem to get it to kick in when on a call. I have already dial-toned a couple of people when talking on the phone. I have tried covering up the sensor by placing the palm of my hand over the to 1/2 of the phone and it never kicks in.
Can someone verify for me that it does work and not some software bug.
Thanks,
Ed
Click to expand...
Click to collapse
Had the problem with mine when I installed a different launcher had to delete it and restart the phone now it works ....for me anyways
Sent from my MB860 using XDA App
Hi I believe I traced the problem with the proximity sensor not working to Handcent SMS. On two separate Atrixes, as soon as I uninstalled Handcent and rebooted the phone the problem went away and stayed away. I have since installed GoSMS and now it happens just sometimes (usually after I install a new app) but a reboot after installing an app ususlly fixes it.
My Phone has a standard Telstra (Australia ROM) and is not unlocked or modified in any way.
Ed Venture said:
Am I the only one having problems with the Proximity Sensor on the Atrix? I can't seem to get it to kick in when on a call. I have already dial-toned a couple of people when talking on the phone. I have tried covering up the sensor by placing the palm of my hand over the to 1/2 of the phone and it never kicks in.
Can someone verify for me that it does work and not some software bug.
Thanks,
Ed
Click to expand...
Click to collapse
hi, you can try this
open /system/build.prop and add this
persist.mot.proximity.touch=1
reboot phone
Seem that i have this problem on my atrix,when i calling someone,the screen turn off immediately and the led on proximity sensor just keep turn on when i stop calling,i cant imagine this atrix have a lot a lot hardware problem
Sent from my MB860 using Tapatalk 2
If you are using unlocked bootloader or if u have unlocked the dim using a code then u will have to disable the In Pocket detection and then try sounds crazy but worked for me.
Sent from my MB860 using xda premium
ranjithkumar1201 said:
If you are using unlocked bootloader or if u have unlocked the dim using a code then u will have to disable the In Pocket detection and then try sounds crazy but worked for me.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
care to share how?
Similar issue
Just installed latest stable build onto my Atrix 4G, everything seemed fine last night, although I was using phone with bluetooth, this morning get a call, answer, screen goes dark, red proximity light comes on, and I can hear no sound, [later on the caller said he could hear me fine].
Phone would not wake up right off, and when it did it I still could not hear caller.
Been screwing around with settings all morning to no avail, discovered that the phone will only work with bluetooth device connected. without bluetooth the device goes dark, cannot wake up, have to hard reboot, with bluetooth and volume button awaken enabled, it performs normally, so possible connection to issues in post with proximity but with a bluetooth twist...
12as2005 said:
hi, you can try this
open /system/build.prop and add this
persist.mot.proximity.touch=1
reboot phone
Click to expand...
Click to collapse
Did that...... Does nothing much....
12as2005 said:
hi, you can try this
open /system/build.prop and add this
persist.mot.proximity.touch=1
reboot phone
Click to expand...
Click to collapse
Worked for me!!!
Stock rom with, root, atrix tweaks installed.
Thank's a lot!!!
I have a Sony Z3+/Z4.
The app Phone Call Management is re-detecting a headset plugged in so my music stopped randomly. Sometimes it would work for hours. Then there are times when it stop every 3 seconds. I can't replicate the exact cause.
I used TB to disable it and everything is fine.
1. How can I fix it? What else could be affecting it?
2. What's Phone Call Management? Google doesn't have an answer.
story said:
I have a Sony Z3+/Z4.
The app Phone Call Management is re-detecting a headset plugged in so my music stopped randomly. Sometimes it would work for hours. Then there are times when it stop every 3 seconds. I can't replicate the exact cause.
I used TB to disable it and everything is fine.
1. How can I fix it? What else could be affecting it?
2. What's Phone Call Management? Google doesn't have an answer.
Click to expand...
Click to collapse
To answer 2 look in settings in all apps category find Phone Call Mangement. If it says something like com.google.[App Name Here] or com.Sony.[App Name Here] then it's best to leave it alone if it's by something else then disable it and see if that fixes your issues if not I don't really have another solution as I haven't owned one of these devices first hand.
Sent from my iPhone using Tapatalk
doughmay said:
To answer 2 look in settings in all apps category find Phone Call Mangement. If it says something like com.google.[App Name Here] or com.Sony.[App Name Here] then it's best to leave it alone if it's by something else then disable it and see if that fixes your issues if not I don't really have another solution as I haven't owned one of these devices first hand.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
It seems to be the ROM's problem. I flashed the original and NagasakiROM and it's still the same. I found a M-ROM from China and it's fine now.
Got the update last night. Tried to check voicemail morning and was greeted with Alvin & The Chipmunks blabbing at me. It's like the speed of the call is x20 speed or something. It's completely unusable. Phone sluggish as hell, too.
Anyone know what's going on with the voice speed? I've never heard of anything like this.
I'm supposed to get a callback for a job interview I had yesterday. Pretty crappy timing. How is Google going to push an update that breaks calls like this? Absurd.
its nokia that pushed the update they did not make the rom right
Same here I told nokia about it and they told me to wait for a bug fix. I told them I wanted to downgrade since your firmware bug broke my phone.
Just wait for a bug fix? So use a Phone that cant make calls right?
So payed a guy to unlock my boot loader to try to flash a rom so i can just make the phone usable.
I spend about 6 hours try to get the rom to work. With little to no luck I was able to get into twrp a few times.
So ya Im in the same boat. I just got this phone back 3 weeks ago from a rma due to a bad chargeing port. Now Im forced to pay some one to unlock the boot loader and try to get a custom rom Just to be able to call
If I cant get the rom working Im going to have to go spend like $200 on a new phone today just sucks
fisterkev said:
Got the update last night. Tried to check voicemail morning and was greeted with Alvin & The Chipmunks blabbing at me. It's like the speed of the call is x20 speed or something. It's completely unusable. Phone sluggish as hell, too.
Anyone know what's going on with the voice speed? I've never heard of anything like this.
I'm supposed to get a callback for a job interview I had yesterday. Pretty crappy timing. How is Google going to push an update that breaks calls like this? Absurd.
Click to expand...
Click to collapse
Same thing happened to me with the sped up chipmunk-y sound. It happened during the dial and after someone picks up. Though it didn't seem to happen every time. Also, I didn't notice it on any incoming calls, just outgoing.
I tried a few things to fix it--rebooting, clearing some app caches, etc. Nothing seemed to work.
My next step was to try a factory reset, but then all of a sudden the issue disappeared. No new update was released/installed, so I just assumed the issue had been on my provider's end (T-Mobile), and they fixed whatever the problem was.
As for sluggishness of the phone after the update: I agree. It seems a little sluggish to me too. Not anything that is making the phone unusable. But it is noticeably more sluggish than when 9.0 was installed.
Have you guys modified the phone in any way like unlocking the bootloader or rooting?
gumbyx84 said:
Have you guys modified the phone in any way like unlocking the bootloader or rooting?
Click to expand...
Click to collapse
I haven't. Just using whatever over the air OS Nokia pushes to the phone.
yes I did pay to unlock the boot loader I used linage from the rom section
it has all the bugs of the stock rom. Cant call out or with out the loud noise bug and no voip apps work
I did get the Android 9 based rom to work. it has a few bugs but its usable.
I more or less gave up im looking at a iphone now.
I spend 20 hours or more trying to get this phone to work
first the usb port goes out and I cant charge.
2 weeks after having the phone back I got a magnetic cable so the usb port would not brake any more cable. That was like $20
After 2 weeks android 10 more or less bricks the phone (a phone that cant make calls)
Then I have to spend like $15 to pay the poor guy to unlock my boot-loader (he did a great job)
I spend a lot more time loading the linage android 10 rom for it to have the same bugs ( in no way is it the devs fault im sure he did not know).
... can unlock your bootloader for a small fee.
I would say all android 10 based rom will have those kind of problems. I can only confirm it on the android 10 linage one
When I flash twrp most of the time the twrp would just freeze if booting form the phone.
I had no problem loading it with fastboot works evey time. So I would only use it install the rom and just boot it when you need it. I would not suggesting flashing it to recovery as it only worked some of the time for me.
Hope all that info helps
QUOTE=gumbyx84;81261583]Have you guys modified the phone in any way like unlocking the bootloader or rooting?[/QUOTE]
---------- Post added at 06:48 PM ---------- Previous post was at 06:44 PM ----------
The calling problem goes in and out. Some times it works some times it dose not. Facebook message outgoing calls the mic will not work, Same with google voice.
if i make calls with out google voice it works 1/2 the time. all the people have the same problem
https://community.phones.nokia.com/discussion/54374/android-10-after-update-on-nokia-7-1
diggeryo said:
Same thing happened to me with the sped up chipmunk-y sound. It happened during the dial and after someone picks up. Though it didn't seem to happen every time. Also, I didn't notice it on any incoming calls, just outgoing.
I tried a few things to fix it--rebooting, clearing some app caches, etc. Nothing seemed to work.
My next step was to try a factory reset, but then all of a sudden the issue disappeared. No new update was released/installed, so I just assumed the issue had been on my provider's end (T-Mobile), and they fixed whatever the problem was.
As for sluggishness of the phone after the update: I agree. It seems a little sluggish to me too. Not anything that is making the phone unusable. But it is noticeably more sluggish than when 9.0 was installed.
Click to expand...
Click to collapse
How to fix the phone call problems
To everyone having calling issues (distortion / squealing, or other people can't hear them), try this: Turn off Voice over LTE. You go to Settings -> Wireless and Networks -> Mobile Networks -> VoLTE, and turn that setting off. This fixed the problem for all 3 Nokia 7.1 phones in our family, when nothing else seemed to work.
Turning off VoLTE and wifi calling works, but VoLTE is important in my area with TMobile. Without it, too many dropped and missed calls. I actually downgraded from an Xperia XZ1 just to get VoLTE, now this happens.
I have TA-1085 running Android 10 that was pushed OTA on 12/25, while I do not have calling issues (from native call app) initially, calling from all 3rd party app (e.g. Messenger or Wechat) are not working: I can hear other side, while the other side can not hear me.
In addition to disabling VoLTE, I also changed the 'preferred network type' (see posting from author 'fiumaxx' on nokia's user forum, search there using android-10-after-update-on-nokia-7-1 as search string). I changed it to LTE/CDMA which works well for me.
Normal call sound is back to normal but 3rd party calling still not working.
zhou68000 said:
I have TA-1085 running Android 10 that was pushed OTA on 12/25, while I do not have calling issues (from native call app) initially, calling from all 3rd party app (e.g. Messenger or Wechat) are not working: I can hear other side, while the other side can not hear me.
In addition to disabling VoLTE, I also changed the 'preferred network type' (see posting from author 'fiumaxx' on nokia's user forum, search there using android-10-after-update-on-nokia-7-1 as search string). I changed it to LTE/CDMA which works well for me.
Normal call sound is back to normal but 3rd party calling still not working.
Click to expand...
Click to collapse
This worked for me:
Go to Settings/Apps and Notifications and then tap on where it says See All xx Apps. Scroll down until you see the Google app and tap on that. On the next screen you see, tap on Permissions and then tap on Microphone. A small window will pop up, and you must change the setting from Allow to Deny.
After changing this setting, Google Assistant won't work (no Hey Google), but the fix is persistent after reboots. This makes me think the real problem may be with the Google app. We'll see.
ikijibiki said:
This worked for me:
Go to Settings/Apps and Notifications and then tap on where it says See All xx Apps. Scroll down until you see the Google app and tap on that. On the next screen you see, tap on Permissions and then tap on Microphone. A small window will pop up, and you must change the setting from Allow to Deny.
After changing this setting, Google Assistant won't work (no Hey Google), but the fix is persistent after reboots. This makes me think the real problem may be with the Google app. We'll see.
Click to expand...
Click to collapse
Thank you so much for sharing! Works like a charm
Unfortunately denying microphone for the Google app did not work for me. I also noticed no one can hear me when making videos calls (Hangouts, Duo, Facebook messenger).
I then decided to factory reset, but did not help. Both VoLTE and video calling still not working.
Anyone else with video calling mic issues?
zhou68000 said:
I have TA-1085 running Android 10 that was pushed OTA on 12/25, while I do not have calling issues (from native call app) initially, calling from all 3rd party app (e.g. Messenger or Wechat) are not working: I can hear other side, while the other side can not hear me.
Click to expand...
Click to collapse
I had the same symptom on normal phone call (other side could not hear me). In my case, it was the Google Assistant not releasing the microphone, and here what worked: open the system settings, go to Google (service&preferences)/Account services/Search, Assistant&Voice/Voice/Voice Match. Them make sure Access With Voice Match is ticked off.
Or try opening settings, searching at the top for "Voice" and open "Voice Match", and tick off "Access with Voice Match".
ikijibiki said:
This worked for me:
Go to Settings/Apps and Notifications and then tap on where it says See All xx Apps. Scroll down until you see the Google app and tap on that. On the next screen you see, tap on Permissions and then tap on Microphone. A small window will pop up, and you must change the setting from Allow to Deny.
After changing this setting, Google Assistant won't work (no Hey Google), but the fix is persistent after reboots. This makes me think the real problem may be with the Google app. We'll see.
Click to expand...
Click to collapse
Confirm this recipe works for my TA-1085. Thanks much.
I solved my random voice problems (others can't hear me on Duo video call, duplex voice on the other side etc.) with the voice match assistant workaround until hopefully gets fixed in a next update. Don't know for sure if the thing is only on Nokia's side or Google app's as well on Android 10, since disabling Hey Google solves all issues
Will have to try/catch on future google app updates as well to find out
Sly_North said:
I had the same symptom on normal phone call (other side could not hear me). In my case, it was the Google Assistant not releasing the microphone, and here what worked: open the system settings, go to Google (service&preferences)/Account services/Search, Assistant&Voice/Voice/Voice Match. Them make sure Access With Voice Match is ticked off.
Or try opening settings, searching at the top for "Voice" and open "Voice Match", and tick off "Access with Voice Match".
Click to expand...
Click to collapse
Under "Voice Match" I don't see any "Access With Voice Match" setting. What I do see is "Hey Google," which says "Access your Assistant any time you say "Hey Google" when your screen is on." Perhaps this is what your mean?
I tried this solution and it works, too. I think it also has the advantage of not completely shutting down Assistant's access to the microphone. Just waking up Assistant by voice. Much less of a price. Thanks!
Has anyone heard anything about a real fix for this issue? I've gotten two Android updates since the upgrade to Android 10, but this issue has not been fixed yet.
After extensive talks and inside info on Nokia's community forums, seems like a Maintenance update (MR) is on the way for May, which they say fixes -among others- both voice bugs. That is, the echo on calls plus sound distortion in some games (e..g Monument Valley 2 for me)
Cross your fingers everyone for a quick release and confirmation of the fixes!
Today was the day at last....! MR update showed up rolling out globally and echo during calls plus crackling sounds in games are finally gone
Better late than never NOKIA
dbal said:
Today was the day at last....! MR update showed up rolling out globally and echo during calls plus crackling sounds in games are finally gone
Better late than never NOKIA
Click to expand...
Click to collapse
Yes, they seem to have fixed the voice call problems with Whatapp, Wechat, Hangouts and etc since the Android 10 update.
Hi, I'm having a issue with my redmi note 9 pro. Whenever i try to make a call, it always goes to speakerphone. I cannot get it to go to the earpiece. WHen i try turning off speakerphone, the audio is still routed through the bottom speaker, and the person on the end of the call notices i sound broken up. WHen i swotch on the speakerphone the sound is clear, and then the person can hear me just fine. I've tried with whatsapp, google voice, and the regular phone app, and all have the same issue. I'm running Evolution X currently as my rom, but i've tried lineage os, and it has the same bug. On stock MIUI I don't remember having this issue, so maybe it's something weird with the custom roms. I'm also rooted with magisk. Anyone got any ideas, or has anyone ever experienced this issue when running custom roms on this phone? Any ideas, or suggestions are welcome. Thanks
Hi, I have this problem too. Of course inside the pubg mobile game. To temporarily solve this problem, first turn off the phone and connect the headphones when the operating system logo is displayed. A hissing sound is heard when plugging in the headphones.
Of course, to avoid this problem, you should use Bluetooth headphones.
Hi, I just tried your suggestion. it doesn't appear to work. My issue is with the earpiece, not headphones. Headphones for me have always worked flawlessly when running custom roms or stock. My issue is when making calls using the earpiece. Making calls using headphones seems to work fine. However when trying to use the earpiece, i cannot get it to work. What i mean by earpiece, is the top speaker of the phone, the one you have to hold close to your ear when making a call. FOr whatever reason calls always remain on the bottom speaker, and never seem to go to the top speaker aka earpiece. This happens in all calls, and in apps like whatsapp. Has anyone else ever experienced this issue? Again, headphones seem to work fine, and yes I'm rooted, and running a custom rom. When i was running stock, I don't ever remember this happening, but now that i'm running a custom rom, i can't get the earpiece to work. I really don't want to go back to the stock miui rom, but idk maybe i will if a solution can't be found
pielordbrian said:
Hi, I'm having a issue with my redmi note 9 pro. Whenever i try to make a call, it always goes to speakerphone. I cannot get it to go to the earpiece. WHen i try turning off speakerphone, the audio is still routed through the bottom speaker, and the person on the end of the call notices i sound broken up. WHen i swotch on the speakerphone the sound is clear, and then the person can hear me just fine. I've tried with whatsapp, google voice, and the regular phone app, and all have the same issue. I'm running Evolution X currently as my rom, but i've tried lineage os, and it has the same bug. On stock MIUI I don't remember having this issue, so maybe it's something weird with the custom roms. I'm also rooted with magisk. Anyone got any ideas, or has anyone ever experienced this issue when running custom roms on this phone? Any ideas, or suggestions are welcome. Thanks
Click to expand...
Click to collapse
I am having the same issue! any solution please let me know!
I am having the same problem - BUT on stock MIUI 12.5 - it started happening after I upgraded. If I could go back I would, but am happy to flasha new ROM if that will fix it.
I was thinking of flashing Lineage 18.1 but if that is having the save issue I ont bother. It must be a note 9 pro issue seeing as I only have the stock version..
I wonder if anyone at all has fixed this issue. I even contact xiaomi technical support but they were useless!
Anybody found its solution please update?
I'm having the exact same issue. When I initiate call it's on loudspeaker even though I didn't select that option. The other side can't hear me well. When I select "speaker" then it's still on loudspeaker, as it should be, and the other person can hear me fine.
I had the problem on crDroid (Android 12) and am currently experiencing the same problem on Pixel Experience (Android 12).
Please help someone us
I found the solution when I changed sim 1 to sim 2 the problem was solved.
mamamoiryani said:
I found the solution when I changed sim 1 to sim 2 the problem was solved.
Click to expand...
Click to collapse
Not quite sure I follow. Are you saying to remove sim 1? Or are you saying to change the default calling sim to sim 2 or something? I should note that I'm using both sims and a SD card. Are you saying I should just use sim slot 2?
mamamoiryani said:
I found the solution when I changed sim 1 to sim 2 the problem was solved.
Click to expand...
Click to collapse
Short version:
OK, so I just tried your advice, and it WORKED.
Long Version:
Ok, so I first removed both sims with the phone off. Then i put one of my 2 sims ONLY in slot 2 like you said. I inserted it into the phone, booted it up, and made a test call. To my surprise, the phone wasn't on speaker. I couldn't beileve it. I tried again, and it worked. I switched to speaker, now it's on speaker. I turned off the speaker and it was back to the earpeice! I tried whatsapp, and same result, the earpiece was working. I then decided to shut the phone down, and put the both sim 1 and 2 back in the phone. Guess what? after booting the phone up again, and making a test call, it still works! I don't understand the rhyme or reason behind it, but I'm not complaining. I'm so happy it FINALLY works.
to recap, Basically here are the steps:
1. Turn Off phone
2. Remove both sim cards.
3. Put a sim only in slot 2
4. Turn on phone and make a test call, it should no longer be on speaker!
5. go ahead and shut down the phone, and put a sim in both slots, if you are using 2 sims.
6. Turn the phone back on, and make a test call. It should still be working on the earpiece!
yes - this worked for me also - I have been looking for so long. A simple and un-remarkab le solution to a serious problem. Xiaomi should have been able to solve this.
All the same - thank you!
Great phone that was hindered for quite a few months by this serious problem
Again - thank you !
mamamoiryani said:
I found the solution when I changed sim 1 to sim 2 the problem was solved.
Click to expand...
Click to collapse
Thank you so much. I have been waiting for it for more than a year.