Related
Hi,
Just recently got the mini. I often accidentally end the calls due to the position of the four corner launcher during call. Is there a way to disable it and use vanilla gingerbread call screen (i.e. the one in Samsung?). Or is there any setting to have "long press" for ending call instead of just click?
Not without root.
That's odd. The proximity sensor should be dealing with this. I mean it does for me and that never happend to me. Check if your sensor is working properly. Dial *#*#7378423#*#* and look in Service tests menu for proximity switch.
donev_go said:
That's odd. The proximity sensor should be dealing with this. I mean it does for me and that never happend to me. Check if your sensor is working properly. Dial *#*#7378423#*#* and look in Service tests menu for proximity switch.
Click to expand...
Click to collapse
He wanted to change the UI
Thanks all. The proximity sensor is working fine. But it is the way I'm holding the phone (coz it's so small! my thumb sometime reach the button when I move the phone away from my face (to use dialpad, or turn on speakerphone, or....). It's annoying.
Now I'm trying some call replacement apps (Ultimate Call Screen HD Free). It's working but it does not look as "refined" as sony one. Wonder if I can replace with "stock" gingerbread dialer....
I didn't root my phone yet. It came with .62 firmware and I'm still don't have time to downgrade and root. I guess if ICS comes out, it will probably change the call interface as well.
Flash cyanogenmod for stock gingerbread call screen
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.
Within the last week my phone stopped working all the time when it's sitting on your desk with the screen off and you move your hand over it to get the Quick Glance preview. It doesn't work more often than it does. Rebooting sometimes helps getting it working again but not for very long.
When making phone calls the screen does turn off when I hold it up to my ear but once the call is over and I remove it from my ear, it doesn't turn back on anymore. This always happens since the problem started.
Also, I decided to open up the samsung gallery app (I rarely use it since I like QuickPic better) to see if the gesture of swiping your hand above the pictures would still advance to the next one and it does.
Any idea what might be causing this to happen?
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.
The simple user experience of unlocking the device on is so bad on Pixel 6. There's just no winning option.
Smart Lock randomly kicks in, so I can't be sure that a single tap of the screen will turn on the phone.
The fingerprint sensor sucks, and requires a tap on the screen just to bring it up. And sometimes I don't even get the option to use my fingerprint.
I don't even like the single-tap gesture to begin with. It means I'm accidentally turning my screen on all the time just when carrying the phone. It almost started a call with my deadbeat father, who I haven't talked to in 20 years
I could go with no screen lock but then I'm locked out of several key features (like viewing my account passwords). Also, pressing the Power button at all on a phone this big is cumbersome, since I then have to reposition my entire hand to go from pressing it to then interacting with the screen.
I'm already rooted because I absolutely needed the Back button to be on the right side. Now I'm hoping modders can fix the unlocking experience because it's the next big issue in my mind.
The fingerprint scanner is actually very good if you set it up right, and will always be displayed with always on display... No tap required. Problem solved
turbosrrgood said:
The fingerprint scanner is actually very good if you set it up right, and will always be displayed with always on display... No tap required. Problem solved
Click to expand...
Click to collapse
Or lift to check turned on rather than AOD.
turbosrrgood said:
...and will always be displayed with always on display... No tap required. Problem solved
Click to expand...
Click to collapse
This is not my experience at all. Sometimes I get a fingerprint sensor icon. Other times my phone is unlocked via Smart Lock and I get an Unlock icon in place of the fingerprint sensor. Other times I get a Lock icon indicating Smart Lock is expired. Other times I get no icon there at all.
If the fingerprint sensor is there and I'm on the dimmed screen, sometimes it'll just light up and deny, and other times it won't even acknowledge that I've put my finger on the sensor.
If the Unlock icon is there, it requires a tap to unlock (no holding!). So that means I have to actually look at the screen and discern which icon is there to know whether I need to tap or hold.
And Lift to Check Phone would be even more problematic for me, since I'm trying to avoid accidental screen interactions and this would only cause more.
On all my other Pixel phones I just touch the back fingerprint sensor and the phone is on. I don't have to think about a dozen different possible states the phone could be in every time I want to turn it on.
Have you tried to recalibrate it via the Pixel tool thing Google has?
Google Pixel - Update and Software Repair
gavingt said:
The simple user experience of unlocking the device on is so bad on Pixel 6. There's just no winning option.
Smart Lock randomly kicks in, so I can't be sure that a single tap of the screen will turn on the phone.
The fingerprint sensor sucks, and requires a tap on the screen just to bring it up. And sometimes I don't even get the option to use my fingerprint.
I don't even like the single-tap gesture to begin with. It means I'm accidentally turning my screen on all the time just when carrying the phone. It almost started a call with my deadbeat father, who I haven't talked to in 20 years
I could go with no screen lock but then I'm locked out of several key features (like viewing my account passwords). Also, pressing the Power button at all on a phone this big is cumbersome, since I then have to reposition my entire hand to go from pressing it to then interacting with the screen.
I'm already rooted because I absolutely needed the Back button to be on the right side. Now I'm hoping modders can fix the unlocking experience because it's the next big issue in my mind.
Click to expand...
Click to collapse
It sounds like smartlock working as intended (which I find useless, and poor security). It will give you an unlock icon instead of the fingerprint. Maybe you simply don't want smart unlock, which is more useful for password only. This seems like more of a matter of figuring out what features you want to use.
If you changed the Animation Scale in Developer Settings then the AOD fingerprint icon can disappear.
turbosrrgood said:
It sounds like smartlock working as intended (which I find useless, and poor security). It will give you an unlock icon instead of the fingerprint. Maybe you simply don't want smart unlock, which is more useful for password only. This seems like more of a matter of figuring out what features you want to use.
Click to expand...
Click to collapse
I never used to use Smart Lock, but on this phone it means I don't have to deal with the inconsistent fingerprint sensor as often.
gavingt said:
I never used to use Smart Lock, but on this phone it means I don't have to deal with the inconsistent fingerprint sensor as often.
Click to expand...
Click to collapse
Try setting up the fingerprint scanner again, slightly moving your finger with ever press during set up to get every angle and view of the print. It's been pretty much perfect for me. I suppose Google could have helped instruct people to do that better in the process.
turbosrrgood said:
It sounds like smartlock working as intended (which I find useless, and poor security). It will give you an unlock icon instead of the fingerprint. Maybe you simply don't want smart unlock, which is more useful for password only. This seems like more of a matter of figuring out what features you want to use.
Click to expand...
Click to collapse
I just restarted my phone, and then repeatedly unlocked and locked it (sometimes by fingerprint, sometimes by tapping). By the end of the video, the fingerprint sensor icon disappeared completely and wouldn't come back until after another restart:
Streamable Video
Watch this video on Streamable.
streamable.com
This is just one example of the inconsistencies. I haven't changed the animation settings either.
I did see it happen a couple of times in your stream. I don't recall seeing that on mine, but I haven't been looking for it. The only other thing I can suggest is make sure you have the latest updates and/or factory reset.
Edit - I tried to replicate your stream, and the sensor showed in all 30 attempts for me. For whatever it's worth, so might be something specific to your device, maybe settings or software issue
turbosrrgood said:
I did see it happen a couple of times in your stream. I don't recall seeing that on mine, but I haven't been looking for it. The only other thing I can suggest is make sure you have the latest updates and/or factory reset.
Edit - I tried to replicate your stream, and the sensor showed in all 30 attempts for me. For whatever it's worth, so might be something specific to your device, maybe settings or software issue
Click to expand...
Click to collapse
It could be a bug related to my specific settings:
Rooted device, still on the October update
Lock after screen timeout: 30 minutes
Power button locks instantly: Off
gavingt said:
I just restarted my phone, and then repeatedly unlocked and locked it (sometimes by fingerprint, sometimes by tapping). By the end of the video, the fingerprint sensor icon disappeared completely and wouldn't come back until after another restart:
Streamable Video
Watch this video on Streamable.
streamable.com
This is just one example of the inconsistencies. I haven't changed the animation settings either.
Click to expand...
Click to collapse
what are you going on about lol. this is the kind of nonsense that is so irritating. you had 100% success rate unlocking your phone. what's the problem. looks to me like it works. so what's the big deal. and then you have the gall to complain that the sensor icon disappeared after you repeatedly locked and unlocked your phone? yea. try starting your car repeatedly. see what happens with the engine.
kramer987 said:
what are you going on about lol. this is the kind of nonsense that is so irritating. you had 100% success rate unlocking your phone. what's the problem. looks to me like it works. so what's the big deal. and then you have the gall to complain that the sensor icon disappeared after you repeatedly locked and unlocked your phone? yea. try starting your car repeatedly. see what happens with the engine.
Click to expand...
Click to collapse
Sure, ignore my multiple posts on the subject. It's not nonsense. I have no idea why you're trying to minimize this, and why you feel the need to be so combative.
gavingt said:
I'm already rooted because I absolutely needed the Back button to be on the right side.
Click to expand...
Click to collapse
You know gesture navigation is a thing now right? Back buttons are so "last decade".
sic0048 said:
You know gesture navigation is a thing now right? Back buttons are so "last decade".
Click to expand...
Click to collapse
Yes, I know and I hate it. It's extra motion that tires out my hand and I often trigger the gestures when I don't mean to.
gavingt said:
Sure, ignore my multiple posts on the subject. It's not nonsense. I have no idea why you're trying to minimize this, and why you feel the need to be so combative.
Click to expand...
Click to collapse
i will just apologize and go on with my day. good luck with the phone.
I went ahead and updated to the November firmware, and wiped my data as well. Now my phone won't show the fingerprint sensor while unlocking under any circumstances. I also found an interesting bug wherein I'm still able to turn my screen on by tapping it repeatedly even with "Tap to check phone" disabled:
screen-20211102-164842[1]
Watch "screen-20211102-164842[1]" on Streamable.
streamable.com
EDIT: And, of course, as I was typing this the fingerprint sensor just magically came back. And it still doesn't work unless I tap the dimmed screen to wake it first. Watch as it straight up ignores my finger the first time:
screen-20211102-171057[1]
Watch "screen-20211102-171057[1]" on Streamable.
streamable.com
I can recreate this 100% of the time by just setting my phone down for a second and picking it back up, then trying to unlock it. And you can't see it in the video, but the sensor doesn't even light up the first time I touch it. This is clearly a software bug.
gavingt said:
I went ahead and updated to the November firmware, and wiped my data as well. Now my phone won't show the fingerprint sensor while unlocking under any circumstances. I also found an interesting bug wherein I'm still able to turn my screen on by tapping it repeatedly even with "Tap to check phone" disabled:
screen-20211102-164842[1]
Watch "screen-20211102-164842[1]" on Streamable.
streamable.com
EDIT: And, of course, as I was typing this the fingerprint sensor just magically came back. And it still doesn't work unless I tap the dimmed screen to wake it first. Watch as it straight up ignores my finger the first time:
screen-20211102-171057[1]
Watch "screen-20211102-171057[1]" on Streamable.
streamable.com
I can recreate this 100% of the time by just setting my phone down for a second and picking it back up, then trying to unlock it.
Click to expand...
Click to collapse
but at least we know you like dunkin donuts, dominos pizza, and your mom forgets stuff
kramer987 said:
try starting your car repeatedly. see what happens with the engine.
Click to expand...
Click to collapse
Guess you don't know anything about cars. You can start and stop a fuel injected car until the battery dies, and nothing will happen to the engine or fuel system. (Yes, the battery will die if you keep starting the car and tuning it off right away) Just as proof of this, most modern cars shut off the engine when you come to a stop, and restart when you let off the brake. If you're in stop and go traffic, the engine will shut off and turn on repeatedly in a short amount of time nd distance.
Now with classic cars and motorcycles, you my flood the carb with repeated starts. Not a big deal, and not any kind of damage.
The only "damage" in repeatedly starting a car would be normal wear and tear on the starter. They do have a finite lifespan. But again, not damage, just use.