Waze only : GPS is not working anymore for Oneplus users

[vrobert78]

Same problem op5 / France / Waze 4.42.0.5

No problem with Google Maps or GPS Test.

[nacgar]

Same problem in Spain with 5T (4.42.0.5), i can use GMaps without problems. Before this update i worked perfectly with Waze

[RickGrimesBE]

#metoo
OP6 (5.1.11) no problem in Google Maps, GPS Toolbox shows good reception of satellites

[cizo2000]

Hello, I have OP5 and issue started yesterday for me. If I reinstalled Waze several times and if I didn't login to it, it locked to GPS for 1-2 seconds and then disconnected and crashed. Afterwards even when I logged in or not, GPS was not working. GPS Status shows dozen of satellites and position fixed. Google maps work as well.

[vince1612]

Just to confirm that staff have been notified, we've been told that they were checking the issue. Once we hear something back we'll let you know.

[vince1612]

It would help staff if people with One Plus devices could try to submit their debug logs for analysis.

Follow all the steps here to enable debug mode on your App and submit them:
https://support.google.com/waze/answer/6270063?hl=en

P.S. If sending logs doesn't work, you can still open a ticket and give as much info about your device OS and App versions to staff.

[ascrounch]

Waze and Oneplus 6 are not working , i'm from France.

There's a problem with Oneplus devices...

[ArTsLeOpS]

Same problem with OP5. Waze HQ is already informed. Can you activate debug mode (search on 2##2) and send logs?

[VILLAformer]

logs sent. When deleting the data from waze and installing again, the Spanish voices from Spain do not appear to me. I have a oneplus 5

[itzwolf]

While this is noted for OnePlus 5 owners, my original Google Pixel XL on Android 9 has been having a lot of lost GPS issues the past few days. Basically during a drive GPS is lost then regained after a minute or 3 later and the yellow arrow fast tracks on the route I have traveled to catch up. Once it happens it appears to be a repetitious cycle every few minutes or so.

I am on the production release v4.42.0.5 and submitted logs yesterday roughly 3:20pm EDT when it happened at one point and just submitted logs this morning at 7:32am EDT that should contain the issue yesterday afternoon between 6pm and roughly 6:30pm.