Hi, long time lurker on XDA, but first time I've needed to ask for help (usually search function does it for me), so please be kind!
I have an Xperia Go, purchased it running gingerbread, upgraded to ICS, then rooted using advice on XDA. Was running 6.1.1.b.10.
My proximity sensor was always quite weak, so whilst on 6.1.1.B.10 I followed the mod as described in this thread to increase strength of the sensor: http://forum.xda-developers.com/showthread.php?t=1917050
At that stage (a few weeks ago) all was rose, had a working phone and proximity sensor.
Over the weekend my phone's update service told me that 6.1.1.b.54 was available, I tried to update directly on the phone, it tried but I was told the update failed. In my mind this must've been because I was rooted, so I thought nothing of it.
However since then the proximity sensor has stopped working at all! I've gone into the service menu where proximity sensor shows as off, and covering the sensor does nothing.
I thought I had better flash the firmware properly, so I flashed 6.1.1.b.54 using the flash tool (not SEUS), but still no luck, proximity sensor does not function.
My hw_config.sh file shows:
# Proximity sensor configuration
dev=/sys/bus/i2c/devices/3-0054/
val_cycle=1
val_nburst=1
val_freq=5
val_threshold=1
Any advice on how I can switch my proximity sensor back on?
Reflash ftf.
Sent from my ST25i using xda premium
Thanks, I tried a factory reset, no joy. Will try a reflash
Reflashed with no joy
Related
First post.
My wifes Samsung Galaxy S2 LTE from Rogers (i727R) which came with 2.3.5 got some water spilled on it. After letting it dry out the phone works fine but the camera just gives a "camera failed" error and the screen auto rotate doenst work at all in any app.
I got the camera working for a bit after doing a factory reset but but it stopped again a few days later. This made me think it was a software issue so I rooted the phone and tried flashing the stock rom back on using Odin which did not help either issue. To rule out that it is corrupted software, is there anything else I should try? New kernel?
When I enter *#0*# and go into the sensor test area, the accelerometer and magnetic sensors do not seem to be working. Gyroscope is working.
If more info is needed, let me know.
Thanks
Use this app to test if they are working: https://market.android.com/details?id=com.bartat.android.elixir&hl=en.
Thanks for the help. I installed elixer and looks like the accelerometer, gravity, linear acceleration, magnetic field, orientation and rotation vector sensors are not working.
Dyno-droid said:
Thanks for the help. I installed elixer and looks like the accelerometer, gravity, linear acceleration, magnetic field, orientation and rotation vector sensors are not working.
Click to expand...
Click to collapse
So that means it's a hardware problem. You'll have to carry it back under warranty (hopefully you have one).
That brings me to my next question.
I rooted and flashed the stock rom on with Odin, hoping that would fix it since the issue was initially fixed with a factory reset. Thought maybe a driver or something got corrupted.
From browsing the forums, it appears there is no way to reset the flash counter yet. Is that correct? If so, would it be worth waiting a while in hopes a fix comes out to reset the counter?
Dyno-droid said:
That brings me to my next question.
I rooted and flashed the stock rom on with Odin, hoping that would fix it since the issue was initially fixed with a factory reset. Thought maybe a driver or something got corrupted.
From browsing the forums, it appears there is no way to reset the flash counter yet. Is that correct? If so, would it be worth waiting a while in hopes a fix comes out to reset the counter?
Click to expand...
Click to collapse
Only a few devices are able to reset the flash counter (so far). You could try flashing a custom rom and see what happens.
NB.: Even if you could reset the counter, that wouldn't really benefit you in this case.
Hey guys,
I know this thread already exists in this forum but has come to an end with no solution and since its kinda very important to sort this issue to be able to use my phone I thought ill start fresh for some input from the experts.
I have a Galaxy S2 I9100 rooted with a custom ROM(slim ICS 4.1 when the issue started) and it started randomly freezing when unlocking the screen and normal use .but since last week it wouldnt let me make or receive calls as the phone freezes and reboots 10-20 secs into the call..i updated to 4.2 with the hope of resolving this but tht didnt work..I have changed kernels and ROMS(resurrection, cm9 release build)..though the dialer did work for calls on resurrection ROM the proxomity sensor wouldnt work..
so i tried going back to stock sammy ICS (XXLPH) and then the dialer would work but again without the proximity sensor and the samsung tests also confirmed that the sensor wasnt registering...
am rooted now and back to slim 4.2(dont like the look of sammy) with siyah kernel 3.2.2...the dialer and proximity sensor don work..the rest of it is all fine..
Ive done all the wipes each time ive installed a new ROM...also done kernel wipes before installing Kernels..
I think its not a ROM/hardware problem but well it could be but hope to get it sorted through the normal techniques..I cant return my phone for repairs as it was in mint condition bot second hand in UK without warranty papers..
Any help would be highly appreciated..thanks
EDIT: It seems the proximity sensor is to blame for this problem as i found out through other posts..and also i can make and receive calls with the headset/headphones plugged (in which case i assume the phone doesnt try to activate the proximity sensor)..
For now i would like to know how to disable the proximity sensor on the phone..I have tried inserting the gsm.proximity.enable=false in the build.prop editor using the ROM Toolbox lite app n rebooted...but that din seem to work...is there any other way to do this??pls help
I am having EXACTLY the same issue as reported here and it's driving me mad. Did you ever find a fix for it?
proximity sensor and screen brightness sensor
3dawg said:
I am having EXACTLY the same issue as reported here and it's driving me mad. Did you ever find a fix for it?
Click to expand...
Click to collapse
I havent managed to find a solution as yet..it seems the proximity sensor and the screen brightness sensor(which are on the same PCB i think as per the unassembling video) have a hardware fault and might need repairing..
Some kernels i think maybe bypass using the proximity sensor if its not working..for now I am back to the SLIM 3.2 ICS rom..It doesnt switch off my screen on call and also no auto brightness adjustment but rest all works ok so am using it for now before i get the hardware repaired..
also the resurrection rom v 2.5.1 works fine in the same manner(havent tested many others..CM7 release build doesnt work)..or you can try that script in build.prop to disable the proximity sensor..
check how it goes..
How about CM9? Do these problems disappear on CM9? CM9 was working well for me but the home key and lock screen never worked. I applied all the common fixes to the keystr file but it never made a difference so I switched to slimics which worked. Then I discovered these annoying call screen off and waking problems :/
proximity sensor and screen brightness sensor
3dawg said:
How about CM9? Do these problems disappear on CM9? CM9 was working well for me but the home key and lock screen never worked. I applied all the common fixes to the keystr file but it never made a difference so I switched to slimics which worked. Then I discovered these annoying call screen off and waking problems :/
Click to expand...
Click to collapse
I tried checking with the testers for the Slim ROMS..regarding differences in kernel or anything for slim 3.2 and 4.2(3.2 works while 4.2 doesnt) but they couldn't tell me what was the exact problem or the differences that should affect in this case..I haven't tried a CM9 ROM yet but it could work..The kernel for the resurrection ROM is siyah kernel but when i tried that kernel with the slim 4.2 ROM that still didn't work for calls as the phone rebooted.
Have you managed to find a replacement cost for the proximity sensor? also does your screen brightness sensor work?
guys last week i bought an xperia p. it came with ics preinstalled and the proximity sensors was working fine but after updating to jb via flashtool the proximity sensor doesnt work now. tried reverting back to ics but the problem still exists. have tried the service menu and it shows proximity sensor is off. is their something i can do to fix it or would i need to send it for repair.
thanks in advance.
js200988 said:
guys last week i bought an xperia p. it came with ics preinstalled and the proximity sensors was working fine but after updating to jb via flashtool the proximity sensor doesnt work now. tried reverting back to ics but the problem still exists. have tried the service menu and it shows proximity sensor is off. is their something i can do to fix it or would i need to send it for repair.
thanks in advance.
Click to expand...
Click to collapse
try back to Gingerbread 2.3
newbie here,
After i installed a tempered glass,it looks like my proximity sensor needs some calibration. Phone display turns off when making a call and cannot turn it back on till i end the call. AFAIK, we could re-calibrate the sensor by going into the service menu using *#*#7378423#*#*. But, in the stock 5.1.1 ROM, there is no calibrate option in the service menu.
Any fix/suggestions that doesn't involve rooting/custom ROM ?
Please help.
Try some of the calibration apps on the Play Store.
I'm also facing this issue..
Have you found out how to fix this proximity issue ?
no calibration setting using *#*#7378423#*#* service menu.
nothing so far mate.
happen to mine too, this what i did
Flash an older version, the last one with calibration option is android 4.3, but i flashed android 4.2; then calibrate there, after that flash the latest without wiping anything.
or like i read in sony forum, repair it through PCC, this one i've never tried tho.
hope it helps
I have this issue with my S3, that is infuriating! Whenever I get a call and answer it, my screen turns off after a short while and during the call I can't turn it back on. The power and home buttons do nothing, and the proximity sensor isn't working either, so I can't turn off a call.
Anyone know how I can fix this? I have Lollipop, CyanogenMod 12.1 custom ROM installed.
Thank you for your time.
This bug partially exists in stock roms too. It's just magnified in custom roms.
You should be able to set it to keep the screen on during calls. It's the only way i know of.
I fixed this problem by opening up the phone, unplugging the proximity sensor, and throwing it in the bin. (the trash to you Americans)
Screen stays on during calls now, but I've not had problems with accidentally ending calls with my face, so I'm happy.
You also lose your front camera because it's part of the same tiny PCB. But I've never used the front camera on a phone in my life. So my solution is perfect for me, but maybe not for you.
The other option is a software fix. There's an app, or a method that you can do yourself to disable the proximity sensor, but I had problems with it, so did it my way.
Edit: I forgot to mention that the reason my proximity sensor wasn't working was because whoever had this phone before me did a screen repair and had half severed the ribbon cable for the proximity sensor by accident. Not just because of the bug that sometimes exists.
Sent from my GT-I9300 using Tapatalk
Proximity sensor problem. Manually calibrating it solved the issue for me.
http://forum.xda-developers.com/showthread.php?t=2569141
Go to that thread and follow instructions. The code for sensors might be different for s3, Google it.
sashankps said:
Proximity sensor problem. Manually calibrating it solved the issue for me.
http://forum.xda-developers.com/showthread.php?t=2569141
Go to that thread and follow instructions. The code for sensors might be different for s3, Google it.
Click to expand...
Click to collapse
Bah, that's the boring way to fix it.
(didn't work for me. maybe work for OP though)
Sent from my GT-I9300 using Tapatalk
I remember that I saw a MOD or xposed module to keep screen on during call.
It's better than throwing the sensor to the bin (trash ) .