I’m in a bit of a bind here - my Mudita Kompakt is completely stuck in airplane mode, and I can’t turn it off. After confirming that the Offline+ toggle is in the connected position, I’ve tried the following steps, but nothing has worked:
Toggling airplane mode on and off from the settings menu
Toggling the Offline+ switch on and off
Restarting the device
I’m including a short video here to show exactly what’s happening.
I’ve already reached out to Mudita Technical Support and am waiting for a reply, but since this is my primary phone and I currently only have Wi-Fi connectivity, I’m hoping to find a workaround as quickly as possible.
If anyone else has experienced this issue and found a solution, your help would be greatly appreciated!
Thank you.
Related note: I’ve reverted back to my iPhone as my primary phone since it reliably functions as, well… a phone. I’m currently considering using the MK as a secondary device, as it still has too many issues and limitations for my daily workflow. I’m not sure what role it fits into my life at the moment, but I don’t want to return it - I don’t want to harm Mudita as a company, and I remain hopeful that at some point in the future (maybe 2027!) it will become a fully usable device.
UPDATE: GEZIMOS SUGGESTED CONNECTING MY PHONE TO WEBADB AND INPUTTING THIS COMMAND “settings put global airplane_mode_on 0” AND IT RESOLVED MY ISSUE.
I LOOKED UP WHAT IT MEANS AND…
What Does This Command Do?
settings put global airplane_mode_on 0
This command writes a value into Android’s global system settings database.
settings → The command-line tool for reading/writing system settings
put → Write a value
global → Change a system-wide setting (not per-user)
airplane_mode_on → The key that stores the Airplane Mode state
Update: This issue just happened again and so is a recurring issue. I just emailed customer support along with a video and hope they can provide a soon resolution. Is this issue happening to anyone else? Wondering if it’s just a defective unit or if it’s a known issue that’s affective multiple users.
Lol, not your fault (and I didn’t even have Airplane Mode enabled before this happened - it just auto-enabled and didn’t even show it was in such mode in the Control Center).
Possible Causes
Based on the symptoms and the solution that worked, here is what likely happened behind the scenes:
State Desynchronization (UI vs. System): The most probable cause is a “state desync.” The Android operating system tracks Airplane Mode in a database (Global Settings). The Mudita Kompakt adds a layer of complexity with its physical Offline+ switch and custom UI. It appears the system database got stuck reading “On” (Value 1), but the communication pathway between the physical switch/UI toggles and that database was broken or blocked. The buttons were “pressing,” but they weren’t permitted to write to the database.
Offline+ Handler Glitch: The Kompakt uses a specific background service to interpret the physical Offline+ slider. If this service crashed or entered an invalid state (e.g., thinking the switch is “halfway” or permanently On), it may have continuously overridden any attempt to turn Airplane Mode off via the software menu.
Race Condition: If the physical switch was toggled rapidly or during a specific system process (like boot-up), the system might have locked the variable to prevent conflict, but then failed to unlock it.
The Command:settings put global airplane_mode_on 0
Why it worked:
This command bypasses the entire user interface and the physical Offline+ switch logic.
Normally, when you toggle the switch, the Phone App tells the System UI, which checks permissions and then updates the Global Settings database.
By using ADB (Android Debug Bridge), you injected the value 0 (OFF) directly into the Android Settings.Global database table. This effectively “teleported” past the broken switch/UI logic and ordered the operating system kernel to wake up the radios immediately.
Hi Urszula, thank you, I recieved this (quite technical) reply from Mudita Support yesterday as well however it does not explain how to resolve the condition. I was fortunate enough to have a friendly developer help me previously while I was back at my desk and with access to a computer to troubleshoot but this issue recurred again while out and left me without connectivity on my primary phone. I still do not have connectivity 2+ days later and am still waiting to hear back re a simple consumer fix.
@stevenjc123 I know that you opened a support ticket & I believe @robert_gwarek is helping you resolve this. You’re right it’s a super unusual situation & I think a factory reset could be something you could try. If that doesn’t work, a warranty return.
Let me know if you need me to step in & help at any moment.