Develop Bugs

[Q] FI25 Com.android.phone has stopped - [RESOLVED]

I'm currently running Re-Calked.E4GT.0.2.1.FI25. For the most part everything is solid, and getting some of the best battery life I've ever gotten out of the phone (24 hrs with ~2hrs screen time no problem if in a good signal area).
The one little problem I'm having is any time I finish a call using my in-car bluetooth device, the screen blacks out for a while then I get a message saying Com.android.phone has stopped.
The device is still connected to bluetooth (music starts streaming again, etc...), but if I try to make another call, the dialer won't enable bluetooth (a lot of weirdness about finding a bluetooth device when you tap the bluetooth button on the dialer UI). A hot-boot puts everything back again the way it should be until my next call. This happens 100% of the time on bluetooth, never on a regular call - speaker or otherwise.
I don't think it's Re-Calked's fault, I've experienced the same problem on the stock ROM (FH25). It was fine on FH13, and I'm fairly certain FI03 was good too, but I got dismal battery performance on these kernels.
Any suggestions? This is a real downer for me ... I'd hate to have to try an older ROM since everything else is effin' fantastic! (BIG thanks tdunham!!)
UPDATE:
If anyone else runs into this problem, flash the FF18 Phone from THIS POST (thanks tdundham)
The problem appears to be related to the phone being in landscape orientation, which is only available during a call when docked in a car dock.
I'm using the Official Samsung Vehicle Mount

Wish I had an answer for this for you but...
I've seen several frustrated posts concerning Bluetooth pairing with vehicles on ICS with no clear workaround/solution. I don't have a vehicle with onboard Bluetooth to troubleshoot the issue. I bet it's a doable fix too if it's just a matter of porting over some older library files or something from FI03. Maybe we can experiment with some file replacements to see if we can get it working.
You listen to music over Bluetooth too? I wonder if the media player is conflicting too somehow. What happens if you don't have streaming music and recieve a call?
Edit: It would help if you could backup and flash back to FI03 to verify if the problem still exists on that version.

tdunham said:
Wish I had an answer for this for you but...
I've seen several frustrated posts concerning Bluetooth pairing with vehicles on ICS with no clear workaround/solution. I don't have a vehicle with onboard Bluetooth to troubleshoot the issue. I bet it's a doable fix too if it's just a matter of porting over some older library files or something from FI03. Maybe we can experiment with some file replacements to see if we can get it working.
You listen to music over Bluetooth too? I wonder if the media player is conflicting too somehow. What happens if you don't have streaming music and recieve a call?
Click to expand...
Click to collapse
Actually it's not a built-in bluetooth. It's a "Belkin Bluetooth Car Hands-Free Kit for Apple iPod, Apple iPhone, BlackBerry,and Android Smartphones, US Version" ... search for that on Amazon ... tried to post a link, but I'm too much of a noob to post links yet, apparently.
I have the phone in a Samsung windshield mount, and the Belkin device ports all audio through the aux-in jack of my car stereo. It also has a built-in microphone so that I can use it for calls.
I have experimented a bit to see if it was a conflicting app, but it still happens even if I'm using nothing else. Worked fine on the older kernels, even with multiple apps running (Car Home Ultra, Waze, and Play Music are typical) went wonky as of FI25. I even tried disconnecting it from the dock and disabling car mode. The only thing that causes it is being connected to bluetooth and ending a call, and then it happens every time. Doesn't matter if I initiate the call or receive it. (Which is useful, because I could easily test by calling 611)
I wish I had another Bluetooth device to test if it was specific to the Belkin ... but that's all I've got.

No problem. I live out of Waze. Glad I found the fix for the full navigation voice cutoff for that (and Google Voice) and included it in the FI25 rom. I'll look into posting a couple of flashable zips for you to experiment with for the Bluetooth library files.

tdunham said:
No problem. I live out of Waze. Glad I found the fix for the full navigation voice cutoff for that (and Google Voice) and included it in the FI25 rom. I'll look into posting a couple of flashable zips for you to experiment with for the Bluetooth library files.
Click to expand...
Click to collapse
Thanks for that ... can't wait to try. Going to flash your new Re-Calked update soon too.
On a tangent regarding Waze ... did you install the latest update? I can't stand the way they use 30% of the screen with that black bar ... even worse when you get close to your destination and that other menu bar pops in above it. 50% of the screen covered with useless info.
I rolled back to the prior version from my Titanium backup.

I only used Waze this morning once after the update but didn't really check it out.
Backup your phone.
Flash this first - FI03.flash.first.zip
Test bluetooth, if it isn't working move on...
Flash this second - FI03.stock.lib.zip
Test bluetooth. Even if it is working, flash this next. FI03.stock.lib.zip

Very cool. I'll give it a shoot tomorrow at lunch if I get a moment.
Sent from my SPH-D710 using xda app-developers app

romgnascher said:
Very cool. I'll give it a shoot tomorrow at lunch if I get a moment.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Yeah, don't forget to backup first.
Sent from my SPH-D710 using xda premium

So, it looks like I was wrong with my initial investigation.
I did flash the first file ... everything connected fine. Placed and disconnected a call no crash. But what I DIDN'T do was put the phone in the car dock.
So, I think the problem isn't bluetooth at all. I think it's some interaction with the car dock. If the phone is connected to the car dock when I disconnect the call ... that's when com.android.phone crashes (I can start the call connected, just need to disconnect before I end the call). I also had a suspicion that Car Home Ultra might have been a factor, but it happens even if Car Home Ultra is not running. I thought I had tested this scenario originally, but I guess I missed that one.
I'll flash back to my nandroid later and reconfirm these results. In the mean time ... any thoughts on what the car dock might be doing to trip up the phone?
UPDATE:
Now that I've narrowed it down to the dock, I found this bug report that appears to be related to my issue (yay, I'm not the only one):
http://code.google.com/p/android/issues/detail?id=34612
Down the end of that thread, it appears that the issue seems to be related to the phone being in portrait mode ... not necesserily the dock, it's just that you can only get portrait mode during a call when docked.

Just curious. Does your dialer rotate when docked so you can make a call?
Anyway, I sent you something in a PM check it out.
Edit: I'm working on one more thing to add to that. Give me a little while.

Cool, I'll look at it afterI get the kids to bed.
Yes, the dialer rotates in the dock. Also, when in a call, the contact's photo is also rotated and moved left.
Sent from my SPH-D710 using xda app-developers app

Ok we're running out of choices I guess. Try this older stock dialer and if that doesn't work, I guess that's it for now.

Thanks for your efforts whatever the outcome!
I'll flash this tomorrow and see how we go.
I just flashed the new Re-Calked update by the way. No problems, good stuff and it's been idling at around 1.6%/hr.

Changing out the phone did the trick!
OP updated with resolution.
Sent from my SPH-D710 using xda app-developers app

Hold your horses there cowboy.
That is a totally unmodified phone.apk. Let me upload a modfied one you can try too. This one is FI03, disabled ascending ringtones, roaming notification fix. Might be something else too but I can't remember.

tdunham said:
Hold your horses there cowboy.
That is a totally unmodified phone.apk. Let me upload a modfied one you can try too. This one is FI03, disabled ascending ringtones, roaming notification fix. Might be something else too but I can't remember.
Click to expand...
Click to collapse
Cool, I'll look at this one too. Have an answer for you by lunch time.

tdunham said:
Hold your horses there cowboy.
That is a totally unmodified phone.apk. Let me upload a modfied one you can try too. This one is FI03, disabled ascending ringtones, roaming notification fix. Might be something else too but I can't remember.
Click to expand...
Click to collapse
So I tried that phone. Crashes on disconnect just like the others. Back to the FF18 phone and it works like it should.

romgnascher said:
So I tried that phone. Crashes on disconnect just like the others. Back to the FF18 phone and it works like it should.
Click to expand...
Click to collapse
That's fine, as long as we got it working for you.

[Q] Audio cutting in and out on my unit how to fix.

Yesterday the audio just stopped working on my unit. It is almost like it is muted or something. I checked it and it seems like everything is ok. Then this morning I was driving and it suddenly came back on. Audio will not cut out when the car is running, but only when I turn the car off for whatever reason(refuel, garage, etc) and then the audio will eventually come back.
I tried flashing the latest malaySK rom and MCU and that did not help. Is this a hardware issue or something? It's behaving like it is muted and when it suddenly comes back it's as if I hit the unmute button or something. Any ideas would be appreciated, I'm about to drive cross country with this.

kruuth said:
Yesterday the audio just stopped working on my unit. It is almost like it is muted or something. I checked it and it seems like everything is ok. Then this morning I was driving and it suddenly came back on. Audio will not cut out when the car is running, but only when I turn the car off for whatever reason(refuel, garage, etc) and then the audio will eventually come back.
I tried flashing the latest malaySK rom and MCU and that did not help. Is this a hardware issue or something? It's behaving like it is muted and when it suddenly comes back it's as if I hit the unmute button or something. Any ideas would be appreciated, I'm about to drive cross country with this.
Click to expand...
Click to collapse
I've seen the same on one of my four units. My interim solution has been to turn power off i.e turn engine off for 35 seconds.
After that the sound comes back. I suspect it has something to do with the delay of 30 seconds implemented in the FW.
If you look in Malaysk's thread he claims its an error in the recent fw.

Any idea as to the last version of the ROM that didn't have this issue?

kruuth said:
Any idea as to the last version of the ROM that didn't have this issue?
Click to expand...
Click to collapse
I don't know. This has been an ongoing case for some time. As I wrote above I think it has to do with the
software delays implemented some time ago. I've turned off Headunitservice and also removed the option
in Xposed concerning MCU. It looks like that solved the problem. Knock on wood

I see. What is this delay issue involving? I really only use the headunit service to change songs in Poweramp I think. The other features are nice but kind of superfluous for my installation.

kruuth said:
I see. What is this delay issue involving? I really only use the headunit service to change songs in Poweramp I think. The other features are nice but kind of superfluous for my installation.
Click to expand...
Click to collapse
The MCU thing is to keep the HU running while you start the engine. That's the SW mod. There's also a hardware mod
implementing a capacitor and a diode doing the same thing. I can wait for the cold boot and have sound, rather than
the other way around.

I understand. How do you disable it? Wouldn't a reboot of the unit fix this issue? I was thinking of just going into xposed and forcing a reboot from in there.

kruuth said:
I understand. How do you disable it? Wouldn't a reboot of the unit fix this issue? I was thinking of just going into xposed and forcing a reboot from in there.
Click to expand...
Click to collapse
Xposed installer/modules/XposedMcu-remove thick. Reboot.

Thanks. What else does this affect?

kruuth said:
Thanks. What else does this affect?
Click to expand...
Click to collapse
AFAIK, only the above.

I've tried downgrading, changing the MCU, etc. No suck luck. The audio seems to just kick on or off.

GPS Keeps Losing Signal

I'm wondering if others are having this issue? With various apps (Pokemon Go, Google Maps) I keep losing GPS signal. Seems to find it no problem when first starting it but will soon start losing it. Pokemon Go reconnects pretty fast but Google Maps is much slower. I'm wondering if this is a hardware or software issue. I was on stock for a while and last week switched to OOS Lite (which is still stock based) and I'm I'm still having this issue. Makes using the phone for navigation about impossible. Hoping someone can help me.

I don't want to lose camera quality but I'm thinking about trying a new OOS based ROM and see if that fixes the issue.

What it shows on Google Maps.

Google turned up several threads about this problem. OnePlus has stated it may be hardware related and only impacts some of the OP3. The latest ROM from OP seems to have more problems than earlier ones. It is supposed to get fixed in some future update but no info supplied regarding the where/when.
---------- Post added at 12:28 PM ---------- Previous post was at 12:26 PM ----------
http://forum.xda-developers.com/oneplus-3/help/gps-issues-t3416544/page7
More info in this thread.

Thanks. Well I've been in contact with OnePlus and they want to do the thing where a tech will remotely access my phone and wipe it. I doubt it will help but I'll let them. I'm wondering if it may be a software issue and I'll need a replacement. I'm not looking forward to that process. I've never done it before but heard it is a nightmare. Plus I cannot go without a phone due to work.

Well just flashed latest version of Cyanogen Mod and Still Seem to have the same issue. Seems to be hardware then. Ugh. Oneplus wants to do a remote thing, but soonest appointment is a week away.

Did you resolved the GPS problem with OnePlus Support. Is it hardware or a software problem? I have the same problem with my OnePlus3

I have those GPS problems as well. I opened and replacement RMA. Let's see... maybe my phone is broken. I tried the official OOS, the community build of OOS and cyanogenmod so far and there wasn't a difference in GPS performance. All poor. I guess everybody how has those issues might have a defect in the device

Same issue here, completely stock. Constantly looses gps signal then reconnects...........very annoying.

Any updates here?
I guess my OP3 is not up for taking on runs or bike rides like any normal modern smart phone should be. What good is GPS tracking of your outing when it loses the signal constantly, sometime for as much as several minutes? Absolutely infuriating. Updates please, and thanks in advance.

EmperorImpervious said:
I guess my OP3 is not up for taking on runs or bike rides like any normal modern smart phone should be. What good is GPS tracking of your outing when it loses the signal constantly, sometime for as much as several minutes? Absolutely infuriating. Updates please, and thanks in advance.
Click to expand...
Click to collapse
for me "gps signal lost" only seems to happen if the screen is off while navigating (not sure if removing google maps/whatever gps app from battery optimization has helped)
google maps seems to navigate continuously if the screen is kept on, although accuracy seems worse than prior phones (i.e. unable to tell if you're on the feeder/frontage or highway)

klawrg said:
for me "gps signal lost" only seems to happen if the screen is off while navigating (not sure if removing google maps/whatever gps app from battery optimization has helped)
google maps seems to navigate continuously if the screen is kept on, although accuracy seems worse than prior phones (i.e. unable to tell if you're on the feeder/frontage or highway)
Click to expand...
Click to collapse
I am experiencing better GPS performance by disabling the "Doze Mode" in the Developer Options (OxygenOS 3.2.7 and everything stock).
I hope it will help

filoponz said:
I am experiencing better GPS performance by disabling the "Doze Mode" in the Developer Options (OxygenOS 3.2.7 and everything stock).
I hope it will help
Click to expand...
Click to collapse
What is the doze mode for?

borijess said:
What is the doze mode for?
Click to expand...
Click to collapse
Doze keeps apps from draining battery while not in use.
However I did not notice a big difference.

filoponz said:
Doze keeps apps from draining battery while not in use.
However I did not notice a big difference.
Click to expand...
Click to collapse
Oh OK. So its best to have it on?

borijess said:
Oh OK. So its best to have it on?
Click to expand...
Click to collapse
Yes, but as I said I did not notice an excessive battery consumption: it maybe depends on the apps you have installed in your phone.
I suggest you try. Let us know if your GPS works better than before.

I have the same issue. Stock Rom 3.2.7. Any news from the support?

Same issue. I thought it was because I had too many apps, so I wiped. The GPS keeps losing its signal.
Enviado desde mi ONEPLUS A3000 mediante Tapatalk

Short of a rma, have you all tried the app 'gps locker'? It holds lock through a persistent notification. It worked well on my note 3 with gps issues.

Quick work around is to download gps test app from play store,
Run it, wait till you get lock,
Once you get lock, close the app but dont kill it,
Now open your other app that need constant gps (maps, waze, pokemon, uber, you name it) and use it,
GPS will run well this way,
You wont lose GPS signal, except when you are under some kind of roof

Sound cutting out

Has anyone found a fix for the sound cutting out after a few seconds of a video or game? I have tried the soubdabout app, Turing the USB option off, disable Power save.. Still happening..
Sent from my SAMSUNG-SM-G891A using Tapatalk

I have the same issue sometimes, I've read around the web and it seems to be a mix of software and hardware related, I read a guy suggest removing and putting back the case (in case you have one) and I did that and the sound came back, haven't had the issue again.
Dakotahorse said:
Has anyone found a fix for the sound cutting out after a few seconds of a video or game? I have tried the soubdabout app, Turing the USB option off, disable Power save.. Still happening..
Sent from my SAMSUNG-SM-G891A using Tapatalk
Click to expand...
Click to collapse

hudtwalcker said:
I have the same issue sometimes, I've read around the web and it seems to be a mix of software and hardware related, I read a guy suggest removing and putting back the case (in case you have one) and I did that and the sound came back, haven't had the issue again.
Click to expand...
Click to collapse
Hmm, I keep mine out of a case,.. Yeah I'm not sure what it is, it's a 50/50 between some say software and some say hardware. I would asume that software would of been fixed by now, either Samsung or 3rd party
Sent from my SAMSUNG-SM-G891A using Tapatalk

So I found a solution for the issue in my case, it does seem to be software but it's really weird cause the issue continues in any firmware, it started when I was on 6.0.1 PI2, then I flashed Nougat and had the same problem (I hated it and battery drain was killing me) I went back to 6.0 and changed to the PK2 version and the issue continued, it was really weird cause it would cut out in audio messages, games but not music, I also tried every single suggestion on every forum and post I could find EXCEPT the Soundabout app, today I gave up, installed soundabout, selected media to speakers and bam, problem solved, I still need further testing, but it seems ok for now, keep in mind that I also have "prevent USB audio routing" on and "Easy Mute" off.
Dakotahorse said:
Hmm, I keep mine out of a case,.. Yeah I'm not sure what it is, it's a 50/50 between some say software and some say hardware. I would asume that software would of been fixed by now, either Samsung or 3rd party
Sent from my SAMSUNG-SM-G891A using Tapatalk
Click to expand...
Click to collapse

Im trying the soundabout app now, I orginally had it set to automatic and was still having the issue, now I set it to speaker and so far so good.

as this worked for me but idk about others... I was told to remove all paired bluetooth devices (on/off doesnt matter) then go to settings>connections>more connection settings>nearby device scanning then turn off... worked for me... (sorry for zombifying an old post but as this is still current with mine and many devices i decided to help)

samsung galaxy s7
Hi. I drop my boyfriend phone today and the volume cut it off for a while. It's that because I drop it off? Or because of the headphones that I had it in...because after I took the headphones off its works but after starts and go again? Pleasee helppp....

Andra1997 said:
Hi. I drop my boyfriend phone today and the volume cut it off for a while. It's that because I drop it off? Or because of the headphones that I had it in...because after I took the headphones off its works but after starts and go again? Pleasee helppp....
Click to expand...
Click to collapse
Is anything still wrong? Or does the sound work both with and without headphones?

Hi. I dropped my phone and have the same problem now. Did you get any useful help?

GPS issues using Maps

I don't know if it's just my unit or there is an inherent problem with the pixel XL 2. It cannot seem to register my location accurately even with high accuracy on. Directions has been useless for me over the last few days. Anybody else have this issue?
If it does not improve rapidly, I'm going to start an RMA...
Sent from my Pixel 2 XL using XDA-Developers Legacy app

i started a RMA this morning after going thru support trying all their troubleshooting steps with no luck.. GPS can lock at times.. but seems to not hold too well..
the reliability of it is very reminiscent of the early batch of Nexus 5 phones.. which were also LG built.... goodness gracious.. history is repeating itself again..

I'm guessing it's your phones. Mine holds lock perfectly. Used navigation for almost 8 hours over the weekend. Never lost connection once.

jaben2 said:
I'm guessing it's your phones. Mine holds lock perfectly. Used navigation for almost 8 hours over the weekend. Never lost connection once.
Click to expand...
Click to collapse
Actually, it just started working correctly when I got home to MN from NY, so I happy now...

Op. Have you tried 8.1 dev?

The question is what settings do you have on? i usually have wifi and gps on since wifi can help with locking into your location at times.
Have you tried making sure wifi is on as well?

I have this exact same issue.
I find if you toggle the GPS off and back on, it immediately starts working again, only to stop working in another 1-2 navigation sessions.
---------- Post added at 04:31 PM ---------- Previous post was at 04:30 PM ----------
aaronc_98 said:
I don't know if it's just my unit or there is an inherent problem with the pixel XL 2. It cannot seem to register my location accurately even with high accuracy on. Directions has been useless for me over the last few days. Anybody else have this issue?
If it does not improve rapidly, I'm going to start an RMA...
Sent from my Pixel 2 XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
Have you done an RMA yet, and does your replacement phone still have the same issue??

WebMatt01 said:
I have this exact same issue.
I find if you toggle the GPS off and back on, it immediately starts working again, only to stop working in another 1-2 navigation sessions.
---------- Post added at 04:31 PM ---------- Previous post was at 04:30 PM ----------
Have you done an RMA yet, and does your replacement phone still have the same issue??
Click to expand...
Click to collapse
I've noticed the same thing - toggling location services off and on fixes the issue when it happens, which makes me suspect it's a software issue.
I use my GPS A LOT between navigation and playing pokemon go, and the issue has only happened 3 times over the last 1 1/2 weeks. I imagine a lot of people wouldn't notice the issue if they don't use GPS too often, as for the most part, it works perfectly.

nyijedi said:
I've noticed the same thing - toggling location services off and on fixes the issue when it happens, which makes me suspect it's a software issue.
I use my GPS A LOT between navigation and playing pokemon go, and the issue has only happened 3 times over the last 1 1/2 weeks. I imagine a lot of people wouldn't notice the issue if they don't use GPS too often, as for the most part, it works perfectly.
Click to expand...
Click to collapse
Yeah. I do a lot of on demand delivery, so I'm using my GPS and navigation ALL day long.

Somewhat off-topic, but for those of you who are using GPS and maps all day long, is there any way to get the screen to turn off between turns? I am finding that my battery is draining a lot faster than usual compared to previous phones.
I wouldn't make such a big deal about it, if it didn't take 4 hours for this thing to charge...

WebMatt01 said:
Yeah. I do a lot of on demand delivery, so I'm using my GPS and navigation ALL day long.
Click to expand...
Click to collapse
Same here. On demand delivery and moonlight as a driver.
My Pixel 1 didn't have this issue.
I noticed that GPS would not work 3/10 times when I use Google maps. Resetting the map app wouldn't work at all.
I'll try toggling "location" on and off the next time I noticed GPS not working.
Aside: I experienced screen burn in with the Pixel 1. Some I use maps often, the navigation bar would always be up. Google should hide the navigation bar. I guess I'll try immersive mode to lessen the chance of screen burn in.
---------- Post added at 11:56 PM ---------- Previous post was at 11:53 PM ----------
WebMatt01 said:
Yeah. I do a lot of on demand delivery, so I'm using my GPS and navigation ALL day long.
Click to expand...
Click to collapse
Cowbell_Guy said:
Somewhat off-topic, but for those of you who are using GPS and maps all day long, is there any way to get the screen to turn off between turns? I am finding that my battery is draining a lot faster than usual compared to previous phones.
I wouldn't make such a big deal about it, if it didn't take 4 hours for this thing to charge...
Click to expand...
Click to collapse
I remember there used to be a setting that maps would put the phone asleep and then the screen on when a your approaching a turn.
I guess they removed that feature. I don't see it anymore.

Just had these issues again. My GPS keeps showing me that i'm facing in the wrong direction, often times by a 90 or 180 degree angle. So if it tells me to turn right on the map, how do i know where to turn if it shows i'm facing the wrong direction? Restarted, no difference.

harsh2193 said:
Just had these issues again. My GPS keeps showing me that i'm facing in the wrong direction, often times by a 90 or 180 degree angle. So if it tells me to turn right on the map, how do i know where to turn if it shows i'm facing the wrong direction? Restarted, no difference.
Click to expand...
Click to collapse
Did you try recalibrating the compass? I've had that issue on a Samsung before which was fixed with compass recalibration

Doug8796 said:
Op. Have you tried 8.1 dev?
Click to expand...
Click to collapse
I haven't tried the 8.1 Dev update yet, but I just got the November 2017 update with some fixes and screen setting changes and it did NOT fix this issue for me.

I second your compass need calibration. Has maps asked you to calibrate? My GPS was off today on maps, it asked me to calibrate and that fixed the issue.

same issues
I'm having the same problems with my Pixel 2 XL, and it is shown clearly with the GPS Status app - at times my GPS signal will toggle on and off randomly, with no reliability whatsoever. Other times it simply refuses to initialize. I haven't tried turning location services on and off yet, but I did get a warranty replacement phone from Verizon, and it had the same issue. I opted to return the replacement phone, since there was no fix.
I've got video of the failure, but I can't seem to post it as I'm too new to the forum.

harsh2193 said:
Just had these issues again. My GPS keeps showing me that i'm facing in the wrong direction, often times by a 90 or 180 degree angle. So if it tells me to turn right on the map, how do i know where to turn if it shows i'm facing the wrong direction? Restarted, no difference.
Click to expand...
Click to collapse
I had this yesterday, it was an exact 180 degrees off (opposite direction). Recalibration couldn't fix it.

Did anyone do an RMA yet? Did it resolve the issue.
I thought the November update would fix it, but it hasn't.
I've uninstalled and reinstalled maps and I still have the issue. I would see my location being tracked on Google maps as I'm driving but Google maps wouldn't provide me turn by turn directions. It'll just be a dot instead of the arrow.
The only way to get it to work is by toggling location off and on.

Pixel 2 XL GPS problem - possible fix.
Hi
I've been having the same problem, my phone would not find the GPS satellites. I found that if I set location services to device only the GPS was not picking up any satellites. I turned location services off, restarted the phone and turned location service on, opened the GPS satellite app I have and the satellites appeared. This might be worth a try. I can't report that this solves the problem long term but it's been working for a few minutes which is better than before!!

Pixel 2 GPS problem - possible fix
Update on post yesterday.
GPS is still working without any obvious issues.
?