Phone shows up as null in Android Studio [closed]
I'm trying to run my app on Android from Android Studio. It's just an empty activity for now. Just to note, I already ran apps in the past using USB debugging and it has worked just fine without me having to tinker with anything.
The problem is that my phone gets recognized correctly the first second I plug it in, but after that it's as if it disconnects and shows up again as "2b54deb59804 [null]".
Tried with another phone (Xiaomi Redmi 6) and it got recognized correctly. Same drivers were used as well, which means it's an issue with my Xiaomi Redmi Note 4.
I tried turning off USB debugging and turning it back on again, as well as restarting my phone, but it made no difference. Tried with setting it in file transfer mode as well, same thing happens. Shows up correctly at first and then goes to null.
Running adb devices command I get:
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
2b54deb59804 connecting
windows-7 android android-studio
asked Jan 26 at 12:32
papibatpapibat
12
closed as off-topic by harrymc, Twisty Impersonator, Ramhound, td512, duDE Jan 28 at 13:54
- This question does not appear to be about computer software or computer hardware within the scope defined in the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
I'm trying to run my app on Android from Android Studio. It's just an empty activity for now. Just to note, I already ran apps in the past using USB debugging and it has worked just fine without me having to tinker with anything.
The problem is that my phone gets recognized correctly the first second I plug it in, but after that it's as if it disconnects and shows up again as "2b54deb59804 [null]".
Tried with another phone (Xiaomi Redmi 6) and it got recognized correctly. Same drivers were used as well, which means it's an issue with my Xiaomi Redmi Note 4.
I tried turning off USB debugging and turning it back on again, as well as restarting my phone, but it made no difference. Tried with setting it in file transfer mode as well, same thing happens. Shows up correctly at first and then goes to null.
Running adb devices command I get:
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
2b54deb59804 connecting
windows-7 android android-studio
asked Jan 26 at 12:32
papibatpapibat
12
closed as off-topic by harrymc, Twisty Impersonator, Ramhound, td512, duDE Jan 28 at 13:54
- This question does not appear to be about computer software or computer hardware within the scope defined in the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
I'm trying to run my app on Android from Android Studio. It's just an empty activity for now. Just to note, I already ran apps in the past using USB debugging and it has worked just fine without me having to tinker with anything.
The problem is that my phone gets recognized correctly the first second I plug it in, but after that it's as if it disconnects and shows up again as "2b54deb59804 [null]".
Tried with another phone (Xiaomi Redmi 6) and it got recognized correctly. Same drivers were used as well, which means it's an issue with my Xiaomi Redmi Note 4.
I tried turning off USB debugging and turning it back on again, as well as restarting my phone, but it made no difference. Tried with setting it in file transfer mode as well, same thing happens. Shows up correctly at first and then goes to null.
Running adb devices command I get:
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
2b54deb59804 connecting
windows-7 android android-studio
asked Jan 26 at 12:32
papibatpapibat
12
I'm trying to run my app on Android from Android Studio. It's just an empty activity for now. Just to note, I already ran apps in the past using USB debugging and it has worked just fine without me having to tinker with anything.
The problem is that my phone gets recognized correctly the first second I plug it in, but after that it's as if it disconnects and shows up again as "2b54deb59804 [null]".
Tried with another phone (Xiaomi Redmi 6) and it got recognized correctly. Same drivers were used as well, which means it's an issue with my Xiaomi Redmi Note 4.
I tried turning off USB debugging and turning it back on again, as well as restarting my phone, but it made no difference. Tried with setting it in file transfer mode as well, same thing happens. Shows up correctly at first and then goes to null.
Running adb devices command I get:
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
2b54deb59804 connecting
windows-7 android android-studio
windows-7 android android-studio
asked Jan 26 at 12:32
papibatpapibat
12
asked Jan 26 at 12:32
papibatpapibat
12
edited Jan 26 at 15:29
papibat
asked Jan 26 at 12:32
papibatpapibat
12
asked Jan 26 at 12:32
papibatpapibat
12
asked Jan 26 at 12:32
papibatpapibat
12
12
closed as off-topic by harrymc, Twisty Impersonator, Ramhound, td512, duDE Jan 28 at 13:54
- This question does not appear to be about computer software or computer hardware within the scope defined in the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.
closed as off-topic by harrymc, Twisty Impersonator, Ramhound, td512, duDE Jan 28 at 13:54
- This question does not appear to be about computer software or computer hardware within the scope defined in the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Works fine with a third USB cable on a different USB port so I suppose that was an issue.
answered Jan 28 at 8:09
papibatpapibat
12
What was an issue?
– Twisty Impersonator
Jan 28 at 14:13
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Works fine with a third USB cable on a different USB port so I suppose that was an issue.
answered Jan 28 at 8:09
papibatpapibat
12
What was an issue?
– Twisty Impersonator
Jan 28 at 14:13
add a comment |
Works fine with a third USB cable on a different USB port so I suppose that was an issue.
answered Jan 28 at 8:09
papibatpapibat
12
What was an issue?
– Twisty Impersonator
Jan 28 at 14:13
add a comment |
Works fine with a third USB cable on a different USB port so I suppose that was an issue.
answered Jan 28 at 8:09
papibatpapibat
12
Works fine with a third USB cable on a different USB port so I suppose that was an issue.
answered Jan 28 at 8:09
papibatpapibat
12
answered Jan 28 at 8:09
papibatpapibat
12
answered Jan 28 at 8:09
papibatpapibat
12
answered Jan 28 at 8:09
papibatpapibat
12
12
What was an issue?
– Twisty Impersonator
Jan 28 at 14:13
add a comment |
What was an issue?
– Twisty Impersonator
Jan 28 at 14:13
What was an issue?
– Twisty Impersonator
Jan 28 at 14:13
What was an issue?
– Twisty Impersonator
Jan 28 at 14:13
add a comment |
