Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GPS doesn't get a fix #103

Open
cmorlok opened this issue Jun 28, 2016 · 10 comments
Open

GPS doesn't get a fix #103

cmorlok opened this issue Jun 28, 2016 · 10 comments
Labels

Comments

@cmorlok
Copy link
Member

cmorlok commented Jun 28, 2016

GPS sometimes doesn't get a fix even when more than 10 satellites are in use. The issue has been introduced with the new M blobs.

@jaimemrjm
Copy link

I can confirm GPS needs several minutes to get location since the latest builds.

@cmorlok
Copy link
Member Author

cmorlok commented Jun 30, 2016 via email

@jaimemrjm
Copy link

Please, find attached the gps.log.zip from logcat. I have used Sat sat to check GPS status. I needs almost 3 minutes to get fix location. Note there's a SIGSEGV.

@cmorlok
Copy link
Member Author

cmorlok commented Jul 7, 2016

The tombstones (/data/tombstones/tombstone*) would be useful, if they still exist.

@jaimemrjm
Copy link

I cannot provide the files, because I have this ROM no more.

@DerSaxxe
Copy link

DerSaxxe commented Jul 9, 2016

Same here with the latest build
tmp_7715-logfiles-2065457878.zip
tmp_7715-tombstones1737011934.zip

@Kra1o5
Copy link
Member

Kra1o5 commented Jul 9, 2016

I will try to fix it for next release (weekend build).

@1tft
Copy link

1tft commented Aug 14, 2016

I can confirm GPS needs several minutes to get location tested with latest build:
Version: RC [2016/07/31]
Firmwarebase: 4.1.0 (Android 6.0.1)
Installation/Upgrade: no upgrade, full clean installation with a factory reset prior installation

On second phone I get fix within seconds.
Reference build on second phone: 2016/05/18
Firmwarebase: 3.2.9 (Android 5.1.1)

@jaimemrjm
Copy link

The issue is fixed. Tested with the latest build from 2016 december.

@cmorlok
Copy link
Member Author

cmorlok commented Jan 5, 2017

No, it's not fixed. I just happens only when under certain conditions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants