Malfunctions due to display protection - Samsung Galaxy Tab S6 Questions & Answers

After I fixed a display protection glas on the screen, the tablet is getting a black after some minutes and it takes up to three minutes until the tablet is available again. Therefore, I checked the Galaxy Tab S6 manual: There is a hint that covering the light sensor with screen protection can cause problems. My screen protection glas and also the others I found on the market do not have a hole on the place of the light sensor.

Try Alien Surface screen protector for Tab S6. I saw they have both holes on the screen protector.
In my country unfortunately is on pre order for the moment.
Link from my country online shop of alien surface for you to check: https://aliensurface.ro/produs/sams...6-alege_acoperirea_telefoane-ecran_precomanda

I got a pack of 3 glass protector from Amazon and after installing the first one the tablet became very laggy. Saw your post here and the manual does indeed say not to cover any of the front sensors with a protector. These only have a cutout for the camera. So I took it off and the tablet was still super laggy. Decided to install the second protector and do a factory reset. So far the lag seems gone. I won't say it's a permanent solution until I've spent more time with it, but I'll report back if the lag returns or not. As much as I hated doing a factory reset so soon after getting the tablet, if it fixed the problem I'll be happy. But yes, it seems covering the sensors can affect this thing.
EDIT: So far things are still going smoothly today. Have everything restored from the Smart Switch PC program and set back up. Have restarted the tablet a few times just to check even. So it seems the factory reset fixed my problems. Don't know if it matters or not, but just to be sure I did my reset from the recovery mode. So my advice for anyone that runs into issues after installing a screen protector is to back everything up, with your on device cloud options and the Smart Switch PC program imo, then factory reset and you should be good to go.

Related

AP4 Touchscreen dead ???

Hi
i flashed AP40 as per all the rite moves
Worked fine for 1st day
Then when turning it on it froze
Then unfroze but everything works fine as long as you use the joystick on side and windows key and ok
ie the touchscreen does not respond any more
i reflashed ap40 same problem
Now it cannot align the screen as touchscreen is not seeing anything ???
Help she cried
mw22 said:
Hi
i flashed AP40 as per all the rite moves
Worked fine for 1st day
Then when turning it on it froze
Then unfroze but everything works fine as long as you use the joystick on side and windows key and ok
ie the touchscreen does not respond any more
i reflashed ap40 same problem
Now it cannot align the screen as touchscreen is not seeing anything ???
Help she cried
Click to expand...
Click to collapse
Have you tried a hard reset? If not, then try it. It should prompt you back through the start-up and screen calibration as a new flash. For info on a hard reset, read the Wiki. You can also try to flash back to the modified AP3 and see if your device is working there. You may actually have a hardware issue.
hi
foun problem Screen protector had becom desensitised and no feedback on screen ??
I left device in car and it became hot screen protector got slight brown mark on edge
new one on me
Now working fine
Whew close call
mw22 said:
hi
foun problem Screen protector had becom desensitised and no feedback on screen ??
I left device in car and it became hot screen protector got slight brown mark on edge
new one on me
Now working fine
Whew close call
Click to expand...
Click to collapse
Glad you fixed your problem. Someone else in the forum had screen problems, I will advise him to try a new screen protector before he sent his unit off for repair.
please do
as i said first for me
normally screen protector packs up gradually but this time just went in one hit ?
I just picked up a new screen protecter for my 7501 from Clear Protector,
it's supposed to be bullet proof,time will tell.
It went on easily and you can't tell it from the original
screen,this stuff is supposedly used on helicopter rotor
blades lead edges to prevent damage from airborne debris.
At $9.95 an application it's not cheap.
bigtsr said:
I just picked up a new screen protecter for my 7501 from Clear Protector,
it's supposed to be bullet proof,time will tell.
It went on easily and you can't tell it from the original
screen,this stuff is supposedly used on helicopter rotor
blades lead edges to prevent damage from airborne debris.
At $9.95 an application it's not cheap.
Click to expand...
Click to collapse
Could you post a link? I always have many problems putting screen protectors on, and the end result is not good - bubbles round the edges etc. even with quality ones, like the Martin protector I have now. I wouldn't mind paying a bit extra for a decent one that went on easily and looked good.
JonSlater said:
Could you post a link? I always have many problems putting screen protectors on, and the end result is not good - bubbles round the edges etc. even with quality ones, like the Martin protector I have now. I wouldn't mind paying a bit extra for a decent one that went on easily and looked good.
Click to expand...
Click to collapse
Yes no problem for the link,make sure you follow theur instructs exactly
re install.
http://cgi.ebay.ca/CP-SCREEN-PROTEC...ryZ20336QQssPageNameZWDVWQQrdZ1QQcmdZViewItem
www.ClearProtector.com

[Q] Change sensitivity of proximity sensor

Is there any way to change the sensitivity of the proximity sensor. It seems every screen protector I try makes the screen turn off when in a call even without anything near the sensor. I had to cut one of the screen protectors to get around it (but had messed up a corner when applying so I replaced it)
Or is there a way to completely disable it so I just have to hit the power button when in a call to manually turn the screen on or off.
+1
Dont have the same problem but would be helpful.
There is a distance setting in the build.prop file. You could try adjusting that and seeing if that helps.
Sent from my MB860 using XDA Premium App
Perfect. Changed the value (increased it from default of 60) and its working great now. Thanks for that tip.
Sent from my MB860
Well after further testing seems that it didn't fix the problem. Seemed to work when I first made the changes but now the screen is stroll turning off and no matter what I change the value to I can't get the proximity sensor to work right.
Spectre51 said:
Well after further testing seems that it didn't fix the problem. Seemed to work when I first made the changes but now the screen is stroll turning off and no matter what I change the value to I can't get the proximity sensor to work right.
Click to expand...
Click to collapse
According to the official Atrix manual -
http://www.motorola.com/staticfiles...s/StaticFiles/Atrix_US-EN_UG_68014798001B.pdf
Note: Your touchscreen might
stay dark if the sensor just
above it is covered. Don't use
covers or screen protectors (even clear ones) that
cover this sensor. To find Motorola accessories for
your phone, visit www.motorola.com/products.
Anyway, why do you guys keep using the screen protectors with this gorilla glass phones? I have carried Moto Milestone in my pocket for a year and D2G for 3 months and there are no scratches on them whatsoever.
I use them on every phone I get because although it is gorilla glass it can still get scratches under the right conditions and I for one do not want my $400+ phone to have a scratch on the screen. Never had a phone that had issues like this with screen protectors and the proximity sensor. Multiple iPhones, Dell streak, nexus one, droid, galaxy s. I've tried two different screen protectors with the atria and both have this issue.
I'm having issues with my proximity sensor too, but it seems that I can't make it turn off the screen when I'm talking. I'm not using any screen protector but I do have a case. It was working fine till a week ago but now I just have to block the phone every time I get a call.
The only difference is that I've installed 2 new games, maybe those are affecting the sensor?
Another thing that isn't working anymore is the auto brightness that's always set to minimum, no matter the light conditions. The phone is online for 260+ hours already (had it go to 500+ before but had to turn it off to add a micro sd card, just to be sure it would find it).
Spectre51 said:
I use them on every phone I get because although it is gorilla glass it can still get scratches under the right conditions and I for one do not want my $400+ phone to have a scratch on the screen. Never had a phone that had issues like this with screen protectors and the proximity sensor. Multiple iPhones, Dell streak, nexus one, droid, galaxy s. I've tried two different screen protectors with the atria and both have this issue.
Click to expand...
Click to collapse
Ugh... thing is if you drop your phone, it could crack both with screen protector and without one. If you grind the screen against your keys, it will get scratched through the protective film.
If you use it normally - the chance of scratching it really small. Just my 2 cents.
xploited said:
Ugh... thing is if you drop your phone, it could crack both with screen protector and without one. If you grind the screen against your keys, it will get scratched through the protective film.
If you use it normally - the chance of scratching it really small. Just my 2 cents.
Click to expand...
Click to collapse
My wife's phone had a screen protector on and got scratched by being in her purse. The actual screen though had no marks. The screen protectors help. Obviously each incident is different but they can help prevent some damage so in my opinion they are worth it.
Sent from my MB860
Hi there,
Got the same trouble..... but I just noticed it work fine at the sun (outdoor)..... turn the screen off in the shadow..... and switch on in the sun....
so I think a light adjustment has to be done.... but where ?...
Thanks to developers

Anyones front camera crashing/not working?

So all of a sudden my v10 has starting crashing whenever a program tries to access the front camera including the stock camera application. I am not able to see anything out of the front camera before it crashes. I tried wiping cache and even hard resetting the phone but nothing has fixed it so I'm guessing its a hardware issue. I am trying to avoid sending it to LG due to a couple slight hairline cracks on the screen, it actually cracked under the tempered glass screen protector I had on it from a very small drop while in a obliq case. I am not sure if they will use this against me and tell me I'm **** out of luck and have to pay a crazy amount of money to have it repaired. Also, other than obvious marks someone could accidentally make when dissembling the phone, is there any indicators that tell LG that the phone has been opened up at all? From the dis-assembly videos I have watched it seems as if there's nothing there to indicate it was open or not.

Phone Difficult To Wake Up

Sometimes if my G5 has not been used for an hour or so, it is refusing to wake up from double tap, power button or volume button quick shortcut. Only plugging it in has seemed to wake it up on these occasions.
Has anyone else had this issue?
Not yet.
I am chocking this up to poor software implementation using the ambient sensor. I found similar issues that the OP was describing, and in my testing, was able to verify something is wonky with how the phone "thinks" it is being looked at or not.
Simply put, if you cover the ambient sensor and the camera (on my device) with your finger, while the phone is asleep/screen off, no matter how many times you press the power button on the back/fingerprint scan, the screen will fail to come up. The moment I introduce some light into the room (open up the sensor), I am able to get response back on the phone.
Ran into this issue last night and for the life of me couldn't figure it out until daylight hit . Also, my case might be obstructing the sensor (lifeproof fre), but I also noticed the issue with no case on.
Logically, I imagine LG was trying to limit power consumption with accidental presses, etc. If the phone knows it is in a dark place, it won't respond (because it thinks it is in a pocket or a bag of some sort). My rebuttle for this is how do they anticipate planning for night-time use of the phone, or are we limited to a daywalker only device?
I am heading down to an AT&T store and seeing if I can replicate this on demo units as well. In which case, we know the issue is inherent in the device (and hopefully addressed in a software update). If I am not able to replicate this at the store, then I bet OP and I got bad units.
Thanks for looking. If anyone has any feedback, or can repro or not repro this issue, please chime back .
mikeythedude said:
I am chocking this up to poor software implementation using the ambient sensor. I found similar issues that the OP was describing, and in my testing, was able to verify something is wonky with how the phone "thinks" it is being looked at or not.
Simply put, if you cover the ambient sensor and the camera (on my device) with your finger, while the phone is asleep/screen off, no matter how many times you press the power button on the back/fingerprint scan, the screen will fail to come up. The moment I introduce some light into the room (open up the sensor), I am able to get response back on the phone.
Ran into this issue last night and for the life of me couldn't figure it out until daylight hit . Also, my case might be obstructing the sensor (lifeproof fre), but I also noticed the issue with no case on.
Logically, I imagine LG was trying to limit power consumption with accidental presses, etc. If the phone knows it is in a dark place, it won't respond (because it thinks it is in a pocket or a bag of some sort). My rebuttle for this is how do they anticipate planning for night-time use of the phone, or are we limited to a daywalker only device?
I am heading down to an AT&T store and seeing if I can replicate this on demo units as well. In which case, we know the issue is inherent in the device (and hopefully addressed in a software update). If I am not able to replicate this at the store, then I bet OP and I got bad units.
Thanks for looking. If anyone has any feedback, or can repro or not repro this issue, please chime back .
Click to expand...
Click to collapse
I have also experienced this issue (opened a thread a week ago). I have the exact same lifeproof case and my problem occured at night as well. Phone did not want to wake up at all until I either restarted it or had some light in the room.
Same problem, same case.
What I have found is if you pull the phone out of the case it wakes up. Thinking proximity sensor.
Sent from my LG-H830 using XDA-Developers mobile app
Yup. It really doesn't take much extra coding for them to allow the power button to "Always Wake" the device... I imagine there will be an update in the near future.
As for me... jumping ship to the S7 edge. I really liked the G3, and was hoping this phone could have been that for me... Well, not like I really swap batteries out often anyway
Same case. Same issue. Take the phone out of the case and throw a blanket over yourself and the phone. (Simulating night) and my screen unlocks easy peasy. Something about this lifeproof case. You would think this issue would have been caught in testing and QC.
Yes the phone has a built prox. override. But it only becomes an issue at night. Outside of the case I have no issues with prox. sensor.
I have experuenced this exact same issue with my g5. Whenever its in the dark the power button nor the double tap will wake the screen when in the lifeproof fre case. When out of the case the phone works just fine.
Word to the wise though if you have a zagg glass screen protector and drop your phone both the screen protector and the screen with shatter even if in the lifeproof case. I just experienced this and now have a replacement phone. Just a heads up.
soninja8 said:
I have also experienced this issue (opened a thread a week ago). I have the exact same lifeproof case and my problem occured at night as well. Phone did not want to wake up at all until I either restarted it or had some light in the room.
Click to expand...
Click to collapse
I have the rs988 variant and I have noticed this behavior when screen is in always on mode: if I suddenly change from light to dark by covering sensors, the always on clock goes out and nothing I do will allow it to wake up, until I allow brighter light again and the clock reappears. and I can use the double tap and power button again to see the screen. I also notice that the always on clock seems to have an auto brightness independent of the screen settings - I leave screen at 50% no auto brightness, yet I still see clock light levels dim in low light, One other thing - I notice that when I answer a call the screen blanks out (the way it is supposed to ) but does not reappear until I press the power button, just taking away from my ear does not bring display back; I also have the lifeproof case. and just removed it and verified my display now works when I take away from my ear; I just took some spray lens cleaner and cleaned all the surfaces of the phone and case with a microfiber cloth and put it back together and has vastly improved the issue, maybe gone, not sure yet. Update: seems like no matter how clean it is there is still a problem with the case doing something to the proximity detector, cleaning made it better. I can always wake up with the power button for the calling screen(sometimes swiping across top sensor too), wonder if the sensor is a passive light sensor or active (rf/infrared emission)
Same issue here same life proof case however it's getting worse as I am a mechanic and this phone goes through greasy hell. The plastic lenses on the lifeproof case are getting scratched and it's getting worse. It is also having a hard time autofocusing through this case. When you pull it out the phone is gorgeous and looks brand new. Good case but it has some downsides. Still better than a broken phone.
daniel3016 said:
Same issue here same life proof case however it's getting worse as I am a mechanic and this phone goes through greasy hell. The plastic lenses on the lifeproof case are getting scratched and it's getting worse. It is also having a hard time autofocusing through this case. When you pull it out the phone is gorgeous and looks brand new. Good case but it has some downsides. Still better than a broken phone.
Click to expand...
Click to collapse
There are allot of other cases you can use but not waterproof. That really sucks good thing for this thread I was going to buy a lifeproof case. Using a otterbox defender right now. Thanks for the post guys saved me some grief.
still under warranty?
daniel3016 said:
Same issue here same life proof case however it's getting worse as I am a mechanic and this phone goes through greasy hell. The plastic lenses on the lifeproof case are getting scratched and it's getting worse. It is also having a hard time autofocusing through this case. When you pull it out the phone is gorgeous and looks brand new. Good case but it has some downsides. Still better than a broken phone.
Click to expand...
Click to collapse
if still under warranty, see if they will honor it. They did with mine but that was right at the beginning when these problems were linked to the case; mine was in the first 3 months, but the new one worked well for a while, now a little flakey again but not enough to bother me...too bad, a great case otherwise
mikeythedude said:
I am chocking this up to poor software implementation using the ambient sensor. I found similar issues that the OP was describing, and in my testing, was able to verify something is wonky with how the phone "thinks" it is being looked at or not.
Simply put, if you cover the ambient sensor and the camera (on my device) with your finger, while the phone is asleep/screen off, no matter how many times you press the power button on the back/fingerprint scan, the screen will fail to come up. The moment I introduce some light into the room (open up the sensor), I am able to get response back on the phone.
Ran into this issue last night and for the life of me couldn't figure it out until daylight hit . Also, my case might be obstructing the sensor (lifeproof fre), but I also noticed the issue with no case on.
Logically, I imagine LG was trying to limit power consumption with accidental presses, etc. If the phone knows it is in a dark place, it won't respond (because it thinks it is in a pocket or a bag of some sort). My rebuttle for this is how do they anticipate planning for night-time use of the phone, or are we limited to a daywalker only device?
I am heading down to an AT&T store and seeing if I can replicate this on demo units as well. In which case, we know the issue is inherent in the device (and hopefully addressed in a software update). If I am not able to replicate this at the store, then I bet OP and I got bad units.
Thanks for looking. If anyone has any feedback, or can repro or not repro this issue, please chime back .
Click to expand...
Click to collapse
It's not a bug and not poor implementation. Its not light for "dark rooms" lol.. As far as I know it's the proximity sensor. When it is blocked it means the phone is in a pocket or bag and should not register taps. It really makes sense. If you dont xover the sensor and double tap doesn't work ..well.. Well, eother you have defective device or sensor , or the sensor is blocked (maybe bad screen protector?). This didnt happen with my G5 even once. It works 100% (assuming I tapped the same place)
Are the problems as described in this thread still manifesting on current firmware?

S21 Ultra Finger Print Sensor Garbage compared to S10e, return phone??

I had a S10e and honestly it was probably one of the best phones I have ever owned. The size was perfect, the cameras were excellent, and the best feature of all was the fingerprint sensor. It worked virtually 100% of the time, first time, no matter what. Sure Apple had face id, but it didn't really matter because the fingerprint sensor was so effortless.
I work with my hands, my hands are frequently dried out, or dirty. Frankly I never thought anything of this because it never created any issues.
I just upgraded to the s21 ultra because I wanted the new cameras and now I regret it.
The fingerprint sensor literally does not work. I have tried removing the TPU screen protector that I have on it. I have four fingerprints saved and they are all of my right thumb. And it literally won't work. every time I pull my phone out of my pocket it tries and tries until it locks itself. When I go to verify fingerprints it gets it maybe one out of 10 attempts. When I am trying to input fingerprints, half the time it says it can't even detect the finger on the screen.
Another major problem is glass screen protectors work much better and you can get a glass screen protector for an s10e for a dollar. You cannot put glass screen protectors on s21u without enormous expense and effort. And they still compromise the fingerprint sensor. The user experience of the s21u has been frankly absolutely terrible compared to the s10e.
And their face ID is completely useless as well. Most of the time it doesn't work and if you are in the dark or low light forget about it.
I really want this phone because of the camera lenses. The 10x lens really is amazing. 100x is probably what you can get to cropping images anyway.
but none of that matters because it's something that you use every once in awhile. You need to get into your phone hundreds of times a day. If they're access technology doesn't work in my opinion the phone is a bust.
It is driving me crazy.
Are they going to fix this or should I get rid of this thing and go back to an s10e?
Read the post literally right above yours about the 30 second fix. I've had many Samsung phones with the fingerprint sensor underneath the screen and I agree with you totally, it does not work. How this isn't the very first topic discussed on any phone review is beyond me. It should be class action lawsuit.
But, my fingerprint sensor works reasonably well now by doing the short 'fix' above. It wasn't targeted to fixing the fingerprint sensor, kind of a by-product. I suggest you give it a try, literally takes 30 seconds and can be reverted back in the same 30 seconds.
Worth a try, good luck.

Categories

Resources