Nexus 4 Sensors not working after operating system update - Nexus 4 Q&A, Help & Troubleshooting

I hope this helps others save time looking for a solution to the sensor problem on the Nexus 4. The 4.2.2 operating system is the last one that allows these sensors to work.
These sensors stopped working when my system updated from version 4.2.2:
Orientation: Qualcomm v1
Accelerometer: LGE Accelerometer Sensor v1
Gyroscope: LGE Gyroscope Sensor v1
...and these sensors are not affected:
Light
Sound
Proximity
Pressure
Magnetic
I have used the custom ROMS for Ver. 6 and above, Chroma, Cyanogen, Pure, ASOP and others and the sensors are still not working.
I reinstalled the factory image 4.2.2 and the sensors worked fine. I then incremented updates through the phone from 4.2.2 as follows:
Jelly Bean 4.1 - 4.3.1
KitKat 4.4 - 4.4.4
Lollipop 5.0 - 5.1.1
and the sensors did not work.
I have installed the factory images for all the updates directly to the phone and after 4.2.2, the sensors do not work.

Based on my experience with the Nexus 4 and Nexus 5, this is an indication of a hardware problem.

audit13 said:
Based on my experience with the Nexus 4 and Nexus 5, this is an indication of a hardware problem.
Click to expand...
Click to collapse
Thanks audit13, I have reinstalled the factory image 4.2.2 and all the sensors are working fine.

Related

GPS issues on custom roms.

I've recently moved to a new state and have been having to use my phone's GPS several times a week.
At the time I was using one of the Cyanogenmod 11 snapshot builds(sorry, I can't remember which one ). The GPS worked flawlessly. I would always update to the next snapshot build as they came out. One our two updates later my GPS couldn't seem to get a fix on my location. I tried wiping and doing a clean install of the ROM. Still had issues.
Eventually I got fed up with cyanogenmod and wiped my phone and installed Paranoid Android 4 beta 1. Had the same problem with the GPS. I tried several of the other beta releases as they came out to see if the problem was resolved. It wasn't.
So I restored my phone to stock using the Google factory images (4.4.2). The GPS worked beautifully. So I stuck with stock for a while and did the OTA update to 4.4.3.
After a while I started to miss the features and customizations that come with custom ROMs. So I wiped and flashed Paranoid Android 4.4 RC2. The GPS still can't seem to lock. On the rare occasion that it does it can't keep up with my car, especially if I turn onto another road.
Does anyone know what's up with the GPS? Didn't seen to have this issue at all on Jelly Bean custom ROMs. Is this an issue with Kitkat custom ROMs? Possibly a hardware issue? Any help would greatly appreciated.
Current setup:
Phone: Nexus 4(16gb)
ROM: Paranoid Android 4.4 RC2
Sent from my Nexus 4 using XDA Free mobile app
There appears to be an issue with KitKat and GPS. I'm running stock 4.4.4 and I can't get a GPS lock. I've tried everything I can, including a factory reset. I don't remember having the issue with 4.4.3, but I've seen issues reported going back to 4.4.2.
I don't know about you, but a reboot usually does it for me.

[Q] Problems with Sensors - Carbon ROM

I flashed a clean install of the latest carbon nightly on my LG G2 (D802 intl.). I also used latest gapps (2014 06 06)
and encountered a problem with the phone's sensors (proximity sensor, light sensor, accelerometer, gyroscope sensor, compass, etc.).
More specifically none of the sensors worked, and applications which use them gave a toast instructing me to enable them.
It is important to note that this does not happen on the older 2014 05 28 nightly therefore any hardware problem can be ruled out.
Did anyone else encounter a similar problem? Any solutions...?
device: LG-D802
build: not sure (used this zip CARBON-KK-NIGHTLY-20140629-0917-d802.zip)
kernel: not sure

SlimKat 7.0 no rotation no brightness sensor

Hi,
Since build 5.10 rotation and light sensor are broken eventough I flashed the latest kk modded modem from this website. I would like to know if someone with a D800 and SlimKat over 5.10 have those two things working.If someone could post this in the SlimKat thread in development section which I cant as it needs more than 10 posts I would be thankful.
Thanks
Software forced rotation works but automatic rotation doesnt, its the position senser thats not working.
Maybe he has moved to new sources have you tried flashing stock kitkat modem at all as this is the obvious choice to me?!
Ok, I flashed the modded kk modem from xda thread from 4 april made to fix rotation and it didnt work. Now guess what? I did what you said and flashed original LG modem found somewhere in the 20 spet 2013 thread and everything worked! I wonder which one is newer.
Thanks!
Glad you're sorted. The stock kit Kat one is newer the modded one is just recently modded not created.
Sent from my LG-D802 using Tapatalk

Note 3 (N9005) auto rotation does not work for any CFW

Dear Community,
I hope that this is the right place to post and any of you can help me.
My (aktual) Hardware/Software bits:
Galaxy Note 3 (SM-N9005)
Android: 5.1.1
Baseband-Version: N9005XXUGBOD3
Kernel-Version 3.4.108-f2fs-temasek-cm12.1-hlte-v1.25+
temaseksnappy #1
Temasek unofficial version V16.4
Build: LMY48J test-keys
Recovery: twrp 2.8.7.0-hlte-4.4
My actual problem is the following: My Note 3 by default had a 4.4.2 OFW on it, which I early upgraded to Lolipop 5.0.1. Everything works for the OFW 4.4.2 and 5.0.1 fine. As soon as I try to flash it with a CFW like CM11, CM12, CM12.1, CM12.1 (temaseksnappy), Gummy 4.4.4 I am losing the feature of auto rotation.
Of cource I did a clean flash, wiping DALVIK/CACHE/DATA and system, double time even one befor the flash, one after.
I also tried to put the battery, sim and sd out for few min before rebooting, while autorotation is manualy turned off.
Even a MODEM I flushed to fix this issue, but without success. Nothing helps but going back to OFW.
My last try was downgrading to the original 4.4.2, including baseband trieing from there to go to any CFW (CM11) as well as from OFW 4.4.2 -> OFW 5.0.1 -> CFW 5.1.1 (http://forum.xda-developers.com/galaxy-note-3/development/hlte-spr-vzw-temaseks-unofficial-t2953375)
There was also a post about a possible missing or broken lib in /system/lib which I replaced
Nothing helps (libGNU... something). This helped me alreay once in OFW after kicking out all the junk apps, but this is a different storry and not related anyhow.
Is there anybody out there who has the same problem or even better knows a solution?
My shot would be that:
1) CM has a problem with my particular hard-/software (Kernel, Baseband, Recovery, whatever) as I just tied CM or at least CM based CFWs.
PLEASE HELP.
Thank you very much in advance.
After about almost a year I cam back, giving again a try to CM, However I still have the same issue. Finally Anybody please!
Do you have the same issue with touchwiz 5.1.1 and 6.0.1?. Not the cm/aosp roms which aren't samsung based.
Sent from my SM-N920C
Rosli59564 said:
Do you have the same issue with touchwiz 5.1.1 and 6.0.1?. Not the cm/aosp roms which aren't samsung based.
Sent from my SM-N920C
Click to expand...
Click to collapse
Hello,
Thx for your reply. Right now I am on CM13 (temasek hlte v9.6)
http://forum.xda-developers.com/galaxy-note-3/development/hlte-spr-vzw-temaseks-unofficial-t2953375
This might should be specially compiled for sm-n9005 like mine.
Everything expect rotation works fine. However The accelleration is also working fine as I tested with "sensor test". Even the integrated camera App is rotating, however the rest is not.
In addition I downloaded "adaptive rotationfree", If I set it "stock Auto" nothing happens, but if I set it to "force auto" the rotation will work exacly once and then stops undtil I force it to portrait again.
What do you mean exactly with "touchwiz"? Is this jus a different kernel or a whole CFW?
As I wrote in the frist post I tried already a lot of CFW and ALL had this issue, but the OFW ;(
What shell I flush to get this working, which is not OFW?
BIG THX for YOUR HELP
Touchwizz is the firmware that comes with the stock Samsung firmware .
Also in custom Samsung based roms .
Hello,
thx for the tip with TouchWiz vs aosp. At the moment I am running "DarkLord N5 Release Candidate 2.12" which can get find here: http://forum.xda-developers.com/galaxy-note-3/development/rom-darklord-s6-port-alpha-t3083087
This Rom is TouchWiz Based and guess what ....
Autorotation works.
However I do not understand what the problem realy is and would prefer to run cm13 insteat. I mean even samsung devices got a accellerator within which works also fine with AOSP software, showing numbers moving while turning the phone. In addition for example on the post http://forum.xda-developers.com/galaxy-note-3/development/hlte-spr-vzw-temaseks-unofficial-t2953375 it is said that this is explicite for note 3 including the model n9005. So ...
Can anybody point me to the problem or even better to the fix?
Is there any chance CM would fix this?
Regards

LG VS980 Sensors not working

Hi,
I recently flashed Resurrection Remix on my G2 after I had some issues with the stock ROM. I got most of the issues worked out, but I can't seem to get any of the sensors to work. I've tried recalibrating them with several apps, but none have worked. I've also tried reading the values with several sensor reading apps, and in Sensors Multitool, it displays sensors for the proximity, gravity, linear acceleration, rotation vector, step counter, and gps sensors, but no values are displayed, just "--". Are there any other troubleshooting steps I should take, or any potential fixes?
Thanks in advance!
Josiah
*EDIT*
I reflashed the stock Lollipop rom, and the sensors still reported no value. I'm not too experienced, but the only thing that I can think of that could cause the problem is the hybrid bootstack I installed before flashing RR (like it said in the instructions). Anything I'm missing?
Device: LG G2 VS980
ROM name: Resurrection Remix
ROM version and base 6.0.1_r66 - MOB31E
kernel version and its settings: 3.4.0-perf-ge62e8d2 [email protected] #1
any mods applied on top of it: None
flashing "style" aka dirty or clean: Clean

Categories

Resources