Related
Hey all,
I got this badass LG R watch for Xmas and it's never had a problem. Then a day or so ago it's started "smearing" on the screen. Anything white/lighter colour sort of ghosts or glows like it's being viewed through frosted glass.
The touch screen still works and any and all functionality is still there with no problems. It's only the view that's sort of washed out. I don't use "always on" and it's not screenburn as I've tried different watch faces and it still does it.
Worst part is: It's not permanent. It's completely intermittent and I have no idea how to duplicate it. I went to take a picture of it to go with this post, and now it's not even bloody doing it.
Not sure if it's related or not, but I've been having difficulties with my phone's OS upgrade at around the same time (4.4.3 is giving me ****s) and it's paired to that, so I don't know if that'd cause issues. Dog knows that the phone is having issues...
Any help/advice is much appreciated! Cheers!
Have run another upgrade across the phone and it appears to be bringing down the frequency of the blurriness. I'm seeing it only once or twice a day since then.
Any ideas?
Hello all, here again with another issue that I haven't seen mentioned anywhere.
My sound and slow performance problem was recently resolved on its own after a complete revert to stock and back to running a custom ROM, but now I have another question. How do you know if the vibration motor is dead?
I took my phone apart recently to see what could be wrong, what could be loose, and what might be dirty, but everything looks really good, the speakers work, wireless charging works, everything seems fine. The only problem is that no matter what I do, vibrate will not work for anything.
Then I noticed what seemed to be the vibration motor, which is a little piece of metal with a rod going through, with metal rings that seem to just spin freely. It's still firmly attached to the motherboard, yet I get no vibration for anything. Even enabling it for my keyboard actually causes the keyboard to lag and skip letters, yet when disabled, its smooth as butter.
I also don't have any settings for vibration strength anymore in Kernel Adiutor, even after testing multiple kernels to see if maybe it wasn't supported.
Has anyone here had any of this happen before? I've already ordered a new motherboard to swap out with this one, but I just wanted to see if there was anything I could do to fix this, or hear what you all have to say. I don't mind spending the little bit of money to fix it myself, but if I could avoid shelling out about 60 for another motherboard, I would prefer to do that.
The fingerprint scanner on the Nokia 9 is terrible! Seems to only read it 20% of the time. I use face unlock sometimes which is nice but I can't always hold phone up to face. Tempted to just use smart lock with my android wear watch but there goes my security. May end up trying to add fingerprints again for a 3rd time...
Mine almost always works, but I have to apply some pressure to it. It's not like most other in-display readers that work with just resting your finger on the screen.
I have each thumb trained twice on it.
It fails completely with a glass screen protector (at least for me).
Worst scanner. Works 50 percent or less and with multiple scans of same fingerprint. Utterly useless.Ar least the Galaxy S10 plus was fixed with updates and my success rate is 90% + on that phone.
Sent from my Nokia 9 using Tapatalk
It's a painful fingerprint scanner, but I've found a way to make it reliable. Not necessarily convenient, but reliable..
Before scanning, I lick my thumb of index finger lightly, then run them together leaving them just slightly damp (just enough so they don't slide smoothly across the phone screen), then touch firmly, but certainly not hard, on the sensor patch.
Works almost first time every time. I also used this same method when training the prints.
stiebs said:
It's a painful fingerprint scanner, but I've found a way to make it reliable. Not necessarily convenient, but reliable..
Before scanning, I lick my thumb of index finger lightly, then run them together leaving them just slightly damp (just enough so they don't slide smoothly across the phone screen), then touch firmly, but certainly not hard, on the sensor patch.
Works almost first time every time. I also used this same method when training the prints.
Click to expand...
Click to collapse
Do you know where that thumb has been since the last time you licked it??? :silly: :silly: :laugh: :laugh:
I received my phone yesterday. My fingerprint scanner seems to work just fine. There are a couple times where it did take a couple tries, but it's been nothing like I've been reading. I'm perfectly content with it. I'll also add that it's been working just as well for me with a plastic screen protector on it.
You guys never had a xiaomi mi 5s. If so, you would not complain about fingerprint scanner ?
I've had about a 75% success rate with the fingerprint scanner. I set it up in a dark room and registered both thumbs and index fingers. There are times when it won't read my fingerprint at all, which seems to be software related. Other times, it will say not recognized. In those cases, I've tried to place my hand over my phone as if I'm covering my PIN at the ATM, creating a bit of a shadow or darkness over the fingerprint area of the screen and then trying it, which seems to work a lot more often. Covering it with the other hand might be a fluke, but I am able to repeat the results again and again.
Edit: I deleted my post, because it was not repeatable. Whatever the software issue is, its too intermittent to isolate through physical means alone. Someone with programming knowledge though should be able to see what might be causing the problem and provide some insight on a workaround until then.
Right now for me, it seems to work when its being charged and battery saver seems to affect its success rate.
for me it depends on the situation, sometimes it doesn't work at all. Things like temp etc seems to be influencing the succes rate. my xz3 has a reader at the back and it doesn't work sometimes as well. they are equal in reliability. But if you are used to a Huawei (like the mate 9) it is terrible. I really had to adjust when I got the XZ3 (coming from a mate 9).
I received mine this morning and it performed a system update out of the box.
I put a glass screen protector on the phone straight away and I've had some success with using the fingerprint reader, although not so much that I would like to use it all the time.
These are my observations so far,
- The 'press harder' message is deceptive. I have never got it to work by pressing harder when it tells me to press harder in a spot where my thumb/finger already is. Instead if I use that as a cue to re-position my thumb/finger then I have much more success. When it works, I have never had to press hard at all.
- It doesn't like my thumb very much. It takes some time to find the right position with my thumb, where as my forefinger is fine.
Update: 16:14
I've been persisting with it and have found the right amount of pressure to make it work more consistently. The message on the screen says press a little harder, and pressing it to the point where it flattens your skin out against the screen makes the chance of success better.
Moseman, i did everything you did, unfortunately its a software issue. You are right about the 'press harder' message, its not true. You don't need to press hard at all to get it to work, which i have been able to test successfully. The issue is not about pressure, its about placement. You must place your finger in the exact position that you placed it when you did the first half of the enrollment. Interestingly, i've noticed that apps that use the finger print reader as part of their login, seem to work much better. Such as ADP app or Bank apps.
You will notice that it probably works better while on charger, and works terrible with battery saver on. I tried many ways to find a workaround to get it to work consistently, but eventually it goes back to working 10% of the time. I believe they will create a fix here soon.
I've heard the face scanner login works much better. GL!
I got a good working scan by holding the phone in landscape mode while learning the scan. Might be coincidence , but i figured since the scanner is the shape of a flat rectangle it might cover more of my finger that way. (in normal use i just unlock in portrait mode, i just did the landscape thing to learn the fingerprint)
Interesting. I will try your method and see what i get. Will post an update later. Thanks Bk227865.
*Update: The method does appear to be working somewhat better. I will have to keep testing. Thanks.
*Update2: I don't know why im obsessed with getting this working. But BK you gave me an idea.
So after trying your method, i wondered if enrollment was the issue. Perhaps i wasn't doing it right, and maybe someone else did do it right, so let me know if you did the following.
I deleted all enrollments and tried again, this time with battery saver off (just to rule anything out related to that). I also made sure that my finger placement was exactly as described in the training photo. Originally and before, i had placed the edge of my fingerprints to the edge of the scanner, but actually it wants you to place the middle part on the scanner.
So when i re-enrolled using the exact finger placement the picture showed, it didn't work 100% of the time, but i do get somewhat better overall success with different finger placements.
Anyone willing to test this out?
Sliksta said:
Interesting. I will try your method and see what i get. Will post an update later. Thanks Bk227865.
*Update: The method does appear to be working somewhat better. I will have to keep testing. Thanks.
*Update2: I don't know why im obsessed with getting this working. But BK you gave me an idea.
So after trying your method, i wondered if enrollment was the issue. Perhaps i wasn't doing it right, and maybe someone else did do it right, so let me know if you did the following.
I deleted all enrollments and tried again, this time with battery saver off (just to rule anything out related to that). I also made sure that my finger placement was exactly as described in the training photo. Originally and before, i had placed the edge of my fingerprints to the edge of the scanner, but actually it wants you to place the middle part on the scanner.
So when i re-enrolled using the exact finger placement the picture showed, it didn't work 100% of the time, but i do get somewhat better overall success with different finger placements.
Anyone willing to test this out?
Click to expand...
Click to collapse
I can vouch for this, great discovery, Sliksta! :good:
UPDATE:
After further experimenting, it seems like the results are only slightly better and this is not a permanent solution.
Wow. Really improved! Almost 8/10 now
The way I did it was placing my thumb in different angles from the beginning. Don't have a lot of troubles with it. Some times the light just doesn't switch on. Direct sunlight doesn't help its accuracy. Wet fingers doesn't help as well. But I would say mostly it works
Thanks all and Chaosdark for testing. I still believe that battery saver somehow effects the consistency of its accuracy. I would say it works more often than not with battery saver off. This might be the inconsistency you are experiencing. Can you/anyone confirm it works better w/ battery saver off?
Today I think I've found something interesting, if you go to verification option in the fingerprint section under security and touch the FP scanner to verify which fingerprint enrollment belongs to which finger, I have found that it detects and identifies the fingerprints enrolled easily and quickly and doesn't ask you to press harder as often as on lockscreen ( needs more testing from other users).
This results makes me hopeful that a software fix is possible and in the making according to Nokia CEO how vaguely suggested there will be a fix in an upcoming update.
What do you guys think?
stiebs said:
It's a painful fingerprint scanner, but I've found a way to make it reliable. Not necessarily convenient, but reliable..
Before scanning, I lick my thumb of index finger lightly, then run them together leaving them just slightly damp (just enough so they don't slide smoothly across the phone screen), then touch firmly, but certainly not hard, on the sensor patch.
Works almost first time every time. I also used this same method when training the prints.
Click to expand...
Click to collapse
This works 100% without pressing harder
Incredible
So, I've noticed a weird problem my RP2 has. I carry it in my hip pocket, and at times (happens frequently enough to be annoying) when I pull it out to use it, the screen doesn't respond to a normal touch. I have to really push down hard on the screen to get it to register. If I let it sit for a few seconds/minutes the touch responsiveness fixes itself and it can be used normally. Not sure if it could be a physical problem with the digitizer/connection or if something is going on when it is "asleep" in my pocket. Just weird that it fixes itself. Anybody else see anything like this or have a suggestion as to what it could be? The phone is totally usable, and even when it messes up it still works I just have to push super hard to get it to do anything. Sometimes i'm afraid I'm going to snap the glass, although I don't really think that is likely to happen. Thanks for any ideas.
Just to weigh in I also have this issue not very often but enough to notice it. Especially since the last update also when I zoom with the stock camera it just freezes.
I'm having similar issues, camera fixes if i reboot but thats annoying if your trying to get a moving shot, also noticed it sometimes freezes switching to portrait mode.
For the screen freeze I have found if i use my finger print to unlock when the screen isnt responding its starts to work. but i didnt have the problem until i put on a crappy glass screen protector.
I just got the phone and im using arters r2 kernel with f2fs on data, as well as magisk and xposed so i wasn't sure if it was something i did but since others are seeing it ill assume its something with the phone and see if theres any fixes or decide if i should return it.
godsfilth said:
I just got the phone and im using arters r2 kernel with f2fs on data, as well as magisk and xposed so i wasn't sure if it was something i did but since others are seeing it ill assume its something with the phone and see if theres any fixes or decide if i should return it.
Click to expand...
Click to collapse
Mine does that too, but I'm not on the new kernel. Maybe it has something to do with the ambient display being turned on.
jonchance_84 said:
Mine does that too, but I'm not on the new kernel. Maybe it has something to do with the ambient display being turned on.
Click to expand...
Click to collapse
hmm maybe, i only had show new notifications turned on but ill try turning it off and see how it goes over the next couple days
Ok so since turning off my ambient display, no issues so far.
karlkarloff said:
So, I've noticed a weird problem my RP2 has. I carry it in my hip pocket, and at times (happens frequently enough to be annoying) when I pull it out to use it, the screen doesn't respond to a normal touch. I have to really push down hard on the screen to get it to register. If I let it sit for a few seconds/minutes the touch responsiveness fixes itself and it can be used normally. Not sure if it could be a physical problem with the digitizer/connection or if something is going on when it is "asleep" in my pocket. Just weird that it fixes itself. Anybody else see anything like this or have a suggestion as to what it could be? The phone is totally usable, and even when it messes up it still works I just have to push super hard to get it to do anything. Sometimes i'm afraid I'm going to snap the glass, although I don't really think that is likely to happen. Thanks for any ideas.
Click to expand...
Click to collapse
I use Ambient Display and sometimes the screen behaves as you've described where it won't reach to touch, but I've always just given it time/pressed the power button repeatedly until the screen came on (or continued to tap the screen lightly)... never tried pressing down very hard.
Not to Necro a thread but I've experienced this aswell, infact it's happening right now as I type this.
Hey, got a question for those that exercise, or work out using their Galaxy Watch 3. Specifically, walking, but also running, treadmills,etc.
Do you see a dropping of your heart rate data at random times during your activity? Heart rate data appears perfect during the day, but will drop randomly during a walk, or treadmill activity.* This has happened both times I've tried the activities, I've only had the watch 3 days.
Anyone found a fix?
Can't speak for running, but for brisk walking the heart rate monitoring has been very good and consistent for me (within 1-2 of a chest strap monitor average after an hour).
It needs to be snug, not tight (it should not be able to slide around on your wrist in any direction). And should be above the orbital bone on your wrist.
Beretta143 said:
Hey, got a question for those that exercise, or work out using their Galaxy Watch 3. Specifically, walking, but also running, treadmills,etc.
Do you see a dropping of your heart rate data at random times during your activity? Heart rate data appears perfect during the day, but will drop randomly during a walk, or treadmill activity.* This has happened both times I've tried the activities, I've only had the watch 3 days.
Anyone found a fix?
Click to expand...
Click to collapse
I have the same problem when in cycling mode :/ At first i thought it was related to tightness of the strap or placement, but no matter how tight or loose it is, it drops, and seems to come back by random seconds or minutes after i notice it has gone.... Seems to only be in exercise mode, as i've never caught it doing it otherwise (i have continuous monitoring enabled)
In any case, the heart sensor really stops working at times during physical activities, especially running. And even at times during the day in a normal situation it stops working.
In any case I did not have this kind of problem with my Galaxy watch active 2.
I hope there will be an update soon.
To elaborate: This happened again for me today, and i took off the watch and could see the green sensor light still going.... tried to clean it and put it back on, but no success.... after ~10 minutes more on my bike, it "magically" started registering HR again.... Very weird.... Hope it is SW and not HW related though
At times I have the same problem with the heart sensor. In any case, it's very frustrating for a watch that calls itself sports / Fitness.
Well i found out that if i move the watch on my wrist during ECG, it ends with "Atrial fibrillation" and the curve looks like garbage
If i have the watch tight on the wrist, it ends sinusal and regular, clean...
So i'd guess that the drops might come from the watch not being secured enough on the wrist. Just tighten it very well before walk/run.
mafy31 said:
Well i found out that if i move the watch on my wrist during ECG, it ends with "Atrial fibrillation" and the curve looks like garbage
If i have the watch tight on the wrist, it ends sinusal and regular, clean...
So i'd guess that the drops might come from the watch not being secured enough on the wrist. Just tighten it very well before walk/run.
Click to expand...
Click to collapse
That was my first thought as well. But it behaves the same way when tightened everywhere from "comfortably loose" to "i think i cut off blood circulation to my hand" :/
early firmware issues perhaps? did you reboot the watch (pressing the bottom button until you see "rebooting" on the display)?
if you experienced better results from older galaxy watches then give the firmware some time to mature.
i use my elliptical daily and whilst i don't like to have a watch on my arm , i left it on to test the auto exercise feature. it picked up i was using an elliptical and the stats/vitals all looked in line with what i expected -- so no dropouts in hr. ive the lte version.
If it's not firmware (and probably not - mine was great out of the box), then it's a hardware issue (wasn't there a clear film on the back of the watch - did you remove that?).
I have not tested running, but brisk walking, riding an exercise bike, and sleeping and all other times of the day the heart rate is spot on for me. It definitely doesn't "drop" and stop reading. If anything, it would just spit out an inaccurate reading for a bit during strenuous exercise.
Epedemic said:
That was my first thought as well. But it behaves the same way when tightened everywhere from "comfortably loose" to "i think i cut off blood circulation to my hand" :/
Click to expand...
Click to collapse
hi exactly the same i tightened the strap of the watch to have traces of it. And always inconsistencies with the heart sensor while running. In any case looking forward to having the next update.
marctronixx said:
early firmware issues perhaps? did you reboot the watch (pressing the bottom button until you see "rebooting" on the display)?
if you experienced better results from older galaxy watches then give the firmware some time to mature.
i use my elliptical daily and whilst i don't like to have a watch on my arm , i left it on to test the auto exercise feature. it picked up i was using an elliptical and the stats/vitals all looked in line with what i expected -- so no dropouts in hr. ive the lte version.
Click to expand...
Click to collapse
How long did you have it track your workout? It seems the problem usually first starts after x minutes, and from there on it seems (to me) completely random when it starts working again (during the workout). I think i will try to see if i can spot it doing it, stop the workout mode, and see if it does HR instantly in "non-workout-mode"... I encourage others to try this too to gather some data.
*edit*: Reboot have been tried to no effect right before workout, but not during (which also kinda defeats the point), and there is no film on the watch.
Looking around, i found this thead about a similar problem one of the older watches: https://us.community.samsung.com/t5/Galaxy-Watch/Galaxy-watch-heart-rate-sensor/td-p/389847/page/7
Going to try out some of the things: 1st: turning off diagnostics. Will keep you in the loop. *edit*: Nope didn't work.
Next: Turning off always on NR monitoring. *edit*: Nope!
Third: Turning off sensor permits for power saving. *edit*: Nope, also didn't work.
Epedemic said:
How long did you have it track your workout? It seems the problem usually first starts after x minutes, and from there on it seems (to me) completely random when it starts working again (during the workout). I think i will try to see if i can spot it doing it, stop the workout mode, and see if it does HR instantly in "non-workout-mode"... I encourage others to try this too to gather some data.
*edit*: Reboot have been tried to no effect right before workout, but not during (which also kinda defeats the point), and there is no film on the watch.
Click to expand...
Click to collapse
I run errands and I always have the problems. The heart rate sensor stops at times .... And when it resumes it completely wrong. With very random measurements.
Beretta143 said:
I run errands and I always have the problems. The heart rate sensor stops at times .... And when it resumes it completely wrong. With very random measurements.
Click to expand...
Click to collapse
My readings seems fine, once it, randomly, resumes. (Eg 140-160 when biking at a fast but not furious (hehe) pace)
Compared to the apple watch it's very finicky. I have to tighten the watch band ridiculously in order to get HR and ECG.
I think the Apple watch is a better overall product.
Update incoming: https://doc.samsungmobile.com/SM-R855F/TGY/doc.html Hope this is what we're looking for.... (Not out in NEE region yet though)
Epedemic said:
Update incoming: https://doc.samsungmobile.com/SM-R855F/TGY/doc.html Hope this is what we're looking for.... (Not out in NEE region yet though)
Click to expand...
Click to collapse
Very good news.