Hey,
I am currently running the 1.48 rom and the problem is sometimes when i wanna turn my HD2's camera on it says came couldn't be initialized (have to reboot to use it) the other problem is that some times the camera will not turn on the light the button gets grayed out for some reason. i HAVE NOT applied the came fix since it messed up the led light completely and not even 10 resets fixed it... when i last installed it.
Anyone has the same issue?
hi,
usealy the camera refuses to turn on the (flash)light when your battery is lower then xx%, i dont know the exact value but if you do a search here in the board you will find it.
for the crashes i cant help you out, but having a look into the various camera threads here may also be helpful.
regards mad
There are a few threads about the camera intitalisation already, and I believe I was the first to submit one. Anyway, I have recently found out the Opera 10 Beta strangely enough caused the issue. I havent experienced the problem since uninstalling it so....give it a try (assuming you installed Opera 10).
Hi all,
I have a i9500 phone.
I have this firmware installed onto my phone
I9500XXUEMJ5_I9500ODDEMJ5_I9500DDUEMJ5_HOME
2 days ago i got a push update, and then i updated my phone.
And then i see that automatic rotate isn't working, because the shealth walking mate wasn't counting the steps.
So i tried rotating my phone didn't work.
I did *#0*# to check the sensors and see that
Accelerometer sensor is showing 0 for everything
Proximity Sensor same
Barometer Sensor same
Light sensor working
Gyroscope Sensor same showing 0
Magnetic sensor same showing 0
I did a hard reset and didn't solve my problem, i then flashed the same firmware again and still didn't work.
Can you guys help me out?
Can't go to samsung tech since i didn't buy the phone their store and i'm from south america (Country Suriname) also
Wishaal said:
Hi all,
I have a i9500 phone.
I have this firmware installed onto my phone
I9500XXUEMJ5_I9500ODDEMJ5_I9500DDUEMJ5_HOME
2 days ago i got a push update, and then i updated my phone.
And then i see that automatic rotate isn't working, because the shealth walking mate wasn't counting the steps.
So i tried rotating my phone didn't work.
I did *#0*# to check the sensors and see that
Accelerometer sensor is showing 0 for everything
Proximity Sensor same
Barometer Sensor same
Light sensor working
Gyroscope Sensor same showing 0
Magnetic sensor same showing 0
I did a hard reset and didn't solve my problem, i then flashed the same firmware again and still didn't work.
Can you guys help me out?
Can't go to samsung tech since i didn't buy the phone their store and i'm from south america (Country Suriname) also
Click to expand...
Click to collapse
I tried to flash the latest version of arrow rom, and all the sensors worked for like 5 minutes then it stopped again.
I flashed the same rom again and same thing happening again.
Hi everyone,
I'm looking for some help about Proximity Sensors. Seems like there's a lot of discussion... but not many solutions.
I currently run CM10.2 on JFLTEXX (Samsung Galaxy S4). After a little while, my prox sensor crapped out and stopped working. I tried disabling from sensors.so file, but i ended up disabling all my sensors (accellerometer, light sensor, etc). I tried taking it apart and cleaning it but that only worked for a few weeks. I've ALSO tried the recalibration and resetting echo 0 and echo 1, but that doesn't work either. I know you can keep the screen on during calls via option, but Skype messes up too and other apps.
I am on one last solution before giving up on this ROM (or phone...). I am trying the Hardware Disabler app but I need to know which driver is the driver for Proximity Sensor. Here's the list:
- 21-0030 under /sys/bus/i2c/drivers/an30259a/
- 17-0077 under /sys/bus/i2c/drivers/bcm2079x-i2c/
- 16-0020 under /sys/bus/i2c/drivers/cypress_touchkey/
- 12-0025 under /sys/bus/i2c/drivers/dummy/
- 120048 under /sys/bus/i2c/drivers/dummy/
- 13-006c under /sys/bus/i2c/drivers/ice4/
- 4-003e under /sys/bus/i2c/drivers/jc/
- 12-0066 under /sys/bus/i2c/drivers/max77693/
- 7-006a under /sys/bus/i2c/drivers/s5k6b2yx/
- 11-0036 under /sys/bus/i2c/drivers/sec-fuelgauge/
- 9-0064 under /sys/bus/i2c/drivers/sii8240_cbus/
- 9-004d under /sys/bus/i2c/drivers/sii8240_disc/
- 9-0049 under /sys/bus/i2c/drivers/sii8240_hdmi/
- 9-0039 under /sys/bus/i2c/drivers/sii9240_tmds/
- 9-0059 under /sys/bus/i2c/drivers/sii8240_tpi/
- 2-0081 under /sys/bus/i2c/drivers/ssp/
- 3-0020 under /sys/bus/i2c/drivers/synaptics_rmi4_i2c/
Which one of the above is the proximity sensor driver?
Really would appreciate the help. I know a lot of other people are looking for this kind of information and did a ton of Google search before I came to post here.
THANKS IN ADVANCE.
J
http://forum.xda-developers.com/showthread.php?t=1658474
My first time here posting, I'm sorry if it's duplicate or in the wrong place ... thanks
Good night people
I want to take advantage of the topic to report the same problem that the comrade had over there
Handset: galaxy s5 g900m
Rom: mashmalow
Date 2017-01-25
In the beginning I thought it was a hardware problem, but before sending for assistance, I can see that with some moves the accelerometer and the gyroscope come back to work for a few moments. First thing was to give hard reset, I realized that the accelerometer and the gyroscope worked, but the moment the screen goes into standby it stops working.
The second attitude was to lock the phone in safety mode, the accelerometer and the gyroscope worked, but the first standby it stops working ..
Third was to pass roms stock, customized CM MIUI, same situation occurred the accelerometer and the gyroscope worked, but the first standby it stops working.
I gave a few beats on the back of the phone, the same thing happened after restarting.
I deleted folder data / etc / sensor, the same thing happened but the first standby it stops working.
****But today I did something that made me sure that the problem is softwere, with the rooted stock rom I installed a custom kernel, phonix kernel, then the accelerometer and the gyroscope worked perfectly, it worked even after returning from the standby, for about 3hr The cell worked very well, but upon receiving a connection the accelerometer and the gyroscope stopped working and when using test sensors dialing * # 0 * # fixed values where it says accelerometer and the gyroscope
Now I stopped messing with my cell phone.
I hope this information can help our team find a solution.
I downgraded to 5.0, and it did not solve...
This connection problem after the updates ...
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.