There are noticeable problems reported with the P9000 GPS. Could it be, they’re related to an issue with the magnetic sensor (internal compass)?
to check if the compass is working good or not : Start the MTK engineering mode with the code: *#*#3646633#*#*, Go to Hardware Testing->Sensor->MSensor->Msensor Current Data.
If you see the message “MSENSOR DATA IS NOT GOOD” there’s a problem with the compass.
The original Elephone flip case seems to affect the msensor.
By removing the case, and calibrating the compass, status changed to "MSENSOR DATA IS GOOD". As soon as the flip case touched the screen, the status changed back to "MSENSOR DATA IS NOT GOOD"
Compass calibration does make the compass work for a while, but it gets disoriented very easy again it seems.
Does anybody have a solution to fix the magnetic sensor / compass?
I do not use flip case but anyway data IS not good is what i get
yeah I dont use the cover now anymore, as I believe from my experience it does affect the status of the compass (and the GPS from my experience)
My data is good now and has been constant since I used MTK engineering to calibrating compass and my reading is accuracy 3.0 DATA IS GOOD - but initially i did have to go outside to get that result as indoors at that time it just was showing as Data is not good. Now my Data shows as Good all the time.
I have to calibrate every week cause it always stop working
Related
I have my SGS2 since two weeks and very pleased with it. All worked fine, also the compass or magnetic sensor.
I tried some custom ROMs but now use the original KE2 again. Since a couple of day I noticed that the magnetic compass does not work anymore. No movement at all. Also checked it with other apps (Google Skymap etc) but no compass.
I checked the sensor with code *#0*# and then select the sonsor tests. It shows MAGNETIC Sensor "Need for calibration" and the needle is stuck and indicates 0 degrees.
I have been trying to callibrate in many ways described on the net but without luck. Does anybody have an idea? or is the Magnetic sensor bad/damaged and should I send the SGS2 back?
Search works .
http://forum.xda-developers.com/search.php?searchid=74782950
jje
Mine is only a few degrees out. Using Stock KE7 XEU Rom.
Not too fussed tbh.
Magnetic sensor
Well, I read all what has been written on the magnetic sensor or compass on XDA developers and other forums. Learned a lot but nothing helped.
I would like to know a way to check if the sensor is bad.
I downloaded the compass app and checked my sensor.
I tried the program "Sensor Test / Plot" to check the sensors. No values at Magnetic field, Orientation, Gravity Sensor and Rotation Vector Sensor. It just says "Waiting" as the program probably does not receive any data.
Until now I beleive it is a sensor problem and not calibration. It could be a problem in the firmware as it occurred after flashing some ROMs. I tried all origianal Samsung ROMs again but without result, the compass stays stuck and phone doesn't know it's orientation.
erikcornelisse said:
I tried the program "Sensor Test / Plot" to check the sensors. No values at Magnetic field, Orientation, Gravity Sensor and Rotation Vector Sensor. It just says "Waiting" as the program probably does not receive any data.
Until now I beleive it is a sensor problem and not calibration. It could be a problem in the firmware as it occurred after flashing some ROMs. I tried all origianal Samsung ROMs again but without result, the compass stays stuck and phone doesn't know it's orientation.
Click to expand...
Click to collapse
Just downloaded the same app and all ok here.
I don't know what happened today but suddenly the magnetic sensor came alife. The test program is now giving readings and senses magnetic influences. Also the compas is showing some movement but is pointing always wrong. North is always down (towards me) and south always up (so compass indicating 180 degr). Rolling the phone causes the heading to change.
I tried calibrating the compass using several described methods and compass programs but without luck. I get tactile feedback of good calibration after figure 8 waving (using a standard compass program). When I start the app it notes that it senses an abnormal magnetic field and needs calibration.
I'm happy that the magnetic sensor seems to work again but I can't get it calibrated.
Problem solves, it was a bad magnetic sensor this time. The phone is under repair and I will get a new board inside. Hopefully I will have it back next week.
Problem indeed solved. Got the phone back with a new magnetic sensor
Sent from my GT-I9100 using XDA Premium App
Dial *#0*#.. select sensor... then hold ur device and move it in air so that it makes an 8... do it a couple of time... it will solve your problem...
The screen won't turn when I turn the device on it's side and it won't look in the right part of the sky on google sky map.
Did the update break the sensors?
They were broken already, according to some reports. I hope the next update fixes them--it's really annoying! I thought mine were OK at one point, but, alas, they're not.
hallo everybody
i've bought a BV6000 (firm ver 20160713 chip MT6755 (Helio P10)) but the proximity sensor is very weak, i've asked on official forum for calibrating\change threshold, but no one have published my question.
now my idea:
on engineering mode i've found ps calibrating tool but nothing happens after calibration and reboot; the default threshold is set to 40 (less than 1cm) and if i could set to 5 or less the range arrive to about 3 cm.
is some days that i try all solutions founded on the web but no one works...
now someone have some skills in calibrating the sensonsor manually? i've also tried with DHD Proximity Recalibrator but give me a kernel error.
maybe edit some files in /sys/devices/als/subsystem/drivers/als_ps is the solution?
any other idea?
thank you!!!
xposed and the module: http://repo.xposed.info/module/com.mrchandler.disableprox
I have an MTK and it kept hanging up when I brought the phone close to my face, so I had to disable it completely.
yeah i've tried this module but is a bit too invasive and need a tasker profile to turn off screen on call, i would remap the threshold (if is possible!)
/sys/devices/als/subsystem/drivers/als_ps there are many files:
a "config" file with
(3 200 0 0 50)
a "status" file with
CUST: 1, (-1 0)
REGS: DF C1 00 06 00
MISC: 0 0
what makes me angry is the farest PS sensibility from engineering mode! (hardware testing>sensor>light/proximity> PS calibration) if only is possible to manually reduce threshold!!
engineering mode ps calibration...
UP! i attach two photos of the engineering mode that show the lower threshold.. but after calibration nothing happens...
I put 4 times complete analysis of proximity sensor issue on Blackview forum. Every time, they delete my post.
None of the calibration would help.
The only solution is to replace one rubber part from phone. More details here:
thank you
at now i have do a tasker scene that block upper buttons and an "immersive mode" shell during call (show up when call+phone app is on screen and hide if not).
is a patchy solution but it works
maybe if i have some other hardware problem i'll try to open the phone
bye!
Could you upload a video of your solution? How did you reach the rubber part?
Thank you!
I could not upload video, because I did not recorded the process, but I will try to describe this process.
Video comparing working BV6000 and broken BV6000 proximity sensors:
https://www.youtube.com/watch?v=s8NYcs-Yo5E
Go to service mode *#9646633* and select
Hardware-->Sensor-->Light/Priximity Sensor-->PS Calibration
If your BV6000 acts like the right yellow model, then you are affected with this issue.
Root cause:
Proximity sensor is good. Rubber part covering sensor is really poor quality and it has a gap just above sensor causing light leaks.
PS reading 0-80 are considered as "far". Phone cannot get proximity readings >100 which are considered as "near", so the phone does not dim the screen at all. This is causing a lot of unwanted touch screens while making a call. If the proximity readings were possible in full range 0-255, then the threshold settings 40-100 would be perfect. This issue cannot be fixed by any calibration.
On my working, green BV6000, this rubber part has a bit different shape and it is made with much softer rubber. The edge which is covering sensor is also much tighter than on the yellow one.
Workaround:
Disassemble the phone, like on video here:
https://www.youtube.com/watch?v=9yLEemeXFnY
You do not need to disassemble the whole phone. Just get to the part, when you can detach main board.
Then turn upside down this rubber part covering proximity sensor. It is not meant to be mounted this way, but it will fit. Basically the part which was close to the screen should go close to sensor. This will make gap between rubber and PS sensor smaller and there will be just tiny light leak. It will not make full proximity range 0-255, but it will improve a lot.
On my phone proximity range expanded from 0-80 to 0-200 after this mod. Phone will dim the screen while making a call, if you head is 1cm above sensor. On working phone 0-255 it dims screen in 2-3cm range.
The only 100% solution:
New working rubber part to be sent to all affected users.
Shame on Blackview, that they not only deleting my posts about this issue on their forum, but also reporting my posts, when I put this analysis somewhere on well known Android forums. This is like they want to cover a problem and not resolve it like they did with faulty OTG boards.
thanks for the brilliant hardware workaround, but if i want to change the values showed in this app
i've seen many phones with different resolution\max range (higher than 1cm!)
how i can edit this values without MTK engineer tool (tried but dont do nothing for this issue)?
thanks to all
PS. BV6000 is a good phone for the price, but this issue is really annoing!
PPS. BV6000 have adups fota search online and be paranoized!
I have tried it by placing the rubber above the sensor both ways but it still doesn't work. Whenever I make a call the screen remains responsive and many apps open up or settings mess up every time. There is no end to it.
Please help. I'm really annoyed with this issue.
Sent from my BV6000 using XDA Free mobile app
Hi all,
First post here! So I replaced the screen on my honor 10 lite the other day, as well as the charging/headphone jack pcb and battery - all working fine aside from now none of the sensors work. So accelerometer, gyro, screen brightness (auto option no longer there in phone brightness settings) and proximity are not working. I know underneath the main motherboard there's a 'sensor board' small pcb - does this handle the function of all the sensors? A new board looks inexpensive enough - i don't see how I could have possibly damaged the board but if replacing it will fix it that would be easy, just don't want to spend more money on repairing this phone if I don't need to.
Appreciate if anyone with any insight could help! Thanks!
The previous owner has dropped my XT2000 at some point and the external (quickview) display is not turning on upon fold. The display itself is working fine, since it's active when turning the phone on, its just not being "told" by the phone to come alive. Upon further inspection, the phone doesn't even go to sleep when folded.
I assume there is only some sensor that's broken. I've tested lighting and proximity sensors on the inner foldable display side and they work fine.
If you know, can you please tell me which sensor might be in charge of turning on the external display on fold, or the sleep function?
P.S. The damage from the fall is actually minimal, just a small crack towards the bottom of the external display. The damage may not even be connected with this issue.