[ROM][10.0][OneUI 2.5][G930X/G935X/N930X/N935X]FloydQ V7.0

[Samsara69]

Of course..

Btw , where others members here,..are they bored?!

I think you right ,must return to stock ROM then remove all useless apps...

 

[magic378]

I did..have u take ur medicine,..?!

 

[endolith]

Samsung has just released an update to the firmware for the S7 to fix GPS issues. It is G930FXXU8EVG3. See https://www.androidauthority.com/samsung-galaxy-s7-s8-updates-3198409/

Can we install this fix with FloydQ 7.0?

Would this fix the issue where the "current location" icon gets stuck and then jumps to a sort of nearby random place and then gets stuck again, but the GPS track itself is correct? I've noticed this is in multiple apps. I imagine the two things are being accessed through two different APIs or functions or something?

• Avenza track: Broken
• Google TImeline track: Broken
• StreetComplete current location: Broken
• Maprika blue icon: Broken
• Maprika red track: Perfectly correct and normal

It's very strange that the same app shows the wrong location for one thing but the correct location for the other. My actual location was at the end of the red line, but the blue icon is "stuck" at a location near, but not identical to, my previous location:

When I'm stationary for a while, the blue icon will update, but still be less accurate than the red line. Avenza and Google Timeline and StreetComplete are getting the same location as the Blue icon, not the red line, so Avenza tracks and Google Timeline tracks look very jerky and only gets fixes in bursts and shows me substantially off roads:

Maprika's .GPX files have the wrong date for timestamps, too. It is currently 2022-09-23 08:17 PM but I just made a track and the timestamp is 2003-02-07 7:17PM. The last .gpx file I have with correct timestamps is from 2022-08-20. Google Timeline is also smooth for August 20 and earlier, but not for August 21 or after.

I thought it was just Maprika at first, but now I'm realizing it affects multiple apps, so it's some issue with the ROM or phone. I know scientists use GPS for precise timing, so maybe the GPS receiver is creating the erroneous timestamps that appear in the GPX tracks, too?

 

[magic378]

Can we install this fix with FloydQ 7.0?

Would this fix the issue where the "current location" icon gets stuck and then jumps to a sort of nearby random place and then gets stuck again, but the GPS track itself is correct? I've noticed this is in multiple apps. I imagine the two things are being accessed through two different APIs or functions or something?

• Avenza track: Broken
• Google TImeline track: Broken
• StreetComplete current location: Broken
• Maprika blue icon: Broken
• Maprika red track: Perfectly correct and normal

It's very strange that the same app shows the wrong location for one thing but the correct location for the other. My actual location was at the end of the red line, but the blue icon is "stuck" at a location near, but not identical to, my previous location:

View attachment 5718947

When I'm stationary for a while, the blue icon will update, but still be less accurate than the red line. Avenza and Google Timeline and StreetComplete are getting the same location as the Blue icon, not the red line, so Avenza tracks and Google Timeline tracks look very jerky and only gets fixes in bursts and shows me substantially off roads:

View attachment 5718949

Maprika's .GPX files have the wrong date for timestamps, too. It is currently 2022-09-23 08:17 PM but I just made a track and the timestamp is 2003-02-07 7:17PM. The last .gpx file I have with correct timestamps is from 2022-08-20. Google Timeline is also smooth for August 20 and earlier, but not for August 21 or after.

I thought it was just Maprika at first, but now I'm realizing it affects multiple apps, so it's some issue with the ROM or phone. I know scientists use GPS for precise timing, so maybe the GPS receiver is creating the erroneous timestamps that appear in the GPX tracks, too?

Dont never ever even think about it..

Enjoy what u got here ma men?!

 

[endolith]

Can we install this fix with FloydQ 7.0?

Would this fix the issue where the "current location" icon gets stuck and then jumps to a sort of nearby random place and then gets stuck again, but the GPS track itself is correct?

OK, I ran StreetComplete and Maprika in split screen and confirmed that the blue dot/arrow are updating at the same time (slowly and inaccurately).

I disabled "use Wi-Fi for increased accuracy" and they seemed to update less often.

I put it in Airplane mode and both stopped updating completely, while the red line kept going. So it's pretty obvious that the blue dot/arrow are only getting location from cell towers/Wi-Fi and not from the GPS receiver, while the red line is getting location from GPS.

Maybe the GPS receiver is returning the wrong timestamp, so sensor fusion is rejecting it? Something like that?

This is an Exynos S7 G930F. I have a G930V at work, I will test it and maybe I can compare before and after the latest firmware update.

 

[endolith]

OK, I ran StreetComplete and Maprika in split screen and confirmed that the blue dot/arrow are updating at the same time (slowly and inaccurately).

With more testing, I realized that Maprika in OpenStreetMap mode shows the blue arrow that is not accurate to the actual GPS position:

But in Google Road view, it shows a blue dot that is accurate and always stays at the tip of the red line:

But timestamps are still wrong:

Meanwhile, the Verizon S7 shows correct location for both, always:

And it has the correct timestamp.

So it seems this is either an issue with FloydQ (which is not running on the Verizon S7) or a difference in hardware (since Verizon is Snapdragon and mine is Exynos, maybe they have different GPS modules or something). The Verizon phone has G930VVRSBCTC1 (Security Patch December 1, 2019) and says there are no updates at this time.

Anyone have an Exynos S7 with FloydQ and can record a track in Maprika in OpenStreetMap mode and see if it's just me or a ROM issue?

 

[kaanaysel]

Hello, Samsung Notes not working from Version 6.0 and still don't work on Version 7. At the other side ROM is really wonderfull and i can pay to you about of thanks. Can you check it Samsung Notes?

 

[Thugscub]

@endolith on OSM I do not have any problems it just takes a while to find itself, 3 min, then is accurate from then on. Also a 935F model. I Don't use Google maps.

 

[endolith]

With more testing, I realized that Maprika in OpenStreetMap mode shows the blue arrow ...

Today it worked normally! It fixed itself! I have no idea why.

The blue arrow in Maprika follows the red line now, and StreetComplete shows a blue track (which I didn't even know it could do) and it matches Maprika's red track. Maprika's timestamp is correct, too! First time it has recorded a track with the correct timestamp since August 20.

Turning off "Improve accuracy" with Wi-Fi didn't fix it; it still wasn't using GPS, but maybe restarting the phone while that was turned off did something?

Google app was updated yesterday, but I doubt that could fix it? It doesn't say anything about it in "What's New".

GPS Status app now shows GPS, GLONASS, BeiDou, and Galileo satellites, while the last time I checked it was only showing GPS and GLONASS.

 

[endolith]

Today it worked normally! It fixed itself! I have no idea why.

Back to being broken. Timestamp is wrong, location is inaccurate, updates of location are rare, EU and Chinese satellites are no longer visible.

I got the barbeuDev GPSTest app which implies that the erroneous timestamps are indeed coming from the GPS receiver and this might be due to a fixable rollover bug? Is this fixable in FloydQ? Does anyone else see this with this app?

Actual time was 2022-09-27 02:29 PM EST. February 11th was indeed 1024 weeks ago, so this seems like the same bug.

This is the link: https://github.com/barbeau/gpstest/blob/master/FAQ.md#why-is-my-gps-time-wrong

Verizon S7 does not have these problems, despite placing them right next to each other. Timestamp is correct and it picks up EU satellites (as well as a greater number of US and Russian ones).

 

[rainer777]

Back to being broken. Timestamp is wrong, location is inaccurate, updates of location are rare, EU and Chinese satellites are no longer visible.

I got the barbeuDev GPSTest app which implies that the erroneous timestamps are indeed coming from the GPS receiver and this might be due to a fixable rollover bug? Is this fixable in FloydQ? Does anyone else see this with this app?

Actual time was 2022-09-27 02:29 PM EST. February 11th was indeed 1024 weeks ago, so this seems like the same bug.

View attachment 5721791

This is the link: https://github.com/barbeau/gpstest/blob/master/FAQ.md#why-is-my-gps-time-wrong

Verizon S7 does not have these problems, despite placing them right next to each other. Timestamp is correct and it picks up EU satellites (as well as a greater number of US and Russian ones).

Did you think of using a newer version of software? The latest release of gpstest is nearly one year old. Just my 2 cents....

 

[endolith]

Did you think of using a newer version of software? The latest release of gpstest is nearly one year old. Just my 2 cents....

Why would that matter?

 

[magic378]

Haleluyah ma men,..?!

This is the end for our galaxy..

No more update.. just enjoy it?!!

No complain anymore please..

 

[ananjaser1211]

As per @endolith , Samsung rolled out an update to fix a certain issue in GPS, for more boring details read this issue

A patch for the bug is out, this allows for accurate GPS Time which allows for more satellites to be connected, so better accuracy etc.

Patch seems to be working fine for now, however if anything weird happens the issue will be updated with more information.

Download : Github

 

[Thugscub]

@Ananjasrer
Many thanks for the awesome rom and latest patch.

Hi Guys can someone here please send a link to the GPS update please. Then I'll run the patch. Thanks.

 

[magic378]

Amazing anan..u just make my day?!

 

[mpadhu]

Hi guys. Do any one face issues with banking apps like icici, paytm, gpay with Magisk installed or do they work fine with magisk hide?.

 

[winamp26]

Hi guys. Do any one face issues with banking apps like icici, paytm, gpay with Magisk installed or do they work fine with magisk hide?.

hi
check this channel

 

[mpadhu]

My S7 edge is randomly restarting when unclocking the screen. Any way to fix this?

 

[magic378]

My S7 edge is randomly restarting when unclocking the screen. Any way to fix this?

Now everything is OK .. n just perfect for custom ROM?!

Reflash your's