Related
[Update March 5th 2014]
Probably all 2014 Note 10.1's sold these past few months are suffering from one or more multitouch issues. From what we now know these appear to be software issues, effecting all current firmware versions for this device.
There are 2 known manifestations of this bug (or more likely: these bugs), described below. In both cases it seems to be a software issue because normally the 2014 Note 10.1 will work fine and the process of re-creating the issues is very clear and repeatable.
It looks like the multitouch driver becomes unstable if either one of the following occurs:
1. (Some models) You place (a part of) your hand on the screen for (at least) 5 seconds without moving it. This would usually happen when you are writing or drawing with the S-Pen.
2. (All models?) You place a finger (or several) on the screen for a longer time (close to 30 seconds) without moving it (them).
After either of these situations a 'defective unit' will show very erratic multitouch behaviour for a while.
It is easiest to see what happens if you use a so-called "Multitouch testing tool" (available Free on the Play Store). Such a tool typically shows all the screen areas where screen touches are detected by the device (in this case: the 2014 Note 10.1). Examples of such tools are: MultiTouch Test, MultiTouch Tester and YAMTT.
Erratic behaviour will usually start with all screen touches suddenly disappearing, meaning the device forgets that you have fingers (or part of your hand) on the screen. If you remove fingers (your hand) from the screen and again touch the screen several times a whole range of behaviour is seen: touches are detected and erroneously forgotten in quick succession. Sometimes so-called ghost-touches appear (meaning, the device will detect touches not anywhere close to where you are actually touching the screen).
This erratic behaviour will usually disappear when you leave the screen alone for a while, although several people (including me) have reported longer running issues (for instance during typing and editing using an on-screen keyboard). A surefire way to get rid of the issues is rebooting your device.
Since this is a "Note" device many people who's 2014 Note 10.1 suffers from these multitouch issues will encounter it while (or after!!) using the S-Pen. Others will notice issues while gaming or during typing/ editing.
The following clip by Kizune shows an example of what can happen while being inside a Multitouch testing app:
More videos you can find below (in post #16) and in the SwiftKey not working well on 2014 Note 10.1 topic, where the roots for starting this topic sprout from.
As of yet Samsung appears to be unaware of these issues, although several have approached them about this, returned their Note tablet, exchanged it or even handed one in for repairs. Hopefully we get this fixed soon.
Note 1: from early reports (in post #83) it looks like the new Note Pro 12.2 doesn't suffer from these issues.
Note 2: It is possible that a build up of static charge (through capacitance) is causing these issues, possibly caused by bad wiring (grounding) of the touch/ S-Pen detection circuitry.
Note 3: A new video has surfaced (in post #89) which shows 'noise' introduced in the touch-detection software while pinching/ zooming (see video below). It is unclear if this is related to the issues mentioned above.
i noticed this using the stock kb. i'm not a particulary fast typist on the screen but i'd get far too many lack of responses when typing on the split kb. standard qwerty was fine, but that have been b/c i'd type slower. i'm able to hit keys quicker on my gn8 without any misregistering of keystokes.
the fact there has been to OTA's in just a week is a sign they let this one out before it was ready. i still love the tablet though.
It happens to me too just like you see in the youtube video.
Just tried YAMTT and I am luckily not showing the issue seen in the video. Perhaps the second OTA solved it?
Sent from my Galaxy Note 10.1 via Tapatalk.
wingdo said:
Just tried YAMTT and I am luckily not showing the issue seen in the video. Perhaps the second OTA solved it.
Click to expand...
Click to collapse
Did you try the "whole hand" thing too? It would be super if Samsung solved things that quickly, but I feel a little aprehensive. We didn't get the recent updates yet in my area so I cannot see for myself.
wingdo said:
Just tried YAMTT and I am luckily not showing the issue seen in the video. Perhaps the second OTA solved it?
Sent from my Galaxy Note 10.1 via Tapatalk.
Click to expand...
Click to collapse
no, I took both OTA's Just before rooting.
wingdo said:
Just tried YAMTT and I am luckily not showing the issue seen in the video. Perhaps the second OTA solved it?
Sent from my Galaxy Note 10.1 via Tapatalk.
Click to expand...
Click to collapse
Same here. I tried a couple touch apps and all were fine. The YAMTT app just seemed buggy at times. but I could not replicate what the video showed on any of the apps and do not have problems in real world applications either.
atg284 said:
Same here. I tried a couple touch apps and all were fine. The YAMTT app just seemed buggy at times. but I could not replicate what the video showed on any of the apps and do not have problems in real world applications either.
Click to expand...
Click to collapse
Did you try the "whole hand" procedure too?
---
I changed the opening post because I feel many will be tempted to just try the youtube clip and not bother reading anything else. Hopefully we won't have too many people voting before properly taking all steps because you cannot change your vote once you voted (an xda forum limitation).
Ettepetje said:
Did you try the "whole hand" procedure too?
---
I changed the opening post because I feel many will be tempted to just try the youtube clip and not bother reading anything else. Hopefully we won't have too many people voting before properly taking all steps because you cannot change your vote once you voted (an xda forum limitation).
Click to expand...
Click to collapse
I did what the person was doing in the video and could not replicate what was happening on his. I also placed my whole had on it and put all ten fingers on it. No bugs. I am on the second update. Build number ending in AMJ4
Edit: the YAMTT app seems buggy because the other touch apps don't go crazy when all ten fingers on on it. But I could not replicate what YAMTT app was doing to the one in the video.
atg284 said:
I did what the person was doing in the video and could not replicate what was happening on his. I also placed my whole had on it and put all ten fingers on it. No bugs. I am on the second update. Build number ending in AMJ4
Click to expand...
Click to collapse
Did you place your whole hand on the screen of the 2014 Note 10.1 for several seconds, without moving it? Did you put your fingers on the screen afterwards? The video is not meant for reproducing the bug, the written procedure is. The video just shows what happens when you write, as the bug has already be introduced before the start of the clip.
Edit: The YAMTT app is not important, puting your hand for several sevonds on the scyeen IS. This creates what goes on afterwards. You can repeat it in any of the Multitouch testing apps, just place your hand (or part of it) on the screen for a while and see in the MT app what happens.
Ettepetje said:
Did you place your whole hand on the screen of the 2014 Note 10.1 for several seconds, without moving it? Did you put your fingers on the screen afterwards? The video is not meant for reproducing the bug, the written procedure is. The video just shows what happens when you write, as the bug has already be introduced before the start of the clip.
Edit: The YAMTT app is not important, puting your hand for several sevonds on the scyeen IS. This creates what goes on afterwards. You can repeat it in any of the Multitouch testing apps, just place your hand (or part of it) on the screen for a while and see in the MT app what happens.
Click to expand...
Click to collapse
Ok, I see. So when I put my whole hand/palm on it for 2-5 seconds then I try to put all ten it starts to "wig out" a bit but it still registers all ten its just sporatic. Also it seems to only have a problem with like 7 or more after because I can put many fingers on it before it wigs out. I still don't see a real world issue on mine even after I do the full hand thing.
Side note once I exit out the app the ten fingers on it are fine again.
What problems are people seeing due to this?
atg284 said:
Ok, I see. So when I put my whole hand/palm on it for 2-5 seconds then I try to put all ten it starts to "wig out" a bit but it still registers all ten its just sporatic. Also it seems to only have a problem with like 7 or more after because I can put many fingers on it before it wigs out. I still don't see a real world issue on mine even after I do the full hand thing.
Side note once I exit out the app the ten fingers on it are fine again.
What problems are people seeing due to this?
Click to expand...
Click to collapse
As far as I am aware the problem doesn't disappear as simple as that. It would be great if there was a way to get rid of it without rebooting.
You could get any type of interface problem afterwards, as even one finger touch can give ghost finger touches. I noticed things being wrong in SwiftKey before finding out what it was.
Ettepetje said:
As far as I am aware the problem doesn't disappear as simple as that. It would be great if there was a way to get rid of it without rebooting.
You could get any type of interface problem afterwards, as even one finger touch can give ghost finger touches. I noticed things being wrong in SwiftKey before finding out what it was.
Click to expand...
Click to collapse
Oh I don't have that at all. no ghost finger touches ever. I have not rebooted over the period of testing either today. Are you fully updated?
I will keep checking this over time though.
Ettepetje said:
The video is not meant for reproducing the bug, the written procedure is. The video just shows what happens when you write, as the bug has already be introduced before the start of the clip.
Click to expand...
Click to collapse
Well, actually the method shown in the video is the "previous version" of the current one. I could produce the bug with that method very often right after booting. But the "whole hand" method is more reliable.
What problems are people seeing due to this?
Click to expand...
Click to collapse
1. When taking notes at the university, I sometimes move the viewport in S Note using the zoom gesture without the zooming motion. And as you can see, putting my hand on the screen as shown in the video triggers the problem for me, so doing that gesture is almost impossible for me. I know there are scrollbars, but they move the viewport too slowly (but of course I use them when I notice the multitouch issues are occurring).
2. Same as above, but when drawing in Sketchbook or ArtFlow. And here it's extremely annoying because there are no scrollbars I could use.
3. A small annoyance compared to the others but: When I play Carmageddon, the multitouch issues get triggered once in a while. And then I can only either control the car, or accelerate or break, but not both simultaneously. Sometimes my touches aren't even registered at all. I often get destroyed due to the multitouch issues.
Kizune said:
Well, actually the method shown in the video is the "previous version" of the current one. I could produce the bug with that method very often right after booting. But the "whole hand" method is more reliable.
Click to expand...
Click to collapse
I changed the description in the opening post. I never had it happen like that yet. Did you know you get the errors just by holding the side of your hand on the screen for a bit? I thought that was how you discovered this. Doing that looks very similar to how you are holding your hand in the videoclip.
Did you find another way to get rid of the issues besides resetting your Note?
Btw: With Carmageddon, if you are high enough level and want to kill pedestrians, not having control means your opponents die crashing into you, ending the race before you finish all pedestrians.
Ettepetje said:
Did you know you get the errors just by holding the side of your hand on the screen for a bit? I thought that was how you discovered this. Doing that looks very similar to how you are holding your hand in the videoclip.
Click to expand...
Click to collapse
Exactly, I noticed it while taking notes. And then I made this my test method to replicate the error.
Anyway, here are some videos. The first shows a real-life situation in S Note with that problem, the second and third show that the problem also occurs in other multitouch test apps (yes, I'm looking at you, atg284 ).
And to make it more "real-world friendly", I used my old "provocation method" because that's how you put your hand on the screen while drawing and writing.
Btw: With Carmageddon, if you are high enough level and want to kill pedestrians, not having control means your opponents die crashing into you, ending the race before you finish all pedestrians.
Click to expand...
Click to collapse
Yup. And I even got that tank-like bonus police car, so they die just by touching my car tank.
I do stand corrected I can reproduce this issue on the new Note, old Note is fine and dandy.
Sent from my Galaxy Note 10.1 via Tapatalk.
wingdo said:
I do stand corrected I can reproduce this issue on the new Note, old Note is fine and dandy.
Click to expand...
Click to collapse
Did it take longer to get the erratic behavior like you said in pm? I'm trying to get the description in the opening post right, since we got 4 people now who claim they don't have it. I think the score should be 100%, and just included the Poll so that people at Samsung would quickly realise how big the impact is.
I can duplicate this.. just didn't figure how to repeat consistently until now..
First noticed when trying to pinch zoom in adobe reader .. you get very jerky redraw back and forth.. this could be app specific , but i haven't seen this on other devices
Sent from my SM-P600 using xda app-developers app
I'm also experiencing this. It's a terrible issue when taking notes in class.
Can we expect a fix?
Hello,
Anyone else has this problem where the fingerprint scanner barely works (almost unusable) ? I tried many ways to enter the fingerprints but it registers like 1 in 10 tries...
Edit 2: Best solution here: https://forum.xda-developers.com/showpost.php?p=72875604&postcount=18
If that does not solve the issue, also try this:
Edit: solution at https://forum.xda-developers.com/showpost.php?p=71964623&postcount=10
kevinlevrone said:
Hello,
Anyone else has this problem where the fingerprint scanner barely works (almost unusable) ? I tried many ways to enter the fingerprints but it registers like 1 in 10 tries...
Click to expand...
Click to collapse
same here. Samsung makes the worst finger print scanners.
thinking of 4 scan for same finger see if that helps.
Huawei makes the best finger print scanners
kevinlevrone said:
Hello,
Anyone else has this problem where the fingerprint scanner barely works (almost unusable) ? I tried many ways to enter the fingerprints but it registers like 1 in 10 tries...
Click to expand...
Click to collapse
That is not normal, my A5 works 9 in 10 on the first try.
Not a single error in my A3
Mine is totally unusable... any idea?
Well, it seems that I'm not the only one with this problem. Hopefully it can be fixed with an update.
I have to say that my thumb skin is a bit damaged (from doing work on cars, around the house, etc.) but this was never a problem with my S7 Edge. I tried a different finger with healthy skin and it does work a lot better, but still not 100%, it seems to me that the A3 sensor has real issues.
same Problem with my girlfriends A3.
Fingerprint scannner works in 1 of 4 times if youre lucky sometimes doesn't work at all.
She has already made 3 scans with 1 finger but didn't really help
Maybe send it back for warrenty repairs if a factory reset won't work'? I'm sorry but fingerprint sensor should work fine.
Chris.nl said:
Maybe send it back for warrenty repairs if a factory reset won't work'? I'm sorry but fingerprint sensor should work fine.
Click to expand...
Click to collapse
To be honest, I don't think this is solvable via warranty work. I am not sending my almost new phone back just to receive a refurbished piece of thrash. I am putting my faith into a firmware update. The funny thing is, I really like the phone even with this problem, it is very fluid and has even better battery life than the S7 Edge.
So here is a workaround I have found, for those having the issue:
- Instead of using the tip of the finger when adding your fingerprint, use the area just below the tip. In the attached picture, use the area marked with green instead of the one marked with red. It will then work 100%, it's amazing how fast and accurate it is. It's just not very smart like the S7/S8 and other phones and it probably has issues when the skin is not 100% perfect or maybe with pronounced geometric distortions like it is the case when using the finger tip.
Hi folks, a workaround for me was disabling the keep screen turned off, became much more accurate after that
I've got similar problem with always on display. When I turned it off everithyng is fine
I am having similar issues with my phone. I have tried using all three stored fingerprints as just my thumb and I still have trouble getting it to unlock. I do have Always On Display turned on, and I don't really want to disable it as suggested in this thread because it's an awesome feature. Samsung should be able to something as easy as a fingerprint scanner right. Hopefully this is simply a software issue that is patched
hi guys
you lock phone with power key or with widget (like screen off)?
After having the same problem I started turning my thumb much more (even almost fully vertical) during the scanning process. Now it works fine. DHNL
hi actually solved the problem what i did is that factory reset the phone, i schedule a weekly restart, i clean my scanner and i assigned all 3 fingerprints on to the same finger and it worked
Hi folks,
I am experiencing the same issue. I found some relief using a different finger. I have registered three of my fingersprints. For some weird reason only one of the three fingers works acceptably good, the other two are successful very rarely. I therefore recommend you to try with a different finger or several of them to find out which one better works for you.
Good luck !
I can confirm there is indeed a problem with SAMSUNG A5 2017 fingerprint system. The recognition rate can be extremely low in some condition (around 10% positive, meaning almost unusable). This seems to be a software bug
Here is a turn around :
If you record your fingerprint with the screen "always on" function activated , then the recognition rate is extremely poor.
if you unactivate this function during recording process, then the rate is ok (higher than 90%), even if you reactivate the always on function after recoring session
I guess this could be solved by Samsung in the latest firmware A5 (2017) update.
Gautier T., A5 owner
gautierT said:
I can confirm there is indeed a problem with SAMSUNG A5 2017 fingerprint system. The recognition rate can be extremely low in some condition (around 10% positive, meaning almost unusable). This seems to be a software bug
Here is a turn around :
If you record your fingerprint with the screen "always on" function activated , then the recognition rate is extremely poor.
if you unactivate this function during recording process, then the rate is ok (higher than 90%), even if you reactivate the always on function after recoring session
I guess this could be solved by Samsung in the latest firmware A5 (2017) update.
Gautier T., A5 owner
Click to expand...
Click to collapse
The trick seems to be working, thanks !!
kevinlevrone said:
Hello,
Anyone else has this problem where the fingerprint scanner barely works (almost unusable) ? I tried many ways to enter the fingerprints but it registers like 1 in 10 tries...
Edit 2: Best solution here: https://forum.xda-developers.com/showpost.php?p=72875604&postcount=18
If that does not solve the issue, also try this:
Edit: solution at https://forum.xda-developers.com/showpost.php?p=71964623&postcount=10
Click to expand...
Click to collapse
updating to nougat fixes this.
you won.t need the workaround with AOD like on marshmallow
Anyone else notice or experience a slower fingerprint unlock after applying the 8.1 OTA update? A VERY noticeable difference in unlocking speed after the update.
1up1up said:
Anyone else notice or experience a slower fingerprint unlock after applying the 8.1 OTA update? A VERY noticeable difference in unlocking speed after the update.
Click to expand...
Click to collapse
No issue here mate, still as fast as it was before on 8.0.0. Might wanna try another reboot to see if it fixes your issue. You could then always try a factory reset as well.
I just downloaded and reinstalled the 8.1 factory image. Went through and setup phone from today's backup and added fingerprints. While the phone was finishing downloading apps from backup, the fingerprint unlock was fast and normal as usual. After apps updated and restore finished, I restarted the phone. Immediately, the slow fingerprint unlock returned. I have very few apps and this wasn't an issue until after I applied the 8.1 OTA side load before the initial posting of this thread. Additional testing of the speed by pressing the power button then unlocking with fingerprint reader yields inconsistent unlock speeds. At this point, I do not want to say that maybe it's because of a particular app that is installed on the phone, but rather it's possibly a problem with 8.1.
Any thoughts?
To put it into perspective, the fingerprint unlock under normal speed feels almost "too sensitive" because it's so fast. Now it registers my fingerprint touch right away but is followed by a slight pause/stutter before unlocking the screen.
1up1up said:
To put it into perspective, the fingerprint unlock under normal speed feels almost "too sensitive" because it's so fast. Now it registers my fingerprint touch right away but is followed by a slight pause/stutter before unlocking the screen.
Click to expand...
Click to collapse
I have this exactly
I too am facing similar problems. My phone on 8.1 takes about 1.5s to unlock while it only took <1s on 8.0. A workaround I took was to have always on display activated. And I ain't a fan of the always on display.
Yup. First thing I noticed was this delay between when the fingerprint is actually recognized (vibrate), until I actually get visual on the screen. Around a second or more
I actually had this issue on 8.1 DP2. But since doing a fresh install of the 8.1 official release, my finger print reader is just as fast as 8.0. Maybe try a new fresh install.
SOLIDFND said:
I too am facing similar problems. My phone on 8.1 takes about 1.5s to unlock while it only took <1s on 8.0. A workaround I took was to have always on display activated. And I ain't a fan of the always on display.
Click to expand...
Click to collapse
I too, am not a fan of the "Always On" display but can confirm that this does fix the problem. Thanks for sharing your finding.
sn0warmy said:
I actually had this issue on 8.1 DP2. But since doing a fresh install of the 8.1 official release, my finger print reader is just as fast as 8.0. Maybe try a new fresh install.
Click to expand...
Click to collapse
Sadly, I actually went through a fresh 8.1 install but fingerprint scanner is still slow with ambient display off. Off to reinstalling my apps...
I found hit super hit or miss. When I flashed my rma phone to dp2 it was slow to unlock. When I flashed 8.1 final it was fast again. I had to flash 8.1 final again but this time the phone was slow to unlock. I got my new device flashed 8.1 on and it is thankfully unlocking quickly. I wish you all luck
I submitted it to Google under DP2 and it has been deferred to a future build... maybe re-submit under the final 8.1 as well??
https://issuetracker.google.com/issues/69984153
Today I also noticed a random "static pop" noise coming from the phone while Chrome browser was open. It was quite distinct and loud and happened twice.
SOLIDFND said:
Sadly, I actually went through a fresh 8.1 install but fingerprint scanner is still slow with ambient display off. Off to reinstalling my apps...
Click to expand...
Click to collapse
Same problem, gets fixed with always on display but if the screen is not on in between the seconds of pressing the power button and ambient display kicks in then the problem is still there. Also tried deleting the fingerprints and redoing the fingerprint initiation, but it did not help. The sensor registers the fingerprint by vibrating but screen gets on only after a second or more. sometimes though it is instantaneous. another problem for Google to fix I guess in next month update.
1up1up said:
To put it into perspective, the fingerprint unlock under normal speed feels almost "too sensitive" because it's so fast. Now it registers my fingerprint touch right away but is followed by a slight pause/stutter before unlocking the screen.
Click to expand...
Click to collapse
Same issue here since updated to 8.1
The fingerprint is recognized quickly (you fell the short vibration) but the screen turns on with a delay of about a second.
I have the same issue when I just press the Powerbutton - it also takes about a second until screen turns on.
Guys, I'm so disappointed with my Pixel 2 XL. Never had so many issues with a stock firmware phone.
Been running 8.1 through the beta for awhile now and haven't had any of these issues. Not sure if I'm just lucky or what but it's been humming along just fine. Just installed the 8.1 official over the 8.1 beta and haven't noticed anything as of yet. Will pay attention to see if I notice anything being slower.
I am also seeing the issue after updating to 8.1. It takes about 2 seconds for the screen to appear. AOD does make it faster but I can deal with it and hopefully google fixes it soon
I searched he'd the issue on google- obviously because I HAVE IT TOO. This is infuriating. This is major functionality. after 8.1 the finger print reader is slow AF. It feel like my old galaxy s4 that i just came away from when i would swipe to unlock it. How many times do we unlock these things a day? We just went from the fastest unlocking phone to the slowest. Why is this effed up? I'm pissed.
We have ppl whining about the freaking hamburger emoji having the cheese on the bottom and the wrong foam in the beer mug, meanwhile it takes forever to get into the phone to do anything much less get to the Emojis. How does BASIC functionality go BACKWARDS with an update?
What's even more infuriating is I can't go back to 8.0!!! Google doesn't allow it do they? I am coming to this phone off a Galaxy s4. One of the big benefits of the pixel family is the "fast updates."I saw someone argue that this isn't necessarily a plus sometimes these new Android versions slow a phone down, and it's done. Sometimes, like in this case, bugs are introduced. The very first update I took on this phone largely argues his point.
Another thing I'm noticing is the battery life seems to be dropping much faster. I'm wondering if it's the flash kernel 2.0 I installed though.
I will be filing a complaint on the link someone so kindly posted above (thank you), and I will be going into the chat option through the help menu on my phone to file a complaint there.
EDIT: it also seems like Google assistant isn't working now either. "Ok Google" brings her up. The mic registers my talking, but no results are displayed.
EDIT 2: I also forgot to mention that along with the slow unlock the swipe function on the finger print reader has been altered. Smiling up and down to toggle the notification drawer is very inconsistent and buggy. I have the finger print quick action app installed. I had a single tap set up to lock the screen. I had my finger print reader un/locking the phone and toggling the notification drawer. While the notification drawer has always been a little buggy, it was VERY functional and very acceptable. Something has changed on the reader so it is having a harder time differentiating between the different movements. Now it usually registers a swipe as a tap and the screen locks. I expected this to happen when I first downloaded the app on 8.0, but I was pleasantly surprised when everything worked through the sensor. Now I am very disappointed. The issue is NOT constant. It comes and goes. Idk why it does that. I'll be seeing if I can figure out why. I will NOT be activating the always on screen as a means to circumvent this issue. I don't want burn in. I've been concerned with that issue associated with always on before the pixel showed up.
jbarcus81 said:
I submitted it to Google under DP2 and it has been deferred to a future build... maybe re-submit under the final 8.1 as well??
https://issuetracker.google.com/issues/69984153
Click to expand...
Click to collapse
I want to jump on board and file an issue too. What do I select the issue as?it's not a developer preview. Is it android system issue? Framework?
fearfighters said:
I have this exactly
Click to expand...
Click to collapse
-deleted
---------- Post added at 06:08 PM ---------- Previous post was at 06:02 PM ----------
1up1up said:
To put it into perspective, the fingerprint unlock under normal speed feels almost "too sensitive" because it's so fast. Now it registers my fingerprint touch right away but is followed by a slight pause/stutter before unlocking the screen.
Click to expand...
Click to collapse
Same here
So I finally took the jump to Pie. One of the smaller issues I have that I didn't before is when trying to set up my fingerprints again, I get an error on the last press which tells me to try again or try another finger.
Yes, an issue for me also. Sometimes it just does not work and other times it tells me the fingerprint sensor is dirty which it is not. Fingerprint sensor issues have been reported by others too after installing Pie. It does not seem to me to be as common as the notification issues with Pie, (which I also have), but it is talked about. I also did a factory reset a couple days after installing 9.0 which did help a couple of apps to work better but did not help the fingerprint or notification problems.
The fingerprint issue is weird as sometimes it is so bad, I think I will not be able to keep the phone, just will not work at all. Then for no discernible reason it will start working fine. It is not just a pain to have to use another login method every time the phone needs to be woken up, but I also use fingerprint sign in for a few apps and it is much harder to have to enter one of my random 14 character passwords when the fingerprint won't work.
Try to put your Ambient display Always on... see if it fixes the fingerprint problem (Google is aware of this issue) till google issues a permanent fix.
Wasn't that only a workaround for people who had fingerprint lag? I don't think it was for fingerprint reading issues.
I did notice a lot more fingerprint reading errors with Pie then redid my fingers and all has been fine.
itzik_man said:
Try to put your Ambient display Always on... see if it fixes the fingerprint problem (Google is aware of this issue) till google issues a permanent fix.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
I've had my unlocked note 10+ for a few weeks now. I have it flashed to tmobile firmware and it's been working great. My issue is with samsung pay and my gym membership. I came from a note 8 and my gym membership is a bar code which worked with the gyms scanner. When I switched over to the note 10+, the gyms scanner wont scan the bar code anymore.I've called Samsung and they said it's a first for them. They had me clear the cache and re-enter my card, both of those attempts didn't work. Has anyone had an issue with this?
any insight?
Anyone?
joon joon said:
I've had my unlocked note 10+ for a few weeks now. I have it flashed to tmobile firmware and it's been working great. My issue is with samsung pay and my gym membership. I came from a note 8 and my gym membership is a bar code which worked with the gyms scanner. When I switched over to the note 10+, the gyms scanner wont scan the bar code anymore.I've called Samsung and they said it's a first for them. They had me clear the cache and re-enter my card, both of those attempts didn't work. Has anyone had an issue with this?
Click to expand...
Click to collapse
When you say barcode that is read by the gym's scanner is it a barcode that is displayed on the screen, and you hold the phone up to a reader for it to scan that bar code from the screen?
If this is the case then there is really no answer.
So in order to get this to work you need to adjust the screen brightness up and/or down, angle of the phone (when held up to the scanner), distance of the phone from the reader, zoom in or zoom out on the bar code (if possible), and make sure the screen is clean.
It's a lot of trial and error until you get it to work, no magic one size fits all cure exists. So all, one or a few of the steps above will help.. You will just have to experiment until you find what works for you.
I had a similar issue (barcode scanning from the phone's screen) while using a store gift card via bar code on the screen of the phone. That's all I did (the things I mentioned above) to get it to work, but it did work eventually.
scottusa2008 said:
When you say barcode that is read by the gym's scanner is it a barcode that is displayed on the screen, and you hold the phone up to a reader for it to scan that bar code from the screen?
If this is the case then there is really no answer.
So in order to get this to work you need to adjust the screen brightness up and/or down, angle of the phone (when held up to the scanner), distance of the phone from the reader, zoom in or zoom out on the bar code (if possible), and make sure the screen is clean.
It's a lot of trial and error until you get it to work, no magic one size fits all cure exists. So all, one or a few of the steps above will help.. You will just have to experiment until you find what works for you.
I had a similar issue (barcode scanning from the phone's screen) while using a store gift card via bar code on the screen of the phone. That's all I did (the things I mentioned above) to get it to work, but it did work eventually.
Click to expand...
Click to collapse
yes correct. ive tried moving it around, up, down, tilting it. tried moving the distance.
when i go to the card, the screen does brighten up a bit but not to full brightness. i guess ill have to try that. with my note 8 it never went to full brightness and still scanned pretty quick. thanks for the input and ill post up after i try putting the brightness up all the way.
joon joon said:
yes correct. ive tried moving it around, up, down, tilting it. tried moving the distance.
when i go to the card, the screen does brighten up a bit but not to full brightness. i guess ill have to try that. with my note 8 it never went to full brightness and still scanned pretty quick. thanks for the input and ill post up after i try putting the brightness up all the way.
Click to expand...
Click to collapse
I would avoid comparing the two phones like that, they are obviously not the same. If they were you wouldn't have to go through this much effort.
You will have to adjust the brightness manually (in case you haven't already). With scanning a barcode off the phone don't rely on the phone's ability to auto adjust based on your previous brightness settings for the level of light present.
Do you have screen protector? Perhaps different phones/screen protectors have different reflection levels.