Hi all,
I've bought a brand new Mi Mix 2S device, and I'm having some issues with the proximity sensor. When accepting a phone call or listening a WhatsApp audio message the screen goes black. It won't light up again until the person calling terminates the call; with WhatsApp audio message it's still worse: I have to lock the screen and unlock it again in order to see something. I've tried to recalibrate it using the hardware test (*#*#*****#*# - I can't remeber the precise number atm), but in the proximity sensor menu the reading is 0 no matter of the sensor covering.
Is there any way I can solve this issue ? Is it a hardware problem ?
Thanks in advice
I have the exact same problem. It seems to happen frequently but not 100% of the time.
rainbow99 said:
I have the exact same problem. It seems to happen frequently but not 100% of the time.
Click to expand...
Click to collapse
I'm wondering if it could be related to the glass screen protector interfering with the ultrasonic proximity sensor...
Drogor said:
I'm wondering if it could be related to the glass screen protector interfering with the ultrasonic proximity sensor...
Click to expand...
Click to collapse
I think it is. Because mine started doing that when I dropped the phone once on the road. But as the other user said it doesn't do that 100% of the time
Sent from my Mi MIX 2S using Tapatalk
fopoku2k2 said:
I think it is. Because mine started doing that when I dropped the phone once on the road. But as the other user said it doesn't do that 100% of the time
Sent from my Mi MIX 2S using Tapatalk
Click to expand...
Click to collapse
My protector is not broken though... anyway where is the sensor positioned ?
Drogor said:
My protector is not broken though... anyway where is the sensor positioned ?
Click to expand...
Click to collapse
No idea
Sent from my Mi MIX 2S using Tapatalk
fopoku2k2 said:
No idea
Sent from my Mi MIX 2S using Tapatalk
Click to expand...
Click to collapse
The thing is mine does that 100% of the times... I fear it might be a hardware problem
Drogor said:
My protector is not broken though... anyway where is the sensor positioned ?
Click to expand...
Click to collapse
Here's a teardown of the Mix 2s and it shows the location of the sensor.
https://www.myfixguide.com/xiaomi-mi-mix-2s-teardown/
No problems with mine but I've only had it a couple days, I do have a glass screen protector coming and will see if that makes a difference once installed.
Thanks to everyone for your help. I've rebooted the phone several times and after the second reboot the calibration seemed to work. Now the sensor seems to work properly (at least at this very moment ).
Seems it was a software issue
How do you perform a proximity sensor harware test?
To the ppl having a problem:
Does your screen protection glass has holes for the sensors??
Thanks for information
Hello all,
My mix2s has this situation too, and does not have screen protection, if anyone finds a solutions please post here.
Thanks,
mine was working well until i flashed the new global beta. nownproximity sensor not working for me.
I tried nearly everything to fix the issue with my proximity sensor, which completely stopped working.
I have also created a poll on xiaomi.eu forum (https://xiaomi.eu/community/threads...nsor-work-as-in-non-ultrasonic-devices.46293/) in order to understand which was the normal functionality of the ultrasonic sensor. Indeed, I suspect that my sensor never worked as expected, as the screen often switched on during calls even if no notifications were received.
According to the hardware test, the sensor doed not work at all.
I tried to flash the persist.img partition but nothing as changed.
Instead, all the other sensors are working fine.
In order to understand if mine and yours is an hardware or software issue, could you please report if you are 100% sure that before flashing a custom rom the ultrasonic sensor worked properly?
I had exactly the same problem (sensor not working all the time or anormal behavior) and it was a hw fault. My solution was a warranty replacement. Now everything works fine.
esteras said:
I had exactly the same problem (sensor not working all the time or anormal behavior) and it was a hw fault. My solution was a warranty replacement. Now everything works fine.
Click to expand...
Click to collapse
As I wrote, my guess is that I also have an hardware issue. The sensor never worked properly and eventually stopped working. The fact that I also flashed a rom during that period is just a coincidence.
---------- Post added at 05:02 PM ---------- Previous post was at 05:00 PM ----------
esteras said:
I had exactly the same problem (sensor not working all the time or anormal behavior) and it was a hw fault. My solution was a warranty replacement. Now everything works fine.
Click to expand...
Click to collapse
One last question: how does the ultrasonic sensor work now? Just like non-ultrasonic sensors? The screen remains switched-off as expected during calls?
guildamx said:
As I wrote, my guess is that I also have an hardware issue. The sensor never worked properly and eventually stopped working. The fact that I also flashed a rom during that period is just a coincidence.
---------- Post added at 05:02 PM ---------- Previous post was at 05:00 PM ----------
One last question: how does the ultrasonic sensor work now? Just like non-ultrasonic sensors? The screen remains switched-off as expected during calls?
Click to expand...
Click to collapse
Now it works as the other phones that I had, very fast. Switch off when I put it near my ear and switch on again when I put it far away. There isn't any difference.
esteras said:
Now it works as the other phones that I had, very fast. Switch off when I put it near my ear and switch on again when I put it far away. There isn't any difference.
Click to expand...
Click to collapse
Thank you very much.
Since my sensor never worked that good, I suppose it was faulty from the beginning.
I use to have that problem too, but then I realized that could be a problem with the case I was using. I took it off and now I don't have any issue with the sensor
rodaven said:
I use to have that problem too, but then I realized that could be a problem with the case I was using. I took it off and now I don't have any issue with the sensor
Click to expand...
Click to collapse
Thank you but it is not my... case
I use the one provided in the box by Xiaomi and moreover the issue is there even if I remove the case.
Related
I don't know if this is just an issue with me or if others are experiencing the same issue.
for some reason my proximity sensor is VERY sensitive... for example if I move my face just 1/2 and inch from the screen my screen turns on and I either press "Mute" or "Speaker" with my cheek OR i hang up on the person I'm calling when I place the phone back against my face.
This happens about 50% of the time... so every other call I make has this issue.
I don't know if I can change the sensitivity or the length of time before the screen turns on.
I'm coming form the Eris/D1/DX/Fascinate and I never had these issues with my older phones.
Any advice or Steps to fix this would be greatly appreciated.
Plz Advise
Happens to me too, but I don't manage to hang up or mute the calls normally. I'd love a solution as well!
Magicadder said:
I don't know if this is just an issue with me or if others are experiencing the same issue.
for some reason my proximity sensor is VERY sensitive... for example if I move my face just 1/2 and inch from the screen my screen turns on and I either press "Mute" or "Speaker" with my cheek OR i hang up on the person I'm calling when I place the phone back against my face.
This happens about 50% of the time... so every other call I make has this issue.
I don't know if I can change the sensitivity or the length of time before the screen turns on.
I'm coming form the Eris/D1/DX/Fascinate and I never had these issues with my older phones.
Any advice or Steps to fix this would be greatly appreciated.
Plz Advise
Click to expand...
Click to collapse
Which kernel / rom are you using? I have heard that some kernels have caused proximity sensor issues but I'm not sure if the issue others have experienced is the same as yours. I'd try a battery pull first, if that doesn't help try a different kernel and see if that fixes it. If the issue still persists, it could be a hardware issue and you might have to get the phone exchanged under the manufacturers warranty.
Sent from my Thunderbolt using Tapatalk
m00nshake said:
Which kernel / rom are you using? I have heard that some kernels have caused proximity sensor issues but I'm not sure if the issue others have experienced is the same as yours. I'd try a battery pull first, if that doesn't help try a different kernel and see if that fixes it. If the issue still persists, it could be a hardware issue and you might have to get the phone exchanged under the manufacturers warranty.
Sent from my Thunderbolt using Tapatalk
Click to expand...
Click to collapse
I'm using Stock firmware with bamf 4.3a Kernal
I've reset this thing too many times... installing different roms and such.. but I can verify that this is happening to another phone. My wife's phone does exactly the same thing. we purchased out tbolts on launch day ( if that helps )
The proximity sensor is located were the Verizon V is at
In between the big V is the sensor. Very hard to see go under a light a tilt the like you would if you want to find scratchs on your phone it really is between the V or I'm you can not find it. Make a phone call and get your index or any finger. And again make sure your under light and make the shadow of your finger go on top of the proximity sensor. Mine is very sensitive also.
-Monky_1
-Monky_1
My proximity sensor seems pretty touchy, as well.
I initially thought it to be a problem with a particular version of Adrynalyne's kernel, but I'm not so sure anymore. Adrynalyne also said that a kernel shouldn't affect the proximity performance -- that HTC puts these setting or whatever in the framework (what that means exactly, I'm not sure).
Anyway, I haven't done any exhaustive testing or anything, but I did notice one thing that seems to help keep my screen off is to have the thing pointed straight down while on the phone. My natural inclination is to have it along my jaw line, with the end pointed at my mouth. But the proximity sensor is to the left-of-center on the phone. Angling it moves the sensor away from your ear a bit. Assuming you've got it up to your right ear, that is.
I'd still welcome any other points folks might have about this.
calbruc said:
My proximity sensor seems pretty touchy, as well.
I initially thought it to be a problem with a particular version of Adrynalyne's kernel, but I'm not so sure anymore. Adrynalyne also said that a kernel shouldn't affect the proximity performance -- that HTC puts these setting or whatever in the framework (what that means exactly, I'm not sure).
Anyway, I haven't done any exhaustive testing or anything, but I did notice one thing that seems to help keep my screen off is to have the thing pointed straight down while on the phone. My natural inclination is to have it along my jaw line, with the end pointed at my mouth. But the proximity sensor is to the left-of-center on the phone. Angling it moves the sensor away from your ear a bit. Assuming you've got it up to your right ear, that is.
I'd still welcome any other points folks might have about this.
Click to expand...
Click to collapse
This is exactly what's happening. It's nice to see that I'm not the only one having this issue... even tho I'm sure it's annoying for everybody. Hopefully we'll be able to get some relief from this.
http://market.android.com/details?id=i4nc4mp.myLock.phone
This app keeps me from smashing my Droids.
this is not a signature I type it in every time maybe sent from my phone or my computer
rizzomegav said:
http://market.android.com/details?id=i4nc4mp.myLock.phone
This app keeps me from smashing my Droids.
this is not a signature I type it in every time maybe sent from my phone or my computer
Click to expand...
Click to collapse
Would this work even tho the Thunderbolt has no physical Trackball or Camera Button?
Not to discredit this app Kudos to the Dev who wrote it, but it seems like a work around and not an actual Fix.
But I'll try it out and reply back with some feedback
Here's what I do and it works for me most of the time. When making or receiving a call, once the call is 'connected' I quickly hit the 'home' button so I'm no longer on the 'phone screen' & then the power button which darkens & locks the screen. Even if the proximity sensor allows the screen to light up, the lockscreen is still there and prevents me from muting or hanging up on the other person. It's not a perfect solution since my jaw has managed to unlock the screen & randomly open apps occasionally but it beats hanging up on someone every 5 seconds.
Sent from my NookColor using Tapatalk
I'll just throw my hat in that I am experiencing the same issues of muting/hanging up on people. I don't recall having the issue on the stock ROM, but have really noticed it since I've been on BAMF 1.5 with Adrynalyn's 4.4.2 kernal included with BAMF 1.5.
I was running 4.4.2 with the stock ROM before BAMF 1.5 and don't recall having proximity sensor issues. Who knows?
Edit: Anybody think that screen protectors are causing interference in any way? I have an Invisible Shield that I've had since shortly after launch date.
gatorguy said:
I'll just throw my hat in that I am experiencing the same issues of muting/hanging up on people. I don't recall having the issue on the stock ROM, but have really noticed it since I've been on BAMF 1.5 with Adrynalyn's 4.4.2 kernal included with BAMF 1.5.
I was running 4.4.2 with the stock ROM before BAMF 1.5 and don't recall having proximity sensor issues. Who knows?
Edit: Anybody think that screen protectors are causing interference in any way? I have an Invisible Shield that I've had since shortly after launch date.
Click to expand...
Click to collapse
BAMF 1.5 is based on the new leak, which includes a fix for the proximity sensor. If the rom you are running isn't based on the recent leak for our phones, then you don't have the fix, and will most likely have problems with it.
Check this thread out at droid forums! It fixed my "problem" with the proximity sensor. Simply blow out the sensor with air. Apparently dust gets in there and jacks it all up. I can confirm big time results with this method.
http://www.droidforums.net/forum/thunderbolt-tech-support/142050-thunderbolt-proximity-sensor-issue.html
Edit: All those kernel switches and setcpu tweaks over pocket lint!!! Damnitman!
Magicadder said:
Would this work even tho the Thunderbolt has no physical Trackball or Camera Button?
Not to discredit this app Kudos to the Dev who wrote it, but it seems like a work around and not an actual Fix.
But I'll try it out and reply back with some feedback
Click to expand...
Click to collapse
Well the fix is only to hold the phone correctly unfortunately. My gf has no problem using either phone (hers or mine) but if I touch them its muted hang up bam.
One of my coworkers has the same problem as me another dosent. Its absolutely user errorish IMO.
It works with my thunder bolt sort of the home key still works. I don't mind it, moreso than buggered calls.
this is not a signature I type it in every time maybe sent from my phone or my computer
gatorguy said:
I'll just throw my hat in that I am experiencing the same issues of muting/hanging up on people. I don't recall having the issue on the stock ROM, but have really noticed it since I've been on BAMF 1.5 with Adrynalyn's 4.4.2 kernal included with BAMF 1.5.
I was running 4.4.2 with the stock ROM before BAMF 1.5 and don't recall having proximity sensor issues. Who knows?
Edit: Anybody think that screen protectors are causing interference in any way? I have an Invisible Shield that I've had since shortly after launch date.
Click to expand...
Click to collapse
A screen protector was an issues for me. The first one I put on did not fit perfectly, so the top of the protector cut directly threw the center of the sensor and collected dust and gave me some issues. The second one i used was applied from the top down to not obstruct the sensor. Solved my problem.
My phone sensor will black out when I am on a call and the phone is against my face, but when I pull the phone away the screen won't come back up for some reason..
I find that it seems to reflect off the arm of my glasses, which is kinda glossy like. When the IR LED reflects back at it, it seems to assume infinite distance. Same thing happened on my Droid.
There was also a case that lacked the cutout for the proximity sensor on the Droid... screen would never turn off because it reflected the IR.
I'm glad to see I'm not the only one with this problem. It's been happening to me for a few weeks now. I've run the majority of available ROMs and kernels (pre- and post- radio update) in multiple combinations so, I believe its safe to say they are not to blame.
I'm not using a screen protector so, that can't be to blame. And I don't have any scratches on my screen either. I'm curious about this dust theory though. It may be the best one I've heard yet. Has anyone else put the air hose to their Thunderbolt yet? I think I'm gonna give it a go asap. But, in the meantime, I'd love to hear whether anyone else has had positive results. If not, I fear I may have to move on to the glasses theory. I really hope it isn't that one though. I don't want to choose between having my Thunderbolt or my sight!
Mine still does it and I'm using the leak , so I don't think there is a fix in it. If so it doesn't work. Locking the screen seems like a pain but that's the best bet for now.
Sent from my ADR6400L using XDA Premium App
dzigns said:
Here's what I do and it works for me most of the time. When making or receiving a call, once the call is 'connected' I quickly hit the 'home' button so I'm no longer on the 'phone screen' & then the power button which darkens & locks the screen. Even if the proximity sensor allows the screen to light up, the lockscreen is still there and prevents me from muting or hanging up on the other person. It's not a perfect solution since my jaw has managed to unlock the screen & randomly open apps occasionally but it beats hanging up on someone every 5 seconds.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
After trying many ways to work around this problem with the proximity sensor I have found that this is actually works the best .... And I can't thank you enough..... I've grown used to this method and so far its flawless.
Thank you again
Sent from my ADR6400L using XDA App
Hello,
After clean install Android 5.0 on Nexus 5 I have lost all sensors.
Do you have similar problem?
Is there any solution to fix it?
What app are you using? This looks like a bug in an app, than in Android itself.
I had this problem even before installed any apps. In android l developer preview I didn't have sensors also, so after installed final version of lollipop the first thing I made was check sensors. On kitkat everything worked perfect.
Wysłane z mojego Nexus 5 przy użyciu Tapatalka
i don't have light and proximity sensors too...
i did full wipe and flash stock OTA
hope they will fix it soon
Since upgrading to Lollipop my proximity and light sensor also stops working after a few minutes. It works again after a restart, but only for a few minutes.
I have flashed 4.4.4 again and the problem is not present there. After upgrading to 5.0 again the problem came back.
the apps are the issue here gentlemen.
1.On call as you bring your phone to ear, screen turns off?Proximity working
2.Adaptive brightness enable and use the phone on same brightness settings in bright and dim areas, screen brightness intensity change?Light sensor working.
3.Screen rotates views?Accelerometer working.
4.Play asphalt or any other motion requiring game, car turns?Gyro working.
5.Open maps, get pointing direction?compass working.
6.Use pedometer, counter change?step counter working.
gamer.11 said:
the apps are the issue here gentlemen.
1.On call as you bring your phone to ear, screen turns off?Proximity working
2.Adaptive brightness enable and use the phone on same brightness settings in bright and dim areas, screen brightness intensity change?Light sensor working.
3.Screen rotates views?Accelerometer working.
4.Play asphalt or any other motion requiring game, car turns?Gyro working.
5.Open maps, get pointing direction?compass working.
6.Use pedometer, counter change?step counter working.
Click to expand...
Click to collapse
No sir, it's definitely not the apps in my case. After a restart the light and proximity sensors work as expected, but a few minutes later they stop working. I could confirm this with the Sensor Box app as well as with no's 1&2 in your post.
I noticed it first because my adaptive brightness did not work and the screen did not switch of in call. I only installed Sensor Box to see if the sensors still work, this confirmed that they actually stop working and that it is not a calibration issue because Sensor Box shows no reading from these sensors.
This is definitely an issue with Lollipop because I flashed 4.4.4 again and everything worked fine confirming that it is not hardware, but after once again upgrading to 5.0 the sensors stop working few minutes after the phone starts up.
m4nic4ndroid said:
No sir, it's definitely not the apps in my case. After a restart the light and proximity sensors work as expected, but a few minutes later they stop working. I could confirm this with the Sensor Box app as well as with no's 1&2 in your post.
I noticed it first because my adaptive brightness did not work and the screen did not switch of in call. I only installed Sensor Box to see if the sensors still work, this confirmed that they actually stop working and that it is not a calibration issue because Sensor Box shows no reading from these sensors.
This is definitely an issue with Lollipop because I flashed 4.4.4 again and everything worked fine confirming that it is not hardware, but after once again upgrading to 5.0 the sensors stop working few minutes after the phone starts up.
Click to expand...
Click to collapse
That's interesting, have you tried any other custom roms or kernels based on lollipop? I know that is a long shot or even that best advice but could you, or have you checked on other roms?
SO only your Proximity and light sensor the issue? Or all the other sensors a bust?
gamer.11 said:
That's interesting, have you tried any other custom roms or kernels based on lollipop? I know that is a long shot or even that best advice but could you, or have you checked on other roms?
SO only your Proximity and light sensor the issue? Or all the other sensors a bust?
Click to expand...
Click to collapse
I haven't tried any other Lollipop ROMs, I thought about it and I might actually give it a go to see if the problem persists on other ROMs as well, but I would prefer to have stock Android running on my phone, so I'm really hoping for a fix from Google. I'm on few other threads about the same issue, so I know there's a lot of people with the same problem. I had this on the dev preview as well.
gamer.11 said:
That's interesting, have you tried any other custom roms or kernels based on lollipop? I know that is a long shot or even that best advice but could you, or have you checked on other roms?
SO only your Proximity and light sensor the issue? Or all the other sensors a bust?
Click to expand...
Click to collapse
I have tried Code-Blue kernel as I have heard it's a good one, but the problem is still there. I might try a different ROM in the near future.
For me it is only the Light and Proximity sensors, all other sensors work 100%
Light Sensor & Proximity Sensor Error
m4nic4ndroid said:
I have tried Code-Blue kernel as I have heard it's a good one, but the problem is still there. I might try a different ROM in the near future.
For me it is only the Light and Proximity sensors, all other sensors work 100%
Click to expand...
Click to collapse
The Same Problem For Me As Well, My Light Sensor & Proximity Sensor Arent Working. I have downloaded the Final Image from Google Website for 5.0 hammerhead. But still the problem persists.
Nyk
After I got the Play services (with secure locations) update two days ago my light and proximity sensors are gone too. They will work for a while after reboot, but eventually they die.
All other sensors are working fine and only other updates have been to Skype, SwiftKey and TuneIn Radio.
Edit: I'm on stock OTA, no root and never unlocked the bootloader.
Sent from my Nexus 5 using Tapatalk
So uninstalling the play services update resolve the issue? I'm back to KitKat as without light sensor I find uncomfortable to use the phone. Will await the fix before moving to lollipop..
Sent from my Nexus 5 using XDA Free mobile app
"Clean install" using factory images? I did, no issues here.
It seems to be working until I get a phone call, after that the sensors will die.
Have uninstalled the Play services update now and the phone has been up and working 100% for a little more than 4 hours now. Will try to make a phone call to see if it still works after that.
Sent from my Nexus 5 using Tapatalk
Did you reboot after disabling update?
Sent from my Nexus 5 using XDA Free mobile app
rawimage said:
It seems to be working until I get a phone call, after that the sensors will die.
Have uninstalled the Play services update now and the phone has been up and working 100% for a little more than 4 hours now. Will try to make a phone call to see if it still works after that.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Uninstalling Play Services and Play Store update made no difference here. Problem still persists.
michalnied said:
Hello,
After clean install Android 5.0 on Nexus 5 I have lost all sensors.
Do you have similar problem?
Is there any solution to fix it?
Click to expand...
Click to collapse
Hi I have the same problems . Sensors are working after restarting my phone random time. Also you can read here
Uninstalling Play services didn't do it for me either. Sensors work for approximately 4-5 hours then they die.
Sent from my Nexus 5 using Tapatalk
Installed Play services update again after a few days and now my phone has been running fine for 50 hours with all sensors working 100%.
Sent from my Nexus 5 using Tapatalk
I have had this phone for exactly 24 hours, and until then the fingerprint scanner installed in it worked relatively well.
After 24H the sensor decided to activate repeatedly automatically (without me touching the sensor) and finally, stop working.
It will not register any new fingerprints or react to the unlock feature or nothing at all. Rebooting won't fix anything, I have yet to try a hard reset.
My question is, even though the phone is really new, has any of this happened to you guys before?
If so, How have you fixed it?
Thank you and sorry if this is in the wrong section.
Mine arrived yesterday, I will let you know how I get on. Hope you get it sorted.
Off topic: I really want to Root it so that I can use titanium backup but I think its too new! I also ordered a plastic Vernee Mars (not pro) case in the hope that it fits, almost identical dimensions
kyleblyth said:
Mine arrived yesterday, I will let you know how I get on. Hope you get it sorted.
Off topic: I really want to Root it so that I can use titanium backup but I think its too new! I also ordered a plastic Vernee Mars (not pro) case in the hope that it fits, almost identical dimensions
Click to expand...
Click to collapse
I hope it works, mine is still broken, and now the audio doesnt work at all, if im playing music for instance, it will not sound, and every now and then, play 0.1s of the song, it's really a good phone but its getting on my nerves
Also, update me about the case
Also wanting an update on the case, dimensions look to be near enough identical and there are more case option around for the non pro.
So, a new update
The fingerprint scanner decided to work suddenly today, I opened security and decided to see if I could add a fingerprint to unlock it and to my surprise it decided to work.
Regarding the speaker, I found out that if I suck on the speaker (yes, i put my mouth on the speaker hole and aspire air gently) the music, app, game, anything begins playing, and as soon as I stop breathing in it stops playing.
Why is this happening to me? It honestly is super strange, I already contacted gearbest and I hope they help me solve it or give me a new one
Sent from my Mars pro using Tapatalk
May I Ask..
alsetema said:
So, a new update
The fingerprint scanner decided to work suddenly today, I opened security and decided to see if I could add a fingerprint to unlock it and to my surprise it decided to work.
Regarding the speaker, I found out that if I suck on the speaker (yes, i put my mouth on the speaker hole and aspire air gently) the music, app, game, anything begins playing, and as soon as I stop breathing in it stops playing.
Why is this happening to me? It honestly is super strange, I already contacted gearbest
Click to expand...
Click to collapse
Hello... May I ask what part of the world you live in? and how long it took GB to send you the phone? I'm on the fence with this device and the Redmi Note 4.. But I must admit.. your situation is really scaring me and giving me 2nd thoughts about going in this direction.. GB I'm sure will take care of you.. but, what is the return policy? do you pay to have it shipped back? and the down time... weeks?
RaiderWill said:
Hello... May I ask what part of the world you live in? and how long it took GB to send you the phone? I'm on the fence with this device and the Redmi Note 4.. But I must admit.. your situation is really scaring me and giving me 2nd thoughts about going in this direction.. GB I'm sure will take care of you.. but, what is the return policy? do you pay to have it shipped back? and the down time... weeks?
Click to expand...
Click to collapse
I live in western Europe, and it took GearBest about a month to mail me the phone (It is understandable due to the high demand of the phone at the time) If i'm honest, since this is one of the very first units, I am not surprised it has fails, Its prone to happening and I already was expecting something to fail in a very very new chinese phone.
I will update my experience with GB
Thanks For Your Help..
alsetema said:
I live in western Europe, and it took GearBest about a month to mail me the phone (It is understandable due to the high demand of the phone at the time) If i'm honest, since this is one of the very first units, I am not surprised it has fails, Its prone to happening and I already was expecting something to fail in a very very new chinese phone.
I will update my experience with GB
Click to expand...
Click to collapse
Hello Alsetema.. I've decided to stick to my homeland and just buy a device from here..
I wish you all the luck in the world with your issue..:good:
Take Care and I still would like to know how things came out for you!
RaiderWill said:
Hello Alsetema.. I've decided to stick to my homeland and just buy a device from here..
I wish you all the luck in the world with your issue..:good:
Take Care and I still would like to know how things came out for you!
Click to expand...
Click to collapse
Thank you very much!
Sent from my Mars pro using Tapatalk
The case for the mars fits, pretty much perfect. Did you try a hard reset in the end, at all? Mine is working really well although ive heard the phone is compromised by malware/spyware (did manage to find the folder but you can't disable anything) that's why I am trying to root asap. Other thread is here to follow: https://forum.xda-developers.com/android/software-hacking/tutorial-vernee-mars-pro-root-t3652213
Did post this one in another thread but this one seems better:
--
I have this device a week and it's great. Directly installed the OTA of September. Everything worked fine.
Up and until yesterday the fingerprint scanner was really sensitive maybe too sensitive. Then yesterday evening the phone was charged to 100% before I went to sleep so I plugged it out and powered it down to be fully loaded at 100% this morning.
After starting up it seems that the fingerprint print scanner is a lot less sensitive and sometimes it feels sensitivity is degrading during the day of use, to just no sensitivity at all.
Does someone else experienced the same? Does someone have a solution?
Sent from my Mars pro using Tapatalk
FJP84 said:
Did post this one in another thread but this one seems better:
--
I have this device a week and it's great. Directly installed the OTA of September. Everything worked fine.
Up and until yesterday the fingerprint scanner was really sensitive maybe too sensitive. Then yesterday evening the phone was charged to 100% before I went to sleep so I plugged it out and powered it down to be fully loaded at 100% this morning.
After starting up it seems that the fingerprint print scanner is a lot less sensitive and sometimes it feels sensitivity is degrading during the day of use, to just no sensitivity at all.
Does someone else experienced the same? Does someone have a solution?
Sent from my Mars pro using Tapatalk
Click to expand...
Click to collapse
It doesn't seem to be a software problem, but a hardware problem. For me the fingerprint sensor works for some time, then one day it messes up and stops working for a week or so. I really dont know what's wrong, seems to fix by itself.
Sent from my Mars pro using Tapatalk
alsetema said:
It doesn't seem to be a software problem, but a hardware problem. For me the fingerprint sensor works for some time, then one day it messes up and stops working for a week or so. I really dont know what's wrong, seems to fix by itself.
Sent from my Mars pro using Tapatalk
Click to expand...
Click to collapse
Thank, so it is a matter of ups and downs?
I did some gaming while on charge yesterday so maybe some heating can cause this?
I also have some Bluetooth issues while calling on my carkit. Music on my carkit is fine. Will an app like Bluetooth Auto connect be of any help?
Besides that I really like the phone overall.
Sent from my Mars pro using Tapatalk
FJP84 said:
Thank, so it is a matter of ups and downs?
I did some gaming while on charge yesterday so maybe some heating can cause this?
I also have some Bluetooth issues while calling on my carkit. Music on my carkit is fine. Will an app like Bluetooth Auto connect be of any help?
Besides that I really like the phone overall.
Sent from my Mars pro using Tapatalk
Click to expand...
Click to collapse
Yes, it seems to be a matter of ups and downs, same with the speaker. Apparently when the humidity is high, my speaker refuses to work at high volumes ( it crackles and then it stops working)
My charger blew up recently actually (But that was because of some problem with my home's powerline). I got a Samsung charger, slightly slower charge, but my battery now lasts for much longer I have realises (I'm speaking 9V charging instead of 12V)
It is true the phone heats a lot, that's why I'd avoid using it while charging or at least if I plan to charge it all the way, since by the end it will be really hot.
Regarding bluetooth, I really havent had any problems whatsoever, therefore I can't really tell, for me bluetooth has always worked well with cars and speakers and so. I doubt an app like that be of any help, since it should pair automatically with the closest bluetooth source so perhaps that could cause a conflict, but I havent tried it so I can't know for sure.
alsetema said:
Yes, it seems to be a matter of ups and downs, same with the speaker. Apparently when the humidity is high, my speaker refuses to work at high volumes ( it crackles and then it stops working)
My charger blew up recently actually (But that was because of some problem with my home's powerline). I got a Samsung charger, slightly slower charge, but my battery now lasts for much longer I have realises (I'm speaking 9V charging instead of 12V)
It is true the phone heats a lot, that's why I'd avoid using it while charging or at least if I plan to charge it all the way, since by the end it will be really hot.
Regarding bluetooth, I really havent had any problems whatsoever, therefore I can't really tell, for me bluetooth has always worked well with cars and speakers and so. I doubt an app like that be of any help, since it should pair automatically with the closest bluetooth source so perhaps that could cause a conflict, but I havent tried it so I can't know for sure.
Click to expand...
Click to collapse
This morning I took it of the charger. Now fingerprint is quite acceptable. Not that over sensitivity which I disliked, and a lot more responsive than yesterday.[emoji2]
Sent from my Mars pro using Tapatalk
FJP84 said:
This morning I took it of the charger. Now fingerprint is quite acceptable. Not that over sensitivity which I disliked, and a lot more responsive than yesterday.[emoji2]
Sent from my Mars pro using Tapatalk
Click to expand...
Click to collapse
It seems to fix by itself
Sent from my Mars pro using Tapatalk
alsetema said:
It seems to fix by itself
Sent from my Mars pro using Tapatalk
Click to expand...
Click to collapse
Cheered too early, messed up again... It seems that a moist finger works better. It notice the touch better, but then it doesn't recognizes it....
Bleutooth calling went ok today. Seems though that I have the P20 or P25 lite version of the Mars Pro. Not the regular P2t
Should have chosen the Xiaomi Note 4 Global instead... I will monitor it a couple of days but I think I will look for a better 64gb/6gb USB type-c device in the near future....[emoji19]
Sent from my Mars pro using Tapatalk
Anyone experiencing ghost touches on the center part of the display? I thought I was just accidentally touching but it turns out there are ghost touches. It rarely happens and I still couldn't figure out the reason. Note: cleaning the screen of moisture didn't help.
ijuanp03 said:
Anyone experiencing ghost touches on the center part of the display? I thought I was just accidentally touching but it turns out there are ghost touches. It rarely happens and I still couldn't figure out the reason. Note: cleaning the screen of moisture didn't help.
Click to expand...
Click to collapse
Haven't noticed personally. Using a screen protector?
I removed the screen protector to check if is causing it but still the same. It happens rarely though.
ijuanp03 said:
I removed the screen protector to check if is causing it but still the same. It happens rarely though.
Click to expand...
Click to collapse
Hmm. It happens during use or in charging or ?.
Shadowthor said:
Hmm. It happens during use or in charging or ?.
Click to expand...
Click to collapse
During. When I'm just scrolling through my apps or even playing games. It doesn't matter if I am in a cold or warm environment. It even happens when I'm doing basically nothing - staring at my homescren and suddenly it opens the app located at the center.
To give you a better view, here's my homescreen. The ghost touch is located on Waze app but sometimes on Moto or even Settings app.
Try safe mode.
I would ditch Waze app and flipboard.
Try clearing the system cache.
See what's running in the background when it happens.
Use the factory diagnostic touch screen test to see if it may be hardware caused. Not sure how you access it it on that phone.
ijuanp03 said:
During. When I'm just scrolling through my apps or even playing games. It doesn't matter if I am in a cold or warm environment. It even happens when I'm doing basically nothing - staring at my homescren and suddenly it opens the app located at the center.
To give you a better view, here's my homescreen. The ghost touch is located on Waze app but sometimes on Moto or even Settings app.
Click to expand...
Click to collapse
Hmm that's weird. Did it happen recently? Did you install any new apps?
Hopefully it's not hardware related.
You can use cqa test to check the hardware. *#*#2486#*#*
Nahhh it's not related to any app. I may be wrong but it could be the software update from Motorola since I didn't encounter the issue when I first used the phone.
ijuanp03 said:
Nahhh it's not related to any app. I may be wrong but it could be the software update from Motorola since I didn't encounter the issue when I first used the phone.
Click to expand...
Click to collapse
A new update got pushed out?
Not entirely new. The latest software update RR31.Q2-12-14-7.
Shadowthor said:
A new update got pushed out?
Click to expand...
Click to collapse
ijuanp03 said:
Not entirely new. The latest software update RR31.Q2-12-14-7.
Click to expand...
Click to collapse
Oh that update. I have it but I don't currently see the ghosting issues you mentioned yet. Did you end up using the cqa test to check screen?
Shadowthor said:
Oh that update. I have it but I don't currently see the ghosting issues you mentioned yet. Did you end up using the cqa test to check screen?
Click to expand...
Click to collapse
Yah. All the standard testing done. My phone seems to work fine now after removing 1 sim while keeping the other. It must be affecting the internals when dual SIM is utilized which is a design flaw or was not tested properly.
ijuanp03 said:
Yah. All the standard testing done. My phone seems to work fine now after removing 1 sim while keeping the other. It must be affecting the internals when dual SIM is utilized which is a design flaw or was not tested properly.
Click to expand...
Click to collapse
Could be a blown sim card. Replace both and follow ESD protocol when handling them, always.
Handle like a stick of ram.
Excessive ESD exposure can cause random failures immediately or worse, days, weeks even years latter. These cards are dirt cheap but a delayed failure can cost you dearly...
ijuanp03 said:
Yah. All the standard testing done. My phone seems to work fine now after removing 1 sim while keeping the other. It must be affecting the internals when dual SIM is utilized which is a design flaw or was not tested properly.
Click to expand...
Click to collapse
Hmm weird. Haven't tested out dual Sim but it shouldn't cause this issue.
I have encountered at least 30 users reporting this problem in China. Including but not limited to many users from official forums.
https://mclub.lenovo.com.cn/forum-1567-1.html
https://mclub.lenovo.com.cn/thread-7814429-1-1.html
https://mclub.lenovo.com.cn/thread-7814577-1-1.html
https://mclub.lenovo.com.cn/thread-7814895-1-1.html
nullschool said:
I have encountered at least 30 users reporting this problem in China. Including but not limited to many users from official forums.
https://mclub.lenovo.com.cn/forum-1567-1.html
https://mclub.lenovo.com.cn/thread-7814429-1-1.html
https://mclub.lenovo.com.cn/thread-7814577-1-1.html
https://mclub.lenovo.com.cn/thread-7814895-1-1.html
Click to expand...
Click to collapse
And so I thought mine is an isolated case. Motorola is yet to confirm if this is hardware or software related.
ijuanp03 said:
Anyone experiencing ghost touches on the center part of the display? I thought I was just accidentally touching but it turns out there are ghost touches. It rarely happens and I still couldn't figure out the reason. Note: cleaning the screen of moisture didn't help.
Click to expand...
Click to collapse
Hello everyone!
I have this same problem here on my brazilian Moto G100 and in the same place almost in the center of the screen. After removing the screen protector, the problem is more difficult to happen, but it still happens rarely, requiring a cleaning of the screen for the problem to stop happening for a while.
I noticed that the problem happens several times when I leave the smartphone leaning against metallic surfaces or other electronic devices.
Is it necessary to use the warranty to replace this screen or can a firmware update solve this problem?
Regards!
I'm Chinese user.My device have this problem.Our forum many people reaction to this problem
I can confirm I have the same problem. I don't know if it's hardware or software yet
wow I haven't had any problem, but if you find any solution or coment from motorola sopport please post it
Hi guys love this P50 pro, but i have a problem with the proximity sensor in direct sunligt when hearing Whatsapp voice messages, the screen goes always dark.
Someone other experiencing this problem? Indoors it works just fine. Tried removing cover and screenprotector but nothing changes.
it happens to me that when calling in strong sun the display flashes, while in the room everything is fine
ok i see. do you think it's a software bug or proximity sensor problem?
Delete
cvetican said:
it happens to me that when calling in strong sun the display flashes, while in the room everything is fine
Click to expand...
Click to collapse
I'm experiencing the same issue. If the phone takes some kind of strong direct sunlight the screen start flashing on and off randomly. I did the Huawei Support test inside the phone and all the sensore are ok.
Got a new update yesterday emui 12.0.1.223 i will check again and report back
Ok! i can say that Huawei with the last Emui update 12.0.1.223 FIXED the issue with the screen and specifically with the proximity sensor that was constantly switching on and off the screen when this one gets direct sunlight on it. Yes thanks Huawei