Jump to content

Solution to Proximity issue with the new leak kernel


Guest burstlam

Recommended Posts

Guest burstlam

The proximity sensor could not initiate properly with the new kernel. (possibly the value is incorrect )

All u need to do is recabilate the sensor by enter the engineer code with ZTE dialer.

Enter *983*0# in dialer to enable the engineer mode menu.

Press "sensor" and then press "recab" button.

u need to do the calibration for once only.

edit : Indeed, the present source is not as update as the .32 one released on 24th June.

(I am quite sure that it is not the same version that compiled the leak version )

So, pls be noted that this fix might not work on all machine for the reason of incompatible driver with the old source.

Edited by burstlam
Link to comment
Share on other sites

Guest leetron1

The proximity sensor could not initiate properly with the new kernel. (possibly the values is incorrect)

All u need to do is recabilate the sensor by enter the engineer code with ZTE dialer.

Enter *983*0# in dialer to enable the engineer mode menu.

Press "sensor" and then press "recab" button.

u need to do the calibration once only.

Thanks Burstlam...discovered this myself using emode helper...good to find a quick & simple solution

Link to comment
Share on other sites

Guest Phoenix Silver

The proximity sensor could not initiate properly with the new kernel. (possibly the value is incorrect )

All u need to do is recabilate the sensor by enter the engineer code with ZTE dialer.

Enter *983*0# in dialer to enable the engineer mode menu.

Press "sensor" and then press "recab" button.

u need to do the calibration for once only.

edit : Indeed, the present source is not as update as the .32 one released on June.

(I am quite sure that it is not the same version that compiled the leak version )

So, pls be noted that this fix might not work on all machine .

I'm sure it's not this kernel compiled in the leaked kernel

This kernel is more a 32 kernel patched 35

Zte just wanted to shut up all the devs and gave us this piece of crap

Link to comment
Share on other sites

Guest t0mm13b

I'm sure it's not this kernel compiled in the leaked kernel

This kernel is more a 32 kernel patched 35

Zte just wanted to shut up all the devs and gave us this piece of crap

Well said! +1 from me :D

Link to comment
Share on other sites

Guest zenmeyang

Hi, i'm getting "connection problem. invalid MMI-code". maybe I dont have the ZTE dialer, but I'm not really sure which one I got. I flashed the recent GSF22...

Thanks for helping!

EDIT: NEVERMIND! calibrated the proximity using ZTE Emode Helper. Works nice now :)

Edited by zenmeyang
Link to comment
Share on other sites

Guest unrandomsam

mine works fine, but the proximity test has fail next to it

If you put the phone up (as if you were answering a call)

then down again

Does it change to ok ?

(You can see it switch from yes to no) if you move it really fast and squint

Link to comment
Share on other sites

Guest timfimjim

The proximity sensor could not initiate properly with the new kernel. (possibly the value is incorrect )

All u need to do is recabilate the sensor by enter the engineer code with ZTE dialer.

Enter *983*0# in dialer to enable the engineer mode menu.

Press "sensor" and then press "recab" button.

u need to do the calibration for once only.

edit : Indeed, the present source is not as update as the .32 one released on 24th June.

(I am quite sure that it is not the same version that compiled the leak version )

So, pls be noted that this fix might not work on all machine for the reason of incompatible driver with the old source.

+1 worked perfectly!

Link to comment
Share on other sites

Guest DrEzkimo

If you put the phone up (as if you were answering a call)

then down again

Does it change to ok ?

(You can see it switch from yes to no) if you move it really fast and squint

yes it does, thanks :) i can relax!

Link to comment
Share on other sites

Guest RottenFoxBreath

still fails on bright sunlight for me...B21, 22, and now on 23.

It works in normal daylight, and indoors, but not in bright sunlight.

fix seems to be to point the screen at the ground, and then the screen comes back on, or use power to end call.

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.