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
Related
My phone goes to sleep
and does NOT wake up, the bottom row of buttons and keyboard both light up if I open them or press them.
Help please!
rossle12 said:
My phone goes to sleep
and does NOT wake up, the bottom row of buttons and keyboard both light up if I open them or press them.
Help please!
Click to expand...
Click to collapse
Stock ROM or custom? Any overclocking?
The phone powers up if you soft reset, correct?
Well, I found out it was a small problem with the rom.
It was a custom rom, and I just installed a different one and it works flawlessly.
With the other one, the light sensor did not work either.
Also, I dropped my phone the other day, and a really small spring fell out.
And the back plain on my screen is loose and opens up easily..
Which ROM?
I hate to hijack this thread but i am having the exact same problem. Basically when i put my phone to sleep its hit or mess as to if it will wake. It seems to have started when i flashed Energy ROM. It was terrible after that, so I switched back to the stock ROM available from the HTC website and all seemed well at first. Now its back to hit or miss.
I cant really rule out a hardware issue such as a broken sensor or something because I'm not sure how the mechanics of it work. When i push the power button on top the phone wakes but not the screen I know this because the 4 lights on the bottom light up and the keyboard as well. I can hit the button repeatedly but it doesnt help. At other times it works flawlessly, but usually does not.
Can anyone give me a suggestion as to what it could be, or a way to rule out a hardware issue?
Exactly my problem!
It was perfectly fine for the first day or so before it started crapping out again..
Can someone please help us with this problem?
It's mind consuming and it's making me worry.
Until TP3 is out, I won't get a new phone ):
Well, the problem is discussed in great detail on the internet, but no one can give a definitive answer. ..
I've been a touch pro 2 user for exactly 3 days... My new HD2 from T-Mobile is in the mail... This is a un acceptable flaw with no real solutiion... Good Luck TP2 users....
Good luck to you.
I've had mine for over two years and it was flawless
Just one recent drop determined everything
Although I Must say, it was one hell of a durable phone
Yea, dont get me wrong. I really like the phone. Thats why I'm getting the HD2. Great OS and big beautiful screen. I'm gonna miss the slide out keyboard but I think thats what breaks these phones.
I'm excited that there's the possibility of running Windows Mobile 7 on it.
rossle12 said:
Can someone please help us with this problem?
Click to expand...
Click to collapse
I'd like to try to help. But you never answered my question of what ROM you are on (and which one you tried previously).
I've determined my problem is 100% hardware related. If I open my keyboard and then grab the screen and tweak it while pressing the power button it comes onn 100% of the time. Sux, but at least I know the cause now
djowen6565 said:
I've determined my problem is 100% hardware related. If I open my keyboard and then grab the screen and tweak it while pressing the power button it comes onn 100% of the time. Sux, but at least I know the cause now
Click to expand...
Click to collapse
Every once in a while my phone would turn on and I wouldn't know why
But yeah, I think it is hardware related.
I previously used Energy then went to Jacko's.
Both were perfectly fine, just the upsetting sleep function and light sensor would keep the phone off.
HELP: Same problem Phone not waking up
Hi saw this thread and was wondering if anyone can help me.
I have an HTC Touch Pro 2 for some month now...
Using the following details:
OS Version: 5.2.21887 (21887.5.0.86)
ROM Version: 2.07..401.1 (80303) WWE
ROM date: 02/04/10
Radio ver: 4.49.25.91
stock ROM basically...
THe issue is that the phone doesn't wake or when using it just freezes/hangs.
Not much software/apps installed... and memory is good as well.
I just don't know what's going on...
Help please.
Thanks
rossle12 said:
Every once in a while my phone would turn on and I wouldn't know why
But yeah, I think it is hardware related.
I previously used Energy then went to Jacko's.
Both were perfectly fine, just the upsetting sleep function and light sensor would keep the phone off.
Click to expand...
Click to collapse
I'd agree with the notion that its likely hardware related. I've flashed maybe 10 different builds of Energy over the last 7 months or so, and never once had and issue with the SOD (sleep of death) that I can recall. A bad flash can sometimes happen. But since you flashed another reputable ROM (Jackos), that somewhat eliminates the possibility that a bad flash is the culprit.
You can start from scratch, by running Task29 to format the ROM area of the phone's memory, and reflash the ROM. But this would be just to eliminate the possibility of a bad ROM flash. My gut says that you won't see any different results.
Running the phone "clean" for a while (to see if you still have the SOD) without any software installed or any other modifications will eliminate the possibility that any software or mods are responsible for the issue.
are you sure its hardware related? because my phone started doing this yesterday too...I had an energy rom from october, and it was really buggy. I am only able to keep my phone from sleeping when it is plugged in to some power, so i flashed the newest energy rom and still having the same problem...wont wake up from sleep
EDIT:
I dont see how this can be hardware related because everytime i soft-reset, the screen works again. this problem only happens when the device goes to sleep...
Any overclocking?
As I already mentioned, I never had any SODs on Energy that I can recall, except when using OCT (OverClocking Tool).
I have done no overclocking...I just flashed the newest energy rom like 15min ago...is there anything else I can do or check? it looks like the phone works still, just no backlight...
After flashing the ROM, maybe try running it "clean" for a day or two, don't install any software or do any mods, reg edits, etc. If you still have problems with the phone waking up with a new ROM, and no other software or other mods, than it may indicate a hardware problem.
And be sure to run Task29 before you flash the new ROM, if you don't already do that.
You guys should read the following thread:
http://forum.xda-developers.com/showthread.php?t=648134
You're not the only ones (by any means) with the SOD issue. But it isn't at all clear what causes the issue. Lots of different theories in that thread about various software or ROMs, with no clear solution.
Lots of conflicting info, but some comments on the thread suggest (as I mentioned) that Task29 may help (certainly can't hurt).
moto2000 said:
are you sure its hardware related?
Click to expand...
Click to collapse
Nope, definitely not sure, especially after reading the thread linked above. But as I suggested before, Task 29, try a different ROM, and run it clean with no software or mods, and start eliminating the variables.
So most of us know about the System UI crash when using Chromecast, but this is even stranger. [Edit: an OTA update fixed this.] Some times, when I wake my phone up at the lockscreen or at times in the middle of a call - the touch screen stops responding. I can press and/or hold the volume buttons and there is a response on screen but I can not interact with the phone at that point. I can't continue to do battery pulls everytime. This is crazy. I'm on stock software. No crazy mods or anything. I've done a reset in the past and flashed the stock package again but this still happens every few hours. Only happens when the screen just wakes up...
Edit: This is a confirmed fix for me.
If you face the same issue, try:
open dialer
press 3845#* INSERT THREE DIGETS OF YOUR MODEL NUMBER THE PRESS #, for example, I am the F400K, so 3845#*400#
Hardware Device Test > Touch
update touch firmware
touch firmware version
wait 10 sec
reboot
I would say there is a misbehaving app causing the phone to lag in wake (that is all the unresponsiveness will be, extreme lag).
Sent from my Nexus 5 using Tapatalk
@Lennyuk - tried for over 30minutes after leaving it alone, I doubt it's a delay... Battery pulls work, but that's not the point.
deedscreen said:
@Lennyuk - tried for over 30minutes after leaving it alone, I doubt it's a delay... Battery pulls work, but that's not the point.
Click to expand...
Click to collapse
That was not his point.....to Find the app that is causing it go one by one uninstalling until you find it.... Something probably to do with app and the screen
Sent from my SM-N900P using Xparent BlueTapatalk 2
Epix4G said:
That was not his point.....to Find the app that is causing it go one by one uninstalling until you find it.... Something probably to do with app and the screen
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Totally agree with @Epix4G on this one. I am assuming you had a korean variant? The SK Telecom stock image is pretty ugly. Took me 3 debloat attempts before I had it behaving the way I wanted it to, but before I debloated, I had some lag issues (SK Telecom... grrrhhh).
Historically, Korean carriers (much like AT&T and Verizon) love putting useless junk on the phones for "productivity" but really they are there to charge Korean users more for other services, etc.
If you haven't done so, I would root and debloat, and see how big of a difference it makes (absolutely amazing performance after debloating on my F400S).
^^^^ - Will take that into consideration.
This may be a possible fix for now, can't yet confirm
open dialer
press 3845#* INSERT THREE DIGETS OF YOUR MODEL NUMBER THE PRESS #, for example, I am the F400K, so 3845#*400#
Hardware Device Test > Touch
update touch firmware
touch firmware version
wait 10 sec
reboot
It may or may not help
EDIT: It's been a few weeks and I haven't had this issue again. Usually every 4-6 hours it used to happen after powering on the screen, but so far so good.
Tried that with 855 version, it's not working. This is REALLY depressing as i just got a new phone and from day one i'm having this problem. I just can't believe LG screwed up like this, and there's no mention of this anywhere online other than this XDA thread. I hope i don't have to root and install custom rom as this really defeats the purpose of the phone.
@deedscreen
I'm having exactly the same problem on an 850 and tried your firmware method. The version number of the firmware did not change after reboot.
ic_fw_version info
SYnaptics 5.5
PanelType 1
version: v1.22
IC_product_id[PLG313]
Touch IC : s3528(family_id = 1, fw_rev = 1)
What version is your firmware? Also, did you find out about the fix from somewhere?
I have the F400K, but just got a US T-Mobile edition, (I'll eventually switch my signature). I would honestly suggest waiting for an OTA update. Call LG so they can document this. If that touchscreen update method doesn't work, I'm not sure what to do. I found the method somewhere online, I don't recall where exactly. If someone can figure out how to side load the touch screen firmware from a working Korean model to others, that would be great. For now, keep calling LG. It won't do much at first, but at least they'll have reports of this issue.
I have (RAW) touch screen firmware version: 30 05 51 96
Same problem, but not only on lock screen
Since 5 days I have my G3 (855 Modell). I was happy the first two days, then I discovered the problem, that the device is always unlocking itself, when in my front pocket. It's because of the Knock on feature. I deactivated this now.
But since yesterday i have the same issue: three times, i was unable to unlock my phone. The touchscreen simply did not respond. I had to remove battery. Today, I read this post and tried the firmware update of the touch, but I have the impression it did not change something in the version.
After this, today I had again once time the non responding touch while unlocking and shortly after, I had the issue after ending a phone call! The touch did no longer respond and had to remove the battery again!
I hope this is not a hardware issue, otherwise I will hurry up to the seller to exchange the phone, because its only 5 days old.
This is happening when the screen is on right? Or is the screen turning off and then not turning I again?
You need to keep Knock feature on, someone already said this. That's why your screen is freezing.
Daum Ex said:
You need to keep Knock feature on, someone already said this. That's why your screen is freezing.
Click to expand...
Click to collapse
Upps, yes, I just read this message now. To late: I was in the shop now and got mine exchanged. Anyway, that issue with the knock on feature should be solved also by LG: it's not acceptable, that the phone is always unlocking in my pocket.But then I wait with deactivating knock on for the moment.
So bad: such a good phone and such an annoying bug
icon71 said:
Upps, yes, I just read this message now. To late: I was in the shop now and got mine exchanged. Anyway, that issue with the knock on feature should be solved also by LG: it's not acceptable, that the phone is always unlocking in my pocket.But then I wait with deactivating knock on for the moment.
So bad: such a good phone and such an annoying bug
Click to expand...
Click to collapse
I sold mine after a few days, i was sick with it. I disabled the knock feature through the hidden menu only to have the screen freeze every day. What, i can't use the phone the way i like? I have to face the screen outwards in my pocket and risk damaging it? Screw that...
That, plus the overheating and horrible build quality (back got scratched in my pocket) was a deal breaker for me...
Daum Ex said:
I sold mine after a few days, i was sick with it. I disabled the knock feature through the hidden menu only to have the screen freeze every day. What, i can't use the phone the way i like? I have to face the screen outwards in my pocket and risk damaging it? Screw that...
That, plus the overheating and horrible build quality (back got scratched in my pocket) was a deal breaker for me...
Click to expand...
Click to collapse
Yes, indeed i also think about it. I got an official statement from support, regarding that the phone is unlocking all the time by itself in my pocket. They told me stuff like:
- this is a normal behaviour and can happen (!!)
- don't put your phone in the front pocket
- use the quick circle case to prevent...
- disable knock on (which is at least not possible over a standard setting, but only via the hidden menu).
I wrote back:
- that for me, this is not a normal behaviour
- that 90% of male users are wearing the phone in the front pocket
- that I don't like to buy a case only to prevent a bug of a premium telephone and
- finally, that they please could tell me, where and how to disable knock on
I am curious about their answer...
Good luck with that, disabling it through the settings doesn't change anything and they probably won't have a fix for months. They'll probably fix it though Android L update which will sadly come 6 months from official release at least.
Next time i purchase an Android phone i'm going with Nexus line...
icon71 said:
Since 5 days I have my G3 (855 Modell). I was happy the first two days, then I discovered the problem...
Click to expand...
Click to collapse
So what happened? How is it doing now?
Hey everyone, I just wanted to report my results of this touchscreen bug.
Well, I've only had my D851 for a week now. Of course I rooted it the same day I received it.
I had no touch issues until after restoring apps with Titanium Backup. I'd restore all user apps, then very few system app via XML. Since I just upgraded from a Galaxy S3 T999 I limited the system apps greatly. So much in fact that I only restored 1 system app......Media Storage 4.4.4 (Playlist). THAT WAS MY SCREEN KILLER!
The media scan on my D851 would render my screen unresponsive. I could only hold the power button and click power off or restart or whatever else was on that power menu. Then the phone would reboot after minutes of of a dead screen.
I flashed back to stock and reproduced the same issue. So now I've been running this device for 3 days without any screen lockups. I just have to rebuild my playlist again LOL.
I hope this helps someone here.
Knock
If you turn off the ability to wake by knocking the screen, it causes this issue where the screen locks. Turn it back on and the problem seems to go away.
I think LG really has to deal with this issue.
Hi guys, I have red a lot about this issue but I'm still confused with my LG G3 855.
First I realize problem with unlocking the phone using double click. Tried to upgrade touch software firmware using hidden menu and the screen became almost totally unresponsive. Tried to re-flash original 5.0 and 4.4.2, factory reset, battery removed, etc. but no luck.
I'm wonder if this is a software problem or became hardware. Should I consider replacing display or problem is in motherboard?
I really don't know what to do! Appreciate any comments or suggestions!!!
Thanks in advance!
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…)
Please refer to this post:
http://forum.xda-developers.com/showpost.php?p=62828995&postcount=1432
Has anyone gotten this problem? The person who posted this has been the only one having this problem. This can't be a rare thing, is it? Is everyone just dealing with this issue until it gets fixed?
Here is a compilation of the comments made about this issue thus far. There seems to be a consensus that screen protectors are not causing this issue.
11th August 2015
AnotherContributor said:
One issue though I've been having is that when I'm making and receiving calls, sometimes the phone display goes black and will frankly not come back on. I press the App button and sometimes the display comes on, sends the call to the Status Bar, and the screen goes dark. So, I have to press the Application button again and draw down the menu to hang the call up. When I press the power button, the screen flashes on for maybe a quarter second then goes dark. It keeps doing that every time you press the power button. The worst case scenario that has happened a handful of times is that when I'm in a call, neither the power nor application button are responsive. When that happens, pretty much the only option is to power down the phone and reboot.
...
I'm not sure if I would be able to dial an extension with the way the phone is acting up. I feel like this was not an issue the first couple of weeks I had CM on the phone. Now, it seems to be happening with every call.
Click to expand...
Click to collapse
14th September 2015
samuraix21 said:
Hi, I have this issue. Were you able to fix this issue? You're the ONLY person that has posted this issue so I'm not sure if this is a rare hardware issue or everyone on this forum is somehow dealing with it until a fix comes up.
Click to expand...
Click to collapse
19th September 2015
hawk1500 said:
are people still experiencing the screen off during call problem? I am not talking about when you put it up to your face, but how the screen turns off and won't come back on?
Click to expand...
Click to collapse
20th September 2015
hawk1500 said:
Naw, no screen protector installed. tried the proximity sensor fix app as well as the xposed don't go to sleep during call module but it still does it.
Click to expand...
Click to collapse
20th September 2015
tonochito said:
i think that bugs should be listed more detailed:
front facing camera does not work well, if i want to take a selfie it crash. video camera also does not work equal it will crash. I had to install Google Camera and Open Camera in order to have both selfie and video options working, With Google Camera i take selfies and with Open Camera i record videos, As the guy talking about the scren off in calls is true, i don't have a screen protector and it has this behaivour, also as i mentioned there is kind of lag when i try to dial a number i have to do twice, it doesn't show up right away. The same goes when i am calling for example my carrier and i have to dial on the IVR i have to dial twice in order to get the dial keypad. I didn't have Google play crash.
Another thing that i notice was setting a wallpaper as screensaver does not fit in the middle or correctly i had to use Quick Pic and the option 768x1280 because with the stock gallery wallpapers are like aside of the middle
Click to expand...
Click to collapse
I think this issue needs some attention. I am having this problem as well (with and without screen protector). There are times that I need to enter extensions and codes during calls which has become impossible. I have two of these phones and they both behave this way. I recommend that people start posting screenshots of the app Proximity Sensor Finder which displays different distance numbers detected by the prox sensor. See my screenshot attachment which shows the proximity sensor always detecting a "covered" state of 0.0cm even when nothing is in front of the screen. Everyone should go try this and post their findings.
Other phones on CM11 were able to fix this problem in the past by adjusting the calibration which is unique for each phone, so I started searching around through the Fire Phone CM11 files and I found these:
/system/etc/permissions/android.hardware.sensor.proximity.xml
I could not discern anything of value from this .xml file.
/persist/sensor_calibration/SHCAL_DU20060142640727.csv
This file seemed promising. Its timestamp is back in 2014 so I assume that this comes straight from the original Fire Phone files. If this file is actively used to govern sensor behavior, I'm wondering if perhaps it is not being read correctly. It makes me wonder if there is a log out there somewhere that could shed more light on it. Anyways, you can open up that badboy in any spreadsheet to discover sensor IDs for a bunch of sensors along with calibration coefficients in the form of:
SENSOR_TYPE=PROX SENSOR_ID=SI1143 SENSOR_REF=4CCU1 COEFF0=550.30
SENSOR_TYPE=PROX SENSOR_ID=SI1143 SENSOR_REF=4CCU1 COEFF0=395.62
SENSOR_TYPE=PROX SENSOR_ID=SI1143 SENSOR_REF=4CCU1 COEFF0=19262.26
You'll have to open it and analyze it in context of the other columns and other sensors. I've attached it (re-saved in xlsx format because .csv files are not permitted - if you don't trust my xlsx just retrieve the file from your phone). I highlighted the rows of interest. We could just mess with coefficient values, but without any guidance, it could just be a waste of time. Plus we don't know if this even governs the sensors or if it's just helpful documentation. If anyone has insight about this or even far fetched theories, please comment!
I'm thinking about doing a 'grep' on the entire file tree for some of these key words like SENSOR_ID=SI1143, SI1143, 4CCU1, COEFF0, SENSOR_TYPE=PROX etc etc - to see if any files use any of these terms. It may prove unfruitful due to the amount of compiled software that is no longer in text form. Any thoughts about any of this?
i have this screen always making a call with any cm11 i have used in the past, i have to press back and again the keypad and works normal, same when i have to dial a number
tonochito said:
i have this screen always making a call with any cm11 i have used in the past, i have to press back and again the keypad and works normal, same when i have to dial a number
Click to expand...
Click to collapse
But if the prox sensor is always detecting a "covered" state, then it completely disables the screen during a call and we are unable to press "back". Could you post your findings from running Proximity Sensor Finder from CM11 Fire Phone?
jdmillard said:
But if the prox sensor is always detecting a "covered" state, then it completely disables the screen during a call and we are unable to press "back". Could you post your findings from running Proximity Sensor Finder from CM11 Fire Phone?
Click to expand...
Click to collapse
i will give a shot, and post my result
In fact, it would be AWESOME if we could get someone (whose screen does behave perfectly during calls) to post their findings from Proximity Sensor Finder. If their screen works perfectly during calls and this app shows 0.0cm all the time for them too, then we can conclude that this app isn't functioning correctly and we know we need to find our root cause elsewhere.
tonochito said:
i will give a shot, and post my result
Click to expand...
Click to collapse
Available but why it doesn't work right?
tonochito said:
Available but why it doesn't work right?
Click to expand...
Click to collapse
Interesting. Is it stuck on 10.00061 even when you cover the front of your phone with your hand? Or does the number fluctuate?
Which ROM build are you on? (I should say, which publish date?)
jdmillard said:
Interesting. Is it stuck on 10.00061 even when you cover the front of your phone with your hand? Or does the number fluctuate?
Which ROM build are you on? (I should say, which publish date?)
Click to expand...
Click to collapse
yes weird it is stuck no matter what i do, well if i put my finger in the "first camera" of the phoen it goes to zero
tonochito said:
yes weird it is stuck no matter what i do, well if i put my finger in the "first camera" of the phoen it goes to zero
Click to expand...
Click to collapse
That suggests to me that the sensor is "all or none" meaning it doesn't bother detecting intermediate values, rather it just has a threshold that determines a covered or not covered state. That seems normal to me. I need to get mine to do that.
Does your screen behave normally during calls? Specifically, does the screen turn on when you pull the phone away from your face?
jdmillard said:
That suggests to me that the sensor is "all or none" meaning it doesn't bother detecting intermediate values, rather it just has a threshold that determines a covered or not covered state. That seems normal to me. I need to get mine to do that.
Does your screen behave normally during calls? Specifically, does the screen turn on when you pull the phone away from your face?
Click to expand...
Click to collapse
Not always as some users says it sometimes goes black, or i have notice that the notification bar sometimes goes down by itself and the annoying problem of the keypad on calls
I just removed my glass screen protector and now mine behaves just as yours. Which is good that it functions as expected, but also a disappointment about the screen protector. I just looked to request a refund and it appears that they have an excellent return policy so I'm not too worried about it. Now I just need to find a screen protector that doesn't cover the prox sensor. ... sigh.
I'm still interested to see what happens with what you were describing: like how the screen would still behave finicky. I'll keep an eye out for that behavior and I'll let you know if I discover anything about it.
---------- Post added at 01:26 PM ---------- Previous post was at 12:38 PM ----------
tonochito said:
Not always as some users says it sometimes goes black, or i have notice that the notification bar sometimes goes down by itself and the annoying problem of the keypad on calls
Click to expand...
Click to collapse
I forgot to say thanks! You posting your results helped me figure out where I was going wrong. Gracias!
jdmillard said:
I just removed my glass screen protector and now mine behaves just as yours. Which is good that it functions as expected, but also a disappointment about the screen protector. I just looked to request a refund and it appears that they have an excellent return policy so I'm not too worried about it. Now I just need to find a screen protector that doesn't cover the prox sensor. ... sigh.
I'm still interested to see what happens with what you were describing: like how the screen would still behave finicky. I'll keep an eye out for that behavior and I'll let you know if I discover anything about it.
---------- Post added at 01:26 PM ---------- Previous post was at 12:38 PM ----------
I forgot to say thanks! You posting your results helped me figure out where I was going wrong. Gracias!
Click to expand...
Click to collapse
your welcome
I have a glass protector and i noticed over time that i developed a specific technique for answering the phone. I sort of slowly move it close to my ear and then the sound comes on (hear ringing, able to hear caller). If i press the answer button then put it to my ear, most of the time i cant hear the caller but they CAN hear me.
Never even considered it being a sensor issue. I thought it was CM bug triggered by my setup somehow. I flashed this rom and put the glass screen on within a couple of days after receiving it in the mail and since touch-wise the tempered glass works perfectly it was never even a thought. Dont mean to go on but is anyone else dealing with issues like the one i describe? Whats strange is i dont recall having that black screen issue others are experiencing.
KLit75 said:
I have a glass protector and i noticed over time that i developed a specific technique for answering the phone. I sort of slowly move it close to my ear and then the sound comes on (hear ringing, able to hear caller). If i press the answer button then put it to my ear, most of the time i cant hear the caller but they CAN hear me.
Never even considered it being a sensor issue. I thought it was CM bug triggered by my setup somehow. I flashed this rom and put the glass screen on within a couple of days after receiving it in the mail and since touch-wise the tempered glass works perfectly it was never even a thought. Dont mean to go on but is anyone else dealing with issues like the one i describe? Whats strange is i dont recall having that black screen issue others are experiencing.
Click to expand...
Click to collapse
I was lucky enough to have a good return policy on the glass screen protectors I recently got (for two Fire Phones). I'm returning them today and I've already ordered this as a replacement:
http://www.amazon.com/gp/product/B00WXY18WK?psc=1&redirect=true&ref_=od_aui_detailpages00
It has excellent reviews, decent price, very thin, and it is specifically mentioned many times in the reviews that there is a little cutout for the prox sensor (and you can see if if you look carefully at the pictures). I'm hoping that it will solve my black screen woes and protect my screen. There are reports from folks on these forums saying that there is still some strange behavior during calls (such as your example among others). I personally haven't encountered what you're describing, but I'll keep an eye out to see if I can be of any help.
jdmillard said:
Here is a compilation of the comments made about this issue thus far. There seems to be a consensus that screen protectors are not causing this issue.
11th August 2015
14th September 2015
19th September 2015
20th September 2015
20th September 2015
Click to expand...
Click to collapse
Hi. I like to get back about this since I've been quoted on this.
For me, the glass protector screen that I brought from XtremeGuard was the issue my dad had when he tried to make or take calls. After I removed it, it was back to normal.
The persistent issues now, based on what my dad is telling me, is that sometimes after you dial in a number and call a person, you don't hear the ringing tone to know if it went through or not. My dad would freak out when someone on the other line said something since the ringing tone is not working.
tonochito said:
Not always as some users says it sometimes goes black, or i have notice that the notification bar sometimes goes down by itself and the annoying problem of the keypad on calls
Click to expand...
Click to collapse
hi
this is usually related to hardware composer.
cheers
superdragonpt said:
hi
this is usually related to hardware composer.
cheers
Click to expand...
Click to collapse
but why? does it matter with the bootloader, i mean i know the CM11 on the Fire phone still on beta with no NFC working and the camera too at least i am using Snap camera and everything works. But making calls is a bit annoying even i don't use the phone to make a lot of calls just for WhatsApp almost all the time
Hey everyone. I'm enjoying this phone but I do have a few small issues which I'm hoping I can forget about once custom ROMs start to come out
(Come on and release factory images already Razer!!!)
One of them is the proximity sensor which I find incorrectly thinks I've taken my head away from the earpiece during a call and then starts spamming commands with my cheeks.
I have this issue on like every second phone call and it's a bit irritating. Especially when I still haven't received (other than the first one when I first got the phone) any more updates.
The other main gripe is the lack of a pocket sensor/script. Probably related. As in, if you have double tap to wake enabled, good luck putting this in an awkward pocket (inside motorbike jacket pocket) without waking the screen and spamming commands again with your fingers.
Lastly. I wish they had just put the fingerprint sensor somewhere else. I have turned the screen off so many times while watching YouTube it's actually starting to really annoy me
Just wondering, even if you like this phone overall, and I do, if anyone else had these gripes?
I'm having the same issue with a Razer phone I picked up this week. It's a pain.
I've tried using this as advised on another thread and it seems to be working fine, so I'm totally lost.
https://play.google.com/store/apps/details?id=ru.andr7e.sensortest
Handaloo said:
I'm having the same issue with a Razer phone I picked up this week. It's a pain.
I've tried using this as advised on another thread and it seems to be working fine, so I'm totally lost.
https://play.google.com/store/apps/details?id=ru.andr7e.sensortest
Click to expand...
Click to collapse
I'm just glad to hear someone else is noticing this. Does nobody else make phone calls on their phones??
Had the issue with the proximity sensor on a phone call again last night. Realllly annoying.
At least factory images are out now, unfortunately, it took so long, developers etc don't look too bothered about this device - I may be wrong and would be delighted to start seeing some custom stuff out there. So long as they can keep the 120Hz functionality!
Yeah I would definitely be tempted if a good Rom was released. You're probably right about it though, not a HUGE demand for these.
I've had it several times with calls and it will be super annoying if it doesn't get fixed with an update soon. I'll give you a shout if I get anywhere with it outside of this thread.
EDIT:
And yet, I just took two calls this morning back to back with ZERO issues.
anyone any more luck on this?
nk33 said:
anyone any more luck on this?
Click to expand...
Click to collapse
Nope. I still get these issues from time to time.
I even switched to global ROM and they exist there too.
Hi all.
This issue was resolved on my phone with a hard reset (volume up + power button), then a factory reset (in settings -> system -> reset options ). The proximity sensor now works as it is supposed to.
Hope this helps.