Related
I have upgraded my HTC Desire to Android 2.2. Unfortunately I have realized that after that update, an embedded compass started acting up. I mean it's not showing the North anymore. It seems to me that it's not an issue with some particular application as I have tried with several ones available on the Market and it needs to be some bug with new OS. Anyway here is what I have figured out and what I have already done in order to get this sorted out. At this point of time, it even looks like I have just some kinda workaround:
Once I pick out 'Calibrate' menu item in Compass v1.1 (developed by Snaptic, Inc.) and then according to the instruction, start off waving my phone in a figure 8 pattern to reset the magnetometer on my device, it's not gonna fix the issue but when I start rolling my phone in a hand (side to side then top to bottom) and then it seems to me that the issue is sorted out as finally compass points out the North, but after I close the application and open it again (or open any other compass based app) the magnetometer is broken again So all what I can do is to reset the magnetometer as per above-mentioned instruction again. It just looks like the device is not able to save some compass calibration setting anymore.
Anyway I was just wondering if some of you already faced this same issue and know how to fix it permanently. I would appreciate it, if you could share any thoughts with me. Thanks in advance.
Hey folks, I don't believe that nobody experiences that issue too. Maybe you just haven't noticed that yet? Anyway could you please just check if your compass works as intended after the upgrade to Android 2.2? Personally, I really believe it's a bug with Froyo.
I think mine is also acting weird.
Wenn starting Google Maps and using streetview in compass mode it only looks up and down and I cannot look from left to right.
When i roll the phone a few times in my hand it starts working.
But after closing Google Maps and starting it again I have to do the rolling again
I was wondering that compass problem too. With ver.2.1 everything worked like a dream as I use compass mostly geocaching. After updating in every app I've tried the compass stucks pointing to approx. to the lower left corner of the screen. Sometimes calibration helps but it stuck again after a while even the app is running all the time.
"Compass" app kinda could wake up after waiting a while but usually it doesn't. In any other software won't work at all as I've tried, 5secs after calibration but nothing more.
JLillia said:
With ver.2.1 everything worked like a dream as I use compass mostly geocaching..
Click to expand...
Click to collapse
@JLillia: Also in my case the compass worked as intended on android 2.1.
Anyway thanks for your answers guys! I really appreciate it! So it looks like at least 3 folks here are experiencing some issues with digital compass after the upgrade to the Froyo on HTC Desire
Wonder if there is anyone here who could disagree with us and say that the upgrade didn't cause any compass degradation on his/her device at all...
I can't say if it worked properly with 2.1, didn't use the compass a lot before.
With 2.1 I needed to calibrate it a few times, but probably not as much as I need to do now. I'm using the "compass" app and it directly tells me it detected an abnormal magnetic field. After calibrating it again, it points north. Haven't checked the correct north with a real compass, so it may have a slight difference.
I put my phone down at the table at 0 degrees N. I turn off my screen, and turn it back on. It is now pointing 90 degrees E. But the interesting thing is.. the east is actually located west, compared with the previous north :?
When I rotate my phone it displays only E or SE, always between 90 degrees E and 130 degrees SE. I can't even find north.
I can rotate my phone 180 degrees (Pointing south), it displays 130 degrees. When I calibrate the phone and I rotate my phone 180 degrees (Still south) it displays 160 degrees S. Which is kinda strange. And when I try to find the 180 degrees point, and rotate my phone again, it displays 35 degrees NE.
After another calibration the values seems to be okay...
My conclusion? Don't trust the compass at all unless you have a real compass to compare.
That person with the exact opposite experience is me
I complained on 2.1 here with many others about the compass going haywire every time you took it off-screen and its lack of stability and consistency. HTC 2.2 totally fixed this issue for me. I've calibrated it once about a week back and it's still accurate every time I'm opening it and in Google Earth.
Beware, the compass draws a lot of power in use so it'll drain the battery very fast. About as fast as playing a 8Mbps 720p VC-1 vid.
-----------------------------------
- Sent via my HTC Desire -
My problem is kinda dame that with Nakebod.
As I said compass stucks pointing to the lower left corner, it infact tells I'm holding the phone towards 120-130 decrees east, where ever I turn the phone to. Calibration helps for a while as after that the compass points approxamtely to north which is enough direction to me, but after a while or at least after swithing apps or taking compass background and back on, it stucks again to the 130 decrees.
Of course I am not using this kind of device as "for real" but I'd like to have it at least somewhat accurate. As geocacher I use compass as a tool with my hobby and I was quite happy with Desire because of the quite accurate GPS but after the update the compass is practically useless.
Just a quick update, I made a quick phone call to HTC support this morning and raised that issue. The support analyst recommended the factory data reset to see if it helps. I guess it's just a standard answer so at this point of time I'm not gonna proceed with that and erase all data on my phone. (Btw, I wonder if it's possible to backup all current data from my unrooted, unbranded Desire?)
Furthermore he promised to get back to me in next few days with some official resolution of that issue so I will keep you updated.
Try calibrating your magnetometer by waving your phone in 8-shaped moves.
I emailed HTC customer care also about the issue and the answer was to factory reset the phone. Of course that was the first thing I had already done at the minute I noticed the problem in first place so I wasn't quite fond of the idea. In fact I have reseted phone three times after the update and allways the result was the same; compass stucks.
Well, I thought that maybe I have some weird app that messes up the compass so I tried one more time...
At first after the reset I downloaded only EStrong file manager, compass and c:eo. Compass worked most of the time! I kept resuming backups and compass did stuck occasionally but not very often (+ abnormal magnetic field). I am not sure what I did leave out of the phone but now the comapss works quite fine. It is a lot more sensitive for magnetic fields than in 2.1 but usually calibration works to it.
So, the conclusion is, that even for some reason first times the reset didn't work, it did help after all. Just backup your data and give it a try. Doesn't cost more than some time. The compass DOES stuck still but is most of the time usable.
At least I left out MoreLocale2, Metal detector and some games. And I DIDN'T calibrate G-sensors after reset.
So, there is still some issues with update and compass but it COULD also be somewhat application related...
G-Sensor calibration might be the answer! Following the first factory reset yesterday which cleared the compass problem initially I reinstalled all apps and calibrated G-sensor to find the problem came back. Then I factory-reset once more last night and reinstalled all apps but didn't do the re-calibration, left the phone on for the night - no problem in the morning. Feel tempted to re-calibrate to proof the point now.
Please inform here how did it do if you re-calibrate. I have an ongoing geocaching challenge, so I won't try that until I'm sure that I don't need the compass for couple of days. After that I'm going to test if calibration is the problem as soon as possible.
I have the same problem. Have tried everything but hard reset. Still, compass worked a lot better on 2.1 :-(
Sent from my HTC Desire using XDA App
nitemarc said:
@JLillia: Also in my case the compass worked as intended on android 2.1.
Anyway thanks for your answers guys! I really appreciate it! So it looks like at least 3 folks here are experiencing some issues with digital compass after the upgrade to the Froyo on HTC Desire
Wonder if there is anyone here who could disagree with us and say that the upgrade didn't cause any compass degradation on his/her device at all...
Click to expand...
Click to collapse
My compass works fine on HTC Desire on Android 2.2.
Try 3d compass, and use its calibration option. Always works for me.
Sent from my HTC Desire using XDA App
nitemarc said:
Just a quick update, I made a quick phone call to HTC support this morning and raised that issue. The support analyst recommended the factory data reset to see if it helps. I guess it's just a standard answer so at this point of time I'm not gonna proceed with that and erase all data on my phone. (Btw, I wonder if it's possible to backup all current data from my unrooted, unbranded Desire?)
Furthermore he promised to get back to me in next few days with some official resolution of that issue so I will keep you updated.
Click to expand...
Click to collapse
Wonder how does HTC support team's SLA look like in terms of resolving client's tickets as my one hasn't been resolved yet... Anyway it seems to me that HTC is not going to confirm that OTA update to Froyo could caused that compass issue.
That's why I decided on factory data reset and it looks like that helped with getting this issue sorted out. After the hard reset, my first step was an initial compass calibration and that's really all what I did. The digital compass is not maybe so precise and accurate as it used to be on Android 2.1 but finally roughly (I would say with 15° margin) points out the north so there is a progress
Just to add my 2c, I can confirm that the compass has become useless since I upgraded to 2.2 on my device. Doing the figure 8 in Compass app has short lived benefits.
Sent from my HTC Desire using XDA App
Neither does my compass react in any application (tried Compass, Places directory, Google Navigation) after update to Froyo.
Calibrating with the 8 movement or G-sensor calibration does not help at all.
However, it always starts working normally when I tilt the phone to the side (so that I look on the slim side of the phone) and then start a short forward and backward rotation with the rotational axis going thru the display.
I need to repeat this every time I unlock the phone and the compass keeps on working until i lock the phone again or until I switch the application.
Weired.
I have the same problem, and it is a bit annoying. The compass works correctly if I wave the phone like in the video posted, but I have to do this every time I start an app that uses the magnetometer. My phone was not like this on 2.1.
Hello,
The screen of my moto 360 goes randomly off and vibrates at that moment, just like when you dim the screen with your hand., but now I'm using it. It's very frustrating because I can't even open an app normally or the screen goed of and I need to start over again. Does anyone know how to fix this?
Having same issues with mine.
Really strange and really annoying. Its like when u cover it with palm. It vibrates and screen goes off but ur in the middle of trying to do something. Anyone else having this problem?
Glad I'm not the only one having this issue, just got my Moto 360 today. I'll be in the Settings or other parts of the watch and it will just randomly turn off. It is really frustrating to deal with.
I have the same issue. I have pretty hairy arms so I wonder if the hairs are somehow triggering the capacitive touch screen.
you guys try to do a reset on the watch yet?? not just a reboot..
Any updates on this? I'm having the same issue
Any updates? I have the same issue I think it happend after udate to 5.0.2 but I'm not sure.
I'm also having the same problem. I picked up a new Moto 360 during the BBY sale rush of the last couple of days. At first it was buggy but the screen seemed to stay on while working with it. Then it had a system update, and since then most bug issues (like the faces not updating with the companion app changes) went away, however from that point the screen constantly shuts off, usually with a little buzz, while I'm interacting with the watch.
For instance, regarding the sensor used to turn off the watch if you palm it. I thought maybe that was it, so I was looking for a way to turn that off. I went into settings, and spend about 10 times of the screen shutting off before I could get to "accessibility settings" just to see if that might be there.
This problem occurs whether I'm wearing the watch or not (trying to eliminate arm hair or similar), and has occurred after a factory reset and re-pair with my phone (Note 4). Ambient sensor settings don't help, because all that does is make the screen go dark instead of off, but it still reverts back to the clock no matter what I was doing.
Any ideas? Any way to turn off a sensor perhaps, maybe in a custom ROM? Since this seems to be associated with an update near as I can tell, I wonder if a fix is coming from Moto or if it's too rare of an issue to be on their radar.
As an update, I replaced the watch with a new one, and this new watch is perfect. It started on outdated software which I left on for a bit to make sure it didn't show the problem, then I updated. Still no issues. I think there is a chance the problem is software regardless, but either way it must be a small portion of watches and isn't necessarily tied to any particular outside software influence (phone model or android version, or installed apps as NONE of those things changed). My advice to people reading this thread is to exchange the watch or get an RMA if possible.
Same Issue
Hi All,
I have the same issue. Sent it back for repair so let's see...
Same issue here as well
I recently bought a Zenfone 2 (ZE551ML) which works exceptionally well however today I've noticed something odd (probably would have noticed it before but the phone was actually a gift so not at all times with me).
During a call the proximity sensor will only turn off the screen when the phone is close but it will not turn the phone on when I move it away. I've gone through many online articles and in the majority of cases it was a problem with the screen protection. However, I do not use any kind of screen protection.
Additionally I've noticed something really odd. Zenfone 2 has an inbuilt testing suite (SMMI Test) which allows testing various parts of the hardware. The proximity sensor test consists of three steps (NEAR, AWAY, NEAR). They should be self-explanatory (NEAR triggers when an object is close, AWAY when its far). In my case the first step (NEAR) always triggers after the test starts but the other two (AWAY, NEAR) simply won't. That's until I use the app switch button (next to the home button) to re-enter the test application again. The other two steps then complete successfully.
Considering the behavior can I rule out a hardware problem and pin the issues to the software?
The proximity sensor issue was successfully resolved by reverting back to the 2.20.40.90 firmware. The 2.40.40.97 version (at least WW) obviously has issues with it.
You can find detailed instructions on how to perform stock recovery in this topic (http://forum.xda-developers.com/zenfone2/help/reverting-to-stock-firmware-t3225632).
Once again props to kanagawaben and all the people which contributed to this topic.
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!
Hi guys,
Lately I've noticed that my fingerprint sensor does not work properly anymore.
Not sure if it's a hardware or software issue?
Though, the test HW for Fingerprint Sensor from Smart Doctor app reports Good status during all tests.
The behavior is strange and not consistent, most of the times it will work fine but from time to time I cannot unlock/wake the phone with the fingerprint sensor, it's not like the fingerprint is not recognized, it's more like putting the finger on the sensor and nothing happens (it doesn't vibrate like is reading it or not) . Not sure if is related to the phone being in standby for longer period, or I don't know ...
I'm more inclined to believe it's a software issue, and seems to have occurred lately after last update to Android 10 (v30f-EUR-xx, phone type LM-G710EM).
I've tried may method, deleting the finger prints and add them again , even did a factory reset but the issue seems to come back.
Do you guys have such issue?
Any idea how to diagnose this further?
dinoc said:
Hi guys,
Lately I've noticed that my fingerprint sensor does not work properly anymore.
Not sure if it's a hardware or software issue?
Though, the test HW for Fingerprint Sensor from Smart Doctor app reports Good status during all tests.
The behavior is strange and not consistent, most of the times it will work fine but from time to time I cannot unlock/wake the phone with the fingerprint sensor, it's not like the fingerprint is not recognized, it's more like putting the finger on the sensor and nothing happens (it doesn't vibrate like is reading it or not) . Not sure if is related to the phone being in standby for longer period, or I don't know ...
I'm more inclined to believe it's a software issue, and seems to have occurred lately after last update to Android 10 (v30f-EUR-xx, phone type LM-G710EM).
I've tried may method, deleting the finger prints and add them again , even did a factory reset but the issue seems to come back.
Do you guys have such issue?
Any idea how to diagnose this further?
Click to expand...
Click to collapse
Make sure your battery isn't swollen. A swollen battery will take out the fingerprint sensor first because it's right on top of the connection.
Hmm, interesting, from the outside I can't feel any difference, the back seem flat.
Exactly the same problem here. But if I check the sensor while it is not working I get a "sensor not respondong error".
Did you solve somehow?
Thank you