SAGA LBC Mod 0.5.4 - screen locked during phone calls - HTC Desire S

Hi,
I have been using SAGA LBC MOD v0.5.4 for a few days. Beside a problem with WPA Enterprise WiFi connection (reported in a separate post), I observe another annoying issue. When I am in a phone call (no matter if I called or received one), I am not able to get back from "screen off" until the call is finished. This means that I have no chance to stop an accidental phone call, once the screen is locked. This is really annoying.
Can anyone confirm such a behavior and found a remedy for it?
Thanks,
/Adam

ediap said:
Hi,
I have been using SAGA LBC MOD v0.5.4 for a few days. Beside a problem with WPA Enterprise WiFi connection (reported in a separate post), I observe another annoying issue. When I am in a phone call (no matter if I called or received one), I am not able to get back from "screen off" until the call is finished. This means that I have no chance to stop an accidental phone call, once the screen is locked. This is really annoying.
Can anyone confirm such a behavior and found a remedy for it?
Thanks,
/Adam
Click to expand...
Click to collapse
when in call on this ROM I don't believe that the screen is locked, I believe what happens is that in an attempt to save battery the proximity sensor detects when it thinks you are holding the phone to your head and blacks out the screen, at least that what happens on mine, when I move the phone away from my head the screen lights.
Do you have a screen protector? if you do then it probably covers the sensor, which is to the left of the led at the top of screen, you can try cutting a small hole in the protector
Swyped from HTC Desire S using XDA Premium

Yes, I have screen protector and it seems it covers the proximity sensor. I will give it a try. Thanks!

This is normal behavior in this mod..

What do you mean by "normal behavior in this mod"?
The fact that if you move the phone away from head, the screen is still black (off) and cannot be restored even by clicking the power button? To me, this seems to be a bug, unless it is caused by a screen protector covering the sensor.

ediap said:
What do you mean by "normal behavior in this mod"?
The fact that if you move the phone away from head, the screen is still black (off) and cannot be restored even by clicking the power button? To me, this seems to be a bug, unless it is caused by a screen protector covering the sensor.
Click to expand...
Click to collapse
This is not behaviour and I've been on that mod since it's first version to it's most recent
On my device, without a screen protector it takes a second or so for the screen to light once the phone is removed from head but out always does
Swyped from HTC Desire S using XDA Premium

Related

[Q] Major problems with Sensation screen

Having problems with the touch screen on my sensation and this has now happened on my secound phone! both phones were ok out of box but after a few days first noticed problems from lockscreen as phone would not always unlock when draging app icon into circle then slowly geting worse until would take several swips on screen to even unlock! then started noticing similar problems in norm opperation? sometimes works ok but some times freezes up have tried factory reset and no differance. very strange having this problem on two phones?
Does the touch screen stop working completely?
Mine did that on Monday, had to get a replacement.
it seams to stutter once awake works slightly better? but still not responsive
I've noticed that the proximity sensor and gyroscope are being used aggressively to filter accidental screen presses.
For example, if I place my sensation flat on a table, the lock screen is very hard to unlock. If i place my other hand near the proximity sensor at the same time (or tilt the phone towards me) it unlocks easily. Until I identified this functionality I was beginning to think my right index finger was unsuitable for touch screens (since when placed on a table I tend to use my right hand, but otherwise use my left to unlock).
Hopefully this will be tweaked with future updates.
Sent from my HTC Sensation Z710e using XDA App
Many thanks I hope itd that simple?
I am having the exact same problem, for example on the lock screen I would swipe up but the ring will move slightly, and one icon I.e the camera icon will move towards the ring, another grip which is buggin me is that it will miss screen taps, I.e when texting or clicking an icon one tap will go unnoticed by the device resulting in either a missed letter, or the app not opening. This also goes for the 4 command buttons at the bottom, it happens on these too. I also get the occasional lock up.
Factory reset did not work
All of you are you using Sense, and no other launcher?
i900frenchaddict said:
All of you are you using Sense, and no other launcher?
Click to expand...
Click to collapse
Had the exact same issue on my first phone but i was using adw launcher, not installed it on my second phone and had no issues at all
Sent from my HTC Sensation Z710e using XDA Premium App
I am currently using launcher pro, but even using the htc stock launcher the problem still arises. When I did a factory reset, the problem was still apparent when entering my pin number for the first time.
Kurisu87 said:
I am having the exact same problem, for example on the lock screen I would swipe up but the ring will move slightly, and one icon I.e the camera icon will move towards the ring, another grip which is buggin me is that it will miss screen taps, I.e when texting or clicking an icon one tap will go unnoticed by the device resulting in either a missed letter, or the app not opening. This also goes for the 4 command buttons at the bottom, it happens on these too. I also get the occasional lock up.
Factory reset did not work
Click to expand...
Click to collapse
As I stated before, I experience this problem but it only occurs when the phone is laid flat and my hands are well away from the proximity sensor at the top left of the screen. I can say that the part you are describing with the lock screen is 100% the same problem I come across in certain situations.
Please test to see if the problem is still present when the phone is tilted in your hand and, if you are laying the phone flat when you experience the problem, try putting your other hand near the proximity sensor when you try to unlock.
If this happens as I describe then it is most likely a software bug which only affects users who have particular phone use habits.
Saying that, as you are having quite severe symptoms, during general use, it may be that you have a faulty proximity sensor in your phone - leading to missed screen taps when the phone thinks you are not touching the phone.
Well I laid the phone flat and unlocked it no less than 20 times, each worked flawlessly no problems at all..... Seems to have me baffled
Yes I've been having the same problem. First noticed it when trying to unlock it (phone was lying down), couldn't get the circle to move. Have had one complete touch-freeze. No input possible, however volume and power button worked. Took the battery out, restarted, and it worked fine.
I notice that input can be difficult sometimes, hit and miss or just have to push harder. Strange. Seems like a software issue to me.
edit: just had the same issue - circle wouldn't move. After picking the phone up I was able to unlock it, however still not as easy as it should be, a bit jerky.
Both my evo and my g2 had a grounding issue, for example if I had the phone laying down on the couch or bed, the screen would not respond to touch but if touch the phone with a finger and try to unlock it with my other hand it would work normally. So it seems to be a common problem with some HTC devices
Sent from my LG-P999 using XDA App
aim1126 said:
Both my evo and my g2 had a grounding issue, for example if I had the phone laying down on the couch or bed, the screen would not respond to touch but if touch the phone with a finger and try to unlock it with my other hand it would work normally. So it seems to be a common problem with some HTC devices
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
The wildfire (my friend's got one) has this problem too. You have to keep touching the metallic housing for it to detect any taps.
You are correct, aim1126. I never considered grounding to be the cause but after re-testing it clearly is.
I guess it is a side effect of having a conductive unibody. So basically there will be no software fix, we just have to keep constant contact between our hands and the unibody. I wonder whether a rubber bumper would actually make this problem worse?
Edit:
Actually, the screen seems to adapt to not being grounded properly after a couple of presses. It works fine for me by the third time I touch the screen - weird. Well at least it is only a minor annoyance!
Sent from my HTC Sensation Z710e using XDA App
aim1126 said:
Both my evo and my g2 had a grounding issue, for example if I had the phone laying down on the couch or bed, the screen would not respond to touch but if touch the phone with a finger and try to unlock it with my other hand it would work normally. So it seems to be a common problem with some HTC devices
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
My wife uses a G2 and I wouldnt call it a grounding "issue" honestly seems like more of a feature to make sure you ment to engage the screen.. Its kinda cool IMO
As far as the screen being laggy this sucks since I wanted to upgrade from my Vibrant to the Sensation.. I also am not sure its a software issue you guys are having.. I am running Sense 3.0 with gingerbread on the G2 and it is very smooth.. The option to silence a call or tirning on speaker phone by turning the phone over is neeto torpedo..
I'm having the same issue, from lock screen I drag the circle up and it just stutters. After a few tries it usually works, once unlocked the touch screen appears to work fine. I'd expect the issue would continue after unlock if it was a hardware issue.
mr_wi said:
I'm having the same issue, from lock screen I drag the circle up and it just stutters. After a few tries it usually works, once unlocked the touch screen appears to work fine. I'd expect the issue would continue after unlock if it was a hardware issue.
Click to expand...
Click to collapse
I made a video about the issue here, where you can see that the touchscreen problems do indeed persist after unlocking. Especially when typing and scrolling.
http://www.youtube.com/watch?v=Bk1BlXZQDrU
bcpk said:
I made a video about the issue here, where you can see that the touchscreen problems do indeed persist after unlocking. Especially when typing and scrolling.
http://www.youtube.com/watch?v=Bk1BlXZQDrU
Click to expand...
Click to collapse
That's very bad. Flaky lock screen is not good, and the example of not being able to scroll through apps without it running one is a killer. There are many times when scrolling through a list of selectable items is necessary.
Are you going to exchange the phone?
Have my hopes set on the Sensation, so would really like to find out what the resolution is.
happens in the pocketnow review that brandon just put up
http://www.youtube.com/watch?v=nlSvcOkoEwk&hd=1&feature=player_detailpage#t=143s

[Q] Dresire S - Proximity Sensor Problem

Got a brand new DS couple of days back and....right from opening the box..the first call..proximity sensor is playing up. Most times i have to pull out the battery to end the call.
Tried the following with no result
1) Installed DHD Proximity re-calibrator
2) Factory reset
3) Installed Vitrous Unity 1.27
4) Back to factory rom, blew hard between ear piece and sensors
5) Removed screen protector and tested
I have S- Off and really dont want to go through the pain of visiting HTC. Would greatly appreciate some help here ...as always !
did you press the back button in between the call?
this has happened to me on stock rom only if i press the back button during the call
i haven't tried it on LBC rom yet
sujitht said:
Got a brand new DS couple of days back and....right from opening the box..the first call..proximity sensor is playing up. Most times i have to pull out the battery to end the call.
Tried the following with no result
1) Installed DHD Proximity re-calibrator
2) Factory reset
3) Installed Vitrous Unity 1.27
4) Back to factory rom, blew hard between ear piece and sensors
5) Removed screen protector and tested
I have S- Off and really dont want to go through the pain of visiting HTC. Would greatly appreciate some help here ...as always !
Click to expand...
Click to collapse
I noticed that only half the proximity sensor is visible, the other half is covered by what appears like black plastic part. Is this how it is supposed to be?
My proximity sensor is completely visible.
No..i haven't pressed the back button.
mikeyd85 said:
My proximity sensor is completely visible.
Click to expand...
Click to collapse
Is it the left sensor of the two sensors?
I have exactly the same problem. The issue seems to be that Desire S proximity sensor active distance is 9cm, when on my older Desire ir is only 1cm.
When working with some Proximity sensor tools, I have discovered, that you need to put your phone like 25cm (have no idea, how many inches) away from any obstacle in 30degree radius. If that is followed, I haven't been able to recreate a battery pull ocasion of sensor failure. However in real life talking, it is impossible to guarantee.
That there must be some sensor configuration possibilities, so that we could decrease sensibility to minimum distance. Such change should solve this sensor bug, as it would be normal operation distance.
Maybe some dev knows, how to play with proximity sensor?
Yeah, I have had this problem a long time with this phone didn't happen that much at first then it became more and more apparent.
Found the problem and solution, it lies with the screen protector, yes it might be transparent but the sensor detects it. Using a sensor testing app from the market it suggested the sensor was covered almost all the time.
So the solution was replace the protector with new one but cut an arc at the top just big enough around the sensor at the top left, easy fix now in call screen is more responsive.
Sent from my HTC Desire S using XDA Premium App
Totaly plausable question,but where is the sensor?
bleach1 said:
Totaly plausable question,but where is the sensor?
Click to expand...
Click to collapse
Top left of the screen in opposite place to led, if you tily screen under light you should see the sensor reflect back at you
Sent from my HTC Desire S using XDA Premium App
Thanks will adapt my screen protector
Sent from my HTC Desire S using XDA Premium App
Proximity sensor
I've been having the same issue. I gave my DS to the HTC workshop and they said it was faulty hardware. They will be replacing the system board since the sensor is soldered to it (under waranty).
Before sending it in, I tried a few roms and hacks but it was never resolved. I recommend you visit your local HTC warranty center.
I have the same problem with the proximity. I installed an app called Anyunlock which seems to have solved the problem. It seems to be able to wake it when the screen turns off after a call. The app allows you to unlock with the volume key and replaces the lock screen with its own. I hope this keeps working

Screen Off Issue while on phone

I am having a weird problem. I am on stock ATT with root. If i am talking to someone using my phone....if i put it on speaker and screen goes off...I cannot make the screen on back again. If i click power button the phone gets disconnected. its really irritating bug.
Also if i am using GPS while driving and If i get a call....after attending the call and I am not able to go back to navigation app. it shows me black screen.
These two things are annoying me like hell. Any help is appreciated...
maybe set display to never sleep? esp. while driving? will drain the battery faster, but in the car presumably you would have a charger available...
Are you using a screen protector or case thats covering the proximity sensor? Its one of the little spots in the upper left corner. Where most protectors have a cut out. Anyways, thats there to shut the screen off on the phone when you are on it so you dont accidentally hit any buttons. If its covered it wont allow you to turn the display on because it thinks its next to your face. Either that or maybe your sensor is bad.

Bad Proximity Sensor?

Is anyone else having an issues when on a call to someone you take it away from your ear and look at your phone and the screen doesn't come back on. I have to hit the power button to make the screen wake up. I'm all stock (4.4.2) with unlocked bootloader. I m trying to see if this is a hardware problem where I need to RMA or software problem.
Mine works perfectly well. Are you sure you don't have anything that might be affecting the proximity sensor, like smudges or a screen protector?
Sent from my Nexus 5 using Tapatalk
No, I don't have any screen protector not any smudges. I saw similar issues on other phones and someone said to clear data and cache on the phone app so I don't know if that will work or not.
ProBird79 said:
Is anyone else having an issues when on a call to someone you take it away from your ear and look at your phone and the screen doesn't come back on. I have to hit the power button to make the screen wake up. I'm all stock (4.4.2) with unlocked bootloader. I m trying to see if this is a hardware problem where I need to RMA or software problem.
Click to expand...
Click to collapse
What time out do you have your screen set to? Sounds like it's simply locking after the designated time.
I've noticed the screen turning on and off occasionally when talking. Almost like the sensor isn't sure if I'm holding it to my head or not but then I do hold it away from my face.
I have the same issue...
I can't hang a call because the screen simply don't turn on when I remove my phone from the ear.
In add at this issue, seems like the proximity sensor turn off the backlight screen only.
When I finish a call, I found the clock screen opened, in my case the settings screen of advanced clock widget...
It's really annoying...
Sent from my Nexus 5 using XDA Premium 4 mobile app
Do you guys have a screen protector applied by any chance? Everyone had this issue with the nexus 4 because the sensor is really sensitive and picks the protector up, not letting it turn the screen on. Try removing a section of the protector where the sensor sits, this will fix your issue.
Surprisingly, I don't have this problem
Team Nexus 5 sucks. Underpowered battery for a 5inch 1080p screen that is non-removable. Weak generic antenna that drops signal. Worst speaker of any device on the market. Cheap plastic build.
dalton8 said:
Do you guys have a screen protector applied by any chance? Everyone had this issue with the nexus 4 because the sensor is really sensitive and picks the protector up, not letting it turn the screen on. Try removing a section of the protector where the sensor sits, this will fix your issue.
Click to expand...
Click to collapse
My phone is naked... No screen protector, no cover...
Sent from my Nexus 5 using XDA Premium 4 mobile app
bblzd said:
What time out do you have your screen set to? Sounds like it's simply locking after the designated time.
I've noticed the screen turning on and off occasionally when talking. Almost like the sensor isn't sure if I'm holding it to my head or not but then I do hold it away from my face.
Click to expand...
Click to collapse
I have it on 15 seconds. Shouldn't that feature be bypassed when a call is in progress so that the proximity sensor is usable. This is the first phone that I've had that has done this to me. On all others the proximity sensor stays live even after the predetermined sleep time.
After 15 seconds you're screen is simply turning off as you have set. Mine does so after 1 minute, which is my screen time out setting.
Sent from my Nexus 5 using Tapatalk
I have 30 minutes of inactivity...
The proximity sensor is broken...
Sent from my Nexus 5 using XDA Premium 4 mobile app
bblzd said:
After 15 seconds you're screen is simply turning off as you have set. Mine does so after 1 minute, which is my screen time out setting.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
During a call shouldn't the screen timeout be bypassed then go back to the default setting once the call has ended? That makes much more sense to me.
ProBird79 said:
During a call shouldn't the screen timeout be bypassed then go back to the default setting once the call has ended? That makes much more sense to me.
Click to expand...
Click to collapse
This seems to be the built in functionality of the phone and not a bug. I can't really say if one way is better then the other but I just turn the screen off during calls now.
This is the bug...
really annoying
same problem
ProBird79 said:
Is anyone else having an issues when on a call to someone you take it away from your ear and look at your phone and the screen doesn't come back on. I have to hit the power button to make the screen wake up. I'm all stock (4.4.2) with unlocked bootloader. I m trying to see if this is a hardware problem where I need to RMA or software problem.
Click to expand...
Click to collapse
Same problem here do any one have solution for this..

Anyone else having this problem?

When I try to pull down the notification bar on the right the screen goes black. Also turns off the always on display. I'm assuming it's something with the Proximity sensor. Tired of all the little bugs and problems with this phone. I’m returning it. Just curious if anybody else is having this problem.
https://youtu.be/moTuJP06JCw
alnova1 said:
When I try to pull down the notification bar on the right the screen goes black. Also turns off the always on display. I'm assuming it's something with the Proximity sensor.
Click to expand...
Click to collapse
No, mine isn't doing that. You might have a dud.
alnova1 said:
When I try to pull down the notification bar on the right the screen goes black. Also turns off the always on display. I'm assuming it's something with the Proximity sensor. Tired of all the little bugs and problems with this phone. I’m returning it. Just curious if anybody else is having this problem.
https://youtu.be/moTuJP06JCw
Click to expand...
Click to collapse
I've had that happen on my Pixel 2 XL. Only once or twice and restart fixed it every time.
It's definitely the prox sensor. Always On Display shuts off when the phone is in your pocket or face down, which is detected by the proximity sensor, so that's totally normal. As far as it happening on the home screen, it seems like the phone thinks you're in a call, which would use the proximity sensor to turn the screen off near your head. I would reboot as @jimv1983 suggested and see if that works.
Are you using a screen protector? Sometimes those can cause issues with the proximity sensor, but usually it just causes the screen to shut off and not come back on during a call as it senses the protector at all times instead of your face.
fury683 said:
It's definitely the prox sensor. Always On Display shuts off when the phone is in your pocket or face down, which is detected by the proximity sensor, so that's totally normal. As far as it happening on the home screen, it seems like the phone thinks you're in a call, which would use the proximity sensor to turn the screen off near your head. I would reboot as @jimv1983 suggested and see if that works.
Are you using a screen protector? Sometimes those can cause issues with the proximity sensor, but usually it just causes the screen to shut off and not come back on during a call as it senses the protector at all times instead of your face.
Click to expand...
Click to collapse
I had a case with a built-in screen protector on it and I thought that might be what was causing it but after taking it off it still did it. Weird thing though once I put it on the wireless charger it stop doing it. Hasn’t done it all day even with case on. Weird. Still thinking about taking it back to Best Buy and swapping it out.
I've had a similar issue where the proximity sensor will not deactivate as long as a call is going (can't hangup, can't unlock, can't speaker phone, can't mute, etc.). I have to wait for the other person to hang up. Get an automated robo-call you accidentally answered....oh well, guess you have to listen to them. I have never been so angry at a phone as I am with this one. Especially as expensive as it is. I absolutely would NOT have bought this phone if I knew ahead of time how aggravating this would be! Thinking of sending it back. BUYERS BEWARE!
tonic1080 said:
I've had a similar issue where the proximity sensor will not deactivate as long as a call is going (can't hangup, can't unlock, can't speaker phone, can't mute, etc.). I have to wait for the other person to hang up. Get an automated robo-call you accidentally answered....oh well, guess you have to listen to them. I have never been so angry at a phone as I am with this one. Especially as expensive as it is. I absolutely would NOT have bought this phone if I knew ahead of time how aggravating this would be! Thinking of sending it back. BUYERS BEWARE!
Click to expand...
Click to collapse
Had this very issue with my pixel XL and blowing on the top speaker grille of dust with compressed air solved it.
But if this is out of the box that sucks. It should not be like that. My pixel was approaching two years when that happened.

Categories

Resources