Related
Hi,
The proximity sensor on my gf's lg g2 has broken and I'm trying to work out how I can disable it so that she can end calls. The screen goes off as soon as the number is dialed and there is no way to turn the screen back on.
The phones rooted and running ResurrectionRemix. The sensor stopped working before it was rooted.
Any suggestions???
Thanks
http://repo.xposed.info/module/com.mrchandler.disableprox
It's an old module for xposed, but confirmed working on 802 running 5.1.1 (not mine, saw one guys post somewhere on xda when I was looking to disable mine)
Oh good, which rom are you running? I tried to install xposed but it came up unsupported
Got a new Note 4 SM-N910C after I replaced my old, as it had display issues (same model). Old and new phone are running 5.0.1., both are rooted. I restored all apps and data from the old phone on the new via Titanium-Backup.
When I open the carema app, or ANY other camera app on the new phone, it won't focus for approximateli 10-15 seconds - afterwards autofocus works snappy and accurately. When I close the camera app and reopen it, sometimes the autofocus reacts immediately, sometimes I have to wait again. After a longer period in which i did not use the camera, the initial lag always occurs.
Same issue when I use the test mode (#0# - Mega cam). In compairison the old model always works perfectly!
Resetting the camera app does not fix the issue. "Shaking" the phone does not fix the issue.
Does anyone know that issue, does anyone hab a suggestion how to solve the problem. I don't know whether this is a hardware (stuck af-motor??) or a software problem.
I thank you for every answer and suggestion in advance.
Are you on the stock ROM now?
Yes, everythin is stock.. just rooted via CF autoroot..
Did you have this problem before you rooted the device?
pimpl said:
Got a new Note 4 SM-N910C after I replaced my old, as it had display issues (same model). Old and new phone are running 5.0.1., both are rooted. I restored all apps and data from the old phone on the new via Titanium-Backup.
When I open the carema app, or ANY other camera app on the new phone, it won't focus for approximateli 10-15 seconds - afterwards autofocus works snappy and accurately. When I close the camera app and reopen it, sometimes the autofocus reacts immediately, sometimes I have to wait again. After a longer period in which i did not use the camera, the initial lag always occurs.
Same issue when I use the test mode (#0# - Mega cam). In compairison the old model always works perfectly!
Resetting the camera app does not fix the issue. "Shaking" the phone does not fix the issue.
Does anyone know that issue, does anyone hab a suggestion how to solve the problem. I don't know whether this is a hardware (stuck af-motor??) or a software problem.
I thank you for every answer and suggestion in advance.
Click to expand...
Click to collapse
It's a hardware problem, the camera lens abit loose. Some tried shaking it but only a temporary fix. Bring it to Samsung Service Centre for repair (if still have warranty). Mine had that problem and was fixed by Samsung.
Update:
I restored the device's factory settings, i.e. Recovery - Full Wipe, and flashed the Lollipop 5.0.1. stock rom via Odin. I did not not restore the camera app usting Titanium Backup.
The error still exists. Shaking the device causes no improvement at all and there are no strange noises during focusing detectable. I suspect that it is therefore definitely not a hardware failure.
.. Once again the error description:
If I do not use the camera for some minutes and open any camera app (e.g. native app, instagram, PS-express, whatsapp, Google Kamera, camera pro and also in the test mode (# 0 # - Mega Cam)) the picture is totally blurry and the focus seems to stay in the macro focus. When I try to set the focus point by touching the screen, the focus indicator appears but the focus does not change for approximately 10 seconds (again, in all camera modes and camera apps). After this "initial lag" the camera works perfectly fine. When I close my camera and open it after a short time, it focuses immediately. When I close my camera and open it after a longer time, initial lag occurs again.
This is extremely annoying.
I suspect that the system deactivates the camera ("deep sleep") so when opening the camera a full "initialization" (i.e. error checking, etc.??) is done every time. According to the Application Manager however, the camera app is active and uses the system's Ram when the lag occurs!
Can anyone - under 5.0.1. - confirm this behavior?
Again, I am very grateful for any kind of help and suggestions!
How difficult is replacing the camera? Is it simple?
As the title suggests these functions won't work. Autorotate started working briefly but now it is still not functional. The hardware is fine, since testing the accelerometer with an app showed change in all directions. Suggestions?
at least give more details. what rom are you on? when did they stop working?
I am running marshmalux v2 with squid's kernel and xposed installed. I am not really sure when it started since my default set up is portrait mode. However a month or so ago when I tried to watch a video on yt the screen wouldn't rotate even though I had shifted to auto rotate. What is really puzzling is that camera rotation works fine.
EDIT: Flashed another ROM to check if the issue persists. It didn't help.
bump
So I have an update on my issue. Maybe it can help someone else but I have partially solved it. As I said earlier flashing stock didn't fix it. Even after frashing a complete factory image, the issue persisted. What seemed to remedy the issue was flashing non-stock based roms such as cyanogen. The gestures still don't work, but auto-rotation functions as it should.
I would be grateful if somebody has a suggestion. I really want to try spectrum ROM, which is stock based.
bump
Hi, anybody can help me, my yd201 proximity sensor not working, i did everything flashing all rom on the forum to try fix this but it still doesn't work. (from 4.+ to the latest MM) with all firmware. i just trying full unroot my phone on root apps then wanna clean system apps using twrp so am try deleting root forder from latest twrp to clean everything, now proximity sensor not working what ever i do rotate, calling, and the biggest problem is back screen is not working too,. download sensor test from the market is working too(device sensor hardware not support on this phone)
please help me what should I do.. if anyone knows where can buy motherboard for yotaphone please give me the link. tnks.
Dahlan abdullah said:
Hi, anybody can help me, my yd201 proximity sensor not working, i did everything flashing all rom on the forum to try fix this but it still doesn't work. (from 4.+ to the latest MM) with all firmware. i just trying full unroot my phone on root apps then wanna clean system apps using twrp so am try deleting root forder from latest twrp to clean everything, now proximity sensor not working what ever i do rotate, calling, and the biggest problem is back screen is not working too,. download sensor test from the market is working too(device sensor hardware not support on this phone)
please help me what should I do.. if anyone knows where can buy motherboard for yotaphone please give me the link. tnks.
Click to expand...
Click to collapse
Open the phone dialer and dial *#*#4636#*#* , if it doesn't work the first time try the code again and it should open the hidden testing menu, choose device test and you can manually test all the phones sensors to confirm if the proximity sensor is working or not. I had a s7 that did the same thing, the proximity sensor just quit working one day and I confirmed it wasn't working with this method. Good luck.
same result, not working too.
maybe problem is from hardware,
any idea on how to fix it, just something like using xposed or what?
Dahlan abdullah said:
same result, not working too.
maybe problem is from hardware,
any idea on how to fix it, just something like using xposed or what?
Click to expand...
Click to collapse
I just dealt with it, sometimes it would work and sometimes it wouldn't. There's an app on the play store that you can use for screen rotation, I ended up using that when I absolutely needed rotate the screen.
i dont care about rotation screen.. i just want the back screen working normally, if tap transfer button on color display it won't open it on epd screen when i rotate the phone..
I don't know if it happened the same with you, I own a YD206 so I am not sure how YD201 behaves, but there's a problem with proximity sensor that makes it working all the time, I have wrote a comment about it and will try to contact Yota about this, meanwhile it would be important for people that are not aware of this problem because is such a faint light to actually confirm if the same is happening to them, YD201 or YD206:
I discovered that I also have this problem, I was with the wrong radio, had to flash the Chinese radio and it suddenly appeared, this is what I have found I have an YD206, so I wonder how the YD201 behaves:
On YD206:
With wrong radio. radio (Russia xx versions) on YD206 , in KitKat or Lollipop ROMs the proximity sensor is OFF by default BUT, as soon you turn ON an app that uses it, it won't turn off again, it keeps blinking even if you force kill the app that started. However it will turn off if the screen is off, after 5 seconds after. Also it's important to acknowledge that 2G only with this radios fails. On Lollipop Wifi won't turn off automatically, just manually.
YD206 With the correct radio. radio S01_003_3034_CN1_M05 2G 3G (UMTS) and 4G (LTE) all work and with better reception, but as soon the screen is ON, the proximity sensor starts working, does not matter what app you have open, when you turn OFF the screen the proximity sensor will turn OFF in about 5 seconds. If you are using the EPD screen the proximity sensor will turn OFF faster than 5 seconds, but as soon you touch the EPD it will turn ON for 3 seconds or so. On Lollipop Wifi won't turn off automatically, just manually.
So the problem acts differently when you flash a different radio, I am not sure where's the bug comes from, but it seems there's also a bug with YotaRom. There's a Xposed module to disable proximity sensor in specific apps, I haven't tried that, I also would like to know how this behaves with the Marshmallow Beta.
(For the ones that are not aware of this problem, keep in mind that to see this problem you need to be on a dark place to see the very faint red light of the proximity sensor.)
Best regards,
This problem is also being discussed here: https://forum.xda-developers.com/yot...tive-t3520013/
I don´t know if it´s a coincidence or not, but I a few days after the update to Oxigen OS 3.6.1 I noticed that the proximity sensor and light sensor of my ONEPLUS 2 stopped working.
I used AndroSenor and Sensor box from the PlayStore, and both os them say thar the proximity and light sensors are missing.
I had a remote session with a ONEPLUS L2 specialist and they wiped my phone and reflashed the latest ROM (ver. 3.6.1), but the problem wasn´t solved..
I guess that, if the sensors don´t appear in the apps I mentioned maybe it´a a hardware problem, but I would like to hear more opinions.
If anyone has any suggestion to try to solve this problem before sending it to repair (out of warranty)??
flash persist.img from fastboot
backup all your info
in some cases it will help
hi there!
I seem to be having quite a similar problem, though, my sensors work, but stop responding after an unspecified period of time (can be anywhere between minutes and hours).
I tried flashing several roms (oreo, nougat) and yesterday i flashed Oreo Pixel Experience (just pure ROM+OP5 camera, no root no custom kernel just to rule out a few things) but the issue remains. Important to mention, i always clean flash.
The best way to describe the issue is: "sometimes the proximity and light sensor just stop working and i dont really know why" which is obviously causing a whole bunch of issues with auto brightness, making calls, picking up when someone calls etc.
The thing is, everything works after a reboot...but only for some time...then the sensors go "offline".
sometimes they work for a couple of hours, even a day...sometimes they die after half an hour or something. I have a feeling that i see them die faster when i have my phone in the pocket and leave it idle for a while, and when i use my phone often and dont really give the phone time to rest they live longer. It almost feels as if the phone goes to some deep sleep when idle for some time, disconnects the sensors, but doesnt turn them on again when woken up.
tried flashing the persist.img as advised just above, but it doesnt seem to have an effect.
anyone has any good idea?
thanks!
allright, being desperate from not being able to use my phone in a normal way i flashed OOS 3.6.1 from official zip files that can be downloaded from oneplus.net support section, using OP recovery and surprise surprise - sensors are working flawlessly! so im ruling out the HW problem. I think im going to stick to OOS for a while to monitor the sensors and eventually im going to try flashing oreo again.
ok, last update from my side: after two days on OOS where everything worked fine i flashed Pixel Oreo build and sensors continue working just fine! so, whoever is experiencing strange behavior of his sensors, i recommend the same approach.
Jackill said:
ok, last update from my side: after two days on OOS where everything worked fine i flashed Pixel Oreo build and sensors continue working just fine! so, whoever is experiencing strange behavior of his sensors, i recommend the same approach.
Click to expand...
Click to collapse
You still have working sensors?
I have exactly the same behavior as you mentioned in your first post. FRUSTRATING!
I've tried flash lineageos 15.1 ROM, no luck. New persist.img from official fastboot oos ROM but no luck either.
flaektrem said:
You still have working sensors?
I have exactly the same behavior as you mentioned in your first post. FRUSTRATING!
I've tried flash lineageos 15.1 ROM, no luck. New persist.img from official fastboot oos ROM but no luck either.
Click to expand...
Click to collapse
Hi! Yes, my sensors are still working just nicely.
Jackill said:
Hi! Yes, my sensors are still working just nicely.
Click to expand...
Click to collapse
So good for you ?
Before when your sensors struggled, did they also disappear from any sensor test app. Or did they just not work?
My prox sensor did not disappear but just hangs at 0 or 5cm if I check the value in any sensor app. And light turns 0 Lux also.
I've similar problem. Went completely stock as suggested but the problem persisted.
flaektrem said:
So good for you
Before when your sensors struggled, did they also disappear from any sensor test app. Or did they just not work?
My prox sensor did not disappear but just hangs at 0 or 5cm if I check the value in any sensor app. And light turns 0 Lux also.
Click to expand...
Click to collapse
Well mine didnt really "dissappear" either. They "froze" too. Lux froze at whatever value it measured the last however i am almost certain it was never exactly 0. Prox behaved the same as you describe: 0 or 5.
lazyfarmer said:
I've similar problem. Went completely stock as suggested but the problem persisted.
Click to expand...
Click to collapse
Interesting. I'm going to flash OOS recovery and latest OOS ROM later today and give it a try.
Jackill said:
Well mine didnt really "dissappear" either. They "froze" too. Lux froze at whatever value it measured the last however i am almost certain it was never exactly 0. Prox behaved the same as you describe: 0 or 5.
Click to expand...
Click to collapse
My lightsensor always freezes at 0 Lux. And when the prox freeze at 0 its impossible to quit a call. So f*cking frustrating so I have to fix this problem ASAP
I have the same problem with my LUX device, sometimes the sensors work randomly. When I reboot my phone the sensors stop working. The screen does not rotate, the most interesting thing is that it did flash the Moto camera mod and the rotation works perfectly with the camera, with the stock camera there is no rotation.
UPDATE:
I scheduled a remote session with Oneplus L2 Team and they performed a full factory reset of all partitions. No luck, problems still persist.
It must be a hardware problem.
In my case I sent the smartphone to them and they said it was a problem with the motherboard.