Related
Hi all,
troubleshooting for a girl with a Bionic; replaced cracked glass/digitizer for her and updated to JB via the OTA update, but her proximity sensor is flaking out.
I've installed a few Prox. Sensor reporting apps to see what values it's putting out: it reads 3cm most of the time, and 100cm when swiping down the notification bar. (100cm is max range, which I assume is a placeholder for a no-report state in the phone, not sure what it has to do with the notification bar.)
Problematic behaviour is that the screen turns off almost instantly after placing a call, and won't come back on except by swiping down (on the blank screen) to pull down the notifications, which temporarily disables the sensor. (it lasts long enough to get ~1 keypress on the keypad, which is *not* a usable workaround even for checking voicemail.)
I'll take the phone apart again and make sure there's nothing in the way of the prox. sensor, as that seems the most likely cause... but any guesses or similar reports from anyone about possible bugs in the firmware update? Any proximity sensor calibration apps for this hardware I'm not seeing in the marketplace, or ROMs that expose that functionality? (I wasn't planning to root the phone, but she won't know the difference if I need to. Was hoping to avoid safestrap to simplify the boot procedure and not interfere with future OTA updates, but warranty is gone already so it's not a big deal if I need to install something new.)
Hi!
I am facing problems with the orientation sensors (accelerometer and/or gyroscope), because installing several applications to test them (or use games), it is clearly observable, that they are a bit off (with enough to be disturbing when required). For example, games or tests that simulate a ball, and my phone is laying on a horizontal table, the ball rolls quickly to the edge of screen. This happens as well with the built-in tests in the "service menu" of the phone, for accelerometer and gyroscope also.
Do you have any suggestions how could I calibrate these sensors globally (for every app)?
Thanks.
Info
vetko said:
Hi!
I am facing problems with the orientation sensors (accelerometer and/or gyroscope), because installing several applications to test them (or use games), it is clearly observable, that they are a bit off (with enough to be disturbing when required). For example, games or tests that simulate a ball, and my phone is laying on a horizontal table, the ball rolls quickly to the edge of screen. This happens as well with the built-in tests in the "service menu" of the phone, for accelerometer and gyroscope also.
Do you have any suggestions how could I calibrate these sensors globally (for every app)?
Thanks.
Click to expand...
Click to collapse
factory Reset ur phone and then use PC companion app to Repair Firmware...
this can wipe current data and install fresh firmware on ur device
:good:
Hi,
I have the same problem. Only the x axis of the accelerometer seems to be affected : it show a value around 1 instead of 0 while the phone is sitting flat. Y and Z display normal values.
All the software solutions I have tried have had no effect at all... It seems the built-in test reads raw data from the accelerometer. It is hard to imagine how this can be a hardware problem though...
Anyway, in my case I believe a software fix (x=x-1) would do the trick but I have no idea how to do such a thing ! Any help ?
@vekto : Have you solved the issue by any chance ?
Would anyone care to try the accelerometer tests and post their results ?
Typing *#*#7378423#*#* will get you on the service menu. The two significant tests are "accelerometer" and "gyroscope".
I'd post some screenshots myself but I'm not allowed yet...
I'm having the same problem now. It seems one axis is affected. Haven't found a way around so far. This is sad because it affects the images taken with Google Camera Sphere mode. The images are badly aligned together with glitches in between. My phone wasn't like this before.
Either a SW fault - might be able to calibrate with GPS Status & Toolbox app, for example - or a FW fault - and reflashing ROM might help (highly unlikely) - or HW fault - the sensor has moved on the board (which is a bad sign anyway, might be on the way to disconnecting itself).
I sent mine to Xperia Care and got it back with the accelerator fixed. Still unclear if it's a HW problem...
It came back with a white spot on the screen (near the power button) though... so I sent it back again
I'm also having issues with the gyroscope. Installed Bubble app to calibrate the gyro. It showed the gyro was of a couple of degrees. Unfortunately the bubble app calibration doesn't work in a game like Need for Speed. It's very difiicult to achieve good times in the game right now since I have to hold it tilted to the left to go straight ahead.
So if anyone has a fix or workaround... Please do post.
Same problem, Seems after factory reset whith wipe dalvik cache.
any solution?
02nd March 2017, my autorotate has completely stopped working, restart, safe-deposit and reset do not fix. Diagnostics show Gyroscope Light Sensor and accelerometer failed testing, 3 years of same issue, surely there must be a fix that works by now?? ( please note, " turning it off and on again " does not fix it )
Helps Please
I have the same issue. Since last week, gyro, accelerometer, light and proximity sensors stop working. I've tried reflashing stock ROM without success. I have not warranty (almost 3 years old), so I even try to disassemble , disconnect an reconnect every flex (I don't know exactly were the sensors are located on the board). After that I get almost 8 hours of fully functionally sensors and then, they stop working again, so I'm almost sure it's a hardware issue.
Same problem for 3 years
I'm just now getting around to doing something about this. As my power button stopped working I can't post requested screenshot without going to the pc. I have been shopping new (fall 2018) phones after having the Z3+ since release. In my research I'm finding the phone still is better than Samsung, LG, and the pixel3 for me because the 3.5mm phone jack is mandatory for me using my device with an i-rig midi requiring both that port and the USB at the same time. I'm going to do everything I can to keep using this phone till it falls to dust. It's one of 4 Sony I've bought since the day Z1 came out of t-mo. I look forward to testing solutions. :good:
Some time after my post, I bought a new jack/proximity sensor flex and replace it. This solved the issue, but weeks later, the bottom portion of the touch screen becomes unresponsive. May be I have done something wrong... may be programmed obsolescence...
Hi I'm facing a problem of my gyroscope I don't know which one is not working a gyroscope or accelerometer. My gyroscope is so delay when I play pubg mobile and I can't also calibrate my Gsensor it always says FAIL but I put in a perfect flat surface please please please help me with this problems
Hi,
I've started this poll for ALL owners of the LG G Watch R.
The question is: does your G Watch R flicker after charging it to full 100% when you take it off the charger?
After selecting yes or no on this poll, can you check your build number on your watch and post it here?
If you post the info, please also note if your watch does flicker or not to keep the results clean.
something like this:
Does flicker:
Software version: 5.0.1
Build number: LWX48P
Serial starting with: 412KPGS0139XXX
or
Does not flicker:
Software version: 5.0.1
Build number: LWX48P
Serial starting with: 412KPGS0139XXX
What I'm trying to figure out by starting this poll, is if it's hardware related or not.
To check your build:
Go to "Settings" on your watch.
Then press "About".
in the about section you will find the following info:
Software version: 5.0.1 (This will change after a new update.)
Build number: LWX48P
Serial starting with: 412KPGS0139XXX (Just replace last 3 digits with XXX, we don't need to know your exact serial number.)
Above info is from my own LG G Watch R.
Thanks for participating
Treborov.
Results so far:
All watches posted so far have Build number: LWX48P. I wonder if there are other build numbers out there? If anyone has a different build number please post it here
Serial ranges: 410KP series, 411KP series and 412KP series.
Everyone so far is running software version 5.0.1 (Which is the latest update.)
Remarks by users about what might cause the flickering effect:
Screen brightness settings: 1x
(Google calendar event) notifications: 1x (Could be any notification because I had the same problem with multiple notifications that all tried to pup up at once)
Watchmaker app: 2x (installed on 2 watches that have the flickering effect.)
Hardware related:
Loose display ribbons: 1x
I have had the snow-crash in one and the flickering in my second watch, now on my third. that one seems all right at the moment. what makes me suspect hardware in stead of software is that the LG G, does not show this problem. and both are technically quite close related.
If my watch shows the flickering again, i will partake in your experiment, as i am quite curious as to what is causing this. I also noticed the much brighter flickering as brightness was down to 1.
As i read the posts concerning this problem, i also noticed that the part that flickers is not always the same, on my watch it was the lower half blinking, others have mentioned the upper half.
It still reminds me of what a led does when power goes below a certain threshold.
Good luck in your project!
RoosW said:
I have had the snow-crash in one and the flickering in my second watch, now on my third. that one seems all right at the moment. what makes me suspect hardware in stead of software is that the LG G, does not show this problem. and both are technically quite close related.
If my watch shows the flickering again, i will partake in your experiment, as i am quite curious as to what is causing this. I also noticed the much brighter flickering as brightness was down to 1.
As i read the posts concerning this problem, i also noticed that the part that flickers is not always the same, on my watch it was the lower half blinking, others have mentioned the upper half.
It still reminds me of what a led does when power goes below a certain threshold.
Good luck in your project!
Click to expand...
Click to collapse
Thanks for leaving a comment, I did read all your comments in the other post about you sending your watch back to LG.
So you're on your third LG G Watch R now right? Not exchanged it for an LG G Watch?
If you got another Watch R. would you mind posting the build number?
Let's just hope your 3rd watch doesn't go all "disco" on you like the other two
Disco time haha. Half of the screen flickers, same as the OP explained. Really annoying, happened 2x already within 3 weeks of owning the watch
Does flicker:
Software version: 5.0.1
Build number: LWX48P
Serial starting with: 411KPZK0129XXX
Software : 5.0.1
Build : LWX48P
Serial starting with : 411KPPB
---------- Post added at 16:39 ---------- Previous post was at 16:32 ----------
So you're on your third LG G Watch R now right? Not exchanged it for an LG G Watch?
Click to expand...
Click to collapse
I had a Pebble before i had an LG G, my wife now has that one, i decided to stay with the LG G R, because the recessed screen helps in preventing random contact with my sleeve (thus interrupting the music playing on my headset), and i like its looks a lot more then the LG G, the screen above the bezel like the 360 has, is why i did not got that one (besides the poor hardware and battery) until someone writes an app that kills the touchscreen until the crown is pushed once or say 2 times, all other options are just to annoying
Hmmm.. 2 days straight of flickering every morning when I tried to check the watch right after I wake up.
I noticed that after I restart the device, a Google calendar event notification will pop up. Then the flickering will stop
Looks like a Calendar Event notification bug in Android wear, could someone confirm this?
Update : It flickers again, no calendar event notification. Maybe this is a hardware problem
Sent from my Nexus 5 using XDA Free mobile app
Does flicker:
Software version: 5.0.1
Build number: LWX48P
Serial starting with: 410KPVH0010XXX
thought the 5.0.1 solve the flicker but it came back after few days
O.K. Update on my watch.
I did a factory reset yesterday on my LG G Watch R.
I haven't touched the watch as in, changing face plate installing software etc.
This morning when I took it off the charger it didn't start flickering like it did the last two days. (So it was working as it should.)
Things I had installed on my watch when it was flickering: (before factory reset)
Multi Calculator
Instaweather app.
Intellicom Watch faces app.
Luxury watch faces app.
WatchMaker free app.
Facer app.
After factory reset, the only thing that automatically popped up on my watch when I checked watch faces, was the Facer app. The rest of the apps wern't showing on my watch anymore.
However, I didn't uninstall those on my phone.
I uninstalled the Facer app on my phone.
After checking the Watch Face options this morning, all the installed programs are back on my watch.
It seems they all got synced again between my phone and my watch.
Maybe I checked to soon yesterday after the reset and these programs weren't synced yet.
I'll take a closer look after next factory reset.
Thanks everyone who has participated so far in this thread :good:
@unclebor
In your app list, we only have 1 common app installed.
I also installed watchmaker, and as far as I remember the flickering started after i installed that! I will uninstall watchmaker and delete the data folder because I already tried uninstalling it but the data folder was not deleted.
Hopefully this is the culprit, if not maybe this is a hardware issue.
Sent from my Nexus 5 using XDA Free mobile app
The flicker is most likely due to a loose display ribbon connector and stops after a while because the watch warms up, the connector expands and makes better contact, but it will remain intermittent since it's not pressed all the way in. You need to open the watch and press in all the connectors (there are 4) and the flicker will likely stop.
For the record, I'm on 5.0.1, LWX48P, 411KPSL0096XXX, no flicker.
Mine does the same with LWX48P. It happends since i started using it with always On screen. Can we return it and exchange to a new one? I like pebbles warranty since they have issues about flickering screens too. Returned and sent me a new one.
Since update 5.0.1 the display flickers sometimes after fully charged. Power off and power on the watch helps for me (no reboot!)
Software version: 5.0.1
Build number: LWX48P
Serial starting with: 410KPNY0036XXX
cheers
Manfred
Update on my watch day 2 after factory reset.
I took it off the charging cradle this morning and again, no flickering.
It seems the factory reset helped so far. (Crosses fingers.)
my current settings are:
Adjust Brightness = 4 (stock after reset)
Always-on screen = off
Face plate = suit
Installed apps:
Intellicom watchfaces (did not select any face plates after reset)
Luxery watchfaces (did not select any face plates after reset)
Watchmaker (did not select any face plates after reset)
InstaWeather (did not use this after reset)
I'm going to change one setting today, and that's the Adjust Brightness = 4 to Adjust Brightness = 1 and see what it will do tomorrow when I take if off the charger.
If indeed it flickers again tomorrow (which I surely hope it won't), I'll change the setting back to 4 and recharge it to 100% and check again.
After tomorrow (if the brightness setting isn't the issue), I'll put the brightness level back to 4 and select a 3rd party watch face.
Yes, this is going to be a slow testing process, because I want to check only after a whole night of charging to not manipulate the charging time.
When I can trigger the flickering process by changing some setting, I'll just recharge it on the fly. Check if I can make it "un-flicker" by undoing the last change I made on the watch.
if that doesn't help, uninstall the program that made it flicker in the first place and check after that. (if it's a 3rd party app and not a Google Wear 5.0.1 setting)
If that doesn't help, factory reset, one more night charging on default settings, if that doesn't make the watch flicker, re-install the program that caused it to flicker and retest the last procedure that triggered the "disco" effect.
Makes sense? LOL for me it does
I wish I had like 10 of these watches, would make the testing process go much faster.
Thanks again for everyone participating in this poll and posting serials and such :good:
It flickers again this morning without the watchmaker app. So that's not the culprit, really annoying, i will return this for warranty.
Sent from my Nexus 5 using XDA Free mobile app
Why don't you guys return the watch? Sod the testing the watch was not designed to flicker! When I get mine on Xmas day, if it flickers.. Back it goes
Sent from my Nexus 5 using Tapatalk
There's a reply on the other thread, he returned it ang LG fixed it. But flickering still persist. So looks like LG doesn't really know how to fix this. But I sent mine for warranty.
No official statement from LG regarding this issue.
Sent from my Nexus 5 using XDA Free mobile app
wicked1683 said:
There's a reply on the other thread, he returned it ang LG fixed it. But flickering still persist. So looks like LG doesn't really know how to fix this. But I sent mine for warranty.
No official statement from LG regarding this issue.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Here are my 2 cents about the flickering on the watch:
Quick summary,
Got the watch (day 1), it was fully charged 100% when I turned it on, paired it and played with the stock settings and options.
Didn't flicker the first morning after full charge (day 2).
I played with it a lot, installed apps, changed face plates, (Also tried out some MOMO 360 face plates through the 3rd party app to see what they looked like on this G Watch R, didn't like them, chose another one), played with the weather app..etc.
Flickered after full charge! (day 3).
Played with it a bit, didn't really pay attention to the flickering because it was working normally after a reboot, just thought it was annoying. However put it in the back of my head for the next morning to check.
Flickered after full charge! (day 4).
Thought it was pretty annoying and checked the web for possible solutions and if other people had the same problem with this "disco effect".
After reading the threads here, I decided to do some testing myself.
I did reset my watch to factory settings.
Didn't flicker after full charge (day 5).
Didn't flicker after full charge (day 6).
Changed display settings to brightness level 1 (was on 4).
If the watch was broken, hardware related, the flickering effect would be there all the time right? (Broken = broken, no matter what the settings).
If it was a loose wire, it wouldn't only flicker after charging. (Unless the watch heats up to a certain level on the charger which would cause a bad connection in the watch itself which makes it flicker only after recharge.)
Therefore I think it's either software related OR the combination between the brightness/always-on settings and hardware.
There might be something in one of the installed (3rd party?) apps OR in the brightness/Always-on settings that triggers the "disco" on your watch.
Maybe if the brightness level is put below stock settings, there is a condenser that regulates the screen brightness? (Going to put this to the test.)
IF tomorrow morning my watch flickers, I know it's the hardware that can't cope with the low brightness setting. If not, I'm going to change the brightness back up to 4 and install a 3rd party watch face.
I still think, because Dersie changed his brightness settings through another app, it is software related.
if it was hardware related, it would always flicker after recharge, no matter which app you use to dim the screen. (condenser/hardware goes all stressed when it has to power up the screen in dimmed mode).
It's like searching for a needle in the haystack, but hey.... I like finding needles in haystacks.
It gotten worse! After charging I decided to turn it off, I slept, when I woke up I turned it on, then seconds later flickering happends. Restarted it, but still the same. I turned it off for a couple of times. Until I decided to just leave it on until flickering dissapears. Did factory reset but still the same. Sick and tired of this, $300 watch and its defective I dont wanna deal with this everyday, Im gonna return it to newegg since they have 30 day return/replacement warranty. But my watch has a lil dent on the bezel already. I hope they still accept it.
unclebor said:
I still think, because Dersie changed his brightness settings through another app, it is software related.
if it was hardware related, it would always flicker after recharge, no matter which app you use to dim the screen. (condenser/hardware goes all stressed when it has to power up the screen in dimmed mode).
Click to expand...
Click to collapse
Mine started flicking after 4 weeks, batt at 42% 2 day after charged, on a table since 1H, so no movement to move hardware screen connector, no after full charge. No issue the last 2 days after using brigntness setup with SWApp....
condenser problem is maybe a way for the problem. It happen only from screen OFF to ON for me, never when screen is already ON for awhile. So only after condenser can be not charged.
Time to let you guys know about what's going on with my watch.
Didn't have much time to post anything the last couple of days :/
All I can say is, so far so good.
The last 3 days it didn't flicker at all.
I am running a 3rd party watch face now, brightness settings set to 1. No flickering after full recharge.
I don't know what caused it in the first place.
Maybe it was a MOTO 360 face watch I tried on my watch to see what it looked like, I don't know.
I will do some more testing after these busy days at the end of the year.
I will post again in this thread when the flickering returns or when I find out how to trigger it.
If I can find out anything else about the "disco effect" on the G Watch R series on other sites, I'll post a link here.
I'm sure this isn't over yet, I guess I am just lucky at the moment that it doesn't flicker.
However, knowing hardware /software it will probably come back since I already experienced the affect on this watch.
Edit: Seems I'm not alone! Hopefully it's not a defect on my sensor after all - http://forum.xda-developers.com/showpost.php?p=56976582&postcount=24
Hi all,
I've got a week-old SM-910T, which I loaded TWRP and rooted the moment I received it. I've taken great physical care of the device so far, and everything has been working great for the few hours it's served me so far
I was on a plane last night and monitoring a few of the sensors (knowing the that Note 4 is equipped with a barometer, I wanted to see how cabin pressure changes during the course of the flight). I'd already experimented with the barometer in the car the previous day for a few minutes and it worked great.
I was also watching the GPS readings. I lost GPS lock a few minutes after takeoff (probably because of the metal plane shell). Then out of curiosity I did an "A-GPS reset" and "compass calibration" with the "GPS Status & Toolbox" app from Play Store, and rebooted the phone, hoping to re-establish a GPS a lock. When the system loaded up again, I noticed that my Barometer was now stuck flat-lined at 1011.4 hPa. This freaked me out a bit, because this sensor was working moments earlier with high precision.
I knew I hadn't hurt the hardware any way (by dropping the phone for example), so I assumed that it was something software related. After having resorted to a full factory reset, and even a full wipe (system, data, cache+dalvik cache) and Stock ROM reinstall, this problem strangely persists (Barometer is still locked to 1011.4 hPa). I even tried to flash the latest kernel ZIP, but that did nothing either. I am concerned that, somehow, the hardware was coincidentally damaged or corrupted. But how would this even be possible?
Could the barometer be region locked, so that I might have merely flown out of the supported region? Or does it only activate under certain conditions? Is there just something silly I might be missing? Some other diagnostic or check I could perform? Should I maybe just try contact Samsung? xD
I've been having this issue on two different handsets (910P). I fly for a living and have figured out that the sensor will flatline if the phone is rebooted when the pressure altitude is above about 3000 feet. I live in Denver, CO at about 5400', so anytime I reboot my phone at home, I lose barometric sensing until I fly again and go to an airport under 3000', or reboot when the cabin altitude is under 3000'. I've contacted Samsung about it, but they just want me to send my phone to their repair facility in Dallas to have it looked at. Guess what they'll say? "Sensor works as it should". I wish they would listen to me and look into this further. I actually miss the use of the baro sensor when it flatlines at home.
Flight Denver to Portland and barometer sensor behavior.
What apps display barometer information? I didn't know there was that sensor in the note 4! ? cool!
Not sure if this is the right area, but I've been having trouble getting the fingerprint sensor to work for some apps - it works fine when waking the phone, but when I try to set it up for a credit card or banking app, it doesn't recognize the print and the app crashes. The apps & fingerprint access worked fine on my last phone (MI Mix 2). But it worked on a password manager app I'm using. Any thoughts out there?
I have the same problem
Same here. Coincidentally i also had a Mix Mix before. In my case Mi Mix 1. I think it might have to do with it being an on screen sensor.
no99sqrd said:
Not sure if this is the right area, but I've been having trouble getting the fingerprint sensor to work for some apps - it works fine when waking the phone, but when I try to set it up for a credit card or banking app, it doesn't recognize the print and the app crashes. The apps & fingerprint access worked fine on my last phone (MI Mix 2). But it worked on a password manager app I'm using. Any thoughts out there?
Click to expand...
Click to collapse
I contacted Blu about it and they told me to clear the cache - no go.
They basically told me that they tried a bunch of apps and it worked for them. Really don't believe it, pretty sure it's a software issue that they may or may not be working on.
no99sqrd said:
I contacted Blu about it and they told me to clear the cache - no go.
They basically told me that they tried a bunch of apps and it worked for them. Really don't believe it, pretty sure it's a software issue that they may or may not be working on.
Click to expand...
Click to collapse
Someone who has bought and reviewed this BOLD-N1, have also complained about same problems, that you have mentioned, with the In-Screen Fingerprint Scanner:
https://www.amazon.com/gp/customer-...=cm_cr_getr_d_rvw_ttl?ie=UTF8&ASIN=B07VHXT1R3
"If you do not need a finger print reader. One amazing buy.
1. Amazing Screen
2. Nice clean design with little branding.
3. Tons of features
4. Fits nicely in hand.
5. Case in the box is actually useful
6. No TMobile USA Wifi calling. But, gets service where my old phone had to jump to Wifi.
7. VoLTE support on TMobile USA (need to turn on in settings)
8. Battery easily lasts a day with reserves in the tank
9. Duo SIMcard is fantastic for me
10. Camera is fine for a $200 phone.
11. I like the hidden camera because I do not take selfies... so hate having a notch for no reason.
12. Works with the Samsung version GameVice TypeC controller.
The finger print reader is my only problem
Works to unlock the phone just fine but CHASE, CitiBank, CapitalOne all would not work or work randomly. CITI finally let me set it up but then would not let me back in. No go for Venmo either. My work password manager app would not even react to the press. It just waited as if nothing was happening.
If the finger print reader was at a better place (even with the no WiFi calling support) this would be a 5/5. Maybe they fix it with a patch. Contacted Blue customer support days ago and no response. Never a good sign..."
Another annoying issue is, the screen goes to 100% brightness when the fingerprint "target" pops up and there's no way to change it back without locking the phone and opening it back up. This is definitely a software issue that needs fixed.
I had a fingerprint matching problem initially, but I think I found a fix and now it works first time, every time for unlock, Chase, AMEX, etc.
When you record your thumbprint press down firmly on the sensor. Then also press firmly when you are trying to use your thumb print to sign in.
My theory is that when you press your thumb it flattens out and becomes bigger (in fact, I was able to create a second thumbprint this way, though it took some time). However, your thumb only flattens out to a point and then it doesn't change anymore. This way it will give you consistent scans.
I think if you record your thumbprint by lightly pressing the sensor, the only way you will get a match will be by pressing with the same amount of light pressure (which can be difficult). Hence it works sometimes and sometimes it doesn't.
Give it a try and report back.
UPDATE: I just tried creating a new fingerprint and I when I recorded it, I would record a light press and a firm press for each spot. I kept moving my finger with multiply pressures until it scanned my entire finger. I am getting 100% match everytime now.
jjsaustin said:
I had a fingerprint matching problem initially, but I think I found a fix and now it works first time, every time for unlock, Chase, AMEX, etc.
When you record your thumbprint press down firmly on the sensor. Then also press firmly when you are trying to use your thumb print to sign in.
My theory is that when you press your thumb it flattens out and becomes bigger (in fact, I was able to create a second thumbprint this way, though it took some time). However, your thumb only flattens out to a point and then it doesn't change anymore. This way it will give you consistent scans.
I think if you record your thumbprint by lightly pressing the sensor, the only way you will get a match will be by pressing with the same amount of light pressure (which can be difficult). Hence it works sometimes and sometimes it doesn't.
Give it a try and report back.
UPDATE: I just tried creating a new fingerprint and I when I recorded it, I would record a light press and a firm press for each spot. I kept moving my finger with multiply pressures until it scanned my entire finger. I am getting 100% match everytime now.
Click to expand...
Click to collapse
Tried a couple (Cap One, Chase, etc.) and all I get is a force closure on the app as soon as I try to set the fingerprint access up.
I haven't used the Capital one app, but I do used the Chase app all the time and it works for me.
Same problem for me... force close on Wawa, WalMart, Cap One bank... useless.