Develop Bugs

[Q] Note 2 No service

Hello everyone.
I have been using my phone for almost 3 years with no issues but recently found out it has the insane chip. After that my phone started going mental with all the reboots and freezes but the worst of all is that suddenly it changed into ''modified'' even though I never rooted. And at the same time with that I got a ''no service''.
I can not call or message or use 4g, only wifi works.
I tried manually entering APN, didnt work
I tried bunch of video instructions on youtube, didnt work
I have no experience in things like rooting or flashing or roms but I went ahead and tried rooting with some automatic program called
Kingoroot. Then I used bunch of different programs like gs2 repair and busybox to see if its about my imei being blocked or something.
Still didnt work.
Weird thing is, my sim card works on other phones but other sim cards still dont work on my phone so I'm guessing its completely on the phone.
Are there any solutions to this because I dont want to buy a new phone while this one is still working? Also since I have no idea about what roms are and all, would be awesome if you told it more detailed.
Thanks in advance

Bump
Just rolled back to no root but weird thing is, even after unrooting it still shows modified.
Some of the solutions I've heard require me to do some software update and delete cache but cant because of the modified state.
Anyway I'm really looking for some solutions

Anyone else have camera issues?

I received my Pixel XL 128GB on this past Wednesday and I have been having constant crashing issues with my Camera. I first thought it may have been the app itself so I tried using various camera apps from the playstore which didn't seem to help.
I tried to delete the app data as well as the cache
deleted any app that may use the camera such as facebook and instagram
reset the phone back to factory twice, trying both the stock and stock updated camera app
I even tried various ROMS like PureNexus and AOPK with no fix in sight.
The error message I receieve is "Camera Error - Can't connect to the camera" prior to that error message the screen is black utilizing the forward facing and rear camera.
I called up support and of course got an idiot Google Customer support rep who could barely speak english telling me that it may be hardware related and that I would it would needed to be replaced.
Is there any other options at this point short of sending my phone back and having them send me a replacement? They are telling me they want to do an authorization hold of another $900 for them to ship me a replacement phone first which is absolutely laughable.

ohms139 said:
I received my Pixel XL 128GB on this past Wednesday and I have been having constant crashing issues with my Camera. I first thought it may have been the app itself so I tried using various camera apps from the playstore which didn't seem to help.
I tried to delete the app data as well as the cache
deleted any app that may use the camera such as facebook and instagram
reset the phone back to factory twice, trying both the stock and stock updated camera app
I even tried various ROMS like PureNexus and AOPK with no fix in sight.
The error message I receieve is "Camera Error - Can't connect to the camera" prior to that error message the screen is black utilizing the forward facing and rear camera.
I called up support and of course got an idiot Google Customer support rep who could barely speak english telling me that it may be hardware related and that I would it would needed to be replaced.
Is there any other options at this point short of sending my phone back and having them send me a replacement? They are telling me they want to do an authorization hold of another $900 for them to ship me a replacement phone first which is absolutely laughable.
Click to expand...
Click to collapse
never experienced anything like that. I think a replacement is probably your best option given that you're already done a factory reset. The one remaining option I might suggest is flashing a full factory image downloaded from Google.
IMO, its not all that "laughable" that google would ask to put a authorization hold on your account. Its only a pending charge and is never actually processed unless you don't return the old phone.

mlin said:
never experienced anything like that. I think a replacement is probably your best option given that you're already done a factory reset. The one remaining option I might suggest is flashing a full factory image downloaded from Google.
IMO, its not all that "laughable" that google would ask to put a authorization hold on your account. Its only a pending charge and is never actually processed unless you don't return the old phone.
Click to expand...
Click to collapse
I have actually done a full factory flash from Google.
Well when I had financing from Verizon or T-Mobile and I had an issue with the phone they sent a replacement first and I had a time frame in which to send the phone back or I would get charged, they never held funds first.

Financing devices works a little different and each company has their own policies. I haven't had an RMA with Google ever, but with Moto (after it was bought by Lenovo) they required a hold and there have been a few other places that if they sent a device to me before I sent one to them they would put a hold on my credit card. I always considered it a standard procedure. As for the Pixel's camera, while there have been some issues mentioned here and other places about camera issues yours seems unique, almost like the camera component was DOA. I would RMA if it was my device.
Sent from my BTV-W09 using Tapatalk

I found this on Google's forum: Camera issue seems to be solved with beta 2 update, can anyone else confirm?
Jason70
5 days
Jason70
yep, 7.1.2 seems to have worked... fingers crossed.... not got camera to fail and it always failed at my workplace due to low signal, but this morning its running great!
ThomasBHV
5 days
ThomasBHV
7.1.2 (NPG471) Yes currently it work well

The above post has more to do with phones in low signal areas that have the camera freeze up usually with purple lines across some of the photo. That issue has been on going mostly with European variants since release. This does not give the unable to connect error.
Sent from my BTV-W09 using Tapatalk

Thanks for all the responses but I guess Support was correct when they said it was the hardware. My new phone works without any issues.

Note 4 Verizon no 4g and now lost 3g - in a strong 4g / 3g area

SOLVED! - see post #7
This SM-N910V is rooted and had 3g but apparently I lost that when mucking around with things trying to get 4g. I've got other phones like a Galaxy S5 and Galaxy Note 5 both Verizon models that get 4g or 3g fine in this same location.
First odd thing I noticed on the Note 4 was a setting that popped up seemingly by itself while in 'More Networks' and 'Mobile Networks' that showed VZWInternet with a circle by that which was not yet checked so I tapped that and it turned green in the circle. I have never been able to see that option again. I don't think this caused the problem though. I've looked at apns-conf.xml in the /system/etc folder and can't see a problem there. I also tried replacing that with another one that is supposed to fix LTE mode. No luck so I put back the original. I wiped cache and reflashed a backup with TWRP which had been working on 3G but that didn't help - no 3g even. I did not wipe Dalvik/ART cache. I had been messing around in the 'Service Mode' menu with a bunch of different settings in an attempt to get 4g working but I'm fairly certain I got everything set back the way it was before I started. I noticed that one setting I had left different in the Service menu did not change back after flashing a restore with TWRP (full restore - all boxes checked). The one setting I left changed was the under the 'AS' protocol menu where I changed the Release version control to "LTE 3GPP REL 9" from LTE 3GPP REL 10". I know enough to be dangerous
Open to any suggestions - am wondering at the moment if I should have wiped the Dalvik/ART cache before the whole TWRP restore? At this point I'd be happy just to get 3g working again.

I also tried Dr. Ketan's LTE Enable. That didn't fix anything. Although I see MNC and MCC numbers in the apns-conf.xml file when I look at the SIM with a SIM info App I just see blanks in those spots on the SIM. Not sure if that's relevant - just giving as much info as I can here.

Did another restore with TWRP after wiping Dalvik/ART cache but that didn't fix it either. Strong cell signal but no 3G or 4G.

More info - I put the SIM card in another phone and it sees 3G at least.

It seems the "lost 3g or 4g" problem is very common and it seems I've looked through dozens of message threads here but I'm not finding any solutions. I'm looking at flashing the 'ltefix.zip' from this thread but it seemed to be for a custom ROM and I've just got the stock - more or less - 5.1.1.

Hmmm.... Been at this all day reading here, searching, trying everything but still no Mobile Data. Is this as elusive as rooting a Verizon Note 5? LOL - it was working at least on 3G. I'll take hints or even wild guesses at this point.

Okay - it finally flashed on me to do a restore of my EFS. Oddly I had done a full restore with TWRP which include EFS but that didn't fix the problem. That TWRP backup was done the same day I did an EFS backup using Dr. Ketan's IMEI tool for the Note 4. When I used the IMEI tool to restore the EFS backup I then had the 3G come back on. This is a 4G SIM so I still don't know why I'm not getting 4G but at least I got 3G back. I did have a hiccup using this IMEI tool which initially caused the phone to repeatedly shutdown after a minute or so and could not be restarted without pulling the battery. I believe it had to do with the 'Restore' button needing to be held down a certain amount of time instead of just a tap. I probably held, released too soon then held longer which I suspect caused a partial or damaged EFS restore. Be careful in how you use this tool or you may end up in that situation. I had to work very fast after a bootup to get it properly restored. After that it was stable again and had 3G.
Now if only I could figure out what it takes to get 4G.

..

I wasn't getting 4G for the longest time, checked the PRL in settings on my GFs phone and noticed my PRL ver was like 50 thousand something while hers was 15518. Got a new Sim card and all my issues went away, PSA do not use *228 programming...EVER.

..

..

acslam said:
Update/more info - I've continued to try and figure this out to no avail, although I got fed up with stock unrooted 5.1 and am now running modestrom v9 with a CQI2 base. And all of that install went fine, except for 4g of course.
I think this is worth mentioning as it might have something to do with the situation:
Way back in the beginning, I had gone through the entire unlock/root process, and everything actually worked fine the first time. This was right about the time the unlock became available, I bought the phone based specifically on that being possible, and got a brand new one at that time. Well, it was awesome for about 2 weeks, fully functional 4g and everything.
I had a very particular goal - I wanted this phone totally unlocked, but I was also very interested in the advanced/wifi calling that was supposedly coming out at that time - I was planning to move to a place with no vzw service and would be reliant on wifi for calls at home. Verizon wasn't clear about the fact that the wifi calling feature wasn't coming until MM, and this was before MM was released, so I was running a completely functional, 5.1.1 rom. I believe it was jasmine. So, under the impression that "advanced calling" would have given me wifi calling, I tried to enable it.
I cant recall if it was immediately, or a few hours after, but this is when the phone lost 4g for the first time. I immediately tried to deactivate the advanced calling feature on my line, but it didn't help. And nothing I could do would bring back 4g. I tried everything possible, and ultimately gave up and threw the phone in a drawer and went back to my note 3.
Fast forward several months, and my note 3 began to have issues with call audio, forcing me to use the 3g-only note 4 in order to actually handle day to day business. Again, I went through the processes of trying to fix 4g, with no success. Now by this time, MM had been released, I believe PD1 was the current firmware. I figured at this point it was time to just odin back to 5.1.1 and start everything over.
So I odin flashed the phone, and it booted into 5.1.1......with no 4g. Again I went through all the things I found here, no improvement. Finally, one day when the phone was bugging me about an OTA, I figured "what can it hurt at this point, its nearly useless without 4g anyhow."
And low and behold, the OTA update from verizon booted up and immediately jumped to 4g.
Now I felt I had a chance, a method that I'd finally proven could fix the problem. I left the phone in that state for a couple weeks, just to prove that it was holding. No problems during this time.
But I got sick of no root, and so I figured it was time to try and go through the steps again. And again, I lost the 4g connection. No big deal, just odin back to 5.1.1 and let it OTA like last time......
Except this time it didn't work. So I odin flashed back to 5.1 again, and let it try to OTA, again. I let the phone continually try to OTA all the way up to current, and flashed back to 5.1 at least 3 times to repeat the process in hopes it might fix something. No change at all. At this point I actually began to try and see if possibly Kies could help me here - maybe there was something related to the phones EFS? Which I don't understand very well btw - it was only through reading this thread that I began to research EFS and its significance. I also attempted to use some of the checkboxes in odin - the ones to erase all NAND and to clear EFS and rebuild it. Neither option made any difference. So I figured next logical step was to start playing around in service mode, which would require unlocking/rooting again......
And thats how I landed here. About an hour ago I got sick of the stock 5.1.1 and went through the whole root/unlock process and I'm currently running modestrom on CQI2 or whatever was just most recently posted. Every other part of the phone seems normal, but still no 4g. I can actually see the radio making an attempt to connect in the service mode - but I don't understand service mode menus well enough to interpret where the actual problem is. Upon boot the phone tries about 3 or 4 times to get an lte signal, during this time there is simply bars of signal, NO data indicator of any kind. Eventually, it gets frustrated and gives up, connecting to 3g and staying there. I realize now that when 3g drops, which is roughly every 10 minutes or so, its actually the phone attempting to establish LTE again. But still, I cannot make any sense of this.
Apologies for the giant post - I'm trying to put anything that could possibly be relevant info into one place here.
So........ anyone got any suggestions?
Click to expand...
Click to collapse
PM sent. Just to share a little of that here I think the first thing I would do is tell VZ you suspect your SIM card is bad and have them put in another one. Tell them it fell out when changing a battery, the dog ate it and by the time it came out you suspect it wasn't quite right anymore - LOL. I do think SIM's flake out sometimes and I know a bad one can prevent 4G from working. If you ever had an EFS backup from anything try restoring ONLY the EFS (if you use TWRP). No guarantees that will fix it but my best guesses at this point. Good luck.

..

I supect Verizon's doing this ...
acslam said:
I got a used stock note 4 to try and compare and see what I could be missing here....
Tried new sim card at least twice, unfortunately no dice, and the same card pops right into the spare note 4 and it wakes up on 4g just fine.......
EFS is something I probably should have been quick enough to dig in deeper on before this, as I don't have any backup of it....... however, I'm not seeing any other symptoms, I can see my imei fine, and every other function works. Is it possible that corrupted EFS can cause the loss of just one type of connection like that?
For giggles I tried a friends att sim, and no lte on that either.
Playing with the app LTE discovery, I can tell that the phone sees 4 different LTE towers just fine, showing db numbers exactly in line with the stock note 4 sitting right next to it, theres just something there under the surface thats stopping them from hooking up...... it stops trying after a couple minutes, rejects them all and connects to 3g.
I'm convinced its some kind of software thing, but I can't tell exactly where the failure is happening.....
I also odin flashed it back to stock bpa1, and still no dice. Is there a means to make an EFS backup without root? I want to see what happens if I try unlocking the other note 4 as well, but this time I want to have the backups......
Click to expand...
Click to collapse
I've been running on Emotion 7.1.1 for months with NO issues (well, some minor stuff, you know....)
Suddenly, two weeks ago I got a notice from Google that I had to sign in on my phone. Verrrryyy odd. At first I suspected some hack attempt, but my Account checked out fine. Having changed my password recently, I had to wait until I got home to login.
After I logged in, all ~appeared~ to be OK. Then I opened my Calendar. B L A N K. All ten years of appointments gone. I freaked out. I have two calendars, one for personal stuff, birthdays and the like, and another with my business appointments, INCLUDING FINANCIAL STATUS of the account. Gone.
Went online on my PC, signed into Gmail and switched to my calendar. Empty. Looked in Trash. Nothing. Vanished. Nada. Niet. There's a long story here about recovery efforts, troubleshooting, Googling, etc, suffice to say that TWO separate, redundant, backups had quietly failed, without the notifications they were supposed to send. I did manage to get from the first week in April back 10 years, but lost the whole summer. Thank YOU-KNOW-WHO that I'm good friends with all my clients.
Fast forward to last week. Suddenly I get 3G only from my Verizon account. Like you, I spent days on the boards, downloading ROMS, wiping, re-wiping, trying everything short of smoke signals to get it back. No joy. I did NOT go back to stock, I must thank you greatly, as that was my next road. Now i see it's a dead end. I will NOT give up my Nougat root just to get 4G.
Perhaps this is a bit conspiracy theory sounding, but I've become convinced that Verizon is playing some game, perhaps to force us to upgrade to a new phone. I learned long ago that corporations have no soul, and will do anything they like to increase profits. They exist for two reasons; to make money for their officers and to make money for their stockholders. Any other semblance of a "Product" or "Service" exist ONLY and SOLELY for that reason. Anyone who is a Yahoo or AOL member knows the level of intrusive ads and attempts to trick people into putting spyware in their machines under the guise of "protection" or "cleanup" programs has jumped to a new level of absurdity since Verizon sucked them up. "Oath" indeed. It's what is coming out of existing customer's mouths! M O N E Y H U N G R Y.
When I chatted at length with a Verizon Tech, she made it clear that she knew the answer was to upgrade to the latest stock (I never admitted to rooting, but she knew, we spoke "between the lines" a lot). She sent me a SIM card, but it., of course, didn't fix the problem, in fact it would not even initialize properly! I had to go back to the original SIM.
Now that we've found a way (after YEARS of trying) around their stupid block on rooting, they change the game. What person who is so into their phone as to root it, will put up with 3G? This is something Verizon is playing at, Sprint too from what I gather.
My only consolation is that I've got so many WiFi's nearly everywhere I go, and when I'm not near one, my Wife's Note 4 (not rooted, on latest update) works fine. I'm glad I decided not to root hers too.
Frankly, this really ticks me off. I have better things to do than spend days copying files, flashing and reloading data. Verizon knows that, and let me tell you, it won't be THEM who sees my money when I finally do upgrade.
Thanks again for saving me from the Stock route, you saved me hours of grief.
Peace out!
PuterPro

I have run into 4g issues with this as well and almost came to conclusion is a modem issue. I want to say but can not confirm that modems that are flashed are relative to bootloader on the device. Just something I've been pondering on as I had a unlocked bootloader device and flashed for wife to use with no root and recently unlocked again.
Sent from my SM-N910V using Tapatalk

Help! Verizon Note 4 random network drop...

I apologize in advance for the long read.
I recently activated Verizon service on a Note 4 that has been sitting unused since the Note 8 came out. The Note 4 is in perfect physical condition, with no scratches on the screen or body, and has been in a protective case since new. I did replace the battery in it prior to activation, as I expect for the life to have been deteriorated.
I did a factory reset and inserted my Verizon SIM card, and it worked perfectly. I installed my everyday apps and a few games on the phone, and I used it without any issue for about a week. During that time, it did install a couple of OTA updates, but I expected that since it had been "off service" for a few years.
After that first week, I put the SIM card back in my NOTE 8 for a couple of days, after which I went back to the Note 4. Initially, 4G data and cell service worked, but within the same day I started having service drops. If I was on the phone and a call dropped, it would show an error message saying "No SIM / SIM Error".
Her is what I have attempted so far:
First, I replaced the SIM with a new one. There was difference in the frequency of the random service drop.
When that did nothing, I assumed that one of the OTA updates from the prior week had done something to modem / radio. The phone was on 6.0.1 at that time. I unlocked the bootloader and installed TWRP, and first tried downgrading to stock 5.1.1, then to a "modified 5.1.1, then to CM 13, and now Lineage 15 (frequently factory reset / cache wipe. There has not been an improvement (or reduction) to the random service drop.
Yesterday, I happened to be on My Verizon online, and I had a message showing that Verizon no long had the information on my phone (IMEI), and requesting that I open a Chat Window to update my info. At this point, the Note 4 is still running the Lineage 15.1. The Verizon team member asked me for the IMEI, and when I looked under the settings, it said "None" under IMEI. In a quick search, I found a forum on Lineage 15.1 that said turning of the screen lock and rebooting the phone will reload the SIM and IMEI info. That worked, and I was able to view the IMEI and verify connection. I explained my issue with the Verizon support, and she said everything appeared to be good on her end. Over the course of 15 minutes, we tested my connection and it worked. About 30 minutes after that, it dropped service again.
Finally, here is where it is at now:
I start with no service. If I do nothing but restart the phone, it will show LTE service for 2 or 3 seconds, then nothing. If I remove and reinstall the SIM, I will get the same 2 or 3 seconds, then nothing. If I turn Airplane Mode on and off, that does not reconnect the service. If I change the lock screen security to "None" and restart the phone, there is no service, but if I set Screen Lock to "Swipe" and restart the phone, I will have LTE service for at least 30 - 45 minutes before it drops, sometimes a few hours. When it does drop, it does not come back on it's own. The only way I have found to get it back it to "Screen Lock - None, reboot, Screen Lock - swipe, reboot".
Will replacing the modem fix the problem? Is there a specific modem that I need to match up to the ROM? Thanks!

bife2003 said:
I apologize in advance for the long read.
I recently activated Verizon service on a Note 4 that has been sitting unused since the Note 8 came out. The Note 4 is in perfect physical condition, with no scratches on the screen or body, and has been in a protective case since new. I did replace the battery in it prior to activation, as I expect for the life to have been deteriorated.
I did a factory reset and inserted my Verizon SIM card, and it worked perfectly. I installed my everyday apps and a few games on the phone, and I used it without any issue for about a week. During that time, it did install a couple of OTA updates, but I expected that since it had been "off service" for a few years.
After that first week, I put the SIM card back in my NOTE 8 for a couple of days, after which I went back to the Note 4. Initially, 4G data and cell service worked, but within the same day I started having service drops. If I was on the phone and a call dropped, it would show an error message saying "No SIM / SIM Error".
Her is what I have attempted so far:
First, I replaced the SIM with a new one. There was difference in the frequency of the random service drop.
When that did nothing, I assumed that one of the OTA updates from the prior week had done something to modem / radio. The phone was on 6.0.1 at that time. I unlocked the bootloader and installed TWRP, and first tried downgrading to stock 5.1.1, then to a "modified 5.1.1, then to CM 13, and now Lineage 15 (frequently factory reset / cache wipe. There has not been an improvement (or reduction) to the random service drop.
Yesterday, I happened to be on My Verizon online, and I had a message showing that Verizon no long had the information on my phone (IMEI), and requesting that I open a Chat Window to update my info. At this point, the Note 4 is still running the Lineage 15.1. The Verizon team member asked me for the IMEI, and when I looked under the settings, it said "None" under IMEI. In a quick search, I found a forum on Lineage 15.1 that said turning of the screen lock and rebooting the phone will reload the SIM and IMEI info. That worked, and I was able to view the IMEI and verify connection. I explained my issue with the Verizon support, and she said everything appeared to be good on her end. Over the course of 15 minutes, we tested my connection and it worked. About 30 minutes after that, it dropped service again.
Finally, here is where it is at now:
I start with no service. If I do nothing but restart the phone, it will show LTE service for 2 or 3 seconds, then nothing. If I remove and reinstall the SIM, I will get the same 2 or 3 seconds, then nothing. If I turn Airplane Mode on and off, that does not reconnect the service. If I change the lock screen security to "None" and restart the phone, there is no service, but if I set Screen Lock to "Swipe" and restart the phone, I will have LTE service for at least 30 - 45 minutes before it drops, sometimes a few hours. When it does drop, it does not come back on it's own. The only way I have found to get it back it to "Screen Lock - None, reboot, Screen Lock - swipe, reboot".
Will replacing the modem fix the problem? Is there a specific modem that I need to match up to the ROM? Thanks!
Click to expand...
Click to collapse
I think you might be dealing with 2 separate issues. I'm kind of guessing about the first issue but the second is a common problem.
I think the original problem is that your sim card is not making a good contact in the sim slot. You could try putting a think piece of cardboard or something that will press the sim card to the sim slot contacts (maybe check to make sure that there isn't any dirt on the contacts but from the sound of it I'm guessing your phone is pretty clean).
The second problem is that all of the aosp roms have varying degrees of signal loss that occurs. Some people have a lot and some not as much, but everyone is affected in some way with what people have been referring to as "sim death".
My suggestion would be to run a stock or modified stock rom until you get your sim problem straightened out and then if you still want to switch to an aosp rom then at least you'll know that any further problems are just the normal sim death that occurs from time to time with those types of roms.
If you've already updated your bootloader to a 6.0.1 version you can flash the modified stock rom that I put together. I haven't had any signal/sim issues at all with that and no reports of it. Like I mentioned before though, the only caveat is that it needs to be on a bootloader that is at least CPD1 or newer. If it's not then your wifi won't work.
Rom link If you're interested.

kevintm78 said:
I think you might be dealing with 2 separate issues. I'm kind of guessing about the first issue but the second is a common problem.
I think the original problem is that your sim card is not making a good contact in the sim slot. You could try putting a think piece of cardboard or something that will press the sim card to the sim slot contacts (maybe check to make sure that there isn't any dirt on the contacts but from the sound of it I'm guessing your phone is pretty clean).
The second problem is that all of the aosp roms have varying degrees of signal loss that occurs. Some people have a lot and some not as much, but everyone is affected in some way with what people have been referring to as "sim death".
My suggestion would be to run a stock or modified stock rom until you get your sim problem straightened out and then if you still want to switch to an aosp rom then at least you'll know that any further problems are just the normal sim death that occurs from time to time with those types of roms.
If you've already updated your bootloader to a 6.0.1 version you can flash the modified stock rom that I put together. I haven't had any signal/sim issues at all with that and no reports of it. Like I mentioned before though, the only caveat is that it needs to be on a bootloader that is at least CPD1 or newer. If it's not then your wifi won't work.
Rom link If you're interested.
Click to expand...
Click to collapse
Thank you for the reply. I think that you may be onto something with both issues. After posting this question today, I did examine the SIM slot, and although all of the pins looked good, and no dust or debris was visible, the metal guide over the SIM did feel slightly loose from the card. I did put in a thin shim, and the significantly improved the time that the phone stays connected. If that was a true issue, along with the possibility of the ROM causing a separate cause, I am absolutely interested on going back to a stock (or modified stock) ROM. The only reason that I did what I did was an attempt to fix the connectivity issue.
Thanks for your help. I will give your ROM a try and let you know how it works.

Are there still snapdragon GPS issues?

This question is only directed to people who had issues from day 1, please don't reply if your GPS has always been working fine.
Are folks who had GPS issues with snapdragon models still continuing to have those issues? Interested in this phone but it definitely isn't worth it to me if I can't get a reliable GPS lock. Sounds like a hardware issue, and after experiencing it with the LG G5 on 3 replacements, I'm just not willing to risk it again.

I've had this issue since day one. Google Maps, GPS locks on without issue but when the APP isn't on "focus" or the screen is locked, my GPS signal is lost. Meaning the blue GPS icon is grey but when I go back into the APP it'll re-enable itself and locks on again. Repeats everytime.
Samsung s20 Ultra US Unlocked. I've reloaded the phone with both versions, U1 and U AT&T but same result. I've used really old version of Google Maps as well as newest version, same issue. I've also tried every kind of battery settings as well.
I don't know what to do next. I was on Samsung support, in hopes they will replace my phone, ultimately said it was a Google Maps issue.....
Help?

I've had S20+ US SD model since day 1 of launch and I've never had a GPS issue....
Edit-I saw you said don't reply if your phone has been working, AFTER I replied lol. My bad.