I just installed: cm-13.0-20160819-SNAPSHOT-ZNH5YAO0IN-bacon.zip and my proximity sensor dont works.
I google it and i installed by TWRP this modem: XNPH44S (11/07/14): https://www.androidfilehost.com/?fid=95784891001607675
that fixed me this problem some builds ago, but now dont works, im having this issue since 5 days and i search most of sites to found solution and didnt work.
Any solution to fix?
Fixed: I uptaded TWRP to lastest version and worked now
Related
Hi all,
Got my OnePlus One last week. It's a Chinese version that comes with ColorOS. I immediately tried to flash CM11 nightly onto it after I checked the phone is working.
For some reason I thought I could flash CM11 directly, and so the first thing I did was installing TWRP 2.8.0.1. Then, I copied CM11 zip in to /sdcard , booted to TWRP recovery, wiped all partitions (including System) and then flashed CM11. In hindsight, I believe it was the wrong way to get CM11. I could have wiped something really important (sensors drivers?) when wiping System.
Initially, CM11 nightly seemed to work OK. Then I noticed the Auto-Rotate is not working at all. I installed CPU-Z and *gasp*, there's not a single sensor listed in the CPU-Z Sensors tab!
I spent hours today trying various methods (flash CM11S, flash ColorOS, flash /persist, /reserve4 partitions). However, the sensors are still dead! Besides auto-rotate, I think auto-brightness, proximity sensors are all dead.
Is there any way to get the sensors working again? Your help is much appreciated!
Try http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 and see if your sensors work after restoring to factory images.
Someone else said only twrp 2.7 is supported for opo, another guy had similar device breaking problems with 2.8.
I'm using TWRP 2.8.0.1 and have no problems. TWRP 2.8 had problems, but 2.8.0.1 resolved them.
Thanks a lot for the quick reply, zephiK! I've run flash-all.sh and I'm in CM11S now.
CPU-Z no longer shows an empty Sensors list! however, only the following 4 sensors have readings:
AK8963 Magnetometer
AK8963 Magnetometer Uncalibrated
TMG-3993 IR_Gesture & Proximity
TMG-3993 Ambient
No readings for the rest...
Does auto rotate work? I'm not really sure how your sensors disappeared in the first place, its very odd.
/system is wiped on every ROM flash anyway so that's not the reason. Glad it's working better at least. Any more issues with the sensors other then some not showing?
Nope, the auto-rotate is still not working.
I've just rebooted CM11S, and... the Sensors tab in CPU-Z became empty again! This is very strange indeed...
I think t is a kernel problem,
Maybe you van flash the original boot.img
Rebooted again. The list of sensors are showing in CPU-Z again, and the same 4 lines have readings (AK8963 Magnetometer, TMG-3993). Still no auto-rotate.
My gut feeling is that there is a low level corruption in one of the "special" partitions. By special I mean the ones that are there but not included in any of the ROMs or factory images. Unfortunately, I don't have a NANDROID backup to restore from (Huge mistake on my part).
Is there a way to download an NANDROID image containing those special partitions?
@gurby1, I thought about kernel problem too, but I've tried flashing many ROMs and kernels:
CM11S 33R
CM11 Nightly 20140296
Franco Kernel r20
ColorOS 2.0 beta
ColorOS 1.2
and the results were the same - broken auto-rotate.
Bump. I'm still looking for a full partitions dump of the OPO.
Something similiar to this one for LG G3: http://forum.xda-developers.com/showthread.php?t=2766437
DecemberNexus said:
Bump. I'm still looking for a full partitions dump of the OPO.
Something similiar to this one for LG G3: http://forum.xda-developers.com/showthread.php?t=2766437
Click to expand...
Click to collapse
Hello,
Did you find a solution ? I have exactly the same issue as you. It even worst, I don't see any sensor on my device. I have installed many ROMs without any success. I hope it is not a HW problem
Thanks.
Guys.. I also have this issue..
Glad if there any solution on this...
Same problem
Guys any solution yet? I'm getting annoyed by this so much.. Please post here if u have found any solutions. Thx.
I also have the sensor problem which is all sensor is "not supported" in antutu and empty in CPU-Z sensor tab. I fixed it by flashing the persist.img from this thread http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
I know it's a very old topic, but was someone able to recover the non working sensors? It's hard to believe it's a hardware issue, as the proximity sensor should be completely separate from the e.g. accelerometer...
Tried flashing all .bin files via fastboot with no luck...
Dzhedaj said:
I know it's a very old topic, but was someone able to recover the non working sensors? It's hard to believe it's a hardware issue, as the proximity sensor should be completely separate from the e.g. accelerometer...
Tried flashing all .bin files via fastboot with no luck...
Click to expand...
Click to collapse
Have you try flash the persist.img?
TheDynamiteGuy said:
Have you try flash the persist.img?
Click to expand...
Click to collapse
Tried flashing everything, modems, persist.img, etc. Nothing helps, so seems something is toast in the hardware...
Hi , i've updated my Oneplus one to official Cm12s.
My screen wont wake up when call comes , i have to double tap / press power buttom in order to see call screen.
Its happening specially when sensor is coverd or phone is in my pocket.
I've tried many diffrent solutions like flashing old 11s modem , new alpha lollipop modem , cm12s proximity fix zip , cm12s extras zip but nothing works !
So i attempted to create this thread , please help if you know how to solve it !
Thanks
Try flashing the latest Lollipop modem:
http://boeffla.df-kunde.de/bacon/modems/Full-YNG1TAS0YL-modem-flashable.zip
Transmitted via Bacon
I am having an issue with my proximity sensor not working at all. The phone goes blank during a phone call and I cannot wake it up until after the call is over.
I am using an unofficial nightly build for CM11 from a few days ago. This was a recent downgrade from the recently released official CM12.1 nightly because I was not pleased with it's stability.
I used an app to see the sensor values and the light sensor works while the proximity reports nothing. Which modem should I try to flash for CM11 to try to get my sensor back?
I read the proximity sensor and the light sensor are the same hardware unit. Is this true? Or is there a chance I have to warranty my phone?
IAmTheRobin said:
I am having an issue with my proximity sensor not working at all. The phone goes blank during a phone call and I cannot wake it up until after the call is over.
I am using an unofficial nightly build for CM11 from a few days ago. This was a recent downgrade from the recently released official CM12.1 nightly because I was not pleased with it's stability.
I used an app to see the sensor values and the light sensor works while the proximity reports nothing. Which modem should I try to flash for CM11 to try to get my sensor back?
I read the proximity sensor and the light sensor are the same hardware unit. Is this true? Or is there a chance I have to warranty my phone?
Click to expand...
Click to collapse
You need to flash a KitKat modem, this is the latest:
http://boeffla.df-kunde.de/bacon/modems/Full-XNPH05Q-modem-flashable.zip
Transmitted via Bacon
Fixed! Thanks.
IAmTheRobin said:
Fixed! Thanks.
Click to expand...
Click to collapse
No worries.
Transmitted via Bacon
Help
Is it possible to flash the modem with cm (stock) recovery? My device is not rooted (bootloader locked).
I'm on cyanogen os 12. (ota update).
.::[email protected]::. said:
Is it possible to flash the modem with cm (stock) recovery? My device is not rooted (bootloader locked).
I'm on cyanogen os 12. (ota update).
Click to expand...
Click to collapse
No, you need a custom recovery. Just unlock your bootloader, simple. It really should be unlocked anyway, you'll be screwed if you get into trouble and need to flash the stock images, because it's at that time that the unlock command won't work, and then you can say bye bye to your phone.
Transmitted via Bacon
Not fixed !
Isuue remain same
Sent from my A0001 using XDA Free mobile app
Proximity sensor not working
I'm on COS12 and my proximity sensor isn't working as well.
Tried reflashing the rom (not clean install but just reflash), and wiping cache and dalvik, but no luck
Also tried the oxygen modem, it gave me no result either...
What should i do now
timmaaa said:
Try flashing the latest Lollipop modem:
http://boeffla.df-kunde.de/bacon/modems/Full-YNG1TAS0YL-modem-flashable.zip
Transmitted via Bacon
Click to expand...
Click to collapse
I downloaded the sensor app and it did show that the proximity sensor was not working.
1) Flashed full CM modem, proximity fixed, no text/notifications on wifi. I know because I sent text with a different phone through WIFI, nothing popped up. I turned off WIFI and I get the texts.
2) Flashed 12.1 CM, same behaviors as above.
3) Flashed back to Team Nocturnal's 5.1.1 build, still same result.
4) I flash CM11 05Q modem, I get notifications/text on WIFI, but the other end is I get the proximity sensor issue; phone doesn't turn off while on a call and it activates the screen.
Still no solution or fix. Just FYI I am an at&t customer on the west coast.
I've some issue related to yours with proximity, but before trying to flash with new firmware - want to ask some people who know more about this than me.
My proximity sensor works good, screen disables during calls, enables while I've put my phone away an ear, BUT it stops working in random situations. I'm using an option to prevent phone unlock with proximity sensor, but phones somehow wakes up in my pocket. After restart all backs to normal. So I think it's not HW related issue as proximity sensor works. Do you think that changing firmware might help?
I'm on latest COS12.1S ROM (updated to second OTA). On COS12S all works good with disabled ambient display option, with enabled same issue. On COS12.1S tried to disable ambient display but no success.
Hey...
Just got a new OnePlus One from the box.
i got him with cm 11s 4.4.4 .
Everything worked just fine...
After updating to CM 12S or CM12.1 or OxygenOS 1.0
The screen doesn't go off during calls..
It really annoying and i wonder how to fix that.
Update :
Tried to flash old modem like the 44S and still doesn't work.. what should i do?
I'm running nighly CM 12.1
You need to flash a Lollipop modem, not KitKat. Have you tried that?
i have been installed 5.0.2 modem...
doesnt work... if i install 5.1.1 proximity work , but gyroscope doesn't work...
update , after installing all types of modems.
44S
and Oxygen OS 1.0 modem
and 5.0.2 CM12S
And 5.1.1
Still nothing...
I found one file on XDA that "fix" the problem and indeed it has fixed it but
after installing that the gyroscope and rotation on phone stopped working...
In the same boat, I'm in stock CM12 5.0.2 and both proximity sensor and gyroscope are not working. Any help ?
My Mate 9 was working until yesterday. I flashed a modified boot image and the fingerprint sensor seems to have been bugged almost. Even after receiving help and flashing the stock boot image, the sensor still doesn't work. Has anyone else had this problem and if so, what's the solution?
I saw u had the exact same problem with me could you able to solve it?
HELP! My gyroscope isn't working after lineageos for microg 19.1 OTA update.
Okay so I installed lineageos for microg (19.1), everything worked (so my gyro too). I got an OTA update, I installed it (everthing went correctly), but later I found out that my gyro doesn't work. I tested some apps that check for a gyroscope and test it, but nothing it even said I didn't have a gyroscope. Does someone have a solution?
I'm on the SM-A525F/DS
this is the lineageos version: 19-20220906-microG-a52q
Build number (if that's important): lineage_a52q-userdebug 12 SQ3A.220705.004eng.root.20220906.041544 dev-keys
(oh and I also used the LOS recovery for the version I was on originally and installed the newer version when I did the OTA update (via the wizard))
Someone please help, I can't find this problem anywhere else!
If you need any more info, just ask.
in pedestrian mode in google maps does not work ? right ?
masterchapter said:
in pedestrian mode in google maps does not work ? right ?
Click to expand...
Click to collapse
I don't have google maps, because I have a degoogled phone (so with MicroG). But if it uses the gyroscope than yes it doesn't work, it doesn't recognize in any app I did multiple tests and it doesn't work in any app. It just feels like the developers of LineageOS accidentally deleted the part of the gyroscope in the a52q build. I don't know, do you have an answer why this happened? The lineageos build before this worked just fine but after the update the gyroscope doesn't work anymore
UPDATE: INSTALLED THE NEW UPDATE AND IT STILL DOESNT WORK
I FIXED IT! Just reinstalled the persist image from the stock rom via odin to my phone