This is driving me crazy so if someone is able to assist then I will be massively grateful.
For some reason it seems like the Hall sensor is causing my phone to never enter deep sleep. I have tried playing around with power settings, full factory resets, all to no avail. I'm not sure it's a hardware issue as all sensors appear to function fine in tests.
Any idea how to approach this?
Are you using a smart-cover?
If yes try it without it and disable Smart-cover option in Settings-Smart Assistance-Smart-cover.
If not, also disable the option.
Also enter bootmenu and empty system cache.
Hall sensor explained here https://www.quora.com/What-is-the-use-of-Hall-effect-sensors-in-smartphones
Thank you for the reply. I'm not using any smart cover, only an outer case that covers the back and sides. I also removed the case to see if that was a variable making a difference but the wakelock persists. The setting for smart covers in settings was already set to off.
I cleared the cache like you suggested but that also didn't change anything.
Oh that's a bummer. I'm sorry but further I have no tip's.
Good luck!
Op try turning off all sensor gizmos and then check.
Sent from my EVR-L29 using Tapatalk
What do you mean by 'sensor gizmos?'
4xjamie said:
What do you mean by 'sensor gizmos?'
Click to expand...
Click to collapse
All the stuff under smart assistance.
Sent from my EVR-L29 using Tapatalk
Ah ok I see. Yep everything is turned off.
Related
Guys, im the developer of Power Switch, an app that switches off your tablet's screen when you shut the case.
The main thread can be found here:
http://forum.xda-developers.com/showthread.php?t=1277712
Ive had reports of problems with the tab's light sensor, so would appreciate some debugging feedback.
You can use the lite version to test, it has all the features, but just wont save as much juice.
Thanks in advance. Feel free to reply here or in the main thread, i read both regularly!
Many thanks!, Looks very interesting, will try it out and see how it does with my Tab.
Let me know if the light sensor work properly please!
Got Pro version on my phone, works great.
Will try it on my tab soon.
I'll check it out when i get home.
Works great on my tab too. Thanks mate.
Edit: I noticed on my phone after testing it on and off a few times, the light sensor stopped working. But after rebooting, I havent seen the problem since.
And I've yet to see a problem on my tab.
So the light sensor works? Can you log some sensitivity settings for me so i can fine tune it...
ftgg99 said:
So the light sensor works? Can you log some sensitivity settings for me so i can fine tune it...
Click to expand...
Click to collapse
Like in different lighting settings? Like dimming the lights in the room? Or using different Sensitivity %s and closing the case?
Or all of the above?
Oh and after some extensive use on my DroidX, I've been having some problems. It turns off while I'm using the phone even in very lighted surroundings.
---------- Post added at 09:38 AM ---------- Previous post was at 09:20 AM ----------
I'm at work right now but I tried a few things.
I'm using a Belkin Folio case and i tested to see how low i could set the % for it to read when the case was closed.
Anything under 10% didn't work (even when i completely covered the light sensor with my finger)
On 100%, even a shadow over the sensor would trigger it.
I'll try a few different lighting instances when I get home.
Thats cool, thanks!
ftgg99 said:
Thats cool, thanks!
Click to expand...
Click to collapse
Sure thing, bud.
Still having issues with it on my DroidX. I've been trying different things but I dont think its user error.
You should be using the proximity sensor, not the light sensor for the phone!
ftgg99 said:
You should be using the proximity sensor, not the light sensor for the phone!
Click to expand...
Click to collapse
Oh well okay haha.
Its much more efficient...
Actually...to be honest, I dont even need it on my phone because its a habit of mine to hit the power button as im setting it down or putting it in my pocket.
I do love it on my tab though. Makes it easier just being able to close my case instead of trying to find the power button lol.
Can't remove this app from my tab! Help please
Sent from my GT-P7500 using xda premium
Disable admin permissions or click the uninstall button. Man, som people...
ftgg99 said:
Disable admin permissions or click the uninstall button. Man, som people...
Click to expand...
Click to collapse
Haha I know right...Don't see why he would want to uninstall it tho
The best ones are the Oles that leave market reviews claiming its "some kind of scam"...
Could you help me how to configure it n make it work? Mine seem not work. Duno how. Im using pro
Sent from my GT-P7500 using XDA Premium App
joseph168 said:
Could you help me how to configure it n make it work? Mine seem not work. Duno how. Im using pro
Sent from my GT-P7500 using XDA Premium App
Click to expand...
Click to collapse
Do you have "Enable Power Switch" Checked?
EDIT: If you're using a tablet with a case that covers the screen when you close it, here's what you need...
1. Check "Enable Power Switch"
2. Check "Admin Permissions" (this gives the app permission to lock your screen or turn the tablet off)
3. Check "Enable Sensors"
4. Check "Use Light Sensors" (I recommend 10-20% Sensitivity)
5. Set up your Confirmation and Activation Delay.
---Activation Delay is how long it takes for the device to read if the case is closed or not. (If you set it to 0 seconds, your screen will cut off even if you simply brush something up against the light sensor on accident) I keep mine at 3 seconds.
---Confirmation Delay starts after you Activation Delay ends. It is a confirmation dialogue box that asks what you want to do. Once the timer for it runs out, it will lock your screen/turn the screen off. (I keep mine at 3 seconds for this as well but you might want it longer)
To recap...Set Activation Delay for how long you want the device to wait before it makes a decision if it should turn off your screen or not. Set Confirmation Delay for how long you want it to wait after the Activation Delay ends to actually turn off the screen.
((If you don't have a case that covers the screen and you want it to turn off when you put your tab upside down, replace step 3 with *Check "Acceleration Sensor"* And make sure you Uncheck "Use Light Sensor"))
Is there a workaround or fix to the proximity sensor issue when using CyanogenMod 10.1? It doesn't matter which dialer I use, my screen goes blank and I can't get it back on to use the keypad or hang up.
Thanks in advance.
Mr.Preacher said:
Is there a workaround or fix to the proximity sensor issue when using CyanogenMod 10.1? It doesn't matter which dialer I use, my screen goes blank and I can't get it back on to use the keypad or hang up.
Thanks in advance.
Click to expand...
Click to collapse
See if enabling wake on volume helps:
Settings > Display > Volume rocker wake
Mr.Preacher said:
Is there a workaround or fix to the proximity sensor issue when using CyanogenMod 10.1? It doesn't matter which dialer I use, my screen goes blank and I can't get it back on to use the keypad or hang up.
Thanks in advance.
Click to expand...
Click to collapse
If you are using a screen protector, there is a known issue regarding placement. If the protector cutout is too close to the sensor, it will interfere with the proper operation of the sensor and blank out the screen too easily.
I ran into a similar issue, turns out the tinting on the screen for the sensors had gotten dirty inside and I had to disassemble my phone and clean the sensor Windows. However if you don't like the idea of disassembling your phone, the HTC rezound proximity calibrator app on Google play might be helpful to you. I would try the app first before doing something more extreme.
retrostudd said:
I ran into a similar issue, turns out the tinting on the screen for the sensors had gotten dirty inside and I had to disassemble my phone and clean the sensor Windows. However if you don't like the idea of disassembling your phone, the HTC rezound proximity calibrator app on Google play might be helpful to you. I would try the app first before doing something more extreme.
Click to expand...
Click to collapse
I don't have a screen protector. This solved it for me. Many thanks.
That said, the settings I'm using are a little weird. I have the Low set to 81, and it doesn't seem to matter what the High is set to (currently 100).
This fix works
retrostudd said:
I ran into a similar issue, turns out the tinting on the screen for the sensors had gotten dirty inside and I had to disassemble my phone and clean the sensor Windows. However if you don't like the idea of disassembling your phone, the HTC rezound proximity calibrator app on Google play might be helpful to you. I would try the app first before doing something more extreme.
Click to expand...
Click to collapse
this totally worked to fixed this same issue I have had. I used to have to go outside on a sunny day for my screen to come on while making a phone call. Once I used this app I was able to get it to come on in a dark room with hardly any light. I may at some point open her up and actually clean the inside of the sensor cover, but for now this worked like a charm.
Thanks for the tip.
One item to note, if you do decide to open your phone and clean the sensor windows, don't clean too aggressively or you will remove the tint from the backside of the glass. Just a tip.
I'm glad you guys have gotten your sensors working again.
I just had this problem today. Previously I never had issues with prox sensor, but just a couple days ago I did a complete wipe (data, cache, dalvik, system and internal SD card) and installed RC1 with a fresh install. The app mentioned above DID fix my issue however I know its a ghetto fix. Before running the app, the proximity sensor would work normally in good light, but not in low light. After running the app it works even in dark light which is great. However, I know its a weird fix. I can actually see the red proximity sensor during calls, when I couldn't previously. I'm glad I got it working, but I know there is something wrong still, and it's definitely ROM related as opposed to hardware because just 2 days earlier it worked fine before the clean install. Hmm..
Sent from my Incredible 4G LTE using xda app-developers app
Hi all! I'm having some brightness issues on my Razr i and any help would be great!
I'm on stock 4.1.2 and was using Power Toggles brightness slider to change the brightness, but suddenly, with no changes on the phone, the brigthness level would change only after turning screen off/on. But the problem is not related to the app I think, because even auto brightness isn't working properly... I mean, when it has to get brighter, it works, but when it has to dim, again only if I turn off/on the screen.
Does anyone know what could be causing it?
Thanks in advance!
Sorry for the bad english.
luizlee86 said:
Hi all! I'm having some brightness issues on my Razr i and any help would be great!
I'm on stock 4.1.2 and was using Power Toggles brightness slider to change the brightness, but suddenly, with no changes on the phone, the brigthness level would change only after turning screen off/on. But the problem is not related to the app I think, because even auto brightness isn't working properly... I mean, when it has to get brighter, it works, but when it has to dim, again only if I turn off/on the screen.
Does anyone know what could be causing it?
Thanks in advance!
Sorry for the bad english.
Click to expand...
Click to collapse
Although you don't think the app is causing the brightness problem's I would recommend uninstalling it for troubleshooting purposes and seeing if after you have uninstalled the app and rebooted the phone if after some time the problem persists. This way we can rule out if the app is or isn't causing the problem.
shimp208 said:
Although you don't think the app is causing the brightness problem's I would recommend uninstalling it for troubleshooting purposes and seeing if after you have uninstalled the app and rebooted the phone if after some time the problem persists. This way we can rule out if the app is or isn't causing the problem.
Click to expand...
Click to collapse
Thanks for the reply. I did uninstall it and the problem remains... I installed volume slider (which has a brightness slider too) and the same happens: non "real time" brightness changing and the auto brightness still doesn't work properly... =/
luizlee86 said:
Thanks for the reply. I did uninstall it and the problem remains... I installed volume slider (which has a brightness slider too) and the same happens: non "real time" brightness changing and the auto brightness still doesn't work properly... =/
Click to expand...
Click to collapse
That is odd, I would recommend booting into recovery and performing a factory reset and then see if that fixes your problem.
shimp208 said:
That is odd, I would recommend booting into recovery and performing a factory reset and then see if that fixes your problem.
Click to expand...
Click to collapse
This is what I was afraid of... =/
I will just wait a little longer to see if anybody faced this issue before. I'm pretty sure a factory reset will do (since it started to act like this all of a sudden) but I want to find the cause so it won't happen again or, if it happens, I won't need to do a factory reset...
It's weird... what could make this issue appear? =/
luizlee86 said:
This is what I was afraid of... =/
I will just wait a little longer to see if anybody faced this issue before. I'm pretty sure a factory reset will do (since it started to act like this all of a sudden) but I want to find the cause so it won't happen again or, if it happens, I won't need to do a factory reset...
It's weird... what could make this issue appear? =/
Click to expand...
Click to collapse
One possible way of figuring out what is causing this issue to happen is to generate a logcat when you are adjusting the brightness settings and see if the log reports any background processes that are causing errors with the brightness control.
shimp208 said:
One possible way of figuring out what is causing this issue to happen is to generate a logcat when you are adjusting the brightness settings and see if the log reports any background processes that are causing errors with the brightness control.
Click to expand...
Click to collapse
Thanks for helping me!
I never generated a logcat before. So I installed CatLog from Store and generated a logcat doing the following:
1) Set brightness to auto
2) Put the phone under a lamp
3) Turned of all the lights: the brightness didn't change
4) Turned off and on the screen: when the screen turned on, the brightness was already on a lower level
The logcat is pretty messed... it shouldn't be like that right? =/
Is this helpful?
luizlee86 said:
Thanks for helping me!
I never generated a logcat before. So I installed CatLog from Store and generated a logcat doing the following:
1) Set brightness to auto
2) Put the phone under a lamp
3) Turned of all the lights: the brightness didn't change
4) Turned off and on the screen: when the screen turned on, the brightness was already on a lower level
The logcat is pretty messed... it shouldn't be like that right? =/
Is this helpful?
Click to expand...
Click to collapse
From looking at the logcat there is a lot of errors and warning messages with loading certain library files and Android runtime services that relate to power and screen brightness sensing. Another peculiar thing I noticed was that NFC seemed to be generating a couple error messages as well. Overall you were definitely right about it not being a normal log in this situation, I also like your testing methodology :good:.
shimp208 said:
From looking at the logcat there is a lot of errors and warning messages with loading certain library files and Android runtime services that relate to power and screen brightness sensing. Another peculiar thing I noticed was that NFC seemed to be generating a couple error messages as well. Overall you were definitely right about it not being a normal log in this situation, I also like your testing methodology :good:.
Click to expand...
Click to collapse
NFC is disabled... =/
Well, so any suggestion? Or just a factory reset would do?
luizlee86 said:
NFC is disabled... =/
Well, so any suggestion? Or just a factory reset would do?
Click to expand...
Click to collapse
Unfortunately a factory reset would probably be the best thing to do.
shimp208 said:
Unfortunately a factory reset would probably be the best thing to do.
Click to expand...
Click to collapse
Just wiped data through CWM and the autobrightness still doesn't work properly...when it has to get brighter, it gets, but when it has to dim, it doesn't...
luizlee86 said:
Just wiped data through CWM and the autobrightness still doesn't work properly...when it has to get brighter, it gets, but when it has to dim, it doesn't...
Click to expand...
Click to collapse
You could also try re-flashing the stock ROM to see if that fixes it, another suggestion that could possibly work is running a fix permissions utlity.
Reflashed stock rom and reinstalled all my apps. Everything was fine. Went to bed and woke up, the same problem with power toggles reappeared...
EDIT: found what was causing it! It is the latest version of Floating Notifications (when show on lockscreen is enabled)!
Thanks a lot shimp!
luizlee86 said:
Reflashed stock rom and reinstalled all my apps. Everything was fine. Went to bed and woke up, the same problem with power toggles reappeared...
Click to expand...
Click to collapse
That's wicked bizarre that even after all those things the problem still persists. You could try bringing it in to Verizon to see if they can do anything otherwise a hardware issue may have arisen.
Sent from my SCH-I535 using xda premium
Check this video ... hope developers will fix this ASAP ...
Note : You need an extra camera to see the Proximity light. Remember, you can't see this with open eyes ! Just like Infrared sensor.
greatricky said:
Check this video ... hope developers will fix this ASAP ...
Note : You need an extra camera to see the Proximity light. Remember, you can't see this with open eyes ! Just like Infrared sensor.
Click to expand...
Click to collapse
sorry but you can't see anything, I cannot read any of those blurred text lines.
the best solution for this is either to stop using it temporarily or switch to aosp4.3/cm10.2. all those sensors that samsung added only drain more battery.
broodplank1337 said:
sorry but you can't see anything, I cannot read any of those blurred text lines.
the best solution for this is either to stop using it temporarily or switch to aosp4.3/cm10.2. all those sensors that samsung added only drain more battery.
Click to expand...
Click to collapse
nevermind, just keep your eyes on the proximity sensor . It doesn't disappear after an incoming phone call !
anyway , how to stop that sensor permanently ?? it turned it off from > settings > call > turn off proximity sensor ! but still the light is visible ... it disappears after phone reboot !
ive noticed this as well
That's probably an air gestures thing.
Sent from my SGH-M919 using Tapatalk 2
elesbb said:
That's probably an air gestures thing.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
Hmmm mine is always shutdown i guess....that purple color is new to me (from the vid)
If you display turns off when coming close to the sensor with your hand during a call, the sensor is active, you just can't see.
Some cameras can see the light, some don't. You can check with an it remote control from your TV!
David
have noticed how this is on. i was gonna go through each individual service running by the system and shut it down and see if it turns off. Its gotta be an APK or jar file doing it. Unless the kernel itself is for some weird reason.
elesbb said:
have noticed how this is on. i was gonna go through each individual service running by the system and shut it down and see if it turns off. Its gotta be an APK or jar file doing it. Unless the kernel itself is for some weird reason.
Click to expand...
Click to collapse
I already turned off all sensors and installed several firmwares (omega ,arrow, wanam) and kernels ... but still ... it's so annoying
The proximity sensor requires 0,350mAh power. That's < 1% usage since we have 2600mAh battery I *think*....
greatricky said:
I already turned off all sensors and installed several firmwares (omega ,arrow, wanam) and kernels ... but still ... it's so annoying
Click to expand...
Click to collapse
Do you know if its still there on CM or Google Edition ROMs?
how to turn it off????
nik511 said:
The proximity sensor requires 0,350mAh power. That's < 1% usage since we have 2600mAh battery I *think*....
Click to expand...
Click to collapse
So I guess you mean it takes 0.35mA.
So if you have a runtime of 15 hours, it takes 5.25mAh... really not that much.
David.
davidbaumann said:
So I guess you mean it takes 0.35mA.
So if you have a runtime of 15 hours, it takes 5.25mAh... really not that much.
David.
Click to expand...
Click to collapse
Yeah
omg on all world doesnt exist app which works on rooted phone and can kill proximity and gesture sensor???
The app Elixir say 0,75mah for my Samsung S4, but also 0,75mah for an original battery of 2600mah is few energy, 2600/0,75= 3467 hours.
When the screen is off and I recieve an incoming call, the flash light rapidly and repeatedly switchs on and off. How do I turn this feature off? I can't find it in settings.
Update: it was a Tasker profile doing it.
That is not a standard feature on the Pixel series yet.
You must either have a custom rom, mod or app that is causing the issue.
vandyman said:
That is not a standard feature on the Pixel series yet.
You must either have a custom rom, mod or app that is causing the issue.
Click to expand...
Click to collapse
I don't have a custom ROM or mod and can't find what app might be causing it. I think it's just some hidden setting related to accessibility.
Worse case would doing a factory reset fix it?
mustardseeds said:
I don't have a custom ROM or mod and can't find what app might be causing it. I think it's just some hidden setting related to accessibility.
Worse case would doing a factory reset fix it?
Click to expand...
Click to collapse
I went digging in accessibility settings and all the phone app settings and couldn't find this anywhere. A factory reset would fix it since it isn't a thing by default.
It turned out that it was a Tasker profile being triggered unintentionally. I have one to shake the phone to turn on the flash light if on the lock screen. I have no clue why incoming calls would affect it.
Glad you solve your issue and replied to this.
Your other issue,,, do you have the vibrant set to on?
vandyman said:
Glad you solve your issue and replied to this.
Your other issue,,, do you have the vibrant set to on?
Click to expand...
Click to collapse
Yes there is a vibrate pattern when torch it togled. I wonder if this activate the shake-left/right context?