The accelerometer on my i927 suddenly started acting up 2 days ago. The screen wouldn't rotate, and games that used the accelerometer would constantly veer to the left. I tried everything I could find on the web and even got excessively creative trying to solve this, to no avail...
This morning, I asked myself 'where haven't I looked yet?'. Well, I hadn't yet done anything in /efs, which survives flashing different ROMs. Looking at /efs, there was a file called 'calibration_data'. I renamed the file to calibration_data.bak with ES File explorer, rebooted, calibrated again and the problem was solved.
For reference, here's other things I tried that had no effect:
Disabling and re-enabling rotation.
Shaking the phone and hitting it carefully.
Rebooting.
Shutting down the phone and removing the battery for 1 hour.
All sorts of programs to reset and calibrate the sensors.
Flashing the stock ICS ROM.
Running calibration in stock ICS.
Using the *#0*# menu in ICS.
Opening the phone and shorting the internal battery momentarily (yeah, I know that's stupid, but it did reset the clock).
Taking the phone's motherboard, padding it in a piece of paper, putting it in a cardboard box and throwing it to a wall (some people reported this problem was solved after dropping their phones, but I didn't want to break anything).
Hope this helps someone.
Related
Screen will not turn back on once phone is put to sleep or if the proximity sensor turns it off during a call. Very annoying, have to soft reset constantly. I currently use Android on my phone cause at least the screen will turn back on when using that.
Right now i have a stock 6.5 t-mobile rom and have tried several other roms as well.
Any suggestions?
Yep, easy fix, I posted this several weeks ago:
With the tilt 2, if the screen does not wakeup, but you can answer the phone, hear music, etc..., it is a malfunctioning light sensor, maybe hardware, or software related (drivers), but it is fixable. Just eliminate all calls for use of the light sensor.
I had this problem and took quite a while to figure it out, as there are several apps that poll the light sensor that cause problems.
First, go to start/settings/system/power/backlight and uncheck the auto adjust backlight option
Second, go to start/settings/personal/buttons/backlight and uncheck the enable keyboard auto backlight sensor.
Last, open advanced config (need to download and install from touchxperience.com, if you do not have it), tab to light sensor and set light sensor polling to disabled.
Now, my phone works normal and will wake up properly from standby like it should. this all seems hardware dependant, as I have in my family 3 of these things and I dropped and broke mine, so bought a new one (4th in the series) and it had the SOD issues, but could restart with softrest. Took me the better part of the day to find a reliable fix, but now all is well again.
Hope this helps other Tilt 2 and similar issues.
There's a lot of reasons for the SOD. The methods above probably worked for some people but never did for me. If they don't work, i'd suggest taking your your micro sd card, running scandisk on it and seeing if there are any errors. I had to switch cards because my card had errors on it. Haven't gotten a SOD since.
Yes, that was the first thing I tried on mine, because I changed the SD card with the new phone, but no errors found, so I kept digging. Stopping the all calls to the light sensor was all that worked for me. There are typically 3 culprits, bad light sensor, bad or overwritten drivers for the light sensor and sd card or ROM errors. All hard to fix and just have to keep trying, or go back for warranty replacement and hope the next one works. For me, only 1 out of 4 in our household has this problem and they essentially all have the same software, ROM and micro SD cards in them. Go figure.
hi, i have the same problem with the sod. i installed the rom from comec. then i deactivated htc sense on my phone an installed spb mobile shell 3.5 and i have no sod
Now before anyone flames me, I did search first "DUH". I could not find any clear solution that doesn't involve flashing roms, rooting etc etc.
All of a sudden, when phone has been on standby overnight, the battery is draining mega fast and it shows that the culprit is this "Mediaserver". What is this and how do I kill the SOB?
Usually my phone battery goes from 100% to about 95% when I wake up in the morning, which is about right. Now for the past 2 days, it goes from 100% to around 50% overnight!!!!!!
Please help someone as I have searched everywhere and I have not found a clear answer. I have not installed anything new, I do not stream media etc.
Thanks in advance!
http://forum.xda-developers.com/showthread.php?t=980575
FYI I typed "media server android battery" in to google and this was the first link.
Maybe try that next time
Umm...thanks very much but that was the first thing I tried. I actually saw that thread of the link you provided but it tells me absolutely nothing. Like I said, I did search first. I am not new here
I would like to know how one kills mediaserver.
I actually restarted my phone and up to now it has gone back to normal. Mediaserver appears near the bottom now with only 2% and the display is back at the top with 65% battery usage.
I must have read through about 10 different threads on the same issue with no clear resolution! Very frustrating indeed.
no worries, I can see you're not new here and I'm sure you've been pulling your hair out searching and reading the same thing over and over. When I read your OP it seemed like the answers in that thread covered things you might not have tried:
MACkjam said:
I could not find any clear solution that doesn't involve flashing roms, rooting etc etc
Click to expand...
Click to collapse
The answers in that thread suggest moving all of your media off your sd, nothing to do with rooting or flashing
But anyway I clearly underestimated how frustrating this problem has been for you, I don't think I could suggest anything you haven't already tried!
Possibly solved mediaserver issue!
Well, I did a soft reset and everything has gone back to normal. Medaserver does not even feature now. It is only visible when I am streaming music via bluetooth stereo headset.
MACkjam said:
Well, I did a soft reset and everything has gone back to normal. Medaserver does not even feature now. It is only visible when I am streaming music via bluetooth stereo headset.
Click to expand...
Click to collapse
Hi I am facing the same issue. would like to know what exactly you mean by soft reset? is it holding power button for about 10sec till phone switches off or do u mean a factory reset ?
Some of them said it worked when they cleaned up a corrupted file so i used a new SD card with just one song to test but everytime i play the song MediaServer wakes up and sucks out my batt. SO this method fails!
Second thing that i tried out was to disable stagefright settings in Build.prop which again has not worked! running out of ideas
device: Galaxy ace
ROM: Miracle V4.
Help would be much appreciated
I was facing similar issues.
here is what i observed
STOCK ROM: No issues.
Miracle ROM V4: Media server prob. Used a clean formatted SDcard with just one song on it and the problem still persisted
Other CM7.2 based ROMs: Media server prob. Used a clean formatted SDcard with just one song on it and the problem still persisted
Factory reset: On CM7.2 based ROMs: No use. problem no solved
Finally i used OmegaROMV4.: No media server problem here. Looks like its only for CM7.2 based ROMS.
I'm getting this on UNOFFICIAL CM9 for Evo. Started after I installed 5 different Portal Soundboards as well as a theme for CM9's Theme Chooser. Going to look into BetterBatteryStats but I'm not too confident based on other forums I've looked through. Also may consider a cache/dalvik wipe... If anyone has tracked this problem down please let me know.
midnightzak said:
I'm getting this on UNOFFICIAL CM9 for Evo. Started after I installed 5 different Portal Soundboards as well as a theme for CM9's Theme Chooser. Going to look into BetterBatteryStats but I'm not too confident based on other forums I've looked through. Also may consider a cache/dalvik wipe... If anyone has tracked this problem down please let me know.
Click to expand...
Click to collapse
I'm using a Nexus 7 that I've only had for a few days, so it was fairly easy to track down the culprit responsible for MediaServer gobbling up my battery.
The Internet did not provide any real solutions, just suggestions, so what I did was disable and/or uninstall any apps that I had installed today (the problem only started today) and also disabled other apps that keep popping up in the task manager, even after killing them a minute before, all to no avail.
One of the things I had also done was copy over a folder of wallpapers that I also have on my HP Touchpad.
I reconnected the N7 to the PC, open the N7's storage, deleted the folder and INSTANTANEOUSLY, MediaServer disappeared from my battery stats. I can't say if this will happen to any folder of pix or music that I might copy over, as this just happened to me a few minutes ago.
Some have spoken about corrupt files, and there is that small chance that one of my pics is corrupt, but it's a darn good start for anyone else, at least knowing where to look first.
I may experiment with it later and if I have anything to report, I'll post it.
Edit,
After experimenting with the wallpapers folder, copying it over to the N7, then removing it, using the wallpaper, rebooting, plugging the USB cable into the PC, then the charger, and disabling and enabling "Gallery", I have found that there is a relationship between having that folder on the N7, and MediaServer coming on and using a lot of battery power. Getting the Media Server to come on, or go off, is not as instantaneous as it was the first time I did it, thus all the other actions mentioned above, until Media Server turned off. One thing for sure is that when the Wallpapers folder was on the N7, there was nothing I could do to stop the Media Server, and to get it to turn off, amongst other things, I had to remove the folder and disable "Gallery".
Once the Media Server is off, it stays off, even after enabling "Gallery", as long as the Wallpapers folder isn't present.
I hope I explained that well enough to be useful.
I've not had this issue up until yesterday, the phone would joy auto rotate, and games such as temple run weren't playable due to the accelerometer not registering anything at all, I reset the phone and it worked fine.
now, the issue has come back, but Won't go, I've reset the phone, Booted in safe mode, performed a factory reset, everything. (the only difference factory reset made was that when I try to calibrate the G sensor it says 'calibration complete' instead of calibration aborted.)
However, still the bubbles do not move.
I've looked on the sensor debug app, it shows no data.
Now, what's strange is on the camera I have taken two identically pictures.
One I took in portrait, the other I took in landscape.
I went to gallery and the picture I took in portrait appears as a landscape picture, and the one I took in landscape appears as a portrait picture :s
Well, that shows the accelerometer is working right? (Even though it's backwards)
I'm really confused, I don't want to have to return my phone but if it's a hardware fault I have no choice.
By the way, I'm completely stock.
-bump-
When I calibrate the phone while moving it around, the calibration aborts.
But when I calibrate it as you should. on a flat surface it says calibration completed.
so therefore, the Accelerometer must be working in there.
Which makes me wonder if it's a hardware fault or an issue with the kernel or Rom? (Stock)
...
Mine had a similar problem in that it stopped auto rotating in anything, turned out to be a hardware fault as like you I tried every software test. Your best bit would to either do a factory resit on the phone (unless already done so) and it that does not fix it have you tired the htc function tester?
If yes to both it may be the case that you have to send it for repair.
My auto rotate was a hardware fault and they had to replace the main board and a lot of other silly components I have to clue as to what they are.
I hope this helps.
Same problem here. This issue actually concerns a lot of people.
No fix for the moment, check this thread for more info:
http://forum.xda-developers.com/showthread.php?t=1588663
If you can't guess what happened from my title, then let me elaborate.
When leaving a nightclub in camden last saturday night, I whipped out my phone to navigate to the bus stop when the heavens bucketed it down on me. Well shortly after getting on the bus and texting my flatmate to see if they are still up and want a game of COD, the screen starts flickering and the contrast went all weird and I lost my mobile signal. So rebooted the phone, still the same (at this point the brain still hadn't clicked that it could have been water damage). So I decided that I should reinstall the rom whilst on the bus, still the same (mine is rooted and running Liquid Smooth beta 3.2). It was only when the phone felt particularly warm at the back that it occurs to me that it's water damage so that was when I decided to take the battery out.
Anyway, now that I've set the scene and the background story, the problem I have now is that the camera doesn't work and I've tried multiple camera apps. All I get is a grey screen, the camera icons doesn't work and I get a message saying "Gallery isn't responding". At the same time Gallery sometimes work and I can't view any videos via MX Player or play anything on youtube (the menu and links are still there though). And my mobile signal just drops to nothing and I have to reboot.
Any ideas on what I can do? I've done the following:
Hardware reset and reflash my phone
Tried different versions of LiquidSmooth Rom
Made sure I'm using the correct version of Gapps
Attempted to run Z-Device Test to no avail, the app just hangs
I've let it dried
Cleared the cache, enable/disable gallery
Cleared the cache on Media Storage app
Used multiple camera apps
Tried to use the camera in the lock screen (just get a black screen)
Since it's water damage I cannot imagine flashing anything will make a difference.
Should have immediately pulled battery and put it in rice asap.
Always a good idea to keep a small plastic bag in your car/bag/briefcase for just that situation.
Yeah.. I had hopes someone in the forum would go, "That doesn't sound like water damage, you can fix it by doing this". Sigh.... It's amazing how one hardware fault can affect things like youtube whilst everything else is fine.
I'll keep my fingers crossed for you that someone will see this and know of another possibility.
Hello! Firstly I'd like to say thanks to any regular posters, this site helped me root my phone in the first place! I am trying to sort out what might be the cause of this problem and remove it, hopefully without starting over, as it was a pain in the butt to get the phone set up how I wanted and I do not have a full night to commit to it at the moment.
I have a Samsung S2 (the t-mobile branded one, sgh-t989), android 4.1.2 (kernel 3.0.31-1003885). This problem is recent and came on suddenly without changing any settings or installing any new software. The phone behaved normally for the first few months I owned it, it is a used phone, however, and I have no idea how the original owner treated it.
The problem is that brightness becomes tied to one or more of the sensors, and it takes several restarts, or sometimes days of waiting for the problem to go away. The brightness most often becomes tied to the accelerometer, where having the phone pointed at 45 degrees (or 01:30 o'clock), results in near 0% brightness, while returning to full brightness at 90-0 (or 3 through 12 o'clock). Occasionally it ties to another sensor (proximity?) or changes seemingly randomly, and once or twice has tied to the compass, with North being the brightness sink (with a similar 'darkness range' to orientation). The problem starts without a discernable cause.
Whatever the problem is, it also appears to disable, or for the most part inhibit multitouch. Around the time the problem started, tasker disabled and refuses to re-enable, if it is relevant. Shortly after the problem started, any push notification began turning on the screen (with a normal timeout, however). The problem persists through changing of any of the settings, toggling any modules, and through multiple resets, and never resolves itself without a cycle of multiple pulling-outs of the battery. After it is resolved, it usually remains fixed for a day or so before re-appearing.
If anyone has any suggestions for chasing down the problem, or has heard of anything similar, I'm all ears. I would like to avoid doing a factory reset, especially since I have no assurance it will resolve the problem. I'm happy to provide any additional information. Thanks for your help!