Ive tried setting it up, but for some odd reason it never implements, even though it says it does. Just defaults back to the stock lock.
Seems fine and works quite well on mine.
Raadius said:
Ive tried setting it up, but for some odd reason it never implements, even though it says it does. Just defaults back to the stock lock.
Click to expand...
Click to collapse
there may be something wrong with your face...
sorry couldnt help myself lol
Hahaha... Forgot about this feature. You need to make sue your entire face is inside the bubble.
Sent from my HTC One X using XDA
you must make sure that your in good light when you setup and when you try to unlock... if not then it will got to the backup lock screen that you setup.
mine works fast as crap... just as soon as my face is in the area it opens.
It gives you like 3 seconds to position your face correctly
Sent from HTC Rezound using xda premium
works really well for me. Recognizes my face in two seconds or less!
Works surprisingly well for me. Make sure you finish the setup and I would recommend trapping 'improve facial recognition'
Sent from my HTC One X using XDA
Not practical for me but I tried it out for novelty's sake and it worked first try.
Sent from my HTC One X using XDA
I tried it out, it works well for me. I found that if you took multiple images, including some from an angle that you'd actually be holding the phone when you unlock it (as opposed to just eye level), it unlocks very fast.
However, as I discovered today... it works a little too well maybe. I was showing the feature to my co-worker who just loves his voice commands, and then mentioned that, though it was a pretty neat feature, it could be cheated by using a photo. We decided to run a little experiment, using his phone (either a Droid or Droid 2) to take a quick snap of me and then seeing if it would work for face unlock off his screen. And it did... very well in fact. I was surprised at how well it worked off of a phone with a small, (relatively) low res screen, and crappy camera.
So, neat feature, not at all secure really.
face unlock is to much of a gimmick, I am in low light a lot so it is useless.
Yeah, this feature sucks for me. Took me forever just to set up the initial pic. I'm in pretty good lighting, but I'll try the "improve recognition" feature in some different locations throughout my day.
worthless.. unlocked for myself every time, tried my dad's face and it unlocked for him too.. no wonder it "works so well" it unlocks for almost anyone
designgears said:
face unlock is to much of a gimmick, I am in low light a lot so it is useless.
Click to expand...
Click to collapse
Yeah, it's pretty neat but not terribly useful for me either. We have to wear safety glasses at work due to OSHA regulations, and it can't detect my face with my safety glasses on. Maybe if I tried to "improve recongition" with my safety glasses on it would, but then at what point does it basically just let anybody in?
I'll just leave my phone unlocked like always and hope nobody goes snooping... like always. They'd be terribly bored even if they did.
mesko402 said:
worthless.. unlocked for myself every time, tried my dad's face and it unlocked for him too.. no wonder it "works so well" it unlocks for almost anyone
Click to expand...
Click to collapse
Well, maybe you both look alike to the face unlock's algorithm. I'm not sure exactly how they do facial recognition, but I'm sure there's some fancy math regarding your facial features involved. FWIW, it wouldn't unlock for any of my co-workers - well, except for the guy with a picture of me on his phone!
For certain values of the word "work".
I've done the "improve recognition" thing a few times but there are just so many different environments and lighting levels that it was extremely hit-and-miss (mostly miss) and I ended up turning it off.
took a bit for the initial recognition but once that finished it worked flawlessly.
it takes less than a few seconds for me to unlock the phone. my friends couldn't unlock the phone with their faces but my dad, who i'm almost a carbon copy of, can unlock it. lol
mesasone said:
I tried it out, it works well for me. I found that if you took multiple images, including some from an angle that you'd actually be holding the phone when you unlock it (as opposed to just eye level), it unlocks very fast.
However, as I discovered today... it works a little too well maybe. I was showing the feature to my co-worker who just loves his voice commands, and then mentioned that, though it was a pretty neat feature, it could be cheated by using a photo. We decided to run a little experiment, using his phone (either a Droid or Droid 2) to take a quick snap of me and then seeing if it would work for face unlock off his screen. And it did... very well in fact. I was surprised at how well it worked off of a phone with a small, (relatively) low res screen, and crappy camera.
So, neat feature, not at all secure really.
Click to expand...
Click to collapse
That's why samsung tweaked this for the SGS 3 to require a "blink" to prove it's a live human (or a video).
yea, my brother and i look allot alike, but it wouldn't unlock for him (unless he did it with my picture). it has fast unlock response, but in low light, it doesn't work at all and just reverts to a secondary unlock method.
I got it working, but it took a while for it to recognize my face and took a long time to get the initial picture captured correctly. I just disabled it after that. No use for me really.
The key for sure is going into settings and improving recognition by taking multiple pics in different lighting,angles and distances. I took 10 or so and I am completely amazed a the speed even in low light.. I think the ops problem is it won't actually lock untill you restart or screen is off for specified minutes. I changed mine to immediate lock and as soon as screen is off it enables face unlock. I think default is 10 minutes. I tried this on my sensation and it was horrible, never worked. Works way better than I could have imagined on the hox.
Related
Hello,
Since it seems like no one has ever asked this question before I've decided to post about it.
On the Droid when you dial a phone number and put the phone up to your ear it locks the phone's screen. Then if you are dealing with a PBX or menu system on the phone that requires you to press a certain option and you move the phone away from your ear to tap the dialer, the screen automatically auto-unlocks. This is, by far, the best feature I have seen in a phone to-date.
Where do I get a dialer that supports that feature (it obviously uses the accelerometer)? Somehow I doubt you can just rip the APK out of the Droid image and have it work on a G1. Or does that feature just not work on the G1 for some reason?
Any replies are appreciated.
--Nickhttp://forum.xda-developers.com/showthread.php?p=6419439#post6419439
nbetcher said:
Hello,
Since it seems like no one has ever asked this question before I've decided to post about it.
On the Droid when you dial a phone number and put the phone up to your ear it locks the phone's screen. Then if you are dealing with a PBX or menu system on the phone that requires you to press a certain option and you move the phone away from your ear to tap the dialer, the screen automatically auto-unlocks. This is, by far, the best feature I have seen in a phone to-date.
Where do I get a dialer that supports that feature (it obviously uses the accelerometer)? Somehow I doubt you can just rip the APK out of the Droid image and have it work on a G1. Or does that feature just not work on the G1 for some reason?
Any replies are appreciated.
--Nick
Click to expand...
Click to collapse
The Droid uses a proximity sensor to tell when it goes up to your ear:
pocketnow.com said:
The Motorola Droid also has a proximity sensor so that the screen shuts off when you hold the phone close to your face. This helps to conserve battery life while at the same time prevent accidental screen input if your cheeks press upon the screen.
Click to expand...
Click to collapse
Not sure how you would do the same thing with the Accel.
That feature actually uses the proximity sensor, which the G1 unfortunately lacks.
jshealton said:
The Droid uses a proximity sensor to tell when it goes up to your ear:
Click to expand...
Click to collapse
Oh. That makes sense.
jshealton said:
Not sure how you would do the same thing with the Accel.
Click to expand...
Click to collapse
Not sure why it would be so hard. Accel can tell how it's positioned and the position next to your ear is completely different from that of holding your phone in front of you. It would just require some evaluation and data recording of degrees and ranges.
nbetcher said:
Oh. That makes sense.
Not sure why it would be so hard. Accel can tell how it's positioned and the position next to your ear is completely different from that of holding your phone in front of you. It would just require some evaluation and data recording of degrees and ranges.
Click to expand...
Click to collapse
Not sure about that. If I remember correctly the accell only sees if the phone is in landscape or portrait orientation, and when you are talking on the phone it is almost straight up and down. Not sideways. Will venture to find an answer.
Edit: You almost have to have the phone on its side for the accel to see that you have moved your phone. Don't know about you but when I talk on the phone it is almost up and down.
jshealton said:
Not sure about that. If I remember correctly the accellerometor only sees if the phone is in landscape or portrait orientation, and when you are talking on the phone it is almost straight up and down. Not sideways. Will venture to find an answer.
Click to expand...
Click to collapse
That certainly can't be since many games, namely Armageddon Squadron (flying game) use the X and Y axis on the phone (roll vs pitch). Also think of rolling objects in games that you have to "steer."
nbetcher said:
That certainly can't be since many games, namely Armageddon Squadron (flying game) use the X and Y axis on the phone (roll vs pitch). Also think of rolling objects in games that you have to "steer."
Click to expand...
Click to collapse
That may be true. I don't have any games on my phone that use the accel. I can only go by logcat durring screen orientation. I am sure you can now, the only problem is at what amout of tilt does the screen lock. And you would have to tie it in to when there is a call connected. Would hate for my sreen to auto lock when I am laying in bed playing with my phone.
jshealton said:
And you would have to tie it in to when there is a call connected. Would hate for my sreen to auto lock when I am laying in bed playing with my phone.
Click to expand...
Click to collapse
Well, of course it's connected to the dialer - that's its only purpose. If the dialer doesn't have foreground then it won't auto-lock.
If developing for Android wasn't such a pain in the ass (compared to C++) and I knew more Java classes/methods then I'd probably just implement this myself. I'll probably get the myTouch Slide soon enough though.
We wouldn't be able to so much measure the exact position to do this but a good shake-like-hell-to-unlock-dialpad event might be possible... If I (or someone) can find some code for a dialer, I'd be happy to take a stab at making it "native..." I know just enough Java/Android to cause some trouble, so it could only be good ;-) If not the dialer, then an app could be started as a service, with an intent to snag the call, and listen for a good jostling. I wonder what this would do to the battery/performance and how often I would have to make it poll the sensor? Hmm....
I'll see if I can poke around and find ANYTHING. Haven't googlified anything yet... I do need something constructive to add to my workload.
And yes, the accelerometer measures force applied to the X, Y and Z axis. you can technically program it to sense when you've dropped (or are dropping) the phone.
boredpcguy said:
We wouldn't be able to so much measure the exact position to do this but a good shake-like-hell-to-unlock-dialpad event might be possible... If I (or someone) can find some code for a dialer, I'd be happy to take a stab at making it "native..." I know just enough Java/Android to cause some trouble, so it could only be good ;-) If not the dialer, then an app could be started as a service, with an intent to snag the call, and listen for a good jostling. I wonder what this would do to the battery/performance and how often I would have to make it poll the sensor? Hmm....
I'll see if I can poke around and find ANYTHING. Haven't googlified anything yet... I do need something constructive to add to my workload.
And yes, the accelerometer measures force applied to the X, Y and Z axis. you can technically program it to sense when you've dropped (or are dropping) the phone.
Click to expand...
Click to collapse
try looking here.
http://github.com/cyanogen/android_packages_apps_Phone
edit: It should be possible, since it looks like a feature to "turn over to silence" has been implemented.
boredpcguy said:
We wouldn't be able to so much measure the exact position to do this but a good shake-like-hell-to-unlock-dialpad event might be possible...
Click to expand...
Click to collapse
I'm not sure if shaking my phone is really much better than tapping the screen twice - both require similar times for completion.
boredpcguy said:
If I (or someone) can find some code for a dialer, I'd be happy to take a stab at making it "native..."
Click to expand...
Click to collapse
Here's a tar.gz of the source-code that was released with the Droid https://android.git.kernel.org/?p=p...9af2e10e23c7c21f22abec5f3d7fa05d6406a2;sf=tgz
Not sure if it's still out and compatible with the newest builds, but the app Shake Awake did this quite some time ago.
Hairybroness said:
Not sure if it's still out and compatible with the newest builds, but the app Shake Awake did this quite some time ago.
Click to expand...
Click to collapse
I used to use this on android 1.1. iirc it stopped working on cupcake, and I haven't checked on it since then.
I don't think this would work, because what if you're laying down with the phone? I'm pretty sure it would mess up with the Accel. I'm not too much into this, but when playing a game like teeter for example, the side of your phone has to be horizontal with..the horizon (correct me if I'm wrong)
Dialer wake-up w/o real sensor
Shake Awake never worked too well for me.
I have always wondered in the back of my non-programmer brain if one who was really good could implement a sonar/feedback type code whereby when the phone was close to an ear, the amount of feedback from the earpiece to the mouthpiece was quite low, but drawn away from the ear increased just enough for the phone to pass through to the code through an intent (is there anything like a feedback intent? I bet Meltus would know!), which would issue the commands to unlock and wake-up.
More ideally would be a program which got the earpiece to put out a search tone up around 20 kHz, which would be analyzed by the mouthpiece. Sound present = user has moved the phone away from the ear, wake up and unlock to touchpad, sound muffled or totally gone = user is still using the earpiece, don't unlock.
BTW, all 2.1 eclair ROMs I've used in the past 3 months have a setting for a substantial improvement to screen awake times during calls.
There really should be a pinned thread for utter disappointed features and/or people.
I am not returning my new SW2. Its too cool to have the lamest, inept and funtion-killing GUI cause me to give up. ** But I bought a Pebble watch the same day because (the SW2n currently):
- can not function as a watch. It does but it goes to sleep VERY fast. WAY too fast. This is completely unacceptable. If I want to drain my f*ing watch and be able to read it all day, I should be able to!!! Put a warning on the settings area.. like: WILL DRAIN BATTERY VERY FAST or something...
- Can not finish reading my incoming sms. Maybe you dont know the girl I am dating but she WRITES A LOT... and this may not be normal amounts ... I really mean a lot. And SONY clearly has NO IDEA about this.
- AND continuing from the above point, it goes back to the f*ing CLOCK in sleep mode. SHOULD dim and remain on my screen until I SAY OTHERWISE. NOW I have to press the power button and NOT make it power off buy accident (another STUPID DESIGN) and make it activate, press the home button and then the stupid function messaging button. NO LOGIC FLOW HERE. I have to read 5 or 6 TXTs by now.
- CAN NOT read the messages in order without going BACK and opening the messaging app again. At least that seems to be what I had to do. I might have missed proper procedure here but if that is true, shame on SONY for lacking a more intuitive operation.
The Poweramp app is cool when it works. It should STAY active. I DONT CARE about anyone else or what slogan SONY wants to claim about battery life. I want FUNCTION my f*ing way. I use Poweramp all the time. But it is not able to stay on my watch, active? Total shame.
The ONLY app I kept on my watch is the custom watch faces. It allwos me to keep the display on until the dumbwatch, overthinking watch disconnects from my RazrMaxx/4.4 Dhacker29 ROM.
So in conclusion, This watch completely fails at being a watch. Fails at running apps because it times out WAY TOO FAST. Fails at every possible area other than fitting well.
Maybe your accelerometer is faulty. It should not timeout when on hand, actually it dims and always shows time.
Sent from my SM-N9005 using Tapatalk
jmaciak said:
Maybe your accelerometer is faulty. It should not timeout when on hand, actually it dims and always shows time.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I hate to be the guy to say it, but is the OP trolling us?
I have the smartwatch 2, just got it yesterday, and what the OP is saying makes no sense.
deitiphobia said:
I hate to be the guy to say it, but is the OP trolling us?
I have the smartwatch 2, just got it yesterday, and what the OP is saying makes no sense.
Click to expand...
Click to collapse
Well it can timeout and go totally blank ... try it, put them on the table and do not move the watch/table and it will dim and then go completely blank after a while, because the accelerometer sees it's not on the hand. So if OP's accelerometer is faulty, it might behave this way ...
jmaciak said:
Well it can timeout and go totally blank ... try it, put them on the table and do not move the watch/table and it will dim and then go completely blank after a while, because the accelerometer sees it's not on the hand. So if OP's accelerometer is faulty, it might behave this way ...
Click to expand...
Click to collapse
I am not a troll. At least I am not trying to be a troll. I do feel slightly underwhelmed buy my experience so far.
And maybe my accelerometer needs checking? If it is supposed to remain on (the screen) for more than 5 seconds when I am wearing it and trying to read something, then yes, something is wrong. Maybe the watch doesnt know when it is on a troll arm?
deitiphobia said:
I hate to be the guy to say it, but is the OP trolling us?
I have the smartwatch 2, just got it yesterday, and what the OP is saying makes no sense.
Click to expand...
Click to collapse
Hello,
What he is saying actually makes perfect sense, especially on this forum - we are not the average, marketing-targeted user and we like to use our devices any way we please, without being limited by design hickups. And we are more sensitive to design flaws and marketing bs than the average consumer.
Sony missed and even lied about basic features and is not allowing, at least so far, anyone to tweak with this product's FW.
In my experience the watch proved very useful ONLY IF YOU ARE NOT RELYING SOLELY ON IT for most of your work - i, for one, would not like to read my correspondence on such a tiny screen and prefer to use the phone instead - but it would sure be nice to know that I CAN use the watch if i wanted to.
Fortunately, while driving a motorcycle, for example, getting a hint of the message content usually suffices for me to determine if i need to pullover and get my phone out, provided i get to see the screen before it times-out, which is another awkwardly missing basic function.
I will, however, hold on to the SW2 for now in hopes that Sony will straighten things the way they should.
Sent from my LT25i using Tapatalk
i agree fully with the OP as well
if i didn't know better, i would suggest posting your opinions on talk sonymobile, but as i already did that and got NO reply from Sony, i guess it would be just a waiste of time
that's my biggest problem with Sony right now: no communication
(although i must admit most manufacturers suck at communicating with their customers, try finding out when the Butterfly s is getting 4.3/4.4, not a chance)
I actually agree with the OP, there are some features that could be included in the settings menu like timeout duration or stopping the watch default to the watch screen every time it goes into standbye especially useful if travelling and using features like poweramp - you need 3x button presses to bring the poweramp screen back on and if you have a messaging app open (reading messages) it should prevent the watch from sleeping
and how fecking hard is it to develop a few watch face designs with different colours etc
TBH I think Sony are in the process of designing a totally new Smartwatch for release in early 2014 and have completely dropped the ball with this one
well, there was an update today, so i guess they didn't drop it completely
update looked good at first, but disappointing anyway
-only 1 extra watch face that's usable, i still want the abilty to design/choose my own watch face
-the option to use the light sensor for brightness is nice, but i'm glad it's optional, don't like it
-music app update totally messed it up (used to work for me)
-camera app update didn't do anything for me, still does nothing
-still no selectable timeout, huge issue for me
---------- Post added at 06:47 PM ---------- Previous post was at 06:36 PM ----------
Find It for SmartWatch by AQ i purchased also doesn't work anymore
argh, their own Find Phone Smart Extension ALSO doesn't work anymore!
JarlSX said:
their own Find Phone Smart Extension ALSO doesn't work anymore!
Click to expand...
Click to collapse
AFAIK I suspect that problems might occur pairing the SW2 with a non-Sony smartphone.
But please let's keep the discussion in one place only, so we can better compare these findings:
http://forum.xda-developers.com/showthread.php?t=2554874
i think i know why the watch can't dim while still displaying an app
those apps don't really run on the watch, they're just displaying what's happening on the phone (that's where the app is installed)
so for a watch-app to work, the watch is constantly communicating with the phone
such a connection will probably drain the watch very quickly
only the watch part can run independently, so that's why it always goes back to that screen, to save power
this is of course just what i think
FWIW, the screen on time can be controlled by the app. I use and app called IPBike for cycling which runs on the phone. This app allows you to use the watch as a head unit on the bars. It has an option to keep the watch screen on for the entire ride.
jmaciak said:
Well it can timeout and go totally blank ... try it, put them on the table and do not move the watch/table and it will dim and then go completely blank after a while, because the accelerometer sees it's not on the hand. So if OP's accelerometer is faulty, it might behave this way ...
Click to expand...
Click to collapse
Should it really go totally blank/black? Mine is only dimmed out and showing clock face all the time, but really dimmy. And it is on the table...
Oh it does, took some time, longer than i expected...
Sent from my GT-N8000 using Tapatalk 4
Since I got the phone, while in pocket, I reject/answer 80% of the calls. I was under the effect of "yay nexus is back, google finally gave us a cheapster" so didn't really got bothered. But days are passing by and it's getting quite annoying, so to the point, could anybody tell me why this phone wakes up the screen on incoming calls when the proximity sensor is covered (ie. in pocket?) (if it's "normal" to do so, then why?). Proxi switch is fine, it triggers during calls and shows activity on sensor testing apps and whatnot. Default calls screen and whatsapp incoming calls, (heck I can unlock the phone with the fingerprint reader in my pocket without taking it out, now explain that.) ... Cherry on top the "slide to answer" thingy is vertical, so yeah there is the problem (while sliding it out from the pocket, it answers or rejects the call). I'm considering throwing it out lol it's so annoying lately. Android 9 was the same? (I had 3 android one phones to fill the superexpensive 3 generation pixel gap) Was I living under a rock? Can anyone try it? Thanks for the helpful inputs in advance.
strapabiro said:
Since I got the phone, while in pocket, I reject/answer 80% of the calls. I was under the effect of "yay nexus is back, google finally gave us a cheapster" so didn't really got bothered. But days are passing by and it's getting quite annoying, so to the point, could anybody tell me why this phone wakes up the screen on incoming calls when the proximity sensor is covered (ie. in pocket?) (if it's "normal" to do so, then why?). Proxi switch is fine, it triggers during calls and shows activity on sensor testing apps and whatnot. Default calls screen and whatsapp incoming calls, (heck I can unlock the phone with the fingerprint reader in my pocket without taking it out, now explain that.) ... Cherry on top the "slide to answer" thingy is vertical, so yeah there is the problem (while sliding it out from the pocket, it answers or rejects the call). I'm considering throwing it out lol it's so annoying lately. Android 9 was the same? (I had 3 android one phones to fill the superexpensive 3 generation pixel gap) Was I living under a rock? Can anyone try it? Thanks for the helpful inputs in advance.
Click to expand...
Click to collapse
There is no pocket mode on stock firmware. If you'd like to add one you can use Edxposed and the dark tricks module.
Sent from my Google Pixel 3a XL using XDA Labs
As hard as I'm trying, I start to see it's nearly impossible to be completely satisfied with the stock android experience. I gave up rooting, flashing, modding long time ago. Ain't got time for that. This leaves one choice, a sad but with time will get used to it.
strapabiro said:
As hard as I'm trying, I start to see it's nearly impossible to be completely satisfied with the stock android experience. I gave up rooting, flashing, modding long time ago. Ain't got time for that. This leaves one choice, a sad but with time will get used to it.
Click to expand...
Click to collapse
Do all 3a do this? I am looking into buying one but don't want to deal with something like that. This is exactly the reason I decided not to buy Galaxy S10e - just try to Google "S10 proximity sensor". It was never officially acknowledged/fixed by Samsung and over the time people just seem to "get used to it" and stop talking about it.
I don't know mate, that's why I asked others to try it please, it's really getting on my nerves and funny thing is, these kind of problems are a hit or miss on warranty claims ... doesn't even worth to try ... and I don't want to take this to reddit either because it'll only get downvoted to a lower than hell level by biased fanboys not to mention the google product forums with the "platinum product experts" and their generic "try this and try that" answers.
So yeah I'm angry.
strapabiro said:
I don't know mate, that's why I asked others to try it please, it's really getting on my nerves and funny thing is, these kind of problems are a hit or miss on warranty claims ... doesn't even worth to try ... and I don't want to take this to reddit either because it'll only get downvoted to a lower than hell level by biased fanboys not to mention the google product forums with the "platinum product experts" and their generic "try this and try that" answers.
So yeah I'm angry.
Click to expand...
Click to collapse
I never had issues, but probably I don't understand the issue yet, so I have a question: how do you know screen is waking up in pocket? For sure it's waking up if you move the device, i.e. take is off the table or turn it around. Are you sure screen switches on in the pocket and not while you are taking it out?
AndDiSa said:
I never had issues, but probably I don't understand the issue yet, so I have a question: how do you know screen is waking up in pocket? For sure it's waking up if you move the device, i.e. take is off the table or turn it around. Are you sure screen switches on in the pocket and not while you are taking it out?
Click to expand...
Click to collapse
You can test by trying to unlock the device while covering the proximity sensor.
Without any mods it'll unlock.
But like that's the main benefit to a Google phone running stock firmware. It's a perfect base for mods.
Sent from my Google Pixel 3a XL using XDA Labs
Skittles9823 said:
You can test by trying to unlock the device while covering the proximity sensor.
Without any mods it'll unlock.
But like that's the main benefit to a Google phone running stock firmware. It's a perfect base for mods.
Sent from my Google Pixel 3a XL using XDA Labs
Click to expand...
Click to collapse
This ... Or cover like 80% of the screen, leave only a small bar uncovered on the lower part of the phone (usbc port side) and ask someone to call you. You'll see on the remaining uncovered part that the screen woke up which is hilarious. Honestly at this point I don't understand how a feature like this can be overlooked by r&d.
Sadly modding is no option for me, for safety and other reasons.
There is another thread about this in the 3a xl section, hope it doesn't count as duplicate.
strapabiro said:
Sadly modding is no option for me, for safety and other reasons.
Click to expand...
Click to collapse
What reasons? This is a Google phone. You're allowed to unlock the bootloader and flash modified software without breaking warrantee.
If you have issues, it's easy to just flash the factory image back to completely stock and relock the bootloader.
Sent from my Google Pixel 3a XL using XDA Labs
@strapabiro,
Have you tried this app?
Skittles9823 said:
What reasons? This is a Google phone. You're allowed to unlock the bootloader and flash modified software without breaking warrantee.
If you have issues, it's easy to just flash the factory image back to completely stock and relock the bootloader.
Sent from my Google Pixel 3a XL using XDA Labs
Click to expand...
Click to collapse
You're shifting the subject, but the short answer is, imagine I never had an apple product in my life but I rather buy an iphone than start doing that But that's me and that's another topic like I said, thanks though.
strapabiro said:
You're shifting the subject, but the short answer is, imagine I never had an apple product in my life but I rather buy an iphone than start doing that But that's me and that's another topic like I said, thanks though.
Click to expand...
Click to collapse
Fair argument.
Sent from my Google Pixel 3a XL using XDA Labs
Today I had my phone in my coat pocket at an appointment for about an hour hanging on a coat rack not even being touched. When I came back to, the screen was on, on the lock screen, and if was pretty warm with battery down a good 25 percent. I'm wondering if what you're talking about here has something to do with this? I was confused why or what was going on with it. No unusual apps were in memory in developer settings.
kc6wke said:
@strapabiro,
Have you tried this app?
Click to expand...
Click to collapse
I have found this "feature" annoying as well on my 3a XL. However I tired the app that you suggested and it seems to work fine. Thanks for providing a decent solution to the OPs question.
My fingerprint reader keeps disabling. I have to turn phone off and back on (reboot is not enough). However then all the apos detect a Biometrics change and I have to reenable fingerprint login for each app.
Even when it works the reader is super sensitive and keeps telling me I've had too many attempts before i pick up the phone.
While I do get the too many attempts thing I haven't had the fingerprint reader disable on my phone
For me its working just perfectly.
It works perfectly for me as well. I have found that using a case helps a lot with false reading attempts.
I also use a slim case and I'm having a very positive experience with the fingerprint reader.
Coming from a Pixel 2 XL with a reader at the back, it took me a few days to get used to thumb based unlock.
But now, I find it much more reliable than the Pixel 2 XL reader, where fingers moisture was a real pain.
Same hands (different finger being used on the 5ii and it works almost 100% of the time (and quick too).
Stock ROM and launcher.
arturiu said:
I also use a slim case and I'm having a very positive experience with the fingerprint reader.
Coming from a Pixel 2 XL with a reader at the back, it took me a few days to get used to thumb based unlock.
But now, I find it much more reliable than the Pixel 2 XL reader, where fingers moisture was a real pain.
Same hands (different finger being used on the 5ii and it works almost 100% of the time (and quick too).
Stock ROM and launcher.
Click to expand...
Click to collapse
What case are you using?
also my fingerprint sensor is absolutely flawless I haven't had any issues or anything that has caused me to be concerned or despised the fingerprint sensor. maybe I'm lucky or maybe I just knew how to set the fingerprint up properly I don't know but my experience with it has been positive
thepersona said:
What case are you using?
Click to expand...
Click to collapse
https://www.amazon.co.uk/GEEMEE-Waterproof-Anti-Scratch-Protective-Transparent/dp/B08H5931YQ
arturiu said:
https://www.amazon.co.uk/GEEMEE-Waterproof-Anti-Scratch-Protective-Transparent/dp/B08H5931YQ
Click to expand...
Click to collapse
Damn it doesn't appear that that case is available in Canada or even the US. Oh well hopefully more cases turn up when the device releases in the US
Try adding the same finger a few times. I haven't had any problems since I did that.
Do you also have this issue, that while calling, you accidentally click on the fingerprint sensor and so activate the screen while it is 'at your ear' and so you 'click' on several options and so on? It happens a lot, I have accidentally adjusted with my ear the brightness or paused the call etc. Very annoying!
I struggled a bit at first to have my fingerprint recognized when trying to unlock, often ending up typing my pin instead.
I noticed a huge improvement by sliding my thumb upwards on the sensor, instead of just pressing it still. Now works almost all the times.
November update might have improved the situation as well.
Not sure if it's something to do with a recent update but my reader is not recognising my fingerprints very well at all now. Anyone seen problems?
The other potential issue is that I've been doing a lot of DIY lately and probably worn away some of the detail on my finger ends .
wazzaworld said:
Not sure if it's something to do with a recent update but my reader is not recognising my fingerprints very well at all now. Anyone seen problems?
The other potential issue is that I've been doing a lot of DIY lately and probably worn away some of the detail on my finger ends .
Click to expand...
Click to collapse
Mine still on 58.0.A.22.21 as it's US variant but recently I am also facing issues with fingerprint scanner if the phone is in (deep?) sleep mode. Earlier it used to be just touch and go but now had to press it or try multiple time to unlock it.
Not sure what's the issue here?
No problems with my FPR. Occasionally it requires a couple of tries but that's true of every single phone on the market.
Mine seems to be working well. I am coming from a P30 Pro with the underscreen sensor, and I had a few Xperias before that. This is by far the fastest Android fingerprint sensor I've used. it seems to instantly recognize everything. It's probably on par with my pre-face ID iPhones, but i don't have one of those anymore to compare it.
I ended up disabling the fingerprint reader completely. Never works from first try when I need it, but somehow easily unlocks when I actually don't need it, as in when just holding it, putting down or in pocket. Also all those buttons on the same side is a really poor design choice, specially power right under volume. Btw, is there a way to disable the assistant button?
hovikg said:
I ended up disabling the fingerprint reader completely. Never works from first try when I need it, but somehow easily unlocks when I actually don't need it, as in when just holding it, putting down or in pocket. Also all those buttons on the same side is a really poor design choice, specially power right under volume. Btw, is there a way to disable the assistant button?
Click to expand...
Click to collapse
Everything I have read, says there's no way to disable it. I'm very surprised I have yet to activate accidentally. But, that might be because the button covers on my case are kind of stiff.
hovikg said:
Never works from first try when I need it, but somehow easily unlocks when I actually don't need it, as in when just holding it, putting down or in pocket.
Click to expand...
Click to collapse
I get the exact same behavior. Very frustrating. Totally disappointed with the fingerprint scanner.
hovikg said:
Btw, is there a way to disable the assistant button?
Click to expand...
Click to collapse
You can disable the assistant app. But if course this is only a solution if you don't use the Google assistant at all.
My favorite fingerprint reader was the Pixel 3 with the reader on the back of the phone. My least favorite has been the under-screen readers on my Huaweis. The reason is less accuracy and fingerprints.
I've had my Xperia 5 ii for a day, and have been on it a lot, and the fingerprint reader has been excellent. My problem is finding it and not dropping the phone while I look.
Hi everyone!
Just purchased a P6a during Black Friday. In general I am quite happy with the device and would want to keep it.
However, I have massive issues with crashes/freezes/reboots when using the camera.
I know that many people have reported similar issues, but my case is somewhat special in that it only happens on weekends. During the work week, I use the camera normally, and there has not been a single crash.
But when I go hiking/mountaineering/trailrunning on the weekends, I have massive problems.
I would say, every five photos I take, something goes wrong.
Sometimes I get a complete freeze in the camera app and have to do a hard reboot.
Sometimes, the phone simply reboots itself.
Sometimes it switched itself off.
Sometimes, the camera app seems to work correctly, but then a few minutes later the phone reboots all by itself.
Sometimes, these crashes result in broken, unreadable JPG photos on my phone.
This has happened up to ten times on each of my outdoor tours. I have observed this now over three weekends, on four different tours. After such a crash/freeze/reboot, the phone seems to work completely normally again, as long as I do not use the camera app. As soon as I use the camera app again, it does not take long until the problem reappears. But only as long as I am outdoors for extended periods of time. Indoors never any issue.
The natural suspicion is that it must have something to do with the temperatures outside. But temperatures here in late autumn Bavaria have not even been all that cold; the problems already occur at relatively moderate temperatures of a few degrees above freezing.
Software is fully updated, of course.
Because of the 100% clear correlation with outdoor activities of a certain minimum length, which I can only interpret as temperature dependency, I guess this must be a hardware defect, and I should ask Amazon for a replacement. But what do you guys think? What would you do? Is there any diagnostics I can do first?
Thanks a lot!
Locked bootloader still? Are you planning to unlock, or open to it? I would recommend doing so and doing a complete clean flash of the latest stock to both slots. Sometimes OTA's arent as complete as we like to think.
If you dont want to unlock the bootloader then I would at least do a factory reset, if you already havent.
Have you done anything to rule out everything else? Like are you positive that it's because of the temperature?
Maybe it's got something to do with cellular connectivity or GPS?
You could try removing your SIM/entering Airplane mode, and/or turning GPS off, and going outside, see if the issue persists?
Thanks for the responses!
No, I am currently not planning to unlock the bootloader. (Maybe I will, once the phone is 2 years old and the implied warranty has expired, but not now.)
Yes, I could do a factory reset. Is there a good non-unlocked way to backup everything I have already setup and configured?
No, I have no way of being completely sure that it is the temperature. Your idea that it might be linked to GPS is an interesting one. After all, I had the geotagging feature of the camera app enabled. I switched this off now, let's see if the problem occurs again.
Problem is, I can only test it on weekends. Being outdoors for only an hour or so has never been enough to trigger the problem. It had to be a longer stay outdoors of a few hours at least, and that I can only do on weekends.
rhhd said:
Maybe I will, once the phone is 2 years old and the implied warranty has expired, but not now.
Click to expand...
Click to collapse
Pretty sure that you can just flash the stock ROM, re-lock bootloader, and they won't know/bat an eye.
---
Could you leave your phone outside for a few hours? Instead of going on a hike?
From what I've gathered from OP and your reply above is that your phone starts acting up if it's been out in the cold for a while and you open the camera app. You might wanna leave it in the cold for a bit, wait for it to cool down to ambient temperatures, then try to open the camera app? If it still acts up, then we can be more certain that it's got nothing to do with geolocation, but with the cold temperature.
Good idea! I'll try that tonight and put it on my balcony for a few hours.
I suppose it could also be the fact that it get's moved/shaken more when I am moving on my outdoor tours...
rhhd said:
I suppose it could also be the fact that it get's moved/shaken more when I am moving on my outdoor tours...
Click to expand...
Click to collapse
Or maybe changes in altitude? Although, I don't know if you're that hardcore at hiking or not
Anyway, leaving it on your balcony could help narrow down the source of the issue.
I don't think it is changes in altitude, because one of the tours was just a trailrun in only hilly terrain with maybe only 200 meters of altitude difference between highest and lowest point, and even on that tour I had massive issues.
rhhd said:
I don't think it is changes in altitude, because one of the tours was just a trailrun in only hilly terrain with maybe only 200 meters of altitude difference between highest and lowest point, and even on that tour I had massive issues.
Click to expand...
Click to collapse
Do you keep your device in your pocket? If so, it wouldn't be able to get too cold.
When running, it is in a mesh pocket of my running vest, so it would get quite cold. On mountain tours it is usually in an outside pocket of my pants. So yes, close to my body, but still some isolating layers away from my body.
Other question, now that we are talking shaking as a possible cause:
When you shake your phone in front of your ear, with the camera module facing towards your ear, do you hear something? I can definitely hear something shaking, as if a tiny metal part is loose inside the phone.
I keep my bootloader locked. Each month when there is an update I unlock the bootloader and update the phone in case something goes wrong. Once I've successfully updated my phone I relock the bootloader which just requires a reboot. Unlocking and relocking the bootloader does not delete data.
rhhd said:
When you shake your phone in front of your ear, with the camera module facing towards your ear, do you hear something? I can definitely hear something shaking, as if a tiny metal part is loose inside the phone.
Click to expand...
Click to collapse
Yup. Super faintly.
When having a camera app open, it definitely sounds like what you were describing. My best guess would be the OIS trying its best to keep everything stabilized.
xrayA4T said:
Unlocking and relocking the bootloader does not delete data.
Click to expand...
Click to collapse
Does it void warranty though? Like what's Google's warranty policy here? Does unlocking the bootloader once void it already?
Lada333 said:
Yup. Super faintly.
When having a camera app open, it definitely sounds like what you were describing. My best guess would be the OIS trying its best to keep everything stabilized.
Click to expand...
Click to collapse
No, I don't mean the OIS sound. I can also hear that one (very very faintly) when the camera app is open and I move the phone. (Sounds like a tiny tiny motor whirring a little.)
But the little clattering that I mean can be heard always, even when the screen is off. Sounds like a tiny screw is loose or something. It is also clearly audible, not nearly as faint as the OIS whirring.
Lada333 said:
Does it void warranty though? Like what's Google's warranty policy here? Does unlocking the bootloader once void it already?
Click to expand...
Click to collapse
No, it's not like you are flashing a custom ROM (which I'm pretty sure doesn't void the warranty in the US or Europe). It just allows you to flash a full ROM, not just an OTA. Google has provided this functionality. There is not warning when unlocking that this will void the warranty.
rhhd said:
Sounds like a tiny screw is loose or something. It is also clearly audible
Click to expand...
Click to collapse
When I shake my phone "front to back," I hear that. Only when the camera app isn't open though. When I open it, I cannot replicate the sound.
rhhd said:
No, I don't mean the OIS sound. I can also hear that one (very very faintly) when the camera app is open and I move the phone. (Sounds like a tiny tiny motor whirring a little.)
But the little clattering that I mean can be heard always, even when the screen is off. Sounds like a tiny screw is loose or something.
Click to expand...
Click to collapse
Interesting. That seems to be a third sound. Yes, I also have that one, and just as in your case it goes away when the camera app is open.
But the sound I mean is independent of the camera app, and also occurs when shaking the phone side-to-side.
OK, the test results are in:
On Tuesday, I left the phone out in the cold on my balcony for 2,5 hours, and yes, afterwards the problems did occur.
On Wednesday, I used the phone indoors, no issues. A new camera app update was installed, I hoped this might be the fix.
But no: On Thursday, I again put the phone outdoors for 2,5h. The problems are back.
I will ask Amazon for a replacement.
Thanks a lot for your suggestions!
rhhd said:
OK, the test results are in:
On Tuesday, I left the phone out in the cold on my balcony for 2,5 hours, and yes, afterwards the problems did occur.
On Wednesday, I used the phone indoors, no issues. A new camera app update was installed, I hoped this might be the fix.
But no: On Thursday, I again put the phone outdoors for 2,5h. The problems are back.
I will ask Amazon for a replacement.
Thanks a lot for your suggestions!
Click to expand...
Click to collapse
That's so strange!
I'd love to know what actually triggered this odd issue.
I mean, yeah, surely, something to do with cold temperatures, but that in itself doesn't explain a lot, does it?
I hope your replacement device won't have any issues!