Related
Hello.
I bought my ogp a week ago and i discovered a problem with the motion sensor and the proximity sensor - both dosent work.
Some one know how to fix it? The seller said it's a software problem and an update will solve it.
Thanks.
Is your phone rooted by chance? There's a program I use called kernel tuner and it has live statistics of all the sensors.
Do you have a screen protector on that covers where the sensors are by chance?
Sent from my LG-E980 using XDA Premium 4 mobile app
answer
No, my phone is not rooted, i checked the sensors with another app and all my sensors are turned off, no one is working and replying data.
About the screen protector it dosent cover the sensors so it is not the problem...
More ideas?
Thanks!
ranrah said:
No, my phone is not rooted, i checked the sensors with another app and all my sensors are turned off, no one is working and replying data.
About the screen protector it doesn't cover the sensors so it is not the problem...
More ideas?
Thanks!
Click to expand...
Click to collapse
Did you try to check for software updates in the About phone section of the settings application? If there's an update there's a chance that that could fix it.
My display does not timeout and it might be related to something to do with the asus cover detection. Kills my battery because if some notification or alert happens to turn on the screen after I maually turned it off, it will not timeout again.
Howerver, I don't have a cover or anything but having this bizarre issue when the asus cover option is turned on my display constantly but sporadically flashes off and on. If the asus cover option is unchecked/disabled then the phone SEEMS to work normally until I get a call. The proximity kicks in but then the display turns itself back on. I installed sensor box and the proximity seems to work just fine -- nothing errant. Same applies for all the other sensors including the magnometer which does 35uT which seems right for my part of the world.
Did factory resets, cleared cache partitions, reinstalled stock roms etc... toggled the display timeout settings etc..nothing there.
Finally installed bettery battery stats and checked adb so it seems like some process is going crazy but I'm not sure if this is normal behaviour for the device or not.
But if its a rogue process anyone know how to kill it or whatever?
Attached is screenshot from battery stats and logcat
sumean said:
My display does not timeout and it might be related to something to do with the asus cover detection. Kills my battery because if some notification or alert happens to turn on the screen after I maually turned it off, it will not timeout again.
Howerver, I don't have a cover or anything but having this bizarre issue when the asus cover option is turned on my display constantly but sporadically flashes off and on. If the asus cover option is unchecked/disabled then the phone SEEMS to work normally until I get a call. The proximity kicks in but then the display turns itself back on. I installed sensor box and the proximity seems to work just fine -- nothing errant. Same applies for all the other sensors including the magnometer which does 35uT which seems right for my part of the world.
Did factory resets, cleared cache partitions, reinstalled stock roms etc... toggled the display timeout settings etc..nothing there.
Finally installed bettery battery stats and checked adb so it seems like some process is going crazy but I'm not sure if this is normal behaviour for the device or not.
But if its a rogue process anyone know how to kill it or whatever?
Attached is screenshot from battery stats and logcat
Click to expand...
Click to collapse
Could you try uninstalling ASUS Cover to see if that makes any difference, or just disable the app? If it happens again, after uninstalling, you can rule it out.
I tried that before, still same thing. I also got a very strong magnet to see if I could somehow recalibrate the magnetic sensor in case that's what the cover uses for detection. That didn't seem to work. Sensor box shows the proximity and magentic sensor seem to be operating normally though....
sumean said:
I tried that before, still same thing. I also got a very strong magnet to see if I could somehow recalibrate the magnetic sensor in case that's what the cover uses for detection. That didn't seem to work. Sensor box shows the proximity and magentic sensor seem to be operating normally though....
Click to expand...
Click to collapse
That seems very strange. Let me forward the issue to our service team to see if they can assist!
---------- Post added at 10:21 AM ---------- Previous post was at 09:43 AM ----------
Here is the response from our customer service team:
Does the customer have a screen protector (Not a flip cover) that may hinder the proximity sensor’s accuracy?
Does the customer have the latest firmware WW-(V2.20.40.90_20150903_4959). To update FW/Build connect to wifi, go under APPS-SETTINGS-ABOUT-SYSTEM UPDATE make sure battery is >50% before updating.
There is a patch on our latest builds/FW for Asus Cover app that fixes stability.
Some things to also try – Wipe Cache and recovery to retest it from our FAQ - https://www.asus.com/support/faq/1006346
If these do not work ask for a screenshot for the build number if you can for us to look deeper into. VOL_DOWN + POWER BUTTON simultaneously take a screenshot under APPS-SETTINGS-ABOUT-SOFTWARE INFORMATION
will try suggestions...
@ASUS_Khang
Man thanks for your help with this.
I do have a screen protector but the aperature is pretty large so I doubt that's interferring. However, I get the same screen flashing off and on when I'm on an active call which would suggest some proximity type issue. SensorBox would suggest the prox sensor is working fine though
I'll update my firmware again after a factory reset just in case the most recent build corrects something.
Thanks again for your help though! I'll report back :fingers-crossed:
ASUS_Khang said:
That seems very strange. Let me forward the issue to our service team to see if they can assist!
---------- Post added at 10:21 AM ---------- Previous post was at 09:43 AM ----------
Here is the response from our customer service team:
Does the customer have a screen protector (Not a flip cover) that may hinder the proximity sensor’s accuracy?
Does the customer have the latest firmware WW-(V2.20.40.90_20150903_4959). To update FW/Build connect to wifi, go under APPS-SETTINGS-ABOUT-SYSTEM UPDATE make sure battery is >50% before updating.
There is a patch on our latest builds/FW for Asus Cover app that fixes stability.
Some things to also try – Wipe Cache and recovery to retest it from our FAQ - https://www.asus.com/support/faq/1006346
If these do not work ask for a screenshot for the build number if you can for us to look deeper into. VOL_DOWN + POWER BUTTON simultaneously take a screenshot under APPS-SETTINGS-ABOUT-SOFTWARE INFORMATION
Click to expand...
Click to collapse
nada
No luck...still getting my screen constantly flashing off and on when I enable smart cover. Tried factory wipe/reset and flashing the latest build. Attached is the screenshot request.
Per chance can you send the support team the logcat that I attached in the 1st post of the thread? Maybe it might be helpful in picking up what was wrong?
sumean said:
@ASUS_Khang
Man thanks for your help with this.
I do have a screen protector but the aperature is pretty large so I doubt that's interferring. However, I get the same screen flashing off and on when I'm on an active call which would suggest some proximity type issue. SensorBox would suggest the prox sensor is working fine though
I'll update my firmware again after a factory reset just in case the most recent build corrects something.
Thanks again for your help though! I'll report back :fingers-crossed:
Click to expand...
Click to collapse
Inquiry
Hey guys, I am facing same problem with my Asus ZenFone 2 ZE551ML. My screen doesn't get timed out automatically. At first it started with Asus Cover, I was not using the cover but screen was getting on - off itself. Proximity sensor doesn't work properly and screen doesn't get timed out by itself. I have disabled the Asus Cover option from Settings but still Screen timeout not working.
Did anything worked here?
@ASUS_Khang Do you know what can fix my problem?
Bought ZenFone 2 ZE551ML a couple months ago and the screen protector and case from Asus all at the same time. Asus cover turned itself on and I have had problems since then. I do not own or use the asus cover. When this happened, I turned asus cover off and since then, can not make or receive calls. I cleaned the cache, did a factory reset, and removed the screen protector. None of these "fixes" worked. I can make a call but then the screen freezes after 2 pulsations and restarts into a boot loop. I see incoming calls but can not answer them because the phone freezes and restarts. No sound heard during calls for outgoing and incoming calls. Everything is updated already!!!
Same problem here. is this issue have been solved? how? thanks in advance...
solved - sorta
asusmakee said:
Same problem here. is this issue have been solved? how? thanks in advance...
Click to expand...
Click to collapse
My workaround involved getting xposed framework and installing a module called magnet off. In essence it disables the hal sensor which was likely damaged somehow. So flip cover is disabled and my screen times out properly.
Can you explain how you installed it plz step by step I am also facing same problem p
:crying:
sumean said:
My workaround involved getting xposed framework and installing a module called magnet off. In essence it disables the hal sensor which was likely damaged somehow. So flip cover is disabled and my screen times out properly.
Click to expand...
Click to collapse
Hey people,
my OnePlus 3 loses much energy (up to 3 percent in 5 Minutes) if it’s inside my pocket (!) - especially then if I move at the same time.
I have already disabled the gesture functions - however, the problem remains.
Actually the problem can only be reproduced in my pockets
- latest Stock-ROM
- no root or other deep system changes
Any ideas how to narrow down this issue?
Best Regards,
Chris
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Well me getting same problem.. still not figured out issue.
Sent from my ONEPLUS A3003 using Tapatalk
dont use it as your pocket vibrator then...
have you checked the smart lock? it can keep your phone unlocked while you carry it.
Hastaloego said:
dont use it as your pocket vibrator then...
have you checked the smart lock? it can keep your phone unlocked while you carry it.
Click to expand...
Click to collapse
Hahaa ;p
well, smart lock is not active in my phone...
Does it only happen when the screen / fingerprint scanner are against your body? Maybe they are detecting skin through your clothes and constantly trying to do something?
binners said:
Does it only happen when the screen / fingerprint scanner are against your body? Maybe they are detecting skin through your clothes and constantly trying to do something?
Click to expand...
Click to collapse
This. I think this is causing the issue. If you are slightly warm/damp/moist (someone reading hates that word ), it will try and scan your leg. My guess is perhaps it's not checking the ambient/proximity sensor to see if it's in the pocket or not.
I had this issue on the OnePlus 2 as well, although not as bad.
binners said:
Does it only happen when the screen / fingerprint scanner are against your body? Maybe they are detecting skin through your clothes and constantly trying to do something?
Click to expand...
Click to collapse
thebcooper said:
This. I think this is causing the issue. If you are slightly warm/damp/moist (someone reading hates that word ), it will try and scan your leg. My guess is perhaps it's not checking the ambient/proximity sensor to see if it's in the pocket or not.
I had this issue on the OnePlus 2 as well, although not as bad.
Click to expand...
Click to collapse
Thanks guys!
I'll try to wear the phone outward inside my pocket to see whether the problem still occurs.
Btw, i did some tests via "GSam Battery Monitor" and figured out the main-process which is producing the problem:
It's the "kernel". Does the kernel controls one of the mentioned sensors (ambient/proximity sensor) ?
MagDag said:
Thanks guys!
I'll try to wear the phone outward inside my pocket to see whether the problem still occurs.
Btw, i did some tests via "GSam Battery Monitor" and figured out the main-process which is producing the problem:
It's the "kernel". Does the kernel controls one of the mentioned sensors (ambient/proximity sensor) ?
Click to expand...
Click to collapse
Just be more wary of the screen being knocked/bumped!
Yeah that handles hardware as far as I know (might also be under other processes if they use it too though)
Alright, thanks for your quick feedback.
I guess i will reset my phone now...
I'm pretty sure it's the fingerprint sensor. Really sad to see that OP3 has this issue too, this started happening to me on OP2 too after the marshmallow update. They made the fingerprint scanner much more sensitive, greatly improving it's speed but this started happening. The workaround is to keep the phone in your pocket screen facing outwards...
I have the same problem. It should be fixable via system update to not activate the fingerprint sensor while the proximity sensor detects something.
Or am i missing something here?
Same issue here
Same issue. It's kind sad that OP can't handle this to prevent waking up using proximity sensor like it happens with duoble tap. I hope that they will release an update soon.
Is there anything in settings called "pocket mode"?? a friend has a THL phone that has pocket mode which stops the phone from doing anything when it detects its in a pocket
Nope, I've searched whole settings and there no option like 'pocket mode'.
same issue and the screen is showing the message "too many attempts. try again later" i can't use my smartwatch because the phone make a call or sent a message it self in my pocket.
I've created an e-mail to support with issue describe. Will update thread while getting reply.
Yes this is a bad bug which OP need to fix asap.
So what's the solution to the problem, finally?
MagDag said:
Hey people,
my OnePlus 3 loses much energy (up to 3 percent in 5 Minutes) if it’s inside my pocket (!) - especially then if I move at the same time.
I have already disabled the gesture functions - however, the problem remains.
Actually the problem can only be reproduced in my pockets
- latest Stock-ROM
- no root or other deep system changes
Any ideas how to narrow down this issue?
Best Regards,
Chris
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Click to expand...
Click to collapse
We simply keep the phone face up in our pockets? That seems like a quick fix we shouldn't have to live with...
ArjunRanaOO7 said:
We simply keep the phone face up in our pockets? That seems like a quick fix we shouldn't have to live with...
Click to expand...
Click to collapse
You would think that priority would be given to the proximity sensor. If triggered it would disable the finger print input.
Maybe it is just me and my device, but since the MM update (the real one, not the beta) my notification LED doesn't work. I have tested it with text messages, emails, missed calls, charger plugged into my computer, charging plugged into a standard charger, and charging plugged into the fast charger... nada on any of them.
Anyone having this issue? If so how have you rectified it? It has been a minute since I first got this thing (got it at launch) and the MM update reset all my settings so maybe there is a setting to turn it back on I am missing?
Help out a brother if you can. Thanks.
OK, so does anyone have any suggestions for an app that might help by letting me manually setup the notification LED?
Is Do not disturb mode on?
Sent from my ASUS_Z00AD using XDA Premium HD app
madman604 said:
Is Do not disturb mode on?
Sent from my ASUS_Z00AD using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for the reply. It is not in DND as far as I can tell (not on).
If you haven't already, try a factory reset first
Trotter516 said:
Thanks for the reply. It is not in DND as far as I can tell (not on).
Click to expand...
Click to collapse
Have you found a fix for that? Facing the same issue and so far no luck.
godzin said:
Have you found a fix for that? Facing the same issue and so far no luck.
Click to expand...
Click to collapse
Actually yes. After I wiped my phone for my wife the notification now works.
Another issue that I recently found the solution to... if your ZF2's proximity sensor has gotten crazy sensitive since the update try cleaning it. Seriously. Especially if you have a tempered glass screen protector. I thought the piece of advice was bogus but I cracked out my lens cleaning spray and cloth and BOOM, the proximity sensor works correctly again.
Trotter516 said:
Actually yes. After I wiped my phone for my wife the notification now works.
Another issue that I recently found the solution to... if your ZF2's proximity sensor has gotten crazy sensitive since the update try cleaning it. Seriously. Especially if you have a tempered glass screen protector. I thought the piece of advice was bogus but I cracked out my lens cleaning spray and cloth and BOOM, the proximity sensor works correctly again.
Click to expand...
Click to collapse
Thanks! Got the led working again after a factory reset.
By the proximity sensor do you mean the little one next to the selfie camera or the GPS?
After a lot of fixed I've got the ZF2 working fine, except for the "smartlock - safe places" that thing can never work right.
godzin said:
Thanks! Got the led working again after a factory reset.
By the proximity sensor do you mean the little one next to the selfie camera or the GPS?
After a lot of fixed I've got the ZF2 working fine, except for the "smartlock - safe places" that thing can never work right.
Click to expand...
Click to collapse
Sorry, I just realized that you had replied.
Yes, the one beside the camera. Many have had an issue where the screen goes black after you start or answer a call, especially after the update. It seems the update made the proximity sensor much more sensitive. Since all decent screen protectors have a small cutout for the proximity sensor it will tend to accumulate dirt and oil from your skin. Wiping it down doesn't seem to get it clean enough for the sensor so you have to get a little more aggressive to clear the problem up. I went months enduring the problem and even set my phone so I could disconnect from calls using the power button and then ended up stumbling over the solution when setting up the phone for my wife when I upgraded to my Axon 7.
No led indicator
Hi i've been experiencing the same issue. After I update my zenfone 2 ZE551ML 4gb/64gb version, I have noticed that the led incator is not working and it is not found in the settings. Also, another issue I have encountered is that quick charging feature is not working sometimes but sometimes it works. I don't know how to fix. I'd be glad if someone could help with a step by step process. Thanks in advance!
I understand that this was an issue on the 7, but this morning I woke up and my 7T wouldn't (when I tapped it). Anybody else having this issue, or have any suggestions on how to fix it?
cjvphd said:
I understand that this was an issue on the 7, but this morning I woke up and my 7T wouldn't (when I tapped it). Anybody else having this issue, or have any suggestions on how to fix it?
Click to expand...
Click to collapse
I am also having this issue after the screen has been off for a while. Anyone have a solution?
I also have this issue, noticed it seems to be something to do with the ambient light sensor? If I cover it up double tap or tap to wake won't work ( like it's in pocket mode).
Pocket mode is no longer an option so it's like it's built in now?
But yea for me it seems like it works fine in the day, but soon as night comes along and I'm in dimmer environments it becomes flakey
italia0101 said:
I also have this issue, noticed it seems to be something to do with the ambient light sensor? If I cover it up double tap or tap to wake won't work ( like it's in pocket mode).
Pocket mode is no longer an option so it's like it's built in now?
But yea for me it seems like it works fine in the day, but soon as night comes along and I'm in dimmer environments it becomes flakey
Click to expand...
Click to collapse
This has been my experience today.
There's a thread on this in the 7 Pro forum with a possible solution. Looks like it's worth a shot:
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-fix-double-tap-to-wake-t3933504
Do You have Greenify installed?
Globus.gd said:
Do You have Greenify installed?
Click to expand...
Click to collapse
No.
I found a problem with no proper configuration of greenify. After some changes, tap to wake is working with no problems.
Globus.gd said:
I found a problem with no proper configuration of greenify. After some changes, tap to wake is working with no problems.
Click to expand...
Click to collapse
What is greenify? And should I have it?
http://greenify.wikidot.com/
italia0101 said:
I also have this issue, [...]
But yea for me it seems like it works fine in the day, but soon as night comes along and I'm in dimmer environments it becomes flakey
Click to expand...
Click to collapse
cjvphd said:
This has been my experience today.
Click to expand...
Click to collapse
Hey guys,
same for me since today. Until some hours ago all was working fine.
But why you think it's related to dimmer/light. Because for me there is no difference when I turn on the light in room or change the timezone in settings. For now it's just not working (like broken)
I rebooted (also turned off and on) several times, turned off and on the inactivity display settings and some other tests, but nothing helped.
CHEERS
bjs339 said:
There's a thread on this in the 7 Pro forum with a possible solution. Looks like it's worth a shot:
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-fix-double-tap-to-wake-t3933504
Click to expand...
Click to collapse
Like for some others in the thread the factorymode won't be opened via *#808#
But I see the process installed and running when searching for it in settings. Maybe there is something crashed in bg?!
CHEERS
---------- Post added at 12:40 AM ---------- Previous post was at 12:05 AM ----------
UPDATE
Suddenly it began working again...
No changes in location, lighting or whatever (except 39 minutes).
But not I can confirm this laggy working of this function. No idea why...
Last days it worked like 10/10 but now maybe 4/10.
CHEERS
Launching the camera in landscape mode seems to trigger it for me occasionally.
Today the rollout for version 10.0.5 was announced and should fix this DT2W bug.
Let's see if it's true.
Official post from OnePlus:
LINK
CHEERS
A through clean up resolves the problem for my phone
i am facing the same issue with my phone. sadly i have noticed it is a reoccurring problem and it has something to do with the sensors. i tried all the fixes like toggling tap to wake, toggling face unlock assists light, clearing the cache and app data but nothing helped my case. factory reset is of no help either so i'd say don't even bother with that.
what really helped me fix this issue multiple times was something rather unexpected. what you should do is take off your phone's cover, get a wet towel, and thoroughly clean the phone all around, being especially thorough around the front facing camera and the top two edges. I give it extra attention around the front side being careful of the top speaker and after a couple of cleans and wipes both tap to wake and lift to wake starts working perfectly fine. then i put on the cover and voila it all good. Give it a try and let me know if it helped resolve this issue for you.
Hannibal226 said:
Today the rollout for version 10.0.5 was announced and should fix this DT2W bug.
Let's see if it's true.
Official post from OnePlus:
LINK
CHEERS
Click to expand...
Click to collapse
What s the difference between dt2w and "tap the screen to show" in ambient display? Are them the same thing or are doing same stuff? Tnx
Flamehell said:
What s the difference between dt2w and "tap the screen to show" in ambient display? Are them the same thing or are doing same stuff? Tnx
Click to expand...
Click to collapse
Hey!
The (single) tap to wake funktion will show up the ambient display, so that u can see clock, messages and use the fingerprintsensor if u want to enter.
It's a quick awake of screen to see Infos with minimal usage of display resources.
DT2W (double tab to wake) is the same as pressing the power button. So this will fully turn on screen into the lockscreen and also activate the face recognition. (for sure fingerprintsensor can be used, too)
BUT you can only activate one of those things and it will automatically turn off for example tab to wake if you activate DT2W.
Personally I like to use the single tab awake for ambient display, as I always can full activate by power button, which would be a dublicate function then.
CHEERS
---------- Post added at 02:08 AM ---------- Previous post was at 02:06 AM ----------
Hannibal226 said:
Today the rollout for version 10.0.5 was announced and should fix this DT2W bug.
Let's see if it's true.
Official post from OnePlus:
LINK
CHEERS
Click to expand...
Click to collapse
First ppl with new update (only some hours, max a day of usage) reported in OP Forum that they didn't have any problem for now.
So seems to fix this screen awake problem.
CHEERS