New Year Service Overdue Bug

[Keato]

This doesn't work for my case. My service overdue was 2051d on 1 Jan 2026 and puts me between 2048d and 2057d, or 1 JAN 2026 and 23 DEC 2025 for a service due date.

Note that my error message is >=2048, but my last service reset was 21 May 2025, so I would not have already received a legitimate service due message on or before Jan 1, 2026, but would have on 21 May 2026.

Love what you did here, I tried with 11-bits as I figured highest bit might be used for the sign, but that didn't work out and 10-bit doesn't appear to either.

I ran all of these XXXXd through the Tcl script (assumed all the XXXXd were what they were on 1 JAN 2026), and here's what I get for each -- first column is now the Last Service Date, i.e. when your Grenadier's service counter was reset -- add 5 years to get the actual Last Service Date, the next service date, add 6 years. The MM and DD are same, only the years shift (so only 5 or 6 years of days were added? I think 5 years worth of days). Note because it matters what date you read your XXXXd value, it may be off a few days MM/DD wise, as I had to make the assumption that all these XXXXd were read on 1 JAN 2026 as it's not specified.

If you recognize your XXXXd or can interpolate, was your last service reset date close to the date in the first column + 5 years +/- a few days (i.e. MM / DD are off a bit)? I left all the columns and values from Glen's table after the '--' for reference.

Last Service Reset -- Error Msg / Modulo 1024 / 10-bit Binary / Days Since Service Due / Service Due Date
2020-12-17 -- 1841 817 1100110001 -207 Jul 27, 2026
2020-12-06 -- 1852 828 1100111100 -196 Jul 16, 2026
2020-12-06 -- 1852 828 1100111100 -196 Jul 16, 2026
2020-11-20 -- 1868 844 1101001100 -180 Jun 30, 2026
2020-11-19 -- 1869 845 1101001101 -179 Jun 29, 2026
2020-10-29 -- 1890 866 1101100010 -158 Jun 08, 2026
2020-10-27 -- 1892 868 1101100100 -156 Jun 06, 2026
2020-10-25 -- 1894 870 1101100110 -154 Jun 04, 2026
2020-10-20 -- 1899 875 1101101011 -149 May 30, 2026
2020-10-16 -- 1903 879 1101101111 -145 May 26, 2026
2020-10-13 -- 1906 882 1101110010 -142 May 23, 2026
2020-10-04 -- 1915 891 1101111011 -133 May 14, 2026
2020-09-22 -- 1927 903 1110000111 -121 May 02, 2026
2020-09-18 -- 1931 907 1110001011 -117 Apr 28, 2026
2020-09-17 -- 1932 908 1110001100 -116 Apr 27, 2026
2020-09-16 -- 1933 909 1110001101 -115 Apr 26, 2026
2020-09-12 -- 1937 913 1110010001 -111 Apr 22, 2026
2020-09-09 -- 1940 916 1110010100 -108 Apr 19, 2026
2020-09-04 -- 1945 921 1110011001 -103 Apr 14, 2026
2020-08-30 -- 1950 926 1110011110 -98 Apr 09, 2026
2020-08-27 -- 1953 929 1110100001 -95 Apr 06, 2026
2020-08-13 -- 1967 943 1110101111 -81 Mar 23, 2026
2020-08-12 -- 1968 944 1110110000 -80 Mar 22, 2026
2020-08-12 -- 1968 944 1110110000 -80 Mar 22, 2026
2020-08-05 -- 1975 951 1110110111 -73 Mar 15, 2026
2020-07-22 -- 1989 965 1111000101 -59 Mar 01, 2026
2020-07-17 -- 1994 970 1111001010 -54 Feb 24, 2026
2020-07-16 -- 1995 971 1111001011 -53 Feb 23, 2026
2020-07-04 -- 2007 983 1111010111 -41 Feb 11, 2026
2020-07-04 -- 2007 983 1111010111 -41 Feb 11, 2026
2020-07-04 -- 2007 983 1111010111 -41 Feb 11, 2026
2020-07-02 -- 2009 985 1111011001 -39 Feb 09, 2026
2020-06-19 -- 2022 998 1111100110 -26 Jan 27, 2026
2020-06-17 -- 2024 1000 1111101000 -24 Jan 25, 2026
2020-06-16 -- 2025 1001 1111101001 -23 Jan 24, 2026
2020-05-28 -- 2044 1020 1111111100 -4 Jan 05, 2026
2020-05-24 -- 2048 0 0000000000 0 Jan 01, 2026
2020-05-21 -- 2051 X XXXXXXXXXX X MMM DD, YYYY
2020-05-15 -- 2057 9 0000001001 9 Dec 23, 2025
2020-05-15 -- 2057 9 0000001001 9 Dec 23, 2025
2020-05-13 -- 2059 11 0000001011 11 Dec 21, 2025
2020-04-28 -- 2074 26 0000011010 26 Dec 06, 2025
2020-04-07 -- 2095 47 0000101111 47 Nov 15, 2025
2020-04-05 -- 2097 49 0000110001 49 Nov 13, 2025
2020-04-05 -- 2097 49 0000110001 49 Nov 13, 2025
2020-03-27 -- 2106 58 0000111010 58 Nov 04, 2025
2020-03-26 -- 2107 59 0000111011 59 Nov 03, 2025
2020-02-25 -- 2137 89 0001011001 89 Oct 04, 2025
2020-02-12 -- 2150 102 0001100110 102 Sep 21, 2025
2020-02-06 -- 2156 108 0001101100 108 Sep 15, 2025
2020-01-03 -- 2190 142 0010001110 142 Aug 12, 2025
2019-11-01 -- 2253 205 0011001101 205 Jun 10, 2025
2019-07-10 -- 2367 319 0100111111 319 Feb 16, 2025
2019-04-10 -- 2458 410 0110011010 410 Nov 17, 2024

/s.

This would explain my 2069d and 13 Dec 2025 due date. You might be onto something

 

[Keato]

Here is a summary of all the posts to date (through post 658). I have categorized significant posts by users into three groups: Symptoms, Proposed Causes and Proposed Solutions. When a reference is helpful, I call out the first user I noticed to post the information and link to their post.


SYMPTOMS

- An error message was first seen on January 1, 2026. It may have first appeared at 0000 GMT (@Logsplitter, post 79) or 0100 GMT (@scottg , post 467) and update at this time every day.

- The reported error message is formatted on the main screen as . . .

"Service overdue ####d" in the United States
"Service overdue #### Day" in Australia, UK, Belgium and Indonesia
"Wartung überfällig ####d" in Germany (although some displayed in US English)
"Mantenimiento vencido ####d" in Spain

. . . where #### is a number between 1492 and 2668 with one report of 6410 (@rwhitinger , post 321). Many of these reports have not been normalized to days overdue on January 1, so the actual service overdue offsets likely vary slightly with the reporting date.

- On January 1, 2026, some (but not all) vehicles with the date set to automatic had their date reset to January 1, 2032. Note this is SIX years ahead and not five as some have posited. (first mention of 2032 by @grond , post 6).

- Three users report no error message (@Steve.B , @badr and @Jean Mercier , all with 2023 model years). (Can't find user @badr - German language forum?)

- Several reports of heater controls also affected, but these appear to be unrelated (@rickydoc , post 250; @Baron von Teuchter , post 288). One user reported heated seats also did not work (@ORSO , post 297).

- At least one report of Android Auto also affected, but later resolved by setting the date to auto (@mirwantandyo , posts 485, 487).


PROPOSED CAUSES

These proposed causes cannot be proven or disproven with the current data set:

- There's a bug in the library of functions used for the firmware (@Korg , post 36). Neusoft supplies the infotainment system (@Clark Kent , post 380).

- There's a bug in the AUTOSAR Classic software provided by Bosch subsidiary ETAS that adds 2050 days of time to the service overdue counter (@Keato , posts 611, 614).

- A bit overflow for 11-bit or 12-bit variables (@HereinDaRockies , post 231).

These proposed causes do not explain all the data submitted by users:

- Errors in converting binary numbers (@Glen , posts 151, 185).

- Five years was erroneously added to the correct service due date (@scottg , posts 418, 459; @Glen , posts 490, 550; @Michael H. , post 527).


PROPOSED SOLUTIONS

There is only one solution that currently works:

- When the error message is displayed, suppress it for the current session by clicking the button on the end of the indicator stalk twice. (@Itsdchz , post 56; @IG Pop , post 639). Some users report having to click three times (@Glen , post 647).

Here are solutions that could be applied by a dealer:

- Have the dealer reset the service interval. Some customers had this done until Ineos issued guidance to not do this until the root cause has been corrected. (@Green Gren , post 433; @RY-Journeyman , post 549; @n545ca , post 557).

- Ineos later issued guidance that if service is due, go ahead and have the service performed and the service reminder reset. Ineos says this will "remove the message permanently." (@IG Pop , post 639).

Here are other proposals which do not work :

- Use a BMW reset tool to reset the service reminder. This has been thoroughly debunked in other threads.

- For those with an automatic date set to 2032, setting the date to manual then back to automatic produces a correct date display. This does not resolve the service overdue error (@Keato , post 614).

- Changing the date to manual and setting it to a date in 2025 does not resolve the problem. (@nathanwind , post 178).

- A reboot of the head unit does not help (@TheDocAUS , post 55).

- Manually set the date to 2026, turn the vehicle of and lock the doors, come back 30 minutes and the service due error is resolved. This does not work. (@scottg , post 515; @Glen post 528).

<end of text>

A correction to this summary: I’m not saying the bug is in AUTOSAR Classic. It’s more likely in the app layer. Otherwise it would be affecting many other big brands

 

[RY-Journeyman]

You are either completely oblivious or an Ineos rep.
Heater issues
Battery Drain
Battery not charging
Car Play/ Android Issues
Can’t Reset service indicator
Problems with tail lights
ADAS

To name a few “issues” with the software.
Why you choose to be ignorant if those issues is anybodies guess

I can assure you I’m an Ineos proud owner not an agent of the dark side . First one to buy in Townsville North Queensland. And I am a medical specialist - radiologist, not an Ineos rep.

I have very little trouble with hvac other than a bit of condensation on the external due to 100% humidity sometimes where I live.

I have zero battery drain issues. I parked in airport car park for a month and came back to 68% battery level. My battery has always charged fine and usually sits at 98-100%.

I had a minor condensation issue causing puddling in the passenger footwell which was rectified by a bit of pipe lagging from the dealer.

My apple car play works fine. Never tried it with android.

I live in the land of the free - Australia. No ADAS - so can’t comment.

My tail lights are fine.

I can’t reset my service indicator on the Ineos. Same as I can do it on my Mercedes, my BMW, my VW, my Mitsubishi or my mini. What is the point you’re making buddy?

Sounds like you got a Friday lemon. If you want my advice you should invoke your lemon laws and buy a nice Honda or Toyota instead. They apparently have reliability oozing out of them, no unique undocumented features and very happy owners according to the ads.

I’m happy with my vehicle - drove it for 2+ years here in Australia. I hired one in namibia and thrashed the living daylights out of it for 3 weeks without a single flaw even when jumping 40m (100+ freedom units whatever that is) sand dunes and fully laden. I also did a sand driving course with the crew that managed and drove vehicles in the desert for the mummy and mad max movies. They loved my Ineos. I like it so much I’m moving country to another land of the free - New Zealand - and taking it with me.

Sorry you’re not having same enjoyment from yours buddy. I love mine.

An observation. Misery loves company. But there’s no company from me in this instance. I do however wish you the best of luck.

 

[IslandFalconer]

I can assure you I’m an Ineos proud owner not an agent of the dark side . First one to buy in Townsville North Queensland. And I am a medical specialist - radiologist, not an Ineos rep.

I have very little trouble with hvac other than a bit of condensation on the external due to 100% humidity sometimes where I live.

I have zero battery drain issues. I parked in airport car park for a month and came back to 68% battery level. My battery has always charged fine and usually sits at 98-100%.

I had a minor condensation issue causing puddling in the passenger footwell which was rectified by a bit of pipe lagging from the dealer.

My apple car play works fine. Never tried it with android.

I live in the land of the free - Australia. No ADAS - so can’t comment.

My tail lights are fine.

I can’t reset my service indicator on the Ineos. Same as I can do it on my Mercedes, my BMW, my VW, my Mitsubishi or my mini. What is the point you’re making buddy?

Sounds like you got a Friday lemon. If you want my advice you should invoke your lemon laws and buy a nice Honda or Toyota instead. They apparently have reliability oozing out of them, no unique undocumented features and very happy owners according to the ads.

I’m happy with my vehicle - drove it for 2+ years here in Australia. I hired one in namibia and thrashed the living daylights out of it for 3 weeks without a single flaw even when jumping 40m (100+ freedom units whatever that is) sand dunes and fully laden. I also did a sand driving course with the crew that managed and drove vehicles in the desert for the mummy and mad max movies. They loved my Ineos. I like it so much I’m moving country to another land of the free - New Zealand - and taking it with me.

Sorry you’re not having same enjoyment from yours buddy. I love mine.

An observation. Misery loves company. But there’s no company from me in this instance. I do however wish you the best of luck.

Typical, because you are happy and have had no issues, and you don’t mind the issues you’re basically saying everyone else who’s not pleased with this BS somehow should jus suck it up and deal because you don’t see it as an issue. Dude if your X-Ray machine acted half as bad as these trucks you’d be screaming to your union rep.

 

[OkGo]

This

Automotive Software | QNX

Boost automotive software safety, reliability, and security with QNX. Explore our platform for cars and light trucks built for real-time performance.

qnx.software

Qnx is just a base platform that will boot and maybe meet some functional safety pieces. You still need to build all the actually management software on top of it.

 

[ADVAW8S]

Despite your ad hominem attack, sure, I can provide an example.

I worked as an air traffic controller for over 25 years at Anchorage ARTCC. By area, Anchorage ARTCC is the largest en route air traffic control facility in the world, with over 33 million square miles of airspace. Our airspace starts at the north pole and is bounded by Canada to the east, Russia and Japan to the west and the Pacific Ocean to the south. This facility controlls traffic in and out of all the airports in Alaska, but also controlls a very large portion of the air traffic flying between North America and Asia.

Up until the late 1990's, en route aircraft were separated vertically by 1,000' up to FL 290 and by 2,000' above that. Procedures - both domestic and by international treaty - dictated that eastbound aircraft would be assigned odd altitudes up to FL 290, then every 4,000' above that. So eastbound altitudes were FL 290, 330, 370, 410, 450 and so on. Westbound altitudes were even up to FL280, then FL 310, 350, 390, 430 and so on. This standard was established for and applied to all aircraft with altimetry certified for IFR under their country of registration's regulations. In other words, all aircraft had altimeters that were accurate enough that when a 2,000' vertical separation standard at FL 290 was applied, even the worst altimeter would not result in two aircraft colliding due to the lack of vertical separation. For an application of this standard, imagine an aircraft flying westbound at FL 310 passing directly below another aircraft flying opposite direction on the same route at FL 330. They'd be separated by a pressure altitude of 2,000'.

Beginning in the early 2000's, technology had advanced enough that precision altimetry, autopilot systems that hold a specified altitude and collision alerting systems (onboard aircraft) had advanced enough that 1,000' vertical separation criteria could be safely applied between properly equipped aircraft above FL 290. Take note of the caveat "properly equipped aircraft" because it's hugely important. Many areas of Anchorage ARTCC at the time had no radar (or other surveillance) and either poor on no direct radio communicatons between air traffic controllers and aircraft. One such area was a nonradar and no radio route segment where aircraft left Canada and flew into Alaska over Yakutat. Aircraft here flew for nearly an hour without any radar surveillance and no direct radio communication with air traffic control. Their position, route, assigned altitude, aircraft type and navigational equipment capabilities were recorded by hand on paper strips about 1-1/2" high and 7" long. As a controller at Anchorage ARTCC, I'd have a paper strip for each aircraft showing it's last position report in Canada and an estimate for when it should show up on my radar about an hour later over Yakutat. There might be 6 or 8 aircraft flightplanned east or west over Yakutat at any one time.

One auspicious day, the facility manager and the union president (representing the controllers) made the surpise announcement that we would now be separating aircraft on the route over Yakutat by a new standard called RVSM that allowed 1,000' vertical separation. This would allow many more aircraft to be on the same (or opposite route) since you could have one aircraft every 1,000' vertically instead of every 2,000'. This would alleviate congestion at airports as far east as New York and points farther west. "Oh, and by the way, you'll still need to apply 2,000' vertical separation to any aircraft not equipped to the RVSM standard," they said.

This announcement was met with consternation from a fair number of controllers. On midnight shifts, this route was worked by just one controller. In addition to this route, this controller would also be respsonsible for providing nonradar (no radar surveillance) approach control services in and out of at least three active airports in southeast Alaska as well as radar sequencing aircraft in and out of Anchorage from the east, all while monitoring/using more than a dozen VHF / UHF radio frequency pairs. In case it's not clear, that's a lot. And for a dirty little aviation secret, tired, sleep-deprived controllers and pilots working the midnight shift aren't the sharpest knife in the drawer, if you get my meaning.

The problem with this new procedure was that the east and west altitudes now worked out like this (I'll just go up to FL 450):

East - 290,     310,      330,      350,      370,      390,      410,      430,    450,   ... and so on
West -     300, 310, 320,      340, 350, 360,      380, 390, 400,      420,     440,       ... and so on

I've aligned the two rows to make it easier - can you see the problem here? That's right, some opposite-direction aircraft will be at the same altitude. In nonradar environments, and especially where there is no direct radio communications between a controller and a pilot, vertical separation is a CORNERSTONE of safe air traffic control. I can't stress this enough . . . vertical separation in these cases is like a commandment handed down from the air traffic control gods . . . you don't violate this tenet.

But - and here's your example @Zimm , the facility chief and the union president told all of us controllers it would be very easy to avoid any problems. "Just look at the aircraft equipment suffix, then apply the appropriate vertical separation minima to each aircraft," they said. I and others pointed out that aiming opposite direction aircraft at each other at the same altitude on a route where there was no radar, no direct comm and nothing other than occasionally imperfect people to detect imminent collisions was extraordinarily dangerous. "Nope," they said, "it'll be easy."

I wrote a letter to my senator and explained that my employer was making a very foolish decision regarding the partial implementation of RVSM (the new 1,000' vertical separation criteria) and putting people's lives in danger. I wasn't fired only because my right to communicate with my senator was legally protected. The senator's staff wrote my employer and asked the very same people implenting this reckless program if there was any problem. Of course, they replied "No - all good here."

Within a year, a controller (not me) made a mistake and two opposite-direction aircraft at the same altitude near Yakutat and not within radar coverage had to take emergency evasive action to avoid a mid-air collision. Blame here was assigned to the controller for failing to identify the conflict. True . . . but entirely predictable. I wrote my senator again and said "Do you remember that bad thing I said would probably happen? Well, it happened. Will you do anything to help now?" I went on to explain that if those aircraft had actually collided, they and the nearly 1,000 passengers would have plunged into the dark, icy and completely inaccessible glaciers and ice fields north of Yakutat where Mt. St. Elias rises to 18,000 feet. Rescue, let alone recovery, would have been impossible . . . actually impossible. So the senator's staff again wrote the very same people responsible for implementing this program and asked if there was a problem. Of course, they replied "No - all good here."

There were several other close calls where controllers made "mistakes," although I'm not sure that's the right word when the game is rigged against you. Eventually, all aircraft were required to have RVSM equipment and the result was that no more aircraft were head on at the same altitude. East altitudes were all odd and west altitudes were all even once more.

@Zimm , I know you're on the edge of your seat by now. You might ask why the facility manager and union president were so eager to cast the solution to an extraordinarily complex problem to be something as simple as "Just look at the aircraft equipment suffix (you dummy), then apply the appropriate vertical separation minima to each aircraft." Well, it turns out RVSM had never been implemented in any United States air traffic facility before this, and reports suggest our manager wanted to be the first. He was, and it was quite a feather in his cap, no doubt affecting his career in a very positive and predictable manner. When the facility manager asked the controller's union president to agree to a new procedure for RVSM (required by the collective bargaining agreement), the president didn't want the people he represented to be cast as stupid or inept, so he agreed without the least hesitation.

So there you go. People suggesting simple solutions to complex problems often have a motivation other than the best outcome. The facility manager and union president survived their decision by sheer outhouse luck . . . not because they took the time to do the hard work of developing, testing and implementing what would have no doubt been a much more complex solution to a complex problem.

<end of fun and almost nearly very tragic story>

p.s., The senator in this story died about 10 years later . . . in an aircraft accident.

And that senator had airport named after him. Be up there in Feb.

 

[TheDocAUS]

TALLY (updated and complied by the unpaid expendable gofer*)
Krabby 1492 days
ResponsiblyReckless 1625 days
Chook 1840 days
anti 1841 days
Itsdchz 1841 days, first US car with the pox
Dlucky 1851 days
BrandonADV 1852 days
TahoeGren 1852 days
Rocky 1856 days
Bjoern 1864 days
Znarfgh 1864 days
PB60 1865 days
Pat-Ard 1868 days
Rok Dr 1869 days
Tx246 1872 days
WanderingSniper 1872 days
Malkay 1875 days
Sonoranrover 1875 days
linksk9rig 1877 day
BluDawg 1879 days
Shopkeep 1879 days
rabia 1879 days
XxShantilisxX 1880 days
mji111 1880 days
PNW IG 1881 days
csjeeper 1884 days
donnygreygrenadier 1885
Michael H 1889 days
Guy 1890 days
Robt 1890 days
Chem409 1890 days
Blackwolf 1891 days
Duncan McDonald 1892 days
Deon 1893 days
joejet 1894 days
grnamin 1897 days
TimeosYoc 1899 days
Korg 1899 days
LPT FSJ 1900 days
GrenADV 1901 days
Green Gren 1903 days
stefan.schaefer.de 1906 days
Grumpy 1906 days
crashnburn 1908 days
HeavyFoot 1915 days
pedrogb 1915 days
Tom Ireland 1916 days
FlyersFan76 1917 days
Jax F1 Dave 1917 days
Old Salt 1919 days
Woody 1919 days
UncleBuck 1924 days
Force Pro 1924 days
Voader O 1925 days
OGrid 1927 days
singlefin 1927 days
Green 1928 days
DrahthaarGuide 1929 days
WhiteBear 1931 days, first car outside ANZ
ecohen2 1932 days
oilpresuure 1933 days
Forefun 1933 days
Happyoldgit 1933 days
DaveB 1935 days
OkGo 1937 days
prezioson 1940 days
NixGrenadier 1940 days
Rupert 1941 days
Gerrymac 1944 days
Peterr's neighour 1944 days
ddv 1945 days (Aug 2023)
Tergosa 1946 days
Rudilf 1948 days
Johnb 1950 days
Fred 1950 days
pmatusov 1953 days
Antgil 1953 days
TheBMcCann 1953 days
Camilondo 1953 days
nr002 1954 days
Knoe 1955 days
rickydoc 1961 days
Peterr 1961 days
IG Pop 1967 days
Jeremy966 1967 days
Ex-defender driver 1968 days
TheDocAUS 1968 days (Feb 2024)
shekesc 1969 days
SilverNZ 1971 days
Joe B 1971 days
Denis M 1975 days
Augustin 1979 days
Telliottaus 1980 days
rwhitinger's better half 1981 days
Zimm 1982 days
OZZA 1987 days
joejet 1989 days
Mohs9 1989 days
MattG 1989 days
Jonnieblaze 1950 days
TJD 1985 days
Phred 1994 days
douggie 1995 days
Isle of Wight Paul 1996 days
Phud 1996 days
Bluesmurf 2003 days
Des Mattes 2003 days
Glen 2007 days
Badger4x4 2007 days
Adam 2007 days
snowball 2009 days
Baron van T 2009 days
Tomdoc 2016 days
gratefuldiver 2021 days
Silverjay 2022 days
Sully 2023 days
BEM-S4 2024 days
theox 2024 days
Chris Hilton 2024 days
Tony H 2025 days
SaudiGR 2026 days
Sylvan 2032 days
Landmannn 2044 days
Oscar786 2045 days
acky 2048 days
n545ca 2050 days
Logsplitter 2051 days
Commodore 2057 days
NeoGTi 2057 days
HelgeL 2059 days
Greasemonkey 2059 days
SD Jeff 2063 days
Keato 2069 days
Lollo050968 2074 days
bemax 2078 days
255/85 2080 days
HessenHUnter 2081 days
Citori21 2081 days
bakepl 2082 days
MurphyMurph 2085 days
McPharmerII 2088 days
Barney 2091 days
LeeroyJ 2093
Wile E Coyote 2095 days
DrewB 2096 days
Dschubba 2097 days
Stu Barnes 2097 days
Manuel4x4 2106 days
Mazeman 2107 days
Jork 2113 days
Zenadier 2114 days
KlasN 2123 days
Wueste 2123 days
Brock63 2124 days
Tazzieman 2137 days
skinny tom 2139 days
Tenac loaner 2139 days
Phobiac 2141 days
ChrisRay 2141
archerwolf 2146 days
pipo 2149 days
Skymark 2156 days
ADVAW8S 2159 days
Ever Pragmatic 2141 days
Grenni-Tom 2153 days
Bayford 2162 days
StKesseler 2171
slukell 2175 days
Island Falconer 2178 days
wolftimj 2183 days
Emil 2190 days
emax 2233 days
bigleonski 2250 days
Ron50 2253 days
Torc Steel 2277 days
Bobineos 2188 days
Mulekick406 2297 days
Clark Kent 2367 days
tnkatoy 2362 days
C-Mack 2458 days
Jorda 2503 days
DeepCJ7 2651 days
mirwantandyo 2668 days
rwhitinger 6410 days

SUMMARY
184 members and an additional 3 members with no alert (4 if you include some chap in Townsville).

No change to first or last place. A photo is needed if you are claiming a new low or new high.

DO NOTHING FOR THE MOMENT

Post in thread 'New Year Service Overdue Bug'

Monday at 1:35 PM

I spoke with my Australian service manager today (my last few days here in AU). He said Ineos had advised them not to reset the service warning just yet as they don’t yet know what caused the fault so don’t know how long the reset would last or what else it might screw up if the service people simply just reset it. Although the mechanics already had reset some local customers they won’t do any more until they get the green light or a fix from Ineos.

• RY-Journeyman

• 
• 
• 

* Wednesday's unpaid expendable gofer.

View: https://youtu.be/F9CdkjLrEt8

 

[FlyersFan76]

My '26 loaner does not have the reminder. The GMT was set to 0 and the year was 2032 I believe.

 

[FlyersFan76]

Qnx is just a base platform that will boot and maybe meet some functional safety pieces. You still need to build all the actually management software on top of it.

Correct. QNX is what most brands are using. Rivian included. From what I have read Neosoft (sp?) is not using QNX's products as a base OS.

 

[ADVAW8S]

@TheDocAUS I'll throw you some few bucks for all your hard work. Enough to get Ms. Gofer something special.

 

[GMAN0911]

2024 Trailmaster. Texas, USA. Experiencing the same issue. I do not reside near any INEOS dealers. Any help would be appreciated.

 

[Zenadier]

Does Ineos truly mean permanently in Scenario 1?

Scenario 1 - if your vehicle is due for a service now, you can proceed with the service as usual. The service counter will be reset and that will remove the message permanently.

When it works properly, the Service Overdue warning can be helpful. Fix it; sure. Delete it; really? Can't be. Is this a rushed statement by an expert? (Former drip under pressure.) Is Scenario 2 rendered pointless? Sorry, that's what I get when I see remove permanently. On our way to 1000.

 

[Glen]

Does Ineos truly mean permanently in Scenario 1?

Scenario 1 - if your vehicle is due for a service now, you can proceed with the service as usual. The service counter will be reset and that will remove the message permanently.

When it works properly, the Service Overdue warning can be helpful. Fix it; sure. Delete it; really? Can't be. Is this a rushed statement by an expert? (Former drip under pressure.) Is Scenario 2 rendered pointless? Sorry, that's what I get when I see remove permanently. On our way to 1000.

I wondered about that too. They'd have to know the nature of the problem to make such a statement with confidence. That could mean the final - and least expensive - solution is to have your service remider reset at your next scheduled service.

 

[BrandonADV]

2024 Trailmaster. Texas, USA. Experiencing the same issue. I do not reside near any INEOS dealers. Any help would be appreciated.

when the message pops up, hit the trip button on the end of the turn signal stalk twice. The message is harmless, just an annoying bug when you first start driving the vehicle. Whenever Ineos comes out with an update to fix it, you'll have to travel to the dealer. Or just learn to live with it.

 

[Zenadier]

Everything is speculation when it comes to anticipating IA software work. I suspect that Scenario 1 was hastily written and that IA is doing everything possible to restore normal functionality of the service warning. If a dealer resets your warning counter in the normal manner, then Ineos has until 1 January 2027 to install a fix, I suspect. No problem, right? Oh wait, (...remember adas).

I know nothing authoritative about any of this.

Another option, without needing to understand the problem, is that they are considering disabling the service counter altogether forever. I don't know about the legal ramifications of that. This solves the current overdue warning AND gets owners off their back regarding the inability to self-clear (reset) the overdue warning. Similarly, if they understand the problem well enough now to foresee a doomsday solution path of big bucks and a timetable of over one year, then toggle off the warning completely and be done with it.

 

[Zenadier]

...

But, why don't they also put the same message on this forum? Is this forum not important for Ineos, or perhaps a pain in the ass?

I also wondered why Ineos Automotive would make their online media announcements on Facebook (maybe other places), but exclude this forum. I thought for sure I'd see the most recent announcements here at theineosforum.com.

After all, we had those LC interviews and my favorite, the INEOS Automotive AMA (ask me anything) forum. Love lost?

Suggestion - @Stu_Barnes

Could you make a place for IA to post announcements here in the forum? You'd have to ensure it is read only for members and make that a guarantee to Ineos. But why not? Get the love back. Thanks Stu.

 

[IslandFalconer]

I also wondered why Ineos Automotive would make their online media announcements on Facebook (maybe other places), but exclude this forum. I thought for sure I'd see the most recent announcements here at theineosforum.com.

After all, we had those LC interviews and my favorite, the INEOS Automotive AMA (ask me anything) forum. Love lost?

Suggestion - @Stu_Barnes

Could you make a place for IA to post announcements here in the forum? You'd have to ensure it is read only for members and make that a guarantee to Ineos. But why not? Get the love back. Thanks Stu.

I have not much love for the company at this point. There was thus initial responsiveness from LC, but that faded as quickly as it started.

 

[anand]

Could you make a place for IA to post announcements here in the forum? You'd have to ensure it is read only for members and make that a guarantee to Ineos. But why not? Get the love back. Thanks Stu.

Stu can answer more in depth and concretely, however, to the best of my knowledge that ability was made available to IA corporate quite a while ago

 

[Emil]

Everything is speculation when it comes to anticipating IA software work. I suspect that Scenario 1 was hastily written and that IA is doing everything possible to restore normal functionality of the service warning. If a dealer resets your warning counter in the normal manner, then Ineos has until 1 January 2027 to install a fix, I suspect. No problem, right? Oh wait, (...remember adas).

I know nothing authoritative about any of this.

Another option, without needing to understand the problem, is that they are considering disabling the service counter altogether forever. I don't know about the legal ramifications of that. This solves the current overdue warning AND gets owners off their back regarding the inability to self-clear (reset) the overdue warning. Similarly, if they understand the problem well enough now to foresee a doomsday solution path of big bucks and a timetable of over one year, then toggle off the warning completely and be done with it.

I suppose their copywriters’ use of language is imprecise or incorrect, caused by internal reorganisation and cost-cutting. For example, only recently IA published a LinkedIn post advertising the QM stating that it had “a 225 kg loading bay.” What was actually meant was that the tailgate can support a load of 225 kg which is indeed impressive. Nobody would buy a pickup truck that can carry only 225kg, but that is what was posted in IA‘s name…

 

[255/85]

I can assure you I’m an Ineos proud owner not an agent of the dark side . First one to buy in Townsville North Queensland. And I am a medical specialist - radiologist, not an Ineos rep.

I have very little trouble with hvac other than a bit of condensation on the external due to 100% humidity sometimes where I live.

I have zero battery drain issues. I parked in airport car park for a month and came back to 68% battery level. My battery has always charged fine and usually sits at 98-100%.

I had a minor condensation issue causing puddling in the passenger footwell which was rectified by a bit of pipe lagging from the dealer.

My apple car play works fine. Never tried it with android.

I live in the land of the free - Australia. No ADAS - so can’t comment.

My tail lights are fine.

I can’t reset my service indicator on the Ineos. Same as I can do it on my Mercedes, my BMW, my VW, my Mitsubishi or my mini. What is the point you’re making buddy?

Sounds like you got a Friday lemon. If you want my advice you should invoke your lemon laws and buy a nice Honda or Toyota instead. They apparently have reliability oozing out of them, no unique undocumented features and very happy owners according to the ads.

I’m happy with my vehicle - drove it for 2+ years here in Australia. I hired one in namibia and thrashed the living daylights out of it for 3 weeks without a single flaw even when jumping 40m (100+ freedom units whatever that is) sand dunes and fully laden. I also did a sand driving course with the crew that managed and drove vehicles in the desert for the mummy and mad max movies. They loved my Ineos. I like it so much I’m moving country to another land of the free - New Zealand - and taking it with me.

Sorry you’re not having same enjoyment from yours buddy. I love mine.

An observation. Misery loves company. But there’s no company from me in this instance. I do however wish you the best of luck.

Take me with you.

I've had two semi-serious offers that might have allowed me to immigrate to NZ. Kinda starting to kick myself.

#780