10 replies to this topic

[Letoo]

Hey fellow bladers, yesterday I got my phone back from a warranty repair ( the screen ceased to function so I got it replaced), immediately TPTed to GEN2 and installed CM7 N208, after few hours of use, restocking apps and stuff I realized that the autobrigtness and proximity during calls dont work; I assumed its because of the ROM and installed GSF B27 with ZTE emode helper to perhaps recalibrate the sensors. Emode displayed that both sensor fail and trying to recalibrate them caused  forced closes or a blackscreen crash; then I TPTed back to stock partition/boot and ziped the stock operators rom to  notice that both sensors fail in it too, zte emode helper that's a part of that rom says that light and promixity sensor fail, when I click to recalibrate them it says "recalibration ok" but nothing really happens, both sensor dont work and emode still claim they fail... Did anyone else faced a problem like mine? Seems to me that it's a hardware issue and I should get it fixed again, but wanted to ask first in case im doing something wrong. Thoughts?

[igors_s]

I'm having same proximity/light sensor issue.

All tools report them as 'fail', recalibration causes force close.

tried following roms,

cyanogenmod
fish n chips
MMHMP RS2
sweedish snow RS2/3
original orange rom, dec11 (recalibration works, but makes no difference, sensors report 'fail')

tried TPT flash aswell.

could anyone advice?

[Letoo]

I couldn't find a solution to this so I sent it to a warranty repair again... and what's funny it came with a note saying the proximity is working fine... and it was working fine indeed. No idea how it got fixed without anyone fixing it, but fine by me :>

[rider89]

I had the same problem (every ROM, every calibration-proximity and auto brightness sensors failed) but earlier have disassembled my Blade.
I decided to disassemble it once again before sending it to repair. And what showed up? The foam seal around the sensors was crumpled-when I was previously assembling it I was not enough cautious and and put the foam seal ON TOP of the sensors and not AROUND them..
So it covered them and stopped them from working well :-)

[igors_s]

Hokay, mine is not a software issue....

Opened the blade up (luckily managed to save the white foil cover on one of the screws) and found the proximity sensor cable severed by the headset jack.
it's cut clean. the edge of the headset jack rubs against it, and looks like if you squeeze it in the area, it will cut the ribbon cable.

rider89, on 06 February 2012 - 09:53 PM, said:

I had the same problem (every ROM, every calibration-proximity and auto brightness sensors failed) but earlier have disassembled my Blade.
I decided to disassemble it once again before sending it to repair. And what showed up? The foam seal around the sensors was crumpled-when I was previously assembling it I was not enough cautious and and put the foam seal ON TOP of the sensors and not AROUND them..
So it covered them and stopped them from working well :-)

[WAWA72]

Letoo you need another Proximtiy Sensor.

Igor i send  today Ort tommorow a New one. If you want i ca send you another too.

[Conal]

Sorry for thread hijack.
I dropped my blade awhile ago and since then both light and proximity sensor have failed or crashed during calibration.
Are they likely to be damaged or could it just be a connection problem? I might have a look just to be sure.

[WAWA72]

You need a New proximity Sensor. Ask me

[WAWA72]

igor_s proximty Sensor arrived hin today. He changed it and it works.

[WAWA72]

igor_s proximty Sensor arrived hin today. He changed it and it works.

[igors_s]

WAWA72, on 16 February 2012 - 01:06 PM, said:

igor_s proximty Sensor arrived hin today. He changed it and it works.

Yeh, received it today. I have opened my phone several times already so replacing it was a breeze. It's so nice to be able to press the phone to the ear.