0

I often use adb shell and other operations such as adb push and adb pull over a USB cable.

On Nexus 5 it always worked perfectly. But since I switched to Samsung S10e I have this very surprising problem:

  1. I open a terminal on my laptop, run adb shell.
  2. I type normally in ADB shell (ls, typing enter, etc), the expected output appears.
  3. As I continue typing, suddenly my typed character is not shown, as if the USB connection was stuck.
  4. I have found a strange workaround: When that happens, I open another terminal and run adb shell in it.
  5. Immediately, that "unstucks" the first terminal, and the "stucked" characters appear.
  6. Now I can use the first terminal again, until it gets stuck again.
  7. When that happens, I type a few characters in the second terminal, and that solves the problem again.
  8. Inevitably as I repeat the trick several times, the second terminal gets stuck too.
  9. When that happens, I open a third terminal, and that "unstucks" the first and second terminals.
  10. Etc. Sometime I need to open a fourth terminal.

This also happens with other ADB commands.

Question: How to investigate the problem? Is there any Android setting that could mitigate or even solve the problem?

  • only when battery is 100% or always? – alecxs Aug 16 '19 at 18:03
  • @alecxs: Always. – Nicolas Raoul Aug 19 '19 at 2:44
  • Hm.. i have this when connected adb over wifi when device goes to sleep – alecxs Aug 20 '19 at 10:34
  • i guess we can assume the reason is related to this? android.stackexchange.com/questions/216103 – alecxs Aug 25 '19 at 15:34
  • @alecxs: The moisture problem started 16 days ago. On the opposite, the present problem has existed since the day I bought the phone (several months ago). – Nicolas Raoul Aug 26 '19 at 0:35

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.