Database Info

Compass issues after upgrading to Lollipop

Hey guys,
New smartphone user here. I've had Nexus 5 for a few months now.
Lollipop is really well made and the new visuals are great. Everything seems to be working well so far, except for my compass. It does not work either in my Compass app or in Google Maps. I've seen a few threads where people lost some of their sensors, so I downloaded Sensor Box to see what it would find.
The magnetic sensor works properly, but there isn't a "compass" sensor in it. Are they different or is the compass position determined using the magnetic sensor? The GPS Essentials compass does work, but it feels very slow and it's all over the place.
Additionally, when I start my Compass app, it does not activate Location like GPS Essentials would, although, it fetches my current address properly on top of the compass itself. (see attachment)
Could it be just that the compass works in a different way in Lollipop and apps have to be updated for it? I'm completely lost. Any help would be appreciated, guys.
Cheers,

I am experiencing the same issue.

I'm also having this issue, only app I did get it to work with was Compass 360. But I really only would need it for Google Maps, so this is still very annoying.
Did anyone come up with a solution, or at least an explanation yet?
Or does anyone know where to file a bug report about such an issue?

Are you sure the APIs just didn't change with Lollipop? If one app works and not another, it may not be a Lollipop bug.

Kompass is dead on for me, no issues whatsoever. Try moving the phone in a horizontal figure 8 to calibrate the kompass and watch for electrical/magnetic interferences.

Gyroscope not working

Hi, the gyroscope of my zenfone 4 max is not working. Apps such as sensorbox detects a "software gyroscope" sensor in the device, but don't get any data from it.
Anyone else having the same problem? Any ideas to fix this? I'm hoping it's not a hardware problem.
Many thanks.

Sorry but I'm a bit naive with the gyroscope test. How should i know of it is working or not? I tried testing it and it just keeps reading. There is no result showing. So either I click pass or fail button.
Does this test has something to do with the autorotate? Because I'm having sensitivity issues with autorotation. It wasn't on but when I play videos and tilt them, it activates.

Huawei Mate 9 Fingerprint sensor - Android 8 Oreo

This thread is created to find a fix to the Huawei Mate 9 fingerprint sensitivity (or lack there of) sensor issue, an issue that also plagues the Google Pixel phones.
Since upgrading to Android 8 I have found the registering a fingerprint with the phone is next to impossible. The sensitivity of the sensor has been cut down from Android 7.x. I have left messages to @HuaweiUSA in a DM to them and in the general public areas of Twitter. I have also posted this to other social venues.
Now, without resorting to rooting and changing a kernel file, I am asking others what can be done to fix this. Before you respond, please note:
1. Yes I cleaned the sensor
2. Yes my fingers are clean.
3. Yes I actually have fingerprints.
4. This thread is to see who else has this problem and to provide fixes/workarounds for those with the problem.
I do note that the fingerprint sensor does work somewhat well after to register your fingerprint. It is only the enrollment of a fingerprint that is the hardest.
If anyone has fixes, please note them here. Many thanks.

UPDATE: Huawei's official answer to the fingerprint sensor problem is to perform a factory reset after you upgraded your phone to Android 8.
Another issue that will affect fingerprint resolution: users REBRANDING their phone.
Huawei has specific firmware to specific brandings. So if you changed your C185 or C900 to C567 (or any other rebranding), you need to change back and then try the upgrade, reboot, factory reset method to fix things. Tech support said this would solve a number of issues beyond just fingerprint issues. Including call quality issues, networking, etc.

My wife updated her Mate 9 to Oreo using OTA, she received the 363 (C432) version directly.
After the update she lost her SD card, ringtones etc...
After a factory reset she struggled to get her fingerprints recognised, as if the phone could not "read" her finger. I did at the end but it was clear the sensor lost its sensitivity...When I tried to store my fingerprint in her phone it worked a lot better but still more difficult then on my Mate 9.
Her phone is an original German phone and not a rebranded model and the factory reset did not solve the issue...
So your not the only one facing this issue.

i use my m9 with OREO (b361) without problems so far! I have no recognition delays more than on my Honor 7 or my LG G5!
i did a factory reset after upgrading and have registered two fingers twice! This is a little bit tricky because often i got the notification that my finger was known by system. But it is possible to register every finger twice if you are a little bit patient.
Please try different finger positions too.

We tried different positions...I stated that compared to my mate 9 running on Oreo the mate 9 from my wife - also running on Oreo has a fingerprint reader who became less sensitive after the update. We have 2 mate 9's so we can compare both of them...

Our both mate 9 too.
Gesendet von meinem MHA-L29 mit Tapatalk

How do I downgrade from android 8 (oero) to android 7 (nougat) ? I have serious problems with the fingerprint sensor after the upgrade.
Thanks.

uja93 said:
How do I downgrade from android 8 (oero) to android 7 (nougat) ? I have serious problems with the fingerprint sensor after the upgrade.
Thanks.
Click to expand...
Click to collapse
Depending on your model, connect your phone to your PC annd open hi suite (if it doesn't automatically), click on update and if your model version is supported, you'll have an option to go back to an earlier build.

Couple things I find that works. About once a month (more if you use your phone more), I will take an alcohol wipe, and clean off the fingerprint sensor.
Next, I have found that once in a while, my index finger on my left hand is REALLY hard to use, but the index finger on my right hand is very fluid and fast. I simply go into the finger print settings, delete the one that isn't working well, recalibrate it and everything is good. Only had to do that once.

I find the sensor pretty fast, even the smallest portion of the finger seems to be registered and the phone opens, hundreds time per day.
BUUUUT, when trying to answer I call I have to rub my whole finger several seconds until it actually answers, I end up with a ringing phone on my ear waiting for it to recognize me.

I had the same problem after updating. Had to reset from factory and fingerprint management was impossible. It would vibrate after every try then fail. Tried dozen times, then factory reset again, same problem. Finally got it to work by pressing my index very hard against the sensor while rotating it. Took a few tries but it worked. Once it was recorded it now works perfectly. Strange. Hope it helps someone

Licaon_Kter said:
BUUUUT, when trying to answer I call I have to rub my whole finger several seconds until it actually answers, I end up with a ringing phone on my ear waiting for it to recognize me.
Click to expand...
Click to collapse
Haha
cuz you need to hold your finger on sensor a few sec in order to answer calls xD
to avoid mistakes

I rebranded my Mate 9, re-installed a factory image -- thank you FunkyDruid, and then the fingerprint menu settings disappeared. I would hate to format it if it's not gonna help.. Annoying though..

Proximity Sensor Issue OP7P

Guys!
Do you experience proximity sensor issues while answering calls on OP7P?
For me while I'm on calls. The display comes on and gets disturbed and get pressed by my ears all the time.
Also any idea of where the proximity sensor is located on OP7P?
Thanks ?

Yes, I'm having the same issues. While I'm on calls I often activate the notifications pulldown. It would be nice to know how to fix this.

If you pull down the notification shade, the sensor is located just above the fifth icon on the first row. IE behind the screen.
If you pull the shade all the way down it is above and between the third and fourth icons. Easiest way to describe it. Put your thumb over that area with auto brightness on to watch the slider move.
Annoying while on a call that the screen comes on.

I'm experiencing the exact same issue with the caller app.
I also tried to make a flip cover to turn screen on or off with a proximity sensor detection app and it didn't work either.
I search a little in engineer mode (*#808#) and found that there is multiple proximity sensor, the IR sensor work quite well but it doesn't seem to be the default one.
The default one seems to be the ultrasonic sensor which works really bad.
There is also a "TP" proximity sensor which seems to be a near field detection which seems to work if I move my hand near the screen.
The sad thing is that in dedicated app to use or test proximity sensor (and in antutu or else) only one proximity sensor is listed (The ultrasonic one I guess) so you cannot switch to use the one which is working well.

Isn't this in the wrong place? Shouldn't it be in the Questions and Answers section?
Mods?

Probably just here looking for a mod to improve the situation

Actually I was going to open a new thread in Q&A when I found this one with the same subject and problem.
Do you think I need to open a new thread?
Is any of you experiencing the same issue as I described in my answer?

did anyone calibrate the proximity sensor using *#808# first? That seems to fix double tap to wake for some people

I tried to with no luck but as I explain in my first message the IR sensor is only used when screen is off (that's why it could help with double tap to wake)
But when screen is on another or couple another sensors are used and you can't calibrate them.
I think ultrasonic sensor is used when screen is on.
Do someone tested proximity sensor with any app on the play store? (Like proximity sensor test)
Put it on a table and check if it's working, mine is absolutely not. If I hold it like I was about to phone it works a little but it's not impressive.
Since I got 9.5.7 (EU version) earlier this evening screen turn off when I make a call.

I'm having this issue since 9.5.8... It's very annoying and I'm really disappointed, I often turn on airplane mode during a call... I tried to calibrate but it doesn't work.
I'm very very frustrated

schmeggy929 said:
did anyone calibrate the proximity sensor using *#808# first? That seems to fix double tap to wake for some people
Click to expand...
Click to collapse
When I click on proximity test it says it needs calibration how do I do that cause otherwise I can not test my proximity sensor cause when I click on it nothing happens
I am on 9.5.8

dallasnights said:
When I click on proximity test it says it needs calibration how do I do that cause otherwise I can not test my proximity sensor cause when I click on it nothing happens
I am on 9.5.8
Click to expand...
Click to collapse
This...

I've been having issues with phone calls but more so with pocket issues.. When I had the 6t pocket mode kept the phone neutral but this phone doesn't seem to have an accurate prox sensor.. Is there a way to activate a pocket mode?
Sent from my [device_name] using XDA-Developers Legacy app

Happening to me too, approached oneplus via live chat about this issue and at one point they said to wipe and reset my phone even if I told them the sensor is working but seems badly calibrated. Will try the wipe & reset and if it's not working I am returning my phone.

Proximity sensor is working fine - there is a bug elsewhere on the firmware that does not lock the screen when it is blacked out

pinzarualex said:
Happening to me too, approached oneplus via live chat about this issue and at one point they said to wipe and reset my phone even if I told them the sensor is working but seems badly calibrated. Will try the wipe & reset and if it's not working I am returning my phone.
Click to expand...
Click to collapse
Let us know if it's going to fix the issue wiping and resetting everything please!!!

Jaco2k said:
Proximity sensor is working fine - there is a bug elsewhere on the firmware that does not lock the screen when it is blacked out
Click to expand...
Click to collapse
But I have had this issue since release.. Do you a link to this information? If that's the case maybe someone can look into the firmware and see if it's minor tweak that can fix it?
Sent from my [device_name] using XDA-Developers Legacy app

Jack_Sparrow_ said:
Let us know if it's going to fix the issue wiping and resetting everything please!!!
Click to expand...
Click to collapse
Of course it didn't fix anything...

Jaco2k said:
Proximity sensor is working fine - there is a bug elsewhere on the firmware that does not lock the screen when it is blacked out
Click to expand...
Click to collapse
This has been an issue since the release. Do you have a link to where you read this information? If it is the firmware maybe someone can look into the settings and see if needs a tweak..
Sent from my [device_name] using XDA-Developers Legacy app

j0hnee said:
This has been an issue since the release. Do you have a link to where you read this information? If it is the firmware maybe someone can look into the settings and see if needs a tweak..
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I have reported this to Funk wizard on the OOS support thread and he said he cannot reproduce it anymore on the latest test build, so... We have to wait for next firmware release and see if that is indeed the case

Asking for a favor from anyone in the Zenfone 7/7 Pro community

Hey! I'd like to ask a favor from someone with a Zenfone 7 in their hands. Could you tell me the driver name of your proximity sensor? You can check it by using Sensor Box (free on the playstore).
I'm asking for this because it seems my phone doesn't even recognise the driver and it just displays as ASUS Proximity Sensor, opposedly to other sensors that display their true name. Maybe I'm tripping and that's just it's real name, but I'm almost sure it had a different name before the sensor started malfunctioning.
I'll attach a couple screens. Thank you in advance.

Here's some screenshots from a borrowed Zenfone 7 Pro, as you can see it's named the same.
To be sure we don't suffer the same fate I did some tests to confirm that sensor is working.

@zcrubby Thank you! Indeed your sensor works well. I'll keep trying to figure out where to find the root folder of the proximity sensor driver to disable it, since I was able to get sensor disabler functioning but didn't do the trick with the proximity sensor. Would you let me know if you know something? Much appreciated!

tommydotwav said:
@zcrubby Thank you! Indeed your sensor works well. I'll keep trying to figure out where to find the root folder of the proximity sensor driver to disable it, since I was able to get sensor disabler functioning but didn't do the trick with the proximity sensor. Would you let me know if you know something? Much appreciated!
Click to expand...
Click to collapse
Any luck in disabling the proximity sensor? I have a strange bug wherein every restart of the device causes the first instance of the camera to flip upside down and come up with the camera obstruction error. But once you click ok several times it's fine.