Hello,
my wife and I both have a Pixel C because it is very convenient for surfing etc.
Yesterday I realized the ambient light sensor on mine stopped working (adaptive brightness not working) and today on my wifes Pixel nearly all sensors stopped working (screen rotation, compass, ... not working).
Using the app "Sensors Multitool" on her tablet I only get those menu entries: "Battery", "WIFI", "Light" and "Distance" (translated names from german). Those are all working.
On my own Pixel I get many more (e.g. Gyroscope, Acceleromator, ...). Light and distance are shown but both receive no useful/no values from the sensors. All others beside of those two are working.
I already tried to factory reset and wipe cache on my wifes tablet - not working
Any further ideas? To me it sounds like hardware defect on both tablets..
There was an update to the secondary processor (EC) code with the Feb OTA, so its possible that its a software glitch - assuming you have updated. Judging from the current known issues, there seems to be some source of variation which makes testing some of this software tricky...
I flashed the old version (6.0.1 (MXB48J)) but sadly it didn't work I guess this also downgrades the code for the EC? Any further ideas? Looks like we've got to send both of them back for a replacement....
Flashing the latest Android N Dev Preview fixed the sensors for me!!
My wifes Pixel got replaced without any problems So everything good from our side.
Related
My z1c has an accelerometer that is broken. This means auto rotation doesn't work for example. Sometimes i can get it working by calibration and/or restart, but after a while the sensor will be off again. I'm testing with the app "android sensor". At the moment the sensor is stuck as if I'm holding my phone horizontally.
I'm running latest software, 14.3.A.0.757
Since i bought it while travelling in Thailand (not the smartest, but my old phone broke, so what to do..), I'm trying to see if anyone here has experience with this, before contacting Sony.
As far as my searches go, i have not been able to locate this as a known problem.
My accelerometer works perfect i have my phone since sunday. Maybe you should perform.a factory reset if that doesnt help its defenetly hardware issue.
Wysłane z mojego D5503 przy użyciu Tapatalka
I got the same problem. Bought it about 9 months ago in Uk. Since few months im on .108. I don't think that firmware is a problem coz it starts about 2 weeks ago. Accelelometer stop working every now and then. Reboot helps but not for long. Gonna contact o2 as still have warranty.
guys i have the same problem with my z1
seems like some software problem ..
because if the hardware is broken it would not start working after restarting
did any of you , opened your phone for replacing or something?
I had this problem too. All sensors would stop responding and give no readings in the service tests. A reboot would fix it for a couple days but the issue would always return. At the time I was running a 108 rom that I had downloaded from this forum, Russian I believe. Recently PC companion told me I had an update but the version was also 108. I did the update without wiping data and I haven't had the problem with the sensors for about 3 weeks.
Still not sure what caused it, it didn't start with my first loading of 108, but some time after that. My best guess is that some app hosed something up and a software update fixed it. Hope it doesn't come back.
Sent from my D5503
Just rebooting the phone worked for me
camaro322hp said:
I had this problem too. All sensors would stop responding and give no readings in the service tests. A reboot would fix it for a couple days but the issue would always return...
Sent from my D5503
Click to expand...
Click to collapse
camaro322hp said:
I had this problem too. All sensors would stop responding and give no readings in the service tests. A reboot would fix it for a couple days but the issue would always return...
Sent from my D5503
Click to expand...
Click to collapse
Same here. I believe that the problem started when I changed my screensaver to one of the animated backgrounds with planets on it. On a first run it would work and rotate the planet render in the background when I tilted the phone. The next day it stopped working. I mean, the screensaver was on, but it would no detect orientation from the gryroscope. The screen also stopped autorotating when playing YouTube videos from the app, the compass app wasn't working and so on. I installed a few small sensor monitoring applications and all of the gave me no readings for the accelerometer or gyroscope sensors. Some other sensors were disabled, such as proximity, illumination level detect and so on. I was afraid that the accelerometer could be broken from humidity, pressure or a small drop that happened, but these small incidents could not explain the problem by their own (specially since the Z1c is thoroughly tested against all of these). I thought of maybe a faulty motherboard construction or whatever and starting considering the possibility of taking it back to the store for the guarantee, but before that I googled and came along this site and a couple others.
I fiddled a bit with Android menu config. settings but to no avail. I completely discarded the factory reset advice (that's SO crazy!).
When I rebooted the phone (no reset, just a regular off and on again process) all sensor readings were back on. I still didn't have the chance to check whether the problem might come back in a few days or not.
The cause may or may not be on the planets screensaver app. I also used Google Earth, YouTube and a few other apps the day sensors stopped working, but none of these gave problems in the past.
Fingers crossed for this issue not reappearing.
Hello everybody on my Z1 accelerometer compass gyroscope and light sensor does not work! any help please?
Yesterday I've had the same trouble, screen orientation stopped working. Apps using the acceleration sensor stopped working (Google Sky i.e.)
First I did a factory reset without any change, still no function. As I still have warranty, I wanted to prepare the phone to send it to Sony for repair. So I switched the phone off, removed SIM and SD (what I haven't done before) and switched it on again. Then I did a factory reset once again and here we go the sensor went back to work.
Probably the factory reset is "deeper" if there's no SIM and SD card in the phone? Who knows.
So, I've moved to LineageOS with my Mi5 at lineage-14.1-20170620-nightly-gemini and everything was fine.
About a week ago I've updated to lineage-14.1-20170704-nightly-gemini and all worked well still.
But yesterday proximity sensor on my phone gone wild: it stopped to work in all situations, but started to work wrong for WhatsApp: if I press play on voice message, screen goes off and WA plays message in main speaker (top one).
Right now I've updated firmware to this (Developer 7.7.6 Firmware from https://forum.xda-developers.com/mi-5/development/tool-flashable-firmware-twrp-easy-t3474898) and updated lineageOS to lineage-14.1-20170711-nightly-gemini but it didn't help.
Proximity sensor now looks completely dead: tried Sensor Box app from GoolePlay and it permanents shows 5.000305. Proximity sensor doesn't work during any calls, etc.
I found some topics with similar issue on Mi5 on miui forum, and sensor calibration seems to solve this issue on stock MIUI, but can't find any info about how to calibrate sensor on lineageOS.
Requesting any assistance, and especially from @bgcngm and @h2o64.
Thanks
Same problem here. Have you found any solution?
Best,
g.
A few days ago, I found my phone can not indicate the direction，such as google maps, some compass apps. The direction arrows are turning counterclockwise.
And I can not use the Panorama and Photo Sphere in the camera to take pictures, the positioning dots are moving to the right.
I suspect that a sensor does not work， but I use the test application and found that the sensor is running normally. My pixel xl is Android8.0, I went back 7.1.2, well the problem was still there. Now I update it to 8.0. (my phone model is 2100, unlocked bootloader, already root)
I don't know how and when this problem happened, hardwares are all working. Maybe it is a bug? Can someone solve this problem?
Have you tried to recalibrate it by moving your phone in a figure 8 pattern?
I tried it, but it did not work
I tried it, but it did not work. Hardwares are no problem, replacement system is also useless. Maybe the reason is I unlocked the bootloader?
KyaBiASaMa said:
I tried it, but it did not work. Hardwares are no problem, replacement system is also useless. Maybe the reason is I unlocked the bootloader?
Click to expand...
Click to collapse
My compass works fine and I've been unlocked for some time now (Verizon phone). I have never been on a 8.0/8+ build currently running 7.1.2. Custom rom. Recently,I've seen several reports of users having unrecoverable issues after switching to the delicious cookie builds aka O.
So, I've moved to LineageOS with my Mi5 at lineage-14.1-20170620-nightly-gemini and everything was fine.
About a week ago I've updated to lineage-14.1-20170704-nightly-gemini and all worked well still.
But yesterday proximity sensor on my phone gone wild: it stopped to work in all situations, but started to work wrong for WhatsApp: if I press play on voice message, screen goes off and WA plays message in main speaker (top one).
Right now I've updated firmware to this (Developer 7.7.6 Firmware from https://forum.xda-developers.com/mi-...-easy-t3474898) and updated lineageOS to lineage-14.1-20170711-nightly-gemini but it didn't help.
Proximity sensor now looks completely dead: tried Sensor Box app from GoolePlay and it permanents shows 5.000305. Proximity sensor doesn't work during any calls, etc.
I found some topics with similar issue on Mi5 on miui forum, and sensor calibration seems to solve this issue on stock MIUI, but can't find any info about how to calibrate sensor on lineageOS.
Does anybody has problem with proximity sensor in Android Pie?
For me it stops work after half day and only reboot helps. In Oreo I haven't this problem
I've gotten this problem during calls
Update: proximity sensor stop work in phone app. With other apps its works without problem.
Interesting. Has worked for me but I've only made a handful of calls since going to Pie.
Sent from my Pixel 2 XL using Tapatalk
new update: looks like I found why proximity stops work. I use Cube Call Recorder and this app after a couple calls "kills" proximity sensor in dialer app. I removed Cube and now everything ok.
I'm having this problem too, but I don't have any sort of call recording app. Randomly it just refuses to put the screen to sleep when I'm on a call. Really frustrating.
Same issue here, since few days I have notice that the proximity sensor during phone calls will not turn off the screen, only reboot restores sensor functionality that's annoying, also I have this pixel 2xl for 2weeks this is an irritating issue. Hope help comes soon.
P.S
No new software has been installed on this phone that I have not used on my previous phones essential ph1 and Samsung Galaxy S8.
Cheers.
Couldn't find this thread earlier.
I'm also facing the same issue now. Android Pie.
Anyone found a Solution?
#5 was my problem