Google Maps Compass issue... - G1 General

I've been telling myself for weeks that I'm not going to worry about it.
In Google Maps when I use the compass mode on Street View it responds... but very strangely. It's difficult to explain but I have to spin in circles slowly just to almost all the way around 360 degrees just to do a 180 on Maps. Obviously the trackball works on it just fine so I'm not really worried about it and it's not worth wiping and starting from scratch. So like I said... I didn't worry about it.
Since then I've tried Haykuro 5.0.1G and everything worked great. Too great in fact. The Google Maps Compass mode works perfectly. I flash back to RC33 and I have the same problems so it doesn't appear to be a hardware issue.
I'm not near metal, I've recalibrated the compass by the "Figure 8" method, all other apps (Brain Genious, Bubble, Planetarium, Sky Map) seem to work alright.
I have all caches to SD, apps to SD, auto-rotate disabled, transitions and such disabled.
And the weird thing is that I was able to go straight from RC33 to 5.0.1G without loosing any apps. I just needed to use Mybackup to restore my data (texts, phone log, etc) so I doubt that it's a problem with an existing app.
I'm thinking it might be my class 4 card with my Maps cache to SD. Maybe I'll try moving it back to see if the problem clears up. Any input anyone?

Related

GPS Inaccuracy while in car?

Strange error I haven't noticed until a few weeks ago.
I've tested in both Damage Control v1, v2.05, and Fresh 2.0d (current ROM i'm running)
With google maps/nav it always places me about 50 feet+ to one side of the street. It moves with the vehicle just fine, but always puts me on a side street, so if I'm traveling down a 2 lane highway it's constantly saying "turn right onto hwy xxx"
My GPS is always DEAD ON accurate though. I mean even inside my house if I'm at the front of the house it puts that dot within 5 feet, if I goto the back of the house (bedroom) it puts me RIGHT OVER that spot. The movement however is not so great. My phone while in the GPS mount has a clear view of the sky through the windshield.
Am I the only one experiencing this?
Google NAV is basically useless, because of the annoying constant re-routing.
I had this on Thursday when I was traveling for the holiday. I was using DC2.0r2 at the time however. I didn't have the same experience with my last install of DC2.05. I will repost after my trip today. Might be some time.
Bump...
10char
Same here.gps problem with 2.1?
Yes I have this problem. It's been mentioned in the main damageless thread and the bug thread so I think people are aware of it.
I was having the same issue with the dcr2 but it went away when I wiped and went over to freshes. Might be cuz It's based off the latest Sprint leak?
Works very well for me on dcv2. I think it's almost as good as co-pilot with the directions. It's so easy to start by going "navigate to 123 fake st". I usually had to restart my phone every time I wanted to use co-pilot otherwise it couldn't find a gps signal.
Also seeing this issue.
When I fired up navigator it started telling me to make the first turn (down the street) before I even got in my car -- so I had to use maps instead. Using maps, my marker was always a bit off. For example, it was showing me consistently North of the road (not on any road) when I was traveling West. Not sure exactly when this started, but I am currently running Fresh 2.0d, just for the record.
EDIT: Also, just FYI, this is with a good and proper GPS lock. It does follow my every move and turn, and is entirely responsive, but it seems as though my location is consistently mis-calibrated somehow, and always by the same amount/direction.
Anyone tried pushing one of the 1.5 gps.conf files to a 2.1 rom and seeing if it makes a difference?? I remember that was a fix in the early 2.1 roms from flipz that came out. Try it and see.
All seemed to be working OK today for me. This is like my third/fourth flash of a 2.1 ROM that seemed to have done it for me. No more flashing for a little while. Not that it is a fix at all, but I've had it both not work and work after switching out a few different ROMs.
I was going to make a thread on this. It was off for most of my trip. I muted the audio and just watched for my exit. After awhile it moved me on top of the road and it was ok, but it did it again a few other places.
It was a really odd bug. DC2.05
It worked for me in D1. But it's off in D2. GPS seems to be fairly accurate when just finding my location in maps. It's when I start to nav that it goes off.
It actually started doing that thing today where it can't find a GPS signal until it's restarted again, so I guess it's not unique to the ROM or nav software. My phone just seems to be bad with GPS if it's been a while without a fresh restart.
Has anyone tried using the Sprint Navigation on this or is it just Google's beta Navigation application? For me I never did actually try the Sprint nav, just stuck in the Google one. I knew where I was going the whole time, so instead of trying things I just shut it off.

Google maps update fixes compass and GPS issues

Hey so I just installed the update for google maps and now the GPS and compass finally seem to be working properly. Anyone else seeing this?
Sent from my SGH-T959 using XDA App
Yes and no. The pointer turns a little smoother in maps but if you go to street view and activate compass mode you will see that the XY axis lags terribly. The vertical axis is fine and very responsive but horizontal is slow like molasses. Compass is IMO still broke.
I installed it, and things seem to be somewhat improved. However, I still consider them to be broken.
Hopefully, this isn't the 'fix' Samsung and T-Mobile was talking about. Spotted nine satellites again, but can only lock onto a single one. The cycle continues.
The Compass is still slow to update and not at all 1:1 with my movement. GPS reception is still poor, and Google Maps still can't decide if I'm in Seattle or Issaquah (hint: I'm not in Issaquah).
Slight improvements, but not fixed.
Thanks for the heads up, though. Anybody else tried it?
I'm pretty sure you're imagining things. The compass problem is strictly a hardware/firmware issue. Simply updating a single app like GMaps isn't going to fix it. But don't take my word for it.
To see the raw sensor data, go to the dialer, and type in *#*#1472365#*#* then press Test Application, then Show Sensor Data. Look at the compass and tell me it's functioning correctly.
My GPS connects faster than heck, but being 30meters off really sucks. I mean my G1 would be 3-9meters off not 30
My vibrant isn't even connecting to a satellite tonight. This ain't no G1.

Google Maps 5 GFX bug

Uninstalled Google Maps 5 after going on a road trip to SF and putting the app through heavy use. On more than one occasion it displayed black graphics when switching back and forth between Spotify, Messaging, and Navigation, meaning it was impossible to navigate unless switching to turn-by-turn text navi.
After several reboots and lots of bad timing I just uninstalled it and am now running 4.X fine and stable.
Anyone else experienced this? It will ONLY show if you are a heavy maps user who multi-task, otherwise you probably haven't ran into it (yet).

New Google Maps has issues

I'm not sure how much of this, is the phone or the ROM or google maps. I'm using MOAR ROM.
Any way first issue:
1) If you are Navigating and receive a call after a few minutes it will squawk that it can't find your location !!! This never happened with old google maps (prior to V7) on my HTC M7. Nor this phone with old google maps. Why would the GPS stop locating you while on a call. I thought it might be this phone, in how it works. But my wife just got the message on her M7 today. I know all about assisted GPS. That is for getting initial lock. Once locked it should be just GPS tracking.
2) It's been hoping location like crazy. The route will take you say on a exit ramp but the Software assumes you didn't take the ramp. Reroutes, then reroutes back when sees it's way off. It's been really bad lately that I almost don't want to use it. I swear it's Google MAPs though. Your location isn't always accurate enough to know what lane your in and it should assume you are on the route. I've seen it jump to parallel side roads while Navigating on the highway. It shouldn't do that and your location isn't always accurate enough for it to differentiate that and should assume you are on the route it gave you.
By the way I have been running the old version for quite some time. But past few months it's been having different issues, like search not working well because I think it was getting too old to work anymore. My wifes M7 was having the same issues. I actually like the new version now, when it works. I finally talked her into switch and she saw issue #1 today. Don't know yet if she has 2nd issue or not yet.
Anyone else have these issues.
I wasn't sure if there are some hidden setting or specific ways I should set my location settings.
I had "High Accuracy" on and I just switched it to "GPS Only" and see if that helps.
I have been experiencing #2 since the last few app updates on both my GS5 and my GS3. So I've been pretty convinced its not device dependent.
I see this #2 on my S5 and my S3. It also makes Waze not find my location until the Google Maps force closes itself. Then it all works. Prior to the force closing, an app like GPS lock will show that it has a very good GPS lock despite what Google Maps thinks. It's google maps and just keep reporting feedback through the google maps app.
Are you ABSOLUTELY sure you did a full clean wipe before flashing? I once dirty flashed on v1.1 and that is the exact problem I had.
I mean....no offense, bro. Even if you did a full wipe before, do a full wipe again. Always TiBu your apps, it'll take less time to set back up.
Version 2.1 does seem the best yet. Also remember to set up everything BEFORE enabling Xposed Installer. Less chance of any FC's.

GPS Can't Lock In My Car (unless Maps is minimized?)

GPS won't lock on my phone unless it is out the window or in the corner of my dashboard and windshield, underneath the wipers. I opened it up and the pins are connected. Curiously, i found that when i minimized my google maps screen to go onto Dolphin Browser to search this problem, my GPS locked on. Then i would go back to Google Maps and the signal would shortly be lost until i brought up dolphin. This could be coincidence, i am unsure. If it is, then it is a big coincidence.
Also, curiously, i came back from a cross-country trip via greyhound and used my GPS frequently while on the bus and had very little issue. Considering i was in completely new place, sometimes mountains, i t would say my GPS worked rather well.
However, the GPS not working in my car has always been an issue. Perhaps my car is coated with some weird conspiracy theorist anti-GPS material, but i doubt that as well.
This is a rooted Galaxy Note 3 running ARYAMOD Rom. I used to use Omega Rom and had similar GPS complaints.
Honestly, the part about my car being coated in mystery anti-GPS material seems to be the only good explanation right now.
EDIT: I seem to have fixed it (hopefully not temporary):
Just in case, i unsnapped the pins and put them back in. i also got that GPS Status Test & Fix - No Ads app that people have suggested. I used that, but then GPS/location wouldn't work in google maps, only when i had that app running so i reset GPS within the app and still nothing. So then i restarted my phone. When i restarted it said that in a previous version of Android, i had it set so that apps couldn't access my GPS (or something like that; i am paraphrasing). It asked if i wanted to re-enable it and i did and now it is working perfectly.
It may be something to do with updating ROMS

Categories

Resources