Status Update
Comments
pa...@google.com <pa...@google.com> #2
Branch: main
commit 6dc78fbbbbadac9c2dc2065150a7af2422c6115c
Author: Rupert Ben Wiser <bewise@chromium.org>
Date: Thu Sep 12 16:16:14 2024
webview: Add support configuration for CHIPS
Adding a boundary interface to let Android developers configure
if partitioned cookies should be enabled or not.
go/chips-android-apis-webview
Bug: 364904765
Change-Id: I683ab5ec157a11aa081db5763380e692ab02c5e6
Reviewed-on:
Reviewed-by: Peter Pakkenberg <pbirk@chromium.org>
Auto-Submit: Rupert Wiser <bewise@chromium.org>
Commit-Queue: Peter Pakkenberg <pbirk@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1354607}
M android_webview/expectations/system_webview_32_64_bundle.AndroidManifest.expected
M android_webview/expectations/system_webview_32_bundle.AndroidManifest.expected
M android_webview/expectations/system_webview_64_bundle.AndroidManifest.expected
M android_webview/expectations/system_webview_bundle.AndroidManifest.expected
M android_webview/expectations/trichrome_webview_32_64_bundle.AndroidManifest.expected
M android_webview/expectations/trichrome_webview_32_bundle.AndroidManifest.expected
M android_webview/expectations/trichrome_webview_64_32_bundle.AndroidManifest.expected
M android_webview/expectations/trichrome_webview_64_bundle.AndroidManifest.expected
M android_webview/expectations/trichrome_webview_bundle.AndroidManifest.expected
M android_webview/glue/java/src/com/android/webview/chromium/AndroidXProcessGlobalConfig.java
M android_webview/glue/java/src/com/android/webview/chromium/WebViewChromiumFactoryProvider.java
M android_webview/nonembedded/java/AndroidManifest.xml
M android_webview/support_library/boundary_interfaces/src/org/chromium/support_lib_boundary/ProcessGlobalConfigConstants.java
M chrome/android/expectations/monochrome_32_64_public_bundle__base.AndroidManifest.expected
M chrome/android/expectations/monochrome_32_public_bundle__base.AndroidManifest.expected
M chrome/android/expectations/monochrome_64_32_public_bundle__base.AndroidManifest.expected
M chrome/android/expectations/monochrome_64_public_bundle__base.AndroidManifest.expected
M chrome/android/expectations/monochrome_public_bundle__base.AndroidManifest.expected
re...@gmail.com <re...@gmail.com> #3
There is already test coverage of CHIPS behavior inside of Chromium in
Due to limitations of AndroidX test infra, manual test instructions are necessary to exercise the toggling of the enable partitioned cookies API. WebView toggles CHIPS behavior with the disable-partitioned-cookies
command line switch.
To demonstrate the API's correctness in toggling this, log statements were inspected when this flag was toggled during WebView startup.
See the diff below for details:
diff --git a/android_webview/glue/java/src/com/android/webview/chromium/WebViewChromiumFactoryProvider.java b/android_webview/glue/java/src/com/android/webview/chromium/WebViewChromiumFactoryProvider.java
index 63c5f5a5b2795..ee589176bdab2 100644
--- a/android_webview/glue/java/src/com/android/webview/chromium/WebViewChromiumFactoryProvider.java
+++ b/android_webview/glue/java/src/com/android/webview/chromium/WebViewChromiumFactoryProvider.java
@@ -490,6 +490,9 @@ public class WebViewChromiumFactoryProvider implements WebViewFactoryProvider {
if (!androidXConfig.getPartitionedCookiesEnabled()) {
cl.appendSwitch("disable-partitioned-cookies");
+ Log.e(TAG, "Partitioned cookies disabled");
+ } else {
+ Log.e(TAG, "Partitioned cookies enabled");
}
// Now safe to use WebView data directory.
pa...@google.com <pa...@google.com> #4
Note: Will add testing when more of the API has been implemented.
re...@gmail.com <re...@gmail.com> #5
Project: platform/frameworks/support
Branch: androidx-main
Author: Adam Walls <
Link:
[WebView] Add API to configure CHIPS
Expand for full commit details
[WebView] Add API to configure CHIPS
This adds an API to allow Android developers to configure CHIPS globally. This is done with ProcessGlobalConfig. In order to prevent this from being published/used prior to Android B's release, RestrictTo annotation is used.
Design: go/chips-android-apis-webview
Test: Will add testing in a follow-up CL.
Bug: 364904765
Change-Id: If6d630562be7209eb2ab00da2dbad9398ba0553e
Files:
- M
webkit/webkit/src/main/java/androidx/webkit/ProcessGlobalConfig.java
- M
webkit/webkit/src/main/java/androidx/webkit/WebViewFeature.java
- M
webkit/webkit/src/main/java/androidx/webkit/internal/StartupFeatures.java
- M
webkit/webkit/src/main/java/androidx/webkit/internal/WebViewFeatureInternal.java
Hash: 4fe72afdcf64cad8b2399ca7a28d1aa57a05f976
Date: Thu Oct 24 17:35:26 2024
pa...@google.com <pa...@google.com> #6
Project: platform/frameworks/support
Branch: androidx-main
Author: Adam Walls <
Link:
Refactor common Webkit test classes into test.common module.
Expand for full commit details
Refactor common Webkit test classes into test.common module.
This is intended to enable new androidx.webkit test targets so that we
do not need to use the Orchestrator annotation to create new test
processes. This is intended as a refactor to reduce the CL size in
aosp/3371538.
The new androidx.webkit.test.common module was created using
the development/project-creator/create_project.py script.
Test: ./webkit/run_instrumentation_tests.sh
Bug: 364904765
Change-Id: If68173a88bd5267d3aa19986ba3f4486d9e17b64
Files:
- M
settings.gradle
- A
webkit/integration-tests/common/build.gradle
- M
webkit/integration-tests/common/src/main/java/androidx/webkit/test/common/PollingCheck.java
- A
webkit/integration-tests/common/src/main/java/androidx/webkit/test/common/TestWebMessageListener.java
- M
webkit/integration-tests/common/src/main/java/androidx/webkit/test/common/WebViewOnUiThread.java
- M
webkit/integration-tests/common/src/main/java/androidx/webkit/test/common/WebkitUtils.java
- M
webkit/integration-tests/instrumentation/build.gradle
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/AsyncStartUpTest.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/CookieManagerCompatTest.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/MultiProfileTest.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/PostMessageTest.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/ProxyControllerTest.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/ServiceWorkerClientCompatTest.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/ServiceWorkerWebSettingsCompatTest.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/TracingControllerTest.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/WebSettingsCompatDarkModeTestBase.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/WebSettingsCompatTest.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/WebSettingsCompatUserAgentMetadataTest.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/WebStorageTest.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/WebViewClientCompatTest.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/WebViewCompatTest.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/WebViewDocumentStartJavaScriptTest.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/WebViewRenderProcessClientTest.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/WebViewRenderProcessTest.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/WebViewWebMessageCompatTest.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/WebViewWebMessageListenerTest.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/internal/AssetHelperTest.java
- M
webkit/integration-tests/instrumentation/src/androidTestTargetSdk32/java/androidx/webkit/WebSettingsCompatForceDarkTest.java
- M
webkit/integration-tests/instrumentation/src/androidTestTargetSdkLatest/java/androidx/webkit/WebSettingsCompatDarkThemeTest.java
- M
webkit/integration-tests/instrumentation/src/androidTestTargetSdkLatest/java/androidx/webkit/WebSettingsCompatLightThemeTest.java
Hash: 463387393fce755928325a57d49cec218631a6a3
Date: Fri Dec 13 23:24:49 2024
ar...@gmail.com <ar...@gmail.com> #7
Project: platform/frameworks/support
Branch: androidx-main
Author: Adam Walls <
Link:
[WebView] Add CHIPS testing via integration tests.
Expand for full commit details
[WebView] Add CHIPS testing via integration tests.
In order to test the enable partitioned cookies API added in
aosp/3318854, integration tests are added.
Note: Since test process restarts are not supported, and the startup
APIs can only be called once per process lifetime, this will avoid
errors by only testing with a single test case that covers a few
use cases.
Test: ./webkit/run_instrumentation_tests.sh
Bug: 364904765
Change-Id: I89354cb04bb92b954a5a51fac06133ebd6a3ae3a
Files:
- M
settings.gradle
- A
webkit/chips-enabled-integration-tests/instrumentation/build.gradle
- A
webkit/chips-enabled-integration-tests/instrumentation/src/androidTest/AndroidManifest.xml
- A
webkit/chips-enabled-integration-tests/instrumentation/src/androidTest/java/androidx/webkit/EnablePartitionedCookiesTest.java
- M
webkit/integration-tests/common/src/main/java/androidx/webkit/test/common/WebViewOnUiThread.java
- M
webkit/run_instrumentation_tests.sh
Hash: 200afa93c09543d6c7320a025fed7f2944689055
Date: Thu Dec 12 03:20:20 2024
pa...@google.com <pa...@google.com> #8
Project: platform/frameworks/support
Branch: androidx-main
Author: Adam Walls <
Link:
[WebView] Expose Enable CHIPS API
Expand for full commit details
[WebView] Expose Enable CHIPS API
aosp/3318854 introduced the enable CHIPS API hidden until it was
deemed ready for release. This exposes the API for use in apps.
Relnote: "Add setPartitionedCookiesEnabled API. This will allow
developers to enable and disable partitioned cookies in WebView. The
feature is available in WebView starting in M130."
Bug: 364904765
Test: ./webkit/run_instrumentation_tests.sh
Change-Id: Ic506a23471946d31b797397e2f71aef0f3ae481a
Files:
- M
webkit/webkit/api/current.txt
- M
webkit/webkit/api/restricted_current.txt
- M
webkit/webkit/src/main/java/androidx/webkit/ProcessGlobalConfig.java
- M
webkit/webkit/src/main/java/androidx/webkit/WebViewFeature.java
- M
webkit/webkit/src/main/java/androidx/webkit/internal/StartupFeatures.java
Hash: 512bc1b685e6c5bbb563c33948b1c3b6b0ec9197
Date: Fri Dec 20 18:03:50 2024
re...@gmail.com <re...@gmail.com> #9
Project: platform/frameworks/support
Branch: androidx-main
Author: Adam Walls <
Link:
Reformat affected classes from aosp/3406800.
Expand for full commit details
Reformat affected classes from aosp/3406800.
aosp/3406800 refactored some common classes that were not formatted
properly.
Bug: 364904765
Test: ./webkit/run_instrumentation_tests.sh
Change-Id: I328af103b753e575c25a383dd709e355a973b98f
Files:
- M
webkit/integration-tests/common/src/main/java/androidx/webkit/test/common/PollingCheck.java
- M
webkit/integration-tests/common/src/main/java/androidx/webkit/test/common/TestWebMessageListener.java
- M
webkit/integration-tests/common/src/main/java/androidx/webkit/test/common/WebViewOnUiThread.java
- M
webkit/integration-tests/common/src/main/java/androidx/webkit/test/common/WebkitUtils.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/AsyncStartUpTest.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/MultiProfileTest.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/PostMessageTest.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/ProxyControllerTest.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/ServiceWorkerClientCompatTest.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/ServiceWorkerWebSettingsCompatTest.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/TracingControllerTest.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/WebSettingsCompatDarkModeTestBase.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/WebSettingsCompatTest.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/WebSettingsCompatUserAgentMetadataTest.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/WebStorageTest.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/WebViewClientCompatTest.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/WebViewCompatTest.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/WebViewDocumentStartJavaScriptTest.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/WebViewRenderProcessClientTest.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/WebViewRenderProcessTest.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/WebViewWebMessageCompatTest.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/WebViewWebMessageListenerTest.java
- M
webkit/integration-tests/instrumentation/src/androidTest/java/androidx/webkit/internal/AssetHelperTest.java
Hash: 818530aa0c71b1b6e1cba00a39494794b45ed6c8
Date: Wed Dec 18 00:18:27 2024
ar...@gmail.com <ar...@gmail.com> #10
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.webkit:webkit:1.13.0-alpha03
ka...@gmail.com <ka...@gmail.com> #11
Project: chromium/src
Branch: main
Author: Adam Walls <
Link:
[WV] Fix adding switch to stale command line reference.
Expand for full commit details
[WV] Fix adding switch to stale command line reference.
Currently, the disable-partitioned-cookies, aka
kDisablePartitionedCookiesSwitch, is used to control CHIPS in WebView.
However, it is currently broken because it uses a stale reference to the
command line object. This is because it is called after the point in
WebView's startup where the native library is loaded and passes off its
command line switches in Java to the native equivalent. This causes
changes that make the old reference stale. It results in an incongruence
between Java and native command line switches, causing undefined and
unintended behavior with CHIPS in WebView.
This fixes this by using the getInstance method to get a fresh reference
to a valid instance of the command line. Another change limits the scope
of the object that caused the issue by adding a block around the code
that references it. Note: The default behavior will be set to on for
now, postponing the decision to change it at a later point.
testing for the glue layer later.
Low-Coverage-Reason: HARD_TO_TEST Though we are looking into adding
Bug: 364904765, 389121692
Test: See bug 389121692 for test instructions.
Change-Id: Icd9a04bbdc3a82197bf27bec428e60f05cd62243
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6171228
Auto-Submit: Adam Walls <avvall@chromium.org>
Reviewed-by: Richard (Torne) Coles <torne@chromium.org>
Commit-Queue: Adam Walls <avvall@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1413072}
Files:
- M
android_webview/glue/java/src/com/android/webview/chromium/WebViewChromiumFactoryProvider.java
Hash: fda51784ebf6743fdd47c1e6fc441fdb05d13945
Date: Wed Jan 29 11:42:08 2025
ar...@gmail.com <ar...@gmail.com> #12
ar...@gmail.com <ar...@gmail.com> #13
ig...@gmail.com <ig...@gmail.com> #14
ar...@gmail.com <ar...@gmail.com> #15
ca...@gmail.com <ca...@gmail.com> #16
before with 5.1.1 all was OK
WiFi and Bluetooth is active.
Thank You
ig...@gmail.com <ig...@gmail.com> #17
pa...@google.com <pa...@google.com> #18
pa...@google.com <pa...@google.com> #19
[Deleted User] <[Deleted User]> #20
[Deleted User] <[Deleted User]> #21
Google Maps is very slow to lock in my actual location, showing that big blue circle covering almost the whole city.
And always when I open the Maps, it always starts at a completely wrong and random location, more than 150m from my current location. The smart lock for trusted places is not working too due that.
Looks like that Maps or location services "resets" when it's not active, and the phone doesn't "remember" the last actual location.
I don't know if this information would be useful, but this is the experience that I'm having. 5.1.1 was working fine.
re...@gmail.com <re...@gmail.com> #22
Otherwise, if it's just complains, don't be surprise if Google does nothing about this issue.
The more reports Google has, the better it is.
And the solution will come faster.
rb...@gmail.com <rb...@gmail.com> #23
ar...@gmail.com <ar...@gmail.com> #24
rb...@gmail.com <rb...@gmail.com> #25
[Deleted User] <[Deleted User]> #26
Note the big blue circle, and the random location of the blue point (my correct location was in home icon).
ar...@gmail.com <ar...@gmail.com> #27
ar...@gmail.com <ar...@gmail.com> #28
in...@gmail.com <in...@gmail.com> #29
ar...@gmail.com <ar...@gmail.com> #30
ja...@gmail.com <ja...@gmail.com> #31
ja...@gmail.com <ja...@gmail.com> #32
Nexus 5 with 6.0
ht...@gmail.com <ht...@gmail.com> #33
ht...@gmail.com <ht...@gmail.com> #34
Hope Google will give this issue HIGH priority!
Ahh yes: I have the Nexus 5 (2013) all stock , no root ,never rooted.
ji...@gmail.com <ji...@gmail.com> #35
GPS fix takes minutes under clear sky, it gets lost easily. Under car roof not usable at all. CLosing app with GPS fix and immediate opening other app that uses GPS again means minutes to get the fix.
wa...@gmail.com <wa...@gmail.com> #36
wa...@gmail.com <wa...@gmail.com> #38
co...@scarletmail.rutgers.edu <co...@scarletmail.rutgers.edu> #39
pa...@google.com <pa...@google.com> #40
Like APN , Service provider ? Device configuration ? It will definitely help to understand the issue
ja...@gmail.com <ja...@gmail.com> #41
4j...@gmail.com <4j...@gmail.com> #42
ar...@gmail.com <ar...@gmail.com> #43
bo...@gmail.com <bo...@gmail.com> #44
1. Phone turned on.
2. WiFi turned OFF. Bluetooth is OFF.
3. GPS Status & Toolbox app started.
4. I went outside with a full view of the sky (Texas).
5. It took over 60 seconds before the first sat was fixed. (1/17 displayed.) Before the 6.- OTA, this might take 15 seconds for a full location to be determined.
6. It took another three minutes for another six sat fixes (7/17).
7. At 8/18, the location was finally established by the phone.
8. First bug report snapshot taken here.
9. Watching the GPS Status, I noticed that when the number of sat. fixes drops below 7 (sometimes 6), the location GPS is location is lost by the phone.
10. Second bug report snapshot taken at the first GPS location lost message.
Send me a link to install QXDM app and I'll install and send you the logs.
ar...@gmail.com <ar...@gmail.com> #45
cm...@gmail.com <cm...@gmail.com> #46
It should not matter if it was an manual update or OTA. Check what was modified and remove it :).
First report was almost 2 months ago, can we get an ETA for fix?
si...@gmail.com <si...@gmail.com> #47
pa...@google.com <pa...@google.com> #48
ar...@gmail.com <ar...@gmail.com> #49
ef...@gmail.com <ef...@gmail.com> #50
ja...@gmail.com <ja...@gmail.com> #51
wa...@gmail.com <wa...@gmail.com> #52
va...@gmail.com <va...@gmail.com> #53
ta...@gmail.com <ta...@gmail.com> #54
The symptoms are the same as #43. I will grab and upload logcat and debug info when I have a chance.
Nexus 5 d821, manually updated the latest update by removing the -w flag during flash.
da...@gmail.com <da...@gmail.com> #55
re...@gmail.com <re...@gmail.com> #56
Just to add some news about my issue: I tried what some of you said, deactivating wifi/BT. There is no change for me when I do this. Even putting the phone on airplane mode (which leave I think the GPS chips on) doesn't change anything.
I have no means to make my GPS working at all.
Till now and since my upgrade to Marshmallow, I'm just localized through the phone waves which is quite poor as localization.
BR
re...@gmail.com <re...@gmail.com> #57
If I can convince him to report you'll have another report as base.
bo...@gmail.com <bo...@gmail.com> #58
ar...@gmail.com <ar...@gmail.com> #59
[Deleted User] <[Deleted User]> #60
The problem apparently fixed itself about 5 days ago, on wifi or mobile network. Even smart lock on trusted places was working properly.
Now it's happening again with no reason.
am...@gmail.com <am...@gmail.com> #61
It usually starts working again for a while after a reboot. But it is very annoying having to reboot my device every time I want to use location services.
ar...@gmail.com <ar...@gmail.com> #62
zi...@gmail.com <zi...@gmail.com> #63
Network is Vodafone (Germany).
It's definitely a Marshmallow issue (no problem with Lollipop 5.1.1)
Update was performed via OTA
The location search setting "WLAN search" doesn't matter.
For me it's the biggest Marshmallow issue because:
- Smart lock doesn't work properly (security issue)
- location based reminders will not work
- location history will display wrong results
- ... and so on
da...@gmail.com <da...@gmail.com> #64
da...@gmail.com <da...@gmail.com> #65
da...@gmail.com <da...@gmail.com> #66
OS 6.0
Smart lock is set on my home address. Seems to work fine when the location is set to Save Mode.
However when I leave the bulding, enter my car and want to use High Accuracy to navigate via google maps device struggle to get the location for long time, it finds the location, then loses it.
Scenario I did. I'm using gps toolbox to see whether phone got the location or not.
I left the phone by the window, connected it to laptop, issued monitor to see the logs. Here is what I've noticed
I've attached the logs from monitor tool.
When I browse the logs I can find smth like:
11-15 22:21:06.025: D/LocationFilter(6145): Location jumpped by 35.84695902947658m. Will ignore change=true
11-15 22:21:12.082: D/LocationFilter(6145): Location jumpped by 35.83592055896468m. Will ignore change=true
11-15 22:21:17.037: D/LocationFilter(6145): Location jumpped by 35.76804403542008m. Will ignore change=true
11-15 22:21:22.043: D/LocationFilter(6145): Location jumpped by 36.208432830478976m. Will ignore change=true
Debug - ok
and then somewhere after couple minutes
11-15 22:22:03.108: E/LocationReceiver(16265): Received bad location: null
11-15 22:22:03.259: D/LocationFilter(6145): Location jumpped by 36.81312042012901m. Will ignore change=true
11-15 22:22:03.286: W/GCoreUlr(6145): Received location statuses too frequently: [LocationAvailability[isLocationAvailable: false], elapsedRealtimeNs: 952469243000000], [LocationAvailability[isLocationAvailable: true], elapsedRealtimeNs: 952470306000000]
Above does not look good, an Error, Warn that I dont understand and again an Error below:
11-15 22:22:04.123: E/SQLiteDatabase(6145): Error inserting context_name=6 end_time=1447622522190 context_family=1 module_id=com.google.android.contextmanager.module.DetectedActivityProducer version=1 sync_state_mod_time_millis=1447622524122 start_time=1447622419922 sync_state=0 context_id=14d3c427-06a3-48e8-b298-58c7fe210909 time_type=3 proto_blob=[B@cb9cbb1
11-15 22:22:04.123: E/SQLiteDatabase(6145): android.database.sqlite.SQLiteConstraintException: UNIQUE constraint failed: context.context_id (code 2067)
zi...@gmail.com <zi...@gmail.com> #67
sr...@gmail.com <sr...@gmail.com> #68
wa...@gmail.com <wa...@gmail.com> #69
ar...@gmail.com <ar...@gmail.com> #70
da...@gmail.com <da...@gmail.com> #71
da...@gmail.com <da...@gmail.com> #72
ja...@gmail.com <ja...@gmail.com> #73
4j...@gmail.com <4j...@gmail.com> #74
ar...@gmail.com <ar...@gmail.com> #75
re...@gmail.com <re...@gmail.com> #76
It's been a month now and there is more and more users complaining about phones you sold us with the new version of your own OS (Android).
What's the deal now ?
Can I send you my Nexus 5 and you put it back to Lollipop ? If yes: how ?
Or can you perhaps send us a very easy and quick tuotiral explaining how to put our N5 back to Lollipop ?
Obviously, there is this only solution to make my phone works like it was before this damn upgrade.
Hoping to read your feedback soon,
Best regards,
Renaud
ws...@gmail.com <ws...@gmail.com> #77
ym...@gmail.com <ym...@gmail.com> #78
ar...@gmail.com <ar...@gmail.com> #79
me...@gmail.com <me...@gmail.com> #80
da...@gmail.com <da...@gmail.com> #81
gs...@gmail.com <gs...@gmail.com> #82
da...@gmail.com <da...@gmail.com> #83
ji...@gmail.com <ji...@gmail.com> #84
ji...@gmail.com <ji...@gmail.com> #85
(my bug report is in #34
ha...@gmail.com <ha...@gmail.com> #86
I have Android one from general Mobile.
5.1.1 version is useful for GPS but 6.0 has problem with GPS location.
by the way ı have just returned back to 5.1.1 version.
ke...@gmail.com <ke...@gmail.com> #87
da...@ratherzen.com <da...@ratherzen.com> #88
Android 6.0
Baseband: M8974A-2.0.50.2.27
Build: MRA58N
Carrier: T-Mobile USA
Bug report:
Issue:
No GPS lock at all. GPS Status shows 0 sats: just looks for GPS location for hours. Doesn't matter how long I wait. GPS worked perfectly with KitKat, issues arose with Lollipop, ZERO GPS ability with Marshmallow.
These have all been OTA updates. Factory data reset done with no improvement.
I look forward to *some* update or information, even if it's "this likely won't be fixed."
Thank you
da...@gmail.com <da...@gmail.com> #89
re...@gmail.com <re...@gmail.com> #90
ha...@gmail.com <ha...@gmail.com> #91
Android 5.1.1 built LUZ59R is stable for GPS usage.
and we are waiting for fixing on Marshmallow.
na...@gmail.com <na...@gmail.com> #92
st...@gmail.com <st...@gmail.com> #93
da...@gmail.com <da...@gmail.com> #94
Only my Nexus 5 with OS 6.0 gets crazy.
da...@gmail.com <da...@gmail.com> #95
da...@gmail.com <da...@gmail.com> #96
But it can't hurt to check and make sure your phone hasn't come partially separated. It might have been enough to disconnect the gps terminals. I wouldn't have normally thought to check this and I seldom have a reason to remove my case.
ne...@gmail.com <ne...@gmail.com> #97
WTF Google?!?! Just own up to your mistakes, and fix it. Let your loyal customers know what is going on and give us a damn timeline. Stop saying it's a Third Party Issue - because it all started after an OS update THAT YOU PROVIDED!
fe...@gmail.com <fe...@gmail.com> #98
hu...@gmail.com <hu...@gmail.com> #99
hs...@gmail.com <hs...@gmail.com> #100
GPS worked perfectly with KitKat, issues arose with Lollipop, ZERO GPS ability with Marshmallow.
Swearing ain't going to help!
KK 4.2.2 radio was the last one that worked properly for my N5!
Vote with your VALET & don't buy GOOGLE MOBILES?
Cheers
jc...@gmail.com <jc...@gmail.com> #101
jc...@gmail.com <jc...@gmail.com> #102
GPS worked flawlessly on Lollipop on this device.
Typical GPS apps used: Waze, Google Maps, GPS Status and Toolbox.
The Moto X Pure got version 6.0. Security patch level November 1, 2015. Motorola build version
Build number is MPH24.49-18
Service provider is Verizon Wireless.
I have reported to Motorola as well.
al...@gmail.com <al...@gmail.com> #103
After I updated the OS to Marshmallow, GPS signal become very discontinued.
I really hope this this issue will be solved in 6.0.1.
ma...@gmail.com <ma...@gmail.com> #104
I have had issues with 5.0 and 6.0 on my Nexus 5. I have been following the link above and saw this one as a very similar issue. Reset my phone so many times trying to get GPS to work. It is quite frustrating.
be...@gmail.com <be...@gmail.com> #105
If you have this problem, don't expect an answer soon.
jc...@gmail.com <jc...@gmail.com> #106
cr...@gmail.com <cr...@gmail.com> #107
The 4 spikes in the RUN.GPS app shows that error. The difference from GPS lost due to low signal inside buildings is that the GPS STATUS app is killed when bug occurs. When I go inside buildings and temporarily lose GPS signal, GSP STATUS app is not killed. So the connection is brutally closed when the phone wants to send some location info to Google servers and can't or some thing like that.
The GPS is killed on all the possible configuration: GSM Data on/off, High Accuracy/Device Only etc.
A similar problem is with LG G3 after Lollipop upgrade.
Google please fix this! I don't know how Lollipop and Marshmallow passed quality checks. Unfortunately thinks like this show that Android is always in beta stage, never a fully polished OS.
da...@gmail.com <da...@gmail.com> #108
ma...@gmail.com <ma...@gmail.com> #109
ky...@gmail.com <ky...@gmail.com> #110
As a test, I just downgraded to 4.4.4 (KTU84P) and my GPS is working flawlessly. Obviously a software issue. This is VERY disappointing considering I bought a Nexus device in order to have support from Google.
I've followed this identical issue for Lollipop for a while now:
Even though someone is assigned to it, nothing is happening. Have you purposely broken our phones so we'll upgrade to the 5X? This is absolutely ridiculous. We've had broken GPS for over a year now.
ha...@gmail.com <ha...@gmail.com> #111
My Android One device (Turkey) seems as working properly 6.0.1 (MMB29K).
Regards
da...@gmail.com <da...@gmail.com> #112
fl...@googlemail.com <fl...@googlemail.com> #113
For the record, I had issues only on 6.0.0, not on 5.x. The issues were that:
1) Wi-Fi-based location didn't seem to work at all, rendering location-based SmartLock dysfunctional indoors.
2) GPS-based location was imprecise about 50% of the time, with the fix jumping back and forth by distances of up to 50 metres (even when the precision of the fix was indicated to be better than that), making GPS tracking apps like Runtastic useless. Also, the phone seemed to have more trouble getting a (good) fix while in a car.
At least problem 1 is fixed now. Because problem 2 only occurred intermittently, I'll need to toy around with 6.0.1 a bit more to verify it's actually fixed.
cr...@gmail.com <cr...@gmail.com> #114
Exactly at 5 minutes GPS signal lost, like clockwork.
I put a screenshot from Run.GPS with GPS Dilution:
re...@gmail.com <re...@gmail.com> #115
re...@gmail.com <re...@gmail.com> #116
I have still the same bug with the freshly upgraded Marshmallow to 6.0.1 than I had with Marshmallow 6.0.0 on Post Luxembourg carrier.
I didn't have this issue before with version 4.4.4 and 5 of Android.
Here is the bug report:
Best regards
mp...@gmail.com <mp...@gmail.com> #117
my Nexus 5 also has problems related to GPS since the update from Android 4 to Android 5. The problems did not vanish after the update to Android 6.0.1.
The symptoms:
1) It takes a long time until a GPS position is aquired.
2) The GPS signal is regularly lost so that my coordinates jump on Google Maps.
Here is my bug report:
The bug report was produced while being outside. Even after 5 minutes no satellites could be locked.
My service provider is O2 Germany.
Best regards
wa...@gmail.com <wa...@gmail.com> #118
I rarely had issues getting a GPS fix outdoors but I've read that the Nexus 5 GPS antenna can have a loose connection inside the case and there are how-to videos to resolve it.
mp...@gmail.com <mp...@gmail.com> #119
you can ignore my post #117. It turns out that it was a hardware problem. The GPS antenna had no contact to the contacts inside the phone. I fixed it by just pressing down onto the back cover where the GPS antenna is located, then it "clicked" and the GPS started working right away.
Thanks to #118 I found video [1] which helped me to press the right spot on the back cover.
Best regards
[1]
vi...@gmail.com <vi...@gmail.com> #120
The problem has gone for me, after Android 6.0.1 update. The GPS works fine when wifi or mobile data are turned on.
But the problem persists when there's no Internet connection, only the GPS. I don't know if it is the proper behavior on this case.
ru...@gmail.com <ru...@gmail.com> #121
For almost a year without gps. Desperate as needed for work. Have to use regular maps.
Unbelievable.
fr...@gmail.com <fr...@gmail.com> #122
accuracy. the blue dot just jumps randomly across the map and in this case when I made the bug report,the map said I was in a far away middle-east country.
da...@gmail.com <da...@gmail.com> #123
cr...@gmail.com <cr...@gmail.com> #124
On Vodafore Romania i have constant GPS only with Data ON. If I switch data, every 5 minutes GPS signal drops for a few seconds.
cr...@gmail.com <cr...@gmail.com> #125
On Vodafore Romania i have constant GPS only with Data ON. If I switch data, every 5 minutes GPS signal drops for a few seconds.
re...@gmail.com <re...@gmail.com> #126
I didn't have any issue with Lollipop 5.1.1 so i tried CM12.1 based on this version...
You know what ?
It doesn't work !
I understand nothing at this point.
re...@gmail.com <re...@gmail.com> #127
I revert back to Lollipop 5.1.1... Same issue.
That means that once the phone had been upgraded to 6.0, this shit is gripped into the phone.
Is it possible to send you my phone and you take a look ?
It would be really appreciate because now I have a really big problem of trust against your softwares on your own phones.
Why would I spend hundreds of dollars on the 5X or 6P if you're not able to do something on a well known Nexus 5 ?
I'm really ready to send you my phone if you need it.
Best regards,
Renaud
to...@gmail.com <to...@gmail.com> #128
I have reverted the handset to Lollipop and the errors that are present in 6 are now present in Lollipop as though something has been changed in the firmware that is not reverted when Lollipop is loaded.
-Tobias
da...@gmail.com <da...@gmail.com> #129
ke...@gmail.com <ke...@gmail.com> #130
A week later I was for work in Congo, Africa and I was unable to get a gps fix (with working internet connection). I upgraded to 6.0.1 and test the gps again but still no fix.
When I came back home in Belgium I tried again and in less then 2 minutes I got a gps fix!!
da...@gmail.com <da...@gmail.com> #131
da...@gmail.com <da...@gmail.com> #132
"Please Provide the Bug report. We will have a look at the issue you reported.
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.
Note: Please upload the bug report to google drive and share the folder to android-bugreport@google.com. After sharing please provide the link for APK/screenshot/bug report"
ba...@gmail.com <ba...@gmail.com> #133
da...@ratherzen.com <da...@ratherzen.com> #134
I replaced my Nexus 5 that was experiencing the GPS issue noted here, with a warranty replacement. The new phone, also updated to Marshmallow, works fine.
ka...@gmail.com <ka...@gmail.com> #135
da...@ratherzen.com <da...@ratherzen.com> #136
It was shipped with lollipop, OTA update to KitKat, OTA update to Marshmallow. Installed Google apps and GPS Status. GPS locks quickly and has stayed locked for hours.
I'm happy to pull any info from the phone if it'll help.
da...@ratherzen.com <da...@ratherzen.com> #137
Sorry if that caused any confusion.
ba...@gmail.com <ba...@gmail.com> #139
My other issue is that battery life is very reduced. But, that may be another forum?
vi...@gmail.com <vi...@gmail.com> #141
ni...@gmail.com <ni...@gmail.com> #142
ni...@gmail.com <ni...@gmail.com> #143
be...@gmail.com <be...@gmail.com> #144
ni...@gmail.com <ni...@gmail.com> #145
re...@gmail.com <re...@gmail.com> #146
ya...@gmail.com <ya...@gmail.com> #147
Same GPS problem since I upgraded to marshmellow
ya...@gmail.com <ya...@gmail.com> #148
ja...@gmail.com <ja...@gmail.com> #149
ma...@gmail.com <ma...@gmail.com> #150
en...@gmail.com <en...@gmail.com> #151
It is frustrating.
re...@gmail.com <re...@gmail.com> #152
I just sent my phone via RMA.
Of course, I know that my operator will reset it first and send me back my phone.
And I will then resend it till my operator will send it to Google.
da...@gmail.com <da...@gmail.com> #153
re...@gmail.com <re...@gmail.com> #154
- Factory reset
- Installed Cyanogen
- Reinstalled back STock Android Lollipop
- Upgraded from Lollipop to Marshmallow
NONE of these actions did something for getting back my GPS.
In my opinion, Marshmallow crashed definitively the GPS chip and of course, every other action can't repair it if the chip is dead.
re...@gmail.com <re...@gmail.com> #155
da...@gmail.com <da...@gmail.com> #156
ni...@gmail.com <ni...@gmail.com> #157
ni...@gmail.com <ni...@gmail.com> #158
ni...@gmail.com <ni...@gmail.com> #160
no...@gmail.com <no...@gmail.com> #161
no...@gmail.com <no...@gmail.com> #162
wa...@gmail.com <wa...@gmail.com> #163
ma...@gmail.com <ma...@gmail.com> #164
Any ideas on a fix?
co...@microdeclic.net <co...@microdeclic.net> #165
fe...@gmail.com <fe...@gmail.com> #166
fe...@gmail.com <fe...@gmail.com> #167
I'm from Panama, my carrier is Claro. I have tried a different data provider and GPS works at least in the limited tests I did. But on a day to day basis I can't use GPS and data at the same time. I'll post a bugreport as soon as I can.
Hope it can be fixed, it's been bothering me for more than 2 years now.
li...@teklion.com <li...@teklion.com> #168
If we turn on Google Maps for instance, the speed starts getting received again. It is probably a different problem (maybe bug?) on android 6.
cj...@gmail.com <cj...@gmail.com> #169
no...@gmail.com <no...@gmail.com> #170
If I disable datas and I use GPS, I have many GPS fix losses.
These losses don't exist if I stay in airplane mode, if I enable datas or if I start the navigation with datas enabled and I disabled later.
I have installed the apk RunGPS Pro Trial to be able to extract GPS datas during a trip.
This application can track the DOP (dilution of precision).
Each trip I made, I can see that I loose de GPS fix at exactly 5 min interval (see graph "DOP")
I have asked each time a bugreport and, each time RunGPS show me I lost the GPS fix, at exactly the same second, I've a network request like that :
DUMP OF SERVICE connectivity:
mNetworkRequestInfoLogs (most recent first):
02-17 17:32:04.007 - REGISTER Request from uid/pid:1000/951 for NetworkRequest [ id=49, legacyType=3, [ Transports: CELLULAR Capabilities: SUPL&NOT_RESTRICTED&TRUSTED&NOT_VPN] ]
02-17 17:27:03.506 - REGISTER Request from uid/pid:1000/951 for NetworkRequest [ id=48, legacyType=3, [ Transports: CELLULAR Capabilities: SUPL&NOT_RESTRICTED&TRUSTED&NOT_VPN] ]
02-17 17:22:03.666 - REGISTER Request from uid/pid:1000/951 for NetworkRequest [ id=47, legacyType=3, [ Transports: CELLULAR Capabilities: SUPL&NOT_RESTRICTED&TRUSTED&NOT_VPN] ]
02-17 17:17:03.518 - REGISTER Request from uid/pid:1000/951 for NetworkRequest [ id=46, legacyType=3, [ Transports: CELLULAR Capabilities: SUPL&NOT_RESTRICTED&TRUSTED&NOT_VPN] ]
02-17 17:12:03.226 - REGISTER Request from uid/pid:1000/951 for NetworkRequest [ id=45, legacyType=3, [ Transports: CELLULAR Capabilities: SUPL&NOT_RESTRICTED&TRUSTED&NOT_VPN] ]
02-17 17:07:02.312 - REGISTER Request from uid/pid:1000/951 for NetworkRequest [ id=44, legacyType=3, [ Transports: CELLULAR Capabilities: SUPL&NOT_RESTRICTED&TRUSTED&NOT_VPN] ]
If I go in the section "SERVICE com.android.phone/.TelephonyDebugService", I found more details :
02-17 17:27:03.509 - clearing log with size=1
NetworkRequest [ id=48, legacyType=3, [ Transports: CELLULAR Capabilities: SUPL&NOT_RESTRICTED&TRUSTED&NOT_VPN] ]
02-17 17:27:03.508 - Dctc.requestNetwork, priority=2
02-17 17:27:03.509 - DcSwitchStateMachine.AttachedState: REQ_CONNECT
02-17 17:27:03.509 - DctController.onExecuteRequest
02-17 17:27:03.509 - DcTracker.incApnRefCount on supl found {mApnType=supl mState=IDLE mWaitingApns={null} mWaitingApnsPermanentFailureCountDown=0 mApnSetting={null} mReason=dataDisabled mDataEnabled=false mDependencyMet=true}
02-17 17:27:03.510 - ApnContext.incRefCount - 0
02-17 17:27:03.510 - applyNewState(supl, true(false), true(true))
02-17 17:27:03.510 - ApnContext.resetErrorCodeRetries
02-17 17:27:03.510 - trySetupData due to dataEnabled
02-17 17:27:03.543 - trySetupData: X apnContext not 'ready' retValue=false
02-17 17:27:33.507 - Cellular releasing Network for
02-17 17:27:33.507 - DctController.releaseNetwork
02-17 17:27:33.507 - DctController.onReleaseRequest
02-17 17:27:33.507 - DcTracker.decApnRefCount on supl found {mApnType=supl mState=IDLE mWaitingApns={null} mWaitingApnsPermanentFailureCountDown=0 mApnSetting={null} mReason=dataEnabled mDataEnabled=true mDependencyMet=true}
02-17 17:27:33.507 - ApnContext.decRefCount - 1
02-17 17:27:33.509 - applyNewState(supl, false(true), true(true))
02-17 17:27:33.509 - cleanUpConnection: tearDown=true reason=dataDisabled
02-17 17:27:33.509 - cleanUpConnection: X tearDown=true reason=dataDisabled
I can see that it's the "supl" APN Type that is requested. That means that data for A-GPS are requested ! But why ? I have already a fix !
Strange things, if I set the Location in "Device only" mode, I have exactly the same requests !
To avoid such requests, I have changed the settings of the GPS in the gps.conf file.
I have disabled MSB in the GPS capabilities section. MSA is already deactivated.
That means I have set the capabilities at 0x31 instead of 0x33 to avoid the 2 modes of operation : Mobile station assisted (MSA) and Mobile station based (MSB).
Like that, I avoid any request from A-GPS...
And, It works like a charm... No more loss of fix with or without data enabled.
That means that when the device send a request for A-GPS datas, whatever the result, the fix is lost !
Now, why 5 minutes ?
In GpsLocationProvider.java, I've found this lines :
// how long to wait if we have a network error in NTP or XTRA downloading
// current setting - 5 minutes
private static final long RETRY_INTERVAL = 5*60*1000;
I have no knowledges in java so, I've stopped to try to understand exactly what's happened with this variable.
I think something is wrong and it is not conditionned by the fact that the fix of the GPS is done.
For users that have a device with root privileges, you can do it by yourself :
With a file explorer like ES explorer, go to "/system/etc"
open the file named "gps.conf"
You should find a variable named "CAPABILITIES"
Edit the file
If this variable is set at 0x37 or 0x35 or 0x33, change the value at 0x31
If this variable is set at 0x36, change the value at 0x30
If this variable is set at 0x27 or 0x25 or 0x23, change the value at 0x21
If this variable is set at 0x26, change the value at 0x20
If this variable is set at 0x17 or 0x15 or 0x13, change the value at 0x11
If this variable is set at 0x16, change the value at 0x10
Save the file and be sure that the permissions of the file are rw-r--r--
Restart the device to take in account the new value and enjoy.
The first fix can take between 30s and 2 min but after that, it should be better and you will not have losses.
It is not a solution, it is a trick to avoid the problem
fe...@gmail.com <fe...@gmail.com> #171
wh...@gmail.com <wh...@gmail.com> #172
di...@gmail.com <di...@gmail.com> #173
I have made some tests with our app and I found out that FusedLocationsApi is not working as before. It does not perform with the same accuracy anymore. Until Android 6, I could easily get locations with accuracy below 10 meters but now, the best I am getting is 25 meters. My Guess, maybe Dozer is not letting FusedLocaitonsApi to work as before in order to save battery (docs does not mention anything related between them).
Cheers
ni...@gmail.com <ni...@gmail.com> #174
Rob.
di...@gmail.com <di...@gmail.com> #175
fe...@gmail.com <fe...@gmail.com> #176
ke...@gmail.com <ke...@gmail.com> #177
lu...@gmail.com <lu...@gmail.com> #178
an...@gmail.com <an...@gmail.com> #179
ev...@gmail.com <ev...@gmail.com> #180
te...@gmail.com <te...@gmail.com> #181
Service provider is VIVO (Brazil).
ku...@gmail.com <ku...@gmail.com> #182
bj...@gmail.com <bj...@gmail.com> #183
Turning of internet and switching to "gps only" mode, i could not get any position data in google maps.
Using GPS Status takes a while for a fix but it will finaly find sattelites to lock on.
The problem never accurs with lollipop.
su...@gmail.com <su...@gmail.com> #184
mi...@gmail.com <mi...@gmail.com> #185
I have the same problem on my Moto G. I'm 1 month into a 4 month trip around SE Asia and without Google map's offline I'd have been lost in Hanoi 100's of times. Then I upgraded to marshmallow and the GPS stopped.
I installed a GPS checker and noticed that when I went on the app the map location updated, but I had to keep flipping between the checker and maps as I moved to get the map position updated.
So I installed a GPS widget hoping it would force the GPS to stay enabled. Good news it works!
The widget I used is called "GPS Widget" but there are probably others, you can set how long this one stays on in hours upto 8. I was nearly going to buy a new phone but now it works just as it used to on lollipop. Give it a go.
no...@gmail.com <no...@gmail.com> #186
Hello, did you tried with the app "gps locker" ?
Normally, it permit to lock the GPS when you turn it on to avoid what you explained...
da...@gmail.com <da...@gmail.com> #187
su...@gmail.com <su...@gmail.com> #188
jw...@gmail.com <jw...@gmail.com> #189
ag...@gmail.com <ag...@gmail.com> #190
du...@gmail.com <du...@gmail.com> #191
When they are activated (the fitness trackers) the GPS shows as a strong signal and they will show current location on their maps, but when the phone screen is not active, they cannot access the GPS, so I end up with a one hour strenuous walk as being 10m or 20m instead of 6-7km!
RunKeeper assure me it is not their app. HTC support said to run GPSTest App in Safe Mode, which of course shows very active signals and accuracy while it is on screen...
Also, HTC Sync no longer works, despite all the System and App cache flushing, reinstalling etc., nothing has fixed that...
Google say "Marshmallow is heavily modified by HTC for their phones, you need to contact them". HTC say, "the GPS Test shows the GPS is working, it must be the App"...
WTF! Nobody wants to take the responsibility of fixing this!
It was all working fine on Lollipop... and because I can't "see" the phone in HTC Sync I can't restore an old (now very old) backup and get a working GPS again...
Anybody have any ideas on the HTC Sync problem?
#145 I'll give this a try and see if that helps!
#170 - Great diagnostics work, pity you have to do Google's job for them... C'mon Google, there are so many complaints here from so many different brands that the only common denominator is Marshmallow! Are you working on a fix? At least let your loyal followers know before you foist Nougat onto us - or is that your plan? The N version will fix everything so you're not wasting your time making M actually work??
du...@gmail.com <du...@gmail.com> #192
Worked perfectly!! Didn't activate my screen once during the workout and checked it at the end, map showed complete route and the maps showed full pace and elevation data.
Mind you my battery went from 70% to 30% in that hour without saver running.
cf...@gmail.com <cf...@gmail.com> #193
so...@gmail.com <so...@gmail.com> #194
Hope this helps.
so...@gmail.com <so...@gmail.com> #195
ma...@gmail.com <ma...@gmail.com> #196
I flashed CM13 the stable release on my N5, and my GPS works again :D
jo...@gmail.com <jo...@gmail.com> #197
ca...@gmail.com <ca...@gmail.com> #198
ow...@gmail.com <ow...@gmail.com> #199
li...@gmail.com <li...@gmail.com> #200
ra...@gmail.com <ra...@gmail.com> #201
As I leave my phone in power saving mode to balance battery issues from living in a quarter mile poor signal area and I generally just listen to the verbal cues rather than waste screen battery, this is a real issue. Please fix.
ni...@gmail.com <ni...@gmail.com> #202
da...@gmail.com <da...@gmail.com> #203
b....@gmail.com <b....@gmail.com> #204
It's very hard to fix GPS. Runkeeper log my run very bad. GPS seems to lost, when screen is off. With google map and screen always display => ok.
After 6.0., this weekend, issue is still here.
Please fixit!
lu...@gmail.com <lu...@gmail.com> #205
Google please fix!
ma...@googlemail.com <ma...@googlemail.com> #206
Maybe that can help with troubleshoting and for my programmer colleagues to fix the problem with a Workaround:
Moto X Android 5.x: no problem at all using LocationServices.FusedLocationApi.requestLocationUpdates
Moto X Android 6.0 : when using LocationServices.FusedLocationApi.requestLocationUpdates the problem occurs reproduceable: no GPS signals are coming to the event handler
Workaround:
instead of using LocationServices.FusedLocationApi.requestLocationUpdates calling mLocationManager.requestLocationUpdates(LocationManager.GPS_PROVIDER, 1000, 0, this) is working.
But: as the best-practice is to use the newer FusedLocationApi and a lot of apps are using this newer method, Google should fix it very quickly. This seems to be a very serious bug within Android 6.0.0.
so...@gmail.com <so...@gmail.com> #207
It's a new power saving mode introduced in Marshmallow that tends to be a bit over-zealous. It's called "Doze" and it puts apps REALLY to sleep when the screen turns off. You can disable this feature on a per app or process basis in Settings\System\Battery\More\Optimize Battery Usage. In there you can disable the Doze feature on whatever app or service you want.
Hope this helps.
Why isn't this more common knowledge by now? And, it seems like a poorly implemented feature if it kills the GPS when your screen turns off...
cj...@gmail.com <cj...@gmail.com> #208
cj...@gmail.com <cj...@gmail.com> #209
Thanks! This one is the solution for me.
I'll keep this thread if I notice anything else.
rp...@gmail.com <rp...@gmail.com> #210
Rafael Pontes
so...@gmail.com <so...@gmail.com> #211
rp...@gmail.com <rp...@gmail.com> #212
Rafael Pontes
b....@gmail.com <b....@gmail.com> #213
b....@gmail.com <b....@gmail.com> #214
I do a factory reset same issue.
I disable optimize battery for "Fused location", "Motorola Sensor Service" (GPS??) and runkeeper. Tomorrow I'll try it.
"Turns out it's not a bug, but a feature" => a feature that result inability to use the GPS !!
ow...@gmail.com <ow...@gmail.com> #215
Today I have got an update of Google Maps. I tried again the GPS position fix within Google Maps. I still do not get a GPS position fix when I just open Google Maps and press the position button on the right side (wifi and cell position fix does work, but is too inaccurate). BUT I do get a GPS position fix immediately when I start the navigation part of Google Maps to any location. My location marker follows my position correctly.
ge...@gmail.com <ge...@gmail.com> #216
so...@gmail.com <so...@gmail.com> #217
rp...@gmail.com <rp...@gmail.com> #218
Rafael Pontes
+55 48 9902.0648
so...@gmail.com <so...@gmail.com> #219
So, I don't know what else to do at this point, since it flat out does not work for Strava, except to disable Power Saving Mode when using it. It's really frustrating to have a BRAND NEW GALAXY S7 with this kind of issue out of the box.
On a final note, I was told to expect Android N in 30-60 days for my phone. Android N is supposed to have a refined version of Doze which should resolve these types of issues.
That's all I got. Good luck everyone.
Galen
mi...@gmail.com <mi...@gmail.com> #220
ga...@gmail.com <ga...@gmail.com> #221
ge...@gmail.com <ge...@gmail.com> #222
th...@gmail.com <th...@gmail.com> #223
gc...@gmail.com <gc...@gmail.com> #224
re...@gmail.com <re...@gmail.com> #225
I did the updates and... Doesn't work anymore...
I just send it again on warranty.
lo...@gmail.com <lo...@gmail.com> #226
Come on Google, sort this out please
al...@gmail.com <al...@gmail.com> #227
li...@gmail.com <li...@gmail.com> #228
li...@gmail.com <li...@gmail.com> #229
I've followed "misterdo...@gmail.com" tips (comments #185 and #220) by installing a GPS WIDGET and all my gps apps worked fine!!
Thank you "misterdo...@gmail.com"
gl...@gmail.com <gl...@gmail.com> #230
"Device Only" location mode no longer works. Every app that uses the Google Maps/Location API returns 0,0 and puts your dot just off the West coast of Africa.
Steps to reproduce:
1. Set location mode to "Device Only"
2. Open Hangouts, Whatsapp, Telegram, etc., and try to share your location with someone
This seems consistent with the main bug reported here - Maps no longer activates/holds the GPS open properly. Pretty disheartening after 6 months. :(
th...@gmail.com <th...@gmail.com> #231
th...@gmail.com <th...@gmail.com> #232
Installed the GPS Widget, and while it seemed to work fine for Maps, I was not receiving verbal notification of GPS signal lost, Zombies Run! definitely was having the same issue. When I would turn the screen back on it would readjust my position, and the sound track (which was set to certain distances) would catch up. See screenshot of how it was 'off', path should have followed the black dotted line, which was the road I was on.
Turned off the battery optimization for the entire phone, and have had no issues with GPS when I tested again with the same program/'mission' as the previous day.
mi...@gmail.com <mi...@gmail.com> #233
Glad it's sorted your problem out. ☺
da...@gmail.com <da...@gmail.com> #234
bm...@gmail.com <bm...@gmail.com> #235
a....@gmail.com <a....@gmail.com> #236
he...@gmail.com <he...@gmail.com> #237
yo...@gmail.com <yo...@gmail.com> #238
gu...@gmail.com <gu...@gmail.com> #239
gu...@gmail.com <gu...@gmail.com> #240
yo...@gmail.com <yo...@gmail.com> #241
co...@gmail.com <co...@gmail.com> #242
gu...@gmail.com <gu...@gmail.com> #243
le...@gmail.com <le...@gmail.com> #244
Navigation is fluid for 5 min, then GPS fix is lost and updated about once every 30 seconds. Same in Google Maps and Waze.
b....@gmail.com <b....@gmail.com> #245
Android: Marshmallow 6.01
No root
Non optimized apps:
Fused Location
GPS status
Google Map
Run keeper
Power Saving Mode disabled
Test 1:
Google Map + GPS widget, wired Moto
first 250km (2 hours) => ok
stop (cofee time), screen off
no way to fix again GPS :( I need restart the phone
Test 2:
Run keeper + GPS Locker, Moto used battery
1 hour used seems => ok
average speed was ok
best speed near 50km/h (31 mph), => ko, who can run at 31mph!? Never had this issue before android 6
I’ve got a good smartphone, I don’t want buy a navigation device and gps sport watch!!
PS: all was good with android 5.x :(
b....@gmail.com <b....@gmail.com> #246
pa...@gmail.com <pa...@gmail.com> #247
I've checked the WiFi settings are allowed to be used for location refinement.
I've cleared the system cache.
I've turned off Battery Optimisation for all GPS-related apps (notably Maps and the GPS Status app I'm using to try and debug)
I've attempted using the GPS Status app and it's finding "0/21 satellites" even when used outside.
My mobile service provider is 3 in the UK.
Any suggestions what next?
fl...@gmail.com <fl...@gmail.com> #248
How the heck could Google miss this?
ka...@gmail.com <ka...@gmail.com> #249
Any suggestions? please help
ro...@gmail.com <ro...@gmail.com> #250
pk...@gmail.com <pk...@gmail.com> #251
After a lot of tries found a temporary workaround for GPS fix.
1. Download Disable Service from play store
2. Install, open and give root permission.
3. Disable GoogleLocationManagerService from Google play services app
4. Open Google maps app
Wow it locks with accurate GPS position.
Note: Don't know the sideeffects, but getting a Google play services stopped error after closing Google Maps, but all other functions including sync and Google play store works.
Some people reported about random Google now crashes.
ow...@gmail.com <ow...@gmail.com> #252
So, Google developers, what is wrong with our systems? Is there any fix you can provide us with? Did you find something out about this issue? Do you need more information from us in order to track this down?
This bug is really annoying. Some days ago I had to use Google Maps in order to take an alternate route to avoid a traffic jam. I got lost, badly lost...
ji...@gmail.com <ji...@gmail.com> #253
As one firmware engineer to the teams at Google, Samsung, T-Mobile... you have an EPIC Fail. You let a clueless marketing guy talk you into killing the functionality of the phone while pursuing 5-8% improvement in battery life. Stupid.
The only solution that I was able to ascertain from Samsung and T-Mo is to go to a Best Buy that has Samsung personnel in-house to flash my S6 back to Android 5.1.1 ... Which is just fine! The GPS works in both Power Save and Airplane mode which is what I need.
b....@gmail.com <b....@gmail.com> #254
With Marshmallow, my gps smartphone is useable as gps, like my old android 2 smartphone!
pa...@gmail.com <pa...@gmail.com> #255
Disable "FusedProviderService" instead of googlelocationmanagerservice. Google now also still works.
pe...@gmail.com <pe...@gmail.com> #256
jo...@gmail.com <jo...@gmail.com> #257
Jc
pe...@gmail.com <pe...@gmail.com> #258
pe...@gmail.com <pe...@gmail.com> #259
sc...@gmail.com <sc...@gmail.com> #260
ro...@googlemail.com <ro...@googlemail.com> #261
of...@gmail.com <of...@gmail.com> #262
cr...@gmail.com <cr...@gmail.com> #263
I can get GPS fix but every 5 minutes I get message "awaiting gps signal"...and after minute or so I get fix again...and so on and on..
I'm so sick of it... :-(
pe...@gmail.com <pe...@gmail.com> #264
co...@gmail.com <co...@gmail.com> #265
Please release a fix due to this we are Stuck in Lollipop release.
do...@gmail.com <do...@gmail.com> #266
of...@gmail.com <of...@gmail.com> #267
ro...@gmail.com <ro...@gmail.com> #268
ch...@gmail.com <ch...@gmail.com> #269
Used to work fine but recently doesn't work.
ja...@gmail.com <ja...@gmail.com> #271
da...@gmail.com <da...@gmail.com> #272
please.. i have some problem about gps on my phone.
after i'm update to android 6.0
please google, gps is very important for me.
please fix it.
thx google
no...@gmail.com <no...@gmail.com> #273
Thank you for the news.
I hope that it wiil solve the problem.
I've written post 170 and I think it's incredible that Google give us no news about development !
pe...@gmail.com <pe...@gmail.com> #274
pe...@gmail.com <pe...@gmail.com> #275
ch...@gmail.com <ch...@gmail.com> #276
jo...@gmail.com <jo...@gmail.com> #277
gr...@gmail.com <gr...@gmail.com> #278
Same problem on LG G3 after update to Marshmallow. GPS out -> "gps signal lost".
ow...@gmail.com <ow...@gmail.com> #279
If I open Google Maps and start the driving mode I get a GPS signal immediately.
Using Google Maps in standard mode does still not provide a GPS signal.
jo...@gmail.com <jo...@gmail.com> #281
GPS will lock for about 30 seconds on boot, then lose lock.
Only way to regain GPS (device only) lock is by switching phone into CDMA only or turning off data completely.
To replicate:
1) Install GPS Status app.
2) Set Mobile Data to "Automatic" and Location mode is set to "Device Only".
3) Reboot device, launching "GPS Status" immediately after boot.
4) After 30 seconds to 1 minute GPS Signal will be lost.
5) Switch Mobile Data to "CDMA only" switch back to GPS Status app. GPS will get lock in seconds.
6) Switch Mobile Data to "CDMA/LTE Only" switch back to GPS Status app. GPS will no longer have a lock and will not gain one again. Waited upwards of 15 minutes on a couple occasions. Closing and re-opening app to no avail.
7) Switch Mobile Data back to "CDMA Only" switch back to GPS Status app. GPS will get lock again in seconds.
Discovery additionally this morning that the device loses it's GPS connection when connected to LTE.
GPS works fine when connected to 3G, but as soon as it connects to LTE the GPS signal is dropped.
br...@gmail.com <br...@gmail.com> #282
e3...@gmail.com <e3...@gmail.com> #283
There is a thing called LPP or LTE Positioning Protocol. I guess setting Android to 'device only' location settings stops LPP (together with the WiFi database) from adding location data into the mix with GPS sensor data for more accurate positioning. But I'm also guessing it still allows LTE (via LPP, a.k.a. the mobile network) to help A-GPS figure out the initial position to get the GPS/Glonass/BD positioning up and running quickly. Anybody know for that a fact?
I've learned that (W)CDMA doesn't use LPP but has it's own set of positioning protocols (RRC & RRLP). So, if things improve when you remove LTE and implicitly its positioning capabilities via LPP, I guess the questions are;
- Is LPP not as good as RRLP?
- Is the LPP implementation in Android not working properly?
- Is the LPP implementation of certain providers set up properly?
Also maybe relevant as many upgraders seem to be complaining, did Lollipop support LPP?
Just my uneducated guesses :)
(LG G5, 6.0.1, Vodafone NL; erratic positioning, sudden location freezes and/or position offset by fixed distance.)
se...@gmail.com <se...@gmail.com> #284
I have noticed, and this may be an important clue, that when I turn off location Ingress inmediately shows me a prompt asking for location services. It's quite weird, because Ingress allows playing for 5 minutes with location turned off, but since the issue started Ingress complains in the same second I pull up the notification bar after turning off location.
rs...@gmail.com <rs...@gmail.com> #286
- Make sure you have the Android tools on your PC.
- From bootloader enter these commands:
fastboot erase modemst1
fastboot erase modemst2
- Reboot.
- It's a good idea to use a program like "GPS Status & Toolbox" so you can verify GPS and force an AGPS reload.
More info is available here, but you don't have to flash anything like NON-HLOS.bin:
And here:
Apparently this has been a known thing since 2014.
I am only posting this because it helped me. I'm not promising it will work for anyone else. But it's unfortunate that no one inside Google has publicized this because it's definitely a thing people are tripping over.
rs...@gmail.com <rs...@gmail.com> #287
zo...@gmail.com <zo...@gmail.com> #288
fe...@gmail.com <fe...@gmail.com> #289
I made a detailed thread on xda developers explaining the problem:
ya...@gmail.com <ya...@gmail.com> #290
ps...@gmail.com <ps...@gmail.com> #291
ol...@gmail.com <ol...@gmail.com> #292
Now my phone is reverting back to lock-screen right after I put in the unlock PIN. It gets unlocked shows a dialog box and quickly reverts back to locked screen before I could read the message in the dialog box. All I could recognize within the split moment is the word "Skype".
Booting into Safe Mode did not solve the problem.
It worked fine before I plugged it in and went to bed, only to wake up and find he phone dead, I charged it and since then I've not been able to get past the locked screen. Bluetooth was on when I plugged the phone in and I went to sleep for the night.
ke...@gmail.com <ke...@gmail.com> #293
gr...@gmail.com <gr...@gmail.com> #294
After my LG G3 (#279), It's the turn of my wife, on is LG G4S after update to Marshmallow. GPS failed
Can we hope a true solution from google ?
ya...@gmail.com <ya...@gmail.com> #295
I think I found a little workaround for my nexus 5 device.
Previously I cannot navigate via google maps, endomondo and strava GPS loggers are also losted GPS signal randomly.
I started to search proper solution by my own.
Please try to use similar setting on your devices:
1. Go to settings->applications->Configure applications->Battery optimalizations:
Switch off battery optimalizations of all GPS apps:
maps,strava,gps,status,endomondo and other apps of your interest.
Important: Switch off battery optimalization for Google Service:
this service named as "Average location"
2.Go to Settings -> Localization -> Scanning :
Turn OFF wifi scanning and turn ON bluetooth scanning.
Thats all on my side I noticed a little improvement especially in time to get GPS-fix.
Moreover GPS is more accurated but I think there is still some problem with real-time compass.
I hope that will be helpfull for some of you.
pa...@gmail.com <pa...@gmail.com> #296
Static determination of position is not working in Maps [now on version 9.25.1]. However, when navigating it DOES work. Interestingly, only when MAPS starts actually navigating, it show a grey "searching for GPS" popup and makes a fix.
I installed the GPS-Status app. It has a setting that that enables a radar-like icon in the notification bar that shows when other programs access the GPS [Settings > Background behaviour > GPS Status in notification bar > Show notification when GPS is in use].
With this option enabled, I see that MAPS does NOT access the GPS in static position determination [no radar-like icon in notification bar], but when I tell MAPS to start navigating to a certain location, the icon shows up and Maps is working like it should.
Tried all battery optimization scenarios, but that did not solve the issue.
Also disabling the Maps app and restoring the default version and then updating again to the latest version of Maps, did not solve the issue.
I'm now regretting the update to Marshmellow due to this Maps issue...
pu...@gmail.com <pu...@gmail.com> #297
I am seriously thinking root it and may be tried some of the "solutions" mentiond above. The worst case would be flash back to Lollipop or but another phone with still Lollipop. :(
Still lingering hope that someone may find the answer to this non-sense dead-grade.
ow...@gmail.com <ow...@gmail.com> #298
did anyone with a Moto G 2nd Gen try to reset his phone to factory defaults? Do you think this will help getting GPS and Google Maps working again?
se...@gmail.com <se...@gmail.com> #299
sh...@gmail.com <sh...@gmail.com> #300
I upgraded my LG G3 to 6.0, and I have the GPS issue. Apps can't find any GPS ( offline Maps), I always to disable and re-enable GPS to work but not working. (WiFi scanning is on)
And also battery low very very fast after update
Please help me to fix this
se...@gmail.com <se...@gmail.com> #301
se...@gmail.com <se...@gmail.com> #302
As many said, the only thing worked for me to fix the GPS signal dropping is turning off "Mobile Data", meaning no internet while driving.
ma...@gmail.com <ma...@gmail.com> #303
se...@gmail.com <se...@gmail.com> #304
Again, as i said on #303, it works flawessly with "Mobile Data" off.
jo...@gmail.com <jo...@gmail.com> #305
al...@snowmoose.com <al...@snowmoose.com> #306
On the drive home, as I was approaching the part of the route where I needed to change highways, I started HERE to guide me through. It initially displayed my current position, but shortly after would report that it was acquiring GPS. I switched to Google Maps and saw similar behavior. I ended up shutting down and restarting the app again and again to confirm that I was still on route.
As noted, it worked on the drive up and had problems on the drive back. There were several software updates installed while I was at my destination; I don't know if these introduced the problem.
th...@gmail.com <th...@gmail.com> #307
bo...@dyob.ca <bo...@dyob.ca> #308
om...@seznam.cz <om...@seznam.cz> #309
ad...@gmail.com <ad...@gmail.com> #310
de...@gmail.com <de...@gmail.com> #311
pe...@gmail.com <pe...@gmail.com> #312
ry...@gmail.com <ry...@gmail.com> #313
na...@gmail.com <na...@gmail.com> #314
vl...@gmail.com <vl...@gmail.com> #315
an...@gmail.com <an...@gmail.com> #316
jo...@gmail.com <jo...@gmail.com> #317
ia...@gmail.com <ia...@gmail.com> #318
ru...@gmail.com <ru...@gmail.com> #319
kt...@gmail.com <kt...@gmail.com> #320
ma...@gmail.com <ma...@gmail.com> #321
ku...@gmail.com <ku...@gmail.com> #322
rs...@gmail.com <rs...@gmail.com> #323
bp...@gmail.com <bp...@gmail.com> #324
br...@gmail.com <br...@gmail.com> #325
Tried to fix with
fastboot erase modemst1
fastboot erase modemst2
but got failed error (phone is unlocked)
Then installed GPS Status app, I've chosen this one
Run it and keep approx 25 minutes, and then catch several satellites. Now it is all fine.
ca...@gmail.com <ca...@gmail.com> #326
3g + GPS works
Ltd + GPS makes the signal drop even after a strong initial fix
Try androidits from play to see the strength of the signal
Regards
ca...@gmail.com <ca...@gmail.com> #327
ib...@gmail.com <ib...@gmail.com> #328
ib...@gmail.com <ib...@gmail.com> #329
jo...@gmail.com <jo...@gmail.com> #330
ca...@gmail.com <ca...@gmail.com> #331
Is the only work around I have found and it works
bo...@dyob.ca <bo...@dyob.ca> #332
ca...@gmail.com <ca...@gmail.com> #333
You must set the radio preferences to 3g.....which by the way downloads in real time Google maps in a fly..
al...@gmail.com <al...@gmail.com> #334
th...@gmail.com <th...@gmail.com> #335
pk...@gmail.com <pk...@gmail.com> #336
vi...@gmail.com <vi...@gmail.com> #337
My mobile is Nexus 5 32 Gb. Please help me on this how to resolve this problem.
pa...@hotmail.com <pa...@hotmail.com> #338
th...@gmail.com <th...@gmail.com> #339
I turned off the power save in my phone (Settings > Power > Power Saver > Off). I tested Strava with the GPS and it worked perfectly. The screen went off and the GPS continued to track.
Obviously not a Strava problem, but is a Marshmallow problem and quite a glaring one. Google need to fix this. Power Saving seems to also turn off the gps as soon as the screen is off.
No difference to my battery without the power saver anyway. Not sure that it was doing much.
fa...@gmail.com <fa...@gmail.com> #340
Samsung Galaxy S5 Neo on Lollipop GPS did not work. Replacing gps.conf file and edit it did not help. After updating to 6.0.1 GPS does not work. It happened that a couple of times caught a GPS fix-and after 2-3 seconds and held for about 30 minutes. Later signal fading. GPS worked well on KitKat.
My network is T-Mobile Poland.
Will there be an amendment to Android 6.0.1 to activity GPS?
PS Sorry for my English.
Regards Simon
ca...@gmail.com <ca...@gmail.com> #341
GPS + 3g
pe...@gmail.com <pe...@gmail.com> #342
da...@gmail.com <da...@gmail.com> #343
pu...@gmail.com <pu...@gmail.com> #344
jc...@gmail.com <jc...@gmail.com> #345
what update are your referring to? An app update? marshmallow OS update, if so which one? remind me of your phone model please?
sh...@gmail.com <sh...@gmail.com> #346
go into your date and time settings. Once there would you please set your device clock to manual and then set it to the wrong time. After you have done this, please go to your home screen and close all the applications using the recent apps button to the left of the home button. After you have completed all this, please go back to the date and time settings and set it back to the correct time and set it back to automatic time. Additionally, please ensure you do not have power saving mode enabled on your device.
jc...@pacpac.com <jc...@pacpac.com> #347
My phone is an HTC 10 with Android 6.01
do...@gmail.com <do...@gmail.com> #348
Have had similar issues since upgrading to Marshmallow, with GPS being lost regularly in Waze/Maps or being very inaccurate.
I have never considered moving to iPhones and away from Android before, but this issue is driving me insane (and costing me a lot of time) and I will have to switch if i cannot get this sorted.
Seriously google - it's been 9 months since this was reported... PLEASE make this a top priority and work out a fix!
My bug reports from today are at
do...@gmail.com <do...@gmail.com> #349
Is there a typo in android-bugreport?
dm...@gmail.com <dm...@gmail.com> #350
pe...@gmail.com <pe...@gmail.com> #351
I have a Samsung Galaxy S7 Edge, the update was an OS update. Looking at software info, it was build MMB29K.G935FXXU1APF2 1 June security patch level.
se...@gmail.com <se...@gmail.com> #352
sz...@gmail.com <sz...@gmail.com> #353
Signing in and out of Google seemed to jog something. But ultimately didn't resolve anything. Tried gps status also did not work.
al...@gmail.com <al...@gmail.com> #354
ki...@gmail.com <ki...@gmail.com> #355
sz...@gmail.com <sz...@gmail.com> #356
sz...@gmail.com <sz...@gmail.com> #357
ow...@gmail.com <ow...@gmail.com> #358
Unfortunately GPS still does not work with Google Maps when using the standard mode (not driving mode). :(
ja...@gmail.com <ja...@gmail.com> #359
GPS works fine in some apps (Pokemon go lol), has a lot of lag and imprecision in gmaps and doesn't work at all in other apps (takes a few minutes to get the first location, randomly looses connection again after a few seconds or doesn't provide any further location updates)
Already tried to reboot the device, enabled and disabled the different gps options and finally even downloaded new apgs data.
an...@gmail.com <an...@gmail.com> #360
I have the Moto G 2nd gen, and because this issue, I made a full resert to factory defaults, but it was van.
ki...@gmail.com <ki...@gmail.com> #361
du...@gmail.com <du...@gmail.com> #362
ki...@gmail.com <ki...@gmail.com> #363
th...@gmail.com <th...@gmail.com> #364
ma...@gmail.com <ma...@gmail.com> #365
wi...@gmail.com <wi...@gmail.com> #366
jm...@gmail.com <jm...@gmail.com> #367
al...@gmail.com <al...@gmail.com> #368
wi...@gmail.com <wi...@gmail.com> #369
None of the above worked. did reset and all is even better...
EDIT! not working, traveled from home to work using internet from MIFI device (downloading apps after reset) and it worked as it should. Came from work on LTE and stoped working in 5 min intervals with verry low acuracy (30m+).
will send it on waranty.
pe...@gmail.com <pe...@gmail.com> #370
n0...@gmail.com <n0...@gmail.com> #371
az...@gmail.com <az...@gmail.com> #372
I tired the 'GPS status' and it was able to locate me withing a minute showing 7 satellites above.
Tired everything - from resetting phone, uninstalling then again installing etc and etc but nothing helped.
Now am unable to use Google fit to keep track of my cycling routes.
Reported the issue many a times, but no fix till date.
ro...@gmail.com <ro...@gmail.com> #374
Really waiting for an update, I really need a gps on my phone and it's actually not possible to use it properly...
jc...@gmail.com <jc...@gmail.com> #375
wa...@gmail.com <wa...@gmail.com> #376
There is clearly a marked difference between the location reporting on the Lollipop devices and the Marshmallow ones, with the 6.0.1 devices being very intermittent and a lot less accurate.
Following on from suggestions on here, i have made some amendments to the Battery Optimization and Power Saving for two of the 6.0.1 users and i will come back with my findings.
an...@gmail.com <an...@gmail.com> #377
ma...@googlemail.com <ma...@googlemail.com> #378
al...@gmail.com <al...@gmail.com> #379
du...@gmail.com <du...@gmail.com> #380
la...@gmail.com <la...@gmail.com> #381
la...@gmail.com <la...@gmail.com> #382
I would not work the GPS in Moto G 2014 (XT1068) in 5.0.2 worked perfectly. I've tried a fastboot the two commands, but has not done any good, enter as usual. Does anyone know any solution? All I can think of is active try to make a clean installation
am...@gmail.com <am...@gmail.com> #383
am...@gmail.com <am...@gmail.com> #384
pt...@gmail.com <pt...@gmail.com> #385
sollution:
install gps toolbox, reset agps, then download.
install faster gps for the correct country gps.conf file
reboot
pt...@gmail.com <pt...@gmail.com> #386
pi...@gmail.com <pi...@gmail.com> #387
co...@gmail.com <co...@gmail.com> #388
ke...@gmail.com <ke...@gmail.com> #389
be...@gmail.com <be...@gmail.com> #390
No problems to locate me in streets, but in parcs, it's horrible, impossible to play Pokemon Go, the position jumps away...
pe...@gmail.com <pe...@gmail.com> #391
ke...@gmail.com <ke...@gmail.com> #392
pb...@gmail.com <pb...@gmail.com> #393
xn...@gmail.com <xn...@gmail.com> #394
ma...@gmail.com <ma...@gmail.com> #395
su...@gmail.com <su...@gmail.com> #396
l....@gmail.com <l....@gmail.com> #397
I was relying on native geolocation via an Cordova plugin, but while investigating I found out that that Cordova recently changed the plugin to be just a wrapper for native html5 geolocation. So I changed the app to use a native Android geolocation plugin (android.location.*) and that did the trick. It is now reliable again.
I also tried using Google Play services plugin for providing positions (com.google.android.gms.* i believe) but that was almost worse than native html5.
So conclusion is that there's something not working in native html5 geolocation. The question is if Huawei or Google is to blame. My money would be on Google.
on...@gmail.com <on...@gmail.com> #398
lg...@gmail.com <lg...@gmail.com> #399
ec...@gmail.com <ec...@gmail.com> #400
I live in Australia. I'd had no issues at all, though I do use it infrequently.
Currently I am travelling in the USA. And the first time the issue occurred was after I entered a new time zone and the time on the phone updated automatically. (I'd travelled hundreds of miles before then without a problem).
After performing the workaround, I lost GPS once, immediately after. But not since. I've kept my time on manual settings and all is good.
jr...@gmail.com <jr...@gmail.com> #401
hh...@gmail.com <hh...@gmail.com> #402
ti...@the-sampsons.co.uk <ti...@the-sampsons.co.uk> #403
wi...@gmail.com <wi...@gmail.com> #404
li...@gmail.com <li...@gmail.com> #405
k....@gmail.com <k....@gmail.com> #406
da...@gmail.com <da...@gmail.com> #407
lh...@gmail.com <lh...@gmail.com> #408
I want to let you know I installed TopNTP 1.1 and will try. Also there's a recommendation to switch to 3G, obviously 4G can cause the issue. I will try it and let you guys know!
lh...@gmail.com <lh...@gmail.com> #409
hi guys, I can confirm (Ulefone Power - 64 Bit MTK6753) I fixed the GPS issues by disabling 4G network. After switching to 3G I tracked using Strava about 3km of walk with NO issue. When I used 4G the issue appeared in about 5mins. Good news
Google Developers - any plans to fix this issue in near time, please?
lu...@gmail.com <lu...@gmail.com> #410
Semi-workaround discovered: Menu > Start Driving (without a destination), I get 'Wating for GPS' briefly then the GPS position starts updating. After pressing 'back' the position might update (once) on the main map view too.
My story: in a unfamilar town, wife takes a wrong turn, baby is getting scratchy. Just the time when GPS on a map would be /really/ handy. Sorry to add to the moaning, but this is the one bug that made me swear in front of the kids ;-)
lu...@gmail.com <lu...@gmail.com> #411
aj...@gmail.com <aj...@gmail.com> #412
ru...@gmail.com <ru...@gmail.com> #413
When I updated my phone to 6.0.1 Marshmallow then the GPS start to lose the localisation. On the Lollipop my GPS module worked perfectly.
Samsung says me that my GPS module is broken. Hardware problem. They are idiots. I'm waiting now for the bug patch :/
ki...@gmail.com <ki...@gmail.com> #414
The Fix
---------------
Replacing the Phone WILL NOT fix the issue.
Resetting the phone WILL NOT fix the issue.
Google Nexus 5x had a similar issue and the fix came with the 6.0.1 update. Nobody else gets any.
Build: MRA58K
Android version: 6.0
-------------------------------------
The Fix
You need to change your phone from LTE 4g to 3g. (radio setting)
First Go to Settings
Select Wireless and Networks
Scroll Down and Touch on Mobile Network
Select “Network Mode”
You will get a Pop Up Screen
Choose WCDMA only
Back out of all settings. Reboot.
Your done.
WCDMA (Means 3G) , GSM (2G ) , LTE (4G)
That's it. Go for a drive and test it.
I hope this post finds you in good health and enjoying life.
With kindest personal regards. Be happy.
sm...@gmail.com <sm...@gmail.com> #415
tr...@gmail.com <tr...@gmail.com> #416
Had the same problems with my Galaxy J5. Very few satellites fix when using GPS on Maps or Waze.
I've tried all possible fixes such as installing GPS Tolls, GPS Fix etc. set to accuracy mode on settings, but with no positive results. The GPS fix was just awfully weak and useless...
What I did? I did a complete hard reset on the phone, setting it back to Marshmallow 6.0.1 (it was on 6.1). All issues gone. GPS now fixes in around 5-10 secs with 8-10 satelites.
Please do a hard reset. It doesn't hurt and probably you will solve the question, since the phone will be reseted to it's original state.
tr...@gmail.com <tr...@gmail.com> #417
ky...@gmail.com <ky...@gmail.com> #418
I'm on Rogers Network in Canada and went to the US on the weekend and roamed onto AT&T and my GPS started to work again. There were some times while I was down there over the 3 days when I would lose the GPS but I would get it back. As soon as I got back to the Rogers network, I lost the GPS again and it has not come back.
Android 6.0.1
Baseband G930W8VLU2APJ4
Kernel Version
3.18.14-9105000
dpi@SWHC3606 #1
Tue Oct 11 20:38:21 KST 2016
Build number
MMB29K.G930W8VLU2APJ4
yi...@gmail.com <yi...@gmail.com> #419
Phone Model: G930FD (Dual Sim) - bought from Amazon Unlocked (Not Opus device)
Android version: 6.0.1
Kernel version: 3.18.14-8888212
KNOX version: 2.6
So far I've tried the following:
1. hard reset the device
2. *#0*# to calibrate "magnetic sensor" until it shows "Blue 3"
3. on/off GPS
I installed "GPS Test" and it shows No GPS satellite signals detected.
Reading through the thread and other forums, I also don't think this is a "S7 dual sim" model only issue.
GPS (and Google map) is an important function to me therefore I am inclined to return the device back to Amazon at this point.
Any other suggestions that I would try?
Referece thread:
br...@gmail.com <br...@gmail.com> #420
da...@gmail.com <da...@gmail.com> #421
da...@gmail.com <da...@gmail.com> #422
tr...@gmail.com <tr...@gmail.com> #423
If you are on maps or waze and you lose the GPS:
1. Turn off mobile data
2. turn off and then turn on GPS
PS: leave mobile data OFF!
al...@gmail.com <al...@gmail.com> #424
fe...@felixwong.ca <fe...@felixwong.ca> #425
j....@gmail.com <j....@gmail.com> #426
I have a Samsung S5 mini (SGH800) which got the update barely a week ago. And since then the gps doesn't respond as it should.
It takes longer to get first lock and then keeps losing it.
I use the gps for work and this situation is a huge problem for me. Besides the inconvenience it can cause safety issues too.
I don´t understand how a problem that's been identified over a year ago is still without resolution.
What am i supposed to do? Buy a new phone? If i have to do that, what assurance do i have it won't have the same problem? Will I be forced to buy with another os?
bg...@gmail.com <bg...@gmail.com> #427
pa...@gmail.com <pa...@gmail.com> #428
I was lucky to be able to capture it on video:
lu...@gmail.com <lu...@gmail.com> #429
GPS so far seems to be working in Maps again! Yay, nice Xmas present.
Android v6.0. Motorola(?) build number: MPB24.65-34-3
lu...@gmail.com <lu...@gmail.com> #430
Google: if this is a battery saving technique - to use just Wifi and Cell networks to save battery on the (non-driving) map screen - it DOES NOT WORK effectively in Europe!
I had much frustration trying to find a 'nearby' location again today. I normally have mobile data off. When I go out of wifi range the location marker jumps to some OLD gps location. Ironically, it seems to update the blue circle to tell me that an accurate (gps) location is available (which it is, in other apps) but it's completely the wrong place in Maps. I can force GPS to update using another app: the location comes temporarily correct on the Map, but then shortly jumps back to the OLD location again! Only in driving mode does it keep a GPS position.
Please fix!
Or could you at least respond to this ticket and suggest the best workaround. Should I just try reverting Maps to the ancient original version? Or roll back Marshmallow to Lollipop (and lose the otherwise good battery saving enhancements)?
on...@gmail.com <on...@gmail.com> #431
ka...@gmail.com <ka...@gmail.com> #432
I've even seen these issues on my Moto X Pure XT1575 on certain ROMs (mostly back on stock) at times. Its been pretty good on the current ROM lately, though accuracy is often poor in situations when it shouldn't, like >+/-30-100m with clear wide view of the sky when my OPO would be reading +/-3-10m.
I did test an XT1607 that was having this issue on an unofficial build Nougat (CM14.1) and saw no effect on the issue.
ad...@gmail.com <ad...@gmail.com> #433
ad...@gmail.com <ad...@gmail.com> #434
This worked with my J5 and my wife's S3:
If you are on maps or waze and you lose the GPS:
1. Turn off mobile data
2. turn off and then turn on GPS
PS: leave mobile data OFF!
This also worked for me, but its only temporary as i do need traffic updates.
fu...@gmail.com <fu...@gmail.com> #435
fu...@gmail.com <fu...@gmail.com> #436
sa...@gmail.com <sa...@gmail.com> #437
sa...@gmail.com <sa...@gmail.com> #438
ha...@gmail.com <ha...@gmail.com> #439
GPS drops out.
First time I have used a satnav.
Anyway, I seem to have fixed my own GPS issue.
Problem looks to be a combination of hardware and clever software.
The clever software is increasing and reducing power to the hardware.
In an effort to manage power.
Disable all power optimization gizmos and do not power optimize location service and associated apps.
Reboot and test.
Not a Google issue.
Not a google issue.
ms...@gmail.com <ms...@gmail.com> #440
i tried many things named in this thread, nothing seems to work. the only thing i did't tried is the "fastboot erase". i saw many users reporting no phone signal after performing this command, so i don't want to try
ms...@gmail.com <ms...@gmail.com> #441
gu...@gmail.com <gu...@gmail.com> #442
jc...@gmail.com <jc...@gmail.com> #443
pe...@gmail.com <pe...@gmail.com> #444
My fingers are crossed that Google has rectified this in the new OS.
I'll report back if that isn't the case.
ko...@gmail.com <ko...@gmail.com> #445
j....@gmail.com <j....@gmail.com> #446
Yesterday, my samsung s5 mini got an update! I thought that finally this problem would have a solution...
Well, it didn't... the problem continues...
A bug reported more than a year ago, still has no adequate response from google...
ia...@gmail.com <ia...@gmail.com> #447
I've got a Ulephone Power mobile with marsmallow 6.0 , maps doesn't work well, it locks in start position and don't refresh position, it happens using every type of location modes.
Regards
re...@gmail.com <re...@gmail.com> #448
That's it.
After sending back few times, they repair it. I don't know what they did though.
Btw, I dont dare to do my updates on my N5 anymore. It's running Android 5 and that's fine for me.
ni...@gmail.com <ni...@gmail.com> #449
pt...@gmail.com <pt...@gmail.com> #450
sa...@gmail.com <sa...@gmail.com> #451
pt...@gmail.com <pt...@gmail.com> #452
si...@gmail.com <si...@gmail.com> #453
lu...@gmail.com <lu...@gmail.com> #454
The GPS comes on while viewing maps, as I would expect it to (not just in "driving" mode). It turns off when Maps is not in view to save battery (unless navigating) - handy.
Description
Since the upgrade from 5.1.1 to Marshmallow 6.0, the GPS of my N5 won't work anymore.
Google Maps can't localize me and Waze tells me directly that I have to switch on my GPS feature (which is already on).
Few apps of GPS localization can't find any GPS.
It's a shame: my Nexus 5 worked perfectly one week before.
My device: Nexus 5 - 16Go