[XDA Assist] mw210461:
I know that this sounds ridiculous, yet I have observed this issue for the third year in a row.

My Neo 003 smartphone (Android 4.2, 2013) fails to read out its sensors (gravity, compass, location etc) during the summer months!

All apps reading the sensor data will 'freeze' or 'hang', or simply report 'waiting for event'.

The values for xyz are stuck at odd values, or change once or twice before hanging.

I can provide more details on the sensor hardware used, screen shots of these weird freezes if interested.

It took a while before I noticed this obvious dependency, as it is so odd and unexplainable.

After working flawlessly for several months the sensor readouts would start to hang more often in later spring of 2014.

The effect got worse over time; I suspected a hardware failure and was pissed when they got stuck for several months in the summer. I contacted the manufacturer and was brushed off - FU! So I kept trying.

To my surprise the sensors would start returning values more often in early fall, and would run perfect again around October, for the entire winter!

And then the SAME happened in 2015 again! And again this year!! Currently all sensors react flawlessly to motion, shaking, rotation. They had become flaky around April, hardly worked in May and failed during the summer, came back to life several weeks ago: I checked them almost daily to see this drift of functionality. Just WHAT is going on here?

I have tried to fool my phone by resetting the date and not going online to keep the wrong time - it did not affect the dependency. It failed to run in summer when set to winter dates.

I use the phone at home exclusively and always in the same rooms. There is no significant environmental change I can think of that could affect this (temperature, pressure, humidity). The problem occurs as well on the road anyways.

I am a phycist by trade, in fact I was quite involved in electronic measurement and data collection for many years.

This phone is driving me nuts, because I can not come up with a resasonable explanation for its odd behavior?

Android seems to use a quite thick layer of software drivers and event handles to manage the sensor readouts; it looked rather confusing to me and was not straight forward as I hoped for.

Since the failing mechanism is NOT hard but 'soft' (slowly shifting from working to failure over several weeks, and back to functionality in a similar way) it can not really be a software 'numbers' glitch, or?

Could other apps (about 600 are installed) interfere and block the readout? But why only in the summertime months??

I REALLY want to learn about this phenomenon, because it is about the weirdest problem I ever saw on an electronic device.

Who can shed some light on this, who can explain how Android initiates the sensor chips and reads them out?

Who has seen the same effect on other phones or devices?

What tests should I conduct to isolate this unique failure pattern (phone in the fridge, in a Faraday cage etc).

I do not want to break my Neo, despite its age it works quite well and runs stable, with its original ROM in place.

It took me THREE years to come forward with this issue, because I could not believe my own observations.

Now it is time to bring it up.

Please explain my spooky phone to me - thanks a lot!

m