Related
Now i love my desire... Its fantastic but it isnt without some issues...
One ive noticed that could be a problem esp when your working with reality overlay apps...
The compass doesn’t seem to work that well...
Its slow to respond to movement and even when it does move its horridly inaccurate. north seems to have a room for error of 60-90 degrees.
Has anyone else noticed this? Is it the same for most digital compasses? or do i have a faulty module?
Hi Nutsy,
I've also noticed these issues with the compass in the Desire. I've worked with magnetic compass chips before and I think it's all to blame on the way these compasses work:
To sense the earth's magnetic field they use a two- or three axis magnetometer. Although it's a very accurate way to sense the earth's weak magnetic field, it's also very sensitive to any other magnetic field. That means that the presence of ferromagnetic materials (like iron) or electrical currents in the vicinity might really screw up your compass reading.
So electrical wires, iron piping, laundry machines (almost anything that you would find indoors that runs on electricity or contains iron), will interfere with your compass.
a good alternative would be to use a gyroscopic compass like they do on submarines, but I don't think these fairly expensive devices aren't used in mobile equipment yet. So the only thing to do is to stay away from anything that might interfere.
The slow response to movement might be caused by internal filtering. These analog sensors produce quite an amount of measurement noise. In order to cancel this, they probably use some sort of filtering algorithm like this one:
step 1 -> Take a new sensor reading.
step 2 -> Add it to a buffer that contains the last 25 readings.
step 3 -> Calculate the mean value of all measurements in this buffer. This will be the compass heading that is sent to Android OS or your application.
step 4 -> Repeat this cycle every 25 milliseconds.
Hope this answers your questions. Of course if you compass readings never make any sense under any circumstances, the thing might just be broken...
Friendly regards,
Joost
Ps.
There's an App in the market called "Metal detector" that actually uses the interference "problem" with the compass to detect ferromagnetic metals.
Wow Thanks for the really detailed reply...
Im glad its not just me then... Didnt really want to RMA it over a dodgy compass unit.
And thanks for letting me know about that app... sounds usful... I guess it could be used to detect wireing in plaster as well?
You're welcome.
In theory you could use it to detect metal or wires in a plaster wall. I've just tried it, and it works quite well. On the other hand, I really don't want to risk electrocution by trusting a telephone to find electrical wires...
My compass is shocking. Actually points closer to South whenever I open Compass or a programme which uses the compass like G-sky. I have to calibrate it every single time.
Thing that annoys me, is if I calibrate, then exit the programme and immediately re-open the programme, it doesn't remember the calibration, it reverts to pointing in a ridiculous direction.
I want to hit it with my fist.
Addtitionally, think it's broken?
jimmymagix said:
My compass is shocking. Actually points closer to South whenever I open Compass or a programme which uses the compass like G-sky. I have to calibrate it every single time.
Thing that annoys me, is if I calibrate, then exit the programme and immediately re-open the programme, it doesn't remember the calibration, it reverts to pointing in a ridiculous direction.
I want to hit it with my fist.
Addtitionally, think it's broken?
Click to expand...
Click to collapse
Yesterday I found out the same thing... Sometimes I cant even get it working after calibration. I was beginning to think that this happened because I dropped it once pretty hard. What should we do next? Can this be solved by replacement with warranty or something?
Smauglys said:
Yesterday I found out the same thing... Sometimes I cant even get it working after calibration. I was beginning to think that this happened because I dropped it once pretty hard. What should we do next? Can this be solved by replacement with warranty or something?
Click to expand...
Click to collapse
Make sure your phone isn't in a case which uses magnets to keep it closed, as they affect the compass. If you're affected, take your phone out of the case and try again. Also, try out in the open, away from structures which may contain a lot of ferrous metal.
In my case the problem is due to powered-on wi-fi module. Turning off wifi, compass works fine. Could Anyone elserepeat my experience?
poldie said:
Make sure your phone isn't in a case which uses magnets to keep it closed, as they affect the compass. If you're affected, take your phone out of the case and try again. Also, try out in the open, away from structures which may contain a lot of ferrous metal.
Click to expand...
Click to collapse
Yes I know that. Tried out doors, and wheres no metal... When I had the G1, the compass worked normally.
In my case the problem is due to powered-on wi-fi module. Turning off wifi, compass works fine. Could Anyone elserepeat my experience?
Click to expand...
Click to collapse
Just tried what you said. It did not help for me. I turned it of completely.
Smauglys said:
Yes I know that. Tried out doors, and wheres no metal... When I had the G1, the compass worked normally.
Just tried what you said. It did not help for me. I turned it of completely.
Click to expand...
Click to collapse
Just went outside to test it again. And I think I found how to get it working. If i launch the compass application, and try to turn the phone in the flat position (on its back), then the arrow moves in random directions. But if i lift the phone that it is facing straight to my face, and then turn left and right a few times, like a steering wheel, the compass "calibrates" as I can see. And then when I lay it down again flat, it starts to work normally. Can anyone try this, if you understood my instructions?
A more accurate way of calibrating the compass is by rotating the phone twice around each axis, ideally you should do this away from anything metallic or any interfering magnetic fields preferably outside.
Er......
Where is the compass?
I dont seem to have a compass! In my list of apps there just isnt one called compass...
The Analogue Compass app is very buggy for me so I use the Compass app -> http://www.androlib.com/android.application.com-apksoftware-compass-qAC.aspx
When taking readings, I;
Always have to recalibrate on startup as far too many objects cause large interferences within the sensor making it go astray, even the charging cable causes it to go berzerk. The known working routine is to calibrate by fast twisting and turning the phone [I do it after running the built-in figure 8 calibration routine]
Keep it mid-upper body height with no metals nearby (jewellery/belt/metallic objects minimum >5ft away), holding still and level across the x-axis
Point the upper-end of the phone in the direction I want the bearing of (this depends on the type you use though, I use the digital type)
I spin the phone around and then retake 2 more readings for a total of 3 readings - averaging them out for a final mean reading
I only have 2 directions calibrated through professional consultation when this room extension was built a few years back and know the rough directions all sides this property faces, but in particular, I'm 100% sure of the exact degree reading one wall faces. This app using the built-in compass sensor reads that bearing spot on everytime after calibration (fluctuation is 1-2 degree max).
Some friends in a Lithuanian Android forum, suggested to do this, like it is shown in the video. Works perfectly every time. And I thought that something was wrong, because I never had to do anything like this on my G1.
Youtube video ID, because I cant add link because of spam protection http://www.youtube.com/watch?v=sP3d00Hr14o
Hello!
A month ago I had an issue when all of a sudden, when I was on a phone call and separated my Note 3 from my ear (to check the time as an ex,), the screen would stay black and the proximity sensor wouldn't work. It was very annoying (to me anyways) as I believe in having a phone working 100%. Honestly...I thought it was ROM and/or kernel related, but it's not. Doing some research here in XDA, I found several members of this community (Sprint Note 3 to be specific) experiencing the same issue. Apparently, it's dust affecting the proximity sensor making it unresponsive.
Long story short, one member said that he fixed his Note 3 by blowing air into the earpiece where the sensor is located. I thought the worse about the guy (lol) thinking it was a crazy idea...BUT, I said, "WTH...let me try it" and sure enough, it FREAKING worked!!! My Note 3 was working properly again!
That very same day, on Google +, I came across this article http://www.infotales.com/samsung-galaxy-note-3-proximity-sensor-issue-fix where the author "YASIR MIRZA" wrote an AWESOME article with this particular issue. He goes real deep into the subject and has 2 different methods more in depth about fixing the issue.
I will NOT maintain this thread since I don't have time. I'm only posting this here because I think it's the right place "Q&A", plus maybe if someone has the issue (like I had), by doing SEARCH (like I did), this thread will pop up and maybe help!!!
READING IT'S FUNDAMENTAL... SO READ FROM THE LINK I'VE PROVIDED WHERE IT HAS MUCH MUCH MUCH USEFUL INFORMATION!
HIT THAT "THANK YOU" BUTTON IF I HELPED OR YOU FIND THIS USEFUL!!! IT DOESN'T BITE...lol
That is a really good and thorough article. While I have not had any proximity sensor issues (yet), people who have will certainly appreciate the how-to. It is for a rooted device, though.
This is all great info, but it doesn't address the core issue which I gather from reading, is dust obscuring the sensor. I'm assuming this will recalibrate the sensor partly covered by dust, but If the dust got on the sensor once, there is pretty good chance it will get there again and change calibration? So how to stop it from getting there in the first place would be my concern, especially because so far my sensor works fine. Maybe solution should be to seal headphone jack, (if that's the culprit) which personally I rarely use, with some rubber insert, easy to remove if needed? And there is another opening (microphone?) right next to it, could that be a way inside as well?
As my phone's not rooted, nor have any compressed air handy, I opted to physically clean the sensor.
It's pretty simple and straightforward (the teardown videos are on youtube). Basically, you just unscrew the back casing and remove the sensor. Then either wipe the sensor window or use a tape to stick up the dust.
Before cleaning my readings were 105 and not working. After cleaning it went down to 40 and has been working ever since. Blowing the dust may simply dislodge it moved it around, having a chance of it finding its way back whereas cleaning it removes it altogether until some new dust finds its way back onto the window.
mwerkz said:
As my phone's not rooted, nor have any compressed air handy, I opted to physically clean the sensor.
It's pretty simple and straightforward (the teardown videos are on youtube). Basically, you just unscrew the back casing and remove the sensor. Then either wipe the sensor window or use a tape to stick up the dust.
Before cleaning my readings were 105 and not working. After cleaning it went down to 40 and has been working ever since. Blowing the dust may simply dislodge it moved it around, having a chance of it finding its way back whereas cleaning it removes it altogether until some new dust finds its way back onto the window.
Click to expand...
Click to collapse
I just fixed my proximity sensor problem by doing a tear down and cleaning the dust out from the screen in front of the sensor also. Fairly easy to do.
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!
Hands-free mode
Hi everyone, just disabled the hands-free mode (steering wheel symbol - from the upper curtain) and your problem is solved.
Cheers.
God bless. :laugh:
The link in the OP does not work; am I missing anything - like a period or some other punctuation or some word(s)?
No Gyroscope, No Proximity Sensor, No Temp...
I have a SM-N900 Showing no values for any sensor, I have tried unplugging and replugging proximity sensor with no sucess, also tried restoring via Odin Stock firmware, no sucess.
The Phone was apparently working fine, without root on stock lollipop, and after resetting the device for selling it, it stopped working.
I can't even rotate the screen...
I also tried the calibration method with no sucess...any suggestions?
Same here!!
It is so frustrating. I've restored to stock, with Odin. Had 3 different roms and have never had my sensors working. I've tried
libgnustl_shared-1.so fix for rotation. It didn't work.
Does anyone have any ideas? I don't have water damage.
I solved my problem by installing google phone app and selecting this phone app as system default from app permissions menu.
I was having this problem before a little and I would just do a simple reboot. However, this morning my clumsy niece dropped my tablet on the floor Now the rotation is not working at all.
I've seen videos which lead me to believe that the issue is due to a loose ME571k cable. I have tried fastening it. I inadvertently took it out and reconnected it. I've tried to fasten it the best I can. The touch screen works. However, orientation is dead.
There was a program mentioned called "Test My Android" and none of the sensor calibrators show any sign of life.
This is driving me crazy. I don't know what to do. Maybe it is loose and I just have to keep on messing with it but it's stressful.
Any advice?
ev1lchris said:
Maybe it is loose...
Click to expand...
Click to collapse
Yes it is - for sure. The 'rotation' sensor is a tiny chip which is unlikely to be damaged by a drop.
re-seat the cable on both ends
spray the contacts of the cable with Electronic Cleaner if possible
apply a layer of thick tape over the cable's motherboard connector, so the back cover will deliver extra pressure on it
Let us know...
Hello, I followed the steps of next video and my screen rotation has fixed
https://youtu.be/cOnccu6Nbl0
Hope it helps you!
Sent from my Nexus 7 using Tapatalk
It seems no matter how many times or how snugly I set the cable in that the screen rotation still does not work.
I'm using an app for rotation now. It works but it drives me crazy.
Hi, two weeks ago I got VR cardboard style glasses and tested with my Lenovo Vibe P1c58. At first it was very very shaky, I tried different ways of calibration of gyroscopes and M sensor (####1111#, compass essentials,...) like 1M times with very little success.
The weirdest thing is that if I place the top of my phone on the side the cardboard magnet is, the VR rotation freezes completely. But even worse, this wasn't that bad one week ago, when even with magnet close, the VR rotated (just a bit less than without magnet). When I slide the magnet button, the camera rotates.
I tried updating to Android 6.0.1 and rooted the device (with a manual in this forums) hoping it would work better, but no luck, still too shaky to use it without getting dizzy :/
With this Android version Xposed does not let me install it so I cannot test with the module found in the forums (median filter for sensors).
Any ideas? Cause I don't really know if this problem has a fix or the sensors are too bad to do something and I should stop trying to get results...
Oh, almost forgot, using an app to see the measurements for sensors I realized that after taking the magnet close to the phone the values got higher (from 40 to 200) and then stayed there, I assume the sensor is getting magnetized and then with time (long I think) is going back to normal values.
By the way, I just knew today about LineageOS, didn't have time to investigate enough, in case it's available, would fix the problems with sensors?
Best regards and thanks in advance.
Hi, everyone. So I have an LG G4 for more than a year now and I am very pleased with its performance. I did have an issue with sometimes the audio is stuck after a call but I think it more has to do with bad reception as I noticed so its rare this days. However, lately something happened with the knock on feature which I cannot figure out at all. Sometimes it just doesn't work. I tap and nothing happens. The power on button is working perfectly but the knock on is unresponsive. I fiddled with the proximity sensor but it's not it. Sometimes it just stops working for 5-6 times and then it works and the again it doesn't. There is no pattern. When it's powering on the feature works with no hiccups but after that it's like the cpu forgets to monitor the process. I don't know. I have tried calibration and it works with no problem for a few minutes and then it goes back again to this stutter. Does anyone have any ideas about this? I am thinking factory reset but the hassle would be pointless if the problem persists and I am in no mood to install all those apps I have from the beginning for no reason. Any hep will be really appreciated. Thanks in advance.
I am experiencing the same issue but mine Knock on is a bit delaying.. for an example, I double tap on the screen and it gives response in 3-4 mins or not... I am suspecting from screen protector which has been mounted for almost a year, it could be corrupted(scratch) Give a try on removing the screen protector(if you have any)
It's a hardware problem. Many threads online about it
Sent from my LG-H811 using Tapatalk
Nailen said:
Hi, everyone. So I have an LG G4 for more than a year now and I am very pleased with its performance. I did have an issue with sometimes the audio is stuck after a call but I think it more has to do with bad reception as I noticed so its rare this days. However, lately something happened with the knock on feature which I cannot figure out at all. Sometimes it just doesn't work. I tap and nothing happens. The power on button is working perfectly but the knock on is unresponsive. I fiddled with the proximity sensor but it's not it. Sometimes it just stops working for 5-6 times and then it works and the again it doesn't. There is no pattern. When it's powering on the feature works with no hiccups but after that it's like the cpu forgets to monitor the process. I don't know. I have tried calibration and it works with no problem for a few minutes and then it goes back again to this stutter. Does anyone have any ideas about this? I am thinking factory reset but the hassle would be pointless if the problem persists and I am in no mood to install all those apps I have from the beginning for no reason. Any hep will be really appreciated. Thanks in advance.
Click to expand...
Click to collapse
Is your case or temp glass protect over prox sensor. That can affect it bad. Also scratches on glass over prox sensor. If not. Then more than likely hardware related.
No the screen protector does not cover the prox sensor. It's cut out as it should be. I am starting to think it's a hardware problem. The thing is why now?!
Nailen said:
No the screen protector does not cover the prox sensor. It's cut out as it should be. I am starting to think it's a hardware problem. The thing is why now?!
Click to expand...
Click to collapse
They are mostly sensors just like on a car. Sometimes it's just there time. Electrical components fail all the time. Are u rooted. Modified anything recently?
TheMadScientist420 said:
They are mostly sensors just like on a car. Sometimes it's just there time. Electrical components fail all the time. Are u rooted. Modified anything recently?
Click to expand...
Click to collapse
No. I haven't touched it at all yet. I am pretty satisfied with the performance so I left it alone. The only thing worth mentioning is that I overheated taking a lot of pictures during an event. Maybe this did a number on it!
I have been discussing the issue with a technican today. It is a hardware issue, you cannot fix it. Apparently, the proximity sensor dies after ~2 years - at least somewhat. Why somewhat?
Check this out: You can check the status of your sensor using MINIOS, type *#546368#*815# (n.b. - swap 815 for your model number).
Now click device test - MT - ok - Individual Item - Sensor test - WAIT!
The proximity sensor will run a test and likely come up with a figure between 60~90. The actual value should be 220+.
Meaning: Your phone thinks it´s ~6-9 cm away from your face, that is not enough to trigger knock-on but it´s far enough to be triggered using the backside button.
My knock on doesn't work, but knock off does. Not a major issue, just annoying!