GPS Rollover on Android Smartphones
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
Regarding the GPS weeks rollover which took place on April 06th 2019. all the websites are talking about the phenomenon but they are not explaining what are the side effects on end users devices if the week number will be 0000.
How an Android smartphone GPS users could be affected regarding this rollover from 1023 to 0000 weeks ?
Regards
gps bugs
asked yesterday
Abdelhafid MadouiAbdelhafid Madoui
541321
add a comment |
Regarding the GPS weeks rollover which took place on April 06th 2019. all the websites are talking about the phenomenon but they are not explaining what are the side effects on end users devices if the week number will be 0000.
How an Android smartphone GPS users could be affected regarding this rollover from 1023 to 0000 weeks ?
Regards
gps bugs
asked yesterday
Abdelhafid MadouiAbdelhafid Madoui
541321
add a comment |
Regarding the GPS weeks rollover which took place on April 06th 2019. all the websites are talking about the phenomenon but they are not explaining what are the side effects on end users devices if the week number will be 0000.
How an Android smartphone GPS users could be affected regarding this rollover from 1023 to 0000 weeks ?
Regards
gps bugs
asked yesterday
Abdelhafid MadouiAbdelhafid Madoui
541321
Regarding the GPS weeks rollover which took place on April 06th 2019. all the websites are talking about the phenomenon but they are not explaining what are the side effects on end users devices if the week number will be 0000.
How an Android smartphone GPS users could be affected regarding this rollover from 1023 to 0000 weeks ?
Regards
gps bugs
gps bugs
asked yesterday
Abdelhafid MadouiAbdelhafid Madoui
541321
asked yesterday
Abdelhafid MadouiAbdelhafid Madoui
541321
asked yesterday
Abdelhafid MadouiAbdelhafid Madoui
541321
asked yesterday
Abdelhafid MadouiAbdelhafid Madoui
541321
asked yesterday
Abdelhafid MadouiAbdelhafid Madoui
541321
541321
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
From what I know the rollover is not the only problem, also an additional week counter 13 bits is introduced. A new data format (with larger data) can of course cause problems if unsupported by the GPS receiver firmware.
Also I have read that some GPS devices use the week counter for plausibility checking of the received data. If the week is smaller than the manufacturing week the data have to be invalid so the simple but bad logic. After the roll-over it will simply reject all incoming data as the receiver thinks that the received data is invalid (e.g. because of radiointerference).
answered yesterday
RobertRobert
3,42921829
"the week counter is increased..." makes it sound like the 10-bit week code is changing. That's not happening. The legacy (ICD-200) message continues to encode a 10-bit week number. There are additional messages (such as in the CNAV data) that transmit a 13-bit week number for newer equipment to read. There's no compatibility issue for older equipment.
– BowlOfRed
21 hours ago
@BowlOfRed Theoretically you are right, however programmers often develop such bad code so that any changes (even those already described in the standard) can and will lead to program failures even if it should continue to work without problems.
– Robert
18 hours ago
I'm unaware of any changes to the data format related to April 6. The 13-bit week number data format has been broadcast in CNAV packets for several years (but only from newer satellites). GPS III sats will also be a change, but none are marked operational yet.
– BowlOfRed
17 hours ago
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "139"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fandroid.stackexchange.com%2fquestions%2f210055%2fgps-rollover-on-android-smartphones%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
From what I know the rollover is not the only problem, also an additional week counter 13 bits is introduced. A new data format (with larger data) can of course cause problems if unsupported by the GPS receiver firmware.
Also I have read that some GPS devices use the week counter for plausibility checking of the received data. If the week is smaller than the manufacturing week the data have to be invalid so the simple but bad logic. After the roll-over it will simply reject all incoming data as the receiver thinks that the received data is invalid (e.g. because of radiointerference).
answered yesterday
RobertRobert
3,42921829
"the week counter is increased..." makes it sound like the 10-bit week code is changing. That's not happening. The legacy (ICD-200) message continues to encode a 10-bit week number. There are additional messages (such as in the CNAV data) that transmit a 13-bit week number for newer equipment to read. There's no compatibility issue for older equipment.
– BowlOfRed
21 hours ago
@BowlOfRed Theoretically you are right, however programmers often develop such bad code so that any changes (even those already described in the standard) can and will lead to program failures even if it should continue to work without problems.
– Robert
18 hours ago
I'm unaware of any changes to the data format related to April 6. The 13-bit week number data format has been broadcast in CNAV packets for several years (but only from newer satellites). GPS III sats will also be a change, but none are marked operational yet.
– BowlOfRed
17 hours ago
add a comment |
From what I know the rollover is not the only problem, also an additional week counter 13 bits is introduced. A new data format (with larger data) can of course cause problems if unsupported by the GPS receiver firmware.
Also I have read that some GPS devices use the week counter for plausibility checking of the received data. If the week is smaller than the manufacturing week the data have to be invalid so the simple but bad logic. After the roll-over it will simply reject all incoming data as the receiver thinks that the received data is invalid (e.g. because of radiointerference).
answered yesterday
RobertRobert
3,42921829
"the week counter is increased..." makes it sound like the 10-bit week code is changing. That's not happening. The legacy (ICD-200) message continues to encode a 10-bit week number. There are additional messages (such as in the CNAV data) that transmit a 13-bit week number for newer equipment to read. There's no compatibility issue for older equipment.
– BowlOfRed
21 hours ago
@BowlOfRed Theoretically you are right, however programmers often develop such bad code so that any changes (even those already described in the standard) can and will lead to program failures even if it should continue to work without problems.
– Robert
18 hours ago
I'm unaware of any changes to the data format related to April 6. The 13-bit week number data format has been broadcast in CNAV packets for several years (but only from newer satellites). GPS III sats will also be a change, but none are marked operational yet.
– BowlOfRed
17 hours ago
add a comment |
From what I know the rollover is not the only problem, also an additional week counter 13 bits is introduced. A new data format (with larger data) can of course cause problems if unsupported by the GPS receiver firmware.
Also I have read that some GPS devices use the week counter for plausibility checking of the received data. If the week is smaller than the manufacturing week the data have to be invalid so the simple but bad logic. After the roll-over it will simply reject all incoming data as the receiver thinks that the received data is invalid (e.g. because of radiointerference).
answered yesterday
RobertRobert
3,42921829
From what I know the rollover is not the only problem, also an additional week counter 13 bits is introduced. A new data format (with larger data) can of course cause problems if unsupported by the GPS receiver firmware.
Also I have read that some GPS devices use the week counter for plausibility checking of the received data. If the week is smaller than the manufacturing week the data have to be invalid so the simple but bad logic. After the roll-over it will simply reject all incoming data as the receiver thinks that the received data is invalid (e.g. because of radiointerference).
answered yesterday
RobertRobert
3,42921829
edited 18 hours ago
answered yesterday
RobertRobert
3,42921829
answered yesterday
RobertRobert
3,42921829
answered yesterday
RobertRobert
3,42921829
3,42921829
"the week counter is increased..." makes it sound like the 10-bit week code is changing. That's not happening. The legacy (ICD-200) message continues to encode a 10-bit week number. There are additional messages (such as in the CNAV data) that transmit a 13-bit week number for newer equipment to read. There's no compatibility issue for older equipment.
– BowlOfRed
21 hours ago
@BowlOfRed Theoretically you are right, however programmers often develop such bad code so that any changes (even those already described in the standard) can and will lead to program failures even if it should continue to work without problems.
– Robert
18 hours ago
I'm unaware of any changes to the data format related to April 6. The 13-bit week number data format has been broadcast in CNAV packets for several years (but only from newer satellites). GPS III sats will also be a change, but none are marked operational yet.
– BowlOfRed
17 hours ago
add a comment |
"the week counter is increased..." makes it sound like the 10-bit week code is changing. That's not happening. The legacy (ICD-200) message continues to encode a 10-bit week number. There are additional messages (such as in the CNAV data) that transmit a 13-bit week number for newer equipment to read. There's no compatibility issue for older equipment.
– BowlOfRed
21 hours ago
@BowlOfRed Theoretically you are right, however programmers often develop such bad code so that any changes (even those already described in the standard) can and will lead to program failures even if it should continue to work without problems.
– Robert
18 hours ago
I'm unaware of any changes to the data format related to April 6. The 13-bit week number data format has been broadcast in CNAV packets for several years (but only from newer satellites). GPS III sats will also be a change, but none are marked operational yet.
– BowlOfRed
17 hours ago
"the week counter is increased..." makes it sound like the 10-bit week code is changing. That's not happening. The legacy (ICD-200) message continues to encode a 10-bit week number. There are additional messages (such as in the CNAV data) that transmit a 13-bit week number for newer equipment to read. There's no compatibility issue for older equipment.
– BowlOfRed
21 hours ago
"the week counter is increased..." makes it sound like the 10-bit week code is changing. That's not happening. The legacy (ICD-200) message continues to encode a 10-bit week number. There are additional messages (such as in the CNAV data) that transmit a 13-bit week number for newer equipment to read. There's no compatibility issue for older equipment.
– BowlOfRed
21 hours ago
@BowlOfRed Theoretically you are right, however programmers often develop such bad code so that any changes (even those already described in the standard) can and will lead to program failures even if it should continue to work without problems.
– Robert
18 hours ago
@BowlOfRed Theoretically you are right, however programmers often develop such bad code so that any changes (even those already described in the standard) can and will lead to program failures even if it should continue to work without problems.
– Robert
18 hours ago
I'm unaware of any changes to the data format related to April 6. The 13-bit week number data format has been broadcast in CNAV packets for several years (but only from newer satellites). GPS III sats will also be a change, but none are marked operational yet.
– BowlOfRed
17 hours ago
I'm unaware of any changes to the data format related to April 6. The 13-bit week number data format has been broadcast in CNAV packets for several years (but only from newer satellites). GPS III sats will also be a change, but none are marked operational yet.
– BowlOfRed
17 hours ago
add a comment |
Thanks for contributing an answer to Android Enthusiasts Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fandroid.stackexchange.com%2fquestions%2f210055%2fgps-rollover-on-android-smartphones%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
