Possible fix for proximity sensor bug.

[Guest tilal6991]

I've heard on the forum the some people are having issues with the proximity sensor of the OMC. Well I just want to inform everyone of a possible fix that worked for blade owners running the Monte Carlo rom. YOU NEED TO BE ROOTED.

Edit build.prop by adding the following two lines at the bottom.

ro.lge.proximity.delay=25

mot.proximity.delay=25

Reboot and hopefully it should be fixed. I never had rge problem so I haven't tested this but it has worked for blade owners with the same problem.

[Guest gitf@ce]

That didn't work for me.

[Guest tilal6991]

That didn't work for me.

ok. Could you please tell me what is issue is exactly and also could you install the app elixir and under sensors see if it detects your proximity sensor properly.

[Guest tillaz]

same here dint work would be good if we could find a way to disable proximity until a fix.

thanks anyway .

Edited August 30, 2011 by tillaz

[Guest tilal6991]

same here dint work would be good if we could find a way to disable proximity until a fix.

thanks anyway .

ok this is a long procedure but try this. This will tell you for sure whether it is a hardware issue. Download cm7 and flash it but don't wipe data. Phone should be working. Try calling someone and see if the proximity sensor works.

[Guest gitf@ce]

I'll do it but surely I need version .5?, and it's no longer available for d/l.

Not working:

WiFi

Bluetooth

Youtube videos - fixed in version 0.6

RIL - fixed in version 0.5 and version 0.6

Mobile Data - fixed in version 0.5 and version 0.6

Camera - fixed in version 0.5

Sensors - fixed in version 0.5

FM Radio - fixed in version 0.5

[Guest gitf@ce]

Look's like it's hardware. The Elixr program is constantly going from 4.0cm to Far even though the phone is laying on it's back with nothing anywhere near it. If I place my finger over the sensor it does not register.

Sod it! I really did not want anymore dealings with Orange.

Looks like we need someone to provide the stock rom with the original recovery partition (as Pauls one is missing it), so that we can return our phones.

[Guest tilal6991]

Look's like it's hardware. The Elixr program is constantly going from 4.0cm to Far even though the phone is laying on it's back with nothing anywhere near it. If I place my finger over the sensor it does not register.

Sod it! I really did not want anymore dealings with Orange.

Looks like we need someone to provide the stock rom with the original recovery partition (as Pauls one is missing it), so that we can return our phones.

I have the recovery backed up but however unfortunately I don't have access to a computer until Saturday - ill post it then.

[Guest Sebastian404]

I have the recovery backed up but however unfortunately I don't have access to a computer until Saturday - ill post it then.

http://blog.podtwo.com/android/rom/ZTE%20Skate%20Stock%20ROMs.html

[Guest tilal6991]

http://blog.podtwo.c...ock%20ROMs.html

thanks for that. Saves me having to upload it. It's ok anyway - the proximity sensor bug has been fixed. :)

[Guest Sebastian404]

BTW, what is the issue your all having EXACTLY.. I've made a bunch of calls with mine without any problems, including going through an IVR and I've not noticed a missing on screen keyboard...

[Guest tilal6991]

BTW, what is the issue your all having EXACTLY.. I've made a bunch of calls with mine without any problems, including going through an IVR and I've not noticed a missing on screen keyboard...

I don't have it either. The issue was that their proximity sensor wasn't calibrated properly so the screen wouldn't light up. It's been fixed on another thread.

[Guest Professor Frink]

I had it but typing in the code suggested elsewhere seems to have sorted the problem. :)

[Guest metal.mickey]

Been through a lot of the proximity threads but still having problems.

im running atomic blue 1.5

and have tried editing the build.prop file but no joy adding the proximity values.

have also tried to flash the proxcal.zip file from another thread/forum, but still no joy.

is there an update for the atomic blue rom that can sort this issue.

Edited December 4, 2011 by metal.mickey

[Guest gitf@ce]

Been through a lot of the proximity threads but still having problems.

im running atomic blue 1.5

and have tried editing the build.prop file but no joy adding the proximity values.

have also tried to flash the proxcal.zip file from another thread/forum, but still no joy.

is there an update for the atomic blue rom that can sort this issue.

This is the fix posted by Tilal that cured it for me (and most people I believe)... Black screen when calling see post #20.

Ludicrous this thread is not a sticky :blink:

Edited December 4, 2011 by gitf@ce

[Guest Simon O]

Ideally we need somebody to create and maintain an FAQ for the Skate. Anyone feel up for doing this?

[Guest tilal6991]

Ideally we need somebody to create and maintain an FAQ for the Skate. Anyone feel up for doing this?

I'll do it. It gets quite annoying seeing people asking the same questions and creating new threads for them.

[Guest metal.mickey]

tried the proximity sensor from the market and i get the values 1cm or 5cm when covered or uncovered so the sensor is working.

post 20 suggests to type in *983*0'# but i get a message saying "connection problem or invalid MMI code".

ive just put Atominc 1.6 is this an upgrade to atomic blue 1.5 as the UI is very diff. Im not one for launchers and stuff but the user XP is quite different.

Ive read that ther is a proximity on of off setting in the call settings or accessiblity tab but i cant find either, are they relevant?

thanks for the help

[Guest metal.mickey]

Bump.

so is there no solution for this error or can anyone suggest a ROM which doesnt have this foible.

MM

[Guest tilal6991]

Bump.

so is there no solution for this error or can anyone suggest a ROM which doesnt have this foible.

MM

Go to bluemonte and type in the code.

[Guest metal.mickey]

Back to BlueMonte...

the *983*0# still doesnt work?

Ive come from bluemonte to atomic blue to atomic 1.6?

[Guest metal.mickey]

i started in bluemonte code doesnt work

tried atomic blue

tried atomic

back to bluemonte code still doesnt work. Im rooted

???

[Guest dadcore]

Worked for me with the latest atomic + zte addons  Is it possible to keep the ZTE dialer around for just this purpose?  I prefer the dialer/contacts that come with Atomic.

[Guest masian]

Hi guys! I have been researching about the sensor issue and i hope this works on our ZTE SKATE. Maybe is not the best solution but for the moment WORKS NICE if you don´t like ZTE dialer and you prefer use built dialer.

First install Atomic custom rom, but you has not to install any app. Next step is install ZTE DIALER (Atomic 1.6 tillaz) from recovery. Reboot our ZTE and push into the phone icon. Mark *983*0# and now you must go sensor menu, press calibrate.

Then, reinstall the custom rom (without wipes), and the dialer app it will work fine. You will be able to see that the modded dialer from the rom it´s running now.

Try on!

Thanks, cheers.

Edited December 6, 2011 by masian

[Guest metal.mickey]

can you point me to the zte dialer zip

MM