Question
I'm developing a Tizen native app and an Android app that communicate with each other using the Samsung Accessory SDK. However, I'm encountering an issue where I can't debug both applications simultaneously. When Tizen Studio is connected to a watch, Android Studio fails to connect to a phone, and vice versa.
Through command line testing, I've discovered that:
- When both adb and sdb servers are killed
- If I connect to an Android device with ADB first, I can't connect to a Tizen device with SDB
- Conversely, if I connect to a Tizen device with SDB first, I can't connect to an Android device with ADB
Has anyone found a solution to debug both applications at the same time?
Answer
Problem Understanding
The issue occurs due to port conflicts between ADB (Android Debug Bridge) and SDB (Smart Development Bridge) when trying to debug both Tizen and Android applications simultaneously. The debug servers compete for device connections, causing one to fail when the other is active.
Solution Methods
-
Connection Order Matters:
- Start Android Studio and connect to your Android device first
- Then start Tizen Studio and connect to your Tizen device
- This order prevents the port conflict
-
Command Line Workaround:
# First kill all existing servers adb kill-server sdb kill-server # Start Android debugging first adb start-server adb devices # Then start Tizen debugging sdb start-server sdb devices -
Using Gear Manager Connection:
- Connect your Tizen watch to your Android phone via Gear Manager
- Ensure the apps can communicate before attempting to debug
- This method sometimes allows simultaneous debugging in both IDEs
Code Examples
Here's the complete command sequence that demonstrates the issue and solution:
# Scenario showing the conflict
adb kill-server
sdb kill-server
sdb start-server
adb start-server
adb devices
# Output shows no devices listed due to conflict
# Working scenario
adb kill-server
sdb kill-server
adb start-server
adb devices
# Android device listed
sdb start-server
sdb devices
# Both devices listed
Additional Tips
- If you encounter the "could not open interface" error (e00002c5 on macOS), it indicates the port conflict
- Remember that SDB can list both Tizen and Android devices, while ADB only lists Android devices
- When devices appear "offline" in one tool, it means they're being used by the other
- For best results, establish all connections through Android Studio before opening Tizen Studio
