So I've using custom roms for a while. But recently I realized rotation out of the blue. Reinstallations and fixes didn't work. So I decided to install TW Stock rom. And to my surprise rotation STILL doesn't work. Did the hardware just die? Any ideas?
ultra99 said:
So I've using custom roms for a while. But recently I realized rotation out of the blue. Reinstallations and fixes didn't work. So I decided to install TW Stock rom. And to my surprise rotation STILL doesn't work. Did the hardware just die? Any ideas?
Click to expand...
Click to collapse
for me too, but I think that a few drops killed it or sth like that. I've ordered new sensor, so will let you know if that fixed proximity sensor problems.
Try apps from play store to test if sensor is working. For me it detected, that sth is near and stay in that state until restart
Related
After flashing a few ROM's I noticed my accelerometer, g-sensor, and magnetometer (compass) stopped working. I thought it might be the ROM that I was using so I restored stock and they still aren't working. I did a factory wipe and it still doesn't work.
If anyone has a fix for this I'd be very happy.
Also, where are these sensors physically located? I have opened my case when I fixed my spring so I want to know if I messed anything up then. Although the sensors were working fine for quite a while after.
thanks for any help!
mkornelson said:
After flashing a few ROM's I noticed my accelerometer, g-sensor, and magnetometer (compass) stopped working. I thought it might be the ROM that I was using so I restored stock and they still aren't working. I did a factory wipe and it still doesn't work.
If anyone has a fix for this I'd be very happy.
Also, where are these sensors physically located? I have opened my case when I fixed my spring so I want to know if I messed anything up then. Although the sensors were working fine for quite a while after.
thanks for any help!
Click to expand...
Click to collapse
I am having the same issue. I have rebooted and re romed like 5 times with no change.
Same problem
I have the same problem, but only for the g-sensor.
It was the same story after installing a custom rom the sensor stopped. This would'nt work again with any other rom.
Please an advice?
I've had this issue for quite a while now.. at first I figured it was just a bug as my screen would no longer rotate but I've flashed and tried several different roms (Probam jelly bean, KitKat, and now on Temasek V28 KitKat) and have tried a few different Kernels such as Devil 2.3.2 and currently using the stock Temasek kernel.
I've downloaded some sensor apps and they list my sensors, but whenever I go to test them such as the accelerom3534, gyroscope, compass.. they don't work at all.. They just say "waiting for data"
The Proximity sensor still appears to be working though.
Anyone had this issue? My phone I don't think is damaged.. I've dropped it on some small falls in the past but it's been in a nice cover as well.
Small update:
Went back to a rooted stock 4.1.2 AT&T ROM, stock kernel, stock modem.. no change. Must be the hardware being broken
epix1718 said:
Small update:
Went back to a rooted stock 4.1.2 AT&T ROM, stock kernel, stock modem.. no change. Must be the hardware being broken
Click to expand...
Click to collapse
Is it your home screen that doesn't rotate or will no apps work.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
ShrekOpher said:
Is it your home screen that doesn't rotate or will no apps work.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
None of the apps will rotate, or say a picture in "gallery". Home screen I know was never designed to rotate.
Also just tried the 1-Click ODIN restore to unrooted stock rom, no difference Screen still does not rotate in any apps.
Sounding like a hardware issue...
Sorry to hear that ...g
epix1718 said:
None of the apps will rotate, or say a picture in "gallery". Home screen I know was never designed to rotate.
Also just tried the 1-Click ODIN restore to unrooted stock rom, no difference Screen still does not rotate in any apps.
Click to expand...
Click to collapse
the only other option I can suggest is to check and make sure all of your settings that effect screen rotation of cleared. Make sure you don't have smart stay on and you have screen rotation enabled in your settings. You may also want to turn them on if they are off and reboot your phone. Then turn them back off and reboot your phone again. If that doesn't fix it I would assume its a hardware issue.
Did you drop your phone recently or get it wet or damp. That's the only thing I have heard can cause the hardware issue.
bringing this thread back to life sense I couldn't do the same for my sensors
Hello there! So I have had a similar experience with the Note 2. It is not hardware related as far as I can determine because I swapped out the prox sensor on mine and it did not help. I feel that it is kernel related. On my previous Note 2, I flashed some kernel, prox sensor stopped working. I flashed back to stock AT&T and it worked for one call before quitting again. That's when I tried a new sensor and camera unit. The phone was under warranty so I triangled away and traded it. With the current Note 2, I flashed Sky note 9.3 and then after a while the prox sensor stopped working, I just thought okay with whatever maybe it's the kernel I'm using. I wanted to upgrade to Sky note Air, so I did. Got all settled in and decided to see if their provided kernel fixed my call sensor, no cigar. So I went into *#0*# and realized that none of my sensors were working. Tried using Devil Kernel, stock, stock ROM, all sorts of configurations and I can't revive any of them. Feeling very defeated.
I rooted my girlfriend's S3 with no problems. I can install a TW rom and everything works as expected. If I installed a ASOP rom, when a call is made or received the screen turns off. If you pull the phone away from your ear the screen stays off. I've browsed around the forums, but have not found anything to resolve the issue. Any ideas of what might cause this on ASOP roms ?
Thanks in advance,
Richard
Try different ROMs to see if the all do this, inlcuding a stock ROM. If they all do the same thing, sounds like it could be a hardware issue with the proximity sensor.
You could test the proximity sensor response. It might be flaky?
I use this app,
https://play.google.com/store/apps/details?id=com.tbs.activity
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
audit13 said:
Try different ROMs to see if the all do this, inlcuding a stock ROM. If they all do the same thing, sounds like it could be a hardware issue with the proximity sensor.
Click to expand...
Click to collapse
The only time it has been an issue is with ASOP roms. If I use a TW rom, there is an option to leave the screen on during a call. This is what I clicked to get the screen on during calls. However, with ASOP roms there is not an option for this. I don't think it's the proximity sensor since the screen stays on with calls on a TW rom. I forgot to mention that the ASOP was KK rom, but I have the same phone different cell provider and do not have this issue. I think I tried a JB rom with the same effect.
When using any ROM, stock or custom, on all of my Android phones, the screen always went black when I placed the phone next to my ear. When I removed the phone from my ear, the screen came back on and I could end the call by clicking a button on the screen.
With a stock ROM, does the screen go off when you place the phonex to your ear and then come back on when you move it away from your ear?
audit13 said:
When using any ROM, stock or custom, on all of my Android phones, the screen always went black when I placed the phone next to my ear. When I removed the phone from my ear, the screen came back on and I could end the call by clicking a button on the screen.
With a stock ROM, does the screen go off when you place the phonex to your ear and then come back on when you move it away from your ear?
Click to expand...
Click to collapse
as soon as you make a call the screen goes black and does not come back on, unless the call ends. I can not end the call either unless I press the lock screen button, slide down the notification bar and press hang-up. This is only on all ASOP roms.. This is my girlfriend's phone, mine works fine. I'm on Sprint though. To make sure everything works only on TW, I put a custom TW rom on her phone. The screen turns black on calls, but I can go to the dialer settings and fix this with the leave screen on function. I don't think it's the proximity sensor, unless the sensor works different between ASOP and TW roms.
riche1 said:
as soon as you make a call the screen goes black and does not come back on, unless the call ends. I can not end the call either unless I press the lock screen button, slide down the notification bar and press hang-up. This is only on all ASOP roms.. This is my girlfriend's phone, mine works fine. I'm on Sprint though. To make sure everything works only on TW, I put a custom TW rom on her phone. The screen turns black on calls, but I can go to the dialer settings and fix this with the leave screen on function. I don't think it's the proximity sensor, unless the sensor works different between ASOP and TW roms.
Click to expand...
Click to collapse
Just to confirm, the screen goes black when you place the phone next to your ear and comes back on when you move it away from your ear on a stock TW ROM, correct? If the phone exhibits this behaviour on a stock ROM, the proximity is working. If it does not, I would still conclude the proximity sensor is not working. I have loaded custom ROMs onto 3 different S3 phones and the screens alway came back on when I moved the phone away from my ear without having to touch the power button.
audit13 said:
Just to confirm, the screen goes black when you place the phone next to your ear and comes back on when you move it away from your ear on a stock TW ROM, correct? If the phone exhibits this behaviour on a stock ROM, the proximity is working. If it does not, I would still conclude the proximity sensor is not working. I have loaded custom ROMs onto 3 different S3 phones and the screens alway came back on when I moved the phone away from my ear without having to touch the power button.
Click to expand...
Click to collapse
This is correct. It works fine on TW roms , but I have to turn on some function in the dialer settings for it to work after the initial install. My girlfriend said her sister's phone did the same thing ( no root ) and she had to go to the dialer settings to get things back to normal. I believe she said this happened after the ATT 4.3 stock update.
If I use any ASOP rom the screen will go black as soon as a call is made by pushing the call button. The only way to get it to come back on is to get the lock screen up and pull the notification bar down to hang up. She does not care whether she uses a ASOP or TW, but I'm baffled by the issue with ASOP roms since mine works great, but I'm with Sprint. The proximity sensor is working fine in my opinion because all of the TW motion features work flawless. I wanted to get her on an ASOP rom because the battery life is so much better. Sorry for the late reply. Thanks for helping!
riche1 said:
This is correct. It works fine on TW roms , but I have to turn on some function in the dialer settings for it to work after the initial install. My girlfriend said her sister's phone did the same thing ( no root ) and she had to go to the dialer settings to get things back to normal. I believe she said this happened after the ATT 4.3 stock update.
If I use any ASOP rom the screen will go black as soon as a call is made by pushing the call button. The only way to get it to come back on is to get the lock screen up and pull the notification bar down to hang up. She does not care whether she uses a ASOP or TW, but I'm baffled by the issue with ASOP roms since mine works great, but I'm with Sprint. The proximity sensor is working fine in my opinion because all of the TW motion features work flawless. I wanted to get her on an ASOP rom because the battery life is so much better. Sorry for the late reply. Thanks for helping!
Click to expand...
Click to collapse
Without making any changes to the stock TW ROM dialer settings, does the screen go black when you place the phone next to your ear and come back on when you move it away from your ear?
If I put a clean install of a TW rom it does not work either. I have to change the dialer settings. My girlfriend told me this happened as soon as she installed the 4.3 update way before I rooted the phone.It happened to her sister too. I did not know about the issue until I rooted. . I doubt it's the recovery I'm using. I had problems installing CM with TeamWin Recovery. I had to use Philz. Like I said, I don't mind keeping her on TW roms and she doesn't care either. It would be great to find out what is causing this. It's got to be something with the proximity sensor detection, but the proximity sensor does work otherwise the TW gestures and features would not right ?
riche1 said:
If I put a clean install of a TW rom it does not work either. I have to change the dialer settings. My girlfriend told me this happened as soon as she installed the 4.3 update way before I rooted the phone.It happened to her sister too. I did not know about the issue until I rooted. . I doubt it's the recovery I'm using. I had problems installing CM with TeamWin Recovery. I had to use Philz. Like I said, I don't mind keeping her on TW roms and she doesn't care either. It would be great to find out what is causing this. It's got to be something with the proximity sensor detection, but the proximity sensor does work otherwise the TW gestures and features would not right ?
Click to expand...
Click to collapse
Was the clean install done using a stock 4.3 TW ROM? I didn't know there was a problem with the 4.3 update that affected the proximity sensor.
audit13 said:
Was the clean install done using a stock 4.3 TW ROM? I didn't know there was a problem with the 4.3 update that affected the proximity sensor.
Click to expand...
Click to collapse
Originally stock 4.3 updated through ATT is when she started to experience the problems. She fixed by going to dialer/settings leave screen on during calls. I rooted the phone not knowing this had been an issue before. After making sure the stock 4.3 was rooted I installed cyanogenmod and thus the issue was back. There was no way to fix it another than to install a TW rom and go through the dialer/settings. If that settings is not checked then the phone will go black as soon as a call is made. I can't find away around it. I keep forgetting to come back on check here for replies.. sorry for the delayed response. Thanks for the help
Richard
riche1 said:
Originally stock 4.3 updated through ATT is when she started to experience the problems. She fixed by going to dialer/settings leave screen on during calls. I rooted the phone not knowing this had been an issue before. After making sure the stock 4.3 was rooted I installed cyanogenmod and thus the issue was back. There was no way to fix it another than to install a TW rom and go through the dialer/settings. If that settings is not checked then the phone will go black as soon as a call is made. I can't find away around it. I keep forgetting to come back on check here for replies.. sorry for the delayed response. Thanks for the help
Richard
Click to expand...
Click to collapse
The behaviour exhibited by the phone after the update is not right. If it was a software issue, it would have been solved by flashing a custom ROM.
I have flash a few custom ROM and non-custom ROMs onto the d2can (i747m) and none of the phones behaved the way yours does.
audit13 said:
The behaviour exhibited by the phone after the update is not right. If it was a software issue, it would have been solved by flashing a custom ROM.
I have flash a few custom ROM and non-custom ROMs onto the d2can (i747m) and none of the phones behaved the way yours does.
Click to expand...
Click to collapse
she said it was not a problem until the phone was updated to 4.3 through ATT software update. This was way before I rooted the phone. The same thing started with her sister's phone. So.. I'm stumped as to what the problem could be. I rooted it because I thought CM11 might fix the issue and that was not the case. I don't know how I can go about fixing it. I don't want to take a chance in bricking the phone.
I have been dealing with this problem for far too long, and Google doesn't seem to help. I've tried disabling any/every feature. It worked once, but now everything is turned off (motion and gestures) and every time the screen rotates, touchwiz has stopped working. I'm running a custom ROM, and no matter which one I run, I get this issue. Does anyone else get this error? Any suggestions for a fix?
Odin back to stock.
If the problems persist, it is most likely hardware.
koop1955 said:
Odin back to stock.
If the problems persist, it is most likely hardware.
Click to expand...
Click to collapse
Quick fix: I saw where changing the animation speed, under developer settings, back to 1x fixed the issue. I did that previously and then it started messing up again. So, I changed it back to .5x, and boom, it stopped unfortunately closing every time I rotated the screen. I guess I can deal with it for now. I know it has to be rom or kernel related, bc it has done it before on different roms. I prefer not being stock
I have started with the stock ROM, and used cm13, and even updated to the newest fully stock ROM 3.2.4 and to no avail.
The camera app either force closes or nothing shows up on screen. Every once in awhile the front camera will work, but I'll click the icon to switch to the rear camera and no effect, it just stays on fron t camera.
I've tried many third-party apps, I've tried cm camera fix, everything I can think. Clearing data and coach for the app the whole shabang.
Now I'm ordering a brand new camera module and I will see what happens. But any help and any information will be much appreciated thanks
Was it working when you bought it...what did you do to it before it broke?
it definitely seems like a hardware issue, had it been a software issue a custom rom or 3rd party camera might have resolved it and since you have tried many roms and reverted back to stock too so it doesnt look like a software issue.
GeneralDisaray2 said:
Was it working when you bought it...what did you do to it before it broke?
Click to expand...
Click to collapse
Funny you should ask, because I honestly don't know when it actually started but I do remember wiping userdata so I could unencrypt my phone and thereafter was when I noticed it no longer worked. Don't know if those 2 things correlate because I flashed back to stock (which is encrypted) and still no luck
Did you solve the camera problem ???