Continuous chime when charging

Hey

I have also faced this issue but on a different scenario - you can follow the thread here: https://discussions.apple.com/thread/250650152?

Yes - the Apple £29 solved my issue and the aftermarket are now lying antique in my cupboard until next time :P

It took Apple 5 years to fix the timer bug for UK iPhone users (where it would display 00:00 on the lock screen). What needs to happen is for everyone to report this and not just put the watch into silent mode when you go to bed. When enough people report the issue, Apple will fix it. But in the mean time, the only fix is using a stainless steel magnetic watch charger.

We have 2 watch series 4 cellular

Same annoying problem on Both (and on our series 3 also) since the last update.

IT IS NOT HARDWARE, since they all started the annoying ding near morning.

Please apple get a grip and give us a solution.

The bing question : WHY IT NEED TO BEEP WHEN CONNECTING TO CHARGER ??? ANYONE

I can figure out it is charging without the beep

OR if you still want the beep shut it off when it is on the charger (Like an automatic theater mode )

I have a hard time comprehending how this is not at all related to hardware. Perhaps it's a software issue but only affecting certain batches or something? If it were just flat out software and had nothing to do with anything else, why would it affect my series 3, on one charger but not another charger? Why would my wife's series 4 not exhibit the problem on either charger we have? Why would my series 4 not show the problem on either charger?

Lastly, why aren't we seeing an enormous number of complaints? Seems to be isolated to only some people, which brings me back to- could it perhaps be somehow tied to a specific batch of some internal component causing the issue? Which was only affected after some kind of change in software that only now even let us know there is a hardware problem?

I'm most likely going to ask Apple to flat out replace both my watch and charger. No one is able to explain what the problem is other than "it's software", nor can they say if there are any implications to how this may or may not affect the longevity of the battery or other power components inside the watch. Without those answers, and without a fix- replacement seems like a reasonable request... thoughts?

I have had enough of not knowing if it’s the third party charger at fault. Today I find the watch having discharged 20% when it hasn’t left the charger. It’s always hot when I pick it up. Last night it even said it was too hot to enable cellular. So, I’ve ordered an Apple one direct from Apple due to arrive on Tuesday. I’ll come back and say if the issue has gone away.

you'll have to read between the lines when I say I know that the next update to WatchOS doesn’t deliver a fix for this IF it truly is software.

if the issue continues, with the genuine Apple charger, I’ll go to Apple for support.

I've been fighting (well HAD been fighting) this issue for quite some time. Began working with Apple support awhile back but they gave the run around and kept tasking me with busy work to try. I gave up and simply pull it off the cable middle of the night when it wakes me. They acknowledged there's a problem and that they have several reports, but gave no indication when it will be resolved. I have little faith they'll deal with it, that's the current Apple MO, do as little as possible and continue to ride the good named they used to be. They're too busy designing a way to shave .001mm of thickness form the next iPhone and designing new talking emojis. My wife and I both have Apple Series 3, mine does it, hers does not. We've switches charges and same issue, always mine, never hers. When these eventually die we'll likely go Garmin.

Mine is doing the same thing. Chiming every minute or so after reaching full charge. I bought mine early to mid last year. It is a series 3 and it never made this chime until the latest software update. So it’s not the charging base. There is a error in the update. Apple needs to fix this.... ASAP

I have this same issue with an Apple 4 using the charging cube and cable included with the watch. None of the fixes of wiping the watch, etc. work. It is sporadic, making troubleshooting even worse. Interestingly I have less issue with a knock off cable, but it too will chime occasionally.

Wow, that's really strange. So, the new watch they gave you- was it new in retail box? Did the new watch come with a new charger and was that used?

Are you using a surge protector?

Apple keeps claiming this is a software issue but I don't believe it. It doesn't all add up, even if the issue did begin for many after an update.

They finally agreed to replace mine, but when I sent it in, they just shipped it back because the repair facility doesn't read case notes. So I reached out to executive relations and now they are sending me a new watch, apparently.

Was your wife's a Nike Watch by chance?

scot84-

I found someone (who luckily kept their profile up to date) on LinkedIn and reached out directly to them. This was after a couple times of emailing Tim Cook. Obviously doesn't go to him, but allegedly is supposed to go to executive relations. The first time I did that I got a call back the next day from my senior advisor and he said he would replace it... maybe executive relations just told him to take care of it. In any case- he didn't take the proper steps apparently and my watch was sent back to me, so I had to try again to get someone at executive relations to reach out.

Good luck. It seems like any watch at any time can start acting up. Looks like someone just had WatchOS 5.2 trigger it- the newest release. After all this time Apple still doesn't have a clue why this is happening......

Judging by the age of this particular complaint forum I find that hard to believe. Apple has been aware of this issue for quite a while. I have seen other inquiries where Apple replied they were working to find the source of the issue dated back just after the last software update. Don’t let them miss lead you. There was a change in the last watch update that had an unintended effect on some watches but not all. They are probably trying to narrow down the particulars of watch manufacturing dates, location, software type, and others to identify why some do and don’t have the issue. They (like many other major tech companies) will not openly admit there is an issue for fear of a drop in sales...

From what I've experienced, Apple are doing a lot in this forum and elsewhere to help people experiencing this technology issue. I found a temporary fix if your watch is chiming at night when fully-charged: https://stadivm.com/threads/series-3-apple-watch-chimes-continuously-when-im-charging-it-up-any-ideas.330/ Hope this is useful for someone.

Well I’ve only ever used genuine apple chargers (one that came with my watch and the other a recent genuine apple purchase to see if a fault had developed with the original charger). So I can’t blame 3rd parties as there are none. The persistent but intermittent pinging whilst on charge only started for me after the last update (having had the watch for 18 months with perfect charging behaviour) - suggesting a software issue surely but no amount of resetting/unpairing etc. has resolved the problem. Things seemed better for a week with the new charger but soon started again. Some nights there’s no pinging other times it can keep pinging every 10 minutes. Occasionally it does it just once or twice other times throughout the night. There is no consistency and so it would be hard if not impossible to recreate in store or sending it in for s ‘repair’. It’s infuriating! I suppose it’s possible there’s a faulty component in the watch but can’t help but feel this is something apple are going to struggle to resolve given the intermittent nature of the problem and lack of consistency in those it’s affecting.

I just reached out to the person in executive relations I worked with, to express my concern with running an update since people are still getting this problem- sometimes after an update, other times randomly.

He reached out to the engineers who replied to him and said the problem was fixed in an update.

Based on rachnesmom's post on May 30th, it seems the update hasn't addressed the fix for everyone which is both disappointing and a little bit alarming that Apple is having this much trouble to fix the problem.

Is anyone else running the most up to date version of Watch OS and still having the problem?

rachnesmom- any update on yours since cleaning / reset etc?