Hi all,
troubleshooting for a girl with a Bionic; replaced cracked glass/digitizer for her and updated to JB via the OTA update, but her proximity sensor is flaking out.
I've installed a few Prox. Sensor reporting apps to see what values it's putting out: it reads 3cm most of the time, and 100cm when swiping down the notification bar. (100cm is max range, which I assume is a placeholder for a no-report state in the phone, not sure what it has to do with the notification bar.)
Problematic behaviour is that the screen turns off almost instantly after placing a call, and won't come back on except by swiping down (on the blank screen) to pull down the notifications, which temporarily disables the sensor. (it lasts long enough to get ~1 keypress on the keypad, which is *not* a usable workaround even for checking voicemail.)
I'll take the phone apart again and make sure there's nothing in the way of the prox. sensor, as that seems the most likely cause... but any guesses or similar reports from anyone about possible bugs in the firmware update? Any proximity sensor calibration apps for this hardware I'm not seeing in the marketplace, or ROMs that expose that functionality? (I wasn't planning to root the phone, but she won't know the difference if I need to. Was hoping to avoid safestrap to simplify the boot procedure and not interfere with future OTA updates, but warranty is gone already so it's not a big deal if I need to install something new.)
Related
Hey guys, got my Focus S about a month ago and everything is working fine. I have noticed one semi-minor bug and want to figure out if its software/hardware related.
On shorter calls (30 seconds-1 minute), when I move my phone away from my face, the screen wakes back up like normal so I can hit End Call.
However, on longer calls (more than 3-4 minutes), when I move the phone away from my face, the screen stays black, and only wakes up when the other person hangs up, after 4-5 seconds.
Its as if the proximity sensor times out, and forgets that my face is there? This seems like a software issue since it works normal on shorter calls. Anyone have any insight on this? I'm still within thirty days of purchase with ATT so I can swap out my unit by this Sunday.
Thanks!
My Focus does this as well, it's always done it and bugs the hell out of me.
Well that makes me feel a lil better >... but it does seem to be a software issue.
Just a theory but, if the samsung focus S has the diagnosis app you could try recalibrating the proximity sensor. There is a thread that has already adressed calibrating the proximity sensor on the original samsung focus.
The diagnosis menu for the Focus S is different than that of the Focus... theres no way to calibrate the proximity sensor on our S's..
I have noticed this same thing. I thought that sensor was real neat until it didn't work all the time. I am still within the window I am contemplating taking jt back for the titan. Not sure yet though. Just seems to maybe be a better phone...
I'm pretty sure I remember my Focus S doing this once. I'll try and test it today and I'll get back to you.
Absolut` said:
The diagnosis menu for the Focus S is different than that of the Focus... theres no way to calibrate the proximity sensor on our S's..
Click to expand...
Click to collapse
please dont take offence, but i dont quite thats an accurate statement. i know many of the diag menu options arent available in the focus s as they were in the focus, but weeks back i do remember testing this function...although i dont recall in what diag function. if i get time, ill see if i can find that function and report back.
Does anyone here knows how to test the sensor that activate the Intelligent Screen when the Moto X gets out of the pocket?
I've had some issues when I remove it to see these notifications or just check the time. The "flip" sensor works flawlessly, but the sensor that activate the screen after remove it from pocket is not working 90% of the time.
I think that is the lighting sensor that activate this move, but I'm not sure yet.
I had an Sony that have a menu that you can check all sensors to see if it's working. Maybe Motorola have some of that to.
Can anyone help me clear this issue? I'm not in the mood to leave for maintenance, since it's so new that I'm concern about the technical specialization of the team that may check it.
It's the forth day of usage and these past 3 I've had no issues with it. All other movements works fine tough.
Thanks all.
Mine does it mostly from accelerometer I think because I can have it sit on the desk but if I try to active the proximity sensor, it doesn't react.
I think there may be an issue with some phones with that 'remove from pocket' sensor. My first MotoMaker X would routinely be on (and in Facebook, Twitter, etc) when I pulled it out of my pocket. The newer MotoMaker X I have however, I never have that issue with.
Wondering if someone (hopefully more than one) can check something to see if this is an issue with my particular phone or something related to the software/hardware. It seems that when a call is placed or received, the proximity sensor goes to "far" and won't reset until it is uncovered and then re-covered. I have searched through the Verizon HTC One forums and have not found anything related to this issue.
If the proximity sensor is covered, and I make a call (via bluetooth headset (double click for last dialed)) or receive a call, the proximity sensor goes to the uncovered state. It then stays in that state until I uncover and then re-cover it. How I checked this was using Elixir 2 and checking the sensor data. I also set up variables in Tasker and Automagic.
So, this was my test procedure:
I start the sensor data in Elixir 2 for the proximity sensor. I cover the sensor with my finger (it now shows "near"). I use my bluetooth headset to place a call. The screen comes on with the current call. I back out of the current screen (the phone screen) and get back to Elixir 2 sensor data. The sensor now shows "far". From that point on, until I uncover the proximity sensor and then cover it, it shows far. I set up variables in Tasker and Automagic that show the same results.
I am running the stock debloated ROM. Rooted and S-Off.
EDITED:
So, this is the latest for my issue. I went from stock ROM to ViperOne 5.8.0. I am still getting the same results. So, I think I have eliminated the software side of it. Would that be right? So, it could be the firmware or the hardware? I'm still wondering if it's my phone only or if it is an issue with the HTC One in general. Is there anyone that can check this? Or give me another route to take?
I'm on ViperOne 5.8.0
Android 4.4.2
Senses 5.5
Any other info you might need, please just ask.
Some thing like that happened to me and i posted a thread and no answers.
My problem is that when the phone is in my pocket only one speaker is ringing(the lower one) and when on the desk face up both of the speakers are ringing.I noticed this affects only the call option(if i get a sms/notication and it's in my pocket/desk both of the speakers work).i've made all off the tests i can find am the problem seems to be from software.When i cover with my finger the sensor and some ones call s me only the bootom speker is ringing,when removing my finger from the sensor and receving cal SURPRISE both of the are ringing.
I've change the software ARHD 53 with ELEMENTALX Kernel.
Cid TMOB-101
alex.foto said:
Some thing like that happened to me and i posted a thread and no answers.
My problem is that when the phone is in my pocket only one speaker is ringing(the lower one) and when on the desk face up both of the speakers are ringing.I noticed this affects only the call option(if i get a sms/notication and it's in my pocket/desk both of the speakers work).i've made all off the tests i can find am the problem seems to be from software.When i cover with my finger the sensor and some ones call s me only the bootom speker is ringing,when removing my finger from the sensor and receving cal SURPRISE both of the are ringing.
I've change the software ARHD 53 with ELEMENTALX Kernel.
Cid TMOB-101
Click to expand...
Click to collapse
Well, seems to be the same here. I have this posted under the Verizon HTC One > One Q&A, Help & Troubleshooting as well as here and at the Android forums. It seems that either no one else is having this issue, no on cares or no one can run this test with free programs. I dunno. The problems I have is that I use by bluetooth headset most of the time. I am a blue collar worker and try not to pull my phone out of my pocket when my hands get filthy. But, when I take or make a call using the headset, the display kicks on and then stays on because I can't use the proximity sensor to turn the screen back off. Guess I'll have to try other routes. This sucks. LOL
I haven't heard of the other issue you are referring to. I can tell you that I have not had that issue with my One. Doesn't mean that it's not a problem. Have you checked the Sounds settings for pocket mode and quiet ring on pickup? If so, I think I would try to either get with Verizon about it or maybe even HTC. It definitely sounds like it could be a phone issue. But I'm kind of new to all of this.
Same problem here, when i'm in a call the screen go on, very annoying.
Now i'm trying this app "rezound prox sensor calibrator"
I've tried every possible solution including Pocked mode& Quiet ring.I still think this is a soft bug till further notice.
Lets hope we get a answer soon.Btw same here with the headset,I'm using a hands free and when i answer/call some one i must manually turn off the screen or its turn of by itself after 1-2 min i think.
psicobelico said:
Same problem here, when i'm in a call the screen go on, very annoying.
Now i'm trying this app "rezound prox sensor calibrator"
Click to expand...
Click to collapse
It's not a calibration issue. When the phone rings or you make a call via a headset and the proximity sensor is covered (ie. in your pocket or screen face down), the display kicks on and the prox sensor seems to default to "far" or "uncovered" (whatever term you like). It will remain at that value until you ACTUALLY uncover the sensor and then cover it back again.
alex.foto said:
I've tried every possible solution including Pocked mode& Quiet ring.I still think this is a soft bug till further notice.
Lets hope we get a answer soon.Btw same here with the headset,I'm using a hands free and when i answer/call some one i must manually turn off the screen or its turn of by itself after 1-2 min i think.
Click to expand...
Click to collapse
The problem I have is that while the display is ON and sitting in my pocket, I have a chance of butt dialing someone or starting programs that drain the battery in addition to the dsplay being on. Not to mention, with the display on in my pocket, the heat builds up in the phone. I guess I have a $700 butt warmer? LOL
so in short this problem has plagued the phone since day one and i suspected a HW issue since nothing fixed it. for those who dont know whats im talking about, you are lucky. the issue is basically that the proximity sensor is missed up so the screen will light up when you are in a call or listening to Whatsapp/Telegram voice messages.
The Solution:
The problem, turned out, was caused by the factory screen protector that came already applied to the phone. i removed it after it was damaged and also removed the case (Spigen Rugged Armor Case), cleaned the phone and VIOLA its working perfectly fine now...
i hope it works for everyone else.
So, what you are saying is:
Since when this phone got launched in May 2019, not a single user facing the proximity sensor issue had the ingenious idea to remove their factory applied screen protector and you are the first one to come up with this "fix"?
I am really sorry to be this discouraging but: This ain't it chief.
Good that it fixed your perception of the issue though
Comrade, the issue is far graver than that. OnePlus 7Pro does not have a proximity sensor per se. It uses software (an ai I think) to "guess" whether to turn on the screen or not which is why listening to voice notes gets crazy...
amirage said:
Comrade, the issue is far graver than that. OnePlus 7Pro does not have a proximity sensor per se. It uses software (an ai I think) to "guess" whether to turn on the screen or not which is why listening to voice notes gets crazy...
Click to expand...
Click to collapse
Even though it does have an infrared sensor under the screen (that has been proven), i agree with you that it seems to be using something like that.. Curiously, the proximity sensor once fired when i flicked off my lights in my room.. This indeed leads me to believe there is more going on than just a simple infrared proximity sensor..
But yeah, i don't think removing the stock screen protector "fixes" the thing.. It may improve things but i doubt it's a fix.. As i said, this phone has been out for a while and people would have noticed if removing the screen protector fixes the proximity sensor for good..So yeah, cheers mate.
I took the screen protector off before I turned the phone on for the first time. I still get the screen lighting up while I'm on a call, often muting it with my cheek.
I must be lucky but at the moment I have no such issue with my new OP7P (MFD: 2019/05). RR Rom. Still have the screen protector on it. What's the MFD of your unit ?
i have problem with my oneplus since i rooted this phone
after root i have installed pixel expereince rom
when i called i found proximity sensor not working
now almost 6 months no fixed i'm stock oos
please help me there is no guard on my phone also no cover
The simplest solution for me has been to use a Bluetooth headset. I rarely use it without it.
I have a strange problem with GW5 sensors: My watch is secured with a PIN and Samsung pay is active. After I register body composition, hearth rate sensor blocks and the security lock doesn't work anymore even if I undress the watch and I put it back on. It stays unlocked. The only way to reset the situation is take a SPO2 measurememt or restart the watch.
Besides, occasionally, the watch locks without any good reason and if I enter the PIN it unlocks only if the screen stays on. When it turns off it locks again.
Somebody else notes this behavior?
I have the 2nd problem you have where the phone locks without any good reason.
Thanks for the answer RigoF. I suspect that the two malfunction are somehow related. Would you mind to make this test:
With the watch working normally take a body composition measurement. Once you get the results, go directly back to the home screen. Undress the watch and check if it locks. If it doesn't work, put it on again and go to the SPO2 widget. Take a measurement of the SPO2 and once you get the results the.watch should start working normally again.
I also noticed that doing this procedure improves the accuracy of the sensors. The other way to solve the issue is restart the watch, but in this case the sensors are not always precise.
Yes I was able to duplicate the behavior you described in post #3. It won't lock after the body composition measurement and returns to normal after the SPO2 measurement.
Thanks a lot. I already spotted this issue in two 5 pro LTE that I had the possibility to use, both brand new and with different CSCs. The BIG message to people that use Sansung pay is: If your watch locks with no good reasons when at your wrist, there is the possibility that everytime you take a body composition measurement your security PIN could malfunction leaving your card accessible even if you undress the watch.
UPDATE. I sent the watch to the Samsung service support. They found that the problem was due to the sensor working intermittently. They changed both the main board and the entire back cover. Now the watch works like a charm.
UPDATE. I sent the watch to the Samsung service support. They found that the problem was due to the sensor working intermittently. They changed both the main board and the entire back cover. Now the watch works like a charm.