App Idea: light sensor decides to turn the screen on or not for incoming call/sms - XPERIA X1 General

An idea i just had:
Its unpractical to accidently accept calls or do stuff on the touchscreen after a SMS while the phone is in the pocket.
But its nice to see who is calling or reading the SMS with out having to turn the screen on before.
So why not use the light sensor, pockets are usually dark. So the software would run in background on an incoming SMS or CALL event it would first check the light sensor, if its dark, dont turn on the screen just start the ringtone sounds. If the environment is bright, just display the caller or SMS right away.
Additional features would be:
- beeing able define the values when to turn on or not
- optional auto screen turn on if it gets brighter (taking the phone out of the pocket), this should only work if there is still someone calling, or a SMS was received in the last 20 (or so) seconds
- program should only read the light sensor on an incoming event to save energy
- optional it could read the light sensor all the time and auto turn on the display everytime it comes out of the pocket, some people might want that
Only problem is, has anyone been able to access the X1 light sensor before? There are programs for the lightsensors of other HTC devices, but the X1 sensors seems diffrent.
A more simple version of this program could simply check the light values every 5 min (or self difineable interval) and set the registry settings for wakeuponcall or wakeuponsms.

Related

Proximity sensor - doesn't seem to be working

I there any settings or something to adjust proximity sensor? I was trying to turn off screen covering sensor with thumb, but.. no effect.
Does it need any setting or my phone is faulty?
I noticed the same thing on my phone today.
The proximity sensor doesn't work if you've switched off the Automatically adjust backlight option in Settings>Sound & Display>Backlight. There doesn't seem to be any way around this as the proximity sensor doesn't have its own option.
Are you in a call? You need to be calling/receiving a call for it to work.
I agree, I think you need to be in a call for the proximity sensor to work properly.
For me it works fine. And i don´t hade automatic backlight on.
aldabal said:
For me it works fine. And i don´t hade automatic backlight on.
Click to expand...
Click to collapse
That's interesting because I can toggle my proximity sensor (whilst in a call) by toggling the automatic backlight. That option must be linked to something else as well.
Screen goes black
I do have the same behavior, when I make a call the phone's screen goes black automatically so if I need to press any key have to press send to get my screen back, then use the keypad, nonsense, is anyone having the same issue ?
for me, the proximity sensor doesn't work at all. I have the automatic backlight setting and yet it still doesn't work. any idea why?
SP300
I just found the solution, I have got the screen protector on "The Original HTC SP300" and is causing the screen to go blank when you do a phone call, If a remove it a little bit from the top left corner and make a call works as spec.

Proximity problem

Hello,
I have bought myself a diamond touch 2, and i directly flashed it to Dutty's R6 rom because i like it much better and i made up my mind about it even before i bought it.
Now i seem to have a problem, and i don't know what would be the problem; either the device or the rom?
Proximity doesn't work; setting automatic backlight dimms the screen to a low-light level. Holding a flashlight above it doesn't make any difference.
Also, when making a call, the display keeps being illuminated the whole time, no matter if i hold it to my ear or not.
Does someone recognize this problem?
Cheerz
Exca said:
Hello,
I have bought myself a diamond touch 2, and i directly flashed it to Dutty's R6 rom because i like it much better and i made up my mind about it even before i bought it.
Now i seem to have a problem, and i don't know what would be the problem; either the device or the rom?
Proximity doesn't work; setting automatic backlight dimms the screen to a low-light level. Holding a flashlight above it doesn't make any difference.
Also, when making a call, the display keeps being illuminated the whole time, no matter if i hold it to my ear or not.
Does someone recognize this problem?
Cheerz
Click to expand...
Click to collapse
Settings\System\Power\Backlight\ Turn off Auto adjust.
If i turn off auto adjust i can indeed set full brightness, but that's not the point. I want the auto-dimming and proximity sensor to work, so when i hold the piece next to my ear it locks and turns off the screen...
If I turn on auto-adjust, it doesn't respond on any lightchange or action; it just dimms the screen to about 40% and keeps it there.. either a bug or a hardware fault with my unit?
Not sure that it ever worked perfect out of the box.
Have you tried tweaking the settings with TD2 Tools?
How do you mean tools? As far as i know i can only find one box to turn auto adjust on.. you have the same configuration, does it work for you?
EDIT: I installed the app "LumosWizard". Now the phone's backlight adjusts depending on the light the sensor receives. The sensor works well as the values go up when putting a flashlight on it.
However, i wonder why this doesn't work with just auto-adjust on, that's what the HTC Auto-Backlight should do right? Also, with this app, the backlight doesn't go out when no light is reveived (auto-lock when putting into pants, or turned off backlight when calling...) ?
This is what i'm looking for: http://www.youtube.com/watch?v=6xakUmz1zwc
=> i don't think this is achieved by an additional application, but is just standard HTC service doing this because of putting on the auto-adjust...
There is NO proximity sensor on Touch DIAMOND II. Only light sensor. Use Touch_InCall_Screen_Tweak instead. This program use G-sensor and block the screen when your phone is in vertical position.
m72m72 said:
There is NO proximity sensor on Touch DIAMOND II. Only light sensor. Use Touch_InCall_Screen_Tweak instead. This program use G-sensor and block the screen when your phone is in vertical position.
Click to expand...
Click to collapse
Thanks, installed and works good!
Still wondering though why i need a 3rd app like LumosWizard to make the lightsensor work, as htc's autoadjust apparently doesn't
I did find this .cab called Glight and it works great on my TD2
More about it here:
http://www.ageye.de/index.php?s=glight/about

Idea to avoid hitting power button every time you put phone away

I use a one minute screen timeout, which is a bit long for the screen to stay on every time you put it back in your pocket. It also gets a little annoying hitting the power button every time after I'm done using it, for example if I'm frequently taking it out and putting it away during a text conversation. So, I used Tasker to tell it to lock the screen every time the proximity sensor fires, combined with WidgetLocker set to its own 10 sec screen timeout. I also told it to NOT do this while on a phone call so the proximity sensor would just turn the screen off but not lock it like normal in that case. So this way, you can keep a longer normal screen timeout, put the phone back in your pocket, and the proximity sensor will fire, lock the screen, and the screen will turn off in 10 seconds. The only issue here is the occasional accidental proximity sensor activation, but it's not too frequent. I'd be curious if anyone else finds this useful.
The Tasker profile:
Context: Proximity Sensor
Task:
1. If %WIN !~ Phone (if not in the phone app)
2. WidgetLocker Cmd Activate (lock screen)
Detecting if the Phone app is open does require enabling the Tasker accessibility service in Settings -> Accessibility -> Accessibility services (check Tasker).
I would shoot someone in the face every time i went to pull down the notification bar and the screen locked :/
mrono said:
I would shoot someone in the face every time i went to pull down the notification bar and the screen locked :/
Click to expand...
Click to collapse
You shouldn't have this issue really unless you frequently overshoot the top of the screen when going for the notification bar.
mrono said:
I would shoot someone in the face every time i went to pull down the notification bar and the screen locked :/
Click to expand...
Click to collapse
God i wish XDA had a "like" button
mrono said:
I would shoot someone in the face every time i went to pull down the notification bar and the screen locked :/
Click to expand...
Click to collapse
Yep, I had a profile like this set up before, but abandoned in very quickly due to this issue. Every time I went near the sensor my screen shut off, no bueno.
Hey... This thing makes phone calls too!
JTNiggle said:
Yep, I had a profile like this set up before, but abandoned in very quickly due to this issue. Every time I went near the sensor my screen shut off, no bueno.
Hey... This thing makes phone calls too!
Click to expand...
Click to collapse
Make a timeout so the proximity sensor has to be activated for at least 3 seconds
initial said:
Make a timeout so the proximity sensor has to be activated for at least 3 seconds
Click to expand...
Click to collapse
Good idea, works pretty nice, Thanks! Seems that 7 seconds is the minimum timeout allowed though, not that that's a problem, running it now. Unless there's is another way to do it that
I must recommend this setup for everyone now.
Context: Proximity Sensor
Task: Display Timeout = 7 Seconds
Handy for work/school too, I just lay my phone face down on my desk and the display takes care of itself.
JTNiggle said:
Good idea, works pretty nice, Thanks! Seems that 7 seconds is the minimum timeout allowed though, not that that's a problem, running it now. Unless there's is another way to do it that
I must recommend this setup for everyone now.
Context: Proximity Sensor
Task: Display Timeout = 7 Seconds
Handy for work/school too, I just lay my phone face down on my desk and the display takes care of itself.
Click to expand...
Click to collapse
Actually, wouldn't that profile change the display timeout to 7 seconds, effective immediately when the proximity sensor activates? So you could accidentally activate it, not be aware, and then have the display suddenly go off on you 7 seconds later. I think what initial was saying was to make it so the proximity sensor itself must be active for at least 3 seconds before anything happens, THEN do what you wish - in my case, I don't actually change the display timeout at all, I just lock the screen with WidgetLocker, at which point a 10 second timeout is in effect from that app.
xdp said:
Actually, wouldn't that profile change the display timeout to 7 seconds, effective immediately when the proximity sensor activates? So you could accidentally activate it, not be aware, and then have the display suddenly go off on you 7 seconds later. I think what initial was saying was to make it so the proximity sensor itself must be active for at least 3 seconds before anything happens, THEN do what you wish - in my case, I don't actually change the display timeout at all, I just lock the screen with WidgetLocker, at which point a 10 second timeout is in effect from that app.
Click to expand...
Click to collapse
That's true. The display timeout does change to 7 seconds. How would you set it so that the proximity sensor must be activated for a certain amount of time?
initial said:
Make a timeout so the proximity sensor has to be activated for at least 3 seconds
Click to expand...
Click to collapse
How do you do this in Tasker?
WillJitsu said:
How do you do this in Tasker?
Click to expand...
Click to collapse
I haven't been able to figure it out, anyone?
WillJitsu said:
That's true. The display timeout does change to 7 seconds. How would you set it so that the proximity sensor must be activated for a certain amount of time?
Click to expand...
Click to collapse
It does just change the display timeout, but only while the proximity sensor is covered. So if you uncover it before 7 seconds, the display stays on like normal, works well for now until I learn some more about Tasker.
Hey guys, I think I figured out how to do this. It requires using variables. Basically, you set a "proximity sensor active" variable that you create to true when it's activated (the context enter task), and set it to false when it's deactivated (the context exit task). Then in the enter task, after setting that variable, you wait 3 seconds, and then test if the variable is still true. If it is that means the exit task has not executed which means the sensor is still active and your task can proceed. If it isn't that means the exit task did execute which means you uncovered the sensor before the 3 second wait time elapsed and so you don't want to proceed. It looks like this:
Context: Proximity Sensor
Enter Task:
1. Variable Set, Name %PROXACTIVE to 1
2. Wait 3 seconds
3. If %PROXACTIVE ~ 1
4. If %WIN !~ Phone
5. If %WIN !~ Voicemail
6. WidgetLocker Cmd Activate
Exit Task:
1. Variable Set, Name %PROXACTIVE to 0
This works fine for me using WidgetLocker, since I only need the task to continue executing after the 3 second wait time, but if you are trying to actually change the display timeout, you'll still have the issue of the value reverting once you uncover the sensor. To get around this, create a separate task that changes the value (Tasks button at the bottom, then New Task), and call this task from the enter task (Tasker -> Perform Task). This puts the action behind a sort of wall that makes your main task oblivious to the fact that it's setting a revertible value, and the value will stick even after you uncover the sensor. Of course, this also means your display timeout will now remain at 7 seconds, so you'll have to create another task to restore that value on screen unlock or something like that.
Let me know if you have any questions, this seems to work okay for me!

proximity issue on stock rom gs4?

Recently, my phone has been having a problem with the proximity sensor during calls. When I finish a call, or want to look at my screen, the screen does not turn on by itself so I need to press the home button for the screen to light up. This is very annoying! I even turned off the option "Turn screen off during calls" (which is supposed to leave my screen lit up all the time) and the screen still goes black.
is it a software issue or hardware?
additional info : it works when i use my fone in a room {proximity ADC 43(43,43,43) } or building, but doesn't work while using outside {proximity ADC 51(51,51,51) }.

Samsung S10+ Proximity Sensor issue

I would like to tell you that it often happens when I pull the S10+ out of my pocket, so the display is not in "stand by" mode, it is not always on display, but it is slightly backlit. Classically, the display is black and shines only AOD. But when I pull it out of my pocket, instead of the classic AOD it shines for hours and even seconds and after them you can see the wallpaper of the locked display and it is slightly backlit. The display itself is dark, but it is slightly backlit and you can see the wallpaper. With the classic AOD, the display is completely black and I have set only hours, minutes, date and battery, and of course, the notification, if any. Does anyone know what it is, whether it can be turned off so that the display does not illuminate the pocket?
I have accidental touch protection on.
As far as I know proximity sensor is only accessible when you are in call, that's why other apps can't access it.
Samsung should remedy this. Because I always change the Always On setting in my pocket. Specifically - Rotation and Brightness Always On.
EDIT: It happens most when I tap wake-up.

Categories

Resources