Related
Hello all,
Sorry if this was covered already, but I couldn't find anything about it.
After updating to 2.2 (OTA), Google Sky Map orientation seems to be acting weird. If I hold it so that I can see the horizon, with the phone in front of me, then spin around in a circle, the program doesn't pick up that movement. It used to work fine in 2.1.
Anyone else experiencing similar problems?
No problem here. Sounds like your compass. Do you have the same prob in street view?
Yes, same problem with street view.
I noticed that if I turn the phone around a bit, tilt up and down while rotating it, then it starts to work. As soon as I kill the app and start it again, I have to do it again. It's as if it's doing some calibration on the g-sensors while the app is running, which is then forgets when the app is killed.
Again, the exact same behaviour happens on street view and sky map.
Same thing is happening with the "Compass" app. At least this one gives me some feedback: "Abnormal magnetic field detected. Please calibrate your device". Doing a "figure-8" calibration solves this in every app, but the problem is that it never stays calibrated. I'm hoping someone else will be able to chime in with a possible fix before I try to do a full factory restore.
If anyone else is having this problem, a factory reset fixed it.
It's a bit of a shame because now I don't know what was really causing the problem.
I'm glad I am not the only one having this problem but I am not going to reset the phone. Has anyone called Sprint about this issue? If I have to reset this thing then I will be resetting to different hardware and a Windows 7 device in a few months.
Going to call Sprint to find out what they can do.
LabRat02 said:
I'm glad I am not the only one having this problem but I am not going to reset the phone. Has anyone called Sprint about this issue? If I have to reset this thing then I will be resetting to different hardware and a Windows 7 device in a few months.
Going to call Sprint to find out what they can do.
Click to expand...
Click to collapse
I am afraid that factory reset is gonna be only one possible solution. Take a look at this thread: http://forum.xda-developers.com/showthread.php?t=747398 I faced similar issue on my Desire. In a nutshell, all apps using embedded compass functionality just acted up (including Google Sky Map) after OTA update to 2.2.
I had a similar problem and then realised it was the magnetic clip on my case causing the problem
Sent from my HTC Desire using XDA App
I've experienced the same problem too.
When I started skymap, the orientation didn't change, no matter how much I was waving the phone.
But today I tried to just uninstall it, reboot and then install it again. Strangely enough, now it's working again .
So you could probably try that first before considering hard reset.
Every time I use a program that uses the compass I do this trick or the compass wont work for me
http://www.youtube.com/watch?v=sP3d00Hr14o
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.
Hey folks, I've got SyndicateROM Frozen running, and have the following problem:
When I use Google SkyMap, it won't let me see above the horizon. If I use GPS Test, which shows pitch/roll, it'll detect up to 90 degrees up, but doesn't seem to register anything higher than that. I mean: when I hold the phone flat on a table, no problem. Pick it up, and face it in front of me so the screen faces me, no problem. Tilt it upward so the camera is looking at the sky, and it doesn't seem to register.
I've tried calibrating compass, accelerometers (with the GPS Test tool, and with sensorcalibutil_yamaha), but to no avail. Tried the calibration tool in system settings, too.
This happens with any Froyo build/ROM I've tried. Did battery pull, etc., no go.
Anyone have any suggestions?
Finally someone else has asked about this. There is an app called "Surveyor" that is used to measure distances with the camera but ever since I started using custom ROMs it isn't able to find horizon. Any help with a possible fix would be appreciated.
Sent from my SPH-D700 using XDA Premium App
I had a problem similar to this (the compass was pointing way off and very erractic). I used an app called Sensor Debug and found that my pitch axis was reading -178 lying flat on a table. I went into the phones display settings and chose the Horizontal Calibration, put the phone upside down flat on a table, but hanging over it so I could reach under and push the Calibrate button. This worked for me like a champ! (Calibrate upside down). I noticed this after the OTA Froyo.
I have the same issue as the OP. I tried installing that sensor debug and it showed 0 for pitch and 0 for roll when laying flat... note... I put it flat but with the camera hanging over the edge of the table.
Anyways, Google Skymap fails for me too...
bump... any word... hopefully from a dev on what is happening?
Not flat with the camera hanging off... upside down flat.. screen side down.. with enough of the screen hanging off to hit the calibrate button..
Sent from my SPH-D700 using XDA App
Hmph.
Welp, looks like I've got to post here, as I'm a new enough member and don't have the necessary # of posts to post to the Developer forum!
In case anyone from the ACS/SyndicateROM team is reading this: AWESOME JOB. Flashed EC05 and Takiya (1.1.0) without a hitch. Amazing that it just keeps all data/settings. I can't thank you guys enough!
Back to the point of this thread: Accelerometers are still not working correctly, even with EC05. I've re-tried:
- Android horizontal calibrate (under settings) both screen up and screen down
- system/bin/sensorcalibutil_yamaha, both screen up and screen down
- Battery out/battery in
- Recalibrate from within GPS test.
Good news is compass works, GPS works. Within GPS test there's a pitch/roll sensor. Doesn't seem to want to register above 90 degrees.
If someone is running EC05/SyndicateRom 1.1.0, would you try running Google SkyMap and see if you can see above the horizon? Basically, I can tilt down and look at the Nadir, but when I tilt up, no matter how far I tilt up, in landscape or portrait mode, it won't show anything above the horizon.
Thanks!
EDIT: Er, the app I use is called "GPS Status," it has the pitch/roll/calibrate stuff.
It seems to work for me (running SRF 1.1.0).
Unless I'm just interpreting what I see incorrectly, but if I start out pointing down, and gradually shift to pointing up, it crosses what I assume is the horizon (because it has directions like north/south written on it) and keeps going.
I'm pretty sure it worked for me on previous versions of SRF though.
Hey all
Haven't found anything online about this, but has anyone noticed their HTC One gestures launching without the phone coming out of pocket?
Mine has launched the camera app, tried to voicedial someone, and been in the clock when I got the phone out to open it.
I was wondering whether anyone had noticed it, and whether the fact that you can interact with the screen without touching it is the culprit of my woes.
I didnt have the issues with the HTC supplied case, but as that has degraded in the days i've had the phone, i'm using it naked and my problems began.
Cheers.
Same to me.
Glad it's not just me. Lets hope it's tweaked in updates.
Hi,
I have a UK sim free model. It sometimes misinterprets a tap or adds a phantom tap. Its not terrible but I'm sure mine has a issue. A quick Google and a tweet tell me I am not alone. Anyone else seeing this? I could return but I'm dubious it's hardware related...just not sure if it's worth waiting for a software update...
RealEvil_UK said:
Hi,
I have a UK sim free model. It sometimes misinterprets a tap or adds a phantom tap. Its not terrible but I'm sure mine has a issue. A quick Google and a tweet tell me I am not alone. Anyone else seeing this? I could return but I'm dubious it's hardware related...just not sure if it's worth waiting for a software update...
Click to expand...
Click to collapse
I have same issues with my g4 here in the US.
Unfortunately same here, on a G4, korean model F500S.
I have the same issues on my G4. So probably returning it won't solve it. I notice it the most when I am scrolling in Facebook or web pages I will open a link accidently.
I have the same, occasionally it just won't respond to some taps, i find just pressing the standby on/off button quickly sorts it but it is very annoying.
same here in israel, sometimes do not respond to double tap on lock screen to wake the G4 up
im sure its a software issue, prolly the LP 5.1
Are so you guys using screen protectors? That was the issue for me with g3 and g2.
20degrees said:
Are so you guys using screen protectors? That was the issue for me with g3 and g2.
Click to expand...
Click to collapse
I am using the out-of-the-box protector on G4. So the thing u mentioned was it with this kinda protector or after-market glass protector?
Try...SGS Touchscreen Booster - Google Play Store
I have run into this same problem with my Verizon G4 (VS986). Many of my taps have gone unrecognized.
I did find this.... http://forum.xda-developers.com/g4/help/fix-touch-screen-registering-touches-t3128518
I tested the software that was recommended...and IT WORKED!
Give it a try...can't hurt!
nipun1110 said:
I am using the out-of-the-box protector on G4. So the thing u mentioned was it with this kinda protector or after-market glass protector?
Click to expand...
Click to collapse
After market but plastic.
Just started to get issues where taps on the far left-hand side of the screen don't work.
blackknightavalon said:
Just started to get issues where taps on the far left-hand side of the screen don't work.
Click to expand...
Click to collapse
Okay, I was able to replicate my bug. It happens after playing a game and stops after some time. Turning autorotate back on and switching back and forth from landscape view fixed it.
Hey guys.
I was searching the forums for a fix that solves the phantom/ghost touches I'm getting frequently on my LG G4, H815 model.
Sorry for the long post but my case looks a little more complex than the ones I've been seen in here.
In my case, that's how it happens:
I receive several multi-touches at the same time, usually when Data is enabled. Sometimes it starts right when I switch from Wi-Fi.
It happens often when I'm driving and using Location+Data as well, which drives me crazy. I does also happens (like another user mentioned in this thread) when scrolling down a feed (such as on Facebook) and it suddenly likes/shares a photo/post. It also drives me crazy! And there is also the case where it taps the keyboard and send crazy typos on chat apps when you are real-time texting someone! Another hassle is right after using the camera and opening the gallery to show someone the taken photo...it suddenly scrolls the gallery and open another photo. I just can't make it to see the taken pic. Therefore, I really wanna fix this so bad since it happens every time I need something right away.
A workaround that's been helping, though it's a pain:
I found that pressing the On/Off button and giving it a few seconds will return it to a normal state. The problem is when it happens while I'm driving and are supposed to take an exit/make a turn at the moment. There are some other cases where I'm into something and giving this few seconds is not an option.
Trying right now:
Someone suggested in this thread to use the SGS Touchscreen Booster. I'm giving it a try right now.
Important notes:
This issue has been happening since I got this phone on November, 2015. We got this 6.0 update recently and I was hoping that it would fix it. It didn't.
I have an after market screen protector that I applied in order to see if the issue would go away. It also didn't.
I have been searching about a digitizer replacement but I don't think is a hardware issue, since it just doesn't happens when I'm only on Wifi at home with Data disabled. I believe that the problem is the Data connection that triggers smth.
Any thoughts?
Does anyone have any idea or have experienced the same scenario before? Any thoughts on my guess of data enabling triggering the ghost touches?
Sorry for the long post and thank you so much for reading it.
I think it's both, its hardware and software, LG tried to fixed it but it makes it worst. You can solve the problem for few seconds putting your five fingers at the home menu, It goes crazy and after it stopped making ****. Anyway this phone is great but all the problems make it ****.
I am going to use this thread even though I think my problem is not as serious as yours are.
My problem is that touches are registered, but no action is taken.
For example. Quickly tapping on an icon on the home screen will highlight it, but it will not open the application. I enabled the option in Developer mode to display the touches and the touch is registered. It's just that the app will not load. If I click for a tad longer - it loads. Happens on both stock Launcher and Action Launcher. I have not noticed it happening outside the launcher.
I read something about a keyboard update, but in the Update Center I don't have anything related to the keyboard.
The icons I see it happening with are located in the lower part of the screen.
I am almost sure that this is a software problem, but several updates have not fixed it. Currently on v20d.
Any suggestions or ideas?
After a few more testing and monitoring, I found out that the ghost touches only take place when I'm on LTE.
And even more weird, while driving through some specific areas when I'm commuting.
It's just so weird to think that some towers may send a LTE signal that may cause the ghost touches.
At home, at work, wifi or data, it doesn't happen.