Develop Bugs

[Poll] Do you use face unlock, pattern, etc?

Just curious about what kind of security people use to unlock their phones. I played with the face unlock when I first got the GN but eventually got too impatient. I'm trying to decide if continuing to "Improve face matching" will eventually make it fast almost every time, or if I should just go ahead and switch to pattern or pin.

If you lock your phone, I found face unlock minimize touching the screen and thus less blur on screen
But sometimes I feel face unlock delay my logging into the phone in case I want to do something quick.... I still prefer pattern unlock
Sent from my Galaxy Nexus using Tapatalk

I used to have no pin because I like the stock lockscreen and being able to put SMS phone etc in the slide to unlock. Now that aokp has the option for both I use pin and lockscreen. Feels like iPhone lock exactly
Sent from my Galaxy Nexus using XDA

I use pattern..but not for security reasons at all. I got tired of pocket dialing people.
Sent from my Galaxy Nexus

Pin. When you think of the personal information on a smartphone it is a little scary. I have droidlost installed for added protection, but I'll only use a pin because anything else is just to insecure. Most pattern locks can be guessed by smudges on the screen in just a few attempts. Face unlock can be cracked with a bad facebook pic.

While face unlock can be hacked with a picture, no one that finds your lost phone is going to know what you look like. I always thought that was an interesting criticism of the face unlock. My friends might be able to hack into my phone, but that's not really who I'm trying to secure it from.
I also used to only use slide, but I have recently become more and more aware of how much information is available to anyone holding my phone. I think identity theft would be pretty easy if I lost it

virtualcertainty said:
Pin. When you think of the personal information on a smartphone it is a little scary. I have droidlost installed for added protection, but I'll only use a pin because anything else is just to insecure. Most pattern locks can be guessed by smudges on the screen in just a few attempts. Face unlock can be cracked with a bad facebook pic.
Click to expand...
Click to collapse
Yeah, pin and password are the only two that are very secure, but I just use slide. My mentality is, I'd be much more concerned if someone got ahold of my wallet with all my cash, ids, cards, etc, but I don't put a lock on that. I just keep it with me all the time, same as my phone. I've never lost either and don't plan to! But I do have SeekDroid just in case.

Face Unlock, just so that when I get into the homescreen, JuiceDefender has turn on my Data Connection. Oh, and too impress friends too

Face Unlock.
It is much better than nothing and I don't want to key in the PIN every time the screen is locked.
I never carry my own photo with me other than the one on my driver license which I confirmed would not unlock my phone. So I don't see why people say Face Unlock is useless.

I use a pattern, get it wrong and I have a picture of you emailed to me.
I used slide to unlocked before I installed cerberus, might as well use the features.
Sent from Mobile..

kensingtn5 said:
While face unlock can be hacked with a picture, no one that finds your lost phone is going to know what you look like. I always thought that was an interesting criticism of the face unlock. My friends might be able to hack into my phone, but that's not really who I'm trying to secure it from.
I also used to only use slide, but I have recently become more and more aware of how much information is available to anyone holding my phone. I think identity theft would be pretty easy if I lost it
Click to expand...
Click to collapse
Actually it would be very easy to find out. Most lockscreens will splash contact information. If you find my phone you will have my name, work phone number, and multiple email addresses. That is at least three ways to google and find pictures for most people. I would argue that this is the most insecure method possible to lock up your device.
Clicked thanks by mistake but thanks for replying anyway

str355 said:
I use a pattern, get it wrong and I have a picture of you emailed to me.
I used slide to unlocked before I installed cerberus, might as well use the features.
Sent from Mobile..
Click to expand...
Click to collapse
how do you get the phone to send you the pic?

I like to use the pattern, but it gets annoying when I'm just sitting at home texting back and forth, as I have to unlock it every single time. I end up turning the security off lol. Sometimes I'm good and turn it back on when I leave the house.

neotekz said:
how do you get the phone to send you the pic?
Click to expand...
Click to collapse
It's the cerberus app.

virtualcertainty said:
Actually it would be very easy to find out. Most lockscreens will splash contact information. If you find my phone you will have my name, work phone number, and multiple email addresses. That is at least three ways to google and find pictures for most people. I would argue that this is the most insecure method possible to lock up your device.
Clicked thanks by mistake but thanks for replying anyway
Click to expand...
Click to collapse
After enabling Face Unlock, when I touch the power button, I can only see the date, time, and the network name. There is no personal information at all.

Amowagou said:
After enabling Face Unlock, when I touch the power button, I can only see the date, time, and the network name. There is no personal information at all.
Click to expand...
Click to collapse
Under security settings click 'Owner info' to turn it on. Shows whatever message you want to the hopefully honest person who finds your phone. Only hitch is that if the phone is plugged in it just says "charging xx%" rather than the message. Don't know if that is a bug or if Google just figured that if your phone is plugged in it is probably not lost.

I'm using a PIN because I installed unlock with WiFi and it requires it. When I'm on a registered WiFi network I just slide to unlock.

virtualcertainty said:
Pin. When you think of the personal information on a smartphone it is a little scary. I have droidlost installed for added protection, but I'll only use a pin because anything else is just to insecure. Most pattern locks can be guessed by smudges on the screen in just a few attempts. Face unlock can be cracked with a bad facebook pic.
Click to expand...
Click to collapse
also, i feel that pattern unlock can be easily seen & remembered by people standing behind you even from quite a distance, as compared to pin/password lock

No. I'm ugly enough and don't need to be reminded of it constantly.
Neat trick though.

i wish there is a slide --> pattern unlock. i want the quick camera access and pattern

swype gesture interrupted

Hi guys,
I have a pretty disturbing problem. When I use swype gestures to type a word, whether with Xperia keyboard or with (my preferred) Google keyboard, sometimes the gesture is interrupted although I do nothing to provocate it. I can not reproduce this bug - it has nothing to do with the speed of swyping. I already turned off the option for having a space when hovering over the space bar. It happens every three minutes or so, but I do not know why.
Does anyone know this problem? Any solution?
I am on 4.4.4, 14.4.A.0.108, Kernel: 3.4.0-perf-g0109737
I uninstalled Xperia Home Launcher, using Google Now launcher only.
Thanks a lot!

same here, IMO is an hardware problem

I flashed a complete new ROM with a new kernel, and the problem persists. That is incredibly annoying.
Any idea how we might get rid of this?

same here. it makes most games unplayable

Using a matt screen protector was the solution for me. Had no interruption since.

eeegamer said:
Using a matt screen protector was the solution for me. Had no interruption since.
Click to expand...
Click to collapse
remove the screen protector that is factory installed and install another one? Which one did you installed? (Amazon link that may be you can share with us?)
Thanks.

Nope, I did not remove the factory installed screen protector - just used the screen protector like you would with any other phone.
I ordered this one: http://www.amazon.de/mumbi-Displays...d=1407017702&sr=8-5&keywords=z1+compact+folie
Unfortunately they are out, but I guess any other matte screen protector will do it also.
I had no issue since putting it on.

Unable to make or take calls properly on CM11

Please refer to this post:
http://forum.xda-developers.com/showpost.php?p=62828995&postcount=1432
Has anyone gotten this problem? The person who posted this has been the only one having this problem. This can't be a rare thing, is it? Is everyone just dealing with this issue until it gets fixed?

Here is a compilation of the comments made about this issue thus far. There seems to be a consensus that screen protectors are not causing this issue.
11th August 2015
AnotherContributor said:
One issue though I've been having is that when I'm making and receiving calls, sometimes the phone display goes black and will frankly not come back on. I press the App button and sometimes the display comes on, sends the call to the Status Bar, and the screen goes dark. So, I have to press the Application button again and draw down the menu to hang the call up. When I press the power button, the screen flashes on for maybe a quarter second then goes dark. It keeps doing that every time you press the power button. The worst case scenario that has happened a handful of times is that when I'm in a call, neither the power nor application button are responsive. When that happens, pretty much the only option is to power down the phone and reboot.
...
I'm not sure if I would be able to dial an extension with the way the phone is acting up. I feel like this was not an issue the first couple of weeks I had CM on the phone. Now, it seems to be happening with every call.
Click to expand...
Click to collapse
14th September 2015
samuraix21 said:
Hi, I have this issue. Were you able to fix this issue? You're the ONLY person that has posted this issue so I'm not sure if this is a rare hardware issue or everyone on this forum is somehow dealing with it until a fix comes up.
Click to expand...
Click to collapse
19th September 2015
hawk1500 said:
are people still experiencing the screen off during call problem? I am not talking about when you put it up to your face, but how the screen turns off and won't come back on?
Click to expand...
Click to collapse
20th September 2015
hawk1500 said:
Naw, no screen protector installed. tried the proximity sensor fix app as well as the xposed don't go to sleep during call module but it still does it.
Click to expand...
Click to collapse
20th September 2015
tonochito said:
i think that bugs should be listed more detailed:
front facing camera does not work well, if i want to take a selfie it crash. video camera also does not work equal it will crash. I had to install Google Camera and Open Camera in order to have both selfie and video options working, With Google Camera i take selfies and with Open Camera i record videos, As the guy talking about the scren off in calls is true, i don't have a screen protector and it has this behaivour, also as i mentioned there is kind of lag when i try to dial a number i have to do twice, it doesn't show up right away. The same goes when i am calling for example my carrier and i have to dial on the IVR i have to dial twice in order to get the dial keypad. I didn't have Google play crash.
Another thing that i notice was setting a wallpaper as screensaver does not fit in the middle or correctly i had to use Quick Pic and the option 768x1280 because with the stock gallery wallpapers are like aside of the middle
Click to expand...
Click to collapse

I think this issue needs some attention. I am having this problem as well (with and without screen protector). There are times that I need to enter extensions and codes during calls which has become impossible. I have two of these phones and they both behave this way. I recommend that people start posting screenshots of the app Proximity Sensor Finder which displays different distance numbers detected by the prox sensor. See my screenshot attachment which shows the proximity sensor always detecting a "covered" state of 0.0cm even when nothing is in front of the screen. Everyone should go try this and post their findings.
Other phones on CM11 were able to fix this problem in the past by adjusting the calibration which is unique for each phone, so I started searching around through the Fire Phone CM11 files and I found these:
/system/etc/permissions/android.hardware.sensor.proximity.xml
I could not discern anything of value from this .xml file.
/persist/sensor_calibration/SHCAL_DU20060142640727.csv
This file seemed promising. Its timestamp is back in 2014 so I assume that this comes straight from the original Fire Phone files. If this file is actively used to govern sensor behavior, I'm wondering if perhaps it is not being read correctly. It makes me wonder if there is a log out there somewhere that could shed more light on it. Anyways, you can open up that badboy in any spreadsheet to discover sensor IDs for a bunch of sensors along with calibration coefficients in the form of:
SENSOR_TYPE=PROX SENSOR_ID=SI1143 SENSOR_REF=4CCU1 COEFF0=550.30
SENSOR_TYPE=PROX SENSOR_ID=SI1143 SENSOR_REF=4CCU1 COEFF0=395.62
SENSOR_TYPE=PROX SENSOR_ID=SI1143 SENSOR_REF=4CCU1 COEFF0=19262.26
You'll have to open it and analyze it in context of the other columns and other sensors. I've attached it (re-saved in xlsx format because .csv files are not permitted - if you don't trust my xlsx just retrieve the file from your phone). I highlighted the rows of interest. We could just mess with coefficient values, but without any guidance, it could just be a waste of time. Plus we don't know if this even governs the sensors or if it's just helpful documentation. If anyone has insight about this or even far fetched theories, please comment!
I'm thinking about doing a 'grep' on the entire file tree for some of these key words like SENSOR_ID=SI1143, SI1143, 4CCU1, COEFF0, SENSOR_TYPE=PROX etc etc - to see if any files use any of these terms. It may prove unfruitful due to the amount of compiled software that is no longer in text form. Any thoughts about any of this?

i have this screen always making a call with any cm11 i have used in the past, i have to press back and again the keypad and works normal, same when i have to dial a number

tonochito said:
i have this screen always making a call with any cm11 i have used in the past, i have to press back and again the keypad and works normal, same when i have to dial a number
Click to expand...
Click to collapse
But if the prox sensor is always detecting a "covered" state, then it completely disables the screen during a call and we are unable to press "back". Could you post your findings from running Proximity Sensor Finder from CM11 Fire Phone?

jdmillard said:
But if the prox sensor is always detecting a "covered" state, then it completely disables the screen during a call and we are unable to press "back". Could you post your findings from running Proximity Sensor Finder from CM11 Fire Phone?
Click to expand...
Click to collapse
i will give a shot, and post my result

In fact, it would be AWESOME if we could get someone (whose screen does behave perfectly during calls) to post their findings from Proximity Sensor Finder. If their screen works perfectly during calls and this app shows 0.0cm all the time for them too, then we can conclude that this app isn't functioning correctly and we know we need to find our root cause elsewhere.

tonochito said:
i will give a shot, and post my result
Click to expand...
Click to collapse
Available but why it doesn't work right?

tonochito said:
Available but why it doesn't work right?
Click to expand...
Click to collapse
Interesting. Is it stuck on 10.00061 even when you cover the front of your phone with your hand? Or does the number fluctuate?
Which ROM build are you on? (I should say, which publish date?)

jdmillard said:
Interesting. Is it stuck on 10.00061 even when you cover the front of your phone with your hand? Or does the number fluctuate?
Which ROM build are you on? (I should say, which publish date?)
Click to expand...
Click to collapse
yes weird it is stuck no matter what i do, well if i put my finger in the "first camera" of the phoen it goes to zero

tonochito said:
yes weird it is stuck no matter what i do, well if i put my finger in the "first camera" of the phoen it goes to zero
Click to expand...
Click to collapse
That suggests to me that the sensor is "all or none" meaning it doesn't bother detecting intermediate values, rather it just has a threshold that determines a covered or not covered state. That seems normal to me. I need to get mine to do that.
Does your screen behave normally during calls? Specifically, does the screen turn on when you pull the phone away from your face?

jdmillard said:
That suggests to me that the sensor is "all or none" meaning it doesn't bother detecting intermediate values, rather it just has a threshold that determines a covered or not covered state. That seems normal to me. I need to get mine to do that.
Does your screen behave normally during calls? Specifically, does the screen turn on when you pull the phone away from your face?
Click to expand...
Click to collapse
Not always as some users says it sometimes goes black, or i have notice that the notification bar sometimes goes down by itself and the annoying problem of the keypad on calls

I just removed my glass screen protector and now mine behaves just as yours. Which is good that it functions as expected, but also a disappointment about the screen protector. I just looked to request a refund and it appears that they have an excellent return policy so I'm not too worried about it. Now I just need to find a screen protector that doesn't cover the prox sensor. ... sigh.
I'm still interested to see what happens with what you were describing: like how the screen would still behave finicky. I'll keep an eye out for that behavior and I'll let you know if I discover anything about it.
---------- Post added at 01:26 PM ---------- Previous post was at 12:38 PM ----------
tonochito said:
Not always as some users says it sometimes goes black, or i have notice that the notification bar sometimes goes down by itself and the annoying problem of the keypad on calls
Click to expand...
Click to collapse
I forgot to say thanks! You posting your results helped me figure out where I was going wrong. Gracias!

jdmillard said:
I just removed my glass screen protector and now mine behaves just as yours. Which is good that it functions as expected, but also a disappointment about the screen protector. I just looked to request a refund and it appears that they have an excellent return policy so I'm not too worried about it. Now I just need to find a screen protector that doesn't cover the prox sensor. ... sigh.
I'm still interested to see what happens with what you were describing: like how the screen would still behave finicky. I'll keep an eye out for that behavior and I'll let you know if I discover anything about it.
---------- Post added at 01:26 PM ---------- Previous post was at 12:38 PM ----------
I forgot to say thanks! You posting your results helped me figure out where I was going wrong. Gracias!
Click to expand...
Click to collapse
your welcome

I have a glass protector and i noticed over time that i developed a specific technique for answering the phone. I sort of slowly move it close to my ear and then the sound comes on (hear ringing, able to hear caller). If i press the answer button then put it to my ear, most of the time i cant hear the caller but they CAN hear me.
Never even considered it being a sensor issue. I thought it was CM bug triggered by my setup somehow. I flashed this rom and put the glass screen on within a couple of days after receiving it in the mail and since touch-wise the tempered glass works perfectly it was never even a thought. Dont mean to go on but is anyone else dealing with issues like the one i describe? Whats strange is i dont recall having that black screen issue others are experiencing.

KLit75 said:
I have a glass protector and i noticed over time that i developed a specific technique for answering the phone. I sort of slowly move it close to my ear and then the sound comes on (hear ringing, able to hear caller). If i press the answer button then put it to my ear, most of the time i cant hear the caller but they CAN hear me.
Never even considered it being a sensor issue. I thought it was CM bug triggered by my setup somehow. I flashed this rom and put the glass screen on within a couple of days after receiving it in the mail and since touch-wise the tempered glass works perfectly it was never even a thought. Dont mean to go on but is anyone else dealing with issues like the one i describe? Whats strange is i dont recall having that black screen issue others are experiencing.
Click to expand...
Click to collapse
I was lucky enough to have a good return policy on the glass screen protectors I recently got (for two Fire Phones). I'm returning them today and I've already ordered this as a replacement:
http://www.amazon.com/gp/product/B00WXY18WK?psc=1&redirect=true&ref_=od_aui_detailpages00
It has excellent reviews, decent price, very thin, and it is specifically mentioned many times in the reviews that there is a little cutout for the prox sensor (and you can see if if you look carefully at the pictures). I'm hoping that it will solve my black screen woes and protect my screen. There are reports from folks on these forums saying that there is still some strange behavior during calls (such as your example among others). I personally haven't encountered what you're describing, but I'll keep an eye out to see if I can be of any help.

jdmillard said:
Here is a compilation of the comments made about this issue thus far. There seems to be a consensus that screen protectors are not causing this issue.
11th August 2015
14th September 2015
19th September 2015
20th September 2015
20th September 2015
Click to expand...
Click to collapse
Hi. I like to get back about this since I've been quoted on this.
For me, the glass protector screen that I brought from XtremeGuard was the issue my dad had when he tried to make or take calls. After I removed it, it was back to normal.
The persistent issues now, based on what my dad is telling me, is that sometimes after you dial in a number and call a person, you don't hear the ringing tone to know if it went through or not. My dad would freak out when someone on the other line said something since the ringing tone is not working.

tonochito said:
Not always as some users says it sometimes goes black, or i have notice that the notification bar sometimes goes down by itself and the annoying problem of the keypad on calls
Click to expand...
Click to collapse
hi
this is usually related to hardware composer.
cheers

superdragonpt said:
hi
this is usually related to hardware composer.
cheers
Click to expand...
Click to collapse
but why? does it matter with the bootloader, i mean i know the CM11 on the Fire phone still on beta with no NFC working and the camera too at least i am using Snap camera and everything works. But making calls is a bit annoying even i don't use the phone to make a lot of calls just for WhatsApp almost all the time

8.1 Update broke proximity sensor ??

hey guys, maybe someone can help with my pixel 2 XL 64 GB in Germany
Since I upgraded to 8.1 my ambient screen doesn't work properly, black screen on calls and so on. I'm pretty sure it's some change with the proximity sensor. i used some apps to test the sensor and when I clean my screen really hard everything works fine (shows "far" in the test app) but when i just wave without touching the screen, it goes to "near" and doesn't recover until i wipe the screen again ( wtf?). I can't really use the phone like this. I am in contact with Google support but they give the generic suggestions like restart the phone etc.
Everything worked fine under 8.0. i actually went ahead and flashed 8.0 back on and it works properly. it seems like they increased the sensors aggressiveness in 8.1.
For most people the problem gets resolved by taking off the screen protector but I don't have one applied. neither are there any scratches on the display. Maybe my sensor is flawed in some way :/
I also tried the turning on /off adaptive brightness trick, to which there is a thread somewhere.
maybe you guys can share your experiences or fixes,
Thanks and Liebe Grüße from Germany !

grigi93 said:
hey guys, maybe someone can help with my pixel 2 XL 64 GB in Germany
Since I upgraded to 8.1 my ambient screen doesn't work properly, black screen on calls and so on. I'm pretty sure it's some change with the proximity sensor. i used some apps to test the sensor and when I clean my screen really hard everything works fine (shows "far" in the test app) but when i just wave without touching the screen, it goes to "near" and doesn't recover until i wipe the screen again ( wtf?). I can't really use the phone like this. I am in contact with Google support but they give the generic suggestions like restart the phone etc.
Everything worked fine under 8.0. i actually went ahead and flashed 8.0 back on and it works properly. it seems like they increased the sensors aggressiveness in 8.1.
For most people the problem gets resolved by taking off the screen protector but I don't have one applied. neither are there any scratches on the display. Maybe my sensor is flawed in some way :/
I also tried the turning on /off adaptive brightness trick, to which there is a thread somewhere.
maybe you guys can share your experiences or fixes,
Thanks and Liebe Grüße from Germany !
Click to expand...
Click to collapse
I myself had some odd behaviors after updating by using the factory image with the -w removed from the flash-all.bat and ended up starting from scratch due to my cat. (Long story) but anyway, I think you will find a few other folks had bad results of some sort or other after updating. Personally, I would back up everything with TiBu and a good nandroid. ( kill any pin or fingerprint stuff first). Get anything off the internal storage you don't want to lose also.
Worst case you have a few hours of putting it back together and best case you flash from scratch and restore your data partition in TWRP.
If you factor in the time screwing around trying to "fix" it, you might be better off starting over. Unless you did actually install 8.1 from scratch them forget all this. Lol

CyberpodS2 said:
I myself had some odd behaviors after updating by using the factory image with the -w removed from the flash-all.bat and ended up starting from scratch due to my cat. (Long story) but anyway, I think you will find a few other folks had bad results of some sort or other after updating. Personally, I would back up everything with TiBu and a good nandroid. ( kill any pin or fingerprint stuff first). Get anything off the internal storage you don't want to lose also.
Worst case you have a few hours of putting it back together and best case you flash from scratch and restore your data partition in TWRP.
If you factor in the time screwing around trying to "fix" it, you might be better off starting over. Unless you did actually install 8.1 from scratch them forget all this. Lol
Click to expand...
Click to collapse
I did enjoy your cat story a while back! Dang varmints!

FWIW - I received the OTA update on my phone (unlocked version) and the proximity sensor seems to be screwed up. I having the same issues you've described. I've also got the mooshi ion glass screen protector on my phone.

CyberpodS2 said:
I myself had some odd behaviors after updating by using the factory image with the -w removed from the flash-all.bat and ended up starting from scratch due to my cat. (Long story) but anyway, I think you will find a few other folks had bad results of some sort or other after updating. Personally, I would back up everything with TiBu and a good nandroid. ( kill any pin or fingerprint stuff first). Get anything off the internal storage you don't want to lose also.
Worst case you have a few hours of putting it back together and best case you flash from scratch and restore your data partition in TWRP.
If you factor in the time screwing around trying to "fix" it, you might be better off starting over. Unless you did actually install 8.1 from scratch them forget all this. Lol
Click to expand...
Click to collapse
thank you! i already did a fresh factory flash of the 8.1 firmware from the Google devs website. Didn't solve the problem though It works fine on 8.0 so I don't get it.
It's really strange that only a bunch of people experience this problem. I kinda hoped for a functioning phone , at least for 1000 bucks.
I'm considering to get a replacement if nobody finds a fix to this.

Not sure if it'll help, but I installed "Sensors test" by Ettore Zaffaroni. Mine works just fine on 8.1 stock unrooted. The version is the OTA update to DP2.
In the Proximity test, at the bottom of that is says:
Vendor: AMS TAOS
Version: 2
Max Range: 5 cm
Resolution: 1 cm
Current: 01. ma
Maybe check and see if it is the same vendor and version. And if the other numbers match. I measured it activating between 1 1/2 inches and 2 inches, pretty much only directly in front of the sensor. I have a screen protector but with a hole cut out over the sensor.

Same issue here, no screen protector installed. Tried a factory reset without luck, tried safe mode without luck. Only started since 8.1 update.

Since the 8.1 OTA, I'm having an issue where the Always on Display doesn't always stay on and when the screen goes black, I can't use double-tap to wake it back up. I have to use the power button to turn the screen back on. I wonder if it's related to the proximity issue, because it's almost as if the screen thinks you have the phone up to your ear...?

ogarlen said:
Since the 8.1 OTA, I'm having an issue where the Always on Display doesn't always stay on and when the screen goes black, I can't use double-tap to wake it back up. I have to use the power button to turn the screen back on. I wonder if it's related to the proximity issue, because it's almost as if the screen thinks you have the phone up to your ear...?
Click to expand...
Click to collapse
Same issue here. Downloaded Sensors test, and Proximity shows as "NEAR", I've got a screen protector covering the sensor.

I have the same issue. Pixel 2 xl, after upgrading to 8.1, proximity sensor says near when screen protector is on. I think that most likely something is messed up with the update.

Wanted to add that I have a screen protector, however had the same one on 8.0 and had no issues. Also that neither DT2W or raise to wake works when the screen goes black, only pressing the power button. The issue seems intermittent. Always On Display seems to be working about half the time, whether I allow the screen to automatically shut off after a minute or if I press the power button to shut the screen off.

yes i did the test with the app sensor test and it shows "near". I downgraded to 8.0 and it works fine.
For all of you guys with screen protectors:
try removing it, it solved the problem for some people but not for me (i didn't have one on the first place)
or try downgrading if you know how to.
I went to my carrier today and they told me they got an email from Google about the 8.1 update is kinda messed up, so i should wait for the next patch. Idk what's going on, but i hope Google is aware of this.
thanks for the replies though!

I'm also having similar problems with my phone with the sensor. Also with the gesture features not working such as, double tap and flip for camera.
Ambient display not functioning is properly the most annoying, along with black screens after phone calls.

I did notify google of this issue. It would be good if all of you spend few minutes to do the same. That will let them know it is not an isolated incident.

Removing my screen protector immediately solved the problem for me. Just ordered another one that won't cover the proximity sensor.

I don't have a screen protector and I have the same issue with my proximity sensor. Anyone figure out a fix?

dpw2atox said:
I don't have a screen protector and I have the same issue with my proximity sensor. Anyone figure out a fix?
Click to expand...
Click to collapse
No fix that I'm aware of,
but there are many more people with similar issues.

Same here, had a full glass screen protector on my 2xl (on Oreo 8.0)and I cracked it when carrying a pair on ladders, phone was in my pocket at the time. So I ordered the same screen protector again... Once again it worked fine but as soon as the update to 8.1 was installed I was getting a black screen whilst receiving a call and had to wait for the caller to hang up before my phone returned to normal. As soon as I removed the screen protector the phone was fine. I've checked this 3 times and the same thing happens. Google have done something to the proximity sensor in the last update, no question.

Same issue here, no screen protector installed. Screen goes black every time I try to use the phone while on a call.

Funny how my phone worked perfectly with my screen protector before this 8.1 update for the two months the phone as been out. Now I can't hang up phone calls or turn the screen on during phone calls. -_- Hope they fix it soon.

Question Lag on the most of applications

I have got magic 4 pro two weeks ago and i note that there is a clear lag when i move between applications or within the application it self, Twitter, Google play Chrome... As sample
The problem is clear after each restart the Mobile and be better if i use it for more days without restart

After reset the Phone nothing changed... It is a clear lag

Finally, the problem was from the screen protector, I've removed and now it's smooth
This protector by Honor

I have another problem: when I unlock the screen(swipe or ampreint), the screen is freezing...to unfreeze I have to lock and unlock again...

I have the same issue (lag) but I've not removed screen protection.
When a use the search mode (swype down) keyboard is very slow and starting app too

This phone is so bad I can't believe it's actually for real, the lag and inconsistent WiFi calling , clearly there is a major issue with the software , I'm really hoping this will get resolved with the next update which I am also hoping will be released very soon.

marek03 said:
This phone is so bad I can't believe it's actually for real, the lag and inconsistent WiFi calling , clearly there is a major issue with the software , I'm really hoping this will get resolved with the next update which I am also hoping will be released very soon.
Click to expand...
Click to collapse
We need Ram Turbo to have a better experience. Please send email to support:
Honor Ram Turbo
https://www.hihonor.com/uk/club/topicdetail/honor-ram-turbo-honors-implementation-of-virtual-ram-brings-real/topicid-28949/ https://www.americanjournal.news/what-is-the-honor-ram-turbo-technology-that-will-come-in-the-new-magic-4-pro-about/...
forum.xda-developers.com

albatli said:
Finally the problem was from the screen protector, i removed and now it's smooth
This protector built by honor
Click to expand...
Click to collapse
How is the phone now, did you make sure that the reason is the screen protector !! because I have the same problem now
Can you confirm this solution please ..?!

hsona said:
How is the phone now, did you make sure that the reason is the screen protector !! because I have the same problem now
Can you confirm this solution please ..?!
Click to expand...
Click to collapse
confirmed
for All, Remove the screen protector immediately,

albatli said:
confirmed
for All, Remove the screen protector immediately,
Click to expand...
Click to collapse
I removed the screen protector but nothing changed unfortunately.