Somehow (I think from calibrating either the compass or the bubble level inside of an app), either my compass, g-sensor, and/or gyro calibration is really messed up. I've tried everything short of exchanging the xoom at BestBuy.
Now, although I can calibrate the compass and have it work inside of a specific 3rd party app (such as 3d compass), the arrow in google maps spins wildly and sky maps is completely useless (while holding the xoom in landscape and panning up or down, the screen begins to rotate/jerk left or right; with the xoom in portrait it jerks constantly to face either North or South).
Can someone please upload their akmd_set.txt file located in /data/misc? After too much searching, I believe that is my last chance of getting it working again. Also, if anyone has any ideas on how else to calibrate the sensors, it would be much appreciated!!
Thanks!
That doesn't sound like a calibration problem to me. Sounds more like faulty sensor or something.
Bad calibration wouldn't cause that unless you'd gotten it right on an axis.
You tried flashing a stock image?
alias_neo said:
That doesn't sound like a calibration problem to me. Sounds more like faulty sensor or something.
Bad calibration wouldn't cause that unless you'd gotten it right on an axis.
You tried flashing a stock image?
Click to expand...
Click to collapse
Yep, tried a system restore followed by flashing a stock img. Could someone plz upload their akmd_set.txt file before I exchange this thing?
Bump.
Anyone, please?
I've been reading, searching, and loving these forums for a year and this is the first question I've asked. Anyone who is rooted can access the file from root explorer.
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!
Hi. Just wondering if anyone out there would happen to have a .img image of the firmware for the trio stealth pro 9.7c. I.ve looked everywhere and can only come up with images that install through CWM recovery. My tablet will not boot into recovery as I flashed a rom that I thought would work, but now no video. Not an emergency, but if someone has it, it would be much appreciated. Thanks in advance
jgb441 said:
Hi. Just wondering if anyone out there would happen to have a .img image of the firmware for the trio stealth pro 9.7c. I.ve looked everywhere and can only come up with images that install through CWM recovery. My tablet will not boot into recovery as I flashed a rom that I thought would work, but now no video. Not an emergency, but if someone has it, it would be much appreciated. Thanks in advance
Click to expand...
Click to collapse
I used a livesuit image that was supposedly for the 9.7 on my 9.7c and everything works flawlessly. Use at your own risk. can't post links. pm me if you want it
Try this.
A member called hammerite said in this post http://forum.xda-developers.com/showthread.php?p=52298998 that the firmware for Wintouch Q91 works with this tablet. Specifically the file name is Q91A30321.img. Google it. I'm just downloading it right now and hope to fix a friend's tablet with it..
Sorry to say that file didn't work for me.
Another works, kinda
Headroom said:
Sorry to say that file didn't work for me.
Click to expand...
Click to collapse
I was grasping at straws and downloaded the Q95A306043G file, and everything works, but you need to put it to english, and the colors are off, kinda like low res kinda look, but it's a good start if someone can fix the res of the screen :fingers-crossed:
A possible work around to get the 9.7c up and running
Headroom said:
Sorry to say that file didn't work for me.
Click to expand...
Click to collapse
Yeah didn't work for me either. But I did find a bit of a work-around to have a functioning tablet again. A bit of a pain in the butt way to go about it, yet it is usable. If anyone wants to give it a try so you can at least use the thing, I'll try to explain it.....here it goes.......
Things needed:
1. LiveSuit or PhoenixSuit (I used PhoenixSuit)
2. Not necessary, but useful later, Root_with_Restore_by_Bin4ry_v32.zip
3. F918-WCDMA-20130423.1.1.11-a106-dou0308.img (copy and paste this into google, you will see a link from a site called pan.baidu.com on the first search page. Turned up about the third search down during my search. It is in Chinese, but the download link to click will have the file size, (310.16mb) click it and another box will appear, click the white box on the right, then yet another box will appear, click the blue box on the left this time, then it will give you the download.) This image is for a ly-f918 tablet, but mostly functional on 9.7c
Now we can start flashing.......
1. Using either LiveSuit or PhoenixSuit, flash the image that you downloaded to the tablet.
2. After the flash, you will notice that the screen colors are messed up and screen rotation is 180 degrees off. For the rotation, I just turned off auto rotate.
We will get to the color issue in a few....The screen will be barely legible at this point, but if you squint just right, you can read it
3. Run Bin4ry to gain root
4. For the screen color issue, I signed into google, went to the play store and downloaded and app called Screen Adjuster Free, ( yes this rom has play store built in) Set the Screen Adjuster to on (box at the top of the app) and set the system brightness to 23%. The screen should now be legible.
Things that are NOT working:
As mentioned, auto rotate is off 180 degrees
Rear camera causes the tablet to shut down
Volume up button lowers the volume, volume down and back buttons do nothing. There are volume up/down icons on the notification bar though
Color still off in the notification bar
I know it seems half-assed, but I DO at least have a working tablet again!!
I did find another rom that touch, wifi and camera do not work, but the screen colors are right:
sun4i_crane_v1.5_T05A_mc32x0_20121012-tm2.img
Maybe if someone knows how to open the images to play around with them, the display driver from the sun4i rom can be put into the F918 rom so the color is right. And possibly fix the screen rotation issue. Then the only things to worry about are the hard buttons and rear camera at that point.
Sorry if this seems lame, but like I said, My Stealth Pro 9.7c is functional again ( to some degree any way ) and if you were in the same boat as I was.....holding a tablet that didn't work at all.......it's better than nothing.
as always, try at your own risk. Let me know if anyone has trouble with this method or improvements. Thanks!
WoppTorr said:
I was grasping at straws and downloaded the Q95A306043G file, and everything works, but you need to put it to english, and the colors are off, kinda like low res kinda look, but it's a good start if someone can fix the res of the screen :fingers-crossed:
Click to expand...
Click to collapse
Just noticed you posted this as I was writing my post Does auto rotate work right? and do the hard buttons fuction correctly? and rear camera work? If it does you're a step closer than I was. maybe if someone takes THAT rom and the second one I posted and made a flashable image, we would have a completely working rom!!
Just seen this thread and posted this earlier http://forum.xda-developers.com/showthread.php?p=53242286
Sent from my Nexus 7 using XDA Free mobile app
jgb441 said:
Just noticed you posted this as I was writing my post Does auto rotate work right? and do the hard buttons fuction correctly? and rear camera work? If it does you're a step closer than I was. maybe if someone takes THAT rom and the second one I posted and made a flashable image, we would have a completely working rom!!
Click to expand...
Click to collapse
Ya it's kinda the same as the one you were using, auto rotate is off 180 degrees, but no auto rotate fixes that been, testing it for awhile and found that utube, and netflix auto turns it upside down, and I have to use that other program to get the colors right, camara worked for a bit then it stopped working, but the play store worked just fine, sorry I've been gone, just busy at work =( volume up doesn't work but volume down does
Downloaded from where.the site won't let me download it
Last week my completely stock N5 stopped auto rotating. After some searching I realized nearly all of the phones sensors were not working. I found a fix thread that suggested deleting the sensor files in the data folder. This worked for a few hours and went back to being broken. At this point my phone was rooted so I tried wiping to see if it was an application problem, no dice. Tried changing roms, nothing.
Are my sensors toast? I'm at a loss.. Help!
Download cpuid on play store and look at sensors section and if they don't show any data they're toast this is a problem with the lg g2s I used to have an lg g2 that had that problem and the nexus 5 is a googlified lg g2
spinninbsod said:
Download cpuid on play store and look at sensors section and if they don't show any data they're toast this is a problem with the lg g2s I used to have an lg g2 that had that problem and the nexus 5 is a googlified lg g2
Click to expand...
Click to collapse
The sensors do show up there. So I suppose there is some hope!
But do they show any data like when you put you finger on the proximity sensor does it show zero and when you remove it show 5 if it does it should be working
Proximity is working now. Looks like the accelerometer isn't. Hmm.