alas無法正確連接模擬器
在提问之前...
- [x] 我已经搜索了现有的 issues
- [x] 我在提问题之前至少花费了 5 分钟来思考和准备
- [x] 我已经阅读了 Wiki 中的 常见问题(FAQ)
- [x] 我正在使用最新版的 Alas
描述你的问题
我使用的是mumu模擬器 alas中填寫的adb serial應該是正確的 但是無法連接到模擬器 而且昨天能正常使用 沒有改過任何設定
═══════════════════════════════════════════════════════════════════════════════════
START
═══════════════════════════════════════════════════════════════════════════════════
INFO 20:11:04.887 │ Start scheduler loop: alas
INFO 20:11:04.922 │ [Server] cn
INFO 20:11:04.932 │ Bind task ['General', 'Alas']
INFO 20:11:04.934 │ Pending tasks: ['Restart', 'Commission', 'Tactical',
'Research', 'Exercise', 'Dorm', 'Meowfficer', 'Guild', 'Reward',
'ShopFrequent', 'ShopOnce', 'Freebies', 'Minigame', 'OpsiAshBeacon',
'OpsiDaily', 'OpsiShop', 'OpsiAbyssal', 'OpsiStronghold', 'OpsiObscure',
'Daily', 'Hard', 'EventSp', 'OpsiMeowfficerFarming']
INFO 20:11:04.935 │ [Task] Restart (Enable, 2025-09-30 00:00:00)
INFO 20:11:04.936 │ Bind task ['General', 'Alas', 'Restart']
═════════════════════════════════════ DEVICE ══════════════════════════════════════
INFO 20:11:05.220 │ DEVICE
INFO 20:11:05.221 │ [IS_ON_PHONE_CLOUD] False
INFO 20:11:05.222 │ [AdbBinary]
C:\AzurLaneAutoScript\toolkit\Lib\site-packages\adbutils\binaries\adb.exe
INFO 20:11:05.223 │ [AdbClient] AdbClient(127.0.0.1, 5037)
INFO 20:11:05.224 │ <<< DETECT DEVICE >>>
INFO 20:11:05.224 │ Here are the available devices, copy to
Alas.Emulator.Serial to use it or set Alas.Emulator.Serial="auto"
INFO 20:11:05.225 │ 127.0.0.1:7555
INFO 20:11:15.229 │ failed to connect to 127.0.0.1:16416
INFO 20:11:15.232 │ already connected to 127.0.0.1:16416
INFO 20:11:15.233 │ [AdbDevice] AdbDevice(serial=127.0.0.1:16416)
INFO 20:11:15.234 │ [PackageName] com.hkmanjuu.azurlane.gp
INFO 20:11:15.234 │ [Server] tw
ERROR 20:11:15.235 │ AdbError: device offline
INFO 20:11:15.238 │ disconnected 127.0.0.1:16416
INFO 20:11:25.242 │ failed to connect to 127.0.0.1:16416
INFO 20:11:25.245 │ already connected to 127.0.0.1:16416
INFO 20:11:25.245 │ <<< DETECT DEVICE >>>
INFO 20:11:25.246 │ Here are the available devices, copy to
Alas.Emulator.Serial to use it or set Alas.Emulator.Serial="auto"
INFO 20:11:25.247 │ 127.0.0.1:7555
INFO 20:11:25.247 │ Here are the devices detected but unavailable
INFO 20:11:25.248 │ 127.0.0.1:16416 (offline)
ERROR 20:11:25.249 │ AdbError: device offline
INFO 20:11:26.252 │ disconnected 127.0.0.1:16416
INFO 20:11:36.256 │ failed to connect to 127.0.0.1:16416
INFO 20:11:36.259 │ already connected to 127.0.0.1:16416
INFO 20:11:36.260 │ <<< DETECT DEVICE >>>
INFO 20:11:36.261 │ Here are the available devices, copy to
Alas.Emulator.Serial to use it or set Alas.Emulator.Serial="auto"
INFO 20:11:36.262 │ 127.0.0.1:7555
INFO 20:11:36.263 │ Here are the devices detected but unavailable
INFO 20:11:36.263 │ 127.0.0.1:16416 (offline)
ERROR 20:11:36.264 │ AdbError: device offline
INFO 20:11:39.268 │ disconnected 127.0.0.1:16416
INFO 20:11:49.270 │ failed to connect to 127.0.0.1:16416
INFO 20:11:49.274 │ already connected to 127.0.0.1:16416
INFO 20:11:49.275 │ <<< DETECT DEVICE >>>
INFO 20:11:49.276 │ Here are the available devices, copy to
Alas.Emulator.Serial to use it or set Alas.Emulator.Serial="auto"
INFO 20:11:49.276 │ 127.0.0.1:7555
INFO 20:11:49.277 │ Here are the devices detected but unavailable
INFO 20:11:49.278 │ 127.0.0.1:16416 (offline)
ERROR 20:11:49.279 │ AdbError: device offline
INFO 20:11:52.281 │ disconnected 127.0.0.1:16416
INFO 20:12:02.283 │ failed to connect to 127.0.0.1:16416
INFO 20:12:02.285 │ already connected to 127.0.0.1:16416
INFO 20:12:02.286 │ <<< DETECT DEVICE >>>
INFO 20:12:02.287 │ Here are the available devices, copy to
Alas.Emulator.Serial to use it or set Alas.Emulator.Serial="auto"
INFO 20:12:02.289 │ 127.0.0.1:7555
INFO 20:12:02.290 │ Here are the devices detected but unavailable
INFO 20:12:02.291 │ 127.0.0.1:16416 (offline)
ERROR 20:12:02.292 │ AdbError: device offline
CRITICAL 20:12:02.293 │ Retry nemud_player_version() failed
CRITICAL 20:12:02.294 │ Request human takeover
如何复现
No response
预期行为
No response
相关 Logs
截图
No response
还有别的吗?
No response
一樣,我也遇到這個問題, 一樣是adb那邊出狀況, 目前先移除MUMU12, 打算改安裝MUMU國際版測試當中
mumu和mumu12我都試過了 都是一樣的問題
尝试重启模拟器,检查网络桥接是否已经关闭
今天起來又可以用了 但是我從來沒打開過網絡橋接 應該不是開了網絡橋接導致的 (網絡橋接要另外安裝驅動才能用 我從來沒安裝過) 我再用一段時間看看會不會再次出現這個問題
我也遇過,某天怎麼用adb都抓不到 後來重新安裝模擬器才恢復正常
一模一样的问题,困扰好几天了,有时候关了模拟器重启可以解决,有时候重设alas可以解决,有时候两者都不行
- 09/30 12:27 問題出現,陸版MUMU12開始無法連接ADB
- 09/30 22:06 陸版依然連接adb失敗,故移除陸版改裝國際版
- 10/01 01:23 國際版安裝後,截圖方案由nemu_ipc改為ADB_nc後正常運行
- 10/01 11:29 國際版第一次報錯,再度無法連接ADB
- 10/01 14:32 MUMU12正常執行中、adb devices 有三個裝置但都offline
- 10/01 15:09 以新版本adb(35.0.1-11580240)覆蓋alas資料夾內adb(29.0.6-6198805),adb kill-server、adb restart-server後,暫時清除emulator-5554、可連接端口5555但minitouch報錯
- 10/01 15:10 出現7555端口、emulator-5554陰魂不散
- 10/01 15:33 疑似ADB_nc導致adb崩潰
- 10/01 15:43 adb成功連線至127.0.0.1:5555,能進行效能測試
- 10/01 15:51 DroidCast_Raw無法OCR識別,改用MaaTouch
- 10/01 15:52 截圖方案改為uiautomator2,目前恢復正常使用
- 10/02 10:05 MUMU的serial又變為emulator-5554,調整alas serial為auto後可正常使用
環境設定:MUMU關閉網路橋接、模擬器內設定已開啟USB調試,DirectX、VT開啟、HyperV關閉;
沒找到ADB連接不穩的根本原因,應該是MUMU的問題比較大,Serial變來變去的,adb顯示的和MUMU裝置診斷顯示的serial是兩回事
不知道為什麼 但之前朋友也遇到這個問題 當時不止Alas出問題,MAA也有問題 之後因其他事故,刪掉了Overwolf 之後就沒有再出現問題 剛剛拜託了他重新安裝Overwolf 問題就又出現了 出現錯誤的log應該是類似的
今天又出現了同一個問題 這幾天設定完全沒改過
═══════════════════════════════════════════════════════════════════════════════════
START
═══════════════════════════════════════════════════════════════════════════════════
INFO 22:06:55.216 │ Start scheduler loop: alas
INFO 22:06:55.258 │ [Server] cn
INFO 22:06:55.270 │ Bind task ['General', 'Alas']
INFO 22:06:55.272 │ Pending tasks: ['Commission', 'Tactical', 'Research',
'Exercise', 'Dorm', 'Meowfficer', 'Guild', 'Reward', 'ShopFrequent',
'OpsiExplore', 'OpsiShop', 'OpsiAbyssal', 'OpsiStronghold', 'OpsiObscure',
'OpsiArchive', 'OpsiMeowfficerFarming']
INFO 22:06:55.273 │ [Task] Commission (Enable, 2025-10-05 08:14:56)
INFO 22:06:55.274 │ Bind task ['General', 'Alas', 'Commission']
═════════════════════════════════════ DEVICE ══════════════════════════════════════
INFO 22:06:58.318 │ DEVICE
INFO 22:06:58.319 │ [IS_ON_PHONE_CLOUD] False
INFO 22:06:58.320 │ [AdbBinary]
C:\AzurLaneAutoScript\toolkit\Lib\site-packages\adbutils\binaries\adb.exe
INFO 22:06:58.321 │ [AdbClient] AdbClient(127.0.0.1, 5037)
INFO 22:06:58.322 │ <<< DETECT DEVICE >>>
INFO 22:06:58.323 │ Here are the available devices, copy to
Alas.Emulator.Serial to use it or set Alas.Emulator.Serial="auto"
INFO 22:06:58.324 │ 127.0.0.1:7555
INFO 22:06:58.325 │ emulator-5554
INFO 22:07:08.327 │ failed to connect to 127.0.0.1:16384
INFO 22:07:08.331 │ already connected to 127.0.0.1:16384
INFO 22:07:08.332 │ [AdbDevice] AdbDevice(serial=127.0.0.1:16384)
INFO 22:07:08.333 │ [PackageName] com.hkmanjuu.azurlane.gp
INFO 22:07:08.333 │ [Server] tw
ERROR 22:07:08.334 │ AdbError: device offline
INFO 22:07:08.337 │ disconnected 127.0.0.1:16384
INFO 22:07:18.341 │ failed to connect to 127.0.0.1:16384
INFO 22:07:18.344 │ already connected to 127.0.0.1:16384
INFO 22:07:18.344 │ <<< DETECT DEVICE >>>
INFO 22:07:18.345 │ Here are the available devices, copy to
Alas.Emulator.Serial to use it or set Alas.Emulator.Serial="auto"
INFO 22:07:18.346 │ 127.0.0.1:7555
INFO 22:07:18.347 │ emulator-5554
INFO 22:07:18.347 │ Here are the devices detected but unavailable
INFO 22:07:18.348 │ 127.0.0.1:16384 (offline)
ERROR 22:07:18.349 │ AdbError: device offline
INFO 22:07:19.353 │ disconnected 127.0.0.1:16384
INFO 22:07:29.356 │ failed to connect to 127.0.0.1:16384
INFO 22:07:29.359 │ already connected to 127.0.0.1:16384
INFO 22:07:29.359 │ <<< DETECT DEVICE >>>
INFO 22:07:29.360 │ Here are the available devices, copy to
Alas.Emulator.Serial to use it or set Alas.Emulator.Serial="auto"
INFO 22:07:29.362 │ 127.0.0.1:7555
INFO 22:07:29.362 │ emulator-5554
INFO 22:07:29.362 │ Here are the devices detected but unavailable
INFO 22:07:29.363 │ 127.0.0.1:16384 (offline)
ERROR 22:07:29.364 │ AdbError: device offline
INFO 22:07:32.367 │ disconnected 127.0.0.1:16384
INFO 22:07:42.369 │ failed to connect to 127.0.0.1:16384
INFO 22:07:42.371 │ already connected to 127.0.0.1:16384
INFO 22:07:42.372 │ <<< DETECT DEVICE >>>
INFO 22:07:42.373 │ Here are the available devices, copy to
Alas.Emulator.Serial to use it or set Alas.Emulator.Serial="auto"
INFO 22:07:42.374 │ 127.0.0.1:7555
INFO 22:07:42.375 │ emulator-5554
INFO 22:07:42.376 │ Here are the devices detected but unavailable
INFO 22:07:42.376 │ 127.0.0.1:16384 (offline)
ERROR 22:07:42.377 │ AdbError: device offline
INFO 22:07:45.380 │ disconnected 127.0.0.1:16384
INFO 22:07:55.382 │ failed to connect to 127.0.0.1:16384
INFO 22:07:55.385 │ already connected to 127.0.0.1:16384
INFO 22:07:55.385 │ <<< DETECT DEVICE >>>
INFO 22:07:55.386 │ Here are the available devices, copy to
Alas.Emulator.Serial to use it or set Alas.Emulator.Serial="auto"
INFO 22:07:55.387 │ 127.0.0.1:7555
INFO 22:07:55.388 │ emulator-5554
INFO 22:07:55.388 │ Here are the devices detected but unavailable
INFO 22:07:55.389 │ 127.0.0.1:16384 (offline)
ERROR 22:07:55.390 │ AdbError: device offline
CRITICAL 22:07:55.390 │ Retry nemud_player_version() failed
CRITICAL 22:07:55.391 │ Request human takeover
有相同問題, 發現個方法可以解決, 因為我同時也有在用MAA, 方法是先開啟MAA, 等MAA ADB連結成功後再開alas 然後等alas成功連結ADB後再把MAA關掉
我也遇到了这个问题,找了个教程,杀掉了mumu运行的所有进程(包括任务管理器-详细信息中的后台进程树),之后重启模拟器和ADB就好了。教程来自CSDN:https://blog.csdn.net/qq_30183767/article/details/81384318 希望能帮到你。