yashsingh1/xdaforums huggingface dataset:
[G2 Original Android Development] popxunga:
Just want to share my GPS tests.

Yesterday and after many months of dirty flashes, I decided to do a clean flash of latest (Feb 12) LOS build for my D802.

Not required, but I did format the phone internal storage too.

1st time, It took about 60 seconds to get a GPS fix.

In the next tests, the GPS fix was acquired in less than 5 seconds (most times was instantaneous) either by closing the test program (open source GPS Test) and/or turn off/on Location services.

I measured more 10 times after reboot and GPS fix was acquired between 30 and 60s the 1st time and then almost instantaneously.

So, the results were consistent across all tests done.

Notes:

1) Tests done with cloudy sky.

2) No connection (WiFi or Data) was used.

3) Airplane mode Off/On did not influence.
[G2 Original Android Development] alvinprimo:
2 last build have gps problem, sometimes when you stand still. While driving in the car hopeless. Now im convert to 20180129 build hope its better
[G2 Original Android Development] frikisama:
Same thing here.
[G2 Original Android Development] n@vier:
I can confirm this with latest build 20180212.

It's a serious problem because GPS seems really broken.
[G2 Original Android Development] Boopie11:
Maybe related to latest GLONASS changes??
[G2 Original Android Development] Yoyo117:
I've had this problem since switching to this ROM semi-regularily. I suspect updating Magisk and not rebooting before applying a system update causes the issue. The fix is easy though: simply restore your /boot partition from a previous backup. Then booting into the updated /system works and Magisk updates again if necessary.
[G2 Original Android Development] n@vier:
I think the same...
[G2 Original Android Development] GepXXX:
Hi guys I want to update the situation of my GPS problem with the last build (Feb 12).

I flashed the Feb 12 build again and opened system/etc/gps.conf:

##################################################

# Select Positioning Protocol on A-GLONASS system

##################################################

# 0x1: RRC CPlane

# 0x2: RRLP UPlane

# 0x4: LPP Uplane

A_GLONASS_POS_PROTOCOL_SELECT = 15

Why 15? I expected something between 0x0 and 0x7 (logic OR of the three flags)!

I changed the value to 0 as suggested ina previous post and now, after some quick tests, I can confirm that GPS is working and has exactly the same behaviour described by popxunga (fix was acquired between 30 and 60s the 1st time and then almost instantaneously).
[G2 Original Android Development] Kapricornus:
Let me revert GLONASS changes in the next Monday's build to see if it fixes GPS issues
[G2 Original Android Development] popxunga:
OK.. But my tests were done using the Feb 12 build without any modification in the GPS configuration. So if you got the same results only after the gps.conf file modification, I guess the issue was/is not directly caused by GLONASS activation in LOS builds.
[G2 Original Android Development] qwertyu123:
People who have the gps problems should test the edit on the gps.conf file.

In my case I never had problems no matter the configuration of gps.conf or the rom version.
[G2 Original Android Development] GepXXX:
After playing with different builds and GPS configuration, now I have restored the Feb 12 build without any modification in the GPS configuration and now it is working for me also.

I have tried many times in recent days with this build and configuation and it never worked, so now I' m quite confused.

Since I don't want to create more confusion, I'll test the Feb 12 build with original configuration for a longer period and I'll come back later.

For Kapricornus: maybe it's the case you consider to leave everything as it is and wait for more feedbacks.

Thank you everybody,

bye
[G2 Original Android Development] gabrielmulle:
Guys, has the download folder changed?

I download a new version using the Lineage updater, click on it and the cell reboot in twrp.

Then I go to /data/lineageos_updates/ folder and there's nothing there.
[G2 Original Android Development] popxunga:
I don't think so. At least I still have that folder in my phone.
[G2 Original Android Development] umeshbluezzz:
No support for ls980?
[G2 Original Android Development] alvinprimo:
Make sure delete updates when instal option not checked, and the rom.zip will stay in the folder
[G2 Original Android Development] n@vier:
I really hope you will revert in the next build that commit because with 15 or 0 in gps.conf GPS doesn't fix for me.

Thanks for your support ;)
[G2 Original Android Development] popxunga:
Did you try a clean flash ?
[G2 Original Android Development] n@vier:
Of course clean flash, otherwise I wouldn't have reported ;)
[G2 Original Android Development] popxunga:
Strange... same phone (D802), same ROM, different results however. What program did you use to test the GPS ?

Do you have Magisk installed ?
[G2 Original Android Development] n@vier:
I use GPS Test (I used GPS status too but same result... ) and I have magisk.
[G2 Original Android Development] popxunga:
Can you clean flash and test without Magisk ?
[G2 Original Android Development] n@vier:
I can't now but I'm quite sure it doesn't depend from magisk because I used AICP and RR that are LOS based ROMs with magisk and GPS worked as it should be...so the main problem i think should be that GLONASS commit because it's a newer feature implemented and many here as I read seem to have some problems with GPS.
[G2 Original Android Development] GepXXX:
GPS didn't work form me too at the beginning.

I'm not an expert so what I'm supposing may have no sense but GPS started to work since I flashed the Gen 8 release.

This is the sequence I did with the last TWRP by Blastgator:

-full wipe + Feb 5 release: GPS KO with original GPS.conf

-dirty flash of Feb 12 release: GPS KO with original and modified GPS.conf

-dirty flash of Gen 8 release: GPS OK

-dirty flash of Feb 12 release: GPS OK with original GPS.conf

I nave been testing the GPS for the last 2 days with GPS status, google maps and waze and it always locks 8/9 satellites very quickly!

I don't know...
[G2 Original Android Development] MarekAG:
What is Gen 8 release and where I can find it?
[G2 Original Android Development] n@vier:
He means the build of 20180108 and if you have the d802 variant you can find here:

https://download.lineageos.org/d802
[G2 Original Android Development] MarekAG:
Ok, so I dirty flashed 20180108 over newest release and now GPS works ok.

Thanks guys for the idea.

Evidently something is broken with GPS in releases after 8 January.
[G2 Original Android Development] n@vier:
If you are root can you share GPS.conf file of that build?

You can find it in system/etc/GPS.conf

Thanks in advance ;)
[G2 Original Android Development] popxunga:
Works for me. So isn't broken.
[G2 Original Android Development] n@vier:
Can you share it as attached file? So I try to replace it with this.
[G2 Original Android Development] GepXXX:
Hi popxunga, in my case, as I wrote, at the beginning with the last builds (clean flash) GPS didn't work even modifying gps.conf.

It started to work when I dirty flashed the last build on the 20180108.

Just a curiosity, how did you get to the last build? Have you ever flashed the 20180108 (or a previous one) before?
[G2 Original Android Development] popxunga:
I flashed all LOS builds so far.

As explained in my GPS test, I formatted everything in my phone, and then flashed the Feb 12 build. So I'm sure there was no traces of anything I had before, that could influence the tests.

Edit: After Feb 12 clean flash along with pico Opengapps, I just setup WiFi, added my Google account and installed the test GPS app and nothing else.
[G2 Original Android Development] MarekAG:
[MENTION=4240321]popxunga[/MENTION] if it's working for you it won't mean that it isn't broken.

I'm not the only person who reports GPS problems.

If it's working for you - great, maybe you are lucky, maybe you have different bootstack or something else which is affecting GPS, idk. But for others GPS is broken in last releases.

So don't say that there is no problem, when the problem is real and persists.

[MENTION=1875664]navier[/MENTION] just copy-paste content of gps.conf which I posted into yours phone gps.conf file. You may want to make copy of your gps.conf first.
[G2 Original Android Development] n@vier:
Yeah thanks. I saw after I checked it and it's the same of the lastest build because I changed the last line...so that file shouldn't be the problem but something else...
[G2 Original Android Development] popxunga:
I can say exactly the same: if it fails for you it doesn't mean is broken for everyone. It works for me and I explained in which conditions. So for me GPS is not broken. Don't forget that most people come here to report failures and much less frequently to report that something works. Anyway there's nonsense to keep arguing on this.
[G2 Original Android Development] n@vier:
Will the new build be released today?
[G2 Original Android Development] MarekAG:
The sense is that you are logically wrong.

GPS doesn't work for some part of people at the same time, so it's not a problem with device or these people.

Something in last ROM releases causes that GPS is broken. I'm not arguing if it's broken for 1% of users or for 99%, but something is wrong.

As I say before: For you GPS works? Great. Good for you. Please just don't write that GPS isn't broken at all. It isn't broken for you, but overall something is wrong in couple last releases.

EOT
[G2 Original Android Development] GepXXX:
Have you tryed to dirty flash 20180212 again after 20180108?
[G2 Original Android Development] popxunga:
Sorry but I'll say that GPS works for me the number of times I want, exactly the same way you will keep saying that GPS is broken.

My logic is simple and correct:

The same working equipment running the same software should produce the same exact result.

My basic test procedure is explained above. Until you do it, for me, the GPS failure you're getting is due to something else you do/have in your phone that when used with latest LOS builds make GPS fail.

So, the first step would be figure out what exactly.

---------- Post added at 05:39 PM ---------- Previous post was at 05:34 PM ----------

Today's builds on Jenkins starting with job #10145 are failing in the sign and mirror phase.
[G2 Original Android Development] Boopie11:
Can someone please tell me if all the changes that happened to the GPS have been in the

Gps.conf file?

Are there any other modified files?

Btw with 22 of January build, GPS standalone works good
[G2 Original Android Development] GepXXX:
I don't completely agree with you when you say that "The same working equipment running the same software should produce the same exact result" because also the history has its importance.

I came to LOS 20180212 with a clean flash after 1 year of CM13, this was my first LOS build, and with 20180212 GPS never worked for days.

Later I dirty flashed 20180108 and then 20180212 again and then... GPS magically started to work very well.

I state that I don't have enough knowledge of hw and sw of the G2 to take conclusions but I found the PCB of the Nexus 5 (very similar to G2, I can't find the one of the G2) and I saw that GPS is on a module external to main microprocessor.

So, what if this module has its own non volatile memory (eeprom?) to store configuration data?: the behaviour of the GPS may be affected not only by the build currently running but also by the previous ones.

For example a previous build could have modified a parameter not managed by the last one.

I repeat, mine are just suppositions due to the strange behavior of my G2.

What I mean is that

Mine is just an hypothesis
[G2 Original Android Development] popxunga:
https://review.lineageos.org/#/c/203899/

That change was introduced after January 22 build. As far as I can see in the change referred above, the modifications were confined to the gps.conf file. Not sure if there were other changes related with this. Only the Developer's team may confirm.

---------- Post added at 06:50 PM ---------- Previous post was at 06:38 PM ----------

I don't know the G2 hardware to that point either. But I guess that a factory reset after a clean flash would clean up anything previously set. Having a good backup out of the phone is always a good idea when doing this type of tests.

And when some doubt persists, going back to stock by kdz flashing is the way.
[G2 Original Android Development] n@vier:
[MENTION=4283595]Kapricornus[/MENTION] all builds on jenkins for G2 failed today :(
[G2 Original Android Development] Kapricornus:
All Monday's builds have failed, not only G2

And since January 22nd there was a single change, the one to gps.conf. If modifying it doesn't help, then reverting won't help either and discussion about it doesn't make much sense
[G2 Original Android Development] gabrielmulle:
Downloading the last release, Feb 20, to see if it resolves the GPS problem. Will give feedback later.

The discussion should be on finding the GPS problem, not if 'there is a problem'.

It is pretty obvious that there is a problem, if 10+ people are saying GPS is not working.

---------- Post added at 11:57 AM ---------- Previous post was at 11:52 AM ----------

Thank you man! This worked. Not sure why that option was selected thou :good:
[G2 Original Android Development] alvinprimo:
This method works! Gps back to normal 20180212 build
[G2 Original Android Development] Boopie11:
So what is the root of the GPS issue?
[G2 Original Android Development] n@vier:
System/etc/GPS.conf
[G2 Original Android Development] Boopie11:
I mean if is the GLONASS 15 thing..
[G2 Original Android Development] alvinprimo:
Gps not locking after update 20180212, I revert to 201801 build

But still take long time to lock position. The I try dirty flash back to 20180212 build like the post I quote before and gps its working. I really not sure what issue here, since i dont modify anything in gps.conf
[G2 Original Android Development] gabrielmulle:
Feedback: so yesterday I installed the last build, Feb 20.

Used Google Maps GPS and it delayed more than 2 min to lock.

Then, tested with Waze and it locked right away.

Then, tested again with Waze and it delayed more than 1 min.

---------- Post added at 01:56 PM ---------- Previous post was at 01:55 PM ----------

what dirty flash back means? Is there any step by step or tutorial on how to do that? Or it just means installing a release without wiping the phone data (reseting to factory)?
[G2 Original Android Development] GepXXX:
It means installing wothout wiping, so install zip image and that's all
[G2 Original Android Development] dsjstc:
Any recent successes with D803 (Canadian)?

Would love to hear if anybody has had success installing an official build on a D803.

As noted here, there seems to be an issue with boot-looping on the D803 with any current official version. I've tried clean installs of four different builds with the same loopy behaviour.

I also posted a regression bug against the error 07 I got when doing a dirty install, but it was rejected, and my followup ignored -- it doesn't inspire me to try posting a regression about the boot-loop, because I've never actually had success with an official build.
[G2 Original Android Development] _kayya:
I am writing just for the inform you, my device (D802) has gps problem issues too after the glonas updates... It can not connect to the satellites or it lost connection after a few seconds... I have tried it with google maps, yandex navi...
[G2 Original Android Development] alvinprimo:
That's what I did. And i wipe dalvic and cache too
[G2 Original Android Development] n@vier:
I can confirm this: I clean flashed the build of 8th January then I updated (with the LOS updater built-in rom) directly to the latest build of 20th February and GPS works as it should be ;)
[G2 Original Android Development] wikowikowiko:
on 3 - 4 latest update, (if i'm not mistaken, since 29 jan build), i had random sim card not detected.

tested the sim card on my lg g4 phone, no issue with the simcard.

as per my observation, when my device got quite warm after playing games, the simcard will not get detected.

but as what i said previously, it was random.

latest build was the worst for me. today i cannot get the phone to detect the simcard no matter how many time i restarted my phone.

and then, i installed 8 january build, now simcard is detected.

regarding the GPS, i can say gps is always working for me. i can get fix using US' gps sats.

anyway, i cannot lock glonass even though the satellites were detected.
[G2 Original Android Development] Sobek5150:
So what are our options for theming? Looks like there isn't substratum support with this rom, or whatever support that needs to be there to keep crashes and bootloops from happening after Apply themes.

My wife's G2 had AICP on it, but it was a year old and way out of date. That brings me to Today, installed 14.1 and substratum now marked "substratum legacy" and caused a bootloop when I attempted setting an Android system theme.

So again, anyone have an alternative?
[G2 Original Android Development] popxunga:
Hi ...

Any idea about the next d802 los 14.1 build release date ?

Thanks
[G2 Original Android Development] xpissio:
Weekly builds for G2 have been moved to Wednesday.
[G2 Original Android Development] popxunga:
Thanks !
[G2 Original Android Development] T2000T2000:
Seems like https://jenkins.lineageos.org/job/android/10378/ is finished but the follow-up signing job is broken :( Damn I really wanted to have the GPS fixes before my vacation next week...
[G2 Original Android Development] n@vier:
Check again you need to wait the upload's time ;)
[G2 Original Android Development] T2000T2000:
Oh, indeed now it is there :)

But strange that https://jenkins.lineageos.org/job/android/10378/console

says it started the signing job

But https://jenkins.lineageos.org/job/android-sign-and-mirror/9325/ is not reachable...
[G2 Original Android Development] gabrielmulle:
Just installed :)

Looking forward to test GPS on my way home today.

Thank you guys for this. Appreciate.
[G2 Original Android Development] bernida:
Just flashed and GPS seems to work again! :)

Also out of curiosity I tried A_GLONASS_POS_PROTOCOL_SELECT = 15 in /system/etc/gps.conf again, and it still works!

So the problem really seemed to be solved by this https://review.lineageos.org/#/c/207681/

I wonder what 15 means and why it is not set to something like 0x4 or 0x2, but because I don't know what it does exactly and I also need to rely on my GPS tomorrow for navigation, I'm reverting back to 0

But, with 15, accuracy in the same spot was about 10-15m, while with set to 0, accuracy was reported 20ish meters, but this could be very well in the margin of error. "In Use" number of sattelites in GPS Test was about the same (7-8)

Maybe there is some potential for optimization! Thanks alot devs!
[G2 Original Android Development] Ogloppi:
I'll report too, that the GPS of D802 works again with the latest update.
[G2 Original Android Development] MarekAG:
I can also confirm: On last update everything works good. Great work guys!
[G2 Original Android Development] nokiac:
Battery life has somehow improved for me after the latest update. Using D800 here. GPS always worked fine though .

Thanks a lot to the devs for this amazing ROM
[G2 Original Android Development] Wilson w:
The GPS works well.Thank you for your jobs!!!!
[G2 Original Android Development] bernida:
There still seems to be something off with finding a fix fast (AGPS?), at least for me

So back in the day before the whole GPS issue, I would find a fix in a matter of seconds.

Since the last patch, while GPS works again (at all), it takes something like 1-2mins to get a fix (seems like it gets no assistance and it always needs to find the position from scratch)

(This is really annoying if I need my phone for navigation in a city)

So I messed around with gps.conf and found this config (down below) to be working perfectly for me, now it locks the position in seconds again

Also: it now says "in-view" sattelites ~20, before it was only ~9

(app used for testing: GPS Test)

So something seems to be wrong in our gps.conf

Unfortunately I don't really know the specifics of what these values do or which one(s) is responsible in particular, so maybe someone who knows details or a developer can have a look into it and set the right values for the next build.

But this worked for me and I will continue to use this config as an intermediate solution. Does anyone of you experience similar issues? If yes, can you try out these values and report back?

Thanks and kind regards

XTRA_SERVER_1=http://xtrapath1.izatcloud.net/xtra2.bin
XTRA_SERVER_2=http://xtrapath2.izatcloud.net/xtra2.bin
XTRA_SERVER_3=http://xtrapath3.izatcloud.net/xtra2.bin
XTRA_VERSION_CHECK=1
ERR_ESTIMATE=0
NTP_SERVER=europe.pool.ntp.org
DEBUG_LEVEL = 2
INTERMEDIATE_POS=0
SUPL_VER=0x10000
SUPL_ES=1
USE_EMERGENCY_PDN_FOR_EMERGENCY_SUPL=1
CAPABILITIES=0x31
SUPL_SECURE_PORT=7275
LPP_PROFILE = 2
NMEA_PROVIDER=0
SGLTE_TARGET=0
A_GLONASS_POS_PROTOCOL_SELECT = 0
[G2 Original Android Development] Ciross:
Hi all,

I confirme the GPS.conf file from bernida is working better than the stock one for me. I come from a clean flash of the 20-02-2018, update to 28-02-2018 build with a dirty flash.

With GPS test I had 6 satellites in use at my window with the stock GPS.conf. And a fix after a minute. I have done this test 3 tomes, 3 different days and I have always a long fix.

At the same window with the new file I have 12 satellites in use and 5 seconds fix.
[G2 Original Android Development] qwertyu123:
Maybe its related to NTP server or the xtra servers.

Can anyone who has problems with stock try first changing NTP server? Stock is using north american server.
[G2 Original Android Development] 4Freedom:
IDK if forcing europe is good for the others continents.

According to comments in AOSP, NTP_SERVER should be different depending on the continent. https://android.googlesource.com/platform/hardware/qcom/gps/+/android-8.1.0_r14/etc/gps.conf

#Test
NTP_SERVER=time.gpsonextra.net
#Asia
# NTP_SERVER=asia.pool.ntp.org
#Europe
# NTP_SERVER=europe.pool.ntp.org
#North America
# NTP_SERVER=north-america.pool.ntp.org

And according to NTP Pool Project http://www.pool.ntp.org/zone/@

In most cases it's best to use pool.ntp.org to find an NTP server (or 0.pool.ntp.org, 1.pool.ntp.org, etc if you need multiple server names). The system will try finding the closest available servers for you