Hello all,
I'm hoping someone an help with this.
I have already asked a few people, but no-one has been able to solve it just yet. I have faith though.
No matter which ROM I use (was using Vegan initially, then tried TnT Lite and even the stock TnT) when I try to use the camera it seems to "crash". The app loads, and I can interact with the app, but the camera screen seems to crash (colored lines for a split second, then nothing) then goes black. I can still change settings in the camera (such as change to video etc) but the camera screen is just black. When I click the shutter button to take picture, the picture appears at the top right in the little box but is just a green square.
Anyone any ideas?
Does it sound like a software issue? Or hardware?
I'm really hoping software as I don't want my tab to be broken.
I have not tried an nvflash yet, but probably going to do that tonight and fully reset it. Might that help?
Thanks in advance!
Mine was doing something like this. I found out with mine that when I opened the case, the camera had popped out of it's spot and wasn't pointing out the keyhole.
Hey guys. Im having a problem with the proximity sensor on my sensation 4g. It was working fine when i bought it. It shut the screen off while calling, but now it does not. I thought that maybe rooting it would fix the problem by getting a custom rom, but i would like some input before i go rom exploring on this phone. I assume its a software issue because i havnt dropped the phone or anything along that line. Any Help would be highly appreciated. I also am looking for the dialer codes that would lead you into a test mode to test the functions on the device. If anyone knows of a code, I would appreciate to learn what it is. thank you for your help.
Make sure Proximity sensor is enabled in Settings > Call Settings > Additional Settings.
thank for your reply. I checked the settings and the only thing that shows up is Caller Id settings and Call waiting. Oh and i downloaded a market app that would show me all the sensors that work on my phone, and the light and proximity sensors both come up with an unknown error. Could it be something from the gingerbread update?
Did anyone figure this out? I have the same problem and its getting pretty annoying.
Me too...:-(
Hello,
I am having the same problem. Earlier, I thought that it was a ROM issue, however, after changing multiple ROMs, it seems to be firmware issue.
On my sensation, I found out that it is related to the back light for the soft keys (home, menu, back and search).
I can get it to work if I turn on pocket mode in Settings > Sound and then restart (once or twice). It will work until next restart.
I have installed AndroSensor from market and it shows one of the 3 messages
Proximity Sensor: Waiting for Event
Proximity Sensor: Unknown Error.
Proximity Sensor: 3.5in
Also, I am getting exceptional battery life which makes me wonder whether phone uses both the cores or if anything else is wrong with the phone.
I am using Energy ROM (3rd Oct).
Any feedback?
Thanks,
Baiju
baijunagori said:
Hello,
I am having the same problem. Earlier, I thought that it was a ROM issue, however, after changing multiple ROMs, it seems to be firmware issue.
On my sensation, I found out that it is related to the back light for the soft keys (home, menu, back and search).
I can get it to work if I turn on pocket mode in Settings > Sound and then restart (once or twice). It will work until next restart.
I have installed AndroSensor from market and it shows one of the 3 messages
Proximity Sensor: Waiting for Event
Proximity Sensor: Unknown Error.
Proximity Sensor: 3.5in
Also, I am getting exceptional battery life which makes me wonder whether phone uses both the cores or if anything else is wrong with the phone.
I am using Energy ROM (3rd Oct).
Any feedback?
Thanks,
Baiju
Click to expand...
Click to collapse
This is interesting b/c I just noticed I have the same problem, too. I do not check the pocket mode because I want to save some battery life. I did get the proximity sensor working during calls "sometimes". And it's really hard to define this "sometimes" b/c I cannot identify the pattern or reproduce the scenario.
My solution to this issue is that If it's not working, I recharge the battery until full, do a reboot, maybe reboot twice, and it is "sometimes" "fixed" by itself. In my case, after doing that, the proximity will work for a while (again, it's hard to determine how long), and just stopping working all the sudden.
I hope there is a easier fix, maybe a app, that would reset the proximity so we can apply it when the sensor does not work.
Hi I just realized the cause, it's because the battery % mod from UOT kitchen. I removed it and everything is fine now. Apparently the UOT kitchen's setting has problem.
I have 2 sensation 4g. One doesn't have any problem with Energy ROM. For the other phone, I went back to Factory settings and reinstalled original TMobile ROM. I still have problem with that one. I have contacted t-mobile and asked for a replacement. It is something with the hardware I suppose.
Baiju
hello
I got the exact same problem and i do many rom/kernel change to figure out this problem but i just can't .
Yungyeh could you explain more how do you solve it ? thks
toowave said:
hello
I got the exact same problem and i do many rom/kernel change to figure out this problem but i just can't .
Yungyeh could you explain more how do you solve it ? thks
Click to expand...
Click to collapse
I guess nothing fancy.
As I've known so far, there are several causes, which can be divided into two categories: Hardware and software .
If your device came with this issue, with a stock rom installed, maybe applied some updates, then you shouldn't wait to call the (HTC/T-mobile?) customer service. Have a exchange or replacement is the only way to correct the hardware issue.
If it's a software issue, i.e. it worked before with a stock rom, but now it fails sometimes after flashing a custom rom, you may go with the following solutions.
Situation One: If the custom rom is fresh installed, charge your device until battery full, stay in charge mode for another 1 - 2 hours, complete power off and on at least twice (three times maybe, make sure the "fastboot" in the power settings is off). Do not install any mod until your rom settles for a few hours. Sometimes the sensor does not work will simply because the cache goes wrong. If after waiting for a few hours and the problem still persists, you may want to check your custom rom's instruction and make sure you've followed every steps.
Situation Two: If the proximity sensor does not work all the sudden, especially after doing a reboot, you should first clear your data for phone app (or any other apps that use the proximity sensor), and then boot into recovery to clear all your cache. After wiping your cache, you have to do what situation 1 instructed because your device is just like a fresh installed one.
Situation Three: If your proximity sensor fails to work after applying a mod, especially some mods cooked from the UOT kitchen, revert back to your previous backup. DO NOT APPLY THAT MOD ANYMORE!!! Try some other mods that work for you and that is friendly to your proximity sensor. This situation also applies to if your flash an inappropriate kernel. Revert back to your previous backup is the only solution.
If none of the situations described above works for you, then I am out of clue. Changing to other custom rom or kernel usually does not work. You may try that but I doubt it will resolve this issue. It may be just your bad luck that the proximity sensor of your device goes to its end. I sincerely hope it not the case.
my sensors are not working!!
accelerometer
gyroscope
light
magnetic field
orientation
proximity
All not working...
Was using HyperSensation-CM7.1-v0.8, then decided to update the kernel, faux newer one, then lost the ability to rotate the phone..
So, did a manual wipe, then super wipe, restored my backup, and still no sensors,
wiped again and tried a diffrent rom nothing changed,
wiped again tried arhd 3.6.7 with stock kernel and faux kernel,
tried cm7 with the kernel it comes with or the newer one and still nothing...
at what level does the software talk to these sensors, is there a 100%way to wipe the phone and start over? i have never had any issue like this before!
Would reverting back to the original rom via fastboot help at all versus what i have done?
if someone has any ideas pm me, its a little bit easier then catching a response here since this is the most popular rom in the world lol, but ill still be reading
I'm having the same probpem. I don't really mess around with Roms or anything and I have 2 sensation 4g that do the same thing. And I believe is an htc problem.
having the same iseu with proximity and light sensor.
Do you have an solution yet ?
yungyeh said:
Hi I just realized the cause, it's because the battery % mod from UOT kitchen. I removed it and everything is fine now. Apparently the UOT kitchen's setting has problem.
Click to expand...
Click to collapse
I`m having the same problem with both proximity and light sensors.They work occasionally but not for to long.Have you found a solution for this?
It's April of 2012 and I have found NO answers or fixes!!!!!!!!!!
Same sensor problem on my sensation.
If I reboot the phone in a dark room, booth sensors are working (I don't know if it's correct when the proximity sensor shows only 3,5 or 0 inches, but it works)
When I go to a lighted room, the proximity sensor stops to work and the light sensor needs more time to measure the illumination.
If I reboot the phone into lighted room, the sensors didn't work.
It is possible to simulate a "dark room" by covering the sensors with a finger ;-)
It is not easy to decide if the error is located into software or the sensors are "overloaded". For finding out a solution I have ordered new flex main board which should contain booth sensors. Hope it helps ^^
schand99 said:
Same sensor problem on my sensation.
If I reboot the phone in a dark room, booth sensors are working (I don't know if it's correct when the proximity sensor shows only 3,5 or 0 inches, but it works)
When I go to a lighted room, the proximity sensor stops to work and the light sensor needs more time to measure the illumination.
If I reboot the phone into lighted room, the sensors didn't work.
It is possible to simulate a "dark room" by covering the sensors with a finger ;-)
It is not easy to decide if the error is located into software or the sensors are "overloaded". For finding out a solution I have ordered new flex main board which should contain booth sensors. Hope it helps ^^
Click to expand...
Click to collapse
@schand99: The Flex/Main Board actually isn't the problem. It is an HTC software/hardware related problem. I have 2 Sensation's here now, one is rooted and unlocked entirely and the Proximity and Ambient Light Sensors and the Capacative Backlights on the touchpad DO NOT WORK. FYI, the touchpad lights work in cooperation of the Ambient Light Sensors: If there is any light under 90.0 Luxes (this is how the sensor measures light) the backlights will come on. If there is anything over 90.0 Luxes, the backlights will stay off. This is based on the fact that you need light in a totally dark environment, or you do not need light as you can see the touchpad and it is not that dark.
It is DEFINITELY not a hardware issue as there are some temporary fixes that will bring them back to life, but usually after a reboot, they are both dead again.
I am curious if your new flex/main cable would do the trick or not. I have tested the sensors chipsets independently and they work fine, there is just something that block their functionality on a software end.
mariosaraylian said:
It is DEFINITELY not a hardware issue as there are some temporary fixes that will bring them back to life, but usually after a reboot, they are both dead again.
I am curious if your new flex/main cable would do the trick or not. I have tested the sensors chipsets independently and they work fine, there is just something that block their functionality on a software end.
Click to expand...
Click to collapse
My report about main flex board changing:
After changing the board booth sensors are working fine. I have tested the functionality of the sensors also on different ROM's like stock rom, OrDroid and CoinDroid. No problem until now. It makes not a difference anymore if I power on the phone into dark room or on a sunny place.
BUT!
I don't recommend to do this by yourself. It is verry difficult to do this work !!
It is my profession to do this kind of work.
AND
to change the board was the right method for fixing the sensor-problem on my HTC Sensation. I had to unlock the hboot 1.27.xx by using the "beer drinking" method. So perhaps I have damaged the sensors by doing this...
schand99 said:
My report about main flex board changing:
After changing the board booth sensors are working fine. I have tested the functionality of the sensors also on different ROM's like stock rom, OrDroid and CoinDroid. No problem until now. It makes not a difference anymore if I power on the phone into dark room or on a sunny place.
BUT!
I don't recommend to do this by yourself. It is verry difficult to do this work !!
It is my profession to do this kind of work.
AND
to change the board was the right method for fixing the sensor-problem on my HTC Sensation. I had to unlock the hboot 1.27.xx by using the "beer drinking" method. So perhaps I have damaged the sensors by doing this...
Click to expand...
Click to collapse
@schand99: That's very strange that it could be the SAME hardware problem for all of these people that are complaining about this issue. I wonder if is some sort of production issue they have. The strange part is that it is not just for the lot of hardware issued for the USA only, it is also in other parts of the world also.
I did a hardware exchange with mine at the TMOUS store and the "new" one I have now is working fine thank God.
I told them that the TMOUS ICS RUU OTA upgrade broke the sensors LOL!
Thanks for your feedback!
i recently bought a g2x from wind mobile. it's flashed to cyanogenmod 7.1
anyways, i noticed while playing doodle jump that my accelerometer seems to be off. i tried searching around and found horizontal calibration and sensorcalibutil_yamaha.
horizontal calibration isnt on my menu (settings->display settings)
i dont have sensorcalibutil_yamaha in my system/bin folder. i read i can dl and push it to the bin folder or put it on my sdcard and run it from there.
tl;dr can anyone upload their sensorcalibutil_yamaha please? searched all over for it but couldnt find a link that is working. thanks
nijohc said:
i recently bought a g2x from wind mobile. it's flashed to cyanogenmod 7.1
anyways, i noticed while playing doodle jump that my accelerometer seems to be off. i tried searching around and found horizontal calibration and sensorcalibutil_yamaha.
horizontal calibration isnt on my menu (settings->display settings)
i dont have sensorcalibutil_yamaha in my system/bin folder. i read i can dl and push it to the bin folder or put it on my sdcard and run it from there.
tl;dr can anyone upload their sensorcalibutil_yamaha please? searched all over for it but couldnt find a link that is working. thanks
Click to expand...
Click to collapse
The sensor is not Yamaha. Just throwing things like that onto your phone is a great way to mess it up. Search for other threads on the code to enter the engineering menu. I believe there is a sensor calibration utility in there.
FYI, the accelerometer, magnetic and orienation sensors in this phone are by Kionix, InvenSense and Aichi Steel. The proximity sensor is by Sharp and the digitizer is by LG. The sensor that monitors IC temp, etc. is made by Rohm. No Yamaha sensors in this device.
i guess that explains why it's not there.
also as an update i did some more searching and found how to do it using the hidden menu, but cm7 does not have it
nijohc said:
i guess that explains why it's not there.
also as an update i did some more searching and found how to do it using the hidden menu, but cm7 does not have it
Click to expand...
Click to collapse
So that is another reason to leave the phone rooted stock.
well i've flashed to stock and accessed hidden menu. i was sure i read about a way to calibrate with that it but i cant find it again so it seems i was tired and delusional yesterday. i guess basically g2x has no calibration app whatsoever. i also tried looking through my system and data folders for a g sensor config file that other devices seem to have, but no luck
am i the only one with this problem? maybe i should go return it for a new one
edit: my backup got corrupted somehow so i have to reflash and install everything again. fml
I have downloaded several compass apps but none is pointing north. Anyone with same problem?
I am using Catch.com's compass app from the Market and it is pointing North fine.
Does your Google Maps report your location correctly? Also, you may want to turn Wi-Fi Location on as well. (Settings>>Location services>>Google's location service [checked]) Also, make sure GPS satellites is checked there.
Tf700's specifications says it has an electronic compass, so no gps is needed to point north.
I tryed catch.com's compass and guess what... it works, its pointing north.
The other compasses still dont work, so catch.com is the one to use.
Thanks for the tip.
KangLx said:
Tf700's specifications says it has an electronic compass, so no gps is needed to point north.
I tryed catch.com's compass and guess what... it works, its pointing north.
The other compasses still dont work, so catch.com is the one to use.
Thanks for the tip.
Click to expand...
Click to collapse
I also have this issue on mine. will give catch.com a try.
KangLx said:
I have downloaded several compass apps but none is pointing north. Anyone with same problem?
Click to expand...
Click to collapse
Mine doesn't even work with catch.com's app. I rotate the device slowly a full 360 deg. and it moves the needle about 45 deg.
This makes certain apps like SkySafari, SkyMap etc. virtually useless.
Does anyone know of a technique to re-calibrate or reset the compass to make it work?
mandables said:
Does anyone know of a technique to re-calibrate or reset the compass to make it work?
Click to expand...
Click to collapse
Mine does it too. The sensors can autocalibrate when rotated. Just like I did with my HTC Incredible, I just hold it in roughly the same orientation I'll be using it in then flip it over twice around the X axis, then rotate it sideways twice around the Y axis, then rotate around the Z axis. It usually reads accurately after doing 2 of the 3 axis but I do all 3 anyway because it takes a matter of seconds to do this.
I also have problem with compass. I tried it to calibrate, but none method works. The compass north is always heading +-45deg to screen top in landscape mode. Is there any way to reset the compass calibration (for.ex. delete some files on rooted device) or is this a HW fault? I'm on rooted stock ROM.
Sv: compass sensor
rkalas said:
I also have problem with compass. I tried it to calibrate, but none method works. The compass north is always heading +-45deg to screen top in landscape mode. Is there any way to reset the compass calibration (for.ex. delete some files on rooted device) or is this a HW fault? I'm on rooted stock ROM.
Click to expand...
Click to collapse
Count me in on compass problems. I begin to suspect that there's a hardware problem. My compass never points north, and calibrating by rotating the pad does not help. Makes geocaching rather impossible, unless you bring your own compass...
Mine seems to be mostly right using the Smart Tools one. I get a magnetic field reading of around 42.the need jumps around a bit, but not more than +/- 10 degrees.
fiidim said:
Mine seems to be mostly right using the Smart Tools one. I get a magnetic field reading of around 42.the need jumps around a bit, but not more than +/- 10 degrees.
Click to expand...
Click to collapse
Ditto, Smart Tools points north more or less accurately. (49 mag) It's off by 15 degrees, and it's 15 degrees off in the opposite direction on my sgs3.
Send from my Samsung Galaxy S3 using Tapatalk 2
My phone is a LG Optimus G (a F180 converted to E975, stock Euro firmware), but from googling this issue it seems to be a problem that can strike any phone with no readily apparent solution...
I first noticed it while playing Star Wars KOTOR, where it'd get stuck; flipping the phone (to better orient the charging lead) started leaving the picture upside down. Initially, I could fix it by long-pressing the home button to get at my notification bar and toggling auto-rotate off and on, before it crapped out entirely (necessitating an orientation-locking app), which led me to think it was a software issue...
But after googling the problem and seeing how widespread it is, I'm thinking maybe these sensors are just prone to failing? I saw all sorts of possible solutions offered, which apparently work for some, but it seems nothing solves it for many, including factory resets and flashing firmware... I uninstalled KOTOR when I was done with it, but to no avail. I don't fancy figuring out how to flash the firmware again, but if that's what it takes...
Does anyone know anything about this issue? Am I stuck with a slightly crippled phone now?