I know there is the Service Menu screen, which you can get to when the phone is locked using the secret code found here: http://forum.xda-developers.com/showthread.php?p=7847292, where the digital compass looks like it can be calibrated in the service tests section. Anyone know if this is a permanent calibration affecting all apps installed?
Also, is there a way to get a permanent calibration of the accelerometer? My accelerometer is off by about 4 degrees and apps which use it, including rotating the screen are noticeably affected. Does anyone know of any apps that can make a permanent calibration that will be system wide? Or any other way of calibrating this sensor for all apps?
Silly22 said:
I know there is the Service Menu screen, which you can get to when the phone is locked using the secret code found here: http://forum.xda-developers.com/showthread.php?p=7847292, where the digital compass looks like it can be calibrated in the service tests section. Anyone know if this is a permanent calibration affecting all apps installed?
Also, is there a way to get a permanent calibration of the accelerometer? My accelerometer is off by about 4 degrees and apps which use it, including rotating the screen are noticeably affected. Does anyone know of any apps that can make a permanent calibration that will be system wide? Or any other way of calibrating this sensor for all apps?
Click to expand...
Click to collapse
Yes this would logically be a system wide calibration... If it were not system wide, then by the same logic, it would only calibrate the accelerometer in the Service Menu, which provides absolutely no use whatsoever.
I have no proof either way, but it makes sense to me...
Why not try calibrating your device incorrectly (i.e. upside-down), and see if it's screwed everywhere else as well...
In the service menus, there does not exist a way to calibrate the accelerometer, just a screen for testing and showing the accelerometer values.
On another forum, one specific to Android, I found a link to this article about calibrating the accelerometer sensor permanently: http://smartanuj.com/samsung-galaxy-s-troubleshooting-and-optimizing-guide
However, that guide involves rooting a Samsung Galaxy S specifically, and running a terminal command. I wonder if there is a method for us X10 users that doesn't involve rooting. If not, does anyone know if there is a similar terminal command applicable to rooted X10's?
It turns out that my accelerometer is off by -.304ish on the horizontal axis. Anyone know how to calibrate it on the system level.
Please help, this can be very annoying when playing games that don't have a calibrator included.
BUMP. If anyone knows a way can you please tell me because this can become a nuisance at times...every game without a calibrator included tends to move towards the left...such as NFS Shift. The car tends to go to the left when holding the phone completely level.
ANY files I can tweak to change the sensor settings.
ANY programs that change the SYSTEM accelerometer
ANY help would be appreciated.
You can access test/calibration service via adb:
Code:
/system/bin/akmd2 -s
BUT I don't recommend it. Be warned that you may mess up your device!
Cheers,
z
DAMN, if a veteran android developer advises not to mess with the files...I would probably be stupid not to listen...I guess I will just leave it alone.
Okay I was stupid and did not listen...and tried it. BUT it doesn't actually change the sensor...
Start Factory Shipment Test
Start HDOE calibration
Start measurement
Start acceleration sensor calibration
I clicked Start acceleration sensor calibration, and and set it up according to the instructions...but everything remains the same.
Still a small tilt in horizontal direction.
My compass works in Zdevice test, but not in certain apps (Though it used to) - it doesn't work when I press compass button in Maps and doesn't work in compass specific apps. It DOES work in Yelp monocle.
Any ideas? I've fixed permissions, done clean installs, everything.
One bump before I give up on this. (don't really use compass mode that much, but would be nice to fix)
Try gps status app. It has a compass calibration tool that will tell you to rotate the phone 2-3 times on each axis. Fixed my wonky readings I had.
Sent from my Evo LTE using Tapatalk 2
kmyerslp said:
Try gps status app. It has a compass calibration tool that will tell you to rotate the phone 2-3 times on each axis. Fixed my wonky readings I had.
Sent from my Evo LTE using Tapatalk 2
Click to expand...
Click to collapse
Just downloaded that - compass doesnt respond at all in that app. It only seems to respond in ZDeviceTest.
It seems like the majority of apps aren't able to "talk" to the compass sensor, but for whatever reason ZDeviceTest can.
Update: I just downloaded "smart compass" and it works fine - Maps will still not enter Compass view. SO CONFUSED
So I'm using the CM11 4.4 Kitkat on my Galaxy S4 and recently found out that my proximity sensor isn't working (when I dial the screen goes black and won't turn on until the call is over). I've read many threads about fixing it but I think it's broken. So all I want now is to disable it but there isn't such option in the Cyanogenmod. Is there anyway to disable it, like with a terminal or something?
bump
bump!
with root explorer go to system/lib/hw and go all the way to the bottom to the last sensors file. its an so file. long press on it and open in text editor. somewhere in the page almost at the bottom you will see where it says ProximitySensor then on one of those line it should say mEnabled. just rename it to mDisabled, then reboot and the proximity sensor is fixed.
qman66 said:
with root explorer go to system/lib/hw and go all the way to the bottom to the last sensors file. its an so file. long press on it and open in text editor. somewhere in the page almost at the bottom you will see where it says ProximitySensor then on one of those line it should say mEnabled. just rename it to mDisabled, then reboot and the proximity sensor is fixed.
Click to expand...
Click to collapse
I know this is an old thread but qman66 you are AWESOME! Was going nuts trying to fix the proximity sensor problem. Ran the commands in terminal emulator that recalibrates the sensor, didn't work for me. Blasted the speaker with compressed air, also didn't work for me. But this method allowed me to disable the proximity sensor while still using an AOSP rom. I will send the phone in for warranty eventually, but I thought I was going to have to use a touchwiz rom until then (touchwiz has the option of disabling the proximity sensor in the call menu).
And I read like 5 or 6 different threads dealing with the Galaxy S4 proximity sensor issue and no one else posted this method before.
kg2128 said:
I know this is an old thread but qman66 you are AWESOME! Was going nuts trying to fix the proximity sensor problem. Ran the commands in terminal emulator that recalibrates the sensor, didn't work for me. Blasted the speaker with compressed air, also didn't work for me. But this method allowed me to disable the proximity sensor while still using an AOSP rom. I will send the phone in for warranty eventually, but I thought I was going to have to use a touchwiz rom until then (touchwiz has the option of disabling the proximity sensor in the call menu).
And I read like 5 or 6 different threads dealing with the Galaxy S4 proximity sensor issue and no one else posted this method before.
Click to expand...
Click to collapse
glad someone found this useful.
While this fixed the call locking problem, it also disables a lot of other hardware sensors. The only one I'd care about is the gyroscope for rotating the camera and watching videos full screen. Any solutions?
sjschoo said:
While this fixed the call locking problem, it also disables a lot of other hardware sensors. The only one I'd care about is the gyroscope for rotating the camera and watching videos full screen. Any solutions?
Click to expand...
Click to collapse
Yeah I noticed that, the best solution is to get the proximity sensor fixed in the end. Then you don't have to disable anything. If your lucky it doesn't even need to be replaced, just cleaned. For me I can live with no rotation, because the screen off during calls is a ridiculous PITA by comparison. Also apps can force landscape mode even with the gyroscope not working. I use force landscape for videos through mx player, and mango reader for manga.
I finally broke down and took the phone apart. There were no warranty stickers to break so assuming you don't mess up royally, it shouldn't effect your resale value. All it took was an eye glass screw driver and a q-tip. Once I was inside I tried the can of air first, but didn't help. Swabbed the back of the glass with the q-tip and that finally provided lasting relief.
i9100 proximity sensor doesn't work
Hi to all!
I have the issue with proximity sensor and didn't manage to find a solution in other similar threads!
The matter is that it is always stay as Released.
In the same time in test screen (*#0*#) there are changing reading for PROXIMITY parameter from 2 up to 240 with no ADC parameter at all. Please look for screenshots. PROXIMITY parameter changes its value when I move my finger in front of the sensor, but as I can understand Android doesn't recognize it because of ADC absence.
Moreover I tried to change proximity sensor for working one (from another phone), but it shows the same as mine (with no ADC readings).
After all I think it is software problem, but I don't know how to solve it. I flashed different firmwares (now it is XWMSE NeatROM v.6.4), but nothing helped.
Please assist! Thanks!
khudko83 said:
Hi to all!
I have the issue with proximity sensor and didn't manage to find a solution in other similar threads!
The matter is that it is always stay as Released.
In the same time in test screen (*#0*#) there are changing reading for PROXIMITY parameter from 2 up to 240 with no ADC parameter at all. Please look for screenshots. PROXIMITY parameter changes its value when I move my finger in front of the sensor, but as I can understand Android doesn't recognize it because of ADC absence.
Moreover I tried to change proximity sensor for working one (from another phone), but it shows the same as mine (with no ADC readings).
After all I think it is software problem, but I don't know how to solve it. I flashed different firmwares (now it is XWMSE NeatROM v.6.4), but nothing helped.
Please assist! Thanks!
Click to expand...
Click to collapse
Changing the rom isn't going to do anything, even factory roms (I've tried it). If a replacement sensor doesn't fix it for you, then it's going to be hard to fix it yourself. All the posts I've seen so far have cleaned the sensor or replaced the sensor and fixed the problem. Otherwise people like me just turn the sensor off.
You were right, proximity software fix didn't help! But how is it possible to work in this (the same wrong) way with changed sensor? Can it be some main board hardware problem? But it doesn't look like this...
Sent from my GT-I9500 using XDA Premium 4 mobile app
Maybe somebody knows how to fix the issue???
Finally fixed
Thanks so much qman66 I have had problems with my proximity sensor on my JFLTEXX pretty much since I got it. Had been using the xposed disable proximity sensor module but xposed doesn't work with CM12. Your simple system tweak has given me use of my phone know call options again
qman66 said:
with root explorer go to system/lib/hw and go all the way to the bottom to the last sensors file. its an so file. long press on it and open in text editor. somewhere in the page almost at the bottom you will see where it says ProximitySensor then on one of those line it should say mEnabled. just rename it to mDisabled, then reboot and the proximity sensor is fixed.
Click to expand...
Click to collapse
Hi, I tied to do this but it says I can't save the changed so file... Can you let me know which root explorer and text editor you are using?
Thanks massively
Not a text file
qman66 said:
with root explorer go to system/lib/hw and go all the way to the bottom to the last sensors file. its an so file. long press on it and open in text editor. somewhere in the page almost at the bottom you will see where it says ProximitySensor then on one of those line it should say mEnabled. just rename it to mDisabled, then reboot and the proximity sensor is fixed.
Click to expand...
Click to collapse
I found sensors.msm8960.so with many references to proximity sensor but it is not a text file!!
Samsung S4 Active w LOS 15.1 (a&Droid 8.1) - how to disable HW sensor(s).
Hi All
Hope some here will help me stay afloat long enough to learn to surf by myself; bit of a noob in this wild ocean here (more of a 'fresh water/indoor pool' kinda dude I guess) - but trying to break out of tis little pond and learn to 'surf'. Anyway, to the point:
1. HW spec
Samsung Galaxy S4 Active
GT - i9295
TWRP 3.3.0-0
Lineage 15.1 20180227 jactivelte
(sometimes with opengapps pico and addonsu15.1 but mostly just LOS and addonsu nothing else)
2. Have the sensors on phone covered up with black electrical tape - all but the notification light are covered and it's gonna stay that way - NOT negotiable!
Obvious Issue: Have the blank screen during phone call problem. Can end calls using power button but I need to use the keypad quite often so need the screen to stay on. How? Ideally want to (SW) disable most if not all hardware sensors - how?
Tried a few fixes but no luck, e.g.:
(a) adding 'the' fix/control many sensors apk no good as not suported under 8.1 (plus want to find out how to do manually myself not use 'hand outs').
(b) edit selected sensor etc ".so" (eg in system hw) files - so far not resulting in the disabled ProximitySensor.
So, I really want to hack this myself at cmd line level, am ok with that (many years IT ops/admin experience in 'fresh water commercial space'). Can mount system using TWRP then adb shell to connect and find and grep for stuff in files but cannot find setttings I need to change to disable sensors for good. Where to look/find more info?
What do I want to achive:
Make calls and have keypad stay on all the time or give me manual option to turn screen on/off with a hw button during call.
How:
I am happy to disable pretty much all sensors (proximity, gyro, compass etc) in system or firmware memory so that I am free from the overlords and really want to be able to use the keypad during calls - and have option to manually turn screen off/on during call would be cool.
Constraint:
Really want to do this from (a) cmd line or (b) edit code/recompile (learning curve) the LOS 15.1 or whatever to disable sensors for good. I will be using this old thing mostly for just call and txt not much else - and cannot be asked to buy an old Nokia handset.
Thanks,
iHAL8999.999... (hi dave...)
I have firmware OF1 for i545 verizon S4 (5.0.1). Freshly re-flashed and reset to factory.
Bootloader is locked but I have ROOT
There is a calibration on my phone that is off for the Gyro. Looking at any app it gives two values for the gyroscope: calibrated and uncalibrated. The uncalibrated values are more accurate than the calibrated values and I would at the minimum like to delete the calibration file wherever it might be.
Here is the problem...
After updating the phone there is no option to calibrate the gyro.
-Motions and gestures in settings does not have the calibrate option
-secret code *#0*# does nothing
-Suggestion of Nova Launcher > activities in widgets shows no "activities" option in widgets
-Terminal does not have a calibration option in the sensors folder like there is in accelerometer
I'm stuck here. Can't find any apps or any general info on how to calibrate the gyro.
Thanks
Bump