Gsm 3d here...
I noticed that the face unlock code if light too low or can't recognize can be bypassed by simply pressing the ok button. actually unlocked with wrong password too.
Anyone else?
Could have been a recent mod I flashed.
welcome to custom roms. Until an official build is released, there will be bugs.
scariola said:
Gsm 3d here...
I noticed that the face unlock code if light too low or can't recognize can be bypassed by simply pressing the ok button. actually unlocked with wrong password too.
Anyone else?
Could have been a recent mod I flashed.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Bat signal for fix!
Mine asks if I want a pattern or PIN code while setting up the face unlock. I chose pattern and if the phone is unable to detect my face it asks for the pattern.
Only tried this on a few sense 3.6 ROMs.
Ok, so it was a zip I flashed that caused this to malfunction.
I setup the passcode for Facelock, then when it didn't recognize me, pressed the ok, or entered passcode incorrectly and it bypassed the security I put in place.
I restored a backup and can say that it no longer accepts incorrect passcode or just clicking ok.
Welcome to the world of flashing zips blindly, lol.
I'm holding out for retina scan (had to edit that before posting, originally wrote rectal scan. Hmmm.... a new idea, maybe not).:silly:
Related
Has anyone got Samsung dive to work for the new S3?
I have set up the account etc but when I use the website to track my phone or call it etc nothing happens.
I am on the O2 network in London. Any help would be much appreciated.
I set mine up yesterday and it setup fine and all, but when I went to track it...it did indeed track the phone, but it said my phone as at my home address when I was sitting in McDonald's. So...not sure why it did that but that is far from accurate!!
Calling and locating it worked from me with the original firmware. After installing Omega I tried again and it still works.
I cant get it working. I go through the motions as per below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
...but remote controls stays "off".
Anyone who has managed to get this set up, at what point does that setting for on/off at the top become available please?
rootSU said:
I cant get it working. I go through the motions as per below:
...but remote controls stays "off".
Anyone who has managed to get this set up, at what point does that setting for on/off at the top become available please?
Click to expand...
Click to collapse
Probably silly question but have you slid the toggle to "ON" - I had that first time as well. Every time you slide the toggle over you have to re-enter your password again.
your 3G enable ?
I eventually got it to slide after various combinations of removing and re-adding the samsung account and ticking / unticking the location tick box
Sent from my GT-I9300 using Tapatalk 2
What i have strangly noticed after s-off. I am running the jubountu bear hboot with viper rez and sebastions 1.2 1836 kernel. however i have noticed this in a couple roms: s is off:
I have had strange symbols appear in the caller id. for example it will say 9042517485 is calling and then when i go back to recent call list. instead of normally saying "unknown caller" it says *%^**&^ .
I have noticed as well people complaning that there voice is echoing in calls with me? any ideas?
Thanks SOO MUCH
Paul
Edit: I have flashed the stock 3.14.605.10 RUU and it si still doing it? to re generate the problem all i have to do is remove my home phone as a contact (it wont do it with contacts) then give myself a call.
and it looks like
#%$XD^$
9045451515
instead of
unkown caller
9045451515
Seems i dont have the problem when on 3.14.605.05 ROM.. ANy fix for this?
It is now doing it on the 3.14.605.05 RUU and 3.14.605.10 .... look at the first number? It displays like this after the phone call is ended in recent calls. HORRIBLE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OK it is not doing this on 3.11.605.22. any ideas? and it does do it on
3.14.605.05 +
3.14.605.10
did u run s-off with sim inside ?
Proz00 said:
did u run s-off with sim inside ?
Click to expand...
Click to collapse
YES i did
In the new 3.14.605.12 it appears above the phone number when i answer a call but does not appear in recent calls.
Just got a Note S and very good it is too.
However i was surprised on first boot up to be taken directly to the homescreen.
You normally get taken to the Google start up screen for language area.
I tried a reset but same again taken directly into the phone without the usual logging into Google.
If i flash the Rom from here http://forum.cubot.net/viewtopic.php?f=21&t=25 will it reinstate the Google login screen at start up ?
This is the screen i get on start up even after a Reset.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I normally get this google screen at start up on other devices.
I just got one of these and can confirm the behaviour - straight to the home screen with no language prompt. It's the same with the beta version of Marshmallow for it.
Seems there is no way to have the google language screen then.
I have this phone as well, why does it matter?
silverblack said:
Just got a Note S and very good it is too.
However i was surprised on first boot up to be taken directly to the homescreen.
You normally get taken to the Google start up screen for language area.
I tried a reset but same again taken directly into the phone without the usual logging into Google.
If i flash the Rom from here http://forum.cubot.net/viewtopic.php?f=21&t=25 will it reinstate the Google login screen at start up ?
This is the screen i get on start up even after a Reset.
I normally get this google screen at start up on other devices.
Click to expand...
Click to collapse
Can't see what the problem is.
philsilvers said:
Can't see what the problem is.
Click to expand...
Click to collapse
Seriously ? the thread is 3 years old and the phone long gone.
For about the detail, this is Huawei Nova 2 Lite(LDN-LX2)
I get this error message after my battery runs out and then comes the alarm notfication in this state appears first red symbol battery out. I immediately to charging(this second time), then appear this error booting.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
At first time i thought it was caused by installing a downloaded theme in the playstore, i have try to wipe data & cache but still same. i get some opinions about this, first, this is just an update failure, maybe EMUI update, nonsense wipe data & cache not work. Second, after newly sign up the phone again, before log in Huawei ID it's appear "Your phone is rooted", i don't know what's happen, dude. I immediately check out about
. Third, this phone still have Bootloader locked and FRP locked, check from fastboot on Huawei multi tool. Fourth, try so many times to get some update EMUI form Huawei eRecovey and restore and get failed to connected server.
I have try to find stock ROM LDN-LX2, and not found. if some one have some clues, or ideas, suggestion, please tell me.
this error booting is very annoying, the device still can boot up to home menu but too late and get some lagg/slow respone at sometimes.
Thank you,
regards, new member.
As a topic, right now i can't unlock my huawei mate20x
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
]
Do you have Google's device manager enabled? You could change your's password there https://www.google.com/android/devicemanager
i.adrian said:
Do you have Google's device manager enabled? You could change your's password there https://www.google.com/android/devicemanager
Click to expand...
Click to collapse
The last version of Android where you could remotely change the device password if you got locked out of your phone was Kit Kat.
The only time I've heard of an update making the device stop recognizing the correct password is when a custom recovery is being used that can't properly decrypt data in which case the owner could boot back into TWRP and reformat the device memory.
In this case it sounds much more like somebody with a stolen phone trying to bypass the security set up by the legitimate owner.
As far as I know helping somebody do that still gets you banned from XDA.
If the OP here is the legitimate owner then there is probably a hardware problem with that phone and he should get it serviced under the warranty.
It's probably a script that's poorly written. Not necessarily the update.
Sent from my AL10
Mate 20 pro wrong pin after update
Hi. I have the same problem. After the software update it ask for the pin.entered it but it says wrong. I dont want to do a hard reset because of my pictures and documents. Pleade help
I have some bad news for you, since your problem is (in fact) similar to this one : https://forum.xda-developers.com/mate-20-pro/help/annoying-issue-mode-official-update-t3900123
There is a known issue with Huawei updates and any "password-lock" function