[Bug] MuMu Android 15 ADB device remains offline after upgrade

[1822818246-lgtm]

Before you asking

• I have searched the existing issues
• I spend at least 5 minutes for thinking and preparing
• I checked Frequently Asked Questions (FAQ) in Wiki page
• I am using the latest version of Alas

Describe the bug

Environment:

• Alas version: 0.4.9 fullcn
• OS: Windows 11
• MuMu version/build:6.5.5
• Android version: Android 15
• Server: CN
• Game: Azur Lane

Problem:
Alas worked normally before upgrading the MuMu instance to Android 15.
After the upgrade, the ADB port is reachable, but the device always remains offline.

ADB output:
127.0.0.1:16448 offline transport_id:1

Alas log:
No available devices
127.0.0.1:16448 (offline)
AdbError: device offline
Retry nemud_player_version() failed
Request human takeover

What I tried:

• ADB debugging is enabled in MuMu
• Restarted the MuMu instance
• Restarted the ADB server
• Disconnected and reconnected 127.0.0.1:16448
• The device still remains offline

Expected:
The device should be detected as device, and Alas should start normally.

Questions:

1. Is MuMu Android 15 currently supported?
2. Does Alas 0.4.9 require a newer bundled ADB version?
3. Is there a recommended MuMu version or Android version for Alas?

To Reproduce

在Android12版本下正常运行
15不行，可复现

Expected behavior

No response

Relevant log output

═══════════════════════════════════════════════════════════════════════════════════
                                       START                                       
═══════════════════════════════════════════════════════════════════════════════════
INFO     10:13:14.242 │ Start scheduler loop: alas                                 
INFO     10:13:14.284 │ [Server] cn                                                
INFO     10:13:14.294 │ Bind task ['General', 'Alas']                              
INFO     10:13:14.424 │ Server "巴巴罗萨" is available.                            
INFO     10:13:14.426 │ Pending tasks: ['Restart', 'Commission', 'Tactical',       
         'Research', 'Dorm', 'Meowfficer', 'Guild', 'Gacha', 'Reward', 'Freebies', 
         'Minigame', 'OpsiAshBeacon', 'OpsiDaily', 'OpsiShop', 'OpsiAbyssal',      
         'OpsiStronghold', 'OpsiObscure', 'Daily', 'Hard', 'OpsiAshAssist',        
         'OpsiMonthBoss', 'Event']                                                 
INFO     10:13:14.427 │ [Task] Restart (Enable, 2026-08-20 17:38:00)               
INFO     10:13:14.427 │ Bind task ['General', 'Alas', 'Restart']                   
═════════════════════════════════════ DEVICE ══════════════════════════════════════
INFO     10:13:14.730 │ DEVICE                                                     
INFO     10:13:14.731 │ [IS_ON_PHONE_CLOUD] False                                  
INFO     10:13:14.731 │ [AdbBinary] E:\AlasApp_0.4.9_fullcn\AzurLaneAutoScript\tool
         kit\Lib\site-packages\adbutils\binaries\adb.exe                           
INFO     10:13:14.732 │ [AdbClient] AdbClient(127.0.0.1, 5037)                     
INFO     10:13:14.733 │ <<< DETECT DEVICE >>>                                      
INFO     10:13:14.733 │ Here are the available devices, copy to                    
         Alas.Emulator.Serial to use it or set Alas.Emulator.Serial="auto"         
INFO     10:13:14.734 │ No available devices                                       
INFO     10:13:14.736 │ Here are the devices detected but unavailable              
INFO     10:13:14.736 │ 127.0.0.1:7555 (offline)                                   
WARNING  10:13:14.737 │ Device 127.0.0.1:7555 is offline, disconnect it before     
         connecting                                                                
INFO     10:13:14.738 │ disconnected 127.0.0.1:7555                                
INFO     10:13:24.741 │ failed to connect to 127.0.0.1:16448                       
INFO     10:13:24.744 │ already connected to 127.0.0.1:16448                       
INFO     10:13:24.745 │ [AdbDevice] AdbDevice(serial=127.0.0.1:16448)              
INFO     10:13:24.745 │ [PackageName] com.bilibili.azurlane                        
INFO     10:13:24.746 │ [Server] cn                                                
ERROR    10:13:24.747 │ AdbError: device offline                                   
INFO     10:13:24.749 │ disconnected 127.0.0.1:16448                               
INFO     10:13:34.751 │ failed to connect to 127.0.0.1:16448                       
INFO     10:13:34.754 │ already connected to 127.0.0.1:16448                       
INFO     10:13:34.755 │ <<< DETECT DEVICE >>>                                      
INFO     10:13:34.756 │ Here are the available devices, copy to                    
         Alas.Emulator.Serial to use it or set Alas.Emulator.Serial="auto"         
INFO     10:13:34.757 │ No available devices                                       
INFO     10:13:34.758 │ Here are the devices detected but unavailable              
INFO     10:13:34.758 │ 127.0.0.1:16448 (offline)                                  
ERROR    10:13:34.759 │ AdbError: device offline                                   
INFO     10:13:35.761 │ disconnected 127.0.0.1:16448                               
INFO     10:13:45.765 │ failed to connect to 127.0.0.1:16448                       
INFO     10:13:45.768 │ already connected to 127.0.0.1:16448                       
INFO     10:13:45.769 │ <<< DETECT DEVICE >>>                                      
INFO     10:13:45.769 │ Here are the available devices, copy to                    
         Alas.Emulator.Serial to use it or set Alas.Emulator.Serial="auto"         
INFO     10:13:45.770 │ No available devices                                       
INFO     10:13:45.770 │ Here are the devices detected but unavailable              
INFO     10:13:45.771 │ 127.0.0.1:16448 (offline)                                  
ERROR    10:13:45.772 │ AdbError: device offline                                   
INFO     10:13:48.774 │ disconnected 127.0.0.1:16448                               
INFO     10:13:58.777 │ failed to connect to 127.0.0.1:16448                       
INFO     10:13:58.780 │ already connected to 127.0.0.1:16448                       
INFO     10:13:58.780 │ <<< DETECT DEVICE >>>                                      
INFO     10:13:58.781 │ Here are the available devices, copy to                    
         Alas.Emulator.Serial to use it or set Alas.Emulator.Serial="auto"         
INFO     10:13:58.782 │ No available devices                                       
INFO     10:13:58.783 │ Here are the devices detected but unavailable              
INFO     10:13:58.784 │ 127.0.0.1:16448 (offline)                                  
ERROR    10:13:58.785 │ AdbError: device offline                                   
INFO     10:14:01.787 │ disconnected 127.0.0.1:16448                               
WARNING  10:14:01.789 │ Device emulator-5558 is offline, disconnect it before      
         connecting                                                                
INFO     10:14:11.791 │ failed to connect to 127.0.0.1:16448                       
INFO     10:14:11.794 │ already connected to 127.0.0.1:16448                       
INFO     10:14:11.794 │ <<< DETECT DEVICE >>>                                      
INFO     10:14:11.795 │ Here are the available devices, copy to                    
         Alas.Emulator.Serial to use it or set Alas.Emulator.Serial="auto"         
INFO     10:14:11.796 │ No available devices                                       
INFO     10:14:11.796 │ Here are the devices detected but unavailable              
INFO     10:14:11.797 │ 127.0.0.1:16448 (offline)                                  
INFO     10:14:11.797 │ emulator-5558 (offline)                                    
ERROR    10:14:11.798 │ AdbError: device offline                                   
CRITICAL 10:14:11.799 │ Retry nemud_player_version() failed                        
CRITICAL 10:14:11.799 │ Request human takeover

Screenshots

Anything else?

No response

[LmeSzinc]

尝试重启模拟器，让模拟器在adb上的状态为 device 而不是 offline