Hey all,
My T-Mo G2's light sensor is stuck at value 219 and I can't figure out why, or how to fix it. It used to work before I flashed a radio, but even though I've tried flashing back, nothing seems to "unstuck" it.
Here's what I've tried:
- Full data/cache wipe
- Factory reset
- 4 different radio images (currently using the latest TMOUS radio from here: http://forum.xda-developers.com/showthread.php?t=970809)
- CM 7.0.3
- CM 7.1-RC1
- CM nightly 144
- Wiping EFS
If I open up Sensor Test, it shows my light sensor (CM3602) permanently stuck at 219.0. There are 2 other values, both of them at 0.
My proximity sensor works - it's 9.0 when nothing is there, 0.0 when I move my finger over it.
It's certainly not the "input" either - I have tried reading in pitch black and in direct sunlight, it's always at 219.0.
Any suggestions on how to fix this? I'd ask in the radio thread but being a new poster I don't have the permissions to post there yet.
Here's the specs on what my phone is running right now:
- HBoot 82.0
- Radio 12.52. 60.25_26.08.04.30
- Cyanogen nightly 144
Turns out that turning off auto brightness makes the sensor work again. I guess that makes it a Cyanogen issue, so I'll go file a bug there.
Related
Anyone else have the camera load to a blank black screen with no buttons in any and all apps that utilize the camera? Camera, Barcode Scanner, Sniper Shot, and all other programs that use the camera fail to load since the update. Anyone have any idea as to why?
DanielWGK said:
Anyone else have the camera load to a blank black screen with no buttons in any and all apps that utilize the camera? Camera, Barcode Scanner, Sniper Shot, and all other programs that use the camera fail to load since the update. Anyone have any idea as to why?
Click to expand...
Click to collapse
Did you try a restart, I have heard of camera problems like this before (i think first FroYo update) and all it needed was a simple reboot.
Reboot didn't work. I reflashed the rom and BAM, it worked again. Crisis averted.
I have the same problem.
I'm running the following:
Azreal 3.0
circular battery widget update
removed HTC lock screen
superior battery charging kernel
wifi hotspot patch
I'm currently trying things to figure out what will fix it.
Here are the current things I have tried that did NOT fix the problem:
Reboot
Wipe cache/davlik cache
fix UID mismatches
I then reflashed azreal 3.0
At this point the camera worked again but everything was wiped. I then reapplied the following patches:
Circular battery
remove HTC lock screen
wifi/hotspot patch
after this everything continued to work
I then applied:
superior battery charging kernel and it broke again
I think the problem is the superior battery charging kernel
i am having the same problem and have not been successful yet fixing it. switched from cm7 back to stock to update my prl and tryed to use the camera while stock when the black blank screen happened. flashed to evdo(sense) and same result. flashed back to cm7 and the 1st time i opened camera it opened the ffc. when i tried to switch and everytime i have tried to open it since i get "camera error cannot connect to camera" help plz!
If you have HW 0004 phone or HW003 with the new camera, you have to make sure your rom has a kernel with the NEW drivers. The kernel in my signature has the new drivers for ASOP roms (like cm 7).
just flashed Savaged-Zen-V002-CFS-HAVS-SBC-WiMAX - GB.zip
with the same result running cm7. seems like ive tried 20 different things with no success. everything i have flashed has been off my sd meaning i have had all of it running before at one time or another with no problem. i really cant think of what ive done new to have caused this
Same here
Happened to me right after I flashed calkulins_format_all.zip and then the MikFroyo4.4.zip yesterday. I thought it was a problem with mikfroyo so I flashed Azraelz 3.1 and still the same issue (i was using azrael 3.0 with no prob prior to mikfroyo).
I'll post if I find anything that works, please also give any suggestions i'm willing to try anything b4 i take her to sprint.
I also flashed calkulins evio rom. When I flash back to stock it will start running again sometimes. Not even right away though. It will be black for a while then if I just let the phone sleep for a bit and come back to it bam. Camera again. For a little while. Then back to the same thing an hour later without doing anything! This is very frustrating! Someone plz help!
Sent from my PC36100 using XDA App
UPDATE
I turned my phone off and switched SD cards to one that has an old backup (3.29, kernel#11), when I booted into recovery, I could hear clicking noices coming from the lens, at a super fast rate (say 2-3 clicks a second).
Not wanting to do any more damage I turned off the phone.
I did just take my phone to sprint to fix my kick stand, maybe they did something to mess with me (thats just my paranoid side speaking)...
But what gives? What would make the camera shutter do that while im in recovery (btw using latest amon ra recovery)?
I don't know if this issue is realted to the ARHD Rom i've installed but since a couple of versions (I'd say since 5.2, but im not sure and yes i did a fullwipe and the right radio) Auto Brightness and the backlight for the home, menu, back and search key stopped working.
I did some research and figured out my sensor is working (tried with GPS Status).
I didn't try to go to an older rom yet, because i want to use the up to date one.
Any sugesstions for a fix?
Greetings
Snowdragon
Am I the only one experiencing this Problem? No fix?
Hey all,
About a year ago I got a new DHD everything was working fine. I rooted it (using visionary), tried cyanogen mod, went back to the original sense/frayo backup and finally installed a new kernel (Buzz)...
After that my proximity sensor stopped working, I kind of just put up with it because I was busy at uni, I just got used to manually turning my screen off. I thought it was something to do with the kernel and/or backup I was running. Since then I have installed Android Revolution 6.3.1 with new kernel and radio and thought it might just start working again but it hasn't...
My question then is:
Could I have done something to affect it while flashing/rooting e.t.c?
Is there any way I can check?
Is it likely to be a hardware failure? (the phone was less than a month old when it stopped working)
oh and I have tried Proximity Re-calibrator and it dose nothing (Unless it doesn't work with ARHD 6.3.1).
Thank you for your time.
This is a common problem. It's in the faq of the ARHD rom and the answer is:
http://forum.xda-developers.com/showthread.php?t=951858
SuLuke said:
This is a common problem. It's in the faq of the ARHD rom and the answer is:
http://forum.xda-developers.com/showthread.php?t=951858
Click to expand...
Click to collapse
I have tried and tried Proximity Sensor Recalibrator.... no change.
What did you do in the app? Did you also read some of the posts below the first posts on how to use it? I mean, a lot of people have already posted there that they have all sorts of problems with the sensor. If there is really nothing that helps you I would try flashing at least one more time with wiping everything (btw, did you do a full wipe before coming to arhd?)
Yes used the super wipe as suggested.
I've been holding my finger over the sensor and increasing the thresholds, attempting to get a change, all combinations of the sliders and it just says 'far' continually.
Thanks for replying, sorry if its just that I'm just using the program incorrectly...
Full wipe and re-flash tried everything in Proximity Sensor Recalibrator nothing changes...
Recently my phone has been randomly crashing: i.e screen would lock, I would attempt to unlock it after x amount of time, and screen would not unlock. The home, menu, back and search 'buttons' on the bottom would light up, and I was still able to manipulate volume, but had to pull battery to reboot.
Attempted re-flash of Cyanogenmod 7.1 & titanium backup to restore apps / data. Crashes would still happen.
Attempted re-flash of Cyanogenmod 7.1 and left as 'stock' install - still crashed.
Attempted flash of Cyanogenmod 7.2 - crashes would still happen.
Tried above with no SD Card in - still crashed.
I read somewhere (forget where) that a dodgy battery could be causing this(?) so have ordered a new one.
Other than that, is there anything else that would cause this, and am I looking at getting a new phone or is there some other fix that someone else can recommend?
Cheers
Jeimuzu88 said:
Recently my phone has been randomly crashing: i.e screen would lock, I would attempt to unlock it after x amount of time, and screen would not unlock. The home, menu, back and search 'buttons' on the bottom would light up, and I was still able to manipulate volume, but had to pull battery to reboot.
Attempted re-flash of Cyanogenmod 7.1 & titanium backup to restore apps / data. Crashes would still happen.
Attempted re-flash of Cyanogenmod 7.1 and left as 'stock' install - still crashed.
Attempted flash of Cyanogenmod 7.2 - crashes would still happen.
Tried above with no SD Card in - still crashed.
I read somewhere (forget where) that a dodgy battery could be causing this(?) so have ordered a new one.
Other than that, is there anything else that would cause this, and am I looking at getting a new phone or is there some other fix that someone else can recommend?
Cheers
Click to expand...
Click to collapse
So just to make sure, you did perform a full wipe and not just cache and dalvik... right. Have you tried it with your phone plugged in? I'm not sure if this works, but with laptops you can run it without their battery as well if you have a bad battery.
Absolution 3.7 /Redemption A16, 17, 18, 19, 20. There now I'm covered for a few days
Yeh it was a full wipe!
I've resigned to the fact that's it a hardware issue, and managed to convince my provider that the phone is busted, they're sending me a replacement tomorrow.
Win.
Thanks for the advice.
So, i'm completely lost. I was playing around with ROMs and mods (the RAM build.prop, for example), and now all my phone's sensors seem to be stuck.
I have reflashed back to completely stock ROM, taken official sprint update. Tried modded ROM, done factory resets, cleared/wiped everything, and still the issue persists.
It would appear my Gyroscope, Accelerometer, Proximity Sensor, and Compass are all not responding at all.
Right now i'm on rooted stock AOJ6.
Does anyone have any ideas? Maybe a corrupted sensor properties file or something similar like that? I'm completely at a loss.
Any help is appreciated.
Guys, it fixed itself. I booted into safe mode, restarted and all the sensors are working again.
I doubt it had anything to do with safe mode, as the sensors weren't working in safe mode.
I have no idea what could have done it. I wish I had a real answer for you.