Related
Hey guys,
hope someone can help me.
I've the feeling that my light sensor might be damaged.
The setting is on automatic light regulation and i've the feeling that the
screen is very dark. Is there any possiblity to check if the light sensor still works fine?
I've already put my finger for a few seconds on it and nothing changes.
I also read in the guide that the screen should wake up when you wipe over the switched off device.
Unfortunately nothing happens when i do so.
Thanks a lot for your support
schelde_sun said:
Hey guys,
hope someone can help me.
I've the feeling that my light sensor might be damaged.
The setting is on automatic light regulation and i've the feeling that the
screen is very dark. Is there any possiblity to check if the light sensor still works fine?
I've already put my finger for a few seconds on it and nothing changes.
I also read in the guide that the screen should wake up when you wipe over the switched off device.
Unfortunately nothing happens when i do so.
Thanks a lot for your support
Click to expand...
Click to collapse
Autobrightness has been too dark since the S2. The S3 also suffers from that bug as does the Note 2. Unless Samsung fixes it with a update you`ll have to wait for a hack and root the phone to be able to change it.
gee2012 said:
Autobrightness has been to dark since the S2. The S3 also suffers from that bug as does the Note 2. Unless Samsung fixes it with a update you`ll have to wait for a hack and root the phone to be able to change it.
Click to expand...
Click to collapse
Thanks a lot for this information. I didn't know this, as it's my first Samsung mobile.
But my impression is that it worked fine, and unfortunately the note 2 fell down at weekend and
now i've the feeling that the regulation is not correct since then. Is there any test to try if the light sensor still works?
And normally the switched off screen should wake up when i swipe over the screen, right? Because it doesn't work, or is it necessary to set up some settings?
Thanks a lot again for the help!
schelde_sun said:
Thanks a lot for this information. I didn't know this, as it's my first Samsung mobile.
But my impression is that it worked fine, and unfortunately the note 2 fell down at weekend and
now i've the feeling that the regulation is not correct since then. Is there any test to try if the light sensor still works?
And normally the switched off screen should wake up when i swipe over the screen, right? Because it doesn't work, or is it necessary to set up some settings?
Thanks a lot again for the help!
Click to expand...
Click to collapse
I think there's a light sensor test in the service menu (can't remember the dialer code to access it though) and for the phone to wake when you swipe over the screen you need to enable "Quick Glance" in Settings > Motion
schelde_sun said:
Hey guys,
hope someone can help me.
I've the feeling that my light sensor might be damaged.
The setting is on automatic light regulation and i've the feeling that the
screen is very dark. Is there any possiblity to check if the light sensor still works fine?
I've already put my finger for a few seconds on it and nothing changes.
I also read in the guide that the screen should wake up when you wipe over the switched off device.
Unfortunately nothing happens when i do so.
Thanks a lot for your support
Click to expand...
Click to collapse
Hello bro,
You might want to test it with *#0*# code using dialpad.. hope this help..
Sent from my GT-N7100 using xda app-developers app
Hi everybody! I'm experiencing an issue with the proximity sensor of my Galaxy Note 2 i317. I think it is screwed up because during calls screen goes off either if the phone is far away from any objects. I don't have a screen protector, so the problem is not there. I was looking for a way to disable the sensor once and for all, so I installed Hardware Disabler from play store and searched for the drivers. The problem is that I can't find it among the list. I know the drivers should be the one from Capella Microsystems, CM36651 but there is nothing like that among the list. I also checked "/" in the parameters settings but nothing. I know I can disable the sensor on samsung stock ROMS via the call settings, but it doesn't solve the problem with VOIP apps like Viber, or Skype or any other like it. But the real matter is that I wish to install a CM10.1 ROM, and that option is missing there so that problem persists in normal calls too.
Now, my questions are :
1) Am I doing something wrong?
2) is it possible that the sensor is screwed up because the drivers are missing somehow? And is there a way to fix it in this case?
3) Are there other ways to disable it?
4)Is there an option in CM10.1 or other AOSP ROMS to disable the sensor during normal calls at least?
Thanks for the help!!
Dialer call settings allow you to toggle the sensor to stay on or off. ..
When combined with the general proximity setting for the phone to stay on while looking at the screen. ..
The device should stay awake ...
Try turning both settings on....
If the device still sleeps. ..your device may have a problem. .
But do not load an AOSP build until you are sure the device functions normally. ..as CM does not contain the constant wake option under general settings. ..g
gregsarg said:
Dialer call settings allow you to toggle the sensor to stay on or off. ..
When combined with the general proximity setting for the phone to stay on while looking at the screen. ..
The device should stay awake ...
Try turning both settings on....
If the device still sleeps. ..your device may have a problem. .
But do not load an AOSP build until you are sure the device functions normally. ..as CM does not contain the constant wake option under general settings. ..g
Click to expand...
Click to collapse
Thanks for your help! Yes I'm using it like you said, on stock ROM. But I wished to know if there is a way to do something like that on any AOSP ROM out there, or to completely disable the sensor.
giulytheboy said:
2) is it possible that the sensor is screwed up because the drivers are missing somehow? And is there a way to fix it in this case?
3) Are there other ways to disable it?
Click to expand...
Click to collapse
Hey there, I have a similar problem due to a cracked glass, but I figured out a little hack to solve it and disable the sensor.
2) The driver files aren't missing; I'm pretty sure that Hardware Disabler just doesn't know where to look. The driver files are located in:
/sys/devices/virtual/sensors/proximity_sensor/
Since Hardware Disabler can't look there, that option is useless.
Do this at your own risk, BTW.
3) You'll need a hex editor app to do this. Open the file named "prox_thresh" (I use ES file explorer) and select your hex editor to edit the file. You'll see a lot of 0's, but you'll need to edit the first line only. Change
31 32 0a
to
30 0a
The rest of the line is just 00.
This seems to work, although I'm pretty sure it's only temporary because I can't get the app to save prox_thresh due to a weird permission error. Maybe you can figure that out.
I'm not sure if deleting the driver folder would work, but I'm not so desperate to try that yet.
Let me know if that helps!
Sent from my SGH-I317 using xda app-developers app
Possible simple fix
I had the same problem. Sometimes the proximity sensor is working well but covered with dirt from the inside.
I gently inserted a guitar pick between the glass and the sensor (light pressure so it will open a crack) and cleaned the glass a little from the inside.
I tested it before and after with an app called proximity finder. it really fixed the problem.
hello everyone , so i use to have this bug back to kitkat also but it wasn't happening as often as it doesnt now that i have lollipop rom installed on my galaxy tab s T705 , the issue is with touch key lights which stays on even when i have them always off from settings , they act super weird when they are in that mode , they go off few sec after screen is off and if i shake the device they go on again as it looks like they are connected to accelerator sensor or something lolz ,the solution is super easy tho just hit the power saving on and then off again and they work normally again i heard some other ppl dealing with same issue but i wanted to know if there is a perma solution for it or not , im sure its a software issue but is there a way to fix it ?
Install a custom rom like cyanogen or something stock based.
I have the same problem. I usually have it set to turn the lights off after 6 seconds, but after a couple of days they don't work anymore. I would change the setting to off, then on, then back to 6 seconds, and it'll work again. After a few more days, they stop. I haven't seen a permanent fix for this.
Sent from my SAMSUNG-SM-G925A using Tapatalk
Same for me. Would usually opt to have the buttons backlight always off, but randomly it starts actin like always on, although the settings remains 'always off'. Toggling the setting to anything else and back to always off fixes the problem temporeraly.
Im running stock swiss lollipop on my t700.
Yes, this is driving me nuts too! I hope they resolve this in the next update and soon!
Sent from my SM-T700 using Tapatalk
Same problem with the lights on after a while even though set to always off. Seems to work properly under 1.5 sec setting option. I would love for the lights to be always off though.
LakersDroid said:
Same problem with the lights on after a while even though set to always off. Seems to work properly under 1.5 sec setting option. I would love for the lights to be always off though.
Click to expand...
Click to collapse
Me too have the touch key settings to always off and found the same problem.
In my case I think it only happens when I plug the Tablet to AC.
Did this happen to anyone under another circumstances?
Thanks in adavance!
LakersDroid said:
Same problem with the lights on after a while even though set to always off. Seems to work properly under 1.5 sec setting option. I would love for the lights to be always off though.
Click to expand...
Click to collapse
I have the same problem as everyone else, which I am very "happy" to hear because I am not the only one apparently dealing with it. I purchased the tablet a couple weeks ago and noticed that even though the setting for the touch key backlight is "always off", it goes on when I open the case, and sometimes goes on and off and goes weird. I contacted Samsung and they requested that I send in the tablet for repairs, so I did. At the same time, I contacted Amazon and they sent me another Tab S tablet. I have a month to return the other one so I figured I'll try this second one and see if I continue to have the same issues like the first one. Sure enough, I had the second tablet for less than a day and it's doing the exact same thing! So far the 1.5 second setting seems to keep the darn lights off. Sometimes doing a soft reset will fix the issue temporarily, but not permanently. If anyone figures out how to fix this, let us know! I'll be following this thread. I hope there's a software update to fix this.
TLAgnesB said:
I have the same problem as everyone else, which I am very "happy" to hear because I am not the only one apparently dealing with it. I purchased the tablet a couple weeks ago and noticed that even though the setting for the touch key backlight is "always off", it goes on when I open the case, and sometimes goes on and off and goes weird. I contacted Samsung and they requested that I send in the tablet for repairs, so I did. At the same time, I contacted Amazon and they sent me another Tab S tablet. I have a month to return the other one so I figured I'll try this second one and see if I continue to have the same issues like the first one. Sure enough, I had the second tablet for less than a day and it's doing the exact same thing! So far the 1.5 second setting seems to keep the darn lights off. Sometimes doing a soft reset will fix the issue temporarily, but not permanently. If anyone figures out how to fix this, let us know! I'll be following this thread. I hope there's a software update to fix this.
Click to expand...
Click to collapse
I believe this is a software bug so all tab s running the 5.0.2 lollipop will have this issue.
And to reply to the other poster: The problem will occur after a while, the lights will just turn on and stay on when you wake the tablet. Changing the setting and choose Always Off will fix it but it will come back after a while.
LakersDroid said:
I believe this is a software bug so all tab s running the 5.0.2 lollipop will have this issue.
And to reply to the other poster: The problem will occur after a while, the lights will just turn on and stay on when you wake the tablet. Changing the setting and choose Always Off will fix it but it will come back after a while.
Click to expand...
Click to collapse
Is there a way to get it back to the stock ROM? I'd rather avoid this light issue until an update to correct this comes out. Thoughts?
TLAgnesB said:
Is there a way to get it back to the stock ROM? I'd rather avoid this light issue until an update to correct this comes out. Thoughts?
Click to expand...
Click to collapse
Yes but you will need root.
LakersDroid said:
I believe this is a software bug so all tab s running the 5.0.2 lollipop will have this issue.
And to reply to the other poster: The problem will occur after a while, the lights will just turn on and stay on when you wake the tablet. Changing the setting and choose Always Off will fix it but it will come back after a while.
Click to expand...
Click to collapse
I heard that there's a new update available for the Tab S. (I already returned my tablet before my 30 days to get a full refund.) Did any one get the new update, and if so, did it fix the issues like this touch key light?
Hey,
I had this problem on the original KK software - upgraded to Lollipop a few days back and I still have the bug... in fact, it is even worse! Occurs more frequently than on LP.
I wouldn't mind leaving the lights on all the time, but they're so damn BRIGHT, and there's no way to adjust the backlight intensity!
Cheers,
Su
I found this solution on another forum...
If you enable smart stay, the touch key light duration will work properly.
Any further movement on this?. I've found that if I take my tab out of the book case the problem goes away. Seems like it's a bug with the case sensor.
No movement that I'm aware of. I'm really frustrated that there hasn't been a fix after all this time. I'm holding out hope that if there is ever an update to Marshmallow, that the issue will go away. Interesting observation about the case -I have a book case on mine. I'll remove it and see what happens...
So I seem to have a whole bunch of problems with my D851, and am curious if others have the same problems and know of fixes. Mine has 20g (stock Lollipop) installed, and is rooted.
Main problem: enabling Xprivacy makes this phone become significantly slower. The settings menu crawls with Xprivacy turned on. Anyone else experience this?
Auto brightness is *way* too dim to use. Surely, I must not be the only person experiencing this? I see a few people mention it in passing, but it doesn't seem to be an big deal. Are people not using auto brightness? Or do most folks not have this issue? All other devices I have with Lollipop allow a brightness range if set on auto. This one doesn't ? Can I get this feature somehow?
Even when I set the brightness manually, it keeps getting reset to 100% some half the times it wakes up from sleep. Anyone else experiencing this? Anyone know of a fix?
Also, the display off time never gets set. I set it to 30sec or 1min, and it always gets reset two 2 min.
The notification LED is virtually useless. It blinks once in like 20 seconds when I get an email (gmail app). I rely on this. Is there a fix to get it to blink every second or 2 seconds? Light manager didn't work.
What I don't understand is, since I experienced all these issue on pretty much a phone out of the box + rooted, I'm surprised they don't seem to be common problems.
Thanks in advance.
fivemill said:
So I seem to have a whole bunch of problems with my D851, and am curious if others have the same problems and know of fixes. Mine has 20g (stock Lollipop) installed, and is rooted.
Main problem: enabling Xprivacy makes this phone become significantly slower. The settings menu crawls with Xprivacy turned on. Anyone else experience this?
Auto brightness is *way* too dim to use. Surely, I must not be the only person experiencing this? I see a few people mention it in passing, but it doesn't seem to be an big deal. Are people not using auto brightness? Or do most folks not have this issue? All other devices I have with Lollipop allow a brightness range if set on auto. This one doesn't ? Can I get this feature somehow?
Even when I set the brightness manually, it keeps getting reset to 100% some half the times it wakes up from sleep. Anyone else experiencing this? Anyone know of a fix?
Also, the display off time never gets set. I set it to 30sec or 1min, and it always gets reset two 2 min.
The notification LED is virtually useless. It blinks once in like 20 seconds when I get an email (gmail app). I rely on this. Is there a fix to get it to blink every second or 2 seconds? Light manager didn't work.
What I don't understand is, since I experienced all these issue on pretty much a phone out of the box + rooted, I'm surprised they don't seem to be common problems.
Thanks in advance.
Click to expand...
Click to collapse
I think maybe you got a dud. Try flashing a rom and see if problems stop,if they don't then get another phone through warranty
Still_living714 said:
I think maybe you got a dud. Try flashing a rom and see if problems stop,if they don't then get another phone through warranty
Click to expand...
Click to collapse
Thanks, I think that was a part of it, but not all of it. I tried flashing stock on a different unit, and I found that the brightness issue was largely (but not fully) better, and the display settings not getting set issue went away. The Xprivacy and LED notification issues remain, and will occur on all units as far as I can tell. I haven't seen anything here that contradicts that info.
fivemill said:
Thanks, I think that was a part of it, but not all of it. I tried flashing stock on a different unit, and I found that the brightness issue was largely (but not fully) better, and the display settings not getting set issue went away. The Xprivacy and LED notification issues remain, and will occur on all units as far as I can tell. I haven't seen anything here that contradicts that info.
Click to expand...
Click to collapse
I have xprivacy and my phone is still very smooth plus my LED works just fine. I even changed the colors
Still_living714 said:
I have xprivacy and my phone is still very smooth plus my LED works just fine. I even changed the colors
Click to expand...
Click to collapse
Thanks a bunch for the info, this is good to know, and good to hear from another D851 user. The Xprivacy issue may be less easy to measure. The LED issue may be more objective. I have no trouble with changing LED colors. It's the blink rate that's at issue. Are you able to get it to blink say, twice per second, or even once per second when you get new email in your gmail app if you use that? Are you using any kind of an LED app?
Also, are you running Lollipop? Stock? Rooted? Thanks.
fivemill said:
Thanks a bunch for the info, this is good to know, and good to hear from another D851 user. The Xprivacy issue may be less easy to measure. The LED issue may be more objective. I have no trouble with changing LED colors. It's the blink rate that's at issue. Are you able to get it to blink say, twice per second, or even once per second when you get new email in your gmail app if you use that? Are you using any kind of an LED app?
Also, are you running Lollipop? Stock? Rooted? Thanks.
Click to expand...
Click to collapse
I'm always rooted lol I'm running fulmics 5.0 and in the settings it gives you the option of length and speed of the LED. I highly recommend that rom if you want to try out marshmallow.
Still_living714 said:
I'm always rooted lol I'm running fulmics 5.0 and in the settings it gives you the option of length and speed of the LED. I highly recommend that rom if you want to try out marshmallow.
Click to expand...
Click to collapse
Very good to know again, thanks for the recommendation! And the LED options are an additional reason. I'll try out fulmics soon.
Hi,
I received my RN8 Pro just yesterday (22nd Oct) (India).
The first thing I noticed is the screen quality.
I find the screen is calibrated a tad bit warmer than usual. Even if you go to the screen settings and tweak it to 'cool', it still remains yellowish.
I came from OnePlus5, which had an AMOLED screen (not fHD/SuperAmoled). There the screen was obviously more crisp, I don't really expect that here. However, the calibration looks bit different if I hold these 2 phones side by side.
What I want to know is, is this just my RN8 Pro, or others also feel the same?
Also, in MIUI where is the 'night light' setting, where I can either manually or automatically turn the screen hue warmer? It's one of the main features in OxygenOS. Actually, the current RN8P calibration looks like 'night light' is already set.
Issue summary:
1) Daytime screen temp looks like as if the 'night mode'/'night light' is already ON. (Note, I don't mean 'reading mode', that's different)
2) Night time screen temp gets very yellowish, almost as if the 'reading mode' is on
3) Screen calibration (warm/default/cool) doesn't change it a lot
4) Can not find the setting to turn off the 'night mode' in #1
Thanks.
In RN8P you can find Night Light in "Reading Mode" in Display option, it turns the screen hue warmer. I'm not sure about the warm color. May "Reading mode" is enabled which is causing this. Try to check that option.
frosthawk said:
In RN8P you can find Night Light in "Reading Mode" in Display option, it turns the screen hue warmer. I'm not sure about the warm color. May "Reading mode" is enabled which is causing this. Try to check that option.
Click to expand...
Click to collapse
No, it's turned off still the screen feelings yellowish.
Exactly. It's so yellowish all the time!
Shubhayudatta said:
Exactly. It's so yellowish all the time!
Click to expand...
Click to collapse
I feel it's not all the time, it's mostly at night. Will compare again now. I got it yesterday afternoon.
Yes. And there is no quick way to disable the night time extra yellow tint.
You think it would be eligible for a replacement?
If you could compare it to another rn8 pro and see an obvious difference then yes you should claim for warranty.
frosthawk said:
If you could compare it to another rn8 pro and see an obvious difference then yes you should claim for warranty.
Click to expand...
Click to collapse
I don't know anyone around who has another RNP8.
I am waiting for others to comment here, for their own devices.
If I find mine is an exceptional issue, I'll try to get it replaced, though I feel that may not exactly come under their replacement policy.
Shubhayudatta said:
I don't know anyone around who has another RNP8.
I am waiting for others to comment here, for their own devices.
If I find mine is an exceptional issue, I'll try to get it replaced, though I feel that may not exactly come under their replacement policy.
Click to expand...
Click to collapse
It's fine in day time, I'm using this phone.
At night the screen turns yellowish automatically, it's miui issue, sceen is fine. Don't bother about replacement, just report the bug from the phone and wait for software update for fix.
@SidDev said:
It's fine in day time, I'm using this phone.
At night the screen turns yellowish automatically, it's miui issue, sceen is fine. Don't bother about replacement, just report the bug from the phone and wait for software update for fix.
Click to expand...
Click to collapse
Goto Settings >> Display >> Reading Mode and turn of Good Night's read option
Its clear that based on the Sunrise and Sunset reading mode is enabling
Its default set as off. And that's the bug, that it's functional even if it's set off.
Shubhayudatta said:
Its default set as off. And that's the bug, that it's functional even if it's set off.
Click to expand...
Click to collapse
Try enabling and disabling it. turn off schedule option if it is enabled.
Check whether night light settings are there in developer option or not
Tried all the enable disable combinations, set as disabled right now, can say it works or not only after the sunset.
And, can't find any related option in the developers setting.
SunilSuni said:
Goto Settings >> Display >> Reading Mode and turn of Good Night's read option
Its clear that based on the Sunrise and Sunset reading mode is enabling
Click to expand...
Click to collapse
Brother with due respect, not everyone is noob.
Those who have phone know what's happening. Everything is turned off in that setting still it gets activated after sunset.
It's a bug and we have to wait for the fix.
---------- Post added at 05:00 PM ---------- Previous post was at 04:58 PM ----------
SunilSuni said:
Try enabling and disabling it. turn off schedule option if it is enabled.
Check whether night light settings are there in developer option or not
Click to expand...
Click to collapse
It's not available, I have wasted some time trying to find what's happening. Trust me, it's a bug.
Shubhayudatta said:
Tried all the enable disable combinations, set as disabled right now, can say it works or not only after the sunset.
And, can't find any related option in the developers setting.
Click to expand...
Click to collapse
Update: All the toggling experiments didn't work. Its again yellowish.
Shubhayudatta said:
Update: All the toggling experiments didn't work. Its again yellowish.
Click to expand...
Click to collapse
As soon as the clock hits 10 pm IST, it became yellowish.
Confirmed bug.
I urge everyone to report this, I have already done that.
@SidDev said:
As soon as the clock hits 10 pm IST, it became yellowish.
Confirmed bug.
I urge everyone to report this, I have already done that.
Click to expand...
Click to collapse
For me it's 6pm. I know 'coz I was waiting for it today.
Shubhayudatta said:
For me it's 6pm. I know 'coz I was waiting for it today.
Click to expand...
Click to collapse
It's 10 pm for me, I hope someone else having phone confirm this too.
Looks like mine got fixed on its own. No more automated yellow tint.
Possibility#1: Xiaomi pushed some OTA
Possibility#2: I forcedly changed the 'good night read' schedule to some random time. 'ON' from 11pm to 1am, and kept the scheduler 'ON'. So, it didn't turn yellow at 6pm (the approx sunset time). Once it's past 6, I turned off everything there. It didn't turn yellow. Rebooted. Didn't turn yellow. Will observe again tomorrow.