Develop Bugs

[Q] Proper proximity sensor values

So here is my problem: Some time ago i was using the "in pocket detection" and it was working perfectly fine, then i disabled it, then yesterday i enabled it and it wouldn't work :/
Since i thought it has something to do with the proximity sensor i downloaded some app that checks sensor output data and it reports value either 3.0 when i move something towards the sensor or 100.0 when i move away. I was wondering if that's the normal behavior. (not increasing linearly but rather acting more like a switch 1-0 behavior)
Also, i have no problems with screen blacking out during calls (it turns off and back on as expected), proximity lock works fine with an external app, but not with the "In Pocket Detection" in settings/display.
Any clues on what could be causing the problem and any suggestions how to fix it?
It is by no means critical but I just want to figure out what's wrong.

I think it's the correct behavior. The proximity sensor works more like a switch. I belive the In Pocket Detection also uses the camera and/or the accelerometer for the "detection" ...

Thanks for your reply.
Well, in the end i just flashed CM7 on it so i don't have the in pocket detection anymore

[Q] Strange airplane mode/gps issue

So noticed something odd.
turning airplane mode on and off doesn't change the gps mode switch (which is fine imho, gps is a sensor like the inclinometer or magnetic compass)
BUT, it interferes with apps ability to access the gps data
ie. airplane mode is on, gps switch is on, run an app that uses gps data and it never sees it even though the status bar will say 'searching for gps' but never sees or locks any satellites.
if you turn off airplane mode it works just fine, if you reenable airplane mode it will continue to work.
tried using lgs online chat and got nothing but idiots, first one insisted the gpad didn't have gps that it used wifi and cellular signals to simulate location finally got him to send me to someone else and this guy insisted that airplane mode should disable all communication and that gps was communication then after trying to explain the difference between active transceiver systems and passive sensor systems he abruptly disconnected the chat without saying anything...
suffice to say not too pleased with lg support right now
anyhoo, anyone elses pad doing this?

[Q] Force-enabling the proximity sensor while the phone is asleep

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?

Screen blanks when I grip the tablet

I just bought a refurbished Tab S and it looks like it hasn't even been used. It came with Android 5 and I didn't notice the problem, although I only used it for a few minutes before doing the OTA update to Android 6.0.1. Although everything seems to be working, if I grip the tablet between the lower right corner and the usb charging port, the screen blanks. Then when I remove my grip from this location the screen comes back on! I know ... weird behavior, right? It only happens in this area and it doesn't happen if I just press on the back or on the screen in this area. I have to actually grip on both sides. It's a beautiful tablet and I would hate to have to return it, so I'm trying to figure out if there is a way to fix it. (In everyday use it is just to annoying to aviod touching this area.) I read a post by vndnguyen (14-Jul-2015) on this forum that said:
---------------------------------
Our Galaxy Tab S has a Grip Sensor. You can check it by:
1) Use *#0*# to open Hardware Test, select GripSensor. You will see the grip sensor is located at the upper-right corner.
2) Use *#1106#. You can set the Grip sensor on/off.
-----------------------------------
So maybe I could fix the problem by turning the Grip sensor off. However I couldn't figure out how to enter these secret codes since a wifi only tablet doesn't have a dialer. I found an application called "Secret Codes" with an icon that looks like a lighted match. It listed a code with a #0 for hardware test. I pushed that button and it said it was invoking the code but then I saw no response from that.

Would selecting "Factory Data Reset" from the Backup and reset settings menu be worth a try to fix this problem? (Would I have to do the Marshmallow update again?).
By the way, here are some additional things I did to see if I could make the problem go away (to no avail):
- Starting the tablet in Safe mode
- Turning off automatic brightness, screen rotation, smart stay, screen timeout, Adaptive display, and screen tone auto adjust
- Turning off lock screen
- Turning off Palm swipe to capture
Any advice would be highly appreciated.
~Paul

Another sensor bug(minor one)

I am having a small issue since I bought this Pixel. Since Nexus 4 I am using double tap to wake by using apps, root or original hardware. So pixel 3 xl came with this feature out of the box and happily using it.
But sometimes it was not working and I was saying "nah it ok, it happens from time to time probably deep sleep issue" and using power button .
Then I also started using screen "always on" feature and realize even always on is active double tap not working, until I cover proximity sensor on and off, and voila! double tap works.
It seems like proximity sensor is latching itself off but does not turns off "always on" Also similiarly "always on" is off as if proximity sensor is shutting it off but when I check I see some whatsapp messege notifications.
It is a weird bug and even after clean flash of android 11 did not solve it(although it broke android auto wireless )
Does anyone else have it ? it is a general bug or hardware issue ?