Database Develop

[Q] Phantom Taps, Bad Screens?

Does anyone have a solution for phantom taps on your NC?
I'm on my 3rd Nook Color when I pick up the replacement unit this afternoon.
My general issues are phantom taps - or the NC doing things I don't want it to. So far a very poor experience when typing, turning a page in a book, or even just navigating the ui. The whole issue may be me, it happens regardless if I am plugged in or not. I keep a very clean screen so there is very to little gunk.
I do have sweaty palms on occasion but not out of the ordinary. I have other touch devices that have never given me this issue. If anything I think the screen is overly sensitive - hardware or software issue?

Nope it's not just you. Mine has a multitude of issues with the touchscreen...
Essentially I cannot use the touchscreen when the device is plugged into stock charger/cable as wherever I put my finger, a random touch appears somewhere on the x-axis near my finger.
It seems that the device does not like changes in temperature or humidity either when it is unplugged. Using my tablet while cold was impossible, and likewise while it had been warm.
I'm on my second tablet from Best Buy-- the first one had dead pixels galore (enough to make the best buy rep say "dang!"), and now this one has a bad touchscreen and hard to press power button.
However: I purchased one of these for my mother a few days before mine at Barnes and Noble, and it has no issues whatsoever... at least not yet.
I've come to the conclusion that this hardware is quite beta, but I'm willing to give them a chance since it is the best bang for the buck, even if I have to go through a couple of returns... it's honestly almost worth the time for me since a tablet is so valuable for schoolwork.

Fortunately mine does not do this. I think maybe for those that are having this issue it may be able to be fixed in a firmware update.
My EVO had extremely similar problems when it first came out with the touchscreen and not being able to use the dropdown menu while the device wasn't grounded. After a firmware update the phone was great with touch sensitivity.

my first one did this also. so far the second is doing fine, but the first didn't have any problems till the 13th day of owning it.
i'm hoping it's just an issue that can be fixed via software - maybe someone put an incorrect voltage input somewhere.

I was having the same issues. I bought a screen protector and that seemed to solve it. So far, it's been working fine.

I noticed the screen protector stabilized the touchscreen a lot. Before I seem to have a problem finding the sweet spot for a touch. Now it seems better.
However, my phantom pinky is always touching something while I am trying to navigate. As long I only get one finger near the screen, it's fine.
Mine came from B&N.
The only other issue I have is the magnetic clasp in the cover seems to throw the internal compass/magnetometer off a lot.

Awats said:
The only other issue I have is the magnetic clasp in the cover seems to throw the internal compass/magnetometer off a lot.
Click to expand...
Click to collapse
Considering the Nook has neither I think you are okay.

khaytsus said:
Considering the Nook has neither I think you are okay.
Click to expand...
Click to collapse
Then how is it managing to correctly position the screen with Google Sky? Is it just spooky smart?

Mine only has problem when screen gets dirty. Try a screen protector or use gloves.

is there really a compass in this thing? I just assumed there wasn't. if there is I'm buying another tomorrow!

Screen protector helps to solve my problem.

Are you seeing more issues right after cleaning the screen? I see issues then and I think it is because I an using some moisture on the cloth. If I just dust it lightly with a dry cloth and live with a few finger prints there seem to be less of an issue.

Awats said:
Then how is it managing to correctly position the screen with Google Sky? Is it just spooky smart?
Click to expand...
Click to collapse
Wifi location services provided by Google from data collection by Street Cars or by Location Services on Android phones.
iolinux333 said:
is there really a compass in this thing? I just assumed there wasn't. if there is I'm buying another tomorrow!
Click to expand...
Click to collapse
....no

khaytsus said:
Wifi location services provided by Google from data collection by Street Cars or by Location Services on Android phones.
....no
Click to expand...
Click to collapse
Oh well, it could be worse although I don't see how Google data can tell which direction I am facing.
Thanks dad!

Awats said:
Oh well, it could be worse although I don't see how Google data can tell which direction I am facing.
Thanks dad!
Click to expand...
Click to collapse
Nor can your Nook Colour.. Using something like TetherGPS would have some heading information, but the NC itself without help would not.
It might show 0, dunno there. Maps for me just shows a dot, if yours is showing different, that'd be... interesting.
For S&G I tried "Compass", it of course FC's immediately like almost all apps that try to use the GPS. Enabled TetherGPS (with no server, just the client) and it ran, but of course no data, no heading, etc.

Is this occuring when the nook is plugged in? sometimes the charger can cause phatom touches with the touchscreen. Cleaning the screen and being on a stable ROM usually gets rid of that problem.

If only I weren't so stupid ...
khaytsus said:
Nor can your Nook Colour.. Using something like TetherGPS would have some heading information, but the NC itself without help would not.
It might show 0, dunno there. Maps for me just shows a dot, if yours is showing different, that'd be... interesting.
For S&G I tried "Compass", it of course FC's immediately like almost all apps that try to use the GPS. Enabled TetherGPS (with no server, just the client) and it ran, but of course no data, no heading, etc.
Click to expand...
Click to collapse
LOL! Ok, I sat down with it and played for a bit. It appears some tilt sensor is handling the up and down tilt. If you raise the screen over your head, it shows those stars and if you tilt it down, I see what is below the horizon. That is pretty consistent. But it's also "simulating" a compass inadvertently.
By that I mean that if I happen to turn it on facing north, it appears to track as you turn in a circle but it's really just me tilting it and it's rotating he view. If you do it enough it has no clue the direction it's facing.
I'm just glad I figured this out before I got lost in the Amazon.

Just got mine plugged it in and unplugged and within stew minutes phantom touches couldn't even reboot it im on cyanogen mod 7
Sent from my SCH-I500 using XDA Premium App

Nook Screen Recalibrate
You guys can try my app from the market

assid2 said:
You guys can try my app from the market
Click to expand...
Click to collapse
Wow, it seems to have improved the accuracy! I need to play with it more to be sure.

Droid 3 GPS Issues

I have had continuous issues with the Droid 3. One of my biggest issues is that the GPS seems completely unstable. I have tried turning on/off GPS options, etc...
Weather I try to use Google Maps or another application such as Endomondo, it cant maintain a lock. It seems to be able to locate me within 12 - 30 feet and then within a mile!!!
Using an application like Endomondo (running, cycling, etc), is completely useless. It can't track my location at all and when it does lock on, it only holds for a few seconds and then gone again.
I took the phone in to Verizon with a complaint about the GPs and screen issues (http://forum.xda-developers.com/showthread.php?t=1239980) and the rep said both were normal for this phone...
Has anyone figured out a way to resolve this problem?

I, too, have the same issue with GPS. I use SportyPal Pro, and cannot use my Droid 3 when running/walking. I can go for a 5 mile run, and SportyPal will show I had ran 6 miles. I can run north to south in a straight line, and when finished, SportyPal will show that I went east and west as much as 400-500 feet off of that straight line and because of that can add anywhere from .1 miles to .5 miles to that 1 mile run.
It is so unreliable that I will use my older decommisioned Droid2 to run with. It works perfectly with the same software.
If anybody has any suggestions, I'm all ears.

bishop0114 said:
I have had continuous issues with the Droid 3. One of my biggest issues is that the GPS seems completely unstable. I have tried turning on/off GPS options, etc...
Weather I try to use Google Maps or another application such as Endomondo, it cant maintain a lock. It seems to be able to locate me within 12 - 30 feet and then within a mile!!!
Using an application like Endomondo (running, cycling, etc), is completely useless. It can't track my location at all and when it does lock on, it only holds for a few seconds and then gone again.
I took the phone in to Verizon with a complaint about the GPs and screen issues (http://forum.xda-developers.com/showthread.php?t=1239980) and the rep said both were normal for this phone...
Has anyone figured out a way to resolve this problem?
Click to expand...
Click to collapse
Sadly, I have the same issues.

Well with only 3 people chiming in, maybe it is bad hardware?

bishop0114 said:
Well with only 3 people chiming in, maybe it is bad hardware?
Click to expand...
Click to collapse
God, I hope not. I have enough problems with this phone as it is.

No problems with GPS for me
Sent from my DROID3 using xda premium

kshen1 said:
No problems with GPS for me
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
Are you using it for navigation only? Or a similar application for running/walking?
The reason I ask is because I do not notice a problem during navigation. It works great for that without any problems. Until I get to downtown Chicago. I almost expect problems there. Even with my Droid2.

i've only had issues with my gps in areas with lte. when im at college im in a city with lte support and my gps doesn't work (my friend who has an X also has issues with his gps when in areas with lte). when im home where there isnt lte support my gps works fine.

No it's not hardware mine works flawlessly and almost instantly fixes position, tho i have modded the gps.conf found in the etc folder. Details for tweaking this for your region can be found here:
http://forum.xda-developers.com/showpost.php?p=13537801&postcount=1
Many thanx to 75markus for this.
Since we don't have a recovery yet to flash a zip you will need to edit the gps.conf file manually.
Oceanic region can be found in my sig below apart of my camera mod.
-smc

The problem I was having with the GPS from Day 1 is that I would occasionally notice that it would not start up at all when openning a GPS-dependant app (such as Maps or Weatherbug, etc). Whenever that happened, I would have to restart the phone, and then the GPS would be able to initialize again... at least, for a while.
Eventually, I was digging around in the setting and found the "VZW location services" option under "Location & security settings". I unchecked that option and, ever since, I've had no problem with the GPS. It seems that th VZW-based location services were causing the problem. Of course, since then, I've rooted and frozen all of the VZW bloat, so I might be able to turn that option back on with no ill effect. Still, it was as simple enough fix.
My issue might not sound exactly the same as yours, but you could give this a try and see if it helps.
-SR-

I'm not having any GPS issues on my phone. Perhaps it's based on the area your in?
I know it's satellite but.. just a guess.

WarER4X said:
The problem I was having with the GPS from Day 1 is that I would occasionally notice that it would not start up at all when openning a GPS-dependant app (such as Maps or Weatherbug, etc). Whenever that happened, I would have to restart the phone, and then the GPS would be able to initialize again... at least, for a while.
Eventually, I was digging around in the setting and found the "VZW location services" option under "Location & security settings". I unchecked that option and, ever since, I've had no problem with the GPS. It seems that th VZW-based location services were causing the problem. Of course, since then, I've rooted and frozen all of the VZW bloat, so I might be able to turn that option back on with no ill effect. Still, it was as simple enough fix.
My issue might not sound exactly the same as yours, but you could give this a try and see if it helps.
-SR-
Click to expand...
Click to collapse
I have been experiencing the exact same problem and temporary solution (restarting) since day 1, on both my first and second droid 3's. Difference is, I've had VZW location services unchecked since around the time I first got the phones, and I am still experiencing the problem... even as recently as last night. I just double-checked the setting, and indeed, VZW location services is stil unchecked.
Once I have lock I usually have no problem continuously using GPS. Last night, I tracked a two and a half hour walk using the My Tracks app, including a 45 minute stop for dinner indoors. For the first 10 minutes, it couldnt find a signal, so I restarted. It got a lock almost instantly following the restart and never lost it after that. I had the app running for the whole excursion. As expected, it got a little confused while I was inside, but automatically picked the signal right back up when I got back outside and tracked my entire walk back home.

a_lazy_dude said:
I have been experiencing the exact same problem and temporary solution (restarting) since day 1, on both my first and second droid 3's. Difference is, I've had VZW location services unchecked since around the time I first got the phones, and I am still experiencing the problem... even as recently as last night. I just double-checked the setting, and indeed, VZW location services is stil unchecked.
Once I have lock I usually have no problem continuously using GPS. Last night, I tracked a two and a half hour walk using the My Tracks app, including a 45 minute stop for dinner indoors. For the first 10 minutes, it couldnt find a signal, so I restarted. It got a lock almost instantly following the restart and never lost it after that. I had the app running for the whole excursion. As expected, it got a little confused while I was inside, but automatically picked the signal right back up when I got back outside and tracked my entire walk back home.
Click to expand...
Click to collapse
When you look at your walk on the map, is it true to where you actually walked? If I do that same walk on my phone, it will show me deviating off course as much as a 1/2 block and then back. I can tolerate that deviation once and maybe twice during my runs/walks. However, mine does it the majority of the time, adding bogus mileage to my walks/runs. In an hour's time, it will deviate approximately 20-30 times.

eallison978 said:
When you look at your walk on the map, is it true to where you actually walked? If I do that same walk on my phone, it will show me deviating off course as much as a 1/2 block and then back. I can tolerate that deviation once and maybe twice during my runs/walks. However, mine does it the majority of the time, adding bogus mileage to my walks/runs. In an hour's time, it will deviate approximately 20-30 times.
Click to expand...
Click to collapse
Just took a closer look at the track it recorded. I definitely do see these kinds of deviations, but they seem to only be in areas where I think it'd be reasonable to expect them. I live in a suburb, so I don't have any tall building to mess with the GPS reception, instead, I have somewhat steep hillsides. It seems I get a fair amount of deviation in the (significantly) hilly areas (it looks like I was walking down people's driveways, then across their front yards, when in reality I was just walking more or less straight down the sidewalk), but in the flat areas the line has almost no significant deviations, just some minor noise. Next time, at the risk of my fiance calling me a geek, I'll take my Droid 1 along for the trip, and see how the two records compare.

a_lazy_dude said:
Just took a closer look at the track it recorded. I definitely do see these kinds of deviations, but they seem to only be in areas where I think it'd be reasonable to expect them. I live in a suburb, so I don't have any tall building to mess with the GPS reception, instead, I have somewhat steep hillsides. It seems I get a fair amount of deviation in the (significantly) hilly areas (it looks like I was walking down people's driveways, then across their front yards, when in reality I was just walking more or less straight down the sidewalk), but in the flat areas the line has almost no significant deviations, just some minor noise. Next time, at the risk of my fiance calling me a geek, I'll take my Droid 1 along for the trip, and see how the two records compare.
Click to expand...
Click to collapse
I've attached screenshots from two runs. D2 is this morning's run with my Droid 2. It's flawless. D3 is the last run I did with my Droid 3. Looking at it you can understand my disgust with it. Ignore the big missing section from both shots. I wouldn't want anyone knowing the exact location of where I live. Someone might come steal my Droid 3.

eallison978 said:
I've attached screenshots from two runs. D2 is this morning's run with my Droid 2. It's flawless. D3 is the last run I did with my Droid 3. Looking at it you can understand my disgust with it. Ignore the big missing section from both shots. I wouldn't want anyone knowing the exact location of where I live. Someone might come steal my Droid 3.
Click to expand...
Click to collapse
WOW... That is awful but a great example of the concern with this phone. You are actually doing much better than me. Mine is only able to triangulate down to about 20 feet and then it bounces between 20 and 300 feet!!!
I am going to call VZW today and see about a replacement phone but I doubt it will resolve the problem.

I just called VZW and once again, they said the accuracy was normal... They said none of their phones can lock on with the accuracy I described and if it has, I have been lucky. He said their phones are only accurate within 500 feet!
I explained to him that with that accuracy, it would be totally useless to use as a navigation device...
He looked through their documentation and said he has no record of other people having issues with the GPS... He also said he has no record of the blue tint when taking pictures.....
Oh well. I hope the replacement fixes it...

bishop0114 said:
WOW... That is awful but a great example of the concern with this phone. You are actually doing much better than me. Mine is only able to triangulate down to about 20 feet and then it bounces between 20 and 300 feet!!!
I am going to call VZW today and see about a replacement phone but I doubt it will resolve the problem.
Click to expand...
Click to collapse
With that kind of change in accuracy, it seems like it isn't using the GPS as all, but just the cell towers. Is the GPS logo showing in the notification bar when that is happening? If it's there, is it blinking or solid?
-SR-

bishop0114 said:
I just called VZW and once again, they said the accuracy was normal... They said none of their phones can lock on with the accuracy I described and if it has, I have been lucky. He said their phones are only accurate within 500 feet!
I explained to him that with that accuracy, it would be totally useless to use as a navigation device...
He looked through their documentation and said he has no record of other people having issues with the GPS... He also said he has no record of the blue tint when taking pictures.....
Oh well. I hope the replacement fixes it...
Click to expand...
Click to collapse
My humble opinion of VZW representatives...they're all full of BS. They're going to tell you what they need to tell you to get your out of the store or off of the phone if you're not buying anything. A representative's main concern is sales. Sell him another phone, renew his contract, add a line, add a feature.
This issue may be better addressed to Motorola directly. I may make that phone call today.

I just got off the phone with Motorola tech support. Same story as VZW gives. There are NO known issues with the Droid 3. I asked about the GPS, the bluish pics the cam takes and battery life. The only thing the tech would say is the phone "needs to be evaluated"

[Q] Note 3, Google Maps, & Arrow Pointer

All
I've been having a really annoying issue with my Note 3 and Google Maps: the dot-arrow that shows my position is pointing in the wrong direction. Yes it does track me per the gps location but the issue is that as I am driving instead of the screen moving from up to down, usually along the length-wise direction, it moves at an angle or across. The only option I have is to hit the location button so that I can always have the top be North. That's not as good as having the heading pointing to the location of travel. Now, I calibrated and recalibrated the compass with GPS Status App (turns around the axes and figure eights) which seems to have worked for some, I have restarted numerous times even after turning on/off location-based services. I have cleared the cache and the google maps data. I have reinstalled it. I have even checked the compass versus real settings - seems to be pointing in the right direction. I still have the same issue. This is very frustrating and disorienting when driving. Looks like a crab moving angled to sideways across the screen.
I am on the latest Stock KitKat 4.4.2 version and Maps 7.7.0.
So, does everyone have this issue? Does anyone think is is a unique configuration issue? Is this a google maps issue? Any thoughts on how to fix?
PS...other Map Apps seem work fine (but like to use Google Maps due to the excellent traffic option)

If other apps seem fine, it might be Google maps. I don't have that issue, but I use Google maps version 6.14 (the old style with location arrow). The note 3 is notorious for all of its gps issues, but if you have good signal and it doesn't cut out then all I can think of is that GMaps is the culprit.
Sent from my SAMSUNG-SM-N900A using Tapatalk

I noticed this issue too! I believe it has to do with being inside a vehicle. The metal may be interfering with the gps signal. If I sit in my car and hold my phone so it points north, the arrow points south. If I open the door and step out (while still pointing north) the arrow magically flips! I can fix it by doing figure 8's in the car, but what a pain!!

Well, I do agree it is a google maps issue. I wonder if I can install older version to check. It only recently happened to me. I do not think it is an in-car issue because I never had the issue before when I was navigating in the car. Will come back if I can side load an older version of gmaps.
By the way, this issue is all over the internet but none of the foxes suggested seem to work for me.

No luck in getting it fixed. Did back down to earlier version of 7 but still had the same issue. Driving me nuts.

navfree... can preload maps but just uses google search for most things. some things arent great but its getting better. ive had the same issue with google maps. its been super sporadic. not a deal breaker...

So excited when I started reading this thread, figured someone would have a solution...lol Had this problem ever since my GSII Skyrocket, the gps works great but the direction is always off in my car... Can't understand what the problem is. Done the calibration to no effect... Hopefully someone who knows how to fix will pop in and steer us in the right direction...lol

I'm also waiting for a fix for this..
Ever since 7.0 "update" its been like this. I tried everything but no luck.
I'm using Exynos Note 3.
I was using an HTC EVO 3D when I recieved thr 7.0 update. Before it was fine but after the update even my HTC started doing the arrow pointer bug, and its still happening on my Note 3 even after the yesterdays maps 8.0 update. So I'm thinking this is all Google's fault but nobody is admitting anything.

Hit *#0*# , then select sensor, little black compus will have red line in middle on bottom left of screen. Shake phone vigorously, line will turn green..... This will fix that issue;however, if you reboot phone, you will have to do this again.
Hope this helps someone.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

wilowolf666 said:
Hit *#0*# , then select sensor, little black compus will have red line in middle on bottom left of screen. Shake phone vigorously, line will turn green..... This will fix that issue;however, if you reboot phone, you will have to do this again.
Hope this helps someone.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Any solution that needs to be applied again after a reboot is not a solution at all (nothing against you, just frustrated at no solution).
I have the same issue as the OP, and GPS status app fixed it, but I lose the fix after a reboot. This is unacceptable and I don't think it's just a few of us experiencing this issue.
Could more people post and say whether they have this issue and if not, how they fixed it?

wilowolf666 said:
Hit *#0*# , then select sensor, little black compus will have red line in middle on bottom left of screen. Shake phone vigorously, line will turn green..... This will fix that issue;however, if you reboot phone, you will have to do this again.
Hope this helps someone.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The issue seems to be resolved by this. I only have to rotate the phone horizontally a couple of times after a reboot and pointers works just fine.

Compass defect or poor calibration fixed by calibration?

For some reason my compass seems to be poorly calibrated and when I use Google Maps the navigation works, but I sometime lose direction. In order to fix I need to rotate my phone in all different ways. But after a reboot the compass goes back to being off. Does anyone else have this issue? Is this a defect or software?

I found exactly the same issue yesterday trying to navigate around London. Google maps has been dodgy lately on my note 3, xperia z and my girlfriends HTC one s so I put it down to a bug, I might try another navigation app to see if it's the phone

BrandonPrice31 said:
For some reason my compass seems to be poorly calibrated and when I use Google Maps the navigation works, but I sometime lose direction. In order to fix I need to rotate my phone in all different ways. But after a reboot the compass goes back to being off. Does anyone else have this issue? Is this a defect or software?
Click to expand...
Click to collapse
Are you using a case? Particularly one with metal in it such as an s-view case. If so, you have to recalibrate the compass after every reboot.

jonstatt said:
Are you using a case? Particularly one with metal in it such as an s-view case. If so, you have to recalibrate the compass after every reboot.
Click to expand...
Click to collapse
this is not dependant on cases etc., same here as on note3, ... : with each reboot the calibration resets. maybe this is how samsung wants it to be!

jonstatt said:
Are you using a case? Particularly one with metal in it such as an s-view case. If so, you have to recalibrate the compass after every reboot.
Click to expand...
Click to collapse
I'm using the s view case hmmm

TML1504 said:
this is not dependant on cases etc., same here as on note3, ... : with each reboot the calibration resets. maybe this is how samsung wants it to be!
Click to expand...
Click to collapse
Do you have same issue?

This has been an ongoing issue with Samsung Phones. This is my 3rd and and none of them have worked correctly in Maps, without navigating.
When you are just driving around (not navigating) you are using the compass....
When you are navigating, Maps is using the GPS and comparing your last point to your current point to determine your direction of travel. This causes navigating to work right and non-navigating to be wrong.
I have not found a consistent solution. Also on Google Skymap, with the AR type view, it is nearly useless for this same reason. It can't seem to sense your proper orientation due to the compass issue. (though I admit to not trying skymap on the Note 4)
Its not so much a bug, as it is Samsung and Google doing things differently.

boufa said:
This has been an ongoing issue with Samsung Phones. This is my 3rd and and none of them have worked correctly in Maps, without navigating.
When you are just driving around (not navigating) you are using the compass....
When you are navigating, Maps is using the GPS and comparing your last point to your current point to determine your direction of travel. This causes navigating to work right and non-navigating to be wrong.
I have not found a consistent solution. Also on Google Skymap, with the AR type view, it is nearly useless for this same reason. It can't seem to sense your proper orientation due to the compass issue. (though I admit to not trying skymap on the Note 4)
Its not so much a bug, as it is Samsung and Google doing things differently.
Click to expand...
Click to collapse
So you have this issue with the Note 4 when using Google Maps while driving? Moving my note in all directions calibrated it but then reboot forgets.

BrandonPrice31 said:
So you have this issue with the Note 4 when using Google Maps while driving? Moving my note in all directions calibrated it but then reboot forgets.
Click to expand...
Click to collapse
I dont mess with the recalibration process. Its annoying and i hate it, but its not so bad that i recalibrate. I also dont reboot very often, but in the past, the recalibration doesnt stick for long even when not rebooting.
I love google maps for navigating, but it sucks for driving around. The biggest issue is that the screen turns off on its own when not navigating. Waze is great for driving around, it doesnt shut off the screen, and gives you all the traffic info you need. It also routes the voice through the phone regardless of if you are connected to the car by bluetooth. The biggest complaint with waze is that it isnt multi window compatible. On my rooted note 2 i used waze on the left of the screen for traffic issues, and maps on the right side of the screen for navigation.

Compass issues

I picked up the nexus 6 from AT&T a couple days ago and love it but I have one issue. The compass is off by 90 to 180 degrees. If I spin it around enough it usually calibrated itself but only lasts until the next time I start maps.
I've seen a couple of comments indicating similar issues but I'm not sure if it is a hardware issue and should be replaced.
Does the compass work correctly for everyone else?
Sent from my Nexus 6 using Tapatalk

Same issue here
I have the same issue with my Nexus 6 64Gb blue, bought in Germany from Amazon.de.
Calibration helps but it decalibrates soon, and then the compass is off by 90° or 180°.

DontHaveACLue said:
I picked up the nexus 6 from AT&T a couple days ago and love it but I have one issue. The compass is off by 90 to 180 degrees. If I spin it around enough it usually calibrated itself but only lasts until the next time I start maps.
I've seen a couple of comments indicating similar issues but I'm not sure if it is a hardware issue and should be replaced.
Does the compass work correctly for everyone else?
Click to expand...
Click to collapse
That would NOT be a hardware issue. That is entirely software.

doitright said:
That would NOT be a hardware issue. That is entirely software.
Click to expand...
Click to collapse
Why are you so sure it's a software issue if the sensor loses calibration no matter what?

max.shirshin said:
Why are you so sure it's a software issue if the sensor loses calibration no matter what?
Click to expand...
Click to collapse
heres one way to calibrate a compass in android.. https://www.youtube.com/watch?v=AzQSsUsOWJc

simms22 said:
heres one way to calibrate a compass in android..
Click to expand...
Click to collapse
Exactly, except that in case of Nexus 6 the calibration only helps for about half an hour. It corrects the compass sensor and it starts behaving as it should, only to start showing random direction when you open Google Maps the next time. I've been testing it for several days, both inside and outside, in different places, running calibration several times a day. In no less than a couple of hours (usually even faster) it goes nuts again.
If you own a Nexus 6 as well, and do NOT have this issue, please let us know where you bought the device and which exact model it was (white or blue? memory size?)
Thank you very much in advance!

ingdir said:
Exactly, except that in case of Nexus 6 the calibration only helps for about half an hour. It corrects the compass sensor and it starts behaving as it should, only to start showing random direction when you open Google Maps the next time. I've been testing it for several days, both inside and outside, in different places, running calibration several times a day. In no less than a couple of hours (usually even faster) it goes nuts again.
If you own a Nexus 6 as well, and do NOT have this issue, please let us know where you bought the device and which exact model it was (white or blue? memory size?)
Thank you very much in advance!
Click to expand...
Click to collapse
bought mine through tmobile. black(blue) 32gb version

max.shirshin said:
Why are you so sure it's a software issue if the sensor loses calibration no matter what?
Click to expand...
Click to collapse
Calibration *IS* a software function. You feed corrections into the compass driver to compensate for the magnetic fields generated by the phone itself. If it is losing calibration, it CAN ONLY be a software issue. The data generated by the compass HARDWARE is not affected by calibration. The calibration adjustments are applied to values after they have been received from the hardware by the driver, and before being passed on to userland.
---------- Post added at 08:02 PM ---------- Previous post was at 07:50 PM ----------
ingdir said:
Exactly, except that in case of Nexus 6 the calibration only helps for about half an hour. It corrects the compass sensor and it starts behaving as it should, only to start showing random direction when you open Google Maps the next time. I've been testing it for several days, both inside and outside, in different places, running calibration several times a day. In no less than a couple of hours (usually even faster) it goes nuts again.
Click to expand...
Click to collapse
Are you totally certain that this is a function of losing calibration and not of needing a NEW calibration? The problem is that a compass reads magnetic fields. Nearly EVERYTHING generates magnetic fields, ABSOLUTELY EVERYTHING that uses electricity will generate magnetic fields. Everything with IRON in it will generate magnetic fields, typically in line with earth's magnetic field so it won't interfere (much), but if that thing with iron in it is MOVED, it will DEFINITELY interfere for quite a long time until it resets.
What the calibration does, is it tries to sort out all the competing magnetic fields in order to lock in to the true earth magnetic field. If you keep switching the compass on at different locations, then absolutely YES, it will spit out various incorrect values. In fact, if you go get yourself a regular old fashioned magnetic compass (with a needle on a pin in an oil bath) and you move it around, it WILL react to all the different things that produce a magnetic field.
Maybe try going into a forest, calibrating it, sitting around for a few hours (maybe a camp fire?), and then checking if it keeps its calibration.

doitright said:
Calibration *IS* a software function. You feed corrections into the compass driver to compensate for the magnetic fields generated by the phone itself. If it is losing calibration, it CAN ONLY be a software issue.
Are you totally certain that this is a function of losing calibration and not of needing a NEW calibration?
Click to expand...
Click to collapse
No, I'm not. Well, here are some possibilities to consider:
1. External magnetic fields affecting the phone in a way the compass goes nuts.
Before Nexus 6, I had Nexus 5 for 1 year and its compass worked perfectly in the same locations where Nexus 6 compass fails: same apartment, same office, same places around the city. Moreover, I don't even remember calibrating my Nexus 5, the compass just worked. Now I have Moto G as a temporary phone as I've sent my N6 back to Amazon, and Moto G compass works excellently as well -- again, no calibration required. So we have at least two devices with compasses working fine in the same environment.
2. Software bug that causes calibration data to be dropped.
I had the compass problem both on stock Lollipop and on CM. I also have a friend who did NOT have any compass issues while running exactly the same setup (first stock, then the same builds of CM) on the same Nexus 6 model. In Android, apps typically can't work with drivers on such a low level that could affect the calibration, and I don't run any special apps (except Google Maps) that do something with the compass. So it CAN be a software bug, but then it has to be very picky. Running a phone on pure CM without Google Maps for several days could be a good test as Maps is the only app that had something to do with a compass on my phone.
3. Some magnetic interference inside the device itself, or the sensor being too sensitive and/or having a hardware problem of its own.
This one seems the most likely to me, as it fits a pattern: the problem happens consistently on one device while never happening on other devices with identical configuration, several users have this problem (there are threads on reddit and other places, too) while the majority seems to be unaffected, and other devices with a compass work just fine in same locations.
Anyway, there obviously ARE devices around which can have a compass working just fine, and be it either a software or a hardware issue with Nexus 6, it's good if more people report a similar issue (or a lack thereof).

I have the same issue. I have calibrated from home and on the road in several states. I does not hold calibration.
I'm road warrior, and this is a real problem when traveling.
Sent from my Nexus 6 using XDA Free mobile app