0
I don’t know why but I was a little afraid to think that since my ADT is in constant contact with my Device (Nexus 5) when disconnecting during an information exchange there may be damage. Could it be that just like a flash drive when disconnecting abruptly during the passage or exchange of information there are risks? Has anyone ever fried part of a device like this? Thank you.
2
TL;DR - Nothing you should worry about.
Long answer:
The risks involved in a disconnection from the USB port during debugging are exactly the same as what the device is subject to during everyday use.
In some old USB implementations it was possible to remove a device while the host is still supplying power to the device. Today this is very rare.
The main problem with removal without ejection is the fact that some operating systems cache in memory files being manipulated on removable media. As in practice you are not manipulating files (ADB takes care of 'serialize' and send your Apks using its own protocol), this risk is non-existent.
On the device side, the operating environment ensures that your new APK package will only be installed if the transfer is successful.
0
I’ve had the experience of disconnecting an Android device while transferring files and the source from the PC burned on time. It happened to me only once, today I do it kind of followed and never had this problem again. However, it was the simple act of disconnecting the USB and the source burned.
I remember a case where a developer did the same - removed a device from the USB port - and the victim was the motherboard. This happened because the USB port did not have any kind of short circuit safety (which it provoked by taking the tilting device laterally).
Browser other questions tagged android
You are not signed in. Login or sign up in order to post.
Very good, withdrew my doubt, no shadow for questions. Thank you!
– paccamicio