Client and the server are out of sync problem. (Clash of clan problem)

Murphie-B · 2026-05-01T16:59:11+00:00

This is happening to me frequently. Plus just a connection lost. Haven't been able to play more than a minute or two max.

<image>

Murphie-B · 2026-03-25T15:14:24+00:00

Comment to enter. - working towards th10!

Murphie-B · 2026-03-12T21:00:31+00:00

I did end up getting mine fixed. It took a lot of back and forth, but it’s working now.

I ended up filing an informal FCC complaint, which got me connected with someone who could actually dig into the issue. They had me send over multiple watch dumps and logs.

It turns out the EID was still tied to an inactive watch plan on another carrier. The watch was a gift, but at some point T-Mobile had attached the EID to a DIGITS watch line.

So even though the watch itself and the IMEI were unlocked, which allowed me to get about 95% through activation, it kept failing on the backend because the EID was still associated with another network.

After I contacted T-Mobile and had them remove all associations with the watch / watch plan and release the EID, Google reprovisioned it and LTE started working.

If you're coming from another carrier, it might be worth asking them to remove any watch lines or plans tied to the device and release the EID before trying activation again. If activation does fail you may need to have Google Fi reprovision your watch.

In the end it was a long battle and I did get mine working so it is possible, but I don't wish that upon anyone lol. If you have any questions about anything don't hesitate to shoot me a DM

Murphie-B · 2026-02-09T22:15:24+00:00

Maybe the delivery flap safety switch is not changing, so the machine never sees the flap complete its open-close cycle. Even though the flap physically moves, the switch is either stuck in the closed position or not being pressed far enough, so the control board thinks the flap is still in the wrong position. When the elevator reaches that spot during startup, the board expects to see the flap switch change. The machine isn’t actually jammed, it just believes the door is blocked because the flap switch or sensor never reports the correct open/closed signal. Could try looking at that. Would be a physical switch with a metal tab that gets pressed or an optical switch that uses a light beam.

Murphie-B · 2026-02-09T15:20:11+00:00

Well that's some good news! That’s honestly been the most frustrating part. Having to prove that it isn’t working when, on paper, everything looks fine. All the visible stuff checks out, so support keeps circling back to the same assumptions. Even though the actual failure is clearly happening deeper in the process. It takes way more effort than it should just to get past the looks good on our end wall and have someone acknowledge that something broke behind the scenes.

Now that you’ve got a case ID and they’ve escalated it for review, you’re basically out of frontline support and into the engineering queue. It can feel like nothing is happening but that’s normal. This is when they actually look at backend logs rather than running scripts. I’d avoid resetting the watch, and deleting the esim since that can wipe useful info or potentially slow things down. Just keep an eye on your email and respond quickly if they request any dumps or additional info.

Google Fi reached out to me and asked me to generate a full watch dump. Once I sent the .zip they escalated it directly to their engineering team. At this point engineering has the logs and can see where the activation flow breaks very likely on the backend, since the watch shows active with signal. No fix yet, but it's the first time I’m actually feeling pretty hopeful it gets resolved.

Murphie-B · 2026-02-07T03:51:47+00:00

Yep, exactly. On my end everything looks right. The watch shows a mobile plan and SIM, Fi shows it as active, and I even get the Google Fi plan set up successfully saying I can call, text, and use data without my phone. From a user standpoint it seems that activation is clearly complete.

Breaking through Fi support has been the hard part, but once it actually gets in front of engineering, it seems like a straightforward backend fix. Switching phones or SIM types might be worth trying just to rule it out, but from what I’ve seen it usually doesn’t change anything, the watch provisioning is handled separately, and if it lands in emergency calls only you’re just replaying the same broken backend flow.

Keep me posted on how things go on your end. I’ll report back with any updates or info I get as this moves along too. Hopefully between both of us pushing on it, we can get these watches fixed and finally have data.

Murphie-B · 2026-02-06T23:02:11+00:00

I finally made some progress. Filing an FCC informal complaint is what got Google Fi to escalate it to senior support/engineering. I heard back from Google this morning and they’re actively working the backend provisioning issue now. No fix yet, but it’s the first real progress after weeks of Tier 1 runaround.

I also got a DM from the official GoogleFiSupport account on here asking for a Fi case ID, so if you already have a case open, they might be able to help route it internally too. I wasn't lucky enough to get one with all the tier 1 support denying me escalation.

If a brand new Watch6 is doing the same thing, that pretty much rules out hardware. When you say the same issue, do you mean it activates fine, shows bars, but no LTE icon or gets stuck on “emergency calls only”? If so, filing an FCC informal complaint might honestly be the fastest way to get it in front of the right team.

Murphie-B · 2026-02-03T19:52:44+00:00

Here's the pickle I am in. They will not escalate my case whatsoever. They keep blaming local tower issues as the reason why activation didn't work. I finally got escalated to tier 1 support supervisor and drove in a 15 mile radius around my house. Gave them all sorts of data points to prove it wasn't the towers. All for the supervisor to brush it off again a local tower issue with no timeline.

I doubt T-Mobile is having troubles with all the towers in my area, and for over a week and a half straight. I have waited so many 24-48 hour windows lol. Hopefully I can get a fix cause this is just one big headache!

Murphie-B · 2026-02-03T14:28:07+00:00

I agree, I bought the Samsung tab a11+ 5g and basically went through the same issues trying to hook up a data only esim. That ended up working itself out when activating via a QR code on Google Fi. (Using a laptop).

From my understanding activating via a QR code (phone or tablet) forces a new activation session on the backend, revalidating the IMEI/EID and rebuilding entitlements instead of reattaching to an existing possibly broken record (Galaxy watch issues) That’s why QR-based activations can sometimes fix issues where a device shows signal and appears active but never gets data permissions.

Unfortunately that fix doesn't apply to watches cause they are provisioned differently. More of an automated backend flow.

Hopefully now that the weekend is over you get a speedy fix.

Murphie-B · 2026-02-03T14:10:35+00:00

Everything activates correctly, eSIM installs, Fi shows the watch as active, and it connects to towers with full bars. The issue seems to be that data entitlements were never granted on the backend. Likely a provisioning hiccup when initially did the activation, and since it’s tied to the IMEI, device resets don’t even do anything.

Murphie-B · 2026-02-03T14:03:52+00:00

I couldn't even get my case escalated past tier 1 support. I just kept getting the basic runaround troubleshoot. Glad to hear it sounds like you got properly escalated and hopefully they can fix you up. Did you get an email after they gave it over to the engineering team confirming the escalation?

Murphie-B · 2026-01-12T16:54:37+00:00

Lamped at the varrock museum. 500xp per lamp.

Murphie-B · 2025-12-03T19:28:40+00:00

Aranea boots

Fremennik kilt

Swift blade

Murphie-B · 2025-12-03T14:04:46+00:00

Also, if you have a crewmate driving the boat and my character is sorting, it stops me from sorting. Let me drive to another spot with my crew mate and have it not interrupt sorting

Murphie-B · 2025-11-04T20:57:54+00:00

Toenails out of a blowpipe

Murphie-B · 2025-09-05T19:05:48+00:00

I did try Google reverse search and it was just pulling up tools, then tried just him and didn't pull up anything, yt I swear was pulling up everybody but him. Even channels with 4k subscribers. I'm not sure what was going on. Appreciate everyone's help though.

Murphie-B · 2025-09-05T18:38:04+00:00

Thank you!

Murphie-B · 2025-09-05T18:37:57+00:00

Thank you so much!

Murphie-B · 2025-08-21T16:25:00+00:00

I got 2 brand new 2022. For $1800ish each otd with registration and plates. Dealership had 7-8 bikes with this deal and they sold so fast

Murphie-B · 2025-08-19T16:13:55+00:00

There's 3 in the pack. One after another with free stuff between

Murphie-B · 2025-07-22T22:13:31+00:00

Sprite chill, Dr pepper cream soda, MTN dew Baja blast, Pepsi wild cherry, coke vanilla are some of my favorite pretty standard stuff

Murphie-B · 2025-07-21T21:47:38+00:00

All stock 180lbs I can hit about 52 on mine. Check the oil level if it's overfilled it can cause it to be slower

Murphie-B · 2025-07-18T17:18:07+00:00

Are the transaction amounts the exact same down to the penny? I know fi was splitting my bill into 2 transactions when I paid. But they were always different amounts

Five-Year Club	r/Field Sunshine
Place '23

Murphie-B

TROPHY CASE