[Q] Is there any fix for the proximity sensor problem(during call) for Nexus 5 - Nexus 5 Q&A, Help & Troubleshooting

Hi everyone,
I have been searching for a fix for this proximity sensor( during call) bug which is in Nexus 5 ,i have seen for some other phone like nexus 4 etc.There is fix for it. But is there any solution for Nexus 5.
The issue can be viewed in this Youtube.

trisankur said:
Hi everyone,
I have been searching for a fix for this proximity sensor( during call) bug which is in Nexus 5 ,i have seen for some other phone like nexus 4 etc.There is fix for it. But is there any solution for Nexus 5.
The issue can be viewed in this Youtube.
Click to expand...
Click to collapse
I`am running 4.4.2 and not rooted and i don`t have that issue. Are you rooted and running stock or custom rom, running mods like xposed framework, running a custom kernel and/or recovery? Info please

ya i am rooted and i m in stock rom only,but using Franco kernal(R32).Xposed framework i m using gravitybox(KK).I have CWM recovery.
What is causing this problem any idea??
N thanks for ur reply.

trisankur said:
ya i am rooted and i m in stock rom only,but using Franco kernal(R32).Xposed framework i m using gravitybox(KK).I have CWM recovery.
What is causing this problem any idea??
N thanks for ur reply.
Click to expand...
Click to collapse
Look in the Xposed and/or Franco kernel thread for a similar issue like yours, there may be a fix posted. Last resort is to flash a stock image in fastboot and that will probably fix your problem.

trisankur said:
Hi everyone,
I have been searching for a fix for this proximity sensor( during call) bug which is in Nexus 5 ,i have seen for some other phone like nexus 4 etc.There is fix for it. But is there any solution for Nexus 5.
The issue can be viewed in this Youtube.
Click to expand...
Click to collapse
When asking for assistance it's best to provide as much information as possible. As it stands I have no idea what you're referring to, and I think it's safe to assume most people won't either.

Ok i will search in there threads.Hope there is some fix posted
Thanks.

trisankur said:
Ok i will search in there threads.Hope there is some fix posted
Thanks.
Click to expand...
Click to collapse
Hi,
But what is "this proximity sensor( during call) bug" you are referring? Honestly I have no idea what you are talking about, I never had noticed a bug or anything else with the proximity sensor during call
Like _MetalHead_ said if you want help describe the problem...

Ok fine i will keep that in mind, next time if i post any questions.

trisankur said:
Ok fine i will keep that in mind, next time if i post any questions.
Click to expand...
Click to collapse
For the next time ok, but for now (in this thread here) you can't describe/explain the problem???

There is video on youtube regarding this.i cant post it in here so.
Anywaz the issue is when i m in call,
Steps
1)Call a number
2)Screen goes off.
if i try to make the screen on(to end the all or anything) i have to press 4-5 times power button which also happens by luck to make the screen on.
Also when in call (screen is off),if i try to do something in the status bar.Like if i touch near status bar(in call screen off),when the call ends u can see the status bar was active even if the screen was off.
Hope i m understandable.

i have posted the description of the issue just now .

Historically, this was usually down to a crap screen protector blocking the sensors. OP - are you using an SP?

EddyOS said:
Historically, this was usually down to a crap screen protector blocking the sensors. OP - are you using an SP?
Click to expand...
Click to collapse
Ya i m using Sceen protector,but this issue is for poeple who r not using SP also ,in other forums i have seen the same issue.

Only happens to me in the dark.

touch control
I have the same problem, during call the screen go black like it shuld be ,but its stilk active so if you tuch it it still responsive as if its on, i found thet if i disable touch control the problem goes away...

trisankur said:
ya i am rooted and i m in stock rom only,but using Franco kernal(R32).Xposed framework i m using gravitybox(KK).I have CWM recovery.
What is causing this problem any idea??
N thanks for ur reply.
Click to expand...
Click to collapse
exactly the same for me!!! (except R33)

Same issue on mine, and I don't use a case or screen protector. It's annoying because I have to enter a passcode to check my voicemail, but the screen stays black when I move the phone away from my head. Putting it on speaker seems to fix the issue, but I don't always want my phone calls broadcast to everyone around me.

Related

Screen problems and a few doubts.

Hey, I have a bit of a problem. My screen is acting weird, clicking randomly or just not responding at all sometimes. The only way to fix it is to lock and unlock my screen. Sometimes, even that doesn't work. I also noticed a dead pixel on my screen. It's not very visible but annoying nonetheless.
Sometimes, after a call, my phone just stops responding, and I need to keep the power button pressed to restart it.
What could be reason for these problems? Also, I still have my warranty left. Would the service centre people be willing to fix an issue such as this?
I'm in college right now and won't be able to give it for service for another week. I'm not sure if parts are still available for our device. :/
Also, any news on the official India ICS update? I've been waiting for a while now, checking the forum every few hours for an update or a stable CM build. I know it devs can do it. Can't wait for it.
PS: Any news of epsy? He's been gone for a while now.
Sorry about so many questions. I'm just curious and kind of confused.
Sent from my GT-I9103 using xda app-developers app
sidaster said:
Hey, I have a bit of a problem. My screen is acting weird, clicking randomly or just not responding at all sometimes. The only way to fix it is to lock and unlock my screen. Sometimes, even that doesn't work. I also noticed a dead pixel on my screen. It's not very visible but annoying nonetheless.
Click to expand...
Click to collapse
it may b a software bug too... which rom r u using n r u rooted ??
chk wid ur scratchgaurd too
dead pixel r covered in warranty so plz rush to ssc..
Sometimes, after a call, my phone just stops responding, and I need to keep the power button pressed to restart it.
Click to expand...
Click to collapse
definately software bug specially with indian gb rom.. recomend you to flash neo 3 rom or move to ics
What could be reason for these problems? Also, I still have my warranty left. Would the service centre people be willing to fix an issue such as this?
Click to expand...
Click to collapse
you need to make d ppl at ssc realize abt d prob or recreate these prob in front of dem...
bt dey wld simply reflash ur countrys latest firmware.. which u can also do....
I'm in college right now and won't be able to give it for service for another week. I'm not sure if parts are still available for our device. :/
Click to expand...
Click to collapse
yes spare parts r available...
if nt den dey will refund u or a similar priced device...!!
Also, any news on the official India ICS update? I've been waiting for a while now, checking the forum every few hours for an update or a stable CM build. I know it devs can do it. Can't wait for it.
Click to expand...
Click to collapse
ics has been released for various region... bt atleast nt for india yet.. bt d quality of all ics region is nearly same...
PS: Any news of epsy? He's been gone for a while now.
Click to expand...
Click to collapse
espy is bzy n wont start wrk untill dec...bt derz already a 90% functional cm10
Sorry about so many questions. I'm just curious and kind of confused.
Click to expand...
Click to collapse
its okk to ask too many quest bt nt here... bt in QA thread...
Sent from my GT-I9103 using Tapatalk 2
@ both persons above; thanks - I myself am facing some problems mentioned in OP (post-call phone dies, sometimes touch is unresponsive and have to lock/unlock screen, slight pixel problem) - and even my phone's warranty runs until Jan 2013.
I'll visit a service center ASAP (possibly this weekend if it's open or next week) and get it sorted.
Cheers!
sidaster said:
My screen is acting weird, clicking randomly or just not responding at all sometimes. The only way to fix it is to lock and unlock my screen. Sometimes, even that doesn't work.
Click to expand...
Click to collapse
may be its about your fingers huh? if u touch the screen with sweated or wet fingers, messaging is going to be nightmare
my advice is cleaning your screen with a clean and wet linen or cotton material, and then with a dry one.
also have a high quality screen protecter film.
if u have already tried this and the prob still occours, thats something that i dont have any idea
Thanks, I'll take it to the SSC as soon add i get home.
btw, i avoid using my phone with sweaty or wet hands, and since wiping the screen doesn't help, that's probably not it.
I think the screen guard might be the culprit after all. I've been thinking of changing it for a while now. any suggestions on which one to get?
Sent from my GT-I9103 using xda app-developers app

[Q] A problem in proximity sensor

Hello
I have a big problem, unfortunately the display screen of my new nexus 5 was crashed over the proximity sensor, so my proximity sensor always on, when I am making calls my screen is off and i can't do any thing even hang up the call , so how can i disable my proximity sensor.
My phone isn't rooted
I don't think you can disable it, not without root anyways. Can you still turn the screen on with the power button?
Sent from my Nexus 5 using Tapatalk
bblzd said:
I don't think you can disable it, not without root anyways. Can you still turn the screen on with the power button?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
no i can't turn it on
Any help please
moodyy25 said:
Any help please
Click to expand...
Click to collapse
Read this thread: http://forum.xda-developers.com/nexus-4/help/solved-how-to-disable-nexus-4-proximity-t2558878
See if any of the suggestions here work for you.
Also try this: https://play.google.com/store/apps/details?id=com.itsme4ucz.screenoff
All of these things were found by searching Google for 2 minutes. Sometimes it can be a better option than here for unique things.
Good Luck.
El Daddy said:
Read this thread: http://forum.xda-developers.com/nexus-4/help/solved-how-to-disable-nexus-4-proximity-t2558878
See if any of the suggestions here work for you.
Also try this: https://play.google.com/store/apps/details?id=com.itsme4ucz.screenoff
All of these things were found by searching Google for 2 minutes. Sometimes it can be a better option than here for unique things.
Good Luck.
Click to expand...
Click to collapse
thank you for your reply
i did google search before posting here and i tried both before posting but it didn't work with me
thank you again , waiting other suggestions
it looks like no solution for this problem ?????????????????
please help
i can't use my phone ?????????????????
if people already given you options, and it doesn't work. what do you think you should do ????????????????????????????
Get it fixed by technician. Disabling it is only a temporary fix.

[Q] Touch screen stops responding must reboot to fix

Recently two n5 we have in the family started doing the same thing,
touch screen is not responsive (buttons do work) and the device must be
rebooted holding the power button to get it working again.
Quite annoying since it happens couple times every day.
Searched around but didn't find any reports.
Both phones stock, rooted, gravity box and touch control installed.
Any ideas?
Thanks
I'm going to take a wild guess here, But try uninstalling touch control and see if the problem occurs again. touch control has no issues on my phone btw.
zubsz said:
I'm going to take a wild guess here, But try uninstalling touch control and see if the problem occurs again. touch control has no issues on my phone btw.
Click to expand...
Click to collapse
Thanks for reply!
What kernel are you using with touch control (Franco 33)?
It was working perfect for us with Franco till about rev 29, after that we got problems with graphic errors on the display once in the while, relished stock offered from touch control installation, and now this problem for change.
lifeisfun said:
Thanks for reply!
What kernel are you using with touch control (Franco 33)?
It was working perfect for us with Franco till about rev 29, after that we got problems with graphic errors on the display once in the while, relished stock offered from touch control installation, and now this problem for change.
Click to expand...
Click to collapse
Yes i'm using franco r33, I reverted to from r34 due to otg issues that I need to get around to sorting out. Hope things go well for you.
zubsz said:
Yes i'm using franco r33, I reverted to from r34 due to otg issues that I need to get around to sorting out. Hope things go well for you.
Click to expand...
Click to collapse
Thanks, will try 33 as well on one of them ?
Just had to be send mine back for same problem, only turning it off didn't fix my problem. Not rooted
Hmm...this just started happening to be as week this week. Happened twice today. I'm running the stock ROM & kernel.
I wonder if an update to some app is causing this.
Sent from my Nexus 5 using Tapatalk
Installed FC 33, the touch screen problem is not there anymore but the graphic distortion is back.
It happens once in the while and looks like poor TV signal for second or two.
chrisnewton said:
Just had to be send mine back for same problem, only turning it off didn't fix my problem. Not rooted
Click to expand...
Click to collapse
Meaning when you rebooted it did not fix it?
lifeisfun said:
Meaning when you rebooted it did not fix it?
Click to expand...
Click to collapse
Correct mate
chrisnewton said:
Correct mate
Click to expand...
Click to collapse
Oh OK, if I reboot it's working fine and since 2 devices have the same problem using same set up, it shouldn't be hw problem.
Well mine has gone back.. Sounds like a different problem.

Led notification light issues

Hi all
Just got my 2nd nexus 5, first one went back for touch screen issues. Got 2nd one and this has problem too.
If someone sends me a text the pulse notification light pulses once and that's it. No repeat. However after that if someone sends me a text it works as it should, ie repeats every 10 seconds.
Seems very random as to when it works properly. Anyone else have this issue?
Thanks all
Chris
chrisnewton said:
Hi all
Just got my 2nd nexus 5, first one went back for touch screen issues. Got 2nd one and this has problem too.
If someone sends me a text the pulse notification light pulses once and that's it. No repeat. However after that if someone sends me a text it works as it should, ie repeats every 10 seconds.
Seems very random as to when it works properly. Anyone else have this issue?
Thanks all
Chris
Click to expand...
Click to collapse
Yes, people have this problem on stock rom.. It appears randomly though and not as often as you're getting. A restart fixes it... Are you using Light Flow or any app to control the LED??
No will light flow solve this?
Sent from my Nexus 5 using Tapatalk
chrisnewton said:
No will light flow solve this?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
May be, May be not. Even light flow has some random problems with LED notifications... For some people it works flawlessly, for some it doesn't... Only way is to try it out...
vin4yak said:
May be, May be not. Even light flow has some random problems with LED notifications... For some people it works flawlessly, for some it doesn't... Only way is to try it out...
Click to expand...
Click to collapse
Trying it now seems to work ok. Strange that my last nexus didn't suffer this problem. Wounder if Google are aware of this issue?
Also on a side note not sure if it's related but I'm sure my first nexus 5 did a software update when I first took it out of the box, my new one did not do that.
chrisnewton said:
Trying it now seems to work ok. Strange that my last nexus didn't suffer this problem. Wounder if Google are aware of this issue?
Also on a side note not sure if it's related but I'm sure my first nexus 5 did a software update when I first took it out of the box, my new one did not do that.
Click to expand...
Click to collapse
Yes, I think they are aware of it... I remember reading it somewhere around XDA about it.. Can't find a link to it though.. I guess we will just have to wait for the update and see... FYI, a reboot fixes the issue temporarily..
It didn't update because the ones which were manufactured in January came with 4.4.2 Out of the box which is the latest update!
vin4yak said:
Yes, I think they are aware of it... I remember reading it somewhere around XDA about it.. Can't find a link to it though.. I guess we will just have to wait for the update and see... FYI, a reboot fixes the issue temporarily..
It didn't update because the ones which were manufactured in January came with 4.4.2 Out of the box which is the latest update!
Click to expand...
Click to collapse
Thanks for your reply mate, for me when I reboot the first message does not work, then they seem ok after that, that's just for sms, I get no notifications at all with whatsapp etc, however light flow seems to work ok at moment but would be nice if Google did a fix.

Touch Problem

Q few months afo i replaced my G3 Screen as old one was broken and after updating it to M.M stock rom or even flashing some other M.M + roms touch is not working from staring after ph boot up.
But when i go down to L.P it work perfectly....
Any one can help....
PlZzz...
Thx....
Yup... need a Moto OEM touchscreen, half of the third party ones, typically the cheaper ones, don't work on Marshmallow. We still don't understand why, but it's been a thing for quite a while.
Piyush Garg said:
Q few months afo i replaced my G3 Screen as old one was broken and after updating it to M.M stock rom or even flashing some other M.M + roms touch is not working from staring after ph boot up.
But when i go down to L.P it work perfectly....
Any one can help....
PlZzz...
Thx....
Click to expand...
Click to collapse
Try nougat roms
Prashant324 said:
Try nougat roms
Click to expand...
Click to collapse
same with that...
Piyush Garg said:
same with that...
Click to expand...
Click to collapse
This is a known issue... we don't know why for sure, but some non-OEM replacement touchscreens do not work with anything but Lollipop... And we don't know how to make it work other than replacing it with an Moto OEM touchscreen or one that is of high quality.
acejavelin said:
This is a known issue... we don't know why for sure, but some non-OEM replacement touchscreens do not work with anything but Lollipop... And we don't know how to make it work other than replacing it with an Moto OEM touchscreen or one that is of high quality.
Click to expand...
Click to collapse
I am interesting why devs dont wanna implement l.mretus synaptics driver in all newer android or custom distributions than lollipop knowing this!
Its really strange , Lenovo is doing nothing in this case but devs could do..but they have conviced that its working(newer driver) for them but its not heh if something is good for everyone..why we can't use it?
pio80 said:
I am interesting why devs dont wanna implement l.mretus synaptics driver in all newer android or custom distributions than lollipop knowing this!
Its really strange , Lenovo is doing nothing in this case but devs could do..but they have conviced that its working(newer driver) for them but its not heh if something is good for everyone..why we can't use it?
Click to expand...
Click to collapse
Because it creates other potential issues for minimal gain I assume. I can't really answer that question definitively.
I have ghost touch issue only while calling........i tried Marshmallow Stock ROM CM 13 and LineageOS14........i couldn't fix this........
NOTE: I didn't remove or replace my display......the phone is intact
Sachin ET said:
I have ghost touch issue only while calling........i tried Marshmallow Stock ROM CM 13 and LineageOS14........i couldn't fix this........
NOTE: I didn't remove or replace my display......the phone is intact
Click to expand...
Click to collapse
Does the screen blank (turn off) when you hold it up to your ear? If so, I do that know, if it doesn't you have a proximity sensor issue and the device needs to be repaired/replaced.
acejavelin said:
Does the screen blank (turn off) when you hold it up to your ear? If so, I do that know, if it doesn't you have a proximity sensor issue and the device needs to be repaired/replaced.
Click to expand...
Click to collapse
Yes the proximity sensor works perfectly fine (Screen Turns off when it's covered while calling)
Sachin ET said:
Yes the proximity sensor works perfectly fine (Screen Turns off when it's covered while calling)
Click to expand...
Click to collapse
So what is the issue then? If the screen is off it shouldn't be recognizing any touches... or am I misunderstanding the problem?
acejavelin said:
So what is the issue then? If the screen is off it shouldn't be recognizing any touches... or am I misunderstanding the problem?
Click to expand...
Click to collapse
I'll explain........the problem is when i am making a call and not holding it to my ear (Or it hapens in the time gap between dialing and holding it to my ear)........same thing happens in the case of incoming call, that is i cant pick the incoming call(either the screen freazes or the ghost touch automatically" Decline" my call).
I am attaching a link down here........please have a look at it........ it is a screen recoded video during an incoming call.
https://drive.google.com/file/d/0B_yXW_DztkJ7Nkt2NlBLQmpQR2M/view?usp=drivesdk
NOTE ( i didn't touch the screen while recording........the whole thing happens automatically)
Thanks

Categories

Resources