Accelerometer fails - Motorola Droid 4

Hi dudes
I'm having problems since few weeks with G-Sensor, it was stop working suddenly, ZDeviceTest says sensors are stucked in 0,0,0 always and any calibration app works (always stuck in 0,0,0). This problem affects to GPS orientation, to camera (undetect when is in landscape) etc.... only way to change to landscape is open keyboard and when close, screen remains in portrait.
I restored by default, rooted looking for to sensor config files, I test another ROMS (Cyanomod 10.2, SlimBean, Pacman, etc), restored to original ICS and JB and I don't know what I can do
Can somebody help me?
Thanks!

Related

[Q] Captivate compass issue

looks like data output of my captivate's sensors is reverted with accelerometer, that means I starting any compass app and puts phone to horizontal surface and rotates it clockwise and counterclockwise, normally compas should rotates but it doesn't.
When I put it at an angle to the surface, compass starts rotating. Behaves itselfs as the accelerometer sensor
The strange thing is that compass working like a charm on KK4 modem, but I can't use KK4 modem on CM\MIUI build because of abnormal sensitivity (it is too sensitive) of mic during call, the caller can't hear me clearly.
I trying to google for this problem but didn't find anything usefull, also I tries to calibrate it, of course it didn't help
Any ideas how to fix the problem, its really annoying me during GPS navigation-the map alvays rotating?
P.S. now I'm using MIUI-1.12.9.10 I9000XXJVT baseband and Glitch v13 kernel
I'm actually seeing the same thing; my compass seemingly responds primarily to accelerometer or gyroscope detected motion (or the magnetometer is just busted). As far as I know, this only started happening after I updated to KK4 and installed CM7 over it (the compass was fine under CM7 installed over KB2). I've tested other modems, including KK4, to no avail. Flat surface calibration (face up and face down) and the compass calibration (using the figure 8 rotation) indeed do not help.
Has anyone else experienced this issue and/or have any suggestions? Could this at all be related to GB bootloaders? I doubt the latter to be the case, but I'm all out of ideas here, because outside of things within the OS, that's the only thing I can think of that's changed.
ROM: CyanogenMod v7.2.0 RC0 KANG
Kernel: Glitch v13.1
Modem: JK4
So I cleared /data/system/yas529.cfg and rebooted the phone, and the system created a new file one on startup. This seems to have... changed... something. That is, the phone seems to be reading the magnetometer now, but it's behaving crazily. Firstly, the compass reads west when the phone is pointed north. Secondly, when I move the phone counterclockwise, the compass actually also spins counterclockwise, so when I reorient the phone from north to west, the compass actually points from west to north.
Compass recalibration via figure 8 motion and pitch/roll recalibration (both with phone face up and face down) don't help. Anyone familiar with /data/system/yas529.cfg, and what a "good" copy looks like? Mine currently has the following values:
Code:
13,19,16,174,26,-158,3,255,255,255,2147483647,2147483647,2147483647,0,
The previous one that seemed to respond primarily to accelerometer/gyroscope had the following values:
Code:
14,19,16,-46,52,-170,3,255,255,255,2147483647,2147483647,2147483647,0,
Well. I have no idea why this worked, but I decided to revert to stock KK4, then reinstalled CM7, starting with 7.1.0, then worked my way up to 7.2.0-RC0.
Testing the GPS again, the compass is working fine now. Looking at /data/system/yas529.cfg, I see the following:
Code:
14,19,16,39,-49,159,3,255,255,255,2147483647,2147483647,2147483647,0,
While in KK4, I also rooted and checked this file, and saw the following:
Code:
13,19,16,36,185,150,3,255,255,255,2147483647,2147483647,2147483647,0,
In either case, the compass worked fine. Perhaps worth noting is the fact that the 6th item in the list is actually positive, which may or may not be related to my previous observation that the compass rotation made no sense (not sure, really). I tried negating that number to see if I could reproduce the issue, but it didn't work (and in fact, calibrating the compass only flipped the number to positive, even though calibration always used to set it negative). Not sure what to say.
Anyway, all looks well now. For anyone else who runs across this issue, the only thing I can suggest is for you to just try reinstalling CM7 (and possibly reverting all the way back to stock if reinstalling alone doesn't help).
I find different apps have different results. There are compass apps that work. Keep looking
Sent from my SGH-I897 using xda premium
I didn't test only a single compass app; I tested several apps (Maps, GPS Essentials, GPS Status, to name a few), tested several different modems (JL3, JK4, KK4, to name a few), and calibrating various sensors (accelerometer/gyroscope, magnetometer, GPS). Nothing helped.
After the reinstall, the exact same apps with the exact same modems are working. The fact is that something was screwed up with the install that caused this.
- When the compass wasn't working, my install process was: KK4, Corn Kernel (without rooting), then straight to CM 7.2.0-RC0.
- Before then (when the compass was working previously), my install process was: KB2, root, CM 7.1.0, and then nightlies upward to 7.2.0.
- This time around (with the compass working), my install process was: KK4, Corn Kernel (with root), then CM 7.1.0, then CM 7.2.0-RC0.
I'm not sure I'm up for reinstalling repeatedly just to eliminate possibilities, but I suspect it may have been an issue with the install/upgrade process itself. Or just a random glitch. Either way, the moral of the story is that if nothing else helps, try reinstalling (possibly from stock).

Do your sensors work in ICS?

After trying all the ICS roms out there, I've come to the conclusion that my auto rotation and proximity sensors simply do not work within the OS itself.
Flashing back to a GB ROM confirmed that the the sensors are definitely working. And they work fine in 3rd party apps running on ICS... But neither auto rotation nor "screen off when in call" work at all.
It seems from a quick search that I'm not the only one with this problem (http://code.google.com/p/ice-cream-sandwich-sgs/issues/detail?id=224).
Anyone know of a fix?
EDIT: Never mind, guess it's a known issue: http://ics.samsung-updates.com/trouble/
Sensors working fine
With TH CM9 ICS running on my device i've no issues with the sensors. All working fine.
Did you try this ROM as well?
Never faced any sensor issue, ROMS tried Slim2.7,2.8,2.9 Team ICSSGS 2.11,3.1,4.2

Problem with g-sensor

Hi to everyone,
First of all, i have to apologyze for my english, and just in case if there is another thread about this, but i haven't been able to fnd a solution or anyone with a similar problem.
I have a problem with the g-sensor of my OB, but i think it's a sw issue, as i can calibrate it with apps like gps settings (or something like that) putting the phone on a flat surface, and then i can see that it behaves normally IN THE APP. But then i go to the gallery and it automatically rotates to landscape mode, no matter how i put the phone. It detects that it is always sideways.
So i would like to know it f there is a way of calibrating the system accelerometer (not using 3rd party apps, which works for the app) and fix this problem.
Note: I have tried stock rom 2.2, 2.3 and cyanogenmod and the result is the same, so i have to disable screen rotation at least for reading properly the menus.
Any help would be appreciated.
Thank you in advance.

Nexus 6, all sensors are not working

Recently I noticed that, while on call, my phones screen not turning off and on, my screen does'nt adjust the brightness levels automatically, my camera app is so slow to start, so I downloaded sensor apps to check sensors, i was shocked to see, none of the sensors are working in that app. Things like gyroscope, gravity, magnet, light, proximity. Nothing is reflected in the app.. What is happening? And how do i get them to be working?
i was running pure nexus rom, then i flashed beanstalk, but failed to install as phone goes in bootloop, so i flashed back pure nexus and realised, none of the sensor is working, i tried everything...flashed to stock several times, but failed to get sensors work again.
anyone else getting the same problem ?
Please guys help me out to get my phones sensors to work again.
Did you use only one app or several? It may be an issue with kernel, maybe a clean flash can solve problem?(if you did not already)
Btw i checked "sensor test" app and it seems everything is working with brand and model name is sensors. I have stock ROM(marshmallow) with hellscore kernel.
Clean flash another ROM. If that doesn't work, backup your data and fastboot flash a factory image to return to absolute bone stock. If it's still not working it's a hardware issue and hopefully you can RMA if within the warranty period.
I gave my nexus 6 to moto service.... They saying.... Display n touch need to replace in order to work sensors..... I can't understand how display n touch linked with sensors....????
Sent from my Nexus 6P using Tapatalk

Problems with Compass and Rotation sensor

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.

Categories

Resources