Related
I'm experiencing a lot of problems with the SwiftKey App lately on my Note 10.1. Even though I switched most functions off, only auto-caps at start of new line is on, I get random inserted digits or even random auto-completion (which is very annoying I can tell you) . Anyone else using SwiftKey who experienced problems on the new Note 10.1?
It also can be very difficult to start a new line because it writes the 2nd, 3rd etc. letter on top of each other.
Edit: had to remove typos and random characters 3 times in the first alinea alone.
Ettepetje said:
I'm experiencing a lot of problems with the SwiftKey App lately on my Note 10.1. Even though I switched most functions off, only auto-caps at start of new line is on, I get random inserted digits or even random auto-completion (which is very annoying I can tell you) . Anyone else using SwiftKey who experienced problems on the new Note 10.1?
It also can be very difficult to start a new line because it writes the 2nd, 3rd etc. letter on top of each other.
Edit: had to remove typos and random characters 3 times in the first alinea alone.
Click to expand...
Click to collapse
have you tried beta 4.3
tonytownsend said:
have you tried beta 4.3
Click to expand...
Click to collapse
Am doing so as we speak type. Nope, still buggy (same bugs).
I must be using the iPad too often because I find I'm unable to select words and then, afterwards, apply strike.
Edit: It also inserts spaces after it erroneously inserted "[ strike][ /strike]" (without the spaces) at the start of the post, in stead of around "speak", making me have to edit "[ QUOTE=tonytownsend" afterwards... Hopefully most of this is solvable in future.
This is just a guess, but could it be the touchscreen instead of SwiftKey?
Both my first and (after I returned it) second Note (which I purchased from another seller) have very annoying touchscreen issues.
I didn't notice it at first because the problem doesn't occur that often if you use the tablet with only one or two fingers. But then I started taking notes at the university and I noticed that I couldn't use the zoom gesture directly after I had put a part of my hand on the screen. It just stopped all of a sudden or it was very jumpy and hard to control.
It became so annoying that I installed YAMTT and checked if anything was wrong with the touchscreen. And indeed, most of the time when I put my hand on the screen as if I was writing or drawing, the screen started to behave strangely afterwards.
I found a method to reproduce the problem all the time. It might be worth checking:
- Start YAMTT in "Touch tester" mode
- Put your whole hand on the screen for around two seconds, then lift it
- If there are some touch indicators still shown, ignore them and just proceed
- Put five fingers on the screen and wait for a few seconds without moving them
- If the touch indicators suddenly disappear, you have the same touchscreen issues
Kizune said:
This is just a guess, but could it be the touchscreen instead of SwiftKey?
Both my first and (after I returned it) second Note (which I purchased from another seller) have very annoying multi-touch issues.
I didn't notice it at first because the problem doesn't occur that often if you use the tablet with only one or two fingers. But then I started taking notes at the university and I noticed that I couldn't use the zoom gesture directly after I had put a part of my hand on the screen. It just stopped all of a sudden or it was very jumpy and hard to control. Single-finger operations and the S Pen kept working fine, though.
It became so annoying that I installed YAMTT and checked if anything was wrong with the touchscreen. And indeed, most of the time when I put my hand on the screen as if I was writing or drawing, the screen started to behave strangely afterwards.
I found a method to reproduce the problem all the time. It might be worth checking:
- Start YAMTT in "Touch tester" mode
- Put your whole hand on the screen for around two seconds, then lift it
- If there are some touch indicators still shown, ignore them and just proceed
- Put five fingers on the screen and wait for a few seconds
- If the touch indicators suddenly disappear, your touchscreen has multi-touch issues
Click to expand...
Click to collapse
I sure hope not. I started a whole topic on the Note 3 forum because I discovered it had a multitouch problem. Haven't been able to produce that type of multitouch issue on any of my other gear besides a Nexus 7. Will check with your method to see what it gives.
I checked the videos in your thread and the behavior is indeed very similar to what I got:
(In the video I haven't used the method described above yet, I discovered it just today)
I discovered that my fingers got remembered (stayed) on the screen if I left 5 of them on the screen. Happened only ones though. Then I tried puting my whole hand on it for a few seconds and then the multitouch algorithm went bananas. Tried with different Multi-touch app too. I think this is a software issue, from the looks of it.
SwiftKey has been giving me problems on my 2014 Note 10.1 from day 1, but they had become 10 times worse today. I just rebooted my Note and it now behaves as normal (still somewhat buggy SwiftKey, like before). I think there are some issues in the Multitouch driver which can be triggered by the "whole hand" method described above, and possibly by other means. My MT driver had already become unstable, hence I could reproduce a defect (finger touches remaining on the screen) without the "whole hand" thing.
Kizune said:
I checked the videos in your thread and the behavior is indeed very similar to what I got:
(In the video I haven't used the method described above yet, I discovered it just today)
Click to expand...
Click to collapse
Kizune, I included your video in a topic about this Multi-touch issue, I hope you don't mind.
Of course it's okay. Let's just hope that Samsung will fix the problem ASAP, it annoys the hell out of me.
I found the newest beta of Swiftkey to be buggy on the Note 1014 so I removed it and went back to Swype.
Too bad as I was enjoying the split keyboard mode.
Itchiee said:
I found the newest beta of Swiftkey to be buggy on the Note 1014 so I removed it and went back to Swype.
Too bad as I was enjoying the split keyboard mode.
Click to expand...
Click to collapse
I will very probably be doing the same. Thanks for getting back on topic.
I installed SwiftKey for tablets, not the phone version. Absolutely no problems typing for me on my note.
Sent from my HTC One using XDA Premium HD app
SlimJ87D said:
I installed SwiftKey for tablets, not the phone version. Absolutely no problems typing for me on my note.
Click to expand...
Click to collapse
I use the same (Tablet) version. Possibly it is caused by a combination of settings. I have most (aiding) options switched off. If I find the time I will experiment.
Try "Touchpal"..it's similar to Swiftkey.. it's free and has plenty of thenes. I actually like it better
Sent from my SAMSUNG-SM-N900A using xda premium
Newest SwiftKey is running perfectly for me on the Note 2014. It's so nice to be able to have a compact keyboard you can undock and move from any part of the screen to another. So convenient for applications. Highly recommended, please try it if you haven't
I recently bought a Zenfone 2 (ZE551ML) which works exceptionally well however today I've noticed something odd (probably would have noticed it before but the phone was actually a gift so not at all times with me).
During a call the proximity sensor will only turn off the screen when the phone is close but it will not turn the phone on when I move it away. I've gone through many online articles and in the majority of cases it was a problem with the screen protection. However, I do not use any kind of screen protection.
Additionally I've noticed something really odd. Zenfone 2 has an inbuilt testing suite (SMMI Test) which allows testing various parts of the hardware. The proximity sensor test consists of three steps (NEAR, AWAY, NEAR). They should be self-explanatory (NEAR triggers when an object is close, AWAY when its far). In my case the first step (NEAR) always triggers after the test starts but the other two (AWAY, NEAR) simply won't. That's until I use the app switch button (next to the home button) to re-enter the test application again. The other two steps then complete successfully.
Considering the behavior can I rule out a hardware problem and pin the issues to the software?
The proximity sensor issue was successfully resolved by reverting back to the 2.20.40.90 firmware. The 2.40.40.97 version (at least WW) obviously has issues with it.
You can find detailed instructions on how to perform stock recovery in this topic (http://forum.xda-developers.com/zenfone2/help/reverting-to-stock-firmware-t3225632).
Once again props to kanagawaben and all the people which contributed to this topic.
I've recently flashed IronRom onto my tablet. It's been in the closet for a year. Only been in use for less than a month. Today, I was listening to music on the tablet. It was steady in a specific position. I had to skip one track and so I unlocked the tab using my fingerprint and went onto tap the next button. But to my surprise, it did not respond. In fact, it completely stopped responding to any touch instructions. I thought it might have been a rom related problem but then I checked TWRP rec and the problem was present there too. Really weird, cause the tab hadn't even moved an inch from the location it was working perfectly before. So how could this be a loosened wire? Any help, guys (other than sending it for repair)?
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
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