Hey. Thanks for reading!
I got an s4 recently and have not had any problems with it till now. I had to call a company today, and I thought the problem I had would not reappear. I'm posting here so...
On two calls lately I'v needed to input numbers during the call to give information. When I try to enter the numbers the screen turns off until I move it a little, then it turns on... until it detects my finger about to touch it, then it turns off again. The call continues through all of this. I could barely input the ten or so digit number I needed to provide. This only occurs during calls. Even when dialing my Voicemail I have a struggle to put in the 4 digit pin because the screen acts like a grinch, turning off when I try to press numbers. I turned off all the s4's "eye-monitoring" features and it still does this. Any ideas?
Thanks!
open your dialer
press the menu button
select call settings
uncheck "Autoscreen off during calls"
voila
seagypsy59 said:
open your dialer
press the menu button
select call settings
uncheck "Autoscreen off during calls"
voila
Click to expand...
Click to collapse
This will work.. but then it'll produce another problem when your cheek starts to press buttons.. ending in a txt msg to your mom whereas the msg was created with speech to text... while you were talking to your g/f.
Found the option. I may just have to turn it on and off as needed.
Now to find the on screen keyboard sensitivity! Thanks!
I have s similar issue where my screen turns off when I start a call and doesn't come back on wheni pull they phone away from my face. It only comes back on wheni puts power button or home button, but then the screen doesn't turn back off when I put it close to my face again. Turning off auto off feature does what is supposed to but then what's the point of the auto off anyway. Still searching for answers for the last 2 weeks.
There should really be a way of adjusting the sensitivity of this. My wife's S4 just recently started doing this, and my guess is that it's picking up the palm of her hand as her cheek and preventing her from being able to actually press any buttons on the numpad while on a call.
nightspeed98 said:
I have s similar issue where my screen turns off when I start a call and doesn't come back on wheni pull they phone away from my face. It only comes back on wheni puts power button or home button, but then the screen doesn't turn back off when I put it close to my face again. Turning off auto off feature does what is supposed to but then what's the point of the auto off anyway. Still searching for answers for the last 2 weeks.
Click to expand...
Click to collapse
This is exactly what is happening to my two week old gs4. I make a call put it up to my face and the screen turns off correctly. Then when I pull it away from my cheek it stays off. The only way to turn it back on it to hit the power button or home button. It's like the sensitivity of the proximity sensor is off.
I just disabled the thing. Really sucks for my conference calls that I mute and unmute and also use have to key into the calls.
Sent from my SCH-I545 using xda app-developers app
.
does anyone have an actual solution for this? i've tried like 5 different custom roms trying to fix it without any luck it's so bad now that i can't even hang up anymore.
nlm842 said:
does anyone have an actual solution for this? i've tried like 5 different custom roms trying to fix it without any luck it's so bad now that i can't even hang up anymore.
Click to expand...
Click to collapse
You guys try using a can of air to blow into the ear piece? Dust gets in there and screws with the proximity sensor. People have fixed it that way. Also if you have a case on try making a call with the case off and see if that happens. Sometimes Even though you wouldn't think it...its too close to the sensor and messes it up. Had that happen to me
Sent from my SCH-I545 using XDA Premium 4 mobile app
Mistertac said:
You guys try using a can of air to blow into the ear piece? Dust gets in there and screws with the proximity sensor. People have fixed it that way. Also if you have a case on try making a call with the case off and see if that happens. Sometimes Even though you wouldn't think it...its too close to the sensor and messes it up. Had that happen to me
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'll try it later today and get back to you on how it worked
Let us know if that works. I've been having this problem as well. However, I feel like it started happening after the last update to VRUEMK2. After that is when I noticed it, although that may just be a coincidence.
Basically no matter if I call someone or answer a call, the second I put it to my face and the screen shuts off(or if I hit the power button) it stays that way forever until the other person hangs up on their end. The screen won't turn back on until they hang up.
Sent from my SCH-I545 using xda app-developers app
My girls sprint s4 was the one doing this and like I said the compressed air thing worked. Poor design if dust can get into the ear piece and mess with a sensor that's not even right next to it. Oh well. Let me know how you guys make out
Sent from my SCH-I545 using XDA Premium 4 mobile app
compressed air works
Just tried the compressed air. It works. I agree that this is stupid.
Huge thank you to whoever mentioned compressed air in this thread. This was driving me nuts at work trying to manage through phone trees or switch calls without being able to get the screen back on. Compressed air was the fix.
THANKS!!!!!
Method 1.
As it happens due to dust so blow Air from ear speaker that will clear the dust from your sensor and solve your prob hopefully.
Method 2 (Root Needed).
go to samsung code *#0*#. then SENSORS and Read your Proximity sensor values.
Calibration is not needed if
your phone doesnt vibrate in normal but does so when u physically put your finger on the Sensor.
Calibration needed if
your phone is vibrating in this menu no matter what, you put your finger on the sensor or not
Follow these steps
1. download Android Terminal from store
2. type these commands to calibrate automatically
$ su
# echo 0 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal
# echo 1 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal
Reboot and see if it works.go to *#0*# and check if it continuously vibrating or only does so when you put your finger on the SENSOR.
I still continuously vibrating even after putting the upper comments use this manual maethod which always works
you need to manually put values in ur /efs/prox_cal.it Reads Hexadecimal value. so you have to convert your decimal values into HEX (which can be done by any online decimal to Hexadecimal converter).
FIND YOUR Decimal Values and pushing them into /efs/prox_cal
Method : finding two values for calibration . offset + normal value.
FINDING OFFSET
cat /sys/devices/virtual/sensors/proximity_sensor/prox_cal
note down the values it returns.. mine is 5,64,100.. you only need the 1st value which is 5.
FINDING NORMAL STATE
cat /sys/devices/virtual/sensors/proximity_sensor/state
note down the value if returns. mine is 64
now ADD OFFSET value + Normal Value
5 + 64 = 69
Convert in Hexadecimal which is 45.
Pushing the value in /efs/prox_cal
# echo -en $'\x45' > /efs/prox_cal (if not working try giving "space" after $ i.e. $ '\x45)
then
# chown system:system /efs/prox_cal
# chmod 644 /efs/prox_cal
# sync
# Reboot
All done. after that go to *#0*# then SENSORS and move your finger on the sensor, yout phone will Vibrate only when you put your finger on the sensors.
Source: click here
Related
I am a new android owner. When I make a phone call the proximity sensor turns the screen off... great, no accidental screen pressing. However, when I finish the phone call or take the phone away from my ear... I get the lock screen. Why? Why doesn't the screen just go back on to whatever screen was on before the phone call... like the dial pad.
I find this annoying. To hang up a phone call, I have to unlock the screen first.
What phone are you using? Software version etc and are you rooted? This doesn't happen to me so it's not a general android issue.
Sent from my Galaxy Nexus
I have the Moto Droid X. Running CyanogenMod 7.1. Also using exDialer as a dialer replacement.
Does it happen with the stock dialer? If not that's your answer
Sent from my Galaxy Nexus
RTContent said:
Does it happen with the stock dialer? If not that's your answer
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Yep it happened with the stock dialer on ICS and it is happening with JB as well. I am really surprised it doesn't bother more people. What is most annoying is that, I initiated a new call and put my phone to my ear to only that the call did not even establish (e.g., due to network iss ue) and when I want to place the call again, it is already locked. It is definitely due to the proximity sensor, as the same thing doesn't happen if i never put the phone to my ear and just keep watching the screen to confirm that the call did get established (and started ringing).
njmsmith said:
I am a new android owner. When I make a phone call the proximity sensor turns the screen off... great, no accidental screen pressing. However, when I finish the phone call or take the phone away from my ear... I get the lock screen. Why? Why doesn't the screen just go back on to whatever screen was on before the phone call... like the dial pad.
I find this annoying. To hang up a phone call, I have to unlock the screen first.
Click to expand...
Click to collapse
If you are rooted, disable your Proximity Sensor in a call. To do so, add following line to /system/build.prop file:
Code:
gsm.proximity.enable=false
.
Plus, make sure to make screen timeout period long. You can use Widgetsoid app (or, other toggle apps) to make it infinite.
SachinShekhar said:
If you are rooted, disable your Proximity Sensor in a call. To do so, add following line to /system/build.prop file:
Code:
gsm.proximity.enable=false
.
Plus, make sure to make screen timeout period long. You can use Widgetsoid app (or, other toggle apps) to make it infinite.
Click to expand...
Click to collapse
I have display timeout set to 2 minutes, so that can't be the problem, as the whole experience when the call is not connected only takes 10 or 15 seconds to complete. However I have security setting to lock the screen in 5 seconds after the display goes to sleep. Perhaps that is somehow related, so I just increased it to 30 seconds, I will see if the problem goes away.
I have the VZW gs3, running the stock rom with the motion lift to ear to call enabled. I've noticed that during a call, when you go to input numbers, such as if you are on automated call center, if you try and press the 1 key the screen goes black as soon as your finger gets too close to it. Then comes back when you are a little further away. Not sure about 2 and 3, but the lower keys did not have the same problem.
I thought maybe the phone is attempting to shut the screen off, thinking I'm holding the phone to my face maybe? Either way really annoying problem, has anyone else noticed the same thing? Is there a workaround or fix?
sleepingkraken said:
I have the VZW gs3, running the stock rom with the motion lift to ear to call enabled. I've noticed that during a call, when you go to input numbers, such as if you are on automated call center, if you try and press the 1 key the screen goes black as soon as your finger gets too close to it. Then comes back when you are a little further away. Not sure about 2 and 3, but the lower keys did not have the same problem.
I thought maybe the phone is attempting to shut the screen off, thinking I'm holding the phone to my face maybe? Either way really annoying problem, has anyone else noticed the same thing? Is there a workaround or fix?
Click to expand...
Click to collapse
It's because when you're moving your finger to the 1 your hand gets in front of the proximity sensor, which turns off the screen. Just be aware of where the rest of your hand is and it won't happen anymore.
Yes, it's the proximity sensor so watch your other fingers and you go to press a key. I must say this is one of the most annoying things of the SIII I have found so far.
Alright, thanks, is the proximity sensor the two small dots next to the samsung logo?
One of them, yes.
AvengerBB said:
One of them, yes.
Click to expand...
Click to collapse
Does that mean I can just bring my finger up to the sensor to make a call when texting? so that I don't have to press my face into the phone?
Hello everybody.
I have a rooted 4.0.4 XXLFB Galaxy S3 and have noticed a problem.
Whenever I'm on a call using my blueooth headset, the screen turns on once every 30 seconds, give or take.
It's a problem because if I have the phone in my pocket, sometimes I mute the call, other times I turn off the headset...
Does anybody know how to solve this?
Thanks in advance.
Posting to add a "me too" to the list. Trying a ton of different things, almost to the point of clean device.
Hit the button and the screen turns off, about 2-5 seconds later, screen turns back on. Does not matter what I do. Seems to do it with speakerphone option too. If neither Bluetooth nor speakerphone are used, and you put the phone to your ear, backlight stays off. Otherwise, it automatically turns back on by itself. Tried with wifi on/off, speaker with bt on/off, different headsets, etc. My Wife's does not have this issue, so I gotta look into what is different. There has gotta be a setting or app installed that is doing this. I've even tried apps such as screebl and others. Some even had a thing to say lock it off till press button, and it still comes back on after 2-5 seconds. I've muted and hung up on many people when the phone was in my pocket because of this issue.
I've not used a BT headset but i'm thinking that maybe because the phone isn't against your head the screen comes on. possibly to give you information about the caller.
I'm not saying you should put the phone to your head even though your using bluetooth either.
thanks, but, don't help, tried that too. Had entire top half of phone covered during most tests. Screen does not turn off unless I press button, then comes back on automatically after 2-5 seconds. I did find one app today that seemed to work, but not sure if it works too well "Smart Screen Off".
Sounds silly but have you tried locking the handset?
That's what I meant by pressing the button. Button on right side that if I am not on a call, turns off screen and locks it.
Ok - narrowed it down a ton. If I leave the in-call status screen up, the screen turns back on after being turned off via power button. If I hit home or have any other screen active, it remains off. So dialer related, but I can deal with an extra button press.
visegrip72 said:
Ok - narrowed it down a ton. If I leave the in-call status screen up, the screen turns back on after being turned off via power button. If I hit home or have any other screen active, it remains off. So dialer related, but I can deal with an extra button press.
Click to expand...
Click to collapse
agree with the above. if you leave call status up while connected via BT headset, screen remains active (comes in and out). if you exit active call status (ie press home) then the screen timeout works. if you are talking on the phone without headset, no problem.
so yes, that's the prob. any solid fix yet?
please and thanks....
visegrip72 said:
Ok - narrowed it down a ton. If I leave the in-call status screen up, the screen turns back on after being turned off via power button. If I hit home or have any other screen active, it remains off. So dialer related, but I can deal with an extra button press.
Click to expand...
Click to collapse
Thanks a lot, visegrip. It was really frustating having to redial every other call because i hang up without noticing.
Any solution to this problem? Hitting a home button and locking the phone is not an option when I keep my phone in a leather holster on my belt. That's a main reason for having bluetooth as hands free.
Problem solved by using Tasker. If anyone need APK patch file to fix a problem, let me know and I'll post it here
Almazick said:
Problem solved by using Tasker. If anyone need APK patch file to fix a problem, let me know and I'll post it here
Click to expand...
Click to collapse
Almazick,
It would be great if you can send me the fix!
ital1981 said:
Almazick,
It would be great if you can send me the fix!
Click to expand...
Click to collapse
Here is the fix for a screen that I created. Let me know if it works or not for you.
http://www.mediafire.com/download.php?1ikj7d4wnjs9hx5
Almazick said:
Problem solved by using Tasker. If anyone need APK patch file to fix a problem, let me know and I'll post it here
Click to expand...
Click to collapse
You know, I use tasker and have been trying to figure this out for a while. I've also been trying Secure settings and Locale Using multiple settings and plug-ins. I have not been able to create anything yet that seems completely reliable.
Not trying to be rude or anything, but I am and always have been a little leary of installing APK files unless I know the source. However, if you would be so kind to post the contexts and tasks so that I may enter them myself manually, it would be greatly appreciated. Thank you in advance.
Inane65 said:
You know, I use tasker and have been trying to figure this out for a while. I've also been trying Secure settings and Locale Using multiple settings and plug-ins. I have not been able to create anything yet that seems completely reliable.
Not trying to be rude or anything, but I am and always have been a little leary of installing APK files unless I know the source. However, if you would be so kind to post the contexts and tasks so that I may enter them myself manually, it would be greatly appreciated. Thank you in advance.
Click to expand...
Click to collapse
Well, It's pretty easy.
Profile -> Phone Offhook
Task:
Wait 20 seconds
App-> Go Home
Display -> System Lock
In case if you'll have any problems just use my apk file which is exactly the same.
Good news! I just took the Jelly Bean update from sprint & this problem is FIXED!
I tried calling and turned off the screen and it stayed off!
I also called and didn't touch the screen and after the timeout, it turned itself off!
Hmmmmm... OK. Thank you. I'll have to try that and see how it works. I was looking, hoping and working on trying to get something that would keep the screen off. Dialing, talking and ending the call. I've got something that seems to work for the most part, (I still get quick flashes, which is fine) but still have some more work to do on it.
Sent from my ADR6425LVW using xda premium
visegrip72 said:
Good news! I just took the Jelly Bean update from sprint & this problem is FIXED!
I tried calling and turned off the screen and it stayed off!
I also called and didn't touch the screen and after the timeout, it turned itself off!
Click to expand...
Click to collapse
It's not fixed. I'm getting crazy about this master bug.
I'm trying to tackle my problem from another angle. So, does anyone know how to disable the touch screen on a Galaxy S2?
I'm trying to have the screen off while an app runs (and thinks the screen is on). I can turn the screen off by this command:
echo 1 > /sys/devices/platform/samsung-pd.2/s3cfb.0/graphics/fb0/blank
Screen will be off, but it still responds to touch. I figure there's probably a similar command to disable the touchscreen. I found a thread that describes how to do it for the nook; however it won't work on this phone (obviously because the hardware's different).
I've seen apps that may disable the touchscreen...however I won't have access to the notification bar while in the app I want to run (frustrating). I plan on creating a script that'll sleep for 2-3 minutes, giving me enough time to get to the app and set it up just the way I want, then the screen will go out. To get the screen back on, I'll either wait until I can ssh in and undo what I did (in the example above, just substitute echo 0 instead of echo 1) or do a hard reboot.
Edit: This may be OS dependent...I'm running ICS 4.0.3 at the moment.
Use below:
# To Disable touchscreen
service call window 18 i32 0
# To Enable touchscreen
service call window 18 i32 1
I use this in my Gesture script thanks to Tungstwenty.
Sent from my GT-I9100 using Tapatalk 2
acekay said:
# To Disable touchscreen
service call window 18 i32 0
# To Enable touchscreen
service call window 18 i32 1
Click to expand...
Click to collapse
Looks like it'll be good enough for my purposes.
I've now realized it might be ever so slightly helpful if I could disable the home and power buttons as well (but not all the buttons, might need volume). I think if I keep it in a pocket or make a little space for it where it won't get disturbed too much, it'll be ok.
Just a note, this doesn't completely turn off the touchscreen. The phone still reacts to touching the screen (specifically, the menu and back buttons light up). And touching the menu or back button will also cause them to light up and make the phone vibrate, though the button is ignored otherwise (i.e. you're in the app, press the back button...it lights up and vibrates the phone, but it does NOT exit the app).
I'll test it in a couple weeks (once the headset and amplifier come in), but I think it'll fit the bill.
Thanks!
Hi,
It did not work in my case (android 6).
Any other way ?
Ranchu
Every time I make a call, the screen dims and then blacks out in a matter of seconds. It's in an Otterbox Defender. I have tried every setting I could find and have it set to turn off display after 10 minutes but something is overriding that for this phone app.
I'm new to LG and the V30 but on my last device it detected proximity to the screen during calls so your cheek doesn't mistakenly hang up or something. I believe it uses the front side camera to detect your head there. Could that be what os going on?
Sent from my LG-H933 using Tapatalk
Mine does the same and I dont think it's to do with proximity sensor. When i make a call on speakerphone or Bluetooth with nothing near the phone, it still dims and blacks out
I agree it's likely not the proximity sensor in this case as I always have it on a desk and use it via bluetooth but thank you for that suggestion. But, in many cases, I need to enter in several series of #'s for conference lines and changing options but the screen blanks out way too fast. When I double tap it to open the screen, I sometimes accidentally hit a # and have to start over again...
diskwzrd said:
I agree it's likely not the proximity sensor in this case as I always have it on a desk and use it via bluetooth but thank you for that suggestion. But, in many cases, I need to enter in several series of #'s for conference lines and changing options but the screen blanks out way too fast. When I double tap it to open the screen, I sometimes accidentally hit a # and have to start over again...
Click to expand...
Click to collapse
Do you mean it turns pure black, or just dims? Mine dims if I'm on a call utilizing the speaker. Just touch the screen to brighten it up, then type your conference numbers.
Sent from my LG-H931 using XDA Labs
Mr CATFISH said:
Do you mean it turns pure black, or just dims? Mine dims if I'm on a call utilizing the speaker. Just touch the screen to brighten it up, then type your conference numbers.
Click to expand...
Click to collapse
I have the exact same problem with my V30. I use Bluetooth, either on a headset or in my car. After a few seconds, the screen dims, and then a few seconds later, it blacks out completely. When it dims, I can tap on it to wake it up, but the screen still responds to the tap, so if I happen to tap where the hangup button is (easy to do in a moving car), I end up hanging up on myself. Or, if I'm navigating through an automated attendant, when I tap the screen to wake it up, it invariably hits a button for a choice I didn't want, and I have to back out or start over. Very frustrating! If the screen goes completely black, then I just hit the power button to turn it back on, but once again, it'll dim out in a few seconds. I would LOVE to have a fix for this! I like this phone better than the past Samsung phones I've had, but the Samsungs don't do this.
I want to add my frustration to this issue as well. I also have a V30 and this happens all the time. My mom has a G6 and says the same as well. It is simply unacceptable. If this is an LG-specific issue and it isn't fixed (or at least given an option to change the screen time-out) then this is a deal-breaker for another LG in the future. (same goes for the glass back as well, but that's another issue...)
Eagerly awaiting a fix or workaround....
captainentropy said:
I want to add my frustration to this issue as well. I also have a V30 and this happens all the time. My mom has a G6 and says the same as well. It is simply unacceptable. If this is an LG-specific issue and it isn't fixed (or at least given an option to change the screen time-out) then this is a deal-breaker for another LG in the future. (same goes for the glass back as well, but that's another issue...)
Eagerly awaiting a fix or workaround....
Click to expand...
Click to collapse
I have the same problem on my V30+ since the oreo update. Before it was OK.
During call screen blacks out and then when I take my ear off screen it does not light up again.
I need to press the power button to have the screen displayed again during call. I wonder it this was not done on purpose in order to preserve battery
Nowever It's frustrating because I was not used to this.
Any ideas?
Thanks Anndy
Same frustration for me. I make regular use of speakerphone and it is very irritating.
Sent from my LG-H933 using Tapatalk
Anndy said:
I have the same problem on my V30+ since the oreo update. Before it was OK.
During call screen blacks out and then when I take my ear off screen it does not light up again.
I need to press the power button to have the screen displayed again during call. I wonder it this was not done on purpose in order to preserve battery
Nowever It's frustrating because I was not used to this.
Any ideas?
Thanks Anndy
Click to expand...
Click to collapse
No fixes yet that I'm aware of. The "solution" I use is to tap or double-tap on the very top of the screen where there are no buttons that will affect the call. But this is by no means an acceptable solution.
captainentropy said:
I want to add my frustration to this issue as well. I also have a V30 and this happens all the time. My mom has a G6 and says the same as well. It is simply unacceptable. If this is an LG-specific issue and it isn't fixed (or at least given an option to change the screen time-out) then this is a deal-breaker for another LG in the future. (same goes for the glass back as well, but that's another issue...)
Eagerly awaiting a fix or workaround....
Click to expand...
Click to collapse
I, too, want to add my frustration with this problem. In my case, the screen goes black immediately after touching the phone icon to connect a call. I talked to the T-Mobile people who said they never heard of this before. This has been an issue since 2012, so that was useless. This started happening with the last update. Hopefully if more people complain, a fix will happen.
Same here...
captainentropy said:
No fixes yet that I'm aware of. The "solution" I use is to tap or double-tap on the very top of the screen where there are no buttons that will affect the call. But this is by no means an acceptable solution.
Click to expand...
Click to collapse
I hope we can get a fix or an option to this soon. It really messes up calls when options are needed during the call.
I've had the exact same problem with my G6 ever since I purchased it (February 2018). It's really annoying and a problem when you are calling an automated voice system and it dims before you can make your selection and double tapping to wake can cause you to hit a wrong number selection (which happened the other day when I was refilling a prescription). Please fix this!
Happens on the V20 also with the latest update from Verizon. The only way around it is to tap in an area you think won't affect the call every few seconds. The number bar on the top seems to work. defintely need a fix for this. Really annoying
Mad Medik said:
I'm new to LG and the V30 but on my last device it detected proximity to the screen during calls so your cheek doesn't mistakenly hang up or something. I believe it uses the front side camera to detect your head there. Could that be what os going on?
Click to expand...
Click to collapse
Me too! The solution? NONE, NONE, and NONE.
I called T-Mobile today about this very problem after my frustration hit the roof. I complained it's impossible to hold business conference calls on my phone because the dialpad screen dims in exactly 5 seconds. I need it fully lit so I can mute/unmute at-will for clear-sounding and respectful meetings. Yet, as every smartphone user knows, computer screens are no match against sunlight. I inevitably fumble my way around the dialpad on a bright day.
I did every configuration possible to mitigate the problem: Screen Timeout (none), Auto Brightness (off), Brightness (100%), Battery Saver (off). Nothing stopped the dialpad from dimming like usual. However, to my own surprise, all other apps respected my settings during a call. So is the LG phone/dialpad app itself ignoring my system settings? Yes. Yes it is. My theory was soon confirmed....
T-Mobile offered to do a 3-way call with an LG representative. The conclusion? I was told flat out it's a "feature of all LG phones", it's the "default", and there is "no way to change it". SERIOUSLY, LG?!?!? Shame on you, LG!!!! I didn't say that to the LG rep, but, I did tell her I will be "forced stay away from future LG phones" if there really was no solution for this and every other phone LG makes. She offered her scripted apology to me several times but, alas, there was nothing she could do.
PS: This is so, so, so disappointing. They could have kept their default but provided a system option to enable the app's FLAG_KEEP_SCREEN_ON. They could have taken my customer compliant seriously. So, for anyone reading this, if you want to do any active use of the dialpad during a call, stay away from LG phones.
pbenedictxda said:
Me too! The solution? NONE, NONE, and NONE.
I called T-Mobile today about this very problem after my frustration hit the roof. I complained it's impossible to hold business conference calls on my phone because the dialpad screen dims in exactly 5 seconds. I need it fully lit so I can mute/unmute at-will for clear-sounding and respectful meetings. Yet, as every smartphone user knows, computer screens are no match against sunlight. I inevitably fumble my way around the dialpad on a bright day.
I did every configuration possible to mitigate the problem: Screen Timeout (none), Auto Brightness (off), Brightness (100%), Battery Saver (off). Nothing stopped the dialpad from dimming like usual. However, to my own surprise, all other apps respected my settings during a call. So is the LG phone/dialpad app itself ignoring my system settings? Yes. Yes it is. My theory was soon confirmed....
T-Mobile offered to do a 3-way call with an LG representative. The conclusion? I was told flat out it's a "feature of all LG phones", it's the "default", and there is "no way to change it". SERIOUSLY, LG?!?!? Shame on you, LG!!!! I didn't say that to the LG rep, but, I did tell her I will be "forced stay away from future LG phones" if there really was no solution for this and every other phone LG makes. She offered her scripted apology to me several times but, alas, there was nothing she could do.
PS: This is so, so, so disappointing. They could have kept their default but provided a system option to enable the app's FLAG_KEEP_SCREEN_ON. They could have taken my customer compliant seriously. So, for anyone reading this, if you want to do any active use of the dialpad during a call, stay away from LG phones.
Click to expand...
Click to collapse
Root, use Google dialer? Does it dim also? I have it installed, I'll check tomorrow morning.
Google dialer "Phone" app doesn't help...nope!
I gave a workaround in an identical thread somewhere else in this forum. Use Waze navigation app during phone calls. The screen won't dim. Drag the phone call thingy over to the Waze screen.
Found it:
ChazzMatt said:
When I have Waze navigation on, my screen doesn't dim. When I make a phone call, I go back to Waze map screen. I can drag the phone call thingy wherever I want. If I need to mute, unmute I just click that to go back to call dialer interface for a few seconds. Then I go back to Waze screen to keep display on.
Yes, it's a wonky workaround, but it works. When I use this while driving, I make sure my phone is plugged in for charging -- because the display will stay on for the entire duration of the phone call.
Click to expand...
Click to collapse
My LG G8X does the same thing, goes dim after a few seconds, then blacks out completely. In the day & age of "press 1 for this, press 2 for that" it really should allow for more time before the phone becomes disfunctionable...
New auto update on LG phone times out too fast
My LG phone auto updated to a 3 sec. screen blackout and can't be changed in any settings menu. The solution is to install the "Keep Screen On Free" app which completely solved the problem and lets you change the time out settings too.