Hi. I spent some time creating a bug report for the Mekede M400 radio software. Here it is:
SYSTEM FAILURE REPORT - MEKEDE M400
Analysis Date: October 14, 2025
Model: Mekede M400 (UIS8581)
System Version: LS-PT/2025-09-01
MCU Version: 202110.09-10.12.29
Total Logs Analyzed: 35+
🚨 EXECUTIVE SUMMARY OF DETECTED ERRORS
CRITICAL SYSTEM PROBLEMS:
- KERNEL PANIC - 4 confirmed cases within 5 days
- DAMAGED IPC SYSTEM - Android Binder framework failure
- CASCADING SYSTEM FAILURE - All modules affected
- CHRONIC INSTABILITY - Daily system crashes
📊 FAILURE STATISTICS
KERNEL PANIC (4 occurrences):
- 10/09/2025 09:12:45 - Binder IPC failure
- 10/10/2025 17:44:37 - Network subsystem failure
- 10/13/2025 18:24:50 - Memory synchronization failure
- 10/14/2025 17:18:23 - Memory management failure
APPLICATION CRASHES (31+ logs):
| Module | Crash Count | Error Type |
|--------|-------------|------------|
| SystemUI | 8 | SecurityException |
| Audio/Amplifier | 3 | SecurityException |
| CAN Bus | 3 | SecurityException |
| CarLink | 3 | SecurityException |
| FileManager | 2 | SecurityException |
| DuduMarket | 1 | SecurityException |
| BtPhone | 1 | SecurityException |
| CarUi | 1 | SecurityException |
| DuduAutoUi | 1 | SecurityException |
| Update Service | 2 | SecurityException |
| TPMS | 1 | SecurityException |
| Base modules | 8 | SecurityException/NullPointerException |
🔍 ROOT CAUSE ANALYSIS
1. PRIMARY CAUSE: DAMAGED ANDROID BINDER IPC
java.lang.SecurityException: Binder invocation to an incorrect interface
at com.syu.ipc.IRemoteToolkit$Stub$Proxy.getRemoteModule(IRemoteToolkit.java:128)
Problem: Fundamental error in Android Binder inter-process communication framework prevents communication between:
- Android system and SYU modules
- Android system and DuduOS modules
- System modules and hardware components
2. CASCADING SYSTEM FAILURE
Failure sequence from 10/14/2025 18:25:XX:
18:25:09 - SYU IPC collapse (Base module)
18:25:10 - DuduAutoUi collapse (dependent on SYU)
18:25:34 - FileManager collapse (first independent DuduOS)
18:25:38 - DuduMarket collapse
18:25:39 - BtPhone + CarUi collapse
18:25:40 - FileManager final collapse
3. MULTI-LEVEL KERNEL DAMAGE
Different kernel areas failing:
- Memory:
unlink_anon_vmas (memory management)
- Synchronization:
down_write (thread synchronization)
- Network:
netlink_broadcast_filtered (network subsystem)
- IPC:
binder_ioctl (Android Binder system)
⚠️ IMPACT ON USER EXPERIENCE
LOST FUNCTIONALITY:
- ❌ User interface (SystemUI crashes)
- ❌ Audio system (Audio module crashes)
- ❌ Car communication (CAN Bus crashes)
- ❌ Phone connectivity (CarLink, BtPhone crashes)
- ❌ System updates (Update Service crashes)
- ❌ Tire monitoring (TPMS crashes)
- ❌ File management (FileManager crashes)
- ❌ App store (DuduMarket crashes)
- ❌ Complete system restart (Kernel panic)
USER EXPERIENCE:
- Radio restarts every 30-60 seconds
- Settings reset after each restart
- System often fails to boot without hardware reset
- Loss of all configurations and data
🛠️ MANUFACTURER RECOMMENDATIONS
1. URGENT SYSTEM FIXES
A. BINDER IPC FRAMEWORK PATCH
// Current error:
SecurityException: Binder invocation to incorrect interface
// Required fix:
- Update Android Binder subsystem
- Improve IPC security mechanisms
- Test inter-process compatibility
B. MCU AND SYSTEM UPDATE
# Current versions:
Android: 2025-09-01
MCU: 2021-10-09
# Required compatibility:
Android + MCU + SYU_IPC + DuduOS_IPC in compatible versions
C. IPC SYSTEMS ISOLATION
Current architecture:
SYU_IPC ←→ DuduOS_IPC (intertwined dependencies)
Required architecture:
SYU_IPC → Android_Binder ← DuduOS_IPC (isolated)
2. ARCHITECTURAL IMPROVEMENTS
A. ELIMINATE SINGLE POINT OF FAILURE
- Current: SYU IPC failure → DuduOS collapse
- Required: Independent communication systems
B. FAILURE RECOVERY MECHANISMS
- Automatic restart of damaged modules
- Isolation of crashing components
- Settings preservation during restarts
C. IMPROVED INTEGRATION TESTING
- IPC stress testing
- Version compatibility testing
- Failure and recovery simulations
3. SPECIFIC TECHNICAL FIXES
A. SYU IPC MODULE
// Problem:
com.syu.ipc.IRemoteToolkit.getRemoteModule() - always fails
// Fix:
- Update SYU IPC libraries
- Improve security handlers
- Better error handling
B. DUDUOS IPC MODULE
// Problem:
com.wow.fyt7862.base.rservice.e$a$a.a() - fails under stress
// Fix:
- Independence from SYU IPC
- Own recovery mechanisms
- Better resource management
C. KERNEL MEMORY MANAGEMENT
// Problem:
kernel panic in unlink_anon_vmas, down_write, netlink_broadcast
// Fix:
- Better memory mapping management
- Improved thread synchronization
- Network subsystem stability
🧪 POST-REPAIR TESTING PROTOCOL
1. IPC STABILITY TESTS
- Continuous SYU ↔ Android communication for 24h
- Continuous DuduOS ↔ Android communication for 24h
- Simultaneous load on all IPC modules
- Failure and recovery simulation of individual components
2. STRESS TESTING
- 48h continuous operation under maximum load
- Multiple application start/stop cycles
- Memory testing under low resources
- Thermal throttling tests
3. COMPATIBILITY TESTING
- Android versions: backward and forward compatibility
- MCU versions: testing with different firmware
- Third-party libraries: SYU, DuduOS, other vendors
📞 FINAL CONCLUSIONS
PROBLEM SUMMARY:
- Fundamental Android Binder framework error
- Incompatibility between system components
- Lack of isolation between vendors (SYU/DuduOS)
- Kernel instability under load
REQUIRED ACTIONS:
- Immediate Android Binder IPC framework update
- Delivery of compatible package: Android + MCU + libraries
- Redesign of inter-vendor communication architecture
- Comprehensive stability testing before update release
FAILURE ASSESSMENT:
- Criticality level: 10/10 (system completely unusable)
- Required repair level: Complete system rebuild
- Repair timeframe: Critical - requires immediate intervention
Report generated based on analysis of 35+ system logs
*Date: 2025-10-14
link to google drive logs
https://drive.google.com/drive/folders/1sQ7q3h_1R_TbnPC5EfXkSNKBUxig_Hzp?usp=drive_link
