Hello,
I'm trying to get some information about Android sensor interactions with the GN2 and power-save.
The issue I'm having is when the screen is off, applications that use the phone motion sensors seem to malfunction, so it would seem the sensors act differently when the screen shuts off or is turned off. Can someone point me in the right direction for a developer's guide that is specific to the GN2 or any information at all on sensor interaction with the GN2?
Thanks!
Related
Hi,
as measured by Z-DeviceTest, the proximity sensor on my Desire is stuck at 0.000 cm in all lighting conditions (including a very bright torch right on top of it).
At first I suspected this was the known problem with dust settling on the sensor, but I've blown and sucked (teh-eh) with everything I have, from every angle, and the sensor is still stuck at that value.
The problem shows up both in CM7 and with the stock firmware.
I have to assume the sensor is broken.
I'm looking for ways to disable the proximity sensor, and in particular to stop it from locking the screen during calls. Naturally, since the sensor is stuck at 0.0000 cm, any time a call is initiated the screen locks up, preventing me from ending the call, dialing tones and so on.
Alternatively, I'd be happy with a way to override the screen lock via hardware buttons. The power\unlock button doesn't work
Inserting a headset during a call does unlock the screen, but naturally this is not a satisfying solution (for example, I can't use this method to make calls while driving, using the speaker).
Solutions tried with no positive effect:
- editing build.prop with "ro.proximity.delay=0"
- using trackball\volume button wake
- using screebl, screen off to control automatic screen locks
Thank you for your time.
Anyone have any pointers?
Is it really hopeless?
Are you root? If so have you considered flashing a rom with the option to disable the proximity sensor? (for example miui-au has that option)
Yes, I have a rooted device. I didn't know miui had that options, I'll check it out; thank you!
I have a pedometer program installed on my phone but it only works when the screen is on. The developer says that sensor on Samsung phones does not detect steps properly when the screen is off. Does anybody know if there is a Mod that would fix this so that the program would detect steps even with the screen off? Thanks.
Wondering if someone (hopefully more than one) can check something to see if this is an issue with my particular phone or something related to the software/hardware. It seems that when a call is placed or received, the proximity sensor goes to "far" and won't reset until it is uncovered and then re-covered. I have searched through the Verizon HTC One forums and have not found anything related to this issue.
If the proximity sensor is covered, and I make a call (via bluetooth headset (double click for last dialed)) or receive a call, the proximity sensor goes to the uncovered state. It then stays in that state until I uncover and then re-cover it. How I checked this was using Elixir 2 and checking the sensor data. I also set up variables in Tasker and Automagic.
So, this was my test procedure:
I start the sensor data in Elixir 2 for the proximity sensor. I cover the sensor with my finger (it now shows "near"). I use my bluetooth headset to place a call. The screen comes on with the current call. I back out of the current screen (the phone screen) and get back to Elixir 2 sensor data. The sensor now shows "far". From that point on, until I uncover the proximity sensor and then cover it, it shows far. I set up variables in Tasker and Automagic that show the same results.
I am running the stock debloated ROM. Rooted and S-Off.
Dont know about the bluetooth thing because i dont have one, but i do have issues sometimes with the proximity sensor when on calls. For example i will dial a number and put the phone to my ear talk awhile and then need to switch to speaker or look at something on the phone while still talking. But when i take the phone away from my ear, the screen stays off, and i have to swipe my finger over the sensor to get it to come back on.
I don't seem to have an issue with that. What seems to happen is that, IF the proximity sensor is covered, and you place a call or answer a call with your headset, when the device "wakes up" to the call screen the proximity sensor defaults to uncovered ( "far" ). Then the sensor does not start responding again until it is actually uncovered.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Anyone?
Hmmm... So, this is the latest for my issue. I went from stock ROM to ViperOne 5.8.0. I am still getting the same results. So, I think I have eliminated the software side of it. Would that be right? So, it could be the firmware or the hardware? I'm still wondering if it's my phone only or if it is an issue with the HTC One in general. Is there anyone that can check this? Or give me another route to take?
I'm on ViperOne 5.8.0
Android 4.4.2
Senses 5.5
Any other info you might need, please just ask.
I use the Gravity Screen app to turn my phone's screen on and off automatically. It works almost perfectly, but I have run into a problem: It seems that the Xperia Arc S disables the proximity sensor automatically when the phone is in deep sleep. This only happens if not connected to a charger though, if I connect the phone, it works perfectly.
My question is: Is it possible to force the phone to keep the proximity sensor on in deep sleep when the phone is running on battery? The app offers several work-arounds, like keeping the cpu awake (not very battery-friendly obviously), or combining the proximity check with a gravity sensor check for the phones position before turning the screen on, but the better solution would be to just enable the sensor.
I have tried creating an empty profile in tasker with the task "stop" and the state set to proximity, then enabled display-off monitoring in Tasker, but sadly this only seems to conflict with Gravity Screen's ability to read the sensor.
This whole thing could possibly also help make pocket mode work more reliably on our phones. I noobishly suspect that this change would have to be made on kernel level?
I just upgraded from an S8 to a 21 FE, I had this setup where my screen will turn off using the proximity sensor, so when I open my case cover or lift it up from the table it just turns on automatically.
Upgrading, I notice the apps I used (Gravity Screen, Smart Screen On Off) are not working as they used to. In most tests, I did seem to suggest the proximity sensor only responds when the front lens is covered by my thumb instead of just hovering over with my hand like before. I did the *#77692# test and the Proximity sensor is working fine then WHEN I enable it so I'm at a lost here, is this a technical issue, is this by design
EnigmaXtreme said:
I just upgraded from an S8 to a 21 FE, I had this setup where my screen will turn off using the proximity sensor, so when I open my case cover or lift it up from the table it just turns on automatically.
Upgrading, I notice the apps I used (Gravity Screen, Smart Screen On Off) are not working as they used to. In most tests, I did seem to suggest the proximity sensor only responds when the front lens is covered by my thumb instead of just hovering over with my hand like before. I did the *#77692# test and the Proximity sensor is working fine then WHEN I enable it so I'm at a lost here, is this a technical issue, is this by design
Click to expand...
Click to collapse
Didn't you find the gesture to double tap the screen to wake up?
ze7zez said:
Didn't you find the gesture to double tap the screen to wake up?
Click to expand...
Click to collapse
I did, but I'm used to waving my phone awake with both my hand and by opening my phone case, but it seems the more recent Galaxy phones don't allow the same use of the proximity sensor
EnigmaXtreme said:
I did, but I'm used to waving my phone awake with both my hand and by opening my phone case, but it seems the more recent Galaxy phones don't allow the same use of the proximity sensor
Click to expand...
Click to collapse
A touch sensor while the screen is locked can consume less power than a proximity sensor placed in a camera, for example.