Found the solution!
It was by matlacki, basically just reflash stock ruu 1.32, re-root and restore your nanadroid and it's all good.
matlacki said:
I had the same problem yesterday and I found the solution (it works for me). Flashed stock RUU 1.32, rooted again, eng/radio-s off, again, flashed CW7 bulid 30 and my proxymity sensor is back to normal.
Click to expand...
Click to collapse
I have done the same and now my proximity sensor is working again when restored from my CM7 nanadroid.
This doesnt make any sense?!
==================================================
Btw i am using build 30
For those who having this proximity sensor issue like myself , I done a test.
Go to setting > CyanogenMod setting >display > automatic backlight > > tick use custom > edit other levels.
For me I can see my sensor functioning will. 7 for total darkness and 59 for din light and 190+ for lamp.
Now try to make a call and watch the screen go off. You can't on it back but there's still ringing tone.
I used my nexus one flash to shine on the sensor and my screen turned back on.
Now go back to the edit other lvl notice that the light sensor doesn't response to the different brightness.
A reboot will fix the problem but if there's s phone call,this bug starts again. Try it!!!
And share your results. If there's ppl with the same as mine, it might be a cm7 bug and not s proximity sensor failure
Its not a CM7 bug. I have never had the proximity sensor problem on any ROM, be it stock or otherwise.
I'm also using build 30 and no proximity sensor problem to report.
i want to believe its not a CM7 bug.
For the past 2 weeks when I was using various CM7 builds, I do not have any proximity issues as described by other users till yesterday, it just popped up.
Nandroid to my old backup (which has no such the problem), and problem still persist.
flashed back to RUU 1.32 rom and the sensor is working in sense rom.
So now i cant even send back for a replacement.
matlacki said:
I had the same problem yesterday and I found the solution (it works for me). Flashed stock RUU 1.32, rooted again, eng/radio-s off, again, flashed CW7 bulid 30 and my proxymity sensor is back to normal.
Click to expand...
Click to collapse
I have done the same and now my proximity sensor is working again when restored from my CM7 nanadroid.
This doesnt make any sense?!
This problem started yesterday evening for me. 5days of CM7 without issues and now this dealbreaker. Need to pull battery after end of a call.
Sent from my Desire HD using XDA App
try flashing 1.32 RUU and redo the whole rooting again > and back to CM7.
seems unreal but it really did solve my problem..
Okay...
I'm having the same problem, i just checked it with the program "Sensorlist" which gives me info about the proximity sensor....
With CM7 it doesn't work, but with stock rooted ROM it works fine...
So it must be a problem with the CM7 software....
Has anyone solved the problem, so it doesn't come back?
Solved my Problem, too.
And I guess I've found the reason for the Problem.
Within the last Days, I've played around a little with the ambient light sensor settings. Both, system side and also with the additional cyanogen settings.
Why do I come to that conclusion?
Well, I made a Backup of all my Apps and Settings via TitaniumBackup.
Then I:
- Wiped my phone via CW + Full-Wipe.zip
- Flashed this 1.72 via CW http://forum.xda-developers.com/showthread.php?t=884327. Tested it = everything fine.
- Wiped again + clean installed PNK_AB CM7. Testet it = everything fine.
- Restored my Apps + Settings. Failure retuned after restart.
Now I was sure, it is Software related.
- So I wiped the data partition via CW and restarted. Everything fine again. Even after Reboot.
- Time to restore Apps + Settings, but this time without the settings from the Cyanogen Apps/Settings, Debug App and SpareParts. Everything fine in first, but the problem retourned after reboot.
- So again: wiping data = everything fine. Rebooted about five times, te be sure. Everything fine.
- Restored Apps + Settings: without: Cyanogen Apps/Settings, Debug App, SpareParts AND SystemSettings.
Voila: The Problem was away and didn't even come back after several reboots.
So my conclusion:
CM7 ambient light settings and system ambient light settings mess each other up. Dunno, which is causing the problem, but it is solved for me, yet.
What's your Opinion guys?
My findings (with input from Apache14):
- The proximity issue only affects those with a non-Sharp LCD.
- The kernel source code released by HTC does not contain the correct code to handle this device. I am still looking for solutions.
- On the 1.32 kernel, when proximity is required, some polling mechanism is activated. I assume this is needed as there is no Interrupt hooked up on a hardware level on this LCD/chip (same sensor uC however).
- There is no source code for this. Not in HTC released kernel source or CM or AOSP.
Currently I am looking at either:
- Getting the latest source code for the DHD kernel which HTC has failed to release. The source code corresponds to some RUU older than 1.32.
or
- Hacking the kernel to do the same polling as present in the 1.32 kernel binaries.
McKebapp said:
Solved my Problem, too.
And I guess I've found the reason for the Problem.
Within the last Days, I've played around a little with the ambient light sensor settings. Both, system side and also with the additional cyanogen settings.
Why do I come to that conclusion?
Well, I made a Backup of all my Apps and Settings via TitaniumBackup.
Then I:
- Wiped my phone via CW + Full-Wipe.zip
- Flashed this 1.72 via CW http://forum.xda-developers.com/showthread.php?t=884327. Tested it = everything fine.
- Wiped again + clean installed PNK_AB CM7. Testet it = everything fine.
- Restored my Apps + Settings. Failure retuned after restart.
Now I was sure, it is Software related.
- So I wiped the data partition via CW and restarted. Everything fine again. Even after Reboot.
- Time to restore Apps + Settings, but this time without the settings from the Cyanogen Apps/Settings, Debug App and SpareParts. Everything fine in first, but the problem retourned after reboot.
- So again: wiping data = everything fine. Rebooted about five times, te be sure. Everything fine.
- Restored Apps + Settings: without: Cyanogen Apps/Settings, Debug App, SpareParts AND SystemSettings.
Voila: The Problem was away and didn't even come back after several reboots.
So my conclusion:
CM7 ambient light settings and system ambient light settings mess each other up. Dunno, which is causing the problem, but it is solved for me, yet.
What's your Opinion guys?
Click to expand...
Click to collapse
how can you remove these parts from the Rom? "the Cyanogen Apps/Settings, Debug App and SpareParts. "?
Sent from my Desire HD using XDA App
Numsefis said:
how can you remove these parts from the Rom? "the Cyanogen Apps/Settings, Debug App and SpareParts. "?
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Didn't remove them from the ROM.
I simply unticked them while/before restoring my FullBackup with TitaniumBackup.
For those that cant get proximity sensor to work on custom kernel/ROMS, try the following (no root required):
Code:
echo '0x50530b0c 0x140b0b0c' > /sys/devices/virtual/optical_sensors/proximity/ps_kadc
This will adjust the calibration values. The 0b part is the 'low tide' aka FAR start and 0c is the 'high tide' aka NEAR start.
IOW, values below FAR start is FAR, and values above NEAR start is NEAR.
Tested this on latest Buzz (Apache14) kernel.
Need to somehow make this persistent, and make sure it does not get reset during normal operation.
Stay tuned
Update: Still thinking of how to apply this at boot, maybe 'init.d' ? Also havent been reset during normal operation.
Thanks for the info
ok but how do you appli that ?
Text editor ? etc.
Flashing default (stock ruu) kernel
did it for me. Prox sensor working as intended.
Sent from my Revolutionized Desire HD using XDA App
I wrote an app to fix this.
See http://forum.xda-developers.com/showthread.php?p=11312762#post11312762.
Great work Leppie!
I had this problem, wile on CM6, started after I installed ADW EX. Used to use launcher pro, but realy liked the transisions in ex, so started using that, and got this problem. Updated to CM7, stil had the problem, no matter rom version. Went back to launcher pro, and now it works like normal. Thinking ther might be something with the launcher, and mabye a hardwere thing in some phones.
I am now on nihtly CM7 34, I think, and no problem.
So for those having this prob, try to switch to another launcher, and reboot a couple of times.
Hope this helps
how did you downgrade?
with Recovery?! or with Gold card?!
i have done both ways but didn't solve my problem :-(
please give me a link of Stock rom ruu!
I installed the official CM10 stable about a week ago and was really surprised how much faster the ROM is than the original ASUS firmware.
suddenly about 2 days ago my screen didn't rotate anymore when I turned the tablet. (Autorotate is switched on!)
I then installed a water level app to check the sensor values and found it to always return 0 deg.
I already tried rebooting and also tried recovering from a TWRP backup, I made right after installing CM10, but the sensors still refuse to give me any feedback.
Any help would be really appreciated.
edit:
Doing a full wipe before restoring my backup resolved the issue!
Hi all, I just got a Defy+ and I noticed that auto rotation is not wotking. Phone is always in portrait mode (auto rotation is enabled in options), I tried couple of roms and result is same. In CM roms compas calibration is working but screen is still stuck in portraid mode. Flashing officialy SBF didnt help....Is this hardver problem or there is still hope for me?
Looking at these pictures Defy on the left (my defy) has problem with compas. On flat surface both show N correctly but when I place them up my defy is showing wrong N. Is there any way to fix this compas error?
Some news...each time I flash SBF auto rotation works only for 5 sec, so I startet to experiment with system/bin/akmd2. I was mowing that file all over the phone memory, giving him diferent permision...and I dont know how but after phone restart auto screen rotation worked. I was so hapy so I decided to flash CM10 and after that flashig autorotation didnt work again. I have tried to repeat steps with akmd2 file but no help. And one strange thing...I have flashed WiUi JB 3.1.21 and in that rom my autorotation is working. Unfortunately that rom is laggy for me and I cant use it. question is why autorotation is working on this wiui rom but not workign on official sbf and other cm roms? Can I use some files from wiui system/bin to put them into CM and make screen autorotation working again? Thx
Solved
All this time autorotation option didnt work and two days ago I have installed game from google market "Traffic Racer". After playing that game for 10 min I noticed that autotoration is working :fingers-crossed: . I thing playing that game with tilt somehove triggered my sensors again and now after flashing many roms autorotation is still workin.
Hi All,
Just wondering if anyone have this issue? Initially the light was intermittently working on the flashlight app but when using the camera was fine. Now the light totally doesn't work even on the camera mode, even if I set as forced flash, it won't work.
This is what I have done: -
(1) I tried a full system hard reset and tried without the installing any updates or applications and still It didn't work.
(2) Booted up in safe mode and tested the light, it does not work.
The phone is N910G and running on unrooted stock 6.0.1
Anything else I could try?
Thank you everyone.
techx