Hello everyone in XDA
This is my first post, but I've already used this blog to solve many of my problems in the past, and for that I thank everyone.
But currently I'm facing a kind of problem I don't find a solution for. What happens is that gyroscope and accelerometer aren't working properly. Most of the times I boot my phone, it switches properly from portrait to landscape mode, and even if I use de CPU-Z app i find they are all outputting readings properly. But after about half an hour none of them outputs nothing at all. Two situations that may be hidding some solutionable behaviour:
1- if I let the sensors-reading app open in memory, the sensors keep outputting data;
2- when the sensors stop outputting data, all the lines in the sensors tab of CPU-Z are blank, however if I force the use of the light sensor it suddently appears the output of its data.
Currently I'm using a nightly of CM, but in the past month I had still the stock rom, which presented the same problem.
I've already thought it could be hardware problem, but I find this inconsistencies somewhat awkward and irregular.
Related
Yes, another proximity question!
I have trouble with this sensor using 3rd party apps.
On system it works fine without a problem (screen on/off during phone call never had any problems)
but any apps which use this sensor stops working after rebooting.
-Gravity screen on/off
-Automaton gestures
-Automate it!
These are the apps I tried and encountered problems with...so pretty much all of them!
The sensor works, cpuz sees it working with both distances 3cm near and 10cm far, but apps don't :S
For example if I try to record sensor state in automate it it just reads '10 far' and notihng else.
aamof rules with sensor far work fine but with near don't....
I encountered this problem both across 10.1 and 10.2 and different roms...anybody else encountered this isse?
I recalibrated tegra.so from adb...I'll try to go back to stock and try from there recalibration but seen thtat it "works"
I'm not sure how that is going to help.....
Rudjgaard said:
Yes, another proximity question!
I have trouble with this sensor using 3rd party apps.
On system it works fine without a problem (screen on/off during phone call never had any problems)
but any apps which use this sensor stops working after rebooting.
-Gravity screen on/off
-Automaton gestures
-Automate it!
These are the apps I tried and encountered problems with...so pretty much all of them!
The sensor works, cpuz sees it working with both distances 3cm near and 10cm far, but apps don't :S
For example if I try to record sensor state in automate it it just reads '10 far' and notihng else.
aamof rules with sensor far work fine but with near don't....
I encountered this problem both across 10.1 and 10.2 and different roms...anybody else encountered this isse?
I recalibrated tegra.so from adb...I'll try to go back to stock and try from there recalibration but seen thtat it "works"
I'm not sure how that is going to help.....
Click to expand...
Click to collapse
yeah, i noticed in viber screen doesn't turn off when you put your phone enxt to your ear. i dont have any other apps that use proximity sensor other than phone app, but that one works without issues.
the issue persists in stock as well as custom roms. no idea how it was on ics, though
It also appears on stock?! wow never would've thought...
It's a pretty considerable bug to have never been mentioned before...
all problems with proximity encountered so far always seemed caused by bad calibration..
this kinda sux :S
Devs and wise people, do you think this could be caused by the fact that the 'near' state is set at 3cm reading and 3rd party apps look for 0 distance with 0% tolerance to have widespread compatibility?
Do you think it is possible to change these settings?
Hi all,
I've found that in the Google Maps app, the direction that the app thinks I am facing is almost invariably wrong, and often varies wildly even when I'm not moving. I think it is related to the rotation vector sensor (Sensor.TYPE_ROTATION_VECTOR) but I was wondering if others had experienced similar problems.
I've looked at the various sensors (and compared them to a Nexus 5) and two stand out: the Uncalibrated Gyro (Sensor.TYPE_GYROSCOPE_UNCALIBRATED), and the Rotation Vector (Sensor.TYPE_ROTATION_VECTOR).
The Uncalibrated Gyro seems to sit with a z-axis value of 1.17 rad/s, and the rotation vector *sometimes* seems to stick at a high value too.
Anyway, the question is:
(1) Do other people find that Google Maps tends to detect them pointing in the wrong direction, or turning when they are in fact not turning, and
(2) Do other people find that the rotation vector sometimes sticks at a weirdly high value (if they have the tools to check: I wrote one to check myself, which I can attach if desirable but being unknown I don't know if anyone would trust to install it =)
Cheers.
This may seem a basic question, but did you try calibrating the compass via the service menu?
Enter *#*#7378423#*#* in the dialler.
Service tests
Compass
Follow the on screen guide.
That always seems to correct any "creep" or odd readings with my compass and gyro. You can also check the gyro from the service test menu.
Sent from my C6603 using Tapatalk
kingvortex said:
This may seem a basic question, but did you try calibrating the compass via the service menu?
Click to expand...
Click to collapse
Cheers, I did do that but it didn't seem to make a difference. However, now GMaps seems to be working pretty well so that's good. (It's done that before, but maybe this time it will last). However, the game Ingress is still having problems (which it doesn't have under Stock). Like GMaps, it tries to detect the direction you are facing. On Stock 4.4.4, Ingress does a tolerable job of detecting direction of facing - it mostly gets it right. However, using CM11 the behaviour is really weird: turning the phone has no effect until a tipping point, at which it is detected that I've done a sudden 180, and if I keep turning the phone it eventually happens again. Doing the phone-calibration-twirl has no effect in this case. (Note: that is rotational movement with the phone laying flat on a table, and a metaphorical tipping point. I'm not standing the phone up until it tips over)
Maybe related, but maybe not: Having done some more testing with a few ROMs and kernels, what I've found is that CM11 (both official and _infected builds, with both the included kernel or the multirom-modified kernel) don't provide a TYPE_GYROSCOPE_UNCALIBRATED sensor (where as the stock 4.4.4 ROM does).
That said, Ingress doesn't appear to *use* the TYPE_GYROSCOPE_UNCALIBRATED (instead only using LINEAR_ACCELERATOR, ROTATION_VECTOR and MAGNETIC_FIELD) so I'm a bit confused. (Edit: I believe these are the sensors being used based on the hex values being passed to getDefaultSensor in the smali of Ingress.)
The sensor results for both stock and CM11 look to be about the same, with the exception of the 'Uncalibrated Gyroscope' not being present in CM11 whereas it is present in stock 4.4.4. I think that sensor missing is probably a bug, but I'm not exactly sure where to report what is probably a device-specific bug for CyanogenMod.
tl;dr;
Calibration movements might have fixed it in Google Maps, but Ingress is still having problems in CM11 (but not Stock 4.4.4).
I think there is a sensor missing in CM11 that is in stock, and that's probably a bug. Where should a device-specific yuga bug in CM11 get reported?
This may seem a basic question, but did you try calibrating the compass via the service menu?
Enter *#*#7378423#*#* in the dialler.
Service tests
Compass
Follow the on screen guide.
That always seems to correct any "creep" or odd readings with my compass and gyro. You can also check the gyro from the service test menu.
Sent from my C6603 using Tapatalk
Sent from my C6603 using XDA Free mobile app
---------- Post added at 10:03 AM ---------- Previous post was at 09:19 AM ----------
Sorry guys for this copy paste, my mistake.
I have exactly the same problem.
Calibration do nothing.
Sent from my C6603 using XDA Free mobile app
Hi!
I am facing problems with the orientation sensors (accelerometer and/or gyroscope), because installing several applications to test them (or use games), it is clearly observable, that they are a bit off (with enough to be disturbing when required). For example, games or tests that simulate a ball, and my phone is laying on a horizontal table, the ball rolls quickly to the edge of screen. This happens as well with the built-in tests in the "service menu" of the phone, for accelerometer and gyroscope also.
Do you have any suggestions how could I calibrate these sensors globally (for every app)?
Thanks.
Info
vetko said:
Hi!
I am facing problems with the orientation sensors (accelerometer and/or gyroscope), because installing several applications to test them (or use games), it is clearly observable, that they are a bit off (with enough to be disturbing when required). For example, games or tests that simulate a ball, and my phone is laying on a horizontal table, the ball rolls quickly to the edge of screen. This happens as well with the built-in tests in the "service menu" of the phone, for accelerometer and gyroscope also.
Do you have any suggestions how could I calibrate these sensors globally (for every app)?
Thanks.
Click to expand...
Click to collapse
factory Reset ur phone and then use PC companion app to Repair Firmware...
this can wipe current data and install fresh firmware on ur device
:good:
Hi,
I have the same problem. Only the x axis of the accelerometer seems to be affected : it show a value around 1 instead of 0 while the phone is sitting flat. Y and Z display normal values.
All the software solutions I have tried have had no effect at all... It seems the built-in test reads raw data from the accelerometer. It is hard to imagine how this can be a hardware problem though...
Anyway, in my case I believe a software fix (x=x-1) would do the trick but I have no idea how to do such a thing ! Any help ?
@vekto : Have you solved the issue by any chance ?
Would anyone care to try the accelerometer tests and post their results ?
Typing *#*#7378423#*#* will get you on the service menu. The two significant tests are "accelerometer" and "gyroscope".
I'd post some screenshots myself but I'm not allowed yet...
I'm having the same problem now. It seems one axis is affected. Haven't found a way around so far. This is sad because it affects the images taken with Google Camera Sphere mode. The images are badly aligned together with glitches in between. My phone wasn't like this before.
Either a SW fault - might be able to calibrate with GPS Status & Toolbox app, for example - or a FW fault - and reflashing ROM might help (highly unlikely) - or HW fault - the sensor has moved on the board (which is a bad sign anyway, might be on the way to disconnecting itself).
I sent mine to Xperia Care and got it back with the accelerator fixed. Still unclear if it's a HW problem...
It came back with a white spot on the screen (near the power button) though... so I sent it back again
I'm also having issues with the gyroscope. Installed Bubble app to calibrate the gyro. It showed the gyro was of a couple of degrees. Unfortunately the bubble app calibration doesn't work in a game like Need for Speed. It's very difiicult to achieve good times in the game right now since I have to hold it tilted to the left to go straight ahead.
So if anyone has a fix or workaround... Please do post.
Same problem, Seems after factory reset whith wipe dalvik cache.
any solution?
02nd March 2017, my autorotate has completely stopped working, restart, safe-deposit and reset do not fix. Diagnostics show Gyroscope Light Sensor and accelerometer failed testing, 3 years of same issue, surely there must be a fix that works by now?? ( please note, " turning it off and on again " does not fix it )
Helps Please
I have the same issue. Since last week, gyro, accelerometer, light and proximity sensors stop working. I've tried reflashing stock ROM without success. I have not warranty (almost 3 years old), so I even try to disassemble , disconnect an reconnect every flex (I don't know exactly were the sensors are located on the board). After that I get almost 8 hours of fully functionally sensors and then, they stop working again, so I'm almost sure it's a hardware issue.
Same problem for 3 years
I'm just now getting around to doing something about this. As my power button stopped working I can't post requested screenshot without going to the pc. I have been shopping new (fall 2018) phones after having the Z3+ since release. In my research I'm finding the phone still is better than Samsung, LG, and the pixel3 for me because the 3.5mm phone jack is mandatory for me using my device with an i-rig midi requiring both that port and the USB at the same time. I'm going to do everything I can to keep using this phone till it falls to dust. It's one of 4 Sony I've bought since the day Z1 came out of t-mo. I look forward to testing solutions. :good:
Some time after my post, I bought a new jack/proximity sensor flex and replace it. This solved the issue, but weeks later, the bottom portion of the touch screen becomes unresponsive. May be I have done something wrong... may be programmed obsolescence...
Hi I'm facing a problem of my gyroscope I don't know which one is not working a gyroscope or accelerometer. My gyroscope is so delay when I play pubg mobile and I can't also calibrate my Gsensor it always says FAIL but I put in a perfect flat surface please please please help me with this problems
I have Note8. It has a very strange sensors error, as below:
- All sensors, from proximity sensor, light sensor, to GPS, iris scanner, and all the other sensors do not work at all.
- In the app like Phone INFO Samsung, CPU-Z or AIDA64, in the Sensors section, all sensors do not work.
- The Auto Brightness function does not work (due to the light sensor), the brightness of the AOD screen is also not adjustable.
- When making a phone call and move the phone close to the ear, the screen does not turn off due to proximity sensor.
- Auto Rotation function is not working (due to rotation sensor).
- Google Maps shows inaccurate location. Other apps that rely on GPS (such as the speedometer app) are completely not working.
- The iris scanner function does not work either.
It was about two weeks ago. I've Wiped the cache, restart the phone but does not make sense.
Yesterday it suddenly returned to normal, I don't know why.
But today - while I'm typing this post - all sensors suddenly do not work again.
Any idea about the error and how to fix it?
Thank you guys
Best advice I can think of is to factory reset and see if that alleviates the problem.
If you did not do anything firmware-related, or you did not drop or submeged your device, the best you can do is to make a warranty claim, pure and simple, if you have no way to make such claim, well, next time you should consider getting a device from an official source
I've read other users have had same problem. Ones I read said it was motherboard issue had to have sammy replace it.
Thank you guys
There is also built-in sensor test. Open dialer and dial *#0*#
I noticed a problem when I was playing Asphalt (racing game on me Note 8). I am unable to use the Tilt controls to move the scar.
Testing out the Sensors using *#0*# at the dialer revealed that all the SENSORS was faulty.
I reset the whole phone just now. The issue is still there with the sensor. As expected Auto rotation doesn't work.
Running the latest version 8.0.
I recently changed my motherboard (under warranty) 3 months back cos something was faulty. Seems it may be another motherboard issue.
Anyone else in this thread solved the issue?
Hey everyone I'm facing the same problem. All sensors stoped working but they were working before on 7.1.1 and i updated my device to oreo and realized all sensors stoped
Then i got another updated for about 900mb i thought maybe this update will fix them and also that update said tha after updating the user cannot downgrade to nougat but after updating the problem still exsist. Please if anyone can help i also try to flash same oreo firmware with odin but doesn't fixed the sensors
Hi there,
I just bought a used Mi 5 to replace my previous one which I lost and I saw it as a good opportunity to try out the MicroG fork of LineageOS. I flashed the newest firmware and installed the OS and it's running quite well all in all – however I have two weird problems:
1. When using mapping software my compass seems way off. Is there an easy way to calibrate it?
2. (Potentially related) The device screen sensor is flipped when held horizontally. The screen orientation seems correct when held as usual, but as soon as I try to take a picture in landscape mode they turn out flipped upside down. Can anybody explain this? Can I overwrite this somehow?
Thanks a lot for any help
PS: I can't edit the title anymore so I'll add this as a separate paragraph. I've had problems with losing my signal at random intervals since I've had the previous Mi 5, with this one it's no different. Is this a known problem for Lineage-based ROMs? Any way to improve the situation there?
Hm.. so I tried the following firmware images from github/XiaomiFirmwareUpdater/firmware_xiaomi_gemini/releases (can't link to this unfortunately):
fw_gemini_miui_MI5Global_V9.6.1.0.OAAMIFD_e569ca4e32_8.0.zip
fw_gemini_miui_MI5_V9.6.1.0.OAACNFD_996b4bcbff_8.0.zip
fw_gemini_miui_MI5Global_8.7.19_7a80214a95_8.0.zip
They all show the same behavior regarding to the camera orientation bug. It's independend of the camera app in use. I also tried enabling and disabling the Camera2 module in Magisk, which did not seem to have any effect. I found a similar issue for the front camera after enabling Camera 2, but this seems to be unrelated.
Does the same happen with non microG versions of LOS?
Have you already calibrated the compass using the gestures in all 3d axis? Search for it on youtube.