Watch beep and show message charging over and over when 99-100%

Tomas5

@Spree no problem english is not my native language

A Former User

@Tomas5 If I were you, I’d return the watch and order a new one. When you are within your return window, the only acceptable thing is to have it replaced for a brand new one. If not possible, return it.

ADHDMonkey

@Tomas5 I would return it. Don’t risk it. Sounds like a dodgy unit.

zhang965

@ADHDMonkey said in Watch beep and show message charging over and over when 99-100%:

@Tomas5 I would return it. Don’t risk it. Sounds like a dodgy unit.

It’s what I called the most useful reply.

Ádám Patkós

@Tomas5 Hello!
My Suunto 5peak behaves the same way. I don’t think it’s a problem. I have been using it for more than 6 months.

Ádám Patkós

Hello!
My Suunto 5peak behaves the same way. I don’t think it’s a problem. I have been using it for more than 6 months.

A Former User

@Tomas5 Any news on the S5P in relation to the charging?

Tomas5

@skifun based on communication with seller and service for central europe, it is going for warranty check to service. I head to post office today.

Tomas5

@Ádám-Patkós thank’s for info, as i mentioned above seller and service center suggested to sent it to them for check. I will post result as soon as i get any new info. But I didn’t have much time so I am only today going to post office to sent it.

Tomas5

So today watch arrived from service with message:

I have checked your device for faults reported in the fault description and performed all the necessary tests, and no fault has been discovered. WATCH ONLY INFORM YOU THAT THEY ARE FULLY CHARGED.

So I don’t understand, watch even don’t have message that they are fully charged but “qualified” servician says it only informs me that it is fully charged.

And it looks like they even didn’t bother to disable power saving mode (or they enabled it again before sending back but watch was set up exactly like when i put it into box). So watch couldn’t beep at all if I am not mistaken.

A Former User

@Tomas5 So, do you accept this or perhaps you’re returning the watch? If this kind of behavior of the watch is by design, there’s nothing you can do but use as it is.

Tomas5

@skifun well i am not able to return it. Since they claim it is ok. But do you think this behavior seems correct? I recorded video of this behavior https://www.dropbox.com/s/uwfr7wiv9f72plt/FullSizeRender.MOV?dl=0

As soon as charged, watch starts to do this, I am afraid to let in on charger to see for how long it will do this. So i disconnect it every time as soon as this starts to happen. But if this is “by desing” than i am afraid I am not target group of suunto anymore

sartoric

@Tomas5
Did you check the charging clamp and cable ?

Tomas5

@sartoric 2 different chargers, and laptop as pover source, i tried cable which arrived with S5Peak, i tried cable from my S5 and i tried even 2 old calbles from Ambit 2 watch. All the time same result.

Tomas5

I never let it beep for longer than 2 minutes because i am concerned how it will impact battery when it starts charging multiple times per minute when battery fully charged.

sartoric

@Tomas5
Did you ever try to connect it to a wall charger?
Maybe it’s the laptop that is disconnecting and reconnecting while fully charged

Tomas5

@sartoric well as i answered you two posts above. 2 different chargers and laptop still same behavior. And as i mentioned multiple posts above. All chargers i tried with my older S5 and they don’t behave so strange like this S5P.

Tomas5

To be more specific i think it was samsung charger, htc charger, and thinkpad laptop.

sartoric

@Tomas5
Oh,ok I missed it
I supposed you were always using laptop as power source

2 different chargers, and laptop as pover source,

Well, so based on others replies and support report it seems to be normal on 5peak.
I’ll ask a friend that has a 5 peak too

Tomas5

@sartoric well only one person here says it has same issue. So i am not sure if normal is right way to say it. But i have some knowledge on electronics and i see that this is clearly bug or design fault