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
Related
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
[Case history]
I've been using CM11 for quite a while and one day I messed up. I installed a Kernel that wasn't compatible with CM11 and I couldn't boot the phone. So I used ADB to push a CM11 ROM and flashed it using TWRP and it was fine...until...
I found that all my sensors were not working....well not all, but 'all'. Please let me explain.
I noticed that Rotation doesn't work anymore; I noticed that Auto Brightness would not work anymore; I also notice Accelometer wouldn't work.
So I downloaded the app 'Phone Tester', and I went to the 'Sensor' section and there was nothing detected there! No sensors at all.
However, I have this cover for my phone and when I cover the phone the screen will go out --> I assumed that means the proximity sensor works? I also noticed that the screen will blackout when I am on a phone call.
[My question]
I searched a bit and had two speculations.
1.) Baseband/Modem problem? --> I tried flashing the KK Modem for D802 and it didn't fix the problem
2.) Kernel problem? --> I think this is quite possible...but didn't flashing the ROM = flashing in a Kernel?
Any help is appreciated!
If I were you I would flash it back to stock and see if they work then
sent from my T-Mobile LG-VS980
herman925 said:
[Case history]
I've been using CM11 for quite a while and one day I messed up. I installed a Kernel that wasn't compatible with CM11 and I couldn't boot the phone. So I used ADB to push a CM11 ROM and flashed it using TWRP and it was fine...until...
I found that all my sensors were not working....well not all, but 'all'. Please let me explain.
I noticed that Rotation doesn't work anymore; I noticed that Auto Brightness would not work anymore; I also notice Accelometer wouldn't work.
So I downloaded the app 'Phone Tester', and I went to the 'Sensor' section and there was nothing detected there! No sensors at all.
However, I have this cover for my phone and when I cover the phone the screen will go out --> I assumed that means the proximity sensor works? I also noticed that the screen will blackout when I am on a phone call.
[My question]
I searched a bit and had two speculations.
1.) Baseband/Modem problem? --> I tried flashing the KK Modem for D802 and it didn't fix the problem
2.) Kernel problem? --> I think this is quite possible...but didn't flashing the ROM = flashing in a Kernel?
Any help is appreciated!
Click to expand...
Click to collapse
it is a baseband issue, as you know cm has not incorporated the lg kk changes which means that the kk baseband would not work you have to flash the d802 jb baseband and you will get sensors working again
XxZombiePikachu said:
it is a baseband issue, as you know cm has not incorporated the lg kk changes which means that the kk baseband would not work you have to flash the d802 jb baseband and you will get sensors working again
Click to expand...
Click to collapse
Thanks! I flashed the JB Baseband and it actually worked!
Hello everybody,
I have a Galaxy S5 (G900F) running on CM13 6.0.1. My problem is that wheter the auto rotation, nor the auto screen brightness works at all. I already had the same problem on CM12.1, I don't know exactly when it happened, so I can't tell if the issue originated due to an update. However, all of the sensors except the thermal sensors are not working. In CPU-Z You can only see the thermal sensors that are fine, the other sensors are blank. I already did factory resets, installed an older backup (not exactly sure if it was still working there), I only didn't install a complete new (stock) rom. I just went from CM12.1 to CM13.
Thanks in advance and happy holidays to You guys
]
im having the same issue.mine started when i flashed marshmallow.so im gasing its a software issue.
Sensors test.apk show the proximity sensor like 'near' or '0cm'
I try with different apk for fix/reset or calibrate it and all of them was unsuccessful.
¿What can i do?
The mobilphone is an Redmi 2 (813).
I tried it with cm13 temasek and CyanPop... both cases doing clean install.
Time ago i saw a method to recalibrate the sensor. It's consist in change values from different archives with an file manager.
(Sorry for my english)
PD: With original ROM all is fine.
hiiiiiiiii!!!, im here
Thanks for no help.
I install cm12 and all works fine
Pls help... If I cover my phone's sensor the screen turns off..even during playing games or videos if my finger covers the sensors... Currently my room is CyanogenMod 13.1 20160417 snapshot ZNH2K
Hello everyone!
So I'm having this weird issue where the camera/flashlight all of a sudden stopped working one day (didn't make any device changes) but it had happened occasionally and all I needed to do was clear dalvik/cache and it would be fine regardless of Lineage version. Now that solution no longer works. I just flashed both stock Nougat and Oreo firmwares to see if it was a hardware issue and the camera works perfectly fine. It's just on Lineage that it all of a sudden won't work (tried clean installs of 14, 15.1, 16 and now 17) and none of them have a working camera so I wanted to get you guys' input on what it could be.
Basically tl;dr
Lineage = camera/flashlight not working
Stock nougat/oreo = camera works perfectly
iTzFeRReTTi said:
Hello everyone!
So I'm having this weird issue where the camera/flashlight all of a sudden stopped working one day (didn't make any device changes) but it had happened occasionally and all I needed to do was clear dalvik/cache and it would be fine regardless of Lineage version. Now that solution no longer works. I just flashed both stock Nougat and Oreo firmwares to see if it was a hardware issue and the camera works perfectly fine. It's just on Lineage that it all of a sudden won't work (tried clean installs of 14, 15.1, 16 and now 17) and none of them have a working camera so I wanted to get you guys' input on what it could be.
Basically tl;dr
Lineage = camera/flashlight not working
Stock nougat/oreo = camera works perfectly
Click to expand...
Click to collapse
Ask in the specific Los thread, theirs numerous camera issue discussions
Sent from my LG-H910 using XDA Labs