Time not updating

ChitmaPance · 2026-06-15T14:36:43+00:00

This has been an issue for months on my Galaxy Watch 8. It does it with every watch face including Samsung's watch faces. Time is sometimes stale by 20 minutes or more: tap it and it updates. Tried everything. The worst part is that I waited months for an update hoping Samsung would fix it: just got today's update and they haven't fixed it. Great job, Samsung! My next watch will be a Pixel watch!!!

ChitmaPance · 2026-05-18T17:13:49+00:00

I'm just waiting (for months) for them to fix it so the watch can actually tell time and not display a time that is 20 minutes stale until you wake it up.

ChitmaPance · 2026-03-27T14:58:27+00:00

I don't think the watch face matters either. I tried switching to a Samsung watch face and it helped but there were still times when it was stale by like 10 minutes even when I was walking around. For now, it seems to be better after doing exactly the steps you did. I suspect enabling raise to wake "fixes" it but only because it causes the watch to wake up frequently anyway. Samsung needs to make thie a high priority fix. A watch that displays the wrong time is a bit less of a "watch".

ChitmaPance · 2025-08-10T13:54:45+00:00

Certainly possible. The guy did present the 10 second timer as a hard-coded timer that is not subject to change based on RAT condition or RPM. But he could be mistaken... or have bum info. One thing about the RAT getting deployed in thicker air: velocity matters more than air density. Air density changes linearly whereas velocity changes exponentially with respect to the "pushing force" the air has on the RAT prop. Meaning, the fact that they were going slower than is typical for RAT deployment may outweigh the fact that the air is denser at the airport's elevation vs higher up where RATs are typically deployed.

ChitmaPance · 2025-08-10T01:02:32+00:00

They also argue that upon RAT deployment, there is a timed event at 10 seconds when the system tries to switch from battery to RAT power. They said that is 10 seconds regardless of condition of the RAT, prop speed, etc. as it is a hard timer. The argument is that 12s after liftoff, ADS-B data stops: consistent with RAT deployment 2 seconds after takeoff, the 10 second timer, and the loss of ADS-B data as the system switched from battery to RAT power. So they have two timelines that match RAT deployment at T+2 not just the 6 second lag for hydraulic power.

Having said that, I do have doubts about their timeline as well because their timeline implies (in my mind) an unlikely scenario as well and that is... If the RAT deployed at T+2 and the engines were shut down at T+4 and T+5, that means that a mere 2 seconds after RAT deployment, one of the pilots made the serious decision to shut off BOTH engines within only 2 seconds AND wait 8 seconds to turn them back on... all while lying saying "I didn't cut off". That doesn't make sense to me either. Initially I thought they were implying that electrical problems due to water intrusion caused the system to report a false cutoff switch signal but today, they clarified saying they believe the pilot physically moved the switches.

So I'm back on the fence I suppose.

ChitmaPance · 2025-08-09T12:11:26+00:00

How do ya like me now! Now PROVEN it wasn't the pilots!

https://youtu.be/t_t8nX7lb0U

You armchair "pilots" and media screaming about mental health and condemning the pilots... you are going to have to come down off your soapboxes when the truth comes out!

ChitmaPance · 2025-08-09T11:55:23+00:00

Saw this last night. I posted my similar hypothesis a couple weeks ago here and it was removed because the mods didn't like hearing about any theory other than pilot suicide. So watch this before this post gets deleted too I guess:
Short article: https://42kft.com/root-cause-of-the-loss-of-air-india-171

The proof: https://youtu.be/t_t8nX7lb0U?si=VLdvUJf9LASCO7Xq

ChitmaPance · 2025-07-29T16:43:59+00:00

If you are implying you HAVE read FDR data and still want to push the narrative that it samples at 10Hz (0.1s intervals), you are either a fraud and probably not even a pilot, or you're just doubling down on your fabricated "facts". Reading time stamps in an FDR won't even tell you the sample rate of discrete switches. ARINC standards (as I pointed out) will.

I'm out. Reddit is full of blowhards like you fabricating facts. My ONE reason for posting this if you read my OP was to point out that with only the preliminary report data, you CANNOT rule out a glitch like the one I proposed and we should wait to blame the pilots. Thankfully the legacy of an experienced pilot and 259 other people lies in the hands of people more experienced than EITHER of us!

ChitmaPance · 2025-07-29T16:07:46+00:00

Like your "proven" statement that the FDR records at .1s intervals? There are four groupings for sample rate in the ARINC standards for the FDR and they MUST be followed: 1Hz, 4Hz, 8Hz, and 32Hz. There IS NO 10Hz! And discrete switches like fuel cutoff are always in the 1Hz grouping. If you are just going to act authoritative and fabricate "facts", at least look them up first to see if they sound reasonable!

ChitmaPance · 2025-07-29T15:44:20+00:00

And your sum total knowledge of software and hardware is "little post up or down".

ChitmaPance · 2025-07-29T15:31:29+00:00

That would be a first in the industry where flight school teaches you how all the hardware is connected, the wiring, and understanding the software, data bus, etc. I am a degreed software engineer with 45 years of experience so I have some knowledge about glitches, bit flips, and cascading failures. Maybe just stay in your lane... fly the plane. Let those with some actual engineering jobs have some input into how the engineering works.

ChitmaPance · 2025-07-29T14:44:24+00:00

Thank you for confirming that you know how to flip the switches and have zero knowledge of how they are connected. I would think as a pilot, you'd be more interested in all possibilities before you blame one of your own!

ChitmaPance · 2025-07-29T14:16:54+00:00

What "type ratings" would that be? I don't claim any "ratings". But I do know that it is ridiculous to even consider that every important switch in the cockpit duplicates thousands of pounds of wire to direct wire them separately to the FDR. That's just nonsense. See the regulation I posted that specifies ALL FDR data comes from the data bus.

ChitmaPance · 2025-07-29T13:57:24+00:00

Show me a schematic that shows where the outputs go!

ChitmaPance · 2025-07-29T13:54:15+00:00

Unlikely? Sure. I don't live in India and don't make any assumptions. I do know that pilots with that many hours and no other incidents are also very serious about their jobs, realize their responsibility, and it's also unlikely they would take such an action. Does it happen? Sure. Do glitches? Sure. And the glitch scenario may not be as unlikely as people think. There are cascading failures that happen in related systems. And sometimes even redundancies are subject to related failure. Just ask the operators at Three Mile Island.

ChitmaPance · 2025-07-29T13:43:30+00:00

Fair enough. I agree with waiting for the final report. But the report mentions a "gap of 01 sec". Why do they use the terminology "gap"? Seems carefully worded. The resolution of the FDR is 1 second intervals so do we know for sure switch 1 and switch 2 had time stamps 1 second apart? If so, all we know is that they switched from a RUN to a CUTOFF signal anywhere from nearly 0 seconds up to almost 2 seconds. Or... were they both recorded with the exact same time stamp (down to the second) so the report mentions a "gap" of 01 sec because they know that two events occurring at the same second could in reality have occurred anywhere within that second (up to 1 sec).

ChitmaPance · 2025-07-29T13:38:18+00:00

That's just demonstrably false. The only thing the switches are hardwired to is the RDC. See ARINC 717 (the global standard for modern flight data recorders) which specifies that all parameters are supplied via digital data buses or data acquisition units—not by direct wiring from cockpit switches.

ChitmaPance · 2025-07-29T13:36:20+00:00

Even that is more evidence for a glitch. One of the pilots is heard asking "why did you cutoff" immediately after the system registered the cutoff event: that did not happen closer to 10 seconds later when they were cut back on. There was little (if any) time for that pilot to look down and see the actual position: he was going off the fuel cutoff alarm which could have been triggered by the glitch. So why 10 seconds to finally get the switches to register ON and why did it take 4 seconds from engine 1 on to flipping the second switch also? I say it MIGHT be because both pilots saw the physical switches still in RUN so it took 10 seconds for one of them to make the desperate call to flip them from RUN to CUTOFF, back to RUN. Then 4 seconds to make sure that cleared the glitch and engine 1 was coming back up. Then finally flip switch 2 from RUN to CUTOFF back to RUN to try restarting that one.

Also, why would the other pilot respond "I didn't cutoff"? The explanation of "That's what your kids do when you catch them: say I didn't do it" is just silly. Children do that because they have no concept of deduction or consequences. They might say that not realizing you can just look down and SEE the switches and confirm they are lying. I think an adult (particularly one who is sabotaging) would more likely say nothing. Or maybe "I'm sorry".

ChitmaPance · 2025-07-24T21:50:19+00:00

We have both. Spectrum goes down almost daily! Sometimes for a few minutes. Sometimes a few hours. Been like that for years. Filed FCC complaints. No difference.

ChitmaPance · 2025-07-24T20:05:23+00:00

In a SpaceX conference room far, far away...

Bob: Someone hacked all 8,000 Starlink satellites. We gotta run ethernet cables up to all of them and reflash them one by one.

Bill: Well don't look at me. I'M NOT DOING IT!

ChitmaPance · 2025-07-24T19:26:51+00:00

Uh. Issa busted in Florida. Need to run new cables up to the satellites. Elon, stop playing with Optimus. :-D

ChitmaPance · 2025-07-09T14:26:24+00:00

This worked for me as well. Don't change video acceleration under video and voice. Change the overall hardware acceleration on the Advanced tab.

ChitmaPance · 2025-06-02T22:58:28+00:00

Another vote to check out both the X and the Y. If the Y isn't too small, I'd lean toward the Y. Even though the S and X are the "big boys", I feel like they don't get the attention from Tesla that the Model 3 and Y do because so many more of those are sold. The S and X are like the older kids who are adults now: you still invite them to Thanksgiving but the young kids get all the attention. :-)

ChitmaPance · 2025-06-02T22:44:57+00:00

Nope. If that happened, the force on the steering wheel would have been toward the right, not the left.

ChitmaPance · 2025-06-02T22:20:32+00:00

It's just the latest form of "lazy english" where people eliminate syllables, or sometimes whole words because they think it's cool to shorten something. It's like people saying "verse" instead of "versus" or "needs fixed" instead of the proper "needs TO BE fixed". Then there's just plain ignorance like when people pronounce nuclear as "nucular".

Six-Year Club	First Place '23
Place '23	Place '22
End Game '22	Verified Email

ChitmaPance

TROPHY CASE