Hi guys,
Kind of new to pocophone but I'm experiencing something really strange that I haven't on any other phone I've had before. Here's the background..
I bought the phone as a gift for my mum and she absolutely loves it but she's told me the phone will randomly make a call itself. I didn't believe it until I saw it happen. She can be on the phone (having made or received a call legitimately) and the call will automatically be put on hold waiting for her to answer a call from another person. The issue is, that person hasn't called her so when she calls back, the person is confused. This can also happen when she isn't on the phone
I checked her call waiting options (turned off and on, neither makes a difference) and reset the phone to factory settings but still getting the same issue. We haven't set up Google assistant or anything similar so the calls wouldn't have been made my a voice command either.
It's really strange and I've looked on the Internet but can't find anything reported on it. The phone is running miui 10 and she is on virgin mobile. The phone is less than 2 weeks old.
Any help is much appreciated.
Vik
Haven't faced something similar. If I were in your shoes, I would 1. Factory reset everything, 2. flashed latest global stable miui ROM and 3. checked again if the same problem persists.
melodystyle2003 said:
Haven't faced something similar. If I were in your shoes, I would 1. Factory reset everything, 2. flashed latest global stable miui ROM and 3. checked again if the same problem persists.
Click to expand...
Click to collapse
Thanks @melodystyle2003. I've tried a factory reset on the phone. When the phone does a factory reset, would that not install the latest stable miui ROM? It installed miui 10 and when I checked for updates on the phone, it informed me that there were no more updates available
I think the problem is, proximity sensor. This used to happen to older family member.
About phone->MIUI version, which version does it use?
green. said:
I think the problem is, proximity sensor. This used to happen to older family member.
Click to expand...
Click to collapse
Thanks @green. Did you ever find a solution to that proximity sensor issue?
melodystyle2003 said:
About phone->MIUI version, which version does it use?
Click to expand...
Click to collapse
@melodystyle2003 here's the version information I see when I go to about phone : Miui Global 10.1. Stable. 10.1.3.0. ( PEJMIFI)
vikz.t said:
@melodystyle2003 here's the version information I see when I go to about phone : Miui Global 10.1. Stable. 10.1.3.0. ( PEJMIFI)
Click to expand...
Click to collapse
This is the latest stable version.
Install the google dialer, and force stop the default one. Also, try switching your network connection, like if it's on 3G, shift it to 2G or vice versa, for some time.
And if proximity sensor is the cause (as mentioned by another fellow member), you can check the sensor wake up time through BBS or similar app. Proximity sensor does appear in the sesnor column of BBS app. And going through the wakelock's data, you might also be able to detect any other possible cause.
Have you tried switching off the 'redial automatically' option in the dialer options? That seems to be your problem.
vikz.t said:
Thanks @green. Did you ever find a solution to that proximity sensor issue?
Click to expand...
Click to collapse
It's not the hardware fault. Old people tends to keep the phone slight upwards while speaking, the proximity sensor wakes the screen and by accidentally registers the touch. This usually happens and the accidentally put the call on hold, accepts the second call or the add new call. You can try using the phone for a day.
Old thread, but just wanted to add that we have the same issue with a Pocophone we use at work. When you put away the phone after a call, then at random times it calls the last person you talked to before the current call. Does it about 1 out of 40 calls and is 100% a phone firmware issue, not some old lady holding her phone wrong.
Related
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!!!
Bought the Atrix last week and unlocked it with the help from the webshop as I'm in Belgium, no problem connecting to Mobistar wich is my provider and data connections works great. But I'm having real problems making phonecalls and recieving calls; the phone reboots or the dialer hangs and it looks like a call is going on when it's not, phone still works but flashing green in the notification area and it's impossible to hang up, need to reboot. This happens like 80% of the times I try to make a call. After a reboot it works fine to call and hang-up one or two times then it crashes again.
Also noted that my Dialer often runs twice in the Running Apps manager - is that normal??
Anyone having the same issues or know what to do, reinstall the Dialer app --> if so how? Is it a hardware or software problem??
A little more info: when I recieved the device it was in a sealed Atrix box but the phone was used and already had an active Blur account so I had to do a hard reset to be able to use it... --> was it returned 'cause of faulty dialer or radio... then resold to me... not nice if so...?
Tried to install dialer one app but it seems only to skin the original dialer...
It's a greate device and works great othervice but in the end it's still a phone... which should be able to make calls...
Help
Ive got an unlocked Atrix too and now in Germany, I have the same problem. Motorola should definitely look into this.
Here's a quick fix for it thou, (not permanent)....
1. type *#*#4636#*#* on the dialer
2. Chose Phone Information
3. Set preferred network to GSM only
Viola...its fixed
problem with this fix is that you wont be able to use your 3G network but the dialer should be working.
Thanks Nazrin (for both replies) !!
It sure did the trick, though no data access is not acceptable on a phone like this!!!
So this meens that all unlocked Atrix's in european GSM networks have the same problems? Haven't seen any others reporting this and there are quite a few in use I've noted in other forums.
Was thinking of trying to have mine replaced (which probably won't be easy and take long time...) but that won't change anything then??
We have to wait for the european version of Atrix rom I suppose??
Any others with the same problem??
No problems buddy, glad it worked..and i have to agree with you..this bug is unacceptable...it seems the phone just ***** up everytime it calls on utms (3g)...im sure there is more people with this problem...
Sent from my Supercharged MOTO ATX
I have the same problem
Hi guys, I have the same exact issue (I'm also in Belgium, on Mobistar). I'm somewhat glad to hear this is a generic issue, and not an issue with my specific phone. At least I can be fairly certain replacing it won't solve this issue then.
I made another post here before I came across this one, has a bit more info: we are seeing modem panics when using 3G + outbound call. I've also contacted Motorola support to no avail:
http://forum.xda-developers.com/showthread.php?t=1028771
You can also read there that I tried another operator, and it did not crash with that one (although 3G did disconnect).
Hopefully Motorola/Qualcomm will start to notice the bug when they release the phone globally, and release a fix.
Either that, or we all have phones from the same bad batch
This bug is really bad for users in europe....cant call on utms...
I really hope motorola takes this seriously cos if there's no fix via software updates then its moto gone for me
Guys, you are all on unlocked att atrix right? I do believe it is a simmiliar software glitch/bug/lock that you have porblems using it on non att networks as the problem with the wifi that it stops working for some of us (check the thread about it for more info). As all suggests there it is a config file problem, unfortunately i or anyone else doesnt know yet which one....
Yeah maybe..but funny thing is wifi is working without a glitch...will have to read that forum later...
Workaround options
So, since it seems we're not gonna get this fixed until there is a new radio/modem firmware available for flashing (and even then..), I've been looking for a workaround.
Found two potential applications that could do what we need: disable data completely when making an outgoing call, or switch to 2G:
- Sanity
- Superpower
I've tested the first (Sanity), and it does not work (fully). It does seem to disable data, but the bands aren't switched so our problem remains. I've contacted the developer here: http://tagliamonte.net/forum/thread-10.html. He seems to be very responsive, so given enough interest, I think he would add the functionality we require.
The second app I only came across today, and have not tried yet. It does not have a function to specifically switch bands when making an outgoing call, but it has a trigger for "Foreground application", so if we make that the dialer/contacts... Question remains if it will be able to do the switch.
Hopefully one of these will lead to a decent workaround for all of us!
Well done unknown...i will try these apps... but the real fix should be from moto...im always reading the net for anything that can solve this issue
reboots on incoming and outgoing calls
Same in Russia on Megafon network, I had to enter 4636 menu and use it as "GSM only". Even this does not fully solve problems, e.g. call forwarding does not show the new destination number while it does actually make the phone divert calls correctly.
My hope is that UK release will trigger new software version which will address this issue. ANYONE has news on this?
FIXED!
YAY! I just fixed this issue
What you need to do: flash the radio from this thread:
http://forum.xda-developers.com/showthread.php?t=1052914
You have to use RSD-lite, since sbf_flash will not work. Flash the 1.87 baseband and enjoy working HSPA (including unlocked upload speeds ^^)
Now I can finally appreciate this phone fully
Enjoy guys!
_unknown said:
YAY! I just fixed this issue
What you need to do: flash the radio from this thread:
http://forum.xda-developers.com/showthread.php?t=1052914
You have to use RSD-lite, since sbf_flash will not work. Flash the 1.87 baseband and enjoy working HSPA (including unlocked upload speeds ^^)
Now I can finally appreciate this phone fully
Enjoy guys!
Click to expand...
Click to collapse
Worked for me as well..brilliant!!!! its working here in germany.....but I wonder the telstra radio will work in my home country with frequencies of 900/2100
Motorola Atrix restart when placing a call
I just got the same exact Dialer problem now, but the flash radio file is gone* in the pointed post, and I don't know exactly how to flash the radio.
Someone can help me? I need the radio file and step by step instruction to how to flash it.
BTW my Atrix 4G works perfect for a year till this Dialer problem started past week.
I also use my phone as a full Linux computer when docked, and it works very fine.
Thanks
* The file was on megaupload, that was closed
No answer
Why I never got an answer of any post I did?
There is something wrong?
Eli
elijacob said:
I just got the same exact Dialer problem now, but the flash radio file is gone* in the pointed post, and I don't know exactly how to flash the radio.
Someone can help me? I need the radio file and step by step instruction to how to flash it.
BTW my Atrix 4G works perfect for a year till this Dialer problem started past week.
I also use my phone as a full Linux computer when docked, and it works very fine.
Thanks
* The file was on megaupload, that was closed
Click to expand...
Click to collapse
Forget about those ways
klingsurf said:
Bought the Atrix last week and unlocked it with the help from the webshop as I'm in Belgium, no problem connecting to Mobistar wich is my provider and data connections works great. But I'm having real problems making phonecalls and recieving calls; the phone reboots or the dialer hangs and it looks like a call is going on when it's not, phone still works but flashing green in the notification area and it's impossible to hang up, need to reboot. This happens like 80% of the times I try to make a call. After a reboot it works fine to call and hang-up one or two times then it crashes again.
Also noted that my Dialer often runs twice in the Running Apps manager - is that normal??
Anyone having the same issues or know what to do, reinstall the Dialer app --> if so how? Is it a hardware or software problem??
A little more info: when I recieved the device it was in a sealed Atrix box but the phone was used and already had an active Blur account so I had to do a hard reset to be able to use it... --> was it returned 'cause of faulty dialer or radio... then resold to me... not nice if so...?
Tried to install dialer one app but it seems only to skin the original dialer...
It's a greate device and works great othervice but in the end it's still a phone... which should be able to make calls...
Help
Click to expand...
Click to collapse
[Sorry for problem in speaking]
i had that problem too , im using CM13 with Marshmallow Version of android
So . the easy way is :
***** search "Default" in settings. then choose " System dialer" as Default ! just it ****
but if there is no search bar in your setting . try this patch:
Android 6 : Setting/Apps then click the setting icon on top(may be diffrent in your case) , then Click on "default ...." then choose " System dialer" as Default! :fingers-crossed:
but in some cases that it didnt work . they have to reinstall gapps .
Or in official Roms , reset will be usefull
any quastions?
hey all,
I am not new to roms or kernels, etc. I have been addicted since my G2.
For the life of me, in the last two days, I cant figure out why my phone goes into speaker mode when I dial a number.
I am sure there is an easy fix. I was using Cognition 1.51 but went back to 1.42 and am using speed mod T27.
Is there a setting I am missing out on?
Thanks for you help, I am tired of having to remove from speaker mode and am close to doing a full wipe and install but would like to avoid this if possible
Edit: I cleaned the USB port and although it was clean, its seems to have made a difference, although it still happens on most calls. Could this be possible?
I am too having the same problem...this is frustrating
Hey there!
Same thing just started happening for me today
Although it doesn't affect all the calls and all numbers, but certain numbers, when they call me, I have this problem
Also, a reboot doesn't help, and the pattern is erratic.
Meaning sometimes the same number calls me, it happens, but sometimes it doesn't.
HEY GUYS!
Do you use GOsms pro? There is a bug report that the version dated 29 Aug messes around with the speaker calls, and the symptoms are consistent with what I'm experiencing, after just updating two days ago
I have updated to the 31 Aug version and will observe if there are anymore such symptoms. Keeping my fingers crossed!
rantzzz said:
HEY GUYS!
Do you use GOsms pro? There is a bug report that the version dated 29 Aug messes around with the speaker calls, and the symptoms are consistent with what I'm experiencing, after just updating two days ago
I have updated to the 31 Aug version and will observe if there are anymore such symptoms. Keeping my fingers crossed!
Click to expand...
Click to collapse
i use Go SMS....I will update it again right now..Hope it will fix
Check the Cognition thread folks,even after updating GO SMS it still happens, even people who don't use GO SMS have this problem which would lead me to believe it is a bug with this latest version of Cognition that needs to be resolved.
jonny68 said:
Check the Cognition thread folks,even after updating GO SMS it still happens, even people who don't use GO SMS have this problem which would lead me to believe it is a bug with this latest version of Cognition that needs to be resolved.
Click to expand...
Click to collapse
Cognition?
Thanks All!
Glad its not something stupid I had done
Updated goSMS and went back to using Cognition 1.40
All seems fine now, will recharge and reboot a few times and see if it happens again
I've had the same issue since i got the phone this monday.
I were ready to have it replaced and found this thread.
Updated go sms pro to todays version and it solved the issue.
Thanks!
Having the same problem too. I haven't rooted my phone (yet) so using standard Samsung rom. It happens on some (not all) calls and is annoying. Recently had other problems with the phone going into carmode by itself. Those seem to have stopped after cleaning the usbport. But the speakermode is persistent. Even after updating GoSms. It appears lots of users are having problems with the S2. This can't be a coincidence. Major flaw from Samsungs side imo...
Apparently after updating, it could happen again
Check out the changelog on GoSMSpro, it states:
2. Fix bug of call is defaulted to speaker(After update, if speaker is still on due to previous version's bug, turn off，it will be OK later)
Wtf?
For the record, it happened to me again today. Impacted one particular number, but subsequently same number called, the speaker was not activated..
Why oh why did they have to mess with calling
Mine is well and truly fixed now.
Back on Cognition 1.40 and Using Ragemod V2 T27 and the update to Go SMS and everything is perfect.
For me I think the GoSmS update was the fix but I reflashed before applying their update.
Problem solved is the main thing
Hi guys,
I am using the S6 Edge (DBT version) with stock Rom. I recently upgraded to 6.0.1 and did a hard reset afterwards. When I first opened whatsapp and tried to make a call I noticed that the screen is always on. When I make a call using the regular phone app (Skype also works, If I remember correctly) the proximity sensor does its job.
My WA version is: 2.16.69
I don't know how to fix this. Can you guys please help me?
Kind Regards,
CombatWombat666
Update:
I did a soft- and a hardreset . Nothing changed. Proximity sensor is still not working with WhatsApp.
I wrote WA about it but did not get an answer, yet.
Any help?
bump
Dear god, I located the issue. It was due to the WhatsApp Beta which I was signed for. If anybody else experiences such issues, delete WA Beta and get yourself the ordinary version.
I have the same issue and was signed up for the beta. Opted out and then Uninstalled and reinstalled the regular version and yet have an issue! Any ideas?
I have the same issue tried uninstalling and reinstalling. WhatsApp version 2.16.95 I never subscribed to the beta service. Any luck anyone.
same problem here. In order to make screen off, I'm just pressing power button on call.
Facing the same problem on my Galaxy S6 with Marshmallow.
Nothing to do with Beta version, same issue on regular version of whatsapp as well.
I un-installed updates and reinstalled them again, reinitialized whatsapp and still no luck, the problem persists.
Any luck with finding the resolution?
same issue
houssam10001 said:
same issue
Click to expand...
Click to collapse
Any update on this please? I am having the same problem, very annoying! My phone is rooted but since the problem exists on stock ROM as well I think it's connected to base directly. I have tried full factory reset of the phone with no luck.
Installing beta app ver. 2.16.189 seems to fix my proximity sensor issue during whatsapp call.
I'm at stock rom G925I.
I had the same problem with my g6 and solved it as follows: 1 uninstall whatsapp 2 do an update by power off and pressing the 3 bottons power, volumen up and menu at the same time and 3 reinstall the latest or beta whatsapp. That should solved it.
Hello,
I am currently having some issues with voice calls on my oneplus, I am writing this because maybe someone else had the same problem and has a solution for it.
The Problems is, that during calls, I dont hear the other Person for about ~10 seconds, or maybe more. This happens most of the times within the first half minute. When it happens I dont hear any voice but the other Person hearing my voice. Besides that the Stock Dialer App turns crazy. It freezes when I hang up or it doesnt hang up when I do so and keeps the call on the background and responds a couple of seconds later.
The weird thing is I have Zero '0' Issues with Whatsapp calls, or any other speaker issues, any other mic issues or anything that would come to mind. I already hard resetted my phone, cleared cache with advanced reboot, tryed the stock google dialer but having same issues with it.
Does anybody had or having same/similar issues with the Oneplus 7T Pro. (updates 10.0.7.HD01BA)
Thx for any help!
ertu54 said:
Hello,
I am currently having some issues with voice calls on my oneplus, I am writing this because maybe someone else had the same problem and has a solution for it.
The Problems is, that during calls, I dont hear the other Person for about ~10 seconds, or maybe more. This happens most of the times within the first half minute. When it happens I dont hear any voice but the other Person hearing my voice. Besides that the Stock Dialer App turns crazy. It freezes when I hang up or it doesnt hang up when I do so and keeps the call on the background and responds a couple of seconds later.
The weird thing is I have Zero '0' Issues with Whatsapp calls, or any other speaker issues, any other mic issues or anything that would come to mind. I already hard resetted my phone, cleared cache with advanced reboot, tryed the stock google dialer but having same issues with it.
Does anybody had or having same/similar issues with the Oneplus 7T Pro. (updates 10.0.7.HD01BA)
Thx for any help!
Click to expand...
Click to collapse
No issue here.is this problem arrived after updating?if yes then try factory resetting.still Not working? Try downgrading.
Sent from my HD1910 using Tapatalk
samrattt said:
No issue here.is this problem arrived after updating?if yes then try factory resetting.still Not working? Try downgrading.
Sent from my HD1910 using Tapatalk
Click to expand...
Click to collapse
Hey, I am actually not sure if it happened after updating to the latest version. But it might occoured after the update. I did a factory reset and cleaned cache, but still. I didnt thought about downgrading thanks I will try it and say if it helped.
samrattt said:
No issue here.is this problem arrived after updating?if yes then try factory resetting.still Not working? Try downgrading.
Sent from my HD1910 using Tapatalk
Click to expand...
Click to collapse
Hey, I was doing some research how to downgrade the firmware of my Oneplus, but couldn't find a way how to do it. Can you tell me how to do it?
Edit: Downgrading didnt helped. Downgraded to 10.0.5 and still the same problem ....
ertu54 said:
Hey, I was doing some research how to downgrade the firmware of my Oneplus, but couldn't find a way how to do it. Can you tell me how to do it?
Edit: Downgrading didnt helped. Downgraded to 10.0.5 and still the same problem ....
Click to expand...
Click to collapse
Check if it's your network