Hi there, I cant work out a way to close apps in the background?
2 Likes
Settings > Manage apps > Click on app you want to close > Force Stop
Currently that’s the only way.
4 Likes
ok thanks, hope this gets implemented propperly soon.
1 Like
@pictoys Can you give us some feedback as to how you would like to be able to close the apps?
hey Urszula, on my regular Android device you can just press the right button at the bottom bar and it shows all open apps and you can close them, or close all apps. normally there is not a lot i have running in the background.
6 Likes
Maybe a long press on the circle button could close the current app? I guess it would be more convenient than the standard android process (at least for me).
2 Likes
@pictoys Now, I get it. After you described it, I see what you’re trying to do. In Mudita Kompakt, the screen doesn’t work the same way. You can’t really swipe through screens. I will ask the team if they plan on implementing something to close apps WITHOUT having to manually FORCE CLOSE apps.
7 Likes
yes to switch between the apps that are open or some place where you can see and cose or switch between them. currently you dont see which ones are open unless you go through each.
4 Likes
It used to be a kind of standard to close apps by double tapping [back]. It would be unfortunate to close anything with [home] button, since right now it’s the only way to switch between opened apps.
1 Like
There is a excellent app for that. You can add a home screen shortcut, I have it working with Niagara launcher. Fir other I can’t say about shortcut
More info here
4 Likes
Cannot get KillApps to work. It asks for accessibility service permission to work when I try to start killing. When I push show settings there is nothing there on service permissions. Any idea what I am doing wrong?
1 Like
Could be a way to get a list of apps (swipe in some direction on the home screen?) with x next to them, or long-press an app icon in the menu to get into the Settings → Manage Apps → screen with back button going back to the apps list, not Manage Apps.
1 Like
Did you give the required permission?
1 Like
You can’t access the accessibility permission anymore in 1.2.0 it was removed by the developers.
I still haven’t gotten a reply why, and I don’t know if it’s coming in next update in September.
1 Like
That’s not good. Kill apps is a great app. If they want to keep this disabled the should develop their own app…
1 Like
It’s not just KillApps, it’s for anything that requires accessibility feature. Leave a comment in the topic I linked, maybe they will answer why they’ve done this.
2 Likes
@gezimos I’ve asked our team about this & what the plan is for the future, but I’m still waiting to hear back. I’ve followed up again this morning.
UPDATE Regarding Accessibility Settings:
Accessibility settings are available in 1.2.0 update:
- A user can change Accessibility settings.
- In the Timing controls section, the user can:
- Touch & hold delay
- Time to take action (Accessibility timeout)
- In the Vibration and haptic strength section, the user can:
- Enable and disable calling vibration
- Enable and disable notification vibration
- Enable and disable touch feedback vibration.
- In the System controls section the user can:
- Enable and disable the option of power button end call
- In the Audio adjustment section, the user can:
- Enable and disable mono audio
- Adjust the audio balance between the left and right speakers
@urszula We’re talking about the accessibility permission feature that was taken away just to be replaced with the “accessibility settings” which to me are useless.
Accessibility permission is required from apps to access certain features to control the device.
For example we used to use the “key mapper” app to make shortcuts for the volume button. Tap volume up 3 times and it would open an app of our choosing or it would turn on the flashlight.
This permission is very important for other stuff as well, there’s tons of apps that require it.
For example a lot of users asked for my app to be able to lock the screen when double tapping in white area. And I can’t do this because your devs took the accessibility permission.
Basically when I try to access the accessibility permission instead of popping up the dialog for the user to allow the permission, we get the “accessibility settings”.
This has nothing to do with what we’re asking.
I don’t have a screenshot from 1.1.1 but it basically looks like this. They removed this dialog and instead it just redirect the the “accessibility settings”.
2 Likes
@gezimos I talked to our team & here’s their response:
Thank you for your detailed feedback, for providing the example screenshot, and for so clearly explaining the impact of the missing Accessibility permission dialog. We sincerely apologize for the frustration and disruption this has caused.
We understand how critical this permission is for many applications, including your own launcher and tools like key mappers that add valuable functionality for users. We agree that its current state has broken the ability to use Lock Screen app you presented.
First and most importantly, this was not an intentional change. You are correct that the standard Android permission dialog has been unintentionally broken in the latest update, and for that, we are very sorry.
We have confirmed this behavior and reported it as a bug to our development team. Restoring this menu is now a priority for us.
We immediately looked for a workaround for you. Normally, it should be possible to access these settings via a hidden menu (Developer Options -> Search -> Accessibility -> Accessibility (Display)), but we have tested this and can confirm that this path is also not working correctly at the moment. We are very sorry to say that at this time, there is no immediate way to grant this permission.
While the removal of this specific dialog was a bug, it does highlight a challenge inherent to our design philosophy.
Our phone was designed with minimalism in mind, and to create a more focused experience, some standard Android options were intentionally hidden or streamlined. However, the Accessibility permission is a core function that should not have been affected.
We must also emphasize that this situation demonstrates the risks associated with sideloading applications. While we allow it, apps that require deep system permissions like Accessibility to modify core system settings can cause potential instabilities. The interaction between our streamlined OS and the complex requirements of such apps can lead to unexpected issues. Please be assured that our team is looking into this bug. We understand its importance to you and other advanced users. We are genuinely grateful for your detailed report, as it helps us identify and correct these issues much faster.
6 Likes