Oddly, charging when on (ie not completely dead), this feature doesn't trigger the alarm.
I really dislike this feature.
Oddly, charging when on (ie not completely dead), this feature doesn't trigger the alarm.
I really dislike this feature.
Guess what is more annoying than a loud sound.
Happens a lot for people who leave USB-C cables in the bottom of bags and they get dirt in the connector (and possibly the residue from that beer that exploded in your bag last year and the sugary water never quite evaporates)
This function measures the voltage drop between two pins and plays a sound when it is too high. So it is possible:
- to just not play a sound, and have it silently switch off the connector (this would feel like a broken cable to you, but at least wouldn't annoy)
- that the threshold is not well adjusted. But this is not rocket science, but simple Ohms law stuff, so I doubt this is the problem
- you could just not have that protection and live with what happens to the IC inside when those pins are shorted. That could be any number of things, most of them more annoying than a sound
Unless you want to change basic laws of physics or the USB-C spec these are the options.
> You really dislike a feature that plays a loud sound instead of shorting pins in you USB-C connector together?
The instead here splits the sentence into those two options. Either a sound is played loudly or pins are shorted. That's how the sentence you wrote is structured, anyway.
Clearly that's not how you considered the situation, but yes, you did claim there were two options.
It's probably a not-entirely-compliant USB implementation on the phone.
Could this by why I hear a really loud buzzing sound when I connect my laptop to a thunderbolt docking station?
The sound only happens for a fraction of a second, and doesn't happen every time; but now that you mention it, it does have the acoustic properties of a warning buzzer!
All components genuine AFAIK and supplied by the same vendor, Toshiba/Dynabook; but I wonder if a failing component somewhere causes a bad state that some component detects, triggering this warning sound...