Hey there,
I managed to drop my phone like perfectly flat on concrete and that made it crack. I Bought a glass replacement as the digitizer was still working and exchanged it.
Now whenever i make a call the screen goes OFF and since the proximity sensor is not working won't come back on until the call is disconnected (The sensor works intermintently, but less then more)
Things i did:
- Used Sensor Kinetics to disable the proximity sensor... no change... screen goes off and wont come back on until the call is disconnected
- Installed KeepScreen - no change... screen goes off and wont come back on until the call is disconnected
- Installed Screen On - no change... screen goes off and wont come back on until the call is disconnected
- Looked for settings in the dialer to prevent screen from going off but found nothing..
I`m to keen to open the phone again since i have to open up the clamps on each side and they might brake.
I need a way to keep the freaggin screen from turning off during a call.. that is all... Any ideas?
Unfortunately, I don't think there's a way via software. I had the same issue when I replaced my digitizer. It turns out there's a small grommet that fits where the proximity sensor is and creates a barrier between the transmitter and receiver parts. If it is missing or displaced, the signal gets bounced back inside the screen and it thinks there is always something right in front of the screen. I was able to cut a small piece of rubber into the basic size and shape as the grommet and insert it, which worked and now the proximity sensor works fine.
Exact same probleam
I do have the same problem on my Moto X 1055, did a google fro few days and gave up, recently i came across xposed Framework from XDA (Thanks to XDA you made my dream come true) , and i was browsing through the modules where i came accross Disable Proximity. I installed it and restarted my device and it works.
Pisces5 said:
I do have the same problem on my Moto X 1055, did a google fro few days and gave up, recently i came across xposed Framework from XDA (Thanks to XDA you made my dream come true) , and i was browsing through the modules where i came accross Disable Proximity. I installed it and restarted my device and it works.
Click to expand...
Click to collapse
Hello,
Can you link me to the framework please? I wanna give it a try
Yes I agree, my sensor doesn't work and disable proximity works like a charm for me to
---------- Post added at 10:10 AM ---------- Previous post was at 10:06 AM ----------
http://repo.xposed.info/module/com.mrchandler.disableprox
Do you have a picture of what the gromet should look like? I replaced my screen/digitizer and now I'm having the same issue. I never saw it so I don't know what I'm looking for or what I need to make! Thanks!
Thanks man! you have just helped a poor friend of mine :good: I could revive my old motox so he will have a phone now!
Related
Hello i found out my N1 Proximity sensor have issue wen a install 2.3.3 my screen shutoff when i do call and stuck blank screen i have to remove the battery and put the back.
i download Elixir App and doing some test and Sensor only Say "NEAR" I put my hand on the screen still say Near...
/etc/permissions
android.hardware.sensor.proximity.xml
android.hardware.sensor.light.xml
/system/lib
libssensorservice.so
Factory Code Nexus One
#*#0588#*#* Proximity sensor test (no work in my N1)
can i restart the sensor?
can i disable Proximity in DIAL ?
do i need to take tHTC Support N1?
where is the CM3602 on N1?
can i fix my self?
and I have the same problem but no answer :-(
___
http://forum.xda-developers.com/showthread.php?t=707234&highlight=nexus+proximity
Hi,
Have the same issue, too !
hmm, looks like a android 2.3 issue on that one....
The same here. Is there any way to do a downgrade to 2.2? The phone is unusable, I'll have to go back to my old Nokia!!
Also, at the same time, when I plug the earphones on the Nexus, it doesn't detect them and continues playing through internal speaker!! And I suspect that the light sensor doesn't work.
Hasta luego.
Nexus one proximity sensor problem
Hi guys i had the same problem with my phone
and I manage to fix it
I open the phone and check where the proximity sensor was
and clean it with the a spray duster they sell in computer store
I clean the entire phone
put i back together and it was fix
thanks me if it works for you like that
You are lucky,, just opened my phone and cleaned the proximity sensor and light sensor with specialized electronics solutions i borrowed from work and nothing happened,,dont know what to do about it
RE: how to disable proximity sensor
hey there, this is my second post, THIS PLACE IS AWESOME!!! I was able to disable my nexus one proximity sensor using the hex edit method (after granting the app root access) and now a brick to be is no more. thank you to the poster who made the original post and the one who mentioned the way to give hexedit root access. my sensor definition was exactly where he said it would be. the name of course was cm3602 (lowercase, looking for uppercase found nothing) I was able to change hex position 0000323d from 32 to 00 , and poof, no more black screen after dialing or when receiving a call. a temporary solution I was using was to use a bluetooth headset.
Thank you all.
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
I broke my screen last week , it fell and was damaged, and the camera stopped working too. I fixed the screen, but the camera is still offline, tried to change the rom, but no changes., i am getting the "Error, camera not available". When i click on camera icon, it shows a black screen after some delay and then right away an error message pops up with "Error! Camera not available". When i load this from any application, such as snapchat or instagram, it crashes the application. Has anyone dealt with such issue before? Give me some hope, what could be wrong.
The camera was not working even before i replaced the screen. (The screen repair was good, i made sure nothing was touched that should'nt be touched.
The phone's proximity sensor seems to be a bit off too, the phone also vibrates ( like it received a text message) randomly.
Unrelated issue: the screen i install has a round ring that appears if i press the screen to hard at a certain spot. it's not too annoying but it is there.
Broken flat cable, broken camera. Physical damage.
Sent from my C6903 using XDA Free mobile app
electrash said:
Broken flat cable, broken camera. Physical damage.
Sent from my C6903 using XDA Free mobile app
Click to expand...
Click to collapse
Ah! what do you think , can it be saved DIY?
marksee said:
Ah! what do you think , can it be saved DIY?
Click to expand...
Click to collapse
Well i didnt opet Z1 before, so i dont know if you can only replace flat cable (if that is problem) or you must replace whole camera module.
Best bet is to give to service center, probably they will put new module on it, and its best in my opinion.
electrash said:
Well i didnt opet Z1 before, so i dont know if you can only replace flat cable (if that is problem) or you must replace whole camera module.
Best bet is to give to service center, probably they will put new module on it, and its best in my opinion.
Click to expand...
Click to collapse
Most likely put a new module in there as the modules are machine made are probably solid.
Status Update
So i opened the phone again, and seems like i was able to fix the screen issue.
Issue of camera remains. I removed the camera from the socket, and disconnected its wire from the motherboard. When i accessed camera without wire connected, it straigth away went to "ERROR. Camera not available. Earlier, when wire was connected, it took about 5 seconds and then outputted the Error. Flash/ Front camera are still not accessible or usable even when front camera was plugged out.
Weird vibrations are felt randomly, i am still trying to pinpoint what causes them, but they have decreased significantly.
My question now is, will replacing the camera fix the camera issue? Or is there a deeper wire/motherboard issue here? What would be your next step to investigate it further. Also, can this be not a broken screen issue but a camera issue covered in warrantly?
Additional info: i have tried reinstalling ROM, flashed T-mobile's original ftf file, cleared camera cache, files etc. used 3rd party apps but no success.
#####SOLVED: SCREEN HAS WEIRD FLOATIES WHEN WE TOUCH AREA NEAR THEM
This is caused because of dust between the digitizer and the back of the phone. To fix this, simply open the phone up and remove any dust particles between the digitizer and the phone. Screen will work perfectly after that.
JustPlayingHard said:
Most likely put a new module in there as the modules are machine made are probably solid.
Click to expand...
Click to collapse
When you say module? you mean the camera with the connection wire ? or something more than that?
marksee said:
When you say module? you mean the camera with the connection wire ? or something more than that?
Click to expand...
Click to collapse
The camera with connection wire
Update: so bluetooth call recieving does not work, people call me, and if i pick it up, voice does not work over bluetooth anymore. music skips randomly too. My question was that will camera module replacement fix this? or is this a deeper issue, such as cable that connects the camera module? what will i need to replace .
I don't think that anybody here could answer your questions. You should take your phone tot a service center.
Sent from my C6903 using XDA Premium 4 mobile app
SOLVED it.
Fixed it! The issue was that the back camera module was malfunctioning. Because of that, phone chip that controls camera (also controls vibrations) was not functioning properly. I bought a used camera module from ebay, plugged it in and phone works perfectly now
Feel free to pm me if anyone else has questions about this, or need help dismantling phone. Xperia Z1s I AM BACK!!!
I just bought a new m7 yesterday and my experience is horrible. It was all ok but after the lollipop upgrade everything is messed up.
Proximity sensor is totally fine because I have checked it with several apps...
problem one: the screen doesn't turn on after I remove tho phone from my ear while calling, so I can't hang up unless the other person hangs up.
Problem 2: Same thing with Lock Screen. It doesn't turn on..
Problem 3: my phone's touch is not working at a certain horizontal line along the screen, When I touch there, two touches are senses just right and left....
If anyone has encountered these problems, please give me a solution or find me a better solution.
ikyorince said:
I just bought a new m7 yesterday and my experience is horrible. It was all ok but after the lollipop upgrade everything is messed up.
Proximity sensor is totally fine because I have checked it with several apps...
problem one: the screen doesn't turn on after I remove tho phone from my ear while calling, so I can't hang up unless the other person hangs up.
Problem 2: Same thing with Lock Screen. It doesn't turn on..
Problem 3: my phone's touch is not working at a certain horizontal line along the screen, When I touch there, two touches are senses just right and left....
If anyone has encountered these problems, please give me a solution or find me a better solution.
Click to expand...
Click to collapse
looks like you are having hardware problem with the digitizer and the proximity sensor, you might want to send back this phone a get another one.
same issue 100% positive its a lollipop bug after a reset it gets fixed but if i update my apps through playstore it comes back
likhon02 said:
same issue 100% positive its a lollipop bug after a reset it gets fixed but if i update my apps through playstore it comes back
Click to expand...
Click to collapse
If the problem returns after updating your apps through the playstore then it's related to one of your app, not lollipop itself. One of your apps must be interfering with the screen or the proximity sensor.
Sent from my HTC One using XDA Labs
alray said:
If the problem returns after updating your apps through the playstore then it's related to one of your app, not lollipop itself. One of your apps must be interfering with the screen or the proximity sensor.
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
anyways found the solution
http://forum.xda-developers.com/htc-one/help/lockscreen-issue-wake-lag-unlock-black-t3450726
Is anyone else having an issue with the always on display? Not a big deal but occasionally the AOD goes off and the tap to wake function doesn't work. Unlocking/locking the phone fixes it but it reoccurs again randomly through the day.
andrewd71 said:
Is anyone else having an issue with the always on display? Not a big deal but occasionally the AOD goes off and the tap to wake function doesn't work. Unlocking/locking the phone fixes it but it reoccurs again randomly through the day.
Click to expand...
Click to collapse
I was having the same issue when I had the edge notification app installed that makes the screen light up around the camera when you get a notification.
Uninstalled and no issues since
Tap to wake not working for me
Not sure if this is connected but in addition to the always on display/tap to wake issue when I'm in a phone call the screen will stay off even when I move the phone from my ear to hang up, see the keypad etc. Again I have to use the power button to wake the screen. A problem with the proximity sensor perhaps?
andrewd71 said:
Not sure if this is connected but in addition to the always on display/tap to wake issue when I'm in a phone call the screen will stay off even when I move the phone from my ear to hang up, see the keypad etc. Again I have to use the power button to wake the screen. A problem with the proximity sensor perhaps?
Click to expand...
Click to collapse
Do you have any notification or edge lighting apps installed?
Mdizzle1 said:
Do you have any notification or edge lighting apps installed?
Click to expand...
Click to collapse
No, I've not installed any apps like that.
I am having both the issue with always on display and the screen staying off during a call even when it's not up to my face. I don't have any edge display app installed. They happened right out of the box. Glad it's not just me.
czm said:
I am having both the issue with always on display and the screen staying off during a call even when it's not up to my face. I don't have any edge display app installed. They happened right out of the box. Glad it's not just me.
Click to expand...
Click to collapse
This is an odd one - are you using a case? I just had a case through the post this morning and now using the phone with the case the issues have stopped! I'll keep checking through the day but as of now all is good.
andrewd71 said:
This is an odd one - are you using a case? I just had a case through the post this morning and now using the phone with the case the issues have stopped! I'll keep checking through the day but as of now all is good.
Click to expand...
Click to collapse
Not using a case. It's sporadic. Tap to wake works fine for a while and then stops. The issue during calls is constant. Not major issues just niggles.
Not noticed any bugs with ambient display, but it has used 20 percent battery in 21hrs.
Seems a bit high to me, have just turned it off, not worth a 5th of my battery.
czm said:
I am having both the issue with always on display and the screen staying off during a call even when it's not up to my face. I don't have any edge display app installed. They happened right out of the box. Glad it's not just me.
Click to expand...
Click to collapse
Yeah I'm having both issues happen RANDOMLY as well. I'm HOPING Google will put out a fix for these two issues very soon.
Tried working with Google's Tech Support Team via chat earlier on the AOD issue. Tried a few things like clearing the cache of the launcher & restarting in Safe Mode then back to Normal Mode, and it seems to be doing it less but then it just did it again for a short time like an hour ago.
Using a case, no edge stuff, and also using Nova Launcher (though it happened in Pixel Launcher as well).
If anyone finds a fix for this, I would appreciate it too!
RockStar2005 said:
Yeah I'm having both issues happen RANDOMLY as well. I'm HOPING Google will put out a fix for these two issues very soon.
Tried working with Google's Tech Support Team via chat earlier on the AOD issue. Tried a few things like clearing the cache of the launcher & restarting in Safe Mode then back to Normal Mode, and it seems to be doing it less but then it just did it again for a short time like an hour ago.
Using a case, no edge stuff, and also using Nova Launcher (though it happened in Pixel Launcher as well).
If anyone finds a fix for this, I would appreciate it too!
Click to expand...
Click to collapse
Mine is fine for a while them randomly the tap-to-wake won't respond. I had also hoped that the OTA would have addressed, but maybe it is affecting far fewer users than other bugs.
czm said:
Mine is fine for a while them randomly the tap-to-wake won't respond. I had also hoped that the OTA would have addressed, but maybe it is affecting far fewer users than other bugs.
Click to expand...
Click to collapse
Yeah. Seems like more and more people are noticing and like me reporting these various issues to Google. So hopefully the next batch will include fixes for all this stuff.
I have same two problem with AOD, touch to wake up and screen off/on when calling.
DOMIN_ said:
I have same two problem with AOD, touch to wake up and screen off/on when calling.
Click to expand...
Click to collapse
I recommend you guys report these issues to Google so to increase the odds of them coming up with an OTA sooner than later. You can call them or chat with them via this link (as I did). Just scroll down to the bottom and choose your contact preference.
RockStar2005 said:
I recommend you guys report these issues to Google so to increase the odds of them coming up with an OTA sooner than later. You can call them or chat with them via this link (as I did). Just scroll down to the bottom and choose your contact preference.
Click to expand...
Click to collapse
On the pixel support forum they also recommend you report it via settings>about phone>send feedback about device. I think this way it also easily picks up the log files.
I believe the answer to all of your questions lies in a faulty proximity sensor. I was driving myself nuts with all of these issues exactly, and no app was the culprit because I factory reset and still had the issue. I'm going to post a link to a Reddit thread that I found that confirmed my suspicions. on Wednesday of this week I went back to Verizon and traded the phone in and now I have received a phone that works 100% as expected.
Reddit thread.
Good luck all, hope this helps.
czm said:
On the pixel support forum they also recommend you report it via settings>about phone>send feedback about device. I think this way it also easily picks up the log files.
Click to expand...
Click to collapse
Yeah I got an e-mail from the support guy to do that as well after he'd ask that I send a bug report. Just did it regarding AOD not staying on all the time and also.............I noticed that Hold for Me doesn't ALWAYS come up when calling businesses. Two examples include T-Mobile Customer Service & a local major hospital in Chicago. In most cases though, it does. Just an FYI. Not sure if this is something that they will fix, but I think it should come up all the time, or AT LEAST when you're calling an established business of ANY kind.
---------- Post added at 05:30 PM ---------- Previous post was at 05:26 PM ----------
Morpherios said:
I believe the answer to all of your questions lies in a faulty proximity sensor. I was driving myself nuts with all of these issues exactly, and no app was the culprit because I factory reset and still had the issue. I'm going to post a link to a Reddit thread that I found that confirmed my suspicions. on Wednesday of this week I went back to Verizon and traded the phone in and now I have received a phone that works 100% as expected.
Reddit thread.
Good luck all, hope this helps.
Click to expand...
Click to collapse
Very interesting!
I REALLY don't want to send mine back because I've spent so much time setting it up already (and my sister's too lol). I did some changes in the settings so I'll just cross my fingers and hope it works right.
Is there a way to recalibrate the proximity sensor?
RockStar2005 said:
Yeah I got an e-mail from the support guy to do that as well after he'd ask that I send a bug report. Just did it regarding AOD not staying on all the time and also.............I noticed that Hold for Me doesn't ALWAYS come up when calling businesses. Two examples include T-Mobile Customer Service & a local major hospital in Chicago. In most cases though, it does. Just an FYI. Not sure if this is something that they will fix, but I think it should come up all the time, or AT LEAST when you're calling an established business of ANY kind.
---------- Post added at 05:30 PM ---------- Previous post was at 05:26 PM ----------
Very interesting!
I REALLY don't want to send mine back because I've spent so much time setting it up already (and my sister's too lol). I did some changes in the settings so I'll just cross my fingers and hope it works right.
Is there a way to recalibrate the proximity sensor?
Click to expand...
Click to collapse
I don't believe it's a calibration issue. The way mine worked (or didn't as the case may be) was sporadic and seemed to almost be as if the sensor or module was loose? Inside the housing. Quite literally, jostling it around would make it work sometimes. Furthermore, if you download the app in that reddit thread, the proximity sensor tester Link Here, you can sort of gauge yourself if it's actually occurring. With mine, sometimes it would work by swiping my hand over the sensor, the color would change. Other times, the color stayed the same, and as the video showed ,I could put pressure on where the sensor was and change the color. But if it wasn't working, jostling the phone around would sometimes make it work and the color would change.
Additionally in the advanced test in that app, it is supposed to tell you how far away from the sensor an object is. On my (nonworking) phone, that number for distance would be pegged at 0 regardless of how far away my hand was. However if I put pressure on the sensor, it would jump to like 5 cm.
See if your phone is doing these things. If so, I would recommend you get it replaced, as it likely will not work properly otherwise. Verizon deemed this a hardware issue when I swapped phones. Also note that I factory reset twice, and one of those times I imported literally nothing when setting it up. So it wasn't a settings or app issue. I do believe there's a rash of faulty proximity sensors going on here.
Morpherios said:
I don't believe it's a calibration issue. The way mine worked (or didn't as the case may be) was sporadic and seemed to almost be as if the sensor or module was loose? Inside the housing. Quite literally, jostling it around would make it work sometimes. Furthermore, if you download the app in that reddit thread, the proximity sensor tester Link Here, you can sort of gauge yourself if it's actually occurring. With mine, sometimes it would work by swiping my hand over the sensor, the color would change. Other times, the color stayed the same, and as the video showed ,I could put pressure on where the sensor was and change the color. But if it wasn't working, jostling the phone around would sometimes make it work and the color would change.
Additionally in the advanced test in that app, it is supposed to tell you how far away from the sensor an object is. On my (nonworking) phone, that number for distance would be pegged at 0 regardless of how far away my hand was. However if I put pressure on the sensor, it would jump to like 5 cm.
See if your phone is doing these things. If so, I would recommend you get it replaced, as it likely will not work properly otherwise. Verizon deemed this a hardware issue when I swapped phones. Also note that I factory reset twice, and one of those times I imported literally nothing when setting it up. So it wasn't a settings or app issue. I do believe there's a rash of faulty proximity sensors going on here.
Click to expand...
Click to collapse
Hey Morpherios,
Ok.............downloaded that app and tried it out several times. It passed some of the time, but then I'd try it again a few minutes later and it would fail on both tests. Ughh!!
You think even though it passed a few times I still need to replace it?