Hi
I have this very weird problem with my Galaxy S2G. My gyro sensor stops working. This is happening for the 5th time. Just to clarify this is not only with the orientation problem. I cannot motion sensor games like Temple run, Bounce, etc.... Every time this happens i have to go back to gb stock rom. Calibrate the sensors. At that point it starts working. This problem is not to a specific rom. On all roms i face this problem. Is there a permanent solution for this? Every now and then it is very irritating to flash stock gb and calibrate the sensors. Hoping to find a permanent solution. Guys help :fingers-crossed:
I have browsed through all the threads and couldn't get a solution to this problem.
Thanks in advance for your support.
Related
I have a really strange problem with the touchscreen. When i touch it with one finger and hold my finger in the same location without moving it on the screen for 20-50sec, my touch is not recognized anymore at this location. Around this location my touch is "seen" by the screen, but not at the specific location. After a few seconds trying to touch the screen at the dead location, it "repairs" itself and everything works fine again.
That is a real problem when you want to play a game like reckless racing 2. There you need to hold the finger at the accelerate-button the whole time and after a few seconds it doesnt work anymore. Has someone experienced the same issue? The best way testing it is with a multitouch tester app .
I would be very thankful if someone could test it. Maybe i have a faulty device.
Im using a german razr with the latest android 2.3.6 firmware.
You can see a video of the problem here at vimeo.com/37909738
Something like this? http://forum.xda-developers.com/showthread.php?t=1467696
Thanks for the link. This really looks like the problem i have. This seems to be a feature? A feature which makes playing some games on the razr almost impossible .
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 everyone. Compass is stuck in my s4 mini. From sensor test (*#0*# then sensors) I can see this (see attachment). It seems like magnetometer is not calibrated. Any way to calibrate it (apart from usual methods like 8 figure or rotate phone around tre axis since I already tried them and they didnt worked) or reset it to stock values? Tried factory reset too.
thanks a lot guys.. I really need help, It may be an hardware issue but I want to try everything via software before send it to sammy
Attachments are in this other thread: http://forum.xda-developers.com/galaxy-s4-mini/help/gt-i9195-compass-properly-possibly-t2861288
Please help
after the latest update, to version 7.3.2.0(LHOMIDD), the proximity sensor's functionality has regressed (actually I do not remember the previous behaviour, can someone comment .
But now, while in a call, and when i place the handset close to the ear, the display switches off, but it does't automatically switch on , once i remove it from the ear.
This is quite irritating, is there a work around for the same?
Yes it happens to me too !! actually my device came with the latest version ! I did not update it !! May be a software issue !?
It's a known issue, hopefully it will be fixed with miui8. A workaround is to disable auto brightness
Well usually restarting fixes it.. go to settings about and click kernal version 5 times it will take u to service mode and try calibrating proximity sensor from there.. if this helped please hit the thnx button : )
Proximity sensor issue
Proximity sensor is not working properly on my Redmi Note 3 . I don't know when it stopped working, noticed it yesterday.
The phone is currently running on 7.5.3.0 MIUI. I am not able to calibrate as well it just displays Fail.
Can someone help?
Try this it'll help me to fix my all Sensors..
http://en.miui.com/forum.php?mod=viewthread&tid=312976&mobile=2
Sent from my Redmi Note 3 using Tapatalk
I have the same problem, even on custom roms I flashed miui and recalibrate the sensor and flashed RR rom there was no issue the issues started after I rebooted and again to temporary fix this issue I had to again reboot the phone and it solves and the problem comes back again after some time.....
@nexuspur, @techocentral, @kesavvel, @ coolant9 , there is one app i found in playstore which may fix this because it reloads the values on evry reboot try it....
https://play.google.com/store/apps/details?id=com.mobiledirection.proximitysensorreset
My MediaPad M5 (SHT-W09) has worked up well until yesterday. Now the fingerprint sensor is not working. I have rebooted, turned off & restarted it. I think the sensor MAy have worked again for a very short way but it is definitely does not work now.
The sensor does not work at logon, does not work for my banking apps and is not seen by other apps.Some apps say that there is no fingerprint sensor.
Has an app or something captured the sensor? If so how do I determine what is "hogging" the sensor?
Or is the sensor no longer working? Is so, is there any way to fix it?
Chris
Has anyone had the fingerprint sensor fail?
Chris
I also have the exact same problem.
It began a couple of months ago. The fingerprint sensor would show up for a couple of minutes after a reboot, but now it has disappeared permanently. Even the settings app won't show it after a restart.
Have you found a solution or some insights that could help us debug this?
I tried clearing the cache and sometimes it works for a while then the problem would reoccur. I did a reset to factory and this fixed the problem for a while.
I did cut back the number of apps.
Now it works perfectly and I don't know what caused the issue! It may have been a stray app.
Sorry about not giving a definite answer.
Chris
I have the mediapad m5 lite and I am having the same problem. It was complaining that the fingerprint hardware wasn't working and I restarted and now it is unaware it exists, even in settings. What was the cache you cleared? Did you have any luck further discovering what the cause is?
The fingerprint sensor works well now.
As I said previously, it must have been an app but I have no idea what
Sorry
Stay safe