Develop Bugs

Compas

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

Galaxy note 3 proximity sensor issue Fix (when making calls)

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.

Fingerprint Hardware Not Available; Camera App Not Responding - troubleshooting insid

Hey Guys, the fingerprint sensor on my Nexus 5x (LG H791) stopped working out of the blue the other day. I bought the phone on eBay about 2 months ago, and the seller told me it had an international warranty. However, this warranty is not supported by LG Canada (so much for being international). FUrthermore, the seller says his stuff shipped from the US, but it actually shipped from Malaysia. Needless to say, I was pretty pissed off.
Anyways, the 5X has been great until the other day. I pulled the phone out of my pocket and tried to unlock it with my fingerprint as I always do. It didn't unlock, didn't vibrate, and didn't do anything. I pressed the power button and tried again. At this point I noticed the dreaded red words across hte bottom that said "Fingerprint Hardware Not Available". After a quick google I see that people have resolved this problem by rebooting the phone - which did I did, but the scanner did not come back. I then cleared the cache, and that did not solve the problem.
I then noticed, that night, that my phone was fully charged whne I went to sleep and when I woke up it was at 20%. Normally, I'll lose 3-5% overnight. I checked what was using my battery and "Phone Idle" had kept my phone awake for 14h!
SO - I've tried removing a bunch of apps, booting in safe mode, playing with the security settings, display timeout, and a bunch of crap - nothing has worked. I have NOT formatted/recovered the phone yet (I'm out at a mining camp and this is the only way I keep in touch with my girl. Also I forgot my USB-C to USB-A cable.)
What do you guys think - did the fingerprint scanner just crap out? I would really like to get it working again, cause I love(d) this phone. I upgraded from a Nexus 4 and I was a big fan of the nexus, until this crappity crap happened.
Anyways, thanks for your help in advance with figuring out these two issues.
B
EDIT - the original title for this post was "[ISSUES] Fingerprint Hardware Not Available - and now Nexus Imprint is missing..." I have since changed the title to reflect both the finger print and the camera trouble shooting, results, and further questions.

Bump - can anyone help???

Guess there isn't anyone here that's knowledgeable enough to help me with this issue..
Well, I tried removing a bunch of apps, to see if something was causing it - it was not. Then my camera stopped working.. Sometimes when I'd open it up my camera would work, and sometimes it would just crash. I've since performed a factory reset on the phone and there is still no option for Nexus imprint. Whenever I try to open the camera the screen goes black, shows the camera icon and then the Camera app just crashes.
I've got a replacement fingerprint sensor which I'm going to install this weekend. I'll keep you guys in the loop, because apparently this is something that no one here can help with.

Got the fingerprint sensor replaced on my phone. When pulling out the old one there was no visible damage. The connection was solid. I installed a new sensor (which I purchased for $16 shipped to my door I'm Canada from esourceparts). After turning the phone on, in my security settings, "Nexus Imprint" appeared. Set up the new fingerprints, and it works flawlessly.
Looks like it was hardware not software.
The camera still doesn't work, battery life has increased remarkably.
Happy again.

bodaciousbob said:
Got the fingerprint sensor replaced on my phone. When pulling out the old one there was no visible damage. The connection was solid. I installed a new sensor (which I purchased for $16 shipped to my door I'm Canada from esourceparts). After turning the phone on, in my security settings, "Nexus Imprint" appeared. Set up the new fingerprints, and it works flawlessly.
Looks like it was hardware not software.
The camera still doesn't work, battery life has increased remarkably.
Happy again.
Click to expand...
Click to collapse
As for the camera fix, have you tried installing factory images?

Exact same issue
I upgraded from a Nexus 4 and I was a big fan of the nexus, until this crappity crap happened.
Click to expand...
Click to collapse
Can't agree with you more (I also upgraded from Nexus 4, and a nexus fan).
I have the exact same issue right now.
It happened to me right after the Nougat upgrade, so I thought it had to do with it, so I tried everything, including downgrade back to Marshmallow, but nothing works.
It's exactly like you wrote, suddenly the fingerprint stopped working, showed this red "hardware" message, then it disappeared completely from the settings, and also the phone started to drain battery twice faster. It's probably has to do with the fingerprint sensor, maybe it's trying to detect it all the time or something, draining the battery.
I'm really frustrated, we're going on a long vacation in 2 weeks and I really need the phone to work well... If I'll order the sensor from ebay right now, it won't get here on time
I think this was my last nexus... (had nexus S, nexus 4, and nexus 5X)
update:
just received OTA update (build NRD90R) which seems to fixed the fingerprint sensor, it works again. hope it will stay this way, don't wanna jinx it.

My fingerprint sensor also seems to have bitten the dust. It sporadically ceased functioning whenever I got it slightly wet, either from sweat when running or if exposed to a little rain. It would always come back after a few hours, however this time it seems to have completely quit. I have done a factory reset and it is still missing. I'm fairly certain I have an issue with the hardware. My phone is under LG's warranty since I bought it from Amazon, so getting the sensor repaired will mean weeks without my phone. It sounds like people are having good luck with replacing the fingerprint sensor themselves. Is this difficult to do? I'd much rather take this route if I can.

I got the "fingerprint hardware not available" message last night out of the blue. Tried a few things to no avail.... Flashed factory image and it works good as new again.
Sent from my Nexus 5X using XDA-Developers mobile app

I went ahead and bought the parts to replace my fingerprint scanner hardware myself. Not 2 hours after I place the order, my fingerprint scanner just randomly starts working again...after 3 weeks. Bizarre. Regardless, I'm planning on holding onto the backup hardware just in case.

doggie13_ said:
As for the camera fix, have you tried install factory images?
Click to expand...
Click to collapse
No I have not.
But that's a good idea. I did a factory reset on the phone and that didn't solve it. After a restart I can open both the rear and front facing cameras without a problem. But after about 3 minutes of the phone being on, some bug happens and I cannot open the camera. I get a black screen and either I can kill the app and continue using the phone, or the phone just restarts. When I get the black screen I cannot switch to the front camera either - the phone just craps out.
I'll try loading the factory images and see if that helps.
So I fixed the problem by taking apart the phone and installing a new fingerprint sensor.
Google Play support, Google Support, and LG Support would not extend service to this phone because it was an international version. Unfortunately, Google support couldnèt do anything other than to tell me to try a hard reset (which I did).
I ordered a new fingerprint sensor from epartsource (Canadian supplier) which cost me $16cad shipped to my door. Taking apart the 5x by following the instructions on ifixit was very painless. It was incredibly easy to replace the sensor as well. Before putting the phone back together we booted the phone up, and went to the security settings - low and behold, nexus imprint was an option again.
The old fingerprint sensor did not appear to have any damage, the clip was firmly in place before we removed it, and the unit looked like it was in good condition.
This has also solved my battery life woes; I can get about 4 days on airplane mode now.
Now, all I need to do is fix the camera (I lost use of the camera about 4 days after the fingerprint sensor crapped out.) I have since ordered a replacement camera from Aliexpress - I'll post up a new thread for that when it comes.
I'm not sure why the fingerprint sensor AND the camera would both stop working at or around the same time. I think that something may have impacted the rear of the phone causing damage to both of them. Very poor if the fingerprint sensor is THAT fragile.
I'm happy to have my phone working near 100% again. I am a very loyal nexus customer, however, that is changing quickly with the lack of service provided by both Google and LG. Google, I hope you're listening. You need to do more to keep your customers.

ariel.levin said:
Can't agree with you more (I also upgraded from Nexus 4, and a nexus fan).
I have the exact same issue right now.
It happened to me right after the Nougat upgrade, so I thought it had to do with it, so I tried everything, including downgrade back to Marshmallow, but nothing works.
It's exactly like you wrote, suddenly the fingerprint stopped working, showed this red "hardware" message, then it disappeared completely from the settings, and also the phone started to drain battery twice faster. It's probably has to do with the fingerprint sensor, maybe it's trying to detect it all the time or something, draining the battery.
I'm really frustrated, we're going on a long vacation in 2 weeks and I really need the phone to work well... If I'll order the sensor from ebay right now, it won't get here on time
I think this was my last nexus... (had nexus S, nexus 4, and nexus 5X)
update:
just received OTA update (build NRD90R) which seems to fixed the fingerprint sensor, it works again. hope it will stay this way, don't wanna jinx it.
Click to expand...
Click to collapse
I got that update too, before I replaced the sensor; it did not fix it.

ggtsu said:
My fingerprint sensor also seems to have bitten the dust. It sporadically ceased functioning whenever I got it slightly wet, either from sweat when running or if exposed to a little rain. It would always come back after a few hours, however this time it seems to have completely quit.
Click to expand...
Click to collapse
The more I thought about it, the more I think it has to do with water. If your finger is slightly wet, DO NOT use your fingerprint sensor. I'm fairly certain it was this that killed mine. Or a slight impact to the back of the phone.
Regardless, I treat my stuff pretty well and I take good care of it. I was at work, however, and I need to spray down things so my hands are constantly wet. I had been using my fingerprint sensor with damp/wet fingers in the few days before it crapped out.

bodaciousbob said:
The more I thought about it, the more I think it has to do with water. If your finger is slightly wet, DO NOT use your fingerprint sensor. I'm fairly certain it was this that killed mine. Or a slight impact to the back of the phone.
Regardless, I treat my stuff pretty well and I take good care of it. I was at work, however, and I need to spray down things so my hands are constantly wet. I had been using my fingerprint sensor with damp/wet fingers in the few days before it crapped out.
Click to expand...
Click to collapse
I like to use my phone with an armband while running and my armband has a "clever" design with an open spot to give you access to the sensor. Unfortunately this means it is in direct contact with my skin and sweat while I run. I got in the habit of sticking a small cloth between the sensor and my skin to keep it dry, but apparently even tiny amounts of moisture on your finger when it's raining seems to be enough to damage it. Anyone know if this is just an issue with the 5X sensor or do other phones also have this problem?

ggtsu said:
I like to use my phone with an armband while running and my armband has a "clever" design with an open spot to give you access to the sensor. Unfortunately this means it is in direct contact with my skin and sweat while I run. I got in the habit of sticking a small cloth between the sensor and my skin to keep it dry, but apparently even tiny amounts of moisture on your finger when it's raining seems to be enough to damage it. Anyone know if this is just an issue with the 5X sensor or do other phones also have this problem?
Click to expand...
Click to collapse
It makes sense... The sensor is probably some sort of heat detector that can discern slight differences in heat on the surface of the sensor. A ridge of your fingerprint would conduct more heat to the sensor than heat that's radiated to the sensor from a fingerprint valley. It probably makes a quick map of the thermal Imprint and matches this to your saved profiles.
Or I'm out to lunch. Lol.
However, I'm pretty sure water killed mine, and the fingerprint sensors are very fragile. I've stopped using mine all together until I have clean hands. This means no using it at work.

Bought a replacement camera module from Aliexpress and finally got around to installing it. With the cover, and the frame off, new camera module installed, I was able to open the camera, use both the front and the back cameras.
However, when I closed it all up and went to use the camera, I get the same errors. Black screen, cannot connect to camera, and then it crashes/restarts the phone.
Definitely not hardware!

doggie13_ said:
As for the camera fix, have you tried installing factory images?
Click to expand...
Click to collapse
I will be trying this later tonight. Currently running Android Beta 7.1.1. I will install 6.0.1 MHC19Q, and going through the list until I find an OS that's got a stable camera.

bodaciousbob said:
I will be trying this later tonight. Currently running Android Beta 7.1.1. I will install 6.0.1 MHC19Q, and going through the list until I find an OS that's got a stable camera.
Click to expand...
Click to collapse
I downgraded from N-Preview 5 (? v.7.1.1) to android 7. Camera would only work for a few moments after immediately rebooting the phone.
Sideloaded 6.0.1 using fastboot and unlocked bootloader - the first time I ran the new install, the camera app crashed instantly. Rebooted, and now it's been working fine.................. Let's see how long it lasts! Will update tomorrow.

So. I followed the instructions on Google's page (https://developers.google.com/android/nexus/images) and I sideloaded build MMB29V. And the camera NOW WORKS! I left the phone powered on over night and the camera will start anytime I need it to. I installed all of the available OTA updates, bringing me up to NBD90W, and my camera is STILL launching flawlessly!
In other words - a fresh factory install fixed the camera issues!+
Edit: Just sideloaded in the latest version of 7.0.0 (NBD90W, Oct 2016) and the camera is stable. The stock android camera is version 4.1.006.125161292. I will keep you updated as it progresses. The actual camera module in my phone is the one that I ordered from Aliexpress ( https://www.aliexpress.com/item/Ori...era-Module-Replacement-Parts/32657390368.html) The black housing on the camera module was a bit different than the OEM one I pulled out. I didn't check any serial numbers to verify; so I don't know if the one from Ali is actually OEM.

bodaciousbob said:
I installed a new sensor (which I purchased for $16 shipped to my door I'm Canada from esourceparts)
Click to expand...
Click to collapse
That's encouraging! Mine died overnight, after being intermittent yesterday. Went onto eBay and ordered a replacement from Asia for about CAD$9 delivered, should arrive around Christmas.
esourceparts (I'm also in Canada) only had the black sensors -- mine is white, and I like white.

bodaciousbob said:
So. I followed the instructions on Google's page (https://developers.google.com/android/nexus/images) and I sideloaded build MMB29V. And the camera NOW WORKS! I left the phone powered on over night and the camera will start anytime I need it to. I installed all of the available OTA updates, bringing me up to NBD90W, and my camera is STILL launching flawlessly!
In other words - a fresh factory install fixed the camera issues!+
Edit: Just sideloaded in the latest version of 7.0.0 (NBD90W, Oct 2016) and the camera is stable. The stock android camera is version 4.1.006.125161292. I will keep you updated as it progresses. The actual camera module in my phone is the one that I ordered from Aliexpress ( https://www.aliexpress.com/item/Ori...era-Module-Replacement-Parts/32657390368.html) The black housing on the camera module was a bit different than the OEM one I pulled out. I didn't check any serial numbers to verify; so I don't know if the one from Ali is actually OEM.
Click to expand...
Click to collapse
I have the same camera problem, can you tell what exactly you did to fix it?
Sent from my Nexus 5X using XDA-Developers mobile app

Knock On Not working properly

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!

Samsung Health update broken HRM?

As title, has anybody else noticed crazy high heart rates on watch/phone since the recent update?

You have to relax a bit and relief stress from you life I guess. [emoji23]
(jokes aside, no weird behaviour from hrm after update, seems normal to me)
Sent from my CLT-L29 using Tapatalk

Yes. I have to reset the watch at times.

Thanks for that. By reset do you mean just switch off or full scrub and restore from back up?
If the latter did it restore everything ok?

Just power it off then back on. Mine does this every now and then. But what's more common for me is a HR that drops to 50 or so like mid day, not sleeping. And I've found it to usually be oily residue on the sensor or just flat out stuck on dead skin buildup making the sensor foggy, so I wipe it off and put it on again and it's fine for another week.

Thanks, I'll give that a try.