Related
We've discovered a problem with the Magnetic Field Sensor over at the OnePlus forums.
It's causing the 'button' mechanism in Cardboard to constantly go off. First video shows the issue in a normal situation - you can see how it peaks every few second.
Second shows it with a strong magnetic field near by - still has an issue.
Really looks like a hardware issue - so we need to test this out and reach out to OnePlus and get them to acknowledge the issue. You can test the sensor using this app - https://play.google.com/store/apps/details?id=com.tdt.magneticfielddetector
You can read more here https://forums.oneplus.net/threads/ghost-touches-when-using-google-cardboard-vr-games.450793/page-2
blackalice said:
We've discovered a problem with the Magnetic Field Sensor over at the OnePlus forums.
It's causing the 'button' mechanism in Cardboard to constantly go off. First video shows the issue in a normal situation - you can see how it peaks every few second.
Really looks like a hardware issue - so we need to test this out and reach out to OnePlus and get them to acknowledge the issue.
+1, Just observed the same.
Click to expand...
Click to collapse
https://forums.oneplus.net/threads/...ardboard-vr-games.450793/page-3#post-14974557
Happy to say that Carl Pei has already commented. Lets see where this goes.
I've checked the compass in google maps seems to be totally fine, seems more accurate than my MotoG3 in side by side tests.
i guess its not a hardware problem, because the pulses are too steady like intended. its looks like the sensor does a reset or gets demagnetize for a better calibration
maybe that's the reason why the level drops within a high magnetic environment like that hard-drive test.
while in low magnetic environment the level rises +40 uT because the higher voltage needed for the reset causes a stronger EMF than the surrounding.
but the EMF sensor doesn't add multiple EMF values, it only shows the actual value, that's why you can see the short drop of 64uT in the 2nd video.
in both cases the we reach nearly the same level of 70-80 uT which could be the default re calibrate level.
it doesn't effects the reading of the EMF direction because that impulse is too short so it looks fine in google maps or what ever app you use.
its just unfortunately that the VR apps uses EMF differential as a trigger mechanism
@blackalice nice post! I hope OnePlus will look into this as a real problem, and come up with a fix for it.
I hope as much people as possible test if they have the same spike, and report it to OnePlus
(maybe edit the post/title and ask for testers)
Is there any workaround for this? I can't watch vr videos, 360 videos on cardboard or other vr video apps since it is constantly resetting my view.
Latest update on this issue.
http://i.imgur.com/b3u8tn1.png
blackalice said:
Latest update on this issue.
http://i.imgur.com/b3u8tn1.png
Click to expand...
Click to collapse
Wow, if that's true, kudos to them for their dedication and commitment.
blackalice said:
Latest update on this issue.
http://i.imgur.com/b3u8tn1.png
Click to expand...
Click to collapse
Hah ! not to say i told you so... but.... https://youtu.be/JQS1m65WUCI?t=40s
Just to let you know, since this wasn't posted here yet:
Carl Pei said:
We got a couple of testers, software engineers and hardware engineers to the office this morning (Sunday) and have resolved this. It has been determined to be a software issue, and our engineers have now already have written solution for it. If the solution passes QT, expect it merged in the upcoming OTA.
Click to expand...
Click to collapse
Source: OnePlus Forums
P1nGu1n_ said:
Just to let you know, since this wasn't posted here yet:
Click to expand...
Click to collapse
Actually, it was... http://forum.xda-developers.com/showpost.php?p=67387451&postcount=7
Hastaloego said:
Actually, it was... http://forum.xda-developers.com/showpost.php?p=67387451&postcount=7
Click to expand...
Click to collapse
You're right, looked for links, but it's posted as a screenshot. That's why I didn't see it :good:
any news on this problem? I still got this problem in OxygenOs 3.2.1
Try updating to 3.2.2 then
any news on this problem?
I had this issue on 3.2.2 and virtual reality was almost unusable because the magnetic sensor keeps getting triggered, what causes videos/games to pause/go to menu
I can test at home on FreedomOS 1.5: OxygenOS 3.2.6 based.
Xperia X Performance (F8132) Accelerometer failure & Screen Auto-rotate irresponsive
Hi All,
I got an issue bothering me since I bought Xperia X Perfomance (F8132) Mid June.
The auto rotate function failed after a while but everything goes fine after reboot.
When it fails, I use "Xperia Service Menu" -> "Service Tests" -> "Accelerometer",
then all X,Y,Z are zero and the ball just sticks and freezes at mid.
I bought from Taiwan and I can find 15 more people having the same symptom with me on 2 forums
( http://mobile01.com and http://gamer.com.tw ).
Hence I don't think it's only me and it's a common issue or common yield problem for Xperia X Perfomance.
I post here because I'd like to find more people with the same issue and raise the attention of SONY in order to find the root cause (i guess it's either over-heat causes this or accelerometer yield issue) and give a patch.
Now I'm using a APP "Rotation Control" to workaround this, but all photos cannot records correct orientation data and no auto-rotate is kinda inconvenient.
For a flag-ship and high-priced cellphone for SONY this year, it is very disappointing to me. :crying:
Version: 35.0.A.1.227 and 35.0.A.1.238 both occur
huangjs said:
Hi All,
I got an issue bothering me since I bought Xperia X Perfomance (F8132) Mid June.
The auto rotate function failed after a while but everything goes fine after reboot.
When it fails, I use "Xperia Service Menu" -> "Service Tests" -> "Accelerometer",
then all X,Y,Z are zero and the ball just sticks and freezes at mid.
I bought from Taiwan and I can find 15 more people having the same symptom with me on 2 forums
( http://mobile01.com and http://gamer.com.tw ).
Hence I don't think it's only me and it's a common issue or common yield problem for Xperia X Perfomance.
I post here because I'd like to find more people with the same issue and raise the attention of SONY in order to find the root cause (i guess it's either over-heat causes this or accelerometer yield issue) and give a patch.
Now I'm using a APP "Rotation Control" to workaround this, but all photos cannot records correct orientation data and no auto-rotate is kinda inconvenient.
For a flag-ship and high-priced cellphone for SONY this year, it is very disappointing to me. :crying:
Version: 35.0.A.1.227 and 35.0.A.1.238 both occur
Click to expand...
Click to collapse
I also have that problem. No more auto-rotation after a while (1-2 days) . Only a reboot fixes that
DiLeon said:
I also have that problem. No more auto-rotation after a while (1-2 days) . Only a reboot fixes that
Click to expand...
Click to collapse
Thank you for letting us know.
It shows it's not a regional FW issue but a global HW or FW one.
I wonder if SONY knowing this. If not, we need to address this and push SONY to work it around.
And if it is not workaroundable, SONY will have a big problem.
I have the same issue on my Xperia X (F5121) bought in Sweden. Haven't checked the accelerometer but the behaviour is the same and reboot is only fix.
I have not had any problems with auto rotation, my accelerometer works fine but my touch screen is messed up
Sent from my F8131 using XDA-Developers mobile app
HellRoot said:
I have not had any problems with auto rotation, my accelerometer works fine but my touch screen is messed up
Click to expand...
Click to collapse
Same
HellRoot said:
I have not had any problems with auto rotation, my accelerometer works fine but my touch screen is messed up
Click to expand...
Click to collapse
Can you specify "messed up"? I've had issues with the touch screen also, mostly that it registers a tap while I'm scrolling resulting in involuntary tapping on links. Also it often takes a while to start scrolling, as if the screen has a hard time recognising the swipe.
I have the same problem. The accelerometer stop working 15 minutes after reboot.
Help me verify if is caused by a third party app or not.
Use your phone in safe mode for a while.
I'm from Hong Kong, the accelerometer and its auto-rotation of my x performance has the same problem that it won't work until i reboot my phone.
I dont think that is caused by a app crashing when the problems occuring in all around the world.
The issue didnt come to me when I was not yet update to 35.0.A.1.282. Please notice this problem SONY. It seriously affected the satisfaction from user of the phone from your brand.
There is a topic on the Sony support forum - see here: http://talk.sonymobile.com/t5/Xperia-X-Performance/Accelerometer-stops-working/m-p/1158490#U1158490
At least they are aware of the problem. As soon as it happens again on my phone, I will send them my logs. I will report any development...
It seems that I uninstall the AR effects in my phone and reboot, it works again
Rotation fails
Hello guys,
I have the same problem. Yesterday it worked fine, but today, the auto rotate don't work. Very disappointing. Only a reboot can help but not every time.
Sony has to do something with it.
Gyroscope/Auto-Rotation Issue
Hey everyone,
I'm also having this same issue, but only since the most recent update from late September. When trying to make a pic display as fullscreen by rotating the phone, nothing happens, unless I reboot the phone. Then within day or two, it starts happening again. When I go to camera it loads up and STAYS in landscape mode, no matter what I do, even closing it out and clearing out the cache & force stopping it then reactivating it. It seems like a software issue that Sony needs to address PRONTO!
It appears another thread here on XDA is dealing with the same issue. I tried shenlong85's idea and it seems to have fixed the issue, but I need another day or so to make sure. If you don't hear from me by Sunday (10/23), assume it's been fixed. Hopefully the Nougat update we're all about to get any day now will permanently fix it!
The memory uninstall updates only prolong the issues. Seems like the firmware issue earlier on.
Nougat... When are u coming?
shenlong85 said:
The memory uninstall updates only prolong the issues. Seems like the firmware issue earlier on.
Nougat... When are u coming?
Click to expand...
Click to collapse
Well, we'll see. I am giving my XP 'til Sunday........if no more auto-rotate issues by then, then I will consider your idea to be gold. lol Of course, once we get Nougat, I'm hoping it will ensure that the issue never comes back period. As of this time, the issue has NOT returned.
I bought my Xperia X Performance from Kogan who sells imports in Australia from Asia and I have the exact same issues with my orientation and touchscreen. However my jumpy touchscreen only seems to occur while charging.
RockStar2005 said:
Hey everyone,
I'm also having this same issue, but only since the most recent update from late September. When trying to make a pic display as fullscreen by rotating the phone, nothing happens, unless I reboot the phone. Then within day or two, it starts happening again. When I go to camera it loads up and STAYS in landscape mode, no matter what I do, even closing it out and clearing out the cache & force stopping it then reactivating it. It seems like a software issue that Sony needs to address PRONTO!
It appears another thread here on XDA is dealing with the same issue. I tried shenlong85's idea and it seems to have fixed the issue, but I need another day or so to make sure. If you don't hear from me by Sunday (10/23), assume it's been fixed. Hopefully the Nougat update we're all about to get any day now will permanently fix it!
Click to expand...
Click to collapse
I tried shenlong85's idea, but less than 24 hours after trying it, I switched my phone from Portrait to Landscape to view a 16:9 widescreen pic I had in my Album, and it WOULD not auto-rotate the pic. So unfortunately this "trick" doesn't work either.
Just have to hope Sony includes a fix with the Nougat update we're about to get any day now from them.
I'm noticing now too that once the Auto-Rotate function stops working, so does Smart Call Handling. Have to swipe screen once again to take calls. Hurry up Nougat!! lol
I'm having the same issue and the only help I'm getting from Sony support is to factory reset my device :\ I'm hoping Nougat makes it's way to our devices soon. I really like this phone and this is a pretty big issue to have.
SpencerElliott said:
I'm having the same issue and the only help I'm getting from Sony support is to factory reset my device :\ I'm hoping Nougat makes it's way to our devices soon. I really like this phone and this is a pretty big issue to have.
Click to expand...
Click to collapse
I agree Spencer. And yes Sony Mobile told me the same thing. I'll do a repair (which yes, includes a factory reset) only IF Nougat doesn't fix it. They say we're getting it "in or close to October", so I'm guessing it's gotta be coming any day now. Hopefully they include a fix with Nougat though and I don't have to do that. Getting tired of this BS with Sony. My Z3 had an issue where if I turned on Stamina Mode, it would 1) mess with my MMS (group/pic/video) text messages.........you don't know how many times I had to ask ppl to resend those to me and how much that sucked lol 2) Cause a "random" battery drain. Only fix was a factory reset. I FINALLY got wise and realized it was SM and kept it off. Found a great app called 360 Hibernation Master that did what SM was supposed to do but better, MINUS the buggy BS. But OF COURSE it doesn't work on any X series phone (at least not my XP), so I'm stuck with SM now. At least Sony Mobile FINALLY fixed that bug with SM so that's not an issue anymore. lol
It is a big issue, and it makes me not want to keep buying their phones.
I was wondering if anyone else had this issue with the front facing camera. There's a couple people that had this issue as well, check the
mentions for SamsungSupport on Twitter a couple days back(at the time of this post)
There's even a video of it in action: https://twitter.com/Hired_Assassin5/status/918633351510200320
As you can see at the top, there's some major discoloration going on. It's almost like a negative image.
https://i.imgur.com/2ipVzgS.jpg
I got the phone on Sep 15th, release day. The camera was working fine up until around Oct 5th that I know of. Taking selfies with the dog, etc.
Well, I opened it up on the 12th, haven't used it for a while, and I noticed that issue you see in the first image. I contacted Samsung and they had me
go through the whole troubleshooting process, all the way to me factory resetting my device. Factory Reset, then skipped all the setup wizards
and went straight to testing the camera. Issue is still present!
So the next day, I went to my carrier store, they said they never seen that before. So they're ordering me a shipment to replace it, possible defect.
Well, that night, I decided to try and look deeper into the issue. Flashlight on camera lenses, didn't see anything. Then I remembered from previous
android phones, there's hardware codes you can enter into the Dialer, so I input *#0*#, which is the hardware testing screen.
It looks like this:
https://i.imgur.com/RhJD4WJ.jpg
So obviously, one of the options is "FRONT CAM". I thought I would "test" it. I clicked on it, and it was working fine! I said oh sh!t, WTH.
This is the screenshot of it:
https://i.imgur.com/2BiaA7U.jpg
Then I took the picture as well, and it turned out just fine, like a normal camera. Well when you tap the screen again, it backs out, and switches
into a different mode, or something. And well sure enough, that issue I was having in my main camera app showed up!
This is a screenshot of it:
https://i.imgur.com/kGgJDD1.jpg
Now this is where I'm wondering if the Geniuses and good people here at XDA can figure out.
If you notice in the first screenshot of the "test" https://i.imgur.com/2BiaA7U.jpg
It says SUB AP at the top left....
Then in the next one, the defective one or whatever https://i.imgur.com/kGgJDD1.jpg
It says SUB CC.
Does anyone know what those are, or what they stand for? And if possible, how can I get my camera app to go back to using the correct mode or whatever that is.
This issue happens in all camera apps, the Samsung default camera app, play store camera apps, etc.
Thanks.
FunYunZ said:
I was wondering if anyone else had this issue with the front facing camera. There's a couple people that had this issue as well, check the
mentions for SamsungSupport on Twitter a couple days back(at the time of this post)
There's even a video of it in action: https://twitter.com/Hired_Assassin5/status/918633351510200320
As you can see at the top, there's some major discoloration going on. It's almost like a negative image.
https://i.imgur.com/2ipVzgS.jpg
I got the phone on Sep 15th, release day. The camera was working fine up until around Oct 5th that I know of. Taking selfies with the dog, etc.
Well, I opened it up on the 12th, haven't used it for a while, and I noticed that issue you see in the first image. I contacted Samsung and they had me
go through the whole troubleshooting process, all the way to me factory resetting my device. Factory Reset, then skipped all the setup wizards
and went straight to testing the camera. Issue is still present!
So the next day, I went to my carrier store, they said they never seen that before. So they're ordering me a shipment to replace it, possible defect.
Well, that night, I decided to try and look deeper into the issue. Flashlight on camera lenses, didn't see anything. Then I remembered from previous
android phones, there's hardware codes you can enter into the Dialer, so I input *#0*#, which is the hardware testing screen.
It looks like this:
https://i.imgur.com/RhJD4WJ.jpg
So obviously, one of the options is "FRONT CAM". I thought I would "test" it. I clicked on it, and it was working fine! I said oh sh!t, WTH.
This is the screenshot of it:
https://i.imgur.com/2BiaA7U.jpg
Then I took the picture as well, and it turned out just fine, like a normal camera. Well when you tap the screen again, it backs out, and switches
into a different mode, or something. And well sure enough, that issue I was having in my main camera app showed up!
This is a screenshot of it:
https://i.imgur.com/kGgJDD1.jpg
Now this is where I'm wondering if the Geniuses and good people here at XDA can figure out.
If you notice in the first screenshot of the "test" https://i.imgur.com/2BiaA7U.jpg
It says SUB AP at the top left....
Then in the next one, the defective one or whatever https://i.imgur.com/kGgJDD1.jpg
It says SUB CC.
Does anyone know what those are, or what they stand for? And if possible, how can I get my camera app to go back to using the correct mode or whatever that is.
This issue happens in all camera apps, the Samsung default camera app, play store camera apps, etc.
Thanks.
Click to expand...
Click to collapse
I'm not having that issue *knocks on wood*
But it doesn't sound like a hardware issue though.
Sub AP, Sub CC are probably different Samsung settings not available to end users. Any advice I'd give is to back up, hard reset, test if problem still present, if problem fixed restore data.
When does the problem usually happen, in bright or low light?
What if you use the front camera "flash" does it still happen?
lennie said:
I'm not having that issue *knocks on wood*
But it doesn't sound like a hardware issue though.
Sub AP, Sub CC are probably different Samsung settings not available to end users. Any advice I'd give is to back up, hard reset, test if problem still present, if problem fixed restore data.
When does the problem usually happen, in bright or low light?
What if you use the front camera "flash" does it still happen?
Click to expand...
Click to collapse
I originally thought it was a hardware issue, but seeing it function normally when I did the diagnostic testing, I knew it had to be
something that triggered the software to not work correctly.
the issue is still present no matter what settings I change. Changing resolution, flash on/off, picture size, HDR on/off/auto, all the settings
I can find, the issue is still exists.
EDIT: Is a hard rest the same as a Factory Reset?
FunYunZ said:
I originally thought it was a hardware issue, but seeing it function normally when I did the diagnostic testing, I knew it had to be
something that triggered the software to not work correctly.
the issue is still present no matter what settings I change. Changing resolution, flash on/off, picture size, HDR on/off/auto, all the settings
I can find, the issue is still exists.
EDIT: Is a hard rest the same as a Factory Reset?
Click to expand...
Click to collapse
hard reset = factory reset
have you tried using Odin and doing a fresh FW install?
htc-8925 said:
have you tried using Odin and doing a fresh FW install?
Click to expand...
Click to collapse
I have not. I did a factory reset.
My friend had the same issue.
whiteangelcl said:
My friend had the same issue.
Click to expand...
Click to collapse
Dam, that's unfortunate. That's 4 people now that have had this issue. I wonder how much worse it will get. Hopefully the new replacement doesn't have this issue.
It's weird because it was working fine for a few weeks, and then something happened. Not sure if it auto updated without me knowing and caused this issue.
FunYunZ said:
Dam, that's unfortunate. That's 4 people now that have had this issue. I wonder how much worse it will get. Hopefully the new replacement doesn't have this issue.
It's weird because it was working fine for a few weeks, and then something happened. Not sure if it auto updated without me knowing and caused this issue.
Click to expand...
Click to collapse
sounds like they're sending you a replacement. make sure you are satisfied with the replacement because they might send you a refurb.
i have the same issue as well ... so what happened at the end ? did they end up finding the issue ? how they fixed it ?
emazens said:
i have the same issue as well ... so what happened at the end ? did they end up finding the issue ? how they fixed it ?
Click to expand...
Click to collapse
Nope, Samsung never got back to me. I just went to the Tmobile store and they were like, yep, never seen that before. So they overnight me a new one.
I just begun to have the same issue on my phone and I'm not happy after spending 1k on it. I'm going to my career tomorrow but unfortunately don't know I this will be resolved. Please Let me know what Samsung did for you.
Same problem on my Note8. Following for solution.
solution anyone?
did anyone of u find a solution?
---------- Post added at 12:41 PM ---------- Previous post was at 12:38 PM ----------
i'm suffering with this problem presently and is trying to find a solve.
totaldepth said:
Same problem on my Note8. Following for solution.
Click to expand...
Click to collapse
i am seeing when i open camera ,camera failed
can anyone advise on how to fix?
If you did not mistreat the device, dropped it or fiddle with system settings or something of the sort, warranty is the all time solution for these problems
Hey my note 8 front camera just experienced the same issue. I've talked to Samsung support, and frankly it seems like it is a hardware issue. It is recommended that you use Samsung Support to make a service request. Free shipping both ways, so if you can live without your phone for a week or two (or have a backup phone to use), that's the route I recommend people going.
Original Problem:
MENU / COMMON APPLICATION ( NATIVE) - CAMERA / VIDEO - CAMERA EFFECTS NOT WORKING
Problem found:
FRONT CAMERA FAIL
Solution:
REPLACED COMPONENT
Click to expand...
Click to collapse
Did you manage to find the cause of the problem?
My front selfie camera has the same problem!
sorry to raise up this issue again.. my s8+ is from Indonesia region, and facing the same issue when try to use front camera is failed with notification Warning Unknown Error Occured.
already try Wipe cache partition and hard reset but still facing the same issue..
but if i use front camera for video call thru whatsapp it's working fine, but yet again if check thru *#0*# for Front Camera it's Camera Failed..
is it hardware issue or FW issue ?
Front Facing camera has double image
Has anyone found a fix for this issue yet? Mine started this issue last year and I haven't found a remedy for it yet. Ugh.
This is a pretty big issue that blue up on the OnePlus forum and Reddit. People are experiencing ghost touches in apps. It's very easy to also experience this by opening cpu-z and letting it sit there for a minute or two not doing anything. It seems not everyone is experiencing this though. I have tested and do experience it. Do you?
Yup. Mine does with cpu-z open. what do we do?
BossJ said:
Yup. Mine does with cpu-z open. what do we do?
Click to expand...
Click to collapse
Depends if it's a hardware or software issue. Personally I already submitted a return request with OnePlus.
I just cancelled my order.. hopefully there is a software fix for you guys
This only happens to me on cpu-z and not in any other app. So I guess a future software update is gonna fix it.
Left it for a minute and didn't notice anything. On 9.5.3, bootloader unlocked and patched boot image with root.
I haven't experienced in a few days, it was happening a lot until I disabled pretty much all gestures.
I installed CPU-Z just to check on my International 8GB/256 model and I've got no issue with ghost touches. Not sure what is causing this for you all, but I do hope it is sorted out for you all.
When I turned off NFC the issue went away for me glad I don't use it whatsoever haha
Purest said:
I haven't experienced in a few days, it was happening a lot until I disabled pretty much all gestures.
Click to expand...
Click to collapse
Well that's not a solution disabling a useful feature to not have ghost touch issue.
On screen/off screen gesture are one of my favorite using it, so not a solution to me.
Simple will return the device.
I haven't order yet but i will next couple of days.
There's many reports across oneplus forum.
https://www.androidpolice.com/2019/...ros-are-suffering-phantom-touch-input-issues/
I left CPU-Z running for at least 10 mins.
And all is OK. Maybe it's a rouge program or something to do with the unlock\twrp?
The only way to be sure is to reset to stock and only install CPU-Z
Seems OnePlus using Novatek panels https://github.com/OnePlusOSS/andro...input/touchscreen/oneplus_touchscreen/Novatek
Poco F1 had same problems with Novatec and only way fix it was replacing whole panels, they tried to fix over updates but witout luck
romanB_SK said:
Seems OnePlus using Novatek panels https://github.com/OnePlusOSS/andro...input/touchscreen/oneplus_touchscreen/Novatek
Poco F1 had same problems with Novatec and only way fix it was replacing whole panels, they tried to fix over updates but witout luck
Click to expand...
Click to collapse
Wow that's seems real bummer.
Why would OP use Novatek display controller since had bad reputation and bad track record.
So the question is how do we know if all that units effected having all of the them Novatek display controller?
Or if there's another supplier for those units that don't have that issue.
Man things are getting much worse if it's hardware related and not software that I thought.
Sent from my V1821A using Tapatalk
It's extremely annoying it has happened to me a few times even when I was boasting about the new device to some colleagues at work. I thought it was me at first until then I read IRS an actual thing. I won't return it yet but I might if it's not sorted soon. It's extremely irritating.
Sent from my [device_name] using XDA-Developers Legacy app
Looks like ghost touches are related to NFC. Try with NFC turned off.
C3C076 said:
Looks like ghost touches are related to NFC. Try with NFC turned off.
Click to expand...
Click to collapse
Can confirm. My Ghost touches seize when NFC is disabled.
Sent from my GM1913 using Tapatalk
I've started yesterday experiencing that ghost touchs and also screen not responsive to touch in some panel sections (mostly the upper right zone). The phone didn't gave me that problem since I bought. I noticed when this happening, pulling the notification bar down to the tile settings makes that zone work again. Same thing happened when that random ghost touchs happens.
Didn't had any problems, don't use NFC, tried turning it on, ghost touches started appearing on cpuz, but not on other apps. As i don't use NFC i probably won't return the phone.
I just tried with CPU-Z and a few seconds after starting the app, the screen turns crazy tapping here and there. Can confirm also disabling NFC solves it.
Turning off nfc or not using gestures or not using cpuz app is just temporary solution.
And there's multiple reports that ghost issues happening other app too.
And we never know if thing get worse over time.
I'm afraid it's a more common issue than we thought but many users simple didn't notice it until now.
Oneplus should clearly take attention on that issue seriously and fix it ASAP.
Shouldn't be happening at all with any kind app or scenario of usage.
Sent from my V1821A using Tapatalk
Is anyone else having an issue with the always on display? Not a big deal but occasionally the AOD goes off and the tap to wake function doesn't work. Unlocking/locking the phone fixes it but it reoccurs again randomly through the day.
andrewd71 said:
Is anyone else having an issue with the always on display? Not a big deal but occasionally the AOD goes off and the tap to wake function doesn't work. Unlocking/locking the phone fixes it but it reoccurs again randomly through the day.
Click to expand...
Click to collapse
I was having the same issue when I had the edge notification app installed that makes the screen light up around the camera when you get a notification.
Uninstalled and no issues since
Tap to wake not working for me
Not sure if this is connected but in addition to the always on display/tap to wake issue when I'm in a phone call the screen will stay off even when I move the phone from my ear to hang up, see the keypad etc. Again I have to use the power button to wake the screen. A problem with the proximity sensor perhaps?
andrewd71 said:
Not sure if this is connected but in addition to the always on display/tap to wake issue when I'm in a phone call the screen will stay off even when I move the phone from my ear to hang up, see the keypad etc. Again I have to use the power button to wake the screen. A problem with the proximity sensor perhaps?
Click to expand...
Click to collapse
Do you have any notification or edge lighting apps installed?
Mdizzle1 said:
Do you have any notification or edge lighting apps installed?
Click to expand...
Click to collapse
No, I've not installed any apps like that.
I am having both the issue with always on display and the screen staying off during a call even when it's not up to my face. I don't have any edge display app installed. They happened right out of the box. Glad it's not just me.
czm said:
I am having both the issue with always on display and the screen staying off during a call even when it's not up to my face. I don't have any edge display app installed. They happened right out of the box. Glad it's not just me.
Click to expand...
Click to collapse
This is an odd one - are you using a case? I just had a case through the post this morning and now using the phone with the case the issues have stopped! I'll keep checking through the day but as of now all is good.
andrewd71 said:
This is an odd one - are you using a case? I just had a case through the post this morning and now using the phone with the case the issues have stopped! I'll keep checking through the day but as of now all is good.
Click to expand...
Click to collapse
Not using a case. It's sporadic. Tap to wake works fine for a while and then stops. The issue during calls is constant. Not major issues just niggles.
Not noticed any bugs with ambient display, but it has used 20 percent battery in 21hrs.
Seems a bit high to me, have just turned it off, not worth a 5th of my battery.
czm said:
I am having both the issue with always on display and the screen staying off during a call even when it's not up to my face. I don't have any edge display app installed. They happened right out of the box. Glad it's not just me.
Click to expand...
Click to collapse
Yeah I'm having both issues happen RANDOMLY as well. I'm HOPING Google will put out a fix for these two issues very soon.
Tried working with Google's Tech Support Team via chat earlier on the AOD issue. Tried a few things like clearing the cache of the launcher & restarting in Safe Mode then back to Normal Mode, and it seems to be doing it less but then it just did it again for a short time like an hour ago.
Using a case, no edge stuff, and also using Nova Launcher (though it happened in Pixel Launcher as well).
If anyone finds a fix for this, I would appreciate it too!
RockStar2005 said:
Yeah I'm having both issues happen RANDOMLY as well. I'm HOPING Google will put out a fix for these two issues very soon.
Tried working with Google's Tech Support Team via chat earlier on the AOD issue. Tried a few things like clearing the cache of the launcher & restarting in Safe Mode then back to Normal Mode, and it seems to be doing it less but then it just did it again for a short time like an hour ago.
Using a case, no edge stuff, and also using Nova Launcher (though it happened in Pixel Launcher as well).
If anyone finds a fix for this, I would appreciate it too!
Click to expand...
Click to collapse
Mine is fine for a while them randomly the tap-to-wake won't respond. I had also hoped that the OTA would have addressed, but maybe it is affecting far fewer users than other bugs.
czm said:
Mine is fine for a while them randomly the tap-to-wake won't respond. I had also hoped that the OTA would have addressed, but maybe it is affecting far fewer users than other bugs.
Click to expand...
Click to collapse
Yeah. Seems like more and more people are noticing and like me reporting these various issues to Google. So hopefully the next batch will include fixes for all this stuff.
I have same two problem with AOD, touch to wake up and screen off/on when calling.
DOMIN_ said:
I have same two problem with AOD, touch to wake up and screen off/on when calling.
Click to expand...
Click to collapse
I recommend you guys report these issues to Google so to increase the odds of them coming up with an OTA sooner than later. You can call them or chat with them via this link (as I did). Just scroll down to the bottom and choose your contact preference.
RockStar2005 said:
I recommend you guys report these issues to Google so to increase the odds of them coming up with an OTA sooner than later. You can call them or chat with them via this link (as I did). Just scroll down to the bottom and choose your contact preference.
Click to expand...
Click to collapse
On the pixel support forum they also recommend you report it via settings>about phone>send feedback about device. I think this way it also easily picks up the log files.
I believe the answer to all of your questions lies in a faulty proximity sensor. I was driving myself nuts with all of these issues exactly, and no app was the culprit because I factory reset and still had the issue. I'm going to post a link to a Reddit thread that I found that confirmed my suspicions. on Wednesday of this week I went back to Verizon and traded the phone in and now I have received a phone that works 100% as expected.
Reddit thread.
Good luck all, hope this helps.
czm said:
On the pixel support forum they also recommend you report it via settings>about phone>send feedback about device. I think this way it also easily picks up the log files.
Click to expand...
Click to collapse
Yeah I got an e-mail from the support guy to do that as well after he'd ask that I send a bug report. Just did it regarding AOD not staying on all the time and also.............I noticed that Hold for Me doesn't ALWAYS come up when calling businesses. Two examples include T-Mobile Customer Service & a local major hospital in Chicago. In most cases though, it does. Just an FYI. Not sure if this is something that they will fix, but I think it should come up all the time, or AT LEAST when you're calling an established business of ANY kind.
---------- Post added at 05:30 PM ---------- Previous post was at 05:26 PM ----------
Morpherios said:
I believe the answer to all of your questions lies in a faulty proximity sensor. I was driving myself nuts with all of these issues exactly, and no app was the culprit because I factory reset and still had the issue. I'm going to post a link to a Reddit thread that I found that confirmed my suspicions. on Wednesday of this week I went back to Verizon and traded the phone in and now I have received a phone that works 100% as expected.
Reddit thread.
Good luck all, hope this helps.
Click to expand...
Click to collapse
Very interesting!
I REALLY don't want to send mine back because I've spent so much time setting it up already (and my sister's too lol). I did some changes in the settings so I'll just cross my fingers and hope it works right.
Is there a way to recalibrate the proximity sensor?
RockStar2005 said:
Yeah I got an e-mail from the support guy to do that as well after he'd ask that I send a bug report. Just did it regarding AOD not staying on all the time and also.............I noticed that Hold for Me doesn't ALWAYS come up when calling businesses. Two examples include T-Mobile Customer Service & a local major hospital in Chicago. In most cases though, it does. Just an FYI. Not sure if this is something that they will fix, but I think it should come up all the time, or AT LEAST when you're calling an established business of ANY kind.
---------- Post added at 05:30 PM ---------- Previous post was at 05:26 PM ----------
Very interesting!
I REALLY don't want to send mine back because I've spent so much time setting it up already (and my sister's too lol). I did some changes in the settings so I'll just cross my fingers and hope it works right.
Is there a way to recalibrate the proximity sensor?
Click to expand...
Click to collapse
I don't believe it's a calibration issue. The way mine worked (or didn't as the case may be) was sporadic and seemed to almost be as if the sensor or module was loose? Inside the housing. Quite literally, jostling it around would make it work sometimes. Furthermore, if you download the app in that reddit thread, the proximity sensor tester Link Here, you can sort of gauge yourself if it's actually occurring. With mine, sometimes it would work by swiping my hand over the sensor, the color would change. Other times, the color stayed the same, and as the video showed ,I could put pressure on where the sensor was and change the color. But if it wasn't working, jostling the phone around would sometimes make it work and the color would change.
Additionally in the advanced test in that app, it is supposed to tell you how far away from the sensor an object is. On my (nonworking) phone, that number for distance would be pegged at 0 regardless of how far away my hand was. However if I put pressure on the sensor, it would jump to like 5 cm.
See if your phone is doing these things. If so, I would recommend you get it replaced, as it likely will not work properly otherwise. Verizon deemed this a hardware issue when I swapped phones. Also note that I factory reset twice, and one of those times I imported literally nothing when setting it up. So it wasn't a settings or app issue. I do believe there's a rash of faulty proximity sensors going on here.
Morpherios said:
I don't believe it's a calibration issue. The way mine worked (or didn't as the case may be) was sporadic and seemed to almost be as if the sensor or module was loose? Inside the housing. Quite literally, jostling it around would make it work sometimes. Furthermore, if you download the app in that reddit thread, the proximity sensor tester Link Here, you can sort of gauge yourself if it's actually occurring. With mine, sometimes it would work by swiping my hand over the sensor, the color would change. Other times, the color stayed the same, and as the video showed ,I could put pressure on where the sensor was and change the color. But if it wasn't working, jostling the phone around would sometimes make it work and the color would change.
Additionally in the advanced test in that app, it is supposed to tell you how far away from the sensor an object is. On my (nonworking) phone, that number for distance would be pegged at 0 regardless of how far away my hand was. However if I put pressure on the sensor, it would jump to like 5 cm.
See if your phone is doing these things. If so, I would recommend you get it replaced, as it likely will not work properly otherwise. Verizon deemed this a hardware issue when I swapped phones. Also note that I factory reset twice, and one of those times I imported literally nothing when setting it up. So it wasn't a settings or app issue. I do believe there's a rash of faulty proximity sensors going on here.
Click to expand...
Click to collapse
Hey Morpherios,
Ok.............downloaded that app and tried it out several times. It passed some of the time, but then I'd try it again a few minutes later and it would fail on both tests. Ughh!!
You think even though it passed a few times I still need to replace it?