I have screen rotation problem,samsung s2 gt-i9100, android version 4.1.2. Screen rotation works sometimes on strange angles. Already tried calibrating but still not fix.
I tried flashing another kernel to solved the problem using SiyahKernel S2-v6.0beta5 but it doesnt rotate anymore no matter how i tilt the phone. I've been repeatedly doing restore factory settings, wipe cache stil not solved.
I've tried dialing *#0*# and go to accelerometer sensor, it seems okay, the needles are moving. I've also tried installing "bubble level" app, the bubble moves, the sensor seems okay.
Again, tried flashing another firmmware XXMS7 Android 4.1.2 Jelly Bean but still not work.
Is there another solution to this problem?
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?
Hi, My friend has a galaxy S3 I9300, and because he isn't exactly android genius, he played with the settings, more specifically, with the gyroscope settings. he pressed on the calibration button, and he calibrated it, but now the screen wont rotate! and when he plays a game that uses the gyroscope, it dosent move at all! and then he tried to calibrate it again, and it went crazy! rotating back and forth. so he did it again and it's not moving again. he tried restarting and pulling out the battrey, but none have worked. he is new to this all android thing, so I would rather him not to do a factory reset. can anyone help?
did he calibrate it properly with the phone horizontal?
slaphead20 said:
did he calibrate it properly with the phone horizontal?
Click to expand...
Click to collapse
yes he did.
He should try a factory reset
Sent from my GT-I9300 using Tapatalk 2
If calibrate has not worked you have two choices factory reset or return under warranty .
Plus most important choice is keep your phone away from your friend .
jje
barlerer said:
Hi, My friend has a galaxy S3 I9300, and because he isn't exactly android genius, he played with the settings, more specifically, with the gyroscope settings. he pressed on the calibration button, and he calibrated it, but now the screen wont rotate! and when he plays a game that uses the gyroscope, it dosent move at all! and then he tried to calibrate it again, and it went crazy! rotating back and forth. so he did it again and it's not moving again. he tried restarting and pulling out the battrey, but none have worked. he is new to this all android thing, so I would rather him not to do a factory reset. can anyone help?
Click to expand...
Click to collapse
Hi!
don't panic, directly flash another firmware from there, you can start all over again and calibrate your friend's gyroscope. make sure you calibrate your phone by placing it on horizontal surface
Hi!
I am having a difficult time in disabling the proximity sensor in Galaxy S II. A few days ago I discovered that it was damaged, but it is probably gonna take a while till I am able to send it to Samsung for repair.
so When I receive a call or someone calls me the screen never comes back and I have to reset it or remove the battery which is pretty annoying.
So I have tried several methods using the Internet.
First there is this option in the caller application which basically disables the proximity sensor when calling. But this is not available in Jelly Bean 4.1. It has been removed...I am not sure why....
Second I tried adding manually in the biuld.prop file the entry
Code:
gsm.proximity.enable=false
After rebooting the phone that did not work either...
Finally I downloaded hardware disabled from the market, ticked the proximity sensor driver, rebooted and that worked fine. However when I do that the CPU remains in very high levels causing the phone to warm up a lot and the battery drain is amazing! So this is not really an option and I disabled that...
So I am wondering if any of u Jelly Bean users have any other ideas to offer cause I am kinda stuck here...
Thank you!
Paladin13 said:
Hi!
I am having a difficult time in disabling the proximity sensor in Galaxy S II. A few days ago I discovered that it was damaged, but it is probably gonna take a while till I am able to send it to Samsung for repair.
so When I receive a call or someone calls me the screen never comes back and I have to reset it or remove the battery which is pretty annoying.
So I have tried several methods using the Internet.
First there is this option in the caller application which basically disables the proximity sensor when calling. But this is not available in Jelly Bean 4.1. It has been removed...I am not sure why....
Second I tried adding manually in the biuld.prop file the entry
Code:
gsm.proximity.enable=false
After rebooting the phone that did not work either...
Finally I downloaded hardware disabled from the market, ticked the proximity sensor driver, rebooted and that worked fine. However when I do that the CPU remains in very high levels causing the phone to warm up a lot and the battery drain is amazing! So this is not really an option and I disabled that...
So I am wondering if any of u Jelly Bean users have any other ideas to offer cause I am kinda stuck here...
Click to expand...
Click to collapse
Wow, thank you, I didn't know this option exists. I am running NeatRom v4 Lite and that option you mentioned is still there. (it is also JellyBean)
Lol got same problem as OP and tried similar things including chmod 0000 to cm3663 folder but no success.
Any ideas?
Every sensor in my phone has stopped working after updating to KitKat. Going in *#0*# and hitting Sensor reveals that they are indeed not working at all. I have tried factory restoring my phone, rooting it, and installing different roms and kernels but none of these have fixed it.
Does anyone have any ideas?