Develop Bugs

screen wont come back on during call

my wife has the att nitro hd, when the screen goes off during a call sometimes nothing including power button will turn it back on. Anyone know of a fix? did the ATT small update fix this?
Actually it comes back on after a long minute or two. Not very helpful if you need the dialpad or keys, etc.
I have just rooted it for her and installed CWM.
I have added a few proximity tweaks to build.prop
gsm.proximity.enable=false (rebooted twice but screen still goes off)
also used the ro.lg.proximity and the mot.lge.proximity (dont recall exact wording) both were set to a value of 5.
I'll have to take alook into the lg hidden dialer menu to see if I can disable this.
I dont like this sensor on my device either, but I have an option in settings to disable it, which makes it bearable.
thanks for the help guys.
I have noticied LG throws together some junky builds, typos, bad english/grammar. Wonky sensors etc. Incorrect kernel build ReadMe's
I thought I recall someone with another device just placing a peice of tape over the sensor. hmmm..worth a try.
cheers.

chrisrotolo said:
gsm.proximity.enable=false (rebooted twice but screen still goes off)
also used the ro.lg.proximity and the mot.lge.proximity (dont recall exact wording) both were set to a value of 5.
Click to expand...
Click to collapse
Congrats. Today, you learned that most of the "tweaks" found at XDA are utter bull****

aremcee said:
Congrats. Today, you learned that most of the "tweaks" found at XDA are utter bull****
Click to expand...
Click to collapse
What about the tweaks that aren't BS? Are they already included in your CM9 builds?

From what I can tell, pretty much the main thing that build.prop is good for is providing information about the system and software (i.e. info about the build). It's not really used much for useful configurations as far as I know.

networks tweaks actually have doubled me download speed.
I still have faith.
but can anyone answer my questions I posted in ICS SLim thread and PM'ed Andasa , no responses yet.
does ICS slim or CM9 have option to keep lcd no during call? and does it work??
what's working not working? I found changelogs but not a working/not working list for CM9.
and has anyone successfully restored a nandroid from ICS to GB without real issues?
thanks guys.

i doubt the ota fixed your issue as the issue is not one that occurs for every nitro.
I can tell you that when I make a phone call they screen stays no.
what's working not working, well, many of us are running it daily with no probs.
as you prolly know, it is a nightly build so a public list of what's working or not isn't rly part of the deal.
i've succesfully restore a nandroid from both slim and cm9 back to the stock att rom and others many many times. dozens.

thanks good enough.
I will have to give it a go.
would you recommend one or the other?
CM9 or slim?
thank you.

well, I like them both a lot. slim is just a trimmed down version of cm9 and i _think_ it does run just a bit snappier........maybe..but it's not wildly different from cm9. I usually switch back&forth throughout the day.

There's no setting in CM9 to disable the proximity sensor, although there may be a way to do it.

We just got a Nitro HD for my wife and her phone also has this issue. I have not gotten to know the phone well enough to try rooting or anything else of that nature, it's pure stock.
When she makes a call the screen turns off immediately after hitting the call button and will not wake up. When she receives a call we get a glimpse of the in-call screen with the various buttons etc but then the screen turns off. If the other party hangs up her screen turns back on, but if she calls something automated, like voicemail, she can't do anything except pull the battery to disconnect.
I've tried putting my thumb over the proximity sensor, hitting all buttons including power, and nothing makes the screen wake up or turns the phone off other than a battery pull.
The phone was running a build from last November when we first got it (V10i?) and today prompted us to update, so I did that hoping it would solve the problem. The phone is currently on V10j, but the problem persists.
Any help?

no driver said:
We just got a Nitro HD for my wife and her phone also has this issue. I have not gotten to know the phone well enough to try rooting or anything else of that nature, it's pure stock.
When she makes a call the screen turns off immediately after hitting the call button and will not wake up. When she receives a call we get a glimpse of the in-call screen with the various buttons etc but then the screen turns off. If the other party hangs up her screen turns back on, but if she calls something automated, like voicemail, she can't do anything except pull the battery to disconnect.
I've tried putting my thumb over the proximity sensor, hitting all buttons including power, and nothing makes the screen wake up or turns the phone off other than a battery pull.
The phone was running a build from last November when we first got it (V10i?) and today prompted us to update, so I did that hoping it would solve the problem. The phone is currently on V10j, but the problem persists.
Any help?
Click to expand...
Click to collapse
If you bought it from a store, get it exchanged for a new one.

actually works much faster on cm9, but therr still should be an optin to keep lcd on during call. i found some free apps that will disable hardware drivers but cant find the name of the proximity sensor driver, only that is named LGE.

Unfortunately it was given to us by a friend after my wife lost her Captivate, so taking it to a store to exchange is probably not going to work too well. As far as I can tell it was never used before we got it--the battery was still in it's own sealed pouch, the texting and driving warning was on the phone, and the phone went through the whole initial setup routine--but they didn't send us the box, I guess to cut down on mailing costs. I was hoping there was a known solution.

Ok, I downloaded two proximity sensor test apps today, but neither showed any activity. On my Captivate I get different readings with Proximity Sensor Finder (market link), but on the Nitro it is stuck at 3cm and it doesn't register anything no matter where I put my hand over the phone.
Can someone whose phone works right try installing this app and make sure that it picks up different readings on this device? OP, if you are still having issues, can you also try this app and see if it is static for you?
Thanks.

Took off the screen protector that they installed at the AT&T store and now the proximity sensor works just fine. OP, do you have a screen protector on your device?

we had an awfully thick one from att. we have since changed it to a super thin one. screen off is not a real problem on cm9, however i feel all devices should have the option to disable proximity sensor/keep lcd on during calls.

It's worth trying to use the warranty on the phone. Even though you dont have the original sales reciept, the phone has been released for less than a year, so no matter when you bought it, it is still within it's year long guaranteed warranty window.
Finished reading the thread, I suppose this post is now irrelevent

[Q] Galaxy Nexus Sleep of Death

Problem: Cannot turn on the screen by pressing the power button sometimes. The screen is black or very dim, I cannot tell. One can see nothing on the screen, and it doesn’t accept any touch input, either. The phone still rings if there’s an incoming call. If this happens, the following several presses (about 10 - 20) on the power button will probably lead to a reboot. The “screen auto-rotate” and the proximity sensor may fail after the reboot, but will recover after a manual reboot.
Frequency: Fewer with higher Rom version. About once per day for 4.3.
Other description:
 The problem frequently happens when I just take the phone outside my house/office, and seldom happens when the phone just stays somewhere.
 The problem seems to be irrelevant to the remaining battery capacity or the uptime, but it never happens when charging.
 The problem seems to be irrelevant to the Apps installed.
 The problem seldom happens in the first 3-4 days after flashing a Rom, but happens more and more frequently as time goes by. My guess is some cache is stuffed by some trash, which causes the problem. The phone may be fine as long as the trash can be cleaned up on a regular basis.
 I manually reboot my phone at most every two days.
Solutions tried, but don’t work
 Flashing official ROMs 4.0.4, 4.1.1, 4.1.2, 4.2.2 and 4.3 following the procedure “adb reboot bootloader; fastboot oem unlock; flash-all; fastboot oem lock”, without google wallet, not rooted.
 Turning off the auto-brightness control, as suggested by some post on the Internet.

Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app

Thymo said:
Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.

Bobby_yan said:
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.
Click to expand...
Click to collapse
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.

Thymo said:
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.
Click to expand...
Click to collapse
No.
No, I just tried the official ROMs. Any suggestion?

Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...

eKeith said:
Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...
Click to expand...
Click to collapse
Thanks a lot. I'm trying it.

Bobby_yan said:
Thanks a lot. I'm trying it.
Click to expand...
Click to collapse
LagFix does NOT help in my case. Any other suggestions? Thanks.

I've also had this blank screen with calls still ring issue for as long as I can remember, nearly 2.5 yrs.
I've always suspected it's my ROM and so I'd try out another ROM'S, BUT no other ROM works like how I'd like, so I always come back to my ROM.
It doesn't happen every single day, but it does happen very often.
I've tried using apps that auto reboot daily, but eventually this blank screen issue will return.
Unfortunately I can't seem to find any solution, so I just put up with it, it's like the 1 only flaw with my ROM.
&
Not to be at all rude, but I'm really glad op has had this issue from testing other versions of Android, cause then at least I know I don't need to give up my great tablet mode ROM.
LOL

I think I've finally found a work around for this screen of death.
Using Exposed, download/install this module/extension:
Disable Proximity
http://repo.xposed.info/module/com.mrchandler.disableprox
It does exactly what it's name is and ever since then I've not once had to remove my GN battery to work again because the screen went completely dead.

NVM
Screen still goes dead.
Anyone find an actual fix to this?

isajoo,
I had pretty much the same problems with my Galaxy Nexus running CyanogenMod 11 M12.
It got better by doing the following :
Blowing dry air in the earpiece… though the proximity sensor is clearly beside it. Can't do any harm though, I guess.
Settings/Applications/All/menu/Reset applications preferences (or whatever that's called in english) : that seemed to do a lot of good to my phone ! However, it's a very unsatisfactory answer on a technical point of view, as I still don't know WHAT was precisely needed. It's a "magic wand" solution for which I can't give an explanation.
Not specifically related, but greatly helped my phone in the responsiveness area : Trimmer (fstrim) (https://play.google.com/store/apps/details?id=com.fifthelement.trimmer), an updated version of LagFix that you may already know
Hope that helped !
(I wanted to try http://www.androidlegend.com/how-to-perform-proximity-sensor-calibration-on-any-samsung-phone/ as well, but apparently, /sys/class/sensors/proximity_sensor/prox_cal does not exist on my phone…)

Wake up delay

Anyone else experiencing a really long delay when you try to wake your phone up? About 70% of the time when I wake my phone up to just use my phone, it has a bad delay. Most of the time it will take around 7 - 10 seconds for the screen to turn on.
I am stock and un-rooted. I have gone into the stock recovery and cleared the cache partition a couple of times, but that doesn't help. I am really hoping for S-off soon. I'm hoping that a custom rom can fix it.

I'm also experiencing this same problem, drives me insane. I'm hoping that maybe the forthcoming 5.1 update will address that issue.

I've never experienced this. I'm stock still. Kinda sounds like a runway app causing the problem.

Never saw this on launch os or 5.1. Have you tried running it without apps for a while?

Last night I disabled instagram. It seemed to fix the problem so far. I don't use it much anyway. My battery stat still shows it as number 2 on the list. I just uninstalled it. Maybe it will fix some issues.

I have this too...but I'd say only about 30 percent of the time. I use the double tap to wake aout it certainly does not all the time.

Mine does it sometimes. I don't know if it's a delay because I push the power button again and it comes on. Another thing that drives me up the wall is that the screen doesn't wake up after taking the phone away from my ear during a call sometimes. I'll have to push the power button to turn the screen on.
Sent from my HTC6535LVW using Tapatalk

Evocm7 said:
Mine does it sometimes. I don't know if it's a delay because I push the power button again and it comes on. Another thing that drives me up the wall is that the screen doesn't wake up after taking the phone away from my ear during a call sometimes. I'll have to push the power button to turn the screen on.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
This sounds like either a case problem, or proximity sensor.
You can test the sensor in htc advantage app.

andybones said:
This sounds like either a case problem, or proximity sensor.
You can test the sensor in htc advantage app.
Click to expand...
Click to collapse
I just tried it, it passed the tests a few times. I have a spigen neo hybrid so it doesn't come even close to the sensor. Who knows.
Sent from my HTC6535LVW using Tapatalk

Mine doesn't wake up after a call sometimes. It just started doing the delay thing again. I wonder if it has anything to do with memory leak on 5.0? I may disable a couple games I downloaded this week and see if that fixes it.

andybones said:
This sounds like either a case problem, or proximity sensor.
You can test the sensor in htc advantage app.
Click to expand...
Click to collapse
Andybones, maybe I'm being a little dense but the htc advantage app? what or where can I find this? Thanks, Howie

meandg5 said:
Andybones, maybe I'm being a little dense but the htc advantage app? what or where can I find this? Thanks, Howie
Click to expand...
Click to collapse
Playstore search app: HTC Help.

andybones said:
Playstore search app: HTC Help.
Click to expand...
Click to collapse
Thank you sir!
Sent from my HTC6535LVW using XDA Free mobile app

!! 7 attempts at swiping up !

Maybe it's just the screen protector, I know I've read some stuff about the screen protector and people rooting and flashing something, but I swear this thing doesn't respond to my touch. I'm on Android p DP 2 and just factory reset it to see if it helps with some app bugs. Just swiped up 7 times before it went up so I could type my pin in, this has been an issue with this particular device.

kickenwing13 said:
Maybe it's just the screen protector, I know I've read some stuff about the screen protector and people rooting and flashing something, but I swear this thing doesn't respond to my touch. I'm on Android p DP 2 and just factory reset it to see if it helps with some app bugs. Just swiped up 7 times before it went up so I could type my pin in, this has been an issue with this particular device.
Click to expand...
Click to collapse
I have noticed this sometimes as well on DP2. I have a fingerprint setup but my phone is usually lying on my desk so i swipe up and enter the pattern. Sometimes it just refuses to swipe up and stay there.. its sort of bounces back down. I have to pick up the phone and use the fingerprint scanner.

They lock screen swipe issue was fixed for me recently on a security update but on dp2 sometimes it's worst then it ever was before the fix.

Just tap the lock, no need to swipe

Ah never noticed that. If you have the fingerprint enabled, tap the fingerprint icon.
akellar said:
Just tap the lock, no need to swipe
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk

akellar said:
Just tap the lock, no need to swipe
Click to expand...
Click to collapse
And this is why you're a senior member, that's pretty helpful. Now swiping away notifications would be wonderful

amazes me that people run essentially a beta version of the software and complain when things arent working correctly.

skimminstones said:
amazes me that people run essentially a beta version of the software and complain when things arent working correctly.
Click to expand...
Click to collapse
Are they not allowed to test and provide feedback? Why does it bother you?
Anyways, to be fair, I've been experiencing this issue off and on ever since I purchased the phone. And no, I'm not running beta firmware.

Why does it bother you if I comment?
If you're running a version of Android that hasn't been officially released yet then there is always going to be issues. That's pretty obvious frankly.

The lockscreen swiping is definitely an issue with the Pixel 2 XL. I always had this issue on Oreo but on P DP2 it's gone. It's interesting how it's the opposite for others in this thread.

Even on Oreo, it's hit or miss.
Swiping away notifications almost always takes at least 2-3 tries.
Super annoying for a phone this expensive.

E30Nova said:
Even on Oreo, it's hit or miss.
Swiping away notifications almost always takes at least 2-3 tries.
Super annoying for a phone this expensive.
Click to expand...
Click to collapse
Oreo Lock Screen Fix (Substratum) from Arol Wright fixed it for me.

skimminstones said:
Why does it bother you if I comment?
If you're running a version of Android that hasn't been officially released yet then there is always going to be issues. That's pretty obvious frankly.
Click to expand...
Click to collapse
You seem very passionate about this issue so let me clarify... It's been an issue the entire life of this phone ON ANY AND ALL SOFTWARE.

skimminstones said:
amazes me that people run essentially a beta version of the software and complain when things arent working correctly.
Click to expand...
Click to collapse
To be fair....even before I jumped on dp2....I had these same lockscreen issues on Oreo. It's just worse on dp2.

kickenwing13 said:
You seem very passionate about this issue so let me clarify... It's been an issue the entire life of this phone ON ANY AND ALL SOFTWARE.
Click to expand...
Click to collapse
Nope, No issues on mine

Yeah the swipe up issue definitely does happen once in a while for me but it's not often or consistent. Now that I know the tap the fingerprint/lock does the same thing, I just do that.
Sent from my Pixel 2 XL using Tapatalk

No issues here. If i'm looking for perfection ill go purchase one of those $25,000 phones and even then you'll find something wrong.

Mate 20 X Unresponsive Screen

Hello guys!
I have bought a brand new Mate 20 X just 3 days ago!
I noticed that some times I click something and it wont do anything or do it with delay and sometimes I click on something and it vibrates like it did it but nothing happened (like home button for example).
Does anyone else face this issue? do you know how to fix it?
Have a great day!

Nothing here, I also use the gestures so never use the home button. Is it specific apps that cause issues or just in general?

yetiweston said:
Nothing here, I also use the gestures so never use the home button. Is it specific apps that cause issues or just in general?
Click to expand...
Click to collapse
everywhere all apps all places

omer919 said:
Hello guys!
I have bought a brand new Mate 20 X just 3 days ago!
I noticed that some times I click something and it wont do anything or do it with delay and sometimes I click on something and it vibrates like it did it but nothing happened (like home button for example).
Does anyone else face this issue? do you know how to fix it?
Have a great day!
Click to expand...
Click to collapse
Yep, it happens to me quite frequently. I don't think it has anything to do with the screen though. Do you have a nano memory card? Are you stock? What apps have you installed? What browser do you use? Mine started doing it after the 192 update (I think) and has been doing it ever since whether I'm on stock or on a custom rom. You'll tap a program and see that it selected but sometimes it takes like five to ten seconds to open.

ajsmsg78 said:
Yep, it happens to me quite frequently. I don't think it has anything to do with the screen though. Do you have a nano memory card? Are you stock? What apps have you installed? What browser do you use? Mine started doing it after the 192 update (I think) and has been doing it ever since whether I'm on stock or on a custom rom. You'll tap a program and see that it selected but sometimes it takes like five to ten seconds to open.
Click to expand...
Click to collapse
All stock, latest update no unlocked bootloader (EVR-L29)
I disabled all gestures, I dont have a nano memory card, its not app related, it even happens on the notifications tray when I try to reply to someone but the button doesnt work. even when I type there is a delay that make me miss some clicks I have done

omer919 said:
everywhere all apps all places
Click to expand...
Click to collapse
Have you tried a hard reset to see if that fixes it?

yetiweston said:
Have you tried a hard reset to see if that fixes it?
Click to expand...
Click to collapse
yes, from recovery. didnt help
also scrolling is very slow compared to other phones even when scrolling the fastest I can its very slow.

ajsmsg78 said:
Yep, it happens to me quite frequently. I don't think it has anything to do with the screen though. Do you have a nano memory card? Are you stock? What apps have you installed? What browser do you use? Mine started doing it after the 192 update (I think) and has been doing it ever since whether I'm on stock or on a custom rom. You'll tap a program and see that it selected but sometimes it takes like five to ten seconds to open.
Click to expand...
Click to collapse
Exactly the same a few times a day on stock or openkirin rr
Sent from my Kirin Treble using Tapatalk

sometimes when I touch with 2 fingers to zoom (for example on a document) it just stays on zoom mode even when I touch with 1 finger (so when I try to move around it will change the size like a 2 fingers gesture).
scrolling is way slower than any other phone I tested, has anyone else noticed that?

Take screen protector off and clean it might be smudged . Maybe you could try glove mode it's more sensitive in settings

stestesteste said:
Take screen protector off and clean it might be smudged . Maybe you could try glove mode it's more sensitive in settings
Click to expand...
Click to collapse
It's not a screen issue, it's a software issue.

stestesteste said:
Take screen protector off and clean it might be smudged . Maybe you could try glove mode it's more sensitive in settings
Click to expand...
Click to collapse
tried both, didnt help.

I thought I was the only one with this issue.
After flashing the Resurrection Remix rom I have never encountered this problem.
I'll be going back to stock soon so I'll see if the problem still exists.

Mine works perfectly. Even with the protective film scratched. Worked perfectly with my previous screen protector, a tempered glass type. I have the chinese EVR-TL00 midnight blue model. Everything stock, no root.

I also have this problem
You're not alone, this is happening to me as well on the EVR-L29. In my experience it is most noticeable when tap typing and a letter I tapped on does not register. Also, once in a while when I tap on an app to open it nothing happens and I'll have to tap it again for it to open. It's a mild annoyance for me, but not to the point of ruining the experience. I'm hoping a future software update addresses this, unless it's hardware related. I love the phone, but this is probably my biggest gripe outside of the possibility of no future upgrades in Huawei's spat with the US.